From do-not-reply at jboss.com  Wed Jul  1 08:52:43 2009
From: do-not-reply at jboss.com (alfred.rsa)
Date: Wed, 1 Jul 2009 08:52:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Newlines/spaces in SOAPMessage
Message-ID: <14762457.1246452763494.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi guys

I have code that works when I call it from a stand-alone application, but when I call it from within JBoss, I get a NPE from the Web service I am calling.
The problem seems to be newline or space characters between the XML tags of the SOAP message. When I use the stand-alone code I get the following output from SOAPMessage().writeTo(System.out)
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body><searchDocDataRequest><f_nr>test_fno</f_nr><userid>cnt_usr</userid><items><cheque format="tiff"><account_nr>62001869538</account_nr></cheque></items></searchDocDataRequest></SOAP-ENV:Body></SOAP-ENV:Envelope>
  | 
>From within JBoss I get:

  | 13:41:03,491 INFO  [STDOUT] <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:Body><searchDocDataRequest><f_nr>test_fno
  | 13:41:03,491 INFO  [STDOUT] </f_nr>
  | 13:41:03,491 INFO  [STDOUT] <userid>cnt_usr
  | 13:41:03,491 INFO  [STDOUT] </userid>
  | 13:41:03,507 INFO  [STDOUT] <items><cheque format='tiff'><account_nr>62001869538
  | 13:41:03,507 INFO  [STDOUT] </account_nr>
  | 13:41:03,507 INFO  [STDOUT] </cheque>
  | 13:41:03,507 INFO  [STDOUT] </items>
  | 13:41:03,523 INFO  [STDOUT] </searchDocDataRequest>
  | 13:41:03,523 INFO  [STDOUT] </env:Body></env:Envelope>
The only difference being the prefix and the newline/space.
Does anybody have any idea on how I can remove this?

Reards
Alfred

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

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


