From do-not-reply at jboss.com  Fri Aug  1 06:37:17 2008
From: do-not-reply at jboss.com (karypid)
Date: Fri, 1 Aug 2008 06:37:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Trying to use jboss.xml instead of
	@WebContext
Message-ID: <2661586.1217587037427.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello,

I'm trying to secure a web service with basic http authentication, but I want to keep all JBoss-specific configuration out of my code. Therefore, I need some pointers as to how to express the @WebContext annotation (used to specify BASIC http authentication) in the jboss.xml deployment descriptor.

In more detail:

I have my service implemented as a stateless session bean. I have found the following code works perfectly to require authorization, but uses JBoss-specific annotations (marked in bold font):

@Stateless
  | @WebService at SecurityDomain("JBossWS")@RolesAllowed("someRole")@WebContext(authMethod = "BASIC", transportGuarantee = "NONE", secureWSDLAccess = false)public class MyWSBean {
  | //...
  | }
  | 
I therefore remove the @SecurityDomain and @WebContext annotations and added a jboss.xml deployment descriptor as follows:

<?xml version="1.0" encoding="UTF-8"?>
  | <jboss>	<security-domain>java:/jaas/JBossWS</security-domain>	<enterprise-beans>
  | 		<session>
  | 			<ejb-name>MyWSBean</ejb-name>
  | 			<port-component>
  | 				<port-component-name>MyWSBean</port-component-name>				<auth-method>BASIC</auth-method>			</port-component>
  | 		</session>
  | 	</enterprise-beans>
  | </jboss>
However, the configuration is not picked up for some reason. All attempts to access the web service fail due to an authorization failure. I can tell that the jboss.xml file is pared because if I mistype something (e.g. use <ejb-name>MyWSBeanWILLNOTMATCH</ejb-name>, or <security-domain>ThisDoesNotExist</security-domain>) then JBoss complains during deployment that the bean / realm does not exist.

Specifically, I verified that my jboss.xml works for replacing the @SecurityDomain annotation by leaving @WebContext in the code and specifying the domain with the <security-domain> tag in jboss.xml: this works.

Can anybody help me out with the proper deployment descriptor content for replacing the @WebContext?

P.S. No other deployment descriptors exists (no webservices.xml and the ejb-jar.xml is empty).


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

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


From msc at antzsystem.de  Fri Aug  1 07:04:30 2008
From: msc at antzsystem.de (Markus Schulz)
Date: Fri, 1 Aug 2008 13:04:30 +0200
Subject: [jbossws-users] [JBossWS] - Trying to use jboss.xml instead of
	@WebContext
In-Reply-To: <2661586.1217587037427.JavaMail.jboss@colo-br-02.atl.jboss.com>
References: <2661586.1217587037427.JavaMail.jboss@colo-br-02.atl.jboss.com>
Message-ID: <200808011304.30442@Mail-Followup-To>

Am Freitag, 1. August 2008 schrieb karypid:
> Hello,
>
> I'm trying to secure a web service with basic http authentication,
> but I want to keep all JBoss-specific configuration out of my code.
> Therefore, I need some pointers as to how to express the @WebContext
> annotation (used to specify BASIC http authentication) in the
> jboss.xml deployment descriptor.
>
> In more detail:
>
> I have my service implemented as a stateless session bean. I have
> found the following code works perfectly to require authorization,
> but uses JBoss-specific annotations (marked in bold font):
>
> @Stateless
>
>   | @WebService at SecurityDomain("JBossWS")@RolesAllowed("someRole")@We
>   |bContext(authMethod = "BASIC", transportGuarantee = "NONE",
>   | secureWSDLAccess = false)public class MyWSBean { //...
>   | }
>
> I therefore remove the @SecurityDomain and @WebContext annotations
> and added a jboss.xml deployment descriptor as follows:
>
> <?xml version="1.0" encoding="UTF-8"?>
>
>   | <jboss>	<security-domain>java:/jaas/JBossWS</security-domain>	<en
>   |terprise-beans> <session>
>   | 			<ejb-name>MyWSBean</ejb-name>
>   | 			<port-component>
>   | 				<port-component-name>MyWSBean</port-component-name>				<auth-
>   |method>BASIC</auth-method>			</port-component> </session>
>   | 	</enterprise-beans>
>   | </jboss>

i have exactly the same problem. Only the port-component seems to be 
ignored, cause changing the jndi-name inside <session> for a bean works 
fine.

-- 
Markus Schulz


From do-not-reply at jboss.com  Fri Aug  1 09:58:05 2008
From: do-not-reply at jboss.com (dakk)
Date: Fri, 1 Aug 2008 09:58:05 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Are there lifecycle methods for a
	service???
Message-ID: <23115924.1217599089383.JavaMail.jboss@colo-br-02.atl.jboss.com>

I've been looking thru the (apparently, wrong) docs to find what methods JBoss will call on a service when it is first being deployed, and then undeployed.... like init and finalize methods.

Are there any such calls, and is there a formal way to access a parameter file in the deployment jar?  I am not so keen on not having even a sparse common service API for all services.

Or, should one simply check for the initialization of globals to determine if it's the first time the service has been called to trigger initialization? E.g. I need to open a connection to a DB.

Any pointers much appreciated!

Thanks. 

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

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


From do-not-reply at jboss.com  Fri Aug  1 10:12:51 2008
From: do-not-reply at jboss.com (dakk)
Date: Fri, 1 Aug 2008 10:12:51 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Are there lifecycle methods for a
	service???
Message-ID: <8867686.1217599972276.JavaMail.jboss@colo-br-02.atl.jboss.com>

Scanning the web I finally found javax.xml.rpc.server.ServletEndpointContext in javax.xml.rpc.server. ServiceLifecycle.

Seems like it would be a good thing to have in the docs... anyone know where this is discussed (or if it works in JBoss)?

Thanks.

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

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


From do-not-reply at jboss.com  Fri Aug  1 11:56:06 2008
From: do-not-reply at jboss.com (pophristov)
Date: Fri, 1 Aug 2008 11:56:06 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Web method memory leak?
Message-ID: <2119991.1217606166817.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello,

We have a web service for file upload/download. We are using a web method that returns a chunk of the file as a byte array for downloading. When the web service client downloads a large file the memory used by the java.exe (monitored using Windows Task Manager) swiftly increases and is never released. Eventually the used memory becomes so much that the whole computer performance decreases dramatically. Same happens if simply return a large byte array:


  | @WebMethod
  | public byte[] downloadChunk() {
  |  return new byte[524288];
  | }
  | 

We are using JBoss 4.2.1 GA with JBossWS 2.0.1. Java 1.5.0_15. It is running on Windows Vista 32.

Any help on solving this will be greatly appreciated. Thank you in advance.

BP

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

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


From do-not-reply at jboss.com  Fri Aug  1 12:04:16 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 1 Aug 2008 12:04:16 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Web method memory leak?
Message-ID: <3025491.1217606656222.JavaMail.jboss@colo-br-02.atl.jboss.com>

If you set the min and max heap sizes to different values, then when the JVM requires more heap space it will get it from the os, after which the JVM rarely lets go of that memory, even if the space required for those objects (the byte array in this case) is cleaned up during a garbage collection. Thus the behavior you are seeing in task manager does not indicate a memory leak - it is just how Java works.

To determine if a memory leak was taking place you would have to monitor the objects in the heap, either by monitoring the garbage collector (this lets you know if there is a possible leak but not where), or by using a tool like VisualVM which lets you take and compare heap dumps.

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

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


From do-not-reply at jboss.com  Sun Aug  3 07:40:15 2008
From: do-not-reply at jboss.com (karypid)
Date: Sun, 3 Aug 2008 07:40:15 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WS URL different for 4.2.2 and 4.2.3
Message-ID: <25725966.1217763615365.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello,

I have two installations of JBoss on my machine (4.2.2 and 4.2.3). In both of them, I have installed JBossWS-Native 3.0.2. When I deploy an EAR that has a EJB-JAR with a web service, I observed that my WS is published in different URL location:

https://localhost:8080/ear_name-ejbjar_name/MyServiceBean?wsdl
https://localhost:8180//MyServiceBean?wsdl

The different port (8080 and 8180) is because I have changed the ports for the 4.2.3 installation so that I may run both of them concurrently. However, 4.2.2 uses the ear/ejb-jar names as a prefix whereas 4.2.3 does not.

The stange thing is that BOTH use the latest stable JBossWS-native stack (i.e. 3.0.2) so I guess the publish location is not controlled fully by JBossWS.

How can I get 4.2.3 to revert back to the old behaviour? Does this seem like a bug in the Application Server?


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

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


From do-not-reply at jboss.com  Sun Aug  3 09:47:30 2008
From: do-not-reply at jboss.com (karypid)
Date: Sun, 3 Aug 2008 09:47:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS URL different for 4.2.2 and 4.2.3
Message-ID: <14862842.1217771250891.JavaMail.jboss@colo-br-02.atl.jboss.com>

I've been toying with this for a while. I was able to use jboss.xml to provide a proper URL-prefix for 4.2.3 using jboss.xml:

<?xml version="1.0" encoding="UTF-8"?>
  | <!DOCTYPE jboss PUBLIC
  |           "-//JBoss//DTD JBOSS 4.2//EN"
  |           "http://www.jboss.org/j2ee/dtd/jboss_4_2.dtd">
  | <jboss>
  | 	<security-domain>java:/jaas/JBossWS</security-domain>
  | 	<webservices>
  | 		<context-root>TYPE_YOUR_PREFERRED_URL_HERE</context-root>
  | 	</webservices>
  | </jboss>

Unfortunately, 4.2.2 seems to completely ignore this!

Anyway, I like the 4.2.3 behavior better (being able to specify the URL prefix of your choice).


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

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


From do-not-reply at jboss.com  Mon Aug  4 02:39:18 2008
From: do-not-reply at jboss.com (dilipreddy)
Date: Mon, 4 Aug 2008 02:39:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: jbossws 1.2.1: wsconsume
	OutOfMemoryError
Message-ID: <4133747.1217831958902.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi
see this
???To solve ???OutofMemoryException:Max GenSpace Exception???  in Jboss portal server: 

http://www.innoq.com/blog/sp/2008/01/jboss_as_42x_and_javalangoutof.html   

see this link and edit the run.bat in windows of conf.run in Unix


might be useful

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

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



From do-not-reply at jboss.com  Mon Aug  4 03:31:18 2008
From: do-not-reply at jboss.com (moweis)
Date: Mon, 4 Aug 2008 03:31:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WS-RM Exception: cannot be cast to
	org.jboss.ws.core.StubExt
Message-ID: <19503935.1217835078193.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I'm running the example found at:
http://jbws.dyndns.org/mediawiki/index.php?title=Native_WS-ReliableMessaging_Tutorial

I'm able to deploy the WS, but when I try to run the sample client:
http://jbws.dyndns.org/mediawiki/index.php?title=Native_WS-ReliableMessaging_Tutorial#Updating_Client_Code_to_Reference_Custom_JAX-WS_Config_File_and_Close_the_Sequence

I get the following exception:
anonymous wrote : Exception in thread "main" java.lang.ClassCastException: $Proxy25 cannot be cast to org.jboss.ws.core.StubExt

at the line:

((StubExt)proxy).setConfigName("Standard Anonymous WSRM Client", "META-INF/wsrm-jaxws-client-config.xml");
  | 
FYI, when I run the client with this line commented out, I get a fault from the service that I'm not using WS-RM:
anonymous wrote : Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: java.lang.IllegalStateException: RM handler was not able to find WS-RM message in the payload
So the service seems to be configured fine, but I am unable to get the client to add WS-RM appropriately.   

Any ideas?

I'm using:
-jboss-4.2.3.GA
-jbossws-native-3.0.2.GA

Thanks in advance!


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

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


From do-not-reply at jboss.com  Mon Aug  4 03:50:41 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 4 Aug 2008 03:50:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <16091698.1217836241640.JavaMail.jboss@colo-br-02.atl.jboss.com>

Can you copy/paste your client code here?

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

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


From do-not-reply at jboss.com  Mon Aug  4 03:55:37 2008
From: do-not-reply at jboss.com (moweis)
Date: Mon, 4 Aug 2008 03:55:37 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <32732716.1217836537084.JavaMail.jboss@colo-br-02.atl.jboss.com>

Sure:

Here is my client code:
package org.jboss.test.ws.jaxws.samples.wsrm.client;
  | 
  | import java.net.URL;
  | import javax.xml.namespace.QName;
  | import javax.xml.ws.Service;
  | import org.jboss.ws.core.StubExt;
  | import org.jboss.ws.extensions.wsrm.api.RMProvider;
  | 
  | import org.jboss.test.ws.jaxws.samples.wsrm.generated.SimpleService;
  | 
  | 
  | public final class SimpleServiceTestCase
  | {
  | 
  |    private static final String serviceURL = "http://localhost:8080/jaxws-samples-wsrm/SimpleService";
  |    
  |    public static void main(String[] args) throws Exception
  |    {
  |    	  String url = null;
  |    	  if ( args != null && args.length > 0 && args[0] != null )
  |    	  	url = args[0];
  |    	  else
  |    	  	url = serviceURL;
  |       System.out.println("Calling wsdl");
  |       QName serviceName = new QName("http://www.jboss.org/jbossws/ws-extensions/wsrm", "SimpleService");
  |       QName portName = new QName("http://www.jboss.org/jbossws/ws-extensions/wsrm", "SimpleServicePort");
  |       URL wsdlURL = new URL(url + "?wsdl");
  |       Service service = Service.create(wsdlURL, serviceName);
  |       SimpleService proxy = (SimpleService)service.getPort(SimpleService.class);
  |       ((StubExt)proxy).setConfigName("Standard Anonymous WSRM Client", "META-INF/wsrm-jaxws-client-config.xml");
  | 	        
  |       proxy.ping(); // one way call
  |       proxy.echo("Hello World!"); // request responce call
  |       ((RMProvider)proxy).closeSequence();
  |    }
  |    
  | }
  | 

It is directly from the client example on the page:
http://jbws.dyndns.org/mediawiki/index.php?title=Native_WS-ReliableMessaging_Tutorial#Updating_Client_Code_to_Reference_Custom_JAX-WS_Config_File_and_Close_the_Sequence

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

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


From do-not-reply at jboss.com  Mon Aug  4 04:27:52 2008
From: do-not-reply at jboss.com (pophristov)
Date: Mon, 4 Aug 2008 04:27:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Web method memory leak?
Message-ID: <30118233.1217838472886.JavaMail.jboss@colo-br-02.atl.jboss.com>

Peter,

Thank you for your reply! Increasing the heap size solved my problem.

BP

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

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


From do-not-reply at jboss.com  Mon Aug  4 04:59:57 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 4 Aug 2008 04:59:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <2376570.1217840397230.JavaMail.jboss@colo-br-02.atl.jboss.com>

"moweis" wrote : 
  | I get the following exception:
  | anonymous wrote : Exception in thread "main" java.lang.ClassCastException: $Proxy25 cannot be cast to org.jboss.ws.core.StubExt
  |  in advance!
  | 
And what is the full stack trace?

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

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


From do-not-reply at jboss.com  Mon Aug  4 05:04:02 2008
From: do-not-reply at jboss.com (moweis)
Date: Mon, 4 Aug 2008 05:04:02 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <5341799.1217840642067.JavaMail.jboss@colo-br-02.atl.jboss.com>

Here is the full stack trace:
anonymous wrote : Exception in thread "main" java.lang.ClassCastException: $Proxy25 cannot be cast to org.jboss.ws.core.StubExt
  | 	at org.jboss.test.ws.jaxws.samples.wsrm.client.SimpleServiceTestCase.main(SimpleServiceTestCase.java:30)
  | 

Line 30 is:
((StubExt)proxy).setConfigName("Standard Anonymous WSRM Client", "META-INF/wsrm-jaxws-client-config.xml");
  | 

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

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


From do-not-reply at jboss.com  Mon Aug  4 05:29:59 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 4 Aug 2008 05:29:59 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <26850367.1217842199749.JavaMail.jboss@colo-br-02.atl.jboss.com>

This is absolute mystery to me :(
I can't believe this is possible?

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

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


From do-not-reply at jboss.com  Mon Aug  4 05:33:11 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 4 Aug 2008 05:33:11 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <93677.1217842391535.JavaMail.jboss@colo-br-02.atl.jboss.com>

Are you using jbossws only libs?
What is your client classpath?

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

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


From do-not-reply at jboss.com  Mon Aug  4 05:36:56 2008
From: do-not-reply at jboss.com (moweis)
Date: Mon, 4 Aug 2008 05:36:56 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <20565752.1217842616737.JavaMail.jboss@colo-br-02.atl.jboss.com>

I'm wondering if the wsconsume didn't run properly?

I ran it twice:
First with a non-WS-Policy wsdl
Second with WS-Policy wsdl


Both generated the same files.

Is that correct?

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

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


From do-not-reply at jboss.com  Mon Aug  4 05:39:14 2008
From: do-not-reply at jboss.com (moweis)
Date: Mon, 4 Aug 2008 05:39:14 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <12437122.1217842754177.JavaMail.jboss@colo-br-02.atl.jboss.com>

Yes, here is my command-line execution:
anonymous wrote : 
  | /System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home/bin/java  -classpath .:../wsconsume/generated/classes/:${JBOSS_WS_HOME}/deploy/lib/jbossws-native-core.jar org.jboss.test.ws.jaxws.samples.wsrm.client.SimpleServiceTestCase

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

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


From do-not-reply at jboss.com  Mon Aug  4 05:42:39 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 4 Aug 2008 05:42:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <19876793.1217842959282.JavaMail.jboss@colo-br-02.atl.jboss.com>

You have to endorse JAXWS.
Try to add:

-Djava.endorsed.dirs=${JBOSS_HOME}/lib/endorsed

to your client launch command.

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

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


From do-not-reply at jboss.com  Mon Aug  4 05:50:42 2008
From: do-not-reply at jboss.com (moweis)
Date: Mon, 4 Aug 2008 05:50:42 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <19482928.1217843442622.JavaMail.jboss@colo-br-02.atl.jboss.com>

I still get the same error :(

anonymous wrote : /System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home/bin/java  -classpath .:..:../wsconsume/generated/classes/:${JBOSS_WS_HOME}/deploy/lib/jbossws-native-core.jar org.jboss.test.ws.jaxws.samples.wsrm.client.SimpleServiceTestCase -Djava.endorsed.dirs=${JBOSS_HOME}/lib/endorsed
  | 
  | Exception in thread "main" java.lang.ClassCastException: $Proxy25 cannot be cast to org.jboss.ws.core.StubExt
  | 	at org.jboss.test.ws.jaxws.samples.wsrm.client.SimpleServiceTestCase.main(SimpleServiceTestCase.java:30)
  | marw

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

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


From do-not-reply at jboss.com  Mon Aug  4 06:06:39 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 4 Aug 2008 06:06:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <11421760.1217844399572.JavaMail.jboss@colo-br-02.atl.jboss.com>

OK, did you see:

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

topic:

Using JBossWS Native with JDK 6

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

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


From do-not-reply at jboss.com  Mon Aug  4 06:29:04 2008
From: do-not-reply at jboss.com (moweis)
Date: Mon, 4 Aug 2008 06:29:04 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <24470709.1217845744725.JavaMail.jboss@colo-br-02.atl.jboss.com>

Yes I did...I copied the libs as stated. 

Question, if I run wsconsume on the wsdl with no WS-RM related info, and run it again with WS-RM configuration, should I see any difference in the generated source?

Because looking at the generated service interface, it doesn't extend StubExt:


  | package org.jboss.test.ws.jaxws.samples.wsrm.generated;
  | 
  | import javax.jws.Oneway;
  | 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.3-b02-
  |  * Generated source version: 2.0
  |  * 
  |  */
  | @WebService(name = "SimpleService", targetNamespace = "http://www.jboss.org/jbossws/ws-extensions/wsrm")
  | public interface SimpleService {
  | 
  | 
  |     /**
  |      * 
  |      * @param arg0
  |      * @return
  |      *     returns java.lang.String
  |      */
  |     @WebMethod
  |     @WebResult(targetNamespace = "")
  |     @RequestWrapper(localName = "echo", targetNamespace = "http://www.jboss.org/jbossws/ws-extensions/wsrm", className = "org.jboss.test.ws.jaxws.samples.wsrm.generated.Echo")
  |     @ResponseWrapper(localName = "echoResponse", targetNamespace = "http://www.jboss.org/jbossws/ws-extensions/wsrm", className = "org.jboss.test.ws.jaxws.samples.wsrm.generated.EchoResponse")
  |     public String echo(
  |         @WebParam(name = "arg0", targetNamespace = "")
  |         String arg0);
  | 
  |     /**
  |      * 
  |      */
  |     @WebMethod
  |     @Oneway
  |     @RequestWrapper(localName = "ping", targetNamespace = "http://www.jboss.org/jbossws/ws-extensions/wsrm", className = "org.jboss.test.ws.jaxws.samples.wsrm.generated.Ping")
  |     public void ping();
  | 
  | }
  | 

Thanks for your help Richard

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

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


From do-not-reply at jboss.com  Mon Aug  4 06:45:49 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 4 Aug 2008 06:45:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <15871899.1217846749884.JavaMail.jboss@colo-br-02.atl.jboss.com>

"moweis" wrote : 
  | Question, if I run wsconsume on the wsdl with no WS-RM related info, and run it again with WS-RM configuration, should I see any difference in the generated source?
  | 
  | Because looking at the generated service interface, it doesn't extend StubExt:
No, the interface implementation is generated via Java proxies at runtime (behind the scenes)

"moweis" wrote : Thanks for your help Richard
Does the client work already?

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

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


From do-not-reply at jboss.com  Mon Aug  4 06:46:50 2008
From: do-not-reply at jboss.com (moweis)
Date: Mon, 4 Aug 2008 06:46:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <3992105.1217846810433.JavaMail.jboss@colo-br-02.atl.jboss.com>

No i still have the same error...

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

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


From do-not-reply at jboss.com  Mon Aug  4 07:44:38 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 4 Aug 2008 07:44:38 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <28154928.1217850278676.JavaMail.jboss@colo-br-02.atl.jboss.com>

To recapitulate your problem is wrong client classpath.
You didn't endorse jbossws client libraries properly.
The last stupid question: is your JBOSS_HOME environment variable defined?

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

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


From do-not-reply at jboss.com  Mon Aug  4 07:54:02 2008
From: do-not-reply at jboss.com (moweis)
Date: Mon, 4 Aug 2008 07:54:02 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <21800641.1217850842663.JavaMail.jboss@colo-br-02.atl.jboss.com>

Yes JBOSS_HOME is set.

What should my classpath be? 

All I currently have in my classpath are 4 locations
1) current directory so that I can access my Client
2) parent directory of META-INF/wsrm-jaxws-endpoint-config.xml 
3) directory for my generated classes from wscompile
4) {$JBOSSWS_HOME}/deploy/lib/jbossws-native-core.jar

Am I missing anything?

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

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


From do-not-reply at jboss.com  Mon Aug  4 08:30:51 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 4 Aug 2008 08:30:51 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <4763833.1217853051793.JavaMail.jboss@colo-br-02.atl.jboss.com>

Yes, you have to ensure (using proper endorsing setup) that jbossws jaxws api will be used instead of jaxws that is distributed with the JVM.

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

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


From do-not-reply at jboss.com  Mon Aug  4 08:42:15 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 4 Aug 2008 08:42:15 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <17531145.1217853735457.JavaMail.jboss@colo-br-02.atl.jboss.com>

Try to add this piece of code to your client source:

URL jaxwsThatIsUsed = javax.xml.ws.Service.class.getProtectionDomain().getCodeSource().getLocation();
  | System.out.println("JAXWS that is used: " + jaxwsThatIsUsed);
  | 
and send me your console output.

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

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


From do-not-reply at jboss.com  Mon Aug  4 09:17:45 2008
From: do-not-reply at jboss.com (moweis)
Date: Mon, 4 Aug 2008 09:17:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <13163388.1217855865709.JavaMail.jboss@colo-br-02.atl.jboss.com>

getCodeSource is returning a null, so I'm unable to call getLocation

I really appreciate your help.

I'm trying to run the example now on my PC, to see if I run into the same problems (I currently running it on a mac).

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

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


From do-not-reply at jboss.com  Mon Aug  4 10:48:47 2008
From: do-not-reply at jboss.com (kosulin)
Date: Mon, 4 Aug 2008 10:48:47 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - javax.naming.Name is an interface,
	and JAXB can't handle int
Message-ID: <25916792.1217861327511.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,
I have a single POJO with 2 methods, first method accesses filesystem, and second - invokes SLSB. When I deploy it to JBoss 5.0.0CR1 (jre 1.6.0_07, Windows Vista SP1), I am getting the following error message:

10:16:02,418 ERROR [AbstractKernelController] Error installing to Real: name=vfszip:/C:/java/jboss-5.0.0.CR1/server/cpportal2/deploy/cpportal2-ear.ear state=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/C:/java/jboss-5.0.0.CR1/server/cpportal2/deploy/cpportal2-ear.ear/statements-web.war
	at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
	at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:180)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:970)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1023)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:911)
	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1392)
	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:784)
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:912)
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:834)
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:672)
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:455)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:594)
	at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541)
	at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:290)
	at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
	at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.IllegalStateException: Cannot build JAXB context
	at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.createJAXBContext(JAXWSMetaDataBuilder.java:955)
	at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:156)
	at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:52)
	at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderJSE.buildMetaData(JAXWSMetaDataBuilderJSE.java:63)
	at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.start(UnifiedMetaDataDeploymentAspect.java:67)
	at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.start(DeploymentAspectManagerImpl.java:146)
	at org.jboss.wsf.container.jboss50.BareWSFRuntime.start(BareWSFRuntime.java:66)
	at org.jboss.wsf.container.jboss50.deployer.JAXWSDeployerHookPostJSE.deploy(JAXWSDeployerHookPostJSE.java:54)
	at org.jboss.wsf.container.jboss50.deployer.AbstractWebServiceDeployer.internalDeploy(AbstractWebServiceDeployer.java:62)
	at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
	at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:174)
	... 23 more
Caused by: org.jboss.ws.WSException: Failed to create JAXBContext
	at org.jboss.ws.core.jaxws.CustomizableJAXBContextFactory.createContext(CustomizableJAXBContextFactory.java:116)
	at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.createJAXBContext(JAXWSMetaDataBuilder.java:951)
	... 33 more
Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 3 counts of IllegalAnnotationExceptions
javax.naming.Name is an interface, and JAXB can't handle interfaces.
	this problem is related to the following location:
		at javax.naming.Name
		at private javax.naming.Name com.wsc.cp.web.statements.jaxws.NamingExceptionBean.remainingName
		at com.wsc.cp.web.statements.jaxws.NamingExceptionBean
javax.naming.Name does not have a no-arg default constructor.
	this problem is related to the following location:
		at javax.naming.Name
		at private javax.naming.Name com.wsc.cp.web.statements.jaxws.NamingExceptionBean.remainingName
		at com.wsc.cp.web.statements.jaxws.NamingExceptionBean
java.lang.StackTraceElement does not have a no-arg default constructor.
	this problem is related to the following location:
		at java.lang.StackTraceElement
		at public java.lang.StackTraceElement[] java.lang.Throwable.getStackTrace()
		at java.lang.Throwable
		at private java.lang.Throwable com.wsc.cp.web.statements.jaxws.NamingExceptionBean.rootCause
		at com.wsc.cp.web.statements.jaxws.NamingExceptionBean

	at com.sun.xml.bind.v2.runtime.IllegalAnnotationsException$Builder.check(IllegalAnnotationsException.java:102)
	at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:438)
	at com.sun.xml.bind.v2.runtime.JAXBContextImpl.(JAXBContextImpl.java:286)
	at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
	at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:105)
	at org.jboss.ws.core.jaxws.CustomizableJAXBContextFactory.createContext(CustomizableJAXBContextFactory.java:110)
	... 34 more
10:16:03,189 WARN  [HDScanner] Failed to process changes
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

*** CONTEXTS IN ERROR: Name -> Error

vfszip:/C:/java/jboss-5.0.0.CR1/server/cpportal2/deploy/cpportal2-ear.ear -> com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 3 counts of IllegalAnnotationExceptions
javax.naming.Name is an interface, and JAXB can't handle interfaces.
	this problem is related to the following location:
		at javax.naming.Name
		at private javax.naming.Name com.wsc.cp.web.statements.jaxws.NamingExceptionBean.remainingName
		at com.wsc.cp.web.statements.jaxws.NamingExceptionBean
javax.naming.Name does not have a no-arg default constructor.
	this problem is related to the following location:
		at javax.naming.Name
		at private javax.naming.Name com.wsc.cp.web.statements.jaxws.NamingExceptionBean.remainingName
		at com.wsc.cp.web.statements.jaxws.NamingExceptionBean
java.lang.StackTraceElement does not have a no-arg default constructor.
	this problem is related to the following location:
		at java.lang.StackTraceElement
		at public java.lang.StackTraceElement[] java.lang.Throwable.getStackTrace()
		at java.lang.Throwable
		at private java.lang.Throwable com.wsc.cp.web.statements.jaxws.NamingExceptionBean.rootCause
		at com.wsc.cp.web.statements.jaxws.NamingExceptionBean



	at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:676)
	at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:661)
	at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:291)
	at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
	at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)

===============================================

Here is my code which causes the problem:

@WebMethod(operationName = "GetStatements")
	public StatementListDO getReportingDates(@WebParam(name = "Username") final String user,
	                                         @WebParam(name = "ClientId") final String clientId,
	                                         @WebParam(name = "TaxYear") final String taxYear,
	                                         @WebParam(name = "AccountNo") final String custAccountNo)
	  throws IncorrectParameterException, DBConnectionException, NamingException
	{
		StatementHandler.logger.info("Received request from user '" + user +
		                             "' for a list of statements available for Client Id " + clientId + ", Tax Year " +
		                             taxYear + ", AccountNo " + custAccountNo);

		StatementListDO sldo = new StatementListDO();
		try
		{
			InitialContext ic = new InitialContext();
			// Statements stmts = (Statements)ic.lookup(Statements.class.getName());
			// sldo = stmts.getReportingDates(clientId, taxYear, custAccountNo);
		}
		catch(NamingException e)
		{
			StatementHandler.logger.error(e);
			throw new DBConnectionException("Processing error");
		}
		return sldo;
	}

If I comment InitalContext out (as I did for the SLSB invocation code), it deploys fine. But how can I resolve my SLSB then?

I'd prefer not to expose SLSB directly through WS annotations, becuase this means having 2 endpoints and 2 WSDL definitions.

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

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


From do-not-reply at jboss.com  Mon Aug  4 10:56:04 2008
From: do-not-reply at jboss.com (kosulin)
Date: Mon, 4 Aug 2008 10:56:04 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: javax.naming.Name is an interface,
	and JAXB can't handle
Message-ID: <12422772.1217861764312.JavaMail.jboss@colo-br-02.atl.jboss.com>

Here is my POJO definition:

@WebService(name = "Statements", targetNamespace = "http://www.mysite.com/", serviceName = "StatementsService", portName = "StatementsPort")
@SOAPBinding(style = SOAPBinding.Style.DOCUMENT, parameterStyle = SOAPBinding.ParameterStyle.WRAPPED)
@BindingType(value = "http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true")
@WebContext(secureWSDLAccess = false)
// @WebContext(secureWSDLAccess = true, transportGuarantee = "CONFIDENTIAL", authMethod = "CLIENT-CERT")
// @SecurityDomain("Statements")
// @RolesAllowed("consumer")
public class StatementHandler
...

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

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


From do-not-reply at jboss.com  Mon Aug  4 11:26:48 2008
From: do-not-reply at jboss.com (kosulin)
Date: Mon, 4 Aug 2008 11:26:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: javax.naming.Name is an interface,
	and JAXB can't handle
Message-ID: <24983169.1217863608306.JavaMail.jboss@colo-br-02.atl.jboss.com>

I resolved the issue by marking it as resource:
@Resource
InitialContext ctx;

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

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


From do-not-reply at jboss.com  Mon Aug  4 11:57:20 2008
From: do-not-reply at jboss.com (moweis)
Date: Mon, 4 Aug 2008 11:57:20 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <7547693.1217865440364.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi Richard,

You were right.
I went ahead and added all the jboss/jbossws jars to my classpath, and I no longer get the cannot be cast exception.

However, I get a new exception now:

anonymous wrote : Exception in thread "main" org.jboss.ws.extensions.wsrm.api.RMException: Unable to create WSRM sequence
  | 	at org.jboss.ws.core.jaxws.client.ClientImpl.createSequence(ClientImpl.java:563)
  | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
  | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
  | 	at $Proxy16.ping(Unknown Source)
  | 	at org.jboss.test.ws.jaxws.samples.wsrm.client.SimpleServiceTestCase.main(SimpleServiceTestCase.java:33)
  | 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:410)
  | 	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:316)
  | 	at org.jboss.ws.core.jaxws.client.ClientImpl.createSequence(ClientImpl.java:550)
  | 	... 4 more
  | Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
  | 	at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:441)
  | 	at org.jboss.ws.core.soap.SOAPMessageImpl.(SOAPMessageImpl.java:84)
  | 	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:292)
  | 	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:304)
  | 	... 5 more
  | 


Here is my client code:
package org.jboss.test.ws.jaxws.samples.wsrm.client;
  | 
  | import java.net.URL;
  | import javax.xml.namespace.QName;
  | import javax.xml.ws.Service;
  | import org.jboss.ws.core.StubExt;
  | import org.jboss.ws.extensions.wsrm.api.RMProvider;
  | 
  | import org.jboss.test.ws.jaxws.samples.wsrm.generated.SimpleService;
  | 
  | 
  | public final class SimpleServiceTestCase
  | {
  | 
  |    private static final String serviceURL = "http://localhost:8080/jaxws-samples-wsrm/SimpleService";
  |    
  |    public static void main(String[] args) throws Exception
  |    {
  |    	  String url = null;
  |    	  if ( args != null && args.length > 0 && args[0] != null )
  |    	  	url = args[0];
  |    	  else
  |    	  	url = serviceURL;
  |       System.out.println("Calling wsdl");
  |       QName serviceName = new QName("http://www.jboss.org/jbossws/ws-extensions/wsrm", "SimpleService");
  |       QName portName = new QName("http://www.jboss.org/jbossws/ws-extensions/wsrm", "SimpleServicePort");
  |       URL wsdlURL = new URL(url + "?wsdl");
  |       Service service = Service.create(wsdlURL, serviceName);
  |       SimpleService proxy = (SimpleService)service.getPort(SimpleService.class);
  | 
  |       ((StubExt)proxy).setConfigName("Standard Anonymous WSRM Client", "META-INF/wsrm-jaxws-client-config.xml");
  | 	        
  |       proxy.ping(); // one way call
  |       proxy.echo("Hello World!"); // request responce call
  |       ((RMProvider)proxy).closeSequence();
  |    }
  |    
  | }
  | 



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

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


From do-not-reply at jboss.com  Mon Aug  4 12:32:48 2008
From: do-not-reply at jboss.com (moweis)
Date: Mon, 4 Aug 2008 12:32:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <3688661.1217867568978.JavaMail.jboss@colo-br-02.atl.jboss.com>


Richard,

Ok, got it working.

You were right all long regarding the classpath.

Thanks for your help and patience!

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

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


From do-not-reply at jboss.com  Mon Aug  4 16:40:05 2008
From: do-not-reply at jboss.com (anaholzbach)
Date: Mon, 4 Aug 2008 16:40:05 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: No tests for @SchemaValidation
	annotation in 3.0.1 ?
Message-ID: <14981914.1217882405192.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

To answer ljgp ("does the schema validation feature really work?"), I've implemented a service endpoint that uses SchemaValidation and it seems to work. I started with an xsd, generated jaxb objects from it and implemented my endpoint using those jaxb objects and the @WebService and @WebMethod annotations. Upon deployment the WSDL was automatically generated. Then I added the @SchemaValidation tag and ran into problems with multiple schema elements and multiple namespaces, because the generated wsdl had one schema for the jaxb objects and another one (with a different namespace) for binding, service, message, portType, etc. I solved that by editing the wsdl to consolidate everything into one schema tag with one namespace and added that edited wsdl locally to my application under META-INF/wsdl. I also had to add minOccurs=1 and maxOccurs=1 in places, since the wsdl's schema ended up with less information than my original schema. 

A call to this webservice with a message that does not conform to the schema results in an Exception which is thrown by the StrictlyValidErrorHandler and wrapped in a SOAP Fault - something like:

 org.xml.sax.SAXException: cvc-complex-type.2.4.b: The content of element 'specimen' is not complete. One of '{specimen_id}' is expected.
  | 

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

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


