Testing the case where an ejb3.1 and a web service via metro are deployed in the same war.
Used HelloEJB31(
http://blogs.sun.com/MaheshKannan/entry/ejb_3_1_in_glassfish) and the fromwsdl example of metro. Then combined them into one for a third situation where both the ejb and metro components are active.
1) setup glassfish-v3-prelude-b27, added ejb and metro with the update tool and it all came up successfully with the admin console up successfully too.
2) HelloEJB31 built, deployed and ran successfully.
3) fromwsdl built, deployed and ran successfully.
4) Started with a copy of HelloEJB31 and pulled the web service code from the fromwsdl example and put it into the modified HelloEJB31 I called HelloEJB31WithWS(See attached copy). Attempted to deploy HelloEJB31WithWS and get a log showing:
[code]
[#|2008-10-02T20:39:36.810-0400|SEVERE|GlassFish10.0|global|_ThreadID=20;_ThreadName=Thread-4;|Exception in processing @Stateless|#]
[#|2008-10-02T20:39:36.810-0400|FINE|GlassFish10.0|javax.enterprise.system.util|_ThreadID=20;_ThreadName=Thread-4;ClassName=null;MethodName=null;|No local string for enterprise.deployment.archivist.annotationprocessingfailed|#]
[#|2008-10-02T20:39:36.810-0400|SEVERE|GlassFish10.0|javax.enterprise.system.tools.deployment|_ThreadID=20;_ThreadName=Thread-4;|Annotations processing failed for file:/C:/glassfishv3-prelude/glassfish/domains/domain1/applications/HelloEJB31WithWS/|#]
[#|2008-10-02T20:39:36.873-0400|SEVERE|GlassFish10.0|global|_ThreadID=20;_ThreadName=Thread-4;|Exception in processing @Stateless|#]
[#|2008-10-02T20:39:36.888-0400|FINE|GlassFish10.0|javax.enterprise.system.util|_ThreadID=20;_ThreadName=Thread-4;ClassName=null;MethodName=null;|No local string for enterprise.deployment.archivist.annotationprocessingfailed|#]
[#|2008-10-02T20:39:36.888-0400|SEVERE|GlassFish10.0|javax.enterprise.system.tools.deployment|_ThreadID=20;_ThreadName=Thread-4;|Annotations processing failed for file:/C:/glassfishv3-prelude/glassfish/domains/domain1/applications/HelloEJB31WithWS/|#]
[#|2008-10-02T20:39:36.904-0400|SEVERE|GlassFish10.0|global|_ThreadID=20;_ThreadName=Thread-4;|Exception in processing @Stateless|#]
[#|2008-10-02T20:39:36.904-0400|FINE|GlassFish10.0|javax.enterprise.system.util|_ThreadID=20;_ThreadName=Thread-4;ClassName=null;MethodName=null;|No local string for enterprise.deployment.archivist.annotationprocessingfailed|#]
[#|2008-10-02T20:39:36.904-0400|SEVERE|GlassFish10.0|javax.enterprise.system.tools.deployment|_ThreadID=20;_ThreadName=Thread-4;|Annotations processing failed for file:/C:/glassfishv3-prelude/glassfish/domains/domain1/applications/HelloEJB31WithWS/|#]
[#|2008-10-02T20:39:36.904-0400|SEVERE|GlassFish10.0|javax.enterprise.system.core|_ThreadID=20;_ThreadName=Thread-4;|Exception while invoking class org.glassfish.webservices.WebServicesDeployer prepare method
java.lang.RuntimeException
at org.glassfish.webservices.WebServicesDeployer.prepare(WebServicesDeployer.java:131)
at com.sun.enterprise.v3.server.ApplicationLifecycle.prepare(ApplicationLifecycle.java:454)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:180)
...
[/code]
Now to check if the addition of the web service is incorrect I then did the following:
5) Commented out the Stateless annotation in the HelloEJB and its usage in HelloServlet. Deployed successfully and then tested the fromwsdl web service with the client in the fromwsdl project successfully.
By commenting out a few Stateless annotation lines, the web service works; open back up the Stateless annotation lines and the above deployment issue occurs.
[Message sent by forum member 'rimartin7' (rimartin7)]
http://forums.java.net/jive/thread.jspa?messageID=303627