From do-not-reply at jboss.com  Thu Jul  2 02:04:53 2009
From: do-not-reply at jboss.com (a.gazzarini)
Date: Thu, 2 Jul 2009 02:04:53 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBoss WS Pojos endpoint authentication
Message-ID: <6219932.1246514693768.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi, I was trying to configure authentication for my pojo endpoint as described on http://www.jboss.org/community/wiki/JBossWS-SecureTransport.
Well, probelm is that my security constraints (web.xml) is protecting all resources (/*) including WSDL, so when I try to invoke the Service.getPort(...) method that invocation fails because credentials are provided later on BindingProvider as shown below:


  | URL wsdlURL = new File("resources/jaxws/samples/context/WEB-INF/wsdl/TestEndpoint.wsdl").toURL();
  | QName qname = new QName("http://org.jboss.ws/jaxws/context", "TestEndpointService");
  | Service service = Service.create(wsdlURL, qname);
  | port = (TestEndpoint)service.getPort(TestEndpoint.class);
  |  
  | BindingProvider bp = (BindingProvider)port;
  | bp.getRequestContext().put(BindingProvider.USERNAME_PROPERTY, "kermit");
  | bp.getRequestContext().put(BindingProvider.PASSWORD_PROPERTY, "thefrog");
  | 

Note that authentication is correctly configured : If i try to access to WSDL using a browser I get the authentication POPUP (I configured BASIC authentication); after inserting credentials the WSDL is correctly displayed. 

Could you help me?

Regards,
Andrea

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

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


From do-not-reply at jboss.com  Thu Jul  2 04:30:14 2009
From: do-not-reply at jboss.com (alfred.rsa)
Date: Thu, 2 Jul 2009 04:30:14 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Newlines/spaces in SOAPMessage
Message-ID: <7151700.1246523414142.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Using WireShark to intercept the transmission, I found that the JBoss SOAPElement.setvalue implementation seems
to add a carriage return linefeed combination to my text which causes the Web Service to crash:

0000   37 32 0d 0a 3c 65 6e 76 3a 45 6e 76 65 6c 6f 70  72..<env:Envelop
  | 0010   65 20 78 6d 6c 6e 73 3a 65 6e 76 3d 27 68 74 74  e xmlns:env='htt
  | 0020   70 3a 2f 2f 73 63 68 65 6d 61 73 2e 78 6d 6c 73  p://schemas.xmls
  | 0030   6f 61 70 2e 6f 72 67 2f 73 6f 61 70 2f 65 6e 76  oap.org/soap/env
  | 0040   65 6c 6f 70 65 2f 27 3e 3c 65 6e 76 3a 42 6f 64  elope/'><env:Bod
  | 0050   79 3e 3c 73 65 61 72 63 68 44 6f 63 44 61 74 61  y><searchDocData
  | 0060   52 65 71 75 65 73 74 3e 3c 66 5f 6e 72 3e 74 65  Request><f_nr>te
  | 0070   73 74 5f 66 6e 6f 0d 0a                          st_fno..
When I use Sun's SAAJ this doesnot happen
Any ideas?
Regards Alfred

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

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


From do-not-reply at jboss.com  Thu Jul  2 08:55:58 2009
From: do-not-reply at jboss.com (sbutt)
Date: Thu, 2 Jul 2009 08:55:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - sending Soap message with timeout
Message-ID: <10511591.1246539358125.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi Folks,
            I have implemented a basic soap client (javax.xml.soap.*). 


  | 
  | public Message processSOAPRequest(Message message) {
  |     try {
  |       MessageFactory msgFactory = MessageFactory.newInstance();
  |       SOAPMessage soap = msgFactory.createMessage();
  |       SOAPPart soapPart = soap.getSOAPPart();
  | 
  |       byte[] buffer = ((String) message.getBody().get()).getBytes();
  |       ByteArrayInputStream stream = new ByteArrayInputStream(buffer);
  |       StreamSource source = new StreamSource(stream);
  |       soapPart.setContent(source);
  |       String action = config.getAttribute(SOAP_ACTION);
  |       if (action != null) {
  |         MimeHeaders headers = soap.getMimeHeaders();
  |         headers.addHeader("SOAPAction", action);
  |       }
  |     
  |       /////////////////////////////////////////////////////////
  | 
  |       SOAPMessage reply = sendSOAPMessage(soap);
  | 
  |       /////////////////////////////////////////////////////////    
  | 
  |       ByteArrayOutputStream out = new ByteArrayOutputStream();
  |       reply.writeTo(out);
  |       String soapMessage = new String(out.toByteArray());
  |       message.getBody().add(soapMessage);
  | 
  |     } catch (SOAPException e) {
  |       logger.error("SOAPException : " + e);
  | 
  |     } catch (IOException e) {
  |       logger.error("IOException : " + e);
  |     }
  | 
  |     return message;
  | 
  |   }
  | 
  | 
  |  private SOAPMessage sendSOAPMessage(SOAPMessage soap) {
  |     SOAPConnection connection = null;
  |     SOAPMessage reply = null;
  |     try {
  |       SOAPConnectionFactory soapConnFactory = SOAPConnectionFactory
  |           .newInstance();
  |       connection = soapConnFactory.createConnection();
  |       String destination = config.getAttribute(URL_ENDPOINT);
  |             
  |       reply = connection.call(soap, destination);
  |   
  |       
  |       
  |     } catch (Exception e) {
  |       logger.error(e);
  |     } finally {
  |       try {
  |         if (connection != null) {
  |           connection.close();
  |         }
  |       } catch (SOAPException e) {
  |         logger.error(e);
  |       }
  |     }
  | 
  |     return reply;
  |   }
  | 
  | 

The input message is JBossEsb message, which I convert to soap message and then send it using SOAPConnection, which works fine. 

The problem with SOAPConnection class is that it does not provide setTimeout(..) method. I read some where that there is another class SOAPConnectionImpl (by axis), which extends SOAPConnection and has this setTimeout method.

I have tried to convert my existing implementation to SOAPConnectionImpl but i always get a classcast exceptions.

Could somebody help me in suggesting a solution to this problem? My main concern is to include timeout feature that is my WS consumer/client should timeout after a certain period if the server does not reply. 

Any other soap message sending implementation with timeout feature are also good.

I have included 
    	
  | <dependency>
  |     <groupId>axis</groupId>
  |     <artifactId>axis</artifactId>
  |     <version>1.4</version>
  | </dependency>
  | 

maven dependencies for axis.

Awaiting replies.

Thanks.

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

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


From do-not-reply at jboss.com  Thu Jul  2 09:07:03 2009
From: do-not-reply at jboss.com (jpredpos)
Date: Thu, 2 Jul 2009 09:07:03 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBoss client WS
Message-ID: <24737896.1246540023903.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi, I'm using JBoss 4.2.3.GA. 

I had a jar that invoke some Web Service SOAP. I haved a Junits that test this web services, and works fine. 

Then, I have an other app. that publish some REST WS, this WS do some staff and call the jar.  I deploy this REST WS in the JBoss

When I invoke the REST WS, the response of the WS SOAP return null ... I had a try - catch and also the Exception is null :-(

Some ideas ? May be, it's necessary some extra configuration to the JBoss ? 

thanks!

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

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


From do-not-reply at jboss.com  Thu Jul  2 10:11:24 2009
From: do-not-reply at jboss.com (jpredpos)
Date: Thu, 2 Jul 2009 10:11:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBoss client WS
Message-ID: <7420062.1246543884914.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I migrated to JBoss 5.1.0  and throws some errors:

11:02:22,389 ERROR [[ServletAdaptor]] Servlet.service() para servlet ServletAdaptor lanz?? excepci??n
javax.servlet.ServletException: non-HTTP request or response
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:829)
        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:191)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
        at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
        at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
        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:158)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
        at java.lang.Thread.run(Thread.java:619)

any ideA?


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

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



From do-not-reply at jboss.com  Fri Jul  3 07:26:08 2009
From: do-not-reply at jboss.com (sty777)
Date: Fri, 3 Jul 2009 07:26:08 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WebServiceException: Undefined port
	type
Message-ID: <28433515.1246620368497.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I had the same problem with JBoss AS 5.0.1 and JBossWS 3.1.1. I looked at one of the samples (, which comes with the JBossWS distribution) under webservice folder. It uses EndpointInterface.java in the client deployment (see the comment at the top in the class). Basically it's pretty much the same as the remote interface - EJB3RemoteInterface, but with a few more annotations.

I created a new interface following the above and replaced "HelloRemote" with it and it worked.

I followed one of the tutorials, which used JBoss AS 5.0.0 CR2 and JBossWS 3.0.4. So, there may be some differences.

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

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


From do-not-reply at jboss.com  Sat Jul  4 12:13:46 2009
From: do-not-reply at jboss.com (mtirumalreddy)
Date: Sat, 4 Jul 2009 12:13:46 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Jar file for
	org.jboss.ws.core.soap.SAAJMetaFactoryImpl.
Message-ID: <8272503.1246724026434.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi,

Please have a look at this post. I think it might be helpful.

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



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

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


From do-not-reply at jboss.com  Sat Jul  4 12:15:46 2009
From: do-not-reply at jboss.com (mtirumalreddy)
Date: Sat, 4 Jul 2009 12:15:46 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Jar file for
	org.jboss.ws.core.soap.SAAJMetaFactoryImpl.
Message-ID: <30417757.1246724146816.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi,

Please have a look at this post. This might be helpful.


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

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

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


From do-not-reply at jboss.com  Mon Jul  6 10:09:49 2009
From: do-not-reply at jboss.com (Oberiko)
Date: Mon, 6 Jul 2009 10:09:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Streamlined tutorial on JBossWS w/
	policies (WS-RM)?
Message-ID: <33231447.1246889389055.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hello,

I'm relatively new to Web Services (only done very simple clients) and I've been struggling to get a WS-RM service/client up for a few days now.  Part of the problem is that I'm seeing many, many different ways on how this is done, to the point that I'm not sure what the "correct" way is.

The service part is, thanks to the @Policy annotations, seemingly very simple for me to set up:
Service

  | package com.webService;
  | 
  | import javax.jws.WebService;
  | 
  | import org.jboss.ws.extensions.policy.PolicyScopeLevel;
  | import org.jboss.ws.extensions.policy.annotation.Policy;
  | import org.jboss.ws.extensions.policy.annotation.PolicyAttachment;
  | 
  | @PolicyAttachment
  | (
  |    @Policy
  |    (
  |       policyFileLocation = "WEB-INF/wsrm-exactly-once-in-order-policy.xml",
  |       scope = PolicyScopeLevel.WSDL_BINDING
  |    )
  | )
  | @WebService
  | public class Reliable {
  | 	public String echo(String parameter){
  | 		return "You reliably passed the string '"+parameter+"'";
  | 	}
  | }
  | 

configuration XML file

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

Now, I'm stuck.  I gather that I need to somehow configure my client to use RM ("The RM Destination requires the use of WSRM" is the message I'm getting), but I am uncertain how to optimally do this.

Client
	
  | public void testReliable(){
  | 	Reliable port = new ReliableService().getReliablePort();
  | 		
  | 	//I need some stuff here it seems
  | 		
  | 	port.echo("a test message");
  | }
  | 
Could someone provide me with the simplest guidelines I need to follow that would work?  I should mention that one of my goals is keep the XML configuration to an absolute minimum, centralizing as much as possible within the application itself.  

Thanks to anyone who can help me out.

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

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


From do-not-reply at jboss.com  Mon Jul  6 15:51:32 2009
From: do-not-reply at jboss.com (randhawag)
Date: Mon, 6 Jul 2009 15:51:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Call a web service
Message-ID: <10010009.1246909892145.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Has anyone been able to resolve this?
We have difficulty connecting via client to web service endpoint. 

When running client we see, 


JBDS 2.0 GA
JAX-WS 2.0
Server: JBoss 4.3 EAP CP02

***********************
Create Web Service Client...
Create Web Service...
Call Web Service Operation...
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/xml/messaging/saaj/soap/AttachmentPartImpl
	at com.sun.xml.ws.message.AttachmentUnmarshallerImpl.(AttachmentUnmarshallerImpl.java:55)
	at com.sun.xml.ws.client.sei.ResponseBuilder$RpcLit$PartBuilder.readResponse(ResponseBuilder.java:635)
	at com.sun.xml.ws.client.sei.ResponseBuilder$RpcLit.readResponse(ResponseBuilder.java:599)
	at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:242)
	at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:210)
	at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:103)
	at $Proxy22.echo(Unknown Source)
	at venture.services.helloworld.clientsample.ClientSample.main(ClientSample.java:16)
Caused by: java.lang.ClassNotFoundException: com.sun.xml.messaging.saaj.soap.AttachmentPartImpl
	at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
	... 8 more

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

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


From do-not-reply at jboss.com  Tue Jul  7 02:40:26 2009
From: do-not-reply at jboss.com (alfred.rsa)
Date: Tue, 7 Jul 2009 02:40:26 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Using SUN's SAAJ implementation
Message-ID: <15200385.1246948826803.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi 

I have been struggling to get a JAX-RPC client to work on JBoss. The reason seems to be due to the CRLF characters inserted between the elements of the SOAP request. This does not happen when running outside of JBoss using SUN's SAAJ.
Also when I deploy my EAR file on Glassfish, it works properly, but not on JBoss 5.1.0. And I really do not want to use Glassfish as we use JBoss for everything else. Can I force my application to use SUN's SAAJ instead of JBoss' ?

Regards
Alfred 

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

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


From do-not-reply at jboss.com  Tue Jul  7 08:14:41 2009
From: do-not-reply at jboss.com (Sefai)
Date: Tue, 7 Jul 2009 08:14:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBossAS 5.1.0.GA & 3.1.2.GA & META-INF
Message-ID: <2306171.1246968881592.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi all,

I have a working war for 4.2.x, containing both a ws client and a server using WSSecurity, when I deploy it on 5.1.0.GA, the serving side worked but client side did not.

After days of debugging I found out that when application tries to consume some other web-service, standard-jaxws-client-config.xml and jboss-wsse-client.xml which are both located under META-INF are not read, but the client config under server/.../deployers/jbossws.deployer/META-INF/standard-jaxws-client-config.xml is read. So the WSSecurity does not work.
 
I moved META-INF under WEB-INF/classes of the war, some wiki I dont remember now was saying resource files must be under WEB-INF/classes for AS 5.x series, this time client worked but applications own WebService did not, it couldn't find standard-jaxws-endpoint-config.xml. So I duplicated META-INF on both directories, now both of them works.

Also server can find the keystore and truststore under WEB-INF, but the client part can only find them when they are under WEB-INF/classes, so I duplicated them, too.

I dont know the details of classloading very much, but I suspect this issue is related to it.

Is this a bug, or known issue of 5.1 which can be avoied with some other setting?

Thanks in advance...

     

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

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


From do-not-reply at jboss.com  Wed Jul  8 10:11:33 2009
From: do-not-reply at jboss.com (gang.yang)
Date: Wed, 8 Jul 2009 10:11:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - DOM API on SOAPElementImpl causes
	NotImplementedException
Message-ID: <25783489.1247062293795.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I'm working in the area where I need to process SOAP messages as DOM. I've been working with JBossWS as well as other providers. I found that JBossWS's SOAPElement implementation does not support many DOM APIs, such as getTextContent and getIdAttributeNode. Although these seem to be convenience APIs, but are used by our software as well as other 3rd party software. Lacking them limited JBossWS's capatibilties. I'm wondering why JBossWS did not implement them since all other providers seem to support them and if JBossWS has a plan to do so.

Thanks,
Gang

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

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


From do-not-reply at jboss.com  Wed Jul  8 10:19:47 2009
From: do-not-reply at jboss.com (MichaW)
Date: Wed, 8 Jul 2009 10:19:47 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WebService Client with MTOM
Message-ID: <6644318.1247062787265.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi,

I'm using jbossws-native-2.0.1 (default for the AS 4.2.2.GA).
I've used ws-consume on a wsdl from a thirdparty (see attached file).

When I try the create the service 

Service service = Service.create(getWsdlUrl(), getServiceName());

I get an error
 Caused by: org.jboss.ws.WSException: Cannot deploy null policy!
  |         at org.jboss.ws.extensions.policy.deployer.PolicyDeployer.deployClientSide(PolicyDeployer.java:146)
  |         at org.jboss.ws.extensions.policy.metadata.PolicyMetaDataBuilder.deployPolicyClientSide(PolicyMetaDataBuilder.java:310)
  |         at org.jboss.ws.extensions.policy.metadata.PolicyMetaDataBuilder.deployPolicy(PolicyMetaDataBuilder.java:277)
  |         at org.jboss.ws.extensions.policy.metadata.PolicyMetaDataBuilder.processPolicies(PolicyMetaDataBuilder.java:236)
  |         at org.jboss.ws.extensions.policy.metadata.PolicyMetaDataBuilder.processPolicyExtensions(PolicyMetaDataBuilder.java:193)
  |         at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.buildMetaData(JAXWSClientMetaDataBuilder.java:93)
  |         at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.<init>(ServiceDelegateImpl.java:131)
  |         at org.jboss.ws.core.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:61)
  |         at javax.xml.ws.Service.<init>(Service.java:83)
  |         at javax.xml.ws.Service.create(Service.java:721)
  |         at nl.denhaag.gbd.services.ebus.attachmentservice.client.AttachmentServiceClient.initEndpoint(AttachmentServiceClient.java:63)
  |         ... 43 more

When I use the same code on a webservice that does not use MTOM everything is working fine. 

What should I do to provide a policy for MTOM on the clientside?

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

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


From do-not-reply at jboss.com  Wed Jul  8 10:26:48 2009
From: do-not-reply at jboss.com (MichaW)
Date: Wed, 8 Jul 2009 10:26:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WebService Client with MTOM - WSDL
Message-ID: <1856596.1247063208453.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

attachmentservice_1.wsdl
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions name="AttachmentService" targetNamespace="http://tempuri.org/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:tns="http://tempuri.org/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:i0="http://ebus.onefox.nl/2009/2/4" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex">
  <wsdl:import namespace="http://ebus.onefox.nl/2009/2/4" location="AttachmentService.wsdl"/>
  <wsdl:types/>
  <wsdl:service name="AttachmentService">
    <wsdl:port name="AttachmentServiceEndpoint" binding="i0:AttachmentServiceEndpoint">
      <soap:address location="http://wkst02.onefox.nl/ebus/AttachmentService.svc"/>
    </wsdl:port>
  </wsdl:service>
</wsdl:definitions>


AttachmentService.wsdl
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://ebus.onefox.nl/2009/2/4" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:tns="http://ebus.onefox.nl/2009/2/4" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex">
  <wsp:Policy wsu:Id="AttachmentServiceEndpoint_policy">
    <wsp:ExactlyOne>
      <wsp:All>
        <wsoma:OptimizedMimeSerialization xmlns:wsoma="http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization"/>
      </wsp:All>
    </wsp:ExactlyOne>
  </wsp:Policy>
  <wsdl:types>
    <xsd:schema targetNamespace="http://ebus.onefox.nl/2009/2/4/Imports">
      <xsd:import schemaLocation="AttachmentService_1.xsd" namespace="http://ebus.onefox.nl/2009/2/4"/>
      <xsd:import schemaLocation="AttachmentService_1_2_3.xsd" namespace="http://ebus.onefox.nl/2009/2/4/attachment"/>
      <xsd:import schemaLocation="AttachmentService_1_2.xsd" namespace="http://schemas.microsoft.com/2003/10/Serialization/"/>
      <xsd:import schemaLocation="AttachmentService.xsd" namespace="http://ebus.onefox.nl/2009/2/4/data"/>
      <xsd:import schemaLocation="AttachmentService_1_2_3_4.xsd" namespace="http://schemas.microsoft.com/Message"/>
    </xsd:schema>
  </wsdl:types>
  <wsdl:message name="ReadDocumentMsg"/>
  <wsdl:message name="ReadDocumentMsg_Headers">
    <wsdl:part name="AuthInfo" element="tns:AuthInfo"/>
    <wsdl:part name="Data" element="q1:ReadDocumentMsg" xmlns:q1="http://ebus.onefox.nl/2009/2/4/attachment"/>
  </wsdl:message>
  <wsdl:message name="AttachmentServiceReadDocumentResMsg">
    <wsdl:part name="ReadDocumentContent" element="q2:ReadDocumentContent" xmlns:q2="http://ebus.onefox.nl/2009/2/4/attachment"/>
  </wsdl:message>
  <wsdl:message name="AttachmentServiceReadDocumentResMsg_Headers">
    <wsdl:part name="Result" element="q3:ReadDocumentResultMsg" xmlns:q3="http://ebus.onefox.nl/2009/2/4/attachment"/>
  </wsdl:message>
  <wsdl:message name="WriteDocumentMsg">
    <wsdl:part name="ReadDocumentContent" element="q4:ReadDocumentContent" xmlns:q4="http://ebus.onefox.nl/2009/2/4/attachment"/>
  </wsdl:message>
  <wsdl:message name="WriteDocumentMsg_Headers">
    <wsdl:part name="AuthInfo" element="tns:AuthInfo"/>
    <wsdl:part name="Data" element="q5:WriteDocumentMsg" xmlns:q5="http://ebus.onefox.nl/2009/2/4/attachment"/>
  </wsdl:message>
  <wsdl:message name="AttachmentServiceWriteDocumentResMsg"/>
  <wsdl:message name="AttachmentServiceWriteDocumentResMsg_Headers">
    <wsdl:part name="Result" element="q6:WriteDocumentResultMsg" xmlns:q6="http://ebus.onefox.nl/2009/2/4/attachment"/>
  </wsdl:message>
  <wsdl:portType name="AttachmentService">
    <wsdl:operation name="ReadDocument">
      <wsdl:input wsaw:Action="http://ebus.onefox.nl/2009/2/4/AttachmentService/ReadDocument" name="ReadDocumentMsg" message="tns:ReadDocumentMsg"/>
      <wsdl:output wsaw:Action="http://ebus.onefox.nl/2009/2/4/AttachmentService/ReadDocumentResponse" name="AttachmentServiceReadDocumentResMsg" message="tns:AttachmentServiceReadDocumentResMsg"/>
    </wsdl:operation>
    <wsdl:operation name="WriteDocument">
      <wsdl:input wsaw:Action="http://ebus.onefox.nl/2009/2/4/AttachmentService/WriteDocument" name="WriteDocumentMsg" message="tns:WriteDocumentMsg"/>
      <wsdl:output wsaw:Action="http://ebus.onefox.nl/2009/2/4/AttachmentService/WriteDocumentResponse" name="AttachmentServiceWriteDocumentResMsg" message="tns:AttachmentServiceWriteDocumentResMsg"/>
    </wsdl:operation>
  </wsdl:portType>
  <wsdl:binding name="AttachmentServiceEndpoint" type="tns:AttachmentService">
    <wsp:PolicyReference URI="#AttachmentServiceEndpoint_policy"/>
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="ReadDocument">
      <soap:operation soapAction="http://ebus.onefox.nl/2009/2/4/AttachmentService/ReadDocument" style="document"/>
      <wsdl:input name="ReadDocumentMsg">
        <soap:header message="tns:ReadDocumentMsg_Headers" part="AuthInfo" use="literal"/>
        <soap:header message="tns:ReadDocumentMsg_Headers" part="Data" use="literal"/>
        <soap:body use="literal"/>
      </wsdl:input>
      <wsdl:output name="AttachmentServiceReadDocumentResMsg">
        <soap:header message="tns:AttachmentServiceReadDocumentResMsg_Headers" part="Result" use="literal"/>
        <soap:body use="literal"/>
      </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="WriteDocument">
      <soap:operation soapAction="http://ebus.onefox.nl/2009/2/4/AttachmentService/WriteDocument" style="document"/>
      <wsdl:input name="WriteDocumentMsg">
        <soap:header message="tns:WriteDocumentMsg_Headers" part="AuthInfo" use="literal"/>
        <soap:header message="tns:WriteDocumentMsg_Headers" part="Data" use="literal"/>
        <soap:body use="literal"/>
      </wsdl:input>
      <wsdl:output name="AttachmentServiceWriteDocumentResMsg">
        <soap:header message="tns:AttachmentServiceWriteDocumentResMsg_Headers" part="Result" use="literal"/>
        <soap:body use="literal"/>
      </wsdl:output>
    </wsdl:operation>
  </wsdl:binding>
</wsdl:definitions>


AttachmentService.xsd

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema elementFormDefault="qualified" targetNamespace="http://ebus.onefox.nl/2009/2/4/data" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://ebus.onefox.nl/2009/2/4/data">
  <xs:complexType name="AuthInfo">
    <xs:sequence>
      <xs:element name="Library" nillable="true" type="xs:string"/>
      <xs:element name="Username" nillable="true" type="xs:string"/>
      <xs:element name="Password" nillable="true" type="xs:string"/>
    </xs:sequence>
  </xs:complexType>
  <xs:element name="AuthInfo" nillable="true" type="tns:AuthInfo"/>
  <xs:complexType name="ReturnFields">
    <xs:sequence>
      <xs:element minOccurs="0" maxOccurs="unbounded" name="ReturnField" nillable="true" type="xs:string"/>
    </xs:sequence>
  </xs:complexType>
  <xs:element name="ReturnFields" nillable="true" type="tns:ReturnFields"/>
  <xs:complexType name="Result">
    <xs:sequence>
      <xs:element minOccurs="0" name="ErrCode" type="xs:int"/>
      <xs:element minOccurs="0" name="ErrDescription" nillable="true" type="xs:string"/>
    </xs:sequence>
  </xs:complexType>
  <xs:element name="Result" nillable="true" type="tns:Result"/>
  <xs:complexType name="Fields">
    <xs:sequence>
      <xs:element minOccurs="0" maxOccurs="unbounded" name="Field" nillable="true" type="tns:Field"/>
    </xs:sequence>
  </xs:complexType>
  <xs:element name="Fields" nillable="true" type="tns:Fields"/>
  <xs:complexType name="Field">
    <xs:sequence>
      <xs:element name="Name" nillable="true" type="xs:string"/>
      <xs:element name="Value" nillable="true" type="xs:string"/>
    </xs:sequence>
  </xs:complexType>
  <xs:element name="Field" nillable="true" type="tns:Field"/>
</xs:schema>


AttachmentService_1.xsd

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema elementFormDefault="qualified" targetNamespace="http://ebus.onefox.nl/2009/2/4" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://ebus.onefox.nl/2009/2/4">
  <xs:import schemaLocation="AttachmentService.xsd" namespace="http://ebus.onefox.nl/2009/2/4/data"/>
  <xs:element name="AuthInfo" nillable="true" type="q1:AuthInfo" xmlns:q1="http://ebus.onefox.nl/2009/2/4/data"/>
</xs:schema>

AttachmentService_1_2.xsd

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://schemas.microsoft.com/2003/10/Serialization/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://schemas.microsoft.com/2003/10/Serialization/">
  <xs:element name="anyType" nillable="true" type="xs:anyType"/>
  <xs:element name="anyURI" nillable="true" type="xs:anyURI"/>
  <xs:element name="base64Binary" nillable="true" type="xs:base64Binary"/>
  <xs:element name="boolean" nillable="true" type="xs:boolean"/>
  <xs:element name="byte" nillable="true" type="xs:byte"/>
  <xs:element name="dateTime" nillable="true" type="xs:dateTime"/>
  <xs:element name="decimal" nillable="true" type="xs:decimal"/>
  <xs:element name="double" nillable="true" type="xs:double"/>
  <xs:element name="float" nillable="true" type="xs:float"/>
  <xs:element name="int" nillable="true" type="xs:int"/>
  <xs:element name="long" nillable="true" type="xs:long"/>
  <xs:element name="QName" nillable="true" type="xs:QName"/>
  <xs:element name="short" nillable="true" type="xs:short"/>
  <xs:element name="string" nillable="true" type="xs:string"/>
  <xs:element name="unsignedByte" nillable="true" type="xs:unsignedByte"/>
  <xs:element name="unsignedInt" nillable="true" type="xs:unsignedInt"/>
  <xs:element name="unsignedLong" nillable="true" type="xs:unsignedLong"/>
  <xs:element name="unsignedShort" nillable="true" type="xs:unsignedShort"/>
  <xs:element name="char" nillable="true" type="tns:char"/>
  <xs:simpleType name="char">
    <xs:restriction base="xs:int"/>
  </xs:simpleType>
  <xs:element name="duration" nillable="true" type="tns:duration"/>
  <xs:simpleType name="duration">
    <xs:restriction base="xs:duration">
      <xs:pattern value="\-?P(\d*D)?(T(\d*H)?(\d*M)?(\d*(\.\d*)?S)?)?"/>
      <xs:minInclusive value="-P10675199DT2H48M5.4775808S"/>
      <xs:maxInclusive value="P10675199DT2H48M5.4775807S"/>
    </xs:restriction>
  </xs:simpleType>
  <xs:element name="guid" nillable="true" type="tns:guid"/>
  <xs:simpleType name="guid">
    <xs:restriction base="xs:string">
      <xs:pattern value="[\da-fA-F]{8}-[\da-fA-F]{4}-[\da-fA-F]{4}-[\da-fA-F]{4}-[\da-fA-F]{12}"/>
    </xs:restriction>
  </xs:simpleType>
  <xs:attribute name="FactoryType" type="xs:QName"/>
  <xs:attribute name="Id" type="xs:ID"/>
  <xs:attribute name="Ref" type="xs:IDREF"/>
</xs:schema>

AttachmentService_1_2_3.xsd

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema elementFormDefault="qualified" targetNamespace="http://ebus.onefox.nl/2009/2/4/attachment" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://ebus.onefox.nl/2009/2/4/attachment">
  <xs:import schemaLocation="AttachmentService.xsd" namespace="http://ebus.onefox.nl/2009/2/4/data"/>
  <xs:import schemaLocation="AttachmentService_1_2_3_4.xsd" namespace="http://schemas.microsoft.com/Message"/>
  <xs:complexType name="ReadDocumentMsg">
    <xs:sequence>
      <xs:element name="DocNumber" type="xs:int"/>
      <xs:element minOccurs="0" name="Version" type="xs:int"/>
      <xs:element name="Form" nillable="true" type="xs:string"/>
      <xs:element minOccurs="0" name="Checkout" type="xs:boolean"/>
      <xs:element minOccurs="0" name="ReturnFields" nillable="true" type="q1:ReturnFields" xmlns:q1="http://ebus.onefox.nl/2009/2/4/data"/>
    </xs:sequence>
  </xs:complexType>
  <xs:element name="ReadDocumentMsg" nillable="true" type="tns:ReadDocumentMsg"/>
  <xs:element name="ReadDocumentContent" type="q2:StreamBody" xmlns:q2="http://schemas.microsoft.com/Message"/>
  <xs:complexType name="ReadDocumentResultMsg">
    <xs:complexContent mixed="false">
      <xs:extension base="q3:Result" xmlns:q3="http://ebus.onefox.nl/2009/2/4/data">
        <xs:sequence>
          <xs:element minOccurs="0" name="DocNumber" type="xs:int"/>
          <xs:element minOccurs="0" name="Version" type="xs:int"/>
          <xs:element minOccurs="0" name="Fields" nillable="true" type="q3:Fields"/>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
  <xs:element name="ReadDocumentResultMsg" nillable="true" type="tns:ReadDocumentResultMsg"/>
  <xs:complexType name="WriteDocumentMsg">
    <xs:sequence>
      <xs:element name="DocNumber" type="xs:int"/>
      <xs:element minOccurs="0" name="Version" type="xs:int"/>
      <xs:element name="Form" nillable="true" type="xs:string"/>
      <xs:element minOccurs="0" name="Checkin" type="xs:boolean"/>
      <xs:element minOccurs="0" name="ReturnFields" nillable="true" type="q4:ReturnFields" xmlns:q4="http://ebus.onefox.nl/2009/2/4/data"/>
      <xs:element minOccurs="0" name="CreateNewVersion" type="xs:boolean"/>
    </xs:sequence>
  </xs:complexType>
  <xs:element name="WriteDocumentMsg" nillable="true" type="tns:WriteDocumentMsg"/>
  <xs:complexType name="WriteDocumentResultMsg">
    <xs:complexContent mixed="false">
      <xs:extension base="q5:Result" xmlns:q5="http://ebus.onefox.nl/2009/2/4/data">
        <xs:sequence>
          <xs:element minOccurs="0" name="DocNumber" type="xs:int"/>
          <xs:element minOccurs="0" name="Version" type="xs:int"/>
          <xs:element minOccurs="0" name="Fields" nillable="true" type="q5:Fields"/>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
  <xs:element name="WriteDocumentResultMsg" nillable="true" type="tns:WriteDocumentResultMsg"/>
</xs:schema>

AttachmentService_1_2_3_4.xsd

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema elementFormDefault="qualified" targetNamespace="http://schemas.microsoft.com/Message" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://schemas.microsoft.com/Message">
  <xs:simpleType name="StreamBody">
    <xs:restriction base="xs:base64Binary"/>
  </xs:simpleType>
</xs:schema>

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

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


From do-not-reply at jboss.com  Wed Jul  8 14:35:54 2009
From: do-not-reply at jboss.com (djkrite)
Date: Wed, 8 Jul 2009 14:35:54 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - org.jboss.ws.WSException: Cannot
	uniquely indentify operatio
Message-ID: <26909195.1247078154637.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hello, 

I'm running JBoss 4.2.3, Java 1.5, and Ubuntu. I am trying to call a Microsoft Exchange web service from a JSF web application. I have written other web service end points and have successfully built clients into my web application. I also use the same code for this client in a stand alone Java application to call the web service and everything works great, but for some reason I am getting this exception in my web app:

  | org.jboss.ws.WSException: Cannot uniquely indentify operation: {http://schemas.microsoft.com/exchange/services/2006/messages}Subscribe
  | 

The exception is thrown when the com.microsoft.schemas.exchange.services._2006.messages.ExchangeServicePortType subscribe method is called. Relevent part of the exception output:

  | 13:17:15,718 ERROR [STDERR] org.jboss.ws.WSException: Cannot uniquely indentify operation: {http://schemas.microsoft.com/exchange/services/2006/messages}Subscribe
  | 13:17:15,719 ERROR [STDERR] 	at org.jboss.ws.metadata.umdm.EndpointMetaData.getOperation(EndpointMetaData.java:417)
  | 13:17:15,719 ERROR [STDERR] 	at org.jboss.ws.core.CommonClient.getOperationMetaData(CommonClient.java:195)
  | 13:17:15,719 ERROR [STDERR] 	at org.jboss.ws.core.CommonClient.getOperationMetaData(CommonClient.java:184)
  | 13:17:15,719 ERROR [STDERR] 	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:309)
  | 13:17:15,719 ERROR [STDERR] 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
  | 13:17:15,719 ERROR [STDERR] 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
  | 13:17:15,719 ERROR [STDERR] 	at $Proxy101.subscribe(Unknown Source)
  | 

There is also is a bunch of output when the javax.xml.ws.Service object is created:

  | 13:17:13,438 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'The "xml:" Namespace'.
  | 13:17:13,438 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'The "xml:" Namespace'.
  | 13:17:13,438 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'This Version:'.
  | 13:17:13,439 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'April 19, 2006'.
  | 13:17:13,439 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'Description'.
  | 13:17:13,439 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'The namespace whose name is'.
  | 13:17:13,439 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'http://www.w3.org/XML/1998/namespace'.
  | 13:17:13,439 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'is bound by definition to'.
  | 13:17:13,439 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'the prefix '.
  | 13:17:13,439 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'xml:'.
  | 13:17:13,439 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'according to  '.
  | 13:17:13,439 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'Namespaces in XML,'.
  | 13:17:13,439 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'W3C Recommendation 14 Jan 1999'.
  | 13:17:13,439 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw '(and by '.
  | 13:17:13,439 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'Namespaces in XML 1.1'.
  | 13:17:13,439 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw ').'.
  | 13:17:13,439 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'Note that unlike all other XML namespaces, both the name '.
  | 13:17:13,439 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'and'.
  | 13:17:13,439 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'the prefix are specified; '.
  | 13:17:13,439 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'i.e., if you want XML 1.0 processors to recognize this namespace, you must use'.
  | 13:17:13,440 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'the reserved prefix '.
  | 13:17:13,440 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'xml:'.
  | 13:17:13,440 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw '.'.
  | 13:17:13,440 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'xml:lang'.
  | 13:17:13,440 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'and '.
  | 13:17:13,440 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'xml:space'.
  | 13:17:13,440 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'As of the last update of this document, the '.
  | 13:17:13,440 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'XML 1.0 (Third Edition) Specification'.
  | 13:17:13,440 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw '(and also the '.
  | 13:17:13,440 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'XML 1.1 Specification'.
  | 13:17:13,440 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw ')'.
  | 13:17:13,440 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'defines two attribute names in this namespace:'.
  | 13:17:13,440 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'xml:lang'.
  | 13:17:13,440 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'Designed for identifying'.
  | 13:17:13,440 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'the human language used in the scope of the element to which it's'.
  | 13:17:13,440 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'attached.'.
  | 13:17:13,440 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'xml:space'.
  | 13:17:13,440 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'Designed to express whether or not the document's creator wishes white'.
  | 13:17:13,441 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'space to be considered as significant in the scope of the element to which'.
  | 13:17:13,441 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'it's attached.'.
  | 13:17:13,441 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'xml:base'.
  | 13:17:13,441 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'The '.
  | 13:17:13,441 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'XML Base specification'.
  | 13:17:13,441 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'describes a facility, similar to that of HTML BASE, for defining base URIs for'.
  | 13:17:13,441 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'parts of XML documents.'.
  | 13:17:13,441 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'It defines a single attribute,'.
  | 13:17:13,441 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'xml:base'.
  | 13:17:13,441 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw ', and describes in'.
  | 13:17:13,441 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'detail the procedure for its use in processing relative URI refeferences.'.
  | 13:17:13,441 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'xml:id'.
  | 13:17:13,441 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'The '.
  | 13:17:13,441 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'xml:id specification'.
  | 13:17:13,442 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'defines'.
  | 13:17:13,442 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'a single attribute, '.
  | 13:17:13,442 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'xml:id'.
  | 13:17:13,442 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw ', known to be of type '.
  | 13:17:13,442 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'ID'.
  | 13:17:13,442 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'independently of any DTD or schema.'.
  | 13:17:13,442 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'Namespace change policy'.
  | 13:17:13,442 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'The '.
  | 13:17:13,442 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'XML Core Working'.
  | 13:17:13,442 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'Group'.
  | 13:17:13,442 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'reserves the right to'.
  | 13:17:13,442 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'bring additional names from this namespace into active use by'.
  | 13:17:13,442 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'providing definitions for them in new specifications or'.
  | 13:17:13,442 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'subsequent editions of existing specifications.  The Working'.
  | 13:17:13,442 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'Group may also make modifications to the definitions of the'.
  | 13:17:13,442 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'names already in use, although such changes will not normally'.
  | 13:17:13,442 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'change the well-formedness or validity of existing documents'.
  | 13:17:13,443 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'or significantly change their meaning.'.
  | 13:17:13,443 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'All changes to the use of this namespace will be achieved by'.
  | 13:17:13,443 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'the publication of documents governed by the W3C Process.'.
  | 13:17:13,443 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'Related Resources'.
  | 13:17:13,443 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'Section'.
  | 13:17:13,443 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw '2.10'.
  | 13:17:13,443 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'of the XML 1.0 specification describes the syntax and semantics of'.
  | 13:17:13,443 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'the '.
  | 13:17:13,443 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'xml:space'.
  | 13:17:13,443 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'attribute.'.
  | 13:17:13,443 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'Section'.
  | 13:17:13,443 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw '2.12'.
  | 13:17:13,443 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'of the XML 1.0 specification describes the syntax and semantics of'.
  | 13:17:13,443 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'the '.
  | 13:17:13,443 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'xml:lang'.
  | 13:17:13,443 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'attribute.'.
  | 13:17:13,444 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'An '.
  | 13:17:13,444 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'XML Schema'.
  | 13:17:13,444 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'fragment'.
  | 13:17:13,444 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'is available which constrains the syntax of '.
  | 13:17:13,444 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'xml:lang'.
  | 13:17:13,444 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw ', '.
  | 13:17:13,444 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'xml:space'.
  | 13:17:13,444 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw ','.
  | 13:17:13,444 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'xml:base'.
  | 13:17:13,444 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'and '.
  | 13:17:13,444 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'xml:id'.
  | 13:17:13,444 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'in the schema language defined by the '.
  | 13:17:13,444 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'XML Schema'.
  | 13:17:13,444 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'Recommendation, Second Edition,'.
  | 13:17:13,444 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'of 28 October 2004.'.
  | 13:17:13,444 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw '(An XML Schema'.
  | 13:17:13,444 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'fragment'.
  | 13:17:13,445 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'for the '.
  | 13:17:13,445 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'CR version'.
  | 13:17:13,445 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'of XML Schema'.
  | 13:17:13,445 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'is still available as well.)'.
  | 13:17:13,445 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'The value of the '.
  | 13:17:13,445 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'xml:lang'.
  | 13:17:13,445 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'attribute must be as specified'.
  | 13:17:13,445 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'by '.
  | 13:17:13,445 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'BCP 47'.
  | 13:17:13,445 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw ','.
  | 13:17:13,445 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'or be empty.'.
  | 13:17:13,445 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'The W3C '.
  | 13:17:13,445 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'XML Base'.
  | 13:17:13,445 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'specification for the '.
  | 13:17:13,445 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'xml:base'.
  | 13:17:13,445 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'attribute.'.
  | 13:17:13,445 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'The W3C '.
  | 13:17:13,446 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'xml:id'.
  | 13:17:13,446 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'specification for the '.
  | 13:17:13,446 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'xml:id'.
  | 13:17:13,446 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-character]::Message=s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'attribute.'.
  | 13:17:13,446 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-schema-ns]::Message=s4s-elt-schema-ns: The namespace of element 'html' must be from the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
  | 13:17:13,446 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-invalid]::Message=s4s-elt-invalid: Element 'html' is not a valid element in a schema document.
  | 13:17:13,447 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=src-import.2]::Message=src-import.2: The root element of document 'null' has to have the namespace name 'http://www.w3.org/2001/XMLSchema' and the local name 'schema'.
  | 

Has anyone ever built a Microsoft web service client on JBoss? Does anyone know what could be the issue?

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

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


From do-not-reply at jboss.com  Thu Jul  9 00:41:58 2009
From: do-not-reply at jboss.com (samwan808)
Date: Thu, 9 Jul 2009 00:41:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - resteasy-maven-import not found
Message-ID: <7701665.1247114518519.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Sorry everyone, since there is no REST group in this forum. 
And REST is kind of Web Service, therefore I think here is the best place I ask for help.

I am trying to install an resteasy example called "spring-hibernate", but I encountered  the following errors (can't download resteasy-maven-import)"

Hi,
I was trying to install an RESTeasy example, but got some errors.
This example I want to install:
/usr/resteasy-jaxrs-1.1.GA/examples/spring-hibernate

Getting the following errors:
spring-hibernate # !mv
mvn clean install
[INFO] Scanning for projects...
Downloading: http://download.java.net/maven/1/org.jboss.resteasy/poms/resteasy-maven-import-1.1.GA.pom
[INFO] Unable to find resource
'org.jboss.resteasy:resteasy-maven-import:pom:1.1.GA' in repository
java.net (http://download.java.net/maven/1)
Downloading: http://repo1.maven.org/maven2//org/jboss/resteasy/resteasy-maven-import/1.1.GA/resteasy-maven-import-1.1.GA.pom
[INFO] Unable to find resource
'org.jboss.resteasy:resteasy-maven-import:pom:1.1.GA' in repository
maven repo (http://repo1.maven.org/maven2/)
Downloading: http://repository.jboss.org/maven2/org/jboss/resteasy/resteasy-maven-import/1.1.GA/resteasy-maven-import-1.1.GA.pom
[INFO] Unable to find resource
'org.jboss.resteasy:resteasy-maven-import:pom:1.1.GA' in repository
jboss (http://repository.jboss.org/maven2)
Downloading: http://scannotation.sf.net/maven2/org/jboss/resteasy/resteasy-maven-import/1.1.GA/resteasy-maven-import-1.1.GA.pom
[INFO] Unable to find resource
'org.jboss.resteasy:resteasy-maven-import:pom:1.1.GA' in repository
scannotation (http://scannotation.sf.net/maven2)
Downloading: http://repo1.maven.org/maven2/org/jboss/resteasy/resteasy-maven-import/1.1.GA/resteasy-maven-import-1.1.GA.pom
[INFO] Unable to find resource
'org.jboss.resteasy:resteasy-maven-import:pom:1.1.GA' in repository
central (http://repo1.maven.org/maven2)
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).


Project ID: org.jboss.resteasy:resteasy-maven-import

Reason: POM 'org.jboss.resteasy:resteasy-maven-import' not found in
repository: Unable to download the artifact from any repository

 org.jboss.resteasy:resteasy-maven-import:pom:1.1.GA

from the specified remote repositories:
 central (http://repo1.maven.org/maven2),
 java.net (http://download.java.net/maven/1),
 scannotation (http://scannotation.sf.net/maven2),
 maven repo (http://repo1.maven.org/maven2/),
 jboss (http://repository.jboss.org/maven2)

 for project org.jboss.resteasy:resteasy-maven-import

Your help is very much appreciated.
Thanks



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

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


From do-not-reply at jboss.com  Thu Jul  9 07:18:22 2009
From: do-not-reply at jboss.com (nadiaebrahim)
Date: Thu, 9 Jul 2009 07:18:22 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WebService on ESB
Message-ID: <19435634.1247138302364.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi there all..

I am very new to the whole jboss esb thing..(I simply downloaded jbossesb-server zip file and unzipped it on my pc )
I am trying to implement a simple webservice on the esb and have used the webservice_producer sample code as given in the jbossesb-server download.(Have put this project in my eclipse as a dynamic web project) and then exported the war file to server/default/deploy directory.

I can see in the server log(below) that it does something with the war file.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
2009-07-09 09:02:33,210 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1021: [/webservice_producer] Configuration option 'com.sun.faces.displayConfiguration' - DISABLED
2009-07-09 09:02:33,210 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1021: [/webservice_producer] Configuration option 'com.sun.faces.validateXml' - DISABLED
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1021: [/webservice_producer] Configuration option 'com.sun.faces.verifyObjects' - DISABLED
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1021: [/webservice_producer] Configuration option 'com.sun.faces.forceLoadConfiguration' - DISABLED
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1021: [/webservice_producer] Configuration option 'com.sun.faces.enableHtmlTagLibValidator' - DISABLED
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1021: [/webservice_producer] Configuration option 'com.sun.faces.preferXHTML' - DISABLED
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1021: [/webservice_producer] Configuration option 'com.sun.faces.compressViewState' - ENABLED
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1021: [/webservice_producer] Configuration option 'com.sun.faces.compressJavaScript' - ENABLED
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1021: [/webservice_producer] Configuration option 'com.sun.faces.externalizeJavaScript' - DISABLED
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1021: [/webservice_producer] Configuration option 'com.sun.faces.sendPoweredByHeader' - ENABLED
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1021: [/webservice_producer] Configuration option 'com.sun.faces.enableJSStyleHiding' - DISABLED
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1021: [/webservice_producer] Configuration option 'com.sun.faces.enableScriptsInAttributeValues' - ENABLED
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1021: [/webservice_producer] Configuration option 'com.sun.faces.writeStateAtFormEnd' - ENABLED
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1021: [/webservice_producer] Configuration option 'com.sun.faces.enableLazyBeanValidation' - ENABLED
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1021: [/webservice_producer] Configuration option 'com.sun.faces.enabledLoadBundle11Compatibility' - DISABLED
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1021: [/webservice_producer] Configuration option 'com.sun.faces.enableRestoreView11Compatibility' - DISABLED
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1021: [/webservice_producer] Configuration option 'com.sun.faces.serializeServerState' - DISABLED
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1021: [/webservice_producer] Configuration option 'com.sun.faces.enableViewStateIdRendering' - ENABLED
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1021: [/webservice_producer] Configuration option 'com.sun.faces.registerConverterPropertyEditors' - DISABLED
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1021: [/webservice_producer] Configuration option 'com.sun.faces.disableUnicodeEscaping' - DISABLED
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1021: [/webservice_producer] Configuration option 'com.sun.faces.developmentMode' - DISABLED
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1018: [/webservice_producer] Configuration option 'javax.faces.STATE_SAVING_METHOD' set to 'server'
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1018: [/webservice_producer] Configuration option 'javax.faces.DEFAULT_SUFFIX' set to '.jsp'
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1018: [/webservice_producer] Configuration option 'com.sun.faces.numberOfViewsInSession' set to '15'
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1018: [/webservice_producer] Configuration option 'com.sun.faces.numberOfLogicalViews' set to '15'
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1018: [/webservice_producer] Configuration option 'com.sun.faces.injectionProvider' set to 'org.jboss.web.jsf.integration.injection.JBossInjectionProvider'
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1018: [/webservice_producer] Configuration option 'com.sun.faces.responseBufferSize' set to '1024'
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1018: [/webservice_producer] Configuration option 'com.sun.faces.clientStateWriteBufferSize' set to '8192'
2009-07-09 09:02:33,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] JSF1018: [/webservice_producer] Configuration option 'com.sun.faces.expressionFactory' set to 'com.sun.el.ExpressionFactoryImpl'
2009-07-09 09:02:33,216 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] No FacesServlet found in deployment descriptor - bypassing configuration
2009-07-09 09:02:33,216 DEBUG [org.jboss.web.tomcat.filters.ReplyHeaderFilter] Adding header name: X-Powered-By='Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0'
2009-07-09 09:02:33,218 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] Initialized: {WebApplication: /C:/java/esb/jbossesb-server-4.5.GA/server/default/tmp/deploy/tmp45897webservice_producer-exp.war/, URL: file:/C:/java/esb/jbossesb-server-4.5.GA/server/default/tmp/deploy/tmp45897webservice_producer-exp.war/, classLoader: java.net.FactoryURLClassLoader at 4cc70e:5031694} jboss.web:j2eeType=WebModule,name=//localhost/webservice_producer,J2EEApplication=none,J2EEServer=none
2009-07-09 09:02:33,218 DEBUG [org.jboss.web.WebModule] Started jboss.web.deployment:war=webservice_producer.war,id=-1402336082
2009-07-09 09:02:33,218 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.web.deployment:war=webservice_producer.war,id=-1402336082 dependent components: []
2009-07-09 09:02:33,223 DEBUG [org.jboss.deployment.MainDeployer] End deployment start on package: webservice_producer.war
2009-07-09 09:02:33,223 DEBUG [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/java/esb/jbossesb-server-4.5.GA/server/default/deploy/webservice_producer.war

----------------------------------------------------------------------------------------------------------------------------------------------------------
My problem is that when I deploy to normal jboss application server ,I would be able to see the wsdl url from the below.
http://localhost:8080/jbossws/services

I see nothing on this url know.
I am also confused at to what the url  http://localhost:8080/contract means.

I have just copied the jbossesb-server to my directory.I have succesfully implemented a customlistener with the jbossesb-server install..

Not sure what I am doing wrong with the webservice ???
can somebody please assist.

Thanks
Nadia 


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

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



From do-not-reply at jboss.com  Thu Jul  9 14:00:11 2009
From: do-not-reply at jboss.com (jdriver)
Date: Thu, 9 Jul 2009 14:00:11 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - missing ant.properties.examples
Message-ID: <27432787.1247162411794.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

In the installation instructions for 3.0.3 GA it says to first copy ant.properties.examples to ant.properties, but the file does not exist.

I have JBoss 4.2.3 and JBossWS 3.0.3 native. I have built an annotated EJB3 project and put the jar file in the deploy directory as instructed in the QuickStart guide. But then I look and there are no registered endpoints.

When I start the server I see my service in the log:
12:15:34,432 INFO  [EJBContainer] STOPPED EJB: com.sample.labor.management.ejb.LaborServiceBean ejbName: LaborServiceBean
12:15:34,432 WARN  [JmxKernelAbstraction] jboss.j2ee:jar=LaborService.jar,name=LaborServiceBean,service=EJB3 is not registered
12:15:34,432 INFO  [TomcatDeployer] undeploy, ctxPath=/LaborService, warUrl=.../tmp/deploy/LaborService.jar13106.war/
12:15:34,432 INFO  [DefaultEndpointRegistry] remove: jboss.ws:context=LaborService,endpoint=LaborServiceBean




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

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


From do-not-reply at jboss.com  Fri Jul 10 06:00:22 2009
From: do-not-reply at jboss.com (a.fluegge)
Date: Fri, 10 Jul 2009 06:00:22 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBoss 5.0.1.GA, JBossWS 3.0.5,
	JDK 1.6 - java.lang.Unsupport
Message-ID: <1476791.1247220022432.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hello!

I'm trying to call a simple web service with following configuration: 5.0.1.GA, JBossWS 3.0.5, JDK 1.6.0_14. Details below.

Callin the service gets the following exception:


  | 11:33:16,163 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
  | java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
  | 	at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:445)
  | 	at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:82)
  | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:215)
  | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:193)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:455)
  | 	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.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85)
  | 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
  | 	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:191)
  | 	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
  | 	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
  | 	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
  | 	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
  | 	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:158)
  | 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
  | 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
  | 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
  | 	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(Thread.java:619)
  | 

I suppose that the SOAPMessage class comes from the JDK 1.6 which is incompatible with the one from JBossWS (in jbossws-native-saaj.jar). The jar file is located in the <JBOSS_HOME>/lib/endorsed dir. All suggestions to solve this problem are to copy the jar files to the endorsed dir, but they are already there!

Can anybody help me?

Thanks,
Andreas


This is the source:


  | package test;
  | 
  | import javax.ejb.Stateless;
  | import javax.jws.WebMethod;
  | import javax.jws.WebService;
  | 
  | import org.apache.commons.logging.Log;
  | import org.jboss.seam.annotations.Logger;
  | 
  | @Stateless
  | @WebService(name = "testService", serviceName = "testService")
  | public class TestService implements TestServiceRemote {
  | 
  | 	@Logger
  | 	private Log	log;
  | 
  | 	@WebMethod
  | 	public String testService(String name) {
  | 		String txt = "testService:" + name;
  | 
  | 		log.info("testService:" + name);
  | 
  | 		return txt;
  | 	}
  | }
  | 
  | package test;
  | 
  | import javax.ejb.Remote;
  | import javax.jws.WebMethod;
  | 
  | @Remote
  | public interface TestServiceRemote {
  | 	@WebMethod
  | 	public String testService(String name);
  | }
  | 

Deployment is no problem, calling the http:.../TestService?wsdl URL gets the following:


  | <definitions name='testService' targetNamespace='http://test/' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://test/' xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
  |  <types>
  |   <xs:schema targetNamespace='http://test/' version='1.0' xmlns:tns='http://test/' xmlns:xs='http://www.w3.org/2001/XMLSchema'>
  |    <xs:element name='testService' type='tns:testService'/>
  |    <xs:element name='testServiceResponse' type='tns:testServiceResponse'/>
  |    <xs:complexType name='testService'>
  |     <xs:sequence>
  |      <xs:element minOccurs='0' name='arg0' type='xs:string'/>
  |     </xs:sequence>
  | 
  |    </xs:complexType>
  |    <xs:complexType name='testServiceResponse'>
  |     <xs:sequence>
  |      <xs:element minOccurs='0' name='return' type='xs:string'/>
  |     </xs:sequence>
  |    </xs:complexType>
  |   </xs:schema>
  |  </types>
  |  <message name='testService_testServiceResponse'>
  | 
  |   <part element='tns:testServiceResponse' name='testServiceResponse'></part>
  |  </message>
  |  <message name='testService_testService'>
  |   <part element='tns:testService' name='testService'></part>
  |  </message>
  |  <portType name='testService'>
  |   <operation name='testService' parameterOrder='testService'>
  |    <input message='tns:testService_testService'></input>
  |    <output message='tns:testService_testServiceResponse'></output>
  | 
  |   </operation>
  |  </portType>
  |  <binding name='testServiceBinding' type='tns:testService'>
  |   <soap:binding style='document' transport='http://schemas.xmlsoap.org/soap/http'/>
  |   <operation name='testService'>
  |    <soap:operation soapAction=''/>
  |    <input>
  |     <soap:body use='literal'/>
  |    </input>
  | 
  |    <output>
  |     <soap:body use='literal'/>
  |    </output>
  |   </operation>
  |  </binding>
  |  <service name='testService'>
  |   <port binding='tns:testServiceBinding' name='testServicePort'>
  |    <soap:address location='http://127.0.0.1:8080/spaceserver-spaceserver/TestService'/>
  |   </port>
  | 
  |  </service>
  | </definitions>
  | 

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

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


From do-not-reply at jboss.com  Fri Jul 10 08:45:24 2009
From: do-not-reply at jboss.com (jdriver)
Date: Fri, 10 Jul 2009 08:45:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: missing ant.properties.examples
Message-ID: <7987217.1247229924364.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I was able to get this to work. I didn't have to run any ant script. The Users Guide had a more complete java source listing and after adding the EJB3 Remote interface the the service deployed correctly.

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

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


From do-not-reply at jboss.com  Fri Jul 10 11:52:01 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 10 Jul 2009 11:52:01 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBoss 5.0.1.GA, JBossWS 3.0.5,
	JDK 1.6 - java.lang.Unsup
Message-ID: <33119264.1247241121630.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Did you download the JDK6 variant of JBoss AS 5.0.1.GA? It already has the necessary jar files in the endorsed directory to avoid this issue:

lib/endorsed/activation.jar
lib/endorsed/jaxb-api.jar
lib/endorsed/jbossws-native-jaxrpc.jar
lib/endorsed/jbossws-native-jaxws-ext.jar
lib/endorsed/jbossws-native-jaxws.jar
lib/endorsed/jbossws-native-saaj.jar
lib/endorsed/resolver.jar
lib/endorsed/serializer.jar
lib/endorsed/stax-api.jar
lib/endorsed/xalan.jar
lib/endorsed/xercesImpl.jar

A search of "setProperty must be overridden" should yield several posts discussing this. (It it should, if search was not broke - at this time only your post shows up.)

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

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


From do-not-reply at jboss.com  Fri Jul 10 15:52:38 2009
From: do-not-reply at jboss.com (kennypollito1)
Date: Fri, 10 Jul 2009 15:52:38 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Deploy from Jdeveloper to JBOSS failed
Message-ID: <23105335.1247255558592.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi,

I have a Web Service project that works fine in jdeveloper 10.1.3.3 and the OC4J. But when I try to deploy it to JBOSS, I got error. Would someone help me out on this? How to do that? Is it required any special step?

Thanks

Kenny

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

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


From do-not-reply at jboss.com  Fri Jul 10 23:21:03 2009
From: do-not-reply at jboss.com (Oberiko)
Date: Fri, 10 Jul 2009 23:21:03 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Streamlined tutorial on JBossWS w/
	policies (WS-RM)?
Message-ID: <22635764.1247282463817.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Still banging my head on this one.  Could anyone let me know if the server code I have posted is valid?  Is the @Policy annotation compatible with WS-RM?

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

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


From do-not-reply at jboss.com  Sat Jul 11 18:34:07 2009
From: do-not-reply at jboss.com (bcraig_2000)
Date: Sat, 11 Jul 2009 18:34:07 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - json binding error Jboss 4.3
Message-ID: <23904402.1247351647914.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I am writing a client and running wsrunclient that will call a service from a .net application. The wsdl for the .net app contains bindings for soap, json and xml. Even though the binding for SOAP is to be used, an exception is raised when it detects that the wsdl contains a json binding and cannot handle the binding. Is there a way to tell the client to ignore the json binding and only deal with the soap info?

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

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


From do-not-reply at jboss.com  Mon Jul 13 04:18:56 2009
From: do-not-reply at jboss.com (a.fluegge)
Date: Mon, 13 Jul 2009 04:18:56 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBoss 5.0.1.GA, JBossWS 3.0.5,
	JDK 1.6 - java.lang.Unsup
Message-ID: <26824627.1247473136842.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Yes, I'm already using the JDK6 version of JBoss. And in fact, there are no search results concerning this issue. :-( 

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

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


From do-not-reply at jboss.com  Mon Jul 13 11:02:39 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 13 Jul 2009 11:02:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBoss 5.0.1.GA, JBossWS 3.0.5,
	JDK 1.6 - java.lang.Unsup
Message-ID: <25207671.1247497359164.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Perhaps a stray jaxws library is being picked up. Try adding -verbose:class to the JAVA_OPTS in the run script. This option causes the JVM to print the location of each class loaded. Look for where the SOAPMessage class gets loaded. By the way, this option generate a lot of output - you better redirect both stdout and stderr to a file.

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

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


From do-not-reply at jboss.com  Mon Jul 13 12:35:09 2009
From: do-not-reply at jboss.com (a.fluegge)
Date: Mon, 13 Jul 2009 12:35:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBoss 5.0.1.GA, JBossWS 3.0.5,
	JDK 1.6 - java.lang.Unsup
Message-ID: <24574609.1247502909993.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Thanks for your answer!

I could solve this issue, although it is a strange behaviour. Testing the web service on another system running Windows XP works fine (I'm using Vista!, didn't mind it matters).

The solution under Vista is to copy all JARs from <JBOSS_HOME>/lib endorsed to <JAVA_HOME>/jre/lib/endorsed (I had to create this directory).

I don't know if the OS is the real reason, but now it works!

Thank you very much!

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

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


From do-not-reply at jboss.com  Mon Jul 13 13:40:01 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 13 Jul 2009 13:40:01 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBoss 5.0.1.GA, JBossWS 3.0.5,
	JDK 1.6 - java.lang.Unsup
Message-ID: <30974195.1247506801462.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I'm using Vista and don't have this problem. Copying the JARs to the JRE's endorsed directory might fix this issue but it could cause you grief with other Java apps. I still think you have some stray jar files that were being picked up by your JVM (you don't have CLASSPATH set, do you?), but -verbose:class will help you locate them.

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

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


From do-not-reply at jboss.com  Tue Jul 14 09:35:16 2009
From: do-not-reply at jboss.com (Oberiko)
Date: Tue, 14 Jul 2009 09:35:16 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Streamlined tutorial on JBossWS w/
	policies (WS-RM)?
Message-ID: <22241156.1247578516826.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Finally got it.  I wrote up a fairly detailed explanation how on Google Knol if it's of use to anyone.

http://knol.google.com/k/neil-mcfarlane/creating-your-first-web-services-in-java/

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

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


From do-not-reply at jboss.com  Tue Jul 14 13:31:32 2009
From: do-not-reply at jboss.com (cracru)
Date: Tue, 14 Jul 2009 13:31:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - @XmlSeeAlso usage
Message-ID: <31782380.1247592692110.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Should I expect @XmlSeeAlso to work on an SLSB/WS SEImpl?


  | @Stateless
  | @WebService()
  | @XmlSeeAlso({Wakeboard.class, WakeboardBinding.class, Tower.class})  
  | public class WakeRider 
  | {
  |        ...
  | }
  | 

I am having no luck in getting the additional classes added to the generated WSDL.

I am using JBoss 4.2.3.GA w/ JBossWS 3.1.1.GA Native.

Thanks, Craig

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

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


From do-not-reply at jboss.com  Tue Jul 14 14:16:08 2009
From: do-not-reply at jboss.com (cracru)
Date: Tue, 14 Jul 2009 14:16:08 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: @XmlSeeAlso usage
Message-ID: <9093755.1247595368243.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I just tested, and it works with: JBoss 4.2.3.GA + JBossWS 3.1.1.GA Metro.

So I guess the question really is: Is it supposed to work in 3.1.1.GA Native?

Thanks, Craig.

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

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


From do-not-reply at jboss.com  Wed Jul 15 01:57:10 2009
From: do-not-reply at jboss.com (sandeep.athira)
Date: Wed, 15 Jul 2009 01:57:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Abstract class as input Parameter
	in WebService
Message-ID: <20396921.1247637430498.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

HI,
  I also have a similar problem with my webservice..
how did u solve the issue..

Thanks and Regards
Sandeep

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

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


From do-not-reply at jboss.com  Wed Jul 15 07:55:31 2009
From: do-not-reply at jboss.com (jaro777)
Date: Wed, 15 Jul 2009 07:55:31 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Certification issue when moved web
	service from war to ejb3
Message-ID: <5778137.1247658931938.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hello @,

  I have following  scenario:

We have war and ejb3 project deployed within ear. Web layer access .Net web service over ssl. Keystore/trustore is defined in Ear/War/WB-INF/jboss-wsse-client.xml. It works nice.

I want to move the logic which calls web service into ejb (and call the ejb in web layer). I moved jboss-wsse-client.xml into Ear/Ejb/META-INF and also corresponding keystore and trustore file + I refactored code.

Unfortunately I get "No certificate found" error when I try to access web service. Even there is no reference to jboss-wsse-client.xml file in server.log after refactoring - like it is ignored totally.

Any idea what is wrong?

Jboss: 4.2.3
WS: 
jbossws-3.0.1-native-2.0.4.GA (build=200803312
 044)

Thanks
jaro

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

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


From do-not-reply at jboss.com  Wed Jul 15 08:51:16 2009
From: do-not-reply at jboss.com (jpredpos)
Date: Wed, 15 Jul 2009 08:51:16 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WS differents ports
Message-ID: <15578077.1247662276766.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi, 

Is possible to open two differents ports for WS REST? 
for example: 
http:://localhost:8080/admin/reloadSomething
and
http://localhost:8082/users/doSomething

thanks 

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

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


From do-not-reply at jboss.com  Wed Jul 15 10:33:00 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Wed, 15 Jul 2009 10:33:00 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS differents ports
Message-ID: <11797728.1247668380844.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

You can open multiple HTTP ports be defining additional Connector entries in the server.xml file. You did not mention the JBoss AS version so I will leave it to you to locate the file (there is only one) since its location seems to change with every release. 

I haven't tried this specifically with web services, but it should work. 

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

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


From do-not-reply at jboss.com  Wed Jul 15 11:16:15 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 15 Jul 2009 11:16:15 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Newlines/spaces in SOAPMessage
Message-ID: <5211266.1247670975236.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

This reminds me of something related to CR/LF when dealing with signatures.
Where do you get the soap elements content from? are you reading them from file?


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

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


From do-not-reply at jboss.com  Wed Jul 15 11:19:02 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 15 Jul 2009 11:19:02 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Using SUN's SAAJ implementation
Message-ID: <22406155.1247671142694.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

See my reply on the other thread you opened on this.
Besides that, you can't use Sun's SAAJ implementation directly on JBoss AS with JBossWS-Native.
If you really want to get rid of jbossws-native-saaj anyway, you can try JBossWS-CXF and/or JBossWS-Metro.

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

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


From do-not-reply at jboss.com  Wed Jul 15 11:34:57 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 15 Jul 2009 11:34:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: sending Soap message with timeout
Message-ID: <5536109.1247672097978.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

The point here is SAAJ does not define an API for setting the timeout directly using the SOAPConnection. So you need to use some kind of proprietary stuff.
Forget about Axis, you can't use it with JBossWS. Take a look at the JBossWS-Native (I assume that's what you're using) org.jboss.ws.core.client.HTTPRemotingConnection that is used under the hood by org.jboss.ws.core.soap.SOAPConnectionImpl (which in turn is the JBossWS-Native impl of SOAPConnection).
HTTPRemotingConnection basically receives and endpoint object which can be an instance of EndpointInfo. That can contain a properties map including org.jboss.ws.timeout property. Setting that, you should be able to basically achieve what you get setting the same prop in the request context when performing a call through a ws port.


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

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


From do-not-reply at jboss.com  Wed Jul 15 11:39:49 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 15 Jul 2009 11:39:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBoss WS Pojos endpoint
	authentication
Message-ID: <11159015.1247672389354.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

https://jira.jboss.org/jira/browse/JBWS-2697

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

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


From do-not-reply at jboss.com  Wed Jul 15 11:48:36 2009
From: do-not-reply at jboss.com (sbutt)
Date: Wed, 15 Jul 2009 11:48:36 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: sending Soap message with timeout
Message-ID: <11693609.1247672916925.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Thanks for your reply but i solved that problem using Jboss ESB's internal HTTP router class: org.jboss.soa.esb.actions.routing.http.HttpRouter

One can send soap messages with it as well, and set connection/socket Timeouts (http properties) etc as well.

Thanks.

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

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


From do-not-reply at jboss.com  Wed Jul 15 11:58:49 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 15 Jul 2009 11:58:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossAS 5.1.0.GA & 3.1.2.GA &
	META-INF
Message-ID: <6631819.1247673529892.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

As a reference, I'd suggest you to take a look at the jbossws wsse sample artifacts that are built for AS5 in jbossws testsuite. Basically AS 5 is strict to standards regarding where to load resources from.

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

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


From do-not-reply at jboss.com  Wed Jul 15 12:06:45 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 15 Jul 2009 12:06:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: DOM API on SOAPElementImpl causes
	NotImplementedExceptio
Message-ID: <2496875.1247674005194.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

get/setTextContent has recently been implemented in NodeImpl. Something else is simply not implemented yet. Feel free to create a jira issue for this and link that here (btw this is an easy chance for contributing adding a small patch ;-) ).

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

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


From do-not-reply at jboss.com  Wed Jul 15 12:11:03 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 15 Jul 2009 12:11:03 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WebService Client with MTOM
Message-ID: <7132682.1247674263720.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Despite having a basic implementation of WS-Policy, JBossWS-Native does not support policies for setting MTOM. This means you need to manually set mtom on client side (please refer to the documentation) or switch to JBossWS-CXF / JBossWS-Metro.

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

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


From do-not-reply at jboss.com  Wed Jul 15 12:15:42 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 15 Jul 2009 12:15:42 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: org.jboss.ws.WSException: Cannot
	uniquely indentify oper
Message-ID: <10401625.1247674542019.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Sure, lots of people use JBossWS as client of Microsoft ws endpoints.
This said, there might be something weird with the wsdl. Can you try posting it?

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

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


From do-not-reply at jboss.com  Wed Jul 15 12:17:39 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 15 Jul 2009 12:17:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: missing ant.properties.examples
Message-ID: <11667970.1247674659454.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Btw there's been a timeframe in the past where the ant.properties.example was missing (you had a custom ant.properties instead). This has already been fixed anyway.

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

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


From do-not-reply at jboss.com  Wed Jul 15 12:20:33 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 15 Jul 2009 12:20:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBoss 5.0.1.GA, JBossWS 3.0.5,
	JDK 1.6 - java.lang.Unsup
Message-ID: <24345961.1247674833905.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Thanks Peter for spreading the right directions on this topic.

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

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


From do-not-reply at jboss.com  Mon Jul 20 11:12:23 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 20 Jul 2009 11:12:23 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem with
	((StubExt)port).setSecurityConfig(_security
Message-ID: <8460365.1248102743275.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Please do not double post. Continued at
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244597

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

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


From do-not-reply at jboss.com  Mon Jul 20 08:14:56 2009
From: do-not-reply at jboss.com (vesposito)
Date: Mon, 20 Jul 2009 08:14:56 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Abstract class as input Parameter
	in WebService
Message-ID: <8475791.1248092096539.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi,
I've not found a solution to problem, so I cannot suggest you the solution. I was waiting for an answer but maybe this issue had not been solved.

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

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


From do-not-reply at jboss.com  Mon Jul 20 09:01:43 2009
From: do-not-reply at jboss.com (SARA1232007)
Date: Mon, 20 Jul 2009 09:01:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Urgent:ask for jar file
Message-ID: <10460488.1248094903670.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi,

Does anyone knows what is the name of jar file have the org.jboss.example.ws.client.ExampleService_PortType class and org.jboss.example.ws.client.ExampleService_Service_Impl class included? And, which software is the jar file included?

Thanks.

Sara

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

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


From do-not-reply at jboss.com  Mon Jul 20 06:25:45 2009
From: do-not-reply at jboss.com (yoshi96)
Date: Mon, 20 Jul 2009 06:25:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Problem with
	((StubExt)port).setSecurityConfig(_securityURL.
Message-ID: <22690449.1248085545431.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi!

Im a newbe trying to complete a web service client tutorial.

I ran into a

java.lang.ClassCastException: $Proxy30 cannot be cast to org.jboss.ws.core.StubExt

when trying to execute line

((StubExt)port).setSecurityConfig(_securityURL.toExternalForm())

The _securityURL contains a URL to the jboss-wsse-client.xml. I cant find what is wrong and would appreciate any pointers or reference to where I can find out what is going wrong. Also please if I am in the wrong forum where should I go?

Thanks in advance

Yoshi

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

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


From do-not-reply at jboss.com  Fri Jul 17 14:48:20 2009
From: do-not-reply at jboss.com (tdgsairam)
Date: Fri, 17 Jul 2009 14:48:20 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - How to make JBossWS @webparam required
Message-ID: <26311757.1247856500452.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hello,

Using the following.
1) bottom-up approach writing service first and generating WSDL.
2) JBoss Native Webservice
3) JBOSS App Server 4.3GA_CP04

Question: In my service implementation @webparam is by default optional for java class types. how can make them required.

Please let me know

Thanks
Sai

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

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


From do-not-reply at jboss.com  Sun Jul 19 12:38:41 2009
From: do-not-reply at jboss.com (nikhilm)
Date: Sun, 19 Jul 2009 12:38:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JAXWS on JBoss 4.2.2
Message-ID: <14726377.1248021521158.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hello all

I have been trying to develop and deply a JAXWS building over the sample presented here (http://www.javabeat.net/articles/print.php?article_id=40) 

I am using Eclipse Version: 3.4.1 (ganymede) to develop this and with jdk1.5.0_17.

Interesting wheny I am trying to deploy it on Jboss-4.0.4, It gets deployed fien and i cann see the wsdl.. but when I try to deploy it on Jboss-4.2.2.GA, I get the error mentioned below, Any pointers to get over this..?
Is there something which the example misses out or did got few jars placed wrong?

--- log ----
org.jboss.xb.binding.JBossXBRuntimeException: Failed to create a new SAX parser
	at org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryImpl.newUnmarshaller(UnmarshallerFactory.java:100)
	at org.jboss.ws.metadata.config.JBossWSConfigFactory.parse(JBossWSConfigFactory.java:76)
	at org.jboss.ws.metadata.config.JBossWSConfigFactory.getConfig(JBossWSConfigFactory.java:134)
	at org.jboss.ws.metadata.umdm.EndpointMetaData.initEndpointConfig(EndpointMetaData.java:704)
	at org.jboss.ws.metadata.umdm.EndpointMetaData.getConfig(EndpointMetaData.java:667)
	at org.jboss.ws.metadata.umdm.ParameterMetaData.getPartName(ParameterMetaData.java:439)
	at org.jboss.ws.metadata.umdm.ParameterMetaData.toString(ParameterMetaData.java:565)
	at java.lang.String.valueOf(String.java:2827)
	at java.lang.StringBuilder.append(StringBuilder.java:115)
	at org.jboss.ws.metadata.umdm.OperationMetaData.setReturnParameter(OperationMetaData.java:346)
	at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.createResponseWrapper(JAXWSMetaDataBuilder.java:403)
	at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.processWebMethod(JAXWSMetaDataBuilder.java:612)
	at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.processWebMethods(JAXWSMetaDataBuilder.java:874)
	at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:140)
	at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:50)
	at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderJSE.buildMetaData(JAXWSMetaDataBuilderJSE.java:63)
	at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.create(UnifiedMetaDataDeploymentAspect.java:66)
	at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
	at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97)
	at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90)
	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy45.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.GeneratedMethodAccessor21.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy9.deploy(Unknown Source)
	at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
	at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610)
	at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
	at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
	at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
Caused by: org.jboss.xb.binding.JBossXBException: Failed to create a new SAX parser
	at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.(SaxJBossXBParser.java:96)
	at org.jboss.xb.binding.UnmarshallerImpl.(UnmarshallerImpl.java:55)
	at org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryImpl.newUnmarshaller(UnmarshallerFactory.java:96)
	... 47 more
Caused by: javax.xml.parsers.ParserConfigurationException: Feature 'http://apache.org/xml/features/xinclude' is not recognized.
	at org.apache.xerces.jaxp.SAXParserFactoryImpl.newSAXParser(Unknown Source)
	at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.(SaxJBossXBParser.java:92)
	... 49 more

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

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

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


From do-not-reply at jboss.com  Fri Jul 17 04:30:35 2009
From: do-not-reply at jboss.com (seventy8)
Date: Fri, 17 Jul 2009 04:30:35 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WS-Client using wsse signature and ssl
Message-ID: <30289512.1247819435213.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi everybody,

I want to implement a ws-client which uses wsse signature and ssl.
There is no problem if I use either wsse signature or ssl.

If only wsse signature is enabled the message is signed correctly. But if I switch to the https service address, I receive an exception saying <wsse:Security> is missing.

Regards

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

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


From do-not-reply at jboss.com  Thu Jul 16 13:48:15 2009
From: do-not-reply at jboss.com (jlankfo)
Date: Thu, 16 Jul 2009 13:48:15 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - NotImplementedException
Message-ID: <1558305.1247766495401.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I am trying to invoke a client handler and add headers to the soap message before they leave. I am getting a NotImplementedException on the following line of code

  | 	         SOAPEnvelope myEnvelope = (SOAPEnvelope) soapMsgContext.getMessage().getSOAPPart().getEnvelope();
  | 
  | 

I have added the following jars to endorsed/lib but to no avail: jaxws-rt.jar, jbossws-native-jaxrpc.jar, jbossws-native-jaxws.jar, jbossws-native-jaxws-ext.jar, jaxb-api.jar, jbossws-native-saaj.jar. If the appendChild method is not implemented am i using the wrong version of one of the jars? If not is there any way to implement it. I need to attach something to the context so that it persists throughout all the services, thats why i was attempting to use the headers. This code also works fine on the server side handler. If it is helpful i am attaching the handler in the following way:


  | CustomerService cs = new CustomerService();
  | 	    customer = cs.getCustomerPort();
  | 	    
  | 	    
  | 	    List<Handler> handlerChain = 
  | 	        ((BindingProvider)customer).getBinding().getHandlerChain();
  | 	    JaxWSClientHandler sh = new JaxWSClientHandler(new QName("http://wtp/","lookupCustomer"));
  | 	    List<Handler> new_handlerChain = new ArrayList<Handler>();
  | 	    new_handlerChain.add(sh);
  | 	       ((BindingProvider)customer).getBinding().setHandlerChain(new_handlerChain);
  | 

org.jboss.util.NotImplementedException
  | 	at org.jboss.ws.core.soap.SOAPPartImpl.appendChild(SOAPPartImpl.java:298)
  | 	at com.sun.xml.bind.marshaller.SAX2DOMEx.startElement(SAX2DOMEx.java:176)
  | 	at com.sun.xml.ws.message.AbstractMessageImpl.writeTo(AbstractMessageImpl.java:158)
  | 	at com.sun.xml.ws.message.AbstractMessageImpl.readAsSOAPMessage(AbstractMessageImpl.java:193)
  | 	at com.sun.xml.ws.handler.SOAPMessageContextImpl.getMessage(SOAPMessageContextImpl.java:79)
  | 	at com.ibm.management.soa.agent.genericdc.JaxWSTracker.attachCorrelatorToMessage(JaxWSTracker.java:146)
  | 	at com.ibm.management.soa.agent.ITMTracker.clientRequest(ITMTracker.java:424)
  | 	at com.ibm.management.soa.agent.GenericTracker.dispatch(GenericTracker.java:300)
  | 	at com.ibm.management.soa.agent.GenericTracker.invoke(GenericTracker.java:257)
  | 	at com.ibm.management.soa.agent.genericdc.JaxWSClientHandler.handleMessage(JaxWSClientHandler.java:115)
  | 	at com.ibm.management.soa.agent.genericdc.JaxWSClientHandler.handleMessage(JaxWSClientHandler.java:1)
  | 	at com.sun.xml.ws.handler.HandlerProcessor.callHandleMessage(HandlerProcessor.java:292)
  | 	at com.sun.xml.ws.handler.HandlerProcessor.callHandlersRequest(HandlerProcessor.java:133)
  | 	at com.sun.xml.ws.handler.ClientSOAPHandlerTube.callHandlersOnRequest(ClientSOAPHandlerTube.java:138)
  | 	at com.sun.xml.ws.handler.HandlerTube.processRequest(HandlerTube.java:116)
  | 	at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
  | 	at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
  | 	at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
  | 	at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
  | 	at com.sun.xml.ws.client.Stub.process(Stub.java:248)
  | 	at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:135)
  | 	at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:109)
  | 	at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
  | 	at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118)
  | 	at $Proxy197.lookupCustomerInNewDB2(Unknown Source)
  | 	at com.ibm.wsm.samples.retail.lc.Customer.lookupCustomer(Customer.java:134)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.wsf.container.jboss50.invocation.InvocationHandlerJSE.invoke(InvocationHandlerJSE.java:106)
  | 	at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:219)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:474)
  | 	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.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85)
  | 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
  | 	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:191)
  | 	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
  | 	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
  | 	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
  | 	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
  | 	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:158)
  | 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
  | 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
  | 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
  | 	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(Thread.java:619)

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

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


From do-not-reply at jboss.com  Thu Jul 16 12:16:50 2009
From: do-not-reply at jboss.com (cesaralbloz)
Date: Thu, 16 Jul 2009 12:16:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Failed to authenticate principal=null,
	securityDomain=jmx-co
Message-ID: <9705859.1247761010989.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I obtain the following exception when deploying a jboss services that tries to create a JMS topic. The system has jmx-invoker protected as detailed the JBoss manual (jmx-console secure domain that uses user/role files)


  | ...
  | 2009-07-16 18:06:05,312 DEBUG [org.jboss.mq.pm.jdbc2.PersistenceManager] Resolving uncommited TXS
  | 2009-07-16 18:06:05,328 DEBUG [org.jboss.mq.pm.jdbc2.PersistenceManager] Started jboss.mq:service=PersistenceManager
  | 2009-07-16 18:06:05,328 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.mq:service=PersistenceManager dependent components: [ObjectName: jboss.mq:service=DestinationManager
  |   State: CREATED
  |   I Depend On:
  |     jboss.mq:service=MessageCache
  |     jboss.mq:service=PersistenceManager
  |     jboss.mq:service=StateManager
  |     jboss.mq:service=ThreadPool
  |     jboss:service=Naming
  |   Depends On Me:
  |     com.alu.cnm.cnbi.cfma.simulator:service=SimulatorService
  |     jboss.mq.destination:service=Topic,name=testTopic
  |     jboss.mq.destination:service=Topic,name=securedTopic
  |     jboss.mq.destination:service=Topic,name=testDurableTopic
  |     jboss.mq.destination:service=Queue,name=testQueue
  |     jboss.mq.destination:service=Queue,name=A
  |     jboss.mq.destination:service=Queue,name=B
  |     jboss.mq.destination:service=Queue,name=C
  |     jboss.mq.destination:service=Queue,name=D
  |     jboss.mq.destination:service=Queue,name=ex
  |     jboss.mq:service=SecurityManager
  |     jboss.mq.destination:service=Queue,name=DLQ
  | ]
  | 2009-07-16 18:06:05,328 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq:service=DestinationManager
  | 2009-07-16 18:06:05,328 DEBUG [org.jboss.mq.server.jmx.DestinationManager] Starting jboss.mq:service=DestinationManager
  | 2009-07-16 18:06:05,343 DEBUG [org.jboss.mq.server.jmx.DestinationManager] Started jboss.mq:service=DestinationManager
  | 2009-07-16 18:06:05,343 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.mq:service=DestinationManager dependent components: [ObjectName: com.alu.cnm.cnbi.cfma.simulator:service=SimulatorService
  |   State: CREATED
  |   I Depend On:
  |     jboss.mq:service=DestinationManager
  | , ObjectName: jboss.mq.destination:service=Topic,name=testTopic
  |   State: CREATED
  |   I Depend On:
  |     jboss.mq:service=DestinationManager
  |     jboss.mq:service=SecurityManager
  | , ObjectName: jboss.mq.destination:service=Topic,name=securedTopic
  |   State: CREATED
  |   I Depend On:
  |     jboss.mq:service=DestinationManager
  |     jboss.mq:service=SecurityManager
  | , ObjectName: jboss.mq.destination:service=Topic,name=testDurableTopic
  |   State: CREATED
  |   I Depend On:
  |     jboss.mq:service=DestinationManager
  |     jboss.mq:service=SecurityManager
  | , ObjectName: jboss.mq.destination:service=Queue,name=testQueue
  |   State: CREATED
  |   I Depend On:
  |     jboss.mq:service=DestinationManager
  |     jboss.mq:service=SecurityManager
  | , ObjectName: jboss.mq.destination:service=Queue,name=A
  |   State: CREATED
  |   I Depend On:
  |     jboss.mq:service=DestinationManager
  | , ObjectName: jboss.mq.destination:service=Queue,name=B
  |   State: CREATED
  |   I Depend On:
  |     jboss.mq:service=DestinationManager
  | , ObjectName: jboss.mq.destination:service=Queue,name=C
  |   State: CREATED
  |   I Depend On:
  |     jboss.mq:service=DestinationManager
  | , ObjectName: jboss.mq.destination:service=Queue,name=D
  |   State: CREATED
  |   I Depend On:
  |     jboss.mq:service=DestinationManager
  | , ObjectName: jboss.mq.destination:service=Queue,name=ex
  |   State: CREATED
  |   I Depend On:
  |     jboss.mq:service=DestinationManager
  | , ObjectName: jboss.mq:service=SecurityManager
  |   State: CREATED
  |   I Depend On:
  |     jboss.security:service=JaasSecurityManager
  |     jboss.mq:service=DestinationManager
  |   Depends On Me:
  |     jboss.mq.destination:service=Topic,name=testTopic
  |     jboss.mq.destination:service=Topic,name=securedTopic
  |     jboss.mq.destination:service=Topic,name=testDurableTopic
  |     jboss.mq.destination:service=Queue,name=testQueue
  |     jboss.mq:service=TracingInterceptor
  |     jboss.mq.destination:service=Queue,name=DLQ
  | , ObjectName: jboss.mq.destination:service=Queue,name=DLQ
  |   State: CREATED
  |   I Depend On:
  |     jboss.mq:service=DestinationManager
  |     jboss.mq:service=SecurityManager
  | ]
  | 2009-07-16 18:06:05,343 DEBUG [org.jboss.system.ServiceController] starting service com.alu.cnm.cnbi.cfma.simulator:service=SimulatorService
  | 2009-07-16 18:06:05,343 INFO  [STDOUT] main:: com.alu.cnm.cfma.server.api.CFMAExternalAlarmServicesFactory: CFMAExternalAlarmServicesFactory instantiated
  | 2009-07-16 18:06:05,656 DEBUG [org.jboss.security.auth.spi.UsersRolesLoginModule] Loaded properties, users=[admin]
  | 2009-07-16 18:06:05,656 DEBUG [org.jboss.security.auth.spi.UsersRolesLoginModule] Loaded properties, users=[admin]
  | 2009-07-16 18:06:05,656 DEBUG [org.jboss.security.auth.spi.UsersRolesLoginModule] Bad password for username=null
  | 2009-07-16 18:06:05,750 ERROR [STDERR] main:: com.alu.cnm.cnbi.cfma.simulator.SimulatorService: SIMULATOR INITIALIZATION FAILED >>> Failed to authenticate principal=null, securityDomain=jmx-console
  | java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console
  | 	at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:97)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.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:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.invocation.local.LocalInvoker$MBeanServerAction.invoke(LocalInvoker.java:169)
  | 	at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:118)
  | 	at org.jboss.invocation.InvokerInterceptor.invokeLocal(InvokerInterceptor.java:209)
  | 	at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:195)
  | 	at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
  | 	at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
  | 	at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
  | 	at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
  | 	at $Proxy57.invoke(Unknown Source)
  | 	at com.alu.cnm.cmi.api.CNMMBeanProxy.invoke(CNMMBeanProxy.java:110)
  | 	at $Proxy56.createTopic(Unknown Source)
  | 	at com.alu.cnm.cnbi.cfma.simulator.SimulatorService.createTopic(SimulatorService.java:53)
  | 	at com.alu.cnm.cnbi.cfma.simulator.SimulatorService.start(SimulatorService.java:35)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.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:995)
  | 	at $Proxy0.start(Unknown Source)
  | 	at org.jboss.system.ServiceController.start(ServiceController.java:417)
  | 	at org.jboss.system.ServiceController.start(ServiceController.java:435)
  | 	at org.jboss.system.ServiceController.start(ServiceController.java:435)
  | 	at org.jboss.system.ServiceController.start(ServiceController.java:435)
  | 	at org.jboss.system.ServiceController.start(ServiceController.java:435)
  | 	at org.jboss.system.ServiceController.start(ServiceController.java:435)
  | 	at org.jboss.system.ServiceController.start(ServiceController.java:435)
  | 	at org.jboss.system.ServiceController.start(ServiceController.java:435)
  | 	at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy4.start(Unknown Source)
  | 	at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy43.start(Unknown Source)
  | 	at org.jboss.deployment.XSLSubDeployer.start(XSLSubDeployer.java:197)
  | 	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.GeneratedMethodAccessor22.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy10.deploy(Unknown Source)
  | 	at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
  | 	at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
  | 	at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
  | 	at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
  | 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
  | 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
  | 	at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
  | 	at $Proxy0.start(Unknown Source)
  | 	at org.jboss.system.ServiceController.start(ServiceController.java:417)
  | 	at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy4.start(Unknown Source)
  | 	at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304)
  | 	at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy5.deploy(Unknown Source)
  | 	at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
  | 	at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
  | 	at org.jboss.Main.boot(Main.java:200)
  | 	at org.jboss.Main$1.run(Main.java:508)
  | 	at java.lang.Thread.run(Thread.java:619)
  | 2009-07-16 18:06:05,765 WARN  [org.jboss.system.ServiceController] Problem starting service com.alu.cnm.cnbi.cfma.simulator:service=SimulatorService
  | java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console
  | 	at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:97)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.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:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.invocation.local.LocalInvoker$MBeanServerAction.invoke(LocalInvoker.java:169)
  | 	at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:118)
  | 	at org.jboss.invocation.InvokerInterceptor.invokeLocal(InvokerInterceptor.java:209)
  | 	at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:195)
  | 	at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
  | 	at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
  | 	at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
  | 	at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
  | 	at $Proxy57.invoke(Unknown Source)
  | 	at com.alu.cnm.cmi.api.CNMMBeanProxy.invoke(CNMMBeanProxy.java:110)
  | 	at $Proxy56.createTopic(Unknown Source)
  | 	at com.alu.cnm.cnbi.cfma.simulator.SimulatorService.createTopic(SimulatorService.java:53)
  | 	at com.alu.cnm.cnbi.cfma.simulator.SimulatorService.start(SimulatorService.java:35)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.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:995)
  | 	at $Proxy0.start(Unknown Source)
  | 	at org.jboss.system.ServiceController.start(ServiceController.java:417)
  | 	at org.jboss.system.ServiceController.start(ServiceController.java:435)
  | 	at org.jboss.system.ServiceController.start(ServiceController.java:435)
  | 	at org.jboss.system.ServiceController.start(ServiceController.java:435)
  | 	at org.jboss.system.ServiceController.start(ServiceController.java:435)
  | 	at org.jboss.system.ServiceController.start(ServiceController.java:435)
  | 	at org.jboss.system.ServiceController.start(ServiceController.java:435)
  | 	at org.jboss.system.ServiceController.start(ServiceController.java:435)
  | 	at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy4.start(Unknown Source)
  | 	at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy43.start(Unknown Source)
  | 	at org.jboss.deployment.XSLSubDeployer.start(XSLSubDeployer.java:197)
  | 	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.GeneratedMethodAccessor22.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy10.deploy(Unknown Source)
  | 	at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
  | 	at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
  | 	at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
  | 	at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
  | 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
  | 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
  | 	at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
  | 	at $Proxy0.start(Unknown Source)
  | 	at org.jboss.system.ServiceController.start(ServiceController.java:417)
  | 	at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy4.start(Unknown Source)
  | 	at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304)
  | 	at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy5.deploy(Unknown Source)
  | 	at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
  | 	at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
  | 	at org.jboss.Main.boot(Main.java:200)
  | 	at org.jboss.Main$1.run(Main.java:508)
  | 	at java.lang.Thread.run(Thread.java:619)
  | 2009-07-16 18:06:05,796 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq.destination:service=Topic,name=testTopic
  | 2009-07-16 18:06:05,796 DEBUG [org.jboss.system.ServiceController] waiting in start jboss.mq.destination:service=Topic,name=testTopic on jboss.mq:service=SecurityManager
  | 2009-07-16 18:06:05,796 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq.destination:service=Topic,name=securedTopic
  | 2009-07-16 18:06:05,796 DEBUG [org.jboss.system.ServiceController] waiting in start jboss.mq.destination:service=Topic,name=securedTopic on jboss.mq:service=SecurityManager
  | 2009-07-16 18:06:05,796 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq.destination:service=Topic,name=testDurableTopic
  | 2009-07-16 18:06:05,796 DEBUG [org.jboss.system.ServiceController] waiting in start jboss.mq.destination:service=Topic,name=testDurableTopic on jboss.mq:service=SecurityManager
  | 2009-07-16 18:06:05,796 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq.destination:service=Queue,name=testQueue
  | 2009-07-16 18:06:05,796 DEBUG [org.jboss.system.ServiceController] waiting in start jboss.mq.destination:service=Queue,name=testQueue on jboss.mq:service=SecurityManager
  | 2009-07-16 18:06:05,796 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq.destination:service=Queue,name=A
  | 2009-07-16 18:06:05,796 DEBUG [org.jboss.mq.server.jmx.Queue.A] Starting jboss.mq.destination:service=Queue,name=A
  | 2009-07-16 18:06:05,843 DEBUG [org.jboss.mq.pm.jdbc2.PersistenceManager] Restored 0 message(s) to: QUEUE.A 0 need recovery.
  | 2009-07-16 18:06:05,843 INFO  [org.jboss.mq.server.jmx.Queue.A] Bound to JNDI name: queue/A
  | 2009-07-16 18:06:05,843 DEBUG [org.jboss.mq.server.jmx.Queue.A] Started jboss.mq.destination:service=Queue,name=A
  | 2009-07-16 18:06:05,843 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.mq.destination:service=Queue,name=A dependent components: []
  | 2009-07-16 18:06:05,843 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq.destination:service=Queue,name=B
  | 2009-07-16 18:06:05,843 DEBUG [org.jboss.mq.server.jmx.Queue.B] Starting jboss.mq.destination:service=Queue,name=B
  | 2009-07-16 18:06:05,859 DEBUG [org.jboss.mq.pm.jdbc2.PersistenceManager] Restored 0 message(s) to: QUEUE.B 0 need recovery.
  | 2009-07-16 18:06:05,859 INFO  [org.jboss.mq.server.jmx.Queue.B] Bound to JNDI name: queue/B
  | 2009-07-16 18:06:05,859 DEBUG [org.jboss.mq.server.jmx.Queue.B] Started jboss.mq.destination:service=Queue,name=B
  | 2009-07-16 18:06:05,859 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.mq.destination:service=Queue,name=B dependent components: []
  | 2009-07-16 18:06:05,859 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq.destination:service=Queue,name=C
  | 2009-07-16 18:06:05,859 DEBUG [org.jboss.mq.server.jmx.Queue.C] Starting jboss.mq.destination:service=Queue,name=C
  | 2009-07-16 18:06:05,859 DEBUG [org.jboss.mq.pm.jdbc2.PersistenceManager] Restored 0 message(s) to: QUEUE.C 0 need recovery.
  | 2009-07-16 18:06:05,859 INFO  [org.jboss.mq.server.jmx.Queue.C] Bound to JNDI name: queue/C
  | 2009-07-16 18:06:05,859 DEBUG [org.jboss.mq.server.jmx.Queue.C] Started jboss.mq.destination:service=Queue,name=C
  | 2009-07-16 18:06:05,859 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.mq.destination:service=Queue,name=C dependent components: []
  | 2009-07-16 18:06:05,859 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq.destination:service=Queue,name=D
  | 2009-07-16 18:06:05,859 DEBUG [org.jboss.mq.server.jmx.Queue.D] Starting jboss.mq.destination:service=Queue,name=D
  | 2009-07-16 18:06:05,859 DEBUG [org.jboss.mq.pm.jdbc2.PersistenceManager] Restored 0 message(s) to: QUEUE.D 0 need recovery.
  | 2009-07-16 18:06:05,859 INFO  [org.jboss.mq.server.jmx.Queue.D] Bound to JNDI name: queue/D
  | 2009-07-16 18:06:05,875 DEBUG [org.jboss.mq.server.jmx.Queue.D] Started jboss.mq.destination:service=Queue,name=D
  | 2009-07-16 18:06:05,875 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.mq.destination:service=Queue,name=D dependent components: []
  | 2009-07-16 18:06:05,875 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq.destination:service=Queue,name=ex
  | 2009-07-16 18:06:05,875 DEBUG [org.jboss.mq.server.jmx.Queue.ex] Starting jboss.mq.destination:service=Queue,name=ex
  | 2009-07-16 18:06:05,875 DEBUG [org.jboss.mq.pm.jdbc2.PersistenceManager] Restored 0 message(s) to: QUEUE.ex 0 need recovery.
  | 2009-07-16 18:06:05,875 INFO  [org.jboss.mq.server.jmx.Queue.ex] Bound to JNDI name: queue/ex
  | 2009-07-16 18:06:05,875 DEBUG [org.jboss.mq.server.jmx.Queue.ex] Started jboss.mq.destination:service=Queue,name=ex
  | 2009-07-16 18:06:05,875 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.mq.destination:service=Queue,name=ex dependent components: []
  | 2009-07-16 18:06:05,875 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq:service=SecurityManager
  | 2009-07-16 18:06:05,875 DEBUG [org.jboss.mq.security.SecurityManager] Starting jboss.mq:service=SecurityManager
  | 2009-07-16 18:06:05,890 DEBUG [org.jboss.security.plugins.JaasSecurityManager.jbossmq] CallbackHandler: org.jboss.security.auth.callback.SecurityAssociationHandler at 4a897c
  | 2009-07-16 18:06:05,890 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] Created securityMgr=org.jboss.security.plugins.JaasSecurityManager at 18845af
  | 2009-07-16 18:06:05,890 DEBUG [org.jboss.security.plugins.JaasSecurityManager.jbossmq] CachePolicy set to: org.jboss.util.TimedCachePolicy at 6946d2
  | 2009-07-16 18:06:05,890 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] setCachePolicy, c=org.jboss.util.TimedCachePolicy at 6946d2
  | 2009-07-16 18:06:05,890 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] Added jbossmq, org.jboss.security.plugins.SecurityDomainContext at 1a896a4 to map
  | 2009-07-16 18:06:05,906 DEBUG [org.jboss.mq.security.SecurityManager] Started jboss.mq:service=SecurityManager
  | 2009-07-16 18:06:05,906 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.mq:service=SecurityManager dependent components: [ObjectName: jboss.mq.destination:service=Topic,name=testTopic
  |   State: CREATED
  |   I Depend On:
  |     jboss.mq:service=DestinationManager
  |     jboss.mq:service=SecurityManager
  | , ObjectName: jboss.mq.destination:service=Topic,name=securedTopic
  |   State: CREATED
  |   I Depend On:
  |     jboss.mq:service=DestinationManager
  |     jboss.mq:service=SecurityManager
  | , ObjectName: jboss.mq.destination:service=Topic,name=testDurableTopic
  |   State: CREATED
  |   I Depend On:
  |     jboss.mq:service=DestinationManager
  |     jboss.mq:service=SecurityManager
  | , ObjectName: jboss.mq.destination:service=Queue,name=testQueue
  |   State: CREATED
  |   I Depend On:
  |     jboss.mq:service=DestinationManager
  |     jboss.mq:service=SecurityManager
  | , ObjectName: jboss.mq:service=TracingInterceptor
  |   State: CREATED
  |   I Depend On:
  |     jboss.mq:service=SecurityManager
  |   Depends On Me:
  |     jboss.mq:service=Invoker
  | , ObjectName: jboss.mq.destination:service=Queue,name=DLQ
  |   State: CREATED
  |   I Depend On:
  |     jboss.mq:service=DestinationManager
  |     jboss.mq:service=SecurityManager
  | ]
  | 2009-07-16 18:06:05,906 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq.destination:service=Topic,name=testTopic
  | 2009-07-16 18:06:05,906 DEBUG [org.jboss.mq.server.jmx.Topic.testTopic] Starting jboss.mq.destination:service=Topic,name=testTopic
  | 2009-07-16 18:06:05,921 INFO  [org.jboss.mq.server.jmx.Topic.testTopic] Bound to JNDI name: topic/testTopic
  | 2009-07-16 18:06:05,937 DEBUG [org.jboss.mq.server.jmx.Topic.testTopic] Started jboss.mq.destination:service=Topic,name=testTopic
  | 2009-07-16 18:06:05,937 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.mq.destination:service=Topic,name=testTopic dependent components: []
  | 2009-07-16 18:06:05,937 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq.destination:service=Topic,name=securedTopic
  | 2009-07-16 18:06:05,937 DEBUG [org.jboss.mq.server.jmx.Topic.securedTopic] Starting jboss.mq.destination:service=Topic,name=securedTopic
  | 2009-07-16 18:06:05,937 INFO  [org.jboss.mq.server.jmx.Topic.securedTopic] Bound to JNDI name: topic/securedTopic
  | 2009-07-16 18:06:05,937 DEBUG [org.jboss.mq.server.jmx.Topic.securedTopic] Started jboss.mq.destination:service=Topic,name=securedTopic
  | 2009-07-16 18:06:05,937 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.mq.destination:service=Topic,name=securedTopic dependent components: []
  | 2009-07-16 18:06:05,937 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq.destination:service=Topic,name=testDurableTopic
  | 2009-07-16 18:06:05,937 DEBUG [org.jboss.mq.server.jmx.Topic.testDurableTopic] Starting jboss.mq.destination:service=Topic,name=testDurableTopic
  | 2009-07-16 18:06:05,937 INFO  [org.jboss.mq.server.jmx.Topic.testDurableTopic] Bound to JNDI name: topic/testDurableTopic
  | 2009-07-16 18:06:05,937 DEBUG [org.jboss.mq.server.jmx.Topic.testDurableTopic] Started jboss.mq.destination:service=Topic,name=testDurableTopic
  | 2009-07-16 18:06:05,937 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.mq.destination:service=Topic,name=testDurableTopic dependent components: []
  | 2009-07-16 18:06:05,937 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq.destination:service=Queue,name=testQueue
  | 2009-07-16 18:06:05,937 DEBUG [org.jboss.mq.server.jmx.Queue.testQueue] Starting jboss.mq.destination:service=Queue,name=testQueue
  | 2009-07-16 18:06:05,953 DEBUG [org.jboss.mq.pm.jdbc2.PersistenceManager] Restored 0 message(s) to: QUEUE.testQueue 0 need recovery.
  | 2009-07-16 18:06:05,968 INFO  [org.jboss.mq.server.jmx.Queue.testQueue] Bound to JNDI name: queue/testQueue
  | 2009-07-16 18:06:05,968 DEBUG [org.jboss.mq.server.jmx.Queue.testQueue] Started jboss.mq.destination:service=Queue,name=testQueue
  | 2009-07-16 18:06:05,968 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.mq.destination:service=Queue,name=testQueue dependent components: []
  | 2009-07-16 18:06:05,968 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq:service=TracingInterceptor
  | 2009-07-16 18:06:05,968 DEBUG [org.jboss.mq.server.jmx.InterceptorLoader] Starting jboss.mq:service=TracingInterceptor
  | 2009-07-16 18:06:05,968 DEBUG [org.jboss.mq.server.jmx.InterceptorLoader] Started jboss.mq:service=TracingInterceptor
  | 2009-07-16 18:06:05,968 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.mq:service=TracingInterceptor dependent components: [ObjectName: jboss.mq:service=Invoker
  |   State: CREATED
  |   I Depend On:
  |     jboss.mq:service=TracingInterceptor
  |     jboss:service=Naming
  |   Depends On Me:
  |     jboss.mq:service=InvocationLayer,type=HTTP
  |     jboss.mq:service=InvocationLayer,type=JVM
  |     jboss.mq:service=InvocationLayer,type=UIL2
  | ]
  | 2009-07-16 18:06:05,968 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq:service=Invoker
  | 2009-07-16 18:06:05,968 DEBUG [org.jboss.mq.server.jmx.Invoker] Starting jboss.mq:service=Invoker
  | 2009-07-16 18:06:05,968 DEBUG [org.jboss.mq.server.jmx.Invoker] Started jboss.mq:service=Invoker
  | 2009-07-16 18:06:05,968 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.mq:service=Invoker dependent components: [ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
  |   State: CREATED
  |   I Depend On:
  |     jboss.mq:service=Invoker
  |     jboss.web:service=WebServer
  | , ObjectName: jboss.mq:service=InvocationLayer,type=JVM
  |   State: CREATED
  |   I Depend On:
  |     jboss.mq:service=Invoker
  | , ObjectName: jboss.mq:service=InvocationLayer,type=UIL2
  |   State: CREATED
  |   I Depend On:
  |     jboss.mq:service=Invoker
  | ]
  | 2009-07-16 18:06:05,968 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq:service=InvocationLayer,type=HTTP
  | 2009-07-16 18:06:05,968 DEBUG [org.jboss.mq.il.http.HTTPServerILService] Starting jboss.mq:service=InvocationLayer,type=HTTP
  | 2009-07-16 18:06:06,062 DEBUG [org.jboss.mq.il.http.HTTPServerILService] Started jboss.mq:service=InvocationLayer,type=HTTP
  | 2009-07-16 18:06:06,062 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.mq:service=InvocationLayer,type=HTTP dependent components: []
  | 2009-07-16 18:06:06,062 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq:service=InvocationLayer,type=JVM
  | 2009-07-16 18:06:06,062 DEBUG [org.jboss.mq.il.jvm.JVMServerILService] Starting jboss.mq:service=InvocationLayer,type=JVM
  | 2009-07-16 18:06:06,078 DEBUG [org.jboss.mq.il.jvm.JVMServerILService] Started jboss.mq:service=InvocationLayer,type=JVM
  | 2009-07-16 18:06:06,078 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.mq:service=InvocationLayer,type=JVM dependent components: []
  | 2009-07-16 18:06:06,078 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq:service=InvocationLayer,type=UIL2
  | 2009-07-16 18:06:06,078 DEBUG [org.jboss.mq.il.uil2.UILServerILService] Starting jboss.mq:service=InvocationLayer,type=UIL2
  | 2009-07-16 18:06:06,078 INFO  [org.jboss.mq.il.uil2.UILServerILService] JBossMQ UIL service available at : /127.0.0.1:8993
  | 2009-07-16 18:06:06,171 DEBUG [org.jboss.mq.il.uil2.UILServerILService] Started jboss.mq:service=InvocationLayer,type=UIL2
  | 2009-07-16 18:06:06,171 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.mq:service=InvocationLayer,type=UIL2 dependent components: []
  | 2009-07-16 18:06:06,171 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq.destination:service=Queue,name=DLQ
  | 2009-07-16 18:06:06,171 DEBUG [org.jboss.mq.server.jmx.Queue.DLQ] Starting jboss.mq.destination:service=Queue,name=DLQ
  | 2009-07-16 18:06:06,187 DEBUG [org.jboss.mq.pm.jdbc2.PersistenceManager] Restored 0 message(s) to: QUEUE.DLQ 0 need recovery.
  | 2009-07-16 18:06:06,187 INFO  [org.jboss.mq.server.jmx.Queue.DLQ] Bound to JNDI name: queue/DLQ
  | 2009-07-16 18:06:06,187 DEBUG [org.jboss.mq.server.jmx.Queue.DLQ] Started jboss.mq.destination:service=Queue,name=DLQ
  | 2009-07-16 18:06:06,187 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.mq.destination:service=Queue,name=DLQ dependent components: []
  | 2009-07-16 18:06:06,187 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq.destination:service=Queue,name=DLQ
  | 2009-07-16 18:06:06,187 DEBUG [org.jboss.system.ServiceController] Ignoring start request for service: jboss.mq.destination:service=Queue,name=DLQ
  | 2009-07-16 18:06:06,265 DEBUG [org.jboss.deployment.MainDeployer] End deployment start on package: hsqldb-ds.xml
  | 2009-07-16 18:06:06,265 DEBUG [org.jboss.deployment.MainDeployer] Deployed package: file:/D:/CALBA/workspace350/CNBI_v20_WorkingCopy/CNBI_processing/deploy/jboss/jboss-4.2.3.GA/server/cnbi/deploy/hsqldb-ds.xml
  | 2009-07-16 18:06:06,265 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Watch URL for: file:/D:/CALBA/workspace350/CNBI_v20_WorkingCopy/CNBI_processing/deploy/jboss/jboss-4.2.3.GA/server/cnbi/deploy/hsqldb-ds.xml -> file:/D:/CALBA/workspace350/CNBI_v20_WorkingCopy/CNBI_processing/deploy/jboss/jboss-4.2.3.GA/server/cnbi/deploy/hsqldb-ds.xml
  | 2009-07-16 18:06:06,265 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/D:/CALBA/workspace350/CNBI_v20_WorkingCopy/CNBI_processing/deploy/jboss/jboss-4.2.3.GA/server/cnbi/deploy/jms/jms-ds.xml
  | 2009-07-16 18:06:06,265 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: file:/D:/CALBA/workspace350/CNBI_v20_WorkingCopy/CNBI_processing/deploy/jboss/jboss-4.2.3.GA/server/cnbi/deploy/jms/jms-ds.xml
  | 2009-07-16 18:06:06,265 DEBUG [org.jboss.deployment.MainDeployer] Copying file:/D:/CALBA/workspace350/CNBI_v20_WorkingCopy/CNBI_processing/deploy/jboss/jboss-4.2.3.GA/server/cnbi/deploy/jms/jms-ds.xml -> D:\CALBA\workspace350\CNBI_v20_WorkingCopy\CNBI_processing\deploy\jboss\jboss-4.2.3.GA\server\cnbi\tmp\deploy\tmp44164jms-ds.xml
  | 2009-07-16 18:06:06,281 DEBUG [org.jboss.deployment.MainDeployer] using deployer org.jboss.deployment.XSLSubDeployer at 260d8d
  | 2009-07-16 18:06:06,296 DEBUG [org.jboss.deployment.XSLSubDeployer] transformed into doc: [#document: null]
  | 2009-07-16 18:06:06,296 DEBUG [org.jboss.deployment.XSLSubDeployer] transformed into doc: <server>
  |  <mbean code='org.jboss.jms.jndi.JMSProviderLoader' name='jboss.mq:service=JMSProviderLoader,name=JMSProvider'>
  |   <attribute name='ProviderName'>DefaultJMSProvider</attribute>
  |   <attribute name='ProviderAdapterClass'>
  |       org.jboss.jms.jndi.JNDIProviderAdapter
  |     </attribute>
  |   <attribute name='FactoryRef'>java:/XAConnectionFactory</attribute>
  |   <attribute name='QueueFactoryRef'>java:/XAConnectionFactory</attribute>
  |   <attribute name='TopicFactoryRef'>java:/XAConnectionFactory</attribute>
  |  </mbean>
  |  <mbean code='org.jboss.jms.asf.ServerSessionPoolLoader' name='jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool'>
  |   <depends optional-attribute-name='XidFactory'>jboss:service=XidFactory</depends>
  |   <attribute name='PoolName'>StdJMSPool</attribute>
  |   <attribute name='PoolFactoryClass'>
  |       org.jboss.jms.asf.StdServerSessionPoolFactory
  |     </attribute>
  |  </mbean>
  |  <mbean code='org.jboss.resource.connectionmanager.TxConnectionManager' display-name='ConnectionManager for ConnectionFactory JmsXA' name='jboss.jca:service=TxCM,name=JmsXA'>
  |   <attribute name='TrackConnectionByTx'>false</attribute>
  |   <attribute name='LocalTransactions'>false</attribute>
  |   <depends optional-attribute-name='ManagedConnectionPool'>
  |    <mbean code='org.jboss.resource.connectionmanager.JBossManagedConnectionPool' display-name='Connection Pool for DataSource JmsXA' name='jboss.jca:service=ManagedConnectionPool,name=JmsXA'>
  |     <depends optional-attribute-name='ManagedConnectionFactoryName'>
  |      <mbean code='org.jboss.resource.connectionmanager.RARDeployment' display-name='ManagedConnectionFactory for ConnectionFactory JmsXA' name='jboss.jca:service=ManagedConnectionFactory,name=JmsXA'>
  |       <attribute name='ManagedConnectionFactoryProperties'>
  |        <properties>
  |         <config-property name='SessionDefaultType' type='java.lang.String'>javax.jms.Topic</config-property>
  |         <config-property name='JmsProviderAdapterJNDI' type='java.lang.String'>java:/DefaultJMSProvider</config-property>
  |        </properties>
  |       </attribute>
  |       <attribute name='RARName'>jms-ra.rar</attribute>
  |       <attribute name='ConnectionDefinition'>org.jboss.resource.adapter.jms.JmsConnectionFactory</attribute>
  |       <depends optional-attribute-name='OldRarDeployment'>jboss.jca:service=RARDeployment,name='jms-ra.rar'</depends>
  |      </mbean>
  |     </depends>
  |     <attribute name='PoolJndiName'>JmsXA</attribute>
  |     <attribute name='MinSize'>0</attribute>
  |     <attribute name='MaxSize'>20</attribute>
  |     <attribute name='BlockingTimeoutMillis'>30000</attribute>
  |     <attribute name='IdleTimeoutMinutes'>15</attribute>
  |     <attribute name='BackGroundValidation'>False</attribute>
  |     <attribute name='BackGroundValidationMinutes'>10</attribute>
  |     <attribute name='PreFill'>False</attribute>
  |     <attribute name='StatisticsFormatter'>org.jboss.resource.statistic.pool.JBossDefaultSubPoolStatisticFormatter</attribute>
  |     <attribute name='UseFastFail'>False</attribute>
  |     <attribute name='Criteria'>ByContainerAndApplication</attribute>
  |    </mbean>
  |   </depends>
  |   <attribute name='JndiName'>JmsXA</attribute>
  |   <depends optional-attribute-name='CachedConnectionManager'>jboss.jca:service=CachedConnectionManager</depends>
  |   <attribute name='SecurityDomainJndiName'>JmsXARealm</attribute>
  |   <depends optional-attribute-name='JaasSecurityManagerService'>jboss.security:service=JaasSecurityManager</depends>
  |   <depends optional-attribute-name='TransactionManagerService'>jboss:service=TransactionManager</depends>
  |  </mbean>
  |  <mbean code='org.jboss.resource.connectionmanager.ConnectionFactoryBindingService' display-name='Binding for ConnectionFactory JmsXA' name='jboss.jca:service=ConnectionFactoryBinding,name=JmsXA'>
  |   <attribute name='JndiName'>JmsXA</attribute>
  |   <attribute name='UseJavaContext'>true</attribute>
  |   <depends optional-attribute-name='ConnectionManager'>jboss.jca:service=TxCM,name=JmsXA</depends>
  |  </mbean>
  | </server>
  | 2009-07-16 18:06:06,296 DEBUG [org.jboss.deployment.SARDeployer] Using existing deployment.document
  | 2009-07-16 18:06:06,296 DEBUG [org.jboss.deployment.SARDeployer] about to copy 0 local directories
  | 2009-07-16 18:06:06,296 DEBUG [org.jboss.deployment.SARDeployer] looking for nested deployments in : file:/D:/CALBA/workspace350/CNBI_v20_WorkingCopy/CNBI_processing/deploy/jboss/jboss-4.2.3.GA/server/cnbi/deploy/jms/jms-ds.xml
  | 2009-07-16 18:06:06,296 DEBUG [org.jboss.deployment.DeploymentInfo] createLoaderRepository from config: LoaderRepositoryConfig(repositoryName: JMImplementation:service=LoaderRepository,name=Default, repositoryClassName: null, configParserClassName: null, repositoryConfig: null)
  | 2009-07-16 18:06:06,296 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 198a455, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 142c63f{ url=null ,addedOrder=0}
  | 2009-07-16 18:06:06,296 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 198a455, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 142c63f{ url=null ,addedOrder=0}
  | 2009-07-16 18:06:06,296 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader3 at 142c63f{ url=null ,addedOrder=0}
  | 2009-07-16 18:06:06,296 DEBUG [org.jboss.deployment.MainDeployer] found 0 subpackages of file:/D:/CALBA/workspace350/CNBI_v20_WorkingCopy/CNBI_processing/deploy/jboss/jboss-4.2.3.GA/server/cnbi/deploy/jms/jms-ds.xml
  | 2009-07-16 18:06:06,296 DEBUG [org.jboss.deployment.MainDeployer] Watching new file: file:/D:/CALBA/workspace350/CNBI_v20_WorkingCopy/CNBI_processing/deploy/jboss/jboss-4.2.3.GA/server/cnbi/deploy/jms/jms-ds.xml
  | 2009-07-16 18:06:06,296 DEBUG [org.jboss.deployment.MainDeployer] create step for deployment file:/D:/CALBA/workspace350/CNBI_v20_WorkingCopy/CNBI_processing/deploy/jboss/jboss-4.2.3.GA/server/cnbi/deploy/jms/jms-ds.xml
  | 2009-07-16 18:06:06,296 DEBUG [org.jboss.deployment.SARDeployer] Deploying SAR, create step: url file:/D:/CALBA/workspace350/CNBI_v20_WorkingCopy/CNBI_processing/deploy/jboss/jboss-4.2.3.GA/server/cnbi/deploy/jms/jms-ds.xml
  | 2009-07-16 18:06:06,296 DEBUG [org.jboss.deployment.SARDeployer] Registering service UCL=jmx.loading:UCL=142c63f
  | 2009-07-16 18:06:06,312 DEBUG [org.jboss.system.ServiceCreator] About to create bean: jboss.mq:service=JMSProviderLoader,name=JMSProvider with code: org.jboss.jms.jndi.JMSProviderLoader
  | 2009-07-16 18:06:06,312 DEBUG [org.jboss.system.ServiceCreator] Created bean: jboss.mq:service=JMSProviderLoader,name=JMSProvider
  | 2009-07-16 18:06:06,312 DEBUG [org.jboss.system.ServiceConfigurator] ProviderName set to DefaultJMSProvider in jboss.mq:service=JMSProviderLoader,name=JMSProvider
  | 2009-07-16 18:06:06,312 DEBUG [org.jboss.system.ServiceConfigurator] ProviderAdapterClass set to org.jboss.jms.jndi.JNDIProviderAdapter in jboss.mq:service=JMSProviderLoader,name=JMSProvider
  | 2009-07-16 18:06:06,312 DEBUG [org.jboss.system.ServiceConfigurator] FactoryRef set to java:/XAConnectionFactory in jboss.mq:service=JMSProviderLoader,name=JMSProvider
  | 2009-07-16 18:06:06,312 DEBUG [org.jboss.system.ServiceConfigurator] QueueFactoryRef set to java:/XAConnectionFactory in jboss.mq:service=JMSProviderLoader,name=JMSProvider
  | 2009-07-16 18:06:06,312 DEBUG [org.jboss.system.ServiceConfigurator] TopicFactoryRef set to java:/XAConnectionFactory in jboss.mq:service=JMSProviderLoader,name=JMSProvider
  | 2009-07-16 18:06:06,328 DEBUG [org.jboss.system.ServiceCreator] About to create bean: jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool with code: org.jboss.jms.asf.ServerSessionPoolLoader
  | 2009-07-16 18:06:06,328 DEBUG [org.jboss.system.ServiceCreator] Created bean: jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool
  | 2009-07-16 18:06:06,328 DEBUG [org.jboss.system.ServiceController] recording that jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool depends on jboss:service=XidFactory
  | 2009-07-16 18:06:06,328 DEBUG [org.jboss.system.ServiceConfigurator] considering XidFactory with object name jboss:service=XidFactory
  | 2009-07-16 18:06:06,328 DEBUG [org.jboss.system.ServiceConfigurator] PoolName set to StdJMSPool in jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool
  | 2009-07-16 18:06:06,328 DEBUG [org.jboss.system.ServiceConfigurator] PoolFactoryClass set to org.jboss.jms.asf.StdServerSessionPoolFactory in jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool
  | 2009-07-16 18:06:06,328 DEBUG [org.jboss.system.ServiceCreator] About to create bean: jboss.jca:service=TxCM,name=JmsXA with code: org.jboss.resource.connectionmanager.TxConnectionManager
  | 2009-07-16 18:06:06,343 DEBUG [org.jboss.system.ServiceCreator] Created bean: jboss.jca:service=TxCM,name=JmsXA
  | 2009-07-16 18:06:06,343 DEBUG [org.jboss.system.ServiceConfigurator] TrackConnectionByTx set to false in jboss.jca:service=TxCM,name=JmsXA
  | 2009-07-16 18:06:06,343 DEBUG [org.jboss.system.ServiceConfigurator] LocalTransactions set to false in jboss.jca:service=TxCM,name=JmsXA
  | 2009-07-16 18:06:06,343 DEBUG [org.jboss.system.ServiceCreator] About to create bean: jboss.jca:service=ManagedConnectionPool,name=JmsXA with code: org.jboss.resource.connectionmanager.JBossManagedConnectionPool
  | 2009-07-16 18:06:06,343 DEBUG [org.jboss.system.ServiceCreator] Created bean: jboss.jca:service=ManagedConnectionPool,name=JmsXA
  | 2009-07-16 18:06:06,343 DEBUG [org.jboss.system.ServiceCreator] About to create bean: jboss.jca:service=ManagedConnectionFactory,name=JmsXA with code: org.jboss.resource.connectionmanager.RARDeployment
  | 2009-07-16 18:06:06,359 DEBUG [org.jboss.system.ServiceCreator] Created bean: jboss.jca:service=ManagedConnectionFactory,name=JmsXA
  | 2009-07-16 18:06:06,359 DEBUG [org.jboss.system.ServiceConfigurator] ManagedConnectionFactoryProperties set to [properties: null] in jboss.jca:service=ManagedConnectionFactory,name=JmsXA
  | 2009-07-16 18:06:06,359 DEBUG [org.jboss.system.ServiceConfigurator] RARName set to jms-ra.rar in jboss.jca:service=ManagedConnectionFactory,name=JmsXA
  | 2009-07-16 18:06:06,359 DEBUG [org.jboss.system.ServiceConfigurator] ConnectionDefinition set to org.jboss.resource.adapter.jms.JmsConnectionFactory in jboss.jca:service=ManagedConnectionFactory,name=JmsXA
  | 2009-07-16 18:06:06,359 DEBUG [org.jboss.system.ServiceController] recording that jboss.jca:service=ManagedConnectionFactory,name=JmsXA depends on jboss.jca:service=RARDeployment,name='jms-ra.rar'
  | 2009-07-16 18:06:06,359 DEBUG [org.jboss.system.ServiceConfigurator] considering OldRarDeployment with object name jboss.jca:service=RARDeployment,name='jms-ra.rar'
  | 2009-07-16 18:06:06,359 DEBUG [org.jboss.system.ServiceController] recording that jboss.jca:service=ManagedConnectionPool,name=JmsXA depends on jboss.jca:service=ManagedConnectionFactory,name=JmsXA
  | 2009-07-16 18:06:06,359 DEBUG [org.jboss.system.ServiceConfigurator] considering ManagedConnectionFactoryName with object name jboss.jca:service=ManagedConnectionFactory,name=JmsXA
  | 2009-07-16 18:06:06,359 DEBUG [org.jboss.system.ServiceConfigurator] PoolJndiName set to JmsXA in jboss.jca:service=ManagedConnectionPool,name=JmsXA
  | 2009-07-16 18:06:06,359 DEBUG [org.jboss.system.ServiceConfigurator] MinSize set to 0 in jboss.jca:service=ManagedConnectionPool,name=JmsXA
  | 2009-07-16 18:06:06,359 DEBUG [org.jboss.system.ServiceConfigurator] MaxSize set to 20 in jboss.jca:service=ManagedConnectionPool,name=JmsXA
  | 2009-07-16 18:06:06,359 DEBUG [org.jboss.system.ServiceConfigurator] BlockingTimeoutMillis set to 30000 in jboss.jca:service=ManagedConnectionPool,name=JmsXA
  | 2009-07-16 18:06:06,359 DEBUG [org.jboss.system.ServiceConfigurator] IdleTimeoutMinutes set to 15 in jboss.jca:service=ManagedConnectionPool,name=JmsXA
  | 2009-07-16 18:06:06,359 DEBUG [org.jboss.system.ServiceConfigurator] BackGroundValidation set to false in jboss.jca:service=ManagedConnectionPool,name=JmsXA
  | 2009-07-16 18:06:06,359 DEBUG [org.jboss.system.ServiceConfigurator] BackGroundValidationMinutes set to 10 in jboss.jca:service=ManagedConnectionPool,name=JmsXA
  | 2009-07-16 18:06:06,359 DEBUG [org.jboss.system.ServiceConfigurator] PreFill set to false in jboss.jca:service=ManagedConnectionPool,name=JmsXA
  | 2009-07-16 18:06:06,359 DEBUG [org.jboss.system.ServiceConfigurator] StatisticsFormatter set to org.jboss.resource.statistic.pool.JBossDefaultSubPoolStatisticFormatter in jboss.jca:service=ManagedConnectionPool,name=JmsXA
  | 2009-07-16 18:06:06,359 DEBUG [org.jboss.system.ServiceConfigurator] UseFastFail set to false in jboss.jca:service=ManagedConnectionPool,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceConfigurator] Criteria set to ByContainerAndApplication in jboss.jca:service=ManagedConnectionPool,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] recording that jboss.jca:service=TxCM,name=JmsXA depends on jboss.jca:service=ManagedConnectionPool,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceConfigurator] considering ManagedConnectionPool with object name jboss.jca:service=ManagedConnectionPool,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceConfigurator] JndiName set to JmsXA in jboss.jca:service=TxCM,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] recording that jboss.jca:service=TxCM,name=JmsXA depends on jboss.jca:service=CachedConnectionManager
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceConfigurator] considering CachedConnectionManager with object name jboss.jca:service=CachedConnectionManager
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceConfigurator] SecurityDomainJndiName set to JmsXARealm in jboss.jca:service=TxCM,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] recording that jboss.jca:service=TxCM,name=JmsXA depends on jboss.security:service=JaasSecurityManager
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceConfigurator] considering JaasSecurityManagerService with object name jboss.security:service=JaasSecurityManager
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] recording that jboss.jca:service=TxCM,name=JmsXA depends on jboss:service=TransactionManager
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceConfigurator] considering TransactionManagerService with object name jboss:service=TransactionManager
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceCreator] About to create bean: jboss.jca:service=ConnectionFactoryBinding,name=JmsXA with code: org.jboss.resource.connectionmanager.ConnectionFactoryBindingService
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceCreator] Created bean: jboss.jca:service=ConnectionFactoryBinding,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceConfigurator] JndiName set to JmsXA in jboss.jca:service=ConnectionFactoryBinding,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceConfigurator] UseJavaContext set to true in jboss.jca:service=ConnectionFactoryBinding,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] recording that jboss.jca:service=ConnectionFactoryBinding,name=JmsXA depends on jboss.jca:service=TxCM,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceConfigurator] considering ConnectionManager with object name jboss.jca:service=TxCM,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] Creating service jboss.mq:service=JMSProviderLoader,name=JMSProvider
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.jms.jndi.JMSProviderLoader] Creating jboss.mq:service=JMSProviderLoader,name=JMSProvider
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.jms.jndi.JMSProviderLoader] Created jboss.mq:service=JMSProviderLoader,name=JMSProvider
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.mq:service=JMSProviderLoader,name=JMSProvider dependents are: []
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] Creating service jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.jms.asf.ServerSessionPoolLoader] Creating jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.jms.asf.ServerSessionPoolLoader] Created jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool dependents are: []
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] Creating service jboss.jca:service=TxCM,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] waiting in create of jboss.jca:service=TxCM,name=JmsXA waiting on jboss.jca:service=ManagedConnectionPool,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] Creating service jboss.jca:service=ManagedConnectionPool,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] waiting in create of jboss.jca:service=ManagedConnectionPool,name=JmsXA waiting on jboss.jca:service=ManagedConnectionFactory,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] Creating service jboss.jca:service=ManagedConnectionFactory,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.resource.connectionmanager.RARDeployment] Creating jboss.jca:service=ManagedConnectionFactory,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.resource.connectionmanager.RARDeployment] Created jboss.jca:service=ManagedConnectionFactory,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.jca:service=ManagedConnectionFactory,name=JmsXA dependents are: [ObjectName: jboss.jca:service=ManagedConnectionPool,name=JmsXA
  |   State: CONFIGURED
  |   I Depend On:
  |     jboss.jca:service=ManagedConnectionFactory,name=JmsXA
  |   Depends On Me:
  |     jboss.jca:service=TxCM,name=JmsXA
  | ]
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] Creating service jboss.jca:service=ManagedConnectionPool,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Creating jboss.jca:service=ManagedConnectionPool,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Created jboss.jca:service=ManagedConnectionPool,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.jca:service=ManagedConnectionPool,name=JmsXA dependents are: [ObjectName: jboss.jca:service=TxCM,name=JmsXA
  |   State: CONFIGURED
  |   I Depend On:
  |     jboss.jca:service=ManagedConnectionPool,name=JmsXA
  |     jboss.jca:service=CachedConnectionManager
  |     jboss.security:service=JaasSecurityManager
  |     jboss:service=TransactionManager
  |   Depends On Me:
  |     jboss.jca:service=ConnectionFactoryBinding,name=JmsXA
  | ]
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] Creating service jboss.jca:service=TxCM,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.resource.connectionmanager.TxConnectionManager] Creating jboss.jca:service=TxCM,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.resource.connectionmanager.TxConnectionManager] Created jboss.jca:service=TxCM,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.jca:service=TxCM,name=JmsXA dependents are: [ObjectName: jboss.jca:service=ConnectionFactoryBinding,name=JmsXA
  |   State: CONFIGURED
  |   I Depend On:
  |     jboss.jca:service=TxCM,name=JmsXA
  | ]
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] Creating service jboss.jca:service=ConnectionFactoryBinding,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] Creating jboss.jca:service=ConnectionFactoryBinding,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] Created jboss.jca:service=ConnectionFactoryBinding,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.jca:service=ConnectionFactoryBinding,name=JmsXA dependents are: []
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] Creating service jboss.jca:service=ConnectionFactoryBinding,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] Ignoring create request for service: jboss.jca:service=ConnectionFactoryBinding,name=JmsXA
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.deployment.MainDeployer] Done with create step of deploying jms-ds.xml
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.deployment.MainDeployer] Begin deployment start file:/D:/CALBA/workspace350/CNBI_v20_WorkingCopy/CNBI_processing/deploy/jboss/jboss-4.2.3.GA/server/cnbi/deploy/jms/jms-ds.xml
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.deployment.SARDeployer] Deploying SAR, start step: url file:/D:/CALBA/workspace350/CNBI_v20_WorkingCopy/CNBI_processing/deploy/jboss/jboss-4.2.3.GA/server/cnbi/deploy/jms/jms-ds.xml
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq:service=JMSProviderLoader,name=JMSProvider
  | 2009-07-16 18:06:06,375 DEBUG [org.jboss.jms.jndi.JMSProviderLoader] Starting jboss.mq:service=JMSProviderLoader,name=JMSProvider
  | 2009-07-16 18:06:06,390 DEBUG [org.jboss.jms.jndi.JMSProviderLoader] attempting to bind org.jboss.jms.jndi.JNDIProviderAdapter at 14481bb to java:/DefaultJMSProvider
  | 2009-07-16 18:06:06,390 DEBUG [org.jboss.jms.jndi.JMSProviderLoader] Bound adapter to java:/DefaultJMSProvider
  | 2009-07-16 18:06:06,390 DEBUG [org.jboss.jms.jndi.JMSProviderLoader] Started jboss.mq:service=JMSProviderLoader,name=JMSProvider
  | 2009-07-16 18:06:06,390 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.mq:service=JMSProviderLoader,name=JMSProvider dependent components: []
  | 2009-07-16 18:06:06,390 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool
  | 2009-07-16 18:06:06,390 DEBUG [org.jboss.jms.asf.ServerSessionPoolLoader] Starting jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool
  | 2009-07-16 18:06:06,406 DEBUG [org.jboss.jms.asf.ServerSessionPoolLoader] initialized with pool factory: org.jboss.jms.asf.StdServerSessionPoolFactory at 1425f38
  | 2009-07-16 18:06:06,406 DEBUG [org.jboss.jms.asf.ServerSessionPoolLoader] pool factory StdJMSPool bound to java:/StdJMSPool
  | 2009-07-16 18:06:06,406 DEBUG [org.jboss.jms.asf.ServerSessionPoolLoader] Started jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool
  | 2009-07-16 18:06:06,406 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool dependent components: []
  | 2009-07-16 18:06:06,406 DEBUG [org.jboss.system.ServiceController] starting service jboss.jca:service=TxCM,name=JmsXA
  | 2009-07-16 18:06:06,406 DEBUG [org.jboss.system.ServiceController] waiting in start j

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

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


From do-not-reply at jboss.com  Thu Jul 16 01:28:39 2009
From: do-not-reply at jboss.com (alfred.rsa)
Date: Thu, 16 Jul 2009 01:28:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Newlines/spaces in SOAPMessage
Message-ID: <16599417.1247722119596.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi Alessio

Thanks for the reply. No I create the SOAP message by getting an instance of the SOAP MessageFactory and then adding elements to the body. 
When i use the SoapMessage writeTo method to a file, it contains no CRLF pairs, but when I intercept the message using WireShark, I see the CRLF's.
So it seems as if the SOAPConnection call method or underlying transport is adding the CRLF's

Using the exact same code in GlassFish, the CRLF's are never added and it works fine, but I do not want to use GlassFish 

Regards
Alfred

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

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


From koxkorrita at laudio.info  Mon Jul 20 18:01:46 2009
From: koxkorrita at laudio.info (Koxkorrita)
Date: Tue, 21 Jul 2009 00:01:46 +0200
Subject: [jbossws-users] error publising one Ws that is made using JAXWs and
	spring
Message-ID: <004701ca0985$acb342d0$0619c870$@info>

hello

i have made one Ws using JAX-WS2

my next step is to use sprig for this WS but using also JAXWS

 

the configuration is the next but always appears one error when i deployed
it into the jboss (below)

 

can you help me please?

 

 

thanks

WEB.XML:

<?xml version="1.0" encoding="UTF-8"?>

<web-app xmlns=" <http://java.sun.com/xml/ns/j2ee>
http://java.sun.com/xml/ns/j2ee" xmlns:xsi="
<http://www.w3.org/2001/XMLSchema-instance>
http://www.w3.org/2001/XMLSchema-instance"

                xsi:schemaLocation="
<http://java.sun.com/xml/ns/j2ee%20http:/java.sun.com/xml/ns/j2ee/web-app_2_
4.xsd> http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"

                version="2.4" id="WebApp_124523456858163658">

 

                <display-name>MiProjservicioWS</display-name>

 

                <servlet>

 
<servlet-name>MiProjservicioServlet</servlet-name>

<servlet-class>com.sun.xml.ws.transport.http.servlet.WSSpringServlet</servle
t-class>

                               <init-param>

 
<param-name>contextConfigLocation</param-name>

                                               <param-value></param-value>

                               </init-param>

                               <load-on-startup>1</load-on-startup>

                </servlet>

                <servlet-mapping>

 
<servlet-name>MiProjservicioServlet</servlet-name>

                               <url-pattern>/MiProjservicioWS</url-pattern>

                </servlet-mapping>

                <session-config>

                                <session-timeout>30</session-timeout>

                </session-config>

 

                <context-param>

 
<param-name>contextConfigLocation</param-name>

                               <param-value>

 
/WEB-INF/MiProjservicioWS-config.xml

 
classpath:config/services/spring.xml

                                               </param-value>

                </context-param>

                

                <listener>

 
<listener-class>org.springframework.web.context.ContextLoaderListener</liste
ner-class>

                </listener>

 

</web-app>

 

 

file: MiProjservicioWS-config.xml

 

<?xml version="1.0" encoding="UTF-8"?>

<beans xmlns=" <http://www.springframework.org/schema/beans>
http://www.springframework.org/schema/beans"

xmlns:xsi=" <http://www.w3.org/2001/XMLSchema-instance>
http://www.w3.org/2001/XMLSchema-instance" 

xmlns:p=" <http://www.springframework.org/schema/p>
http://www.springframework.org/schema/p"

xmlns:aop=" <http://www.springframework.org/schema/aop>
http://www.springframework.org/schema/aop" 

xmlns:tx=" <http://www.springframework.org/schema/tx>
http://www.springframework.org/schema/tx"

xmlns:ws=" <http://jax-ws.dev.java.net/spring/core>
http://jax-ws.dev.java.net/spring/core" 

xmlns:wss=" <http://jax-ws.dev.java.net/spring/servlet>
http://jax-ws.dev.java.net/spring/servlet"

xsi:schemaLocation="http://www.springframework.org/schema/beans

 <http://www.springframework.org/schema/beans/spring-beans-2.5.xsd>
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd 

 <http://www.springframework.org/schema/aop>
http://www.springframework.org/schema/aop

 <http://www.springframework.org/schema/aop/spring-aop-2.5.xsd>
http://www.springframework.org/schema/aop/spring-aop-2.5.xsd 

 <http://www.springframework.org/schema/tx>
http://www.springframework.org/schema/tx

 <http://www.springframework.org/schema/tx/spring-tx-2.5.xsd>
http://www.springframework.org/schema/tx/spring-tx-2.5.xsd 

 <http://jax-ws.dev.java.net/spring/core>
http://jax-ws.dev.java.net/spring/core

 <https://jax-ws.dev.java.net/spring/core.xsd>
https://jax-ws.dev.java.net/spring/core.xsd 

 <http://jax-ws.dev.java.net/spring/servlet>
http://jax-ws.dev.java.net/spring/servlet

 <https://jax-ws.dev.java.net/spring/servlet.xsd>
https://jax-ws.dev.java.net/spring/servlet.xsd">

                <bean
class="com.domain.mio.MiProj.controllers.MiProjExceptionResolver">

                </bean>

                <wss:binding url="/MiProjservicioWS">

                               <wss:service>

                                               <ws:service
bean="myservicioService" />

                               </wss:service>

                </wss:binding>

                <bean id="myservicioService"

 
class="com.domain.mio.MiProj.ws.servicio.impl.MiProjservicioWSImpl" />

</beans>

 

impl class:

package com.domain.mio.MiProj.ws.servicio.impl;

 

 

import javax.jws.WebMethod;

import javax.jws.WebParam;

import javax.jws.WebService;

import javax.xml.ws.RequestWrapper;

import javax.xml.ws.ResponseWrapper;

import org.apache.commons.logging.Log;

import org.apache.commons.logging.LogFactory;

import com.domain.mio.MiProj.entidades.periodosDedonacionRequestType;

import com.domain.mio.MiProj.entidades.periodosDedonacionResponseType;

import com.domain.mio.MiProj.entidades.NotificacionPagoRequestType;

import com.domain.mio.MiProj.entidades.NotificacionPagoResponseType;

import
com.domain.mio.MiProj.entidades.NotificaciondonacionValidacionTemporadaReque
stType;

import
com.domain.mio.MiProj.entidades.NotificaciondonacionValidacionTemporadaRespo
nseType;

import com.domain.mio.MiProj.ws.servicio.service.MiProjservicioWS;

import org.springframework.beans.factory.annotation.Autowired;

import org.springframework.context.ApplicationContext;

 

import org.springframework.beans.factory.annotation.Autowired;

import org.springframework.web.context.support.SpringBeanAutowiringSupport;

 

 

 

@WebService(

                       name="MiProjservicioWS",

                       serviceName="MiProjservicioWS",

                       targetNamespace="
<http://www.MiProj.org/MiProjservicioWS>
http://www.MiProj.org/MiProjservicioWS"  

                   )

public class MiProjservicioWSImpl extends SpringBeanAutowiringSupport {

                @Autowired

    private MiProjservicioWS trami;

 

                

                /*

                 * log

                 */

                private static final Log log =
LogFactory.getLog(MiProjservicioWSImpl.class);

                

 

 

                @WebMethod(operationName = "getperiodosDedonacionRequest")

                public periodosDedonacionResponseType
getperiodosDedonacionRequest(@WebParam(name =
"periodosDedonacionRequestType")periodosDedonacionRequestType
periodosDedonacionRequestType) {

 
trami.getperiodosDedonacionRequest(periodosDedonacionRequestType);

                               return null;

                }

 

                @WebMethod(operationName = "setNotificacionPagoRequest")

                public NotificacionPagoResponseType
setNotificacionPagoRequest(@WebParam(name =
"notificacionPagoRequestType")NotificacionPagoRequestType
notificacionPagoRequestType) {

 
trami.setNotificacionPagoRequest(notificacionPagoRequestType);

                               return null;

                }

 

                @WebMethod(operationName =
"setNotificaciondonacionValidacionTemporadaRequest")

                public NotificaciondonacionValidacionTemporadaResponseType
setNotificaciondonacionValidacionTemporadaRequest(@WebParam(name =
"notificaciondonacionValidacionTemporadaRequestType")

 
NotificaciondonacionValidacionTemporadaRequestType
notificaciondonacionValidacionTemporadaRequestType) {

 
trami.setNotificaciondonacionValidacionTemporadaRequest(notificaciondonacion
ValidacionTemporadaRequestType);

                               return null;

                }

 

}

 

 

