11:25 a.m.
Antoine Brun [http://community.jboss.org/people/abr] created the discussion
"Re: jboss6 final and jbossws 3.4.0"
To view the discussion, visit: http://community.jboss.org/message/578778#578778
--------------------------------------------------------------
ok, I'll try with jbossws native 3.4.1 as soon as it is available.
in the mean time, I tried to declare the handler like that:
@HandlerChain(file = "handler-chain.xml")
and I get:
DEPLOYMENTS IN ERROR:
Deployment "vfs:///home/abr/workspace/api/dist/ubi-api.ear" is in error due to
the following reason(s): javax.xml.ws.WebServiceException: Could not find the handler
configuration file handler-chain.xml specified by @HandlerChain annotation
so next I tried:
@HandlerChain(file = "/handler-chain.xml")
and I get:
DEPLOYMENTS IN ERROR:
Deployment "vfs:///home/abr/workspace/api/dist/ubi-api.ear" is in error due to
the following reason(s): javax.xml.ws.WebServiceException: false false Element <?xml
version="1.0" encoding="utf-8"?><handler-config>
<handler-chain>
<handler-chain-name>SoapHandler</handler-chain-name>
<handler>
<handler-name>SoapMessageValidationHandler</handler-name>
<handler-class>com.ubiqube.api.ws.soapHandler.MessageValidationSoapHandler</handler-class>
</handler>
</handler-chain>
</handler-config> is not a valid root element in file
vfs:/home/abr/workspace/api/dist/ubi-api.ear/ubi-api-ejb.jar/handler-chain.xml
So with CXF 3.4.1the "/" must be there, wheras with native 3.4.0 it was not
necessary (note that I did not try with the / and native 3.4.0).
Do you know when the jbossws native 3.4.1 will be available for download?
Another question, maybe you can point me to some doc: why choosing jbossws CXF against
native? Is it a certification issue?
Thank you for your time and answer
Antoine
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/578778#578778]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
2:28 p.m.
Alessio Soldano [http://community.jboss.org/people/alessio.soldano%40jboss.com] created
the discussion
"Re: jboss6 final and jbossws 3.4.0"
To view the discussion, visit: http://community.jboss.org/message/578807#578807
--------------------------------------------------------------
OK, here you go: http://jboss.org/jbossws/downloads http://jboss.org/jbossws/downloads
(JBossWS 3.4.1 binary downloads, check the Install.txt as usual for installation
information)
Regarding why using the CXF based stack instead of the Native one, right compliance with
standards is a reason, for instance Apache CXF is JAXWS 2.2 compliant (we contributed to
that) and JBossWS-CXF included in JBoss AS 6 is passing the webservice related part of
JavaEE 6 certification testsuite (btw the ws stuff goes beyond the EE6 web profile).
Better support for WS-* is another reason. Performance is also better right now with
JBossWS-CXF.
Well try to repdoruce your @HandlerChain issue soon.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/578807#578807]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4:05 a.m.
Antoine Brun [http://community.jboss.org/people/abr] created the discussion
"Re: jboss6 final and jbossws 3.4.0"
To view the discussion, visit: http://community.jboss.org/message/578927#578927
--------------------------------------------------------------
Alessio Soldano wrote:
OK, here you go: http://jboss.org/jbossws/downloads http://jboss.org/jbossws/downloads
(JBossWS 3.4.1 binary downloads, check the Install.txt as usual for installation
information)
I've downloaded the binary.
First I installed it in my jboss 6 install.
Then I tried to deploy my application.
First the EJB seemed to be correctly deployed:
...
10:45:32,798 INFO [org.jboss.ejb3.instantiator.deployer.BeanInstantiatorDeployerBase]
Installed org.jboss.ejb3.instantiator.impl.Ejb31SpecBeanInstantiator@c6bb9a into MC at
org.jboss.ejb.bean.instantiator/ubi-api/ubi-api-ejb/ConfProfileBean
1
...
then the WSDL:
...
10:45:41,224 INFO [org.jboss.wsf.stack.jbws.WSDLFilePublisher] WSDL published to:
file:/home/abr/workspace/jboss-6.0.0.Final/server/ubiqube/data/wsdl/ubi-api.ear/ubi-api-ejb.jar/VpnService.wsdl
...
then the endpoints:
...
10:45:42,242 INFO [org.jboss.wsf.framework.management.DefaultEndpointRegistry] register:
jboss.ws:context=webapi,endpoint=FirewallBean
...
then I get
...
10:45:42,456 INFO [org.jboss.ejb3.deployers.JBossASKernel] Created KernelDeployment for:
ubi-api-ejb.jar
10:45:42,460 INFO [org.jboss.ejb3.deployers.JBossASKernel] installing bean:
jboss.j2ee:ear=ubi-api.ear,jar=ubi-api-ejb.jar,name=VoipProfileBean,service=EJB3
10:45:42,460 INFO [org.jboss.ejb3.deployers.JBossASKernel] with dependencies:
10:45:42,460 INFO [org.jboss.ejb3.deployers.JBossASKernel] and demands:
10:45:42,460 INFO [org.jboss.ejb3.deployers.JBossASKernel]
jboss-injector:topLevelUnit=ubi-api.ear,unit=ubi-api-ejb.jar,bean=VoipProfileBean;
Required: Described
10:45:42,460 INFO [org.jboss.ejb3.deployers.JBossASKernel]
jboss.ejb:service=EJBTimerService; Required: Described
10:45:42,460 INFO [org.jboss.ejb3.deployers.JBossASKernel]
jboss-switchboard:appName=ubi-api,module=ubi-api-ejb; Required: Create
10:45:42,461 INFO [org.jboss.ejb3.deployers.JBossASKernel] and supplies:
10:45:42,461 INFO [org.jboss.ejb3.deployers.JBossASKernel]
jndi:VoipProfileBean/remote
10:45:42,461 INFO [org.jboss.ejb3.deployers.JBossASKernel]
Class:com.ubiqube.api.interfaces.deprecated.profil.voip.VoipProfileService
10:45:42,461 INFO [org.jboss.ejb3.deployers.JBossASKernel]
jndi:ubi-api/VoipProfileBean/remote-com.ubiqube.api.interfaces.deprecated.profil.voip.VoipProfileService
10:45:42,466 INFO [org.jboss.ejb3.deployers.JBossASKernel] Added
bean(jboss.j2ee:ear=ubi-api.ear,jar=ubi-api-ejb.jar,name=VoipProfileBean,service=EJB3) to
KernelDeployment of: ubi-api-ejb.jar
..
10:45:46,121 INFO [org.jboss.ejb3.proxy.impl.jndiregistrar.JndiSessionRegistrarBase]
Binding the following Entries in Global JNDI:
CDRBean/remote - EJB3.x Default Remote Business Interface
ubi-api/CDRBean/remote-com.ubiqube.api.interfaces.profile.voip.CDRService - EJB3.x
Remote Business Interface
10:45:46,121 WARN [org.jboss.ejb3.TimerServiceContainer] EJBTHREE-2193: using deprecated
TimerServiceFactory for restoring timers
*And then it fails with*
10:45:46,133 INFO [org.jboss.ejb3.session.SessionSpecContainer] Stopping
jboss.j2ee:ear=ubi-api.ear,jar=ubi-api-ejb.jar,name=CDRBean,service=EJB3
10:45:46,137 INFO [org.jboss.ejb3.EJBContainer] STOPPED EJB:
com.ubiqube.api.ejb.profile.voip.CDRBean ejbName: CDRBean
10:45:46,140 INFO [org.jboss.ejb3.session.SessionSpecContainer] Stopping
jboss.j2ee:ear=ubi-api.ear,jar=ubi-api-ejb.jar,name=VpnWS,service=EJB3
10:45:46,141 INFO [org.jboss.ejb3.EJBContainer] STOPPED EJB:
com.ubiqube.api.ws.endpoints.vpn.VpnWS ejbName: VpnWS
10:45:46,145 INFO [org.jboss.ejb3.session.SessionSpecContainer] Stopping
jboss.j2ee:ear=ubi-api.ear,jar=ubi-api-ejb.jar,name=SecurityBean,service=EJB3
10:45:46,146 INFO [org.jboss.ejb3.EJBContainer] STOPPED EJB:
com.ubiqube.api.ejb.common.security.SecurityBean ejbName: SecurityBean
10:45:46,151 WARN [org.jboss.kernel.plugins.dependency.StartStopLifecycleAction] Error
during stop for
jboss-switchboard:appName=ubi-api,module=ubi-api-ejb,name=ConfigurationVariableWS:
javax.naming.NameNotFoundException: ORB not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:771) [:5.0.5.Final]
at org.jnp.server.NamingServer.getBinding(NamingServer.java:779) [:5.0.5.Final]
at org.jnp.server.NamingServer.unbind(NamingServer.java:349) [:5.0.5.Final]
at org.jnp.interfaces.NamingContext.unbind(NamingContext.java:873) [:5.0.5.Final]
at org.jboss.util.naming.Util.unbind(Util.java:151)
[jboss-common-core.jar:2.2.17.GA]
at org.jboss.util.naming.Util.unbind(Util.java:141)
[jboss-common-core.jar:2.2.17.GA]
at
org.jboss.switchboard.mc.SwitchBoardImpl.unbindFromRelevantContext(SwitchBoardImpl.java:303)
[:1.0.0-alpha-15]
at org.jboss.switchboard.mc.SwitchBoardImpl.stop(SwitchBoardImpl.java:102)
[:1.0.0-alpha-15]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_23]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[:1.6.0_23]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[:1.6.0_23]
at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_23]
I have no idea what this ORB is...
The full deployement log (server.log) is attached to the message.
So I tried to run the jbossws 3.4.1 included tests: ant tests.
They all failed (attached the tests reports)
Antoine
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/578927#578927]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4:14 a.m.
Alessio Soldano [http://community.jboss.org/people/alessio.soldano%40jboss.com] created
the discussion
"Re: jboss6 final and jbossws 3.4.0"
To view the discussion, visit: http://community.jboss.org/message/578929#578929
--------------------------------------------------------------
Hi,
regarding the jbossws testsuite failures, that seems like an issue with logging, please
try commenting out the following line in tests/ant-import/build-testsuite.xml :
<sysproperty key="java.util.logging.manager"
value="org.jboss.wsf.common.logging.JDKLogManager"/>
Regarding the "ORB" issue, that does not tell me a lot too unfortunately and
seems to be an EJB3 issue, if any. Btw, that's a WARN during undeploy, am I wrong?
Might not be a real issue after all, perhaps you can try posting on the ejb3 forum about
that.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/578929#578929]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4:35 a.m.
Alessio Soldano [http://community.jboss.org/people/alessio.soldano%40jboss.com] created
the discussion
"Re: jboss6 final and jbossws 3.4.0"
To view the discussion, visit: http://community.jboss.org/message/578934#578934
--------------------------------------------------------------
Ah, regarding the
</handler-config> is not a valid root element in file
vfs:/home/abr/workspace/api/dist/ubi-api.ear/ubi-api-ejb.jar/META-INF/soapHandler/handler-chain.xml
....
exception I see in your server log, are you using the proper handler chain descriptor
format? Check
http://anonsvn.jboss.org/repos/jbossws/framework/tags/jbossws-framework-3...
http://anonsvn.jboss.org/repos/jbossws/framework/tags/jbossws-framework-3...
for an example.
Also, at first sight you seems to have issues with app already installed, when having
deployment failures, consider restarting the app server before re-trying the deployment,
as you might end up in an inconsistent status.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/578934#578934]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4:54 a.m.
Antoine Brun [http://community.jboss.org/people/abr] created the discussion
"Re: jboss6 final and jbossws 3.4.0"
To view the discussion, visit: http://community.jboss.org/message/578936#578936
--------------------------------------------------------------
Alessio Soldano wrote:
Ah, regarding the
> </handler-config> is not a valid root element in file
vfs:/home/abr/workspace/api/dist/ubi-api.ear/ubi-api-ejb.jar/META-INF/soapHandler/handler-chain.xml
....
>
exception I see in your server log, are you using the proper handler chain descriptor
format? Check
http://anonsvn.jboss.org/repos/jbossws/framework/tags/jbossws-framework-3...
http://anonsvn.jboss.org/repos/jbossws/framework/tags/jbossws-framework-3...
for an example.
I think that those traces are just remains from a previous test that failed.
The handler-chain seems to be correctly parsed with jbossws native 3.4.1 and I'm
declaring it like that:
@HandlerChain(file = "handler-chain.xml")
Attached are logs from a single boot/ear deploy sequence (I'm not undeploying the ear
and I'm using twiddle/JMX).
By the way, is there a clean way to uninstall the jbossws module from the jboss install?
I'd like to check my EJB deployment without the web service module
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/578936#578936]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
5:07 a.m.
Alessio Soldano [http://community.jboss.org/people/alessio.soldano%40jboss.com] created
the discussion
"Re: jboss6 final and jbossws 3.4.0"
To view the discussion, visit: http://community.jboss.org/message/578943#578943
--------------------------------------------------------------
AFAICS, the "ORB not found" exceptions begin just after:
2011-01-05 11:40:45,432 INFO
[org.jboss.web.tomcat.service.deployers.TomcatDeployment] (RMI TCP
Connection(4)-10.11.1.112) deploy, ctxPath=/webapi2
2011-01-05 11:40:45,449 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment]
(RMI TCP Connection(4)-10.11.1.112) undeploy, ctxPath=/webapi2
which kind of suggest me the app is beeing undeployed. Also, all the exceptions are
"... during stop for...".
Regarding cleaning removing the webservice module from the app server, that's not easy
with AS 6 (things are going to change here on AS 7). The only solution I can think about
is creating your own server profile without the webservice stuff, something in the middle
of "minimal" and "default" profile. But that's not straightforward
for sure.
It's probably faster for you to comment out the @WebServices annotations (assuming
you're using EJB3 endpoints only) in your sources.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/578943#578943]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
5:16 a.m.
Antoine Brun [http://community.jboss.org/people/abr] created the discussion
"Re: jboss6 final and jbossws 3.4.0"
To view the discussion, visit: http://community.jboss.org/message/578948#578948
--------------------------------------------------------------
I think that I got it now:
My EJB that are WS endpoints have the following annotation:
@WebContext(authMethod = "BASIC", contextRoot = "webapi",
urlPattern = "/ConfigurationVariableWS")
the context root was to override the default context root which is something like ubi-ejb
(whatever...)
And in the application context I also had
<module>
<web>
<web-uri>ubi-api.war</web-uri>
<context-root>webapi</context-root>
</web>
</module>
I can't remember exactly why at that time I needed to do that. I hope that I can get
rid of this, more tests will tell.
What is not intuitive at all is the error message...
Anyway, my WS seem to deploy correctly now, I'll do some more tests.
I hope that the handler-chain issue will be solved in a future jbossws CXF release as
I'd rather use CXF than change jboss default packaging.
Thank you for you time,
Antoine
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/578948#578948]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
5056
days inactive
5057
days old
7 comments
2 participants
participants (2)
-
Alessio Soldano -
Antoine Brun