From do-not-reply at jboss.com  Sat Mar  1 04:08:17 2008
From: do-not-reply at jboss.com (cardel)
Date: Sat, 1 Mar 2008 04:08:17 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Seam 2.0.1 & JBossWS & WAR
	deployment
Message-ID: <15606801.1204362497306.JavaMail.jboss@colo-br-02.atl.jboss.com>

PROBLEM SOLVED

I need to add context filter for my servlet. So i tried this:

in web.xml

  <filter>
  |      <filter-name>Seam Context Filter</filter-name>
  |      <filter-class>org.jboss.seam.web.ContextFilter</filter-class>
  |   </filter>
  | 
  |   <filter-mapping>
  |      <filter-name>Seam Context Filter</filter-name>
  |      <url-pattern>/test</url-pattern>        
  |   </filter-mapping>

or another solution is add context filter into components.xml


  | .
  | .
  | xmlns:web="http://jboss.com/products/seam/web"
  | .
  | .
  | <web:context-filter url-pattern="/test"/>

I've tried both and both works right.
Now I can use Component.getInstance and everything works

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

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


From do-not-reply at jboss.com  Sat Mar  1 04:33:16 2008
From: do-not-reply at jboss.com (jyc5131)
Date: Sat, 1 Mar 2008 04:33:16 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: jdk 1.6,
	jbossws 2.0.1 and jboss as 4.2.2.ga
Message-ID: <13026451.1204363996780.JavaMail.jboss@colo-br-02.atl.jboss.com>

Anyone else can help me?

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

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


From do-not-reply at jboss.com  Sat Mar  1 12:43:40 2008
From: do-not-reply at jboss.com (elgabo)
Date: Sat, 1 Mar 2008 12:43:40 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - setting context root for EJB based web
	services
Message-ID: <14746919.1204393421157.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello,

I have a very simple web service annotated with @Stateless and @WebService

@Stateless
@WebService
public class MyWebService
{
public void doSomething(){...}
}

when I deploy just the service.jar file the web service's endpoint is

http://localhost:8080/service/MyService

but if I put the jar inside the myear.ear file the web context changes

http://localhost:8080/myear-service/MyService

I have read here that since version 4.0 you can set the web service's context root by simply adding
webservice-context-root to the jboss.xml file, but there is no example on how to do this.  I would like to set the context root just to "service".

Thanks for all your help.



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

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


From do-not-reply at jboss.com  Sat Mar  1 23:28:57 2008
From: do-not-reply at jboss.com (jyc5131)
Date: Sat, 1 Mar 2008 23:28:57 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: jdk 1.6,
	jbossws 2.0.1 and jboss as 4.2.2.ga
Message-ID: <425731.1204432137164.JavaMail.jboss@colo-br-02.atl.jboss.com>

I found the StatelessBeanContext in Jboss4.2.2GA is conflict with the  InvocationHandlerEJB3 JbossWS2.0.1 later, the jbossws install won't update the jbossws-jboss42.jar, so the problem is appeared.

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

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


From do-not-reply at jboss.com  Sun Mar  2 17:59:33 2008
From: do-not-reply at jboss.com (adesai@atech.com)
Date: Sun, 2 Mar 2008 17:59:33 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - steps / guide to consume WSDL web
	service
Message-ID: <31265393.1204498773040.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello there,

This is my first ever attempt to play with Web Services and I need your help.

I've a WSDL web service and I need to consume it in JBoss 4.2.2 GA which comes with JBoss Portal Server 2.6.4.

1. Do I need to generate any Java code from the WSDL? If yes, how should I generate it? any tools? 
2. Where should I keep those Java files? Do I need any jar files to compile those java?
3. Do I need to write any XML configuration file to consume it? If yes, how? any samples?
4. Do I need to write any client code? e.g. JSP/Java/servlet to access the web service? Any samples? 

Basically, I'm looking for a end-to-end guide to consume a WSDL web service in JBoss. 

Thanks for your help.
Regards,
-Amol
 



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

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


From do-not-reply at jboss.com  Sun Mar  2 18:15:17 2008
From: do-not-reply at jboss.com (adesai@atech.com)
Date: Sun, 2 Mar 2008 18:15:17 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: How to write Jboss Web Service
	Client for JBoss 4.0.4 GA
Message-ID: <17158361.1204499718001.JavaMail.jboss@colo-br-02.atl.jboss.com>

hey buddy,

I was wondering whether u got the answer for your questions? I'm sailing in a same boat as yours and need a head start to consume a WSDL web service. Please do send me links of info/docs if you have any

thank u so much

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

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


From do-not-reply at jboss.com  Sun Mar  2 22:50:58 2008
From: do-not-reply at jboss.com (shashankjain)
Date: Sun, 2 Mar 2008 22:50:58 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - how to get an attribute fully qualified
Message-ID: <26496044.1204516258452.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,
Is there anyway by using annotation to make an attribute fully qualified. I need to this for partial encryption using WS Security.
The example says modify the WSDL but in my case its generated by runtime.So I need some sort of annotation to make an attribute fully qualified.
Pls let me know of alternatives in case any
Regards
Shashank

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

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


From do-not-reply at jboss.com  Mon Mar  3 03:37:18 2008
From: do-not-reply at jboss.com (techie_techie)
Date: Mon, 3 Mar 2008 03:37:18 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: How to write Jboss Web Service
	Client for JBoss 4.0.4 GA
Message-ID: <10571122.1204533438311.JavaMail.jboss@colo-br-02.atl.jboss.com>

If you are looking for simple RPC client then try to write on similer lines of  example given on download page. I got that way working.

Let me know your exact environment?

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

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


From do-not-reply at jboss.com  Mon Mar  3 11:14:13 2008
From: do-not-reply at jboss.com (adesai@atech.com)
Date: Mon, 3 Mar 2008 11:14:13 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: How to write Jboss Web Service
	Client for JBoss 4.0.4 GA
Message-ID: <274308.1204560853648.JavaMail.jboss@colo-br-02.atl.jboss.com>

I'm using JBoss 4.2.2.GA App Server on Windows. I have a WSDL web service to consume. I did execute wsconsume command, it created Java files out of WSDL and I don't know what to do next. Do i need to write any XML config? Client java class? Servlet? Can you please guide me? thank you very much for all your help.

Regards,
-Amol


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

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


From do-not-reply at jboss.com  Mon Mar  3 11:44:02 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 3 Mar 2008 11:44:02 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: steps / guide to consume WSDL web
	service
Message-ID: <10763461.1204562642950.JavaMail.jboss@colo-br-02.atl.jboss.com>

Did you read the documentaiton? http://jbws.dyndns.org/mediawiki/index.php?title=User_Guide#Web_Service_Clients I agree that it is not very clear, but the steps are all there is you look for them.

I also have another resource that has the steps laid out more clearly, but it is not free, I can supply the url if you like. 

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

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


From do-not-reply at jboss.com  Mon Mar  3 12:06:30 2008
From: do-not-reply at jboss.com (adesai@atech.com)
Date: Mon, 3 Mar 2008 12:06:30 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: steps / guide to consume WSDL web
	service
Message-ID: <10009463.1204563990692.JavaMail.jboss@colo-br-02.atl.jboss.com>

thanks Peter. Yes, that would be great. Please pass on the URL.

best regards,
-Amol


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

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


From do-not-reply at jboss.com  Mon Mar  3 12:12:36 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 3 Mar 2008 12:12:36 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: steps / guide to consume WSDL web
	service
Message-ID: <9686399.1204564356932.JavaMail.jboss@colo-br-02.atl.jboss.com>

The book JBoss in Action has a chapter dedicated to web services and contains a complete example application with step-by-step instructions for building and configuring the web service and client. The book is not published yet (it is based on JBossAS 5, which is not out yet, but the web services will run with 4.2.x), but the publisher has an early access program that enables you to get access to the un-edited chapters right now.  http://www.manning.com/jamae

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

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


From do-not-reply at jboss.com  Mon Mar  3 14:28:32 2008
From: do-not-reply at jboss.com (adesai@atech.com)
Date: Mon, 3 Mar 2008 14:28:32 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: steps / guide to consume WSDL web
	service
Message-ID: <10983171.1204572513001.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thanks Author! 

Best regards,
-Amol

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

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


From do-not-reply at jboss.com  Mon Mar  3 15:48:24 2008
From: do-not-reply at jboss.com (srini.ragu)
Date: Mon, 3 Mar 2008 15:48:24 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - bindings.xjc file for JAVA to WSDL
	approach
Message-ID: <17840493.1204577304309.JavaMail.jboss@colo-br-02.atl.jboss.com>

Can I pass in bindings.xjc, so the global rules in the bindings file will be used when JBossWS generates WSDL from source? I am using JAXB for binding.

Or by throwing this file in the path or any specific location could I make the implementation to use this for generating WSDL schema.

I need all the BigDecimal in Java to be extended as nillable type in the generated XSD. I can do this by the @XMLElement annotation on the property. But I want this rule to be applied globally for any Schema generated by the JBoss-WS stack.

Any idea or clarification on whether this is possible or not will be helpful.

Regards,
Srini

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

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


From do-not-reply at jboss.com  Mon Mar  3 17:48:06 2008
From: do-not-reply at jboss.com (mendaye)
Date: Mon, 3 Mar 2008 17:48:06 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - JBoss 4.0.4GA - Error generating Web
	Service Consumer code
Message-ID: <32256382.1204584487052.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello,

I have been trying to generate a web service consumer code in JBoss4.0.4 GA form WSDL that has dot-net service endpoint. However, using wstools ant task I got the following error..


  |   [wstools] java.lang.NullPointerException
  |   [wstools]     at org.jboss.ws.tools.WSDLToJava.appendMethods(WSDLToJava.java:2
  | 84)
  |   [wstools]     at org.jboss.ws.tools.WSDLToJava.createSEIFile(WSDLToJava.java:3
  | 33)
  |   [wstools]     at org.jboss.ws.tools.WSDLToJava.createSEI(WSDLToJava.java:355)
  |   [wstools]     at org.jboss.ws.tools.WSDLToJava.generateSEI(WSDLToJava.java:174
  | )
  |   [wstools]     at org.jboss.ws.tools.helpers.ToolsHelper.handleWSDLToJavaGenera
  | tion(ToolsHelper.java:326)
  |   [wstools]     at org.jboss.ws.tools.WSTools.process(WSTools.java:132)
  |   [wstools]     at org.jboss.ws.tools.WSTools.generate(WSTools.java:119)
  |   [wstools]     at org.jboss.ws.tools.ant.wstools.execute(wstools.java:103)
  |   [wstools]     at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja
  | va:288)
  |   [wstools]     at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
  |   [wstools]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
  | hodAccessorImpl.java:25)
  |   [wstools]     at java.lang.reflect.Method.invoke(Method.java:585)
  |   [wstools]     at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchU
  | tils.java:105)
  |   [wstools]     at org.apache.tools.ant.Task.perform(Task.java:348)
  |   [wstools]     at org.apache.tools.ant.Target.execute(Target.java:357)
  |   [wstools]     at org.apache.tools.ant.Target.performTasks(Target.java:385)
  |   [wstools]     at org.apache.tools.ant.Project.executeSortedTargets(Project.jav
  | a:1329)
  |   [wstools]     at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
  | 
  |   [wstools]     at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(De
  | faultExecutor.java:41)
  |   [wstools]     at org.apache.tools.ant.Project.executeTargets(Project.java:1181
  | )
  |   [wstools]     at org.apache.tools.ant.Main.runBuild(Main.java:698)
  |   [wstools]     at org.apache.tools.ant.Main.startAnt(Main.java:199)
  |   [wstools]     at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
  |   [wstools]     at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
  | 
  | BUILD FAILED
  | c:\ws-test\EnNet\ws_client_build.xml:102: Error running jbossws:
  | 
  | Total time: 7 seconds
  | 
--------------------------------------------------------------------------
Configuration file (wstolls-config.xml)


  | 
  | <?xml version="1.0" encoding="UTF-8"?>
  | <configuration
  |    xmlns="http://www.jboss.org/jbossws-tools"
  |    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  |    xsi:schemaLocation=
  |    "http://www.jboss.org/jbossws-tools
  |     http://www.jboss.org/jbossws-tools/schema/jbossws-tool_1_0.xsd">
  |  <wsdl-java file="http://192.168.0.160:8090/wsdl/IEnNET?wsdl">
  |   <!--
  |         <mapping file="jaxrpc-mapping.xml" />
  |   -->
  |   </wsdl-java>
  | </configuration>
  | 


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

The same error happen when I use wstools.bat, look below..


  | C:\WS-Test\EnNet>c:\dev\jboss\jboss-4.0.4.GA\bin\wstools -config wstools-config.
  | xml -dest dest
  | ========================================================================="
  | .
  |   WSTools Environment
  | .
  |   JBOSS_HOME: c:\DEV\JBoss\jboss-4.0.4.GA\bin\\..
  | .
  |   JAVA: C:\Program Files\Java\jdk1.5.0_13\bin\java
  | .
  |   JAVA_OPTS:
  | .
  | ========================================================================="
  | .
  | Exception in thread "main" java.lang.NullPointerException
  |         at org.jboss.ws.tools.WSDLToJava.appendMethods(WSDLToJava.java:284)
  |         at org.jboss.ws.tools.WSDLToJava.createSEIFile(WSDLToJava.java:333)
  |         at org.jboss.ws.tools.WSDLToJava.createSEI(WSDLToJava.java:355)
  |         at org.jboss.ws.tools.WSDLToJava.generateSEI(WSDLToJava.java:174)
  |         at org.jboss.ws.tools.helpers.ToolsHelper.handleWSDLToJavaGeneration(Too
  | lsHelper.java:326)
  |         at org.jboss.ws.tools.WSTools.process(WSTools.java:132)
  |         at org.jboss.ws.tools.WSTools.generate(WSTools.java:119)
  |         at org.jboss.ws.tools.WSTools.main(WSTools.java:61)
  | 

Can someone help on this issue please?

Thanks,
Surafel

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

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


From do-not-reply at jboss.com  Tue Mar  4 08:03:20 2008
From: do-not-reply at jboss.com (boopet)
Date: Tue, 4 Mar 2008 08:03:20 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Problems with multipart/related
	responses
Message-ID: <20858447.1204635801050.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi everyone,

we have created a JBossWS Client with version 2.0.1 consuming a Axis2 webservice, that is sending its responses in multipart/related format.

Everything works fine when testing with SoapUi. but when calling a method with the JBoss client, we get this error message:

Caused by: java.lang.IllegalArgumentException: multipart/related stream invalid, no root part was found
  | 	at org.jboss.ws.core.soap.attachment.MultipartRelatedDecoder.decodeMultipartRelatedMessage(MultipartRelatedDecoder.java:164)
  | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:228)
  | 	at org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP.read(SOAPMessageUnMarshallerHTTP.java:84)
  | 	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:175)

I have already tried with the libraries from 2.0.3. But this causes the same problems. 

This is the response received from Axis2 Server:

HTTP/1.1 200 OK
  | Date: Tue, 04 Mar 2008 09:41:08 GMT
  | Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_98BB2CA94931E2B9C21204623668217; type="application/xop+xml"; start="0.urn:uuid:98BB2CA94931E2B9C21204623668218 at apache.org"; start-info="text/xml"
  | Server: Apache-Coyote/1.1
  | Transfer-Encoding: chunked
  | 
  | --MIMEBoundaryurn_uuid_98BB2CA94931E2B9C21204623668217
  | Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"
  | Content-Transfer-Encoding: binary
  | Content-ID: <0.urn:uuid:98BB2CA94931E2B9C21204623668218 at apache.org>
  | 
  | <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><ns:loadEloFileUrlResponse xmlns:ns="http://eloservice.giag.com"><ns:return>http://some_url_notshown</ns:return></ns:loadEloFileUrlResponse></soapenv:Body></soapenv:Envelope>
  | --MIMEBoundaryurn_uuid_98BB2CA94931E2B9C21204623668217--

Did somebody have similar problems?
If this is a known issue please let me know. 
Thanks for your help!

Regards,
Norbert

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

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


From do-not-reply at jboss.com  Tue Mar  4 09:09:40 2008
From: do-not-reply at jboss.com (ejb3workshop)
Date: Tue, 4 Mar 2008 09:09:40 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Using custom principal class with
	JBossWS
Message-ID: <24159739.1204639780763.JavaMail.jboss@colo-br-02.atl.jboss.com>

I would like to use my own Principal class with my own LoginModule. I configured the LoginModule in login-config.xml and annotated by SLSB as follows :


  | @Stateless(name="JobAPIWeb")
  | @WebService(name="JobAPIWeb", portName="...Port", serviceName="JobAPIWebService", targetNamespace="...")
  | @EndpointConfig(configName = "Standard WSSecurity Endpoint")
  | @SecurityDomain(value="THZone")
  | @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL, parameterStyle = SOAPBinding.ParameterStyle.BARE)
  | public class JobAPIWeb implements JobAPIWebRemote {
  | ...
  | 

Authentication takes place, however when I try to access the principal via 


  | m_sessionContext.getCallerPrincipal().getClass().getName()
  | 

it presents me with a org.jboss.ws.extensions.security.SimplePrincipal, rather then my own class returned in the LoginModules commit method.

My search so far led me to ReceiveUsernameOperation in which the UserNameToken is converted to a SimplePrincipal.

http://fisheye.jboss.com/browse/JBossWS/trunk/jbossws-core/src/main/java/org/jboss/ws/extensions/security/ReceiveUsernameOperation.java?r=4023


Are there any configuration options which would allow me to access the principal object as it is returned by my LoginModule.

Thanks in advance.
Alex

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

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


From do-not-reply at jboss.com  Tue Mar  4 14:59:59 2008
From: do-not-reply at jboss.com (rafik777)
Date: Tue, 4 Mar 2008 14:59:59 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - webservice on jbos 4.0.2
Message-ID: <22076791.1204660799359.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello, 
I want to know:
Is it possible to run some of brand new web service technology like jax-ws, metro or CXF on old AS jboss 4.0.2?

There is buil-in ws4ee.
I tried do this but unfortunately with no results.

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

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


From do-not-reply at jboss.com  Tue Mar  4 16:29:01 2008
From: do-not-reply at jboss.com (rafik777)
Date: Tue, 4 Mar 2008 16:29:01 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - ws4ee wscompile
Message-ID: <12628330.1204666141809.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hey,

Is it natural that when I generate artifacts by wscompile i get  4 *.java files per service method in the same package like service (interface and Endpoint-impl) ?

I tried to change package name in config.xml but then only one file (ServiceName_SerializerRegistry) moved to new package.

This's messy architecture.

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

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


From do-not-reply at jboss.com  Wed Mar  5 01:14:38 2008
From: do-not-reply at jboss.com (fastbob)
Date: Wed, 5 Mar 2008 01:14:38 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - SSL and native libraries
Message-ID: <22371135.1204697678595.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hopefully I have the correct forum section. While I've researched the issue a bit, I can't claim to fully understand what's going on. 

On Windows XP, using JBoss 4.2.2 (no modifications) and Sun jdk 1.6, we enabled SSL by uncommenting the SSL connector in service.xml:
          <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"
  |            address="${jboss.bind.address}" maxThreads="100" 
  |            scheme="https" secure="true" clientAuth="false"
  |            keystoreFile="${jboss.server.home.dir}/conf/my.keystore"
  |            keystorePass="something" sslProtocol = "TLS" />
This seemed to be handled fine during startup - no native library found but startup continued and SSL worked:
05:47:06,150 INFO  [NativeServerConfig] JBoss Web Services - Native
  | 05:47:06,150 INFO  [NativeServerConfig] jbossws-native-2.0.1.SP2 (build=200710210837)
  | 05:47:06,941 INFO  [Embedded] Catalina naming disabled
  | 05:47:07,281 INFO  [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Java\jdk1.6.0\bin;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\Java\jdk1.6.0\bin;C:\Java\apache-ant-1.7.0\bin;C:\Java\jikes_1.22\bin;C:\Java\maven-2.0.7\bin;c:\tools\cygwin\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\cvsnt;C:\Program Files\MySQL\MySQL Server 5.0\bin;c:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\QuickTime\QTSystem\
  | 05:47:07,352 INFO  [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
  | 05:47:08,083 INFO  [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8443
  | 05:47:08,093 INFO  [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-0.0.0.0-8009
  | 

On Fedora8 Linux, we copied the same JBoss directory to the system (same Sun jdk 1.6). However, the log showed the following during startup:
03:22:19,508 INFO  [NativeServerConfig] JBoss Web Services - Native
  | 03:22:19,508 INFO  [NativeServerConfig] jbossws-native-2.0.1.SP2 (build=200710210837)
  | 03:22:20,310 INFO  [Embedded] Catalina naming disabled
  | 03:22:20,462 WARN  [Connector] Property debug not found on the protocol handler.
  | 03:22:20,466 WARN  [Connector] Property clientAuth not found on the protocol handler.
  | 03:22:20,466 WARN  [Connector] Property keystoreFile not found on the protocol handler.
  | 03:22:20,467 WARN  [Connector] Property keystorePass not found on the protocol handler.
  | 03:22:20,747 INFO  [AprLifecycleListener] Loaded Apache Tomcat Native library 1.1.10.
  | 03:22:20,751 INFO  [AprLifecycleListener] APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
  | 03:22:21,092 INFO  [Http11AprProtocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
  | 03:22:21,094 ERROR [Http11AprProtocol] Error initializing endpoint
  | java.lang.Exception: No Certificate file specified
  |         at org.apache.tomcat.jni.SSLContext.setCertificate(Native Method)
  |         at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:683)
  | ...
So it appears that on Fedora the native library was loaded, but then the properties of the SSL connector were not loaded. Startup eventually failed due to the port being in use:
03:23:12,305 INFO  [Http11AprProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
  | 03:23:12,383 ERROR [Http11AprProtocol] Error starting endpoint
  | java.lang.Exception: Socket bind failed: [98] Address already in use
  |         at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:611)
  |         at org.apache.tomcat.util.net.AprEndpoint.start(AprEndpoint.java:716)
  |         at org.apache.coyote.http11.Http11AprProtocol.start(Http11AprProtocol.java:137)
  | 
I'm not clear what we need to change in the configuration to get things working on Linux. It seems like removing the native library would work against better performance. Any pointers would be appreciated. Thanks.

Bob

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

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


From do-not-reply at jboss.com  Wed Mar  5 08:06:48 2008
From: do-not-reply at jboss.com (schueffi)
Date: Wed, 5 Mar 2008 08:06:48 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - multiple webservices in different
	virtualhosts
Message-ID: <26531322.1204722408680.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

i have jboss-4.2.2 configured to serve content for two different virtualhosts (in jboss-web/server.xml), www.host-a.com and www.host-b.com . 

Now, i want to deploy a pojo-jaxws based webservice on both of these virtualhosts (each configured to serve only for its particular virtualhost in jboss-web.xml) but it fails with "Endpoint already registered" when deploying the second one. 
Deploying only one of it leads to the correct result for the particular webservice, it is just not possible to deploy both the same time.
 
Both endpoints use the same context-root, and the same url-pattern, but different virtual-hosts.
(e.g.
www.host-a.com/service/MyService  -> webservice-a
www.host-b.com/service/MyService  -> webservice-b
)

Is this deployment-scenario possible? A related bug report might be JBWS-981, although this is only for EJB-based endpoints instead of pojo-based JSE-Endpoints.

regards

Stefan Schueffler

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

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


From do-not-reply at jboss.com  Wed Mar  5 09:10:35 2008
From: do-not-reply at jboss.com (rcarmichael)
Date: Wed, 5 Mar 2008 09:10:35 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - @WebService method argument names
Message-ID: <13515220.1204726235902.JavaMail.jboss@colo-br-02.atl.jboss.com>

If I've got an EJB3 Bean with @Stateless and @WebService defined with a method like:

  | addNumbers(int num1, int num2)
  | 

the WSDL generated will simply call the arguments arg0 and arg1. Is there a way to force the WSDL generated to actually use the proper argument names? In this silly case it isn't important but it is confusing for my web service users not to know the argument names.

Thanks!
- Ryan

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

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


From do-not-reply at jboss.com  Wed Mar  5 10:19:55 2008
From: do-not-reply at jboss.com (sjackson88)
Date: Wed, 5 Mar 2008 10:19:55 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Runtime classloader cannot be null
Message-ID: <5928411.1204730395640.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have the same issue using jboss-4.2.2.GA and JBossWS2.0.1SP2 or JBossWS2.0.3.  

I need to make my .war dependent on the service that provides the data being served by the web service.  My .war contains a single class; it uses @WebService and @WebMethod to tag what needs to be exposed to the wsdl.

I used a < depends > element in jboss-web.xml to make the .war dependent on the service.  Unfortunately it appears that the DeploymentAspectManagerImpl is executing despite the .war still waiting for creation/startup.  My guess is that JAXWSMetaDataBuilderJSE then tries to pull the classloader while the .war is in this state and receives null.

Is there another way to accomplish this dependency?  

Here's a snippet of the log after the interceptors have been set up:


  | 2008-03-05 10:08:22,953 DEBUG [org.jboss.deployment.MainDeployer] Done with create step of deploying TEST.war
  | 2008-03-05 10:08:22,953 DEBUG [org.jboss.deployment.MainDeployer] Begin deployment start file:/C:/jboss-4.2.2.GA/server/default/deploy/TEST.war/
  | 2008-03-05 10:08:22,953 DEBUG [org.jboss.system.ServiceController] starting service jboss.web.deployment:war=TEST.war,id=-1578707402
  | 2008-03-05 10:08:22,953 DEBUG [org.jboss.system.ServiceController] Start requested before create, calling create now for service: jboss.web.deployment:war=TEST.war,id=-1578707402
  | 2008-03-05 10:08:22,953 DEBUG [org.jboss.system.ServiceController] Creating service jboss.web.deployment:war=TEST.war,id=-1578707402
  | 2008-03-05 10:08:22,953 DEBUG [org.jboss.system.ServiceController] waiting in create of jboss.web.deployment:war=TEST.war,id=-1578707402 waiting on test.test:service=TEST.0
  | 2008-03-05 10:08:22,953 DEBUG [org.jboss.system.ServiceController] waiting in start jboss.web.deployment:war=TEST.war,id=-1578707402 on test.test:service=TEST.0
  | 2008-03-05 10:08:22,953 DEBUG [org.jboss.wsf.container.jboss42.JAXWSDeployerHookPostJSE] deploy: TEST.war
  | 2008-03-05 10:08:22,953 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider] provide SPI 'class org.jboss.wsf.spi.deployment.DeploymentAspectManagerFactory'
  | 2008-03-05 10:08:22,953 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider] class org.jboss.wsf.spi.deployment.DeploymentAspectManagerFactory Implementation: org.jboss.wsf.framework.deployment.DefaultDeploymentAspectManagerFactory at 709366
  | 2008-03-05 10:08:22,953 DEBUG [org.jboss.wsf.framework.deployment.DefaultDeploymentAspectManagerFactory] DeploymentAspectManager for: WSDeploymentAspectManagerPostJSE
  | 2008-03-05 10:08:22,953 DEBUG [org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl] RuntimeLoaderDeploymentAspect:Create
  | 2008-03-05 10:08:22,953 DEBUG [org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl] JAXBIntroDeploymentAspect:Create
  | 2008-03-05 10:08:22,953 DEBUG [org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl] UnifiedMetaDataDeploymentAspect:Create
  | 2008-03-05 10:08:22,953 DEBUG [org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderJSE] START buildMetaData: [name=TEST.war]
  | 2008-03-05 10:08:22,953 ERROR [org.jboss.deployment.MainDeployer] Could not start deployment: file:/C:/jboss-4.2.2.GA/server/default/deploy/TEST.war/
  | 

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

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


From do-not-reply at jboss.com  Wed Mar  5 10:25:04 2008
From: do-not-reply at jboss.com (sjackson88)
Date: Wed, 5 Mar 2008 10:25:04 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Runtime classloader cannot be null
Message-ID: <22420577.1204730704080.JavaMail.jboss@colo-br-02.atl.jboss.com>

I forgot to mention I'm not using a loader-repository.  My jboss-web.xml looks like this:


  | <?xml version="1.0" encoding="UTF-8"?>
  | 
  | <!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.4//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd">
  | 
  | 
  | <jboss-web>
  |     
  |     <depends>test.test:service=TEST.0</depends> 
  |     
  | </jboss-web>
  | 

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

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


From do-not-reply at jboss.com  Wed Mar  5 16:22:05 2008
From: do-not-reply at jboss.com (fbenvegna)
Date: Wed, 5 Mar 2008 16:22:05 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Question: Is it possible having both
	WS-Addressing and WS-Se
Message-ID: <22709275.1204752125899.JavaMail.jboss@colo-br-02.atl.jboss.com>

Is it possible having both WS-Addressing and WS-Security with JBossWS?
If YES, give me an example, please!

It's possible with CXF but I don't know with others... 

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

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


From do-not-reply at jboss.com  Wed Mar  5 17:59:01 2008
From: do-not-reply at jboss.com (ghinkle)
Date: Wed, 5 Mar 2008 17:59:01 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: avoid lazy-initialization exceptions
Message-ID: <26299987.1204757941305.JavaMail.jboss@colo-br-02.atl.jboss.com>

Just sending along a link to our solution to this problem. Like I said, we don't like it, but it works.

This is the invoker:
http://viewvc.rhq-project.org/cgi-bin/viewvc.cgi/rhq/trunk/modules/enterprise/server/safe-invoker/src/main/java/org/rhq/enterprise/server/util/EJB3SafeEndpointInvoker.java?revision=7&view=markup

And this is how we deploy it:
http://viewvc.rhq-project.org/cgi-bin/viewvc.cgi/rhq/trunk/modules/enterprise/server/safe-invoker/src/main/java/org/rhq/enterprise/server/util/EJB3SafeEndpointInvokerDeploymentAspect.java?revision=7&view=markup

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

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


From do-not-reply at jboss.com  Thu Mar  6 02:20:32 2008
From: do-not-reply at jboss.com (fastbob)
Date: Thu, 6 Mar 2008 02:20:32 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: SSL and native libraries
Message-ID: <5724439.1204788032571.JavaMail.jboss@colo-br-02.atl.jboss.com>

I tried an experiment. I commented out the SSL connector and things worked (except for SSL, of course).

But I found the cause of the problem. I took a closer look at the installed packages on fedora. Tomcat was installed as part of the system packages (probably by me), and as soon as I removed the tomcat-native package, the native library was not loaded. SSL started working.

Bob

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

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


From do-not-reply at jboss.com  Thu Mar  6 04:11:12 2008
From: do-not-reply at jboss.com (schueffi)
Date: Thu, 6 Mar 2008 04:11:12 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: @WebService method argument names
Message-ID: <28798119.1204794672446.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi

i think the solution should be somewhat like


  | @WebMethod
  | public int addNumbers(
  |   @WebParam(name = "myParamName1") int num1, 
  |   @WebParam(name = "myParamName2") int num2
  | )
  | 

regards

Stefan Schueffler

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

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


From do-not-reply at jboss.com  Thu Mar  6 08:40:21 2008
From: do-not-reply at jboss.com (rcarmichael)
Date: Thu, 6 Mar 2008 08:40:21 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: @WebService method argument names
Message-ID: <21309041.1204810821951.JavaMail.jboss@colo-br-02.atl.jboss.com>

That solution works perfectly, thank you for taking the time to respond.

- Ryan

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

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


From do-not-reply at jboss.com  Thu Mar  6 08:53:39 2008
From: do-not-reply at jboss.com (khkachn)
Date: Thu, 6 Mar 2008 08:53:39 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Throwing Exception from a web
	service method
Message-ID: <31816232.1204811619996.JavaMail.jboss@colo-br-02.atl.jboss.com>

 .

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

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


From do-not-reply at jboss.com  Thu Mar  6 10:43:07 2008
From: do-not-reply at jboss.com (squ1rr3l)
Date: Thu, 6 Mar 2008 10:43:07 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: SSL and native libraries
Message-ID: <5836923.1204818187226.JavaMail.jboss@colo-br-02.atl.jboss.com>

"fastbob" wrote : I tried an experiment. I commented out the SSL connector and things worked (except for SSL, of course).
  | 
  | But I found the cause of the problem. I took a closer look at the installed packages on fedora. Tomcat was installed as part of the system packages (probably by me), and as soon as I removed the tomcat-native package, the native library was not loaded. SSL started working.
  | 
  | Bob

Same thing here.  Apparently, there is a problem with the native libraries.  I have had a lot of problems getting SSL enabled for any Win32 apr-based libraries.

In this case, I had everything working on a Windows 2003 server.  Then I applied the native libraries (from http://labs.jboss.org/jbossweb/downloads/jboss-native/?action=a&windowstate=maximized), and SSL died.  Same errors that you specified:
10:23:42,564 WARN  [Connector] Property strategy not found on the protocol handler.
  | 10:23:42,580 WARN  [Connector] Property clientAuth not found on the protocol handler.
  | 10:23:42,580 WARN  [Connector] Property keystoreFile not found on the protocol handler.
  | 10:23:42,580 WARN  [Connector] Property keystorePass not found on the protocol handler.
  | 10:23:42,752 INFO  [AprLifecycleListener] Loaded Apache Tomcat Native library 1.1.12.
  | 10:23:42,845 INFO  [AprLifecycleListener] APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
  | 10:23:44,408 INFO  [Http11AprProtocol] Initializing Coyote HTTP/1.1 on http-172.25.141.151-8080
  | 10:23:44,424 ERROR [Http11AprProtocol] Error initializing endpoint
  | java.lang.Exception: No Certificate file specified
  |         at org.apache.tomcat.jni.SSLContext.setCertificate(Native Method)
  |         at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:683)
  |         at org.apache.coyote.http11.Http11AprProtocol.init(Http11AprProtocol.java:107)
  |         at org.apache.catalina.connector.Connector.initialize(Connector.java:1073)
  | ....
  | 

I have had similar issues trying to get LDAP over SSL working in Windows using the Apache ldap modules, which also rely on APR and APRUtils Win32 binaries.  I've posted messages to the APR-dev mailing list, but they sent me to the Apache-dev list, and the issue was pretty much just ignored there.

I imagine there is somebody that knows what's going on with this, but I can't figure it out.

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

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


From do-not-reply at jboss.com  Thu Mar  6 13:00:08 2008
From: do-not-reply at jboss.com (websfasciomaster)
Date: Thu, 6 Mar 2008 13:00:08 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Problem retrieving service in
	developing a client
Message-ID: <27923082.1204826408747.JavaMail.jboss@colo-br-02.atl.jboss.com>

My client code is:
System.out.println("Starting Test Client");
  |         URL url = new URL("http://localhost:8080/EspertoWS/ServiceBean?wsdl");
  |         QName qname = new QName("http://ws.server.espertoEnel.nergal.it/","ServiceBean");
  |         System.out.println("Creating a service Using: \n\t" 
  |                                    + url + " \n\tand " + qname);
  |         ServiceFactoryImpl factory = (ServiceFactoryImpl) ServiceFactoryImpl.newInstance();
  |         System.out.println("Passa! Qname: "+qname.getNamespaceURI());
  |         
  |         Service remote = factory.createService(url,qname);
  |         System.out.println("Obtaining reference to a proxy object. Remote: wsdl location "+remote.getWSDLDocumentLocation()+" Service name:"+remote.getServiceName());
  |         ServiceLocale proxy = (ServiceLocale) remote.getPort(qname,ServiceLocale.class);
  | 
and when i run this i obtain this excepition:
Exception in thread "main" org.jboss.ws.metadata.wsdl.WSDLException: javax.wsdl.WSDLException: WSDLException (at /definitions/message[1]/part): faultCode=UNBOUND_PREFIX: Unable to determine namespace of 'tns:getCurvaAllarmiPicchiResponse'.
	at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:154)
	at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:321)
	at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCClientMetaDataBuilder.buildMetaData(JAXRPCClientMetaDataBuilder.java:115)
	at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCClientMetaDataBuilder.buildMetaData(JAXRPCClientMetaDataBuilder.java:86)
	at org.jboss.ws.core.jaxrpc.client.ServiceImpl.(ServiceImpl.java:111)
	at org.jboss.ws.core.jaxrpc.client.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:157)
	at org.jboss.ws.core.jaxrpc.client.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:128)
	at it.nergal.espertoEnel.server.hibernate.test.TestWS.main(TestWS.java:31)
