From do-not-reply at jboss.com  Sun Jun  1 03:43:19 2008
From: do-not-reply at jboss.com (leorr)
Date: Sun, 1 Jun 2008 03:43:19 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Invoking Web service from in a JSP.
Message-ID: <21500201.1212306200001.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am using the jbossws-native-2.0.1.GA version, and succesfully compiled and executed the samples (used wsconsume/wsrunclient).
I have created a war file for the web service and also a jar for the Web service Client, and deployed both on JBoss.

I want to invoke the web service within a JSP file, could some please help me with a source file and and instructions...

thanks in advance,
Leor

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154859#4154859

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154859


From asoldano at redhat.com  Sun Jun  1 05:49:02 2008
From: asoldano at redhat.com (Alessio Soldano)
Date: Sun, 01 Jun 2008 11:49:02 +0200
Subject: [jbossws-users] JBoss clustering with webservices
In-Reply-To: <5bc4c4570805301536k3770b352od1d7f816ba33adfc@mail.gmail.com>
References: <5bc4c4570805301517w1d3b66d0s2c0180d12ed997fe@mail.gmail.com>
	<5bc4c4570805301536k3770b352od1d7f816ba33adfc@mail.gmail.com>
Message-ID: <4842708E.2000202@redhat.com>

Hi,
something like LVS (http://www.linuxvirtualserver.org/) might be the 
solution for you. Perhaps refer the documentation page 
(http://www.linuxvirtualserver.org/Documents.html) for available 
configurations matching your requirements.
Cheers
Alessio Soldano

Leandro Sales ha scritto:
> Hi. I'm implementing cluster of nodes with jboss. Each node provides a
> Webservice implemented with EJB (@Stateless, @Webservice and
> @Clustered). I deployed the webservice .jar bean into the
> server/all/farm directory and hence the webservice is replicated among
> the nodes of the cluster. How can I provide the load balancing for
> these nodes considering the to points listened below:
>
> 1 - The webservice consumer needs to point to a unique address (the
> interceptor, which is responsible to select a node and forward to
> request to it). How to define this interceptor?
>
> 2 - Once one node is selected, I don't want that the node response
> pass back through the interceptor (like documentations explains),
> instead I want the webservice response be directly sent to the client.
> Is this possible?
>
> Thank you. All points/suggestion are greatfully accepted.
>
> Best regards.
>
> -Leandro
> _______________________________________________
> jbossws-users mailing list
> jbossws-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossws-users
>   



From leandroal at gmail.com  Sun Jun  1 09:39:22 2008
From: leandroal at gmail.com (Leandro Sales)
Date: Sun, 1 Jun 2008 10:39:22 -0300
Subject: [jbossws-users] JBoss clustering with webservices
In-Reply-To: <4842708E.2000202@redhat.com>
References: <5bc4c4570805301517w1d3b66d0s2c0180d12ed997fe@mail.gmail.com>
	<5bc4c4570805301536k3770b352od1d7f816ba33adfc@mail.gmail.com>
	<4842708E.2000202@redhat.com>
Message-ID: <5bc4c4570806010639r45010f42ucb398b094370fdf0@mail.gmail.com>

Hello Alessio,
   thank you for the answer. Is LVS project still maintained? The
latest release for linux kernel is for 2.6.10, but the latest stable
Linux kernel is 2.6.25-4. Considering just my first question in the
previous e-mail (The webservice consumer needs to point to a unique
address (the interceptor, which is responsible to select a node and
forward to request to it). How to define this interceptor?), is it
possible to implement this using JBoss + Webservice even though the
response pass back through the Interceptor? If yes, how can I
implement the client cluster interceptor since it is not possible to
get the Webservice reference via JNDI? Or is that a way to do this?

Thank you,
Leandro.

On Sun, Jun 1, 2008 at 6:49 AM, Alessio Soldano <asoldano at redhat.com> wrote:
> Hi,
> something like LVS (http://www.linuxvirtualserver.org/) might be the
> solution for you. Perhaps refer the documentation page
> (http://www.linuxvirtualserver.org/Documents.html) for available
> configurations matching your requirements.
> Cheers
> Alessio Soldano
>
> Leandro Sales ha scritto:
>>
>> Hi. I'm implementing cluster of nodes with jboss. Each node provides a
>> Webservice implemented with EJB (@Stateless, @Webservice and
>> @Clustered). I deployed the webservice .jar bean into the
>> server/all/farm directory and hence the webservice is replicated among
>> the nodes of the cluster. How can I provide the load balancing for
>> these nodes considering the to points listened below:
>>
>> 1 - The webservice consumer needs to point to a unique address (the
>> interceptor, which is responsible to select a node and forward to
>> request to it). How to define this interceptor?
>>
>> 2 - Once one node is selected, I don't want that the node response
>> pass back through the interceptor (like documentations explains),
>> instead I want the webservice response be directly sent to the client.
>> Is this possible?
>>
>> Thank you. All points/suggestion are greatfully accepted.
>>
>> Best regards.
>>
>> -Leandro
>> _______________________________________________
>> jbossws-users mailing list
>> jbossws-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbossws-users
>>
>
>



-- 
Leandro Melo de Sales
Pervasive and Embedded Computing Laboratory
Computer Science MSc.
BRisa and E-Phone Projects Manager
Network Admin @ http://embedded.ufcg.edu.br/indexen.html
+55 83 3310-1404 (extension 208)

http://www.leandrosales.com/


From do-not-reply at jboss.com  Mon Jun  2 09:58:59 2008
From: do-not-reply at jboss.com (communityman)
Date: Mon, 2 Jun 2008 09:58:59 -0400 (EDT)
Subject: [jbossws-users] 
	[JBossWS] - axis 1, jboss 4.0.4, base64deserializer, linux, windows
Message-ID: <1328600.1212415139211.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello community,

I'm facing a strange issue while using a webservice deployed in jboss.
In windows environnement, i mean locally, all works fine.
In axis.log, i've :

2008-06-02 12:23:14 DEBUG [DeserializationContextImpl] Enter: DeserializationContextImpl::startElement(, identifiant)
2008-06-02 12:23:14 DEBUG [ProjectResourceBundle] org.apache.axis.i18n.resource::handleGetObject(pushHandler00)
2008-06-02 12:23:14 DEBUG [DeserializationContextImpl] Pushing handler org.apache.axis.encoding.ser.Base64Deserializer at 1a8c22b

But in linux, read 4, i've :
2008-06-02 12:22:36 DEBUG [DeserializationContextImpl] Enter: DeserializationContextImpl::startElement(, identifiant)
2008-06-02 12:22:36 DEBUG [ProjectResourceBundle] org.apache.axis.i18n.resource::handleGetObject(cantHandle00)
2008-06-02 12:22:36 DEBUG [ProjectResourceBundle] org.apache.axis.i18n.resource::handleGetObject(toAxisFault00)
2008-06-02 12:22:36 DEBUG [enterprise] Mapping Exception to AxisFault
org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize.

Anyone has an idea ?
thaank you.

Faithfylly

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155052#4155052

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155052


From do-not-reply at jboss.com  Mon Jun  2 10:49:39 2008
From: do-not-reply at jboss.com (leorr)
Date: Mon, 2 Jun 2008 10:49:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Class javax/xml/rpc/ParameterMode
	violates loader constraint
Message-ID: <28286780.1212418179667.JavaMail.jboss@colo-br-02.atl.jboss.com>

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


From do-not-reply at jboss.com  Mon Jun  2 12:17:34 2008
From: do-not-reply at jboss.com (ljgp)
Date: Mon, 2 Jun 2008 12:17:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: No tests for @SchemaValidation
	annotation in 3.0.1 ?
Message-ID: <12806477.1212423454949.JavaMail.jboss@colo-br-02.atl.jboss.com>

A reply would still be appreciated. Does the schema validation feature really work ?

Cheers, Luc.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155118#4155118

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155118


From do-not-reply at jboss.com  Mon Jun  2 17:06:26 2008
From: do-not-reply at jboss.com (sheshi)
Date: Mon, 2 Jun 2008 17:06:26 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Error while generating annotated Java
	classes using wsconsum
Message-ID: <25192206.1212440786774.JavaMail.jboss@colo-br-02.atl.jboss.com>

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


From do-not-reply at jboss.com  Tue Jun  3 05:57:25 2008
From: do-not-reply at jboss.com (Grid.Qian)
Date: Tue, 3 Jun 2008 05:57:25 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - a problem when call web service using
	web service client
Message-ID: <29987516.1212487045102.JavaMail.jboss@colo-br-02.atl.jboss.com>

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


From do-not-reply at jboss.com  Wed Jun  4 02:28:05 2008
From: do-not-reply at jboss.com (siddharth_god)
Date: Wed, 4 Jun 2008 02:28:05 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - SOAP Header Parameters and xml param
	renaming in Doc style E
Message-ID: <1762242.1212560885819.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

  I have a Document literal - wrapped style endpoint. I am using wstools with its config file to generate all necessary artifacts. But even if i mark some of the method parameters in my endpoint with `header="true" mode="IN"` and `xml-name="<some-name-here>"1, the WSDL doesn't seem to reflect any of these. I want to put some of method parameters as part of SOAP header. Thats why i provided that configuration. This works fine if i compile my endpoint as a RPC endpoint, but same thing does not work in Document - literal-wrapped style. Can somebody please point out whats wrong or atleast is it possible to have SOAP header params in case of Document-wrapped style ?

Thanks,
Sid

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155549#4155549

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155549


From do-not-reply at jboss.com  Wed Jun  4 11:00:48 2008
From: do-not-reply at jboss.com (victorstar)
Date: Wed, 4 Jun 2008 11:00:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - invalid timestamps
Message-ID: <13212288.1212591648720.JavaMail.jboss@colo-br-02.atl.jboss.com>

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


From do-not-reply at jboss.com  Wed Jun  4 11:22:54 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Wed, 4 Jun 2008 11:22:54 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: invalid timestamps
Message-ID: <856629.1212592974699.JavaMail.jboss@colo-br-02.atl.jboss.com>

"victorstar" wrote : 
  | Meanwhile I see no other solutions but patching 3.0.1 manually. Are there any other solutions/workarounds?
  | 
Yes, wait few days. 3.0.2 release is coming out soon ;)

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155725#4155725

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155725


From do-not-reply at jboss.com  Wed Jun  4 11:38:41 2008
From: do-not-reply at jboss.com (victorstar)
Date: Wed, 4 Jun 2008 11:38:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: invalid timestamps
Message-ID: <668520.1212593921520.JavaMail.jboss@colo-br-02.atl.jboss.com>

Soon like in a week or so? Can I at least sign up anywhere for new release notifications?

I'm asking because of some project on the track right now and it would be helpful to see if we can wait until 3.0.2 or have to patch 3.0.1 for now

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155736#4155736

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155736


From do-not-reply at jboss.com  Wed Jun  4 11:56:49 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Wed, 4 Jun 2008 11:56:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: invalid timestamps
Message-ID: <28420999.1212595009899.JavaMail.jboss@colo-br-02.atl.jboss.com>

"victorstar" wrote : Soon like in a week or so?
Yes

"victorstar" wrote : Can I at least sign up anywhere for new release notifications?
here


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155744#4155744

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155744


From do-not-reply at jboss.com  Wed Jun  4 11:57:24 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Wed, 4 Jun 2008 11:57:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: invalid timestamps
Message-ID: <20920344.1212595044494.JavaMail.jboss@colo-br-02.atl.jboss.com>

https://lists.jboss.org/mailman/listinfo/jbossws-announce

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155745#4155745

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155745


From do-not-reply at jboss.com  Wed Jun  4 12:07:01 2008
From: do-not-reply at jboss.com (victorstar)
Date: Wed, 4 Jun 2008 12:07:01 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: invalid timestamps
Message-ID: <29130316.1212595621763.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thanks Richard!

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155750#4155750

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155750


From do-not-reply at jboss.com  Thu Jun  5 04:26:01 2008
From: do-not-reply at jboss.com (heiko.braun@jboss.com)
Date: Thu, 5 Jun 2008 04:26:01 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: a problem when call web service
	using web service client
Message-ID: <12239482.1212654361469.JavaMail.jboss@colo-br-02.atl.jboss.com>

It's the JAXWS API that uses a service loader mechanism to pull the implementation. You have to make sure that WS invocation don't have the Sun API (jaxws-rt.jar, jaxws-tools.jar, jaxws-api.jar) on the classpath. JBossWS ships with it's own impl. of the API wich then delegates to the correct provider implementation: jboss-jaxws.jar

It's a little tricky to get both tooling and web service invocations into the project, because tooling still requires those jars mentioned above.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155882#4155882

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155882


From do-not-reply at jboss.com  Thu Jun  5 04:27:09 2008
From: do-not-reply at jboss.com (heiko.braun@jboss.com)
Date: Thu, 5 Jun 2008 04:27:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: a problem when call web service
	using web service client
Message-ID: <13909956.1212654429169.JavaMail.jboss@colo-br-02.atl.jboss.com>

So, conceptually you start with two different classpath settings, depending on the use case.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155883#4155883

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155883


From do-not-reply at jboss.com  Thu Jun  5 04:31:33 2008
From: do-not-reply at jboss.com (aguyngueran)
Date: Thu, 5 Jun 2008 04:31:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBoss-4.2.2-GA + JOSS-1.7 and WCF client
Message-ID: <6497965.1212654693448.JavaMail.jboss@colo-br-02.atl.jboss.com>

I'm having problems with SOAP fault declaration from JOSSO. It is like this:

<wsdl:message name="IdentityProvisioningException">
    <wsdl:part name="fault" type="impl:IdentityProvisioningException" /> 
</wsdl:message>

The problem is 'type' attribute which according to WS-Basic Profile http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html#Bindings_and_Faults.

So 'type' should be replaced by 'element' attribute. The warning message from WCF SvcUtil is:

Warning: Fault named IdentityProvisioningException in operation resolveAuthenticationAssertion cannot be imported. Unsup
ported WSDL, the fault message part must reference an element. This fault message does not reference an element. If you
have edit access to the WSDL document, you can fix the problem by referencing a schema element using the 'element' attri
bute.

And I don't know where to start with this problem. Is is JBoss issue (Ws-BP is supported here I think), JOSSO issue or WCF problem?

Thanks in advance.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155885#4155885

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155885


From do-not-reply at jboss.com  Thu Jun  5 14:19:48 2008
From: do-not-reply at jboss.com (jinglei)
Date: Thu, 5 Jun 2008 14:19:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Can not find truststore url
Message-ID: <8140831.1212689988434.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am seeing the same warn in the log file, Here is what I have the connector configured in the server.xml,

    <Connector SSLEnabled="true" address="${jboss.bind.address}" clientAuth="false" emptySessionPath="true" keystoreFile="${jboss.server.home.dir}/conf/local.keystore" keystorePass="123456" truststoreFile="${jboss.server.home.dir}/conf/local.keystore" maxHttpHeaderSize="8192" maxThreads="100" port="8443" protocol="HTTP/1.1" scheme="https" secure="true" sslProtocol="TLS" strategy="ms"/>

Thanks.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156076#4156076

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156076


From do-not-reply at jboss.com  Thu Jun  5 18:10:40 2008
From: do-not-reply at jboss.com (GalinaAtHP)
Date: Thu, 5 Jun 2008 18:10:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBoss AS 4.0.2 and JDK versions
Message-ID: <6679230.1212703840062.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi all,
simple question: need to find out if JBoss AS 4.0.2 is certified with JDK 1.6.
In general, I have hard time finding certification matrix for AS.
Would really appreciate help.
Thanks, Galina  

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156130#4156130

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156130


From do-not-reply at jboss.com  Thu Jun  5 18:19:00 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Thu, 5 Jun 2008 18:19:00 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBoss AS 4.0.2 and JDK versions
Message-ID: <22517304.1212704340921.JavaMail.jboss@colo-br-02.atl.jboss.com>

You probably should have asked this in the config forum http://www.jboss.com/index.html?module=bb&op=viewforum&f=61, not the web services forum.

But to answer your question, see http://wiki.jboss.org/wiki/JBossVsJavaJDKVersionMatrix

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156132#4156132

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156132


From do-not-reply at jboss.com  Fri Jun  6 02:42:52 2008
From: do-not-reply at jboss.com (max.andersen@jboss.com)
Date: Fri, 6 Jun 2008 02:42:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: a problem when call web service
	using web service client
Message-ID: <24875740.1212734572762.JavaMail.jboss@colo-br-02.atl.jboss.com>

So are these two jars ever needed at *runtime* or *compiletime* for users applications ?

The question is if our AS runtime adapter should explicilty excluded these jars when being asked which jars should be available to a WAR or EJB project.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156184#4156184

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156184


From do-not-reply at jboss.com  Fri Jun  6 09:43:22 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 6 Jun 2008 09:43:22 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Http Basic Authentication / GET and
	POST differences?
Message-ID: <29127432.1212759802243.JavaMail.jboss@colo-br-02.atl.jboss.com>

IOW you get a not-authorized error while trying to retrieve the wsdl before invoking the service, don't you? (check the logs to see what actually is asked with the GET call)
In this case you could store the wsdl locally (which btw is a general suggestion for clients to reduce network traffic).

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156307#4156307

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156307


From do-not-reply at jboss.com  Fri Jun  6 10:12:57 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 6 Jun 2008 10:12:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Which version of JBossWS?
Message-ID: <28527732.1212761578006.JavaMail.jboss@colo-br-02.atl.jboss.com>

You might be able to use JBossWS 1.2.1. For recent releases/target containers please refer this http://jbws.dyndns.org/mediawiki/index.php?title=Supported_Target_Containers

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156320#4156320

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156320


From do-not-reply at jboss.com  Fri Jun  6 10:29:29 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 6 Jun 2008 10:29:29 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Retrieve SOAP header
Message-ID: <28884132.1212762569289.JavaMail.jboss@colo-br-02.atl.jboss.com>

In an handler you can get the SOAPMessage from the MessageContext and then use the SOAPMessage's getSOAPHeader() method.
Otherwise create your endpoint as webservice provider (see org.jboss.test.ws.jaxws.samples.provider.ProviderBeanMessage for example) implementing Provider.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156330#4156330

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156330


From do-not-reply at jboss.com  Fri Jun  6 10:39:12 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 6 Jun 2008 10:39:12 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: arguments passed as null into
	method when invoked from P
Message-ID: <14798945.1212763152893.JavaMail.jboss@colo-br-02.atl.jboss.com>

This seems a PHP client issue, you should start looking at the message that is actually produced and goes on the wire and eventually ask for some kind of php support.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156332#4156332

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156332


From do-not-reply at jboss.com  Fri Jun  6 10:53:07 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 6 Jun 2008 10:53:07 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Upgrading from
	jbossws-native-2.0.2.GA to jbossws-3.0.1-
Message-ID: <25268305.1212763987781.JavaMail.jboss@colo-br-02.atl.jboss.com>

This might be due to a bug that has been fixed in 3.0.1 that caused the chunked encoding to be always disabled http://jira.jboss.com/jira/browse/JBWS-2000.
The default jaxws client configuration has chunk size = 2048; if the server you're calling doesn't support chunked encoding, you might want to disable it setting the http://org.jboss.ws/http#chunksize property to 0 (zero) in the standard-jaxws-client-config.xml (or in your own config).
I also suggest you to try using http/1.0 when .NET endpoints are involved and this kind of issues appear.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156342#4156342

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156342


From do-not-reply at jboss.com  Fri Jun  6 11:23:27 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 6 Jun 2008 11:23:27 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: New to WS... Need help...
Message-ID: <5972781.1212765807540.JavaMail.jboss@colo-br-02.atl.jboss.com>

"PeterJ" wrote : As a hint - I never run the "default" configuration. Instead I make a copy of it and modify the copy and run that. This way I can easily "refresh" my configuration by deleting it and recopying "default" again. (I actually do this as part of my Ant script.)

This is often useful, just remember that the JBossWS deploy procedure also changes libraries outside the JBOSS_HOME/server/your_configuration/

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156350#4156350

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156350


From do-not-reply at jboss.com  Fri Jun  6 11:46:39 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 6 Jun 2008 11:46:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Endpoint already registered
Message-ID: <25037543.1212767199886.JavaMail.jboss@colo-br-02.atl.jboss.com>

Generally speaking, the "Endpoint already registered" error can be caused by a failed deploy/undeploy that left the endpoint registry in a inconsistent state (i.e. the endpoint is registered but is actually not available). Do the errors you get somehow influence the deploy/undeploy?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156359#4156359

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156359


From do-not-reply at jboss.com  Fri Jun  6 13:17:24 2008
From: do-not-reply at jboss.com (tomstrummer)
Date: Fri, 6 Jun 2008 13:17:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - @WebServiceRef for JAX-RPC service?
Message-ID: <2487501.1212772644651.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi, does the @WebServiceRef annotation work for JAX-RPC services?

I can retrieve and use a service from the InitalContext (so I know it works) but I was hoping to get rid of the JNDI lookup.  However if I use @WebServiceRef I just get a NullPointerException.  Do I have to do anything fancy in my web.xml in order to enable the annotation scanning?  This is all in a servlet.

I'm using JBossAS 4.2.2.GA upgraded to the latest JBossWS client (3.0.1-native-2.0.4.GA)

This doesn't work:

  | public class TestServiceServlet extends HttpServlet {
  | 	
  | 	@WebServiceRef(wsdlLocation="META-INF/wsdl/IEnNET.wsdl")
  | 	IEnNETService service;
  | 	
  | 	@Override
  | 	protected void doGet(HttpServletRequest req, HttpServletResponse resp)
  | 			throws ServletException, IOException {
  | 		
  | 		try {
  | 			IEnNET port = service.getIEnNETPort(); // throws NPE
  | 			// ...
  | 

This does work:

  | public class TestServiceServlet extends HttpServlet {
  | 	
  | 	@Override
  | 	protected void doGet(HttpServletRequest req, HttpServletResponse resp)
  | 			throws ServletException, IOException {
  | 		
  | 		try {
  | 			InitialContext ctx = new InitialContext();
  | 			IEnNETService service = (IEnNETService)ctx.lookup("java:comp/env/service/EnNET");
  | 			IEnNET port = service.getIEnNETPort();
  | 

web.xml looks like this:

  | 	<service-ref>
  | 		<service-ref-name>service/EnNET</service-ref-name>
  | 		<service-interface>com.gridlogix.webservices.IEnNETService</service-interface>
  | 		<wsdl-file>META-INF/wsdl/IEnNET.wsdl</wsdl-file>
  | 		<jaxrpc-mapping-file>META-INF/jaxrpc-mapping.xml</jaxrpc-mapping-file>
  | 		<port-component-ref>
  | 			<service-endpoint-interface>com.gridlogix.webservices.IEnNET</service-endpoint-interface>
  | 		</port-component-ref>
  | 	</service-ref>
  | 

Thanks.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156382#4156382

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156382


From do-not-reply at jboss.com  Fri Jun  6 14:16:08 2008
From: do-not-reply at jboss.com (tomstrummer)
Date: Fri, 6 Jun 2008 14:16:08 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JWSDP 2.0 with JBoss 4.0.4 ?
Message-ID: <19074903.1212776168692.JavaMail.jboss@colo-br-02.atl.jboss.com>

"jason.greene at jboss.com" wrote : We don't support soap encoding. We recommend using our tool, but if you prefer to stick with wscompile thats fine. Just make sure you are using rpcliteral or documentliteral.
  | 
  | -Jason

Hi Jason -- sorry to resurrect an old thread but I'm seeing a similar problem.  

I am consuming a web service that I don't have control over (I think it's a .NET WS).  First I tried using Apache CXF's wsdl2java to generate the client stubs, which complained about soapenc:Array in the WSDL (I don't remember the exact error).  Googling suggested I needed an XML-RPC client, which JBossWS supports.  

So the JBossWS' wsconsume tool generates my stubs and jaxrpc-mapping.xml file correctly, and I can even create and call the web service.  But I see this same warning about soap encoding.  I am a WS noob -- what should I do?

Thanks in advance.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156398#4156398

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156398


From do-not-reply at jboss.com  Mon Jun  9 07:48:08 2008
From: do-not-reply at jboss.com (ljgp)
Date: Mon, 9 Jun 2008 07:48:08 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: No tests for @SchemaValidation
	annotation in 3.0.1 ?
Message-ID: <5072301.1213012088682.JavaMail.jboss@colo-br-02.atl.jboss.com>

A reply would _really_ be appreciated. I know that support here is on a best effort basis, but I am still hoping to get a useful answer to this (imho) simple question.

Regards, Luc.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156655#4156655

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156655


From do-not-reply at jboss.com  Mon Jun  9 10:28:24 2008
From: do-not-reply at jboss.com (soni_rahul337)
Date: Mon, 9 Jun 2008 10:28:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - org.jboss.ws.WSException: Cannot
	generate wsdl from interfac
Message-ID: <13655087.1213021704558.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,All 

I have created the webservice that returns the user defined type. I have to use the jboss wstools for developing service. For that I have created the class that containts the getter and setter methods and the required interface and the and the class that implements the intreface with the logic. but now when I am returning the complex-type it will not allow me to generate the wsdl file and another artifacts neccesary for creating the service. The same webservice works fine for the String[] as a return parameter. I have read that wstools generate the response and request classes for the complex type but in my case it wont create. what to do in that case.

Here is the exception that i am getting while executing the wstools ant task:--


  | 
  | [jbosswstools] org.jboss.ws.WSException: Cannot generate wsdl from: interface com.test.testdb.TestDataConnectionInterface
  | [jbosswstools] at org.jboss.ws.tools.JavaToWSDL.generate(JavaToWSDL.java:348)
  | [jbosswstools] at org.jboss.ws.tools.helpers.ToolsHelper.handleJavaToWSDLGeneration(ToolsHelper.java:122)
  | [jbosswstools] at org.jboss.ws.tools.WSTools.process(WSTools.java:132)
  | [jbosswstools] at org.jboss.ws.tools.WSTools.generate(WSTools.java:120)
  | [jbosswstools] at org.jboss.ws.tools.ant.wstools.execute(wstools.java:103)
  | [jbosswstools] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
  | [jbosswstools] at org.apache.tools.ant.Task.perform(Task.java:364)
  | [jbosswstools] at org.apache.tools.ant.Target.execute(Target.java:341)
  | [jbosswstools] at org.apache.tools.ant.Target.performTasks(Target.java:369)
  | [jbosswstools] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
  | [jbosswstools] at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
  | [jbosswstools] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
  | [jbosswstools] at org.eclipse.ant.internal.ui.antsupport.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32)
  | [jbosswstools] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
  | [jbosswstools] at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:423)
  | [jbosswstools] at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:137)
  | 
  | 


My Environment is:--

Jboss 4.0.5 GA
Apache Ant 1.6.5
Jdk 1.5.0_11

Regards and Thanks in Advace,
Rahul

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156715#4156715

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156715


From jbossws-users at lists.jboss.org  Mon Jun  9 11:35:41 2008
From: jbossws-users at lists.jboss.org (VIAGRA ® Trusted Site)
Date: Mon, 9 Jun 2008 11:35:41 -0400
Subject: [jbossws-users] Dear jbossws-users@lists.jboss.org June 81% 0FF 
Message-ID: <20080609103542.15463.qmail@Cantata> 

An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossws-users/attachments/20080609/2fca848a/attachment.html 

From do-not-reply at jboss.com  Mon Jun  9 14:34:23 2008
From: do-not-reply at jboss.com (florian79)
Date: Mon, 9 Jun 2008 14:34:23 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - authMethod=FORM
Message-ID: <25335801.1213036463902.JavaMail.jboss@colo-br-02.atl.jboss.com>


does anyone has experience with JAX-WS using the authMethod=FORM like this:

  | @WebService(...)
  | @WebContext(contextRoot = "/context-ws", urlPattern = "/Manager", authMethod = "FORM", transportGuarantee = "NONE", secureWSDLAccess = false)
  | @Stateless
  | @SecurityDomain("xx")
  | 

where to set the login page and the login errorpage?
is there any example/HowTo available?

the authMethod=BASIC works well!


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156801#4156801

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156801


From do-not-reply at jboss.com  Mon Jun  9 14:44:21 2008
From: do-not-reply at jboss.com (tomstrummer)
Date: Mon, 9 Jun 2008 14:44:21 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Bug? SOAP response causes
	ArrayIndexOutOfBoundsEx
Message-ID: <1741224.1213037061671.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am trying to consume a 3rd party web service.  When JBossWS parses the response, an ArrayIndexOutOfBoundsException is thrown from the JBoss XML binding code.  I have generated stubs using the wstools command.  

I'm guessing this is a bug?  I would love to help debug it but I'm kinda lost..  I'm not sure what namespace-to-package name conversion should be going on when the SOAP response is parsed since the mapping is already done in a jaxrpc-mapping.xml file.  And the jaxrpc-mapping isn't parsed each time a response is sent, right?

WS Response:

  | <?xml version="1.0"?>
  | <SOAP-ENV:Envelope
  | 	xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
  | 	xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  | 	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  | 	xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
  | 	<SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
  | 		xmlns:NS2="Gridlogix.EnNET.Types">
  | 		<NS1:GetObjectResponse xmlns:NS1="Gridlogix.EnNET.Types.IEnNET">
  | 			<return xsi:type="NS2:GlxObject">
  | 				<Identifier xsi:type="NS2:GlxIdentifier">
  | 					<Name xsi:type="xsd:string">Servers</Name>
  | 					<DisplayName xsi:type="xsd:string"></DisplayName>
  | 					<Index xsi:type="xsd:int">0</Index>
  | 					<Scope xsi:type="NS2:GlxMemberScope">msPublic</Scope>
  | 					<ClassID xsi:type="xsd:string">BACServerList</ClassID>
  | 					<TypeID xsi:type="xsd:int">1464013352</TypeID>
  | 				</Identifier>
  | 				<ObjectCount xsi:type="xsd:int">5</ObjectCount>
  | 				<PropertyCount xsi:type="xsd:int">4</PropertyCount>
  | 				<MethodCount xsi:type="xsd:int">7</MethodCount>
  | 				<DefaultProperty xsi:type="xsd:string"></DefaultProperty>
  | 				<Interfaces xsi:type="xsd:string">
  | 					IBACServerList,IPersistable
  | 				</Interfaces>
  | 				<ListClass xsi:type="xsd:string">GlxServer</ListClass>
  | 			</return>
  | 		</NS1:GetObjectResponse>
  | 	</SOAP-ENV:Body>
  | </SOAP-ENV:Envelope>
  | 

jaxrpc-mapping looks like this:

  | <?xml version='1.0' encoding='UTF-8'?><java-wsdl-mapping version='1.1' xmlns='http://java.sun.com/xml/ns/j2ee' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xsi:schemaLocation='http://java.sun.com/xml/ns/j2ee http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd'>
  |  <package-mapping>
  |   <package-type>com.gridlogix.webservices</package-type>
  |   <namespaceURI>Gridlogix.EnNET.Types</namespaceURI>
  |  </package-mapping>
  |  <package-mapping>
  |   <package-type>com.gridlogix.webservices</package-type>
  |   <namespaceURI>http://www.gridlogix.com/WebServices/</namespaceURI>
  |  </package-mapping>
  |  <java-xml-type-mapping>
  |   <java-type>com.gridlogix.webservices.GlxVersionInfo</java-type>
  |   <root-type-qname xmlns:typeNS='Gridlogix.EnNET.Types'>typeNS:GlxVersionInfo</root-type-qname>
  |   <qname-scope>complexType</qname-scope>
  |   <variable-mapping>
  |  ....
  | 

And the WSDL looks like this:

  | <?xml version="1.0" encoding="utf-8"?>
  | <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" 
  | xmlns:xs="http://www.w3.org/2001/XMLSchema" name="IEnNETService" 
  | targetNamespace="http://www.gridlogix.com/WebServices/" 
  | xmlns:tns="http://www.gridlogix.com/WebServices/" 
  | xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" 
  | xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" 
  | xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" 
  | xmlns:ns1="Gridlogix.EnNET.Types">
  |   <types>
  |     <xs:schema targetNamespace="Gridlogix.EnNET.Types" xmlns="Gridlogix.EnNET.Types">
  |       <xs:complexType name="GlxRem">
  |         <xs:sequence/>
  |       </xs:complexType>
  |       .....
  | 

Finally.. the stack trace...

  | java.rmi.RemoteException: Call invocation failed; nested exception is: 
  | 	org.jboss.ws.WSException: org.jboss.ws.core.binding.BindingException: org.jboss.ws.core.jaxrpc.binding.jbossxb.UnmarshalException: Failed to parse source: 21
  | 	at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:536)
  | 	at org.jboss.ws.core.jaxrpc.client.CallImpl.invoke(CallImpl.java:277)
  | 	at org.jboss.ws.core.jaxrpc.client.PortProxy.invoke(PortProxy.java:151)
  | 	at $Proxy277.getObject(Unknown Source)
  | 	at com.enernoc.eea.dpm.web.TestServiceServlet.doGet(TestServiceServlet.java:57)
  | 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
  | 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
  | 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
  | 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
  | 	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
  | 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
  | 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
  | 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
  | 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
  | 	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
  | 	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
  | 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
  | 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
  | 	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
  | 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
  | 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
  | 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
  | 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
  | 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
  | 	at java.lang.Thread.run(Thread.java:619)
  | Caused by: org.jboss.ws.WSException: org.jboss.ws.core.binding.BindingException: org.jboss.ws.core.jaxrpc.binding.jbossxb.UnmarshalException: Failed to parse source: 21
  | 	at org.jboss.ws.core.soap.XMLContent.unmarshallObjectContents(XMLContent.java:250)
  | 	at org.jboss.ws.core.soap.XMLContent.transitionTo(XMLContent.java:97)
  | 	at org.jboss.ws.core.soap.DOMContent.transitionTo(DOMContent.java:77)
  | 	at org.jboss.ws.core.soap.SOAPContentElement.transitionTo(SOAPContentElement.java:140)
  | 	at org.jboss.ws.core.soap.SOAPContentElement.getObjectValue(SOAPContentElement.java:171)
  | 	at org.jboss.ws.core.EndpointInvocation.transformPayloadValue(EndpointInvocation.java:263)
  | 	at org.jboss.ws.core.EndpointInvocation.getReturnValue(EndpointInvocation.java:197)
  | 	at org.jboss.ws.core.CommonClient.syncOutputParams(CommonClient.java:499)
  | 	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:387)
  | 	at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:517)
  | 	... 24 more
  | Caused by: org.jboss.ws.core.binding.BindingException: org.jboss.ws.core.jaxrpc.binding.jbossxb.UnmarshalException: Failed to parse source: 21
  | 	at org.jboss.ws.core.jaxrpc.binding.JBossXBDeserializer.deserialize(JBossXBDeserializer.java:111)
  | 	at org.jboss.ws.core.jaxrpc.binding.JBossXBDeserializer.deserialize(JBossXBDeserializer.java:62)
  | 	at org.jboss.ws.core.binding.DeserializerSupport.deserialize(DeserializerSupport.java:60)
  | 	at org.jboss.ws.core.soap.XMLContent.unmarshallObjectContents(XMLContent.java:180)
  | 	... 33 more
  | Caused by: org.jboss.ws.core.jaxrpc.binding.jbossxb.UnmarshalException: Failed to parse source: 21
  | 	at org.jboss.ws.core.jaxrpc.binding.jbossxb.JBossXBUnmarshallerImpl.unmarshal(JBossXBUnmarshallerImpl.java:65)
  | 	at org.jboss.ws.core.jaxrpc.binding.JBossXBDeserializer.deserialize(JBossXBDeserializer.java:103)
  | 	... 36 more
  | Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: 21
  | 	at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:179)
  | 	at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:126)
  | 	at org.jboss.ws.core.jaxrpc.binding.jbossxb.JBossXBUnmarshallerImpl.unmarshal(JBossXBUnmarshallerImpl.java:61)
  | 	... 37 more
  | Caused by: java.lang.ArrayIndexOutOfBoundsException: 21
  | 	at org.jboss.xb.binding.Util.xmlNamespaceToJavaPackage(Util.java:229)
  | 	at org.jboss.xb.binding.Util.xmlNameToClassName(Util.java:310)
  | 	at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtCharactersHandler.unmarshal(RtCharactersHandler.java:83)
  | 	at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endElement(SundayContentHandler.java:985)
  | 	at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endElement(SundayContentHandler.java:246)
  | 	at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.endElement(SaxJBossXBParser.java:296)
  | 	at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
  | 	at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source)
  | 	at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
  | 	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
  | 	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
  | 	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
  | 	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
  | 	at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
  | 	at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
  | 	at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
  | 	at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:175)
  | 	... 39 more
  | 

Thanks in advance...

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156806#4156806

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156806


From do-not-reply at jboss.com  Mon Jun  9 15:30:10 2008
From: do-not-reply at jboss.com (florian79)
Date: Mon, 9 Jun 2008 15:30:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: authMethod=FORM
Message-ID: <284833.1213039810547.JavaMail.jboss@colo-br-02.atl.jboss.com>

authMethod=Form is not supported

http://jbws.dyndns.org/mediawiki/index.php?title=User_Guide#WebContext

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156814#4156814

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156814


From do-not-reply at jboss.com  Mon Jun  9 16:15:52 2008
From: do-not-reply at jboss.com (tomstrummer)
Date: Mon, 9 Jun 2008 16:15:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Certain WS request syntax not
	supported in AS 4.2.x
Message-ID: <1617452.1213042552853.JavaMail.jboss@colo-br-02.atl.jboss.com>

"alessio.soldano at jboss.com" wrote : The soap message you wrote is using rpc/encoded style. This is not supported anymore since a lot of time, because it has been disallowed by WS-I Basic Profile.

Can anyone give a hint on what can be done to consume a RPC/encoded web service?  Unfortunately I'm writing a client, the service itself is out of my control.  I have no choice, but all of the Java WS toolkits (metro, CXF, JBoss WS) seem to have not support it...

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156824#4156824

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156824


From do-not-reply at jboss.com  Mon Jun  9 16:21:40 2008
From: do-not-reply at jboss.com (lujop)
Date: Mon, 9 Jun 2008 16:21:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: problem with calling ssl web service
Message-ID: <4987771.1213042900884.JavaMail.jboss@colo-br-02.atl.jboss.com>

I've the same problem. Someone has any workarround?

I submitted a bug in the JIRA:
http://jira.jboss.org/jira/browse/JBWS-2216


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156825#4156825

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156825


From do-not-reply at jboss.com  Mon Jun  9 19:36:36 2008
From: do-not-reply at jboss.com (andregps)
Date: Mon, 9 Jun 2008 19:36:36 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Two ejb's in one wstools config file?
Message-ID: <24802194.1213054596984.JavaMail.jboss@colo-br-02.atl.jboss.com>

How can i configure the mapping of two ejb's in one wstools config file, in order to generate one webservices.xml?  or in this case i have to generate two webservices.xml?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156877#4156877

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156877


From do-not-reply at jboss.com  Tue Jun 10 03:08:33 2008
From: do-not-reply at jboss.com (rajesh_css)
Date: Tue, 10 Jun 2008 03:08:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - How to use webservices in jboss portals
Message-ID: <19137231.1213081713982.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,
I am working on jbossportals ,how to use webservices in jboss portals.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156907#4156907

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156907


From do-not-reply at jboss.com  Tue Jun 10 07:12:13 2008
From: do-not-reply at jboss.com (kishor@datavsn.com)
Date: Tue, 10 Jun 2008 07:12:13 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Ho to use web services in jboss-4.0.5
	and EJB 2.0
Message-ID: <29526220.1213096333575.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am running a JBoss Server 4.0.5, EJB2.0 and I want to use web services. How to start with it and does it needs any additional s/w's ?

Just Wondering...
-Kishor.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156961#4156961

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156961


From do-not-reply at jboss.com  Tue Jun 10 11:06:01 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 10 Jun 2008 11:06:01 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: How to use webservices in jboss
	portals
Message-ID: <6112791.1213110361676.JavaMail.jboss@colo-br-02.atl.jboss.com>

It should be no different than using web services from a client.

I assume that you are writing a portlet, and that portlet will call a web service. In that case, the portlet acts just like any other web services client, and the web service invocation within the portlet looks the same as for any web services client.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157053#4157053

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157053


From do-not-reply at jboss.com  Tue Jun 10 11:07:51 2008
From: do-not-reply at jboss.com (agohar)
Date: Tue, 10 Jun 2008 11:07:51 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JbossWS array type issues
Message-ID: <20706558.1213110472163.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I am having a problem with JBossWS for Array elements in wsdl. I am using JBoss-4.2.2. 

One of my webservices method returns an object (complex type), which contains the array of other objects in it. Here is the snippt from my wsdl


  |    <xs:complexType name='MyVO'>
  |     <xs:sequence>
  |      <xs:element maxOccurs='unbounded' name='attr1' type='xs:string'/>
  |      <xs:element maxOccurs='unbounded' name='attr2' type='tns:MyOtherVO'/>
  |      <xs:element name='attr3' type='tns:MyOtherVO'/>
  |      <xs:element maxOccurs='unbounded' name='attr4' type='tns:MyOtherVO2'/>
  |      <xs:element name='attr5' type='xs:int'/>
  |      <xs:element name='attr6' type='xs:string'/>
  |      <xs:element name='attr7' type='xs:string'/>
  |      <xs:element name='attr8' type='xs:int'/>
  |     </xs:sequence>
  |    </xs:complexType>
  | 

This Object is returned from one of the webservices method and when attr2 and attr4 are null array or empty array, it doesn't return anything back to the soap client. I want it to return empty array. 

Is it possible?

Thanks

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157054#4157054

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157054


From do-not-reply at jboss.com  Tue Jun 10 11:14:54 2008
From: do-not-reply at jboss.com (nraghava)
Date: Tue, 10 Jun 2008 11:14:54 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Method Overloading and SOAP Annotations
Message-ID: <7203978.1213110894465.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have my HelloWorld EJB3 service with 3 overloaded methods and corresponding SOAP Annotations.

Hello World Impl Code: 

  | public class SomeServiceBean implements SomeService {
  | 
  |     @WebMethod
  |     @WebResult(name="someData")
  |  public string SomeMethod ( @WebParam(name="somedaylong") long X,
  |                                                 @WebParam(name="somedaylong")  long Y, 
  |                                                 @WebParam(name="somemonth") string Z) {
  | ....
  | }
  | 
  |     @WebMethod
  |     @WebResult(name="someData")
  |  public string SomeMethod ( @WebParam(name="somedayint") int X,
  |                                                 @WebParam(name="someweekint")  int Y, 
  |                                                 @WebParam(name="somemonth") string Z) {
  | ....
  | }
  | 
  | 
  |     @WebMethod
  |     @WebResult(name="someData")
  |  public string SomeMethod ( @WebParam(name="somedaylong") long X,
  |                                                 @WebParam(name="someweekint")  int Y, 
  |                                                 @WebParam(name="somemonth") string Z) {
  | ....
  | }
  | }
  | 
  | 

Per the WSDL Spec, the combination of method name and in/out parameter name should be unique as in this case i.e.,

[SomeMethod, somedaylong, somedaylong, somemonth]
[SomeMethod, somedayint, somedayint, somemonth]
[SomeMethod, somedaylong, somedayint, somemonth]

When I deploy this service in my JBoss 4.2.1 GA container i get the following error message:

  | 2008-06-06 14:23:26,714 WARN  [org.jboss.ws.metadata.wsdl.WSDLBinding] Multiple binding operations r
  | eference: {http://Some.services.xyz.com/}SomeMethod
  | 2008-06-06 14:23:26,715 WARN  [org.jboss.ws.metadata.wsdl.WSDLBinding] Multiple binding operations r
  | eference: {http://Some.services.xyz.com/}SomeMethod
  | 2008-06-06 14:23:26,715 WARN  [org.jboss.ws.metadata.wsdl.WSDLBinding] Multiple binding operations r
  | eference: {http://Some.services.xyz.com/}SomeMethod
  | 2008-06-06 14:23:26,742 ERROR [org.jboss.deployment.MainDeployer] Could not start deployment: file:/
  | var/lib/jbossas/server/production/tmp/deploy/tmp34936Some-service-ear-1.0-SNAPSHOT.ear-contents/Some
  | -service-ejb-1.0-SNAPSHOT.jar
  | java.lang.IllegalArgumentException: Duplicate operation with name=SomeMethod, found in binding '{htt
  | p://Some.services.xyz.com/}SomeServiceBinding'.
  |         at com.ibm.wsdl.BindingImpl.getBindingOperation(BindingImpl.java:244)
  |         at org.jboss.ws.tools.wsdl.WSDL11Reader.getBindingOperation(WSDL11Reader.java:940)
  |         at org.jboss.ws.tools.wsdl.WSDL11Reader.getOperationStyle(WSDL11Reader.java:949)
  |         at org.jboss.ws.tools.wsdl.WSDL11Reader.processPortTypeOperations(WSDL11Reader.java:655)
  |         at org.jboss.ws.tools.wsdl.WSDL11Reader.processPortType(WSDL11Reader.java:642)
  |         at org.jboss.ws.tools.wsdl.WSDL11Reader.processBinding(WSDL11Reader.java:1035)
  |         at org.jboss.ws.tools.wsdl.WSDL11Reader.processPort(WSDL11Reader.java:1560)
  |         at org.jboss.ws.tools.wsdl.WSDL11Reader.processPorts(WSDL11Reader.java:1545)
  |         at org.jboss.ws.tools.wsdl.WSDL11Reader.processServices(WSDL11Reader.java:1515)
  |         at org.jboss.ws.tools.wsdl.WSDL11Reader.processDefinition(WSDL11Reader.java:174)
  |         at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:128)
  |         at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:321)
  |         at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaDat
  | a(JAXWSWebServiceMetaDataBuilder.java:166)
  |         at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(
  | JAXWSServerMetaDataBuilder.java:50)
  |         at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderEJB3.buildMetaData(JAXWSMetaDataB
  | uilderEJB3.java:78)
  |         at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.create(UnifiedMetaDataDeployment
  | Aspect.java:71)
  |         at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(Unknown Source)
  |         at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97)
  |         at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90)
  |         at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInt
  | erceptorSupport.java:188)
  |         at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
  |         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  |         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  |         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  |         at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  |         at $Proxy34.start(Unknown Source)
  |         at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
  |         at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
  |         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
  |         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
  |         at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
  |         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  |         at java.lang.reflect.Method.invoke(Method.java:585)
  |         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  |         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  |         at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
  |         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  |         at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterce
  | ptor.java:142)
  |         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  |         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  |         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  |         at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  |         at $Proxy9.deploy(Unknown Source)
  |         at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
  |         at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610)
  |         at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeplo
  | ymentScanner.java:263)
  |         at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploym
  | entScanner.java:274)
  |         at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeployme
  | ntScanner.java:225)
  | 


Any help is much appreciated?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157060#4157060

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157060


From do-not-reply at jboss.com  Wed Jun 11 04:20:17 2008
From: do-not-reply at jboss.com (agohar)
Date: Wed, 11 Jun 2008 04:20:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - @WebContext url pattern problem
Message-ID: <18230241.1213172417425.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I am using jboss-4.2.2 and EJB 3.0 SLSB to generate a webservice. I've defined a @WebContext for the webservice like:


  | @WebContext (contextRoot = "/myweb", urlPattern="/myweb-service/WebDelegateEndPoint")
  | 

Notice that "myweb" is common in contextRoot and urlPattern attributes. When jbossws generates the webservice, it generates the URL for the webservice as:

http://localhost:8080/myweb/-service/WebDelegateEndPoint?wsdl

Notice the missing "myweb" in the url pattern.

I am expecting it to generate:

http://localhost:8080/myweb/myweb-service/WebDelegateEndPoint?wsdl

Is it a bug or am i doing anything wrong? Any idea?

Thanks

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157246#4157246

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157246


From do-not-reply at jboss.com  Wed Jun 11 04:34:01 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 11 Jun 2008 04:34:01 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: @WebContext url pattern problem
Message-ID: <20320373.1213173241473.JavaMail.jboss@colo-br-02.atl.jboss.com>

This might be a bug, could you please fill in the JIRA attaching a small test reproducing the issue?
Thank you

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157248#4157248

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157248


From do-not-reply at jboss.com  Wed Jun 11 08:05:24 2008
From: do-not-reply at jboss.com (max.andersen@jboss.com)
Date: Wed, 11 Jun 2008 08:05:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: a problem when call web service
	using web service client
Message-ID: <24496094.1213185924982.JavaMail.jboss@colo-br-02.atl.jboss.com>

Heiko - any update ? :)

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157321#4157321

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157321


From do-not-reply at jboss.com  Wed Jun 11 11:17:57 2008
From: do-not-reply at jboss.com (medalhas)
Date: Wed, 11 Jun 2008 11:17:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Upgrading from
	jbossws-native-2.0.2.GA to jbossws-3.0.1-
Message-ID: <17376487.1213197477320.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi, 

Thanks your info it was very helpful. Problem solved.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157419#4157419

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157419


From do-not-reply at jboss.com  Thu Jun 12 00:13:44 2008
From: do-not-reply at jboss.com (BrettSc)
Date: Thu, 12 Jun 2008 00:13:44 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: please help - web services still
	dont work for me - jbos
Message-ID: <27505931.1213244024674.JavaMail.jboss@colo-br-02.atl.jboss.com>

Just a minor change to the libraries...

jbossclient-all.jar should be jbossall-client.jar.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157566#4157566

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157566


From do-not-reply at jboss.com  Thu Jun 12 19:57:40 2008
From: do-not-reply at jboss.com (BrettSc)
Date: Thu, 12 Jun 2008 19:57:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - setProperty must be overridden by all
	subclasses of SOAPMess
Message-ID: <8208345.1213315060412.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I've installed JBoss4.2.2 and upgraded JBossws to native-3.0.1-2.0.4.  ant deploy-jboss422 works fine but when I run the ant tests 90% or better fail with the "setProperty must be overridden..." exception and the rest fail for other reasons. 

I'm thinking I've gotten something corrupted but cleaning, redeploying and re-running give the same results.


  | 17:46:38,395 ERROR [RequestHandlerImpl] Error processing web service request
  | org.jboss.ws.WSException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
  | 	at org.jboss.ws.WSException.rethrow(WSException.java:68)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:325)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:201)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:134)
  | 	at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
  | 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
  | 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
  | 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
  | 	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
  | 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
  | 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
  | 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
  | 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
  | 	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
  | 	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
  | 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
  | 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
  | 	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
  | 	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:562)
  | 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
  | 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
  | 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
  | 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
  | 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
  | 	at java.lang.Thread.run(Unknown Source)
  | Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
  | 	at javax.xml.soap.SOAPMessage.setProperty(Unknown Source)
  | 	at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:83)
  | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:171)
  | 	at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:245)
  | 	at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:174)
  | 	at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:104)
  | 	at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:671)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:488)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:284)
  | 	... 23 more
  | 

Not sure where I took the wrong turn...any help would be appreciated.

-Brett


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157846#4157846

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157846


From do-not-reply at jboss.com  Thu Jun 12 20:45:17 2008
From: do-not-reply at jboss.com (BrettSc)
Date: Thu, 12 Jun 2008 20:45:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: setProperty must be overridden by
	all subclasses of SOAP
Message-ID: <21711237.1213317917921.JavaMail.jboss@colo-br-02.atl.jboss.com>

ack...I had verified I was using jdk 1.5 from ant but somehow the server was getting jdk 1.6. 

Sorry about that...works much better now.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157855#4157855

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157855


From do-not-reply at jboss.com  Mon Jun 16 11:50:32 2008
From: do-not-reply at jboss.com (ben.lidgey)
Date: Mon, 16 Jun 2008 11:50:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: @PostConstruct never invoked
Message-ID: <29217623.1213631432824.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am also seeing this behaviour with JAX-WS 2.0 web services deployed to JBoss 4.2.2.

@PostConstruct and @PreDestroy are called when the web service is run "manually" by defining an Endpoint in a main method, but not when deployed.

Does anyone know why this is? 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158407#4158407

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158407


From do-not-reply at jboss.com  Mon Jun 16 12:29:05 2008
From: do-not-reply at jboss.com (tomstrummer)
Date: Mon, 16 Jun 2008 12:29:05 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Bug? SOAP response causes
	ArrayIndexOutOfBoundsEx
Message-ID: <11323009.1213633745140.JavaMail.jboss@colo-br-02.atl.jboss.com>

I hate to bump this but I was really hoping for some help since JBossWS seemed to be the only toolkit that was getting me anywhere with this old RPC/encoded service.  Most of the other Java WS frameworks wouldn't even generate the client stub classes from the WSDL.  

I'd be happy to give more details, file a bug report, dig into code, etc but I'm at a loss as to where to start.  Is this even supported by JBossWS anymore?  I know RPC/encoded services are not WS-I compliant and all that jazz, but that doesn't help me since I have an old 3rd party service that I have to integrate with :(

My last resort will be hand-crafting the request and response!  And the WSDL is not trivial since there are a number of complex types.  Any help would be greatly appreciated!  

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158419#4158419

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158419


From do-not-reply at jboss.com  Mon Jun 16 11:04:56 2008
From: do-not-reply at jboss.com (DrPizza)
Date: Mon, 16 Jun 2008 11:04:56 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Creating web service endpoints
	on-the-fly
Message-ID: <24764073.1213628696384.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello,

We would like to generate web service endpoints dynamically (rather than statically configured using the annotations).

Is there any reasonably simple way of doing this?



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158381#4158381

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158381


From do-not-reply at jboss.com  Mon Jun 16 17:23:34 2008
From: do-not-reply at jboss.com (APieropan)
Date: Mon, 16 Jun 2008 17:23:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Problem calling a ws in a servlet
Message-ID: <20552507.1213651414712.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,
i am developing an application using jboss 4.2.2,ejb 3.0 and netbeans.
Following one of the tutorials online i created a web service inside the ejb container, then i created a web service inside my web container. After that i created a servlet. In the servlet  i used the "command call web service operation" to auto generate the needed code to call the ws.
The result is the injection 

  | @WebServiceRef(wsdlLocation = "http://localhost:8080/prova/NewWebService?wsdl")
  | 
That is not supported in jboss 4.2 causing a null pointer exception when i try to access the requested resource.

I tried the "walkaruond" found on this forum using this code in stand of the previous injection:

  | private NewWebServiceService service;
  | service = new NewWebServiceService();
  | 

and i got the following exception:

  | java.lang.ClassCastException: org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl cannot be cast to javax.xml.ws.spi.ServiceDelegate21
  | 

Can someone help me solving this trouble, is there any working "walkaround" to call a ws inside a servlet using Jboss 4.2 and Netbeans?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158513#4158513

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158513


From do-not-reply at jboss.com  Tue Jun 17 02:54:02 2008
From: do-not-reply at jboss.com (tommy.bergkvist)
Date: Tue, 17 Jun 2008 02:54:02 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Streaming webservices
Message-ID: <29145312.1213685642397.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I am using jbossas 4.2.2, jbossws 3.0.1.
I am having some trouble with my webservice implementation. My endpoint needs to be able to both send and receive large XMLs. In my case there are large elements (100 Mb) which are Base64 encoded.

All attempts on sending such XML ends up as a DOMSource on my endpoint. Is there any way to configure Webservices to not parse the incoming message and use StreamSource instead. I have no interest what so ever to marshall/unmarshall, validate, use Interceptors nor Handlers. I would be very pleased if incoming message could be streamed straight down to disk.

If StreamSource is not possible, then a StaxSource using the Woodstox implementation would be nice as well (it handles large Elements).

I am also having a similar problem with my stand-alone client. It runs with java 1.6. As soon as an Element is larger than 100kb I get an Exception that end element is missing, It seams that the XMLStreamReader (which is used by com.sun.xml.internal.ws.client.dispatch) can not handle large Elements.

Do I need to use Spring to be able to stream over Webservices?

Anyone has any ideas?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158588#4158588

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158588


From do-not-reply at jboss.com  Tue Jun 17 03:32:55 2008
From: do-not-reply at jboss.com (sagimann)
Date: Tue, 17 Jun 2008 03:32:55 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem calling a ws in a servlet
Message-ID: <18045853.1213687975456.JavaMail.jboss@colo-br-02.atl.jboss.com>

I'm getting the same problem. Are you sure JBoss 4.2 doesn't support WebServiceRef annotation? could you pls point me to a doc ref that says that? I've been looking all over for an "official" statement about this...

anyway, I worked around the problem as you did. However, make sure that the object you create with the 'new' statement is of the class that was auto-generated for you on the client side - not of the class that was used to implement the "real" service.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158603#4158603

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158603


From do-not-reply at jboss.com  Tue Jun 17 03:35:35 2008
From: do-not-reply at jboss.com (sagimann)
Date: Tue, 17 Jun 2008 03:35:35 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: @WebServiceRef for JAX-RPC service?
Message-ID: <1012001.1213688136030.JavaMail.jboss@colo-br-02.atl.jboss.com>

I'm having the same problem. did you solve this?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158604#4158604

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158604


From do-not-reply at jboss.com  Tue Jun 17 03:43:04 2008
From: do-not-reply at jboss.com (sagimann)
Date: Tue, 17 Jun 2008 03:43:04 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Web Service Client
Message-ID: <26812820.1213688584330.JavaMail.jboss@colo-br-02.atl.jboss.com>

hi, I'm having the same problem with the NPE. Did you solve this? By the way, I noticed that the latest JBossWS comes with many test cases, some of which uses annotations and seem to pass the test-run... However, I was still unable to "reproduce" the success...

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158605#4158605

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158605


From do-not-reply at jboss.com  Tue Jun 17 03:45:35 2008
From: do-not-reply at jboss.com (APieropan)
Date: Tue, 17 Jun 2008 03:45:35 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem calling a ws in a servlet
Message-ID: <25855314.1213688735803.JavaMail.jboss@colo-br-02.atl.jboss.com>

I found that WebServiceRef is not supported in Jboss 4.2 web container even on this forum. If you search that annotation you can find many topics related.

What do you mean by the class auto generated on the client side? When i create a web service client the only thing that is generate by the ide is a web service reference wsdl.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158606#4158606

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158606


From do-not-reply at jboss.com  Tue Jun 17 04:57:34 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Tue, 17 Jun 2008 04:57:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Bug? SOAP response causes
	ArrayIndexOutOfBoundsEx
Message-ID: <2026033.1213693054591.JavaMail.jboss@colo-br-02.atl.jboss.com>

"tomstrummer" wrote : 
  | I'd be happy to give more details, file a bug report, dig into code, etc but I'm at a loss as to where to start.  Is this even supported by JBossWS anymore?  I know RPC/encoded services are not WS-I compliant and all that jazz, but that doesn't help me since I have an old 3rd party service that I have to integrate with :(
  | 
No, we don't support RPC/encoded as well :(

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158630#4158630

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158630


From do-not-reply at jboss.com  Tue Jun 17 09:27:41 2008
From: do-not-reply at jboss.com (pramod_bs)
Date: Tue, 17 Jun 2008 09:27:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Streaming webservices
Message-ID: <33035726.1213709261781.JavaMail.jboss@colo-br-02.atl.jboss.com>

I think one option to solve your problem could be to use soap as an attachemnt feature. There are samples in the jboss source download.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158698#4158698

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158698


From do-not-reply at jboss.com  Tue Jun 17 09:59:56 2008
From: do-not-reply at jboss.com (tomstrummer)
Date: Tue, 17 Jun 2008 09:59:56 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: @WebServiceRef for JAX-RPC service?
Message-ID: <2983031.1213711196872.JavaMail.jboss@colo-br-02.atl.jboss.com>

"sagimann" wrote : I'm having the same problem. did you solve this?

Unfortunately, no.  I think there was an open issue related to this, with a fix version of JBossAS 5.0.  I guess updating JBossAS 4 with the latest JBossWS JARs is not enough.  

I had to go the traditional route and do a JNDI lookup as described here:
http://jbws.dyndns.org/mediawiki/index.php?title=JAX-RPC_User_Guide#Web_Services_Clients

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158707#4158707

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158707


From do-not-reply at jboss.com  Wed Jun 18 04:18:05 2008
From: do-not-reply at jboss.com (tommy.bergkvist)
Date: Wed, 18 Jun 2008 04:18:05 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Streaming webservices
Message-ID: <3095909.1213777085637.JavaMail.jboss@colo-br-02.atl.jboss.com>

Unfortunately I am note the one who is responsible for the technical specifiaction. The transport should comply with a specified XSD and also various clients and servers (not only the ones I am implementing) should be able to communicate.

Also, the XML elements that are that large actually contains binary documents that the server is not required to understand. They should just be stored in an archive as base64 encoded strings.

I have tried to figure out how to solve this, but there does not seem to exist any implementation to handle streaming webservices with large XML elements. The one parser I have used which can handle this is Woodstox, but jboss does not support this, right? Maybe in the future?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158908#4158908

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158908


From do-not-reply at jboss.com  Wed Jun 18 09:43:08 2008
From: do-not-reply at jboss.com (shaikbash)
Date: Wed, 18 Jun 2008 09:43:08 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - EJB Web Service Stateful?
Message-ID: <1521007.1213796588116.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,
I have developed a simple EJB based web-service as shown below:

@Stateless
@Remote(MySession.class)
@WebService(endpointInterface = "test.MySession")
@WebContext(contextRoot = "/mySession")
public class MySessionBean implements MySession
{
  private int count;
  
  public int getCount()
  {
    return ++count;
  }
}

This is deployed on JBOSS 4.2.2 server.
I have a servlet based client, which connects to this service using the jbossws-3.0.1-native-2.0.4 jars. Whenever I call the getCount() method from the client I get an incremented value. I was expecting to always get 1 as the return value, since my EJB is stateless. My question is how is it retaining the state? Any light on this is greately appreciated.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158989#4158989

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158989


From do-not-reply at jboss.com  Wed Jun 18 13:11:03 2008
From: do-not-reply at jboss.com (tomstrummer)
Date: Wed, 18 Jun 2008 13:11:03 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Bug? SOAP response causes
	ArrayIndexOutOfBoundsEx
Message-ID: <19982475.1213809063423.JavaMail.jboss@colo-br-02.atl.jboss.com>

But you (and Axis1) could actually generate client stubs!  Damn.  I think there is absolutely no Java WS framework that supports RPC/encoded services.  I'm pretty sure I've tried them all.  What's worse, the difference in the message seems almost trivial.  

Maybe some XSL magic could help...  Does JBossWS offer the ability to hook into the XML event stream before it's sent on to the XML-> Java mapping?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159055#4159055

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159055


From do-not-reply at jboss.com  Wed Jun 18 14:18:21 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 18 Jun 2008 14:18:21 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Streaming webservices
Message-ID: <22696690.1213813101840.JavaMail.jboss@colo-br-02.atl.jboss.com>

Is the javax.xml.ws.Provider a solution for you? You might want to check the org.jboss.test.ws.jaxws.samples.provider test cases.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159068#4159068

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159068


From do-not-reply at jboss.com  Wed Jun 18 19:30:15 2008
From: do-not-reply at jboss.com (tbansal)
Date: Wed, 18 Jun 2008 19:30:15 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re:
Message-ID: <33421405.1213831815368.JavaMail.jboss@colo-br-02.atl.jboss.com>

I ran into a similar issue and fixed it. The interface stubs generated by wsconsume had namespaces defined for the header and the body in annotations. The annotations were not inherited by the implementation class. I manully carried over all the annotations including namespace bindings to the implementation class and it worked since then.




View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159119#4159119

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159119


From do-not-reply at jboss.com  Thu Jun 19 04:15:28 2008
From: do-not-reply at jboss.com (tommy.bergkvist)
Date: Thu, 19 Jun 2008 04:15:28 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Streaming webservices
Message-ID: <18016652.1213863328899.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am using the Provider and the server receives a Source. However, it is a DOMSource, which means the entire message is in memory. I would like to receive a StreamSource with an InputStream. Then I can parse it myself with the appropriate tools.

I have tried to disable all my Logical- and SOAPMessageHandlers to avoid parsing by jboss, but it does not seem to help. Is there somthing I can implement or configure to avoid parsing into DOM tree?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159184#4159184

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159184


From do-not-reply at jboss.com  Thu Jun 19 06:29:26 2008
From: do-not-reply at jboss.com (mnemonics)
Date: Thu, 19 Jun 2008 06:29:26 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - TypeNotPresentExceptionProxy when
	trying to get the Port of
Message-ID: <4900187.1213871366795.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

We've generated code with wsimport (sun) from a wsdl and imported that in our webapp. When we try to get the port from the service (in order to make a web service call) it fails wirth the following error:


  | java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy
  |         at sun.reflect.annotation.AnnotationParser.parseClassArray(AnnotationParser.java:653)
  |         at sun.reflect.annotation.AnnotationParser.parseArray(AnnotationParser.java:460)
  |         at sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:286)
  |         at sun.reflect.annotation.AnnotationParser.parseAnnotation(AnnotationParser.java:222)
  |         at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:69)
  |         at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:52)
  |         at java.lang.Class.initAnnotationsIfNecessary(Class.java:3031)
  |         at java.lang.Class.getAnnotation(Class.java:2989)
  |         at java.lang.Class.isAnnotationPresent(Class.java:3001)
  |         at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.assertSEIConstraints(ServiceDelegateImpl.java:283)
  |         at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:180)
  |         at javax.xml.ws.Service.getPort(Service.java:143)
  | 

When running this code from a (simple) client with Java EE5 libraries (javaee.jar, webservices-rt.jr) it's ok.
But from within JBoss 4.2.2 it fails. We also tried the JBoss-ws update, but same problem.

Any ideas?


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159223#4159223

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159223


From do-not-reply at jboss.com  Thu Jun 19 08:16:08 2008
From: do-not-reply at jboss.com (extasy)
Date: Thu, 19 Jun 2008 08:16:08 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBoss Shutdown hook
Message-ID: <25118720.1213877768903.JavaMail.jboss@colo-br-02.atl.jboss.com>

What is the advantage of invoking JBoss shutdown hook compared with calling system.exit.

How can we invoke JBoss shutdown hook.


Thanks in advance
Babu

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159249#4159249

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159249


From do-not-reply at jboss.com  Thu Jun 19 08:54:30 2008
From: do-not-reply at jboss.com (mnemonics)
Date: Thu, 19 Jun 2008 08:54:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: TypeNotPresentExceptionProxy when
	trying to get the Port
Message-ID: <26688017.1213880070770.JavaMail.jboss@colo-br-02.atl.jboss.com>

Solved it!

Although similar the code generation of wsimport (Sun) is not identical to the wsconsume of JBoss.
Generation the code with wsconsume works ok.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159264#4159264

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159264


From do-not-reply at jboss.com  Thu Jun 19 18:35:31 2008
From: do-not-reply at jboss.com (bbucy)
Date: Thu, 19 Jun 2008 18:35:31 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Schema Validation - Failed to read
	schema document
Message-ID: <29274569.1213914931493.JavaMail.jboss@colo-br-02.atl.jboss.com>

Trying to turn on Schema Validation for a webservice I have created.  All is ok running without validation, wsconsume has no issues generating artifacts on the server side, nor any issues running wsconsume on client side, nor any issue running the client and getting a response from the server when schema validation is NOT enabled.  But, as soon as I turn on schema validation, I get the following error on the server.

17:03:59,347 INFO  [SOAPBodyElementDoc] Validating: XML_VALID
17:03:59,363 WARN  [StrictlyValidErrorHandler] org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'OneCardTxnRequest.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
17:03:59,363 WARN  [StrictlyValidErrorHandler] org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'OneCardTxnResponse.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
17:03:59,363 ERROR [StrictlyValidErrorHandler] org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 'ocreq:OCReq' to a(n) 'element declaration' component.
17:03:59,363 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
org.jboss.ws.WSException: org.xml.sax.SAXException: src-resolve: Cannot resolve the name 'ocreq:OCReq' to a(n) 'element declaration' component.
	at org.jboss.ws.WSException.rethrow(WSException.java:68)
	at org.jboss.ws.core.soap.SOAPBodyElementDoc.validatePayload(SOAPBodyElementDoc.java:130)
	at org.jboss.ws.core.soap.SOAPBodyElementDoc.transitionTo(SOAPBodyElementDoc.java:82)
	at org.jboss.ws.core.soap.SOAPContentElement.getObjectValue(SOAPContentElement.java:173)
	at org.jboss.ws.core.EndpointInvocation.transformPayloadValue(EndpointInvocation.java:263)
........

My wsdl does import two xml schemas that represent the request and response documents.  Actually, had this as a single schema, but thought I'd break it up too see if the issue was dealing with both elements.  Anways, a snippet of the wsdl is as follows.

<wsdl:definitions xmlns="http://schemas.xmlsoap.org/wsdl/" 
				  xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" 
				  xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
				  xmlns:ocreq="http://request.doc.onecard.exchange.hps.com/" 
				  xmlns:ocrsp="http://response.doc.onecard.exchange.hps.com/" 
				  xmlns:tns="http://ws.onecard.exchange.hps.com/"
				  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
				  targetNamespace="http://ws.onecard.exchange.hps.com/">
	<wsdl:types>
		<xs:schema targetNamespace="http://ws.onecard.exchange.hps.com/" version="1.0" xmlns:tns="http://ws.onecard.exchange.hps.com/" xmlns:ocreq="http://request.doc.onecard.exchange.hps.com/" xmlns:ocrsp="http://response.doc.onecard.exchange.hps.com/" xmlns:xs="http://www.w3.org/2001/XMLSchema">
			<xs:import schemaLocation="OneCardTxnRequest.xsd" namespace="http://request.doc.onecard.exchange.hps.com/"/>
			<xs:import schemaLocation="OneCardTxnResponse.xsd" namespace="http://response.doc.onecard.exchange.hps.com/"/>
			<xs:element name="doTransaction" type="tns:doTransaction"/>
			<xs:element name="doTransactionResponse" type="tns:doTransactionResponse"/>
			<xs:complexType name="doTransaction">
				<xs:sequence>
					<xs:element minOccurs="0" ref="ocreq:OCReq"/>
				</xs:sequence>
			</xs:complexType>
			<xs:complexType name="doTransactionResponse">
				<xs:sequence>
					<xs:element minOccurs="0" ref="ocrsp:OCRsp"/>
				</xs:sequence>
			</xs:complexType>
		</xs:schema>
	</wsdl:types>
.................
</wsdl:definitions>

And a snippet of my Service implementation class is as follows.

@WebService(serviceName="OneCardService", portName = "OneCardInterface", endpointInterface="com.hps.exchange.onecard.ws.OneCardInterfaceType",
		targetNamespace = "http://ws.onecard.exchange.hps.com/", wsdlLocation = "WEB-INF/wsdl/OneCard.wsdl" )
@SchemaValidation
public class OneCardInterface extends SpringBeanAutowiringSupport implements OneCardInterfaceType
{
......
}

I do actually generate my artifacts using wsconsume in a different project and then copy my wsdl and the two xml schemas to my WAR's WEB-INF/wsdl directory.  Not sure, if that could be effecting anything.  Kind of running around in circles at this point.  Any ideas would be greatly, greatly appreciated.  Thanks, Bob

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159403#4159403

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159403


From balanscott at gmail.com  Thu Jun 19 20:26:46 2008
From: balanscott at gmail.com (Alan Scott)
Date: Thu, 19 Jun 2008 20:26:46 -0400
Subject: [jbossws-users] EJB v3 Compatibilities with Apache Axis
Message-ID: <485AF946.3050506@gmail.com>

Is there any way to use an EJBv3 webservice deployed in jbossws with a 
solution that is trying to access it via Apache Axis? The core issue is 
that this is fromm a vendor system and for whatever reason the vendor 
system has the params to our deployed web service mapped but when the 
web service is invoked it is not getting any of the params.

Any assistance would be greatly appreciated.


From do-not-reply at jboss.com  Fri Jun 20 03:47:51 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 20 Jun 2008 03:47:51 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Schema Validation - Failed to read
	schema document
Message-ID: <6107678.1213948071911.JavaMail.jboss@colo-br-02.atl.jboss.com>

Are you having this issue only with more than one imported schema? In this case please see http://jira.jboss.org/jira/browse/JBWS-2235

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159465#4159465

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159465


From do-not-reply at jboss.com  Fri Jun 20 03:51:40 2008
From: do-not-reply at jboss.com (FrankTheTank)
Date: Fri, 20 Jun 2008 03:51:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBoss Shutdown hook
Message-ID: <19686256.1213948300796.JavaMail.jboss@colo-br-02.atl.jboss.com>

You have your concepts mixed up.

A shutdown hook is a (or multiple) task you can add to the system that will then be executed when the system recieves a shutdown from the OS.

So, lets say you have a connection somewhere and you want it to be closed gracefully when the system shuts down. You would create a task that does exactly this and register it with the shutdown hook.

System.exit() tells the application to abort and (I'm only guessing now) would then call the shutdown hook.

Someone correct me if I am wrong.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159469#4159469

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159469


From do-not-reply at jboss.com  Fri Jun 20 08:54:55 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Fri, 20 Jun 2008 08:54:55 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBossWS 3.0.2 Released
Message-ID: <30324148.1213966495832.JavaMail.jboss@colo-br-02.atl.jboss.com>

We're happy to announce the release of JBossWS 3.0.2 GA that includes Native (fully certified JAX-WS web services implementation), Metro  and Apache CXF integration

Native runs on jboss-5.0.0.Beta4, jboss-4.2.2 and jboss-4.2.1
Both Metro and CXF run on jboss-5.0.0.Beta4 and jboss-4.2.2

JAXWS brings to web services what EJB3 brings to EJB. With its greatly simplified programming model and functional enhancements it is designed to take the place of previous JAX-RPC web service implementations.

The binaries, including the samples can be obtained here:
http://labs.jboss.com/jbossws/downloads/

Installation instructions can be found here:
http://jbws.dyndns.org/mediawiki/index.php/Main_Page

To get started please have a look at the Quick Start and User Guide:
http://jbws.dyndns.org/mediawiki/index.php/Quick_Start
http://jbws.dyndns.org/mediawiki/index.php/JAX-WS_User_Guide

If you don't know it already, you'll be surprised how easy it is to do Web Services.

Big thanks to the team and many contributors for all the hard work to make this release possible.

The JBossWS team 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159549#4159549

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159549


From balanscott at gmail.com  Fri Jun 20 09:07:58 2008
From: balanscott at gmail.com (Alan Scott)
Date: Fri, 20 Jun 2008 09:07:58 -0400
Subject: [jbossws-users] Can Apache Axis use EJBv3 Based Web Services
Message-ID: <485BABAE.6020500@gmail.com>

Can vendor systems that use Apache Axis as their WS layer read and use 
EJBv3 based web services? We are having an issue with a vendors system 
and we can clearly show we are passing the params to our web service in 
their technology; however, the web service never get the params. When we 
use SOAP-UI or the Web Services Explorer in Eclipse everything works great.

Any recommendations, web links or help would be greatly appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossws-users/attachments/20080620/bb87f898/attachment.html 

From balanscott at gmail.com  Fri Jun 20 09:10:32 2008
From: balanscott at gmail.com (Alan Scott)
Date: Fri, 20 Jun 2008 09:10:32 -0400
Subject: [jbossws-users] [JBossWS] - EJB Web Service Stateful?
In-Reply-To: <1521007.1213796588116.JavaMail.jboss@colo-br-02.atl.jboss.com>
References: <1521007.1213796588116.JavaMail.jboss@colo-br-02.atl.jboss.com>
Message-ID: <485BAC48.1040804@gmail.com>

shaikbash wrote:
> Hi,
> I have developed a simple EJB based web-service as shown below:
>
> @Stateless
> @Remote(MySession.class)
> @WebService(endpointInterface = "test.MySession")
> @WebContext(contextRoot = "/mySession")
> public class MySessionBean implements MySession
> {
>   private int count;
>   
>   public int getCount()
>   {
>     return ++count;
>   }
> }
>
> This is deployed on JBOSS 4.2.2 server.
> I have a servlet based client, which connects to this service using the jbossws-3.0.1-native-2.0.4 jars. Whenever I call the getCount() method from the client I get an incremented value. I was expecting to always get 1 as the return value, since my EJB is stateless. My question is how is it retaining the state? Any light on this is greately appreciated.
>
>
> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158989#4158989
>
> Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158989
> _______________________________________________
> jbossws-users mailing list
> jbossws-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossws-users
>
>   
We always do these within a conversation context of a web application. 
In other words, our Seam web application form/action calls the service. 
Other than that everything else does looks the same to me.




From balanscott at gmail.com  Fri Jun 20 09:15:27 2008
From: balanscott at gmail.com (Alan Scott)
Date: Fri, 20 Jun 2008 09:15:27 -0400
Subject: [jbossws-users] Test Post
Message-ID: <485BAD6F.8090407@gmail.com>

None of my post seem to be posting..


From dlofthouse at redhat.com  Fri Jun 20 09:20:59 2008
From: dlofthouse at redhat.com (Darran Lofthouse)
Date: Fri, 20 Jun 2008 14:20:59 +0100
Subject: [jbossws-users] Test Post
In-Reply-To: <485BAD6F.8090407@gmail.com>
References: <485BAD6F.8090407@gmail.com>
Message-ID: <485BAEBB.5030702@redhat.com>

This mailing list is just really just used as an archive to the forums, 
if you have questions you should post them directly to the forum: -

http://www.jboss.com/index.html?module=bb&op=viewforum&f=200

Regards,
Darran Lofthouse.


Alan Scott wrote:
> None of my post seem to be posting..
> _______________________________________________
> jbossws-users mailing list
> jbossws-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossws-users



From do-not-reply at jboss.com  Fri Jun 20 09:33:08 2008
From: do-not-reply at jboss.com (bbucy)
Date: Fri, 20 Jun 2008 09:33:08 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Schema Validation - Failed to read
	schema document
Message-ID: <19159198.1213968788091.JavaMail.jboss@colo-br-02.atl.jboss.com>

Actually originally I was importing a single schema (e.g. OneCardTxn.xsd) which had two elements defined (e.g. OCReq and OCRsp).  I was receiving the exact same error just failing on the single import.

So, I ended up changing it to two schemas (e.g. OneCardTxnRequest.xml and OneCardTxnResponse.xml) thinking that may have been the problem.

By the way, I am using jbossws-3.0.1-native-2.0.4.GA deployed on JBoss_4_2_2_GA with JBoss Messaging 1.4.0.SP3 replacing JBossMQ.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159562#4159562

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159562


From do-not-reply at jboss.com  Fri Jun 20 12:33:38 2008
From: do-not-reply at jboss.com (gcoleman)
Date: Fri, 20 Jun 2008 12:33:38 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: EJB Web Service Stateful?
Message-ID: <32951464.1213979618472.JavaMail.jboss@colo-br-02.atl.jboss.com>

Stateless EJBs are only stateless in the sense that they're not associated with any particular client session.

The actual EJB instances can and will be pooled by the application server.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159612#4159612

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159612


From do-not-reply at jboss.com  Fri Jun 20 14:22:53 2008
From: do-not-reply at jboss.com (yangg)
Date: Fri, 20 Jun 2008 14:22:53 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: What controls the SOAP version used
	in JBoss
Message-ID: <14202464.1213986173719.JavaMail.jboss@colo-br-02.atl.jboss.com>

Amit,

I'm having a similar problem. Did you find the answer to how to control the SOAP version in JBoss 4.2.2?

Thanks,
Gang

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159648#4159648

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159648


From do-not-reply at jboss.com  Sun Jun 22 13:12:10 2008
From: do-not-reply at jboss.com (argol1278)
Date: Sun, 22 Jun 2008 13:12:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - wsconsume https
Message-ID: <22489719.1214154730112.JavaMail.jboss@colo-br-02.atl.jboss.com>

hi all

I want to develop web service over https but i have problem with generating artifactes from https:
-----------------------------------------------------
1) It is possible to generate artifactes from https://site/wsdl.wsdl ?
------------------------------------------------------
I configure tomcat ssl 
jboss-4.2.2.GA\server\default\deploy\jboss-web.deployer\servers  
and web.xml in my application

<security-constraint>
  |     <web-resource-collection>
  |        <web-resource-name>Protected Context</web-resource-name>
  |          <url-pattern>/*</url-pattern>
  |     </web-resource-collection> -->
  | 	<!-- auth-constraint goes here if you requre authentication -->
  | 	<!--<user-data-constraint>
  | 			<transport-guarantee>CONFIDENTIAL</transport-guarantee>
  | 		</user-data-constraint>
  | 	</security-constraint>
  | 
-----------------------------------------------------
2) I must configure somthing else to work with ssl web service?
-----------------------------------------------------

my ant task   <?xml version="1.0" encoding="UTF-8"?> 
  | <project name="helloworld" default="run" basedir="."> 
  |  <description> 
  |   Pierwszy ant 
  |  </description> 
  |  <path id="web.services.classpath">
  |     <fileset dir="C:/Java/jdk1.5.0_15/lib" includes="*.jar" />
  |     <fileset dir="C:/jboss-4.2.2.GA/lib/endorsed/"  includes="*.jar" />
  |     <fileset dir="C:/jboss-4.2.2.GA/lib/" includes="*.jar" />
  |     <fileset dir="C:/jboss-4.2.2.GA/client/" includes="*.jar" />
  | 	
  | </path>
  | 
  |  
  | <target name="run">
  | <taskdef name="wsconsume" classname="org.jboss.wsf.spi.tools.ant.WSConsumeTask">
  |  		<classpath refid="web.services.classpath"/>						
  |  </taskdef>	
  |   
  | 
  | <wsconsume
  | fork="true"
  | destdir="d:\ant\bin"
  | sourcedestdir="d:\ant\src"
  | keep="true"
  | wsdl="https://127.0.0.1/Bank/Authorization?wsdl"
  | package="endpoint"
  | verbose="true">
  | <jvmarg value="-Djavax.net.ssl.keyStore=server.keystore -Djavax.net.ssl.keyStorePassword=pracamgr -Djavax.net.ssl.trustStore=server.keystore -Djavax.net.ssl.trustStorePassword=pracamgr" /> 
  | </wsconsume>
  | </target>
  | </project>
  | 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159784#4159784

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159784


From do-not-reply at jboss.com  Mon Jun 23 13:23:36 2008
From: do-not-reply at jboss.com (pisce)
Date: Mon, 23 Jun 2008 13:23:36 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Using Jax-WS RI with JBoss AS 4.2.2?
Message-ID: <27149990.1214241816323.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello all,

I have a simple question. How do you make an EAR app (EJB endpoints) work with Jax-ws RI on JBoss AS 4.2.2, instead of (or in collaboration with) JBossWs?

I tried to remove 'jbossws.sar' from server/default/deploy, and ship Jax-ws RI 2.1.4's jars into my EAR's /lib directory. JBoss AS seems to hot-deploy fine, but the Endpoint is never registered, and the WSDL is never published. I guess I could need several descriptors that are located in 'jbossws.sar', but they all refer to JBossWs beans...

If I ship Jax-ws RI's jars into my EAR, and don't remove 'jbossws.sar', I get weird errors probably due to conflictual jars versions.

Any help is welcome

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160000#4160000

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160000


From do-not-reply at jboss.com  Tue Jun 24 11:22:44 2008
From: do-not-reply at jboss.com (sgtw_speed)
Date: Tue, 24 Jun 2008 11:22:44 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WebService behind LB/SSL Proxy
Message-ID: <17806851.1214320964796.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi SunFire,

Did you ever manage to get this sorted out?  We are experiencing the same issue.  

We have an F5 load balancer but the WSDL which gets returned always shows the direct address of one of the cluster nodes instead of the url for the F5 :(

Thus, the only part that is being load balanced is retrieval of the WSDL !!

You say you solved the problem with the domain name, so you might have the answer :)

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160273#4160273

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160273


From do-not-reply at jboss.com  Tue Jun 24 13:33:28 2008
From: do-not-reply at jboss.com (dlopezleon)
Date: Tue, 24 Jun 2008 13:33:28 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: problem with wsconsume
Message-ID: <20103695.1214328808112.JavaMail.jboss@colo-br-02.atl.jboss.com>

I'm having  the same problem with jboss-4.2.2.GA + jbossws-cxf-3.0.2.GA and my path doesn't contain any space.

  | diego at localhost:~/bin/jboss-4.2.2.GA/client$ ../bin/wsconsume.sh -k -p ar.com.selenca.ws.client -o /home/diego/dev/java/examples-workspace/jbossws-client-example/src/main/java/ http://127.0.0.1:8080/jbossws-server-example-1.0-SNAPSHOT/ProfileMgmtBean?wsdl
  | /home/diego/bin/jboss-4.2.2.GA/client
  | Exception in thread "main" java.lang.IllegalStateException: Failed to load: org.jboss.ws.tools.jaxws.impl.SunRIConsumerFactoryImpl
  | ...
  | Caused by: java.lang.ClassNotFoundException: org.jboss.ws.tools.jaxws.impl.SunRIConsumerFactoryImpl
  | ...
  | 
looking at wsconsume.sh it loads into the classpath some libraries that doesn't exist in the 'client' folder from the AS. It looks for 
jaxws-tools.jar
jaxws-rt.jar
streambuffer.jar
stax-ex.jar

and I've had to rename jbossws-metro-client.jar to jbossws-metro-client.jar in that script.
Should those libraries be in the jbossws-cxf distribution?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160308#4160308

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160308


From do-not-reply at jboss.com  Tue Jun 24 19:33:10 2008
From: do-not-reply at jboss.com (shaikbash)
Date: Tue, 24 Jun 2008 19:33:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: EJB Web Service Stateful?
Message-ID: <16226620.1214350390410.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thanks for the reply. 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160392#4160392

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160392


From do-not-reply at jboss.com  Wed Jun 25 02:38:23 2008
From: do-not-reply at jboss.com (dee_n)
Date: Wed, 25 Jun 2008 02:38:23 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Wsconsume Error - with <xs:any> elements
Message-ID: <30949659.1214375903145.JavaMail.jboss@colo-br-02.atl.jboss.com>

When I try to create client stubs from a deployed WSDL using wsconsume, I get the following error:

 
[ERROR] Property "Any" is already defined. Use <jaxb:property> to resolve this conflict.
line 18 of file:/C:/JBoss/jboss-4.2.2.GA/bin/gismo.wsdl

The error occurs on all the lines in the wsdl where <s:any> elements appear. Part of the wsdl is as follows: 

.
.
.
<wsdl:types>
    <s:element name="AddLPResponse">
        <s:complexType>
          <s:sequence>
            <s:element minOccurs="0" maxOccurs="1" name="QPResult">
              <s:complexType>
                <s:sequence>
                  <s:any minOccurs="0" maxOccurs="unbounded" namespace="http://www.w3.org/2001/XMLSchema" processContents="lax" />
                  <s:any minOccurs="1" namespace="urn:schemas-microsoft-com:xml-diffgram-v1" processContents="lax" />
                </s:sequence>
              </s:complexType>
            </s:element>
          </s:sequence>
        </s:complexType>
      </s:element>
.
.
.
</wsdl:types>

Can any one please help with this?



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160433#4160433

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160433


From do-not-reply at jboss.com  Wed Jun 25 03:55:09 2008
From: do-not-reply at jboss.com (helmutdoe)
Date: Wed, 25 Jun 2008 03:55:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Need help : JBossWS Security!
Message-ID: <14732333.1214380509393.JavaMail.jboss@colo-br-02.atl.jboss.com>

Same Problem here ...

$Proxy29 cannot be cast to org.jboss.ws.core.StubExt

did someone solve this problem?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160445#4160445

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160445


From do-not-reply at jboss.com  Wed Jun 25 04:43:35 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 25 Jun 2008 04:43:35 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Using Jax-WS RI with JBoss AS 4.2.2?
Message-ID: <12081273.1214383415908.JavaMail.jboss@colo-br-02.atl.jboss.com>

You can't change the webservice stack that way, at least it's not that simple. Since JBossWS 3.0 we however support the Metro (jaxws RI) stack, see http://jbws.dyndns.org/mediawiki/index.php?title=WSF.
In short, simply download the latest jbossws-metro-3.0.2, install it and you're ready to go with your jaxws-ri based application.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160462#4160462

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160462


From do-not-reply at jboss.com  Wed Jun 25 05:33:57 2008
From: do-not-reply at jboss.com (jsports)
Date: Wed, 25 Jun 2008 05:33:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Can not visit http://jbws.dyndns.org
	for jbossws documents!
Message-ID: <5222667.1214386437373.JavaMail.jboss@colo-br-02.atl.jboss.com>

why move them from jboss.org to http://jbws.dyndns.org/?



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160475#4160475

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160475


From do-not-reply at jboss.com  Wed Jun 25 05:37:08 2008
From: do-not-reply at jboss.com (jsports)
Date: Wed, 25 Jun 2008 05:37:08 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Can not visit
	http://jbws.dyndns.org for jbossws documen
Message-ID: <18566853.1214386628236.JavaMail.jboss@colo-br-02.atl.jboss.com>

and the jbossws download doest not contain any documents.




View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160476#4160476

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160476


From do-not-reply at jboss.com  Wed Jun 25 06:02:10 2008
From: do-not-reply at jboss.com (timeagentess)
Date: Wed, 25 Jun 2008 06:02:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - new format required for wsdl in
	JBossws>2.0.0?
Message-ID: <27424461.1214388130491.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello all,

I have some problems transitioning from JBoss 4.0.5 + JBossws 2.0.0 to JBoss 4.2.0 + JBossws 3.0.2.
A simple web service (deployed as an annotated EJB within an ear) which was working perfectly in the initial configuration cannot be consumed by wsconsume in the second configuration:

anonymous wrote : [wsconsume] Failed to read the WSDL document: http://nifhel:8080/webservices-ws/services/WSTwo?wsdl, because 1) could not find the document; /2) the document could not be read; 3) the root element of the document is not <wsdl:definitions>.
  | [wsconsume] [ERROR] failed.noservice=Could not find wsdl:service in the provided WSDL(s): 
  | [wsconsume]  At least one WSDL with at least one service definition needs to be provided.
  | [wsconsume] 	Failed to parse the WSDL.
  | ...
  | 

My generated WSDL file indeed does not have a wsdl:service tag as root, it looks like this (with some parts eliminated for clarity):

anonymous wrote : 
  | <definitions name='WSTwoServiceBeanService' targetNamespace='http://localhost:8080/atb' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://localhost:8080/atb' xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
  |  
  |   <xs:schema targetNamespace='http://localhost:8080/atb' version='1.0' xmlns:tns='http://localhost:8080/atb' xmlns:xs='http://www.w3.org/2001/XMLSchema'>
  |    <xs:element name='hello' type='tns:hello'/>
  |    <xs:element name='helloResponse' type='tns:helloResponse'/>
  |    <xs:complexType name='hello'>
  |     <xs:sequence>
  |      <xs:element minOccurs='0' name='arg0' type='xs:string'/>
  |     </xs:sequence>
  | 
  |    </xs:complexType>
  |    <xs:complexType name='helloResponse'>
  |     <xs:sequence>
  |      <xs:element minOccurs='0' name='return' type='xs:string'/>
  |     </xs:sequence>
  |    </xs:complexType>
  |   </xs:schema>
  |  
  |  [...]
  | 

How can I influence the generation of a wsdl document which complies to what wsconsume seems to expect? Or is there another mistake I might have made?

Additional things I tried: Searching around led me to this forum post: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102431
and this JIRA issue: http://jira.jboss.org/jira/browse/JBESB-1719, which seem (?) to be related to my problem.

Setting fork="true" for wsconsume like suggested in the forum post linked above led to the gnu.getopt.LongOpt class to be reported as not found, and after adding the corresponding jar to the classpath I get an almost identical error to the one I've started with:
anonymous wrote : [wsconsume] parsing WSDL...
  | [wsconsume] [ERROR] Connection reset
  | [wsconsume] Failed to read the WSDL document: http://nifhel:8080/webservices-ws/services/WSTwo?wsdl, because 1) could not find the document; /2) the document could not be read; 3) the root element of the document is not <wsdl:definitions>.
  | [wsconsume] [ERROR] failed.noservice=Could not find wsdl:service in the provided WSDL(s): 
  | [wsconsume]  At least one WSDL with at least one service definition needs to be provided.
  | [wsconsume] 	Failed to parse the WSDL.
  | [wsconsume] Failed to invoke WsImport
  | [wsconsume] java.lang.IllegalStateException: WsImport invocation failed. Try the verbose switch for more information
  | [wsconsume] 	at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:234)
  | [wsconsume] 	at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:223)
  | [wsconsume] 	at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:81)
  | [wsconsume] Error: Could not import. (use --verbose to see full traces)
  | [wsconsume] java.lang.IllegalStateException: WsImport invocation failed. Try the verbose switch for more information
  | [wsconsume] 	at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:234)
  | [wsconsume] 	at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:223)
  | [wsconsume] 	at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:81)

Can anyone help with this issue? 
Thank you very much!

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160485#4160485

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160485


From do-not-reply at jboss.com  Wed Jun 25 06:24:46 2008
From: do-not-reply at jboss.com (timeagentess)
Date: Wed, 25 Jun 2008 06:24:46 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Need help : JBossWS Security!
Message-ID: <18109368.1214389486124.JavaMail.jboss@colo-br-02.atl.jboss.com>

I can confirm the same issue occurring when working with JBoss 4.0.5 & JBossWS 2.0.0.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160491#4160491

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160491


From do-not-reply at jboss.com  Wed Jun 25 09:46:17 2008
From: do-not-reply at jboss.com (helmutdoe)
Date: Wed, 25 Jun 2008 09:46:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Need help : JBossWS Security!
Message-ID: <4284155.1214401577551.JavaMail.jboss@colo-br-02.atl.jboss.com>

"helmutdoe" wrote : Same Problem here ...
  | 
  | $Proxy29 cannot be cast to org.jboss.ws.core.StubExt
  | 
  | did someone solve this problem?

Im using JBoss AS 4.2.2 GA & JBossWS native 3.0.2 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160552#4160552

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160552


From do-not-reply at jboss.com  Wed Jun 25 10:10:36 2008
From: do-not-reply at jboss.com (timeagentess)
Date: Wed, 25 Jun 2008 10:10:36 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Need help : JBossWS Security!
Message-ID: <10406130.1214403036135.JavaMail.jboss@colo-br-02.atl.jboss.com>

I apologize, I might have been a bit ambiguous -- I wanted to say that I encountered the same "<wsse:Security> is missing" error when the client pings the web service.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160562#4160562

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160562


From do-not-reply at jboss.com  Wed Jun 25 10:33:04 2008
From: do-not-reply at jboss.com (zeko)
Date: Wed, 25 Jun 2008 10:33:04 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Error on starting
	jbossws-native-3.0.2.GA with custom server
Message-ID: <1067531.1214404384142.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

our server setup defines follwowing properties:

  |                  -Djboss.platform.mbeanserver \
  |                  -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl \
  |                  -Djboss.server.base.dir=${DOMAIN_HOME}/config \
  |                  -Djboss.server.home.dir=${DOMAIN_HOME} \
  |                  -Djboss.server.home.url=file:${DOMAIN_HOME}/config \
  |                  -Djboss.server.temp.dir=${DOMAIN_HOME}/tmp \
  |                  -Djboss.server.data.dir=${DOMAIN_HOME}/data \
  |                  -Djboss.server.log.dir=${DOMAIN_HOME}/log"
  | 
  | 

which runs fine using the previous version of JbossWS.
Using the standard directory structure as depicted in 
http://docs.jboss.org/jbossas/jboss4guide/r2/html/ch01.html and *not* defining those properties is fine, too.

So I gues there must be some hard coded dependencies.

first error is:

  | 16:04:38,815 ERROR [AbstractKernelController] Error installing to Configured: name=WSDeployerHook_JAXWS_PRE_JSE state=Instantiated mode=Manu
  | al requiredState=Installed
  | org.jboss.joinpoint.spi.JoinpointException: Property runtime not found for AbstractBeanInfo at 3e1d25{name=org.jboss.wsf.container.jboss42.JAXW
  | SDeployerHookPreJSE classInfo= properties=[deploymentType, class, phaseTwoInterceptors, deploymentManagerName, deploymentModelFactory, phase
  | OneInterceptors, deploymentAspectManager] methods=[, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ] constructors=[] e
  | vents=}
  |         at org.jboss.kernel.plugins.config.Configurator.resolveProperty(Configurator.java:659)
  |         at org.jboss.kernel.plugins.config.Configurator.getPropertySetterJoinPoint(Configurator.java:433)
  |         at org.jboss.kernel.plugins.config.Configurator.getPropertySetterJoinPoints(Configurator.java:398)
  |         at org.jboss.kernel.plugins.config.AbstractKernelConfigurator.getPropertySetterJoinPoints(AbstractKernelConfigurator.java:112)
  |         at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$ConfigureAction.installAction(KernelControllerContextActions.j
  | ava:313)
  |         at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$KernelControllerContextAction.install(KernelControllerContextA
  | ctions.java:147)
  |         at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
  |         at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)
  |         at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:593)
  |         at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:346)
  |         at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:438)
  |         at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:379)
  |         at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:263)
  |         at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:164)
  |         at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.changeBean(AbstractKernelDeployer.java:327)
  |         at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.changeBeans(AbstractKernelDeployer.java:311)
  |         at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.change(AbstractKernelDeployer.java:139)
  |         at org.jboss.kernel.deployment.jboss.JBossBeanDeployment.startService(JBossBeanDeployment.java:81)
  |         at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
  |         at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
  |         at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
  |         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  |         at java.lang.reflect.Method.invoke(Method.java:585)
  |         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  |         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  |         at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
  |         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  |         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  |         at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
  |         at $Proxy0.start(Unknown Source)
  |         at org.jboss.system.ServiceController.start(ServiceController.java:417)
  |         at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
  |         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  |         at java.lang.reflect.Method.invoke(Method.java:585)
  |         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  |         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  |         at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
  |         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  |         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  |         at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  |         at $Proxy20.start(Unknown Source)
  |         at org.jboss.deployment.SimpleSubDeployerSupport.startService(SimpleSubDeployerSupport.java:356)
  |         at org.jboss.deployment.SimpleSubDeployerSupport.start(SimpleSubDeployerSupport.java:127)
  |         at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
  |         at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
  |         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
  |         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
  |         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 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  |         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  |         at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
  |         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  |         at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
  |         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  |         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  |         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  |         at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  |         at $Proxy10.deploy(Unknown Source)
  |         at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
  |         at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
  |         at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
  |         at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
  |         at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
  |         at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
  |         at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
  |         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  |         at java.lang.reflect.Method.invoke(Method.java:585)
  |         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  |         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  |         at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
  |         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  |         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  |         at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
  |         at $Proxy0.start(Unknown Source)
  |         at org.jboss.system.ServiceController.start(ServiceController.java:417)
  |         at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
  |         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  |         at java.lang.reflect.Method.invoke(Method.java:585)
  |         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  |         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  |         at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
  |         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  |         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  |         at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  |         at $Proxy4.start(Unknown Source)
  |         at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
  |         at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
  |         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
  |         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
  |         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
  |         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  |         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMet

Any ideas?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160568#4160568

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160568


From do-not-reply at jboss.com  Wed Jun 25 11:14:18 2008
From: do-not-reply at jboss.com (marcelotmelo)
Date: Wed, 25 Jun 2008 11:14:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: How to set a parameter mandatory
	for a given operation
Message-ID: <3768723.1214406858159.JavaMail.jboss@colo-br-02.atl.jboss.com>

Have you found an answer to this question?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160579#4160579

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160579


From do-not-reply at jboss.com  Wed Jun 25 11:21:12 2008
From: do-not-reply at jboss.com (d.behrwind)
Date: Wed, 25 Jun 2008 11:21:12 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Trouble using @WebContext to encrypt
	communication
Message-ID: <20971013.1214407272166.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I'd like to use the the @WebContext  annotation in my Seam project to encrypt the whole web service communication as described here: http://jbws.dyndns.org/mediawiki/index.php?title=Secure_transport

My problem is that I don't know which jar to take. I understand that @WebContext  is not part of JAX-WS integrated with Java SE, but ships with the JBossWS jar jbossws-spi.jar. So I tried to put this jar in my war, which always results in the following when deploying to my jboss-4.2.2: 
java.lang.ClassNotFoundException: Unexpected error during load of: com.symtavision.wstest_jbossws.handler.PayloadPrinterService, msg=Bad version number in .class file
  | 	at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:560)
  | 	at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:415)
  | 	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
  | 	at org.jboss.ejb3.Ejb3AnnotationHandler.populateBaseInfo(Ejb3AnnotationHandler.java:293)
  | 	at org.jboss.ejb3.Ejb3DescriptorHandler.populateBaseInfo(Ejb3DescriptorHandler.java:215)
  | 	at org.jboss.ejb3.Ejb3AnnotationHandler.getContainers(Ejb3AnnotationHandler.java:138)
  | 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:486)
  | 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:442)
  | 	at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:423)
  | 	at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:384)
  | 	at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:327)
  | 	at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:77)
  | 	at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
  | 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
  | 	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:585)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
  | 	at $Proxy0.create(Unknown Source)
  | 	at org.jboss.system.ServiceController.create(ServiceController.java:330)
  | 	at org.jboss.system.ServiceController.create(ServiceController.java:273)
  | 	at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:585)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy33.create(Unknown Source)
  | 	at org.jboss.ejb3.EJB3Deployer.create(EJB3Deployer.java:492)
  | 	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 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
  | 	at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
  | 	at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
  | 	at org.jboss.wsf.container.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:76)
  | 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
  | 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy34.create(Unknown Source)
  | 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
  | 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
  | 	at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:585)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy9.deploy(Unknown Source)
  | 	at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
  | 	at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
  | 	at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
  | 	at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
  | 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
  | 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
  | 	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:585)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
  | 	at $Proxy0.start(Unknown Source)
  | 	at org.jboss.system.ServiceController.start(ServiceController.java:417)
  | 	at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:585)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy4.start(Unknown Source)
  | 	at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
  | 	at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
  | 	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 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy5.deploy(Unknown Source)
  | 	at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
  | 	at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
  | 	at org.jboss.Main.boot(Main.java:200)
  | 	at org.jboss.Main$1.run(Main.java:508)
  | 	at java.lang.Thread.run(Thread.java:595)
  | Caused by: java.lang.UnsupportedClassVersionError: Bad version number in .class file
  | 	at java.lang.ClassLoader.defineClass1(Native Method)
  | 	at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
  | 	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
  | 	at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
  | 	at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
  | 	at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
  | 	at java.security.AccessController.doPrivileged(Native Method)
  | 	at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
  | 	at org.jboss.mx.loading.RepositoryClassLoader.findClassLocally(RepositoryClassLoader.java:682)
  | 	at org.jboss.mx.loading.RepositoryClassLoader.findClass(RepositoryClassLoader.java:662)
  | 	at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
  | 	at org.jboss.mx.loading.RepositoryClassLoader.loadClassLocally(RepositoryClassLoader.java:200)
  | 	at org.jboss.mx.loading.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:131)
  | 	at org.jboss.mx.loading.LoadMgr3.nextTask(LoadMgr3.java:399)
  | 	at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:527)
  | 	... 123 more

(I tried with both: the jar found in jboss and the one from the JBossWS binaries)

So, what steps are necessary to make use of all JBossWS features (not only JAX-WS)?

Any help is appreciated. Thanks in advance!

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160582#4160582

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160582


From do-not-reply at jboss.com  Wed Jun 25 12:59:59 2008
From: do-not-reply at jboss.com (helmutdoe)
Date: Wed, 25 Jun 2008 12:59:59 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Need help : JBossWS Security!
Message-ID: <32015280.1214413199875.JavaMail.jboss@colo-br-02.atl.jboss.com>

The <wsse:Security> missing occurs if i remove the followin line on my code.

 ((StubExt) ksb).setConfigName("Standard WSSecurity Client");
  | 

And this is traceable to me because then the client application do not know how he should configure the SecurityHandlers. Since i had debugged the client code i was able to locate when the exception occurs.


  | ((StubExt) ksb).setSecurityConfig("META-INF/jboss-wsse-client.xml");
  | 

I have a problem on understanding how the client side gets this xml. Since Webservices have to be interoperable only the wsdl should be public.

Im looking forward to fix these problems

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160606#4160606

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160606


From do-not-reply at jboss.com  Wed Jun 25 14:07:49 2008
From: do-not-reply at jboss.com (gryffin)
Date: Wed, 25 Jun 2008 14:07:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - SSL not activating
Message-ID: <7370428.1214417269732.JavaMail.jboss@colo-br-02.atl.jboss.com>

I'm deploying an EJB3 based web service on jboss 4.2.2. It deploys okay, and I can access it on port 8443, but not via https. JBoss says it's deployed to https, but only response via http. 

I'm not getting any errors in the log, can anyone give me a good idea as to what I'm missing? What needs to be set in order to tell JBoss to deploy via https? Thx.

app. policy from login-config.xml
    <application-policy name="nlsapidev">
  | 	    <authentication>
  | 	      <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule"
  | 	        flag="required">
  | 	        <module-option name="usersProperties">props/jbossws-users.properties</module-option>
  | 	        <module-option name="rolesProperties">props/jbossws-roles.properties</module-option>
  | 	        <module-option name="unauthenticatedIdentity">anonymous</module-option>
  | 	      </login-module>
  | 	    </authentication>
  |   	</application-policy>



Deployed MetaData:

  | UnifiedMetaData: 
  |  implementation: jbossws-3.0.1-native-2.0.4.GA (build=200803312044)
  |  deploymentName: TimeService.jar
  |  securityDomain: nlsapidev
  | 
  | ServiceMetaData:
  |  qname={http://www.boeing.com/nmt/ejb3/TimeService}TimeService
  |  refName=null
  |  wsdName=null
  |  wsdlFile=null
  |  wsdlLocation=file:/C:/jboss-4.2.2.GA/server/default/tmp/jbossws/TimeService7841.wsdl
  |  jaxrpcMapping=null
  |  publishLocation=null
  |  securityConfig=found
  |  properties=null
  | 
  | TypesMetaData: 
  |   [complexType={http://www.w3.org/2001/XMLSchema}string,javaType=java.lang.String]
  | 
  | 
  | ServerEndpointMetaData as shown in the log:
  |  type=JAXWS
  |  qname={http://www.boeing.com/nmt/ejb3/TimeService}TimeAgentPortBindingNamePort
  |  id=jboss.ws:context=TimeService,endpoint=TimeServiceBean
  |  address=https://127.0.0.1:8443/TimeService
  |  binding=http://schemas.xmlsoap.org/wsdl/soap/http
  |  linkName=TimeServiceBean
  |  implName=com.boeing.nmt.ejb3.TimeServiceBean
  |  seiName=com.boeing.nmt.ejb3.TimeServiceBean
  |  serviceMode=null
  |  portComponentName=null
  |  contextRoot=/TimeService
  |  urlPattern=/*
  |  configFile=META-INF/standard-jaxws-endpoint-config.xml
  |  configName=Standard WSSecurity Endpoint
  |  authMethod=BASIC
  |  transportGuarantee=CONFIDENTIAL
  |  secureWSDLAccess=false
  |  properties={}
  | 
  | OperationMetaData:
  |  qname={http://www.boeing.com/nmt/ejb3/TimeService}getCurrentTime
  |  javaName=getTime
  |  style=rpc/literal
  |  oneWay=false
  |  soapAction=getThisTimeSoapAction
  | ReturnMetaData:
  |  xmlName=timeThis
  |  partName=timeThis
  |  xmlType={http://www.w3.org/2001/XMLSchema}string
  |  javaType=java.lang.String
  |  mode=OUT
  |  inHeader=false
  |  index=-1
  | 
  | HandlerMetaDataJAXWS:
  |  type=POST
  |  name=WSSecurity Handler
  |  class=class org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer
  |  params=[]
  |  protocols=##SOAP11_HTTP
  |  services=null
  |  ports=null
  | 
  | HandlerMetaDataJAXWS:
  |  type=POST
  |  name=Recording Handler
  |  class=class org.jboss.wsf.framework.invocation.RecordingServerHandler
  |  params=[]
  |  protocols=##SOAP11_HTTP
  |  services=null
  |  ports=null


jboss-wsse-server.xml:
<?xml version="1.0" encoding="UTF-8"?>
  | 
  | <jboss-ws-security 
  | 			xmlns='http://www.jboss.com/ws-security/config' 
  | 			xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
  |     <key-store-file>C:\jboss-4.2.2.GA\server\default\conf\server.keystore</key-store-file>
  | 	<key-store-password>************</key-store-password>
  | 	<trust-store-file>C:\jboss-4.2.2.GA\server\default\conf\server.truststore</trust-store-file>
  | 	<trust-store-password>*************</trust-store-password>
  | 	<config>
  | 		<sign type="x509v3" alias="nlsapidev"/>   
  | 		<encrypt type="x509v3" alias="nlsapidev"/>
  | 		<requires>
  | 			<signature/>
  | 		</requires>
  | 	</config>
  | </jboss-ws-security>


endpointstandard-jaxws-endpoint-config.xml:

<?xml version="1.0" encoding="UTF-8"?>
  | <jaxws-config xmlns="urn:jboss:jaxws-config:2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:javaee="http://java.sun.com/xml/ns/javaee"
  |               xsi:schemaLocation="urn:jboss:jaxws-config:2.0 jaxws-config_2_0.xsd">
  | 
  |    <endpoint-config>
  |       <config-name>Standard WSSecurity Endpoint</config-name>
  |       <post-handler-chains>
  |          <javaee:handler-chain>
  |             <javaee:protocol-bindings>##SOAP11_HTTP</javaee:protocol-bindings>
  |             <javaee:handler>
  |                <javaee:handler-name>WSSecurity Handler</javaee:handler-name>
  |                <javaee:handler-class>org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer</javaee:handler-class>
  |             </javaee:handler>
  |          </javaee:handler-chain>
  |       </post-handler-chains>
  |    </endpoint-config>
  | 
  | </jaxws-config>



and EJB class info:

@SecurityDomain("nlsapidev")
  | @PermitAll
  | @WebService( //endpointInterface = "com.boeing.nmt.ejb3.TimeServiceEndpoint",
  | 			name="TimeAgentPortBindingName", 
  | 			targetNamespace = "http://www.boeing.com/nmt/ejb3/TimeService",
  | 			serviceName = "TimeService"
  | 			)
  | @SOAPBinding(	style = SOAPBinding.Style.RPC, 
  | 				use=SOAPBinding.Use.LITERAL, 
  | 				parameterStyle=SOAPBinding.ParameterStyle.BARE
  | 				)
  | @WebContext(	contextRoot="/TimeService", 
  | 				urlPattern="/*",
  | 				authMethod="BASIC", 
  | 				transportGuarantee="CONFIDENTIAL",
  | 				secureWSDLAccess=false
  | 				)
  | @EndpointConfig(configName = "Standard WSSecurity Endpoint")
  | @Stateless
  | public class TimeServiceBean implements com.boeing.nmt.ejb3.TimeServiceRemote 
  | {

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160626#4160626

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160626


From do-not-reply at jboss.com  Thu Jun 26 02:22:48 2008
From: do-not-reply at jboss.com (gagan_123456)
Date: Thu, 26 Jun 2008 02:22:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Error while invoking webservice
Message-ID: <27731457.1214461368378.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,
      
       I am working on JBPM BPEL.I tried to deploy the  example hello which is given by JBPM BPEL.It is working fine.I followed the user guide to do this.
       While I am trying to invoke that deployed webservice by "ant test" command  i am getting the following error 
              "Error running jbossws:" 

Please any one help me on this.

Thanks 

 
     

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160740#4160740

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160740


From do-not-reply at jboss.com  Thu Jun 26 03:41:53 2008
From: do-not-reply at jboss.com (timeagentess)
Date: Thu, 26 Jun 2008 03:41:53 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Need help : JBossWS Security!
Message-ID: <30057954.1214466113091.JavaMail.jboss@colo-br-02.atl.jboss.com>

"helmutdoe" wrote : The <wsse:Security> missing occurs if i remove the followin line on my code.
  | 
  |  ((StubExt) ksb).setConfigName("Standard WSSecurity Client");
  |   | 
  | 
  | And this is traceable to me because then the client application do not know how he should configure the SecurityHandlers. Since i had debugged the client code i was able to locate when the exception occurs.
  | 
  | 
  |   | ((StubExt) ksb).setSecurityConfig("META-INF/jboss-wsse-client.xml");
  |   | 
  | 

Hmm, interesting -- I have both lines of code as you mentioned them in my client, but I'm still getting the "missing <wsse:Security>" error. So I must be doing something else wrong, as well :)

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160751#4160751

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160751


From do-not-reply at jboss.com  Thu Jun 26 03:50:15 2008
From: do-not-reply at jboss.com (timeagentess)
Date: Thu, 26 Jun 2008 03:50:15 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: new format required for wsdl in
	JBossws>2.0.0?
Message-ID: <9554244.1214466615259.JavaMail.jboss@colo-br-02.atl.jboss.com>

Never mind, solved -- my bad ;)

For some reason, when working with the newer JBossWS, the wsconsume build script did not know how to resolve the localhost name in the given wsdl location to "localhost" and the wsdl was not found. Replacing the actual name with "localhost" solved the problem. 

Hopefully this helps someone.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160754#4160754

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160754


From do-not-reply at jboss.com  Thu Jun 26 05:48:24 2008
From: do-not-reply at jboss.com (timeagentess)
Date: Thu, 26 Jun 2008 05:48:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WS-Security trouble:
	{http://www.w3.org/2005/08/addressing}A
Message-ID: <14662800.1214473704929.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello all,

I am trying to use WS-Security and have a client and web service exchange signed messages.
However, I have run into some trouble -- can't get rid of this error (seen on both server and client consoles):
anonymous wrote : ERROR [SOAPFaultHelperJAXWS] SOAP request exception
  | javax.xml.ws.addressing.AddressingException: Required element {http://www.w3.org/2005/08/addressing}Action is missing
  | 
  |         at org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.getRequiredHeaderContent(SOAPAddressingPropertiesImpl.java:71)
  |         at org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.readHeaders(SOAPAddressingPropertiesImpl.java:141)
  |         at org.jboss.ws.extensions.addressing.jaxws.WSAddressingServerHandler.handleInbound(WSAddressingServerHandler.java:82)
  | [...]
  | 

My configuration is JBoss 4.0.5 & JBossWS 2.0.0, and the files as described below.

I. Web service, deployed as SLSB in ear archive:
|-ejb.jar (contains Endpoint implementation WSTwoServiceBean.java)
|-META-INF
|---server.keystore
|---server.truststore
|---application.xml
|---jboss-wsse-server.xml
|---standard-jaxws-endpoint-config.xml

Service endpoint implementation: WSTwoServiceBean.java

//EJB3 annotations
  | @javax.ejb.Stateless
  | @org.jboss.annotation.ejb.RemoteBinding(jndiBinding = "WebServices/WSTwoServiceBeanInterface")
  | @javax.ejb.Remote({com.atb.webservices.wstwo.WSTwoServiceBeanInterface.class})
  |  
  | // WS annotations
  | @javax.jws.WebService(endpointInterface = "com.atb.webservices.wstwo.WSTwoRemoteInterface", targetNamespace = "http://localhost:8080/atb")
  | @org.jboss.wsf.spi.annotation.WebContext(contextRoot = "/webservices-ws", urlPattern="/services/WSTwo/*")
  | @javax.jws.soap.SOAPBinding(style = javax.jws.soap.SOAPBinding.Style.DOCUMENT, use = javax.jws.soap.SOAPBinding.Use.LITERAL, parameterStyle = javax.jws.soap.SOAPBinding.ParameterStyle.WRAPPED)
  | @HandlerChain(file="resource://META-INF/standard-jaxws-endpoint-config.xml")
  | @EndpointConfig(configName = "Standard WSSecurity Endpoint")
  | @SecurityDomain("JBossWS") 
  | public class WSTwoServiceBean implements WSTwoServiceBeanInterface {
  | 	@WebMethod
  | 	public String hello(String s){
  | 		return "Hello, " + s + "!";
  | 	}
  | }
  | 

jboss-wsse-server.xml:

<jboss-ws-security xmlns="http://www.jboss.com/ws-security/config"
  | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  | xsi:schemaLocation="http://www.jboss.com/ws-security/config
  | http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd">
  | <key-store-file>META-INF/server.keystore</key-store-file>
  | <key-store-password>server</key-store-password>
  | <trust-store-file>META-INF/server.truststore</trust-store-file>
  | <trust-store-password>server</trust-store-password>
  | <config>
  |     <sign type="jks" alias="server"/>
  |     <requires>
  |        <signature/>
  |     </requires>
  | </config>
  | </jboss-ws-security>


standard-jaxws-endpoint-config.xml:

<jaxws-config xmlns="urn:jboss:jaxws-config:2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:javaee="http://java.sun.com/xml/ns/javaee"
  |   xsi:schemaLocation="urn:jboss:jaxws-config:2.0 jaxws-config_2_0.xsd">
  |    
  |   <endpoint-config>
  |     <config-name>Standard WSSecurity Endpoint</config-name>
  |     <post-handler-chains>
  |       <javaee:handler-chain>
  |         <javaee:protocol-bindings>##SOAP11_HTTP</javaee:protocol-bindings>
  |         <javaee:handler>
  |           <javaee:handler-name>WSSecurity Handler</javaee:handler-name>
  |           <javaee:handler-class>org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer</javaee:handler-class>
  |         </javaee:handler>
  |       </javaee:handler-chain>
  |     </post-handler-chains>
  |   </endpoint-config>
  |   
  | </jaxws-config>
  | 
II. Client, standalone application:
|-TestWS.java
|-META-INF
|---jboss-wsse-client.xml
|---standard-jaxws-client-config.xml
|---client.keystore
|---client.truststore

(Even though, being a standalone client, I suspect placing the files in a folder other than META-INF wouldn't make any difference)

TestWS.java:


  |                 WSTwoServiceBeanService wstwoService = new WSTwoServiceBeanService();
  |                 WSTwo wstwo = wstwoService.getPort(WSTwo.class);       
  |         
  | 		URL securityURL = null;
  | 		URL securityConfig = null;
  | 		try {
  | 			securityURL = new File("META-INF/jboss-wsse-client.xml").toURL();
  | 			securityConfig = new File("META-INF/standard-jaxws-client-config.xml").toURL();
  | 		} catch (MalformedURLException e) {
  | 			System.out.println(e);
  | 		}
  | 		((StubExt)wstwo).setSecurityConfig(securityURL.toExternalForm());
  | 		((StubExt)wstwo).setConfigName("Standard WSSecurity Client", securityConfig.toExternalForm());
  | 
  | 		String response = wstwo.hello("world");
  | 		System.out.println("Web service answered with: " + response);
  | 


jboss-wsse-client.xml:

<jboss-ws-security xmlns="http://www.jboss.com/ws-security/config"
  | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  | xsi:schemaLocation="http://www.jboss.com/ws-security/config
  | http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd">
  | <key-store-file>d:/workspace/wsclient/META-INF/client.keystore</key-store-file>
  | <key-store-password>client</key-store-password>
  | <key-store-type>jks</key-store-type>
  | <trust-store-file>d:/workspace/wsclient/META-INF/client.truststore</trust-store-file>
  | <trust-store-password>client</trust-store-password>
  | <trust-store-type>jks</trust-store-type>
  | <config>
  |     <sign type="jks" alias="client"/>
  |     <requires>
  |        <signature/>
  |     </requires>
  | </config>
  | </jboss-ws-security> 


standard-jaxws-client-config.xml:

<jaxws-config xmlns="urn:jboss:jaxws-config:2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:javaee="http://java.sun.com/xml/ns/javaee"
  |   xsi:schemaLocation="urn:jboss:jaxws-config:2.0 jaxws-config_2_0.xsd"> 
  |  
  |   <client-config>
  |     <config-name>Standard WSSecurity Client</config-name>
  |     <post-handler-chains>
  |       <javaee:handler-chain>
  |         <javaee:protocol-bindings>##SOAP11_HTTP</javaee:protocol-bindings>
  |         <javaee:handler>
  |           <javaee:handler-name>WSSecurityHandlerOutbound</javaee:handler-name>
  |           <javaee:handler-class>org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerClient</javaee:handler-class>
  |         </javaee:handler>
  |       </javaee:handler-chain>
  |     </post-handler-chains>
  |   </client-config>
  |   
  | </jaxws-config>
  | 

Thank you!

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160786#4160786

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160786


From do-not-reply at jboss.com  Thu Jun 26 05:48:32 2008
From: do-not-reply at jboss.com (hedinant)
Date: Thu, 26 Jun 2008 05:48:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Http filter for WS
Message-ID: <292843.1214473712613.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi all.

I deployed a web srvice from my jar and i like to attach a filter from my war (or some ather way) to the servlet endpoint.

May i do it? 
And how to do it, if possible?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160787#4160787

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160787


From do-not-reply at jboss.com  Thu Jun 26 06:20:25 2008
From: do-not-reply at jboss.com (hedinant)
Date: Thu, 26 Jun 2008 06:20:25 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Stateful webservices
Message-ID: <15922559.1214475625281.JavaMail.jboss@colo-br-02.atl.jboss.com>

Stateful webservices is not yet supported by jboss (4.2.2)
Am i right?
or how to use them?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160802#4160802

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160802


From do-not-reply at jboss.com  Thu Jun 26 10:03:08 2008
From: do-not-reply at jboss.com (sivman)
Date: Thu, 26 Jun 2008 10:03:08 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: IndexOutOfBoundsException when
	transforming into SAAJ SO
Message-ID: <24764633.1214488988456.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi Arjen,

    I am facing the same problem deploying onto the jboss, did you get any solution for this. I tried with different saaj jars, but no luck.

Thanks
Siva.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160881#4160881

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160881


From do-not-reply at jboss.com  Thu Jun 26 14:19:23 2008
From: do-not-reply at jboss.com (randiz)
Date: Thu, 26 Jun 2008 14:19:23 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - document response
Message-ID: <26668189.1214504363949.JavaMail.jboss@colo-br-02.atl.jboss.com>

Is there a way I can send and return a xml document as a response from a web service  method ? when I specify a document (dom4j) as response from method  eg Document method() {... }  then jboss will not deploy the ear. When I try to return a xml string eg String method() { ...} then all the <  > characters get translated to '<' and '>'which is not acceptable ( even <![CDATA[  ... ]]>  does not work ). Jboss version is 4.2.2GA.

thanx
randiz


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160955#4160955

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160955


From do-not-reply at jboss.com  Thu Jun 26 15:53:34 2008
From: do-not-reply at jboss.com (zeko)
Date: Thu, 26 Jun 2008 15:53:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWs 3.0.1 client
	IllegalAnnotationsException
Message-ID: <1484314.1214510014484.JavaMail.jboss@colo-br-02.atl.jboss.com>

A bit late but maybe of interest for others:
For us it helped to use a custom Jaxb-binding.
Serializable is not importent here - the trick isusing the "generateElementProperty" attribute to chagne the way
some attributes are generated.
anonymous wrote : 
  | <?xml version="1.0" encoding="UTF-8"?>
  | <jxb:bindings jxb:version="2.1"
  |     xmlns:jxb="http://java.sun.com/xml/ns/jaxb"
  |     xmlns:xs="http://www.w3.org/2001/XMLSchema"
  |     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  |     xsi:schemaLocation="http://java.sun.com/xml/ns/jaxb http://java.sun.com/xml/ns/jaxb/bindingschema_2_0.xsd"
  |     xmlns:xjc="http://java.sun.com/xml/ns/jaxb/xjc" 
  |     >
  | 	<jxb:bindings schemaLocation="xyz.xsd" node="/xs:schema">
  | 		<jxb:globalBindings generateElementProperty="false">
  | 			<xjc:serializable uid="1" />
  | 		</jxb:globalBindings>
  | 	</jxb:bindings>
  | </jxb:bindings>
  | 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160973#4160973

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160973


From do-not-reply at jboss.com  Thu Jun 26 16:09:13 2008
From: do-not-reply at jboss.com (randiz)
Date: Thu, 26 Jun 2008 16:09:13 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: document response
Message-ID: <4164147.1214510954139.JavaMail.jboss@colo-br-02.atl.jboss.com>

I meant < and > get translated to < and >

thanks
randiz

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160979#4160979

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160979


From do-not-reply at jboss.com  Thu Jun 26 16:12:36 2008
From: do-not-reply at jboss.com (randiz)
Date: Thu, 26 Jun 2008 16:12:36 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: document response
Message-ID: <28311120.1214511156604.JavaMail.jboss@colo-br-02.atl.jboss.com>

 sorry for typo again < and > gets translated to lt; and gt;

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160982#4160982

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160982


From do-not-reply at jboss.com  Fri Jun 27 09:09:41 2008
From: do-not-reply at jboss.com (d.behrwind)
Date: Fri, 27 Jun 2008 09:09:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Need help: Errors during SSL connection
Message-ID: <990616.1214572181750.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I'm using Seam 2.0.2.SP1 on JBossAS 4.2.2.GA and want to publish some web services. Communication shall be encrypted using SSL. So I'm trying to follow  the instructions at http://jbws.dyndns.org/mediawiki/index.php?title=Secure_transport.

After finally getting the server running with SSL, my client is now unable to connect. 

If I configure the SSL connector in the server.xml as suggested in the article:
<Connector port="8443" address="${jboss.bind.address}"
  |         maxThreads="100" minSpareThreads="5" maxSpareThreads="15"
  |         scheme="https" secure="true" clientAuth="want"
  |         keystoreFile="C:\Entwicklung\jboss-4.2.2.GA\server\default\conf\keystores\wsse.keystore" 
  |         keystorePass="symtaweb"
  |         truststoreFile="C:\Entwicklung\jboss-4.2.2.GA\server\default\conf\keystores\wsse.keystore" 
  |         truststorePass="symtaweb"
  |         sslProtocol = "TLS" /> 
the result is:
Exception in thread "main" com.sun.xml.internal.ws.client.ClientTransportException: HTTP transport error: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
  | 	at com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:119)
  | 	at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:128)
  | 	at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:74)
  | 	at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:581)
  | 	at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:540)
  | 	at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:525)
  | 	at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:422)
  | 	at com.sun.xml.internal.ws.client.Stub.process(Stub.java:235)
  | 	at com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:120)
  | 	at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:230)
  | 	at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:210)
  | 	at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:103)
  | 	at $Proxy29.login(Unknown Source)
  | 	at com.symtavision.test.jbossws.Test.main(Test.java:32)
  | Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
  | 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:808)
  | 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1096)
  | 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1123)
  | 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1107)
  | 	at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:405)
  | 	at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:166)
  | 	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:832)
  | 	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:230)
  | 	at com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:107)
  | 	... 13 more
  | Caused by: java.io.EOFException: SSL peer shut down incorrectly
  | 	at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:333)
  | 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:789)
  | 	... 21 more
  | 

And when using the default configuration:
    <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"
  |                maxThreads="150" scheme="https" secure="true"
  |                clientAuth="false" sslProtocol="TLS"
  | 		   keystoreFile="C:\Entwicklung\jboss-4.2.2.GA\server\default\conf\keystores\.keystore" 
  | 		   keystorePass="symtaweb" />
I get this: 

Exception in thread "main" com.sun.xml.internal.ws.client.ClientTransportException: request requires HTTP authentication: Unauthorized
  | 	at com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.checkResponseCode(HttpClientTransport.java:197)
  | 	at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:137)
  | 	at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:74)
  | 	at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:581)
  | 	at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:540)
  | 	at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:525)
  | 	at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:422)
  | 	at com.sun.xml.internal.ws.client.Stub.process(Stub.java:235)
  | 	at com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:120)
  | 	at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:230)
  | 	at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:210)
  | 	at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:103)
  | 	at $Proxy29.login(Unknown Source)
  | 	at com.symtavision.test.jbossws.Test.main(Test.java:32)

I'm setting the required system properties programmatically instead of using XML configuration:

public static void main(String[] args) {
  | 
  | 		System.setProperty("javax.net.ssl.keyStore", "C:/Entwicklung/jboss-4.2.2.GA/server/default/conf/keystores/.keystore");
  | 		System.setProperty("javax.net.ssl.trustStore", "C:/Entwicklung/jboss-4.2.2.GA/server/default/conf/keystores/.keystore");
  | 		System.setProperty("javax.net.ssl.keyStorePassword", "symtaweb");
  | 		System.setProperty("javax.net.ssl.trustStorePassword", "symtaweb"); 
  | 		System.setProperty("javax.net.ssl.keyStoreType", "jks");
  | 		System.setProperty("javax.net.ssl.trustStoreType", "jks");
  | 
  | 		// obtain proxy
  | 		LoginService loginService = new LoginServiceService()
  | 				.getLoginServicePort();
  | 
  | 		// maintain Session
  | 		((BindingProvider) loginService).getRequestContext().put(
  | 				BindingProvider.SESSION_MAINTAIN_PROPERTY, true);
  | 
  | 		// *** regular method calls *** //
  | 
  | 		System.out.println("logging in... \n \t success: "
  | 				+ loginService.login("daniel", ""));
  | 
  | 		System.out.println("still logged in?\n\t" + loginService.isLoggedin());
  | 
  | 		System.out.println("logging out... \n \t success: "
  | 				+ loginService.logout());
  | 
  | 		System.out.println("still logged in?\n\t" + loginService.isLoggedin());
  | 
  | 	}

And I was not able to set the @SecurityDomain("JBossWS") annotation in the server class. (I don't know which jar to import ...)

Tanks for any help!

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161151#4161151

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161151


From do-not-reply at jboss.com  Fri Jun 27 10:11:04 2008
From: do-not-reply at jboss.com (timeagentess)
Date: Fri, 27 Jun 2008 10:11:04 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-Security trouble:
	{http://www.w3.org/2005/08/addressi
Message-ID: <27834058.1214575864918.JavaMail.jboss@colo-br-02.atl.jboss.com>

I intercepted the SOAP messages being sent, and it seems that the client signs the message, but the service does not answer in kind.

When setting up the client and server for message encryption, the same thing occurs -- the client correctly encrypts the outgoing message, 
but then this error appears:

anonymous wrote : Endpoint {http://localhost:8080/atb}WSTwoServiceBeanPort does not contain operation meta data for: {http://www.w3.org/2001/04/xmlenc#}EncryptedData
  | 

Does this vaguely mean that the service is not able to properly encrypt its response? Maybe this rings a bell for someone. 

Thank you!

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161186#4161186

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161186


From do-not-reply at jboss.com  Fri Jun 27 14:23:13 2008
From: do-not-reply at jboss.com (paramsevak)
Date: Fri, 27 Jun 2008 14:23:13 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - web service conflicts with jbossws and
	jaxws
Message-ID: <238487.1214590993437.JavaMail.jboss@colo-br-02.atl.jboss.com>

I used wconsume to auto-generate a webservice client. The client works within eclipse after I remove the jaxws-rt.jar and jaxws-tools.jar from the classpath. 

However when I use the same client-code from within an ejb deployed to jboss-4.2.2GA I get the following error. I have tried removing the jaxws-rt.jar and jaxws-tools.jar from the %JBOSS_HOME%/client/ dir but the following error still occurs.

e calling FM. Exception: Failed to create a new SAX parser
14:17:16,557 ERROR [STDERR] org.jboss.xb.binding.JBossXBRuntimeException: Failed to create a new SAX parser
14:17:16,557 ERROR [STDERR]     at org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryImpl.newUnmarshaller
(UnmarshallerFactory.java:100)
14:17:16,557 ERROR [STDERR]     at org.jboss.ws.metadata.config.JBossWSConfigFactory.parse(JBossWSConfigFactory.jav
a:76)
14:17:16,557 ERROR [STDERR]     at org.jboss.ws.metadata.config.JBossWSConfigFactory.getConfig(JBossWSConfigFactory
.java:134)
14:17:16,557 ERROR [STDERR]     at org.jboss.ws.metadata.umdm.EndpointMetaData.initEndpointConfig(EndpointMetaData.
java:704)
14:17:16,557 ERROR [STDERR]     at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.rebuildEndpointMe
taData(JAXWSClientMetaDataBuilder.java:288)
14:17:16,557 ERROR [STDERR]     at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortInternal(ServiceDelegateI
mpl.java:262)
14:17:16,557 ERROR [STDERR]     at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java
:193)
14:17:16,557 ERROR [STDERR]     at javax.xml.ws.Service.getPort(Service.java:116)
14:17:16,557 ERROR [STDERR]     at com.cbc.services.salt.fm.TuxedoWebService.getFmservicesFMGWWSHTTPPort(TuxedoWebS
ervice.java:58)
14:17:16,557 ERROR [STDERR]     at com.cbc.services.salt.fm.FMInterface.transactFM(FMInterface.java:78)
14:17:16,557 ERROR [STDERR]     at com.cbc.isac.ejb20.iccon.IcconBean.tpcall(IcconBean.java:2543)
14:17:16,557 ERROR [STDERR]     at com.cbc.isac.ejb20.iccon.IcconBean.getAllConsumerStatements(IcconBean.java:3173)

14:17:16,557 ERROR [STDERR]     at com.cbc.isac.ejb20.iccon.IcconBean.getAllActiveStatements(IcconBean.java:701)
14:17:16,557 ERROR [STDERR]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
14:17:16,557 ERROR [STDERR]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
14:17:16,557 ERROR [STDERR]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:25)
14:17:16,557 ERROR [STDERR]     at java.lang.reflect.Method.invoke(Method.java:585)
14:17:16,557 ERROR [STDERR]     at org.jboss.invocation.Invocation.performCall(Invocation.java:359)
14:17:16,557 ERROR [STDERR]     at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSes
sionContainer.java:237)
14:17:16,557 ERROR [STDERR]     at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedCo
nnectionInterceptor.java:158)
14:17:16,557 ERROR [STDERR]     at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessio
nInstanceInterceptor.java:169)
14:17:16,557 ERROR [STDERR]     at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor
.java:63)
14:17:16,557 ERROR [STDERR]     at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.jav
a:121)
14:17:16,557 ERROR [STDERR]     at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java
:350)
14:17:16,557 ERROR [STDERR]     at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181)
14:17:16,557 ERROR [STDERR]     at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168)
14:17:16,557 ERROR [STDERR]     at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
14:17:16,557 ERROR [STDERR]     at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInt
erceptor.java:138)
14:17:16,557 ERROR [STDERR]     at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648)
14:17:16,557 ERROR [STDERR]     at org.jboss.ejb.Container.invoke(Container.java:960)
14:17:16,557 ERROR [STDERR]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
14:17:16,557 ERROR [STDERR]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
14:17:16,557 ERROR [STDERR]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:25)
14:17:16,557 ERROR [STDERR]     at java.lang.reflect.Method.invoke(Method.java:585)
14:17:16,557 ERROR [STDERR]     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155
)
14:17:16,557 ERROR [STDERR]     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
14:17:16,557 ERROR [STDERR]     at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
14:17:16,557 ERROR [STDERR]     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
14:17:16,557 ERROR [STDERR]     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
14:17:16,557 ERROR [STDERR]     at org.jboss.invocation.unified.server.UnifiedInvoker.invoke(UnifiedInvoker.java:23
1)
14:17:16,572 ERROR [STDERR]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
14:17:16,572 ERROR [STDERR]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
14:17:16,572 ERROR [STDERR]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:25)
14:17:16,572 ERROR [STDERR]     at java.lang.reflect.Method.invoke(Method.java:585)
14:17:16,572 ERROR [STDERR]     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155
)
14:17:16,572 ERROR [STDERR]     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
14:17:16,572 ERROR [STDERR]     at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
14:17:16,572 ERROR [STDERR]     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
14:17:16,572 ERROR [STDERR]     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
14:17:16,572 ERROR [STDERR]     at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandle
r.java:201)
14:17:16,572 ERROR [STDERR]     at $Proxy16.invoke(Unknown Source)
14:17:16,572 ERROR [STDERR]     at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
14:17:16,572 ERROR [STDERR]     at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.
java:573)
14:17:16,572 ERROR [STDERR]     at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
14:17:16,572 ERROR [STDERR]     at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
14:17:16,572 ERROR [STDERR] Caused by: org.jboss.xb.binding.JBossXBException: Failed to create a new SAX parser
14:17:16,572 ERROR [STDERR]     at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.(SaxJBossXBParser.java:96
)
14:17:16,572 ERROR [STDERR]     at org.jboss.xb.binding.UnmarshallerImpl.(UnmarshallerImpl.java:55)
14:17:16,572 ERROR [STDERR]     at org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryImpl.newUnmarshaller
(UnmarshallerFactory.java:96)
14:17:16,572 ERROR [STDERR]     ... 54 more
14:17:16,572 ERROR [STDERR] Caused by: javax.xml.parsers.ParserConfigurationException: Feature 'http://apache.org/x
ml/features/xinclude' is not recognized.
14:17:16,572 ERROR [STDERR]     at org.apache.xerces.jaxp.SAXParserFactoryImpl.newSAXParser(Unknown Source)
14:17:16,572 ERROR [STDERR]     at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.(SaxJBossXBParser.java:92
)
14:17:16,572 ERROR [STDERR]     ... 56 more
14:17:16,572 INFO  [IcconBean] com.cbc.isac.ejb20.iccon.IcconBean.requestTuxedoService(String, String) - closing tu
xedo connection

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161276#4161276

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161276


From do-not-reply at jboss.com  Sat Jun 28 03:25:45 2008
From: do-not-reply at jboss.com (fbenvegna)
Date: Sat, 28 Jun 2008 03:25:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - RPC WSDL and load balancing problem
Message-ID: <24188217.1214637945493.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have a JBoss Cluster with two application server and an Apache with mod_jk as load balancer.
With web application no problem but with web-services there are...
my web-services WSDL (style RPC) reports an include on other WSDL URL that include a random identifier. Identifiers change on every deploy and are different from a machine to other.

PROBLEM with load balancing and wsdl rewrite configured: when a client requests WSDL on host A retrieve WSDL A, with included URL on machine A, but when it tries to retrieve the included WSDL A the request goes on host B, so....  error!

The problem only happens with JBossWS Native, no problem with JBossWS Metro because there isn't any deploy dependent identifier on generated WSDL.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161331#4161331

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161331


From do-not-reply at jboss.com  Mon Jun 30 04:58:58 2008
From: do-not-reply at jboss.com (timeagentess)
Date: Mon, 30 Jun 2008 04:58:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-Security trouble:
	{http://www.w3.org/2005/08/addressi
Message-ID: <29573778.1214816338834.JavaMail.jboss@colo-br-02.atl.jboss.com>

Tried out the same configuration in JBoss 4.2.2 with JBossWS 3.0.2, thinking maybe there was some bug which was fixed in the meantime.

However, I am getting the same errors, which leads me to think that I must be doing something extremely stupid. 
Doesn't anybody have any clue about this? I appreciate any and every suggestions (even if it's an angry "RTFM" reply :D )

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161421#4161421

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161421


From do-not-reply at jboss.com  Mon Jun 30 05:24:14 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 30 Jun 2008 05:24:14 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-Security trouble:
	{http://www.w3.org/2005/08/addressi
Message-ID: <1836788.1214817854678.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi, as a general suggestion, I first of all suggest you to try using some more recent versions of both JBoss AS and JBossWS.
This said:

"timeagentess" wrote : 
  | anonymous wrote : ERROR [SOAPFaultHelperJAXWS] SOAP request exception
  |   | javax.xml.ws.addressing.AddressingException: Required element {http://www.w3.org/2005/08/addressing}Action is missing
  |   | 
  |   |         at org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.getRequiredHeaderContent(SOAPAddressingPropertiesImpl.java:71)
  |   |         at org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.readHeaders(SOAPAddressingPropertiesImpl.java:141)
  |   |         at org.jboss.ws.extensions.addressing.jaxws.WSAddressingServerHandler.handleInbound(WSAddressingServerHandler.java:82)
  |   | [...]
  |   | 
You get this message because you're using WS-Addressing and the Action header is missing in your SOAP message. This is not related to WS-Security.


anonymous wrote : 
  | @HandlerChain(file="resource://META-INF/standard-jaxws-endpoint-config.xml")
  | @EndpointConfig(configName = "Standard WSSecurity Endpoint")
  | 

Since you're using the standard endpoint configuration, you should try simplifying your configuration a bit (to better track down what's happening), i.e. remove the @HandlerChain annotation and forget about the standard-jaxws-endpoint-config.xml file (you already have the "Standard WSSecurity Endpoint" in the configuration that is automatically loaded by jbossws).


Regarding this:
anonymous wrote : 
  | Endpoint {http://localhost:8080/atb}WSTwoServiceBeanPort does not contain operation meta data for: {http://www.w3.org/2001/04/xmlenc#}EncryptedData 
  | 
under which conditions you got this? Try looking at the log and verify the security handler on server side is configured (the ws-security conf is selected).

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161434#4161434

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161434


From do-not-reply at jboss.com  Mon Jun 30 05:28:18 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 30 Jun 2008 05:28:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: RPC WSDL and load balancing problem
Message-ID: <23103700.1214818098306.JavaMail.jboss@colo-br-02.atl.jboss.com>

Sorry, what identifier do you refer to? Please post an example.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161437#4161437

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161437


From do-not-reply at jboss.com  Mon Jun 30 05:35:57 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 30 Jun 2008 05:35:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: web service conflicts with jbossws
	and jaxws
Message-ID: <21375319.1214818557574.JavaMail.jboss@colo-br-02.atl.jboss.com>

Most probably you're getting this because your server classpath includes an old version of xerces not supporting xinclude. Please check (see the endorsed dir). 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161440#4161440

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161440


From do-not-reply at jboss.com  Mon Jun 30 05:46:41 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 30 Jun 2008 05:46:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Need help: Errors during SSL
	connection
Message-ID: <31770422.1214819201885.JavaMail.jboss@colo-br-02.atl.jboss.com>

You nevertheless need to set the security domain you want to use on server side. This can be done either using the @SecurityDomain annotation or through the deployment descriptor.
The org.jboss.annotation.security.SecurityDomain should be in jbossws-core.jar in the jbossws version that is included in jboss4.2.2.GA by default (assuming you didn't update it).

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161444#4161444

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161444


From do-not-reply at jboss.com  Mon Jun 30 05:49:44 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 30 Jun 2008 05:49:44 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: document response
Message-ID: <15414187.1214819384906.JavaMail.jboss@colo-br-02.atl.jboss.com>

You could take a look at the SwA and MTOM attachment technologies http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#Attachments

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161445#4161445

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161445


From do-not-reply at jboss.com  Mon Jun 30 05:59:48 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 30 Jun 2008 05:59:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: IndexOutOfBoundsException when
	transforming into SAAJ SO
Message-ID: <14032372.1214819988369.JavaMail.jboss@colo-br-02.atl.jboss.com>

It could be, feel free to create an issue on the JBossWS JIRA referencing this forum thread. Thank you.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161451#4161451

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161451


From do-not-reply at jboss.com  Mon Jun 30 06:05:16 2008
From: do-not-reply at jboss.com (poutsma)
Date: Mon, 30 Jun 2008 06:05:16 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: IndexOutOfBoundsException when
	transforming into SAAJ SO
Message-ID: <5188226.1214820316722.JavaMail.jboss@colo-br-02.atl.jboss.com>

I've create an issue here:http://jira.jboss.org/jira/browse/JBWS-2186.

Also, see http://blog.springsource.com/arjen/archives/2008/05/19/the-sorry-state-of-saaj.

Cheers,

Arjen

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161452#4161452

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161452


From do-not-reply at jboss.com  Mon Jun 30 06:15:15 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 30 Jun 2008 06:15:15 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Need help : JBossWS Security!
Message-ID: <1257536.1214820915687.JavaMail.jboss@colo-br-02.atl.jboss.com>

"helmutdoe" wrote : Same Problem here ...
  | 
  | $Proxy29 cannot be cast to org.jboss.ws.core.StubExt
  | 
  | did someone solve this problem?

Could you please post your client side code, including the imports? (you too xinhua). I suspect you might be mixing jaxrpc and jaxws classes.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161455#4161455

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161455


From do-not-reply at jboss.com  Mon Jun 30 06:19:44 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 30 Jun 2008 06:19:44 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Need help : JBossWS Security!
Message-ID: <18083551.1214821184444.JavaMail.jboss@colo-br-02.atl.jboss.com>

"helmutdoe" wrote : The <wsse:Security> missing occurs if i remove the followin line on my code.
  | 
  |  ((StubExt) ksb).setConfigName("Standard WSSecurity Client");
  |   | 
  | 
  | And this is traceable to me because then the client application do not know how he should configure the SecurityHandlers.
Yes, without that the client doesn't even know that ws-security is to be used.

anonymous wrote : 
  |   | ((StubExt) ksb).setSecurityConfig("META-INF/jboss-wsse-client.xml");
  |   | 
  | 
  | I have a problem on understanding how the client side gets this xml. Since Webservices have to be interoperable only the wsdl should be public.
Of course it is not public, it's client side specific since it contains the location to the client keystores, etc.
The jbossws code will look for the specified location the client application jar. Please note you can also provide absolute path to point to an external file.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161457#4161457

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161457


From do-not-reply at jboss.com  Mon Jun 30 06:25:22 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 30 Jun 2008 06:25:22 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: SSL not activating
Message-ID: <15649019.1214821523018.JavaMail.jboss@colo-br-02.atl.jboss.com>

You should check the jbossweb tomcat configuration that's in place on your AS. You might also want to post it here so that we can better understand.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161460#4161460

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161460


From do-not-reply at jboss.com  Mon Jun 30 06:57:03 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 30 Jun 2008 06:57:03 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Error while invoking webservice
Message-ID: <29036450.1214823423899.JavaMail.jboss@colo-br-02.atl.jboss.com>

http://www.jboss.com/index.html?module=bb&op=viewforum&f=217

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161470#4161470

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161470


From do-not-reply at jboss.com  Mon Jun 30 07:02:08 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 30 Jun 2008 07:02:08 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Can not visit
	http://jbws.dyndns.org for jbossws documen
Message-ID: <19835884.1214823728550.JavaMail.jboss@colo-br-02.atl.jboss.com>

We're currently working on moving the jbossws documentation, sorry for the issue you might have.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161471#4161471

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161471


From do-not-reply at jboss.com  Mon Jun 30 07:16:25 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 30 Jun 2008 07:16:25 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Trouble using @WebContext to
	encrypt communication
Message-ID: <6285458.1214824585353.JavaMail.jboss@colo-br-02.atl.jboss.com>

This might be due to a JRE version mismatch (the one you're using, the one used to compile that library, etc)

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161476#4161476

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161476


From do-not-reply at jboss.com  Mon Jun 30 08:15:34 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 30 Jun 2008 08:15:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: What controls the SOAP version used
	in JBoss
Message-ID: <13887006.1214828134402.JavaMail.jboss@colo-br-02.atl.jboss.com>

JBossWS native supports both SOAP 1.1 and SOAP 1.2. This is configured according to the binding type specified in the wsdl being deployed / consumed.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161486#4161486

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161486


From do-not-reply at jboss.com  Mon Jun 30 08:18:15 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 30 Jun 2008 08:18:15 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: What controls the SOAP version used
	in JBoss
Message-ID: <8777123.1214828295595.JavaMail.jboss@colo-br-02.atl.jboss.com>

You can also use the @BindingType annotation.

See the following constants:

  | /**
  |     * A constant representing the identity of the SOAP 1.1 over HTTP binding.
  |     */
  |    public static final String SOAP11HTTP_BINDING = "http://schemas.xmlsoap.org/wsdl/soap/http";
  | 
  |    /**
  |     * A constant representing the identity of the SOAP 1.2 over HTTP binding.
  |     */
  |    public static final String SOAP12HTTP_BINDING = "http://www.w3.org/2003/05/soap/bindings/HTTP/";
  | 
  |    /**
  |     * A constant representing the identity of the SOAP 1.1 over HTTP binding
  |     * with MTOM enabled by default.
  |     */
  |    public static final String SOAP11HTTP_MTOM_BINDING = "http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true";
  | 
  |    /**
  |     * A constant representing the identity of the SOAP 1.2 over HTTP binding
  |     * with MTOM enabled by default.
  |     */
  |    public static final String SOAP12HTTP_MTOM_BINDING = "http://www.w3.org/2003/05/soap/bindings/HTTP/?mtom=true";
  | 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161487#4161487

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161487


From do-not-reply at jboss.com  Mon Jun 30 08:28:21 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 30 Jun 2008 08:28:21 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Schema Validation - Failed to read
	schema document
Message-ID: <16030348.1214828901778.JavaMail.jboss@colo-br-02.atl.jboss.com>

Is the imported xsd actually available along with the wsdl when the validation is perfomed? Perhaps you might create a jira issue for this, attaching a simple application proving this.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161489#4161489

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161489


From do-not-reply at jboss.com  Mon Jun 30 08:48:34 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 30 Jun 2008 08:48:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: @WebServiceRef for JAX-RPC service?
Message-ID: <18261723.1214830114978.JavaMail.jboss@colo-br-02.atl.jboss.com>

javax.xml.ws.WebServiceRef annotation is for JAX-WS only.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161494#4161494

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161494


From do-not-reply at jboss.com  Mon Jun 30 08:52:36 2008
From: do-not-reply at jboss.com (poisoner)
Date: Mon, 30 Jun 2008 08:52:36 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Jbossws Tutorial.
Message-ID: <18233438.1214830356611.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,
i am trying the same example but i am getting incomplete deployment.
The service is registered, but the wsdl is empty.
Somebody to have idea what is the problem?

  | 15:41:47,421 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
  |  
  | --- Packages waiting for a deployer ---
  | org.jboss.deployment.DeploymentInfo at 7f08c218 { url=file:/C:/jboss/jboss-portal-2.6.2.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse }
  |   deployer: null
  |   status: Starting
  |   state: INIT_WAITING_DEPLOYER
  |   watch: file:/C:/jboss/jboss-portal-2.6.2.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse
  |   altDD: null
  |   lastDeployed: 1214570470468
  |   lastModified: 1214570426218
  |   mbeans:
  |  
  | --- Incompletely deployed packages ---
  | org.jboss.deployment.DeploymentInfo at 49deb077 { url=file:/C:/jboss/jboss-portal-2.6.2.GA/server/default/deploy/sum.war }
  |   deployer: MBeanProxyExt[jboss.web:service=WebServer]
  |   status: Deployment FAILED reason: String index out of range: -1
  |   state: FAILED
  |   watch: file:/C:/jboss/jboss-portal-2.6.2.GA/server/default/deploy/sum.war
  |   altDD: null
  |   lastDeployed: 1214570496406
  |   lastModified: 1214570496390
  |   mbeans:
  |     jboss.web:j2eeType=Servlet,name=Sum,WebModule=//localhost/sum,J2EEApplication=none,J2EEServer=none (state not available)
  |     jboss.web:j2eeType=Servlet,name=jsp,WebModule=//localhost/sum,J2EEApplication=none,J2EEServer=none (state not available)
  |     jboss.web:j2eeType=Servlet,name=default,WebModule=//localhost/sum,J2EEApplication=none,J2EEServer=none (state not available)
  |  
  |  
  |  
  |  
  |  
  |  
  |  
  |  
  | /*
  |  * Sum.java
  |  * created by borislav
  |  * created on 27.06.2008
  |  */
  |  
  | import javax.jws.WebMethod;
  | import javax.jws.WebService;
  | import javax.jws.soap.SOAPBinding;
  |  
  |  
  |  
  | @WebService
  | @SOAPBinding(style = SOAPBinding.Style.RPC)
  | public class Sum {
  |  
  | 	@WebMethod
  | 	public int sumAB(int a, int b){
  | 		return a+b;
  | 	}
  |  
  | }
  |  
  |  
  |  
  |  
  |  
  | web.xml
  |  
  | <?xml version="1.0" encoding="UTF-8"?>
  |  
  | <web-app version="2.5"
  |     xmlns="http://java.sun.com/xml/ns/javaee"
  |     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  |     xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
  |  
  |    <servlet>
  |     <servlet-name>Sum</servlet-name>
  |     <servlet-class>Sum</servlet-class>
  |   </servlet>
  |  
  |   <servlet-mapping>
  |     <servlet-name>Sum</servlet-name>
  |     <url-pattern>/*</url-pattern>
  |   </servlet-mapping>
  |  
  | </web-app>
  | 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161499#4161499

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161499


From do-not-reply at jboss.com  Mon Jun 30 08:54:18 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 30 Jun 2008 08:54:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Method Overloading and SOAP
	Annotations
Message-ID: <30770171.1214830458639.JavaMail.jboss@colo-br-02.atl.jboss.com>

Try using the operationName parameter of the @WebMethod annotation.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161501#4161501

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161501


From do-not-reply at jboss.com  Mon Jun 30 08:56:57 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 30 Jun 2008 08:56:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Ho to use web services in
	jboss-4.0.5 and EJB 2.0
Message-ID: <17079563.1214830617716.JavaMail.jboss@colo-br-02.atl.jboss.com>

If you can't upgrade your JBoss Application Server at least to 4.2.x, the documentation is here http://jbws.dyndns.org/mediawiki/index.php?title=JAX-RPC_User_Guide

Otherwise (much better), install JBoss 4.2.x and upgrade to the lastest JBossWS 3.0.2.GA. Then all the documentation you need is here: http://jbws.dyndns.org/mediawiki/index.php?title=JBossWS

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161502#4161502

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161502


From do-not-reply at jboss.com  Mon Jun 30 10:09:42 2008
From: do-not-reply at jboss.com (manu_leon_sp)
Date: Mon, 30 Jun 2008 10:09:42 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Use of RPC/Encoded
Message-ID: <8336718.1214834982253.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello,
I have a wsdl that used rpc/encoded. I have read documentation of Jboss and it says that "JBossWS has basic support for rpc/encoded that is provided as is for simple interop scenarios with SOAP stacks that do not support literal encoding. "

I don't know how to generate a JBossWS usin Rpc/Encoded. The aren't any example of this and in the documentation I dint'  founf nothing of this and in other forums I had read that I can't use it.

Can you help me or say where I can foun more information about this?

Thanks,



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161527#4161527

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161527


From do-not-reply at jboss.com  Mon Jun 30 10:33:37 2008
From: do-not-reply at jboss.com (timeagentess)
Date: Mon, 30 Jun 2008 10:33:37 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-Security trouble:
	{http://www.w3.org/2005/08/addressi
Message-ID: <28410680.1214836417198.JavaMail.jboss@colo-br-02.atl.jboss.com>

"alessio.soldano at jboss.com" wrote : Hi, as a general suggestion, I first of all suggest you to try using some more recent versions of both JBoss AS and JBossWS.
Hi, thanks for the suggestions! As a matter of fact, I am using JBoss 4.2.2 and JBossWS 3.0.2 now, with the same problems. Some more answers/questions for each of your points below.

anonymous wrote : You get this message because you're using WS-Addressing and the Action header is missing in your SOAP message. This is not related to WS-Security.
  | 
Have I inadvertently activated WS-Addressing? (that was most certainly not my intention). I thought for using WS-Addressing one has to have an annotation like this on the web service class: @EndpointConfig(configName = "Standard WSAddressing Endpoint") ?

anonymous wrote : 
  | Endpoint {http://localhost:8080/atb}WSTwoServiceBeanPort does not contain operation meta data for: {http://www.w3.org/2001/04/xmlenc#}EncryptedData 
  | 
  | under which conditions you got this? Try looking at the log and verify the security handler on server side is configured (the ws-security conf is selected).

I got this when requesting encryption in both client and service jboss-wsse-****.xml
I'm not sure if this part of the log is what you referred to, but the security config seems to be null:
anonymous wrote : 2008-06-30 15:23:36,422 DEBUG [org.jboss.system.ServiceConfigurator] SecurityConf set to [security: null] in jboss.mq.destination:service=Topic,name=testTopic
  | 2008-06-30 15:23:36,422 DEBUG [org.jboss.mq.server.jmx.Topic.testTopic] Setting securityConf: [security: null]
 
On the service endpoint it seems to be ok:
anonymous wrote : ServerEndpointMetaData:
  |  type=JAXWS
  |  qname={http://wsthree.ws.atb.com/}WSThreeServiceBeanPort
  | [...]
  |  configFile=META-INF/standard-jaxws-endpoint-config.xml
  |  configName=Standard WSSecurity Endpoint
  |  authMethod=null
  |  transportGuarantee=null
  |  secureWSDLAccess=false
  |  properties={} 

(I suppose META-INF/standard-jaxws-endpoint-config.xml is taken from the JBossWS.sar deployment, as it is not present in my web service deployment anymore? )

And a bit lower in the log file the handler seems to be ok as well:
anonymous wrote : HandlerMetaDataJAXWS:
  |  type=POST
  |  name=WSSecurity Handler
  |  class=class org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer
  |  params=[]
  |  protocols=##SOAP11_HTTP ##SOAP11_HTTP_MTOM
  |  services=null
  |  ports=null

------------------------------------------------

Anyway, to sum up what I have now and what does not work:

Web service:

  | @WebService
  | @SOAPBinding(style = javax.jws.soap.SOAPBinding.Style.DOCUMENT, 
  | 		use = javax.jws.soap.SOAPBinding.Use.LITERAL, 
  | 		parameterStyle = javax.jws.soap.SOAPBinding.ParameterStyle.WRAPPED)
  | @EndpointConfig(configName = "Standard WSSecurity Endpoint")
  | public class WSThreeServiceBean implements WSThreeRemoteInterface {
  |    @WebMethod
  |    public String hello(String input) {
  | 	   return "Hello, " + input + "!";
  |    }
  | }

In the META-INF folder there is the keystore, truststore and jboss-wsse-server.xml

Client:
[...]
  | securityURL = new File("META-INF/jboss-wsse-client.xml").toURL();
  | ((StubExt)wsthree).setSecurityConfig(securityURL.toExternalForm());
  | ((StubExt)wsthree).setConfigName("Standard WSSecurity Client");
  | 

with keystore, truststore and jboss-wsse-client.xml in the META-INF (client is standalone).

Both service and client request messages to be signed.
Tracing the SOAP messages, looks like the client sends a properly signed message, which the service receives, then answers without signing the message. 
The client replies with "This service requires <wsse:Security>, which is missing.", which is logical, since the service sent an unsigned message.

If I comment out ((StubExt)wsthree).setConfigName("Standard WSSecurity Client"); in the client, the request-reply goes "perfectly": the client sends an unsigned message, and the service answers with an unsigned message as well.

What is not so clear to me is how to make the web service sign the message -- does it need something else besides the @EndpointConfig annotation and jboss-wsse-server.xml?

Thank you! (And I really apologize if I am asking stupid questions in the wrong direction, I think I've gotten to the point where I can't see the forest because of the trees anymore...)

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161532#4161532

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161532


From do-not-reply at jboss.com  Mon Jun 30 10:45:43 2008
From: do-not-reply at jboss.com (xinhua)
Date: Mon, 30 Jun 2008 10:45:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Need help : JBossWS Security!
Message-ID: <4766160.1214837143509.JavaMail.jboss@colo-br-02.atl.jboss.com>

"alessio.soldano at jboss.com" wrote : "helmutdoe" wrote : Same Problem here ...
  |   | 
  |   | $Proxy29 cannot be cast to org.jboss.ws.core.StubExt
  |   | 
  |   | did someone solve this problem?
  | 
  | Could you please post your client side code, including the imports? (you too xinhua). I suspect you might be mixing jaxrpc and jaxws classes.

Hi, here is my import
import java.io.File;
  | import java.net.URL;
  | import javax.xml.namespace.QName;
  | import javax.xml.ws.BindingProvider;
  | import javax.xml.ws.Service;
  | import org.jboss.ws.core.StubExt;
  | 

is that right, thanks.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161534#4161534

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161534


From do-not-reply at jboss.com  Mon Jun 30 11:08:52 2008
From: do-not-reply at jboss.com (helmutdoe)
Date: Mon, 30 Jun 2008 11:08:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Need help : JBossWS Security!
Message-ID: <21970464.1214838532356.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi all, 

yes think you were right i had mixed RPC und JAXWS. Also after a while i was able to fix the <wsse:Securtiy> -Tag missing by using the folloing code


  | import java.io.File;
  | import java.net.MalformedURLException;
  | import java.net.URL;
  | import java.util.ArrayList;
  | import java.util.List;
  | import javax.xml.namespace.QName;
  | import javax.xml.ws.BindingProvider;
  | import javax.xml.ws.Service;
  | import javax.xml.ws.handler.Handler;
  | import org.jboss.ws.core.StubExt;
  | import org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerClient;
  | import org.jboss.ws.extensions.addressing.jaxws.WSAddressingClientHandler;
  | 
  | ...
  |  System.setProperty("org.jboss.ws.wsse.keyStore","src/WEB-INF/keystore.jks");
  |             System.setProperty("org.jboss.ws.wsse.trustStore", "src/WEB-INF/cacerts.jks");
  |             System.setProperty("org.jboss.ws.wsse.keyStorePassword", "changeit");
  |             System.setProperty("org.jboss.ws.wsse.trustStorePassword", "changeit");
  |             System.setProperty("org.jboss.ws.wsse.keyStoreType", "jks");
  |             System.setProperty("org.jboss.ws.wsse.trustStoreType", "jks");  
  |             
  |             
  |             
  |             // Create Service Binding
  |             URL url = new URL("http://localhost:8080/LottoBean/LottoEJBWS?wsdl");
  |             QName qName = new QName("urn:com:tools:wsse", "LottoEJBWSService");
  | 
  |             //LottoEJBWSService service = new LottoEJBWSService(url,qName);
  |             LottoEJBWS port = Service.create(url, qName).getPort(LottoEJBWS.class);
  | 
  |             ((StubExt) port).setSecurityConfig(new File("src/META-INF/jboss-wsse-client.xml").toURI().toURL().toExternalForm());
  |             ((StubExt) port).setConfigName("Standard WSSecurity Client");
  | 
  |             BindingProvider binding = (BindingProvider)port;
  |             List<Handler> handlerChain = new ArrayList<Handler>();
  |            // handlerChain.add(new WSAddressingClientHandler());
  |             handlerChain.add(new WSSecurityHandlerClient());
  |             handlerChain.add(new LogHandler());            
  |             binding.getBinding().setHandlerChain(handlerChain);
  | 

With this code and my configured handlers i be able to sign messages. If i add encryption to the WebService Endponit i run in an other Exception.


  | Endpoint {urn:com:tools:wsse}LottoEJBWSPort does not contain operation meta data for: {http://www.w3.org/2001/04/xmlenc#}EncryptedData
  | javax.xml.ws.soap.SOAPFaultException: Endpoint {urn:com:tools:wsse}LottoEJBWSPort does not contain operation meta data for: {http://www.w3.org/2001/04/xmlenc#}EncryptedData
  |         at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:72)
  |         at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:109)
  |         at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:579)
  | ....
  | 

The code below shows my xml handler files.

standard-jaxws-client-config.xml



  | 
  |   <client-config>
  |     <config-name>Standard WSSecurity Client</config-name>
  |     <post-handler-chains>
  |       <javaee:handler-chain>
  |         <javaee:protocol-bindings>##SOAP11_HTTP ##SOAP11_HTTP_MTOM</javaee:protocol-bindings>
  |         <javaee:handler>
  |           <javaee:handler-name>WSSecurityHandlerOutbound</javaee:handler-name>
  |           <javaee:handler-class>org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerClient</javaee:handler-class>
  |         </javaee:handler>
  |       </javaee:handler-chain>
  |     </post-handler-chains>
  |   </client-config>
  | 


standard-jaxws-endpoint-config.xml


  | 
  | 
  | <endpoint-config>
  |     <config-name>Standard WSSecurity Endpoint</config-name>
  |     <post-handler-chains>
  |       <javaee:handler-chain>
  |         <javaee:protocol-bindings>##SOAP11_HTTP ##SOAP11_HTTP_MTOM</javaee:protocol-bindings>
  |         <javaee:handler>
  |           <javaee:handler-name>WSSecurity Handler</javaee:handler-name>
  |           <javaee:handler-class>org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer</javaee:handler-class>
  |         </javaee:handler>
  |         <javaee:handler>
  |           <javaee:handler-name>Recording Handler</javaee:handler-name>
  |           <javaee:handler-class>org.jboss.wsf.framework.invocation.RecordingServerHandler</javaee:handler-class>
  |         </javaee:handler>
  |       </javaee:handler-chain>
  |     </post-handler-chains>
  |   </endpoint-config>
  | 

jboss-wsse-client.xml


  | <jboss-ws-security xmlns="http://www.jboss.com/ws-security/config" 
  | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  | xsi:schemaLocation="http://www.jboss.com/ws-security/config 
  | http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd">
  |     <config>
  |         <sign type="x509v3" alias="s1as" includeTimestamp="false"/>
  |         <encrypt type="x509v3" alias="s1as" />   
  |         <requires>
  |             <signature/>
  |          </requires>
  |     </config>
  | </jboss-ws-security>
  | 

jboss-wsse-server.xml


  |   <jboss-ws-security xmlns="http://www.jboss.com/ws-security/config" 
  |             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  |             xsi:schemaLocation="http://www.jboss.com/ws-security/config 
  |                     http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd">
  | 	<key-store-file>WEB-INF/keystore.jks</key-store-file>
  | 	<key-store-password>changeit</key-store-password>
  |         <key-store-type>jks</key-store-type>
  | 	<trust-store-file>WEB-INF/cacerts.jks</trust-store-file>
  | 	<trust-store-password>changeit</trust-store-password>
  | 	<config>
  | 		<sign type="x509v3" alias="s1as" includeTimestamp="false"/>
  |                 <encrypt type="x509v3" alias="s1as" />   
  | 		<requires>
  | 			<signature/>
  | 		</requires>
  |     </config>
  | </jboss-ws-security>
  | 

Thnx for any hints



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161537#4161537

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161537


From do-not-reply at jboss.com  Mon Jun 30 12:54:45 2008
From: do-not-reply at jboss.com (xinhua)
Date: Mon, 30 Jun 2008 12:54:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Need help : JBossWS Security!
Message-ID: <15011197.1214844885517.JavaMail.jboss@colo-br-02.atl.jboss.com>

Sorry, forgot to paste the codes

  | 	public static void main(String[] args) {
  |         KSBService ksb = null;
  |         try {
  |                 //SSL keystore
  |         	System.setProperty("javax.net.ssl.keyStore", "c:\\ksbws.keystore");
  |         	System.setProperty("javax.net.ssl.trustStore", "c:\\ksbws.keystore");
  |         	System.setProperty("javax.net.ssl.keyStorePassword", "test");
  |         	System.setProperty("javax.net.ssl.trustStorePassword", "test");
  |         	System.setProperty("javax.net.ssl.keyStoreType", "jks");
  |         	System.setProperty("javax.net.ssl.trustStoreType", "jks");
  |         	System.setProperty("org.jboss.security.ignoreHttpsHost","true");
  | 
  |                 //Signature keystore
  |         	System.setProperty("org.jboss.ws.wsse.keyStore","c:\\ksbws_security.keystore");
  |         	System.setProperty("org.jboss.ws.wsse.trustStore","c:\\ksbws_security.keystore");
  |         	System.setProperty("org.jboss.ws.wsse.keyStorePassword", "test");
  |         	System.setProperty("org.jboss.ws.wsse.trustStorePassword", "test");
  |         	System.setProperty("org.jboss.ws.wsse.keyStoreType", "jks");
  |         	System.setProperty("org.jboss.ws.wsse.trustStoreType", "jks");
  |         	
  |             Service service = Service.create(new URL("http://localhost:8180/KSBService/KSBServiceBean?wsdl"),
  |                     new QName("http://xxx.xxx.de/","KSBServiceBeanService") );
  |             
  |             
  |             
  |             
  |             ksb= service.getPort(KSBService.class);
  |             
  |    			URL securityURL = new File("META-INF/jboss-wsse-client.xml").toURL();
  | 			URL securityConfig= new File("META-INF/standard-jaxws-client-config.xml").toURL();
  | 			((StubExt) port).setSecurityConfig(securityURL.toExternalForm());
  | 			((StubExt) port).setConfigName("Standard WSSecurity Client",securityConfig.toExternalForm());
  | 
  | 			
  | 			((BindingProvider) port).getRequestContext().put(BindingProvider.USERNAME_PROPERTY, "kermit");
  | 			((BindingProvider) port).getRequestContext().put(BindingProvider.PASSWORD_PROPERTY, "thefrog");
  | 
  |             
  |             
  |         } catch (Exception e) {
  | ....
  | ...
  | 

and also, i am not very clear about mixing jaxrpc and jaxws classes. :? 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161556#4161556

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161556


From do-not-reply at jboss.com  Mon Jun 30 16:47:45 2008
From: do-not-reply at jboss.com (paramsevak)
Date: Mon, 30 Jun 2008 16:47:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: web service conflicts with jbossws
	and jaxws
Message-ID: <7553106.1214858865342.JavaMail.jboss@colo-br-02.atl.jboss.com>

I do have the latest xercesimpl.jar is in the %JBOSS_HOME%/client/endorsed/ dir. Any other ideas? Anything would help.

Thanks

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161600#4161600

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161600


From do-not-reply at jboss.com  Mon Jun 30 16:50:15 2008
From: do-not-reply at jboss.com (paramsevak)
Date: Mon, 30 Jun 2008 16:50:15 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: web service conflicts with jbossws
	and jaxws
Message-ID: <32111738.1214859015819.JavaMail.jboss@colo-br-02.atl.jboss.com>

I do have the latest xercesimpl.jar is in the %JBOSS_HOME%/lib/endorsed/ dir. Any other ideas? Anything would help.

Thanks

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161604#4161604

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161604