tag:blogger.com,1999:blog-6868595312516376692.post4462788077667665302..comments2023-11-23T09:33:53.598+01:00Comments on Enterprise Software Development with Java: Scaling up to WebLogic 12c Server from GlassFish 3.xMarkus Eiselehttp://www.blogger.com/profile/16195673592300911244noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-6868595312516376692.post-70062952153168356482012-01-30T10:23:39.361+01:002012-01-30T10:23:39.361+01:00Hi Ed,
as far as I know, this shouldn't happe...Hi Ed,<br /><br />as far as I know, this shouldn't happen. If the original GF descriptors are in place the WLS ones should be ignored. If you have a simple example, go ahead and file a bug in the GF JIRA!<br /><br />Rgds,<br />MMarkus Eiselehttps://www.blogger.com/profile/16195673592300911244noreply@blogger.comtag:blogger.com,1999:blog-6868595312516376692.post-37534557401223413042012-01-27T17:34:21.752+01:002012-01-27T17:34:21.752+01:00Is there a way to disable this behaviour in Glassf...Is there a way to disable this behaviour in Glassfish?<br />We have an application that we support on Glassfish2, Websphere are Weblogic. We generate the deployment descriptors automatically. Now that we are adding support for Glassfish3, it is reading not only the files we intend but also the weblogic ones - and complaining! For example, weblogic-webservices.xml contains:<br /> JAXWS<br />but Glassfish3 reads that and grumbles:<br /><br />[#|2012-01-27T15:31:00.121+0000|SEVERE|glassfish3.1.1|javax.enterprise.webservices.org.glassfish.webservices|_ThreadID=17;_ThreadName=Thread-2;|WS00057: WebService type is declared as JAXWS but should be either has a JAX-WS or JAX-RPC|#]<br /><br />I imagine that if we "fix" that to "JAX-WS" then Weblogic will grumble...<br /><br />This is a nice idea but sometimes it's easier to keep things separate. At least the ability to disable the feature would be appreciated.Edhttps://www.blogger.com/profile/05627054821545935055noreply@blogger.comtag:blogger.com,1999:blog-6868595312516376692.post-65290825083915534692011-12-13T14:12:42.375+01:002011-12-13T14:12:42.375+01:00Hi Alexis,
Thanks for the comment. As I stated in...Hi Alexis,<br /><br />Thanks for the comment. As I stated in the text, GF knows even more about WLS than the other way round. But you would agree, that WLS has some unique productive management features that makes it more likely to scale up for applications, than scale down? <br />I would be happy to read some official statements about the conversion of the platform and the desired usage scenarios beginning with development up to high available production environments. Last sentence explicitly NOT stating, that GF wouldn't be able to do it!!<br /><br />Thanks,<br />..OO(and sorry for pushing at that corner. Orcl is still doing too less to address the explicit values of both servers, if you ask me)<br />MarkusMarkus Eiselehttps://www.blogger.com/profile/16195673592300911244noreply@blogger.comtag:blogger.com,1999:blog-6868595312516376692.post-540772659664418162011-12-13T14:06:28.193+01:002011-12-13T14:06:28.193+01:00You'll note that GlassFish already has support...You'll note that GlassFish already has support for WebLogic deployment descriptors. This enables application portability across both containers.Anonymousnoreply@blogger.com