Caused by: javax.wsdl.WSDLException: WSDLException (at /definitions/message[1]/part): faultCode=UNBOUND_PREFIX: Unable to determine namespace of 'tns:getCurvaAllarmiPicchiResponse'.
	at com.ibm.wsdl.util.xml.DOMUtils.getQName(DOMUtils.java:309)
	at com.ibm.wsdl.util.xml.DOMUtils.getQualifiedAttributeValue(DOMUtils.java:367)
	at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.getQualifiedAttributeValue(JBossWSDLReaderImpl.java:2046)
	at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.parsePart(JBossWSDLReaderImpl.java:1305)
	at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.parseMessage(JBossWSDLReaderImpl.java:1284)
	at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.parseDefinitions(JBossWSDLReaderImpl.java:336)
	at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.readWSDL(JBossWSDLReaderImpl.java:2293)
	at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.readWSDL(JBossWSDLReaderImpl.java:2257)
	at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.readWSDL(JBossWSDLReaderImpl.java:2310)
	at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.readWSDL(JBossWSDLReaderImpl.java:2331)
	at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.readWSDL(JBossWSDLReaderImpl.java:2363)
	at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:127)
	... 7 more


My web service class is:
@Stateless
  | //@WebService(serviceName="sdsws",portName="sdswsport")
  | @WebService(endpointInterface="it.nergal.espertoEnel.server.ws.ServiceLocale", 
  | 		serviceName="EspertoWS",portName="ServiceBeanPort",
  | 		targetNamespace="http://localhost:8080/EspertoWS/ServiceBean")
  | public class ServiceBean implements ServiceLocale{
  | .......
  | }


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

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


From do-not-reply at jboss.com  Fri Mar  7 09:51:35 2008
From: do-not-reply at jboss.com (Fugee47)
Date: Fri, 7 Mar 2008 09:51:35 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Problems getting client to work
Message-ID: <30293136.1204901495280.JavaMail.jboss@colo-br-02.atl.jboss.com>

i got a standalone java-client working:
 
package simpleclient;
 
import javax.xml.ws.WebServiceRef;
import helloservice.endpoint.HelloService;
import helloservice.endpoint.Hello;
 
public class HelloClient {
@WebServiceRef(wsdlLocation="http://localhost:8080/helloservice/Hello?wsdl")
static HelloService service = new HelloService();
 
public static void main(String[] args) {
System.out.println("Retrieving the port from the following service: " + service);
Hello port = service.getHelloPort();
System.out.println("Invoking the sayHello operation on the port.");
String name;
if (args.length > 0) {
name = args[0];
} else {
name = "No Name";
}
String response = port.sayHello(name);
System.out.println(response);
}
}
 
 
but when i copy the code into a new function and access it from within a jsp-file, i get errors.
 
package simpleclient;
 
import javax.xml.ws.WebServiceRef;
import helloservice.endpoint.HelloService;
import helloservice.endpoint.Hello;
 
public class HelloClient {
@WebServiceRef(wsdlLocation="http://localhost:8080/helloservice/Hello?wsdl")
static HelloService service = new HelloService();
 
public static String say(String args) {
Hello port = service.getHelloPort();
String name;
if (args != null) {
name = args;
} else {
name = "No Name";
}
String response = port.sayHello(name);
return response;
}
}
 
 
 
ERROR [ServiceDelegateImpl] Cannot create proxy for SEI helloservice.endpoint.Hello from: vfsfile:/opt/jboss-5.0.0.Beta4/server/default/deploy/
11:51:14,647 ERROR [[jsp]] Servlet.service() for servlet jsp threw exception
java.lang.IllegalArgumentException: helloservice.endpoint.Hello is not an interface
 
i dont understand this error, since the standalone client does not complain about helloservice.endpoint.Hello being not an interface 

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

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


From do-not-reply at jboss.com  Fri Mar  7 12:07:58 2008
From: do-not-reply at jboss.com (asouza_2000)
Date: Fri, 7 Mar 2008 12:07:58 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - XML Binding - XMLGregorianDate to
	xs:dateTime rather than xs
Message-ID: <18616890.1204909678286.JavaMail.jboss@colo-br-02.atl.jboss.com>

I pretty much hope you guys can help me out here.

I, via xjc, compiled a .XSD into several classes. Automatically xs:dateTime schema types are translated to XMLGregorianCalendar java type. No problem about that.
I then use some of the generated classes as WS parameters for a service I'm designing. No problem about that either.
The thing is that when JBoss WS generates the WSDL file from my service, it translates the XMLGregorianDate type to xs:anySimpleType. I checked it out and it seems that it should be the default behavior of JAXB.
I'd like to know how can I force the translation of XMLGregorianCalendar to xs:dateTime rather than put an annotation @XMLSchemaType in all the properties that are XMLGregorianCalendar types.

Thanks in advance,

Antonio Souza.

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

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


From do-not-reply at jboss.com  Fri Mar  7 14:17:05 2008
From: do-not-reply at jboss.com (anguilla)
Date: Fri, 7 Mar 2008 14:17:05 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - How to tell which Web Service stack(s)
	are in which Redhat J
Message-ID: <4622939.1204917425178.JavaMail.jboss@colo-br-02.atl.jboss.com>

Please forgive this total newbie question, but I have been searching for 3 days to an answer to this question. I'm sure the info is out there, and I just haven't been smart enough to stumble upon it. Anyway, I am trying to understand which web service stacks are integrated in the various JBoss product offerings from Redhat, what standards each implement, and what the RH web services roadmap looks like. I am totally confused by all this, probably because I come from a background where I only had the choice of using ASP.NET for web services, and now there are too many options 8=).

If I buy JBoss Application Server from Redhat, am I getting JBossWS as the web service solution? Or is JBossWS something that I have to acquire separately? Or are there multiple WS implementations (of which JBossWS is only one), any of which can be utilized with the JBoss AS? 

I purchased the JBoss Developer Studio from Redhat, which came with an entitlement to RHEL 5 (which I installed), and came bundled with the JBoss Enterprise Application Platform (which appears to include JBoss Application Server 4.2). How can I tell what the web service stack is for the AS? On the IDE side of things, it looks like the JBDS wants me to create Apache Axis or Axis2 web services. I don't see any mention of JBossWS in the IDE. Am I missing some crucial plug-in? 

I fear the answer to my questions is that I am just totally clueless, but if some kind soul could point me to some specific information (just telling me to go to the forum or wiki won't help, as I've already been there and am still confused), I would really appreciate it. Thanks in advance.

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

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


From do-not-reply at jboss.com  Fri Mar  7 14:22:13 2008
From: do-not-reply at jboss.com (GTWebDev)
Date: Fri, 7 Mar 2008 14:22:13 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Upgrading to 4.2.2 changed published
	WSDL
Message-ID: <25751314.1204917733762.JavaMail.jboss@colo-br-02.atl.jboss.com>

We recently upgraded our JBossAS from 4.0.5 to 4.2.2.  We have EJBs exposed as Web Services.  Since the upgrade, applications that consume the Services no longer work due to changes in the WSDL produced by 4.2.2.  Though our EJBs are annotated, the WSLDs are very different.  We have tried to annotate at the package level to get the WSDL to match the old services in 4.0.5 but have had no luck.  

Errors we experience are similar to the following:
12:46:10,048 ERROR [SOAPFaultHelperJAXWS] SOAP request exception javax.ejb.EJBException: java.lang.NullPointerException

All is good if we Re-consume the service but the is not a viable solutions for all of our clients.

Has anyone experienced XmlSchema changes when upgrading?  Does anyone have a solution for such a problem?  Any guidance is appreciated.


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

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


From do-not-reply at jboss.com  Fri Mar  7 14:35:41 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 7 Mar 2008 14:35:41 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: How to tell which Web Service
	stack(s) are in which Redh
Message-ID: <23862785.1204918541476.JavaMail.jboss@colo-br-02.atl.jboss.com>

Yes, if you get JBossAS (community version) or JBossEAP (enterprise/supported version), it comes with JBossWS as the web service stack. Usually the easiest way to figure out which version of JBossWS is included is to look at the Manifest.mf file in one of the JBossWS jar file, like client/jbossws-client.jar, which in JBossEAP 4.2 says:

Implementation-Version: jbossws-1.2.1.GA (build=200704151756)

I don't use JBoss Developer Studio, so I cannot comment on its insistence of doing Axis-based web services.

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

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


From do-not-reply at jboss.com  Fri Mar  7 15:12:07 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 7 Mar 2008 15:12:07 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Problems getting client to work
Message-ID: <10970410.1204920727880.JavaMail.jboss@colo-br-02.atl.jboss.com>

We are already discussing this at http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134809#4134809

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

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


From do-not-reply at jboss.com  Sun Mar  9 08:03:12 2008
From: do-not-reply at jboss.com (arrojusrikanth)
Date: Sun, 9 Mar 2008 08:03:12 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - webservice compiler error
Message-ID: <18808263.1205064192384.JavaMail.jboss@colo-br-02.atl.jboss.com>

when compile webservice with ant it generating compiler errors


  | 
  | 
  | D:\programs\webservices\calculatorwebservice>ant
  | Buildfile: build.xml
  | 
  | prepare:
  |     [mkdir] Created dir: 
  | 
  | D:\programs\webservices\calculatorwebservice\build
  |     [mkdir] Created dir: 
  | 
  | D:\programs\webservices\calculatorwebservice\build\
  | 
  | clas
  | ses
  | 
  | compile:
  |     [javac] Compiling 3 source files to 
  | 
  | D:\programs\webservices\calculatorwebser
  | vice\build\classes
  |     [javac] 
  | 
  | D:\programs\webservices\calculatorwebservice\src\we
  | 
  | bservice1\Calcula
  | torBean.java:2: cannot find symbol
  |     [javac] symbol  : class Stateless
  |     [javac] location: package javax.ejb
  |     [javac] import javax.ejb.Stateless;
  |     [javac]                  ^
  |     [javac] 
  | 
  | D:\programs\webservices\calculatorwebservice\src\we
  | 
  | bservice1\Calcula
  | tor.java:9: incompatible types
  |     [javac] found   : javax.jws.WebService
  |     [javac] required: 
  | 
  | java.lang.annotation.Annotation
  |     [javac] @WebService(name="Calculator1")
  |     [javac]  ^
  |     [javac] 
  | 
  | D:\programs\webservices\calculatorwebservice\src\we
  | 
  | bservice1\Calcula
  | tor.java:10: incompatible types
  |     [javac] found   : javax.jws.soap.SOAPBinding
  |     [javac] required: 
  | 
  | java.lang.annotation.Annotation
  |     [javac] @SOAPBinding(style=Style.RPC)
  |     [javac]  ^
  |     [javac] 
  | 
  | D:\programs\webservices\calculatorwebservice\src\we
  | 
  | bservice1\Calcula
  | tor.java:10: duplicate annotation
  |     [javac] @SOAPBinding(style=Style.RPC)
  |     [javac]                         ^
  |     [javac] 
  | 
  | D:\programs\webservices\calculatorwebservice\src\we
  | 
  | bservice1\Calcula
  | tor.java:13: incompatible types
  |     [javac] found   : javax.jws.WebMethod
  |     [javac] required: 
  | 
  | java.lang.annotation.Annotation
  |     [javac]    @WebMethod int add(int x, int y);
  |     [javac]     ^
  |     [javac] 
  | 
  | D:\programs\webservices\calculatorwebservice\src\we
  | 
  | bservice1\Calcula
  | tor.java:15: incompatible types
  |     [javac] found   : javax.jws.WebMethod
  |     [javac] required: 
  | 
  | java.lang.annotation.Annotation
  |     [javac]    @WebMethod int subtract(int x, int 
  | 
  | y);
  |     [javac]     ^
  |     [javac] 
  | 
  | D:\programs\webservices\calculatorwebservice\src\we
  | 
  | bservice1\Calcula
  | torBean.java:6: cannot find symbol
  |     [javac] symbol: class Stateless
  |     [javac] @Stateless
  |     [javac]  ^
  |     [javac] 
  | 
  | D:\programs\webservices\calculatorwebservice\src\we
  | 
  | bservice1\Calcula
  | torBean.java:7: incompatible types
  |     [javac] found   : javax.jws.WebService
  |     [javac] required: 
  | 
  | java.lang.annotation.Annotation
  |     [javac] @WebService(name="Calculator1", 
  | 
  | endpointInterface="webservice1.Calcu
  | lator")
  |     [javac]  ^
  |     [javac] 
  | 
  | D:\programs\webservices\calculatorwebservice\src\we
  | 
  | bservice1\Client.
  | java:17: warning: [deprecation] 
  | 
  | webservice1.Calculator in webservice1 has been d
  | eprecated
  |     [javac]       Calculator calculator = 
  | 
  | (Calculator) service.getPort(Calculato
  | r.class);
  |     [javac]       ^
  |     [javac] 
  | 
  | D:\programs\webservices\calculatorwebservice\src\we
  | 
  | bservice1\Client.
  | java:17: warning: [deprecation] 
  | 
  | webservice1.Calculator in webservice1 has been d
  | eprecated
  |     [javac]       Calculator calculator = 
  | 
  | (Calculator) service.getPort(Calculato
  | r.class);
  |     [javac]                                ^
  |     [javac] 
  | 
  | D:\programs\webservices\calculatorwebservice\src\we
  | 
  | bservice1\Client.
  | java:17: warning: [deprecation] 
  | 
  | webservice1.Calculator in webservice1 has been d
  | eprecated
  |     [javac]       Calculator calculator = 
  | 
  | (Calculator) service.getPort(Calculato
  | r.class);
  |     [javac]                                         
  | 
  |                    ^
  |     [javac] 
  | 
  | D:\programs\webservices\calculatorwebservice\src\we
  | 
  | bservice1\Client.
  | java:18: warning: [deprecation] add(int,int) in 
  | 
  | webservice1.Calculator has been
  | deprecated
  |     [javac]       System.out.println("1 + 1 = " + 
  | 
  | calculator.add(1, 1));
  |     [javac]                                         
  | 
  |         ^
  |     [javac] 
  | 
  | D:\programs\webservices\calculatorwebservice\src\we
  | 
  | bservice1\Client.
  | java:19: warning: [deprecation] subtract(int,int) 
  | 
  | in webservice1.Calculator has
  | been deprecated
  |     [javac]       System.out.println("1 - 1 = " + 
  | 
  | calculator.subtract(1, 1));
  |     [javac]                                         
  | 
  |         ^
  |     [javac] 8 errors
  |     [javac] 5 warnings
  | 
  | BUILD FAILED
  | D:\programs\webservices\calculatorwebservice\build.
  | 
  | xml:47: Compile failed; see t
  | he compiler error output for details.
  | 
  | Total time: 10 seconds
  | 
  | D:\programs\webservices\calculatorwebservice>
  | 

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

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


From do-not-reply at jboss.com  Sun Mar  9 09:35:32 2008
From: do-not-reply at jboss.com (QkI)
Date: Sun, 9 Mar 2008 09:35:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - cannot be cast to
	java.lang.RuntimeException
Message-ID: <26853200.1205069732570.JavaMail.jboss@colo-br-02.atl.jboss.com>

When I try to run my ws client, I get error

  | Exception in thread "main" java.lang.ClassCastException: java.lang.ExceptionInInitializerError cannot be cast to java.lang.RuntimeException
  | 	at com.sun.xml.internal.ws.protocol.soap.client.SOAPMessageDispatcher.doSend(SOAPMessageDispatcher.java:268)
  | 	at com.sun.xml.internal.ws.protocol.soap.client.SOAPMessageDispatcher.send(SOAPMessageDispatcher.java:139)
  | 	at com.sun.xml.internal.ws.encoding.soap.internal.DelegateBase.send(DelegateBase.java:86)
  | 	at com.sun.xml.internal.ws.client.EndpointIFInvocationHandler.implementSEIMethod(EndpointIFInvocationHandler.java:174)
  | 	at com.sun.xml.internal.ws.client.EndpointIFInvocationHandler.invoke(EndpointIFInvocationHandler.java:108)
  | 	at $Proxy16.sayHello(Unknown Source)
  | 	at biz.safo.ws.client.Client.main(Client.java:12)
  | 

this's my ws

  | @Stateless
  | @WebService(name="Hello",
  | 			targetNamespace="http://ws.safo.biz",
  | 			serviceName="HelloService")
  | public class Hello implements HelloRemote {
  | 
  | 	@WebMethod
  | 	public String sayHello(String name) {
  | 		System.out.println("<< sayHello");
  | 		return "Hello, " + name;
  | 	}
  | 
  | }
  | 

and client

  | public class Client {	   
  | 	public static void main(String[] args) {	
  | 		HelloService service = new HelloService();
  | 		Hello hello = service.getHelloPort();
  | 		hello.sayHello("heh");
  | 	}
  | }
  | 

classes Hello and HelloService i generate by wsconsume.
My configuration JBoss 4.2.1, jbossws 2.0.3, jdk6.

Any idea what I'm doing wrong?

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

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


From do-not-reply at jboss.com  Sun Mar  9 14:56:37 2008
From: do-not-reply at jboss.com (Juergen.Zimmermann)
Date: Sun, 9 Mar 2008 14:56:37 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: How to tell which Web Service
	stack(s) are in which Redh
Message-ID: <7497749.1205088997963.JavaMail.jboss@colo-br-02.atl.jboss.com>

JBossTools is based on Eclipse WTP. WTP has a wizard for Axis. That's the simple reason why an Axis wizard is shipped with JBossTools.

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

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


From do-not-reply at jboss.com  Sun Mar  9 19:04:09 2008
From: do-not-reply at jboss.com (anguilla)
Date: Sun, 9 Mar 2008 19:04:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: How to tell which Web Service
	stack(s) are in which Redh
Message-ID: <2857916.1205103849990.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thanks for the helpful replies. It also helped that I finally got the JBossEAP running, and was then able to http://localhost:8080/jbossws. The info that I got via that page, especially the wiki, was quite helpful (although it is hard for me to determine if some of it is out-of-date or not). Thanks, everyone!

p.s. Oh, and I think that perhaps I neglected to pick up JBossTools...

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

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


From do-not-reply at jboss.com  Mon Mar 10 02:44:28 2008
From: do-not-reply at jboss.com (kalparser)
Date: Mon, 10 Mar 2008 02:44:28 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - SOAPElementImpl cast excepion (JBoss
	4.2 + Axis2 + JDK1.6)
Message-ID: <19657298.1205131468058.JavaMail.jboss@colo-br-02.atl.jboss.com>

Need help ugently!
Does anyone have the same problem as below?
 
----------------------------------------------------
14:40:01,221 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
java.lang.ClassCastException: org.apache.axis2.saaj.SOAPElementImpl cannot be cast to org.jboss.ws.core.soap.SOAPElementImpl
	at org.jboss.ws.core.soap.SOAPEnvelopeImpl.(SOAPEnvelopeImpl.java:60)
	at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:124)
	at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:96)
	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:262)
	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:185)
	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:389)
	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272)
	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189)
	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122)
	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.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)

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

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


From do-not-reply at jboss.com  Mon Mar 10 06:27:56 2008
From: do-not-reply at jboss.com (heiko.braun@jboss.com)
Date: Mon, 10 Mar 2008 06:27:56 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: cannot be cast to
	java.lang.RuntimeException
Message-ID: <29033468.1205144876902.JavaMail.jboss@colo-br-02.atl.jboss.com>

Read about JDK 6 installation in the WIKI

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

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


From do-not-reply at jboss.com  Mon Mar 10 07:34:39 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 10 Mar 2008 07:34:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: webservice compiler error
Message-ID: <18921528.1205148879496.JavaMail.jboss@colo-br-02.atl.jboss.com>

The workaround is to copy/paste all jars from .sh scripts to your batch file that are not mentioned there.
Or you can use SVN snapshot or wait for next release scheduled to the end of March where this is already fixed.

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

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


From do-not-reply at jboss.com  Mon Mar 10 07:53:11 2008
From: do-not-reply at jboss.com (QkI)
Date: Mon, 10 Mar 2008 07:53:11 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: cannot be cast to
	java.lang.RuntimeException
Message-ID: <2533486.1205149991057.JavaMail.jboss@colo-br-02.atl.jboss.com>

"heiko.braun at jboss.com" wrote : Read about JDK 6 installation in the WIKI
I was reading about installation on JDK6, but this solution didn't solve my problem. 

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

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


From do-not-reply at jboss.com  Mon Mar 10 11:11:41 2008
From: do-not-reply at jboss.com (kcp)
Date: Mon, 10 Mar 2008 11:11:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBoss 4.0.4GA - Error generating
	Web Service Consumer co
Message-ID: <23673617.1205161901434.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I am notz sur eif you are using the version of JBossWS that ship with JBoss 4.0.4 or if you used an newer one, so I'm just guessing here. In some newer version of JBossWS the attribute that links to the wsdl was not called "file" any more. It's name was changed to "location".

Hope, this helps
Charly

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

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


From do-not-reply at jboss.com  Mon Mar 10 13:33:40 2008
From: do-not-reply at jboss.com (earniedyke)
Date: Mon, 10 Mar 2008 13:33:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Compile errors with wsconsume generated
	source
Message-ID: <9839018.1205170420793.JavaMail.jboss@colo-br-02.atl.jboss.com>

Greetings all,

I am trying to use wsconsume to generate the artifacts for a very simple web service (see wsdl below). Here are the results of executing the command:

C:\JBoss\jboss-4.2.2.GA\bin>wsconsume -k -p org.ebsinc.adalert.ws -o c:\ebs\work
  | spaces\ws-adalert\adalert-service\src -s c:\ebworkspaces\ws-adalert\adalert-serv
  | uces\src http://localhost:81/services/echoService?wsdl
  | parsing WSDL...
  | 
  | 
  | generating code...
  | org\ebsinc\adalert\ws\\Proxy0.java
  | org\ebsinc\adalert\ws\Echo.java
  | org\ebsinc\adalert\ws\EchoResponse.java
  | org\ebsinc\adalert\ws\EchoService.java
  | org\ebsinc\adalert\ws\Log.java
  | org\ebsinc\adalert\ws\LogResponse.java
  | org\ebsinc\adalert\ws\ObjectFactory.java
  | org\ebsinc\adalert\ws\package-info.java
  | c:\ebworkspaces\ws-adalert\adalert-servuces\src\org\ebsinc\adalert\ws\Proxy0.java:2:<identifier>expected package org.ebsinc.adalert.ws.;
  |                               ^
  | c:\ebworkspaces\ws-adalert\adalert-servuces\src\org\ebsinc\adalert\ws\EchoServic
  | e.java:10: malformed floating point literal
  | import org.ebsinc.adalert.ws..Proxy0;
  |                             ^
  | 2 errors
  | compilation failed, errors should have been reported
  | 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:190)
  |         at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:2
  | 16)
  |         at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:79)
  | 

Any ideas why this is happening? I am using JBoss 4.2.2.GA's wsconsume.

Thanks in advance for any and all help.

Earnie!


wsdl:

<?xml version="1.0" encoding="UTF-8"?>
  | <wsdl:definitions targetNamespace="http://simple.components.mule.org" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://simple.components.mule.org" xmlns:intf="http://simple.components.mule.org" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><!--WSDL created by Apache Axis version: 1.4
  | Built on Apr 22, 2006 (06:55:48 PDT)--><wsdl:types><schema elementFormDefault="qualified" targetNamespace="http://simple.components.mule.org" xmlns="http://www.w3.org/2001/XMLSchema"><element name="echo"><complexType><sequence><element name="in0" type="xsd:string"/></sequence></complexType></element><element name="echoResponse"><complexType><sequence><element name="echoReturn" type="xsd:string"/></sequence></complexType></element><element name="log"><complexType><sequence><element name="in0" type="xsd:string"/></sequence></complexType></element><element name="logResponse"><complexType/></element></schema></wsdl:types>
  |   <wsdl:message name="logRequest">
  |     <wsdl:part element="impl:log" name="parameters"/>
  |   </wsdl:message>
  |   <wsdl:message name="echoRequest">
  |     <wsdl:part element="impl:echo" name="parameters"/>
  |   </wsdl:message>
  |   <wsdl:message name="echoResponse">
  |     <wsdl:part element="impl:echoResponse" name="parameters"/>
  | 
  |   </wsdl:message>
  |   <wsdl:message name="logResponse">
  |     <wsdl:part element="impl:logResponse" name="parameters"/>
  |   </wsdl:message>
  |   <wsdl:portType name="$Proxy0">
  |     <wsdl:operation name="echo">
  |       <wsdl:input message="impl:echoRequest" name="echoRequest"/>
  |       <wsdl:output message="impl:echoResponse" name="echoResponse"/>
  |     </wsdl:operation>
  | 
  |     <wsdl:operation name="log">
  |       <wsdl:input message="impl:logRequest" name="logRequest"/>
  |       <wsdl:output message="impl:logResponse" name="logResponse"/>
  |     </wsdl:operation>
  |   </wsdl:portType>
  |   <wsdl:binding name="echoServiceSoapBinding" type="impl:$Proxy0">
  |     <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
  |     <wsdl:operation name="echo">
  |       <wsdlsoap:operation soapAction=""/>
  | 
  |       <wsdl:input name="echoRequest">
  |         <wsdlsoap:body use="literal"/>
  |       </wsdl:input>
  |       <wsdl:output name="echoResponse">
  |         <wsdlsoap:body use="literal"/>
  |       </wsdl:output>
  |     </wsdl:operation>
  |     <wsdl:operation name="log">
  |       <wsdlsoap:operation soapAction=""/>
  | 
  |       <wsdl:input name="logRequest">
  |         <wsdlsoap:body use="literal"/>
  |       </wsdl:input>
  |       <wsdl:output name="logResponse">
  |         <wsdlsoap:body use="literal"/>
  |       </wsdl:output>
  |     </wsdl:operation>
  |   </wsdl:binding>
  |   <wsdl:service name="echoService">
  | 
  |     <wsdl:port binding="impl:echoServiceSoapBinding" name="echoService">
  |       <wsdlsoap:address location="http://localhost:81/services/echoService"/>
  |     </wsdl:port>
  |   </wsdl:service>
  | </wsdl:definitions>

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

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


From do-not-reply at jboss.com  Mon Mar 10 16:50:40 2008
From: do-not-reply at jboss.com (viniciuscarvalho)
Date: Mon, 10 Mar 2008 16:50:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Yet another WS-Security question ...
Message-ID: <20607212.1205182240971.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello there! I'm using JBoss 4.2.1.GA with JBoss WS 

Before one can point, I've already read:

http://jbws.dyndns.org/mediawiki/index.php?title=User_Guide#WS-Security
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=105580&postdays=0&postorder=asc&start=10
http://jbws.dyndns.org/mediawiki/index.php?title=WS-Security_options
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=94406&postdays=0&postorder=asc&start=10

Although those really helped me getting things started, I could not get security running.

I have 2 services that need to have an encryption/sign options. I decided to do this using certificates.