From do-not-reply at jboss.com  Tue Aug  5 08:35:03 2008
From: do-not-reply at jboss.com (r.eloc)
Date: Tue, 5 Aug 2008 08:35:03 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: jbossws with apache
Message-ID: <10306700.1217939703182.JavaMail.jboss@colo-br-02.atl.jboss.com>

"palin" wrote : 
  | I would check what url apache is actually trying to connect to; I mean, it's ok that you get a "http GET not supported" if you access an endpoint using your browser. As a matter of fact, endpoints support POST, GET is supposed to work only for wsdl retrieval calls.
  | 

Why is GET not supported?  All the other web service frameworks I have used (Apache Axis, .NET) have supported that, it's quite useful when developing and testing.

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

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


From do-not-reply at jboss.com  Tue Aug  5 08:43:12 2008
From: do-not-reply at jboss.com (rohit.macherla)
Date: Tue, 5 Aug 2008 08:43:12 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - setRollbackOnly() error during
	WebService invocation
Message-ID: <20278513.1217940193059.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi all, 

I am using the JBoss 4.2.2.GA server installed on HP-UX platform. I have some WebServices deployed in this server. These WebServices connect to the Oracle Database 9 and after that, they invoke other WebServices. We are not using Connection Pooling when we connect to the Database and are using the regular : 
 

  | Class.forName("oracle.jdbc.driver.OracleDriver").newInstance();
  | con=DriverManager.getConnection("jdbc:oracle:thin:@hostname:sid","user","pwd");
  | 

We are closing the connection when all the things are done in our code. Since we are using Java, this closing of connection happens in the :

  | finally{
  | 
  | }
  |  block.
Note that our WebServices are just Java classes that have been annotated. Hence, we are not using any EJB or Servlets directly. Atleast we are not developing them. When our WebService is invoking other WS, we sometimes get the following exception : 
anonymous wrote : 
  | 
  | javax.xml.ws.soap.SOAPFaultException: java.lang.IllegalStateException: Cannot call setRollbackOnly() current thread is NOT ass 
  | ociated with a transaction 
  | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:69) 
  | at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:109) 
  | at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:553) 
  | at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:371) 
  | 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 $Proxy300.process(Unknown Source) 
  | at com.clarity.oss.ws.ServiceManagerCallbackImpl.orderStateChanged(ServiceManagerCallbackImpl.java:481) 
  | 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.wsf.container.jboss42.DefaultInvocationHandler.invoke(DefaultInvocationHandler.java:102) 
  | at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220) 
  | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:408) 
  | 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:595) 	 
  | 

According to the web, this error occurs when a transaction is marked for rollback while it is already closed. I have also found that a transaction timeout attribute needs to be updated, I don't know if it is relevant or not and I am unable to understand which timeout variable to update. 

Any help on this issue is much appreciated. Thank you.


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

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


From do-not-reply at jboss.com  Tue Aug  5 09:43:21 2008
From: do-not-reply at jboss.com (rodrigo.luizduiarte)
Date: Tue, 5 Aug 2008 09:43:21 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - java.lang.IllegalStateException:
	Endpoint already registered
Message-ID: <9889253.1217943801667.JavaMail.jboss@colo-br-02.atl.jboss.com>

Somebody knows to resolve this problem?
I don't know to resolve. Somebody can help me?

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

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


From do-not-reply at jboss.com  Tue Aug  5 10:00:20 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Tue, 5 Aug 2008 10:00:20 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: java.lang.IllegalStateException:
	Endpoint already regist
Message-ID: <11549832.1217944820191.JavaMail.jboss@colo-br-02.atl.jboss.com>

See JBWS-1762.
You need to 
 * upgrade to JBossWS 2.0.3 or higher
 * and switch to JBossAS  4.2.3 or higher.

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

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


From do-not-reply at jboss.com  Tue Aug  5 12:57:27 2008
From: do-not-reply at jboss.com (rodrigo.duarte)
Date: Tue, 5 Aug 2008 12:57:27 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: java.lang.IllegalStateException:
	Endpoint already regist
Message-ID: <29580618.1217955447779.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thank you Richard.
I will migrate from  jbossAS 4.2.2 to jbossAS 4.2.3

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

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


From do-not-reply at jboss.com  Tue Aug  5 13:29:41 2008
From: do-not-reply at jboss.com (macmanolo)
Date: Tue, 5 Aug 2008 13:29:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - wsconsume and rpc/encoded soap message
Message-ID: <15675646.1217957381421.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I'm was looking for a rpc/enc compatible client and according tohttp://xfire.codehaus.org/Stack+Comparison jbossws can to so.

I tried using the wsconsume tool to generate the stubs from a give wsdl.
Here's the error message I get:


anonymous wrote : ./wsconsume.sh -k -o /Users/mn/Desktop/webservice/ http://www*****/server_side/soap_server.php?wsdl
  | parsing WSDL...
  | 
  | 
  | [WARNING] src-resolve: Cannot resolve the name 'SOAP-ENC:Array' to a(n) 'type definition' component.
  |   line 50 of http://www*****/server_side/soap_server.php?wsdl#types?schema1
  | 
  | [ERROR] undefined simple or complex type 'SOAP-ENC:Array'
  |   line 50 of http://www*****/server_side/soap_server.php?wsdl
  | 
  | [ERROR] undefined attribute 'SOAP-ENC:arrayType'
  |   line 51 of http://www*****/server_side/soap_server.php?wsdl
  | 
  | [ERROR] undefined simple or complex type 'SOAP-ENC:Array'
  |   line 62 of http://www*****/server_side/soap_server.php?wsdl
  | 
  | [ERROR] undefined attribute 'SOAP-ENC:arrayType'
  |   line 63 of http://www*****/server_side/soap_server.php?wsdl
  | 
  | [ERROR] undefined simple or complex type 'SOAP-ENC:Array'
  |   line 69 of http://www*****/server_side/soap_server.php?wsdl

I get the same error message if I use the wsimport tool in the java 6 jdk. Since wsimport does not support rpc/enc I thought it has something to do with the encoding.

What went wrong here?
How can I set the encoding to rpc/enc in the wsconsume tool?

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

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


From do-not-reply at jboss.com  Wed Aug  6 05:14:10 2008
From: do-not-reply at jboss.com (ljgp)
Date: Wed, 6 Aug 2008 05:14:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: No tests for @SchemaValidation
	annotation in 3.0.1 ?
Message-ID: <25524050.1218014050538.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi Ana,

This sounds promising ! Which JBossWs and JBoss AS release did you use ? Would you mind sharing your code ?

Our procedure for developing the code was a bit different. We are using handwritten WSDL and XSD, everything else is generated from this, then the @SchemaValidation tag was added to the code.

Best regards, Luc.

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

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


From do-not-reply at jboss.com  Wed Aug  6 05:50:18 2008
From: do-not-reply at jboss.com (ravi.sah)
Date: Wed, 6 Aug 2008 05:50:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - problem of calling Web Service Client
	using jdk 1.6.0 with J
Message-ID: <31677780.1218016218964.JavaMail.jboss@colo-br-02.atl.jboss.com>

I developed a webservice using JAXWS and created a web service client for this web service.

I deployed the webservice on JBoss 4.2.0.GA. When I run the JBoss Server using jdk 1.5.0_14. It is working fine. But when I run the JBoss Server using jdk 1.6.0. It is throwing following error.

I tried the compile the webservice and its client using both versions of jdk separately and test it on JBoss server one by one. But the problem remains the same.

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 $Proxy83.markingsRetrieve(Unknown Source)
        at com.aha.web.TestServlet.processRequest(TestServlet.java:51)
        at com.aha.web.TestServlet.doPost(TestServlet.java:101)
        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.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:182)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
        at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
        at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
        at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:441)
        at org.jboss.ws.core.soap.SOAPMessageImpl.(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)
        ... 25 more

Can anyone help me?

Thanks in Advance.

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

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


From do-not-reply at jboss.com  Wed Aug  6 06:16:38 2008
From: do-not-reply at jboss.com (macmanolo)
Date: Wed, 6 Aug 2008 06:16:38 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Cannot consume any WSDL using
	wsconsume...
Message-ID: <2065330.1218017798419.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I don't know what I'm doing wrong but I cannot consume any webservice.
I have tried those:
http://soap.4s4c.com/weblogs/subscribe.wsdl
http://www.transactionalweb.com/SOAP/globalocator.wsdl
http://soap.search.msn.com/webservices.asmx?wsdl

Everytime I get an error message similar to this:
anonymous wrote : tag240127:bin ag$ ./wsconsume.sh -k -o /Users/ag/Desktop/webservice/ http://soap.4s4c.com/weblogs/subscribe.wsdl
  | parsing WSDL...
  | 
  | 
  | [WARNING] src-resolve: Cannot resolve the name 'soapenc:Array' to a(n) 'type definition' component.
  |   line 16 of http://soap.4s4c.com/weblogs/subscribe.wsdl#types?schema1
  | 
  | [ERROR] undefined simple or complex type 'soapenc:Array'
  |   line 16 of http://soap.4s4c.com/weblogs/subscribe.wsdl
  | 

What is my mistake? Please help me!

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

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


From do-not-reply at jboss.com  Wed Aug  6 07:38:46 2008
From: do-not-reply at jboss.com (kcp)
Date: Wed, 6 Aug 2008 07:38:46 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Cannot consume any WSDL using
	wsconsume...
Message-ID: <21144803.1218022726571.JavaMail.jboss@colo-br-02.atl.jboss.com>

These webservices use the rpc/encoded style. JbossWS does not support this style. It's use has been discouraged because of interoperability issues (keyword WS-I Basic Profile).

You could either use another webservice stack (e.g. Axis 1) or write a handlaer to transform the SOAP message.

Sorry, that I do not have any better new for you.
Charly



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

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


From do-not-reply at jboss.com  Wed Aug  6 07:43:20 2008
From: do-not-reply at jboss.com (kcp)
Date: Wed, 6 Aug 2008 07:43:20 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: problem of calling Web Service
	Client using jdk 1.6.0 wi
Message-ID: <27017045.1218023000379.JavaMail.jboss@colo-br-02.atl.jboss.com>

Yes, there some issues between Java6 and JBossWS. Since Java6, some webservice related libs are part of the JDK. Hence the problem.

The best solution would be to stick to Java5. For more details take a look at http://jbws.dyndns.org/mediawiki/index.php?title=Install_JBossWS#Using_JBossWS_with_JDK_6

Regards
Charly

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

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


From do-not-reply at jboss.com  Wed Aug  6 08:04:05 2008
From: do-not-reply at jboss.com (macmanolo)
Date: Wed, 6 Aug 2008 08:04:05 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Cannot consume any WSDL using
	wsconsume...
Message-ID: <17896130.1218024245350.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

thanks for your reply.

The JbossWS user guide says jbossws supports rpc/enc:
http://jbws.dyndns.org/mediawiki/index.php/JAX-WS_User_Guide#RPC.2FEncoded


Which other library would you recommend to use rpc/enc webservices (axis 1 is outdated)?


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

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


From do-not-reply at jboss.com  Wed Aug  6 08:23:34 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Wed, 6 Aug 2008 08:23:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Cannot consume any WSDL using
	wsconsume...
Message-ID: <3838792.1218025414136.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thanks for your note. I fixed our documentation.

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

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


From do-not-reply at jboss.com  Wed Aug  6 08:39:23 2008
From: do-not-reply at jboss.com (argol1278)
Date: Wed, 6 Aug 2008 08:39:23 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - get complex type in web service client
Message-ID: <9450026.1218026363424.JavaMail.jboss@colo-br-02.atl.jboss.com>

Whene i invoke web service in client application i have java.lang.NullPointerException. 
In log in SOAP message there are values but client can't get them. This is what i have done:

  | @XmlAccessorType(XmlAccessType.FIELD)
  | @XmlType(name = "Users",namespace="http://webServices.ejb/" ,propOrder = { "userid","name","surname","login",
  | "password","status","email" })
  | @XmlRootElement(namespace="http://webServices.ejb/",  name = "test")
  | public class Users implements Serializable{
  | 
  | 	@XmlElement(namespace="http://webServices.ejb/",name="userid")
  | 	private int userid;
  | 	@XmlElement(namespace="http://webServices.ejb/")
  | 	private String name;
  | 	@XmlElement(namespace="http://webServices.ejb/")
  | 	private String surname;
  | 	@XmlElement(namespace="http://webServices.ejb/")
  | 	private String login;
  | 	@XmlElement(namespace="http://webServices.ejb/")
  | 	private String password;
  | 	@XmlElement(namespace="http://webServices.ejb/")
  | 	private int status;
  | 	@XmlElement(namespace="http://webServices.ejb/")
  | 	private String email;
  | 	@XmlTransient
  | 	private Set addresses = new HashSet(0);
  | 	@XmlTransient
  | 	private Set accounts = new HashSet(0);
  | 
  | 
  | 
  | 	public Users() {
  | 	}
  | 
  | 	public int getUserid() {
  | 		return this.userid;
  | 	}
  | 
  | 	public void setUserid(int userid) {
  | 		this.userid = userid;
  | 	}
  | 
  | 	public String getName() {
  | 		return this.name;
  | 	}
  | 
  | 	public void setName(String name) {
  | 		this.name = name;
  | 	}
  | 
  | 	public String getSurname() {
  | 		return this.surname;
  | 	}
  | 
  | 	public void setSurname(String surname) {
  | 		this.surname = surname;
  | 	}
  | 
  | 	public String getLogin() {
  | 		return this.login;
  | 	}
  | 
  | 	public void setLogin(String login) {
  | 		this.login = login;
  | 	}
  | 
  | 	public String getPassword() {
  | 		return this.password;
  | 	}
  | 
  | 	public void setPassword(String password) {
  | 		this.password = password;
  | 	}
  | 
  | 	public int getStatus() {
  | 		return this.status;
  | 	}
  | 
  | 	public void setStatus(int status) {
  | 		this.status = status;
  | 	}
  | 
  | 	public String getEmail() {
  | 		return this.email;
  | 	}
  | 
  | 	public void setEmail(String email) {
  | 		this.email = email;
  | 	}
  | 
  | 	public Set getAccounts() {
  | 		return accounts;
  | 	}
  | 
  | 	public void setAccounts(Set accounts) {
  | 		this.accounts = accounts;
  | 	}
  | 
  | 	public Set getAddresses() {
  | 		return addresses;
  | 	}
  | 
  | 	public void setAddresses(Set addresses) {
  | 		this.addresses = addresses;
  | 	}
  | 
  | 
  | }
  | 
  | 


  | @Stateless(mappedName = "UsersOperations")
  | @WebService(name = "UsersOperations")
  | public class UsersOperations implements UsersOperationsEjbRemote, UsersOperationsEjbLocal {
  |  
  |     /**
  |      * Default constructor. 
  |      */
  |     public UsersOperations() {
  |         // TODO Auto-generated constructor stub
  |     }
  |  
  | 	 @WebMethod
  | 	 public Users test(@WebParam(name = "userid") int userid){
  |                  // Hibernate query
  | 		 Users u = queryUserDetails(userid);
  | 		 System.out.println(u.getLogin());
  | 		 return u;
  | 	 }
  |     
  |  
  | }
  | 

CLIENT


  | @WebService(name = "UsersOperations", targetNamespace = "http://webServices.ejb/")
  | @XmlSeeAlso({bankDB.Users.class})
  | public interface UsersOperations {
  | 	
  | @WebMethod
  |     @WebResult(targetNamespace = "http://webServices.ejb/")
  |     public Users test(@WebParam(name = "userid") int userid);
  | }
  | 


  | @WebServiceClient(name = "UsersOperationsService", targetNamespace = "http://webServices.ejb/", wsdlLocation = "http://127.0.0.1:8080/Bank-BankEJB/UsersOperations?wsdl")
  | public class UsersOperationsService
  |     extends Service
  | {
  |  
  |     private final static URL UsersOperationsService_WSDL_LOCATION;
  |  
  |     static {
  |         URL url = null;
  |         try {
  |             url = new URL("http://127.0.0.1:8080/Bank-BankEJB/UsersOperations?wsdl");
  |         } catch (MalformedURLException e) {
  |             e.printStackTrace();
  |         }
  |         UsersOperationsService_WSDL_LOCATION = url;
  |     }
  |  
  |     public UsersOperationsService(URL wsdlLocation, QName serviceName) {
  |         super(wsdlLocation, serviceName);
  |     }
  |  
  |     public UsersOperationsService() {
  |         super(UsersOperationsService_WSDL_LOCATION, new QName("http://webServices.ejb/", "UsersOperationsService"));
  |     }
  |  
  |     /**
  |      * 
  |      * @return
  |      *     returns Notification
  |      */
  |     @WebEndpoint(name = "UsersOperationsPort")
  |     public UsersOperations getUsersOperationsPort() {
  |         return (UsersOperations)super.getPort(new QName("http://webServices.ejb/", "UsersOperationsPort"), UsersOperations.class);
  |     }
  |  
  | 


  | // invoke web service in client
  | UsersOperationsService service = newUsersOperationsService();
  | UsersOperations ejb = service.getUsersOperationsPort();
  | Users u = ejb.test(2);
  | 



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

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


From do-not-reply at jboss.com  Wed Aug  6 10:34:53 2008
From: do-not-reply at jboss.com (cappeca)
Date: Wed, 6 Aug 2008 10:34:53 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Deploying JDeveloper/Oracle
	webservices on JBossWS
Message-ID: <11285226.1218033293803.JavaMail.jboss@colo-br-02.atl.jboss.com>

Has anybody found a solution to this problem?

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

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


From do-not-reply at jboss.com  Wed Aug  6 13:44:21 2008
From: do-not-reply at jboss.com (lfoggy)
Date: Wed, 6 Aug 2008 13:44:21 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Enabling MTOM-Support at JBossWS
	client fails
Message-ID: <33015827.1218044661210.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,
I am also having the same problem. I am using JAX-WS 2.0.3 with jboss 4.0.5, and enabling mtom on the client side to send an attachment to the server. When I check the content of the msg in trace mode, it looks like it is inline. Is there anything else I need to do or maybe the trace mode is not showing the correct msg body?
Any help would be appreciated.
Thanks,


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

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


From do-not-reply at jboss.com  Wed Aug  6 20:57:52 2008
From: do-not-reply at jboss.com (moxi)
Date: Wed, 6 Aug 2008 20:57:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Multiple WSDL bindings warning
Message-ID: <25869231.1218070672544.JavaMail.jboss@colo-br-02.atl.jboss.com>

"tperrigo" wrote : Any ideas on this one?  This has really got me stuck...
  | 

If you solved this problem, please let me know.

Because it's a real big problem, in production fills my logs to quickly, i have logs of Gigabytes only with this messages, because every call to WebService generate to many messages of this type. 

A quickly solution is change Log configuration, but i can't move that info in Production Servers becuz the client don't gave us permission to modify that configuration, and becuz our team use Log for other purposes.

I consume .Net Webservices too, we are using JBoss 4.2.2. 

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

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


From do-not-reply at jboss.com  Thu Aug  7 04:02:30 2008
From: do-not-reply at jboss.com (mick_mcgovern@hotmail.com)
Date: Thu, 7 Aug 2008 04:02:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - How to get complex types fully defined
	by exposed WSDL
Message-ID: <13802862.1218096150711.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I've got a web service EJB with a method signature that includes some of our own classes.

Problem is that the exposed WSDL defines these classes as complex but then does not provide the detailed definition - meaning that a client would not be able to dynamically call the method based purely on reading the WSDL.

Is there a way to get the exposed WSDL to fully define the complex types?

Code fragment and generated WSDL follows.

Thanks

JBoss AS 4.2.0

@WebService(name = "EnquireAccountServiceBean", targetNamespace = ServiceConstants.WEB_SERVICE_NAME_SPACE, serviceName = "EnquireAccountServiceBean")
@WebContext(contextRoot = "/XMLTranServiceBeanService")
@SOAPBinding(style = SOAPBinding.Style.RPC)
@Stateless(name = "EnquireAccountServiceBean")
public class EnquireAccountServiceBean extends BaseServiceBean implements EnquireAccountService {


	@WebMethod
	public AccountBalance enquireAccountBalance(TransactionInfo info, String accountNum) {	
	......
	
Exposed WSDL:





<xs:schema targetNamespace="http://www.whatever.com" version="1.0">
<xs:complexType name="transactionInfo"/>
<xs:complexType name="accountBalance"/>
</xs:schema>










......

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

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


From do-not-reply at jboss.com  Thu Aug  7 04:19:35 2008
From: do-not-reply at jboss.com (r.eloc)
Date: Thu, 7 Aug 2008 04:19:35 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - HTTP GET
Message-ID: <11542155.1218097175623.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I'm using JBoss to host JAX-WS services but when I try to visit the service URL (not the WSDL) in the browser then I get an error message saying "HTTP GET not supported", why is this?

Also, what is the best way to test JAX-WS services?  In .NET you get a test form if you visit the service URL in a browser and this allows you to submit values and see the XML response, is there anything like this for JAX-WS?

Thanks,
Russell!

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

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


From do-not-reply at jboss.com  Thu Aug  7 04:27:39 2008
From: do-not-reply at jboss.com (pacer11)
Date: Thu, 7 Aug 2008 04:27:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - java.lang.ClassCastException:
	org.jboss.ws.core.soap.SOAPMes
Message-ID: <25813982.1218097660000.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am using JBossWS with JBoss 4.2.3 with JDK 1.5 and getting the following Exception when executing a test Web Service.  The Web Service is successfully deployed

04:10:39,318 ERROR [[AccountService]] Servlet.service() for servlet AccountServi
ce threw exception
java.lang.ClassCastException: org.jboss.ws.core.soap.SOAPMessageImpl
        at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultH
elperJAXWS.java:245)
        at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(
SOAPFaultHelperJAXWS.java:174)
        at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessage
FromException(SOAP11BindingJAXWS.java:104)
        at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBindin
g.java:671)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHan
dlerImpl.java:488)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHand
lerImpl.java:284)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl
.java:201)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(Request
HandlerImpl.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(Appl
icationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
        at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi
lter.java:96)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:235)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:230)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:175)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit
yAssociationValve.java:182)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv
e.java:84)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:127)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:102)
        at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedC


Any Ideas??

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

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


From do-not-reply at jboss.com  Thu Aug  7 04:38:10 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Thu, 7 Aug 2008 04:38:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: HTTP GET
Message-ID: <23429013.1218098290660.JavaMail.jboss@colo-br-02.atl.jboss.com>

"r.eloc" wrote : Hi,
  | 
  | I'm using JBoss to host JAX-WS services but when I try to visit the service URL (not the WSDL) in the browser then I get an error message saying "HTTP GET not supported", why is this?
We only support GET for WSDL and XML schema retrievals.
"r.eloc" wrote : Also, what is the best way to test JAX-WS services?  In .NET you get a test form if you visit the service URL in a browser and this allows you to submit values and see the XML response, is there anything like this for JAX-WS?
  | 
No

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

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


From do-not-reply at jboss.com  Thu Aug  7 04:44:27 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Thu, 7 Aug 2008 04:44:27 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: HTTP GET
Message-ID: <26346530.1218098667907.JavaMail.jboss@colo-br-02.atl.jboss.com>

"r.eloc" wrote : Also, what is the best way to test JAX-WS services?
It depends on the kind of tests you need / how is going to run the tests (a developer or not).

anonymous wrote : In .NET you get a test form if you visit the service URL in a browser and this allows you to submit values and see the XML response, is there anything like this for JAX-WS?

Nothing specifically defined by JAX-WS of course, but you could take a look here: http://jbws.dyndns.org/mediawiki/index.php?title=Staging_tests

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

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


From do-not-reply at jboss.com  Thu Aug  7 05:15:49 2008
From: do-not-reply at jboss.com (r.eloc)
Date: Thu, 7 Aug 2008 05:15:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: HTTP GET
Message-ID: <13101939.1218100549173.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thanks for the quick reply.

I'm thinking from a developer perspective.  It's handy to use the web browser whilst developing just as a quick check to make sure the service has been deployed ok and is returning some kind of data and not an error message.

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

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


From do-not-reply at jboss.com  Thu Aug  7 06:06:51 2008
From: do-not-reply at jboss.com (craiggreenhalgh)
Date: Thu, 7 Aug 2008 06:06:51 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Hide certain fields in return object
Message-ID: <3876077.1218103611090.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I have an object that is returned as part of a web service.  If there anyway to not have certain fields as part of the returned object?

Thanks



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

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


From do-not-reply at jboss.com  Thu Aug  7 06:28:19 2008
From: do-not-reply at jboss.com (prabhun)
Date: Thu, 7 Aug 2008 06:28:19 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Migrating web services from Jboss 4.0.3
	to Jboss 4.2.3
Message-ID: <24640364.1218104899784.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

We have an application running on jboss-4.0.3SP1 which uses web services. The web services are invoked by Oracle procedures.

Now ,we are trying to migrate our application to Jboss 4.2.3.
However the existing web services are failing, throwing the following exception.
ERROR [SOAPFaultHelperJAXRPC] SOAP request exception javax.xml.rpc.soap.SOAPFaultException: Endpoint {http://localhost:8080/jmxclient/Jmxclientinvoker}JMXClientInvokerSeiPort does not contain operation meta data for: {http://127.0.0.1:8080/}sendTextmessage

We found that jboss-4.0.3SP1 uses Axis based web services and jboss-4.2.3 uses JbossWS. 

In that case is there no backward compatibility?  

Please let me know what will be the problem? and How to resolve this?
 
Thanks,
Prabhu


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

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


From do-not-reply at jboss.com  Thu Aug  7 11:12:50 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Thu, 7 Aug 2008 11:12:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Hide certain fields in return object
Message-ID: <28962340.1218121970848.JavaMail.jboss@colo-br-02.atl.jboss.com>

Try marking them as transient:

private transient String password;

Such fields will not be serialized.

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

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


From do-not-reply at jboss.com  Thu Aug  7 12:30:21 2008
From: do-not-reply at jboss.com (craiggreenhalgh)
Date: Thu, 7 Aug 2008 12:30:21 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Hide certain fields in return object
Message-ID: <25186384.1218126622087.JavaMail.jboss@colo-br-02.atl.jboss.com>

No I still need them persisted, just dont want to pass them back via a web service.  For example why would @Version be sent back?  It is not use to the user

Any ideas?

Thanks



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

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


From do-not-reply at jboss.com  Thu Aug  7 21:34:16 2008
From: do-not-reply at jboss.com (bhmt)
Date: Thu, 7 Aug 2008 21:34:16 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Slow Performance (configuration issue?)
Message-ID: <4127388.1218159256430.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hey all,

We did a performance test to compare Axis2 and JBoss WS implementatioins with a simple string echo service.

   
  | @WebService
  | @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.WRAPPED)
  | public interface EchoService
  | {
  |     @WebMethod
  |     public String echo(String s);
  | }
  |    
  | @Local
  | public interface EchoServiceLocal extends EchoService {}
  | 
  | @Remote
  | public interface EchoServiceRemote extends EchoService {}
  | 
  | @Stateless
  | @WebService(endpointInterface="com.echo.EchoService")
  | @WebContext(contextRoot="/echosvc")
  | public class EchoServiceBean implements EchoServiceRemote, EchoServiceLocal
  | {
  |     @Override
  |     public String echo(String s) { return s; }
  | }
  | 


Test1
-----
Client: JBoss 4.2.3.GA client
Server: JBoss 4.2.3.GA
Throughput: 50 requests/second


Test2
-----
Client: JBoss 4.2.3.GA client
Server: JBoss 4.2.3.GA + Axis2 WAR (v1.4)
Throughput: 200 requests/second


Test3
-----
Client: Axis2 (v1.4) client (using ADB)
Server: JBoss 4.2.3.GA + Axis2 (using ADB)
Throughput: 400 requests/second


Test4
-----
Client: JBoss 4.2.3.GA client
Server: Tomcat (v6) + Axis2 WAR (v1.4)
Throughput: 400 requests/second

All tests run 10000 request in single thread on same computer running both client and server.
Java version: 1.6.0_06,Sun Microsystems Inc.

It seems the jbossws-3.0.1-native-2.0.4.GA (this is the default one in JBoss 4.2.3.GA) is the bottleneck.
Tried jbossws-native-3.0.2.GA (replaced jbossws-3.0.1-native-2.0.4.GA) in the same JBossAS, got same result.

Is there any configuration for JBossWS that is limiting performance?


Thanks for your input!

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

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


From do-not-reply at jboss.com  Fri Aug  8 03:01:39 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 8 Aug 2008 03:01:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Hide certain fields in return object
Message-ID: <2428645.1218178899219.JavaMail.jboss@colo-br-02.atl.jboss.com>

Did you try using @XmlTransient jaxb annotation?

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

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


From do-not-reply at jboss.com  Fri Aug  8 08:27:52 2008
From: do-not-reply at jboss.com (karypid)
Date: Fri, 8 Aug 2008 08:27:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <29892487.1218198472898.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello,

I had the exact same problem and got as far as fixing the StubExt issue, but now I am stuck at the "Unable to create WSRM sequence" exception.

How did you fix that? My classpath seems to be correct. Here's the client:

	public void pingTest() {
  | 		System.err.println("java.class.path: "
  | 				+ System.getProperty("java.class.path"));
  | 		System.err.println("java.endorsed.dirs: "
  | 				+ System.getProperty("java.endorsed.dirs"));
  | 
  | 		URL jaxwsThatIsUsed = javax.xml.ws.Service.class.getProtectionDomain()
  | 				.getCodeSource().getLocation();
  | 		System.out.println("JAXWS that is used: " + jaxwsThatIsUsed);
  | 
  | 		ssp.ping("test");
  | 	}

The output is:

JAXWS that is used: file:/D:/Programs/jboss/as0/jboss-4.2.3.GA/client/jbossws-native-jaxws.jar
  | java.class.path: [lots of stuff...];D:\Programs\jboss\as0\jboss-4.2.3.GA\client\jbossws-native-core.jar;[...more stuff];D:\Programs\jboss\as0\jboss-4.2.3.GA\lib\endorsed\serializer.jar;D:\Programs\jboss\as0\jboss-4.2.3.GA\lib\endorsed\xalan.jar;D:\Programs\jboss\as0\jboss-4.2.3.GA\lib\endorsed\xercesImpl.jar
  | java.endorsed.dirs: D:\Programs\jboss\as0\jboss-4.2.3.GA\lib\endorsed

What did I miss?


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

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


From do-not-reply at jboss.com  Fri Aug  8 08:33:38 2008
From: do-not-reply at jboss.com (karypid)
Date: Fri, 8 Aug 2008 08:33:38 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <29080789.1218198818104.JavaMail.jboss@colo-br-02.atl.jboss.com>

Actually, I don't have the exact same problem. My exception is;

org.jboss.ws.extensions.wsrm.api.RMException: Unable to create WSRM sequence
  | at org.jboss.ws.core.jaxws.client.ClientImpl.createSequence(ClientImpl.java:563)
  | at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
  | at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
  | at $Proxy21.ping(Unknown Source)
  | at test.ws.stationsService.StationsServiceTest.pingTest(StationsServiceTest.java:58)
  | 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.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
  | at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
  | at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
  | at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
  | at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
  | at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:66)
  | at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35)
  | at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
  | at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
  | at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
  | at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38)
  | at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
  | at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
  | at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
  | at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
  | at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
  | Caused by: org.jboss.ws.WSException: Cannot obtain operation meta data for: {http://docs.oasis-open.org/ws-rx/wsrm/200702}CreateSequence
  | at org.jboss.ws.core.CommonClient.getOperationMetaData(CommonClient.java:203)
  | at org.jboss.ws.core.CommonClient.getOperationMetaData(CommonClient.java:184)
  | at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:309)
  | at org.jboss.ws.core.jaxws.client.ClientImpl.createSequence(ClientImpl.java:550)
  | ... 24 more

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

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


From do-not-reply at jboss.com  Fri Aug  8 16:12:49 2008
From: do-not-reply at jboss.com (shelleyjose)
Date: Fri, 8 Aug 2008 16:12:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: consume WS error after update to
	JBossWS 2.0
Message-ID: <18362854.1218226369551.JavaMail.jboss@colo-br-02.atl.jboss.com>

I was trying to run a standalone client for a webservice and I had the same issue. Removed  jaxws-rt.jar and jaxws-tools.jar from JBOSS_HOME/client and copied the xercesImpl.jar file from JBOSS_HOME/lib/endorsed to JBOSS_HOME/client. That solved the problem. 

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

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


From do-not-reply at jboss.com  Mon Aug 11 04:51:09 2008
From: do-not-reply at jboss.com (karypid)
Date: Mon, 11 Aug 2008 04:51:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <18885333.1218444669305.JavaMail.jboss@colo-br-02.atl.jboss.com>

Ok, I've got WS-ReliableMessaging to work. The problem was that the WS-Policy information had to be removed from the WSDL and put into a separate file, using the @PolicyAttachment annotation to refer to it.

The tutorial at http://jbws.dyndns.org/mediawiki/index.php?title=Native_WS-ReliableMessaging_Tutorial imports the WS-Policy namespace in the WSDL file and embeds the policy there. But JBoss generates and publishes its own WSDL for the web service, using the information from the annotations.

The solution can be found at: http://jbws.dyndns.org/mediawiki/index.php?title=WS_Reliable_Messaging

You need to create a separate XML file (e.g. wsrm-exactly-once-in-order-policy.xml) containing the policy: <?xml version="1.0" encoding="UTF-8"?>
  | <wsp:Policy
  |    wsu:Id="exactly_one_in_order_rm_delivery"
  |    xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
  |    xmlns:wsrmp="http://docs.oasis-open.org/ws-rx/wsrmp/200702"
  |    xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
  |    <wsrmp:DeliveryAssurance>
  |       <wsp:Policy>
  |          <wsrmp:ExactlyOnce/>
  |          <wsrmp:InOrder/>
  |       </wsp:Policy>
  |    </wsrmp:DeliveryAssurance>
  | </wsp:Policy>
  | 
