[JBossWS] - Re: consume WS error after update to JBossWS 2.0
by gryffin
I have a similar problem. ( Running 4.0.5 with JBossWS2.0.0-native.GA. ) When I remove these two jars from my path, my client won't get out of first gear. It complains of missing xerces libraries.
| Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/xerces/xs/
| XSModel
| at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.buildMetaData
| (JAXWSClientMetaDataBuilder.java:81)
| at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.<init>(ServiceDelegateImpl.j
| ava:131)
| at org.jboss.ws.core.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.
| java:61)
| at javax.xml.ws.Service.<init>(Service.java:83)
| at com.boeing.nmt.client.ws.NetworkLocationService.<init>(NetworkLocationServic
| e.java:45)
| at com.boeing.nmt.client.ws.NLSClient.main(NLSClient.java:23)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063739#4063739
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063739
16 years, 12 months
[JBossWS] - Can I provide SAML Support for JBoss WS Handler with WSS4J?
by BmanT
Hi,
I'm new to the idea of handlers - but I've been tasked to write a handler that can create SAML assertions and from the JBossWS spec status page, I see that it is 0% complete.
On a basic level, from what I understand about handlers, I can write a java class that will extend a *Handler. And then set the handler for the service in the xml file. And as long as the handler is on the classpath - it will be used. So can I package the WSS4J libraries, with my handler class so I can use the functionality? Or maybe just drop the wss4j.jar in the Jboss lib?
Also - I'm writing the handler - but I am not writing the service. Does a handler have to be packaged with the service? Or can it be added as a jar or war file?
The User Guide seems to indicate it has to be within the Service WAR file, but I just want to know if its possible to extract the handler to a separate archive. Why you ask? because another company is tasked with writing the service - but I am tasked with writing the handler - and I'm new to it - so I don't even know if that is possible.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063651#4063651
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063651
16 years, 12 months
[JBossWS] - Latency problem due to small TCP/IP packetsize
by mhohmann
Hello,
we run a couple of webservices as interfaces to some datawarehouse reports. The webservices take some parameters in the soap-request to run the sql-querys against the DB. The result-data is returned as an XML-element in the body of the soap-reponse.
An average reponse is about 130KB. With an MTU around 1500Byte the response should fit in <100 packets, but a network sniff showed that the server generates >10,000 packets for one response. The push-option in the IP-header is also set which instructs the IP-stack to send the paket immediatly before its payload-capacity is filled.
This leads to latency problems because the firewall between the server and the client-applications takes more time to examine the packets. In case of a 130KB response a webservice-request through the firewall takes 10 seconds compare to <2 seconds without the firewall between client and server.
Are there any options to configure the packetsize or some buffer parameters to change the behavior of packet generation (or Sockets) in JBoss, JBossWS or JVM? I really don´t know where to search for a Solution.
I hope someone can help me.
I'm looking foreward for your replies. Thanks in advance.
Michael Hohmann
PS: Sorry for my bad english
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063470#4063470
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063470
16 years, 12 months
[JBossWS] - consume WS error after update to JBossWS 2.0
by M.Schumpa
Hi dear community,
I'm pretty new to the whole JBoss WebService topic and I'm writing a diploma thesis about it. to get startet, I wrote a simple example which consist of a WebService and an Java Client connecting to that Service in order to consume it.
Everything went fine with the JBoss 4.2.0 GA release.
Because I need some of the feature of JAXB 2.0, I upgraded to JBossWS 2.0. I think everything went fine here, because I get the following message in the console while starting JBoss.[ManagedEndpointRegistry] jbossws-native-2.0.0.GA (build=200707051029)
I added the all the jars in %JBOSS_HOME%\client and %JBOSS_HOME%\lib\endorsed to classpath, like I did it while using the JBoss 4.2.0 GA release.
My problem is:
If I try to reach the service with the following code I get an WebServiceException
| URL url = new URL("http://127.0.0.1:8080/BspDog/Examples?wsdl");
| QName qname = new QName("http://dogstapler.com/","ExamplesService");
| Service service = Service.create(url,qname);
| ExamplesEndpoint ee = service.getPort(ExamplesEndpoint.class);
|
The wsdl is reachable at the given location. The first lines of it look like this:
| <definitions name='ExamplesService' targetNamespace='http://dogstapler.com/' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://dogstapler.com/' xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
| <types>
| <xs:schema targetNamespace='http://dogstapler.com/' version='1.0' xmlns:tns='http://dogstapler.com/' xmlns:xs='http://www.w3.org/2001/XMLSchema'>
|
The error thrown by the client while executing the 3rd line of the sample code:
| 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.<init>(Service.java:83)
| at javax.xml.ws.Service.create(Service.java:721)
| at com.dogstapler.client.ClientBspDog3.main(ClientBspDog3.java:31)
| 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.<clinit>(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:66)
| at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:422)
| at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:270)
| at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:103)
| at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:81)
| 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:210)
| at javax.xml.bind.ContextFinder.find(ContextFinder.java:366)
| 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.
M.Schumpa
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063438#4063438
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063438
16 years, 12 months