One of the services, is a pure JSR-189 WS:


  | @Stateless(name="CSMQueryService")
  | @WebService(serviceName="CSMQueryService",targetNamespace="http://www.synos.com.br/CSM/definitions")
  | @SOAPBinding(use = SOAPBinding.Use.LITERAL, style = SOAPBinding.Style.DOCUMENT)
  | @WebContext(contextRoot="/csm/services",urlPattern="/CSMQueryService")
  | @EndpointConfig(configName = "Standard WSSecurity Endpoint")
  | @HandlerChain(file="resource://META-INF/ServerHandler.xml")
  | public class CSMQueryServiceImpl implements CSMQueryService
  | 
  | 

The other, is a bit trick since I've implemented the WSDL from a top-down approach, and it was hand created. But, I can't get even this one working :(

I have a jar, with jboss-wsse-server.xml, ServerHandler, csm.keystore, csm.truststore inside its META-INF dir.

During deployment, there's no error, neither warning on the console. But, when I access the service's WSDL I was hoping to find some ws-security related stuff in there, but there was none, this was my first concern.

So I tried to access it using SOAPUI (I'll not try to run tests using jboss ws clients, since this service will be accessed using other languages like .net). Well, I did not set the certificate on SOAPUI on purpose, but I was expecting an error like "Not allowed", instead, a nullpointer was thrown:


  | 2008-03-10 17:34:05,463 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] getHandlerChain: [type=POST,info=[service={http://www.synos.com.br/CSM/definitions}CSMQueryService,port={http://www.synos.com.br/CSM/definitions}CSMQueryServiceImplPort,binding=http://schemas.xmlsoap.org/wsdl/soap/http]]
  | 2008-03-10 17:34:05,464 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler executor: [WSSecurity Handler]
  | 2008-03-10 17:34:05,464 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Enter: handleIn BoundMessage
  | 2008-03-10 17:34:05,470 ERROR [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Exception during handler processing
  | java.lang.NullPointerException
  | 	at org.jboss.ws.extensions.security.Util.matchNode(Util.java:188)
  | 	at org.jboss.ws.extensions.security.Util.matchNode(Util.java:183)
  | 	at org.jboss.ws.extensions.security.Util.findElement(Util.java:89)
  | 	at org.jboss.ws.extensions.security.WSSecurityDispatcher.handleInbound(WSSecurityDispatcher.java:114)
  | 	at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:78)
  | 	at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:41)
  | 	at org.jboss.wsf.spi.jaxws.handler.GenericHandler.handleMessage(GenericHandler.java:55)
  | 	at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:295)
  | 	at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:140)
  | 	at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:87)
  | 	at org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:115)
  | 	at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:159)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:396)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:260)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:177)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:110)
  | 	at org.jboss.wsf.spi.invocation.EndpointServlet.service(EndpointServlet.java:72)
  | 	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:128)
  | 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
  | 	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:241)
  | 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
  | 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
  | 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
  | 	at java.lang.Thread.run(Thread.java:595)
  | 2008-03-10 17:34:05,481 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Exit: handleIn BoundMessage with status: false
  | 2008-03-10 17:34:05,481 DEBUG [org.jboss.ws.core.jaxws.handler.MessageContextJAXWS] Begin response processing
  | 2008-03-10 17:34:05,481 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] popMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at 1e7879f (Thread http-127.0.0.1-8080-1)
  | 2008-03-10 17:34:05,481 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] pushMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at 4fe915 (Thread http-127.0.0.1-8080-1)
  | 2008-03-10 17:34:05,484 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception
  | javax.xml.ws.WebServiceException: java.lang.NullPointerException
  | 	at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.processHandlerFailure(HandlerChainExecutor.java:276)
  | 	at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:155)
  | 	at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:87)
  | 	at org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:115)
  | 	at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:159)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:396)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:260)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:177)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:110)
  | 	at org.jboss.wsf.spi.invocation.EndpointServlet.service(EndpointServlet.java:72)
  | 	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:128)
  | 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
  | 	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:241)
  | 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
  | 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
  | 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
  | 	at java.lang.Thread.run(Thread.java:595)
  | Caused by: java.lang.NullPointerException
  | 	at org.jboss.ws.extensions.security.Util.matchNode(Util.java:188)
  | 	at org.jboss.ws.extensions.security.Util.matchNode(Util.java:183)
  | 	at org.jboss.ws.extensions.security.Util.findElement(Util.java:89)
  | 	at org.jboss.ws.extensions.security.WSSecurityDispatcher.handleInbound(WSSecurityDispatcher.java:114)
  | 	at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:78)
  | 	at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:41)
  | 	at org.jboss.wsf.spi.jaxws.handler.GenericHandler.handleMessage(GenericHandler.java:55)
  | 	at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:295)
  | 	at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:140)
  | 	... 27 more
  | 2008-03-10 17:34:05,503 DEBUG [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] Cannot obtain fault meta data for: class javax.xml.ws.WebServiceException
  | 2008-03-10 17:34:05,503 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] callFaultHandlerChain: PRE
  | 2008-03-10 17:34:05,503 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] callFaultHandlerChain: ENDPOINT
  | 2008-03-10 17:34:05,503 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] callFaultHandlerChain: POST
  | 2008-03-10 17:34:05,503 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Enter: handleOutBoundFault
  | 2008-03-10 17:34:05,503 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Exit: handleOutBoundFault with status: true
  | 

It is my first time using WS-Sec on jbossws. I have used it before on glassfish. And the provider added few stuff on the WSDL to let the client know about the extensions to the WSDL.

I believe that my questions are:

1st: Does jbossws add this meta-data inside the secured service?
2nd: How do I get it running?

Regards[/url]

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

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


From do-not-reply at jboss.com  Tue Mar 11 08:10:54 2008
From: do-not-reply at jboss.com (anil_dongre)
Date: Tue, 11 Mar 2008 08:10:54 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Jboss Juddi configuration
Message-ID: <31299112.1205237454437.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi
I do not know whether this is the right place for my question.
I am new to jboss and Juddi. I tried configuring juddi on JBoss 4.2 GA. My database is MySQL.
I have similarly configured Juddi on tomcat.
I tried a small application to create an organisation using JAXR. This sample works fine with my tomcat installation but when i try it with JBoss it throws a table not found exception for the table Publisher. I guess something is wrong with my configuration of Juddi on JBoss.
Can any help me with this. Can someone tell me exactly how do i configure my datasource. Can someone also tell me how do i test my Juddi configuration like i can in tomcat with happyjuddi.
Thanks in advance

Regards
Anil

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

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


From do-not-reply at jboss.com  Tue Mar 11 12:04:18 2008
From: do-not-reply at jboss.com (MakkaPakka)
Date: Tue, 11 Mar 2008 12:04:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: NullPointerException with jbossws
	2.0.1
Message-ID: <11481401.1205251458581.JavaMail.jboss@colo-br-02.atl.jboss.com>

I've checked out the jira bug 1800 and it appears that this problem is fixed in jbossws 202 onwards.

I've tried both 202 and 203 and they fail to deploy if I include the  -Dcom.sun.management.jmxremote.

Admittedly I am using Java 6 Update4 which I understand is unsupported?

Does anyone have any suggestions?

11-03-08 15:19:19,908 ERROR main [org.jboss.deployment.MainDeployer] Could not start deployment: file:/C:/jboss-4.2.2.GA/server/default/deploy/test.ear/test.jar/
java.lang.NullPointerException
	at org.jboss.wsf.framework.deployment.WebAppGeneratorDeploymentAspect.generatWebDeployment(WebAppGeneratorDeploymentAspect.java:105)
	at org.jboss.wsf.framework.deployment.WebAppGeneratorDeploymentAspect.create(WebAppGeneratorDeploymentAspect.java:84)
	at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
	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(SubDeployerInterceptorSupport.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 $Proxy32.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.GeneratedMethodAccessor28.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	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.GeneratedMethodAccessor5.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	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:597)
	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:597)
	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:619)

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

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


From do-not-reply at jboss.com  Tue Mar 11 12:20:59 2008
From: do-not-reply at jboss.com (MakkaPakka)
Date: Tue, 11 Mar 2008 12:20:59 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: NullPointerException with jbossws
	2.0.1
Message-ID: <3248245.1205252459802.JavaMail.jboss@colo-br-02.atl.jboss.com>

Have some more info about my experiments version 202.


If I add this in to my launch args there is no exception at startup.....


  | -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl
  | -Djboss.platform.mbeanserver
  | -Dcom.sun.management.jmxremote=true
  | -Dcom.sun.management.jmxremote.port=13095 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false

However, upon connecting with jboss - all of the jconsole tabs are disabled. ie Overview, Memory, Threads, Classes, VMSummary are all disabled. Only the MBeans tab is enabled.

If I launch JBoss with these args...


  | -Dcom.sun.management.jmxremote=true
  | -Dcom.sun.management.jmxremote.port=13095 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false


...ie I remove the jboss mbean entries, then I get the exception I posted above.

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

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


From do-not-reply at jboss.com  Tue Mar 11 15:01:16 2008
From: do-not-reply at jboss.com (JGF1)
Date: Tue, 11 Mar 2008 15:01:16 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBoss & JAX-WS. Beginners Guide
Message-ID: <27520821.1205262076667.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi folks.
I've recently been finished reading a book called Beginning Java EE 5 Platform from Novice to Professional.

It contained an example using JAX-WS.

When I tried to locate one of the jars, I couldn't find it:
ie:jbossws.jar. According to book it's in jbossws.sar folder..

Tried compiling code without this but came across two errors based on jars in my classpath:
warning: [path] bad path element "c:\apps\jboss-4.2.2.ga\client\jsr173_1.0_api.jar": no such file or directory
warning: [path] bad path element "c:\apps\jboss-4.2.2.ga\client\jaxb1-impl.jar": no such file or directory

1) Wondered if someone could shed some light on this for me?

(The authors do state the JAX-WS was incomplete at the time the book was being written. I have downloaded jboss-4.2.2ga,
- Says no full implementations of JSR-181 WS meta-data for J EE 5/JAX-WS 2.0 formerly JAX-RPC. Book was published in 2006...)

These are the jars in my classpath:
c:\apps\jboss-4.2.2.ga\server\all\lib\servlet-api.jar;
c:\apps\jboss-4.2.2.ga\server\all\lib\jsp-api.jar;
c:\apps\jboss-4.2.2.ga\server\all\deploy\jbossws.sar\wsdl4j.jar;
c:\apps\jboss-4.2.2.ga\client\jboss-jaxrpc.jar;
c:\apps\jboss-4.2.2.ga\lib\concurrent.jar;
c:\apps\jboss-4.2.2.ga\lib\jboss-common.jar;
c:\apps\jboss-4.2.2.ga\client\jboss-j2ee.jar;
c:\apps\jboss-4.2.2.ga\lib\commons-httpclient.jar;
c:\apps\jboss-4.2.2.ga\client\jbossall-client.jar;
c:\apps\jboss-4.2.2.ga\server\all\lib\jboss.jar;
c:\apps\jboss-4.2.2.ga\server\all\lib\jboss-remoting.jar;
c:\apps\jboss-4.2.2.ga\server\all\lib\jboss-transaction.jar;
c:\apps\jboss-4.2.2.ga\server\all\lib\jnpserver.jar;
c:\apps\jboss-4.2.2.ga\server\all\deploy\ejb3.deployer\jboss-ejb3.jar;
c:\apps\jboss-4.2.2.ga\server\all\lib\jboss-ejb3x.jar;
c:\apps\jboss-4.2.2.ga\server\all\deploy\jboss-aop-jdk50.deployer\jboss-aop-jdk50.jar;
c:\apps\jboss-4.2.2.ga\server\all\deploy\jboss-aop-jdk50.deployer\jboss-aspect-library-jdk50.jar;
c:\apps\jboss-4.2.2.ga\client\jboss-common-client.jar;c:\apps\jboss-4.2.2.ga\client\jbosssx-client.jar;
c:\apps\jboss-4.2.2.ga\server\all\lib\ejb3-persistence.jar;C:\apps\apache-tomcat-6.0.16\lib\jsf-api.jar;

(The ones in bold I have just added. The ejb3 ones are the others they say are required as well as the missing jbossws.jar)


This was the example

  | package webservices;
  | 
  | import java.rmi.Remote;
  | 
  | public interface SimpleService extends Remote
  | {
  | String echo(String input);
  | }
  | 


  | package webservices;
  | 
  | import org.jboss.annotation.ejb.RemoteBinding;
  | import org.jboss.ws.annotation.PortComponent;
  | 
  | import javax.jws.WebMethod;
  | import javax.jws.WebService;
  | import javax.ejb.Remote;
  | import javax.ejb.Stateless;
  | 
  | @WebService(name = "EndpointInterface", targetNamespace = "http://localhost",
  |   serviceName = "SimpleService")
  | @PortComponent(contextRoot="/jbosswsest", urlPattern="/*")
  | @Remote(SimpleService.class)
  | @Stateless
  | public class SimpleServiceImpl implements SimpleService
  | {
  |   @WebMethod
  |   public String echo(String input)
  |   {
  |     return input;
  |   }
  | }
  | 


  | package client;
  | 
  | import webservices.SimpleService;
  | import javax.xml.rpc.ServiceFactory;
  | import javax.xml.rpc.Service;
  | import javax.xml.namespace.QName;
  | import java.net.URL;
  | 
  | public class SimpleServiceClient {
  |   private static final String _namespace = "http://localhost";
  |   private static final String _service = "SimpleService";
  |   private static final String _wsdl = "http://localhost:8080/jbosswstest?wsdl";
  | 
  |   public static void main(String[] args) {
  |     try {
  |       URL defUrl = new URL(_wsdl);
  |       // Create the Service Factory
  |       ServiceFactory serviceFactory = ServiceFactory.newInstance();
  |       // Load the service implementation class
  |       Service remoteService = serviceFactory.createService(defUrl,
  |         new QName(_namespace, _service));
  |       // Load a proxy for our class
  |       SimpleService invoker =
  |         (SimpleService) remoteService.getPort(SimpleService.class);
  |       // Invoke our  interface for each argument
  |       for (int i = 0; i < args.length; i++) {
  |         String returnedString = invoker.echo(args);
  |         System.out.println("sent string: " + args 
  |           + ", received string: " + returnedString);
  |       }
  |     } catch (Exception e) {
  |       e.printStackTrace();
  |     } 
  |  }
  | }
  | 

My compile fails with the following:

  | warning: [path] bad path element "c:\apps\jboss-4.2.2.ga\client\jsr173_1.0_api.jar": no such file or directory
  | warning: [path] bad path element "c:\apps\jboss-4.2.2.ga\client\jaxb1-impl.jar": no such file or directory
  | webservices\SimpleServiceImpl.java:3: package org.jboss.annotation.ejb does not exist
  | import org.jboss.annotation.ejb.RemoteBinding;
  |                                ^
  | webservices\SimpleServiceImpl.java:4: package org.jboss.ws.annotation does not exist
  | import org.jboss.ws.annotation.PortComponent;
  |                               ^
  | webservices\SimpleServiceImpl.java:13: cannot find symbol
  | symbol: class PortComponent
  | @PortComponent(contextRoot="/jbosswsest", urlPattern="/*")
  |  ^
  | 3 errors
  | 2 warnings
  | 


The book says you need the following to run client app:
c:\apps\jboss-4.2.2.ga\client\jboss-jaxrpc.jar;
c:\apps\jboss-4.2.2.ga\client\log4j.jar;
c:\apps\jboss-4.2.2.ga\client\logkit.jar;
c:\apps\jboss-4.2.2.ga\client\jbossws-client.jar;
c:\apps\jboss-4.2.2.ga\client\activation.jar;
c:\apps\jboss-4.2.2.ga\client\jboss-saaj.jar;
c:\apps\jboss-4.2.2.ga\client\mail.jar;
c:\apps\jboss-4.2.2.ga\client\wsdl4j.jar;
c:\apps\jboss-4.2.2.ga\lib\endorsed\xercesImpl.jar;
c:\apps\jboss-4.2.2.ga\client\jbossall-client.jar;
c:\apps\jboss-4.2.2.ga\server\all\lib\jboss-remoting.jar;
c:\apps\jboss-4.2.2.ga\server\all\lib\javax.servlet.jar

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

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


From do-not-reply at jboss.com  Tue Mar 11 15:08:43 2008
From: do-not-reply at jboss.com (JGF1)
Date: Tue, 11 Mar 2008 15:08:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBoss & JAX-WS. Beginners Guide
Message-ID: <22658974.1205262523503.JavaMail.jboss@colo-br-02.atl.jboss.com>

BTW: Should an 'i' enclosed in square brackets [ ] change output to italic when it's embedded in a code block. It's debatable I suppose. But not what I wanted :)

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

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


From do-not-reply at jboss.com  Tue Mar 11 15:42:23 2008
From: do-not-reply at jboss.com (JGF1)
Date: Tue, 11 Mar 2008 15:42:23 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBoss & JAX-WS. Beginners Guide
Message-ID: <13194813.1205264543659.JavaMail.jboss@colo-br-02.atl.jboss.com>

"JGF1" wrote : warning: [path] bad path element "c:\apps\jboss-4.2.2.ga\client\jsr173_1.0_api.jar": no such file or directory
  | warning: [path] bad path element "c:\apps\jboss-4.2.2.ga\client\jaxb1-impl.jar": no such file or directory
  | 
  | 1) Wondered if someone could shed some light on this for me?
  | 

I think I may have tracked this one down.
jaxb-impl.jar has a manifest with the two offenders 
jsr173_1.0_api.jar & jaxb1-impl.jar
This was located in the jbossws.sar folder



I think this got pulled in because of the introduction of jboss-jaxrpc.jar.
It's manifest contains a reference to jaxb-impl.jar..

Perhaps the folks doing the JBoss builds need to be made aware of this...

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

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


From do-not-reply at jboss.com  Tue Mar 11 16:35:44 2008
From: do-not-reply at jboss.com (JGF1)
Date: Tue, 11 Mar 2008 16:35:44 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBoss & JAX-WS. Beginners Guide
Message-ID: <21565879.1205267744792.JavaMail.jboss@colo-br-02.atl.jboss.com>

I noticed in a PDF by Radim Marek over at BSG that @PortComponent is not supported in and @WebContext is now used instead.
Also @WebContext has been moved to org.jboss.wsf.spi.annotation
Is there an online guide for JBoss's implementation of Webservices using JAX-WS that someone can point me too that can give me an introduction and bring things up to date. (or perhaps an up to date book)
I liked the idea of using annotations to code web services in Java in a fashion similar to the example they gave in the book.

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

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


From do-not-reply at jboss.com  Tue Mar 11 17:05:58 2008
From: do-not-reply at jboss.com (mathews567)
Date: Tue, 11 Mar 2008 17:05:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Stateless EJB (EJB 2.1) components to
	webservices
Message-ID: <7765883.1205269558928.JavaMail.jboss@colo-br-02.atl.jboss.com>

I would like to know the best way (axis/jaxrpc) to convert a stateless EJB (EJB 2.1) components to webservices which need to be deployed in JBoss 4.0.5 GA. Our EJBS have java.util.collection classes also as method arguments.

If possible please give us the steps to convert EJB 2.1 into web services.

Thanks in advance.

Mathew


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

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


From do-not-reply at jboss.com  Wed Mar 12 06:49:38 2008
From: do-not-reply at jboss.com (scallens)
Date: Wed, 12 Mar 2008 06:49:38 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBossXSModel goes into endless loop
Message-ID: <11956883.1205318978621.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I am new to JbossWs & JAX-WS.

I created my first Webservice, but when I want to deploy it (now using jboss-4.2.2.GA but I have the same error with other versions) JBossXSModel goes into endless loop :-(

Can anybody help me with this problem?

1. service:

package test.ws;
  | 
  | import javax.jws.WebMethod;
  | import javax.jws.WebService;
  | import javax.jws.soap.SOAPBinding;
  | import javax.jws.soap.SOAPBinding.ParameterStyle;
  | import javax.jws.soap.SOAPBinding.Style;
  | import javax.jws.soap.SOAPBinding.Use;
  | 
  | import test.ws.xhtml.Html;
  | import test.ws.xhtml.ObjectFactory;
  | 
  | @WebService(wsdlLocation="WEB-INF/wsdl/MyService.wsdl")
  | @SOAPBinding(style=Style.DOCUMENT, use=Use.LITERAL, parameterStyle=ParameterStyle.WRAPPED)
  | public class MyService {
  |     
  |     @WebMethod
  |     public Html getHmtl() {
  |         return new ObjectFactory().createHtml();
  |     }     
  | }

2. wsdl-file

<definitions name="MyServiceService" 
  | 	targetNamespace="http://ws.test/" 
  | 	xmlns="http://schemas.xmlsoap.org/wsdl/" 
  | 	xmlns:tns="http://ws.test/"
  | 	xmlns:xhtml="http://www.w3.org/1999/xhtml" 
  | 	xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
  |  	xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
  | 	<types>
  | 		<xsd:import namespace="http://www.w3.org/1999/xhtml" schemaLocation="http://www.w3.org/2002/08/xhtml/xhtml1-strict.xsd"/>
  | 	</types>
  | 	<message name="MyService_getHmtl">
  | 		<part name="getHmtl" element="tns:getHmtl"/>
  | 	</message>
  | 	<message name="MyService_getHmtlResponse">
  | 		<part name="getHmtlResponse" element="tns:getHmtlResponse"/>
  | 	</message>
  | 	<portType name="MyService">
  | 		<operation name="getHmtl" parameterOrder="getHmtl">
  | 			<input message="tns:MyService_getHmtl"/>
  | 			<output message="tns:MyService_getHmtlResponse"/>
  | 		</operation>
  | 	</portType>
  | 	<binding name="MyServiceBinding" type="tns:MyService">
  | 		<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
  | 		<operation name="getHmtl">
  | 			<soap:operation soapAction=""/>
  | 			<input>
  | 				<soap:body use="literal"/>
  | 			</input>
  | 			<output>
  | 				<soap:body use="literal"/>
  | 			</output>
  | 		</operation>
  | 	</binding>
  | 	<service name="MyServiceService">
  | 		<port name="MyServicePort" binding="tns:MyServiceBinding">
  | 			<soap:address location="REPLACE_WITH_ACTUAL_URL"/>
  | 		</port>
  | 	</service>
  | </definitions>

3. logfile

2008-03-12 10:58:38,906 DEBUG [org.jboss.ws.metadata.umdm.UnifiedMetaData] Eagerly initialize the meta data model
  | 2008-03-12 10:58:38,906 DEBUG [org.jboss.ws.metadata.wsdl.xmlschema.JBossXSModel] Registered as anon type: {http://www.w3.org/1999/xhtml:>p} -> Complex type ...

After this, JBossXSModel goes into an endless loop...

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

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


From do-not-reply at jboss.com  Wed Mar 12 13:08:50 2008
From: do-not-reply at jboss.com (squ1rr3l)
Date: Wed, 12 Mar 2008 13:08:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: webservice <transport-guarantee>
	CONFIDENTIAL does not w
Message-ID: <25119992.1205341730934.JavaMail.jboss@colo-br-02.atl.jboss.com>

So am I securing the consoles wrong?  If I add 

  |      <security-constraint>
  |         <user-data-constraint>
  |            <transport-guarantee>CONFIDENTIAL</transport-guarantee>
  |         </user-data-constraint>
  |      </security-constraint>
  | 
to the web.xml files in both /server/prod/deploy/jboss-web.deployer/ROOT.war/WEB-INF and  /server/prod/deploy/jmx-console.war/WEB-INF it seems to have no affect.  I can still connect to both unsecured on port 8080.  https works fine, but I have to specify it, and 8080 is still allowed on both apps.

Is there something else required?


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

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


From do-not-reply at jboss.com  Wed Mar 12 14:57:02 2008
From: do-not-reply at jboss.com (pramod_bs)
Date: Wed, 12 Mar 2008 14:57:02 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Steps for implementing WS-Security in
	JBoss using Username t
Message-ID: <11212604.1205348222305.JavaMail.jboss@colo-br-02.atl.jboss.com>

This posting might be useful for those people trying to implement WS-Security using username toekn authentication. I couldn't find a single document anywhere on the web. I though i will ceate a comrehensive doc.
Please let me know if you guys see any flaw here,


Steps for implementing WS-Security in JBoss using Username token Authentication

I. Server:

1.	Create Endpoint for Web Service (Ex: A stateless session bean)

Code sample: TestWSEJB.java


package test;

import javax.ejb.Stateless;
import javax.jws.WebService;
import javax.jws.WebMethod;
import javax.jws.soap.SOAPBinding;
import org.jboss.annotation.security.SecurityDomain;
import org.jboss.ws.annotation.EndpointConfig;

@Stateless                                                              
@WebService
	    (name="TestWSEJB",
		targetNamespace = "http://test",
		serviceName = "TestWSEJBService")
		@SOAPBinding(style = SOAPBinding.Style.DOCUMENT)
		@EndpointConfig(configName = "Standard WSSecurity Endpoint")
		@SecurityDomain("JBossWS")

public class TestWSEJB {
	@WebMethod
	public String ping (String name)
	{
		return "Hello : " + name;
	}
}


@EndpointConfig(configName = "Standard WSSecurity Endpoint")
           This is the configuration in the {JBOSS_HOME}jboss-4.2.1.GA\server\default\deploy\jbossws.sar\META-INF\standard-jaxws-endpoint-config.xml file

Portion of standard-jaxws-endpoint-config.xml file:

<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>

@SecurityDomain("JBossWS")

This is the configuration for security domain for JBossWS in the {JBOSS_HOME} \jboss-4.2.1.GA\server\default\conf\login-config.xml


Portion of standard-jaxws-endpoint-config.xml file:

    <application-policy name="JBossWS">
      
        <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>
      
    </application-policy>

2.	jboss-wsse-server.xml.
Create jboss-wsse-server.xml and save in META-INF or WEB-INF folder based on the EJB or Web project)

Sample file:

  <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">
	
		
           
		  
	
  </jboss-ws-security>


3.	Authentication information
In the above Security domain (JBossWS) the credentials are in the {JBOSS_HOME} jbossws-user.properties in jboss-4.2.1.GA\server\default\conf\props\jbossws-users.properties. (Default is UsersRolesLoginModule)



II. Client:

1.	Create the client for Web Service.

Sample Code:

Test.java:

package test;
import java.io.File;
import java.net.URL;
import java.util.Map;

import javax.xml.namespace.QName;
import javax.xml.ws.BindingProvider;
import javax.xml.ws.Service;
import javax.xml.ws.WebServiceRef;

import org.jboss.ws.core.StubExt;

public class Test {

	public static void main(String[] args) {
		try {
			Test client = new Test();
			client.doTest(args);
		} catch(Exception e) {
			e.printStackTrace();
		}
	}

	public void doTest(String[] args) {
		try {
			URL url = new URL("http://localhost:8080/WS_Security_Test/TestWSEJB?wsdl");
			QName qn = new QName("http://test","TestWSEJBService");
			Service s = Service.create(url, qn);
			TestWSEJB port = s.getPort(TestWSEJB.class);
			URL securityURL = new File("ejbModule/META-INF/jboss-wsse-client.xml").toURL();
			((StubExt)port).setSecurityConfig(securityURL.toExternalForm());
			((StubExt)port).setConfigName("Standard WSSecurity Client");
			((BindingProvider)port).getRequestContext().put(BindingProvider.USERNAME_PROPERTY, "kermit");;
			((BindingProvider)port).getRequestContext().put(BindingProvider.PASSWORD_PROPERTY, "thefrog");;
			System.out.println("Invoking the sayHello operation    on the port.");
			String response = port.ping("Pramod") ;
			System.out.println(response);
		} catch(Exception e) {
			e.printStackTrace();
		}
	}
}

((StubExt)port).setConfigName("Standard WSSecurity Client");
           This is the configuration in the {JBOSS_HOME}jboss-4.2.1.GA\server\default\deploy\jbossws.sar\META-INF\ standard-jaxws-client-config.xml file
Portion of 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</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>


TestWSEJB.java:

package test;

import javax.jws.WebMethod;
import javax.jws.WebParam;
import javax.jws.WebResult;
import javax.jws.WebService;
import javax.xml.ws.RequestWrapper;
import javax.xml.ws.ResponseWrapper;


/**
 * This class was generated by the JAX-WS RI.
 * JAX-WS RI 2.1.1-b03-
 * Generated source version: 2.0
 * 
 */
@WebService(name = "TestWSEJB", targetNamespace = "http://test")
public interface TestWSEJB {


    /**
     * 
     * @param arg0
     * @return
     *     returns java.lang.String
     */
    @WebMethod
    @WebResult(targetNamespace = "")
    @RequestWrapper(localName = "ping", targetNamespace = "http://test", className = "test.Ping")
    @ResponseWrapper(localName = "pingResponse", targetNamespace = "http://test", className = "test.PingResponse")
    public String ping(
        @WebParam(name = "arg0", targetNamespace = "")
        String arg0);

}


2.	jboss-wsse-client.xml.
Create jboss-wsse-client.xml and save in META-INF or WEB-INF folder based on the EJB or Web project ?????? based on the client)

Sample file:


<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">
	
		
	
</jboss-ws-security>


III. Tools Used:

JBoss Application Server ?????? www.jboss.org
Eclipse IDE ?????? www.eclipse.org
SoapUI for testing Web Services ?????? www.soapui.org
Ws-Consume ??????  Jboss tool (I jboss bin folder)
WireShark (TCP-IP monitoring tool) ?????? http://www.wireshark.org
 
Output from Wireshark (any other TCPIP monitoring tools can be used) -> This is the SOAP-Envelope that actually goes from the client to the server.

<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>
	<env:Header>
		<wsse:Security env:mustUnderstand='1'
			xmlns:wsse='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd'
			xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd'>
			<wsse:UsernameToken
				wsu:Id='token-1-1205175076833-11112467'>
				<wsse:Username>admin</wsse:Username>
				<wsse:Password>admin</wsse:Password>
			</wsse:UsernameToken>
		</wsse:Security>
	</env:Header>
	<env:Body>
		<ns2:ping xmlns:ns2="http://test">
			<arg0>Pramod</arg0>
		</ns2:ping>
	</env:Body>
</env:Envelope>



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

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



From do-not-reply at jboss.com  Wed Mar 12 15:30:27 2008
From: do-not-reply at jboss.com (heiko.braun@jboss.com)
Date: Wed, 12 Mar 2008 15:30:27 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Steps for implementing WS-Security
	in JBoss using Userna
Message-ID: <20121220.1205350227552.JavaMail.jboss@colo-br-02.atl.jboss.com>

Excellent! Would like to contribute it to the tutorial section of the WIKI? 

http://jbws.dyndns.org/mediawiki/index.php?title=Tutorials

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

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


From do-not-reply at jboss.com  Wed Mar 12 16:44:20 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 12 Mar 2008 16:44:20 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Steps for implementing WS-Security
	in JBoss using Userna
Message-ID: <13890998.1205354660055.JavaMail.jboss@colo-br-02.atl.jboss.com>

Yep, this could be a nice tutorial on username tp. A suggestion I can give about this is  to say that the StubExt.PROPERTY_AUTH_TYPE property can be used to set the auth type; for example adding
((BindingProvider)port).getRequestContext().put(StubExt.PROPERTY_AUTH_TYPE, StubExt.PROPERTY_AUTH_TYPE_WSSE);
prevents the client from using the default basic auth (of course the soap header elements are written nevertheless, as you can see).

 Btw pramod_bs, soon I'm going to add some further docs on this topic, since the implementation of digest+nonces support is almost done (JBWS-1988), thus I could link your tutorial if you add it to the wiki.

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

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


From do-not-reply at jboss.com  Wed Mar 12 17:31:49 2008
From: do-not-reply at jboss.com (poornimaanne)
Date: Wed, 12 Mar 2008 17:31:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Turn on clientAuth only on the web
	services