Then, in the web service implementation, use annotations to link that policy to the web service:
@WebService
  | @EndpointConfig(
  |         configFile = "META-INF/wsrm-jaxws-endpoint-config.xml",
  |         configName = "Standard WSRM Endpoint"
  | )
  | @PolicyAttachment(@Policy(
  |         policyFileLocation = "META-INF/wsrm-exactly-once-in-order-policy.xml",
  |         scope = PolicyScopeLevel.WSDL_BINDING)
  | )
  | public class MyRMService { ...

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

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


From do-not-reply at jboss.com  Mon Aug 11 04:59:50 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 11 Aug 2008 04:59:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <27846727.1218445190301.JavaMail.jboss@colo-br-02.atl.jboss.com>

"karypid" wrote : Ok, I've got WS-ReliableMessaging to work. The problem was that the WS-Policy information had to be removed from the WSDL and put into a separate file, using the @PolicyAttachment annotation to refer to it.
  | 
  | The tutorial at http://jbws.dyndns.org/mediawiki/index.php?title=Native_WS-ReliableMessaging_Tutorial imports the WS-Policy namespace in the WSDL file and embeds the policy there. But JBoss generates and publishes its own WSDL for the web service, using the information from the annotations.
  | 
This is the reason why tutorial specifies 
wsdlLocation = "WEB-INF/wsdl/SimpleService.wsdl"
in service endpoint (it forces JBossWS to don't generate the WSDL at runtime but use provided one instead).

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

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


From do-not-reply at jboss.com  Mon Aug 11 05:18:30 2008
From: do-not-reply at jboss.com (karypid)
Date: Mon, 11 Aug 2008 05:18:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <10726025.1218446310169.JavaMail.jboss@colo-br-02.atl.jboss.com>

Understood. However, I can't get it to work. When I add the WSDL file to the META-INF/wsdl folder of my EJB jar (I use a stateless session bean to implement the web service and the "start from WSDL" approach via wsconsume), JBoss publishes the web service using a file:// URL. For instance, the following SLSB (notice that the PolicyFile annotation is commented out):

@Stateless
  | @WebService(serviceName = "StationsService", wsdlLocation = "META-INF/wsdl/StationsService.wsdl",
  |     targetNamespace = "http://www.armoniq.com/StationsService/",
  |     endpointInterface = "com.armoniq.stationsservice.StationsServicePortType"
  | )
  | @EndpointConfig(configFile = "META-INF/wsrm-jaxws-endpoint-config.xml", configName = "Standard WSRM Endpoint")
  | //@PolicyAttachment(@Policy(policyFileLocation = "META-INF/wsrm-exactly-once-in-order-policy.xml", scope = PolicyScopeLevel.WSDL_BINDING))
  | public class StationsService implements StationsServicePortType {
  | 	// Logger logger = Logger
  | 	// .getLogger(StationsService.class.getClass().getName());
  | 
  | 	public void ping(String in) {
  | 		System.out.println("Ping received with text: " + in);
  | 		// logger.log(Level.INFO, "Ping received with text: " + in);
  | 	}
  | }

Causes JBoss to publish this WSDL:

<wsdl:definitions name="StationsService"
  |     targetNamespace="http://www.armoniq.com/StationsService/"
  |     xmlns:echoes="http:/www.armoniq.com/echoes/2008/core"
  |     xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" 
  |     xmlns:tns="http://www.armoniq.com/StationsService/" 
  |     xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" 
  |     xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" 
  |     xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  |  <wsdl:types>
  |   <xsd:schema targetNamespace="http://www.armoniq.com/StationsService/">
  |    <xsd:import namespace="http:/www.armoniq.com/echoes/2008/core"
  |            schemaLocation="http://localhost:8080/myrm.ear-myrm.ws.impl/StationsService?wsdl&resource=myrm.base.xsd"/>
  |    <xsd:element name="ping">
  |     <xsd:complexType>
  |      <xsd:sequence>
  |       <xsd:element name="in" type="xsd:string"/>
  |      </xsd:sequence>
  |     </xsd:complexType>
  |    </xsd:element>
  |   </xsd:schema>
  |  </wsdl:types>
  |  <wsdl:message name="pingRequest">
  |   <wsdl:part element="tns:ping" name="parameters"/>
  |  </wsdl:message>
  |  <wsdl:portType name="StationsServicePortType">
  |   <wsdl:operation name="ping">
  |    <wsdl:input message="tns:pingRequest"/>
  |   </wsdl:operation>
  |  </wsdl:portType>
  |  <wsdl:binding name="StationsServiceSOAP" type="tns:StationsServicePortType">
  |   <wsp:PolicyReference URI="#wsrm11policy"/>
  |   <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
  |   <wsdl:operation name="ping">
  |    <soap:operation soapAction="http://www.armoniq.com/StationsService/fetchSchedule"/>
  |    <wsdl:input>
  |     <soap:body use="literal"/>
  |    </wsdl:input>
  |   </wsdl:operation>
  |  </wsdl:binding>
  |  <wsdl:service name="StationsService">
  |   <wsdl:port binding="tns:StationsServiceSOAP" name="StationsServicePort">
  |    <soap:address location="file://localhost:8080/myrm.ear-myrm.ws.impl/StationsService"/>
  |   </wsdl:port>
  |  </wsdl:service>
  |  <wsp:UsingPolicy/>
  |  <wsp:Policy wsu:Id="wsrm11policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
  |   <wsp:All>
  |    <wsp:ExactlyOne>
  |     <wsp:All>
  |      <ns1:RMAssertion xmlns:ns1="http://docs.oasis-open.org/ws-rx/wsrmp/200702"/>
  |      <ns2:UsingAddressing xmlns:ns2="http://www.w3.org/2006/05/addressing/wsdl"/>
  |     </wsp:All>
  |    </wsp:ExactlyOne>
  |   </wsp:All>
  |  </wsp:Policy>
  | </wsdl:definitions>

Notice the <soap:address> tag that uses file:// as a protocol.

Even in the jbossws management console (http://localhost:8080/jbossws/services) the link uses this address and clicking on it does not work. You have to copy the link from the web page, paste it to the address bar of the browser and replace file: with http: to get to the (incorrect) WSDL.

I am using JBoss 4.2.3 and JBossWS 3.0.2.


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

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


From do-not-reply at jboss.com  Mon Aug 11 06:57:38 2008
From: do-not-reply at jboss.com (karypid)
Date: Mon, 11 Aug 2008 06:57:38 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <10206274.1218452258639.JavaMail.jboss@colo-br-02.atl.jboss.com>

Ok, I've finally found out what was wrong.

First of all, the tutorial is correct and everything should work fine
even without the @Policy annotation (provided of course you embed
your WS-Policy in the WSDL file).

Strange thing though:

When using "wsdLocation" in @WebService, JBoss reads the WSDL file you provided and does the following:

1) if the <soap:address> tag in the WSDL file has a "file://..." URL in it,
it does NOT replace it with the actual address where your web service
endpoint was bound.
2) if the <soap:address> tag in the WSDL file has an "http://..." URL in it,
it replaces it with the actual address where your web service
endpoint was bound.

I had the bad luck of having specified file://path/to/my/contract.wsdl causing the weird behavior.

I know this is totally unrelated to the topic of this thread by now, but I
wanted not to leave any lingering doubt regarding the approach without
@Policy (which I prefer by the way).

In any case, before I go running to JIRA, can someone explain if there's
some reason why JBoss won't touch the file:// address bindings and
therefore this is proper behavior, or would you consider this a bug?


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

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


From do-not-reply at jboss.com  Mon Aug 11 08:27:26 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 11 Aug 2008 08:27:26 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <14442780.1218457646120.JavaMail.jboss@colo-br-02.atl.jboss.com>

It's a bug

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

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


From do-not-reply at jboss.com  Mon Aug 11 08:56:34 2008
From: do-not-reply at jboss.com (karypid)
Date: Mon, 11 Aug 2008 08:56:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM Exception: cannot be cast to
	org.jboss.ws.core.Stu
Message-ID: <5720249.1218459394408.JavaMail.jboss@colo-br-02.atl.jboss.com>

In that case... https://jira.jboss.org/jira/browse/JBWS-2277

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

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


From do-not-reply at jboss.com  Mon Aug 11 14:28:28 2008
From: do-not-reply at jboss.com (karypid)
Date: Mon, 11 Aug 2008 14:28:28 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: standard BASIC AUTH
Message-ID: <1297591.1218479308959.JavaMail.jboss@colo-br-02.atl.jboss.com>

Have you found a way to do this? I also asked this question recently,
but for an EJB endpoint. See:

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=140182.

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

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


From do-not-reply at jboss.com  Mon Aug 11 14:42:30 2008
From: do-not-reply at jboss.com (lfoggy)
Date: Mon, 11 Aug 2008 14:42:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Enabling MTOM-Support at JBossWS
	client fails
Message-ID: <7950488.1218480150965.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,
I have been trying to compare my classes with the sample xop examples in jbossws package and finally I was able to find the problem.
Here are my classes:
class AttachmentType {
     @XmlMimeType("application/octet-stream")
     protected DataHandler dh;

....

class AttachmentTypeHolder {
    protected List attachments;

....

In my endpoint class if I have the following method signature, then the xop works:

    public AttachmentType echoDataHandler(DHRequest request)

but if I change the method signature to this:

    public AttachmentHolder echoDataHandler(DHRequest request)

then the response is returned inline and not xop encoded.

Is there anything I have to do to fix this. I am using Doc/Literal Wrapped wsdl, with a WSDL-first approach.

Any help would really be appreciated.
Thanks,


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

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


From do-not-reply at jboss.com  Tue Aug 12 07:39:43 2008
From: do-not-reply at jboss.com (karypid)
Date: Tue, 12 Aug 2008 07:39:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WS-RM violates both <ExactlyOnce/> and
	<InOrder/> ?
Message-ID: <18712077.1218541183624.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have a web service with WS-RM enabled. Here is the WSDL as published by JBoss, with the associated policy in bold fonts:

<definitions name="StationsService" targetNamespace="http://www.armoniq.com/StationsService/" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://www.armoniq.com/StationsService/" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  |  <types>
  |   <xs:schema targetNamespace="http://www.armoniq.com/StationsService/" version="1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema">
  |    <xs:element name="echo">
  |     <xs:complexType>
  |      <xs:sequence>
  |       <xs:element name="in" type="xs:string"/>
  |      </xs:sequence>
  |     </xs:complexType>
  |    </xs:element>
  |    <xs:element name="echoResponse">
  |     <xs:complexType>
  |      <xs:sequence>
  |       <xs:element name="out" type="xs:string"/>
  |      </xs:sequence>
  |     </xs:complexType>
  |    </xs:element>
  |   </xs:schema>
  |  </types>
  |  <message name="StationsServicePortType_echoResponse">
  |   <part element="tns:echoResponse" name="echoResponse"/>
  |  </message>
  |  <message name="StationsServicePortType_echo">
  |   <part element="tns:echo" name="echo"/>
  |  </message>
  |  <portType name="StationsServicePortType">
  |   <operation name="echo" parameterOrder="echo">
  |    <input message="tns:StationsServicePortType_echo"/>
  |    <output message="tns:StationsServicePortType_echoResponse"/>
  |   </operation>
  |  </portType>
  |  <binding name="StationsServicePortTypeBinding" type="tns:StationsServicePortType">
  |   <wsp:PolicyReference URI="#exactly_one_in_order_rm_delivery"/>
  |   <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
  |   <operation name="echo">
  |    <soap:operation soapAction="http://www.armoniq.com/StationsService/echo"/>
  |    <input>
  |     <soap:body use="literal"/>
  |    </input>
  |    <output>
  |     <soap:body use="literal"/>
  |    </output>
  |   </operation>
  |  </binding>
  |  <service name="StationsService">
  |   <port binding="tns:StationsServicePortTypeBinding" name="StationsServicePort">
  |    <soap:address location="http://localhost:8080/eessi.ear-eessi.ws.mta/StationsServiceImpl"/>
  |   </port>
  |  </service>
  |  <wsp:Policy wsu:Id="exactly_one_in_order_rm_delivery" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
  |   <wsp:All>
  |    <wsrmp:DeliveryAssurance xmlns:wsrmp="http://docs.oasis-open.org/ws-rx/wsrmp/200702">
  |     <wsp:Policy>
  |      <wsp:ExactlyOne>
  |       <wsp:All>
  |        <wsrmp:ExactlyOnce/>
  |        <wsrmp:InOrder/>
  |       </wsp:All>
  |      </wsp:ExactlyOne>
  |     </wsp:Policy>
  |    </wsrmp:DeliveryAssurance>
  |   </wsp:All>
  |  </wsp:Policy>
  | </definitions>

When starting up, JBoss logs that that the service is running properly with the appropriate JAX-WS handlers for WS-ReliableMessaging:

HandlerMetaDataJAXWS:
  |  type=POST
  |  name=WSAddressing Handler
  |  class=class org.jboss.ws.extensions.addressing.jaxws.WSAddressingServerHandler
  |  params=[]
  |  protocols=##SOAP11_HTTP
  |  services=null
  |  ports=null
  | 
  | HandlerMetaDataJAXWS:
  |  type=POST
  |  name=WSRM Handler
  |  class=class org.jboss.ws.extensions.wsrm.jaxws.RMServerHandler
  |  params=[]
  |  protocols=##SOAP11_HTTP
  |  services=null
  |  ports=null
  | 2008-08-12 14:16:20,081 DEBUG [org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl] RMDeploymentAspect:Start
  | 2008-08-12 14:16:20,081 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider] provide SPI 'class org.jboss.wsf.spi.management.ServerConfigFactory'
  | 2008-08-12 14:16:20,081 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider] class org.jboss.wsf.spi.management.ServerConfigFactory Implementation: org.jboss.wsf.framework.management.ServerConfigFactoryImpl at 187b08d
  | 2008-08-12 14:16:20,112 INFO  [org.jboss.ws.extensions.wsrm.server.RMDeploymentAspect] WS-RM invocation handler associated with endpoint http://localhost:8080/eessi.ear-eessi.ws.mta/StationsServiceImpl
  | 2008-08-12 14:16:20,112 DEBUG [org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl] PublishContractDeploymentAspect:Start
  | 2008-08-12 14:16:20,112 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider] provide SPI 'class org.jboss.wsf.spi.management.ServerConfigFactory'
  | 2008-08-12 14:16:20,112 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider] class org.jboss.wsf.spi.management.ServerConfigFactory Implementation: org.jboss.wsf.framework.management.ServerConfigFactoryImpl at 7720d7
  | 2008-08-12 14:16:20,112 DEBUG [org.jboss.wsf.stack.jbws.WSDLFilePublisher] Publish WSDL file: file:/D:/Programs/jboss/as0/jboss-4.2.3.GA/server/default/tmp/jbossws/StationsService13926.wsdl
  | 2008-08-12 14:16:20,112 INFO  [org.jboss.wsf.stack.jbws.WSDLFilePublisher] WSDL published to: file:/D:/Programs/jboss/as0/jboss-4.2.3.GA/server/default/data/wsdl/eessi.ear.ear/eessi.ws.mta.jar/StationsService13926.wsdl

I then try to send two messages from a simple Java client using asynchronous invocation:

	public void wsrmTest() throws InterruptedException, ExecutionException,
  | 			MalformedURLException {
  | 		final int MAX_PACKETS = 2;
  | 		Response<EchoResponse> response = null;
  | 
  | 		QName serviceName = new QName(
  | 				"http://www.armoniq.com/StationsService/", "StationsService");
  | 		URL wsdlURL = new URL(
  | 				"http://localhost:8080/eessi.ear-eessi.ws.mta/StationsServiceImpl?wsdl");
  | 		StationsService ss = new StationsService(wsdlURL, serviceName);
  | 		ssp = ss.getStationsServicePort();
  | 		((StubExt) ssp).setConfigName("Standard Anonymous WSRM Client",
  | 				"META-INF/wsrm-jaxws-client-config.xml");
  | 
  | 		for (int i = 0; i < MAX_PACKETS; i++)
  | 			response = ssp.echoAsync("PACKET " + i);
  | 		System.out.println("Sent out all my packets asynchronously...");
  | 
  | 		System.out.println("Last response: " + response.get());
  | 		Thread.sleep((MAX_PACKETS + 1) * 2000);
  | 		System.out.println("All packets should have returned...");
  | 		((RMProvider) ssp).closeSequence();
  | 	}

When running, JBoss throws this exception:

2008-08-12 14:21:18,039 DEBUG [org.jboss.ws.extensions.wsrm.server.RMServerSequence] Inbound Sequence: urn:uuid:5074e327-2f26-424f-a744-47836a765fd, received message no. 1
  | 2008-08-12 14:21:18,055 DEBUG [org.jboss.ws.extensions.wsrm.server.RMInvocationHandler] Invoking method: echo
  | 2008-08-12 14:21:18,055 DEBUG [org.jboss.ws.core.EndpointInvocation] getRequestPayload
  | 2008-08-12 14:21:18,055 DEBUG [org.jboss.ws.core.EndpointInvocation] getRequestParamValue: {http://www.armoniq.com/StationsService/}echo
  | 2008-08-12 14:21:18,055 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] -----------------------------------
  | 2008-08-12 14:21:18,055 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] Transitioning from XML_VALID to OBJECT_VALID
  | 2008-08-12 14:21:18,055 DEBUG [org.jboss.ws.core.soap.XMLContent] getObjectValue [xmlType={http://www.armoniq.com/StationsService/}echo,javaType=class com.armoniq.stationsservice.Echo]
  | 2008-08-12 14:21:18,055 DEBUG [org.jboss.ws.core.jaxws.JAXBDeserializer] deserialize: [xmlName={http://www.armoniq.com/StationsService/}echo,xmlType={http://www.armoniq.com/StationsService/}echo]
  | 2008-08-12 14:21:18,055 DEBUG [org.jboss.ws.core.jaxws.handler.MessageContextJAXWS] Begin response processing
  | 2008-08-12 14:21:18,055 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] popMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at 54c2b8 (Thread http-localhost%2F127.0.0.1-8080-5)
  | 2008-08-12 14:21:18,055 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] pushMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at 1ce4608 (Thread http-localhost%2F127.0.0.1-8080-5)
  | 2008-08-12 14:21:18,055 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception
  | org.jboss.ws.extensions.wsrm.RMFault: The value of wsrm:Identifier is not a known Sequence identifier.
  | 	at org.jboss.ws.extensions.wsrm.server.RMInvocationHandler.getUnknownSequenceFault(RMInvocationHandler.java:297)
  | 	at org.jboss.ws.extensions.wsrm.server.RMInvocationHandler.prepareResponseContext(RMInvocationHandler.java:242)
  | 	at org.jboss.ws.extensions.wsrm.server.RMInvocationHandler.invoke(RMInvocationHandler.java:306)
  | 	at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:221)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:466)
  | 	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:182)
  | 	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)
  | 2008-08-12 14:21:18,071 DEBUG [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] Cannot obtain fault meta data for: class org.jboss.ws.extensions.wsrm.RMFault
  | 2008-08-12 14:21:18,071 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] callFaultHandlerChain: PRE
  | 2008-08-12 14:21:18,071 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] callFaultHandlerChain: ENDPOINT
  | 2008-08-12 14:21:18,071 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] callFaultHandlerChain: POST
  | 2008-08-12 14:21:18,071 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Enter: handleOutBoundFault
  | 2008-08-12 14:21:18,071 DEBUG [org.jboss.ws.extensions.addressing.jaxws.WSAddressingServerHandler] handleFault
  | 2008-08-12 14:21:18,071 DEBUG [org.jboss.ws.extensions.wsrm.jaxws.RMServerHandler] handling fault message
  | 2008-08-12 14:21:18,071 DEBUG [org.jboss.ws.extensions.wsrm.jaxws.RMServerHandler] SequenceFault WSRM message was serialized to payload
  | 2008-08-12 14:21:18,071 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Exit: handleOutBoundFault with status: true
  | 2008-08-12 14:21:18,071 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] closeHandlerChain
  | 2008-08-12 14:21:18,071 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] close
  | 2008-08-12 14:21:18,071 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] closeHandlerChain
  | 2008-08-12 14:21:18,071 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] close
  | 2008-08-12 14:21:18,071 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] closeHandlerChain
  | 2008-08-12 14:21:18,071 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] close

If I don't use the asynchronous invocation, my client works just fine. Any idea what I am doing wrong?


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

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


From do-not-reply at jboss.com  Tue Aug 12 08:31:44 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Tue, 12 Aug 2008 08:31:44 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM violates both <ExactlyOnce/>
	and <InOrder/> ?
Message-ID: <21987474.1218544304129.JavaMail.jboss@colo-br-02.atl.jboss.com>

Can you submit exchanged messages to this forum?

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

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


From do-not-reply at jboss.com  Tue Aug 12 08:56:30 2008
From: do-not-reply at jboss.com (kosulin)
Date: Tue, 12 Aug 2008 08:56:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Enabling MTOM-Support at JBossWS
	client fails
Message-ID: <32768446.1218545790427.JavaMail.jboss@colo-br-02.atl.jboss.com>

The cause is, may be, in 'protected' declaration.
I used 

private DataHandler stmtContent;

@XmlElement(name = "StatementContent", required = false)
@XmlMimeType("application/zip")
public final DataHandler getStmtContent()
{
	return this.stmtContent;
}
public final void setStmtContent(DataHandler stmtContent)
{
	this.stmtContent = stmtContent;
}

and it works fine with .NET client.

Another thing you can do:
put into your endpoint declaration
@MTOM(enabled = true)
in addition to @BindingType


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

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


From do-not-reply at jboss.com  Tue Aug 12 09:09:00 2008
From: do-not-reply at jboss.com (kosulin)
Date: Tue, 12 Aug 2008 09:09:00 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Hide certain fields in return object
Message-ID: <4520226.1218546540886.JavaMail.jboss@colo-br-02.atl.jboss.com>

Not sure this is what you want, but if I need to send some attribute only if it is not empty, then I declare it as:

	@XmlElement(name = "StatementDate", required = false)
	public final Date getStmtDate()
	{
		return this.stmtDate;
	}
If I want the the attribute to be sent even if it is empty, I use nillable=true

This would not work if you want to prevent a non-empty attribute from being sent though.


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

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


From do-not-reply at jboss.com  Tue Aug 12 09:17:40 2008
From: do-not-reply at jboss.com (kosulin)
Date: Tue, 12 Aug 2008 09:17:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WS Secutiry configration questions
Message-ID: <6865034.1218547060400.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,
We have few external clients requesting their data from the same server using the same endpoint.
I would like to configure security using both their and ours private keys as follows:
- every client signs their request with their private key, and the server uses the corresponding public key (from keystore) to authorize them and get their principal.
- our response is signed with our server private key (from trusted store), and clients use our public key to authenticate the response.

I tried to get through WIKI and User Guide, tried jboss-wsse-server.xml configs from there, but there is no example similar to what I need if I did not miss something.

How do I configure WS-Security for this scenario?

My env: java 6, JBoss 5.0.0CR1, jbossws core 3.02. Clients are .NET if this is important.

Thanks.

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

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


From do-not-reply at jboss.com  Tue Aug 12 09:28:20 2008
From: do-not-reply at jboss.com (kosulin)
Date: Tue, 12 Aug 2008 09:28:20 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Location of keysore and truststore for
	jboss-ws-server.xml
Message-ID: <7665445.1218547700233.JavaMail.jboss@colo-br-02.atl.jboss.com>

Is it possible to point jboss-ws-server.xml to keystore and truststore located somewhere on file system instead of WEB_INF?
<key-store-file>${jboss.server.home.dir}/conf/my.keystore</key-store-file> is not working.
Thanks.

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

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


From do-not-reply at jboss.com  Tue Aug 12 09:36:06 2008
From: do-not-reply at jboss.com (kosulin)
Date: Tue, 12 Aug 2008 09:36:06 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - I meant, jboss-wsse-server.xml
Message-ID: <28619629.1218548166700.JavaMail.jboss@colo-br-02.atl.jboss.com>

Wrong file name/

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

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


From do-not-reply at jboss.com  Tue Aug 12 09:51:03 2008
From: do-not-reply at jboss.com (kosulin)
Date: Tue, 12 Aug 2008 09:51:03 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: problem of calling Web Service
	Client using jdk 1.6.0 wi
Message-ID: <29827553.1218549063385.JavaMail.jboss@colo-br-02.atl.jboss.com>

It is possible to use java 6 with jbossws (I use 3.02).
You have to add 
-Djava.endorsed.dirs="%JBOSS_HOME%\lib\endorsed"
for Windows or
-Djava.endorsed.dirs=$JBOSS_HOME/lib/endorsed
for Linux/Unix.

into your startup script JAVA_OPTS.

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

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


From do-not-reply at jboss.com  Tue Aug 12 10:02:06 2008
From: do-not-reply at jboss.com (karypid)
Date: Tue, 12 Aug 2008 10:02:06 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM violates both <ExactlyOnce/>
	and <InOrder/> ?
Message-ID: <4231152.1218549726882.JavaMail.jboss@colo-br-02.atl.jboss.com>

I created a new project from scratch and the exception has gone away.

I believe that the reason is that I was using a synchronous-only interface on the server side.

The service endpoint interface code for the server was generated WITHOUT using: <enableAsyncMapping>true</enableAsyncMapping>

For the client I re-ran wsconsume and generated a SEI with asynchronous mapping enabled.

Unfortunately I placed the SEI in my EAR's /lib folder and forgot to update it.

Asynchronous invocation now works but the messages are delivered out-of-order.
I will create a new post for that...


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

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


From do-not-reply at jboss.com  Tue Aug 12 10:55:53 2008
From: do-not-reply at jboss.com (karypid)
Date: Tue, 12 Aug 2008 10:55:53 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Can't get WS-RM to do ExactlyOnce +
	InOrder
Message-ID: <26226333.1218552953999.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am using this web service to test WS-RM:
@Stateless
  | @WebService(serviceName = "MyRMTestService",
  |         portName = "MyRMTestSOAP",
  |         targetNamespace = "http://www.example.org/MyRMTest/",
  |         endpointInterface = "org.example.myrmtest.MyRMTest"
  | )
  | @EndpointConfig(
  |         configFile = "META-INF/wsrm-jaxws-endpoint-config.xml",
  |         configName = "Standard WSRM Endpoint"
  | )
  | @PolicyAttachment(@Policy(
  |         policyFileLocation = "META-INF/wsrm-exactly-once-in-order-policy.xml",
  |         scope = PolicyScopeLevel.WSDL_BINDING
  | ))
  | public class MyRMTestService {
  | 	public String echo(String in) {
  | 		System.out.println("RECEIVED: " + in);
  | 		try {
  | 			Thread.sleep(2000);
  | 		} catch (InterruptedException e) {
  | 			e.printStackTrace();
  | 		}
  | 		System.out.println("RETURNING from: " + in);
  | 		return in;
  | 	}
  | }The policy file contains:<?xml version="1.0" encoding="UTF-8"?>
  | <wsp:Policy wsu:Id="exactly_one_in_order_rm_delivery"
  | 	xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
  | 	xmlns:wsrmp="http://docs.oasis-open.org/ws-rx/wsrmp/200702"
  | 	xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
  | 	<wsrmp:DeliveryAssurance>
  | 		<wsp:Policy>
  | 			<wsrmp:ExactlyOnce />
  | 			<wsrmp:InOrder />
  | 		</wsp:Policy>
  | 	</wsrmp:DeliveryAssurance>
  | </wsp:Policy>I was assuming that if I send out 5 messages using a simple client they should arrive exactly once and in order. Instead, using this client:	public void wsrmTest() throws Throwable {
  | 		final int MAX_PACKETS = 5;
  | 
  | 		try {
  | 			QName serviceName = new QName("http://www.example.org/MyRMTest/",
  | 					"MyRMTestService");
  | 			URL wsdlURL = new URL(
  | 					"http://localhost:8080/myRMTest/MyRMTestService?wsdl");
  | 			MyRMTest_Service ss = new MyRMTest_Service(wsdlURL, serviceName);
  | 			ssp = ss.getMyRMTestSOAP();
  | 			((StubExt) ssp).setConfigName("Standard Anonymous WSRM Client",
  | 					"META-INF/wsrm-jaxws-client-config.xml");
  | 
  | 			Response<EchoResponse> asyncResponse = null;
  | 			for (int i = 0; i < MAX_PACKETS; i++)
  | 				asyncResponse = ssp.echoAsync("ASYNC PACKET " + i);
  | 
  | 			System.out
  | 					.println("Last response: " + asyncResponse.get());
  | 		} catch (Throwable t) {
  | 			t.printStackTrace();
  | 			throw t;
  | 		}
  | 
  | 		((RMProvider) ssp).closeSequence();
  | 	} I get the following output:17:53:14,426 INFO  [STDOUT] RECEIVED: ASYNC PACKET 4
  | 17:53:14,426 INFO  [STDOUT] RECEIVED: ASYNC PACKET 2
  | 17:53:14,426 INFO  [STDOUT] RECEIVED: ASYNC PACKET 3
  | 17:53:14,458 INFO  [STDOUT] RECEIVED: ASYNC PACKET 1
  | 17:53:14,458 INFO  [STDOUT] RECEIVED: ASYNC PACKET 0
  | 17:53:16,426 INFO  [STDOUT] RETURNING from: ASYNC PACKET 4
  | 17:53:16,426 INFO  [STDOUT] RETURNING from: ASYNC PACKET 2
  | 17:53:16,426 INFO  [STDOUT] RETURNING from: ASYNC PACKET 3
  | 17:53:16,457 INFO  [STDOUT] RETURNING from: ASYNC PACKET 1
  | 17:53:16,457 INFO  [STDOUT] RETURNING from: ASYNC PACKET 0Is there something wrong with my policy file? Why do messages get delivered "out-of-order"?

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

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


From do-not-reply at jboss.com  Tue Aug 12 12:29:30 2008
From: do-not-reply at jboss.com (lfoggy)
Date: Tue, 12 Aug 2008 12:29:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Enabling MTOM-Support at JBossWS
	client fails
Message-ID: <29336057.1218558570768.JavaMail.jboss@colo-br-02.atl.jboss.com>

Well, I am using document/literal wrapped for my wsdl file, and what I have found so far is that mtom only works if the parameter type of the method is DataHandler. For example, this works:

@WebMethod
@RequestWrapper(localName = "sendOctet", targetNamespace = "http://xxx.com/webservice/mtom/", className = "com.xxx.webservice.mtom.SendOctet")
@ResponseWrapper(localName = "sendOctetResponse", targetNamespace = "http://xxx.com/stat/webservice/mtom/", className = "com.xxx.webservice.mtom.SendOctetResponse")
public void sendOctet(
        @WebParam(name = "octet", targetNamespace = "")
        DataHandler octet,

But if I pass something like List, or another holder bean that contains a DataHandler field, mtom does not work anymore, and the message is send inline.



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

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


From do-not-reply at jboss.com  Tue Aug 12 12:30:43 2008
From: do-not-reply at jboss.com (smjain)
Date: Tue, 12 Aug 2008 12:30:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS Eventing client - basics question
Message-ID: <2479276.1218558643702.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi Manu,
I am trying to setup WS-Eventing on JBoss WS 2.0.3
Can you please let me know of the steps..I am not able to do it from what is mentioned on wiki
Regards
Shashank

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

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


From do-not-reply at jboss.com  Tue Aug 12 13:22:53 2008
From: do-not-reply at jboss.com (anaholzbach)
Date: Tue, 12 Aug 2008 13:22:53 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: No tests for @SchemaValidation
	annotation in 3.0.1 ?
Message-ID: <7890121.1218561773679.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi Luc,

I've posted a Tutorial on the JBossWS wiki (http://jbws.dyndns.org/mediawiki/index.php?title=SchemaValidation_Demo) and would like to upload a file with an eclipse project that implements the steps detailed, but it seems that the JBoss wiki does not like .zip files. I could send it to you if you email me. 

Richard, is there a way to upload a zip file on the wiki ? Thanks,

Ana

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

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


From do-not-reply at jboss.com  Tue Aug 12 14:01:02 2008
From: do-not-reply at jboss.com (kosulin)
Date: Tue, 12 Aug 2008 14:01:02 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Enabling MTOM-Support at JBossWS
	client fails
Message-ID: <1480252.1218564062555.JavaMail.jboss@colo-br-02.atl.jboss.com>

The following code works for me (java 6, JBoss 5.0.0CR1, jbossws Core 3.02):

@WebService(...)
@EndpointConfig(...)
@SOAPBinding(style = SOAPBinding.Style.DOCUMENT, parameterStyle = SOAPBinding.ParameterStyle.WRAPPED)
@MTOM(enabled = true)
@BindingType(value = "http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true")
public class StatementService
{
...
	@WebMethod(operationName = "GetStatementContent")
	public StatementListDO getStatementContent(@WebParam(name = "FileName") final String fileName)
{
		StatementListDO sldo = new StatementListDO();
...
		ArrayList statements = new ArrayList(1);
		final File f7z = new File(fileName);
		StatementDO statement = new StatementDO();
		statement.setStmtContent(new DataHandler(new FileDataSource(f7z)));
		statements.add(statement);
		sldo.setStatements(statements);
		return sldo;
}
...
}

@XmlType
@XmlRootElement(name = "StatementList")
public class StatementListDO
  implements Serializable
{
	private ArrayList statements;
	@XmlElement(name = "Statements", nillable = true, required = false)
	public final ArrayList getStatements()
	{
		return this.statements;
	}
	public final void setStatements(ArrayList statements)
	{
		this.statements = statements;
	}

}

@XmlType
public final class StatementDO
  implements Serializable
{
...
	private DataHandler stmtContent;
	@XmlElement(name = "StatementContent", required = false)
	@XmlMimeType("application/zip")
	public final DataHandler getStmtContent()
	{
		return this.stmtContent;
	}
	public final void setStmtContent(DataHandler stmtContent)
	{
		this.stmtContent = stmtContent;
	}
...
}

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

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


From do-not-reply at jboss.com  Tue Aug 12 14:02:10 2008
From: do-not-reply at jboss.com (kosulin)
Date: Tue, 12 Aug 2008 14:02:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Enabling MTOM-Support at JBossWS
	client fails
Message-ID: <7563603.1218564130910.JavaMail.jboss@colo-br-02.atl.jboss.com>

I hope my example should work also if I used StatementListDO as web parameter.

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

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


From do-not-reply at jboss.com  Tue Aug 12 14:10:11 2008
From: do-not-reply at jboss.com (kosulin)
Date: Tue, 12 Aug 2008 14:10:11 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Enabling MTOM-Support at JBossWS
	client fails
Message-ID: <12056295.1218564611045.JavaMail.jboss@colo-br-02.atl.jboss.com>

You use the very old stack.
May be, one of these bugs are the cause (these were fixed since your revision):
[JBWS-1736] - MTOM property at service-ref level
[JBWS-1460] @XmlMimeType on SEI parameter declarations
[JBWS-1973] - MTOM/XOP attachments not inlined when using JAX-WS handlers
[JBWS-2000] - MTOM: Chunked encoding transfer problem
[JBWS-2012] - Attachment support for JAX-WS collections
[JBWS-2014] - MTOM + WS-Security not working


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

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


From do-not-reply at jboss.com  Tue Aug 12 14:12:04 2008
From: do-not-reply at jboss.com (kosulin)
Date: Tue, 12 Aug 2008 14:12:04 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Location of keysore and truststore
	for jboss-ws-server.x
Message-ID: <18338542.1218564724871.JavaMail.jboss@colo-br-02.atl.jboss.com>

It does not work if I pass the absolute path, also.

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

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


From do-not-reply at jboss.com  Tue Aug 12 14:33:18 2008
From: do-not-reply at jboss.com (kosulin)
Date: Tue, 12 Aug 2008 14:33:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: How to get complex types fully
	defined by exposed WSDL
Message-ID: <7701590.1218565998262.JavaMail.jboss@colo-br-02.atl.jboss.com>

Do you use @XmlElement annotation for all exposed attributes of your complex data objects?

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

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


From do-not-reply at jboss.com  Tue Aug 12 14:34:13 2008
From: do-not-reply at jboss.com (kosulin)
Date: Tue, 12 Aug 2008 14:34:13 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: How to get complex types fully
	defined by exposed WSDL
Message-ID: <22164113.1218566053721.JavaMail.jboss@colo-br-02.atl.jboss.com>

And look for @WebParam

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

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


From do-not-reply at jboss.com  Tue Aug 12 14:59:15 2008
From: do-not-reply at jboss.com (lfoggy)
Date: Tue, 12 Aug 2008 14:59:15 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Enabling MTOM-Support at JBossWS
	client fails
Message-ID: <21181378.1218567555831.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thank you very much for the replies.
In your case the code is working because StatementDO has a single DataHandler field.

public final class StatementDO 
implements Serializable  { 
... 
private DataHandler stmtContent; 

I think the problem is when there is a List of DataHandlers.
public final class StatementDO 
implements Serializable  { 
... 
private List stmtContent;

I also think you are right and the problem might be taken care of  by this:
[JBWS-2012] - Attachment support for JAX-WS collections 

unfortunately it was fixed in version 3.0.2 and I can't move up to that version yet since I am running Jboss 4.0.5 for now. 

Thanks,


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

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


From do-not-reply at jboss.com  Tue Aug 12 16:25:33 2008
From: do-not-reply at jboss.com (ljgp)
Date: Tue, 12 Aug 2008 16:25:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: No tests for @SchemaValidation
	annotation in 3.0.1 ?
Message-ID: <24778366.1218572733267.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi Ana,

Thanks a lot ! I will try it out asap !

Luc.

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

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


From do-not-reply at jboss.com  Tue Aug 12 20:08:12 2008
From: do-not-reply at jboss.com (vxj45)
Date: Tue, 12 Aug 2008 20:08:12 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: More soap:address problems
Message-ID: <24742636.1218586092054.JavaMail.jboss@colo-br-02.atl.jboss.com>

Is there a solution to issue 1? I am using jboss version 4.2.1.

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

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


From do-not-reply at jboss.com  Tue Aug 12 20:47:11 2008
From: do-not-reply at jboss.com (vxj45)
Date: Tue, 12 Aug 2008 20:47:11 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Rewriting SOAP address
Message-ID: <30697696.1218588431515.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have Apache talking to JBoss using mod_jk. Client talks to Apache over SSL. The protocol in the soapAddress in returned wsdl is http. In jboss-beans.xml, I have modifySoapAddress set to true and webServiceHost is commented out. How do I get https as protocol in the returned address? I am using JBoss version 4.2.1.
Thanks for your help!

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

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


From jbossws-users at lists.jboss.org  Wed Aug 13 01:13:51 2008
From: jbossws-users at lists.jboss.org (VIAGRA ® Official Site)
Date: Wed, 13 Aug 2008 01:13:51 -0400
Subject: [jbossws-users] August 75% Sale!
Message-ID: <20080813091410.4639.qmail@Admin>

An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossws-users/attachments/20080813/ccdc2f44/attachment.html 

From do-not-reply at jboss.com  Wed Aug 13 01:16:52 2008
From: do-not-reply at jboss.com (kbhdk1976)
Date: Wed, 13 Aug 2008 01:16:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: setHeader and setServerURL,
	using javax.xml.ws.Service?
Message-ID: <7468735.1218604612468.JavaMail.jboss@colo-br-02.atl.jboss.com>

Has anyone found a solution to this ? I can't seem to add a complex type as a header, and I can only find simple string type examples.

If you have the anwer, please reply to this post.

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

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


From do-not-reply at jboss.com  Wed Aug 13 02:46:38 2008
From: do-not-reply at jboss.com (karypid)
Date: Wed, 13 Aug 2008 02:46:38 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: More soap:address problems
Message-ID: <3430156.1218609998595.JavaMail.jboss@colo-br-02.atl.jboss.com>

Try using @WebContext. It works for me using JBossWS-Native 3.0.2 (which is the latest stable version).

For example:@WebContext(authMethod = "BASIC", transportGuarantee=true, secureWSDLAccess = true)
  | @WebService
  | public class MyService ... {
  | ...
  | }

Make sure to enable the  "secureWSDLAccess" flag if you need HTTPS-only access for the published WSDL contract. I understand the "transportGuarantee" is for actual access to the service.


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

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


From do-not-reply at jboss.com  Wed Aug 13 04:36:26 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Wed, 13 Aug 2008 04:36:26 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-RM violates both <ExactlyOnce/>
	and <InOrder/> ?
Message-ID: <29117809.1218616586880.JavaMail.jboss@colo-br-02.atl.jboss.com>

There's no support for in order delivery at the moment. See: JBWS-2039

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

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


From do-not-reply at jboss.com  Wed Aug 13 04:38:30 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Wed, 13 Aug 2008 04:38:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Can't get WS-RM to do ExactlyOnce +
	InOrder
Message-ID: <9019334.1218616710633.JavaMail.jboss@colo-br-02.atl.jboss.com>

There's no support for in order delivery at the moment. See JBWS-2039

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

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


From do-not-reply at jboss.com  Wed Aug 13 05:38:32 2008
From: do-not-reply at jboss.com (xinhua)
Date: Wed, 13 Aug 2008 05:38:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Need help: SAXParseException: An
	invalid XML character (Unic
Message-ID: <27149788.1218620312548.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I encounter an exception by requesting my soap application. 



  | Caused by: java.io.IOException: org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x1f) was found in the element content of the document
  |         at org.jboss.wsf.common.DOMUtils.parse(DOMUtils.java:160)
  |         at org.jboss.wsf.common.DOMUtils.parse(DOMUtils.java:141)
  |         at org.jboss.ws.core.soap.SOAPElementWriter.writeElement(SOAPElementWriter.java:117)
  |         ... 26 more

i think , it is because some utf-8 chars in soap xml can not be handled correctly. I have tried -Dfile.encoding=utf-8 in jvm but it does not help.

i use jbossws-native-3.0.2.GA + jbossAS4.2.2.GA+sun1.5 jdk

How can i fix it ? Can someone help?

Thanks in advance!

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

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


From do-not-reply at jboss.com  Wed Aug 13 11:42:07 2008
From: do-not-reply at jboss.com (eric@attask.com)
Date: Wed, 13 Aug 2008 11:42:07 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: setHeader and setServerURL,
	using javax.xml.ws.Service?
Message-ID: <18427730.1218642127526.JavaMail.jboss@colo-br-02.atl.jboss.com>

Wow  it's already been a year.  Kbhdk1976, to be honest I just used Axis. As far as I can tell JBossws1.2 SP1 doesn't support headers of complex type. I haven't tried the new jbossws so I can't comment on it.

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

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


From do-not-reply at jboss.com  Wed Aug 13 13:39:01 2008
From: do-not-reply at jboss.com (prabhun)
Date: Wed, 13 Aug 2008 13:39:01 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - ERROR [SOAPFaultHelperJAXWS] SOAP
	request exception org.jbos
Message-ID: <24849214.1218649141579.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

We have a web service developed using JbossWS (JAX-WS). It works fine when invoked from a java client.
But the same throws the "Cannot find child element: arg0" exception when invokde from a Oracle PL/SQL soap call.

Please let me know what could be the problem. 

Thanks,
Prabhu

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

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


From do-not-reply at jboss.com  Wed Aug 13 13:39:52 2008
From: do-not-reply at jboss.com (prabhun)
Date: Wed, 13 Aug 2008 13:39:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - SOAP exception - Cannot find child
	element: arg0
Message-ID: <13222753.1218649192174.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

We have a web service developed using JbossWS (JAX-WS). It works fine when invoked from a java client.
But the same throws the "Cannot find child element: arg0" exception when invokde from a Oracle PL/SQL soap call.

Please let me know what could be the problem.

Thanks,
Prabhu

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

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


From do-not-reply at jboss.com  Wed Aug 13 16:38:39 2008
From: do-not-reply at jboss.com (kosulin)
Date: Wed, 13 Aug 2008 16:38:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Location of keysore and truststore
	for jboss-ws-server.x
Message-ID: <27626568.1218659919772.JavaMail.jboss@colo-br-02.atl.jboss.com>

here is the reason:
https://jira.jboss.org/jira/browse/JBAS-3442
Looks like there is no solution yet. This is just weird because we have to give our developers access to our production keystore! Also, every time we get new client, we will have to redeploy the application :-(

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

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


From do-not-reply at jboss.com  Thu Aug 14 02:32:28 2008
From: do-not-reply at jboss.com (lfoggy)
Date: Thu, 14 Aug 2008 02:32:28 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - mtom on the server
Message-ID: <32749169.1218695548026.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,
If I want to make mtom optional on the server, what is the best way of configuring that? Is there any way to package the BindingType outside the webservice class, so that users can turn mtom on or off?
Thanks,



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

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


From do-not-reply at jboss.com  Thu Aug 14 03:39:10 2008
From: do-not-reply at jboss.com (smjain)
Date: Thu, 14 Aug 2008 03:39:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS Eventing client - basics question
Message-ID: <6037331.1218699550743.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am able to deploy the WS-Eventing samples but when I run the Sysmon sample test case I am getting errors in logs.

Testsuite: org.jboss.test.ws.jaxws.samples.wseventing.SysmonTestCase
Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 7.029 sec

Testcase: testSubscribe took 1.609 sec
	Caused an ERROR
javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Cannot extract schema definition: java.net.ConnectException: Connection refused: connect
org.jboss.ws.metadata.wsdl.WSDLException: javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Cannot extract schema definition: java.net.ConnectException: Connection refused: connect
	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.jaxws.JAXWSClientMetaDataBuilder.buildMetaData(JAXWSClientMetaDataBuilder.java:86)
	at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.(ServiceDelegateImpl.java:133)
	at org.jboss.ws.core.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:63)
	at javax.xml.ws.Service.(Service.java:82)
	at javax.xml.ws.Service.create(Service.java:334)
	at org.jboss.test.ws.jaxws.samples.wseventing.SysmonTestCase.setUp(SysmonTestCase.java:88)
	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
	at junit.extensions.TestSetup.run(TestSetup.java:23)
Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Cannot extract schema definition: java.net.ConnectException: Connection refused: connect
	at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:394)
	at org.jboss.ws.tools.wsdl.WSDL11Reader.processDefinition(WSDL11Reader.java:178)
	at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:128)
Caused by: 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:195)
	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:382)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
	at sun.net.www.http.HttpClient.(HttpClient.java:231)
	at sun.net.www.http.HttpClient.New(HttpClient.java:304)
	at sun.net.www.http.HttpClient.New(HttpClient.java:316)
	at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:813)
	at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:765)
	at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:690)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:934)
	at java.net.URL.openStream(URL.java:1007)
	at org.jboss.ws.tools.wsdl.WSDL11Reader.handleSchemaImports(WSDL11Reader.java:588)
	at org.jboss.ws.tools.wsdl.WSDL11Reader.processSchemaInclude(WSDL11Reader.java:560)
	at org.jboss.ws.tools.wsdl.WSDL11Reader.processSchemaInclude(WSDL11Reader.java:529)
	at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:385)