ERROR:

2009-07-20 18:37:28,869 DEBUG
[org.springframework.beans.factory.xml.DefaultDocumentLoader] Using JAXP
provider [org.apache.xerces.jaxp.DocumentBuilderFactoryImpl]

2009-07-20 18:37:28,873 DEBUG
[org.springframework.beans.factory.xml.PluggableSchemaResolver] Loading
schema mappings from [META-INF/spring.schemas]

2009-07-20 18:37:28,875 DEBUG
[org.springframework.beans.factory.xml.PluggableSchemaResolver] Loaded
schema mappings:
{http://www.springframework.org/schema/lang/spring-lang-2.5.xsd=org/springfr
amework/scripting/config/spring-lang-2.5.xsd,
<http://www.springframework.org/schema/lang/spring-lang.xsd=org/springframew
ork/scripting/config/spring-lang-2.5.xsd>
http://www.springframework.org/schema/lang/spring-lang.xsd=org/springframewo
rk/scripting/config/spring-lang-2.5.xsd,
<http://www.springframework.org/schema/context/spring-context-2.5.xsd=org/sp
ringframework/context/config/spring-context-2.5.xsd>
http://www.springframework.org/schema/context/spring-context-2.5.xsd=org/spr
ingframework/context/config/spring-context-2.5.xsd,
<http://www.springframework.org/schema/context/spring-context.xsd=org/spring
framework/context/config/spring-context-2.5.xsd>
http://www.springframework.org/schema/context/spring-context.xsd=org/springf
ramework/context/config/spring-context-2.5.xsd,
<http://www.springframework.org/schema/util/spring-util-2.0.xsd=org/springfr
amework/beans/factory/xml/spring-util-2.0.xsd>
http://www.springframework.org/schema/util/spring-util-2.0.xsd=org/springfra
mework/beans/factory/xml/spring-util-2.0.xsd,
<http://www.springframework.org/schema/security/spring-security-2.0.xsd=org/
springframework/security/config/spring-security-2.0.xsd>
http://www.springframework.org/schema/security/spring-security-2.0.xsd=org/s
pringframework/security/config/spring-security-2.0.xsd,
<http://www.springframework.org/schema/security/spring-security-2.0.2.xsd=or
g/springframework/security/config/spring-security-2.0.2.xsd>
http://www.springframework.org/schema/security/spring-security-2.0.2.xsd=org
/springframework/security/config/spring-security-2.0.2.xsd,
<http://www.springframework.org/schema/util/spring-util-2.5.xsd=org/springfr
amework/beans/factory/xml/spring-util-2.5.xsd>
http://www.springframework.org/schema/util/spring-util-2.5.xsd=org/springfra
mework/beans/factory/xml/spring-util-2.5.xsd,
<http://www.springframework.org/schema/tool/spring-tool-2.0.xsd=org/springfr
amework/beans/factory/xml/spring-tool-2.0.xsd>
http://www.springframework.org/schema/tool/spring-tool-2.0.xsd=org/springfra
mework/beans/factory/xml/spring-tool-2.0.xsd,
<http://www.springframework.org/schema/beans/spring-beans-2.0.xsd=org/spring
framework/beans/factory/xml/spring-beans-2.0.xsd>
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd=org/springf
ramework/beans/factory/xml/spring-beans-2.0.xsd,
<http://www.springframework.org/schema/tool/spring-tool-2.5.xsd=org/springfr
amework/beans/factory/xml/spring-tool-2.5.xsd>
http://www.springframework.org/schema/tool/spring-tool-2.5.xsd=org/springfra
mework/beans/factory/xml/spring-tool-2.5.xsd,
<http://www.springframework.org/schema/beans/spring-beans-2.5.xsd=org/spring
framework/beans/factory/xml/spring-beans-2.5.xsd>
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd=org/springf
ramework/beans/factory/xml/spring-beans-2.5.xsd,
<http://www.springframework.org/schema/beans/spring-beans.xsd=org/springfram
ework/beans/factory/xml/spring-beans-2.5.xsd>
http://www.springframework.org/schema/beans/spring-beans.xsd=org/springframe
work/beans/factory/xml/spring-beans-2.5.xsd,
<http://www.springframework.org/schema/jee/spring-jee.xsd=org/springframewor
k/ejb/config/spring-jee-2.5.xsd>
http://www.springframework.org/schema/jee/spring-jee.xsd=org/springframework
/ejb/config/spring-jee-2.5.xsd,
<http://www.springframework.org/schema/security/spring-security-2.0.4.xsd=or
g/springframework/security/config/spring-security-2.0.4.xsd>
http://www.springframework.org/schema/security/spring-security-2.0.4.xsd=org
/springframework/security/config/spring-security-2.0.4.xsd,
<http://www.springframework.org/schema/tool/spring-tool.xsd=org/springframew
ork/beans/factory/xml/spring-tool-2.5.xsd>
http://www.springframework.org/schema/tool/spring-tool.xsd=org/springframewo
rk/beans/factory/xml/spring-tool-2.5.xsd,
<http://www.springframework.org/schema/security/spring-security.xsd=org/spri
ngframework/security/config/spring-security-2.0.4.xsd>
http://www.springframework.org/schema/security/spring-security.xsd=org/sprin
gframework/security/config/spring-security-2.0.4.xsd,
<http://www.springframework.org/schema/security/spring-security-2.0.1.xsd=or
g/springframework/security/config/spring-security-2.0.1.xsd>
http://www.springframework.org/schema/security/spring-security-2.0.1.xsd=org
/springframework/security/config/spring-security-2.0.1.xsd,
<http://www.springframework.org/schema/webflow-config/spring-webflow-config-
2.0.xsd=org/springframework/webflow/config/spring-webflow-config-2.0.xsd>
http://www.springframework.org/schema/webflow-config/spring-webflow-config-2
.0.xsd=org/springframework/webflow/config/spring-webflow-config-2.0.xsd,
<http://www.springframework.org/schema/jee/spring-jee-2.0.xsd=org/springfram
ework/ejb/config/spring-jee-2.0.xsd>
http://www.springframework.org/schema/jee/spring-jee-2.0.xsd=org/springframe
work/ejb/config/spring-jee-2.0.xsd,
<http://www.springframework.org/schema/oxm/spring-oxm-1.5.xsd=/org/springfra
mework/oxm/config/spring-oxm-1.5.xsd>
http://www.springframework.org/schema/oxm/spring-oxm-1.5.xsd=/org/springfram
ework/oxm/config/spring-oxm-1.5.xsd,
<http://www.springframework.org/schema/jee/spring-jee-2.5.xsd=org/springfram
ework/ejb/config/spring-jee-2.5.xsd>
http://www.springframework.org/schema/jee/spring-jee-2.5.xsd=org/springframe
work/ejb/config/spring-jee-2.5.xsd,
<http://www.springframework.org/schema/lang/spring-lang-2.0.xsd=org/springfr
amework/scripting/config/spring-lang-2.0.xsd>
http://www.springframework.org/schema/lang/spring-lang-2.0.xsd=org/springfra
mework/scripting/config/spring-lang-2.0.xsd,
<http://www.springframework.org/schema/util/spring-util.xsd=org/springframew
ork/beans/factory/xml/spring-util-2.5.xsd>
http://www.springframework.org/schema/util/spring-util.xsd=org/springframewo
rk/beans/factory/xml/spring-util-2.5.xsd}