Message-ID: <31628636.1205357509072.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I have an issue which I have been trying to solve with JBoss4.0.4-GA but hadn't any success so far. 

I have my web application myapp.war and web services running in the single JBoss instance. 
1)I would like anyone to be able to access the web application myapp.war using url https://myhost:8443/myapp without any client authentication. 
2)But I would like to put the web services on port 8444 and turn on client Authentication on that port so that people with a valid certificate only can access the web services using URL https://myhost:8444/jbossws/. 

I have added connectors for ports 8443 with clientAuth=false and 8444 with clientAuth=true. Can anyone suggest me how to disable jbossws on port 8443 and how to disable myapp on 8444? Any help would be appreciated.

Thanks,
Poornima

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

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


From do-not-reply at jboss.com  Wed Mar 12 23:02:22 2008
From: do-not-reply at jboss.com (pramod_bs)
Date: Wed, 12 Mar 2008 23:02:22 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Steps for implementing WS-Security
	in JBoss using Userna
Message-ID: <23537240.1205377342343.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thanks for the suggestions. I have a question. I am trying to figure out how to add a password digest to this. Please help

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

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


From do-not-reply at jboss.com  Wed Mar 12 23:07:41 2008
From: do-not-reply at jboss.com (pramod_bs)
Date: Wed, 12 Mar 2008 23:07:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Steps for implementing WS-Security
	in JBoss using Userna
Message-ID: <14876027.1205377661604.JavaMail.jboss@colo-br-02.atl.jboss.com>

"heiko.braun at jboss.com" wrote : Excellent! Would like to contribute it to the tutorial section of the WIKI? 
  | 
  | http://jbws.dyndns.org/mediawiki/index.php?title=Tutorials

I added a link from the Tutorials for this forum item. Is this good enough or is there anyway I can create a Tutorial page?

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

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


From do-not-reply at jboss.com  Thu Mar 13 08:58:32 2008
From: do-not-reply at jboss.com (satyendrakpatel)
Date: Thu, 13 Mar 2008 08:58:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - java.lang.NoClassDefFoundError:
	javax/jws/WebService
Message-ID: <21103908.1205413112335.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi all,

I am trying to run the SSO (Single Sign. On) example which you can find from
http://labs.jboss.com/jbosssso/downloads/ .
I try to deploy and run the example Booking and DVDStore........
But on start of the JBOSS server I get java.lang.NoClassDefFoundError: javax/jws/WebService exception.
..
..
..
17:41:51,157 INFO  [TransactionManagerService] Starting recovery manager
17:41:51,298 INFO  [TransactionManagerService] Recovery manager started
17:41:51,298 INFO  [TransactionManagerService] Binding TransactionManager JNDI Reference
17:41:56,391 INFO  [EJB3Deployer] Starting java:comp multiplexer
17:41:58,532 WARN  [ServiceController] Problem creating service jboss.j2ee:service=EJB3,module=booking-sso.
jar
java.lang.NoClassDefFoundError: javax/jws/WebService
        at org.jboss.ejb3.ProxyFactoryHelper.getEndpointInterface(ProxyFactoryHelper.java:74)
        at org.jboss.ejb3.ProxyFactoryHelper.getLocalInterfaces(ProxyFactoryHelper.java:105)
        at org.jboss.ejb3.ProxyDeployer.initializeLocalBindingMetadata(ProxyDeployer.java:115)
        at org.jboss.ejb3.SessionContainer.instantiated(SessionContainer.java:114)
        at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:492)
        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.ja
va:142)
        at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
        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.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.ja
va: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(AbstractDeploymentSc
anner.java:263)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.ja
va: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.ja
va: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)
17:41:58,798 WARN  [ServiceController] Problem creating service jboss.j2ee:service=EJB3,module=jboss-seam.j
ar
java.lang.NoClassDefFoundError: javax/jws/WebService
        at org.jboss.ejb3.ProxyFactoryHelper.getEndpointInterface(ProxyFactoryHelper.java:74)
        at org.jboss.ejb3.ProxyFactoryHelper.getLocalInterfaces(ProxyFactoryHelper.java:105)
        at org.jboss.ejb3.ProxyDeployer.initializeLocalBindingMetadata(ProxyDeployer.java:115)
        at org.jboss.ejb3.SessionContainer.instantiated(SessionContainer.java:114)
        at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:492)
        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.ja
va:142)
        at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
        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.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.ja
va: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(AbstractDeploymentSc
anner.java:263)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.ja
va: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.ja
va: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)
17:41:59,001 INFO  [EJB3Deployer] Deployed: file:/C:/apps/jboss-4.2.1.GA/server/default/deploy/jboss-sso.sa
r/booking-sso.jar
17:41:59,016 INFO  [EJB3Deployer] Deployed: file:/C:/apps/jboss-4.2.1.GA/server/default/deploy/jboss-sso.sa
r/jboss-seam.jar
:
:
:
I also added the jar jboss-ejb3-all.jar

Thanks 


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

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


From do-not-reply at jboss.com  Thu Mar 13 15:26:13 2008
From: do-not-reply at jboss.com (rodosa)
Date: Thu, 13 Mar 2008 15:26:13 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: NullPointer in JavaToWSDL
	conversion using wstools
Message-ID: <6087796.1205436373343.JavaMail.jboss@colo-br-02.atl.jboss.com>

I've a similar problem ... how did you solucionate it?

Thanks

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

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


From do-not-reply at jboss.com  Thu Mar 13 15:36:01 2008
From: do-not-reply at jboss.com (rphadnis)
Date: Thu, 13 Mar 2008 15:36:01 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: setting context root for EJB based
	web services
Message-ID: <16319295.1205436961037.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am assuming you are using JBoss 4.2.2 or atleast JBossWS 2.0.1. If that is true you can set the context root using the following annotation:

import org.jboss.wsf.spi.annotation.WebContext;
.....
@WebContext(contextRoot="/YourContextRoot")


The WebContext class is in the jbossws-spi.jar in the client folder of your jboss 4.2.2 installation.

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

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


From do-not-reply at jboss.com  Thu Mar 13 15:37:43 2008
From: do-not-reply at jboss.com (rphadnis)
Date: Thu, 13 Mar 2008 15:37:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: how to change the context path
Message-ID: <33020529.1205437063628.JavaMail.jboss@colo-br-02.atl.jboss.com>

Check if this is helpful

http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136442#4136442

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

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


From do-not-reply at jboss.com  Thu Mar 13 16:53:10 2008
From: do-not-reply at jboss.com (trouby)
Date: Thu, 13 Mar 2008 16:53:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - communicating with WS in c# thorugh
	Java - encoding problem
Message-ID: <11926676.1205441590865.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hey,

I have a simple .NET ws based on WCF technology with some simple method which expect an object that has few string properties,


I have created the relevant artifacts with wsimport and everything works as expected,

The string property is encoded with UTF-8, for some reason, on the .NET ws side the strings are not getting decoded correctly. when I dump the strings I see gibberish,

I'm not sure why but I was expecting a UTF-8 content on the WS side,


The method calls to the WS are being invoked through Jboss EJB using the WS 2.0.3 package,


Many thanks,

Asaf.

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

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


From do-not-reply at jboss.com  Thu Mar 13 18:33:45 2008
From: do-not-reply at jboss.com (adesai@atech.com)
Date: Thu, 13 Mar 2008 18:33:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Error while starting server -
	SearchPortTypePort does not co
Message-ID: <24986099.1205447625834.JavaMail.jboss@colo-br-02.atl.jboss.com>

hi there,

I'm using JBoss Portal Server 2.6.4 (bundled with App server). I've a written a client to access WSDL. There is no compilation error. however; when i try to restart the portal server, getting following error message. Can somebody let me know what's going wrong? thanks for your help.



  |   faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client
  |  faultSubcode: 
  |  faultString: Endpoint {http://www.<companyname>.com/km/search}SearchPortTypePort does not contain operation meta data for: {http://www.<companyname>.com/product/simple/search}searchContent
  |  faultActor: 
  |  faultNode: 
  |  faultDetail: 
  | 	{http://xml.apache.org/axis/}stackTrace:Endpoint {http://www.<companyname>.com/km/search}SearchPortTypePort does not contain operation meta data for: {http://www.<companyname>.com/product/simple/search}searchContent
  | 	at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
  | 	at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
  | 	at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
  | 	at org.apache.xerces.parsers.AbstractSAXParser.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 javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
  | 	at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
  | 	at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
  | 	at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
  | 	at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
  | 	at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
  | 	at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
  | 	at org.apache.axis.client.Call.invoke(Call.java:2767)
  | 	at org.apache.axis.client.Call.invoke(Call.java:2443)
  | 	at org.apache.axis.client.Call.invoke(Call.java:2366)
  | 	at org.apache.axis.client.Call.invoke(Call.java:1812)
  | 	at com.<companyname>.www.product.simple.search.SearchPortTypeBindingStub.searchContent(Unknown Source)
  | 	at com.<companyname>.search.service.client.SearchServiceClient.callWSDL(Unknown Source)
  | 	at org.jboss.portlet.hello.bean.CallWSDL.callWSDL(Unknown Source)
  | 	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.apache.el.parser.AstValue.invoke(AstValue.java:131)
  | 	at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276)
  | 	at org.apache.jasper.el.JspMethodExpression.invoke(JspMethodExpression.java:68)
  | 	at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:77)
  | 	at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:91)
  | 	at javax.faces.component.UICommand.broadcast(UICommand.java:383)
  | 	at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:447)
  | 	at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:752)
  | 	at com.sun.faces.portlet.LifecycleImpl$InvokeApplicationPhase.execute(LifecycleImpl.java:658)
  | 	at com.sun.faces.portlet.LifecycleImpl.phase(LifecycleImpl.java:329)
  | 	at com.sun.faces.portlet.LifecycleImpl.execute(LifecycleImpl.java:245)
  | 	at com.sun.faces.portlet.FacesPortlet.processAction(FacesPortlet.java:220)
  | 	at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl.invokeAction(PortletContainerImpl.java:458)
  | 	at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl.dispatch(PortletContainerImpl.java:401)
  | 	at org.jboss.portal.portlet.container.PortletContainerInvoker$1.invoke(PortletContainerInvoker.java:86)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131)
  | 	at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.org$jboss$portal$core$aspects$portlet$TransactionInterceptor$invokeNotSupported$aop(TransactionInterceptor.java:86)
  | 	at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeNotSupported_N4547270787964792031.invokeNext(TransactionInterceptor$invokeNotSupported_N4547270787964792031.java)
  | 	at org.jboss.aspects.tx.TxPolicy.invokeInNoTx(TxPolicy.java:66)
  | 	at org.jboss.aspects.tx.TxInterceptor$NotSupported.invoke(TxInterceptor.java:112)
  | 	at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeNotSupported_N4547270787964792031.invokeNext(TransactionInterceptor$invokeNotSupported_N4547270787964792031.java)
  | 	at org.jboss.aspects.tx.TxPolicy.invokeInNoTx(TxPolicy.java:66)
  | 	at org.jboss.aspects.tx.TxInterceptor$NotSupported.invoke(TxInterceptor.java:102)
  | 	at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeNotSupported_N4547270787964792031.invokeNext(TransactionInterceptor$invokeNotSupported_N4547270787964792031.java)
  | 	at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.invokeNotSupported(TransactionInterceptor.java)
  | 	at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.invoke(TransactionInterceptor.java:56)
  | 	at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.core.aspects.portlet.HeaderInterceptor.invoke(HeaderInterceptor.java:50)
  | 	at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.portlet.aspects.portlet.ProducerCacheInterceptor.invoke(ProducerCacheInterceptor.java:53)
  | 	at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.core.aspects.portlet.AjaxInterceptor.invoke(AjaxInterceptor.java:51)
  | 	at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.portlet.aspects.portlet.ModesInterceptor.invoke(ModesInterceptor.java:62)
  | 	at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.portlet.bridge.BridgeInterceptor.invoke(BridgeInterceptor.java:47)
  | 	at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.portlet.aspects.portlet.WindowStatesInterceptor.invoke(WindowStatesInterceptor.java:55)
  | 	at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.portlet.aspects.portlet.PortletSessionSynchronizationInterceptor.invoke(PortletSessionSynchronizationInterceptor.java:80)
  | 	at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.portlet.aspects.portlet.ContextTrackerInterceptor.invoke(ContextTrackerInterceptor.java:46)
  | 	at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.portlet.aspects.portlet.ContextDispatcherInterceptor$1.doCallback(ContextDispatcherInterceptor.java:104)
  | 	at org.jboss.portal.web.command.CommandDispatcher$CallbackCommand.execute(CommandDispatcher.java:74)
  | 	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.portal.web.command.CommandServlet.doGet(CommandServlet.java:131)
  | 	at org.jboss.portal.web.command.CommandServlet.doPost(CommandServlet.java:162)
  | 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
  | 	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.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654)
  | 	at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557)
  | 	at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481)
  | 	at org.jboss.portal.web.command.CommandServlet.include(CommandServlet.java:80)
  | 	at org.jboss.portal.web.command.CommandDispatcher.include(CommandDispatcher.java:50)
  | 	at org.jboss.portal.web.jboss.JBossWebContext.include(JBossWebContext.java:66)
  | 	at org.jboss.portal.web.ServletContainer.include(ServletContainer.java:182)
  | 	at org.jboss.portal.portlet.impl.spi.AbstractRequestContext.dispatch(AbstractRequestContext.java:81)
  | 	at org.jboss.portal.portlet.aspects.portlet.ContextDispatcherInterceptor.invoke(ContextDispatcherInterceptor.java:76)
  | 	at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.portlet.aspects.portlet.SecureTransportInterceptor.invoke(SecureTransportInterceptor.java:68)
  | 	at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.portlet.aspects.portlet.ValveInterceptor.invoke(ValveInterceptor.java:60)
  | 	at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:157)
  | 	at org.jboss.portal.portlet.container.PortletContainerInvoker.invoke(PortletContainerInvoker.java:198)
  | 	at org.jboss.portal.portlet.state.producer.ProducerPortletInvoker.invoke(ProducerPortletInvoker.java:233)
  | 	at org.jboss.portal.core.impl.portlet.state.ProducerPortletInvoker.org$jboss$portal$core$impl$portlet$state$ProducerPortletInvoker$invoke$aop(ProducerPortletInvoker.java:53)
  | 	at org.jboss.portal.core.impl.portlet.state.ProducerPortletInvoker$invoke_N8654503705355129869.invokeNext(ProducerPortletInvoker$invoke_N8654503705355129869.java)
  | 	at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126)
  | 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
  | 	at org.jboss.portal.core.impl.portlet.state.ProducerPortletInvoker$invoke_N8654503705355129869.invokeNext(ProducerPortletInvoker$invoke_N8654503705355129869.java)
  | 	at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126)
  | 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
  | 	at org.jboss.portal.core.impl.portlet.state.ProducerPortletInvoker$invoke_N8654503705355129869.invokeNext(ProducerPortletInvoker$invoke_N8654503705355129869.java)
  | 	at org.jboss.portal.core.impl.portlet.state.ProducerPortletInvoker.invoke(ProducerPortletInvoker.java)
  | 	at org.jboss.portal.portlet.federation.impl.FederatedPortletInvokerService.invoke(FederatedPortletInvokerService.java:147)
  | 	at org.jboss.portal.portlet.federation.impl.FederatingPortletInvokerService.invoke(FederatingPortletInvokerService.java:150)
  | 	at org.jboss.portal.core.impl.model.instance.InstanceContainerImpl$1.invoke(InstanceContainerImpl.java:99)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131)
  | 	at org.jboss.portal.portlet.management.PortletContainerManagementInterceptorImpl.invoke(PortletContainerManagementInterceptorImpl.java:58)
  | 	at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.portlet.aspects.portlet.PortalSessionSynchronizationInterceptor.invoke(PortalSessionSynchronizationInterceptor.java:116)
  | 	at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.core.model.instance.InstanceSecurityInterceptor.invoke(InstanceSecurityInterceptor.java:91)
  | 	at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.portlet.aspects.portlet.ConsumerCacheInterceptor.invoke(ConsumerCacheInterceptor.java:175)
  | 	at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:157)
  | 	at org.jboss.portal.core.impl.model.instance.InstanceContainerImpl.org$jboss$portal$core$impl$model$instance$InstanceContainerImpl$invoke$aop(InstanceContainerImpl.java:427)
  | 	at org.jboss.portal.core.impl.model.instance.InstanceContainerImpl$invoke_N8654503705355129869.invokeNext(InstanceContainerImpl$invoke_N8654503705355129869.java)
  | 	at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126)
  | 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
  | 	at org.jboss.portal.core.impl.model.instance.InstanceContainerImpl$invoke_N8654503705355129869.invokeNext(InstanceContainerImpl$invoke_N8654503705355129869.java)
  | 	at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126)
  | 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
  | 	at org.jboss.portal.core.impl.model.instance.InstanceContainerImpl$invoke_N8654503705355129869.invokeNext(InstanceContainerImpl$invoke_N8654503705355129869.java)
  | 	at org.jboss.portal.core.impl.model.instance.InstanceContainerImpl.invoke(InstanceContainerImpl.java)
  | 	at org.jboss.portal.core.impl.model.instance.AbstractInstance.invoke(AbstractInstance.java:231)
  | 	at org.jboss.portal.core.model.portal.command.action.InvokePortletWindowActionCommand.execute(InvokePortletWindowActionCommand.java:174)
  | 	at org.jboss.portal.core.controller.ControllerCommand$1.invoke(ControllerCommand.java:68)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131)
  | 	at org.jboss.portal.core.aspects.controller.node.EventBroadcasterInterceptor.invoke(EventBroadcasterInterceptor.java:123)
  | 	at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.core.aspects.controller.ControlInterceptor.invoke(ControlInterceptor.java:56)
  | 	at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.core.aspects.controller.PageCustomizerInterceptor.invoke(PageCustomizerInterceptor.java:133)
  | 	at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.core.aspects.controller.PolicyEnforcementInterceptor.invoke(PolicyEnforcementInterceptor.java:78)
  | 	at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.core.aspects.controller.node.PortalNodeInterceptor.invoke(PortalNodeInterceptor.java:81)
  | 	at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.core.aspects.controller.NavigationalStateInterceptor.invoke(NavigationalStateInterceptor.java:42)
  | 	at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.core.controller.ajax.AjaxInterceptor.invoke(AjaxInterceptor.java:56)
  | 	at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.core.aspects.controller.ResourceAcquisitionInterceptor.invoke(ResourceAcquisitionInterceptor.java:50)
  | 	at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:157)
  | 	at org.jboss.portal.core.controller.ControllerContext.execute(ControllerContext.java:134)
  | 	at org.jboss.portal.core.controller.Controller.processCommand(Controller.java:235)
  | 	at org.jboss.portal.core.controller.Controller.handle(Controller.java:217)
  | 	at org.jboss.portal.server.RequestControllerDispatcher.invoke(RequestControllerDispatcher.java:51)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131)
  | 	at org.jboss.portal.core.cms.aspect.IdentityBindingInterceptor.invoke(IdentityBindingInterceptor.java:47)
  | 	at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.server.aspects.server.ContentTypeInterceptor.invoke(ContentTypeInterceptor.java:68)
  | 	at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.core.aspects.server.PortalContextPathInterceptor.invoke(PortalContextPathInterceptor.java:45)
  | 	at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.core.aspects.server.LocaleInterceptor.invoke(LocaleInterceptor.java:96)
  | 	at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.core.aspects.server.UserInterceptor.invoke(UserInterceptor.java:246)
  | 	at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.server.aspects.server.SignOutInterceptor.invoke(SignOutInterceptor.java:98)
  | 	at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.core.impl.api.user.UserEventBridgeTriggerInterceptor.invoke(UserEventBridgeTriggerInterceptor.java:65)
  | 	at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.core.aspects.server.TransactionInterceptor.org$jboss$portal$core$aspects$server$TransactionInterceptor$invoke$aop(TransactionInterceptor.java:49)
  | 	at org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java)
  | 	at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
  | 	at org.jboss.aspects.tx.TxInterceptor$RequiresNew.invoke(TxInterceptor.java:253)
  | 	at org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java)
  | 	at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
  | 	at org.jboss.aspects.tx.TxInterceptor$RequiresNew.invoke(TxInterceptor.java:262)
  | 	at org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java)
  | 	at org.jboss.portal.core.aspects.server.TransactionInterceptor.invoke(TransactionInterceptor.java)
  | 	at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.server.aspects.LockInterceptor$InternalLock.invoke(LockInterceptor.java:69)
  | 	at org.jboss.portal.server.aspects.LockInterceptor.invoke(LockInterceptor.java:130)
  | 	at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	at org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:157)
  | 	at org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:250)
  | 	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.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
  | 	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:595)
  | 
  | 	{http://xml.apache.org/axis/}hostname:

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

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


From do-not-reply at jboss.com  Fri Mar 14 04:20:24 2008
From: do-not-reply at jboss.com (thomas.diesler@jboss.com)
Date: Fri, 14 Mar 2008 04:20:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Error while starting server -
	SearchPortTypePort does no
Message-ID: <7692688.1205482824322.JavaMail.jboss@colo-br-02.atl.jboss.com>


  | 	at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
  | 	at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
  | 	at org.apache.axis.client.Call.invoke(Call.java:2767)
  | 

How does Axis come into the game?

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

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


From do-not-reply at jboss.com  Fri Mar 14 04:26:45 2008
From: do-not-reply at jboss.com (thomas.diesler@jboss.com)
Date: Fri, 14 Mar 2008 04:26:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: communicating with WS in c# thorugh
	Java - encoding prob
Message-ID: <11089926.1205483206007.JavaMail.jboss@colo-br-02.atl.jboss.com>

javax.xml.soap.SOAPMessage


  |    /** Specifies the character type encoding for the SOAP Message. Valid values include "utf-8" and "utf-16". The default is "utf-8". */
  |    public static final String CHARACTER_SET_ENCODING = "javax.xml.soap.character-set-encoding";
  | 

The soap message can either be UTF-8 or UTF-16 encoded

We regularly attend the MSFT .NET interop workshop and don't see that issue there

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

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


From do-not-reply at jboss.com  Fri Mar 14 04:30:39 2008
From: do-not-reply at jboss.com (thomas.diesler@jboss.com)
Date: Fri, 14 Mar 2008 04:30:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: java.lang.NoClassDefFoundError:
	javax/jws/WebService
Message-ID: <4289994.1205483439869.JavaMail.jboss@colo-br-02.atl.jboss.com>

Is jbossws deployed?

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

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


From do-not-reply at jboss.com  Fri Mar 14 04:29:50 2008
From: do-not-reply at jboss.com (thomas.diesler@jboss.com)
Date: Fri, 14 Mar 2008 04:29:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: NullPointer in JavaToWSDL
	conversion using wstools
Message-ID: <8004402.1205483390677.JavaMail.jboss@colo-br-02.atl.jboss.com>

Wy are you not moving to jboss-4.2.x and use jax-ws?

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

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


From do-not-reply at jboss.com  Fri Mar 14 04:34:16 2008
From: do-not-reply at jboss.com (thomas.diesler@jboss.com)
Date: Fri, 14 Mar 2008 04:34:16 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Turn on clientAuth only on the web
	services
Message-ID: <20002717.1205483656490.JavaMail.jboss@colo-br-02.atl.jboss.com>

This is a general tomcat issue. Security is configured per endpoint. i.e. you should configure client authentication for every deployed endpoint

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

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


From do-not-reply at jboss.com  Fri Mar 14 05:36:40 2008
From: do-not-reply at jboss.com (satyendrakpatel)
Date: Fri, 14 Mar 2008 05:36:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: java.lang.NoClassDefFoundError:
	javax/jws/WebService
Message-ID: <11124698.1205487400659.JavaMail.jboss@colo-br-02.atl.jboss.com>

yes Jbossws is already deployed there........
Is any  thing else required for this?


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

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


From do-not-reply at jboss.com  Fri Mar 14 06:15:21 2008
From: do-not-reply at jboss.com (trouby)
Date: Fri, 14 Mar 2008 06:15:21 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: communicating with WS in c# thorugh
	Java - encoding prob
Message-ID: <32254877.1205489721310.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hey,

Well, something is wrong,
I have a file saved as unicode, I read the content of the file into a java String variable and pass it to the WS,

I see gibberish on the other side (C#), 


Is there any way to investigate it? are there any WS testcases in C#/.NET and WS client code in java so I can take a look and see what's wrong ?


I have an assumption that the content gets encoded more than once on the way for some reason,


Many thanks,

Asaf.

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

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


From do-not-reply at jboss.com  Fri Mar 14 07:39:30 2008
From: do-not-reply at jboss.com (rashmi_yes)
Date: Fri, 14 Mar 2008 07:39:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Single API called twice after certain
	time
Message-ID: <7589951.1205494770149.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,
My Client is calling an web service API in remote machine. This API will take around 7 minutes to execute. But before completing the execution, the same API is called again after 5 minutes. But actually, the client is not calling the same API again. It had been called automatically.

When the first call completes execution, it is trying to return the result but throwing the below error & the value is not returned. But the second call(which was called automatically) completes & returns successfully.

Could anybody help me on this problem

thrown error in first call:

java.io.IOException: stream is closed
        at sun.net.httpserver.Request$WriteStream.write(Request.java:378)
        at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65
)
        at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
        at sun.net.httpserver.ExchangeImpl.sendResponseHeaders(ExchangeImpl.java
:192)
        at sun.net.httpserver.HttpExchangeImpl.sendResponseHeaders(HttpExchangeI
mpl.java:68)
        at com.sun.xml.internal.ws.transport.http.server.ServerConnectionImpl.ge
tOutput(ServerConnectionImpl.java:116)
        at com.sun.xml.internal.ws.util.SOAPConnectionUtil.send(SOAPConnectionUt
il.java:106)
        at com.sun.xml.internal.ws.util.SOAPConnectionUtil.sendResponse(SOAPConn
ectionUtil.java:115)
        at com.sun.xml.internal.ws.protocol.soap.server.SOAPMessageDispatcher.se
ndResponse(SOAPMessageDispatcher.java:382)
        at com.sun.xml.internal.ws.protocol.soap.server.SOAPMessageDispatcher.re
ceive(SOAPMessageDispatcher.java:159)
        at com.sun.xml.internal.ws.server.Tie.handle(Tie.java:90)
        at com.sun.xml.internal.ws.transport.http.server.WSHttpHandler.process(W
SHttpHandler.java:173)
        at com.sun.xml.internal.ws.transport.http.server.WSHttpHandler.handleExc
hange(WSHttpHandler.java:121)
        at com.sun.xml.internal.ws.transport.http.server.WSHttpHandler.handle(WS
HttpHandler.java:97)
        at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:65)
        at sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:65)
        at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:68)
        at sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.
java:556)
        at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:65)
        at sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:528)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:885)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:907)
        at java.lang.Thread.run(Thread.java:619)
javax.xml.ws.WebServiceException: java.lang.NullPointerException
        at com.sun.xml.internal.ws.util.SOAPConnectionUtil.send(SOAPConnectionUt
il.java:109)
        at com.sun.xml.internal.ws.util.SOAPConnectionUtil.sendResponse(SOAPConn
ectionUtil.java:115)
        at com.sun.xml.internal.ws.protocol.soap.server.SOAPMessageDispatcher.se
ndResponse(SOAPMessageDispatcher.java:382)
        at com.sun.xml.internal.ws.protocol.soap.server.SOAPMessageDispatcher.re
ceive(SOAPMessageDispatcher.java:159)
        at com.sun.xml.internal.ws.server.Tie.handle(Tie.java:90)
        at com.sun.xml.internal.ws.transport.http.server.WSHttpHandler.process(W
SHttpHandler.java:173)
        at com.sun.xml.internal.ws.transport.http.server.WSHttpHandler.handleExc
hange(WSHttpHandler.java:121)
        at com.sun.xml.internal.ws.transport.http.server.WSHttpHandler.handle(WS
HttpHandler.java:97)
        at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:65)
        at sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:65)
        at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:68)
        at sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.
java:556)
        at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:65)
        at sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:528)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:885)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:907)
        at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.NullPointerException
        at com.sun.xml.internal.messaging.saaj.soap.MessageImpl.writeTo(MessageI
mpl.java:1219)
        at com.sun.xml.internal.ws.util.SOAPConnectionUtil.send(SOAPConnectionUt
il.java:106)
        ... 16 more
Mar 13, 2008 6:41:14 PM com.sun.xml.internal.ws.protocol.soap.server.SOAPMessage
Dispatcher receive
SEVERE: java.lang.NullPointerException
javax.xml.ws.WebServiceException: java.lang.NullPointerException
        at com.sun.xml.internal.ws.util.SOAPConnectionUtil.send(SOAPConnectionUt
il.java:109)
        at com.sun.xml.internal.ws.util.SOAPConnectionUtil.sendResponse(SOAPConn
ectionUtil.java:115)
        at com.sun.xml.internal.ws.protocol.soap.server.SOAPMessageDispatcher.se
ndResponse(SOAPMessageDispatcher.java:382)
        at com.sun.xml.internal.ws.protocol.soap.server.SOAPMessageDispatcher.re
ceive(SOAPMessageDispatcher.java:159)
        at com.sun.xml.internal.ws.server.Tie.handle(Tie.java:90)
        at com.sun.xml.internal.ws.transport.http.server.WSHttpHandler.process(W
SHttpHandler.java:173)
        at com.sun.xml.internal.ws.transport.http.server.WSHttpHandler.handleExc
hange(WSHttpHandler.java:121)
        at com.sun.xml.internal.ws.transport.http.server.WSHttpHandler.handle(WS
HttpHandler.java:97)
        at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:65)
        at sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:65)
        at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:68)
        at sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.
java:556)
        at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:65)
        at sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:528)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:885)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:907)
        at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.NullPointerException
        at com.sun.xml.internal.messaging.saaj.soap.MessageImpl.writeTo(MessageI
mpl.java:1219)
        at com.sun.xml.internal.ws.util.SOAPConnectionUtil.send(SOAPConnectionUt
il.java:106)
        ... 16 more


Thanks,
Rashmi

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

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


From do-not-reply at jboss.com  Fri Mar 14 08:34:30 2008
From: do-not-reply at jboss.com (mimra)
Date: Fri, 14 Mar 2008 08:34:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Message faults not signed
Message-ID: <14811907.1205498070198.JavaMail.jboss@colo-br-02.atl.jboss.com>

We have a project running on JBoss 4.2.0 (JBossWS 1.2.1.GA) which exposes an EJB3 web service like:


  | @Stateless
  | @WebService(wsdlLocation="META-INF/wsdl/LovWS.wsdl", targetNamespace = "http://rep.oio.dk/wmdata.dk/as2007/schemas/2006/11/20/")
  | @SOAPBinding(style = SOAPBinding.Style.DOCUMENT)
  | @HandlerChain(file = "resource://META-INF/ServerHandlers.xml", name = "SecureHandlerChain")
  | @WebContext(contextRoot="/as2007/facade")
  | public class LovWS extends WSBean {
  | .
  | .
  | .
  | 	@WebMethod()	
  | 	@WebResult(name="resultat")
  | 	public LovType hentLov(@WebParam(name="Kode") String kode) throws WSException{
  | 		if ("".equals(kode)){
  | 			throw new WSException(165,"Kode argumentet er tomt");
  | 		}		
  | 	.
  | 	.
  | 	.
  | 	}
  | }
  | 

Now if the request to the web service is successful, the response is singed as expected.
However, if any exception is thrown and a SOAP fault is returned, then the SOAP body is not signed.