Testcase: testUnsubscribe took 1.109 sec
	Caused an ERROR
javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Cannot extract schema definition: java.net.ConnectException: Connection refused: connect
org.jboss.ws.metadata.wsdl.WSDLException: javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Cannot extract schema definition: java.net.ConnectException: Connection refused: connect
	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.jaxws.JAXWSClientMetaDataBuilder.buildMetaData(JAXWSClientMetaDataBuilder.java:86)
	at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.(ServiceDelegateImpl.java:133)
	at org.jboss.ws.core.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:63)
	at javax.xml.ws.Service.(Service.java:82)
	at javax.xml.ws.Service.create(Service.java:334)
	at org.jboss.test.ws.jaxws.samples.wseventing.SysmonTestCase.setUp(SysmonTestCase.java:88)
	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
	at junit.extensions.TestSetup.run(TestSetup.java:23)
Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Cannot extract schema definition: java.net.ConnectException: Connection refused: connect
	at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:394)
	at org.jboss.ws.tools.wsdl.WSDL11Reader.processDefinition(WSDL11Reader.java:178)
	at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:128)
Caused by: 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:195)
	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:382)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
	at sun.net.www.http.HttpClient.(HttpClient.java:231)
	at sun.net.www.http.HttpClient.New(HttpClient.java:304)
	at sun.net.www.http.HttpClient.New(HttpClient.java:316)
	at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:813)
	at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:765)
	at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:690)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:934)
	at java.net.URL.openStream(URL.java:1007)
	at org.jboss.ws.tools.wsdl.WSDL11Reader.handleSchemaImports(WSDL11Reader.java:588)
	at org.jboss.ws.tools.wsdl.WSDL11Reader.processSchemaInclude(WSDL11Reader.java:560)
	at org.jboss.ws.tools.wsdl.WSDL11Reader.processSchemaInclude(WSDL11Reader.java:529)
	at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:385)

Testcase: testNotification took 1.093 sec
	Caused an ERROR
javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Cannot extract schema definition: java.net.ConnectException: Connection refused: connect
org.jboss.ws.metadata.wsdl.WSDLException: javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Cannot extract schema definition: java.net.ConnectException: Connection refused: connect
	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.jaxws.JAXWSClientMetaDataBuilder.buildMetaData(JAXWSClientMetaDataBuilder.java:86)
	at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.(ServiceDelegateImpl.java:133)
	at org.jboss.ws.core.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:63)
	at javax.xml.ws.Service.(Service.java:82)
	at javax.xml.ws.Service.create(Service.java:334)
	at org.jboss.test.ws.jaxws.samples.wseventing.SysmonTestCase.setUp(SysmonTestCase.java:88)
	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
	at junit.extensions.TestSetup.run(TestSetup.java:23)
Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Cannot extract schema definition: java.net.ConnectException: Connection refused: connect
	at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:394)
	at org.jboss.ws.tools.wsdl.WSDL11Reader.processDefinition(WSDL11Reader.java:178)
	at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:128)
Caused by: 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:195)
	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:382)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
	at sun.net.www.http.HttpClient.(HttpClient.java:231)
	at sun.net.www.http.HttpClient.New(HttpClient.java:304)
	at sun.net.www.http.HttpClient.New(HttpClient.java:316)
	at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:813)
	at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:765)
	at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:690)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:934)
	at java.net.URL.openStream(URL.java:1007)
	at org.jboss.ws.tools.wsdl.WSDL11Reader.handleSchemaImports(WSDL11Reader.java:588)
	at org.jboss.ws.tools.wsdl.WSDL11Reader.processSchemaInclude(WSDL11Reader.java:560)
	at org.jboss.ws.tools.wsdl.WSDL11Reader.processSchemaInclude(WSDL11Reader.java:529)
	at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:385)



Dont really know whats happening...What I also observed is that all web services wsdl dont have a service element . Pleas help me on this..

Regards
Shashank

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

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


From do-not-reply at jboss.com  Thu Aug 14 03:40:18 2008
From: do-not-reply at jboss.com (jimpo)
Date: Thu, 14 Aug 2008 03:40:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Design issue: packaging JAX-WS artifacts
Message-ID: <706219.1218699618065.JavaMail.jboss@colo-br-02.atl.jboss.com>

We have a project with several web services (A, B , C) and a client that uses them. The services and the client are separate subprojects, each built independently. Both the services and the client use jbossws JAX-WS but of course other types of external clients may exist as well.

We create the interfaces from wsdl and schemas using wsconsume. This produces the service interface and tens of data classes for each service.

What's the best approach for packaging these artifacts? 

- having the same classes created for the client and the services so that the same classes exist in 2 places results in having to update lot of classes in 2 places when the interface changes
- we could create separate jars for each web service interface: a.jar, b.jar, c.jar and include for example a.jar both in web service a project and the client project. This of course complicates the build structure a bit
- or we could create a single webservice-api.jar which contains the artifacts for a, b, and c. Bit simpler build, but feels a bit bad to combine these 3 services which have nothing to do with each other into same package


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

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


From do-not-reply at jboss.com  Thu Aug 14 07:51:48 2008
From: do-not-reply at jboss.com (kbhdk1976)
Date: Thu, 14 Aug 2008 07:51:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WebServiceException: Unable to load
	Provider
Message-ID: <6402856.1218714708626.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have an almost similar problem. 

I use JBoss 4.2.2. I have removed jaxws-rt.jar and jaxws-tools.jar from the client directory, and copied the xercesImpl.jar into it from the lib/endorsed directory, as described in this thread. I have also copied the 

It still fails with;

javax.xml.ws.WebServiceException: Unable to load Provider: Failed to load javax.xml.ws.spi.Provider: com.sun.xml.ws.spi.ProviderImpl
	at javax.xml.ws.spi.Provider.provider(Provider.java:98)
	at javax.xml.ws.Service.(Service.java:83)

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)

Caused by: java.lang.NoClassDefFoundError
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

Can anyone tell me what I'm doing wrong ??

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

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


From do-not-reply at jboss.com  Thu Aug 14 10:37:22 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Thu, 14 Aug 2008 10:37:22 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBossWS 3.0.3 Released
Message-ID: <23053451.1218724642477.JavaMail.jboss@colo-br-02.atl.jboss.com>

I'm happy to announce the release of JBossWS 3.0.3 GA which includes Native (fully certified JAX-WS web services implementation), Metro and Apache CXF integration.

For a list of the new features, improvements and bug fixes, please refer the release notes available here:
http://labs.jboss.com/file-access/default/members/jbossws/downloads/ReleaseNotes-jbossws-native-3.0.3.GA.txt

The supported target containers for this release are JBoss 4.2.2.GA, JBoss 4.2.3.GA and JBoss 5.0.0.CR1.

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

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

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

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

Many thanks to the team and contributors making this release possible.

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

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


From do-not-reply at jboss.com  Thu Aug 14 10:53:31 2008
From: do-not-reply at jboss.com (ritesh001)
Date: Thu, 14 Aug 2008 10:53:31 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Cannot find endpoint meta data with
	super-simple WS
Message-ID: <21637094.1218725611415.JavaMail.jboss@colo-br-02.atl.jboss.com>

jimpo, have you found a solution to this problem? I'm having the same problem, though my service deploys just fine on GlassFish and WebLogic, just that JBoss is screwed up with "cannot find endpoint meta data" error.

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

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


From do-not-reply at jboss.com  Thu Aug 14 10:58:40 2008
From: do-not-reply at jboss.com (joshua_hj)
Date: Thu, 14 Aug 2008 10:58:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Using Threads inside Web Services
Message-ID: <20921560.1218725920613.JavaMail.jboss@colo-br-02.atl.jboss.com>

Dear all,

According to the EJB specification using threads inside EJB applications is disallowed because Thread management should be managed by the EJB container. Please find the reference below:
http://java.sun.com/blueprints/qanda/ejb_tier/restrictions.html

What about Web Services? Can we use threads inside Web Services? Should we do it? Is there any kind of restrictions regarding the use of threads inside web services?

Thanks,
Joshua

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

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


From do-not-reply at jboss.com  Thu Aug 14 15:17:34 2008
From: do-not-reply at jboss.com (ritesh001)
Date: Thu, 14 Aug 2008 15:17:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Error in generating WSDL
Message-ID: <18241703.1218741455120.JavaMail.jboss@colo-br-02.atl.jboss.com>

I'm having the same issue, I've a simple HelloWorld that i'm trying to deploy on JBoss, but keep getting "cannot find endpoint meta data" error. I'm able to deploy it on GlassFish and WebLogic, just JBoss is giving me problems. 

Here's the thread that i made for this issue
[url]
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=140865[/url]

Please help me fix this!

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

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


From do-not-reply at jboss.com  Thu Aug 14 17:41:22 2008
From: do-not-reply at jboss.com (john_hedden)
Date: Thu, 14 Aug 2008 17:41:22 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBossWS Benefits
Message-ID: <27266912.1218750082195.JavaMail.jboss@colo-br-02.atl.jboss.com>

Someone please enlighten me...

If Ive already got CXF 2.1.1 running in Seam 2.0.1 already deployed on JBoss 4.2.2 then what benefit do I get by installing JBossWS patch?  Basically whats the difference between running WS with/without JBossWS patch?

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

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


From do-not-reply at jboss.com  Fri Aug 15 02:56:47 2008
From: do-not-reply at jboss.com (jimpo)
Date: Fri, 15 Aug 2008 02:56:47 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Cannot find endpoint meta data with
	super-simple WS
Message-ID: <14144022.1218783407555.JavaMail.jboss@colo-br-02.atl.jboss.com>

"ritesh001" wrote : jimpo, have you found a solution to this problem? I'm having the same problem, though my service deploys just fine on GlassFish and WebLogic, just that JBoss is screwed up with "cannot find endpoint meta data" error.

Sorry I can't help you. I can't remember if I figured out a solution this, and I am not using this approach anymore (I am creating the interface artifacts from WSDL using wsconsume tool). Also I'm using jbossws 2.0 now for other reasons.

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

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


From do-not-reply at jboss.com  Fri Aug 15 10:40:16 2008
From: do-not-reply at jboss.com (vxj45)
Date: Fri, 15 Aug 2008 10:40:16 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: More soap:address problems
Message-ID: <1379073.1218811216503.JavaMail.jboss@colo-br-02.atl.jboss.com>

I tried setting transportGuarantee="true" and transportGuarantee="CONFIDENTIAL". It didn't work for me. I am using jbossws1.2. Forgive my ignorance but how is jbossws-native different from jbossws1.2?

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

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


From do-not-reply at jboss.com  Fri Aug 15 10:54:29 2008
From: do-not-reply at jboss.com (kosulin)
Date: Fri, 15 Aug 2008 10:54:29 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: mtom on the server
Message-ID: <1285941.1218812069614.JavaMail.jboss@colo-br-02.atl.jboss.com>

Do you mean, for some client you want to use SOAP with attachments, and for others - MTOM? I do not believe you can enable or do this dynamically, because it is part of the service endpoint contract definition.
What we do, we have only one XML atttribute defined as @XmlMimeType("application/zip") and at the same time as @XmlElement(..., required=false). As a result, when this attribute is not null, it is sent using MTOM, and when it is null it is absent from response, and there is no MTOM encoding in this response.

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

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


From do-not-reply at jboss.com  Fri Aug 15 14:10:37 2008
From: do-not-reply at jboss.com (enpasos)
Date: Fri, 15 Aug 2008 14:10:37 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Error SAP WS-Security client
	calling JBoss Security WS
Message-ID: <13956850.1218823837125.JavaMail.jboss@colo-br-02.atl.jboss.com>

Requiring "ValueType to be set" breaks the wsse standard 1.0 and 1.1!!! 
(tested in jbossws-3.0.1-native-204.GA)
Please change. Thanks a lot.

See ...
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf

page 22, lines  702 - 708

702 /wsse:SecurityTokenReference/wsse:Reference/@ValueType
703 This optional attribute specifies a URI that is used to identify the type of token being
704 referenced. This specification does not define any processing rules around the usage of
705 this attribute, however, specifications for individual token types MAY define specific
706 processing rules and semantics around the value of the URI and how it SHALL be
707 interpreted. If this attribute is not present, the URI MUST be processed as a normal URI.
708 The usage of ValueType is RECOMMENDED for references with local URIs.



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

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


From do-not-reply at jboss.com  Sun Aug 17 02:07:34 2008
From: do-not-reply at jboss.com (lfoggy)
Date: Sun, 17 Aug 2008 02:07:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: mtom on the server
Message-ID: <16967904.1218953254167.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am concerned if a client can not process mtom encoded attachments, so I like to make mtom optional on the server. (this is an in-house application, so customers will have control over the server) So when server is not mtom-enabled, attachment is send inline.
The javadoc for BindingType annotation states that the annotation may be overriden programmatically. I was thinking maybe I can use that to read mtom configuration from a properties file, but I am not sure how do that.

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

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


From do-not-reply at jboss.com  Sun Aug 17 06:53:48 2008
From: do-not-reply at jboss.com (skajotde)
Date: Sun, 17 Aug 2008 06:53:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Web Service URL pattern
Message-ID: <20205097.1218970428739.JavaMail.jboss@colo-br-02.atl.jboss.com>

You can apply annotation @RolesAllowed, eg.:

holder for auth roles constant:

public class Roles {
  | private static final XXX = "033";
  | 
  | }

and in Webservice:

@WebMethod
  | @RolesAllowed(Roles.XXX)
  | public void youMethod(....

This annotation is same as in EJB and use JAAS to configuration.

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

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


From do-not-reply at jboss.com  Mon Aug 18 15:49:40 2008
From: do-not-reply at jboss.com (karypid)
Date: Mon, 18 Aug 2008 15:49:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS Benefits
Message-ID: <22158792.1219088980827.JavaMail.jboss@colo-br-02.atl.jboss.com>

I suppose "choice" is one advantage.

Lots of "non-standardized" web services functionality (for example, WS-ReliableMessaging or WS-Eventing) is accessed via a different API for each of the various stacks (CXF, Metro, etc).

Rather than coding to a specific Web Services stack, you can use the JBossWS "wrapper APIs". Then you have the option of switching your web services stack among the supported options (Metro, CXF, Native) without having to change your code.


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

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


From do-not-reply at jboss.com  Mon Aug 18 17:52:55 2008
From: do-not-reply at jboss.com (gsekar)
Date: Mon, 18 Aug 2008 17:52:55 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WebServiceException: Unable to load
	Provider
Message-ID: <8991068.1219096375483.JavaMail.jboss@colo-br-02.atl.jboss.com>

https://jira.jboss.org/jira/browse/JBPAPP-941

This fixed the same issue I was having. I didnt have to remove or copy any jars

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

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


From do-not-reply at jboss.com  Tue Aug 19 04:44:51 2008
From: do-not-reply at jboss.com (karypid)
Date: Tue, 19 Aug 2008 04:44:51 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - [UsingAddressing] tag is not added to
	auto-generated WSDL fo
Message-ID: <2640562.1219135491903.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I used the @EndpointConfig annotation to add WS-Addressing handlers to my SEI implementation as described in the WS-Addressing tutorial. I noticed however that even though JBoss adds the WS-Addressing handlers to the the endpoint, it does not specify it in the WSDL that gets published for the web service. In fact, the WSDL generated and published is identical whether you enable WS-Addressing or not.

The WS-Addressing tutorial at http://jbws.dyndns.org/mediawiki/index.php?title=Native_WS-Addressing_Tutorial uses a "manual" approach to make this information available in the contract: It uses the "wsdlLocation" attribute of the @WebService annotation to refer to a pre-constructed WSDL that has an appropriate service definition:

<service name='AddressingService'>
  |   <port binding='tns:ServiceIfaceBinding' name='AddressingServicePort'>
  |    <soap:address location='REPLACE_WITH_ACTUAL_URL'/>
  |    <!-- - - - - - - - - - - - - - - -->
  |    <!-- Added extensibility element -->
  |    <!-- - - - - - - - - - - - - - - -->
  |    <UsingAddressing xmlns="http://www.w3.org/2006/05/addressing/wsdl"/>
  |   </port>
  |  </service>

 I would expect JBoss to add the UsingAddressing tag to the generated WSDL contract to "warn" clients that it is required.

Is this only possible when using pre-constructed WSDL?



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

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


From do-not-reply at jboss.com  Tue Aug 19 05:14:37 2008
From: do-not-reply at jboss.com (Dennisk)
Date: Tue, 19 Aug 2008 05:14:37 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBossWS throws exception when receiving
	unbound soap header
Message-ID: <15022887.1219137277466.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello,

I hope some one can help me with this problem, it's causing me headaches:

I use Jax-ws in my webservice client project deployed on JBoss4.2.2GA (with JBossWs patch) to communicate with a party through soap. When I receive a reply to my request I get the following exception:
2008-08-19 10:37:42,020 ERROR [org.jboss.ws.core.soap.SOAPMessageUnMarshaller] Cannot unmarshall SOAPMessage
  | javax.xml.soap.SOAPException: Invalid SOAPHeaderElement name: api-version
  | 	at org.jboss.ws.core.soap.SOAPHeaderImpl.addChildElement(SOAPHeaderImpl.java:64)
  | 	at org.jboss.ws.core.soap.EnvelopeBuilderDOM.buildSOAPHeader(EnvelopeBuilderDOM.java:174)
  | 	at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:138)
  | 	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.SOAPMessageUnMarshaller.read(SOAPMessageUnMarshaller.java:84)
  | 	at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:473)
  | 	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:305)
  | 	at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:135)
  | 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
  | 	at org.jboss.remoting.Client.invoke(Client.java:1634)
  | 	at org.jboss.remoting.Client.invoke(Client.java:548)
  | 	at org.jboss.ws.core.client.RemotingConnectionImpl.invoke(RemotingConnectionImpl.java:183)
  | 	at org.jboss.ws.core.client.SOAPRemotingConnection.invoke(SOAPRemotingConnection.java:77)
  | 	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:337)
  | 	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 $Proxy389.getDatabases(Unknown Source)
  | 	at com.myorganize.services.mail.MailServiceBean.getDatabaseId(MailServiceBean.java:180)
  | 
  | 

It looks like the parsing of the unbound soap header element (api-version) causes an exception (I do not need this info anyway). Strangely enough in Eclipse I used the jaxws-rt implementation for testing these calls and there it worked perfectly and caused no exceptions. I looked at the jboss code (org.jboss.ws.core.soap.SOAPHeaderImpl.addChildElement) that trows the exception and it seems to throw it when the namespace or prefix is null, but I do not exactly know how or why these could be null.

Can anybody give me some info on what the exact problem could be and maybe what the best solution is? Or is there a setting or configuration item that can direct jboss to ignore soap header elements.

I already tried to use the jaxws-rt implementation in JBoss (4.2.2.GA) but I could not get a working set because the jbossws core seems to be tightly coupled with the jboss application server, and I keep getting compatibility and classloading issues with implementation classes of jbossws/saaj and jaxws-rt. 
ps. I cannot change the wsdl and define the header elements because the other party will not change the wsdl. 
pss. I hope to avoid having to write a raw soap msg handler to remove the element since it is a lot of work and I think it should not be necessary. 

The return message with the api-version soap header element that causes the problem:

  | <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  |   <soap:Header>
  |     <api-version>1.82</api-version>
  |   </soap:Header>
  |   <soap:Body>
  |     <ns1:getDatabasesResponse xmlns:ns1="http://tservice.services.xxxxxxxx.com/">
  |       <databaseInfos>
  |         <id>yDK</id>
  |         <name>_Expeditie</name>
  |         <subscriberFields>email</subscriberFields>
  |         ............deleted contents of message..................
  |         <subscriberFields>naam</subscriberFields>
  |       </databaseInfos>
  |     </ns1:getDatabasesResponse>
  |   </soap:Body>
  | </soap:Envelope>
  | 

Thanks in advance for looking at this problem...regards,

Dennis

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

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


From do-not-reply at jboss.com  Tue Aug 19 09:52:23 2008
From: do-not-reply at jboss.com (jaki)
Date: Tue, 19 Aug 2008 09:52:23 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - SimpleDeserializer error on returning
	complex type
Message-ID: <6044463.1219153943730.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi, 

I have exposed a stateless ejb3 bean as a WS and it has a method returning a complex type.

Signature:

@WebMethod
  | 	public MapBean getMap(String test)

The class MapBean just has 2 string members along with their getters/setters.

I'm using an axis WS client for it (using the Call interface) but invoking the Web service gives me the below error:
Caused by: org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize.
  |         at org.apache.axis.encoding.ser.SimpleDeserializer.onStartChild(SimpleDeserializer.java:145)
  |         at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
  |         at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165)
  |         at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
  |         at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
  |         at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
  |         at org.apache.axis.client.Call.invoke(Call.java:2448)
  |         ... 3 more 

What's wierd is, it works without the error if I change the binding from document/wrapped to document/BARE but in that case the input arguements take the form '<arg0 xsi:type='xsd:string' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xsd='http://www.w3.org/2001/XMLSchema'>nabble</arg0>' even inside the webmethod! Kindly help me here. 

WSDL for response:

xs:complexType name="getMapResponse">
  |     <xs:sequence>
  |      <xs:element minOccurs="0" name="return" type="tns:mapBean"/>
  |     </xs:sequence>
  |    </xs:complexType>
  |    <xs:complexType name="mapBean">
  |     <xs:sequence>
  |      <xs:element minOccurs="0" name="key" type="xs:string"/>
  |      <xs:element minOccurs="0" name="value" type="xs:string"/>
  |     </xs:sequence>
  |    </xs:complexType>

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

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


From do-not-reply at jboss.com  Tue Aug 19 12:06:06 2008
From: do-not-reply at jboss.com (kosulin)
Date: Tue, 19 Aug 2008 12:06:06 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS 3.0.3 Released
Message-ID: <15370678.1219161966969.JavaMail.jboss@colo-br-02.atl.jboss.com>

Why there is no source distribution for latest releases available?
Thanks.

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

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


From do-not-reply at jboss.com  Tue Aug 19 12:20:17 2008
From: do-not-reply at jboss.com (JBossWS_NewBee)
Date: Tue, 19 Aug 2008 12:20:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Providing your own wsdl instead of
	the generated one.
Message-ID: <8219678.1219162817798.JavaMail.jboss@colo-br-02.atl.jboss.com>

ngtdave and PeterJ:
 
 Thank you very much for the post. It was quite helpful. I was able to publish the EchoService.wsdl.
However, the EchoClient as per the JBossWSUserGuide(http://www.jboss.org/jbossws/docs/jaxws_userguide-2.0/index.html#d0e741)
gives me the following Exception:

Command:
wsrunclient.bat EchoClient 'HelloWorld'
Exception in thread "main" javax.xml.ws.WebServiceException: java.lang.IllegalStateException: Could not setup remoting client
   at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(Clien
tImpl.java:304)
        at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:242)
        at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:16
4)
        at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:15
0)
        at $Proxy15.echo(Unknown Source)
        at echo.EchoClient.main(EchoClient.java:15)
Caused by: java.lang.IllegalStateException: Could not setup remoting client
        at org.jboss.ws.core.client.RemotingConnectionImpl.createRemotingClient(
RemotingConnectionImpl.java:240)

Any pointers?

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

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


From do-not-reply at jboss.com  Tue Aug 19 12:47:43 2008
From: do-not-reply at jboss.com (ngtdave)
Date: Tue, 19 Aug 2008 12:47:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Providing your own wsdl instead of
	the generated one.
Message-ID: <13290993.1219164463667.JavaMail.jboss@colo-br-02.atl.jboss.com>

Do you have all the proper client jars in your classpath?

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

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


From do-not-reply at jboss.com  Tue Aug 19 12:52:58 2008
From: do-not-reply at jboss.com (JBossWS_NewBee)
Date: Tue, 19 Aug 2008 12:52:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Providing your own wsdl instead of
	the generated one.
Message-ID: <20864485.1219164778956.JavaMail.jboss@colo-br-02.atl.jboss.com>

Yes, I do..I updated the wsrunclient.bat script to include all the relevant jars: 
Here's the list of jars:
set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/jboss-xml-binding.jar
set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/activation.jar
set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/javassist.jar
set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/getopt.jar
set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/jaxb-api.jar
set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/jaxb-impl.jar
set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/jbossall-client.jar
set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/stax-api.jar
set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/wstx.jar
set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/jboss-j2ee.jar
set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/jboss-saaj.jar
set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/jboss-jaxws.jar
set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/jboss-jaxrpc.jar
set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/jbossws-client.jar
set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/log4j.jar
set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/mail.jar
set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/wsdl4j.jar

Here's the EchoClient class:

  | package echo;
  | 
  | public class EchoClient {
  | 
  | 	/**
  | 	 * @param args
  | 	 */
  | 	public static void main(String[] args) {
  | 	  if (args.length != 1) {
  | 	  	System.err.println("usage: EchoClient <message>");
  | 		System.exit(1);
  | 	  }
  | 	  EchoService service = new EchoService();
  | 	  Echo echo = service.getEchoPort();
  | 	  System.out.println("Server said: " + echo.echo(args[0]));
  | 	}
  | 
  | }

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

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


From do-not-reply at jboss.com  Tue Aug 19 13:31:51 2008
From: do-not-reply at jboss.com (JBossWS_NewBee)
Date: Tue, 19 Aug 2008 13:31:51 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Exception with WSClient
Message-ID: <2327853.1219167111298.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am stuck for the last 2 days getting the exact same exception as you did when I run my WSClient. How did you add the trustore? 

Thanks!





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

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


From do-not-reply at jboss.com  Tue Aug 19 13:35:59 2008
From: do-not-reply at jboss.com (JBossWS_NewBee)
Date: Tue, 19 Aug 2008 13:35:59 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Providing your own wsdl instead of
	the generated one.
Message-ID: <28706258.1219167359664.JavaMail.jboss@colo-br-02.atl.jboss.com>

This thread reports the same WSClientException as I am getting
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171340

However, I wonder why would I need a trustore to get the WSClient to run.


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

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


From do-not-reply at jboss.com  Tue Aug 19 14:36:22 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 19 Aug 2008 14:36:22 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Providing your own wsdl instead of
	the generated one.
Message-ID: <3687688.1219170982276.JavaMail.jboss@colo-br-02.atl.jboss.com>

Do you have a META-INF/standard-jaxws-client-config.xml packages with your client? If so, please post the contents?

You did not post the full stack trace - were there are more "caused by" entries in that trace?

Post the contents of the WSDL.

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

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


From do-not-reply at jboss.com  Tue Aug 19 15:04:10 2008
From: do-not-reply at jboss.com (JBossWS_NewBee)
Date: Tue, 19 Aug 2008 15:04:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Providing your own wsdl instead of
	the generated one.
Message-ID: <21648277.1219172650658.JavaMail.jboss@colo-br-02.atl.jboss.com>

Here are the contents of META-INF
META-INF/
META-INF/MANIFEST.MF
META-INF/wsdl/
META-INF/wsdl/EchoService.wsdl

I don't have a standard-jaxws-client-config.xml

This is the entire stack trace with all the 'caused by' entries

  | Exception in thread "main" javax.xml.ws.WebServiceException: java.lang.IllegalSt
  | ateException: Could not setup remoting client
  |         at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(Clien
  | tImpl.java:304)
  |         at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:242)
  | 
  |         at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:16
  | 4)
  |         at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:15
  | 0)
  |         at $Proxy15.echo(Unknown Source)
  |         at echo.EchoClient.main(EchoClient.java:15)
  | Caused by: java.lang.IllegalStateException: Could not setup remoting client
  |         at org.jboss.ws.core.client.RemotingConnectionImpl.createRemotingClient(
  | RemotingConnectionImpl.java:240)
  |         at org.jboss.ws.core.client.RemotingConnectionImpl.invoke(RemotingConnec
  | tionImpl.java:153)
  |         at org.jboss.ws.core.client.SOAPRemotingConnection.invoke(SOAPRemotingCo
  | nnection.java:77)
  |         at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:331)
  |         at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:230)
  | 
  |         ... 4 more
  | Caused by: java.lang.NullPointerException
  |         at org.jboss.remoting.InvokerLocator.resolveHost(InvokerLocator.java:333
  | )
  |         at org.jboss.remoting.InvokerLocator.URIParse(InvokerLocator.java:257)
  |         at org.jboss.remoting.InvokerLocator.parse(InvokerLocator.java:213)
  |         at org.jboss.remoting.InvokerLocator.<init>(InvokerLocator.java:193)
  |         at org.jboss.ws.core.client.RemotingConnectionImpl.createRemotingClient(
  | RemotingConnectionImpl.java:213)
  |         ... 8 more