2009-07-20 18:37:28,875 DEBUG
[org.springframework.beans.factory.xml.PluggableSchemaResolver] Found XML
schema [http://www.springframework.org/schema/beans/spring-beans-2.5.xsd] in
classpath: org/springframework/beans/factory/xml/spring-beans-2.5.xsd

2009-07-20 18:37:29,521 ERROR
[org.springframework.web.context.ContextLoader] Context initialization
failed

org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line
1 in XML document from ServletContext resource
[/WEB-INF/MiProjservicioWS-config.xml] is invalid; nested exception is
org.xml.sax.SAXParseException: White spaces are required between publicId
and systemId.

 at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefi
nitions(XmlBeanDefinitionReader.java:404)

 at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefini
tions(XmlBeanDefinitionReader.java:342)

 at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefini
tions(XmlBeanDefinitionReader.java:310)

 at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadB
eanDefinitions(AbstractBeanDefinitionReader.java:143)

 at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadB
eanDefinitions(AbstractBeanDefinitionReader.java:178)

 at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadB
eanDefinitions(AbstractBeanDefinitionReader.java:149)

 at
org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDef
initions(XmlWebApplicationContext.java:124)

 at
org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDef
initions(XmlWebApplicationContext.java:92)

 at
org.springframework.context.support.AbstractRefreshableApplicationContext.re
freshBeanFactory(AbstractRefreshableApplicationContext.java:123)

 at
org.springframework.context.support.AbstractApplicationContext.obtainFreshBe
anFactory(AbstractApplicationContext.java:422)

 at
org.springframework.context.support.AbstractApplicationContext.refresh(Abstr
actApplicationContext.java:352)

 at
org.springframework.web.context.ContextLoader.createWebApplicationContext(Co
ntextLoader.java:255)

 at
org.springframework.web.context.ContextLoader.initWebApplicationContext(Cont
extLoader.java:199)

 at
org.springframework.web.context.ContextLoaderListener.contextInitialized(Con
textLoaderListener.java:45)

 at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:
3856)

 at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4361)

 at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:7