Is this expected behavior?  Is there any way to get JBossWS to also sign the SOAP faults?

Best regards
Michael

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

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


From do-not-reply at jboss.com  Fri Mar 14 10:40:51 2008
From: do-not-reply at jboss.com (rodosa)
Date: Fri, 14 Mar 2008 10:40:51 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Call a web service
Message-ID: <18048504.1205505651522.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello!

         I'm new in JbossWS. I have been looking into the documentation but... I'm a bit lost. I've generated a web service that I can see at http://localhost:8080/jbossws/services. My problem is how I can access form a client application ... and if I have to produce something with wstools.

I notice that wsdl file is automaticaly created in data folder of Jboss 4.2.2. But what happens with wsconsume tools? I've executed and this created me several files. I have to use them to call my web service? or ... I have to do something similar to 


  |  String urlstr   = "http://127.0.0.1:8080/proyecto/JbpmService?wsdl";
  | 
  |  URL url =  new URL(urlstr);
  | 
  | 	        QName qname = new QName("http://ws/",
  | 	                                "JbpmService");
  | 
  | 	        
  | 	        ServiceFactory factory = ServiceFactory.newInstance();
  | 	        Service        service = factory.createService(url, qname);
  | 
  | 

This second option doesn't works for me because the following exception is thrown:

  | Exception in thread "main" java.lang.IllegalArgumentException: Cannot obtain wsdl service: {http://ws/}JbpmService
  | 	at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCClientMetaDataBuilder.buildMetaDataInternal(JAXRPCClientMetaDataBuilder.java:172)
  | 	at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCClientMetaDataBuilder.buildMetaData(JAXRPCClientMetaDataBuilder.java:134)
  | 	at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCClientMetaDataBuilder.buildMetaData(JAXRPCClientMetaDataBuilder.java:86)
  | 	at org.jboss.ws.core.jaxrpc.client.ServiceImpl.<init>(ServiceImpl.java:111)
  | 	at org.jboss.ws.core.jaxrpc.client.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:157)
  | 	at org.jboss.ws.core.jaxrpc.client.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:128)
  | 	at client.JbpmWSClient.main(JbpmWSClient.java:61)
  | 

how I could solucionate this problem?

Thanks

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

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


From do-not-reply at jboss.com  Fri Mar 14 12:07:42 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 14 Mar 2008 12:07:42 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Call a web service
Message-ID: <16067720.1205510862404.JavaMail.jboss@colo-br-02.atl.jboss.com>

Yes, you use the files generated by wsconsume in your client. As an example, say you have a hello web service (I am not sowing all the code):

class Hello {
  |   public String sayHello(String name) {...}
  | }

wsconsume will create an interface named Hello and a class named HelloService (and possibly other classes). The code for the client is:

public class Client {
  |   public static void main(String[] args) {
  |     HelloService svc = new HelloService();
  |     Hello hello = svc.getHelloPort();
  |     System.out.println(hello.sayHello(args[0]));
  |   }
  | }

Compile the client with the classes generated by wsconsume, and package the client and the wsconsume classes info a jar file. Then use wsrunclient to run it:

wsrunclient -classpath client.jar Hello me


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

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


From do-not-reply at jboss.com  Fri Mar 14 12:51:56 2008
From: do-not-reply at jboss.com (adesai@atech.com)
Date: Fri, 14 Mar 2008 12:51:56 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Error while starting server -
	SearchPortTypePort does no
Message-ID: <7806957.1205513516346.JavaMail.jboss@colo-br-02.atl.jboss.com>

Sorry Thomos, my bad, terrible mistake. 

Can you please let me know what all Jars i'll need to include in the lib to make my client work?

/amol

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

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


From do-not-reply at jboss.com  Fri Mar 14 13:06:42 2008
From: do-not-reply at jboss.com (j0llyr0g3r)
Date: Fri, 14 Mar 2008 13:06:42 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Jboss support for Webservices over REST?
Message-ID: <6258495.1205514402898.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hey folks, 

i know this question calls for a response like:

- "use the forum search!"
- "Just f****ng google it!"
- RTFM

But as a matter of fact, i did all of that without any results.

So, in a nutshell:

Does Jboss offer any functionalities to deal with Webservices over REST?

For example URL-parsing, parameter validation etc....

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

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


From do-not-reply at jboss.com  Fri Mar 14 13:40:01 2008
From: do-not-reply at jboss.com (Intecdom)
Date: Fri, 14 Mar 2008 13:40:01 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - I can't create .SAR from eclipse
Message-ID: <7069176.1205516401938.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello everyone,

Fist of all, I'm quite new with eclipse and JBoss, and I've tried reading all the information I've found about them before asking you... But I've not succeed in the next problem. If any of you can help me, I'd be deeply thankfull...

I'm developing a web application with eclipse-JBoss.

I've created an EJB project with a service.

My first problem is that I cannot create a ".sar" directly by building the project, and surfing the net I saw a trick... I change the extension ".jar" to ".sar" manually inside the ".ear" produced. I thought this was not so bad as the service seems to work in this way... But I'm sure there should be a way to get directly the file .sar

The second problem (the main one) is that I can access and use properly all the web pages, BeansClients and ServerBeans if the service is not started. But when I started the service (manually from JBoss), some parts of the project stop working.

Might the second problem follows the first one? Any help in any of them?

Thanks.

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

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


From do-not-reply at jboss.com  Fri Mar 14 14:49:00 2008
From: do-not-reply at jboss.com (poornimaanne)
Date: Fri, 14 Mar 2008 14:49:00 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Turn on clientAuth only on the web
	services
Message-ID: <6264755.1205520540439.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thanks Thomas. Do you mean that we need to authenticate endpoints even when we access them from different ports? Is there a way to disable a web application to be accessed from a port?


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

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


From do-not-reply at jboss.com  Fri Mar 14 14:56:35 2008
From: do-not-reply at jboss.com (rphadnis)
Date: Fri, 14 Mar 2008 14:56:35 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Call a web service
Message-ID: <24808787.1205520996014.JavaMail.jboss@colo-br-02.atl.jboss.com>

Can you make sure that the url for the wsdl is accessible? For example you can put the url in a browser location bar and make sure it shows up.

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

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


From do-not-reply at jboss.com  Sat Mar 15 14:31:15 2008
From: do-not-reply at jboss.com (rodosa)
Date: Sat, 15 Mar 2008 14:31:15 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Call a web service
Message-ID: <24253223.1205605875333.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thanks for yours answers but I should make sth bad because it doesn't work.

1) rphadnis: Yes, the url for the wsdl is accessible. I could see in the browser.

2) PeterJ: I have some problems. I follow the steps you've mencionated but I don't know what's wrong. This is what occurs when I try to execute the client.


  | Entro en el cliente
  | Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/util/NotImp
  | lementedException
  |         at java.lang.Class.getDeclaredConstructors0(Native Method)
  |         at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
  |         at java.lang.Class.getConstructor0(Class.java:2699)
  |         at java.lang.Class.newInstance0(Class.java:326)
  |         at java.lang.Class.newInstance(Class.java:308)
  |         at javax.xml.ws.spi.FactoryFinder.newInstance(FactoryFinder.java:36)
  |         at javax.xml.ws.spi.FactoryFinder.find(FactoryFinder.java:95)
  |         at javax.xml.ws.spi.Provider.provider(Provider.java:76)
  |         at javax.xml.ws.Service.<init>(Service.java:57)
  |         at client.JbpmServiceService.<init>(JbpmServiceService.java:42)
  |         at client.JbpmWSClient.main(JbpmWSClient.java:79)
  | 

Any ideas? Thank you very much

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

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


From do-not-reply at jboss.com  Sat Mar 15 16:13:43 2008
From: do-not-reply at jboss.com (JoPe)
Date: Sat, 15 Mar 2008 16:13:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Cannot find service endpoint target
Message-ID: <25524161.1205612023457.JavaMail.jboss@colo-br-02.atl.jboss.com>

I had the same problem as hansOtto. The cause in my case was that the <jta-data-source> written in my META-INF/persistence.xml file didn't match the datasource name in the ...-ds.xml in my deployment directory. (And this needs to match the ...-ds.xml file name afaik.)

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

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


From do-not-reply at jboss.com  Sat Mar 15 16:54:49 2008
From: do-not-reply at jboss.com (rodosa)
Date: Sat, 15 Mar 2008 16:54:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Call a web service
Message-ID: <1706879.1205614489520.JavaMail.jboss@colo-br-02.atl.jboss.com>

If I run the client as Java application the following exception it's thrown:


  | java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/C:/jboss-4.2.2.GA/client/jaxb-impl.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
  | 	at com.sun.xml.bind.v2.model.impl.ModelBuilder.<clinit>(ModelBuilder.java:172)
  | 	at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:422)
  | 	at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(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(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
  | 	at java.lang.reflect.Method.invoke(Unknown Source)
  | 	at javax.xml.bind.ContextFinder.newInstance(Unknown Source)
  | 	at javax.xml.bind.ContextFinder.find(Unknown Source)
  | 	at javax.xml.bind.JAXBContext.newInstance(Unknown Source)
  | 	at javax.xml.bind.JAXBContext.newInstance(Unknown Source)
  | 	at com.sun.xml.ws.spi.ProviderImpl.getEPRJaxbContext(ProviderImpl.java:186)
  | 	at com.sun.xml.ws.spi.ProviderImpl.<clinit>(ProviderImpl.java:65)
  | 	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
  | 	at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
  | 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
  | 	at java.lang.reflect.Constructor.newInstance(Unknown Source)
  | 	at java.lang.Class.newInstance0(Unknown Source)
  | 	at java.lang.Class.newInstance(Unknown Source)
  | 	at javax.xml.ws.spi.FactoryFinder.newInstance(Unknown Source)
  | 	at javax.xml.ws.spi.FactoryFinder.find(Unknown Source)
  | 	at javax.xml.ws.spi.Provider.provider(Unknown Source)
  | 	at javax.xml.ws.Service.<init>(Unknown Source)
  | 	at client.JbpmServiceService.<init>(JbpmServiceService.java:42)
  | 	at client.JbpmWSClient.<clinit>(JbpmWSClient.java:85)
  | Exception in thread "main" 
  | 

I've put jaxb-api.jar in the lib/endorsed folder but it doesn't work. 

Any ideas?

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

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


From do-not-reply at jboss.com  Mon Mar 17 05:34:33 2008
From: do-not-reply at jboss.com (rodosa)
Date: Mon, 17 Mar 2008 05:34:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Call a web service
Message-ID: <2510401.1205746473585.JavaMail.jboss@colo-br-02.atl.jboss.com>

The before exception was solucionated putting the libraries into the endorsed lib folder of my JAVA_HOME. But now I have another problem. I was looking information about that in google and I think that is a problem of bad situation of my files I don't now exactly. This is the exception:


  | Exception in thread "main" com.sun.xml.ws.model.RuntimeModelerException: runtime modeler error: Wrapper class ws.jaxws.Hola is not found. Have you run APT to generate them?
  | 	at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:249)
  | 	at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:545)
  | 	at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:492)
  | 	at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:334)
  | 	at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:220)
  | 	at com.sun.xml.ws.client.WSServiceDelegate.addSEI(WSServiceDelegate.java:588)
  | 	at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:291)
  | 	at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:274)
  | 	at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:267)
  | 	at javax.xml.ws.Service.getPort(Service.java:92)
  | 	at client.JbpmServiceService.getJbpmServicePort(JbpmServiceService.java:52)
  | 	at client.JbpmWSClient.main(JbpmWSClient.java:91)
  | 
  | 

And my files are in the following directories:

*client*  //The client and the files generated with wsconsume
   -Hola.java
   -HolaResponse.java
   -JbpmService.java
   -JbpmServiceService.java
   -JbpmWSClient.java
   -ObjectFactory.java
   -package-info.java

*ws*
   -JbpmService.java


Any ideas?


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

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


From do-not-reply at jboss.com  Mon Mar 17 06:09:02 2008
From: do-not-reply at jboss.com (rodosa)
Date: Mon, 17 Mar 2008 06:09:02 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Call a web service
Message-ID: <23309228.1205748544374.JavaMail.jboss@colo-br-02.atl.jboss.com>

I don't know why it's looking into ws.jaxws.Hola directory because it doesn't exist! I built it and to check what happens and now the exception is :


  | Exception in thread "main" java.lang.IllegalArgumentException: ws.JbpmService is not an interface
  | 	at java.lang.reflect.Proxy.getProxyClass(Unknown Source)
  | 	at java.lang.reflect.Proxy.newProxyInstance(Unknown Source)
  | 	at com.sun.xml.ws.client.WSServiceDelegate.createEndpointIFBaseProxy(WSServiceDelegate.java:546)
  | 	at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:292)
  | 	at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:274)
  | 	at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:267)
  | 	at javax.xml.ws.Service.getPort(Service.java:92)
  | 	at client.JbpmServiceService.getJbpmServicePort(JbpmServiceService.java:52)
  | 	at client.JbpmWSClient.main(JbpmWSClient.java:91)
  | 

This is right. I haven't got the interface there, I have the class. So,  how I have to put the files to this work fine??? Have I to create the jaxws manually to this works fine??

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

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


From do-not-reply at jboss.com  Mon Mar 17 11:09:45 2008
From: do-not-reply at jboss.com (camunda)
Date: Mon, 17 Mar 2008 11:09:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Webservice invocation woes!
Message-ID: <9164548.1205766585968.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi Jihnd,

how did you get rid of the ClassCastException?

java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.ver1_1.Envelope1_1Impl

Thanks a lot
Bernd

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

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


From do-not-reply at jboss.com  Mon Mar 17 11:35:20 2008
From: do-not-reply at jboss.com (heiko.braun@jboss.com)
Date: Mon, 17 Mar 2008 11:35:20 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Webservice invocation woes!
Message-ID: <9346127.1205768120498.JavaMail.jboss@colo-br-02.atl.jboss.com>

If you run JDK 6 you'll need to endorse a bunch of libraries. SAAJ is one of them. Take a look at the WS WIKI, it's documented there.

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

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


From do-not-reply at jboss.com  Mon Mar 17 11:47:48 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 17 Mar 2008 11:47:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Call a web service
Message-ID: <14792587.1205768868765.JavaMail.jboss@colo-br-02.atl.jboss.com>

Be careful because after you use wsconsume to generate the stubs, you will have to items named ws.JbpmService. One is the web service class, the other is the interface generated by wsconsume. You want to include only the generated interface in your client's classpath.

Also,m are you suing wsrunclient to run the client? It build the correct classpath, you need to add in only the jar file containing your client code and the generated stubs.

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

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


From do-not-reply at jboss.com  Mon Mar 17 11:58:45 2008
From: do-not-reply at jboss.com (adesai@atech.com)
Date: Mon, 17 Mar 2008 11:58:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Error while starting server -
	SearchPortTypePort does no
Message-ID: <26174103.1205769525969.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

just in case, if anybody is looking for the answer, here are the jars required:

jaxb-api
jaxb-impl
jaxb-xjc
jboss-jaxrpc
jboss-jaxws

Thanks.

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

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


From do-not-reply at jboss.com  Mon Mar 17 12:25:38 2008
From: do-not-reply at jboss.com (rodosa)
Date: Mon, 17 Mar 2008 12:25:38 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Call a web service
Message-ID: <6957411.1205771138680.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello!

         Now I'm executing from Eclipse, because I'm building an .ear that contains a dinamic web project where the web service is inside. But I got the following error:


  | Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/xml/messaging/saaj/soap/AttachmentPartImpl
  | 	at com.sun.xml.ws.message.AttachmentUnmarshallerImpl.<clinit>(AttachmentUnmarshallerImpl.java:55)
  | 	at com.sun.xml.ws.client.sei.ResponseBuilder$DocLit.readResponse(ResponseBuilder.java:500)
  | 	at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:242)
  | 	at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:210)
  | 	at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:103)
  | 	at $Proxy25.hola(Unknown Source)
  | 	at client.JbpmWSClient.main(JbpmWSClient.java:95)
  | 
  | 

If I generate the jar and executing it with wsrunclient the following exception it's thrown (the library jboss-common-client.jar is in my path):


  | Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/util/NotImplementedException
  |         at java.lang.Class.getDeclaredConstructors0(Native Method)
  |         at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
  |         at java.lang.Class.getConstructor0(Class.java:2699)
  |         at java.lang.Class.newInstance0(Class.java:326)
  |         at java.lang.Class.newInstance(Class.java:308)
  |         at javax.xml.ws.spi.FactoryFinder.newInstance(FactoryFinder.java:36)
  |         at javax.xml.ws.spi.FactoryFinder.find(FactoryFinder.java:95)
  |         at javax.xml.ws.spi.Provider.provider(Provider.java:76)
  |         at javax.xml.ws.Service.<init>(Service.java:57)
  |         at client.JbpmServiceService.<init>(JbpmServiceService.java:42)
  |         at client.JbpmWSClient.main(JbpmWSClient.java:79)
  | 



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

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


From do-not-reply at jboss.com  Mon Mar 17 12:32:09 2008
From: do-not-reply at jboss.com (anayak)
Date: Mon, 17 Mar 2008 12:32:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - org.jboss.ws.WSException
Message-ID: <7382417.1205771529744.JavaMail.jboss@colo-br-02.atl.jboss.com>

Does anyone have the idea about the following exception?
I was trying to deploy a webservice.

The exception says : org.jboss.ws.WSException: arg0 is not a valid property on class ...

I am not getting any resource regarding the exception.

Thanks.

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

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


From do-not-reply at jboss.com  Mon Mar 17 13:35:55 2008
From: do-not-reply at jboss.com (trouby)
Date: Mon, 17 Mar 2008 13:35:55 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: communicating with WS in c# thorugh
	Java - encoding prob
Message-ID: <7245182.1205775355071.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hey,

I performed some tests and now I am sure there's encoding problem but I'm not sure on which size,

I've created the simplest WS .NET method with one string parameter and after calling the WS method, on the .NET side I see gibberish instead of UTF8 encoded string,


Please note, English works fine, the problem occurs only in other languages (in my situation it's hebrew)


Is there anything I can do? 
I'm clueless, I'm finding myself encoding/decoding strings in Base64 because of this issue :(



Many thanks,

Asaf.

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

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


From do-not-reply at jboss.com  Mon Mar 17 14:50:00 2008
From: do-not-reply at jboss.com (anayak)
Date: Mon, 17 Mar 2008 14:50:00 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: org.jboss.ws.WSException
Message-ID: <12045976.1205779800857.JavaMail.jboss@colo-br-02.atl.jboss.com>

Its a bit urgent.
I would appreciate any response.

Thanks.

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

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


From do-not-reply at jboss.com  Mon Mar 17 15:47:57 2008
From: do-not-reply at jboss.com (anayak)
Date: Mon, 17 Mar 2008 15:47:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: org.jboss.ws.WSException
Message-ID: <12503197.1205783277350.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am posting the sample of the code.
Package and Import statements are removed.

@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(propOrder = { "id" })
@XmlRootElement(name = "getMyRequest")
public class MyRequest {
	private Long id;
	public Long getId() { return id; }
	public void setId(Long id) { this.id = id; }
}


@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(name = "", propOrder = { "name" })
@XmlRootElement(name = "getMyResponse")
public class MyResponse {
	private String name;
	public String getName() { return name; }
	public void setName(String name) { this.name = name; }
}

@WebService(name = "MyFunctions")
public interface MyFunctions {
	@WebMethod(operationName = "getName")
	@WebResult(name = "name")
	@RequestWrapper(localName = "getMyRequest", className = "com.test.services.server.MyRequest")
	@ResponseWrapper(localName = "getMyResponse", className = "com.test.services.server.MyResponse")
	public String getName(Long tourId);
}

@Stateless
@WebService(endpointInterface = "com.test.services.MyFunctions")
@TransactionAttribute(TransactionAttributeType.REQUIRED)
public class MyFunctionImpl implements MyFunctions {
	public String getName(Long tourId) { return null; }
}

The following is the error I get.
I am using jboss 4.2.2 GA.

org.jboss.deployment.DeploymentException: Could not create deployment: file:/D:/Software/jboss/extracted/jboss-4.2.2.GA/server/hermes/deploy/temp.jar; - nested throwable: (org.jboss.ws.WSException: arg0 is not a valid property on class com.test.services.server.MyRequest)
	at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
	at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1050)
	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
	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$ScannerThread.loop(AbstractDeploymentScanner.java:274)
	at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
Caused by: org.jboss.ws.WSException: arg0 is not a valid property on class com.test.services.server.MyRequest
	at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getElementPropertyAccessor(JAXBContextImpl.java:926)
	at org.jboss.ws.metadata.acessor.JAXBAccessor$1$1.create(JAXBAccessor.java:75)
	at org.jboss.ws.metadata.umdm.ParameterMetaData.eagerInitialize(ParameterMetaData.java:480)
	at org.jboss.ws.metadata.umdm.OperationMetaData.eagerInitialize(OperationMetaData.java:458)
	at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitializeOperations(EndpointMetaData.java:533)
	at org.jboss.ws.metadata.umdm.EndpointMetaData.initializeInternal(EndpointMetaData.java:519)
	at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitialize(EndpointMetaData.java:507)
	at org.jboss.ws.metadata.umdm.ServiceMetaData.eagerInitialize(ServiceMetaData.java:429)
	at org.jboss.ws.metadata.umdm.UnifiedMetaData.eagerInitialize(UnifiedMetaData.java:196)
	at org.jboss.wsf.stack.jbws.EagerInitializeDeploymentAspect.create(EagerInitializeDeploymentAspect.java:50)
	at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
	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(SubDeployerInterceptorSupport.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)
	... 20 more


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

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


From do-not-reply at jboss.com  Mon Mar 17 16:38:59 2008
From: do-not-reply at jboss.com (poornimaanne)
Date: Mon, 17 Mar 2008 16:38:59 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Turn on clientAuth only on the web
	services
Message-ID: <3925622.1205786339771.JavaMail.jboss@colo-br-02.atl.jboss.com>

Is it even possible to tie a web application to a port?

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

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


From do-not-reply at jboss.com  Tue Mar 18 00:58:46 2008
From: do-not-reply at jboss.com (paparaoa)
Date: Tue, 18 Mar 2008 00:58:46 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Passing objects to JBoss Webservices
Message-ID: <18555065.1205816326127.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello,
I have got a web method in my webservice as follows:


  | @WebMethod
  | 	public Hashtable<String,String> getPointValues(@WebParam(name="pointList") List<String> pointList)
  | 	{
  | 		Hashtable<String, String> pointValueList = new Hashtable<String, String>();
  | 		for(int i=0;i<pointList.size();i++)
  | 		{
  | 	        pointValueList.put(pointList.get(i),getValueForPoint(pointList.get(i)));
  | 		}
  | 		return pointValueList;
  | 	}
  | 


I am making use of jboss remoting client to invoke the above method.
In the above method it takes argument as a list of string. I am forming a soap message and invoking the above method from my client as follows

Object response = remotingClient.invoke(soapmessage);

where the soap message is as follows:


  | <soapenv:Envelope xmlns:obix="http://obixservice/obix" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
  | <soapenv:Header/>
  | <soapenv:Body>
  | <obix:getPointValues>
  | <pointList>P003</pointList>
  | <pointList>P002</pointList>
  | <pointList>P004</pointList>
  | <pointList>P001</pointList>
  | <pointList>P005</pointList>
  | <pointList>P007</pointList>
  | <pointList>P006</pointList>
  | <pointList>P010</pointList>
  | <pointList>P009</pointList>
  | <pointList>P011</pointList>
  | <pointList>P008</pointList>
  | <pointList>P012</pointList>
  | </obix:getPointValues>
  | </soapenv:Body>
  | </soapenv:Envelope>
  | 


the getPointValues method mentioned above is expected to return hashtable. 
But its returning a string containing soap message.

How do i make this method return a hashtable ?


Thanks
R.Naik




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

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


From do-not-reply at jboss.com  Tue Mar 18 09:11:10 2008
From: do-not-reply at jboss.com (rodosa)
Date: Tue, 18 Mar 2008 09:11:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Call a web service
Message-ID: <10348825.1205845870849.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello!!

    I've get to call the web service from a Java application in Eclipse. I've solucionated the before error adding the library saaj-impl.jar. 

   Now I have a problem. I have jbpm-jpdl.3.2.2 installed in a remote machine.I would like to call this web service from here. But jbpm uses Jboss 4.0.4. I've added some libraries to the lib directory and I've copy the files that I've generated in the other machine (Jboss 4.2.2). I've modified the files replacing localhost with the IP where the webService exist. But it seems that it doesn't find the wsdl. I can do pings to my remote machine but if I put http://x.x.x.x:8080/proyecto/JbpmService?wsdl in the browser the system doesn't find anything.


  | Exception in thread "main" javax.xml.ws.WebServiceException: Failed to access the WSDL at: http://x.x.x.x:8080/proyecto/JbpmService?wsdl. It failed with: 
  | 	Connection refused: connect.
  | 	at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(RuntimeWSDLParser.java:136)
  | 	at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:122)
  | 	at com.sun.xml.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:226)
  | 	at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:189)
  | 	at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:159)
  | 	at com.sun.xml.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:81)
  | 	at javax.xml.ws.Service.<init>(Service.java:56)
  | 	at jbpmservice.ws.JbpmService_Service.<init>(JbpmService_Service.java:40)
  | 	at client.JbpmWSClient.main(JbpmWSClient.java:15)
  | Caused by: java.net.ConnectException: Connection refused: connect
  | 	at java.net.PlainSocketImpl.socketConnect(Native Method)
  | 	at java.net.PlainSocketImpl.doConnect(Unknown Source)
  | 	at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
  | 	at java.net.PlainSocketImpl.connect(Unknown Source)
  | 	at java.net.Socket.connect(Unknown Source)
  | 	at java.net.Socket.connect(Unknown Source)
  | 	at sun.net.NetworkClient.doConnect(Unknown Source)
  | 	at sun.net.www.http.HttpClient.openServer(Unknown Source)
  | 	at sun.net.www.http.HttpClient.openServer(Unknown Source)
  | 	at sun.net.www.http.HttpClient.<init>(Unknown Source)
  | 	at sun.net.www.http.HttpClient.New(Unknown Source)
  | 	at sun.net.www.http.HttpClient.New(Unknown Source)
  | 	at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
  | 	at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
  | 	at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
  | 	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
  | 	at java.net.URL.openStream(Unknown Source)
  | 	at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.createReader(RuntimeWSDLParser.java:785)
  | 	at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(RuntimeWSDLParser.java:236)
  | 	at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:107)
  | 	... 7 more
  | 
  | 

Any ideas? 

Thanks

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

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


From do-not-reply at jboss.com  Tue Mar 18 12:41:23 2008
From: do-not-reply at jboss.com (thomas.diesler@jboss.com)
Date: Tue, 18 Mar 2008 12:41:23 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: java.lang.NoClassDefFoundError:
	javax/jws/WebService
Message-ID: <30365847.1205858483178.JavaMail.jboss@colo-br-02.atl.jboss.com>

The missing class is in jboss-jaxws.jar

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

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


From do-not-reply at jboss.com  Tue Mar 18 13:23:45 2008
From: do-not-reply at jboss.com (Crucifix)
Date: Tue, 18 Mar 2008 13:23:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: org.xml.sax.SAXParseException:
	Premature end of file ERR
Message-ID: <4642427.1205861025095.JavaMail.jboss@colo-br-02.atl.jboss.com>

piliana,

  I'm having the same issue connecting a .NET client to JBoss.  Could you please specify what you had to do to resolve this in .NET?  (I couldn't find a way to PM or e-mail you about this.)

  Your help would be greatly appreciated!

-David

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

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


From do-not-reply at jboss.com  Wed Mar 19 06:09:35 2008
From: do-not-reply at jboss.com (chavali)
Date: Wed, 19 Mar 2008 06:09:35 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - AddChild() giving
	java.util.NoSuchElementException
Message-ID: <16251720.1205921375802.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

    Following code is giving java.util.NoSuchElementException. The exception is thrown at addChild() method.

String xmlString = "<ns1:echo xmlns:ns1=\"http://ws.apache.org/axis2/xsd\"> <ns1:echo>Hello</ns1:echo> 	</ns1:echo>";
XMLStreamReader parser2 = XMLInputFactory.newInstance().createXMLStreamReader(new StringReader(xmlString));
OMXMLParserWrapper builder2 = new StAXOMBuilder(parser2);
OMElement documentElement = builder2.getDocumentElement();

SOAPFactory fac = OMAbstractFactory.getSOAP11Factory();
 SOAPEnvelope envelope1 = fac.getDefaultEnvelope(); 
envelope1.getBody().addChild( (OMNode)documentElement );
newMsgContext.setEnvelope( envelope1 );

Can anybody help in this regard.





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

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


From do-not-reply at jboss.com  Wed Mar 19 17:36:54 2008
From: do-not-reply at jboss.com (zach.mabe@cox.com)
Date: Wed, 19 Mar 2008 17:36:54 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - ServiceEndpointInvoker rethrows
	runtimeexception, headers th
Message-ID: <4122310.1205962614887.JavaMail.jboss@colo-br-02.atl.jboss.com>

In version 2.0.3.GA, I am seeing an issue where the org.jboss.ws.core.server.ServiceEndpointInvoker is  catching a runtimeexception thrown from within a handler, calling the handleFault operations of the handlers but then rethrowing the exception.  

Since this is a runtimeexception, it ends up being passed back out to org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(...) where a new SOAP Fault message is created because (I think) the requesthandlerimpl doesn't repeek the messagecontextstack for a fresh context. 

Is this a bug or am I not understanding how it is supposed to work.  

The main problem with this is my custom handler throws a WebServiceException when the request isn't valid.  I see that the WSAddressingServerHandling is putting the correct ws-addressing stuff in the response.  But that response isn't what ends up being sent to the client.  The client then complains because the response is missing the action header.


Thanks
Zach Mabe



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

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


From do-not-reply at jboss.com  Wed Mar 19 19:46:00 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 19 Mar 2008 19:46:00 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: ServiceEndpointInvoker rethrows
	runtimeexception, header
Message-ID: <11965275.1205970360400.JavaMail.jboss@colo-br-02.atl.jboss.com>

While working on JBWS-1941 I fixed a bit the native stack behaviour about exception handling. You might want to try the current trunk version or wait for the next release (1st April 2008) to see if it solves you issue.

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

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


From do-not-reply at jboss.com  Thu Mar 20 07:17:30 2008
From: do-not-reply at jboss.com (rodosa)
Date: Thu, 20 Mar 2008 07:17:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Change the endopoint address
Message-ID: <22694159.1206011850555.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello!

    How I have to do to change the endpoint address? I would like that my wsdlLocation was in a different ip than localhost. But when I deploy my .ear it's created the Endpoint Address at localhost	


  | http://127.0.0.1:8080/proyecto/JbpmService?wsdl 
  | 

How I chage the localhost with other IP?

Thanks

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

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


From do-not-reply at jboss.com  Thu Mar 20 08:50:44 2008
From: do-not-reply at jboss.com (rodosa)
Date: Thu, 20 Mar 2008 08:50:44 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Change the endopoint address
Message-ID: <20360603.1206017444964.JavaMail.jboss@colo-br-02.atl.jboss.com>

If I start the server with the -b option, specifying the ip ... the endpoint uses this IP. But ... are there another solution for this?

Could I set the varaible jboss.bind.address in any configuration file? how?

Thanks

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

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


From do-not-reply at jboss.com  Thu Mar 20 09:33:37 2008
From: do-not-reply at jboss.com (zach.mabe@cox.com)
Date: Thu, 20 Mar 2008 09:33:37 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: ServiceEndpointInvoker rethrows
	runtimeexception, header