I am suspicious of one entry in my wsdl though: "Replace with actual url"
I am thinking if I need to change this to "http://localhost:8080/echo"
This is the wsdl. 


  | <?xml version="1.0" encoding="UTF-8"?>
  | <definitions name='EchoService' 
  |  targetNamespace='http://echo/' 
  |  xmlns='http://schemas.xmlsoap.org/wsdl/' 
  |  xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' 
  |  xmlns:tns='http://echo/' xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
  |  <types>
  |   <xs:schema targetNamespace='http://echo/' version='1.0' xmlns:tns='http://echo/'     xmlns:xs='http://www.w3.org/2001/XMLSchema'>
  |    <xs:element name='echo' type='tns:echo'/>
  |    <xs:element name='echoResponse' type='tns:echoResponse'/>
  |    <xs:complexType name='echo'>
  |     <xs:sequence>
  |      <xs:element minOccurs='0' name='arg0' type='xs:string'/>
  |     </xs:sequence>
  |    </xs:complexType>
  |    <xs:complexType name='echoResponse'>
  |     <xs:sequence>
  |      <xs:element minOccurs='0' name='return' type='xs:string'/>
  |     </xs:sequence>
  |    </xs:complexType>
  |   </xs:schema>
  |  </types>
  |  <message name='Echo_echo'>
  |   <part element='tns:echo' name='echo'/>
  |  </message>
  |  <message name='Echo_echoResponse'>
  |   <part element='tns:echoResponse' name='echoResponse'/>
  |  </message>
  |  <portType name='Echo'>
  |   <operation name='echo' parameterOrder='echo'>
  |    <input message='tns:Echo_echo'/>
  |    <output message='tns:Echo_echoResponse'/>
  |   </operation>
  |  </portType>
  |  <binding name='EchoBinding' type='tns:Echo'>
  |   <soap:binding style='document' transport='http://schemas.xmlsoap.org/soap/http'/>
  |   <operation name='echo'>
  |    <soap:operation soapAction=''/>
  |    <input>
  |     <soap:body use='literal'/>
  |    </input>
  |    <output>
  |     <soap:body use='literal'/>
  |    </output>
  |   </operation>
  |  </binding>
  |  <service name='EchoService'>
  |   <documentation>Congrats!  You have published your own WSDL!</documentation>
  |   <port binding='tns:EchoBinding' name='EchoPort'>
  |    <soap:address location='REPLACE_WITH_ACTUAL_URL'/>
  |   </port>
  |  </service>
  | </definitions>

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

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


From do-not-reply at jboss.com  Tue Aug 19 15:26:35 2008
From: do-not-reply at jboss.com (ngtdave)
Date: Tue, 19 Aug 2008 15:26:35 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Providing your own wsdl instead of
	the generated one.
Message-ID: <22973699.1219173995693.JavaMail.jboss@colo-br-02.atl.jboss.com>

I think you're on the right track, notice it's having a problem resolving the host, and you have not put the actual host URL in the WSDL.

That's probably it.

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

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


From do-not-reply at jboss.com  Tue Aug 19 15:44:39 2008
From: do-not-reply at jboss.com (kosulin)
Date: Tue, 19 Aug 2008 15:44:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WSSecurity problem: Could not locate
	certificate by key iden
Message-ID: <1497440.1219175079556.JavaMail.jboss@colo-br-02.atl.jboss.com>

We use Ws-Security over https (java 6, jboss 5.0CR1, jbossws core 3.0.2). Client is java 6 (Sun XWSS). Server uses a real production certificate, client -a self-signed one (I was told it was created with openssl, not keytool). Request is successfully validated during SSL handshake using CLIENT-CERT, and authorized with JAAS. This means on the java.security.cert level the server is able to recognize and authenticate the certificate as valid one (compared to the truststore). However, on WS-Security level we get an exception. Below is the trace. What is wrong with key identifier? Thanks.

2008-08-19 15:20:14,592 TRACE [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] (http-0.0.0.0-8443-1:) BEFORE handleRequest - org.jboss.wsf.framework.invocation.RecordingServerHandler at 17a08d4
<S:Envelope xmlns:S='http://schemas.xmlsoap.org/soap/envelope/'>
 <S:Header>
  <wsse:Security S:mustUnderstand='1' xmlns:wsse='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd'>
   <wsu:Timestamp wsu:Id='XWSSGID-12191736147481681242501' xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd'>
    <wsu:Created>2008-08-19T19:20:14Z</wsu:Created>
    <wsu:Expires>2008-08-19T19:25:14Z</wsu:Expires>
   </wsu:Timestamp>
   <ds:Signature Id='XWSSGID-12191736146031743555814' xmlns:ds='http://www.w3.org/2000/09/xmldsig#'>
    <ds:SignedInfo>
     <ds:CanonicalizationMethod Algorithm='http://www.w3.org/2001/10/xml-exc-c14n#' xmlns:ds='http://www.w3.org/2000/09/xmldsig#'>
      
     </ds:CanonicalizationMethod>
     <ds:SignatureMethod Algorithm='http://www.w3.org/2000/09/xmldsig#rsa-sha1' xmlns:ds='http://www.w3.org/2000/09/xmldsig#'/>
     <ds:Reference URI='#XWSSGID-1219173614748711119660' xmlns:ds='http://www.w3.org/2000/09/xmldsig#'>
      <ds:DigestMethod Algorithm='http://www.w3.org/2000/09/xmldsig#sha1' xmlns:ds='http://www.w3.org/2000/09/xmldsig#'/>
      <ds:DigestValue xmlns:ds='http://www.w3.org/2000/09/xmldsig#'>D5VC3nxO1mCHdvlx3ZlL+pKVOMo=</ds:DigestValue>
     </ds:Reference>
     <ds:Reference URI='#XWSSGID-12191736147481681242501' xmlns:ds='http://www.w3.org/2000/09/xmldsig#'>
      <ds:DigestMethod Algorithm='http://www.w3.org/2000/09/xmldsig#sha1' xmlns:ds='http://www.w3.org/2000/09/xmldsig#'/>
      <ds:DigestValue xmlns:ds='http://www.w3.org/2000/09/xmldsig#'>sl1ERXikaFn0w4iWQtKnNS2dYuE=</ds:DigestValue>
     </ds:Reference>
    </ds:SignedInfo>
    <ds:SignatureValue>d4zmVhrNWDjNqSQ8tHXH7iEUAKj0pmnFwkbTWdyQEiCRry4INKT4lZpVnNG6qcsKMM+fh1CPOyd4
eHCZYOZjdpFhPYEIbfBzjZuiOkrnXmwIVm43bS7bCW+R9xELJ67cgldJL03G9ntcdsOo3I/vxEGn
BRZm4siJbM2VbUrtLfE=</ds:SignatureValue>
    <ds:KeyInfo>
     <wsse:SecurityTokenReference wsu:Id='XWSSGID-12191736147371393264612' 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:KeyIdentifier EncodingType='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary' ValueType='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier'>VsF5XAhG06l2TVSo6RafX5b9epw=</wsse:KeyIdentifier>
     </wsse:SecurityTokenReference>
    </ds:KeyInfo>
   </ds:Signature>
  </wsse:Security>
 </S:Header>
 <S:Body wsu:Id='XWSSGID-1219173614748711119660' xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd'>
  <ns2:GetAllStatementList xmlns:ns2='http://www.wsc.com/'>
   test
   0
   sm0
   2007
   TX10000976
  </ns2:GetAllStatementList>
 </S:Body>
</S:Envelope>
2008-08-19 15:20:14,592 TRACE [org.jboss.ws.core.CommonMessageContext] (http-0.0.0.0-8443-1:) put: APPLICATION:org.jboss.ws.allow.expand.dom=true
2008-08-19 15:20:14,592 TRACE [org.jboss.ws.core.CommonMessageContext] (http-0.0.0.0-8443-1:) get(javax.xml.ws.handler.message.outbound): APPLICATION:javax.xml.ws.handler.message.outbound=false
2008-08-19 15:20:14,593 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (http-0.0.0.0-8443-1:) getChildNodes
2008-08-19 15:20:14,593 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (http-0.0.0.0-8443-1:) getChildNodes
2008-08-19 15:20:14,593 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (http-0.0.0.0-8443-1:) getChildNodes
2008-08-19 15:20:14,593 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (http-0.0.0.0-8443-1:) getChildNodes
2008-08-19 15:20:14,593 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (http-0.0.0.0-8443-1:) getChildNodes
2008-08-19 15:20:14,593 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (http-0.0.0.0-8443-1:) getChildNodes
2008-08-19 15:20:14,593 TRACE [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] (http-0.0.0.0-8443-1:) AFTER handleRequest - org.jboss.wsf.framework.invocation.RecordingServerHandler at 17a08d4: unchanged
2008-08-19 15:20:14,593 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (http-0.0.0.0-8443-1:) getChildNodes
2008-08-19 15:20:14,593 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (http-0.0.0.0-8443-1:) getChildNodes
2008-08-19 15:20:14,593 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (http-0.0.0.0-8443-1:) getChildNodes
2008-08-19 15:20:14,594 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (http-0.0.0.0-8443-1:) getChildNodes
2008-08-19 15:20:14,594 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (http-0.0.0.0-8443-1:) getChildNodes
2008-08-19 15:20:14,594 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (http-0.0.0.0-8443-1:) getChildNodes
2008-08-19 15:20:14,594 TRACE [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] (http-0.0.0.0-8443-1:) BEFORE handleRequest - WSSecurity Handler: unchanged
2008-08-19 15:20:14,594 TRACE [org.jboss.ws.core.CommonMessageContext] (http-0.0.0.0-8443-1:) put: APPLICATION:org.jboss.ws.allow.expand.dom=true
2008-08-19 15:20:14,594 TRACE [org.jboss.ws.core.CommonMessageContext] (http-0.0.0.0-8443-1:) get(javax.xml.ws.handler.message.outbound): APPLICATION:javax.xml.ws.handler.message.outbound=false
2008-08-19 15:20:14,594 TRACE [org.jboss.ws.core.CommonMessageContext] (http-0.0.0.0-8443-1:) get(javax.xml.ws.addressing.context.inbound): null
2008-08-19 15:20:14,594 DEBUG [org.jboss.ws.core.soap.SOAPMessageDispatcher] (http-0.0.0.0-8443-1:) getDispatchDestination: {http://www.wsc.com/}GetAllStatementList
2008-08-19 15:20:14,594 DEBUG [org.jboss.ws.extensions.security.SecurityStore] (http-0.0.0.0-8443-1:) loadStore: vfszip:/opt/jboss/jboss-5.0.0.CR1/server/cpportal2/deploy/cpportal2-ear.ear/statements-web.war/WEB-INF/cpportal2.keystore
2008-08-19 15:20:14,594 DEBUG [org.jboss.ws.extensions.security.SecurityStore] (http-0.0.0.0-8443-1:) loadStore: vfszip:/opt/jboss/jboss-5.0.0.CR1/server/cpportal2/deploy/cpportal2-ear.ear/statements-web.war/WEB-INF/cpportal2.keystore
2008-08-19 15:20:14,595 TRACE [org.jboss.ws.extensions.security.SecurityStore] (http-0.0.0.0-8443-1:) decrypt password: password
2008-08-19 15:20:14,595 TRACE [org.jboss.ws.extensions.security.SecurityStore] (http-0.0.0.0-8443-1:) decrypt password: password
2008-08-19 15:20:14,595 TRACE [org.jboss.ws.extensions.security.SecurityStore] (http-0.0.0.0-8443-1:) decrypted password: password
2008-08-19 15:20:14,595 TRACE [org.jboss.ws.extensions.security.SecurityStore] (http-0.0.0.0-8443-1:) decrypted password: password
2008-08-19 15:20:14,595 DEBUG [org.jboss.ws.extensions.security.SecurityStore] (http-0.0.0.0-8443-1:) loadStore: vfszip:/opt/jboss/jboss-5.0.0.CR1/server/cpportal2/deploy/cpportal2-ear.ear/statements-web.war/WEB-INF/cpportal2.truststore
2008-08-19 15:20:14,595 DEBUG [org.jboss.ws.extensions.security.SecurityStore] (http-0.0.0.0-8443-1:) loadStore: vfszip:/opt/jboss/jboss-5.0.0.CR1/server/cpportal2/deploy/cpportal2-ear.ear/statements-web.war/WEB-INF/cpportal2.truststore
2008-08-19 15:20:14,595 TRACE [org.jboss.ws.extensions.security.SecurityStore] (http-0.0.0.0-8443-1:) decrypt password: password
2008-08-19 15:20:14,595 TRACE [org.jboss.ws.extensions.security.SecurityStore] (http-0.0.0.0-8443-1:) decrypt password: password
2008-08-19 15:20:14,595 TRACE [org.jboss.ws.extensions.security.SecurityStore] (http-0.0.0.0-8443-1:) decrypted password: password
2008-08-19 15:20:14,595 TRACE [org.jboss.ws.extensions.security.SecurityStore] (http-0.0.0.0-8443-1:) decrypted password: password
2008-08-19 15:20:14,596 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (http-0.0.0.0-8443-1:) getFirstChild
2008-08-19 15:20:14,596 ERROR [org.jboss.ws.extensions.security.WSSecurityDispatcher] (http-0.0.0.0-8443-1:) Internal error occured handling inbound message:
org.jboss.ws.extensions.security.exception.SecurityTokenUnavailableException: Could not locate certificate by key identifier
        at org.jboss.ws.extensions.security.KeyResolver.resolveKeyIdentifier(KeyResolver.java:116)
        at org.jboss.ws.extensions.security.KeyResolver.resolve(KeyResolver.java:89)
        at org.jboss.ws.extensions.security.KeyResolver.resolveCertificate(KeyResolver.java:131)
        at org.jboss.ws.extensions.security.KeyResolver.resolvePublicKey(KeyResolver.java:141)
        at org.jboss.ws.extensions.security.KeyResolver.resolvePublicKey(KeyResolver.java:161)
        at org.jboss.ws.extensions.security.element.Signature.(Signature.java:60)
        at org.jboss.ws.extensions.security.element.SecurityHeader.(SecurityHeader.java:87)
        at org.jboss.ws.extensions.security.SecurityDecoder.decode(SecurityDecoder.java:192)
        at org.jboss.ws.extensions.security.WSSecurityDispatcher.decodeMessage(WSSecurityDispatcher.java:105)
        at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:83)
        at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:41)
        at org.jboss.wsf.common.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:97)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:127)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:171)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:466)
        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:235)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:183)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:189)
        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:90)
        at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:96)
        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:325)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
        at java.lang.Thread.run(Unknown Source)


Some service config details:
--------------------------
@WebService(name = "Statements", targetNamespace = "http://www.wsc.com/", serviceName = "StatementsService", portName = "StatementsPort")
@EndpointConfig(configName = "Standard WSSecurity Endpoint")
@SOAPBinding(style = SOAPBinding.Style.DOCUMENT, parameterStyle = SOAPBinding.ParameterStyle.WRAPPED)
@MTOM(enabled = true)
@BindingType(value = "http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true")
@WebContext(secureWSDLAccess = true)
@SecurityDomain("CPPortal2WSCert")
@DeclareRoles( {"statements-client"})
@RolesAllowed( {"statements-client"})
public class StatementService
------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" id="WebApp_ID" version="2.5">
  <display-name>statements</display-name>
  
  	<servlet-name>Statements</servlet-name>
  	<servlet-class>com.wsc.cp.web.statements.StatementService</servlet-class>
  
  
  <servlet-mapping>
  	<servlet-name>Statements</servlet-name>
  	<url-pattern>/statements</url-pattern>
  </servlet-mapping>
  
  <session-config>
    <session-timeout>30</session-timeout>
  </session-config>
  
  <login-config>
  	<auth-method>CLIENT-CERT</auth-method>
  </login-config>
	
	<security-constraint>
    <web-resource-collection>
      <web-resource-name>Statements</web-resource-name>
  		<url-pattern>/statements</url-pattern>
    </web-resource-collection>
    <user-data-constraint>
      <transport-guarantee>CONFIDENTIAL</transport-guarantee>
    </user-data-constraint>
  </security-constraint>
</web-app>
----------------------------------
<jboss-ws-security xmlns="http://www.jboss.com/ws-security/config"
                   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                   xsi:schemaLocation="http://www.jboss.com/ws-security/config
                   http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd">
	<key-store-file>WEB-INF/cpportal2.keystore</key-store-file>
	<key-store-password>password</key-store-password>
	<key-store-type>jks</key-store-type>
	<trust-store-file>WEB-INF/cpportal2.truststore</trust-store-file>
	<trust-store-password>password</trust-store-password>
	<trust-store-type>jks</trust-store-type>
	<timestamp-verification createdTolerance="5" warnCreated="true" expiresTolerance="10" warnExpires="true" />	
		
		
		
<!--  		 -->
		
			
<!-- 			  -->      
		
		
			
		
	
</jboss-ws-security>
----------------------------------
CN\=test.client=statements-client
-------------------------------------------

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

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


From do-not-reply at jboss.com  Tue Aug 19 15:50:00 2008
From: do-not-reply at jboss.com (kosulin)
Date: Tue, 19 Aug 2008 15:50:00 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSSecurity problem: Could not
	locate certificate by key
Message-ID: <30231706.1219175400871.JavaMail.jboss@colo-br-02.atl.jboss.com>

jboss-wsse-server.xml in the original message is incomplete. here is the missing part:

timestamp ttl="300"/>
sign type="x509v3" alias="cpportal2" includeTimestamp="true"/>
requires>
			signature/>

		authenticate>
			signatureCertAuth certificatePrincipal="org.jboss.security.auth.certs.SubjectCNMapping"/>
		/authenticate>
	/config>

For unknown reason the forum editor rejects posting of correct xml, and I was forced to remove leading angle brackets. Sorry for inconvenience.

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

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


From do-not-reply at jboss.com  Tue Aug 19 15:56:46 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 19 Aug 2008 15:56:46 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSSecurity problem: Could not
	locate certificate by key
Message-ID: <15423793.1219175806730.JavaMail.jboss@colo-br-02.atl.jboss.com>

kosulin wrote : For unknown reason the forum editor rejects posting of correct xml

You can post XML text by selecting the text and clicking the Code button - this places code BBCode tags around the xml text. Also, you can Preview the post to ensure proper formatting before clicking Submit.

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

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


From do-not-reply at jboss.com  Tue Aug 19 17:20:37 2008
From: do-not-reply at jboss.com (JBossWS_NewBee)
Date: Tue, 19 Aug 2008 17:20:37 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Providing your own wsdl instead of
	the generated one.
Message-ID: <3355905.1219180837460.JavaMail.jboss@colo-br-02.atl.jboss.com>

Looks like I am out of luck again :( 
Oh! this is so frustrating..

So, I made the following update to my wsdl:

  | <service name='EchoService'>
  |   <documentation>Congrats!  You have published your own WSDL!</documentation>
  |   <port binding='tns:EchoBinding' name='EchoPort'>
  |    <soap:address location='http://localhost:8080/echo'/>
  |   </port>
  |  </service>

packaged the war and deployed it and now I see this error in the JBossConsole:


  | 12:38:28,359 INFO  [WSDLFilePublisher] WSDL published to: file:/C:/sfsl/runtime/
  | localhost/workstation/jboss/data/wsdl/echo.war/EchoService.wsdl
  | 12:38:28,359 ERROR [ServiceEndpointDeployer] Cannot start service endpoint
  | org.jboss.ws.WSException: Cannot load service endpoint interface: echo.Echo
  |         at org.jboss.ws.metadata.umdm.EndpointMetaData.getServiceEndpointInterfa
  | ce(EndpointMetaData.java:238)
  |         at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitializeOperations
  | (EndpointMetaData.java:510)
  |         at org.jboss.ws.metadata.umdm.EndpointMetaData.initializeInternal(Endpoi
  | ntMetaData.java:504)
  |         at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitialize(EndpointM
  | etaData.java:492)
  |         at org.jboss.ws.metadata.umdm.ServiceMetaData.eagerInitialize(ServiceMet
  | aData.java:429)
  |         at org.jboss.ws.metadata.umdm.UnifiedMetaData.eagerInitialize(UnifiedMet
  | aData.java:192)
  |         at org.jboss.ws.core.server.ServiceEndpoint.start(ServiceEndpoint.java:1
  | 12)
  |         at org.jboss.ws.core.server.ServiceEndpointManager.startServiceEndpoint(
  | ServiceEndpointManager.java:702)
  |         at org.jboss.ws.core.server.ServiceEndpointDeployer.start(ServiceEndpoin
  | tDeployer.java:140)
  |         at org.jboss.ws.integration.jboss42.DeployerInterceptor.startServiceEndp
  | oint(DeployerInterceptor.java:144)
  |         at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerIn
  | terceptor.java:96)
  |         at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.
  | start(SubDeployerInterceptorSupport.java:188)
  |         at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterce
  | ptor.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 $Proxy47.start(Unknown Source)
  |         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 sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source)
  |         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
  | sorImpl.java:25)
  |         at java.lang.reflect.Method.invoke(Method.java:585)
  |         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
  | er.java:155)
  |         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  |         at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
  | or.java:133)
  |         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  |         at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
  | BeanOperationInterceptor.java:142)
  |         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  |         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
  | java:264)
  |         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  |         at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  |         at $Proxy10.deploy(Unknown Source)
  |         at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
  | tScanner.java:421)
  |         at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
  | canner.java:634)
  |         at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
  | doScan(AbstractDeploymentScanner.java:263)
  |         at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
  | bstractDeploymentScanner.java:336)
  |         at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
  | upport.java:289)
  |         at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
  | eanSupport.java:245)
  |         at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
  |         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
  | sorImpl.java:25)
  |         at java.lang.reflect.Method.invoke(Method.java:585)
  |         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
  | er.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(ServiceControl
  | ler.java:978)
  |         at $Proxy0.start(Unknown Source)
  |         at org.jboss.system.ServiceController.start(ServiceController.java:417)
  |         at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
  |         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
  | sorImpl.java:25)
  |         at java.lang.reflect.Method.invoke(Method.java:585)
  |         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
  | er.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(DelegatingMethodAcces
  | sorImpl.java:25)
  |         at java.lang.reflect.Method.invoke(Method.java:585)
  |         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
  | er.java:155)
  |         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  |         at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
  | or.java:133)
  |         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  |         at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
  | BeanOperationInterceptor.java:142)
  |         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  |         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
  | java:264)
  |         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  |         at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  |         at $Proxy5.deploy(Unknown Source)
  |         at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
  |         at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
  |         at org.jboss.Main.boot(Main.java:200)
  |         at org.jboss.Main$1.run(Main.java:508)
  |         at java.lang.Thread.run(Thread.java:595)
  | Caused by: java.lang.ClassNotFoundException: echo.Echo
  |         at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa
  | der.java:1358)
  |         at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa
  | der.java:1204)
  |         at org.jboss.ws.metadata.umdm.EndpointMetaData.getServiceEndpointInterfa
  | ce(EndpointMetaData.java:229)
  |         ... 84 more

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

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


From do-not-reply at jboss.com  Tue Aug 19 18:25:39 2008
From: do-not-reply at jboss.com (gryffin)
Date: Tue, 19 Aug 2008 18:25:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - IllegalStateException Cannot find
	property
Message-ID: <10582395.1219184739420.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am using JBoss 4.2.2 w/ JbossWS Native 3.0.2. After some toil I got a client based on this config working, but then I run into this error which no one else seems to have run into. 


I called a ws to retrieve an AssDTO, I updat the AssetDTO, then call the ws' 'update' method passing it back the updated AssetDTO and it barfs with this un-descriptive error. 

Has anyone else seen this? Thanks!

Exception in thread "main" javax.xml.ws.WebServiceException: java.lang.IllegalStateException: Cannot find property: javax.xml.ws.handler.message.outbound
  | 	at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:410)
  | 	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:316)
  | 	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 $Proxy18.update(Unknown Source)
  | 	at com.boeing.nmt.nls.mv4client.MV4Client.deleteAssociationsForAsset(MV4Client.java:234)
  | 	at com.boeing.nmt.nls.test.AssetTest.main(AssetTest.java:22)
  | Caused by: java.lang.IllegalStateException: Cannot find property: javax.xml.ws.handler.message.outbound
  | 	at org.jboss.ws.core.jaxws.handler.MessageContextJAXWS.processPivot(MessageContextJAXWS.java:109)
  | 	at org.jboss.ws.core.jaxws.client.ClientImpl.processPivot(ClientImpl.java:369)
  | 	at org.jboss.ws.core.CommonClient.processPivotInternal(CommonClient.java:479)
  | 	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:407)
  | 	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:304)
  | 	... 5 more



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

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


From do-not-reply at jboss.com  Tue Aug 19 18:30:52 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 19 Aug 2008 18:30:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Providing your own wsdl instead of
	the generated one.
Message-ID: <17072861.1219185052565.JavaMail.jboss@colo-br-02.atl.jboss.com>

According to this line in your WSDL:

targetNamespace='http://echo/'

the web service class is in a package named echo, and according to this line:

<portType name='Echo'>

the simple class name is Echo, which makes the full class name echo.Echo. Therefore, you must have an echo.Echo class in the WAR file for your web service. Apparently, you don't:

Caused by: java.lang.ClassNotFoundException: echo.Echo

(Hint: always look for the initial exception - with nested exceptions look for 'caused by')


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

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


From do-not-reply at jboss.com  Tue Aug 19 18:34:23 2008
From: do-not-reply at jboss.com (gryffin)
Date: Tue, 19 Aug 2008 18:34:23 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: IllegalStateException Cannot find
	property
Message-ID: <25732966.1219185263784.JavaMail.jboss@colo-br-02.atl.jboss.com>

Here's the relevant part of the port class, 

/**
  |  * This class was generated by the JAX-WS RI.
  |  * JAX-WS RI 2.1.3-b02-
  |  * Generated source version: 2.0
  |  * 
  |  */
  | @WebService(name = "AssetAPIServicePortType", targetNamespace = "http://service.api.mobileview.aeroscout.com")
  | public interface AssetAPIServicePortType {
  | 
  | 
  |     /**
  |      * 
  |      * @param in0
  |      * @return
  |      *     returns com.boeing.nmt.foo.AssetDTO
  |      */
  |     @WebMethod
  |     @WebResult(name = "out", targetNamespace = "http://service.api.mobileview.aeroscout.com")
  |     @RequestWrapper(localName = "update", targetNamespace = "http://service.api.mobileview.aeroscout.com", className = "com.boeing.nmt.foo.Update")
  |     @ResponseWrapper(localName = "updateResponse", targetNamespace = "http://service.api.mobileview.aeroscout.com", className = "com.boeing.nmt.foo.UpdateResponse")
  |     public AssetDTO update(
  |         @WebParam(name = "in0", targetNamespace = "http://service.api.mobileview.aeroscout.com")
  |         AssetDTO in0);

And here's the Update class itself. Perhaps I'm missing some namespace value in here?


  | package com.boeing.nmt.foo;
  | 
  | import java.io.Serializable;
  | import javax.xml.bind.annotation.XmlAccessType;
  | import javax.xml.bind.annotation.XmlAccessorType;
  | import javax.xml.bind.annotation.XmlElement;
  | import javax.xml.bind.annotation.XmlRootElement;
  | import javax.xml.bind.annotation.XmlType;
  | 
  | 
  | /**
  |  * <p>Java class for anonymous complex type.
  |  * 
  |  * <p>The following schema fragment specifies the expected content contained within this class.
  |  * 
  |  * <pre>
  |  * &lt;complexType>
  |  *   &lt;complexContent>
  |  *     &lt;restriction base="{http://www.w3.org/2001/XMLSchema}anyType">
  |  *       &lt;sequence>
  |  *         &lt;element name="in0" type="{http://dto.api.mobileview.aeroscout.com}UserDTO"/>
  |  *       &lt;/sequence>
  |  *     &lt;/restriction>
  |  *   &lt;/complexContent>
  |  * &lt;/complexType>
  |  * </pre>
  |  * 
  |  * 
  |  */
  | @XmlAccessorType(XmlAccessType.FIELD)
  | @XmlType(name = "", propOrder = {
  |     "in0"
  | })
  | @XmlRootElement(name = "update", namespace = "http://service.api.mobileview.aeroscout.com")
  | public class Update
  |     implements Serializable
  | {
  | 
  |     private final static long serialVersionUID = 1L;
  |     @XmlElement(namespace = "http://service.api.mobileview.aeroscout.com", required = true, nillable = true)
  |     protected UserDTO in0;
  | 
  |     /**
  |      * Gets the value of the in0 property.
  |      * 
  |      * @return
  |      *     possible object is
  |      *     {@link UserDTO }
  |      *     
  |      */
  |     public UserDTO getIn0() {
  |         return in0;
  |     }
  | 
  |     /**
  |      * Sets the value of the in0 property.
  |      * 
  |      * @param value
  |      *     allowed object is
  |      *     {@link UserDTO }
  |      *     
  |      */
  |     public void setIn0(UserDTO value) {
  |         this.in0 = value;
  |     }
  | 
  | }
  | 

This code was generated by wsconsume from the JBossWS package. I used a jaxb binding file with generateElementProperty="false" .

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

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


From do-not-reply at jboss.com  Tue Aug 19 21:09:19 2008
From: do-not-reply at jboss.com (JBossWS_NewBee)
Date: Tue, 19 Aug 2008 21:09:19 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Providing your own wsdl instead of
	the generated one.
Message-ID: <21713531.1219194559407.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thanks, Peter. This fixed it!

-Anu



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

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


From do-not-reply at jboss.com  Wed Aug 20 08:55:54 2008
From: do-not-reply at jboss.com (ngtdave)
Date: Wed, 20 Aug 2008 08:55:54 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Providing your own wsdl instead of
	the generated one.
Message-ID: <17017259.1219236954236.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thanks PeterJ!

Sorry Anu, I wasn't reading very carefully, I should have paid more attention before answering. 

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

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


From do-not-reply at jboss.com  Wed Aug 20 09:55:16 2008
From: do-not-reply at jboss.com (rohit.macherla)
Date: Wed, 20 Aug 2008 09:55:16 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Handling timeouts in WebService client
Message-ID: <327693.1219240516988.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi all,

I have JBoss 4.2.2.GA version installed on a HP Unix machine. We have a WebService, say A, that calls another WebService, say B. When A calls B it usually takes a lot of time, say 3-4 minutes to respond. I would like to know where to configure the timeout value for the WebService client A.

I have increased the Transaction timeout of the transaction-manager MBean to 400 ( I guess it is in seconds). Still we don't find any improvement and we get a transfer-timeout error.

  | 
  |   <!--
  |       | The fast in-memory transaction manager.
  |       | Deprecated in JBossAS v4.2. Use JBossTS JTA instead.
  |     - ->
  |    <mbean code="org.jboss.tm.TransactionManagerService"
  |       name="jboss:service=TransactionManager"
  |       xmbean-dd="resource:xmdesc/TransactionManagerService-xmbean.xml">
  |       <attribute name="TransactionTimeout">400</attribute>
  |       <!- - set to false to disable transaction demarcation over IIOP - ->
  |       <attribute name="GlobalIdsEnabled">true</attribute>
  |       <depends optional-attribute-name="XidFactory">jboss:service=XidFactory</depends>
  | 
  |       <!- - Transaction Integrity Checking - ->
  |       <!- - Force a rollback if another thread is associated with the transaction at commit - ->
  |       <!- - <depends optional-attribute-name="TransactionIntegrityFactory"
  |                proxy-type="org.jboss.tm.integrity.TransactionIntegrityFactory">
  |          <mbean code="org.jboss.tm.integrity.FailIncompleteTransaction"
  |                 name="jboss:service=TransactionManager,plugin=TransactionIntegrity"/>
  |       </depends> - ->
  |    </mbean>
  |    -->
  | 
  |    <!-- JBoss Transactions JTA -->
  |    <mbean code="com.arjuna.ats.jbossatx.jta.TransactionManagerService"
  |       name="jboss:service=TransactionManager">
  |       <attribute name="TransactionTimeout">400</attribute>
  |       <attribute name="ObjectStoreDir">${jboss.server.data.dir}/tx-object-store</attribute>
  |    </mbean>
  | 
  | 
  | 
Also, since we are developing the code in Java, we have found some of the following properties that are configured in our code :

  | 
  | timeout.TestTimeOut_Service service = new timeout.TestTimeOut_Service();
  |             timeout.TestTimeOut port = service.getTestTimeOutPort();
  |             
  | ((BindingProvider)port).getRequestContext().
  |                     put("com.sun.xml.ws.request.timeout", 4*60*1000);
  |             
  |             ((BindingProvider)port).getRequestContext().put(
  |                     BindingProviderProperties.REQUEST_TIMEOUT,
  |                     4*60*1000);
  |             
  |             ((BindingProvider)port).getRequestContext().put(
  |                     BindingProviderProperties.CONNECT_TIMEOUT,
  |                     4*60*1000);
  |             
  |             ((BindingProvider)port).getRequestContext().put(
  |                     "com.ibm.SOAP.requestTimeout",
  |                     4*60*1000);
  |             ((BindingProvider)port).getRequestContext().put(
  |                     "org.jboss.webservice.timeout",
  |                     4*60*1000);
  |             
  |             ((BindingProvider)port).getRequestContext().put(
  |                     "org.jboss.webservice.client.timeout",
  |                     4*60*1000);
  |             ((BindingProvider)port).getRequestContext().put(
  |                     "org.jboss.ws.timeout",
  |                     4*60*1000);
  | 
  | 

where, the "TestTimeOut_Service" is the WebService name and the 'port' object is the WebService Port for the "TestTimeOut_Service". We are using NetBeans for developing. And this code change does not help us in increasing the timeout because the WebService A throws a transfer timeout at about 120 seconds almost always.

Please suggest a proper place where we can set the client timeout when calling other 

webservices.

Thanks.

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

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


From do-not-reply at jboss.com  Wed Aug 20 11:53:26 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 20 Aug 2008 11:53:26 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS 3.0.3 Released
Message-ID: <24611630.1219247606289.JavaMail.jboss@colo-br-02.atl.jboss.com>

Sorry, this got lost when we moved to Maven some time ago. I created a jira issue for it: https://jira.jboss.org/jira/browse/JBWS-2286

In the mean time, please note sources are both available through SVN and Maven repositories:

* http://jbws.dyndns.org/mediawiki/index.php?title=Building_From_Source (please not there's a tag for each release we do)
* http://repository.jboss.org/maven2/org/jboss/ws/

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

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


From do-not-reply at jboss.com  Thu Aug 21 05:29:29 2008
From: do-not-reply at jboss.com (PeterAndersen)
Date: Thu, 21 Aug 2008 05:29:29 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Using rpc/encoded
Message-ID: <11530500.1219310969560.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi

I need to integrate to a rpc/encoded ws, according to this i need to use jax-rpc, but the jbossws jax-rpc state the following:

- JBossWS conforms to the WS-I basic profile, which eliminates the encoded
- use. This leaves you with the following style/use models:
-
-    * RPC/Literal
-    * Document/Literal
-    * Message style 

see: http://jbws.dyndns.org/mediawiki/index.php?title=JAX-RPC_User_Guide#Getting_started

Is the conclusion that jbossws do not support rpc/encoded?

/Peter


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

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


From do-not-reply at jboss.com  Thu Aug 21 05:40:27 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Thu, 21 Aug 2008 05:40:27 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Create the simplest WebService
	possible
Message-ID: <14262479.1219311627856.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi Sergio,
I don't want to start a flame, just need to understand how to move to further improve the jbossws docs (which, btw, improved a lot since 1 year ago).

"smmartins" wrote : 
  |  - changed several JBoss libs from place
  | 
Do you mean what is explained here? http://jbws.dyndns.org/mediawiki/index.php?title=Installation (section "Using  JBossWS Native with JDK 6)

anonymous wrote : 
  |  - Found two really useful web pages:
  |    - http://www.theregister.co.uk/2007/01/23/ejb_web_services/
  | 
The fast introduction to the WS world is covered in the pages belonging to this wiki category http://jbws.dyndns.org/mediawiki/index.php?title=Category:WS_Culture.
The development strategies using the tools as well as the client generation and run steps are described here http://jbws.dyndns.org/mediawiki/index.php?title=JBossWS_JAX-WS_Tools.
Do you think something is missing? (maybe a page for real beginners-who-don't-want-to-read-lots-of-pages with a super-slim walkthrough?) Or you did not find those pages, so they should be better advertised / more easily reachable from the doc home page?


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

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


From do-not-reply at jboss.com  Thu Aug 21 05:50:48 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Thu, 21 Aug 2008 05:50:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: jbossws with apache
Message-ID: <32135988.1219312248886.JavaMail.jboss@colo-br-02.atl.jboss.com>

"r.eloc" wrote : "palin" wrote : 
  |   | I would check what url apache is actually trying to connect to; I mean, it's ok that you get a "http GET not supported" if you access an endpoint using your browser. As a matter of fact, endpoints support POST, GET is supposed to work only for wsdl retrieval calls.
  |   | 
  | 
  | Why is GET not supported?  All the other web service frameworks I have used (Apache Axis, .NET) have supported that, it's quite useful when developing and testing.

I'd say because when you invoke a service, you provide the soap request message, thus you need POST.

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

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


From do-not-reply at jboss.com  Thu Aug 21 06:18:24 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Thu, 21 Aug 2008 06:18:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS URL different for 4.2.2 and 4.2.3
Message-ID: <17194301.1219313904944.JavaMail.jboss@colo-br-02.atl.jboss.com>

That's most probably because of this: https://jira.jboss.org/jira/browse/JBWS-1813
IOW there was a bug which was fixed in AS 4.2.3.GA.

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

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


From do-not-reply at jboss.com  Thu Aug 21 07:42:32 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Thu, 21 Aug 2008 07:42:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Trying to use jboss.xml instead of
	@WebContext
Message-ID: <16804783.1219318952583.JavaMail.jboss@colo-br-02.atl.jboss.com>

Which version of JBoss Application Server are you using? If it's 4.2.2.GA please try moving to 4.2.3.GA as this might be due to an already fixed bug.

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

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


From do-not-reply at jboss.com  Thu Aug 21 07:47:50 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Thu, 21 Aug 2008 07:47:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: wsconsume and rpc/encoded soap
	message
Message-ID: <14266363.1219319270707.JavaMail.jboss@colo-br-02.atl.jboss.com>

Please search in the forum for this topic. In few words jbossws native has really basic rpc/enc functionalities, we should actually say that rpc/enc is not supported any more. That's because the WS-I Basic Profile disallowed it.

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

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


From do-not-reply at jboss.com  Thu Aug 21 07:51:10 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Thu, 21 Aug 2008 07:51:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Deploying JDeveloper/Oracle
	webservices on JBossWS
Message-ID: <27202965.1219319470049.JavaMail.jboss@colo-br-02.atl.jboss.com>

Check you classpath and verify which version of wsdl4j you're currently using.

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

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


From do-not-reply at jboss.com  Thu Aug 21 07:58:54 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Thu, 21 Aug 2008 07:58:54 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Multiple WSDL bindings warning
Message-ID: <27066281.1219319934748.JavaMail.jboss@colo-br-02.atl.jboss.com>

That's a warning message saying that the wsdl you're consuming has multiple bindings for the same interface. The last binding is actually used in those cases.

If you have problems with the generated log, also consider you can just limit the logs of org.jboss.ws.metadata.wsdl.WSDLDefinitions class, without affecting your business code or any other JBoss class.

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

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


From do-not-reply at jboss.com  Thu Aug 21 08:53:09 2008
From: do-not-reply at jboss.com (karypid)
Date: Thu, 21 Aug 2008 08:53:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Trying to use jboss.xml instead of
	@WebContext
Message-ID: <9891687.1219323189382.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello,

I am using the very latest: JBossAS 4.2.3.GA and JBossWS-Native 3.0.3.GA.

When my EJB is coded as follows:

@Stateless
  | @WebService(
  |     serviceName="MyBasicWS", portName = "MyBasicWSSOAP",
  |     targetNamespace = "http://www.example.org/MyBasicWS/",
  |     endpointInterface = "org.example.mybasicws.MyBasicWS")
  | @WebContext(authMethod="BASIC")
  | @RolesAllowed("friend")
  | public class MyBasicWSImpl {
  | 	public String echo(String in) {
  | 		System.out.println("RECEIVED: " + in);
  | 		return in;
  | 	}
  | }

I use the following jboss.xml to set the security domain:

<!DOCTYPE jboss PUBLIC
  |       "-//JBoss//DTD JBOSS 4.2//EN"
  |       "http://www.jboss.org/j2ee/dtd/jboss_4_2.dtd">
  | <jboss>
  | 	<security-domain>java:/jaas/JBossWS</security-domain>
  | 	<webservices>
  | 		<context-root>myBasicWS</context-root>
  | 	</webservices>
  | </jboss>

Everything works like a charm with the combination above (I must access the EJB as kermit/thefrog from the default jbossws-xxxx.properties files). However, I want to get rid of the @WebContext annotation. My idea (which does not work) is the following combination:

@Stateless
  | @WebService(
  |     serviceName="MyBasicWS", portName = "MyBasicWSSOAP",
  |     targetNamespace = "http://www.example.org/MyBasicWS/",
  |     endpointInterface = "org.example.mybasicws.MyBasicWS")
  | //@WebContext(authMethod="BASIC")
  | //Undesirable
  | //The above should be picked up from jboss.xml
  | @RolesAllowed("friend")
  | public class MyBasicWSImpl {
  | 	public String echo(String in) {
  | 		System.out.println("RECEIVED: " + in);
  | 		return in;
  | 	}
  | }

Then, I try to express that the EJB must use BASIC authentication method as follows:

<!DOCTYPE jboss PUBLIC
  |       "-//JBoss//DTD JBOSS 4.2//EN"
  |       "http://www.jboss.org/j2ee/dtd/jboss_4_2.dtd">
  | <jboss>
  | 	<security-domain>java:/jaas/JBossWS</security-domain>
  | 	<webservices>
  | 		<context-root>myBasicWS</context-root>
  | 	</webservices>
  | 	<enterprise-beans>
  | 		<session>
  | 			<ejb-name>MyBasicWSImpl</ejb-name>
  | 			<port-component>
  | 				<port-component-name>MyBasicWSSOAP</port-component-name>
  | 				<auth-method>BASIC</auth-method>
  | 			</port-component>
  | 		</session>
  | 	</enterprise-beans>
  | </jboss>

In this case however, the client throws an authorization failure exception:

javax.xml.ws.soap.SOAPFaultException: Authorization failure
  | 	at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:77)
  | 	at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:107)
  | 	at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:577)
  | 	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:381)
  | 	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:291)
  | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
  | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
  | 	at $Proxy19.echo(Unknown Source)
  | 	at test.TestBasicWS.basicAuthTest(TestBasicWS.java:41)