90)

 at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:770)

 at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553)

 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

 at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)

 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)

 at java.lang.reflect.Method.invoke(Method.java:597)

 at
org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:296
)

 at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)

 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)

 at org.apache.catalina.core.StandardContext.init(StandardContext.java:5312)

 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

 at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)

 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)

 at java.lang.reflect.Method.invoke(Method.java:597)

 at
org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:296
)

 at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)

 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)

 at
org.jboss.web.tomcat.service.TomcatDeployer.performDeployInternal(TomcatDepl
oyer.java:301)

 at
org.jboss.web.tomcat.service.TomcatDeployer.performDeploy(TomcatDeployer.jav
a:104)

 at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:375)

 at org.jboss.web.WebModule.startModule(WebModule.java:83)

 at org.jboss.web.WebModule.startService(WebModule.java:61)

 at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.
java:289)

 at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupp
ort.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:597)

 at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java
:155)

 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)

 at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)

 at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:26
4)

 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)

 at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.jav
a: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:597)

 at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java
:155)

 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)

 at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)

 at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:26
4)

 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)

 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)

 at $Proxy44.start(Unknown Source)

 at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466)

 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

 at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)

 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)

 at java.lang.reflect.Method.invoke(Method.java:597)

 at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java
:155)

 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)

 at