Message-ID: <21102097.1206020017381.JavaMail.jboss@colo-br-02.atl.jboss.com>

Alessio,


That looks spot on as the solution for this issue.  Thanks for the quick response and, more importantly,  the fix.   

Thanks
Zach Mabe

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

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


From do-not-reply at jboss.com  Thu Mar 20 10:12:43 2008
From: do-not-reply at jboss.com (ramboid)
Date: Thu, 20 Mar 2008 10:12:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - InvokerServlet in JBoss 4.2.2
Message-ID: <10343626.1206022363813.JavaMail.jboss@colo-br-02.atl.jboss.com>


--------------------------------------------------------------------------------
 
With JBoss 4.2.2, can I use the InvokerServlet in th e<servlet-mapping> section of my web.xml? With JBoss 4.0.5GA, I was able to create war deploymenst with a web xml that would map the servlets as follows: 

<servlet-name>invoker</servlet-name> 
<servlet-class> 
org.apache.catalina.servlets.InvokerServlet 
</servlet-class> 
<load-on-startup>2</load-on-startup> 

<servlet-mapping> 
<servlet-name>invoker</servlet-name> 
<url-pattern>/servlet/*</url-pattern> 
</servlet-mapping> 

But in JBoss 4.2.2 I must explicitly add a mapping for each servlet in the web.xml file instead of jsut using the invoker 


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

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


From do-not-reply at jboss.com  Thu Mar 20 15:02:16 2008
From: do-not-reply at jboss.com (pramod_bs)
Date: Thu, 20 Mar 2008 15:02:16 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Change the endopoint address
Message-ID: <27480752.1206039736829.JavaMail.jboss@colo-br-02.atl.jboss.com>

I think if you comment out this line then it will take whatever the ipaddress we give in the server:


   "webServiceHost">${jboss.bind.address} 

File is: 
C:\Program Files\jboss-4.2.1.GA\server\default\deploy\jbossws.sar\jbossws.beans\META-INF\jboss-beans.xml

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

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


From do-not-reply at jboss.com  Thu Mar 20 15:31:08 2008
From: do-not-reply at jboss.com (pramod_bs)
Date: Thu, 20 Mar 2008 15:31:08 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Interceptor for JBossWS
Message-ID: <31453181.1206041468746.JavaMail.jboss@colo-br-02.atl.jboss.com>

How I can write an Interceptor for a web service. Here is the scenario:
I have a service with WS-Security. After the JBossWS authenticated the user I need to intercept for applying policy using XACML. Ay ideas will be greatly appreciated.

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

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


From do-not-reply at jboss.com  Thu Mar 20 19:38:03 2008
From: do-not-reply at jboss.com (jsb)
Date: Thu, 20 Mar 2008 19:38:03 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Servlet regarded as ServiceEndPoint
Message-ID: <15067314.1206056283316.JavaMail.jboss@colo-br-02.atl.jboss.com>

I just ran into this using JBoss AS 4.0.5 with included JBossWS, and my servlet name DOES end with Servlet... turns out my web xml formatting was causing the endsWith("Servlet") to see more than the name string.

Changing:
<servlet>
  |    <servlet-name>MyServlet</servlet-name>
  |     <servlet-class>
  |         com.example.MyServlet
  |     </servlet-class>
  |         ...
  | </servlet>
..to:
<servlet>
  |    <servlet-name>MyServlet</servlet-name>
  |     <servlet-class>com.example.MyServlet</servlet-class>
  |         ...
  | </servlet>
...corrected the problem for me.

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

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


From do-not-reply at jboss.com  Fri Mar 21 07:31:49 2008
From: do-not-reply at jboss.com (rodosa)
Date: Fri, 21 Mar 2008 07:31:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Change the endopoint address
Message-ID: <22590254.1206099109172.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thank you!!! It works!!!

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

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


From do-not-reply at jboss.com  Fri Mar 21 09:52:43 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 21 Mar 2008 09:52:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Change the endopoint address
Message-ID: <30440957.1206107563260.JavaMail.jboss@colo-br-02.atl.jboss.com>

http://jbws.dyndns.org/mediawiki/index.php?title=FAQ#How_does_rewriting_of_the_soap_address_in_WSDL_work.3F

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

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


From do-not-reply at jboss.com  Fri Mar 21 09:58:22 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 21 Mar 2008 09:58:22 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Interceptor for JBossWS
Message-ID: <17520455.1206107902711.JavaMail.jboss@colo-br-02.atl.jboss.com>

Did you already take a look at the handler documentation? http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#Handler_Framework

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

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


From do-not-reply at jboss.com  Fri Mar 21 10:06:14 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 21 Mar 2008 10:06:14 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Passing objects to JBoss Webservices
Message-ID: <12159412.1206108374373.JavaMail.jboss@colo-br-02.atl.jboss.com>

Using a webservice client instead of performing a call directly through remoting would prevent you from manually unmarshalling the soap message ;-)
You might take a look at the distribution samples and the documentation about ws clients: http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#Web_Service_Clients

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

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


From do-not-reply at jboss.com  Fri Mar 21 10:13:27 2008
From: do-not-reply at jboss.com (pramod_bs)
Date: Fri, 21 Mar 2008 10:13:27 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Interceptor for JBossWS
Message-ID: <2028474.1206108807639.JavaMail.jboss@colo-br-02.atl.jboss.com>

I looked at the doc. I might have got lost. My confusion is how to include my XACML policy validation inside the handler chain after JBossWS handles the username token authentication. Or is there another better way of handling this?

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

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


From do-not-reply at jboss.com  Fri Mar 21 10:22:45 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 21 Mar 2008 10:22:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: communicating with WS in c# thorugh
	Java - encoding prob
Message-ID: <10665934.1206109365618.JavaMail.jboss@colo-br-02.atl.jboss.com>

Well, you could start investigating what actually goes to the wire to understand which side is the problem. This way we could eventually see if there's an issue and perhaps create a test case showing it.

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

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


From do-not-reply at jboss.com  Fri Mar 21 10:25:23 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 21 Mar 2008 10:25:23 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Error while starting server -
	SearchPortTypePort does no
Message-ID: <25100025.1206109524052.JavaMail.jboss@colo-br-02.atl.jboss.com>

You might also look at the wsrunclient script in the distribution, since it references all the libraries required to run a standard web service client.

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

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


From do-not-reply at jboss.com  Fri Mar 21 10:32:57 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 21 Mar 2008 10:32:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Jboss support for Webservices over
	REST?
Message-ID: <33339827.1206109977438.JavaMail.jboss@colo-br-02.atl.jboss.com>

JBossWS currently does not support REST; you might want to monitor this: http://jira.jboss.org/jira/browse/JBWS-1548.

Apart from what's in JBossWS, there's also the RestEasy project providing an implementation of JSR 311:http://wiki.jboss.org/wiki/Wiki.jsp?page=RESTeasyJAXRS

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

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


From do-not-reply at jboss.com  Fri Mar 21 11:33:41 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 21 Mar 2008 11:33:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Message faults not signed
Message-ID: <17770196.1206113622080.JavaMail.jboss@colo-br-02.atl.jboss.com>

Right now there's no way to have JBossWS native sign and/or encrypt faults. This issue was however addressed in the past, please monitor JBWS-1119 (http://jira.jboss.org/jira/browse/JBWS-1119), I'll see if it's possible to have this feature back soon.

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

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


From do-not-reply at jboss.com  Fri Mar 21 11:39:46 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 21 Mar 2008 11:39:46 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Steps for implementing WS-Security
	in JBoss using Userna
Message-ID: <27324248.1206113986060.JavaMail.jboss@colo-br-02.atl.jboss.com>

"pramod_bs" wrote : Thanks for the suggestions. I have a question. I am trying to figure out how to add a password digest to this. Please help

This will be available with next 2.0.4 native release: http://jbws.dyndns.org/mediawiki/index.php?title=WS-Security_options#Password_digest.2C_nonces_and_timestamp

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

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


From do-not-reply at jboss.com  Fri Mar 21 11:55:21 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 21 Mar 2008 11:55:21 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossXSModel goes into endless loop
Message-ID: <12617706.1206114921984.JavaMail.jboss@colo-br-02.atl.jboss.com>

May be I'm missing something... what are you actually trying to do with this WS? Did you code the wsdl by hand (contract-first approach)? Do you really want to import the whole xhtml schema into your types? ;-)
This said, there might also be an issue with the JBossXSModel, but before looking for it please check if this is really what you need. Then you could create a JIRA issue with a testcase showing this behavior.

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

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


From do-not-reply at jboss.com  Fri Mar 21 12:07:50 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 21 Mar 2008 12:07:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBoss & JAX-WS. Beginners Guide
Message-ID: <7936610.1206115671139.JavaMail.jboss@colo-br-02.atl.jboss.com>

A common problem of computer science books is that they become out of date ;-)
For sure we have documentation about JAX-WS web services, http://jbws.dyndns.org/mediawiki/index.php?title=JBossWS and it is constantly maintained up to date.
In particular, you might want to read this: http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide

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

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


From do-not-reply at jboss.com  Fri Mar 21 12:19:49 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 21 Mar 2008 12:19:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Yet another WS-Security question ...
Message-ID: <7960874.1206116390342.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,
regarding your first concern, i.e. nothing related to ws-security in the wsdl, that's right since we currently support ws-security only, not ws-security policy, thus even if the security processing is correctly configured you should not expect it to be advertised in the wsdl.
Regarding your second issue, i.e. the null pointer exception you're getting, could you please tell me which JBossWS version you are using? Is it the one that ships with JBoss 4.2.1.GA? Btw you might want to try with the latest JBossWS version, since we've been making many fixes and changes to this stuff recently, so your issue might have been already addressed.

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

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


From do-not-reply at jboss.com  Fri Mar 21 12:30:20 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 21 Mar 2008 12:30:20 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Compile errors with wsconsume
	generated source
Message-ID: <26243918.1206117020231.JavaMail.jboss@colo-br-02.atl.jboss.com>

The "$Proxy0" port type name could be your problem. You might want to try editing that in the wsdl and running wsconsume again.

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

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


From do-not-reply at jboss.com  Fri Mar 21 12:55:10 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 21 Mar 2008 12:55:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Upgrading to 4.2.2 changed
	published WSDL
Message-ID: <1707761.1206118511035.JavaMail.jboss@colo-br-02.atl.jboss.com>

Which versions of jbossws are involved? the default ones coming with the AS? Could you provide further details about the exception you're getting?

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

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


From do-not-reply at jboss.com  Fri Mar 21 13:02:49 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 21 Mar 2008 13:02:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem retrieving service in
	developing a client
Message-ID: <13776696.1206118969816.JavaMail.jboss@colo-br-02.atl.jboss.com>

Could you please post here the wsdl? This might be a problem in the wsdl definition.

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

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


From do-not-reply at jboss.com  Fri Mar 21 13:10:06 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 21 Mar 2008 13:10:06 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: SSL and native libraries
Message-ID: <12119787.1206119407083.JavaMail.jboss@colo-br-02.atl.jboss.com>

Did you already try posting here? http://www.jboss.com/index.html?module=bb&op=viewforum&f=50

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

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


From do-not-reply at jboss.com  Fri Mar 21 13:13:17 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 21 Mar 2008 13:13:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Throwing Exception from a web
	service method
Message-ID: <9197647.1206119598116.JavaMail.jboss@colo-br-02.atl.jboss.com>

Sure, you should be able. The log will of course trace it, but you would get a soap fault message sent. What the issue you're having exactly?

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

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


From do-not-reply at jboss.com  Fri Mar 21 13:26:33 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 21 Mar 2008 13:26:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Question: Is it possible having
	both WS-Addressing and W
Message-ID: <19985771.1206120393893.JavaMail.jboss@colo-br-02.atl.jboss.com>

Yes, it's indeed possible. However there's not a standard pre-built endpoint configuration for this, thus you would have to provide it (see standard-jaxws-endpoint-config.xml for instance) with both the addressing and security handlers.

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

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


From do-not-reply at jboss.com  Fri Mar 21 13:38:39 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 21 Mar 2008 13:38:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: webservice on jbos 4.0.2
Message-ID: <24246473.1206121119889.JavaMail.jboss@colo-br-02.atl.jboss.com>

If you managed to upgrade at least to 4.0.5.GA you could use JBossWS up to 2.0.3 native, which of course include JAX-WS features.
If you have to stick with 4.0.2 you might want to try jbossws really old 1.0.3, 1.0.4 or 1.2.1 which had a preview implementation of JSR-181.
CXF and Metro integration is available starting from JBossWS 3.0.0, which requires AS 4.2.1 at least.
See 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=4138354#4138354

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


From do-not-reply at jboss.com  Fri Mar 21 13:55:07 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 21 Mar 2008 13:55:07 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Bug in wiki WS-Security document or?
Message-ID: <5751095.1206122107182.JavaMail.jboss@colo-br-02.atl.jboss.com>

Yes, the JAX-WS security handler should be configured as a post handler. I fixed the documentation on the wiki. Thanks!

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

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


From do-not-reply at jboss.com  Fri Mar 21 14:15:00 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 21 Mar 2008 14:15:00 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: referencing jboss-wsse-client.xml
	in WAR
Message-ID: <16025662.1206123301008.JavaMail.jboss@colo-br-02.atl.jboss.com>

Given that JBossWS should load by default the META-INF/jboss-wsse-client.xml in your jar file if you don't explicitly provide that url, generally speaking you can access resources in a jar using the getResource() method of Class.

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

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


From do-not-reply at jboss.com  Fri Mar 21 14:21:14 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 21 Mar 2008 14:21:14 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: How to setup wsse usernametoken for
	ejb3 based web servi
Message-ID: <22647177.1206123674157.JavaMail.jboss@colo-br-02.atl.jboss.com>

http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#Proprietary_Annotations

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

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


From do-not-reply at jboss.com  Fri Mar 21 16:40:47 2008
From: do-not-reply at jboss.com (actonwang)
Date: Fri, 21 Mar 2008 16:40:47 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - resource injection in WS handler not
	working in jboss JAX-WS
Message-ID: <25389716.1206132047632.JavaMail.jboss@colo-br-02.atl.jboss.com>

hi,

       I tried to use resource injection in WS Handler as described in JAX-WS spec which is a MUST feature.

       I tested it in both Sun impl and Jbosss JAX-WS 2.0.x with Jboss 4.2.2. It is working well in Sun impl but not working in JBoss WS.
   
       here is the simple test. I am using web war as deployement, inside web.xml, I have the following:

   <env-entry>
     <env-entry-name>customFormat</env-entry-name>
     <env-entry-type>java.lang.String</env-entry-type>
     <env-entry-value>Path1: $PATH_INFO, Outbound: $MESSAGE_OUTBOUND_PROPERTY - $NODE</env-entry-value>
     <injection-target> 
     <injection-target-class>testjaxws.handler.DefaultCustomLoggingWrapperHandler</injection-target-class>
     <injection-target-name>customFormat</injection-target-name> 
     </injection-target>
   </env-entry>

inside DefaultCustomLoggingWrapperHandler class, I have:

    @Resource
    private String customFormat = null;


defined.

       It is never gets injected with this value no matter what I tried. 

       Anyone could help to explain if jboss WS has implemented it or not? If   it is implemented, how should we make it work?

Thanks a lot!!
actonwang


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

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


From do-not-reply at jboss.com  Sat Mar 22 04:40:56 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Sat, 22 Mar 2008 04:40:56 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: resource injection in WS handler
	not working in jboss JA
Message-ID: <12306042.1206175256710.JavaMail.jboss@colo-br-02.atl.jboss.com>

http://jira.jboss.org/jira/browse/JBWS-2074

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

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


From do-not-reply at jboss.com  Sun Mar 23 08:05:04 2008
From: do-not-reply at jboss.com (jpramondon)
Date: Sun, 23 Mar 2008 08:05:04 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: ServiceLifecycle troubles
Message-ID: <4446760.1206273904404.JavaMail.jboss@colo-br-02.atl.jboss.com>

It may sounds a bit late now, but that was really usefull mate !

Thanks for posting your solution.

J

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

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


From do-not-reply at jboss.com  Mon Mar 24 04:33:24 2008
From: do-not-reply at jboss.com (kanumalla)
Date: Mon, 24 Mar 2008 04:33:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: EntityManager injection in
	Webservice
Message-ID: <16363062.1206347604902.JavaMail.jboss@colo-br-02.atl.jboss.com>

wtf!

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

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


From do-not-reply at jboss.com  Mon Mar 24 11:32:33 2008
From: do-not-reply at jboss.com (JGF1)
Date: Mon, 24 Mar 2008 11:32:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WebService response problem
Message-ID: <7575764.1206372753146.JavaMail.jboss@colo-br-02.atl.jboss.com>

"omatzura" wrote : Hi,
  | 
  | hmm... maybe this is happening because you are using jdk 1.6.. can you try running jboss under jdk 1.5 instead?
  | 
  | regards again,
  | 
  | /Ole
  | eviware.com
This begs the question.. What is it about jdk 1.6 & Soap versus jdk1.5.

What has changed to make jdk 1.6 incompatible with prior release. I had assumed newer versions would be backwardly compatible..

I came across the same issue following along with an Eclipse example hosted here:
http://www.mirrorservice.org/sites/download.eclipse.org/eclipseMirror/technology/phoenix/europa/EclipseIdeForJeeDevelopers/
My config was similar:
eclipse-jee-europa-winter-win32.zip (Plus updates to get past weird null pointer error : see https://bugs.eclipse.org/bugs/show_bug.cgi?id=219627
java_app_platform_sdk-5_04-windows.exe

java version "1.6.0_04"
Java(TM) SE Runtime Environment (build 1.6.0_04-b12)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode)

JBoss 4.2.2 GA
(Eclipse says Java 5 JRE is required).
(Release notes for JBoss 4.2.2GA say JDK5 required). 


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

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


From do-not-reply at jboss.com  Mon Mar 24 15:12:30 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 24 Mar 2008 15:12:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WebService response problem
Message-ID: <13181610.1206385950740.JavaMail.jboss@colo-br-02.atl.jboss.com>

If you look at the runtime library that accompanies JDK 6, you will see that it now includes many of the web services packages that were not in JDK 5. Every Java SE release, it appears that Sun adds in more packages that earlier had appeared only in Java EE.  Because JBossAS 4.2.x and 4.0.x are qualified with JDK 5, they include the web services jars, which are not at the same level as the ones on JDK 6. (From what I recall when I researched this in depth many months ago, the web services libraries included in JBossAS 4.2.x were newer than what is included in JDK 6.) Placing the web service jars from JBossAS into the endorsed directory causes the JDK to use those classes instead of the ones in the runtime jar.

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

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


From do-not-reply at jboss.com  Mon Mar 24 16:35:32 2008
From: do-not-reply at jboss.com (jpramondon)
Date: Mon, 24 Mar 2008 16:35:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: wstools-config.xml
Message-ID: <10749780.1206390932247.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi there,

I'm probably exhuming a pretty old post now, but I just wanted to make things clearer for me.
I've been reading a lot this week-end on JBossWS, WStools and a lot of surrounding topics and suffs.
>From what I understand, you suggest giving up using WSTools in the profit of annotations.
Here's where I'm a bit confused : 
- I thought annotations where for JAX-WS
- I know I can (correct me if I'm wrong alright) do some JAX-RPC with JAX-WS, because the latter supports the former.
- but wasn't JAX-WS only to use with Java 6 ? Or in other words : may I use annotations to replace my use of WSTools even if I'm coding JAX-RPC style webservices with java 5 ? 

Cheers,

J

"thomas.diesler at jboss.com" wrote : webservices.xml supports multiple service endpoints. You have to merge the wstools generated webservices.xml files manully.
  | 
  | BTW, wscompile does not generate webservices.xml at all.
  | 
  | Why not use JSR181 endpoints and get rid of all those offline tools generation issue all together?

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

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


From do-not-reply at jboss.com  Mon Mar 24 16:41:32 2008
From: do-not-reply at jboss.com (actonwang)
Date: Mon, 24 Mar 2008 16:41:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: resource injection in WS handler
	not working in jboss JA
Message-ID: <7918455.1206391292711.JavaMail.jboss@colo-br-02.atl.jboss.com>

hi,

   FYI: by looking at source code of HandlerResolverImpl, it looks at public fields and public methods with @Resource annotation and if it is any, it just throws "Not implemented" error.

   Really hope that it can also look at private fields and possible retrace back to any mark in parent classes as well after this ability is added in.

thx
acton

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

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


From do-not-reply at jboss.com  Mon Mar 24 22:19:48 2008
From: do-not-reply at jboss.com (pramod_bs)
Date: Mon, 24 Mar 2008 22:19:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WS-Security and Handlers
Message-ID: <27331438.1206411588561.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have a simple web service which I have implemented username token authentication. Also I have my own Policy handler which I have configured using @handlerChain. I would like to invoke this handler between the JBossWS authenticates the usernametoken and actual execution of the method. 


package test;

import javax.ejb.Stateless;
import javax.jws.HandlerChain;
import javax.jws.WebService;
import javax.jws.WebMethod;
import javax.jws.soap.SOAPBinding;
import org.jboss.annotation.security.SecurityDomain;
import org.jboss.ws.annotation.EndpointConfig;

import com.sun.xacml.Indenter;
import com.sun.xacml.ctx.ResponseCtx;

@Stateless                                                              
@WebService
	    (name="TestWSEJB",
		targetNamespace = "http://test",
		serviceName = "TestWSEJBService")
		@SOAPBinding(style = SOAPBinding.Style.DOCUMENT)
		@EndpointConfig(configName = "Standard WSSecurity Endpoint")
		@SecurityDomain("JBossWS")
		@HandlerChain(file = "jaxws-handlers-server.xml") 
public class TestWSEJB {
	@WebMethod
	public String ping (String name) throws Exception
	{
		return "Hello : " + name;
	}
}



<?xml version="1.0" encoding="UTF-8"?>

<handler-chains 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 javaee_web_services_1_2.xsd">

   <handler-chain>
      <protocol-bindings>##SOAP11_HTTP</protocol-bindings>
      
         <handler-name> PolicyHandler </handler-name>
         <handler-class> test.WSXACMLPolicyHandler </handler-class>
          <soap-role>SecurityProvider</soap-role>
      
   </handler-chain>
</handler-chains>






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

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


From do-not-reply at jboss.com  Mon Mar 24 22:27:55 2008
From: do-not-reply at jboss.com (pramod_bs)
Date: Mon, 24 Mar 2008 22:27:55 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: How to setup wsse usernametoken for
	ejb3 based web servi
Message-ID: <4143444.1206412075761.JavaMail.jboss@colo-br-02.atl.jboss.com>

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=131719

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

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


From do-not-reply at jboss.com  Tue Mar 25 06:19:32 2008
From: do-not-reply at jboss.com (darran.lofthouse@jboss.com)
Date: Tue, 25 Mar 2008 06:19:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Servlet regarded as ServiceEndPoint
Message-ID: <23171879.1206440372880.JavaMail.jboss@colo-br-02.atl.jboss.com>

http://jira.jboss.com/jira/browse/JBWS-1093

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

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


From do-not-reply at jboss.com  Tue Mar 25 07:10:32 2008
From: do-not-reply at jboss.com (chavali)
Date: Tue, 25 Mar 2008 07:10:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - SessionManagement using soapsession
Message-ID: <17976662.1206443432433.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

   Somebody can give code example or link on using soapsession/transport session for maintaining session across multiple services in a servicegroup. 

Chavali

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

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


From do-not-reply at jboss.com  Tue Mar 25 08:38:22 2008
From: do-not-reply at jboss.com (JGF1)
Date: Tue, 25 Mar 2008 08:38:22 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WebService response problem
Message-ID: <32524839.1206448702522.JavaMail.jboss@colo-br-02.atl.jboss.com>

"PeterJ" wrote : (From what I recall when I researched this in depth many months ago, the web services libraries included in JBossAS 4.2.x were newer than what is included in JDK 6.).
Many thanks for reply. I am beginning to appreciate the complexities of what's going on better now. Out of interest how did you go about doing this research/analysis? Investigating what versions of classes are in what jars is one of the things I am struggling to get my head around when working with Java. I understand technologies like Maven/Ivy can help but am stll a novice and have not used them too much yet.

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

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


From do-not-reply at jboss.com  Tue Mar 25 09:28:36 2008
From: do-not-reply at jboss.com (davidkally)
Date: Tue, 25 Mar 2008 09:28:36 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - connecting to WS from different machine
Message-ID: <29632095.1206451716322.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi all,

I need to connect to a deployed WS from different machine.

What I tried to do and it did not work is:

Copy the WSDL file to the machine where the client application is, then I changed the <soap:address> from saying localhost to the actual IP (e.g. clint.ncl.ac.uk) and I keept the rest as it was.

However as I said it did not work !!??

can anyone tell me what to do or change in jboss-4.2.1.GA which i use as Application server?????

thanks for Listening.




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

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


From do-not-reply at jboss.com  Tue Mar 25 09:37:31 2008
From: do-not-reply at jboss.com (ronari2@yahoo.com)
Date: Tue, 25 Mar 2008 09:37:31 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: communicating with WS in c# thorugh
	Java - encoding prob
Message-ID: <25224452.1206452251306.JavaMail.jboss@colo-br-02.atl.jboss.com>


Asaf,

We had the same problem. The problem occur because not all the steps that are involved in Web Services creation support UTF-8 by default.

Add to your JBoss startup script the following parameter: -Dfile.encoding=utf-8

This should solve your problem. 

Ronen

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

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


From do-not-reply at jboss.com  Tue Mar 25 10:15:50 2008
From: do-not-reply at jboss.com (davidkally)
Date: Tue, 25 Mar 2008 10:15:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: connecting to WS from different
	machine
Message-ID: <12390243.1206454550318.JavaMail.jboss@colo-br-02.atl.jboss.com>

hi again all,

i fixed it now, the problem was that i need to run jboss with this commend:
./run.sh -c all -b my hostmachine.aa.uk

instead of what i was doing:
./run.sh

i hope this could be helpful for somebody else.






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

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


From do-not-reply at jboss.com  Tue Mar 25 11:33:07 2008
From: do-not-reply at jboss.com (trouby)
Date: Tue, 25 Mar 2008 11:33:07 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: communicating with WS in c# thorugh
	Java - encoding prob
Message-ID: <19226737.1206459187937.JavaMail.jboss@colo-br-02.atl.jboss.com>

Great,

I wouldn't never imagine that this flag is related to WS encoding,


Many thanks,

Asaf.

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

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


From do-not-reply at jboss.com  Tue Mar 25 11:40:58 2008
From: do-not-reply at jboss.com (Maffewl)
Date: Tue, 25 Mar 2008 11:40:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - question about WS client accessing
	local wsdl
Message-ID: <2307460.1206459658281.JavaMail.jboss@colo-br-02.atl.jboss.com>

I'm trying to find the best way access a local wsdl, instead of going over http to a remote WSDL when creating a client-side service.

I want to package the WSDL in the same jar as my classes i've compiled as a resource but I haven't quite figured out how to create a java.net.URL to point at that WSDL.

I have been sucessful putting the wsdl in a known location and creating a URL with a file protocol and pointing to the absolute path on the server,  but thats not as flexible as I want it to be, i was hoping to deploy it in a JAR

Has anyone else been sucessful with this?

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

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


From do-not-reply at jboss.com  Tue Mar 25 15:09:39 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 25 Mar 2008 15:09:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WebService response problem
Message-ID: <28242768.1206472179473.JavaMail.jboss@colo-br-02.atl.jboss.com>

Add the -verbose:class JVM option to the command line (to JAVA_OPTS in the run scripts). This option causes the JVM to print out the location of each class loaded. I noticed when using JDK 6 that the web services classes were suddenly coming from the runtime jar. Also, if I recall correctly, with JDK 6 I was getting a missing method exception. I unzipped the sources for JDK 6 and noted that the method was indeed missing but when looking at the sources from the app server, the method was there.

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

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


From do-not-reply at jboss.com  Tue Mar 25 15:41:47 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 25 Mar 2008 15:41:47 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: question about WS client accessing
	local wsdl
Message-ID: <20248540.1206474107758.JavaMail.jboss@colo-br-02.atl.jboss.com>

Have you tried something like this:

URL x = Thread.currentThread().getContextClassLoader().findResource(WSDL_NAME);

where WSDL_NAME is the relative path to the file within the JAR.

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

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


From do-not-reply at jboss.com  Wed Mar 26 02:10:00 2008
From: do-not-reply at jboss.com (foongkim)
Date: Wed, 26 Mar 2008 02:10:00 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - EndPoint problems.. please help
Message-ID: <13271537.1206511800227.JavaMail.jboss@colo-br-02.atl.jboss.com>

hi, i have this Web Service pojo which using annotation method. 

After i have deploy to my production server (IP:182.123.1.10) and the endpoint display like this
http://localhost.localdomain:8080/myWebApp/myWebServicemethod

the host name part [localhost.localdomain] seems is not right.. and i want to change it.. how can i do that?? 

I have search all the configuration file in my jBoss 4.2 and i couldn't find any related tag to modify this.

If i go to http://182.123.1.10:8080/jbossws/ under the "Access JMX VIew" - JBoss Server - Web Service, 

i can see the exact value for host which is "localhost.localdomain" and i can not change it..

please help.

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

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


From do-not-reply at jboss.com  Wed Mar 26 03:26:55 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 26 Mar 2008 03:26:55 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: EndPoint problems.. please help
Message-ID: <9466250.1206516415298.JavaMail.jboss@colo-br-02.atl.jboss.com>

>From the jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml


  | <!--
  |         The WSDL, that is a required deployment artifact for an endpoint, has a <soap:address>
  |         element which points to the location of the endpoint. JBoss supports rewriting of that SOAP address.
  |       
  |         If the content of <soap:address> is a valid URL, JBossWS will not rewrite it unless 'modifySOAPAddress' is true.
  |         If the content of <soap:address> is not a valid URL, JBossWS will rewrite it using the attribute values given below.
  |         
  |         If 'webServiceHost' is not set, JBossWS uses requesters protocol host when rewriting the <soap:address>.
  |     -->
  |     <property name="webServiceHost">${jboss.bind.address}</property>
  |     <property name="modifySOAPAddress">true</property>
  | 
  |     <!-- 
  |       Set these properties to explicitly define the ports that will be used for rewriting the SOAP address.
  |       Otherwise the ports will be identified by querying the list of installed connectors. 
  |       If multiple connectors are found the port of the first connector is used.
  |       <property name="webServiceSecurePort">8443</property>
  |       <property name="webServicePort">8080</property>
  |     -->
  | 
  | 

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

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


From do-not-reply at jboss.com  Wed Mar 26 03:49:16 2008
From: do-not-reply at jboss.com (kk1107)
Date: Wed, 26 Mar 2008 03:49:16 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Deployment failure
Message-ID: <22711197.1206517756348.JavaMail.jboss@colo-br-02.atl.jboss.com>

Please let me know how did you solve this problem. I am facing similar problem. thanks

~Samy

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

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


From do-not-reply at jboss.com  Wed Mar 26 04:05:53 2008
From: do-not-reply at jboss.com (foongkim)
Date: Wed, 26 Mar 2008 04:05:53 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: EndPoint problems.. please help
Message-ID: <1435804.1206518753994.JavaMail.jboss@colo-br-02.atl.jboss.com>

got it.....

thank you so much!

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

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


From do-not-reply at jboss.com  Wed Mar 26 09:11:32 2008
From: do-not-reply at jboss.com (jacobsm)
Date: Wed, 26 Mar 2008 09:11:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Providing your own wsdl instead of
	the generated one.
Message-ID: <31265254.1206537092874.JavaMail.jboss@colo-br-02.atl.jboss.com>

ngtdave and PeterJ:

Thank you for this topic.  It was quite helpful.

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

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


From do-not-reply at jboss.com  Wed Mar 26 09:16:04 2008
From: do-not-reply at jboss.com (ngtdave)
Date: Wed, 26 Mar 2008 09:16:04 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Providing your own wsdl instead of
	the generated one.
Message-ID: <13931223.1206537364231.JavaMail.jboss@colo-br-02.atl.jboss.com>

Glad to have helped. :)

"jacobsm" wrote : ngtdave and PeterJ:
  | 
  | Thank you for this topic.  It was quite helpful.

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

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


From do-not-reply at jboss.com  Wed Mar 26 11:11:44 2008
From: do-not-reply at jboss.com (kkkasper)
Date: Wed, 26 Mar 2008 11:11:44 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Connection refused
Message-ID: <7978549.1206544304084.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello 

I have a problem. When I envoke a webservice call on a weblogic 8 from within jboss i get a connection refused error. 
Calling it from OUTSIDE jboss everything works fine (using the same class for doing the calling)
, but when run inside JBOSS (that is being run as part of executing a webservice call on the jboss), it refuses 
to do the call to the weblogic server. (see stack trace below)

I've tried connecting to the WS url using a URL object just to see if that was possible and I 
was able to read and output to the screen the full wsdl file. However, looking at the stack trace, it looks 
as though its the call thats failing.. but i don't know..

I'm using axis2 for the webservice call which nicely generated code based on the service's wsdl file.


I hope someone has a clue as what I have done wrong. I'm a rookie both at jboss and WS for the moment ;-)

many thanks!
K

I'm running 

14:48:19,203 INFO  [Server] Starting JBoss (MX MicroKernel)...
14:48:19,234 INFO  [Server] Release ID: JBoss [Zion] 4.0.3RC1 (build: CVSTag=JBoss_4_0_3_RC1 date=200506260723)
14:48:19,234 INFO  [Server] Home Dir: C:\jboss-4.0.3RC1
14:48:19,234 INFO  [Server] Home URL: file:/C:/jboss-4.0.3RC1/
14:48:19,234 INFO  [Server] Library URL: file:/C:/jboss-4.0.3RC1/lib/
14:48:19,234 INFO  [Server] Patch URL: null
14:48:19,234 INFO  [Server] Server Name: default
14:48:19,234 INFO  [Server] Server Home Dir: C:\jboss-4.0.3RC1\server\default
14:48:19,234 INFO  [Server] Server Home URL: file:/C:/jboss-4.0.3RC1/server/default/
14:48:19,234 INFO  [Server] Server Data Dir: C:\jboss-4.0.3RC1\server\default\data
14:48:19,250 INFO  [Server] Server Temp Dir: C:\jboss-4.0.3RC1\server\default\tmp
14:48:19,250 INFO  [Server] Server Config URL: file:/C:/jboss-4.0.3RC1/server/default/conf/
14:48:19,250 INFO  [Server] Server Library URL: file:/C:/jboss-4.0.3RC1/server/default/lib/
14:48:19,250 INFO  [Server] Root Deployment Filename: jboss-service.xml
14:48:19,250 INFO  [Server] Starting General Purpose Architecture (GPA)...
14:48:20,437 INFO  [ServerInfo] Java version: 1.6.0_01,Sun Microsystems Inc.
14:48:20,437 INFO  [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.6.0_01-b06,Sun Microsystems Inc.
14:48:20,437 INFO  [ServerInfo] OS-System: Windows XP 5.1,x86
14:48:21,312 INFO  [Server] Core system initialized


and here is the stack trace

14:50:12,109 INFO  [STDOUT] calling http://10.xxx.xxx.xxx:7001/Doc/webservice/Document.jws?WSDL
14:50:17,703 INFO  [STDOUT] java.rmi.RemoteException: SOAP Fault:javax.xml.rpc.soap.SOAPFaultException
Detail:

 <bea_fault:stacktrace   xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">java.net.ConnectException: Connection refused: connect
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:193)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
        at java.net.Socket.connect(Socket.java:519)
        at java.net.Socket.connect(Socket.java:469)
        at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:388)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:515)
        at sun.net.www.http.HttpClient.(HttpClient.java:233)
        at sun.net.www.http.HttpClient.New(HttpClient.java:306)
        at sun.net.www.http.HttpClient.New(HttpClient.java:318)
        at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:792)
        at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:733)
        at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:658)
        at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:836)
        at weblogic.webservice.binding.http11.Http11ClientBinding.send(Http11ClientBinding.java:399)
        at weblogic.webservice.core.handler.ClientHandler.handleRequest(ClientHandler.java:37)
        at weblogic.webservice.core.HandlerChainImpl.handleRequest(HandlerChainImpl.java:143)
        at weblogic.webservice.core.ClientDispatcher.send(ClientDispatcher.java:231)
        at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:143)
        at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
        at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
        at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:303)
        at weblogic.jws.proxies.DocumentBatchSoap_Stub.updateBatchStatus(DocumentBatchSoap_Stub.java:482)
        at weblogic.jws.proxies.DocumentBatchSoap_Stub.updateBatchStatus(DocumentBatchSoap_Stub.java:504)
 ...
       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:597)
        at org.jboss.invocation.Invocation.performCall(Invocation.java:345)
        at org.jboss.ejb.MessageDrivenContainer$ContainerInterceptor.invoke(MessageDrivenContainer.java:475)
        at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:185)
        at org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor.invoke(MessageDrivenInstanceInterceptor.java:87)
        at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:48)
        at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:105)
        at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:300)
        at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:166)
        at org.jboss.ejb.plugins.RunAsSecurityInterceptor.invoke(RunAsSecurityInterceptor.java:94)
        at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:192)
        at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
        at org.jboss.ejb.MessageDrivenContainer.internalInvoke(MessageDrivenContainer.java:389)
        at org.jboss.ejb.Container.invoke(Container.java:873)
        at org.jboss.ejb.plugins.jms.JMSContainerInvoker.invoke(JMSContainerInvoker.java:1090)
        at org.jboss.ejb.plugins.jms.JMSContainerInvoker$MessageListenerImpl.onMessage(JMSContainerInvoker.java:1392)
        at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:256)
        at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:904)
        at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:160)
        at org.jboss.mq.SpySession.run(SpySession.java:333)
        at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:180)
        at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
        at java.lang.Thread.run(Thread.java:619)
</bea_fault:stacktrace>
; nested exception is:
        javax.xml.rpc.soap.SOAPFaultException

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

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


From do-not-reply at jboss.com  Wed Mar 26 11:47:52 2008
From: do-not-reply at jboss.com (zach.mabe@cox.com)
Date: Wed, 26 Mar 2008 11:47:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Overriding InvocationHandlerFactory
Message-ID: <16225682.1206546472505.JavaMail.jboss@colo-br-02.atl.jboss.com>

Particulars:  Jboss AS 4.2.2.GA, JBossWS native 2.0.3.GA with JSE endpoints.


I am trying to implement my own InvocationHandlerFactory so that I can implement my own InvocationHandler instead of the DefaultInvocationHandlerJAXWS.   

To do so, I've created my implementations of the factory and the handler.  These classes are in WEB-INF/classes directory of the WAR file.

In the base dir of the WAR. I've created the file 
META-INF\services\org.jboss.wsf.spi.invocation.InvocationHandlerFactory
with the name of my factory class as the only line.

I also have this same file in the classes directory of the WEB-INF directory so its path   looks like
WEB-INF/classes/META-INF/services/org.jboss.wsf.spi.invocation.InvocationHandlerFactory


Regardless, the ServiceLoader keeps finding service file in jboss-4.2.2.GA-Cox-AS/server/default/lib/jbossws-jboss42.jar.

So the question is...am I supposed to be able to override that service definition?  If so, can I configure the classloader to find the service file in my war before looking in the lib directory without screwing stuff up?

Thanks
Zach





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

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


From do-not-reply at jboss.com  Thu Mar 27 09:54:55 2008
From: do-not-reply at jboss.com (yogeshkb)
Date: Thu, 27 Mar 2008 09:54:55 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Generating XSDs and WSDLs as separate
	files
Message-ID: <17530026.1206626095095.JavaMail.jboss@colo-br-02.atl.jboss.com>

HI,

I wanted to use the wsprovide tool to generate XSD schema and WSDL for a webservice as two different files. The default mechanism generates the schema embedded inside the wsdl. Is there any options to generate these artifacts into separate files?

Any help on this pls?

Regards,
Yogesh

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

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


From do-not-reply at jboss.com  Thu Mar 27 10:46:55 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Thu, 27 Mar 2008 10:46:55 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Generating XSDs and WSDLs as
	separate files
Message-ID: <10388181.1206629215660.JavaMail.jboss@colo-br-02.atl.jboss.com>

No, there isn't such option :(

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

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


From do-not-reply at jboss.com  Thu Mar 27 11:56:22 2008
From: do-not-reply at jboss.com (r12345_2003)
Date: Thu, 27 Mar 2008 11:56:22 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - java.lang.IllegalStateException: Cannot
	obtain endpoint meta
Message-ID: <32868343.1206633382901.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi All,

I am very new to JBoss web services and am trying to create a sample web service application using JBoss WS. Here is what i have done so far:

1) Created a POJO for the web service. Its source code is as follows:

package test.webservices;
  | 
  | import javax.jws.WebMethod;
  | import javax.jws.WebParam;
  | import javax.jws.WebService;
  | import javax.jws.soap.SOAPBinding;
  | 
  | 
  | @WebService(name = "CalculatorService")
  | public class CalculatorService
  | {
  |     @WebMethod
  |      public Integer add(@WebParam(name = "arg1")Integer arg1, at WebParam(name = "arg2") Integer arg2){
  |         return arg1+arg2;
  |     }
  | }
  | 

2) Created entry in web.xml. My web.xml looks like the following:

  | <?xml version="1.0" encoding="UTF-8"?>
  | <web-app version="2.4" 
  | 	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://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
  | 
  |     <servlet>
  |         <servlet-name>CalculatorService</servlet-name>
  |         <servlet-class>test.webservices.CalculatorService</servlet-class>
  |     </servlet>
  | 
  |     <servlet-mapping>
  |         <servlet-name>CalculatorService</servlet-name>
  |         <url-pattern>/CalculatorService</url-pattern>
  |     </servlet-mapping>
  |   
  | </web-app>
  | 

3) Deployed the project as a war file.  However when i start the server, i see the following exception trace:
java.lang.IllegalStateException: Cannot obtain endpoint meta data
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleWSDLRequest(RequestHandlerImpl.java:520)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doGet(RequestHandlerImpl.java:144)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:126)
  | 	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.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:595)
  |  

When i open the link  http://localhost:8080/jbossws/services, I can see an end point name and end point address. However when i click on the WSDL link, i do not see the WSDL.

Can someone help me in figuring out what might be the issue?

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

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


From do-not-reply at jboss.com  Thu Mar 27 13:46:59 2008
From: do-not-reply at jboss.com (bensonfungjava)
Date: Thu, 27 Mar 2008 13:46:59 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: How to change http to https in
	wsdlsoap:address on WSDL
Message-ID: <9900145.1206640019225.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I also have the same problem and using the same config.  Unforunately, it doesn't work.  Please advise

Thanks
Benson

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

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


From do-not-reply at jboss.com  Fri Mar 28 07:05:29 2008
From: do-not-reply at jboss.com (nareshshah)
Date: Fri, 28 Mar 2008 07:05:29 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - need sample program for web service
Message-ID: <14081300.1206702329405.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am new to WS and  using jboss-portal-2.6.3.GA server. Does this server support the WS ? Can i get link where i can start with sample WS program ?

Actually i want WS using EJB ...
Thankx in advance.

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

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


From do-not-reply at jboss.com  Fri Mar 28 10:09:20 2008
From: do-not-reply at jboss.com (rruppel)
Date: Fri, 28 Mar 2008 10:09:20 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - How to Define WebService URL?
Message-ID: <4300263.1206713360413.JavaMail.jboss@colo-br-02.atl.jboss.com>

Well,

the problem is that the Jboss 4.2.2 changed the default webservice url, to:

/ProjectName-JarName/WebserviceName

while at Jboss 4.0.5 tbe default was:

/JarName/WebServiceName

so I want to redefine the Url of my WebServices  

I saw this topic and it seems that its possible, but it doenst explain how:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=52977&view=previous

thanks for any help

regards

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

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


From do-not-reply at jboss.com  Fri Mar 28 11:37:53 2008
From: do-not-reply at jboss.com (marc.durand@agfa.com)
Date: Fri, 28 Mar 2008 11:37:53 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problems with multipart/related
	responses
Message-ID: <12288315.1206718673073.JavaMail.jboss@colo-br-02.atl.jboss.com>

I believe you are having the problem because Axis2 sends the a "start" parameter in the Content-Type and the value is not delimited by < and >.  I.e., it should be this:

start="<0.urn:uuid:98BB2CA94931E2B9C21204623668218 at apache.org>"

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

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


From do-not-reply at jboss.com  Fri Mar 28 15:58:06 2008
From: do-not-reply at jboss.com (rinconmaradona)
Date: Fri, 28 Mar 2008 15:58:06 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: No way to write a working client
Message-ID: <29990863.1206734286476.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello GenesisD, I'm having the exact same problem, and the exact same mental issues, can you help me?

How did you solve this??

Thx!!

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

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


From do-not-reply at jboss.com  Sat Mar 29 12:34:03 2008
From: do-not-reply at jboss.com (whitexos12)
Date: Sat, 29 Mar 2008 12:34:03 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - How to create a Web Service in JBoss
Message-ID: <8877929.1206808443833.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I am new to JBoss and mostly work with BEA and Oracle AS. I just downloaded jboss-4.2.2.GA. Now how do I deploy a Web Service are there any special kinds to create an ear for a Web Service. As I just have a simple HelloWorld program that I need to expose it as a Web Service and deploy it on JBoss but don't know what commands do I need to create a Web Service ear out of it and how to deploy it on the server. 

Can someone please provide a simple example step by step to build and deploy a Web Service in JBoss.

As in oracle I can use the following to build an ear for a Web Service

<target name="assemble-webservice" depends="setup">
  |     <echo message="-----> Assembling the service ear file." />
  |     <copy todir="${out.dir}/war/WEB-INF/lib">
  |       <fileset dir="${out.lib}">
  |            <include name="*.jar"/>
  |       </fileset>
  |     </copy>
  |     <oracle:topDownAssemble appName="${app.name}"
  |     wsdl="${wsdl.file}" className="${implementaion.class}"
  |     input="${bld.webservice.dir}" output="${out.dir}"
  |     ear="${lib.dir}/${app.name}_service.ear">
  |       <!--fileset refid="resources" /-->		
  |     </oracle:topDownAssemble>
  |   </target>

and in BEA can use the following:

<servicegen
  |        destEar="${build}"
  |        warName="helloWorldService.war">
  |        <service
  |                 javaClassComponents="com.xx.ab.webservice.helloWorldWebservice"
  |                 targetNamespace="http://xmlns.xx.com/ab/helloWorldService"
  |                 serviceName="HelloWorldService"
  |                 serviceURI="/helloWorldService"
  |                 style="document"
  |                 protocol="http"
  |                 expandMethods="True">
  |                 <handlerChain name="ExpressChain" handlers="com.xx.ab.handler.SOAPHandler"/>
  |        </service>
  |       <classpath>
  |         <pathelement path="${classes}"/>
  |         <pathelement path="${lib}/dynamic/*.jar"/>
  |       </classpath>
  |      </servicegen>

Now how do I do it in JBoss. What commands to use to create an ear for a Web Service. Any small tutorial will really help alot. Any help is really appreciated.

Thanks

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

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


From do-not-reply at jboss.com  Sat Mar 29 13:42:56 2008
From: do-not-reply at jboss.com (sajhak)
Date: Sat, 29 Mar 2008 13:42:56 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - javaEE5 JAX-WS web services - JBOSS
	4.2.2
Message-ID: <20891630.1206812576054.JavaMail.jboss@colo-br-02.atl.jboss.com>

hi , 

can i deploy javaEE5 conformed web services (JAX-WS web services , not JAX-RPC web services ) in JBOSS 4.2.2 ? 

so can i managed the configuration only with anotations rather than any configuration files ? 

also , if anybody have sample code of a simple webservice endpoint and a client , pls send me or give me a link..

Saji

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

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


From do-not-reply at jboss.com  Sat Mar 29 14:18:10 2008
From: do-not-reply at jboss.com (sajhak)
Date: Sat, 29 Mar 2008 14:18:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBoss & JAX-WS. Beginners Guide
Message-ID: <28791590.1206814690625.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hey JGF1 , 

i m having the exact same problem as i refer the same book u have read.
did you sort it out the problem ? could you please tell me the modifications needed to run that example correctly ?

im using JBOSS 4.2.2 GA too.

thanks
saji



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

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


From do-not-reply at jboss.com  Sat Mar 29 15:46:33 2008
From: do-not-reply at jboss.com (whitexos12)
Date: Sat, 29 Mar 2008 15:46:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Deployment failure
Message-ID: <31489214.1206819993086.JavaMail.jboss@colo-br-02.atl.jboss.com>

"kk1107" wrote : Please let me know how did you solve this problem. I am facing similar problem. thanks
  | 
  | ~Samy


I too am getting the same error can someone please tell how to solve this issue it's very important any help is appreciated.

Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 2 counts of
  | IllegalAnnotationExceptions
  | java.util.List is an interface, and JAXB can't handle interfaces.
  |         this problem is related to the following location:
  |                 at java.util.List
  | java.util.List does not have a no-arg default constructor.
  |         this problem is related to the following location:
  |                 at java.util.List
  | 
  |         at com.sun.xml.bind.v2.runtime.IllegalAnnotationsException$Builder.check
  | (IllegalAnnotationsException.java:102)

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

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


From do-not-reply at jboss.com  Sat Mar 29 15:55:24 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Sat, 29 Mar 2008 15:55:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: javaEE5 JAX-WS web services - JBOSS
	4.2.2
Message-ID: <9146392.1206820524076.JavaMail.jboss@colo-br-02.atl.jboss.com>

yes

yes

(Did you read the documentation? http://jbws.dyndns.org/mediawiki/index.php?title=JBossWS)

See also http://www.jboss.com/index.html?module=bb&op=viewtopic&t=131079

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

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


From do-not-reply at jboss.com  Sat Mar 29 15:58:54 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Sat, 29 Mar 2008 15:58:54 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: How to create a Web Service in JBoss
Message-ID: <18045115.1206820734685.JavaMail.jboss@colo-br-02.atl.jboss.com>

I assume that you are asking about era packaging because your web service also an EJB. If that is correct, all you really need to do is package the EJB class in a jar file and copy the jar file to server/xxx/deploy. Then you should be able to view the web service using http://localhost:8080/jbossws/services.

Also, see the documentation at http://jbws.dyndns.org/mediawiki/index.php?title=JBossWS

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

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


From do-not-reply at jboss.com  Sat Mar 29 16:02:19 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Sat, 29 Mar 2008 16:02:19 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Deployment failure
Message-ID: <16246493.1206820939384.JavaMail.jboss@colo-br-02.atl.jboss.com>

whitexos12, the error you are getting:

java.util.List is an interface, and JAXB can't handle interfaces.

means that your web service is either taking a List as a parameter or returning a List. That is not allowed because List is not a class, it is an interface. You have to change the parameter (or return type) to a class that implements List, such as ArrayList.

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

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


From do-not-reply at jboss.com  Sat Mar 29 17:06:13 2008
From: do-not-reply at jboss.com (whitexos12)
Date: Sat, 29 Mar 2008 17:06:13 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Deployment failure
Message-ID: <18716989.1206824773967.JavaMail.jboss@colo-br-02.atl.jboss.com>

"kk1107" wrote : Please let me know how did you solve this problem. I am facing similar problem. thanks
  | 
  | ~Samy


I too am getting the same error can someone please tell how to solve this issue it's very important any help is appreciated.

Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 2 counts of
  | IllegalAnnotationExceptions
  | java.util.List is an interface, and JAXB can't handle interfaces.
  |         this problem is related to the following location:
  |                 at java.util.List
  | java.util.List does not have a no-arg default constructor.
  |         this problem is related to the following location:
  |                 at java.util.List
  | 
  |         at com.sun.xml.bind.v2.runtime.IllegalAnnotationsException$Builder.check
  | (IllegalAnnotationsException.java:102)

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

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


From do-not-reply at jboss.com  Sun Mar 30 07:42:29 2008
From: do-not-reply at jboss.com (HTCPrasad)
Date: Sun, 30 Mar 2008 07:42:29 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Ejb3.0 Stateless session bean as
	webservice in jboss4.2.2
Message-ID: <10442022.1206877349876.JavaMail.jboss@colo-br-02.atl.jboss.com>

I had created three files like
 
SimpleWS.java

package com.htc.htcws;

import javax.jws.WebService;
import javax.jws.WebMethod;
import java.rmi.Remote;
import java.rmi.RemoteException;
import javax.jws.soap.SOAPBinding;
import javax.jws.soap.SOAPBinding.Style;


@WebService
@SOAPBinding(style=Style.RPC)
public interface SimpleWS extends Remote
{
  @WebMethod
   public  String greet(String person) 
            throws RemoteException;
}

SimpleWSBean.java
package com.htc.htcws; 

import javax.jws.WebService;
import javax.jws.WebMethod;
import javax.ejb.Remote;
import javax.ejb.Stateless;
import javax.jws.soap.SOAPBinding;
import javax.jws.soap.SOAPBinding.Style;
      
@Stateless
@Remote(SimpleWS.class)
@WebService(endpointInterface="com.htc.htcws.SimpleWS")
@SOAPBinding(style=SOAPBinding.Style.RPC)
public class SimpleWSBean implements SimpleWS
{
  @WebMethod
  public  String greet(String person) 
  {
   return "Hi "+person+" all Good Wishes for Tamil New Year's Day";
  }
  
}

SimpleWSClient.java

package com.htc.htcws;
import javax.xml.rpc.ServiceFactory;
import javax.xml.rpc.Service;
import javax.xml.namespace.QName;
import java.net.URL;
import org.apache.log4j.Logger;
import org.apache.log4j.FileAppender;
import org.apache.log4j.HTMLLayout;
import javax.xml.transform.stream.StreamSource;
import javax.xml.ws.Dispatch;
import javax.xml.ws.Service.Mode;
import javax.xml.ws.Response;
import java.io.StringReader;

public class SimpleWSClient
{ 
  static Logger logger;

  public static void main(String[] args)
  {   
    final String _NAMESPACE = "http://htcws.htc.com/";
    final String _SERVICE = "SimpleWSBeanService";
  
   
  try
  {
   logger = Logger.getRootLogger();
    logger.addAppender(new FileAppender(new HTMLLayout(),
                                       "mylog1.log",true));  
  
  
   URL url =  
     new URL("http://127.0.0.1:10080/simpws/SimpleWSBean?wsdl");
 
    QName qName = new QName(_NAMESPACE,_SERVICE);
    if(args.length!=1)
 
    {
      System.out.print("Give the person-name as args[0]");
      System.exit(1);
    }  
    
    

    ServiceFactory sFactory = ServiceFactory.newInstance();
    
    Service service = sFactory.createService(url,qName);

    System.out.println(".."+service);
  
    SimpleWS invoker =
            (SimpleWS)service.getPort(SimpleWS.class); 
    System.out.println("##"+invoker);

    String res = invoker.greet(args[0]);
    
    System.out.println("Response is::"+res);
   }
   catch(Exception ex)
   {
       System.err.println("Caught the exception as"+ex);
   }
  }

}

the bean getting deployed.but whie running client the error is

java:
     [java] ..org.jboss.ws.core.jaxrpc.client.ServiceImpl at b8c8e6
     [java] ##org.jboss.ws.core.jaxrpc.client.CallImpl at 1542a75
     [java] Caught the exception asjava.rmi.RemoteException: Call invocation failed; nested exception is: 
     [java] 	java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage


    My os is windows vistas ,browser is firefox beta4.0

can you please suggest where the error is or how to use Dispatch,Response objects here
mail is  dtrprasad at gmail.com
                                            

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

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


From do-not-reply at jboss.com  Sun Mar 30 17:26:42 2008
From: do-not-reply at jboss.com (sajhak)
Date: Sun, 30 Mar 2008 17:26:42 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: javaEE5 JAX-WS web services - JBOSS
	4.2.2
Message-ID: <2391723.1206912402484.JavaMail.jboss@colo-br-02.atl.jboss.com>

   

   thanks for the link Peter.

when i deploy the service endpoint , it gives an error saying something relevent to JAXB2.0 .... 

The service implementation is as folows is as follows.


  | public class SayHelloWebServiceBean implements SayHelloWebService {
  | 
  |     public String sayHello(String name) {
  |         return "Hello , welcome " + name;
  |     }
  | }
  | 


i feel the error is  because my methods parameters and return types are "String" . is that the case ?

if so how should i correct that ?

Is this an issue with  JBOSS (application server) ? because , as i remember right , in Sun Application server , this method wont give errors..

pls help

thanks in advance
Saji

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

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


From do-not-reply at jboss.com  Sun Mar 30 17:29:38 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Sun, 30 Mar 2008 17:29:38 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Ejb3.0 Stateless session bean as
	webservice in jboss4.2.
Message-ID: <9080899.1206912578680.JavaMail.jboss@colo-br-02.atl.jboss.com>

What version of JBossAS are you using? And did you install any other version of JBossWS into JBossAS?

Are you by any chance using JDK 6? If so, see http://jira.jboss.org/jira/browse/JBWS-1439.

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

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


From do-not-reply at jboss.com  Sun Mar 30 17:51:43 2008
From: do-not-reply at jboss.com (anacarda)
Date: Sun, 30 Mar 2008 17:51:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Loading a file into an InputStream
	within webservice code
Message-ID: <3243539.1206913903600.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I have a webservice I have created, and it works fine.

However, I am now wanting to load a file (xslt file in my case), to pass it through to Xalan for transformation.

However... I do not know how to load the file.

The main issue I am having, is I don't know where the file should be...

I am currently using getResourceAsStream() function... is this correct?:
InputStream loInputXSLT = getClass().getResourceAsStream("/xslt/file.xslt");

Class is defined as the following:
@Name("myWebService")
  | @Stateless
  | @WebService(name = "MyWeb", serviceName = "MyWeb")
  | public class MyWeb implements MyWebRemote {

I am also using the seam framework, but I don't think this is a seam specific question, so I am asking it here :)

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

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


From do-not-reply at jboss.com  Sun Mar 30 18:11:33 2008
From: do-not-reply at jboss.com (anacarda)
Date: Sun, 30 Mar 2008 18:11:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: How to Define WebService URL?
Message-ID: <7682245.1206915093857.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am also wanting to know how this can be done

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

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


From do-not-reply at jboss.com  Sun Mar 30 21:11:46 2008
From: do-not-reply at jboss.com (wiggy)
Date: Sun, 30 Mar 2008 21:11:46 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - help completely stuck trying to access
	an EJB3 WS - please h
Message-ID: <23698026.1206925906875.JavaMail.jboss@colo-br-02.atl.jboss.com>

Could someone please help me - really confused about how get JBOSS WS working properly

trying to get a seam application exposed with web services.  Tried to write a simple WS test and came unstuck.  I need help as this is now holding me back and its doing my head in.  I have another developer stuck waiting for me to expose a service.

here goes.

1.  created an EAR based server.  Here is the webservice endpoint class in the wstest2-ejb project within the EAR.


  | package org.domain.wstest2.webservices;
  | 
  | import java.util.List;
  | 
  | import javax.ejb.Stateless;
  | import javax.jws.WebMethod;
  | import javax.jws.WebResult;
  | import javax.jws.WebService;
  | 
  | 
  | import org.jboss.seam.Component;
  | 
  | @Stateless (name="HelloService")
  | @WebService (
  | 	         name="HelloServiceWS", 
  | 	         serviceName="HelloService" )
  | public class HelloServiceBean implements HelloServiceRemote
  | {
  | 	@WebMethod (operationName="sayHello")
  | 	@WebResult (name="helloResult")
  | 	public String hello ()
  | 	{
  | 		return "hello World";
  | 	}
  | }
  | 
  | 

as it was going to be a seam based test - i created in the META-INF the following standard-jaxws-endpoint-config.xml


  | <?xml version="1.0" encoding="UTF-8"?>
  | <!-- webservice seam SOAP handler profile -->
  | <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>Seam WebService Endpoint</config-name>
  | 		<pre-handler-chains>
  | 			<javaee:handler-chain>
  | 				<javaee:protocol-bindings>##SOAP11_HTTP</javaee:protocol-bindings>
  | 				<javaee:handler>
  | 					<javaee:handler-name>SOAP Request Handler</javaee:handler-name>
  | 					<javaee:handler-class>org.jboss.seam.webservice.SOAPRequestHandler</javaee:handler-class>
  | 				</javaee:handler>
  | 			</javaee:handler-chain>
  | 		</pre-handler-chains>
  | 	</endpoint-config>
  | </jaxws-config>
  | 

so far so good - deploy the EAR to jboss4.2.2.  checked the localhost:8080/jbossws and checked where the generated WSDL is stored 

heres what it gives me 


  | http://127.0.0.1:8080/wstest2-ear-wstest2-ejb/HelloService?wsdl 
  |  
  | 
  | 
  | heres is the generated WSDL 
  | 
  | 
  |   | 
  |   | 
  |   |  <definitions name="HelloService" targetNamespace="http://webservices.wstest2.domain.org/" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://webservices.wstest2.domain.org/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  |   | - <types>
  |   | - <xs:schema targetNamespace="http://webservices.wstest2.domain.org/" version="1.0" xmlns:tns="http://webservices.wstest2.domain.org/" xmlns:xs="http://www.w3.org/2001/XMLSchema">
  |   |   <xs:element name="sayHello" type="tns:sayHello" /> 
  |   |   <xs:element name="sayHelloResponse" type="tns:sayHelloResponse" /> 
  |   | - <xs:complexType name="sayHello">
  |   |   <xs:sequence /> 
  |   |   </xs:complexType>
  |   | - <xs:complexType name="sayHelloResponse">
  |   | - <xs:sequence>
  |   |   <xs:element minOccurs="0" name="helloResult" type="xs:string" /> 
  |   |   </xs:sequence>
  |   |   </xs:complexType>
  |   |   </xs:schema>
  |   |   </types>
  |   | - <message name="HelloServiceWS_sayHelloResponse">
  |   |   <part element="tns:sayHelloResponse" name="sayHelloResponse" /> 
  |   |   </message>
  |   | - <message name="HelloServiceWS_sayHello">
  |   |   <part element="tns:sayHello" name="sayHello" /> 
  |   |   </message>
  |   | - <portType name="HelloServiceWS">
  |   | - <operation name="sayHello" parameterOrder="sayHello">
  |   |   <input message="tns:HelloServiceWS_sayHello" /> 
  |   |   <output message="tns:HelloServiceWS_sayHelloResponse" /> 
  |   |   </operation>
  |   |   </portType>
  |   | - <binding name="HelloServiceWSBinding" type="tns:HelloServiceWS">
  |   |   <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /> 
  |   | - <operation name="sayHello">
  |   |   <soap:operation soapAction="" /> 
  |   | - <input>
  |   |   <soap:body use="literal" /> 
  |   |   </input>
  |   | - <output>
  |   |   <soap:body use="literal" /> 
  |   |   </output>
  |   |   </operation>
  |   |   </binding>
  |   | - <service name="HelloService">
  |   | - <port binding="tns:HelloServiceWSBinding" name="HelloServiceWSPort">
  |   |   <soap:address location="http://127.0.0.1:8080/wstest2-ear-wstest2-ejb/HelloService" /> 
  |   |   </port>
  |   |   </service>
  |   |   </definitions>
  |   | 
  | 
  | Then I got a little stuck.  I scouted round for stuff and entually got to the wsconsum.bat documentation to generate client artifacts.
  | 
  | can the wsconsume and generated the client stubs - and then imported them into my client project (I did this as an EJB3) so that i could use the dependency injection (or so i thought).
  | 
  | heres my EJB client 
  | 
  | 
  |   | package test;
  |   | 
  |   | import javax.ejb.Stateless;
  |   | import javax.xml.ws.WebServiceRef;
  |   | 
  |   | import org.domain.wstest2.webservices.*;
  |   | 
  |   | @Stateless
  |   | public class TestHelloBean implements TestHelloService, TestHelloServiceRemote 
  |   | {
  |   | 
  |   |                 //inject instance of generated service class from wsconsume
  |   | 	@WebServiceRef (HelloService.class)
  |   | 	private HelloService helloServiceEP;
  |   | 	
  |   | 	public String sayHello()
  |   | 	{
  |   |                                 //get WS from the End point
  |   | 		HelloServiceWS helloService = helloServiceEP.getHelloServiceWSPort();
  |   | 
  |   |                                 //call my simple method
  |   | 		String res = helloService.sayHello();
  |   | 		return res;
  |   | 		//return "hello";
  |   | 	}
  |   | }
  |   | 
  | 
  | I have a simple main method that does the ctx lookup to get a remote interface to my TestHelloBean  - this is run from the command line and i watch the error trace 
  | 
  | 
  |   | package test;
  |   | 
  |   | import java.util.Hashtable;
  |   | 
  |   | import javax.naming.InitialContext;
  |   | import org.domain.wstest2.webservices.*;
  |   | 
  |   | public class Test {
  |   | 
  |   | 	/**
  |   | 	 * @param args
  |   | 	 */
  |   | 	public static void main(String[] args) throws Exception
  |   | 	{
  |   | 
  |   | 		InitialContext ctx;
  |   | 		// TODO Auto-generated method stub
  |   | 
  |   | 		TestHelloServiceRemote test;
  |   | 
  |   | 		HelloService s = new HelloService();
  |   | 		HelloServiceWS  ws = s.getHelloServiceWSPort();
  |   | 		
  |   | 		
  |   | 			ctx = getInitialContext();
  |   | 
  |   | 			test = (TestHelloServiceRemote) ctx.lookup ("TestHelloBean/remote");
  |   | 			//String res = ws.sayHello();//test.sayHello();
  |   | 			String res = test.sayHello();			System.out.println ("test: returned " + res + " \n");
  |   | 
  |   | 	}
  |   | 
  |   | 	public static InitialContext getInitialContext() throws Exception
  |   | 	{
  |   | 	   Hashtable<String, String> props = getInitialContextProperties();
  |   | 	   return new InitialContext(props);
  |   | 	}
  |   | 
  |   | 	private static Hashtable<String,String> getInitialContextProperties()
  |   | 	{
  |   | 	   Hashtable <String, String> props = new Hashtable <String, String>();
  |   | 	   props.put("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory");
  |   | 	   props.put("java.naming.provider.url", "jnp://localhost:1099");
  |   | 	   props.put("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces");
  |   | 	   return props;
  |   | 	}
  |   | 
  |   | }
  |   | 
  |   | 
  | 
  | 
  | this gives me an error like this 
  | 
  | 
  | 
  |   | 
  |   | Exception in thread "main" javax.ejb.EJBException: javax.xml.ws.WebServiceException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
  |   | 	at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:63)
  |   | 	at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83)
  |   | 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
  |   | 	at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:304)
  |   | 	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
  |   | 	at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
  |   | 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
  |   | 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
  |   | 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
  |   | 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
  |   | Caused by: javax.xml.ws.WebServiceException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
  |   | 	at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:317)
  |   | 	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:255)
  |   | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164)
  |   | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
  |   | 	at $Proxy144.sayHello(Unknown Source)
  |   | 	at test.TestHelloBean.sayHello(TestHelloBean.java:18)
  |   | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  |   | 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
  |   | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
  |   | 	at java.lang.reflect.Method.invoke(Unknown Source)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
  |   | 	at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
  |   | 	at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
  |   | 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
  |   | 	at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:304)
  |   | 	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
  |   | 	at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
  |   | 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
  |   | 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
  |   | 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
  |   | 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
  |   | 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
  |   | 	at org.jboss.remoting.Client.invoke(Client.java:1634)
  |   | 	at org.jboss.remoting.Client.invoke(Client.java:548)
  |   | 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)
  |   | 	at $Proxy25.sayHello(Unknown Source)
  |   | 	at test.Test.main(Test.java:30)
  |   | 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)
  |   | 	at $Proxy25.sayHello(Unknown Source)
  |   | 	at test.Test.main(Test.java:30)
  |   | 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:67)
  |   | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:161)
  |   | 	at org.jboss.ws.core.CommonSOAP11Binding.createMessage(CommonSOAP11Binding.java:59)
  |   | 	at org.jboss.ws.core.CommonSOAPBinding.bindRequestMessage(CommonSOAPBinding.java:156)
  |   | 	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:289)
  |   | 	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:243)
  |   | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164)
  |   | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
  |   | 	at $Proxy144.sayHello(Unknown Source)
  |   | 	at test.TestHelloBean.sayHello(TestHelloBean.java:18)
  |   | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  |   | 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
  |   | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
  |   | 	at java.lang.reflect.Method.invoke(Unknown Source)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
  |   | 	at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
  |   | 	at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
  |   | 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
  |   | 	at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
  |   | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |   | 	at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:304)
  |   | 	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
  |   | 	at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
  |   | 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
  |   | 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
  |   | 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
  |   | 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
  |   | 
  | 
  | i've also tried this from the client (without the ejb lookup ) as follows (modified client)
  | 
  | 
  | 
  | 
  |   | 
  |   | 
  |   | ...
  |   | 		HelloService s = new HelloService();
  |   | 		HelloServiceWS  ws = s.getHelloServiceWSPort();		
  |   | 		
  |   | 			ctx = getInitialContext();
  |   | 
  |   | 			test = (TestHelloServiceRemote) ctx.lookup ("TestHelloBean/remote");
  |   | 
  |   | 			String res = ws.sayHello();			//String res = test.sayHello();
  |   | 			System.out.println ("test: returned " + res + " \n");
  |   | 
  | 
  | 
  | This also errors with this at the client side 
  | 
  | 
  |   | Exception in thread "main" javax.xml.ws.WebServiceException: No Content-type in the header!
  |   | 	at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:143)
  |   | 	at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:74)
  |   | 	at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:559)
  |   | 	at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:518)
  |   | 	at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:503)
  |   | 	at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:400)
  |   | 	at com.sun.xml.ws.client.Stub.process(Stub.java:235)
  |   | 	at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:120)
  |   | 	at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:230)
  |   | 	at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:210)
  |   | 	at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:103)
  |   | 	at $Proxy24.sayHello(Unknown Source)
  |   | 	at test.Test.main(Test.java:29)
  |   | 
  | 
  | and this at the server 
  | 
  | 
  |   | 02:06:11,100 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
  |   | 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:67)
  |   | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:207)
  |   | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:185)
  |   | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:389)
  |   | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272)
  |   | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189)
  |   | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122)
  |   | 	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.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)
  |   | 02:06:11,111 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:310)
  |   | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189)
  |   | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122)
  |   | 	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.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:67)
  |   | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:161)
  |   | 	at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:232)
  |   | 	at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:161)
  |   | 	at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:104)
  |   | 	at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:645)
  |   | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:430)
  |   | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272)
  |   | 	... 22 more
  |   | 02:06:11,121 ERROR [[HelloService]] Servlet.service() for servlet HelloService threw exception
  |   | 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:67)
  |   | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:161)
  |   | 	at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:232)
  |   | 	at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:161)
  |   | 	at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:104)
  |   | 	at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:645)
  |   | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:430)
  |   | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272)
  |   | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189)
  |   | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122)
  |   | 	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.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)
  |   | 
  |   | 

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

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