On the server side, I see this:

15:41:47,349 ERROR [RoleBasedAuthorizationInterceptor] Insufficient permissions, principal=null, requiredRoles=[friend], principalRoles=[]
  | 15:41:47,349 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
  | javax.ejb.EJBAccessException: Authorization failure
  | 	at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:120

Apparently, JBoss disregards the BASIC-auth and does NOT assign a principal to the session. Therefore the role-based authenticator denies access to the method (as it should).

Apparently, my jboss.xml does not tell JBoss to associate basic-auth with the published web service. I was suspicious of what I should put in the "port-component-name" value. Supposedly, the documentation says: Maps to the port-component-name in the webservices.xml descriptor. However, I do not use a webservices.xml file but use the @WebService annotation instead.

In the code above I use the value for the "portName" attribute of @WebService but I also tried the ejb-name (MyBasicWSImpl) and the serviceName (MyBasicWS) with no luck.

Any clues as to how I can achieve this while keeping the code JBoss-clear?


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

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


From do-not-reply at jboss.com  Thu Aug 21 14:02:20 2008
From: do-not-reply at jboss.com (medalhas)
Date: Thu, 21 Aug 2008 14:02:20 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Consuming rpc/encoded WS
Message-ID: <3153416.1219341740415.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I have deployed application, that has some WS developed on JAX-WS.
This WS are consumed by other applications so cannot change them.

Now i have this third party WS that i have to consume, but they are developed with NuSOAP(php) and are rpc/encoded.
As JAX-WS doesn't support rpc/encoded i cannot use the wsconsume, 

what is best way to consume this webservices?


Environment:
Java 5
JBoss 4.2.2
jbossws-3.0.1-native-2.0.4.GA
Seam 2.0.2SP1

Regards.


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

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


From do-not-reply at jboss.com  Thu Aug 21 14:35:00 2008
From: do-not-reply at jboss.com (felipepontes)
Date: Thu, 21 Aug 2008 14:35:00 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem consuming .net webservice
	with jbossws-3.0.1-nat
Message-ID: <11058291.1219343700225.JavaMail.jboss@colo-br-02.atl.jboss.com>

Claudio, I'm facing the same problem. I need consume web services behind a proxy server. Did you resolved it?

Felipe.

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

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


From do-not-reply at jboss.com  Thu Aug 21 15:12:10 2008
From: do-not-reply at jboss.com (kosulin)
Date: Thu, 21 Aug 2008 15:12:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WS-Security: possible bug with MTOM
Message-ID: <30314423.1219345930240.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi, I use MTOM to send zip archive with WS response, and it works like a charm. However, when I add support for WS-Security, all web methods which send plain XML response, succeed, but the method which responds with ZIP file attached using MTOM, I get an Exception:
14:59:47,457 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
  | org.jboss.ws.WSException: No ByteArrayConverter for content type: application/zip
  |         at org.jboss.ws.core.utils.MimeUtils.getConverterForContentType(MimeUtils.java:217)
  |         at org.jboss.ws.extensions.xop.XOPContext.replaceBase64Representation(XOPContext.java:290)
  |         at org.jboss.ws.extensions.xop.XOPContext.restoreXOPDataDOM(XOPContext.java:266)
  |         at org.jboss.ws.extensions.xop.XOPContext.restoreXOPDataDOM(XOPContext.java:275)
  |         at org.jboss.ws.extensions.xop.XOPContext.restoreXOPDataDOM(XOPContext.java:275)
  |         at org.jboss.ws.extensions.xop.XOPContext.restoreXOPDataDOM(XOPContext.java:275)
  |         at org.jboss.ws.core.soap.SOAPContentElement.handleMTOMTransitions(SOAPContentElement.java:600)
  |         at org.jboss.ws.extensions.xop.RestoreXOPElementVisitor.visitSOAPContentElement(RestoreXOPElementVisitor.java:73)
  |         at org.jboss.ws.core.soap.SOAPContentElement.accept(SOAPContentElement.java:611)
  |         at org.jboss.ws.extensions.xop.RestoreXOPElementVisitor.visitXOPElements(RestoreXOPElementVisitor.java:54)
  |         at org.jboss.ws.extensions.xop.RestoreXOPElementVisitor.visitXOPElements(RestoreXOPElementVisitor.java:63)
  |         at org.jboss.ws.extensions.xop.XOPContext.visitAndRestoreXOPData(XOPContext.java:246)
  |         at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callResponseHandlerChain(HandlerDelegateJAXWS.java:109)
  |         at org.jboss.ws.core.server.ServiceEndpointInvoker.callResponseHandlerChain(ServiceEndpointInvoker.java:132)
  |         at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:267)
  |         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:466)
  |         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:235)
  |         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:183)
  |         at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:189)
  |         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
  |         at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:90)
  |         at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:96)
  |         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:325)
  |         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
  |         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
  |         at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
  |         at java.lang.Thread.run(Unknown Source)
  | 

application/zip is a standard MIME-type. Is this a bug or my fault?

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

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


From do-not-reply at jboss.com  Thu Aug 21 15:27:17 2008
From: do-not-reply at jboss.com (kosulin)
Date: Thu, 21 Aug 2008 15:27:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-Security: possible bug with MTOM
Message-ID: <31389332.1219346837195.JavaMail.jboss@colo-br-02.atl.jboss.com>

Sorry, here is my config: jre 1.6.0_07, JBoss 5.0.0CR1, jbossws-3.0.2.

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

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


From do-not-reply at jboss.com  Fri Aug 22 04:39:52 2008
From: do-not-reply at jboss.com (dkjha9)
Date: Fri, 22 Aug 2008 04:39:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Deploying JDeveloper/Oracle
	webservices on JBossWS
Message-ID: <11738859.1219394392509.JavaMail.jboss@colo-br-02.atl.jboss.com>

Web services developed using Jdeveloper cant be deployed on any App Server other than OC4J:

refer the below link.. 

http://forums.oracle.com/forums/thread.jspa?threadID=390017&tstart=0

Regards 
Dhananjay

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

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


From do-not-reply at jboss.com  Fri Aug 22 12:00:42 2008
From: do-not-reply at jboss.com (cappeca)
Date: Fri, 22 Aug 2008 12:00:42 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Deploying JDeveloper/Oracle
	webservices on JBossWS
Message-ID: <27123513.1219420848299.JavaMail.jboss@colo-br-02.atl.jboss.com>

That discussion is 2 years old, is that still up to date? I have only tried OC4J and JBoss, so I can't say (making arrangements right now to test it with WebSphere). If so, I'd like to see some official statement regarding this.

In any case, this part calls my attention:

"The Oracle Web Service team is currently working on a document explaning how you can create JAX-RPC services and deploy them in different container, but it is still an ongoing project and Tomcat is not the first targetted platform."

Any news on this, since it's been two years?

"Since you look familiar with Apache Axis, it is today the most portable Web Service stack, it has some limitations (support of WS-* for example), but based on your use case it looks using Apache Axis will be the best approach. As you may know Apace Axis is supported on OracleAS 10g R2 and R3."

And this, has anyone with the problem in this thread switched to Apache Axis?


As for the wsdl4j question, I have replaced mine with version 1.6.2, and it still seem incompatible with the Oracle library. Now, before we use the JDeveloper to deploy on JBoss, we have to copy a lot of libraries to the JBoss structure, in a process called ADF Runtime Installation. I'm assuming that should solve the class cast problem, but apparently not. My question is, why is this cast necessary inside JBoss?



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

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


From do-not-reply at jboss.com  Fri Aug 22 15:52:18 2008
From: do-not-reply at jboss.com (mjcolbert)
Date: Fri, 22 Aug 2008 15:52:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Strange
	java.lang.ClassCastException: org.jboss.axis.Mes
Message-ID: <27149830.1219434738713.JavaMail.jboss@colo-br-02.atl.jboss.com>

Does anybody have a complete solution for this problems. I am getting it as well with the CLassCastException.
It works fine as a standalone client but under EJB with JBoss ith fails to execute completely.

I am using jboss 4.0.3 
I am sure it is the same problem as this.

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

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


From do-not-reply at jboss.com  Fri Aug 22 15:54:31 2008
From: do-not-reply at jboss.com (gryffin)
Date: Fri, 22 Aug 2008 15:54:31 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: IllegalStateException Cannot find
	property
Message-ID: <24878905.1219434871147.JavaMail.jboss@colo-br-02.atl.jboss.com>

I installed JBossAS 4.2.3, this time NOT updating it to JBossWS 3.0.4. I get the same error running my client through Eclipse. I tried wsrunclient ( v4.2.3) and got a different error:


C:\Documents and Settings\tx714c\My Documents\workspace\MV4Client2\bin>c:\jboss-4.2.3.GA\bin\wsruncl
  | ient com.boeing.nmt.nls.test.AssetTest
  | log4j:WARN No appenders could be found for logger (org.jboss.ws.metadata.builder.jaxws.JAXWSWebServi
  | ceMetaDataBuilder).
  | log4j:WARN Please initialize the log4j system properly.
  |         ====================================
  | DISABLE TAG: FFF123456789
  | Exception in thread "main" 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 $Proxy19.findPopulatedTagByNetworkId(Unknown Source)
  |         at com.boeing.nmt.nls.mv4client.MV4Client.disableTag(MV4Client.java:305)
  |         at com.boeing.nmt.nls.test.AssetTest.main(AssetTest.java:25)
  | Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses
  |  of SOAPMessage
  |         at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:441)
  |         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)
  |         ... 5 more

I am using code generated by JBoss, using JBoss to run it, why is JBoss carping out?

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

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


From do-not-reply at jboss.com  Fri Aug 22 17:02:52 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 22 Aug 2008 17:02:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: IllegalStateException Cannot find
	property
Message-ID: <3628137.1219438972884.JavaMail.jboss@colo-br-02.atl.jboss.com>

Based on the error message "setProperty must be overridden by all subclasses of SOAPMessage" I will guess that you are running with JDK 6. You should either fall back to JDK 1.5 or see http://jbws.dyndns.org/mediawiki/index.php?title=Install_JBossWS#Using_JBossWS_with_JDK_6 for getting this to work with JDK 6.

I also want to caution you about running within a directory that has spaces in its name - that tends to give various Java libraries fits. It might not be an issue right now, but if you see weird errors you might want to move your code elsewhere. 

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

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


From do-not-reply at jboss.com  Fri Aug 22 18:33:18 2008
From: do-not-reply at jboss.com (japuentem)
Date: Fri, 22 Aug 2008 18:33:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Problem working with webservices
Message-ID: <1368740.1219444398617.JavaMail.jboss@colo-br-02.atl.jboss.com>

hi

i create 5 webservices and all share the same database configuration. I have my database configuration file on the C:\jboss-4.0.5.GA\bin folder, now i need to use different configuration file to each webservice.

Anyone know if i can do this

Thanks

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

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


From do-not-reply at jboss.com  Sun Aug 24 06:25:51 2008
From: do-not-reply at jboss.com (karypid)
Date: Sun, 24 Aug 2008 06:25:51 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem working with webservices
Message-ID: <7466236.1219573551785.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello,

Your problem description is too short to allow someone to help you.

Web services do not have a database configuration. I will assume that the web services you created access a database, and that your problem is that you now want each web service to connect to a different database server.

If that is the case, then unfortunately your post is most likely off-topic on this forum.


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

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


From do-not-reply at jboss.com  Sun Aug 24 10:29:58 2008
From: do-not-reply at jboss.com (bhushans)
Date: Sun, 24 Aug 2008 10:29:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Namespace Problem
Message-ID: <23706143.1219588198366.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am using Jboss4.2.3 GA with sun jdk 1.5 
I have java class representing a web service. It uses JAX-WS annotations (needless to say :)).

The "targetnamespace" specified in @Webservice annotation is - 

targetNamespace = "http://abc.com/web/services/MyService".

I have a method in the class called "doJob" (tagged with necessary annotations to be a valid web method). In the @WebParam annotation for this method I am specifying the another targetNamespace having value -

targetNamespace = "http://webservice.web.service.com".

Once this webservice is deployed the corresponding wsdl files shows targetNamespace at root level (definitions node) as "http://abc.com/web/services/MyService" which is expected, however under binding section the same "namespace" is repeated even for the operation "doJob", where as I want it to be "http://webservice.web.service.com"

I have pasted the relevant section of wsdl below - 



    <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
    
      <soap:operation soapAction=""/>
      
        <soap:body use="literal" namespace="http://abc.com/web/services/MyService"/>
      
      
        <soap:body use="literal" namespace="http://abc.com/web/services/MyService"/>
      
    .......


Is this the correct way to do it?.

Thnx in advance

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

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


From do-not-reply at jboss.com  Mon Aug 25 02:00:18 2008
From: do-not-reply at jboss.com (nandanT)
Date: Mon, 25 Aug 2008 02:00:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Error passing Complex Types as
	parameters in Web Service
Message-ID: <4681691.1219644018359.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I have created a simple Hello World Web Service.
I have created a POJO HelloParam
The method exposed in the web service "sayHello" takes HelloParam object as parameter.
The WSDL is generated and is deployed successfully over JBoss.
But when I run the client, I get the following error:

Exception in thread "main" org.jboss.ws.WSException: Cannot obtain java type mapping for: {http://ejb3webservice.wipro.com/}helloParam

Following are the classes that I have created: 

  | package com.wipro.ejb3webservice;
  | 
  | import java.io.Serializable;
  | 
  | public class HelloParam implements Serializable{
  | 	/**
  | 	 * 
  | 	 */
  | 	private static final long serialVersionUID = 5446103626304202057L;
  | 	String firstName;
  | 	String lastName;
  | 	
  | 	/**
  | 	 * @return the firstName
  | 	 */
  | 	public String getFirstName() {
  | 		return firstName;
  | 	}
  | 	/**
  | 	 * @param firstName the firstName to set
  | 	 */
  | 	public void setFirstName(String firstName) {
  | 		this.firstName = firstName;
  | 	}
  | 	/**
  | 	 * @return the lastName
  | 	 */
  | 	public String getLastName() {
  | 		return lastName;
  | 	}
  | 	/**
  | 	 * @param lastName the lastName to set
  | 	 */
  | 	public void setLastName(String lastName) {
  | 		this.lastName = lastName;
  | 	}
  | 	/**
  | 	 * @param firstName
  | 	 * @param lastName
  | 	 */
  | 	public HelloParam(String firstName, String lastName) {
  | 		super();
  | 		this.firstName = firstName;
  | 		this.lastName = lastName;
  | 	}
  | 	/**
  | 	 * 
  | 	 */
  | 	public HelloParam() {
  | 		
  | 	}
  | }
  | 

The interface that is exposed as webservice is :

package com.wipro.ejb3webservice;
  | 
  | import java.rmi.Remote;
  | 
  | import javax.jws.WebService;
  | import javax.jws.soap.SOAPBinding;
  | import javax.jws.soap.SOAPBinding.Style;
  | 
  | 
  | @WebService
  | @SOAPBinding(style = Style.RPC)
  | public interface HelloWorld extends Remote {
  | 	public void sayHello(HelloParam helloParam);
  | }

And the implementation of the interfaces is:

package com.wipro.ejb3webservice;
  | 
  | import javax.ejb.Remote;
  | import javax.ejb.Stateless;
  | import javax.jws.WebMethod;
  | import javax.jws.WebParam;
  | import javax.jws.WebService;
  | 
  | 
  | @Stateless
  | @Remote(HelloWorld.class)
  | @WebService(name="HelloWorldName" ,serviceName="HelloWorldImplService",endpointInterface = "com.wipro.ejb3webservice.HelloWorld")
  | public class HelloWorldImpl implements HelloWorld {
  | 
  | 	@WebMethod
  | 	public void sayHello(
  | 			@WebParam(name="helloParam" )
  | 			HelloParam helloParam)
  | 			{
  | 		System.out.println("first name" + helloParam.getFirstName()+"last name--"+ helloParam.getLastName());
  | 		
  | 	}
  | }


The WSDL file genereated is:

<?xml version="1.0" encoding="UTF-8"?>
  | <definitions name="HelloWorldImplService" targetNamespace="http://ejb3webservice.wipro.com/" xmlns:tns="http://ejb3webservice.wipro.com/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/">
  |   <types>
  |     <xs:schema targetNamespace="http://ejb3webservice.wipro.com/" version="1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema">
  |    <xs:complexType name="helloParam">
  |     <xs:sequence>
  |      <xs:element minOccurs="0" name="firstName" type="xs:string"/>
  |      <xs:element minOccurs="0" name="lastName" type="xs:string"/>
  |     </xs:sequence>
  |    </xs:complexType>
  |   </xs:schema>
  |   </types>
  |   <message name="HelloWorld_sayHelloResponse">
  |   </message>
  |   <message name="HelloWorld_sayHello">
  |     <part name="arg0" type="tns:helloParam">
  |     </part>
  |   </message>
  |   <portType name="HelloWorld">
  |     <operation name="sayHello" parameterOrder="arg0">
  |       <input message="tns:HelloWorld_sayHello">
  |     </input>
  |       <output message="tns:HelloWorld_sayHelloResponse">
  |     </output>
  |     </operation>
  |   </portType>
  |   <binding name="HelloWorldBinding" type="tns:HelloWorld">
  |     <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
  |     <operation name="sayHello">
  |       <soap:operation soapAction=""/>
  |       <input>
  |         <soap:body use="literal" namespace="http://ejb3webservice.wipro.com/"/>
  |       </input>
  |       <output>
  |         <soap:body use="literal" namespace="http://ejb3webservice.wipro.com/"/>
  |       </output>
  |     </operation>
  |   </binding>
  |   <service name="HelloWorldImplService">
  |     <port name="HelloWorldNamePort" binding="tns:HelloWorldBinding">
  |       <soap:address location="http://localhost:8080/Ejb3Webservice/HelloWorldImpl"/>
  |     </port>
  |   </service>
  | </definitions>
  | 

Can any one help me on this issue.
Its very urgent.

Thanks and Regards
-Nandan

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

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


From do-not-reply at jboss.com  Mon Aug 25 03:32:17 2008
From: do-not-reply at jboss.com (karypid)
Date: Mon, 25 Aug 2008 03:32:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-Security: possible bug with MTOM
Message-ID: <1689447.1219649537180.JavaMail.jboss@colo-br-02.atl.jboss.com>

Just an idea: try using application/octet-stream.

Not sure it would help though...


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

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


From do-not-reply at jboss.com  Mon Aug 25 03:35:58 2008
From: do-not-reply at jboss.com (smjain)
Date: Mon, 25 Aug 2008 03:35:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-Eventing and subscription
	expiration time
Message-ID: <12791251.1219649758422.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am using JBoss WS 2.0.3 and wanted to change the max lease time..
Whats the MBean parameter for doing so. I didnt find an in the Subscription Manager MBean. Can you please help me in that
Regards
Shashank

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

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


From do-not-reply at jboss.com  Mon Aug 25 08:04:50 2008
From: do-not-reply at jboss.com (viniciuscarvalho)
Date: Mon, 25 Aug 2008 08:04:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Can't get a dependency on
	jboss.ws:service=EndpointRegistry
Message-ID: <23276708.1219665890686.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello there! I've created MBeans several times on jboss, and I can't find what am I missing here.

I'm developing a DatabaseRecordProcessor, it's start method looks like this:


  | 	public void start() throws Exception{
  | 		try
  | 		{
  | 		  MBeanServer server = MBeanServerLocator.locate();
  | 		  ManagedEndpointRegistryMBean registry = (ManagedEndpointRegistryMBean)MBeanProxyExt.create(ManagedEndpointRegistryMBean.class, "jboss.ws:service=EndpointRegistry");
  | 			
  | 		  	Set<ObjectName> names = registry.getEndpoints();
  | 			for(ObjectName o : names){
  | 				((ManagedEndpointMBean)MBeanProxyExt.create(ManagedEndpointMBean.class, o)).addRecordProcessor(this);
  | 			}
  | 		}
  | 		catch (Exception e)
  | 		{
  | 		  e.printStackTrace();
  | 		}
  | 
  | 	}
  | 

and the jboss-service:


  | <?xml version="1.0" encoding="UTF-8"?>
  | <server>
  | <mbean name="bobsam:service=DatabaseRecordProcessor" code="com.furiousbob.management.DatabaseRecordProcessor">
  | 	<depends>jboss.ws:service=EndpointRegistry</depends>
  | </mbean>
  | 
  | </server>
  | 

Well, it all seems ok. But it never gets installed, the jmx-core complains about jboss.ws:service=EndpointRegistry is NOTINSTALLED.

What's funny is that: if I remove the dependency and put my sar on the deploy.last it works fine. What I can't understand is why the dependency mechanism is not working for jboss.ws mbeans?

Regards

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

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


From do-not-reply at jboss.com  Mon Aug 25 08:09:16 2008
From: do-not-reply at jboss.com (karypid)
Date: Mon, 25 Aug 2008 08:09:16 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS throws exception when
	receiving unbound soap hea
Message-ID: <17995711.1219666156147.JavaMail.jboss@colo-br-02.atl.jboss.com>

Have you checked whether the "mustUnderstand" header is set in your SOAP messages? Just a thought...

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

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


From do-not-reply at jboss.com  Mon Aug 25 09:21:57 2008
From: do-not-reply at jboss.com (smjain)
Date: Mon, 25 Aug 2008 09:21:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-Eventing and subscription
	expiration time
Message-ID: <7149298.1219670517224.JavaMail.jboss@colo-br-02.atl.jboss.com>

"heiko.braun at jboss.com" wrote : Thanks Stefano, i did patch the eventing source acccordingly. This will make it into 1.0.4.
I checked that this was added in 1.0.4 and then removed later..
I am using WS 2.0.3. How do I configure the lease time...
Regards
Shashank

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

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


From do-not-reply at jboss.com  Mon Aug 25 10:14:10 2008
From: do-not-reply at jboss.com (kosulin)
Date: Mon, 25 Aug 2008 10:14:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-Security: possible bug with MTOM
Message-ID: <18881335.1219673650291.JavaMail.jboss@colo-br-02.atl.jboss.com>

The issue with application/octet stream is in how out client handles response. Clients (java and .NET) invoke a proper plug-in based on the MIME type, and we need to support at least 3 various MIME-types (ZIP, exe, pdf). We can make workaround by analyzing the file extension, but the main question is: is this the bug (both WS-Security and MTOM work great separately), or am I doing something wrong?

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

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


From do-not-reply at jboss.com  Mon Aug 25 10:40:03 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 25 Aug 2008 10:40:03 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Handling timeouts in WebService
	client
Message-ID: <26766319.1219675204069.JavaMail.jboss@colo-br-02.atl.jboss.com>

To setup the client invocation timeout, you have to setup the client timeout property in the request context through your port instance; the timeout will be then be passed to the remoting layer:

  | ((BindingProvider)port).getRequestContext().put(StubExt.PROPERTY_CLIENT_TIMEOUT, timeout);
  | 

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

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


From do-not-reply at jboss.com  Mon Aug 25 10:53:24 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 25 Aug 2008 10:53:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Strange
	java.lang.ClassCastException: org.jboss.axis.Mes
Message-ID: <28311370.1219676004432.JavaMail.jboss@colo-br-02.atl.jboss.com>

"mjcolbert" wrote : Does anybody have a complete solution for this problems. I am getting it as well with the CLassCastException.
  | It works fine as a standalone client but under EJB with JBoss ith fails to execute completely.
  | 
  | I am using jboss 4.0.3 
  | I am sure it is the same problem as this.

I suggest you to switch to a recent jboss installation; then check the classpath and ensure you're only using libraries coming from your jboss installation. This will be enough to get rid of this class cast exceptions.

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

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


From do-not-reply at jboss.com  Mon Aug 25 10:57:49 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 25 Aug 2008 10:57:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: [UsingAddressing] tag is not added
	to auto-generated WSD
Message-ID: <22315824.1219676269989.JavaMail.jboss@colo-br-02.atl.jboss.com>

Yes. Feel free to create a feature request issue on JIRA.

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

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


From do-not-reply at jboss.com  Mon Aug 25 11:08:48 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 25 Aug 2008 11:08:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS throws exception when
	receiving unbound soap hea
Message-ID: <10925943.1219676928502.JavaMail.jboss@colo-br-02.atl.jboss.com>

To use the jaxws reference implementation you need to install JBossWS-Metro on your application server, you can't do that simply copying the Sun's libraries. Please refer the download page.
Sorry, there's not an option to ignore the soap headers in the incoming messages.

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

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


From do-not-reply at jboss.com  Mon Aug 25 11:15:41 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 25 Aug 2008 11:15:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: More soap:address problems
Message-ID: <31744115.1219677341917.JavaMail.jboss@colo-br-02.atl.jboss.com>

JBossWS Native is the name we gave to our own stack implementation when JBossWS started supporting the Metro and CXF stacks too, see http://jbws.dyndns.org/mediawiki/index.php?title=WSF
JBossWS 1.2 is a really old version of JBossWS instead.

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

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


From do-not-reply at jboss.com  Mon Aug 25 12:44:21 2008
From: do-not-reply at jboss.com (viniciuscarvalho)
Date: Mon, 25 Aug 2008 12:44:21 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Receiving notifications from endpoints
Message-ID: <17360972.1219682661126.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello there! Is there a way to be notified when new endpoints get registred? I was looking at the source code for the ManagedEndpointRegistry and could not find any notifications using the JMX notification mechanism.
Is there an way to acomplish that?

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

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


From do-not-reply at jboss.com  Mon Aug 25 13:44:41 2008
From: do-not-reply at jboss.com (preston)
Date: Mon, 25 Aug 2008 13:44:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Keystore problems... using metro
Message-ID: <23700706.1219686281908.JavaMail.jboss@colo-br-02.atl.jboss.com>

I'm new to all this, so if pieces of my post don't make sense please ask me to explain further.

I've used metro to consume a wsdl and create the source files. Now I'm trying to use those files from within JBoss. 

The test server has a cert that I needed to add to my keystore. I've done this using keytool. The problem I seem to be having is that I don't think JBoss is using the keystore because I get the following error

"javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorEx
ception: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: una
ble to find valid certification path to requested target "

I've made the following changes to my startJBoss.bat
SET JAVA_OPTS = %JAVA_OPTS% -Djavax.net.ssl.keyStore=mykeystore
SET JAVA_OPTS = %JAVA_OPTS% -Djavax.net.ssl.keyStorePassword=password

Any ideas?



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

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


From do-not-reply at jboss.com  Mon Aug 25 14:31:53 2008
From: do-not-reply at jboss.com (stepmarti)
Date: Mon, 25 Aug 2008 14:31:53 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Keystore problems... using metro
Message-ID: <25350497.1219689113051.JavaMail.jboss@colo-br-02.atl.jboss.com>

I preston.
Please specify the Web Service that you need to consume, for example, Does it use WS-Security?, if so, you have to configure the ws-security-client flie to reference the keystore and trustore.

Peraphs by your post the error messages relates to public key in trutstore file. Rmemeber that you have to add the cert to keystore and trsutore file.



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

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


From do-not-reply at jboss.com  Mon Aug 25 14:39:35 2008
From: do-not-reply at jboss.com (kosulin)
Date: Mon, 25 Aug 2008 14:39:35 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Problem: MTOM, SoapException, and WSE 3
Message-ID: <2934877.1219689575149.JavaMail.jboss@colo-br-02.atl.jboss.com>

Our client uses WSE 3 to get MTOM-enabled response from us. However, if for some reason we have to return a SOAP fault, the client can't handle response, because it is not MTOM-enabled. This is well known limitation on MS side (request/response content type should have the same MTOM encoding), but I need some workaround on the server side. Is it possible to force JBossWS (3.0.2) to use MTOM encoding with response, such as WebFault, even when there is no encoded element included? Thanks.

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

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


From do-not-reply at jboss.com  Mon Aug 25 14:56:23 2008
From: do-not-reply at jboss.com (preston)
Date: Mon, 25 Aug 2008 14:56:23 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Keystore problems... using metro
Message-ID: <25692594.1219690583876.JavaMail.jboss@colo-br-02.atl.jboss.com>

It's an internal web service so I can't post the url. How would I know if it uses WS-Security.

Are you saying I have to add the cert to BOTH the keystore and truststore? If so is the truststore just another keystore?

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

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


From do-not-reply at jboss.com  Mon Aug 25 17:10:48 2008
From: do-not-reply at jboss.com (stepmarti)
Date: Mon, 25 Aug 2008 17:10:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Keystore problems... using metro
Message-ID: <22600916.1219698648041.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I am no asking you for URL Web Service, I am asking you for security configuration.

"How would I know if it uses WS-Security"
Re: If the Web Service is implemented using metro you can see it in security service configuration file.

Respect to keystore, really, you only have to add the cert to truststore because there is where java looks for trust certificates that comes with messages (server sends a message and signs and/or encrypts it whit a cert).



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

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


From do-not-reply at jboss.com  Mon Aug 25 17:28:27 2008
From: do-not-reply at jboss.com (TheOverlord)
Date: Mon, 25 Aug 2008 17:28:27 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JbossWS vs Apache Axis
Message-ID: <28871690.1219699707686.JavaMail.jboss@colo-br-02.atl.jboss.com>

I'm currently using JBoss with Apache Axis.

However, I recently became aware of JBossWS.

Which one is better ??

I want to see a list of pros and cons of each.

Thank you.

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

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


From do-not-reply at jboss.com  Tue Aug 26 08:54:14 2008
From: do-not-reply at jboss.com (rishabh2u)
Date: Tue, 26 Aug 2008 08:54:14 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Cannot find endpoint meta data with
	super-simple WS
Message-ID: <12475083.1219755254460.JavaMail.jboss@colo-br-02.atl.jboss.com>


Yeah this is still a problem in in jboss  4.2.3 GA. and 2.0.4 GA. and Java 5.
On some forums there are workarounds to this problem by isolating some jars etc. I am working on a solution and willl update this post soon.

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

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


From do-not-reply at jboss.com  Tue Aug 26 12:07:45 2008
From: do-not-reply at jboss.com (gryffin)
Date: Tue, 26 Aug 2008 12:07:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: IllegalStateException Cannot find
	property
Message-ID: <28641459.1219766865930.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thanks PeterJ for your suggestion.

I went ahead and tried again from a 'space-less' directory path and ensured that I was using Java 1.5.x. No improvment.

C:\MV4Client2\bin>\jboss-4.2.3.ga\bin\wsrunclient com.boeing.nmt.nls.test.AssetTest
log4j:WARN No appenders could be found for logger (org.jboss.ws.metadata.builder.jaxws.JAXWSWebServi
ceMetaDataBuilder).
log4j:WARN Please initialize the log4j system properly.
        ====================================
DISABLE TAG: FFF123456789
Tag deleted: false
Exception in thread "main" javax.xml.ws.WebServiceException: java.lang.IllegalStateException: Cannot
 find property: javax.xml.ws.handler.message.outbound
        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 $Proxy19.update(Unknown Source)
        at com.boeing.nmt.nls.mv4client.MV4Client.disableTag(MV4Client.java:308)
        at com.boeing.nmt.nls.test.AssetTest.main(AssetTest.java:25)
Caused by: java.lang.IllegalStateException: Cannot find property: javax.xml.ws.handler.message.outbo
und
        at org.jboss.ws.core.jaxws.handler.MessageContextJAXWS.processPivot(MessageContextJAXWS.java
:109)
        at org.jboss.ws.core.jaxws.client.ClientImpl.processPivot(ClientImpl.java:363)
        at org.jboss.ws.core.CommonClient.processPivotInternal(CommonClient.java:476)
        at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:404)
        at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
        ... 5 more