org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java
:133)

 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)

 at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOpe
rationInterceptor.java:142)

 at
org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:9
7)

 at
org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServic
eMBeanSupport.java:238)

 at
org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerIntercepto
r.java:87)

 at
org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(S
ubDeployerInterceptorSupport.java:188)

 at
org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.ja
va:95)

 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)

 at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:26
4)

 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)

 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)

 at $Proxy45.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.GeneratedMethodAccessor21.invoke(Unknown Source)

 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)

 at java.lang.reflect.Method.invoke(Method.java:597)

 at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java
:155)

 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)

 at
org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java
:133)

 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)

 at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOpe
rationInterceptor.java:142)

 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)

 at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:26
4)

 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(URLDeploymentScanne
r.java:421)

 at
org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.
java:610)

 at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(
AbstractDeploymentScanner.java:263)

 at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(Ab
stractDeploymentScanner.java:274)

 at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(Abs
tractDeploymentScanner.java:225)

Caused by: org.xml.sax.SAXParseException: White spaces are required between
publicId and systemId.

 at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)

 at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)

 at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)

 at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)

 at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)

 at org.apache.xerces.impl.XMLScanner.scanExternalID(Unknown Source)

 at org.apache.xerces.impl.XMLDocumentScannerImpl.scanDoctypeDecl(Unknown
Source)

 at
org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(Unkn
own Source)

 at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)

 at org.apache.xerces.impl.xs.opti.SchemaParsingConfig.parse(Unknown Source)

 at org.apache.xerces.impl.xs.opti.SchemaParsingConfig.parse(Unknown Source)

 at org.apache.xerces.impl.xs.opti.SchemaDOMParser.parse(Unknown Source)

 at
org.apache.xerces.impl.xs.traversers.XSDHandler.getSchemaDocument(Unknown
Source)

 at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown
Source)

 at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(Unknown Source)

 at org.apache.xerces.impl.xs.XMLSchemaValidator.findSchemaGrammar(Unknown
Source)

 at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown
Source)

 at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown
Source)

 at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
Source)

 at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatc
her.dispatch(Unknown Source)

 at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)

 at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

 at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

 at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)

 at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)

 at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)

 at
org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(Def
aultDocumentLoader.java:75)

 at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefi
nitions(XmlBeanDefinitionReader.java:396)

 ... 102 more

2009-07-20 18:37:29,522 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/MiProjserv
icioWS]] Excepci??n enviando evento inicializado de contexto a instancia de
escuchador de clase org.springframework.web.context.ContextLoaderListener

 

org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line
1 in XML document from ServletContext resource
[/WEB-INF/MiProjservicioWS-config.xml] is invalid; nested exception is
org.xml.sax.SAXParseException: White spaces are required between publicId
and systemId.

 at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefi
nitions(XmlBeanDefinitionReader.java:404)

 at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefini
tions(XmlBeanDefinitionReader.java:342)

 at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefini
tions(XmlBeanDefinitionReader.java:310)

 at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadB
eanDefinitions(AbstractBeanDefinitionReader.java:143)

 at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadB
eanDefinitions(AbstractBeanDefinitionReader.java:178)

 at org.springframework.beans.factory.support.AbstractBeanDefinit

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossws-users/attachments/20090721/28654d1e/attachment.html 

From do-not-reply at jboss.com  Tue Jul 21 01:22:11 2009
From: do-not-reply at jboss.com (sumanta306)
Date: Tue, 21 Jul 2009 01:22:11 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - javax.xml.ws.WebServiceException: WSDL
	metadata is missing i
Message-ID: <8620008.1248153731499.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I'm using JBoss-4.2.2GA with jbossws-native-3.1.2.GA.
i  deployed stateful webservice without any error.
But calling this Webservice I  get this exception in client: 

Exception in thread "main" javax.xml.ws.WebServiceException: WSDL metadata is missing in EPR
  | 	at com.sun.xml.ws.spi.ProviderImpl.getPort(ProviderImpl.java:147)
  | 	at javax.xml.ws.EndpointReference.getPort(Unknown Source)
  | 	at stateful.client.BookService.getPort(BookService.java:48)
  | 	at stateful.client.Main.main(Main.java:33)

my client code is :

BookService class:

@WebServiceClient(name = "BookService", targetNamespace = "http://server.stateful/", wsdlLocation = "http://localhost:8080/StatefulWS/book?wsdl")
  | public class BookService extends Service {
  | 
  | 	private final static URL SERVICE_WSDL_LOCATION;
  | 	static {
  | 		URL url = null;
  | 		try {
  | 			url = new URL("http://localhost:8080/StatefulWS/book?wsdl");
  | 		} catch (MalformedURLException e) {
  | 			e.printStackTrace();
  | 		}
  | 		SERVICE_WSDL_LOCATION = url;
  | 	}
  | 
  | 	public BookService(URL wsdlDocumentLocation, QName serviceName) {
  | 		super(wsdlDocumentLocation, serviceName);
  | 
  | 	}
  | 
  | 	public BookService() {
  | 		super(SERVICE_WSDL_LOCATION, new QName("http://server.stateful/",
  | 				"BookService"));
  | 	}
  | 
  | 	@WebEndpoint(name = "BookService")
  | 	public BookRemote getPort() {
  | 		return (BookRemote) super.getPort(new QName("http://server.stateful/", "BookPort"),	BookRemote.class);
  | 	}
  | 	
  | 	@WebEndpoint(name = "BookService")
  | 	public BookRemote getPort(EndpointReference ref, Class<BookRemote> cl) {
  | 
  | 		
  | 		return ref.getPort(cl);
  | 	}
  | 	
  | 
  | }




main class::::

 BookStoreRemote bookstore = new BookStoreService().getBookStorePort();
  |         BookService service = new BookService();
  | 
  |                
  |         BookRemote book1 = service.getPort(bookstore.getProduct("abc001"),BookRemote.class);
  | 


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

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


From do-not-reply at jboss.com  Tue Jul 21 03:14:55 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Tue, 21 Jul 2009 03:14:55 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: NotImplementedException
Message-ID: <18058359.1248160495874.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi,

   from the stack trace I see you're mixing Sun webservices and JBossWS-Native libraries. This is your problem.
If you want to use Metro in JBoss, then install JBossWS-Metro integration properly to the JBoss AS and refer to the libraries installed by the ant deploy-XYZ target only.

Richard

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

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


From do-not-reply at jboss.com  Tue Jul 21 03:18:57 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Tue, 21 Jul 2009 03:18:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JAXWS on JBoss 4.2.2
Message-ID: <4265677.1248160737113.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi,

   JBossWS community version doesn't support JBoss 4.x series and below anymore.
I highly recommend you to switch to JBossAS 5.1.0 

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

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


From do-not-reply at jboss.com  Tue Jul 21 03:24:58 2009
From: do-not-reply at jboss.com (ashutoshdeora)
Date: Tue, 21 Jul 2009 03:24:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WSDL metadata
Message-ID: <9821878.1248161098948.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

can any one tell me what is the meaning of WSDL metadata 
please explain this 
i am facing the problem of missing WSDL metadata 


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

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


From do-not-reply at jboss.com  Tue Jul 21 03:25:41 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Tue, 21 Jul 2009 03:25:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: javax.xml.ws.WebServiceException:
	WSDL metadata is missi
Message-ID: <6226384.1248161141940.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi, 

   I see two issues here. First JBossWS-Native-3.1.2 is supported on AS 5.x series and above only. The second issue I see is you're using wrong classpath. I see sun libraries in the stack trace. Please ensure you're using AS 5.x version and correct JBossWS-Native classpath in your IDE.

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

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


From do-not-reply at jboss.com  Tue Jul 21 04:04:30 2009
From: do-not-reply at jboss.com (pio1k)
Date: Tue, 21 Jul 2009 04:04:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Inheritance problem
Message-ID: <6263835.1248163470144.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hello.

I have a problem with class inheritance in web services. I want to make a web service with one method to add objects of classes (B, C and other in the future) which inheritated from my basic class (A). My source code:

Server side:
1) TestService.java
@WebService(serviceName = "TestService")
  | @Stateless
  | @XmlSeeAlso({B.class, C.class})
  | public class TestService {
  |     @EJB
  |     TestMgmtLocal             tl  = null;
  |     
  |     @WebMethod(operationName = "testAddA")  
  |     public @WebResult(name = "A")  
  |     A testAddA(@WebParam(name = "testA") A testA) {
  |         return tl.testAddA(testA);
  |     }
  | }

2) TestMgmtLocal.java
@Local
  | public interface TestMgmtLocal extends TestMgmtRemote {
  |  
  | }

3) TestMgmtRemote.java
@Remote
  | public interface TestMgmtRemote {
  |     A testAddA(A testA);
  | }

4) TestMgmt.java
@Stateless
  | public class TestMgmt implements TestMgmtLocal {
  |     @Resource
  |     private SessionContext ctx = null;
  |     
  |     public A testAddA(A testA) {
  |         if (testA instanceof A) {
  |             System.out.println("class A");
  |         }
  |         
  |         if (testA instanceof B) {
  |             System.out.println("class B");
  |         }
  |         
  |         if (testA instanceof C) {
  |             System.out.println("class C");
  |         }
  |         
  |         return testA;
  |     }
  | }

5) A.java
public class A implements Serializable {
  |  
  |     private static final long serialVersionUID = 110181269433550832L;
  |  
  |     private int a = -1;
  |  
  |     public int getA() {
  |         return a;
  |     }
  |  
  |     public void setA(int a) {
  |         this.a = a;
  |     }
  | }

6) B.java
public class B extends A implements Serializable {
  |  
  |     private static final long serialVersionUID = 6921792702940813727L;
  |  
  |     private int b = -1;
  |  
  |     public int getB() {
  |         return b;
  |     }
  |  
  |     public void setB(int b) {
  |         this.b = b;
  |     }
  | }

7) C.java
public class C extends A implements Serializable {
  |  
  |     private static final long serialVersionUID = 7823155353151239133L;
  |  
  |     private int c = -1;
  |  
  |     public int getC() {
  |         return c;
  |     }
  |  
  |     public void setC(int c) {
  |         this.c = c;
  |     }
  | }

Client side:
1) TestClient.java
public class TestClient {
  |  
  | 	public static void main(String[] args) {
  | 		TestServiceProxy proxy = new TestServiceProxy();
  | 		TestService_PortType port = proxy.getTestService_PortType();
  | 		try {
  | 			C c = new C();
  | 			c.setA(2);
  | 			c.setC(3);
  | 			port.testAddA(c);
  | 		} catch(RemoteException e) {
  | 			System.out.println(e);
  | 		}
  | 	}
  | }


I found this page:
http://blog.vinodsingh.com/2008/09/anytype-object-over-webservice-and.html
but it doesn't work in my web service. In testAddA method I always get an object of A class (when I send from client object of B or C class). I've also tried to add @XmlSeeAlso annotation to A class but it doesn't help. Maybe I did something wrong? Any ideas? Any other solutions of this problem?

I'm using:
1) JBoss 4.2.3GA (I tired also on JBoss 5.1.GA)
2) Java 1.5 update 15 

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

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


From do-not-reply at jboss.com  Tue Jul 21 04:28:09 2009
From: do-not-reply at jboss.com (ashutoshdeora)
Date: Tue, 21 Jul 2009 04:28:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: javax.xml.ws.WebServiceException:
	WSDL metadata is missi
Message-ID: <32919717.1248164889854.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

i am also facing the same problem as mentioned above 
i am using AS 5.x 
but still i am getting this error 

my requirement is a bit different 
i have to use AS 4.2.3 
so what JBossWS-Native version i should use for this 
and second thing is 
my web service should be STATEFUL 
i cannot use stateless WEBSERVICE 

and the change of class path which you have mentioned in the post
which is releated to the getPort()

which path i have to change 

i need to use the EndpointReference 
the jar having this is rt.jar (this is in the java jre )

the another is in JBOSSRUNTIME LIB named as jaxws-rt.jar 
which one i have to remove or modify  please tell 







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

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


From do-not-reply at jboss.com  Tue Jul 21 05:57:39 2009
From: do-not-reply at jboss.com (_guido)
Date: Tue, 21 Jul 2009 05:57:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem JBOSS-5.1.GA-jdk6 and
	WebService:SOAP request ex
Message-ID: <31886893.1248170259114.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hello,

i have the same problem (jboss-5.1.0.GA-jdk6   &  jdk6  (& debian linux)).

i got the "setProperty must be overwritten...."-Exception when i access my simple stateless session bean webservice. this service is working without problems under jboss-5.1.0.GA & jdk5.

this is a part of classes loaded at a jboss start (perhaps this helps):


  | [Loaded javax.xml.soap.SOAPMessage from /home/guido/appz/jboss-5.1.0.GA/lib/endorsed/jbossws-native-saaj.jar]
  | [Loaded org.jboss.ws.core.soap.SOAPMessageImpl from jar:file:/home/guido/appz/jboss-5.1.0.GA/server/default/deployers/jbossws.deployer/jbossws-native-core.jar!/]
  | 

thx for your help,
guido

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

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


From do-not-reply at jboss.com  Tue Jul 21 06:36:37 2009
From: do-not-reply at jboss.com (konstt2000)
Date: Tue, 21 Jul 2009 06:36:37 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Problem deploy WS in JBOSS 4.3
Message-ID: <20276957.1248172597587.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi,

I've work with WS. 

@WebService
  | @SOAPBinding(
  | 		  style = SOAPBinding.Style.DOCUMENT,
  | 	      use = SOAPBinding.Use.LITERAL,
  | 	      parameterStyle = SOAPBinding.ParameterStyle.WRAPPED
  | 	 )
  | public class WebServiceGde {
  | 	
  | 	
  | 	@WebMethod
  | 	public ResultadoGde guardar(MiClase solicitudes){
  | 		
  | 		ResultadoGde resultadoGde = new ResultadoGde();		
  | 		resultadoGde.setCodigoError(11);
  | 		resultadoGde.setDescripcion("KO");
  | 		
  | 		return resultadoGde;
  | 	}	
  | }


public class MiClase {
  | 	private long cdSolicitud;
  | 	private int cdEstado;
  | 	private int cdTipoSolicitud;
  | 	private String cdTipoTrans;
  | 	private Date fechaRecepc;
  | 	
  | 	private Date fechaUltModif;
  | 	private String origen;
  | 	private Long idProcesoBpm;
  | 	private String estadoInterno;
  | 	private String notas;
  | 		
  | 	private String indExento;
  | 	private String indCartera;
  | 	private String indTarifa;
  | 	private String indesglo;
  | 	private String desviosx;
  | 	
  | 	private String secundar;
  | 	private String terciari;
  | 	private String segdiari;
  | 	private String segintra;
  | 	private boolean invirtua;
  | 	
  | 	private String segtreal;
  | 	/*private String resecund;
  | 	private String pruebasx;*/
  |         //Getter and Setter..

If I deployment:
12:25:59,122 INFO  [DefaultEndpointRegistry] register: jboss.ws:context=WebServicesGDE,endpoint=WebServiceGde
  | 12:25:59,122 INFO  [DefaultEndpointRegistry] register: jboss.ws:context=WebServicesGDE,endpoint=HolaMundoWs
  | 12:25:59,154 INFO  [TomcatDeployer] deploy, ctxPath=/WebServicesGDE, warUrl=.../tmp/deploy/tmp55743WebServicesGDE-exp.war/
  | 12:25:59,325 ERROR [MainDeployer] Could not start deployment: file:/D:/jboss-soa-p.4.3.0/jboss-as_SOA/server/default/deploy/WebServicesGDE.war
  | java.lang.ClassFormatError: Invalid constant pool index 63 in class file es/ree/gde/webservice/modelo/MiClase
  | 	at java.lang.ClassLoader.defineClass1(Native Method)

I've tring delete some parameter the MiClase.java and it work fine.
If I add more parameter the error:
java.lang.ClassFormatError: Repetitive
  | > > method name/signature...

I've tring with JDK5 and JDK6

?????? It's a bug JBOSS ?

Thanks.

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

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



From do-not-reply at jboss.com  Thu Jul 23 08:39:58 2009
From: do-not-reply at jboss.com (_guido)
Date: Thu, 23 Jul 2009 08:39:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem JBOSS-5.1.GA-jdk6 and
	WebService:SOAP request ex
Message-ID: <10744265.1248352798521.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

thank you jlankfo,

this helps me a lot because i started the server with the run.sh script (usually i used the eclipse ide) and the webservice works fine (finally: without any changes at the script:)).

eclipse uses the run.jar to start jboss. 
i added:

 -Djava.endorsed.dirs=.......jboss-5.1.0.GA/lib/endorsed 

to the server vm arguments in eclipse and everything works perfect.

thanks for the push to the solution,

guido




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

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


From do-not-reply at jboss.com  Thu Jul 23 07:53:28 2009
From: do-not-reply at jboss.com (nikhilm)
Date: Thu, 23 Jul 2009 07:53:28 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JAXWS on JBoss 4.2.2
Message-ID: <4350213.1248350008518.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I shall switch over to jboss-5.*, but the problem was of few unwanted older jars kept on deploy, which probably were causing the problems. After cleaning up the deploy directory and putting jaxb-api-2.1 in endorsed.. the web service was up. 

Thanks..

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

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


From do-not-reply at jboss.com  Wed Jul 22 14:25:16 2009
From: do-not-reply at jboss.com (andrewe)
Date: Wed, 22 Jul 2009 14:25:16 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Resteasy,
	handling and logging of WebApplicationExceptio
Message-ID: <30717553.1248287116631.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Little late, but I noticed the same thing - JBoss seems to log to STDERR for things I didn't expect (like when a resource is deployed via jax.ws.rs.Application class). 

I thought it would show up via my log4j appender, but no such luck. Is this a bug in Resteasy?

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

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


From do-not-reply at jboss.com  Wed Jul 22 15:01:50 2009
From: do-not-reply at jboss.com (jlankfo)
Date: Wed, 22 Jul 2009 15:01:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem JBOSS-5.1.GA-jdk6 and
	WebService:SOAP request ex
Message-ID: <25098980.1248289310288.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

According to the release notes no confiugration changes should be needed if the jdk6 version was downloaded but it also suggests one other thing.

anonymous wrote : The other option is to download the jdk6 distribution (jboss-5.0.0.GA-jdk6.zip) in which case no configuration changes are required. If you still have problems using JBoss with a Sun Java 6 runtime, you may want to set  -Dsun.lang.ClassLoader.allowArraySyntax=true, as described in http://jira.jboss.com/jira/browse/JBAS-4491.

Also make sure jaxb-api.jar is in the endorsed folder as well.

Might I suggest temporarily deleting the other copies of the jar files, which are usually in the jboss/client folder and jboss/lib, just to see if this is the problem.

jar files:

jaxb-api.jar
jbossws-native-saaj.jar
jbossws-native-jaxrpc.jar
jbossws-native-jaxws.jar
jbossws-native-jaxws-ext.jar 
[/url]

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

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


From do-not-reply at jboss.com  Wed Jul 22 13:38:45 2009
From: do-not-reply at jboss.com (jlankfo)
Date: Wed, 22 Jul 2009 13:38:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Invalid number of payload elements
Message-ID: <17010358.1248284325461.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Sorry I have searched and searched but I can't find information on this error anywhere. I am attempting to add a soap fault to a soap context in a rather large application. The code to add the fault is below.


  | SOAPFactory soapFactory = SOAPFactory.newInstance();
  |           SOAPBody soapbody = soapMsgContext.getMessage().getSOAPBody();
  |           SOAPFault fault = soapbody.getFault();
  |           fault = soapbody.addFault();
  |           Name fc = soapFactory.createName("Server",null,SOAPConstants.URI_NS_SOAP_ENVELOPE);
  |           fault.setFaultCode(fc);
  |           fault.setFaultString("Testing123");
  |           fault.setFaultActor("http://localhost:8080/Converter");
  |           fault.addDetail().addChildElement("test");
  | 

I keep getting this error and I don't have any clue what it means.


  | org.jboss.ws.WSException: Invalid number of payload elements: 2
  | 	at org.jboss.ws.core.CommonSOAPBinding.unbindRequestMessage(CommonSOAPBinding.java:379)
  | 	at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:213)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:474)
  | 	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.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85)
  | 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
  | 	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:191)
  | 	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
  | 	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
  | 	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
  | 	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
  | 	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:158)
  | 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
  | 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
  | 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
  | 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
  | 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
  | 	at java.lang.Thread.run(Thread.java:619)
  | 

Can anyone shed some light on this error? 

Note: I am adding other things to the header but the application works fine without the above fault script however it is when I add it in that it starts breaking.

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

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


From do-not-reply at jboss.com  Wed Jul 22 02:59:40 2009
From: do-not-reply at jboss.com (edward.yakop)
Date: Wed, 22 Jul 2009 02:59:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - maven archetype for jbossws + metro
Message-ID: <18259557.1248245980083.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi,

Is there a maven archetype for this stack?
I'm interested with generating wsdl/consume and integration test.

Regards,
Edward Yakop

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

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


From do-not-reply at jboss.com  Tue Jul 21 15:49:37 2009
From: do-not-reply at jboss.com (jlankfo)
Date: Tue, 21 Jul 2009 15:49:37 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: NotImplementedException
Message-ID: <9421985.1248205777655.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

So I can't edit my posts but what I ment to say instead of jbossws is native...

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

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


From do-not-reply at jboss.com  Tue Jul 21 15:47:32 2009
From: do-not-reply at jboss.com (jlankfo)
Date: Tue, 21 Jul 2009 15:47:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: NotImplementedException
Message-ID: <133129.1248205652587.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

That makes sense but it leaves me with a few more questions. Why is it using sun web services for the client and jbossws for the server? Is there a way I can make the client use jbossws services or do I need metro? And finally why would metro work differently?

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

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


From do-not-reply at jboss.com  Tue Jul 21 16:00:28 2009
From: do-not-reply at jboss.com (konstt2000)
Date: Tue, 21 Jul 2009 16:00:28 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem deploy WS in JBOSS 4.3
Message-ID: <28967328.1248206428916.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

"PeterJ" wrote : Are you working in Eclipse or some other IDE? It sounds like the MiClase.class file is invalid. Check the description of ClassFormatError in the javadocs.

I'm working in Eclipse, but I've compiled also without using eclipse with the same result.

I have removed the getter and setter and have put the attributes as public for MiClase.java and it works, but it does not look like to me an acceptable solution.

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

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


From do-not-reply at jboss.com  Tue Jul 21 12:56:12 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 21 Jul 2009 12:56:12 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem deploy WS in JBOSS 4.3
Message-ID: <28698787.1248195372923.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Are you working in Eclipse or some other IDE? It sounds like the MiClase.class file is invalid. Check the description of ClassFormatError in the javadocs.

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

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