From do-not-reply at jboss.com  Sun Mar 30 21:38:20 2008
From: do-not-reply at jboss.com (HTCPrasad)
Date: Sun, 30 Mar 2008 21:38:20 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Ejb3.0 Stateless session bean as
	webservice in jboss4.2.
Message-ID: <2410864.1206927500962.JavaMail.jboss@colo-br-02.atl.jboss.com>

hello Sir,


   Thanks. i had changed jdk version and it is working.
 i will try this in jboss5.0.0 beta4.

                         with lots of regards
                         Prasad DTR

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

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


From do-not-reply at jboss.com  Sun Mar 30 21:56:22 2008
From: do-not-reply at jboss.com (wiggy)
Date: Sun, 30 Mar 2008 21:56:22 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: help completely stuck trying to
	access an EJB3 WS - plea
Message-ID: <33423490.1206928582090.JavaMail.jboss@colo-br-02.atl.jboss.com>

one more thing i saw some references to jsdk 1.6 (which i was using) vs 1.5.

i rest all my code and the server to 1.5 and redid the call - i still get the error (client side log trace - the server side shows no activity).  This is my client doing the ejb lookup call 

 
  | 	public static void main(String[] args) throws Exception
  | 	{
  | 
  | 		InitialContext ctx;
  | 		// TODO Auto-generated method stub
  | 
  | 		TestHelloServiceRemote test;
  | 
  | 		//HelloService s = new HelloService();
  | 		//HelloServiceWS  ws = s.getHelloServiceWSPort();
  | 		
  | 		
  | 			ctx = getInitialContext();
  | 
  | 			test = (TestHelloServiceRemote) ctx.lookup ("TestHelloBean/remote");
  | 
  | 			//String res = ws.sayHello();
  | 			String res = test.sayHello();
  | 	...	
  | 

which throws the error 

  | 
  | Exception in thread "main" javax.ejb.EJBException: javax.xml.ws.WebServiceException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
  | 	at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:63)
  | 	at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83)
  | 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
  | 	at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:304)
  | 	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
  | 	at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
  | 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
  | 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
  | 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
  | 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
  | Caused by: javax.xml.ws.WebServiceException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
  | 	at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:317)
  | 	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:255)
  | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164)
  | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
  | 	at $Proxy144.sayHello(Unknown Source)
  | 	at test.TestHelloBean.sayHello(TestHelloBean.java:18)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
  | 	at java.lang.reflect.Method.invoke(Unknown Source)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
  | 	at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
  | 	at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
  | 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
  | 	at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:304)
  | 	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
  | 	at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
  | 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
  | 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
  | 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
  | 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
  | 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
  | 	at org.jboss.remoting.Client.invoke(Client.java:1634)
  | 	at org.jboss.remoting.Client.invoke(Client.java:548)
  | 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)
  | 	at $Proxy0.sayHello(Unknown Source)
  | 	at test.Test.main(Test.java:30)
  | 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)
  | 	at $Proxy0.sayHello(Unknown Source)
  | 	at test.Test.main(Test.java:30)
  | 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:67)
  | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:161)
  | 	at org.jboss.ws.core.CommonSOAP11Binding.createMessage(CommonSOAP11Binding.java:59)
  | 	at org.jboss.ws.core.CommonSOAPBinding.bindRequestMessage(CommonSOAPBinding.java:156)
  | 	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:289)
  | 	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:243)
  | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164)
  | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
  | 	at $Proxy144.sayHello(Unknown Source)
  | 	at test.TestHelloBean.sayHello(TestHelloBean.java:18)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
  | 	at java.lang.reflect.Method.invoke(Unknown Source)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
  | 	at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
  | 	at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
  | 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
  | 	at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:304)
  | 	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
  | 	at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
  | 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
  | 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
  | 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
  | 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
  | 
  | 