C:\MV4Client2\bin>echo %JAVA_HOME%
C:\Program Files\Java\jdk1.5.0_15

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

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


From do-not-reply at jboss.com  Tue Aug 26 12:48:49 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 26 Aug 2008 12:48:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: IllegalStateException Cannot find
	property
Message-ID: <30339345.1219769329411.JavaMail.jboss@colo-br-02.atl.jboss.com>

It might not be an improvement, but at least it is different - the error message has changed! I don't recognize this error - I will have to do some research.

Did you regenerate the client stubs using the JBossAS 4.2.3 libraries/tools and JDK 1.5?

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

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


From do-not-reply at jboss.com  Tue Aug 26 13:02:27 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 26 Aug 2008 13:02:27 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: IllegalStateException Cannot find
	property
Message-ID: <23841141.1219770147507.JavaMail.jboss@colo-br-02.atl.jboss.com>

OK, just read the first post, and it looks like you are back to the error message in that post.

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

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


From do-not-reply at jboss.com  Tue Aug 26 13:24:29 2008
From: do-not-reply at jboss.com (jrinderle)
Date: Tue, 26 Aug 2008 13:24:29 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - RESTeasy and X-HTTP-Method-Override
Message-ID: <13701620.1219771469897.JavaMail.jboss@colo-br-02.atl.jboss.com>

Are there any plans to support the X-HTTP-Method-Override request header (automatically/transparently) in RESTeasy? (Forgive me if this is already a feature -- I searched the forums and wiki and did not find anything.) This would make it much easier to support clients that cannot send PUT/DELETE requests. Yes, overriding POST is less than ideal but I think the Google convention of using X-HTTP-Method-Override is a reasonable/convenient work-around. If RESTeasy could dispatch POST requests with the X-HTTP-Method-Override header automatically it would be a big time saver. I think Jersey just added something like this via a filtering approach, but I'd prefer to stick with RESTeasy.

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

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


From do-not-reply at jboss.com  Tue Aug 26 13:29:39 2008
From: do-not-reply at jboss.com (gryffin)
Date: Tue, 26 Aug 2008 13:29:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: IllegalStateException Cannot find
	property
Message-ID: <25336227.1219771779188.JavaMail.jboss@colo-br-02.atl.jboss.com>

Here's the output with more detail about the run environment:

C:\MV4Client2\bin>\jboss-4.2.3.ga\bin\wsrunclient com.boeing.nmt.nls.test.AssetTest
  |                                                                   .
  | Java directory: "C:\Program Files\Java\jdk1.5.0_15\bin\java"
  |                                                                        .
  | Java version:
  | java version "1.5.0_15"
  | Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_15-b04)
  | Java HotSpot(TM) Client VM (build 1.5.0_15-b04, mixed mode, sharing)
  |                                                                   .
  | Execution directory: C:\MV4Client2\bin\
  |                                                                   .
  | log4j:WARN No appenders could be found for logger (org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder).
  | log4j:WARN Please initialize the log4j system properly.
  |         ====================================
  | DISABLE TAG: FFF123456789
  | Tag deleted: false
  | Exception in thread "main" javax.xml.ws.WebServiceException: java.lang.IllegalStateException: Cannot find property: javax.xml.ws.handler.message.outbound

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

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


From do-not-reply at jboss.com  Tue Aug 26 13:41:27 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 26 Aug 2008 13:41:27 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: IllegalStateException Cannot find
	property
Message-ID: <14895610.1219772487591.JavaMail.jboss@colo-br-02.atl.jboss.com>

I looked at the source code.

The 'outbound' property is set to false when the client sends a request to JBossAS and to true when JBossAS responds back. The exception means that property has not been set.

Earlier in the stack trace, in CommonClient.invoke, line 404, we find that someone commited the cardinal sin of exception handling - they dropped the exception on the floor not even bothering to log it. Instead, they called processPivotInternal which eventually threw the exception that you saw.

So that is why the exception makes no sense - the real cause for the problem was thrown away.

Unfortunately, unless someone else has any ideas, the only thing I can think of is for you to patch CommonClient.invoke and log the exception so that you can discover the root cause.

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

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


From do-not-reply at jboss.com  Tue Aug 26 13:52:19 2008
From: do-not-reply at jboss.com (gryffin)
Date: Tue, 26 Aug 2008 13:52:19 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: IllegalStateException Cannot find
	property
Message-ID: <21138680.1219773139744.JavaMail.jboss@colo-br-02.atl.jboss.com>

Okay, PeterJ. That helps define the problem. I'd understood that the property wasn't being set, but I hadn't found my way far enough upstream in the source to find the headwaters, so to speak, in CommonClient. 

I'll look into tweaking the class and see what I get. Thanks!

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

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


From do-not-reply at jboss.com  Tue Aug 26 16:24:10 2008
From: do-not-reply at jboss.com (bkyle)
Date: Tue, 26 Aug 2008 16:24:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - ant tests errors: NoClassDefFoundError:
	org/jboss/wsf/test/G
Message-ID: <26435232.1219782250493.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I'm new to web services on JBoss.  I'm trying to debug my installation of JBossWS native 3.0.2 on JBossAS 4.2.1

When I try to run the tests that come in the jbossws-native-dist\tests directory, I get this error:
NoClassDefFoundError: org/jboss/wsf/test/GenericSOAPHandler

I put the console output below from both the client side (where the ant tests are running) and from the server side (where JBossAS is running).

Any ideas what the problem is?  I would really appreciate the help.

-Brent.


****************** CLIENT ANT TESTS SIDE *****************
tests-run-internal:
    [junit] WARNING: multiple versions of ant detected in path for junit
    [junit]          jar:file:/C:/java/apache-ant-1.7.1/lib/ant.jar!/org/apache/tools/ant/Project.class
    [junit]      and jar:file:/C:/java/jbossws-native-dist/deploy/lib/ant.jar!/org/apache/tools/ant/Project.class
    [junit] Running org.jboss.test.ws.console.ConsoleAccessTestCase
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.062 sec
    [junit] Running org.jboss.test.ws.jaxws.samples.advanced.retail.RetailSampleTestCase
    [junit] javax.management.MBeanException
    [junit]     at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:180)

    [junit]     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:163)
    [junit]     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    [junit]     at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
    [junit]     at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    [junit]     at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:14
2)
    [junit]     at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    [junit]     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    [junit]     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [junit]     at java.lang.reflect.Method.invoke(Method.java:585)
    [junit]     at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266)
    [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [junit]     at java.lang.reflect.Method.invoke(Method.java:585)
    [junit]     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    [junit]     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    [junit]     at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
    [junit]     at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    [junit]     at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:14
2)
    [junit]     at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74)
    [junit]     at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    [junit]     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    [junit]     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    [junit]     at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
    [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [junit]     at java.lang.reflect.Method.invoke(Method.java:585)
    [junit]     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    [junit]     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    [junit]     at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    [junit]     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    [junit]     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    [junit]     at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:818)
    [junit]     at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:419)
    [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [junit]     at java.lang.reflect.Method.invoke(Method.java:585)
    [junit]     at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
    [junit]     at sun.rmi.transport.Transport$1.run(Transport.java:153)
    [junit]     at java.security.AccessController.doPrivileged(Native Method)
    [junit]     at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
    [junit]     at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
    [junit]     at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
    [junit]     at java.lang.Thread.run(Thread.java:595)
    [junit] Caused by: org.jboss.deployment.DeploymentException: Could not create deployment: file:/C:/java/jbossws-nati
ve-dist/output/test-libs/jaxws-samples-retail.jar; - nested throwable: (java.lang.NoClassDefFoundError: org/jboss/wsf/te
st/GenericSOAPHandler)
    [junit]     at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
    [junit]     at org.jboss.deployment.MainDeployer.create(MainDeployer.java:991)
    [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
    [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
    [junit]     at sun.reflect.GeneratedMethodAccessor23.invoke(Unknown Source)
    [junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [junit]     at java.lang.reflect.Method.invoke(Method.java:585)
    [junit]     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    [junit]     ... 48 more
    [junit] Caused by: java.lang.NoClassDefFoundError: org/jboss/wsf/test/GenericSOAPHandler
    [junit]     at java.lang.ClassLoader.defineClass1(Native Method)
    [junit]     at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
    [junit]     at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
    [junit]     at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
    [junit]     at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
    [junit]     at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
    [junit]     at java.security.AccessController.doPrivileged(Native Method)
    [junit]     at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    [junit]     at org.jboss.mx.loading.RepositoryClassLoader.findClassLocally(RepositoryClassLoader.java:675)
    [junit]     at org.jboss.mx.loading.RepositoryClassLoader.findClass(RepositoryClassLoader.java:655)
    [junit]     at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
    [junit]     at org.jboss.mx.loading.RepositoryClassLoader.loadClassLocally(RepositoryClassLoader.java:193)
    [junit]     at org.jboss.mx.loading.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:131)
    [junit]     at org.jboss.mx.loading.LoadMgr3.nextTask(LoadMgr3.java:399)
    [junit]     at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:520)
    [junit]     at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:408)
    [junit]     at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
    [junit]     at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
    [junit]     at org.jboss.ws.metadata.umdm.HandlerMetaData.getHandlerClass(HandlerMetaData.java:115)
    [junit]     at org.jboss.ws.metadata.umdm.HandlerMetaDataJAXWS.toString(HandlerMetaDataJAXWS.java:86)
    [junit]     at java.lang.String.valueOf(String.java:2615)
    [junit]     at java.lang.StringBuilder.append(StringBuilder.java:116)
    [junit]     at org.jboss.ws.metadata.umdm.ServerEndpointMetaData.toString(ServerEndpointMetaData.java:214)
    [junit]     at java.lang.String.valueOf(String.java:2615)
    [junit]     at java.lang.StringBuilder.append(StringBuilder.java:116)
    [junit]     at org.jboss.ws.metadata.umdm.ServiceMetaData.toString(ServiceMetaData.java:458)
    [junit]     at java.lang.String.valueOf(String.java:2615)
    [junit]     at java.lang.StringBuilder.append(StringBuilder.java:116)
    [junit]     at org.jboss.ws.metadata.umdm.UnifiedMetaData.toString(UnifiedMetaData.java:227)
    [junit]     at java.lang.String.valueOf(String.java:2615)
    [junit]     at java.lang.StringBuilder.append(StringBuilder.java:116)
    [junit]     at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderEJB3.buildMetaData(JAXWSMetaDataBuilderEJB3.j
ava:93)
    [junit]     at org.jboss.ws.core.server.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:92)
    [junit]     at org.jboss.ws.integration.jboss42.DeployerInterceptor.createServiceEndpoint(DeployerInterceptor.java:1
27)
    [junit]     at org.jboss.ws.integration.jboss42.DeployerInterceptorEJB.createServiceEndpoint(DeployerInterceptorEJB.
java:43)
    [junit]     at org.jboss.ws.integration.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:78)
    [junit]     at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSup
port.java:180)
    [junit]     at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
    [junit]     at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    [junit]     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    [junit]     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    [junit]     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    [junit]     at $Proxy34.create(Unknown Source)
    [junit]     at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
    [junit]     ... 54 more
    [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 3.656 sec


****************** SERVER SIDE ********************
12:52:06,538 INFO  [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
12:52:06,616 INFO  [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
12:52:06,663 INFO  [Server] JBoss (MX MicroKernel) [4.2.1.GA (build: SVNTag=JBoss_4_2_1_GA date=200707131605)] Started i
n 29s:266ms
12:53:00,960 ERROR [MainDeployer] Could not create deployment: file:/C:/java/jbossws-native-dist/output/test-libs/jaxws-
samples-retail.jar
java.lang.NoClassDefFoundError: org/jboss/wsf/test/GenericSOAPHandler
        at java.lang.ClassLoader.defineClass1(Native Method)
        at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
        at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
        at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
        at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
        at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
        at org.jboss.mx.loading.RepositoryClassLoader.findClassLocally(RepositoryClassLoader.java:675)
        at org.jboss.mx.loading.RepositoryClassLoader.findClass(RepositoryClassLoader.java:655)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        at org.jboss.mx.loading.RepositoryClassLoader.loadClassLocally(RepositoryClassLoader.java:193)
        at org.jboss.mx.loading.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:131)
        at org.jboss.mx.loading.LoadMgr3.nextTask(LoadMgr3.java:399)
        at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:520)
        at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:408)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        at org.jboss.ws.metadata.umdm.HandlerMetaData.getHandlerClass(HandlerMetaData.java:115)
        at org.jboss.ws.metadata.umdm.HandlerMetaDataJAXWS.toString(HandlerMetaDataJAXWS.java:86)
        at java.lang.String.valueOf(String.java:2615)
        at java.lang.StringBuilder.append(StringBuilder.java:116)
        at org.jboss.ws.metadata.umdm.ServerEndpointMetaData.toString(ServerEndpointMetaData.java:214)
        at java.lang.String.valueOf(String.java:2615)
        at java.lang.StringBuilder.append(StringBuilder.java:116)
        at org.jboss.ws.metadata.umdm.ServiceMetaData.toString(ServiceMetaData.java:458)
        at java.lang.String.valueOf(String.java:2615)
        at java.lang.StringBuilder.append(StringBuilder.java:116)
        at org.jboss.ws.metadata.umdm.UnifiedMetaData.toString(UnifiedMetaData.java:227)
        at java.lang.String.valueOf(String.java:2615)
        at java.lang.StringBuilder.append(StringBuilder.java:116)
        at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderEJB3.buildMetaData(JAXWSMetaDataBuilderEJB3.java:93)
        at org.jboss.ws.core.server.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:92)
        at org.jboss.ws.integration.jboss42.DeployerInterceptor.createServiceEndpoint(DeployerInterceptor.java:127)
        at org.jboss.ws.integration.jboss42.DeployerInterceptorEJB.createServiceEndpoint(DeployerInterceptorEJB.java:43)

        at org.jboss.ws.integration.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:78)
        at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.jav
a:180)
        at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy34.create(Unknown Source)
        at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
        at sun.reflect.GeneratedMethodAccessor23.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 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.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
        at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74)
        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.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
        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.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.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:818)
        at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:419)
        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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
        at sun.rmi.transport.Transport$1.run(Transport.java:153)
        at java.security.AccessController.doPrivileged(Native Method)
        at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
        at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
        at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
        at java.lang.Thread.run(Thread.java:595)
12:53:01,382 ERROR [ServiceEndpointPublisher] Cannot obtain waURL for: jaxws-samples-retail.jar
12:53:02,866 INFO  [TomcatDeployer] deploy, ctxPath=/jaxws-samples-asynchronous, warUrl=.../tmp/deploy/tmp3562jaxws-samp
les-asynchronous-exp.war/

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

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


From do-not-reply at jboss.com  Wed Aug 27 05:05:56 2008
From: do-not-reply at jboss.com (saravanan_kri)
Date: Wed, 27 Aug 2008 05:05:56 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Non-java webservices in JBOSS
Message-ID: <4446287.1219827956522.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I am new to JBOSS and web service. I would like to know whether we can host a non-java web service (especially C and C++) in JBOSS. Please help...

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

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


From do-not-reply at jboss.com  Wed Aug 27 19:00:57 2008
From: do-not-reply at jboss.com (yi_zhang)
Date: Wed, 27 Aug 2008 19:00:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Is there a wsconsume equivalent to
	wsdl2Java's namespace
Message-ID: <28236415.1219878057683.JavaMail.jboss@colo-br-02.atl.jboss.com>


This solution worked for me:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118735#4118735


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

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


From do-not-reply at jboss.com  Wed Aug 27 20:36:04 2008
From: do-not-reply at jboss.com (kerryrward)
Date: Wed, 27 Aug 2008 20:36:04 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Native WS-Reliable Messaging Error -
	The RM Destination requ
Message-ID: <19223742.1219883764398.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am trying to implement a web service that does both MTOM-XOP and reliable messaging.  I have the service running with MTOM-XOP and patterned it after the MTOMEndPoint EJB3 example provided in the jboss native ws 3.0.2.  I am running JBoss 4.2.2.  

I then tried to implement the steps from the Reliable Messaging Tutorial at 
http://jbws.dyndns.org/mediawiki/index.php?title=Native_WS-ReliableMessaging_Tutorial


I had problems with the wsdl I modified, so I added the following annotations to the endpoint and let JBOSS build the wsdl instead

@WebService(
  | 		name = "EflexServiceEndpoint", 
  | 		serviceName = "EflexService", 
  | 		endpointInterface = "com.eflex.webservice.EflexServiceEndpoint"
  | //		wsdlLocation = "WEB-INF/wsdl/EflexService.wsdl"
  | )
  | @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
  | @BindingType(value = "http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true")
  | @EndpointConfig
  | (
  |    configFile = "META-INF/wsrm-jaxws-endpoint-config.xml",
  |    configName = "Standard WSRM Endpoint"
  | )
  | @PolicyAttachment(@Policy(
  |         policyFileLocation = "META-INF/wsrm-exactly-once-in-order-policy.xml",
  |         scope = PolicyScopeLevel.WSDL_BINDING)
  | )
  | 
  | public class EflexServiceEndpointBean implements EflexServiceEndpoint
  | {
  | 
  | 

Here is the exception I get:

anonymous wrote : org.jboss.ws.extensions.wsrm.RMFault: The RM Destination requires the use of WSRM
  |         at org.jboss.ws.extensions.wsrm.server.RMInvocationHandler.prepareResponseContext(RMInvocationHandler.java:134)
  |         at org.jboss.ws.extensions.wsrm.server.RMInvocationHandler.invoke(RMInvocationHandler.java:306)
  |         at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:221)
  |         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:466)
  |         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)
  | 

Which seems to say that my service is expecting WSRM, but that the client has not implemented it.

Here is my client code.


  |  public final class EflexServiceClient
  | {
  | 
  |    private static final String serviceURL = "http://localhost:80/wseflex/EflexService";
  |    
  |    public static void main(String[] args) throws Exception
  |    {
  | 	   InputStream is = null;
  | 	   if (args.length != 0)
  | 	   {
  | 		   is = new FileInputStream(args[0]);
  | 	   } else {
  | 		   is = new ByteArrayInputStream("<test>reqest</test>".getBytes());
  | 	   }
  | 	   
  |       QName serviceName = new QName("http://webservice.eflex.com/", "EflexService");
  |       URL wsdlURL = new URL(serviceURL + "?wsdl");
  |       Service service = Service.create(wsdlURL, serviceName);
  |       EflexServiceEndpoint port = (EflexServiceEndpoint)service.getPort(EflexServiceEndpoint.class);
  |       SOAPBinding binding = (SOAPBinding)((BindingProvider)port).getBinding();
  |       binding.setMTOMEnabled(true);
  |       ((StubExt)port).setConfigName("Standard Anonymous WSRM Client", "META-INF/wsrm-jaxws-client-config.xml");
  |       
  |       Source src = new StreamSource(is);
  |       SourceRequest request = new SourceRequest();
  |       request.setData(src);
  | 
  |       SourceResponse response = port.echoSource(request);
  |       Source respSource = response.getData();
  | 
  |       ((RMProvider)port).closeSequence();
  | ...
  | 
  | 

Any help on this is greatly appreciated.  Thanks.

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

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


From do-not-reply at jboss.com  Thu Aug 28 06:38:23 2008
From: do-not-reply at jboss.com (navinbhat)
Date: Thu, 28 Aug 2008 06:38:23 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Interoperability issue between JBoss
	service and gSOAP clien
Message-ID: <27921331.1219919903528.JavaMail.jboss@colo-br-02.atl.jboss.com>

Environment:
          JBOSS AS 4.2.3,JBoss-native-3.0.3,JDK 5 update 15,Windows XP SP2,Eclipse 3.3.x.

Description:
         I generated service code from wsdl using wsconsume (contract first  approach). I wrote the service skeleton code as a stateless EJB, where in i have a operation which recieves and sends back an MTOM attachment. I have enabled MTOM using the following annotation.
@BindingType(value="http://www.w3.org/2003/05/soap/bindings/HTTP/?mtom=true").I deployed the service in JBoss Application server 4.2.3.

The SOAP 1.2 client is written in gSOAP framework (Running on linux) generated from the same wsdl file.When the gSOAP client sends an MTOM attachment the JBoss service throws an exception, the stack trace is shown below.

NOTE: The same JBoss service works fine with JBoss client.

Stack trace
12:11:27,705 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
javax.xml.soap.SOAPException: Cannot decode multipart related message
	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:253)
	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:193)
	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:457)
	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295)
	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205)
	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
	at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:81)
	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:182)
	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)
Caused by: javax.mail.internet.ParseException: Expected ';', got "/"
	at javax.mail.internet.ParameterList.(ParameterList.java:179)
	at javax.mail.internet.ContentType.(ContentType.java:100)
	at org.jboss.ws.core.soap.attachment.MultipartRelatedDecoder.isValidRootType(MultipartRelatedDecoder.java:80)
	at org.jboss.ws.core.soap.attachment.MultipartRelatedDecoder.decodeMultipartRelatedMessage(MultipartRelatedDecoder.java:160)
	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:241)
	... 25 more

Let me know if more detail is required,

Thanks in advance,
Navin Bhat


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

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


From do-not-reply at jboss.com  Thu Aug 28 08:03:01 2008
From: do-not-reply at jboss.com (confused)
Date: Thu, 28 Aug 2008 08:03:01 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - cxf does not work with JBOSS 4.2.3 ??
Message-ID: <17682258.1219924981304.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,
you are my big hope ;-).  I built some WS with cxf and tried to run they with JBOSS 4.2.3. When th ws try to get a connection follow exception  will throwed: "java.lang.ClassCastException: org.apache.cxf.jaxws.ServiceImpl cannot be cast to javax.xml.ws.spi.ServiceDelegate21"

Any Ideas?

PS: CXF knows javax.xml.ws.spi.ServiceDelegate an no ServiceDelegate21

Thanks!

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

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


From do-not-reply at jboss.com  Thu Aug 28 08:09:45 2008
From: do-not-reply at jboss.com (confused)
Date: Thu, 28 Aug 2008 08:09:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: cxf does not work with JBOSS 4.2.3
	??
Message-ID: <17622767.1219925386125.JavaMail.jboss@colo-br-02.atl.jboss.com>

CXF-version was 2.1.2

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

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


From do-not-reply at jboss.com  Thu Aug 28 11:33:29 2008
From: do-not-reply at jboss.com (riveradon)
Date: Thu, 28 Aug 2008 11:33:29 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Issues with WS-Eventing and JBoss-4.2.3
Message-ID: <5582104.1219937609855.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hey all,

I am having issues running under JBoss-4.2.3 with regards to WS-Eventing. The same code and configuration worked between JBoss-4.2.1 and JBoss-4.2.2. Now I am hitting a snag trying to execute the same code either standalone or within the JBoss environment.  Listed below is the stack trace. 


  | javax.xml.ws.WebServiceException: java.io.IOException: Could not transmit message
  | 	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 $Proxy13.registerService(Unknown Source)
  | 	at com.issinc.atd.situationadvisory.eventing.Test.registerService(Test.java:102)
  | 	at com.issinc.atd.situationadvisory.eventing.Test.main(Test.java:120)
  | 	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 com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)
  | Caused by: java.io.IOException: Could not transmit message
  | 	at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:255)
  | 	at org.jboss.ws.core.client.SOAPProtocolConnectionHTTP.invoke(SOAPProtocolConnectionHTTP.java:73)
  | 	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:339)
  | 	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
  | 	... 10 more
  | Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker. Connection refused: connect.
  | 	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:348)
  | 	at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:137)
  | 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
  | 	at org.jboss.remoting.Client.invoke(Client.java:1634)
  | 	at org.jboss.remoting.Client.invoke(Client.java:548)
  | 	at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:233)
  | 	... 13 more
  | Caused by: 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:195)
  | 	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
  | 	at java.net.Socket.connect(Socket.java:520)
  | 	at sun.net.NetworkClient.doConnect(NetworkClient.java:152)
  | 	at sun.net.www.http.HttpClient.openServer(HttpClient.java:388)
  | 	at sun.net.www.http.HttpClient.openServer(HttpClient.java:523)
  | 	at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
  | 	at sun.net.www.http.HttpClient.New(HttpClient.java:304)
  | 	at sun.net.www.http.HttpClient.New(HttpClient.java:321)
  | 	at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:813)
  | 	at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:765)
  | 	at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:690)
  | 	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:857)
  | 	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:277)
  | 	... 18 more
  | 

Any ideas on what the cause for the above exception would be greatly appreciated.   

Thanks!


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

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


From do-not-reply at jboss.com  Thu Aug 28 14:46:51 2008
From: do-not-reply at jboss.com (simmonsatbhm)
Date: Thu, 28 Aug 2008 14:46:51 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: NullPointerException from
	JBossXSEntityResolver
Message-ID: <11092405.1219949211337.JavaMail.jboss@colo-br-02.atl.jboss.com>

I'm encountering this same problem. Has a fix been made or a different version of jboss-ws available to correct this problem?

Or is martinschweigert's solution the only working solution?

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

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


From do-not-reply at jboss.com  Thu Aug 28 21:34:05 2008
From: do-not-reply at jboss.com (rishabh2u)
Date: Thu, 28 Aug 2008 21:34:05 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Cannot find endpoint meta data with
	super-simple WS
Message-ID: <5460556.1219973645055.JavaMail.jboss@colo-br-02.atl.jboss.com>

ok... this problem seems to be not a problem :-0
Can you make sure that your  war does not contain the javax.jws contating jar in it. If you use the Banana example from jimpo then you should not have any jars in your war as all. It shoud have only 3 files, web.xml,Banana.class and the manifest file.
This totally worked for me on jboss 4.2.3 GA., JBoss 2.0.4 GA. and Java 5.


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

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


From do-not-reply at jboss.com  Fri Aug 29 06:45:33 2008
From: do-not-reply at jboss.com (jimpo)
Date: Fri, 29 Aug 2008 06:45:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Getting handle of the original XML
	message in JAX-WS
Message-ID: <4821284.1220006733324.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am using JAX-WS to implement my web services. I start with a WSDL and then create the stubs and data objects using jbossws 2.0's wscompile tool. I have bunch of service operations A,B, and C that work like this, 'normally'.

Now I would like to have a different kind of operation D which takes two parameter's D1 and D2. I want to have D1 mapped into a Java object like wsconsume -generated classes do. But, D2 should map into a String containing the xml representation of the parameter.

How can I do this with JAX-WS and jbossws?

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

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


From do-not-reply at jboss.com  Fri Aug 29 07:03:35 2008
From: do-not-reply at jboss.com (jimpo)
Date: Fri, 29 Aug 2008 07:03:35 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Getting handle of the original XML
	message in JAX-WS
Message-ID: <16614652.1220007815065.JavaMail.jboss@colo-br-02.atl.jboss.com>

As an example, web service request that contains

  | <vac:archiveDecision>
  |  <vac:employeeNumber>123</vac:employeeNumber>
  |  <vac:decision>
  |   <foo>
  |    dsadsa
  |   </foo>
  |   <bar>
  |    <baz>asdasd</baz>
  |    <baz2>asdasd</baz2>
  |   </bar>
  |  </vac:decision>
  | </vac:archiveDecision>

Should be mapped into Java object

class Some {
  | int employeeNumber;
  | String decision
  | }

with values employeeNumber = 123, 
  | decision = "<vac:decision><foo>dsadsa</foo><bar><baz>asdasd</baz><baz2>asdasd</baz2></bar></vac:decision>"

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

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


From do-not-reply at jboss.com  Fri Aug 29 07:53:34 2008
From: do-not-reply at jboss.com (jimpo)
Date: Fri, 29 Aug 2008 07:53:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Getting handle of the original XML
	message in JAX-WS
Message-ID: <12649678.1220010814586.JavaMail.jboss@colo-br-02.atl.jboss.com>

guess I should give wscompile a JAXB binding xml that defines this kind of mapping.

I can't figure out how to construct this binding.xml. How do I define a mapping which maps ComplexType 'archiveDecisionType's element 'decision' into a String containing the element's xml? Any examples?

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

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


From do-not-reply at jboss.com  Fri Aug 29 10:20:09 2008
From: do-not-reply at jboss.com (riveradon)
Date: Fri, 29 Aug 2008 10:20:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Issues with WS-Eventing and
	JBoss-4.2.3
Message-ID: <13998126.1220019609145.JavaMail.jboss@colo-br-02.atl.jboss.com>

The following is an example of the code I am trying to execute using the JBoss-4.2.3 libraries. This is a simple main program and interface: 

Client 


  | public class Test {
  | 
  |     private static Logger mLogger = Logger.getLogger(Test.class);
  | 
  |     public void registerService() {
  |         final String METHOD_NAME = "registerService";
  |         mLogger.debug(METHOD_NAME + " - ENTRY");
  |         boolean result = false;
  |         try {
  |             // Running the getCurrent function
  |             Service service = Service.create(
  |                     new URL("http://ssdr_server:8080/ssdi-ssdr/ssdi-ssdr?wsdl"),
  |                     new QName("http://ssdr.webservices.com/", "SsdrRegistryService"));
  |             ISsdr servicePort = service.getPort(ISsdr.class);
  | 
  |             String registerRDF = "payload";
  | 
  |             // Registering the ssdr via the SSDR Web Service
  |             result = servicePort.registerService(registerRDF);
  |             mLogger.info("Register results are:" + result);
  | 
  |         } catch (Exception e) {
  |             mLogger.error(METHOD_NAME + " : Exception: ", e);
  |         }
  |         mLogger.debug(METHOD_NAME + " - EXIT");
  |     }
  | 
  |     public static void main(String[] args) {
  |         Test test = new Test();
  |         test.registerService();
  |     }
  | }
  | 


Interface 


  | @WebService
  | @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL,
  | 		     parameterStyle = SOAPBinding.ParameterStyle.WRAPPED)
  | public interface ISsdr {
  | @WebMethod
  | 	public boolean registerService(@WebParam(name = "serviceRDF") String serviceRDF);
  | 
  | 	@WebMethod
  | 	public boolean unregisterService(@WebParam(name = "serviceRDF") String serviceRDF);
  | 
  | 	@WebMethod
  | 	public ArrayList<String> serviceLookup(@WebParam(name="serviceRequestRDF")
  | 			String serviceRequestRDF);
  | }
  | 

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

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


From do-not-reply at jboss.com  Fri Aug 29 17:06:14 2008
From: do-not-reply at jboss.com (SagarD)
Date: Fri, 29 Aug 2008 17:06:14 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Problem Deploying StatelessSessionBean
	as JAX Websrvice on J
Message-ID: <9322112.1220043974676.JavaMail.jboss@colo-br-02.atl.jboss.com>


