[JBossWS] - invalid timestamps
by victorstar
Using jbossws 3.0.1 native for both server and client.
Ran into this problem when server and client running on different machines - even slightest difference in time makes the communication impossible due to "invalid timestamp.... message claims to be created before..." exceptions.
Makes we wonder - slight time differences between machines is a pretty common thing. And looks like jbossws is not usable in this situations? So how do you people use it in production?
Or am I missing something here (I truly hope that I do!).
I know 3.0.2 should have support for additional parameters in the config files to deal with this issue. But it's not available yet. Any ETA for 3.0.2 release? How stable/production ready are the current SVN snapshots?
Also I had a hard time figuring out the exact path of the current native branch. Any help here would be appreciated.
Meanwhile I see no other solutions but patching 3.0.1 manually. Are there any other solutions/workarounds?
I've found one thread on this board discussing this issue but no other suggestions other than waiting for 3.0.2 or patching 3.0.1.
Any help would be greatly appreciated!
Thanks!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155715#4155715
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155715
16 years, 7 months
[JBossWS] - a problem when call web service using web service client
by Grid.Qian
Hi guys,
Now I focus on extending wtp web service framework to support JBoss WS. To do this task, we must firstly create a dynamic web project and then generate web service or web service client codes. So far I can create web service and web service client. For user's convenience I generate a client sample to call web service.
Because I use the WTP dynamic project and jboss server, when the project is created, all the jars that are from jboss server lib folder and client folder are added to project classpath. When I run the web service client sample to call web service, a issue occurs.
And after I google this issue, I found a same issue. I know the issue will be fixed by removing jaxws-rt.jar and jaxws-tools.jar from classpath. But this looks like jaxws in JBoss is "incomplete" or something, and I want to know why this issue occurs?
the link:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063438#4063438
the client sample codes:
System.out.println("***********************");
System.out.println("Create Web Service Client...");
HelloWorldService service1 = new HelloWorldService();
System.out.println("Create Web Service...");
HelloWorld port1 = service1.getHelloWorldPort();
System.out.println("Create Web Service Operation...");
System.out.println("Server said: " + port1.sayHello());
System.out.println("***********************");
the issue:
Exception in thread "main" javax.xml.ws.WebServiceException: Unable to load Provider: Failed to load javax.xml.ws.spi.Provider: com.sun.xml.ws.spi.ProviderImpl
at javax.xml.ws.spi.Provider.provider(Provider.java:98)
at javax.xml.ws.Service.(Service.java:83)
at org.example.www.helloworld.HelloWorldService.(HelloWorldService.java:40)
at org.example.www.helloworld.clientsample.ClientSample.main(ClientSample.java:10)
Caused by: java.lang.IllegalStateException: Failed to load javax.xml.ws.spi.Provider: com.sun.xml.ws.spi.ProviderImpl
at javax.xml.ws.spi.ProviderLoader.loadProvider(ProviderLoader.java:96)
at javax.xml.ws.spi.Provider.provider(Provider.java:90)
... 3 more
Caused by: java.lang.ExceptionInInitializerError
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at java.lang.Class.newInstance0(Class.java:350)
at java.lang.Class.newInstance(Class.java:303)
at javax.xml.ws.spi.ProviderLoader.loadProvider(ProviderLoader.java:91)
... 4 more
Caused by: javax.xml.ws.WebServiceException: Error creating JAXBContext for W3CEndpointReference.
at com.sun.xml.ws.spi.ProviderImpl.getEPRJaxbContext(ProviderImpl.java:188)
at com.sun.xml.ws.spi.ProviderImpl.(ProviderImpl.java:65)
... 11 more
Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 2 counts of IllegalAnnotationExceptions
Two classes have the same XML type name "address". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at com.sun.xml.ws.developer.MemberSubmissionEndpointReference$Address
at public com.sun.xml.ws.developer.MemberSubmissionEndpointReference$Address com.sun.xml.ws.developer.MemberSubmissionEndpointReference.addr
at com.sun.xml.ws.developer.MemberSubmissionEndpointReference
this problem is related to the following location:
at javax.xml.ws.wsaddressing.W3CEndpointReference$Address
at private javax.xml.ws.wsaddressing.W3CEndpointReference$Address javax.xml.ws.wsaddressing.W3CEndpointReference.address
at javax.xml.ws.wsaddressing.W3CEndpointReference
Two classes have the same XML type name "elements". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at com.sun.xml.ws.developer.MemberSubmissionEndpointReference$Elements
at public com.sun.xml.ws.developer.MemberSubmissionEndpointReference$Elements com.sun.xml.ws.developer.MemberSubmissionEndpointReference.referenceProperties
at com.sun.xml.ws.developer.MemberSubmissionEndpointReference
this problem is related to the following location:
at javax.xml.ws.wsaddressing.W3CEndpointReference$Elements
at private javax.xml.ws.wsaddressing.W3CEndpointReference$Elements javax.xml.ws.wsaddressing.W3CEndpointReference.referenceParameters
at javax.xml.ws.wsaddressing.W3CEndpointReference
at com.sun.xml.bind.v2.runtime.IllegalAnnotationsException$Builder.check(IllegalAnnotationsException.java:102)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:438)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.(JAXBContextImpl.java:286)
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:117)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:211)
at javax.xml.bind.ContextFinder.find(ContextFinder.java:372)
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:522)
at com.sun.xml.ws.spi.ProviderImpl.getEPRJaxbContext(ProviderImpl.java:186)
... 12 more
I'm looking foreward for your replies. Thanks in advance
Grid
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155257#4155257
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155257
16 years, 7 months
[JBossWS] - Error while generating annotated Java classes using wsconsum
by sheshi
Hi All,
I am trying to generate annotated Java classes/sources using wsconsume tool (top down approach) for WS-Trust WSDL. Everytime I run the tool, I get the following exception.
E:\java\jboss-4.2.2.GA\bin>wsconsume -v -k http://docs.oasis-open.org/ws-sx/ws-t
rust/200512/ws-trust-1.3.wsdl
JBossWS-Native stack deployed
parsing WSDL...
[ERROR] Failed to read the WSDL document: http://docs.oasis-open.org/ws-sx/ws-tr
ust/200512/ws-trust-1.3.wsdl, because 1) could not find the document; /2) the do
cument could not be read; 3) the root element of the document is not <wsdl:defin
itions>.
unknown location
Failed to parse the WSDL.
Failed to invoke WsImport
java.lang.IllegalStateException: WsImport invocation failed. Try the verbose swi
tch for more information
at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumer
Impl.java:220)
at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:2
23)
at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:81)
I tried accessing the WSDL locally and it failed with an same kinda exception for a XSD file the WSDL refers to.
E:\java\jboss-4.2.2.GA\bin>wsconsume -v -k ws-trust-1.3.wsdl
JBossWS-Native stack deployed
parsing WSDL...
[ERROR] Failed to read the WSDL document: http://docs.oasis-open.org/ws-sx/ws-tr
ust/200512/ws-trust-1.3.xsd, because 1) could not find the document; /2) the doc
ument could not be read; 3) the root element of the document is not <wsdl:defini
tions>.
unknown location
Failed to parse the WSDL.
Failed to invoke WsImport
java.lang.IllegalStateException: WsImport invocation failed. Try the verbose swi
tch for more information
at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumer
Impl.java:220)
at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:2
23)
at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:81)
E:\java\jboss-4.2.2.GA\bin>
I would appreciate if someone help me with this issue.
Thanks in advance
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155158#4155158
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155158
16 years, 7 months
[JBossWS] - Class javax/xml/rpc/ParameterMode violates loader constraint
by leorr
I am encountering the following error when trying to invoke a web service.
using Jboss 4.2.2 and jbossws-native-2.0.1.GA webservices.
"Class javax/xml/rpc/ParameterMode violates loader constraints"
Has anyone got an idea?
thanks,
org.apache.jasper.JasperException: javax.servlet.ServletException: java.lang.LinkageError: Class javax/xml/rpc/ParameterMode violates loader constraints
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:521)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:397)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:336)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
root cause
javax.servlet.ServletException: java.lang.LinkageError: Class javax/xml/rpc/ParameterMode violates loader constraints
org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:850)
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:779)
org.apache.jsp.views.jbossws_jsp._jspService(jbossws_jsp.java:183)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:336)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
root cause
java.lang.LinkageError: Class javax/xml/rpc/ParameterMode violates loader constraints
java.lang.ClassLoader.defineClass1(Native Method)
java.lang.ClassLoader.defineClass(ClassLoader.java:620)
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1814)
org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:872)
org.jboss.web.tomcat.service.WebAppClassLoader.findClass(WebAppClassLoader.java:139)
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1325)
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1204)
java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
java.lang.Class.forName0(Native Method)
java.lang.Class.forName(Class.java:164)
$Proxy255.(Unknown Source)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155079#4155079
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155079
16 years, 7 months