if i change the code - just to call from the client (no ejb lookup) as follows 


  | 
  | 	public static void main(String[] args) throws Exception
  | 	{
  | 
  | 		InitialContext ctx;
  | 		// TODO Auto-generated method stub
  | 
  | 		TestHelloServiceRemote test;
  | 
  | 		HelloService s = new HelloService();
  | 		HelloServiceWS  ws = s.getHelloServiceWSPort();
  | 		
  | 		
  | 			ctx = getInitialContext();
  | 
  | 			test = (TestHelloServiceRemote) ctx.lookup ("TestHelloBean/remote");
  | 
  | 			String res = ws.sayHello();			//String res = test.sayHello();
  | 		
  | ...
  | 
  | 

i now get the following error


  | Exception in thread "main" javax.xml.ws.WebServiceException: Unable to load Provider: Failed to load javax.xml.ws.spi.Provider: com.sun.xml.ws.spi.ProviderImpl
  | 	at javax.xml.ws.spi.Provider.provider(Provider.java:98)
  | 	at javax.xml.ws.Service.<init>(Service.java:83)
  | 	at org.domain.wstest2.webservices.HelloService.<init>(HelloService.java:40)
  | 	at test.Test.main(Test.java:21)
  | Caused by: java.lang.IllegalStateException: Failed to load javax.xml.ws.spi.Provider: com.sun.xml.ws.spi.ProviderImpl
  | 	at javax.xml.ws.spi.ProviderLoader.loadProvider(ProviderLoader.java:96)
  | 	at javax.xml.ws.spi.Provider.provider(Provider.java:90)
  | 	... 3 more
  | Caused by: java.lang.ExceptionInInitializerError
  | 	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
  | 	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
  | 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
  | 	at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
  | 	at java.lang.Class.newInstance0(Class.java:350)
  | 	at java.lang.Class.newInstance(Class.java:303)
  | 	at javax.xml.ws.spi.ProviderLoader.loadProvider(ProviderLoader.java:91)
  | 	... 4 more
  | Caused by: javax.xml.ws.WebServiceException: Error creating JAXBContext for W3CEndpointReference. 
  | 	at com.sun.xml.ws.spi.ProviderImpl.getEPRJaxbContext(ProviderImpl.java:188)
  | 	at com.sun.xml.ws.spi.ProviderImpl.<clinit>(ProviderImpl.java:65)
  | 	... 11 more
  | Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 2 counts of IllegalAnnotationExceptions
  | Two classes have the same XML type name "address". Use @XmlType.name and @XmlType.namespace to assign different names to them.
  | 	this problem is related to the following location:
  | 		at com.sun.xml.ws.developer.MemberSubmissionEndpointReference$Address
  | 		at public com.sun.xml.ws.developer.MemberSubmissionEndpointReference$Address com.sun.xml.ws.developer.MemberSubmissionEndpointReference.addr
  | 		at com.sun.xml.ws.developer.MemberSubmissionEndpointReference
  | 	this problem is related to the following location:
  | 		at javax.xml.ws.wsaddressing.W3CEndpointReference$Address
  | 		at private javax.xml.ws.wsaddressing.W3CEndpointReference$Address javax.xml.ws.wsaddressing.W3CEndpointReference.address
  | 		at javax.xml.ws.wsaddressing.W3CEndpointReference
  | Two classes have the same XML type name "elements". Use @XmlType.name and @XmlType.namespace to assign different names to them.
  | 	this problem is related to the following location:
  | 		at com.sun.xml.ws.developer.MemberSubmissionEndpointReference$Elements
  | 		at public com.sun.xml.ws.developer.MemberSubmissionEndpointReference$Elements com.sun.xml.ws.developer.MemberSubmissionEndpointReference.referenceProperties
  | 		at com.sun.xml.ws.developer.MemberSubmissionEndpointReference
  | 	this problem is related to the following location:
  | 		at javax.xml.ws.wsaddressing.W3CEndpointReference$Elements
  | 		at private javax.xml.ws.wsaddressing.W3CEndpointReference$Elements javax.xml.ws.wsaddressing.W3CEndpointReference.referenceParameters
  | 		at javax.xml.ws.wsaddressing.W3CEndpointReference
  | 
  | 	at com.sun.xml.bind.v2.runtime.IllegalAnnotationsException$Builder.check(IllegalAnnotationsException.java:102)
  | 	at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:438)
  | 	at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(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
  | 

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

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


From do-not-reply at jboss.com  Sun Mar 30 22:29:52 2008
From: do-not-reply at jboss.com (whitexos12)
Date: Sun, 30 Mar 2008 22:29:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: How to create a Web Service in JBoss
Message-ID: <10577989.1206930592831.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I have a POJO that I need to expose it as a web service but can't find steps to follow to create a Web Service from creation to deployment, what commands to run to create a service any special configuration file needed etc.

Thanks

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

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


From do-not-reply at jboss.com  Sun Mar 30 22:19:40 2008
From: do-not-reply at jboss.com (wiggy)
Date: Sun, 30 Mar 2008 22:19:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: help completely stuck trying to
	access an EJB3 WS - plea
Message-ID: <5919965.1206929980307.JavaMail.jboss@colo-br-02.atl.jboss.com>

I also saw this discussion on the jira 

Same topic discussed here http://www.jboss.com/index.html?module=bb&op=viewtopic&t=99036 
[ Show ?? ] Stephan Heffner [16/Mar/07 05:59 AM] Same topic discussed here http://www.jboss.com/index.html?module=bb&op=viewtopic&t=99036 

I have tried putting the jboss-saaj.jar in the endorsed directory and restarted and cleaned everything - no soap (excuse pun)

any ideas- this is really holding me up 



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

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



From do-not-reply at jboss.com  Mon Mar 31 00:38:29 2008
From: do-not-reply at jboss.com (ds-crcpress)
Date: Mon, 31 Mar 2008 00:38:29 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - How to specify the truststore location
	for a web service cli
Message-ID: <25566164.1206938309444.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello,
 
I have the following scenario:
 
I am trying to call a Webservice that communicates via a secure socket (in other words, its located at https://hostname/path/to/service?wsdl).  When I call the Stateless Session Bean that has the proxy injected via @WebServiceRef, I get an odd UndeclaredThrowable exception.  It turns out it is because it cannot communicate with the webservice and is throwing an IOException which was not declared in the remote interface (thus trickling up and causing the UndeclaredThrowable rmi layer exception).
 
I created a unit test to try calling the web service outside of the EJB container, and got it working.  I had to specify the truststore location with a system property javax.net.ssl.trustStore and javax.net.ssl.trustStorePassword property (which keeps the IOException from being thrown).

Now comes the tricky part: how do I specify these properties for the JBoss application server?  I tried using the SystemProperties service, but it does not work--I still get the same exception.
 
Any other idea?
 
Thanks,
 
David

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

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


From do-not-reply at jboss.com  Mon Mar 31 04:55:22 2008
From: do-not-reply at jboss.com (r12345_2003)
Date: Mon, 31 Mar 2008 04:55:22 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Error in generating WSDL
Message-ID: <14906940.1206953722120.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi All,

I am trying to create a web service using a simple POJO. I have written the code for the Java class and made changes to the web.xml. I deployed the project as a war file. When I access the URL http://localhost:8080/jbossws/services, I can see the web service deployed. However when I click on the link for the web service, I cannot see the WSDL. I get an error message which says XML Parsing Error: no element found.
 
Is there any other configuration change required?

I am using Jboss 4.2.2.GA.

Please help!

Thanks in advance.

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

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


From do-not-reply at jboss.com  Mon Mar 31 11:04:35 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 31 Mar 2008 11:04:35 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: javaEE5 JAX-WS web services - JBOSS
	4.2.2
Message-ID: <19971761.1206975875137.JavaMail.jboss@colo-br-02.atl.jboss.com>

Please post the code for SayHelloWebService.

Also, you need an @WebService annotation.  See the discussion at http://www.jboss.com/index.html?module=bb&op=viewtopic&t=104843

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

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


From do-not-reply at jboss.com  Mon Mar 31 11:08:49 2008
From: do-not-reply at jboss.com (wiggy)
Date: Mon, 31 Mar 2008 11:08:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - help help! - cant get basic web service
	to work on 4.2.2, wh
Message-ID: <33187397.1206976129701.JavaMail.jboss@colo-br-02.atl.jboss.com>

hello again this is a related to the thread 

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=132718

i started the other night.  and discussed in 

http://jira.jboss.org/jira/browse/JBWS-1439

I have

1. installed the jbossws 3.01 native ontop of my as4.2.2 build.
2. server and the projects are set to run with jdk 1.5_09
3. my /lib/endorsed has bee updated with new copies of  
jaxb-api, jboss-jaxrpc, jboss-jaxws, jboss-jaxws-ext, jboss-saaj jars.
4.  my server/default/lib directory has been updated with copied jboss-jaxrpc, jboss-jaxws, jboss-jaxws-ext jars.
5. my /client dir has patched files 

I have an ejb ws i deploy as an ear (wstest2) and my simple WS appears in the localhost:8080/jbossws explorer. with its generated wsdl (no problems here).

however it fails when i try 

1.  try to use it with eclipse WS explorer.  I can fin it but when i invoke it i get an error - heres the server log.

 

  | 
  | 15:33:36,530 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
  | 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:217)
  | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:195)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:447)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:284)
  | 	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.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)
  | 15:33:36,530 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.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)
  | 	... 22 more
  | 15:33:36,540 ERROR [[HelloService]] Servlet.service() for servlet HelloService threw exception
  | 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)
  | 	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.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)
  | 15:36:05,184 INFO  [EJBContainer] STOPPED EJB: test.TestHelloBean ejbName: TestHelloBean
  | 15:36:05,184 WARN  [JmxKernelAbstraction] jboss.j2ee:jar=wsTestClient.jar,name=TestHelloBean,service=EJB3 is not registered
  | 15:36:05,455 INFO  [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer
  | 15:36:05,455 INFO  [JmxKernelAbstraction] installing MBean: jboss.j2ee:jar=wsTestClient.jar,name=TestHelloBean,service=EJB3 with dependencies:
  | 15:36:05,465 INFO  [EJBContainer] STARTED EJB: test.TestHelloBean ejbName: TestHelloBean
  | 15:36:05,475 INFO  [EJB3Deployer] Deployed: file:/E:/jboss/jboss-4.2.2.GA/server/default/deploy/wsTestClient.jar/
  | 16:04:04,138 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
  | 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:217)
  | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:195)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:447)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:284)
  | 	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.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)
  | 16:04:04,138 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.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)
  | 	... 22 more
  | 16:04:04,158 ERROR [[HelloService]] Servlet.service() for servlet HelloService threw exception
  | 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)
  | 	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.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)
  | 

2.  if i generate the client stubs for this wsdl using wsconsume and build test code to invoke the service i get 


  | 
  | xception in thread "main" javax.ejb.EJBException: javax.xml.ws.WebServiceException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
  | 	at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:63)
  | 	at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83)
  | 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
  | 	at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:304)
  | 	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
  | 	at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
  | 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
  | 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
  | 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
  | 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
  | Caused by: javax.xml.ws.WebServiceException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
  | 	at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404)
  | 	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314)
  | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
  | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
  | 	at $Proxy184.sayHello(Unknown Source)
  | 	at test.TestHelloBean.sayHello(TestHelloBean.java:18)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
  | 	at java.lang.reflect.Method.invoke(Unknown Source)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
  | 	at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
  | 	at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
  | 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
  | 	at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:304)
  | 	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
  | 	at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
  | 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
  | 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
  | 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
  | 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
  | 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
  | 	at org.jboss.remoting.Client.invoke(Client.java:1634)
  | 	at org.jboss.remoting.Client.invoke(Client.java:548)
  | 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)
  | 	at $Proxy0.sayHello(Unknown Source)
  | 	at test.Test.main(Test.java:30)
  | 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)
  | 	at $Proxy0.sayHello(Unknown Source)
  | 	at test.Test.main(Test.java:30)
  | 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.CommonSOAP11Binding.createMessage(CommonSOAP11Binding.java:59)
  | 	at org.jboss.ws.core.CommonSOAPBinding.bindRequestMessage(CommonSOAPBinding.java:158)
  | 	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:291)
  | 	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
  | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
  | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
  | 	at $Proxy184.sayHello(Unknown Source)
  | 	at test.TestHelloBean.sayHello(TestHelloBean.java:18)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
  | 	at java.lang.reflect.Method.invoke(Unknown Source)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
  | 	at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
  | 	at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
  | 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
  | 	at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:304)
  | 	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
  | 	at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
  | 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
  | 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
  | 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
  | 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
  | 


I desparetly need to get on with some real work and i cant move because i cant get the blessed ws to work - 

Brilliant ideas please???  what do i do to fix this problem


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

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


From do-not-reply at jboss.com  Mon Mar 31 11:20:23 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 31 Mar 2008 11:20:23 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: How to create a Web Service in JBoss
Message-ID: <15381152.1206976823742.JavaMail.jboss@colo-br-02.atl.jboss.com>

The documentation (I gave you the link earlier) contains everything you need to a POJO-based web service.

I also have a tutorial that includes creating a simple web service, but it is not free. I can give provide the URL, if you like.

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

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


From do-not-reply at jboss.com  Mon Mar 31 11:39:16 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 31 Mar 2008 11:39:16 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Error in generating WSDL
Message-ID: <7003604.1206977956859.JavaMail.jboss@colo-br-02.atl.jboss.com>

Please post the source code for your web service.

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

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


From do-not-reply at jboss.com  Mon Mar 31 13:39:40 2008
From: do-not-reply at jboss.com (rinconmaradona)
Date: Mon, 31 Mar 2008 13:39:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Writing a WS cliente
Message-ID: <32257516.1206985180246.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi all, 

I'm trying to write a Hello World client for a deployed web service. This subject was addressed a year ago by GenesisD, but the problem was never solved in the forum.

Any way, I hope you can help me, my client:

package demo;
  | 
  | import java.net.URL;
  | 
  | import javax.xml.namespace.QName;
  | import javax.xml.rpc.Service;
  | import javax.xml.rpc.ServiceFactory;
  | 
  | public class demoCliente 
  | {
  |     public static void main(String[] args) throws Exception 
  |     {
  |     	String endpointURL = "http://localhost:8080/orquestador/OrquestadorWS?wsdl";
  | 		URL wsdlURL = new URL(endpointURL);
  | 		
  | 		String targetNS = "http://webservices.orquestador.cupi2.uniandes/jaws";
  | 		QName serviceName = new QName(targetNS, "IOrquestadorWSService");
  | 		
  | 		ServiceFactory factory = ServiceFactory.newInstance();
  | 		Service service = factory.createService(wsdlURL, serviceName);
  | 		
  | 		IOrquestadorWS orquestador = (IOrquestadorWS) service.getPort(IOrquestadorWS.class);
  | 		orquestador.receiveItemInformation("Algo");
  | 
  |     }
  | }

The error the cliente produces:
Exception in thread "main" java.lang.NoSuchMethodError: org.jboss.ws.utils.JBossWSEntityResolver.getEntityMap()Ljava/util/Map;
  | 	at org.jboss.ws.utils.JBossWSEntityResolver.resolveNamespaceURI(JBossWSEntityResolver.java:65)
  | 	at org.jboss.ws.tools.JavaToXSD.parseSchema(JavaToXSD.java:164)
  | 	at org.jboss.ws.metadata.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:227)
  | 	at org.jboss.ws.metadata.wsdl.WSDL11Reader.processDefinition(WSDL11Reader.java:118)
  | 	at org.jboss.ws.metadata.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:145)
  | 	at org.jboss.ws.metadata.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:273)
  | 	at org.jboss.ws.deployment.JSR109ClientMetaDataBuilder.buildMetaData(JSR109ClientMetaDataBuilder.java:110)
  | 	at org.jboss.ws.deployment.JSR109ClientMetaDataBuilder.buildMetaData(JSR109ClientMetaDataBuilder.java:82)
  | 	at org.jboss.ws.jaxrpc.ServiceImpl.<init>(ServiceImpl.java:96)
  | 	at org.jboss.ws.jaxrpc.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:157)
  | 	at org.jboss.ws.jaxrpc.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:128)
  | 	at demo.demoCliente.main(demoCliente.java:20)
  | 

I have cofirmed that this method exists in the class JBossEntityResolver and it's inherited by JBossWSEntityResolver. All of this in the library jbossall-client.jar. THX!!

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

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


From do-not-reply at jboss.com  Mon Mar 31 15:11:23 2008
From: do-not-reply at jboss.com (rruppel)
Date: Mon, 31 Mar 2008 15:11:23 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: How to Define WebService URL?
Message-ID: <9336601.1206990683629.JavaMail.jboss@colo-br-02.atl.jboss.com>

nobody knows it?

I thought it would be simple.... but Its hard to find something about this =(

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

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


From do-not-reply at jboss.com  Mon Mar 31 16:22:58 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 31 Mar 2008 16:22:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: How to Define WebService URL?
Message-ID: <22942267.1206994978215.JavaMail.jboss@colo-br-02.atl.jboss.com>

Have you tried using @WebService(serviceName="xxx")?

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

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


From do-not-reply at jboss.com  Mon Mar 31 17:58:52 2008
From: do-not-reply at jboss.com (sajhak)
Date: Mon, 31 Mar 2008 17:58:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: javaEE5 JAX-WS web services - JBOSS
	4.2.2
Message-ID: <24776299.1207000732207.JavaMail.jboss@colo-br-02.atl.jboss.com>

Here s the code for  SayHelloWebService
import javax.ejb.Remote;
  | import javax.jws.WebMethod;
  | import javax.jws.WebService;
  | import javax.jws.soap.SOAPBinding;
  | 
  | @Remote
  | @WebService(
  |         name = "SayHello",
  |         targetNamespace = "http://org.jboss.ws/samples/retail/profile")
  | //@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
  | 
  | public interface SayHelloWebService {
  |     @WebMethod
  |     public String sayHello(String name);
  | }

PS : by the way , when i put the JAXB2.0-.jar file into the lib of the JBOSS the problem is solved.I did that without any understanding , as the exception said something like "endorsed directory....place that jar file in the xxx directory ... " 
now it works fine , but im not clear about why i had to place that .jar in the lib ?? that kinda thing hasnt mentioned any of the materials i reffered.
could u explain the reason for that ?

thanks
Saji

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

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


From do-not-reply at jboss.com  Mon Mar 31 19:11:30 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 31 Mar 2008 19:11:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: javaEE5 JAX-WS web services - JBOSS
	4.2.2
Message-ID: <14678176.1207005090995.JavaMail.jboss@colo-br-02.atl.jboss.com>

Are you using JDK 6?  If so, no wonder you are running into problems.

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

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


From do-not-reply at jboss.com  Mon Mar 31 21:39:36 2008
From: do-not-reply at jboss.com (pramod_bs)
Date: Mon, 31 Mar 2008 21:39:36 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WS-Security Usernametoken in a war file.
Message-ID: <17722187.1207013977004.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have implemented WS-Security username token authentication for a web application. But for some reason the authentication is not working. Is there any config needed in web.xml. The same code is working in a simple statelss EJB.

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

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


From do-not-reply at jboss.com  Mon Mar 31 22:24:10 2008
From: do-not-reply at jboss.com (raags)
Date: Mon, 31 Mar 2008 22:24:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Using (Hash)Map in wrapper class
Message-ID: <4645758.1207016650086.JavaMail.jboss@colo-br-02.atl.jboss.com>

Is this a known JAX-WS issue? I'm not able to find any bug tracked against it.. Can you help me here? 

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

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


From do-not-reply at jboss.com  Mon Mar 31 22:37:10 2008
From: do-not-reply at jboss.com (jttjunk)
Date: Mon, 31 Mar 2008 22:37:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Using (Hash)Map in wrapper class
Message-ID: <8711387.1207017430925.JavaMail.jboss@colo-br-02.atl.jboss.com>

I guess the map isn't really suited to send over a webservice. It was a while ago I was doing this, I'm not sure whether it worked at all.

I ended up with this as SOAPBinding:
@SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL, parameterStyle = SOAPBinding.ParameterStyle.WRAPPED)

Hope it helps!

Good luck

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

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