> Hi  All,
>
> I am deployed an  stateless session bean as JAX webservice on JBOSS 
> 4.2.2GA and when trying to invoke the Web service through  client 
> Application.
>
> Please try to give some pointers on the error below
>
> 21:12:22,250 INFO  [JmxKernelAbstraction] creating wrapper delegate
> for: org.jboss.ejb3.stateless.StatelessContainer
> 21:12:22,250 INFO  [JmxKernelAbstraction] installing MBean:
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewWebService,service
> =EJB3
> with dependencies:
> 21:12:22,500 INFO  [JmxKernelAbstraction]
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewSessionBean,servic
> e=EJB3 21:12:22,500 INFO  [EJBContainer] STARTED EJB:
> org.mdacc.hp.ris.NewWebService ejbName: NewWebService
> 21:12:22,515 INFO  [EJB3Deployer] Deployed:
> _file:/C:/jboss-4.2.2.GA/server/default/deploy/TestJBoss_EJBWSHibernat
> e.jar_
> 21:12:22,515 INFO  [DefaultEndpointRegistry] register:
> jboss.ws:context=TestJBoss_EJBWSHibernate,endpoint=NewWebService
> 21:12:22,562 INFO  [TomcatDeployer] deploy, 
> ctxPath=/TestJBoss_EJBWSHibernate,
> warUrl=.../tmp/deploy/TestJBoss_EJBWSHibernate.jar1035.war/
> 21:12:23,015 INFO  [WSDLFilePublisher] WSDL published to:
> _file:/C:/jboss-4.2.2.GA/server/default/data/wsdl/TestJBoss_EJBWSHiber
> nate.jar/NewWebServiceService1036.wsdl_
> 21:20:45,468 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
> java.lang.ClassCastException:
> com.sun.xml.messaging.saaj.soap.ver1_1.Envelope1_1Impl
>         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:399)
>         at
> org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:274)
>         at
> org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:191)
>         at
> org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:124)
>         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)
> 21:20:45,734 ERROR [RequestHandlerImpl] Error processing web service 
> request
> org.jboss.ws.WSException: java.lang.ClassCastException:
> com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl
>         at org.jboss.ws.WSException.rethrow(WSException.java:68)
>         at
> org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:315)
>         at
> org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:191)
>         at
> org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:124)
>         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(Appli
> cationFilterChain.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)
> Caused by: java.lang.ClassCastException:
> com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl
>         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:440)
>         at
> org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:274)
>         ... 22 more
> 21:20:46,218 ERROR [[NewWebService]] Servlet.service() for servlet 
> NewWebService threw exception
> java.lang.ClassCastException:
> com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl
>         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:440)
>         at
> org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:274)
>         at
> org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:191)
>         at
> org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:124)
>         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.proces
> s(Http11Protocol.java:583)
>
>         at
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
>         at java.lang.Thread.run(Thread.java:595)
> 22:46:49,234 INFO  [EJBContainer] STOPPED EJB:
> org.mdacc.hp.ris.NewWebService ejbName: NewWebService
> 22:46:49,234 INFO  [EJBContainer] STOPPED EJB:
> org.mdacc.hp.ris.NewSessionBean ejbName: NewSessionBean
> 22:46:49,234 WARN  [JmxKernelAbstraction]
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewSessionBean,servic
> e=EJB3
> is not registered
> 22:46:49,234 WARN  [JmxKernelAbstraction]
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewWebService,service
> =EJB3
> is not registered
> 22:46:49,234 INFO  [TomcatDeployer] undeploy, 
> ctxPath=/TestJBoss_EJBWSHibernate,
> warUrl=.../tmp/deploy/TestJBoss_EJBWSHibernate.jar1035.war/
> 22:46:49,359 INFO  [DefaultEndpointRegistry] remove:
> jboss.ws:context=TestJBoss_EJBWSHibernate,endpoint=NewWebService
> 22:47:45,968 INFO  [JmxKernelAbstraction] creating wrapper delegate
> for: org.jboss.ejb3.stateless.StatelessContainer
> 22:47:45,968 INFO  [JmxKernelAbstraction] installing MBean:
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewSessionBean,servic
> e=EJB3
> with dependencies:
> 22:47:45,984 INFO  [EJBContainer] STARTED EJB:
> org.mdacc.hp.ris.NewSessionBean ejbName: NewSessionBean
> 22:47:46,015 INFO  [JmxKernelAbstraction] creating wrapper delegate
> for: org.jboss.ejb3.stateless.StatelessContainer
> 22:47:46,015 INFO  [JmxKernelAbstraction] installing MBean:
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewWebService,service
> =EJB3
> with dependencies:
> 22:47:46,250 INFO  [JmxKernelAbstraction]
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewSessionBean,servic
> e=EJB3
> 22:47:46,265 INFO  [EJBContainer] STARTED EJB:
> org.mdacc.hp.ris.NewWebService ejbName: NewWebService
> 22:47:46,265 INFO  [EJB3Deployer] Deployed:
> _file:/C:/jboss-4.2.2.GA/server/default/deploy/TestJBoss_EJBWSHibernat
> e.jar_
> 22:47:46,281 INFO  [DefaultEndpointRegistry] register:
> jboss.ws:context=TestJBoss_EJBWSHibernate,endpoint=NewWebService
> 22:47:46,359 INFO  [TomcatDeployer] deploy, 
> ctxPath=/TestJBoss_EJBWSHibernate,
> warUrl=.../tmp/deploy/TestJBoss_EJBWSHibernate.jar1039.war/
> 22:47:46,890 INFO  [WSDLFilePublisher] WSDL published to:
> _file:/C:/jboss-4.2.2.GA/server/default/data/wsdl/TestJBoss_EJBWSHiber
> nate.jar/NewWebServiceService1040.wsdl_
> 23:04:52,281 INFO  [EJBContainer] STOPPED EJB:
> org.mdacc.hp.ris.NewWebService ejbName: NewWebService
> 23:04:52,296 INFO  [EJBContainer] STOPPED EJB:
> org.mdacc.hp.ris.NewSessionBean ejbName: NewSessionBean
> 23:04:52,296 WARN  [JmxKernelAbstraction]
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewSessionBean,servic
> e=EJB3
> is not registered
> 23:04:52,296 WARN  [JmxKernelAbstraction]
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewWebService,service
> =EJB3
> is not registered
> 23:04:52,296 INFO  [TomcatDeployer] undeploy, 
> ctxPath=/TestJBoss_EJBWSHibernate,
> warUrl=.../tmp/deploy/TestJBoss_EJBWSHibernate.jar1039.war/
> 23:04:52,812 INFO  [DefaultEndpointRegistry] remove:
> jboss.ws:context=TestJBoss_EJBWSHibernate,endpoint=NewWebService
> 23:05:11,515 INFO  [JmxKernelAbstraction] creating wrapper delegate
> for: org.jboss.ejb3.stateless.StatelessContainer
> 23:05:11,515 INFO  [JmxKernelAbstraction] installing MBean:
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewSessionBean,servic
> e=EJB3
> with dependencies:
> 23:05:11,531 INFO  [EJBContainer] STARTED EJB:
> org.mdacc.hp.ris.NewSessionBean ejbName: NewSessionBean
> 23:05:11,546 INFO  [JmxKernelAbstraction] creating wrapper delegate
> for: org.jboss.ejb3.stateless.StatelessContainer
> 23:05:11,546 INFO  [JmxKernelAbstraction] installing MBean:
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewWebService,service
> =EJB3
> with dependencies:
> 23:05:11,781 INFO  [JmxKernelAbstraction]
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewSessionBean,servic
> e=EJB3
> 23:05:11,796 INFO  [EJBContainer] STARTED EJB:
> org.mdacc.hp.ris.NewWebService ejbName: NewWebService
> 23:05:11,796 INFO  [EJB3Deployer] Deployed:
> _file:/C:/jboss-4.2.2.GA/server/default/deploy/TestJBoss_EJBWSHibernat
> e.jar_
> 23:05:11,828 INFO  [DefaultEndpointRegistry] register:
> jboss.ws:context=TestJBoss_EJBWSHibernate,endpoint=NewWebService
> 23:05:11,906 INFO  [TomcatDeployer] deploy, 
> ctxPath=/TestJBoss_EJBWSHibernate,
> warUrl=.../tmp/deploy/TestJBoss_EJBWSHibernate.jar1043.war/
> 23:05:12,375 INFO  [WSDLFilePublisher] WSDL published to:
> _file:/C:/jboss-4.2.2.GA/server/default/data/wsdl/TestJBoss_EJBWSHiber
> nate.jar/NewWebServiceService1044.wsdl_
> 23:23:42,609 INFO  [EJBContainer] STOPPED EJB:
> org.mdacc.hp.ris.NewWebService ejbName: NewWebService
> 23:23:42,609 INFO  [EJBContainer] STOPPED EJB:
> org.mdacc.hp.ris.NewSessionBean ejbName: NewSessionBean
> 23:23:42,609 WARN  [JmxKernelAbstraction]
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewSessionBean,servic
> e=EJB3
> is not registered
> 23:23:42,625 WARN  [JmxKernelAbstraction]
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewWebService,service
> =EJB3
> is not registered
> 23:23:42,625 INFO  [TomcatDeployer] undeploy, 
> ctxPath=/TestJBoss_EJBWSHibernate,
> warUrl=.../tmp/deploy/TestJBoss_EJBWSHibernate.jar1043.war/
> 23:23:43,156 INFO  [DefaultEndpointRegistry] remove:
> jboss.ws:context=TestJBoss_EJBWSHibernate,endpoint=NewWebService
> 23:23:56,203 INFO  [JmxKernelAbstraction] creating wrapper delegate
> for: org.jboss.ejb3.stateless.StatelessContainer
> 23:23:56,203 INFO  [JmxKernelAbstraction] installing MBean:
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewSessionBean,servic
> e=EJB3
> with dependencies:
> 23:23:56,218 INFO  [EJBContainer] STARTED EJB:
> org.mdacc.hp.ris.NewSessionBean ejbName: NewSessionBean
> 23:23:56,234 INFO  [JmxKernelAbstraction] creating wrapper delegate
> for: org.jboss.ejb3.stateless.StatelessContainer
> 23:23:56,234 INFO  [JmxKernelAbstraction] installing MBean:
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewWebService,service
> =EJB3
> with dependencies:
> 23:23:56,671 INFO  [JmxKernelAbstraction]
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewSessionBean,servic
> e=EJB3
> 23:23:56,687 INFO  [EJBContainer] STARTED EJB:
> org.mdacc.hp.ris.NewWebService ejbName: NewWebService
> 23:23:56,687 INFO  [EJB3Deployer] Deployed:
> _file:/C:/jboss-4.2.2.GA/server/default/deploy/TestJBoss_EJBWSHibernat
> e.jar_
> 23:23:56,734 INFO  [DefaultEndpointRegistry] register:
> jboss.ws:context=TestJBoss_EJBWSHibernate,endpoint=NewWebService
> 23:23:56,781 INFO  [TomcatDeployer] deploy, 
> ctxPath=/TestJBoss_EJBWSHibernate,
> warUrl=.../tmp/deploy/TestJBoss_EJBWSHibernate.jar1047.war/
> 23:23:57,093 INFO  [WSDLFilePublisher] WSDL published to:
> _file:/C:/jboss-4.2.2.GA/server/default/data/wsdl/TestJBoss_EJBWSHiber
> nate.jar/NewWebServiceService1048.wsdl_
> 23:40:32,156 INFO  [EJBContainer] STOPPED EJB:
> org.mdacc.hp.ris.NewWebService ejbName: NewWebService
> 23:40:32,156 INFO  [EJBContainer] STOPPED EJB:
> org.mdacc.hp.ris.NewSessionBean ejbName: NewSessionBean
> 23:40:32,156 WARN  [JmxKernelAbstraction]
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewSessionBean,servic
> e=EJB3
> is not registered
> 23:40:32,156 WARN  [JmxKernelAbstraction]
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewWebService,service
> =EJB3
> is not registered
> 23:40:32,156 INFO  [TomcatDeployer] undeploy, 
> ctxPath=/TestJBoss_EJBWSHibernate,
> warUrl=.../tmp/deploy/TestJBoss_EJBWSHibernate.jar1047.war/
> 23:40:32,484 INFO  [DefaultEndpointRegistry] remove:
> jboss.ws:context=TestJBoss_EJBWSHibernate,endpoint=NewWebService
> 23:40:42,000 INFO  [JmxKernelAbstraction] creating wrapper delegate
> for: org.jboss.ejb3.stateless.StatelessContainer
> 23:40:42,000 INFO  [JmxKernelAbstraction] installing MBean:
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewSessionBean,servic
> e=EJB3
> with dependencies:
> 23:40:42,015 INFO  [EJBContainer] STARTED EJB:
> org.mdacc.hp.ris.NewSessionBean ejbName: NewSessionBean
> 23:40:42,031 INFO  [JmxKernelAbstraction] creating wrapper delegate
> for: org.jboss.ejb3.stateless.StatelessContainer
> 23:40:42,031 INFO  [JmxKernelAbstraction] installing MBean:
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewWebService,service
> =EJB3
> with dependencies:
> 23:40:42,468 INFO  [JmxKernelAbstraction]
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewSessionBean,servic
> e=EJB3
> 23:40:42,468 INFO  [EJBContainer] STARTED EJB:
> org.mdacc.hp.ris.NewWebService ejbName: NewWebService
> 23:40:42,484 INFO  [EJB3Deployer] Deployed:
> _file:/C:/jboss-4.2.2.GA/server/default/deploy/TestJBoss_EJBWSHibernat
> e.jar_
> 23:40:42,515 INFO  [DefaultEndpointRegistry] register:
> jboss.ws:context=TestJBoss_EJBWSHibernate,endpoint=NewWebService
> 23:40:42,562 INFO  [TomcatDeployer] deploy, 
> ctxPath=/TestJBoss_EJBWSHibernate,
> warUrl=.../tmp/deploy/TestJBoss_EJBWSHibernate.jar1051.war/
> 23:40:43,171 INFO  [WSDLFilePublisher] WSDL published to:
> _file:/C:/jboss-4.2.2.GA/server/default/data/wsdl/TestJBoss_EJBWSHiber
> nate.jar/NewWebServiceService1052.wsdl_
> 23:55:51,984 INFO  [EJBContainer] STOPPED EJB:
> org.mdacc.hp.ris.NewWebService ejbName: NewWebService
> 23:55:51,984 INFO  [EJBContainer] STOPPED EJB:
> org.mdacc.hp.ris.NewSessionBean ejbName: NewSessionBean
> 23:55:51,984 WARN  [JmxKernelAbstraction]
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewSessionBean,servic
> e=EJB3
> is not registered
> 23:55:51,984 WARN  [JmxKernelAbstraction]
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewWebService,service
> =EJB3
> is not registered
> 23:55:51,984 INFO  [TomcatDeployer] undeploy, 
> ctxPath=/TestJBoss_EJBWSHibernate,
> warUrl=.../tmp/deploy/TestJBoss_EJBWSHibernate.jar1051.war/
> 23:55:52,500 INFO  [DefaultEndpointRegistry] remove:
> jboss.ws:context=TestJBoss_EJBWSHibernate,endpoint=NewWebService
> 23:56:06,562 INFO  [JmxKernelAbstraction] creating wrapper delegate
> for: org.jboss.ejb3.stateless.StatelessContainer
> 23:56:06,562 INFO  [JmxKernelAbstraction] installing MBean:
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewSessionBean,servic
> e=EJB3
> with dependencies:
> 23:56:06,562 INFO  [EJBContainer] STARTED EJB:
> org.mdacc.hp.ris.NewSessionBean ejbName: NewSessionBean
> 23:56:06,578 INFO  [JmxKernelAbstraction] creating wrapper delegate
> for: org.jboss.ejb3.stateless.StatelessContainer
> 23:56:06,578 INFO  [JmxKernelAbstraction] installing MBean:
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewWebService,service
> =EJB3
> with dependencies:
> 23:56:06,781 INFO  [JmxKernelAbstraction]
> jboss.j2ee:jar=TestJBoss_EJBWSHibernate.jar,name=NewSessionBean,servic
> e=EJB3
> 23:56:06,796 INFO  [EJBContainer] STARTED EJB:
> org.mdacc.hp.ris.NewWebService ejbName: NewWebService
> 23:56:06,796 INFO  [EJB3Deployer] Deployed:
> _file:/C:/jboss-4.2.2.GA/server/default/deploy/TestJBoss_EJBWSHibernat
> e.jar_
> 23:56:06,828 INFO  [DefaultEndpointRegistry] register:
> jboss.ws:context=TestJBoss_EJBWSHibernate,endpoint=NewWebService
> 23:56:06,875 INFO  [TomcatDeployer] deploy, 
> ctxPath=/TestJBoss_EJBWSHibernate,
> warUrl=.../tmp/deploy/TestJBoss_EJBWSHibernate.jar1055.war/
> 23:56:07,281 INFO  [WSDLFilePublisher] WSDL published to:
> _file:/C:/jboss-4.2.2.GA/server/default/data/wsdl/TestJBoss_EJBWSHiber
> nate.jar/NewWebServiceService1056.wsdl_
> 00:00:29,515 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
> java.lang.ClassCastException:
> com.sun.xml.messaging.saaj.soap.ver1_1.Envelope1_1Impl
>         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:399)
>         at
> org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:274)
>         at
> org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:191)
>         at
> org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:124)
>         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)
> 00:00:29,687 ERROR [RequestHandlerImpl] Error processing web service 
> request
> org.jboss.ws.WSException: java.lang.ClassCastException:
> com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl
>         at org.jboss.ws.WSException.rethrow(WSException.java:68)
>         at
> org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:315)
>         at
> org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:191)
>         at
> org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:124)
>         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(Appli
> cationFilterChain.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)
> Caused by: java.lang.ClassCastException:
> com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl
>         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:440)
>         at
> org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:274)
>         ... 22 more
> 00:00:30,171 ERROR [[NewWebService]] Servlet.service() for servlet 
> NewWebService threw exception
> java.lang.ClassCastException:
> com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl
>         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:440)
>         at
> org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:274)
>         at
> org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:191)
>         at
> org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:124)
>         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.proces
> s(Http11Protocol.java:583)
>
>         at
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
>         at java.lang.Thread.run(Thread.java:595)
> Thanks & Regards
> Shiva


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

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


From do-not-reply at jboss.com  Sat Aug 30 15:13:51 2008
From: do-not-reply at jboss.com (skajotde)
Date: Sat, 30 Aug 2008 15:13:51 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Confused by JBossWS versioning
Message-ID: <15410414.1220123631207.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi All

I have read FAQ, Release notes, wiki and I'm still confused about visioning JBossWS:

jbossws-native-2.0.3.GA (which comes with JBossAS 4.2.2 GA)
jbossws-3.0.1-native-2.0.4.GA Is it 3.0 or 2.0 version? 
jbossws-native-3.0.2.GA

Specially confusing is jbossws-3.0.1-native-2.0.4.GA. It is nothing in release notes in Jira. According to http://jbws.dyndns.org/mediawiki/index.php?title=Supported_Target_Containers there is no such release.

Also confusing is number version which is sometimes before "native" and sometimes after. 


What is release jbossws-3.0.1-native-2.0.4.GA ?



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

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


From do-not-reply at jboss.com  Sat Aug 30 18:24:32 2008
From: do-not-reply at jboss.com (skajotde)
Date: Sat, 30 Aug 2008 18:24:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Standalone JBossWS
Message-ID: <26004474.1220135072226.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi

I have question about standalone JBossWS (thanks to JBoss Microcontainer).

According to http://jbws.dyndns.org/mediawiki/index.php?title=Install_JBossWS 

anonymous wrote : JBossWS Web Service Framework builds on top of JBoss Microcontainer which supports direct POJO deployment and standalone use outside the JBoss 

I didn't find "standalone" example on wiki, source or forum from one year past. Is there any available? 

One founded http://jbws.dyndns.org/mediawiki/index.php?title=Setup_your_IDE is about running deployed services on JBoss
anonymous wrote : 
  | Once you have imported the project, you need to start the JBoss application server that is configured in your ant.properties file...

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

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


From do-not-reply at jboss.com  Sat Aug 30 20:56:31 2008
From: do-not-reply at jboss.com (skajotde)
Date: Sat, 30 Aug 2008 20:56:31 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Missing jbossws.integration.target in
	ant.properties in 3.0.
Message-ID: <27708970.1220144191378.JavaMail.jboss@colo-br-02.atl.jboss.com>

I think there is missing property jbossws.integration.target in ant.properties in jbossws-native-3.0.3.GA. I'm comparing also jboss-native-2.0.3.GA and this property is there. Without this is build error ;>

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

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


From do-not-reply at jboss.com  Sat Aug 30 21:09:00 2008
From: do-not-reply at jboss.com (skajotde)
Date: Sat, 30 Aug 2008 21:09:00 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Missing jbossws.integration.target
	in ant.properties in
Message-ID: <55543.1220144941021.JavaMail.jboss@colo-br-02.atl.jboss.com>

Problem is with ant eclipse after fresh download jbossws-native-3.0.3.GA

  | C:\RG\Instalki\jbossws-native-dist>ant eclipse
  | Buildfile: build.xml
  | 
  | prepare:
  | 
  | init:
  | 
  | BUILD FAILED
  | C:\RG\Instalki\jbossws-native-dist\build.xml:47: jbossws.integration.target not set
  | 
  | Total time: 0 seconds
  | C:\RG\Instalki\jbossws-native-dist>

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

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


From do-not-reply at jboss.com  Sun Aug 31 06:42:59 2008
From: do-not-reply at jboss.com (skajotde)
Date: Sun, 31 Aug 2008 06:42:59 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Problem with Deploy and undeploy
	JBossWS-native-3.0.3.GA
Message-ID: <8649540.1220179379372.JavaMail.jboss@colo-br-02.atl.jboss.com>

After deploy JBossWS-native-3.0.3.GA on JBossAS 4.2.2.GA and next undeploy, replace with JBossWS-native-2.0.3.GA (which comes with defaults) there is problem when server starts.


  | 12:38:22,250 ERROR [MainDeployer] Could not create deployment: file:/C:/RG/Labs/jboss-4.2.2.GA/server/default/deploy/jbossws.sar/
  | org.jboss.deployment.DeploymentException: No ClassLoaders found for: org.jboss.wsf.container.jboss42.DeployerInterceptorJSE; - nested throwable: (java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.wsf.container.jboss42.DeployerInterceptorJSE)
  | 	at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:196)
  | 	at org.jboss.system.ServiceController.install(ServiceController.java:226)
  | 	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.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.install(Unknown Source)
  | 	at org.jboss.deployment.SARDeployer.create(SARDeployer.java:249)
  | 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
  | 	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.java:142)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy9.deploy(Unknown Source)
  | 	at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
  | 	at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
  | 	at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
  | 	at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
  | 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
  | 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
  | 	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:585)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
  | 	at $Proxy0.start(Unknown Source)
  | 	at org.jboss.system.ServiceController.start(ServiceController.java:417)
  | 	at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:585)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy4.start(Unknown Source)
  | 	at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
  | 	at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:585)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy5.deploy(Unknown Source)
  | 	at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
  | 	at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
  | 	at org.jboss.Main.boot(Main.java:200)
  | 	at org.jboss.Main$1.run(Main.java:508)
  | 	at java.lang.Thread.run(Thread.java:595)
  | Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.wsf.container.jboss42.DeployerInterceptorJSE
  | 	at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212)
  | 	at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:521)
  | 	at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:415)
  | 	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
  | 	at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:1204)
  | 	at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:286)
  | 	at org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:344)
  | 	at org.jboss.system.ServiceCreator.install(ServiceCreator.java:157)
  | 	at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:451)
  | 	at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171)
  | 	... 81 more
  | 


Steps to deploy, undeploy and deploy previous version:


  | 
  | C:\RG\Labs\jbossws-native-3.0.3.GA>ant deploy-jboss422
  | Buildfile: build.xml
  | 
  | target-jboss422:
  | 
  | prepare:
  | 
  | init:
  |      [echo] integration.target=jboss422
  | 
  | undeploy-jboss422:
  |    [delete] Deleting directory C:\RG\Labs\jboss-4.2.2.GA\server\default\deploy\jbossws.sar
  |    [delete] Deleting directory C:\RG\Labs\jboss-4.2.2.GA\server\default\deploy\juddi-service.sar
  | 
  | prepare-deploy:
  | 
  | deploy-structure-jboss42:
  |    [delete] Deleting directory C:\RG\Labs\jbossws-native-3.0.3.GA\output\deploy-jboss422
  | 
  | check-parameters:
  | 
  | deploy-jbossws-endorsed:
  | 
  | deploy-jbossws-native42:
  |     [mkdir] Created dir: C:\RG\Labs\jbossws-native-3.0.3.GA\output\deploy-jboss422\bin
  |      [copy] Copying 8 files to C:\RG\Labs\jbossws-native-3.0.3.GA\output\deploy-jboss422\bin
  |     [mkdir] Created dir: C:\RG\Labs\jbossws-native-3.0.3.GA\output\deploy-jboss422\client
  |      [copy] Copying 23 files to C:\RG\Labs\jbossws-native-3.0.3.GA\output\deploy-jboss422\client
  |     [mkdir] Created dir: C:\RG\Labs\jbossws-native-3.0.3.GA\output\deploy-jboss422\lib
  |     [mkdir] Created dir: C:\RG\Labs\jbossws-native-3.0.3.GA\output\deploy-jboss422\server\default\lib
  |      [copy] Copying 8 files to C:\RG\Labs\jbossws-native-3.0.3.GA\output\deploy-jboss422\server\default\lib
  |     [mkdir] Created dir: C:\RG\Labs\jbossws-native-3.0.3.GA\output\deploy-jboss422\server\default\deploy\jbossws.sar
  |      [copy] Copying 11 files to C:\RG\Labs\jbossws-native-3.0.3.GA\output\deploy-jboss422\server\default\deploy\jbossws.sar
  |     [unzip] Expanding: C:\RG\Labs\jbossws-native-3.0.3.GA\deploy\lib\jbossws-native-management.war into C:\RG\Labs\jbossws-native-3.0.3.GA\output\deploy-jboss422\server\default\deploy\jbossws.sar\jbos
  | sws-management.war
  |      [copy] Copying 1 file to C:\RG\Labs\jbossws-native-3.0.3.GA\output\deploy-jboss422\server\default\deploy\jbossws.sar\jbossws.beans
  |      [copy] Copying 5 files to C:\RG\Labs\jbossws-native-3.0.3.GA\output\deploy-jboss422\server\default\deploy\jbossws.sar\META-INF
  |     [mkdir] Created dir: C:\RG\Labs\jbossws-native-3.0.3.GA\output\deploy-jboss422\server\default\deploy\juddi-service.sar
  |     [unzip] Expanding: C:\RG\Labs\jbossws-native-3.0.3.GA\deploy\lib\juddi-service.sar into C:\RG\Labs\jbossws-native-3.0.3.GA\output\deploy-jboss422\server\default\deploy\juddi-service.sar
  | 
  | deploy-jboss422:
  |      [copy] Copying 79 files to C:\RG\Labs\jboss-4.2.2.GA
  |      [copy] Copied 30 empty directories to 2 empty directories under C:\RG\Labs\jboss-4.2.2.GA
  | 
  | BUILD SUCCESSFUL
  | Total time: 5 seconds
  | C:\RG\Labs\jbossws-native-3.0.3.GA>ant undeploy-jboss422
  | Buildfile: build.xml
  | 
  | target-jboss422:
  | 
  | prepare:
  | 
  | init:
  |      [echo] integration.target=jboss422
  | 
  | undeploy-jboss422:
  |    [delete] Deleting directory C:\RG\Labs\jboss-4.2.2.GA\server\default\deploy\jbossws.sar
  |    [delete] Deleting directory C:\RG\Labs\jboss-4.2.2.GA\server\default\deploy\juddi-service.sar
  | 
  | BUILD SUCCESSFUL
  | Total time: 0 seconds
  | C:\RG\Labs\jbossws-native-3.0.3.GA>cd C:\RG\Labs\jbossws-native-2.0.3.GA
  | 
  | C:\RG\Labs\jbossws-native-2.0.3.GA>ant deploy-jboss422
  | Buildfile: build.xml
  | 
  | prepare:
  | 
  | undeploy-jboss422-endorsed:
  | 
  | undeploy-jboss422:
  | 
  | deploy-jboss422-endorsed:
  | 
  | deploy-jboss422:
  |     [unzip] Expanding: C:\RG\Labs\jbossws-native-2.0.3.GA\lib\jbossws-core-scripts.zip into C:\RG\Labs\jboss-4.2.2.GA\bin
  |      [copy] Copying 14 files to C:\RG\Labs\jboss-4.2.2.GA\client
  |     [mkdir] Created dir: C:\RG\Labs\jboss-4.2.2.GA\server\default\deploy\jbossws.sar
  |     [unjar] Expanding: C:\RG\Labs\jbossws-native-2.0.3.GA\lib\jbossws-native42.sar into C:\RG\Labs\jboss-4.2.2.GA\server\default\deploy\jbossws.sar
  |     [mkdir] Created dir: C:\RG\Labs\jboss-4.2.2.GA\server\default\deploy\juddi-service.sar
  |     [unzip] Expanding: C:\RG\Labs\jbossws-native-2.0.3.GA\lib\juddi-service.sar into C:\RG\Labs\jboss-4.2.2.GA\server\default\deploy\juddi-service.sar
  |     [unzip] Expanding: C:\RG\Labs\jbossws-native-2.0.3.GA\lib\jbossws-framework-scripts.zip into C:\RG\Labs\jboss-4.2.2.GA\bin
  |      [copy] Copying 3 files to C:\RG\Labs\jboss-4.2.2.GA\client
  |      [copy] Copying 3 files to C:\RG\Labs\jboss-4.2.2.GA\server\default\lib
  | 
  | BUILD SUCCESSFUL
  | Total time: 4 seconds
  | C:\RG\Labs\jbossws-native-2.0.3.GA>
  | 

I think ant scripts doesn't remove some library?

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

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


From do-not-reply at jboss.com  Sun Aug 31 07:02:15 2008
From: do-not-reply at jboss.com (skajotde)
Date: Sun, 31 Aug 2008 07:02:15 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem with Deploy and undeploy
	JBossWS-native-3.0.3.GA
Message-ID: <23468565.1220180535417.JavaMail.jboss@colo-br-02.atl.jboss.com>

It is diff from cygwin:


  | kamild at kde ~/RG/Labs
  | $ diff -r jboss-4.2.2.GA-fresh/ jboss-4.2.2.GA-deploy-undeploy/ -q
  | Files jboss-4.2.2.GA-fresh/bin/wsrunclient.bat and jboss-4.2.2.GA-deploy-undeploy/bin/wsrunclient.bat differ
  | Files jboss-4.2.2.GA-fresh/bin/wsrunclient.sh and jboss-4.2.2.GA-deploy-undeploy/bin/wsrunclient.sh differ
  | Files jboss-4.2.2.GA-fresh/bin/wstools.bat and jboss-4.2.2.GA-deploy-undeploy/bin/wstools.bat differ
  | Files jboss-4.2.2.GA-fresh/bin/wstools.sh and jboss-4.2.2.GA-deploy-undeploy/bin/wstools.sh differ
  | Files jboss-4.2.2.GA-fresh/client/jaxb-api.jar and jboss-4.2.2.GA-deploy-undeploy/client/jaxb-api.jar differ
  | Files jboss-4.2.2.GA-fresh/client/jaxb-impl.jar and jboss-4.2.2.GA-deploy-undeploy/client/jaxb-impl.jar differ
  | Files jboss-4.2.2.GA-fresh/client/jaxb-xjc.jar and jboss-4.2.2.GA-deploy-undeploy/client/jaxb-xjc.jar differ
  | Files jboss-4.2.2.GA-fresh/client/jaxws-rt.jar and jboss-4.2.2.GA-deploy-undeploy/client/jaxws-rt.jar differ
  | Files jboss-4.2.2.GA-fresh/client/jaxws-tools.jar and jboss-4.2.2.GA-deploy-undeploy/client/jaxws-tools.jar differ
  | Files jboss-4.2.2.GA-fresh/client/jboss-jaxrpc.jar and jboss-4.2.2.GA-deploy-undeploy/client/jboss-jaxrpc.jar differ
  | Only in jboss-4.2.2.GA-deploy-undeploy/client: jboss-jaxws-ext.jar
  | Files jboss-4.2.2.GA-fresh/client/jboss-jaxws.jar and jboss-4.2.2.GA-deploy-undeploy/client/jboss-jaxws.jar differ
  | Files jboss-4.2.2.GA-fresh/client/jboss-saaj.jar and jboss-4.2.2.GA-deploy-undeploy/client/jboss-saaj.jar differ
  | Files jboss-4.2.2.GA-fresh/client/jbossws-client.jar and jboss-4.2.2.GA-deploy-undeploy/client/jbossws-client.jar differ
  | Files jboss-4.2.2.GA-fresh/client/jbossws-common.jar and jboss-4.2.2.GA-deploy-undeploy/client/jbossws-common.jar differ
  | Files jboss-4.2.2.GA-fresh/client/jbossws-framework.jar and jboss-4.2.2.GA-deploy-undeploy/client/jbossws-framework.jar differ
  | Only in jboss-4.2.2.GA-fresh/client: jbossws-jboss42.jar
  | Files jboss-4.2.2.GA-fresh/client/jbossws-spi.jar and jboss-4.2.2.GA-deploy-undeploy/client/jbossws-spi.jar differ
  | Files jboss-4.2.2.GA-fresh/client/policy.jar and jboss-4.2.2.GA-deploy-undeploy/client/policy.jar differ
  | Only in jboss-4.2.2.GA-fresh/client: stax-api.jar
  | Files jboss-4.2.2.GA-fresh/client/stax-ex.jar and jboss-4.2.2.GA-deploy-undeploy/client/stax-ex.jar differ
  | Files jboss-4.2.2.GA-fresh/client/streambuffer.jar and jboss-4.2.2.GA-deploy-undeploy/client/streambuffer.jar differ
  | Files jboss-4.2.2.GA-fresh/client/wsdl4j.jar and jboss-4.2.2.GA-deploy-undeploy/client/wsdl4j.jar differ
  | Only in jboss-4.2.2.GA-fresh/client: wstx.jar
  | Only in jboss-4.2.2.GA-deploy-undeploy/server/default: data
  | Files jboss-4.2.2.GA-fresh/server/default/deploy/jbossws.sar/META-INF/MANIFEST.MF and jboss-4.2.2.GA-deploy-undeploy/server/default/deploy/jbossws.sar/META-INF/MANIFEST.MF differ
  | Files jboss-4.2.2.GA-fresh/server/default/deploy/jbossws.sar/META-INF/standard-jaxws-client-config.xml and jboss-4.2.2.GA-deploy-undeploy/server/default/deploy/jbossws.sar/META-INF/standard-jaxws-clie
  | nt-config.xml differ
  | Files jboss-4.2.2.GA-fresh/server/default/deploy/jbossws.sar/META-INF/standard-jaxws-endpoint-config.xml and jboss-4.2.2.GA-deploy-undeploy/server/default/deploy/jbossws.sar/META-INF/standard-jaxws-en
  | dpoint-config.xml differ
  | Files jboss-4.2.2.GA-fresh/server/default/deploy/jbossws.sar/jaxb-api.jar and jboss-4.2.2.GA-deploy-undeploy/server/default/deploy/jbossws.sar/jaxb-api.jar differ
  | Files jboss-4.2.2.GA-fresh/server/default/deploy/jbossws.sar/jaxb-impl.jar and jboss-4.2.2.GA-deploy-undeploy/server/default/deploy/jbossws.sar/jaxb-impl.jar differ
  | Files jboss-4.2.2.GA-fresh/server/default/deploy/jbossws.sar/jboss-jaxb-intros.jar and jboss-4.2.2.GA-deploy-undeploy/server/default/deploy/jbossws.sar/jboss-jaxb-intros.jar differ
  | Files jboss-4.2.2.GA-fresh/server/default/deploy/jbossws.sar/jboss-jaxrpc.jar and jboss-4.2.2.GA-deploy-undeploy/server/default/deploy/jbossws.sar/jboss-jaxrpc.jar differ
  | Only in jboss-4.2.2.GA-deploy-undeploy/server/default/deploy/jbossws.sar: jboss-jaxws-ext.jar
  | Files jboss-4.2.2.GA-fresh/server/default/deploy/jbossws.sar/jboss-jaxws.jar and jboss-4.2.2.GA-deploy-undeploy/server/default/deploy/jbossws.sar/jboss-jaxws.jar differ
  | Files jboss-4.2.2.GA-fresh/server/default/deploy/jbossws.sar/jboss-saaj.jar and jboss-4.2.2.GA-deploy-undeploy/server/default/deploy/jbossws.sar/jboss-saaj.jar differ
  | Files jboss-4.2.2.GA-fresh/server/default/deploy/jbossws.sar/jbossws-context.war/index.html and jboss-4.2.2.GA-deploy-undeploy/server/default/deploy/jbossws.sar/jbossws-context.war/index.html differ
  | Files jboss-4.2.2.GA-fresh/server/default/deploy/jbossws.sar/jbossws-context.war/styles.css and jboss-4.2.2.GA-deploy-undeploy/server/default/deploy/jbossws.sar/jbossws-context.war/styles.css differ
  | Files jboss-4.2.2.GA-fresh/server/default/deploy/jbossws.sar/jbossws-core.jar and jboss-4.2.2.GA-deploy-undeploy/server/default/deploy/jbossws.sar/jbossws-core.jar differ
  | Only in jboss-4.2.2.GA-fresh/server/default/deploy/jbossws.sar: jbossws-native.jar
  | Files jboss-4.2.2.GA-fresh/server/default/deploy/jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml and jboss-4.2.2.GA-deploy-undeploy/server/default/deploy/jbossws.sar/jbossws.beans/META-INF/jboss-be
  | ans.xml differ
  | Files jboss-4.2.2.GA-fresh/server/default/deploy/jbossws.sar/policy.jar and jboss-4.2.2.GA-deploy-undeploy/server/default/deploy/jbossws.sar/policy.jar differ
  | Files jboss-4.2.2.GA-fresh/server/default/deploy/jbossws.sar/stax-api.jar and jboss-4.2.2.GA-deploy-undeploy/server/default/deploy/jbossws.sar/stax-api.jar differ
  | Files jboss-4.2.2.GA-fresh/server/default/deploy/jbossws.sar/wsdl4j.jar and jboss-4.2.2.GA-deploy-undeploy/server/default/deploy/jbossws.sar/wsdl4j.jar differ
  | Files jboss-4.2.2.GA-fresh/server/default/deploy/jbossws.sar/wstx.jar and jboss-4.2.2.GA-deploy-undeploy/server/default/deploy/jbossws.sar/wstx.jar differ
  | Files jboss-4.2.2.GA-fresh/server/default/deploy/jbossws.sar/xmlsec.jar and jboss-4.2.2.GA-deploy-undeploy/server/default/deploy/jbossws.sar/xmlsec.jar differ
  | Only in jboss-4.2.2.GA-deploy-undeploy/server/default/deploy: juddi-service.sar
  | Only in jboss-4.2.2.GA-fresh/server/default/lib: jboss-jaxrpc.jar
  | Only in jboss-4.2.2.GA-fresh/server/default/lib: jboss-jaxws.jar
  | Only in jboss-4.2.2.GA-fresh/server/default/lib: jboss-saaj.jar
  | Files jboss-4.2.2.GA-fresh/server/default/lib/jbossws-common.jar and jboss-4.2.2.GA-deploy-undeploy/server/default/lib/jbossws-common.jar differ
  | Files jboss-4.2.2.GA-fresh/server/default/lib/jbossws-framework.jar and jboss-4.2.2.GA-deploy-undeploy/server/default/lib/jbossws-framework.jar differ
  | Only in jboss-4.2.2.GA-fresh/server/default/lib: jbossws-jboss42.jar
  | Files jboss-4.2.2.GA-fresh/server/default/lib/jbossws-spi.jar and jboss-4.2.2.GA-deploy-undeploy/server/default/lib/jbossws-spi.jar differ
  | Only in jboss-4.2.2.GA-deploy-undeploy/server/default: log
  | 

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

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


From do-not-reply at jboss.com  Sun Aug 31 07:07:25 2008
From: do-not-reply at jboss.com (skajotde)
Date: Sun, 31 Aug 2008 07:07:25 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem with Deploy and undeploy
	JBossWS-native-3.0.3.GA
Message-ID: <22454405.1220180845809.JavaMail.jboss@colo-br-02.atl.jboss.com>

Good news ;>

Problem resolved after copying jbossws-jboss42.jar to C:\RG\Labs\jboss-4.2.2.GA-deploy-undeploy\server\default\lib

Commands which helped: 

java -jar jarscan.jar -dir C:\RG\Labs\jboss-4.2.2.GA-fresh -class DeployerInterceptorJSE
  | 
  | java -jar jarscan.jar -dir C:\RG\Labs\jboss-4.2.2.GA-deploy-undeploy -class DeployerInterceptorJSE
  | 

Ant scripts should copy this file ?

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

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


From do-not-reply at jboss.com  Sun Aug 31 08:24:11 2008
From: do-not-reply at jboss.com (skajotde)
Date: Sun, 31 Aug 2008 08:24:11 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Standalone JBossWS
Message-ID: <15842457.1220185451530.JavaMail.jboss@colo-br-02.atl.jboss.com>

I'm really impressed by JBossWS Testsuite. One tests only executes 2-3 seconds with deploy-execute-undeploy on running JBoss. 

On my project one cycle is 10-20 minutes ;/ Many projects with few ears built by maven instead of JBoss Tools, so IDE support is limited. Additionally one problem during deployment blocks my developing even It is not really involved. It is hard ;> and until now I have too little skills to run this with JBoss Embedded (which is not officially supported now)

I have some experience in Spring so move to this library in testing EJB from IDE (Pojo services with setters). Now I can tests in couple of seconds instead of 10 minutes It looks really nice but doesn't cover full JWS features. My JWS is just Pojo ;>

JBossWS Testsuite way (one war per JWS) doesn't match to my case because I don't know how to fast deploy EJB which is required by these JWS (create a few dozen virtual jars with EJB ?) Other solution which comes me to mind is to attach local spring to remote JBoss but I don't know is it good ;> My Spring EM Factory is local and JWS is remote deployed.

When I have read 

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

anonymous wrote : JBossWS Web Service Framework builds on top of JBoss Microcontainer which supports direct POJO deployment and standalone  use outside the JBoss 

I had hope that now it just need to wrapper my JWS Pojo in JBossWS Standalone and everything go ;> Is it really option ?

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

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