From do-not-reply at jboss.com  Thu Jul 23 13:53:32 2009
From: do-not-reply at jboss.com (vav)
Date: Thu, 23 Jul 2009 13:53:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Problem with getting port
Message-ID: <29492497.1248371612016.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi, 

I'm using JBoss 4.0.4 + jbossws-native-2.0.3.GA.
I have created a simple ws:


  | @WebService
  | (
  |     name = "TestJSE",
  |     serviceName = "TestJSEService",
  |     portName = "TestJSEPort",
  |     targetNamespace = "http://com.tbs.webservice/test"
  | )
  | @SOAPBinding(style = SOAPBinding.Style.RPC)
  | public class TestJSE
  | {
  |    @WebMethod
  |    public String testGetMessageContext()
  |    {
  |       return "TEST!";
  |    }
  | }
  | 

Than I've packed it into war i successfully deployed.
The wsdl accessed via browser.

My web.xml config is here:

  |     <servlet>
  |         <servlet-name>TestJSE</servlet-name>
  |         <servlet-class>com.tbs.webservice.TestJSE</servlet-class>
  |     </servlet>
  |     <servlet-mapping>
  |         <servlet-name>TestJSE</servlet-name>
  |         <url-pattern>/*</url-pattern>
  |     </servlet-mapping>
  | 

But when I try to make a client test, I get error:

  | java.lang.NoClassDefFoundError: javassist/ClassPath
  | 	at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.initWrapperGenerator(JAXWSMetaDataBuilder.java:919)
  | 	at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.resetMetaDataBuilder(JAXWSMetaDataBuilder.java:926)
  | 	at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(JAXWSClientMetaDataBuilder.java:280)
  | 	at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortInternal(ServiceDelegateImpl.java:264)
  | 	at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:195)
  | 	at javax.xml.ws.Service.getPort(Service.java:115)
  | 	at com.tbs.webservice.Tests.testApplClientAccessJSE(Tests.java:21)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:40)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)
  | 

My test is:

  |         URL wsdlLocation = new URL("http://127.0.0.1:8080/test?wsdl");
  |         QName serviceName = new QName("http://com.tbs.webservice/test", "TestJSEService");
  |         Service service = Service.create(wsdlLocation, serviceName);
  |         service.getPort(new QName("http://com.tbs.webservice/test", "TestJSEPort"), TestJSEI.class);
  |         assertEquals("The 'mafia' boss is currently out of office, please call again.", true);
  | 

Can somebody help me with this?
Thanks!

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

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


From do-not-reply at jboss.com  Thu Jul 23 15:10:43 2009
From: do-not-reply at jboss.com (sanrosh95)
Date: Thu, 23 Jul 2009 15:10:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - How to Connect to a JBoss WS Protected
	by FORM Based Authent
Message-ID: <23790588.1248376243628.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi ,

I have a Jboss Web Service and the URL is Protected using Form Based authentication .

How can i consume a web service which is protected by FORM Based authentication i have seen example of only BASIC authentication

Thanks
San

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

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


From do-not-reply at jboss.com  Thu Jul 23 16:47:52 2009
From: do-not-reply at jboss.com (sasanplus)
Date: Thu, 23 Jul 2009 16:47:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Inspecting Web application
Message-ID: <31303442.1248382072532.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi,

I am trying to get the list of web services from a given .war file. I do not want to use JMX or lookinto web.xml.

is there a way through JBossWS API?

Thanks,
Sasan

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

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


From do-not-reply at jboss.com  Thu Jul 23 17:42:45 2009
From: do-not-reply at jboss.com (mornblues)
Date: Thu, 23 Jul 2009 17:42:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WS on a web project
Message-ID: <22838996.1248385365722.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hello, I'm a little lost around here, I need pointers where to start. I have a web project deployed on jboss 4.2.3 as a war. I want to export some of its model as an web service. I'm hoping to be able to simply annotate a few interfaces and have them exported as web services, not sure if that's possible.

I have done a little google and there seems to be a lot of web service implementations for java, I'm aiming for the one with the simplest integration with jboss 4.2.3. Maybe there's something already embedded to it? Things aren't very clear to me right now.

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

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


From do-not-reply at jboss.com  Thu Jul 23 17:45:00 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Thu, 23 Jul 2009 17:45:00 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Inspecting Web application
Message-ID: <24835262.1248385500433.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

With the app server running, go to http://loclahost:8080/jbossws, and click the "View a list of deployed services" link.

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

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


From do-not-reply at jboss.com  Thu Jul 23 17:54:14 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Thu, 23 Jul 2009 17:54:14 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS on a web project
Message-ID: <21121477.1248386054768.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Look at the free chapter 9 at http://manning.com/jamae/, it covers web services. While the book is geared towards AS 5.x, the web services should work the same on 4.2.3 since both 4.2.x and 5.x use fairly compatible versions of JBoss WS.

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

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


From do-not-reply at jboss.com  Thu Jul 23 19:03:28 2009
From: do-not-reply at jboss.com (sasanplus)
Date: Thu, 23 Jul 2009 19:03:28 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Inspecting Web application
Message-ID: <14908286.1248390208727.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

actually I meant programmatically.

I am getting Jboss local MBeanServer and I am querying my domain, but I can not get to my MBean through queries.

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

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


From do-not-reply at jboss.com  Fri Jul 24 02:21:04 2009
From: do-not-reply at jboss.com (ashutoshdeora)
Date: Fri, 24 Jul 2009 02:21:04 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: javax.xml.ws.WebServiceException:
	WSDL metadata is missi
Message-ID: <5293232.1248416464018.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

i am posting the web.xml here 
please tell what to change in this 


<?xml version="1.0" encoding="UTF-8"?>
  | <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
  |   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  |   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
  |   version="2.4">
  |   <display-name>TestStateFulWSMetro</display-name>
  |   
  | 	<listener>
  | 		<listener-class>
  | 			com.sun.xml.ws.transport.http.servlet.WSServletContextListener  			
  | 		</listener-class>
  | 	</listener>
  | 
  | 	<servlet>
  | 		<!--description>JAX-WS endpoint</description-->
  | 		<!--display-name>JAX-WS servlet</display-name-->
  | 		<servlet-name>jaxWsServlet</servlet-name>
  | 		<servlet-class>com.sun.xml.ws.transport.http.servlet.WSServlet</servlet-class>
  | 		<!-- load-on-startup>1</load-on-startup-->
  | 	</servlet>
  | 	<servlet-mapping>
  | 		<servlet-name>jaxWsServlet</servlet-name>
  | 		<url-pattern>/book</url-pattern>
  | 	</servlet-mapping>
  | 	<servlet-mapping>
  | 		<servlet-name>jaxWsServlet</servlet-name>
  | 		<url-pattern>/bookstore</url-pattern>
  | 	</servlet-mapping>
  | 
  | 
  | 
  | 	<session-config>
  | 		<session-timeout>60</session-timeout>
  | 	</session-config>
  |   <welcome-file-list>
  |     <welcome-file>index.html</welcome-file>
  |     <welcome-file>index.htm</welcome-file>
  |     <welcome-file>index.jsp</welcome-file>
  |     <welcome-file>default.html</welcome-file>
  |     <welcome-file>default.htm</welcome-file>
  |     <welcome-file>default.jsp</welcome-file>
  |   </welcome-file-list>
  | </web-app>

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

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


From do-not-reply at jboss.com  Fri Jul 24 05:53:17 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Fri, 24 Jul 2009 05:53:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: javax.xml.ws.WebServiceException:
	WSDL metadata is missi
Message-ID: <17975350.1248429197176.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

"ashutoshdeora" wrote : 
  | i have to use AS 4.2.3 
  | so what JBossWS-Native version i should use for this 
  |  See this matrix.
"ashutoshdeora" wrote : 
  | my web service should be STATEFUL 
  | i cannot use stateless WEBSERVICE 
  | 
The JBossWS webservices have been always stateful.
But there was a bug with instance reuse, see JBWS-2486.
Luckily this issue have been fixed in JBossWS Native 3.1.1, so you're ready
to go with JBossWS-Native-3.1.1.GA on JBossAS-4.2.3 ;)
"ashutoshdeora" wrote : 
  | i need to use the EndpointReference 
  | the jar having this is rt.jar (this is in the java jre )
  | 
  | the another is in JBOSSRUNTIME LIB named as jaxws-rt.jar 
  | which one i have to remove or modify  please tell 
  | 
I'm getting really confused :( So you're using JBossWS Native or JBossWS Metro?
This JBossWS-Native forum, for JBossWS-Metro specific user questions please use this forum.


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

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


From do-not-reply at jboss.com  Fri Jul 24 05:58:04 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Fri, 24 Jul 2009 05:58:04 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: javax.xml.ws.WebServiceException:
	WSDL metadata is missi
Message-ID: <3058608.1248429484986.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

"ashutoshdeora" wrote : i am posting the web.xml here 
  | please tell what to change in this 
  | 

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

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


From do-not-reply at jboss.com  Fri Jul 24 06:14:37 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Fri, 24 Jul 2009 06:14:37 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Inspecting Web application
Message-ID: <28581926.1248430477686.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

"sasanplus" wrote : 
  | is there a way through JBossWS API?
  | 
This sounds really hacky, don't it?
OK, you can use JBossWS SPI (see our code base),
but as it's not J2EE standard it is possible it will change in the future.
In other words if you're going to use proprietary API,
remember that your solution might not be portable in the future ;)

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

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


From do-not-reply at jboss.com  Fri Jul 24 06:15:53 2009
From: do-not-reply at jboss.com (ashutoshdeora)
Date: Fri, 24 Jul 2009 06:15:53 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: javax.xml.ws.WebServiceException:
	WSDL metadata is missi
Message-ID: <5168019.1248430553376.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>


sorry there is no Metro any where in this project 
if you have told it by name 
then its my mistake i am very sorry for that 
i am using JBoss Native WS  
i will follow your suggestion 
i want to know about the class path which u have mentioned in your 1st reply 

please tel about that 



 

<?xml version="1.0" encoding="UTF-8"?>
  | <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
  |   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  |   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
  |   version="2.4">
  |   <display-name>TestStateFulWS</display-name>
  |   
  | 	<listener>
  | 		<listener-class>
  | 			com.sun.xml.ws.transport.http.servlet.WSServletContextListener  			
  | 		</listener-class>
  | 	</listener>
  | 
  | 	<servlet>
  | 		<!--description>JAX-WS endpoint</description-->
  | 		<!--display-name>JAX-WS servlet</display-name-->
  | 		<servlet-name>jaxWsServlet</servlet-name>
  | 		<servlet-class>com.sun.xml.ws.transport.http.servlet.WSServlet</servlet-class>
  | 		<!-- load-on-startup>1</load-on-startup-->
  | 	</servlet>
  | 	<servlet-mapping>
  | 		<servlet-name>jaxWsServlet</servlet-name>
  | 		<url-pattern>/book</url-pattern>
  | 	</servlet-mapping>
  | 	<servlet-mapping>
  | 		<servlet-name>jaxWsServlet</servlet-name>
  | 		<url-pattern>/bookstore</url-pattern>
  | 	</servlet-mapping>
  | 
  | 
  | 
  | 	<session-config>
  | 		<session-timeout>60</session-timeout>
  | 	</session-config>
  |   <welcome-file-list>
  |     <welcome-file>index.html</welcome-file>
  |     <welcome-file>index.htm</welcome-file>
  |     <welcome-file>index.jsp</welcome-file>
  |     <welcome-file>default.html</welcome-file>
  |     <welcome-file>default.htm</welcome-file>
  |     <welcome-file>default.jsp</welcome-file>
  |   </welcome-file-list>
  | </web-app>	

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

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


From do-not-reply at jboss.com  Fri Jul 24 06:17:10 2009
From: do-not-reply at jboss.com (vav)
Date: Fri, 24 Jul 2009 06:17:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem with getting port
Message-ID: <27641925.1248430630988.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

The problem solved.
Just removed javaee.jar from a project.

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

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


From do-not-reply at jboss.com  Fri Jul 24 06:24:03 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Fri, 24 Jul 2009 06:24:03 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: javax.xml.ws.WebServiceException:
	WSDL metadata is missi
Message-ID: <27875195.1248431043339.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

"ashutoshdeora" wrote : 
  | i want to know about the class path which u have mentioned in your 1st reply 
  | 
You have to reference jbossws jars in your client classpath only.
You also need to set -Djava.endorsed.dirs=$JBOSS_HOME/lib/endorsed in your client classpath (IDE or shell script)

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

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


From do-not-reply at jboss.com  Fri Jul 24 11:14:43 2009
From: do-not-reply at jboss.com (yonghongb)
Date: Fri, 24 Jul 2009 11:14:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WSDL is not genreated
Message-ID: <25671504.1248448483096.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi,

I'm using jboss 4.2.2GA, JBOSSWS native 3.0.4, jdk 1.5

I created a web service and a client application in my local using eclipse. Everything was fine. 

I created a war file and deploy it to our test server jboss/../../deploy.

WSDL is not genreated.

Any idea?

Thanks

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

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


From do-not-reply at jboss.com  Fri Jul 24 13:10:09 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 24 Jul 2009 13:10:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSDL is not genreated
Message-ID: <25147063.1248455409611.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

The WSDL is generated dynamically(?) when asked for. Go to  http://localhost:8080/jbossws and click on the "View a list of deployed services" and then click on the WSDL link for your service. Also note the URL - you can use it at any time to see the WSDL.

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

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


From do-not-reply at jboss.com  Fri Jul 24 13:56:44 2009
From: do-not-reply at jboss.com (yonghongb)
Date: Fri, 24 Jul 2009 13:56:44 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSDL is not genreated
Message-ID: <4837916.1248458204914.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Thanks for your replay. I went to http:hostname:port/jbossws/services.
I got : There are currently no endpoints deployed.

I checked jboss/.../data/wsdl ,  there is no myApp.war folder there.

Any idea?

Thanks






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

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


From do-not-reply at jboss.com  Fri Jul 24 14:01:07 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 24 Jul 2009 14:01:07 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSDL is not genreated
Message-ID: <19975386.1248458467998.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Did you declare any endpoints in your app? If so, could you post one of your endpoints?

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

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


From do-not-reply at jboss.com  Fri Jul 24 14:21:07 2009
From: do-not-reply at jboss.com (sinjem)
Date: Fri, 24 Jul 2009 14:21:07 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBoss 5.0.1.GA Native Maven2 Eclipse
	POM dependencies: deplo
Message-ID: <4759384.1248459667962.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I'm trying to build a quick and simple JBossws annotated web service that deploys in a war. Everything works great in eclipse (3.4) with JBoss Tools. 

However, as soon as I enabled Maven2 on the project and remove the JBoss Runtime java build path dependency the project will no longer deploy within eclipse. I've tried every pom dependency configuration I can think of with no luck.

Does anyone have this working who is willing to share the dependency tags from their pom.xml with me? 

Here's what I have that is not working:

<dependencies>
  | 		<dependency>
  | 			<groupId>junit</groupId>
  | 			<artifactId>junit</artifactId>
  | 			<version>4.6</version>
  | 			<scope>test</scope>
  | 		</dependency>
  | 		<dependency>
  | 			<groupId>org.jboss.jbossas</groupId>
  | 			<artifactId>jboss-as-main</artifactId>
  | 			<version>5.0.1.GA</version>
  | 		</dependency>
  | 		<dependency>
  | 			<groupId>jboss.jbossws</groupId>
  | 			<artifactId>jboss-jaxws</artifactId>
  | 			<version>3.0.1-native-2.0.4.GA</version>
  | 		</dependency>
  | 	</dependencies>

If there's a tutorial somewhere that describes this I'd appreciate that as a response too. Any help is greatly appreciated.

  -Jeff

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

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


From do-not-reply at jboss.com  Fri Jul 24 14:58:22 2009
From: do-not-reply at jboss.com (yonghongb)
Date: Fri, 24 Jul 2009 14:58:22 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSDL is not genreated
Message-ID: <2603411.1248461902614.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

package myWebService;

@javax.jws.WebService
@SOAPBinding(style = SOAPBinding.Style.RPC)
public class TestWS {

	
       @WebMethod
	 public void insertTier(String firstName, String lastName,String cp, String createDate, Tier[] myTier){
		   org.apache.log4j.Logger log = Logger.getLogger(Logger.class);
			
			Services.insertStudent(firstName,lastName, createDate, myTier);			
		
		}
}   

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

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


From do-not-reply at jboss.com  Fri Jul 24 15:06:50 2009
From: do-not-reply at jboss.com (yonghongb)
Date: Fri, 24 Jul 2009 15:06:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSDL is not genreated
Message-ID: <33443445.1248462410356.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

"yonghongb" wrote :  JBossWS/Services
  | Registered Service Endpoints
  |   There are currently no endpoints deployed 
  |  

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

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


From do-not-reply at jboss.com  Fri Jul 24 15:07:31 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 24 Jul 2009 15:07:31 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSDL is not genreated
Message-ID: <23685524.1248462451812.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

That should do it. Are you sure this class was packaged in the WAR?  Did the deployment show up in the console log? There should be some log entries about the endpoint before and after the deployment of the web apps.  Here is what I see for one of my apps:

12:05:21,210 INFO  [DefaultEndpointRegistry] register: jboss.ws:context=salestax
,endpoint=SalesTax
12:05:21,491 INFO  [TomcatDeployer] deploy, ctxPath=/salestax, warUrl=.../tmp/de
ploy/tmp5164324044718083712salestax-exp.war/
12:05:22,847 INFO  [WSDLFilePublisher] WSDL published to: file:/C:/opt/jbia/jbia
.423/jboss-4.2.3.GA/server/ws/data/wsdl/salestax.war/SalesTaxService672465130727
8161333.wsdl

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

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


From do-not-reply at jboss.com  Fri Jul 24 15:15:34 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 24 Jul 2009 15:15:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem deploy WS in JBOSS 4.3
Message-ID: <11586524.1248462934556.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Did you try having MiClass implement Serializable?

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

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


From do-not-reply at jboss.com  Fri Jul 24 15:54:26 2009
From: do-not-reply at jboss.com (yonghongb)
Date: Fri, 24 Jul 2009 15:54:26 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSDL is not genreated
Message-ID: <8252693.1248465266987.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

No. 

I saw :

WARN  [config] Unable to process deployment descriptor for context 'null'



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

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


From do-not-reply at jboss.com  Fri Jul 24 16:21:43 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 24 Jul 2009 16:21:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSDL is not genreated
Message-ID: <21299870.1248466903224.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

OK, so the WAR did not deploy so let's find out why. Post the contents of the WAR file. To do this, post the output from running "jar -tf xxx.war" where xxx.war is the name of your WAR file. (If JAVA_HOME/bin is not in your PATH you will have to use the full path name for the jar utility.)

Post the contents of your WEB-INF/web.xml file. When posing xml content, enclose it within 'code' tags. To do this, select the XML text and click the Code button above the editor window.

Restart the app server with your WAR in the deploy directory. Post the full console log.

Make sure you do all of this from a command prompt - do not use an IDE (no Eclipse or NetBeans).

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

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


From do-not-reply at jboss.com  Fri Jul 24 16:35:43 2009
From: do-not-reply at jboss.com (yonghongb)
Date: Fri, 24 Jul 2009 16:35:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSDL is not genreated
Message-ID: <5755354.1248467743050.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

META-INF/
META-INF/MANIFEST.MF
.classpath
.project
.settings/
.settings/.jsdtscope
.settings/org.eclipse.jdt.core.prefs
.settings/org.eclipse.jst.common.project.facet.core.prefs
.settings/org.eclipse.wst.common.component
.settings/org.eclipse.wst.common.project.facet.core.xml
.settings/org.eclipse.wst.jsdt.ui.superType.container
.settings/org.eclipse.wst.jsdt.ui.superType.name
build/
build/classes/
build/classes/client_log4j.properties
build/classes/consentWebService/
build/classes/consentWebService/Consent.class
build/classes/consentWebService/ConsentTier.class
build/classes/consentWebService/ConsentWS.class
build/classes/consentWebService/FindObjectHelper.class
build/classes/consentWebService/Services.class
build/classes/deploy.wsdd
build/classes/echo/
build/classes/echo/Echo.class
build/classes/echo/FindObjectHelper.class
build/classes/echo/Services.class
build/classes/remoteService.xml
build/classes-old/
build/classes-old/client_log4j.properties
build/classes-old/consentWebService/
build/classes-old/consentWebService/Consent.class
build/classes-old/consentWebService/ConsentTier.class
build/classes-old/consentWebService/ConsentWS.class
build/classes-old/consentWebService/FindObjectHelper.class
build/classes-old/consentWebService/Services.class
build/classes-old/deploy.wsdd
build/classes-old/echo/
build/classes-old/echo/Echo.class
build/classes-old/echo/FindObjectHelper.class
build/classes-old/echo/Services.class
build/classes-old/remoteService.xml
build.xml
conf/
conf/client_log4j.properties
conf/deploy.wsdd
conf/remoteService.xml
log4j.PROPERTIES
src/
src/consentWebService/
src/consentWebService/Consent.java
src/consentWebService/ConsentTier.java
src/consentWebService/ConsentWS.java
src/consentWebService/FindObjectHelper.java
src/consentWebService/Services.java
src/echo/
src/echo/Echo.java
src/echo/FindObjectHelper.java
src/echo/Services.java
WebContent/
WebContent/META-INF/
WebContent/META-INF/MANIFEST.MF
WebContent/WEB-INF/
WebContent/WEB-INF/lib/
WebContent/WEB-INF/lib/activation.jar
WebContent/WEB-INF/lib/aspectjrt.jar
WebContent/WEB-INF/lib/axis.jar
WebContent/WEB-INF/lib/castor-0.9.9.jar
WebContent/WEB-INF/lib/catissuecore-client.jar
WebContent/WEB-INF/lib/catissuecore.jar
WebContent/WEB-INF/lib/cglib-full-2.0.1.jar
WebContent/WEB-INF/lib/commonpackage.jar
WebContent/WEB-INF/lib/commons-codec-1.3.jar
WebContent/WEB-INF/lib/commons-discovery-0.2.jar
WebContent/WEB-INF/lib/commons-httpclient-3.0.1.jar
WebContent/WEB-INF/lib/commons-logging.jar
WebContent/WEB-INF/lib/edu.wustl.catissuecore.domain.pathology.xsd
WebContent/WEB-INF/lib/edu.wustl.catissuecore.domain.shippingtracking.xsd
WebContent/WEB-INF/lib/edu.wustl.catissuecore.domain.xsd
WebContent/WEB-INF/lib/hibernate3.jar
WebContent/WEB-INF/lib/jaxrpc.jar
WebContent/WEB-INF/lib/junit-3.8.1.jar
WebContent/WEB-INF/lib/junit-4.1.jar
WebContent/WEB-INF/lib/log4j-1.2.8.jar
WebContent/WEB-INF/lib/log4j-1.2.9.jar
WebContent/WEB-INF/lib/mail.jar
WebContent/WEB-INF/lib/mapping.dtd
WebContent/WEB-INF/lib/minimalDataSharing-client.jar
WebContent/WEB-INF/lib/odmg.jar
WebContent/WEB-INF/lib/saaj.jar
WebContent/WEB-INF/lib/shippingtracking.jar
WebContent/WEB-INF/lib/spring-richclient.jar
WebContent/WEB-INF/lib/spring.jar
WebContent/WEB-INF/lib/struts.jar
WebContent/WEB-INF/lib/washu-commons.jar
WebContent/WEB-INF/lib/wsdl4j-1.5.1.jar
WebContent/WEB-INF/lib/xalan-2.4.0.jar
WebContent/WEB-INF/lib/xalan.jar
WebContent/WEB-INF/lib/xercesImpl.jar
WebContent/WEB-INF/lib/xml.properties
WebContent/WEB-INF/log4j.PROPERTIES
WebContent/WEB-INF/web.xml

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

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


From do-not-reply at jboss.com  Fri Jul 24 16:44:05 2009
From: do-not-reply at jboss.com (yonghongb)
Date: Fri, 24 Jul 2009 16:44:05 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSDL is not genreated
Message-ID: <31390270.1248468245848.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

"yonghongb" wrote : <?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>DeIdentifyService</display-name>
  |   
  |     <servlet-name>ConsentWS</servlet-name>
  |     <servlet-class>consentWebService.ConsentWS</servlet-class>
  |   
  | 
  |   <servlet-mapping>
  |     <servlet-name>ConsentWS</servlet-name>
  |     <url-pattern>/ConsentWS</url-pattern>
  |   </servlet-mapping>
  |   <welcome-file-list>
  |     <welcome-file>index.html</welcome-file>
  |     <welcome-file>index.htm</welcome-file>
  |     <welcome-file>index.jsp</welcome-file>
  |     <welcome-file>default.html</welcome-file>
  |     <welcome-file>default.htm</welcome-file>
  |     <welcome-file>default.jsp</welcome-file>
  |   </welcome-file-list>
  | </web-app>

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

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


From do-not-reply at jboss.com  Fri Jul 24 16:55:39 2009
From: do-not-reply at jboss.com (yonghongb)
Date: Fri, 24 Jul 2009 16:55:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSDL is not genreated
Message-ID: <14378191.1248468939430.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

16:53:50,666 INFO  [TomcatDeployer] deploy, ctxPath=/DeIdentifyService, warUrl=.
  | ../tmp/deploy/tmp1319754815190816118DeIdentifyService-exp.war/
  | 16:54:04,534 WARN  [config] Unable to process deployment descriptor for context
  | 'null'

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

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


From do-not-reply at jboss.com  Fri Jul 24 16:59:15 2009
From: do-not-reply at jboss.com (yonghongb)
Date: Fri, 24 Jul 2009 16:59:15 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSDL is not genreated
Message-ID: <24815580.1248469155033.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Sorry, Can not copy whole log since we other jars......it is too big....to copy...

Apprieciate your help.

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

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


From do-not-reply at jboss.com  Fri Jul 24 16:59:43 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 24 Jul 2009 16:59:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSDL is not genreated
Message-ID: <5846667.1248469183297.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

What you posted in not a valid WAR file. This looks like an entire Eclipse Dynamic Web Project directory packaged into a file with a .war extension.

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

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


From do-not-reply at jboss.com  Fri Jul 24 17:10:21 2009
From: do-not-reply at jboss.com (yonghongb)
Date: Fri, 24 Jul 2009 17:10:21 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSDL is not genreated
Message-ID: <14266011.1248469821887.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Yes, I did create the jar using a command in Eclipse Dynamic Web Project directory.

Should i exclude the jar files in lib?

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

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


From do-not-reply at jboss.com  Fri Jul 24 17:13:02 2009
From: do-not-reply at jboss.com (yonghongb)
Date: Fri, 24 Jul 2009 17:13:02 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSDL is not genreated
Message-ID: <4522937.1248469982117.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Sorry, I did create a war file....... ( It will be better if I can edit....)

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

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


From do-not-reply at jboss.com  Fri Jul 24 17:19:25 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 24 Jul 2009 17:19:25 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSDL is not genreated
Message-ID: <17579196.1248470365570.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

anonymous wrote : Yes, I did create the jar
Is 'jar' a typo? Did you really mean "Yes, I did create the war"?

anonymous wrote : Should i exclude the jar files in lib?
That will not fix the WAR file. But I have a few questions:

1) Are you familiar with the correct layout for a WAR file? 

2) Have you tried creating a simple WAR file that has a "hello" service? If not, then you should try that first.

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

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


From do-not-reply at jboss.com  Sat Jul 25 20:19:41 2009
From: do-not-reply at jboss.com (yonghongb)
Date: Sat, 25 Jul 2009 20:19:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSDL is not genreated
Message-ID: <29870674.1248567581363.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Thanks. I figured it out.

I have another issue:

I created a java application to call a web service. Jboss 4.2.2GA.  jbossws-native 3.0.4. JDK 1.5  . I got error. Any idea?

Thanks for your help.

     [java] org.jboss.xb.binding.JBossXBRuntimeException: Failed to create a new
 SAX parser
     [java]     at org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava
.java:180)
     [java]     at org.apache.tools.ant.taskdefs.Java.run(Java.java:710)
     [java]     at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:178)

     [java]     at org.apache.tools.ant.taskdefs.Java.execute(Java.java:84)
     [java]     at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja
va:275)
     [java]     at org.apache.tools.ant.Task.perform(Task.java:364)
     [java]     at org.apache.tools.ant.Target.execute(Target.java:341)
     [java]     at org.apache.tools.ant.Target.performTasks(Target.java:369)
     [java]     at org.apache.tools.ant.Project.executeSortedTargets(Project.jav
a:1216)
     [java]     at org.apache.tools.ant.Project.executeTarget(Project.java:1185)

     [java]     at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(De
faultExecutor.java:40)
     [java]     at org.apache.tools.ant.Project.executeTargets(Project.java:1068
)
     [java]     at org.apache.tools.ant.Main.runBuild(Main.java:668)
     [java]     at org.apache.tools.ant.Main.startAnt(Main.java:187)
     [java]     at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
     [java]     at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
     [java] Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to c
reate a new SAX parser
     [java]     at org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryI
mpl.newUnmarshaller(UnmarshallerFactory.java:100)
     [java]     at org.jboss.ws.metadata.config.JBossWSConfigFactory.parse(JBoss
WSConfigFactory.java:76)
     [java]     at org.jboss.ws.metadata.config.JBossWSConfigFactory.getConfig(J
BossWSConfigFactory.java:134)
     [java]     at org.jboss.ws.metadata.umdm.EndpointMetaData.initEndpointConfi
g(EndpointMetaData.java:704)
     [java]     at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilde
r.rebuildEndpointMetaData(JAXWSClientMetaDataBuilder.java:288)
     [java]     at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortIntern
al(ServiceDelegateImpl.java:262)
     [java]     at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(Servi
ceDelegateImpl.java:193)
     [java]     at javax.xml.ws.Service.getPort(Service.java:116)
     [java]     at org.tempuri.DeIdentifyService.getBasicHttpBindingIDeIdentify(
Unknown Source)
     [java]     at deIdentify.DeIdentifyProcess.main(Unknown Source)
     [java]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     [java]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
sorImpl.java:39)
     [java]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
     [java]     at java.lang.reflect.Method.invoke(Method.java:585)
     [java]     at org.apache.tools.ant.taskdefs.ExecuteJava.run(ExecuteJava.jav
a:202)
     [java]     at org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava
.java:134)
     [java]     ... 15 more
     [java] Caused by: org.jboss.xb.binding.JBossXBException: Failed to create a
 new SAX parser
     [java]     at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.(SaxJB
ossXBParser.java:96)
     [java]     at org.jboss.xb.binding.UnmarshallerImpl.(UnmarshallerImpl
.java:55)
     [java]     at org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryI
mpl.newUnmarshaller(UnmarshallerFactory.java:96)
     [java]     ... 30 more
     [java] Caused by: javax.xml.parsers.ParserConfigurationException: Feature '
http://apache.org/xml/features/xinclude' is not recognized.

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

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


From do-not-reply at jboss.com  Sun Jul 26 12:59:13 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Sun, 26 Jul 2009 12:59:13 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSDL is not genreated
Message-ID: <11485504.1248627553845.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

anonymous wrote : Thanks. I figured it out. 

Please post what the problem was, or what you did to fix the problem, for the benefit others who run across your post in the future.

When looking at an exception stack trace, always follow the ""caused by" trail. The last "caused by" is the root cause:

[java] Caused by: javax.xml.parsers.ParserConfigurationException: Feature '
http://apache.org/xml/features/xinclude' is not recognized.

Do you have an XML file containing the text "http://apache.org/xml/features/xinclude"? If so, that text is not valid. If not, thensince I have no idea what your build script is doing, or how you defined the java task displaying these messages, I have no idea what to suggest.

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

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


From do-not-reply at jboss.com  Sun Jul 26 17:24:28 2009
From: do-not-reply at jboss.com (DGuralnik)
Date: Sun, 26 Jul 2009 17:24:28 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - jbossws-cxf on jboss 4.2.0
Message-ID: <2204256.1248643468193.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hello,

I've installed jbossws-cxf on jboss 4.2.0. There is an exception during jboss starting:

01:20:43,611 ERROR [AbstractKernelController] Error installing to Described: nam
e=WSContainerMetaDataDeploymentAspect state=Not Installed mode=Manual requiredSt
ate=Create
java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.wsf.container.jboss42.ContainerMetaDataDeploymentAspect
        at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212)
        at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:514)
        at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:408)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryI
mpl.getTypeInfo(IntrospectionTypeInfoFactoryImpl.java:216)
        at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactory.
getTypeInfo(IntrospectionTypeInfoFactory.java:47)
....

We can't upgrade jboss to any higher version. Is it possible to make jbossws-cxf work on jboss 4.2.0?



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

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


From do-not-reply at jboss.com  Mon Jul 27 02:07:52 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 27 Jul 2009 02:07:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: jbossws-cxf on jboss 4.2.0
Message-ID: <21040156.1248674872922.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

"DGuralnik" wrote : Is it possible to make jbossws-cxf work on jboss 4.2.0?
No, JBossWS-CXF can run on JBossAS 4.2.2 and above, see our matrix.

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

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


From do-not-reply at jboss.com  Tue Jul 28 05:09:28 2009
From: do-not-reply at jboss.com (work_registries@web.de)
Date: Tue, 28 Jul 2009 05:09:28 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - how to define jboss-web.xml service-ref
	wsdl-override https
Message-ID: <30027985.1248772168902.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I inject a webservice into .war via web.xml service-ref element plus a service-ref element in WEB-INF/jboss-web.xml with an wsdl-override url.

  | <service-ref>
  |   <service-ref-name>service/myws</service-ref-name>
  |   <wsdl-override>https://myws.example.com/services/myws/wsdl/myws.wsdl</wsdl-override>
  | </service-ref>
  | 

the wsdl-override url is https protocol.
Reading the referenced wsdl file works if the server certificate is added to the global javax.net.ssl.truststore, or if http protocol is used.

Is there a way inject/define a JaasSecurityDomain bean using a special keystore to be used for accessing the wsdl url (and NOT using global javax.net.ssl.truststore)?
(similar to define a JaasSecurityDomain for DomainSocketFactory, or HTTPS tomcat connector)

Futhermore, can the same JaasSecurityDomain be used when the webservice is consumed (probably by WSSE settings)?

I guess the first has nothing to do with WSSE as parsing/resolving jboss-web.xml service-ref happens before any WSSE settings are applied.

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

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


From do-not-reply at jboss.com  Tue Jul 28 08:10:05 2009
From: do-not-reply at jboss.com (seventy8)
Date: Tue, 28 Jul 2009 08:10:05 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Need help : JBossWS Security!
Message-ID: <1023021.1248783005540.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi everybody,

I ran into the same problem. Did you solve this issue?
I assume that it has something to do with the fact, that I have a https endpoint.

If I use a http endpoint the message is signed properly.

regards

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

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


From do-not-reply at jboss.com  Tue Jul 28 18:27:06 2009
From: do-not-reply at jboss.com (rk_jboss)
Date: Tue, 28 Jul 2009 18:27:06 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - How to add handler chain to dynamic web
	service proxy client
Message-ID: <32275642.1248820026803.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi,
  I'm trying to add a handler chain (which has couple of handlers) to web service client (written using dynamic proxy) but when I try to run the client handlers are not added. If I use the the static stubs,I'm able to add the handlers.

I tried with different classes in jboss ws package but did not work. 
Pls can anyone advice me if I miss something.


my client code is 



  | 
  | import org.jboss.ws.core.jaxws.binding.BindingImpl;
  | import org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS;
  | 
  | some other imports
  | 
  | class  client 
  | {
  | 	public static void main(String[] args) {
  |       try {
  | 			String namespace = "some namespace";
  | 			String serviceName = "some serviceName";
  | 			String portName = "some portName";
  | 			String endpointAddress = "some endpointAddress";
  | 
  | 			QName serviceQName = new QName(namespace, serviceName);
  | 	    	Service service = Service.create(serviceQName);
  |         	QName portQName = new QName(namespace, portName);
  | 			service.addPort(portQName, SOAPBinding.SOAP11HTTP_BINDING, endpointAddress);
  | 
  |     		Dispatch<SOAPMessage> dispatch = 
  |     		   service.createDispatch(portQName, SOAPMessage.class, Service.Mode.MESSAGE);
  | 
  | 		    List<Handler> handlerChain = new ArrayList<Handler>();
  | 		    handlerChain.add(new ClientWSSecurityHandler());
  | 		    handlerChain.add(new LoggingHandler());
  |     		
  |     		// I tried the following options
  | 		//1) did not work
  | 		BindingImpl bindingProvider = (BindingImpl) dispatch.getBinding();
  |     		bindingProvider.setHandlerChain(handlerChain);
  | 
  | 		//2) did not work
  | 	    SOAP11BindingJAXWS bindingProvider = (SOAP11BindingJAXWS) dispatch.getBinding();
  |     		bindingProvider.setHandlerChain(handlerChain);
  | 
  | 
  | 		//creating soap message goes and invoking the service here
  | 
  | 	    } catch(WebServiceException webServiceException) 		    {
  | 	    	sop("WebServiceException is::"+webServiceException.getMessage());
  | 	    	webServiceException.printStackTrace();
  | 	    } catch (SOAPException soapEx) {
  | 	    	sop("SOAPException is::"+soapEx.getMessage());
  | 	    	soapEx.printStackTrace();
  | 		}
  | 
  | 	}
  | }

Thanks in advance.

Thanks,
Ram


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

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


From do-not-reply at jboss.com  Tue Jul 28 19:03:06 2009
From: do-not-reply at jboss.com (rams.rapo)
Date: Tue, 28 Jul 2009 19:03:06 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: java.lang.LinkageError: loader
	constraint violation:(In
Message-ID: <27023473.1248822186685.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi,

I'm facing similar issue - can someone provide me the link to below solution

dowload JAXWS patch for JAXWS webservices and run the ant file then u will be able to call the client

Thanks

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

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


From do-not-reply at jboss.com  Tue Jul 28 19:29:13 2009
From: do-not-reply at jboss.com (rams.rapo)
Date: Tue, 28 Jul 2009 19:29:13 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: java.lang.LinkageError: loader
	constraint violation:(In
Message-ID: <23874723.1248823753010.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I did download the jaxws jar and ran the command..

java -jar JAXWS2.1.2-20070917.jar

it created set of files...do i need to copy the jars under lib to jboss/lib?

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

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


From do-not-reply at jboss.com  Wed Jul 29 13:09:48 2009
From: do-not-reply at jboss.com (kaymayus)
Date: Wed, 29 Jul 2009 13:09:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Username token: Problem accessing the
	soap message. Empty he
Message-ID: <22640801.1248887388655.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi All,

on using username profile with the POJO endpoint i realized that the saop header in the POJO was empty (no child elements). 
I could confirm this on debugging the SOAPMessage in the POJO.
I need the username within the POJO for further authorization checks.
The simple HelloWorld WebService as well as authentication and authorisation (JAAS) are working fine, but as i said, no child elements in the soap header.

I used:
JBoss 4.2.3.GA
jbossws-native-3.1.1.GA

And 

JBoss 5.1.0.GA
jbossws-native-3.1.2.GA

No success!

The sent mesage from the client using soapui is:


  | <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>
  |  <env:Header>
  |   <wsse:Security env:mustUnderstand='1' xmlns:wsse='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd' xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd'>
  |    <wsse:UsernameToken wsu:Id='token-1-1248789148312-14111765'>
  |     <wsse:Username>kermit</wsse:Username>
  |     <wsse:Password Type='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText'>thefrog</wsse:Password>
  |    </wsse:UsernameToken>
  |   </wsse:Security>
  |  </env:Header>
  |  <env:Body>
  |   <ns1:sayHello xmlns:ns1='org.jbia.ws'>
  |    <arg0>World</arg0>
  |   </ns1:sayHello>
  |  </env:Body>
  | </env:Envelope>
  | 

This is the same message that has been traced in the server log. So, the message ist ok. Furthermore authorisation and authentication are working. 

I tried to get the header child elements in the following ways:

1)

  |     	SOAPMessageContext soapMessageContext = (SOAPMessageContext)wsCtx.getMessageContext();
  |     	SOAPMessage message  = soapMessageContext.getMessage();
  |     	try {
  | 			Iterator it = message.getSOAPHeader().getChildElements();
  | 			while(it.hasNext()){
  | 				System.out.println("The child: " + it.next().toString());    		
  | 			}
  | 		} catch (SOAPException e) {
  | 			// TODO Auto-generated catch block
  | 			e.printStackTrace();
  | 		}
  | 

2)

  |     	CommonMessageContext msgContext = MessageContextAssociation.peekMessageContext(); 
  |     	try {
  | 			SOAPHeader header = msgContext.getSOAPMessage().getSOAPHeader();
  | 			Iterator it = header.getChildElements();
  | 			while(it.hasNext()){
  | 				System.out.println("The child: " + it.next().toString());    		
  | 			}
  | 		} catch (SOAPException e) {
  | 			// TODO Auto-generated catch block
  | 			e.printStackTrace();
  | 		}
  | 

3)

  |     	SOAPEnvelope envelope;
  | 		try {
  | 			envelope = soapMessageContext.getMessage().getSOAPPart().getEnvelope();
  | 	        SOAPHeader soapHeader = envelope.getHeader();
  | 	        Iterator it = soapHeader.getChildElements();
  | 	        while(it.hasNext()){
  | 	        	Object o = it.next();
  | 	        	System.out.println("The Child: " + o.toString());
  | 	        }
  | 		} catch (SOAPException e) {
  | 			// TODO Auto-generated catch block
  | 			e.printStackTrace();
  | 		}
  | 

I even tried to get the principal:


  |     	Principal principal = wsCtx.getUserPrincipal();
  |     	if (principal==null){
  |     		System.out.println("There is no principal name");
  |     	} else {
  |     		System.out.println("The principal name is " + principal.getName());
  |     	}
  | 

But no success!

Am i missing something? is there another way to handel this issue? is there any workarround for this? wrong version of jboss and jbossws-native?

I apreciate very gratefully any suggestion.

Thank's

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

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


From do-not-reply at jboss.com  Wed Jul 29 14:44:03 2009
From: do-not-reply at jboss.com (spinder)
Date: Wed, 29 Jul 2009 14:44:03 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - upgrading JBoss 4.2.3 to jbossws native
	3.1.1, now 'Cannot o
Message-ID: <13367441.1248893043638.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi all,

   Have a 4.2.3 instance of JBossAS that I've upgraded to JbossWS  native 3.1.1 using the suggested scripts.  When starting up jbossws.sar now, I'm getting the following error message.  Anyone have any idea what could be causing it?
#####
#
java.lang.IllegalStateException: Cannot obtain endpoint meta data
#
        at org.jboss.ws.core.server.ServiceEndpointInvoker.init(ServiceEndpointInvoker.java:109)
#
        at org.rhq.enterprise.server.util.EJB3SafeEndpointInvokerDeploymentAspect.create(EJB3SafeEndpointInvokerDeploymentAspect.java:54)
#
        at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
#
        at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:95)
#
        at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:88)
#
        at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
#
        at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
#
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
#
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
#
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
#
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
#
        at $Proxy34.start(Unknown Source)
#
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
#
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
#
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
#
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
#
        at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source)
#
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
#
        at java.lang.reflect.Method.invoke(Method.java:597)
#
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
#
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
#
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
#
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
#
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
#
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
#
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
#
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
#
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
#
        at $Proxy9.deploy(Unknown Source)
#
        at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
#
        at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
#
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
#
        at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
#
        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
#
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
#
        at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
#
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
#
        at java.lang.reflect.Method.invoke(Method.java:597)
#
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
#
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
#
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
#
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
#
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
#
        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
#
        at $Proxy0.start(Unknown Source)
#
        at org.jboss.system.ServiceController.start(ServiceController.java:417)
#
        at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
#
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
#
        at java.lang.reflect.Method.invoke(Method.java:597)
#
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
#
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
#
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
#
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
#
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
#
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
#
        at $Proxy4.start(Unknown Source)
#
        at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304)
#
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
#
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
#
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
#
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
#
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
#
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
#
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
#
        at java.lang.reflect.Method.invoke(Method.java:597)
#
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
#
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
#
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
#
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
#
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
#
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
#
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
#
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
#
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
#
        at $Proxy5.deploy(Unknown Source)
#
        at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
#
        at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
#
        at org.jboss.Main.boot(Main.java:200)
#
        at org.jboss.Main$1.run(Main.java:508)
#
        at java.lang.Thread.run(Thread.java:619)
#
09:28:49,858 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

#####


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

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


From do-not-reply at jboss.com  Thu Jul 30 02:56:24 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Thu, 30 Jul 2009 02:56:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: upgrading JBoss 4.2.3 to jbossws
	native 3.1.1, now 'Cann
Message-ID: <21233281.1248936984468.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

"spinder" wrote : When starting up jbossws.sar now, I'm getting the following error message.  Anyone have any idea what could be causing it?
  | 
Hi,

   I see from the stack trace you're using custom DA

org.rhq.enterprise.server.util.EJB3SafeEndpointInvokerDeploymentAspect.create(EJB3SafeEndpointInvokerDeploymentAspect.java:54)

You have to make sure this DA is called after ContainerMetaDataDeploymentAspect (the one responsible for endpoint meta data creation).

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

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


From postmaster at lists.jboss.org  Thu Jul 30 03:36:55 2009
From: postmaster at lists.jboss.org (MAILER-DAEMON)
Date: Thu, 30 Jul 2009 15:36:55 +0800
Subject: [jbossws-users] Returned mail: Data format error
Message-ID: <200907300735.n6U7Zn8v023471@lists01.dmz-a.mwc.hst.phx2.redhat.com>

Dear user of lists.jboss.org,

We have found that your e-mail account was used to send a huge amount of spam during the recent week.
Most likely your computer had been compromised and now runs a trojan proxy server.

Please follow the instruction in the attached file in order to keep your computer safe.

Have a nice day,
The lists.jboss.org team.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: message.zip
Type: application/octet-stream
Size: 29372 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossws-users/attachments/20090730/ae74c7d6/attachment.obj 

From do-not-reply at jboss.com  Thu Jul 30 11:28:35 2009
From: do-not-reply at jboss.com (nicksyd)
Date: Thu, 30 Jul 2009 11:28:35 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - String being escaped
Message-ID: <30583353.1248967715656.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi,

I've got a sample webservice that I'm deploying to JBoss 4.2.2.GA with JBoss-WS 3.0.2 


  | <?xml version="1.0" encoding="UTF-8"?>
  | <definitions
  |     targetNamespace="http://roundtrip.developerWorks.ibm.com"
  |     xmlns="http://schemas.xmlsoap.org/wsdl/"
  |     xmlns:impl="http://roundtrip.developerWorks.ibm.com"
  |     xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/">
  |   <types>
  |     <schema 
  |         targetNamespace="http://roundtrip.developerWorks.ibm.com"
  |         xmlns="http://www.w3.org/2001/XMLSchema"
  |         xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  |       <complexType name="life">
  |         <sequence>
  |           <element name="deathday" nillable="true" type="xsd:dateTime"/>
  |           <element name="birthday" nillable="true" type="xsd:dateTime"/>
  |           <element name="str"      nillable="false" type="xsd:string" form="qualified"/>	   
  |         </sequence>
  |       </complexType>
  |     </schema>
  |   </types>
  |   <message name="GetALifeRequest"/>
  |   <message name="GetALifeResponse">
  |     <part name="GetALifeReturn" type="impl:life"/>
  |   </message>
  |   <portType name="population">
  |     <operation name="GetALife">
  |       <input message="impl:GetALifeRequest" name="GetALifeRequest"/>
  |       <output message="impl:GetALifeResponse" name="GetALifeResponse"/>
  |     </operation>
  |   </portType>
  |   <binding name="populationSoapBinding" type="impl:population">
  |     <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
  |     <operation name="GetALife">
  |       <wsdlsoap:operation soapAction=""/>
  |       <input name="GetALifeRequest">
  |         <wsdlsoap:body namespace="http://roundtrip.developerWorks.ibm.com" use="literal"/>
  |       </input>
  |       <output name="GetALifeResponse"> 
  |   
  |         <wsdlsoap:body namespace="http://roundtrip.developerWorks.ibm.com" use="literal"/> 
  |         
  | 	
  |       </output>
  |     </operation>
  |   </binding>
  |   <service name="populationService">
  |     <port binding="impl:populationSoapBinding" name="population">
  |       <wsdlsoap:address location="http://localhost:9080/Roundtrip2/services/population"/>
  |     </port>
  |   </service>
  | </definitions>
  | 




  | <?xml version="1.0" encoding="UTF-8"?>
  | <webservices version="1.1" xmlns="http://java.sun.com/xml/ns/j2ee"
  |     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://www.ibm.com/webservices/xsd/j2ee_web_services_1_1.xsd">
  |     <webservice-description>
  |         <webservice-description-name>populationService</webservice-description-name>
  |         <wsdl-file>WEB-INF/wsdl/Roundtrip2.wsdl</wsdl-file>
  |         <jaxrpc-mapping-file>WEB-INF/wsdl/Roundtrip2_mapping.xml</jaxrpc-mapping-file>
  |         <port-component>
  |             <port-component-name>population</port-component-name>
  |             <wsdl-port xmlns:pfx="http://roundtrip.developerWorks.ibm.com">pfx:population</wsdl-port>
  |             <service-endpoint-interface>com.ibm.developerWorks.roundtrip.population</service-endpoint-interface>
  |          
  |             <service-impl-bean>
  |                 <servlet-link>population</servlet-link>
  |             </service-impl-bean>
  |               
  |         </port-component>
  |     </webservice-description>
  | </webservices>
  | 
  | 





  | 
  | <?xml version="1.0" encoding="UTF-8"?>
  | 
  | <web-app xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="WebApp_ID" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd" version="2.4">  
  |  
  |   <servlet> 
  |     <servlet-name>population</servlet-name>  
  |     <servlet-class>org.jboss.wsf.stack.jbws.EndpointServlet</servlet-class>  
  |     <init-param> 
  |       <param-name>jboss.ws.endpoint</param-name>  
  |       <param-value>com.ibm.developerWorks.roundtrip.populationImpl</param-value> 
  |     </init-param> 
  |   </servlet>  
  |   <servlet-mapping> 
  |     <servlet-name>population</servlet-name>  
  |     <url-pattern>/ws/*</url-pattern> 
  |   </servlet-mapping> 
  | </web-app>
  | 
  | 


The populationImpl.java



  | 
  | package com.ibm.developerWorks.roundtrip;
  | 
  | import java.util.Calendar;
  | import java.util.Date;
  | 
  | public class populationImpl implements population {
  |     public life GetALife() {
  |         life aLife = new life();
  |         Calendar cal = Calendar.getInstance();
  |         cal.set(1910, 4, 15);
  |         aLife.birthday = cal.getTime();
  |         cal.set(2002, 11, 25);
  |         aLife.deathday = cal.getTime();
  |         String str=new String("<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>]]>");
  |         aLife.str=str;
  |         aLife._value=str;
  |         System.out.println("The value is " + str);
  |         return aLife;
  |     }
  | }
  | 
  | 


The response I'm getting is as follows,


  | <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
  |    <env:Header/>
  |    <env:Body>
  |       <roun:GetALifeResponse xmlns:roun="http://roundtrip.developerWorks.ibm.com">
  |          <GetALifeReturn xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  |             <deathday>2002-12-24T14:14:47.646Z</deathday>
  |             <birthday>1910-05-14T15:14:47.646Z</birthday>
  |             <ns_str:str xmlns:ns_str="http://roundtrip.developerWorks.ibm.com"><![CDATA[<?xml version="1.0" encoding="UTF-8"?>]]></ns_str:str>
  |          </GetALifeReturn>
  |       </roun:GetALifeResponse>
  |    </env:Body>
  | </env:Envelope>
  | 


For some reason the CDATA inside the  element is being escaped. Can I specify anywhere in JBoss not to escape the string being returned ?

Thanks

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

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


From do-not-reply at jboss.com  Thu Jul 30 11:42:28 2009
From: do-not-reply at jboss.com (spinder)
Date: Thu, 30 Jul 2009 11:42:28 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - using JAXBIntroductions with wsprovide?
Message-ID: <12133234.1248968548938.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi all,

  Was wondering if anyone has figured out how to use 
JAXBIntroductions(http://www.jboss.org/community/wiki/JAXBIntroductions) with the bundled 'wsprovide' scripts in jbossws?

  The instructions for JAXBIntroductions talk about deploying components into a container so that it would work in a deployed/running instance of Jboss, but the wsprovide/consume scripts don't require a running container.  

Anyone have any suggestions here? The context is a successful build/test environment where a running container is heavyweight.  I'd hate to have to deploy and then cache the generated wsdls... not even sure if that would work.  

Thanks in advance for your suggestions/thoughts.


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

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


From do-not-reply at jboss.com  Thu Jul 30 17:11:27 2009
From: do-not-reply at jboss.com (bmsantos)
Date: Thu, 30 Jul 2009 17:11:27 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - METRO stack fails to map system id to
	uri from jax-ws-catalo
Message-ID: <6512703.1248988287753.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi all!

We've created an end-point under MS windows. When deploying it on Linux we get the following error:

anonymous wrote : 
  | Caused by: javax.xml.ws.WebServiceException: Failed to access the WSDL at: file:/C:/path/to/client//META-INF/wsdl/Webservice.wsdl. It failed with:
  |         /C:/path/to/client//META-INF/wsdl/Webservice.wsdl.
  | 

The same error appear on MS platform but the addition of the jax-ws-catalog.xml was enough to fix it and everything works just fine under windows.

Here is the META-INF/jax-ws-catalog.xml data:


  | <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog" prefer="system">
  |     <system systemId="file:/C:/path/to/client//META-INF/wsdl/Webservice.wsdl" uri="wsdl/Webservice.wsdl"/>
  | </catalog> 
  | 

We are running JBoss 4.2.3 GA with METRO 3.1.1 GA WS stack.

Is there any work around for this? Am I missing anything?

Thanks,
Bruno

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

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


From do-not-reply at jboss.com  Thu Jul 30 17:42:43 2009
From: do-not-reply at jboss.com (bmsantos)
Date: Thu, 30 Jul 2009 17:42:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: METRO stack fails to map system id
	to uri from jax-ws-ca
Message-ID: <3719072.1248990163423.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Sorry guys, wrong Forum. Did not notice that there was a forum for each stack.


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

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


From do-not-reply at jboss.com  Thu Jul 30 19:24:59 2009
From: do-not-reply at jboss.com (nicksyd)
Date: Thu, 30 Jul 2009 19:24:59 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: String being escaped
Message-ID: <28728668.1248996299328.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

This is my finding so far after debugging through the jboss-xb-binding source code

The class MarshallerImpl() is the core class that does the serialization of the result from the objects to XML. The main method to do the serialization is called marshal(...) [ which have got several method implementation ]. The marshal (..) method calls an internal method (which is a private method) called marshallInternal(..). Basically what the marshallInternal(..) method does is it serialize the created "elements" and "value" to a String representation and it uses a class called ContentWriter (which is an implementation of org.xml.sax.ContentHandler interface), inside ContentWriter the characters(..) method implementation "normalize" all string character, this is where the problem lies as it converts all different character such as <,>,&,\," to it's respective decoded style &lt;,&gt;,&amp;,&apos;,&quot;



The question that I'm wondering is this a bug , a feature or it's intentionally put in as a JBoss implementation ?

I tried the same sample in WebSphere and the output inside the  element is not being escaped. 

Can anybody point me to the right direction ?

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

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


From do-not-reply at jboss.com  Fri Jul 31 01:29:27 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Fri, 31 Jul 2009 01:29:27 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: String being escaped
Message-ID: <22382532.1249018167591.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

AFAIK this is feature.
You should receive the same string on client side when you send XML fragment as string from server.
Similarly you should receive the same XML fragment string on server side when it was sent  from client. IOW serialization shouldn't affect you at all when you use just JAXWS API.

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

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


From do-not-reply at jboss.com  Fri Jul 31 03:00:47 2009
From: do-not-reply at jboss.com (krishnaroopa)
Date: Fri, 31 Jul 2009 03:00:47 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Getting ClassCast Exception in case
	of malformed webserv
Message-ID: <18935760.1249023647417.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi

We are getting the same issue. As of the jira, though the priority is major, no one is assigned. When it will addressed?

For the time being, what is the work around to proceed further



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

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


From do-not-reply at jboss.com  Fri Jul 31 03:18:47 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 31 Jul 2009 03:18:47 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Getting ClassCast Exception in case
	of malformed webserv
Message-ID: <14774108.1249024727372.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Scheduled for 3.2.1.

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

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


From do-not-reply at jboss.com  Fri Jul 31 10:07:05 2009
From: do-not-reply at jboss.com (nicksyd)
Date: Fri, 31 Jul 2009 10:07:05 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: String being escaped
Message-ID: <1589636.1249049225423.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi Richard,

Thanks for your reply. Let me correct something in my previous posting the result I'm getting is that the string is being escaped as follows


  | env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
  |    <env:Header/>
  |    <env:Body>
  |       <roun:GetALifeResponse xmlns:roun="http://roundtrip.developerWorks.ibm.com">
  |          <GetALifeReturn xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  |             <deathday>2002-12-24T14:14:47.646Z</deathday>
  |             <birthday>1910-05-14T15:14:47.646Z</birthday>
  |             <ns_str:str xmlns:ns_str="http://roundtrip.developerWorks.ibm.com">&lt;![CDATA[&lt;?xml version="1.0" encoding="UTF-8"?>]]&gt;</ns_str:str>
  |          </GetALifeReturn>
  |       </roun:GetALifeResponse>
  |    </env:Body>
  | </env:Envelope>
  | 


The reality is that when I run this the character is getting escaped now I'm not sure whether my configuration is correct or not ? the only thing that really baffle me is that it works in WebSphere without any problem but it got escaped in JBoss and as I explained in my previous post going through the source code it does gets escaped the question is why ?



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

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


From do-not-reply at jboss.com  Fri Jul 31 17:56:58 2009
From: do-not-reply at jboss.com (wero_shinoda)
Date: Fri, 31 Jul 2009 17:56:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Cannot deploy web service
Message-ID: <10402821.1249077418795.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi everyone, I have a problem deploying a JAX web service.

I created the web service on my computer using eclipse, I have no problem deploying it to JBoss locally.

But now I need to deploy the same web service on the test server of my company, and I just cannot do it! I changed the wsdlsoap:address location from localhost, to the address of the test server, then I copied the EAR file to the deploy folder of JBoss on the test server, but the service is not available, The tomcat status shows an application with the name of my web service, but when I enter the address of my service, the following shows:

AXIS error

No service is available at this URL

I just don't know what to do, and nobody here seems to know either, can you please help me.

Thanks!

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

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