From do-not-reply at jboss.com  Wed Oct  1 06:38:19 2008
From: do-not-reply at jboss.com (ajayks)
Date: Wed, 1 Oct 2008 06:38:19 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Not getting instance of Service
	object from a WSDL file.
Message-ID: <23426415.1222857499389.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thanks Peter for the taking time to reply.
1.What is strange in my JBOSS 4.2..2 installation  is that I have not finding   following jars in my $JBOSS_HOME/client/ path  :-
  jbossws-native-jaxws.jar
  jbossws-native-core.jar
  client/jbossws-native-jaxws-ext.jar
  client/jbossws-native-jaxrpc.jar
  jbossws-native-saaj.jar

 In fact these jars are not available in any path of my  JBOSS installation.
 Is the normal JBOSS 4.2.2 installation does not include all these jars .
 do I need to insatll JBOSS JAX-WS integartion layer in order to make    
 JBOSS JAXWS compliant.
2.I  made the client stub with wsconsume and I checked the all the names used in the  both stub and "stepts to call to make web service using  WSDL location".
The all the names used both  in  the stub and in the "stepts to call to make web service using  WSDL location" are same.
In Fact, I am  not able to call deployed web service  either with stub created by wsconsume or   by using WSDL location primitive.
Could please let me know what could be the  reason of my problem and what is its soution.
with best rehards,
Ajay Kumar,
ST Microelectronics Ltd.,
Noida, India.




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

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


From razvan at anaconda.cs.pub.ro  Wed Oct  1 07:16:21 2008
From: razvan at anaconda.cs.pub.ro (Razvan Deaconescu)
Date: Wed, 01 Oct 2008 14:16:21 +0300
Subject: [jbossws-users] Accesing an EJB from a WS server endpoint
Message-ID: <1222859781.4626.174.camel@valhalla.cs.pub.ro>

Hi!

I am trying (unsuccessfully) to acces an EJB from within a webservice
endpoint in JBoss 4.2.3GA

The EJB is deployed within an ear. The WS endpoint is deployed in a war
file. I am trying to access the WS endpoint using InitalContext's lookup
method:

--
Context initial = new InitialContext();
Object objref = initial.lookup("java:comp/env/ejb/SimpleDB");
---

However, this fails with "EJB not found exception". I probably didn't do
the correct mapping in the WS web.xml file:

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

  <servlet>
    <servlet-name>SecureStore</servlet-name>
    <servlet-class>SecureStore.SecureStoreServer</servlet-class>
  </servlet>


  <servlet-mapping>
          <servlet-name>SecureStore</servlet-name>
          <url-pattern>/SecureStoreServer</url-pattern>
  </servlet-mapping>

  <!-- reference on a remote bean without ejb-link-->
  <ejb-ref>
    <ejb-ref-name>ejb/Op</ejb-ref-name>
    <ejb-ref-type>Session</ejb-ref-type>
    <home>org.objectweb.earsample.beans.secusb.OpHome</home>
    <remote>org.objectweb.earsample.beans.secusb.Op</remote>

  </ejb-ref>

  <!-- reference on a remote bean using ejb-link-->
  <ejb-ref>
    <ejb-ref-name>ejb/EjbLinkOp</ejb-ref-name>
    <ejb-ref-type>Session</ejb-ref-type>

    <home>org.objectweb.earsample.beans.secusb.OpHome</home>
    <remote>org.objectweb.earsample.beans.secusb.Op</remote>
    <ejb-link>secusb.jar#Op</ejb-link>
  </ejb-ref>

  <!-- reference on a local bean -->
  <ejb-local-ref>
    <ejb-ref-name>ejb/OpLocal</ejb-ref-name>
    <ejb-ref-type>Session</ejb-ref-type>
    <local-home>org.objectweb.earsample.beans.secusb.OpLocalHome

    </local-home>
    <local>org.objectweb.earsample.beans.secusb.OpLocal</local>
    <ejb-link>secusb.jar#Op</ejb-link>
  </ejb-local-ref>

</web-app>
---

I have tried all the above reference methods but none of them worked.

Can anyone give me a hint about what I should do?

Regards,
Razvan



From do-not-reply at jboss.com  Wed Oct  1 07:19:18 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Wed, 1 Oct 2008 07:19:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Not getting instance of Service
	object from a WSDL file.
Message-ID: <16589075.1222859959003.JavaMail.jboss@colo-br-02.atl.jboss.com>

"ajayks" wrote : Thanks Peter for the taking time to reply.
  | 1.What is strange in my JBOSS 4.2..2 installation  is that I have not finding   following jars in my $JBOSS_HOME/client/ path  :-
  |   jbossws-native-jaxws.jar
  |   jbossws-native-core.jar
  |   client/jbossws-native-jaxws-ext.jar
  |   client/jbossws-native-jaxrpc.jar
  |   jbossws-native-saaj.jar
  | 
These jars were introduced since JBossWS 3.0.1 release. 

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

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


From do-not-reply at jboss.com  Wed Oct  1 09:23:22 2008
From: do-not-reply at jboss.com (jopersson)
Date: Wed, 1 Oct 2008 09:23:22 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JbossWS from ip address to host name
Message-ID: <23722975.1222867402858.JavaMail.jboss@colo-br-02.atl.jboss.com>


Hi,

Found the problem. We sit in a Windows environment where '_' is standard in machine names. Removed underscore and things work fine now.

/johan

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

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


From do-not-reply at jboss.com  Wed Oct  1 09:34:48 2008
From: do-not-reply at jboss.com (jimpo)
Date: Wed, 1 Oct 2008 09:34:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Does wsdl-override work in Jboss
	4.2.3GA?
Message-ID: <14091308.1222868088699.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am trying to use jboss.xml and wsdl-override to set the location where my webservices (annotated with @WebServiceRef into an EJB) are at. 

With JBoss 4.2.1GA this works, but identical ear in 4.2.3 seems to not use the wsdl-override at all.

Is there a known issue with JBoss 4.2.3GA and wsdl-override?

jboss.xml: 


  |         <session>
  |         	<ejb-name>ApplicationListingAction</ejb-name>
  |         	<service-ref>
  |         		<service-ref-name>com.fooz.baz.portlet.searchandapply.ApplicationListingAction/vacationRequestService</service-ref-name>
  |         		<wsdl-override>http://remoteserver:8080/service/vacation?wsdl</wsdl-override>
  |         	</service-ref>
  |         	<service-ref>
  |         		<service-ref-name>com.fooz.baz.portlet.searchandapply.ApplicationListingAction/employeeService</service-ref-name>
  |             	<wsdl-override>http://remoteserver:8080/employee-service/employee?wsdl</wsdl-override>
  |         	</service-ref>
  |         </session>
  |     </enterprise-beans>
  | </jboss>	

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

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


From do-not-reply at jboss.com  Wed Oct  1 10:37:53 2008
From: do-not-reply at jboss.com (sagimann)
Date: Wed, 1 Oct 2008 10:37:53 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Passing subclasses as parameters
Message-ID: <4449407.1222871873282.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,
I've encountered an issue while trying to declare web service methods which accept subclasses. The published WSDL does not contain the sub classes even if I specify them in @XmlSeeAlso. I've read some posts about this here, and it seems that it should be supported in JBossWS 2.0.2 and higher, but I tried 2.0.2 and 3.0.3 - still the same result.

My web service code:

  | import javax.jws.WebService;
  | import javax.jws.WebMethod;
  | import javax.jws.WebParam;
  | import javax.xml.bind.annotation.XmlSeeAlso;
  | 
  | @WebService
  | @XmlSeeAlso(SubBean.class)
  | public class Hello {
  |     @WebMethod public String testAbstractBeanArg(
  |             @WebParam AbstractBean bean) {
  |         return "abstract bean: " + bean.getClass().getName() + " " + bean.toString();
  |     }
  | }
  | 

Now, I look in the published WSDL, and I only see the abstractBean declaration - no subBean declaration. This does not happen with JAXWS RI 2.1 (Metro), which properly generates the "subBean" schema.

any ideas what should I do to see the subBean schema?
thanks.

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

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


From do-not-reply at jboss.com  Wed Oct  1 10:53:44 2008
From: do-not-reply at jboss.com (jorgemoralespou_2)
Date: Wed, 1 Oct 2008 10:53:44 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Are ports reusable/concurrent?
Message-ID: <17379845.1222872824119.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi, I'm developing an application with JBossWS, and using it as server and as client, invoking some other webservices in other servers.
Doing tunning of my app, I have found that too much time is spent every time I invoke getPort on a service, as it seems that everytime is generating the port on the fly.


2008-10-01 15:46:18,103:org.jboss.ws.core.jaxws.spi.ServiceDelegateImplCannot get port meta data for: {http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/service}SendSms|
2008-10-01 15:46:18,103:org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilderSTART: rebuildMetaData|
2008-10-01 15:46:18,103:org.jboss.ws.metadata.umdm.EndpointMetaDatasetParameterStyle: null|
2008-10-01 15:46:18,103:org.jboss.ws.metadata.umdm.EndpointMetaDataCreate new config [name=Standard Client,file=META-INF/standard-jaxws-client-config.xml]|
2008-10-01 15:46:18,103:org.jboss.ws.metadata.config.JBossWSConfigFactorygetConfig: [name=Standard Client,url=META-INF/standard-jaxws-client-config.xml]|
2008-10-01 15:46:18,103:org.jboss.ws.metadata.config.JBossWSConfigFactoryparse: file:/C:/jboss-4.2.3/core/server/som/deploy/jbossws.sar/META-INF/standard-jaxws-client-config.xml|
2008-10-01 15:46:18,181:org.jboss.ws.metadata.umdm.EndpointConfigMetaDataConfigure EndpointMetaData|
2008-10-01 15:46:18,181:org.jboss.ws.metadata.umdm.EndpointConfigMetaDataAdded 0 PRE handlers|
2008-10-01 15:46:18,181:org.jboss.ws.metadata.umdm.EndpointConfigMetaDataAdded 0 ENDPOINT handlers|
2008-10-01 15:46:18,181:org.jboss.ws.metadata.umdm.EndpointConfigMetaDataAdded 0 POST handlers|
2008-10-01 15:46:18,181:org.jboss.ws.metadata.umdm.EndpointMetaDatasetParameterStyle: WRAPPED|
2008-10-01 15:46:18,181:org.jboss.ws.metadata.umdm.EndpointMetaDataUsing default style: document|
2008-10-01 15:46:18,213:org.jboss.ws.metadata.umdm.EndpointMetaDatasetParameterStyle: WRAPPED|
2008-10-01 15:46:18,228:org.jboss.ws.metadata.umdm.EndpointMetaDatasetParameterStyle: WRAPPED|
2008-10-01 15:46:18,228:org.jboss.ws.metadata.umdm.EndpointMetaDatasetParameterStyle: WRAPPED|
2008-10-01 15:46:18,244:org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilderJAXBContext [types=[class com.hp.som.ws.parlayx21.sms.send.SendSms_Type, class com.hp.som.ws.parlayx21.sms.send.SendSmsResponse, class com.hp.som.ws.parlayx21.common.PolicyExceptionInfo, class com.hp.som.ws.parlayx21.common.ServiceExceptionInfo, class com.hp.som.ws.parlayx21.sms.send.SendSmsRingtone, class com.hp.som.ws.parlayx21.sms.send.SendSmsRingtoneResponse, class com.hp.som.ws.parlayx21.common.PolicyExceptionInfo, class com.hp.som.ws.parlayx21.common.ServiceExceptionInfo, class com.hp.som.ws.parlayx21.sms.send.SendSmsLogo, class com.hp.som.ws.parlayx21.sms.send.SendSmsLogoResponse, class com.hp.som.ws.parlayx21.common.PolicyExceptionInfo, class com.hp.som.ws.parlayx21.common.ServiceExceptionInfo, class com.hp.som.ws.parlayx21.sms.send.GetSmsDeliveryStatus, class com.hp.som.ws.parlayx21.sms.send.GetSmsDeliveryStatusResponse, class com.hp.som.ws.parlayx21.common.PolicyExceptionInfo, class com.hp.som.ws.parlayx21.common.ServiceExceptionInfo],tns=http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/interface]|
2008-10-01 15:46:18,478:org.jboss.ws.metadata.umdm.OperationMetaDataFound best matching java method: public abstract java.lang.String com.hp.som.ws.parlayx21.sms.send.SendSms.sendSms(java.util.List,java.lang.String,com.hp.som.ws.parlayx21.common.ChargingInformation,java.lang.String,com.hp.som.ws.parlayx21.common.SimpleReference) throws com.hp.som.ws.parlayx21.common.PolicyException,com.hp.som.ws.parlayx21.common.ServiceException|
2008-10-01 15:46:18,478:org.jboss.ws.metadata.umdm.OperationMetaDataFound best matching java method: public abstract java.lang.String com.hp.som.ws.parlayx21.sms.send.SendSms.sendSmsRingtone(java.util.List,java.lang.String,com.hp.som.ws.parlayx21.common.ChargingInformation,java.lang.String,com.hp.som.ws.parlayx21.sms.common.SmsFormat,com.hp.som.ws.parlayx21.common.SimpleReference) throws com.hp.som.ws.parlayx21.common.PolicyException,com.hp.som.ws.parlayx21.common.ServiceException|
2008-10-01 15:46:18,509:org.jboss.ws.metadata.umdm.OperationMetaDataFound best matching java method: public abstract java.lang.String com.hp.som.ws.parlayx21.sms.send.SendSms.sendSmsLogo(java.util.List,java.lang.String,com.hp.som.ws.parlayx21.common.ChargingInformation,byte[],com.hp.som.ws.parlayx21.sms.common.SmsFormat,com.hp.som.ws.parlayx21.common.SimpleReference) throws com.hp.som.ws.parlayx21.common.PolicyException,com.hp.som.ws.parlayx21.common.ServiceException|
2008-10-01 15:46:18,509:org.jboss.ws.metadata.umdm.OperationMetaDataFound best matching java method: public abstract java.util.List com.hp.som.ws.parlayx21.sms.send.SendSms.getSmsDeliveryStatus(java.lang.String) throws com.hp.som.ws.parlayx21.common.PolicyException,com.hp.som.ws.parlayx21.common.ServiceException|
2008-10-01 15:46:18,509:org.jboss.ws.metadata.umdm.EndpointMetaDataUsing default encoding style: literal|
2008-10-01 15:46:18,572:org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilderEND: rebuildMetaData

ServiceMetaData:
 qname={http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/service}SendSms
 refName=null
 wsdName=null
 wsdlFile=null
 wsdlLocation=null
 jaxrpcMapping=null
 publishLocation=null
 securityConfig=null
 properties=null

TypesMetaData: 
  [complexType={http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/interface}sendSms,javaType=com.hp.som.ws.parlayx21.sms.send.SendSms_Type]
  [complexType={http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/interface}sendSmsResponse,javaType=com.hp.som.ws.parlayx21.sms.send.SendSmsResponse]
  [complexType={http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/interface}PolicyException,javaType=com.hp.som.ws.parlayx21.common.PolicyExceptionInfo]
  [complexType={http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/interface}ServiceException,javaType=com.hp.som.ws.parlayx21.common.ServiceExceptionInfo]
  [complexType={http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/interface}sendSmsRingtone,javaType=com.hp.som.ws.parlayx21.sms.send.SendSmsRingtone]
  [complexType={http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/interface}sendSmsRingtoneResponse,javaType=com.hp.som.ws.parlayx21.sms.send.SendSmsRingtoneResponse]
  [complexType={http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/interface}sendSmsLogo,javaType=com.hp.som.ws.parlayx21.sms.send.SendSmsLogo]
  [complexType={http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/interface}sendSmsLogoResponse,javaType=com.hp.som.ws.parlayx21.sms.send.SendSmsLogoResponse]
  [complexType={http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/interface}getSmsDeliveryStatus,javaType=com.hp.som.ws.parlayx21.sms.send.GetSmsDeliveryStatus]
  [complexType={http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/interface}getSmsDeliveryStatusResponse,javaType=com.hp.som.ws.parlayx21.sms.send.GetSmsDeliveryStatusResponse]

|
2008-10-01 15:46:18,572:org.jboss.ws.metadata.umdm.EndpointMetaDataConfigure SOAPBinding|
2008-10-01 15:46:18,572:org.jboss.ws.core.jaxws.handler.HandlerResolverImplinitHandlerChain: PRE|
2008-10-01 15:46:18,572:org.jboss.ws.core.jaxws.handler.HandlerResolverImplinitHandlerChain: ENDPOINT|
2008-10-01 15:46:18,572:org.jboss.ws.core.jaxws.handler.HandlerResolverImplinitHandlerChain: POST|
2008-10-01 15:46:18,572:org.jboss.ws.core.jaxws.handler.HandlerResolverImplgetHandlerChain: [type=PRE,info=[service={http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/service}SendSms,port={http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/service}SendSms,binding=http://schemas.xmlsoap.org/wsdl/soap/http]]|
2008-10-01 15:46:18,572:org.jboss.ws.core.jaxws.handler.HandlerResolverImplgetHandlerChain: [type=POST,info=[service={http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/service}SendSms,port={http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/service}SendSms,binding=http://schemas.xmlsoap.org/wsdl/soap/http]]|
2008-10-01 15:46:18,572:org.jboss.ws.core.jaxws.handler.HandlerResolverImplgetHandlerChain: [type=ENDPOINT,info=[service={http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/service}SendSms,port={http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/service}SendSms,binding=http://schemas.xmlsoap.org/wsdl/soap/http]]|
2008-10-01 15:46:18,572:org.jboss.ws.core.jaxws.binding.BindingImplsetHandlerChain: []|
2008-10-01 15:46:18,572:org.jboss.ws.core.jaxws.spi.ServiceDelegateImplNo port configuration for: {http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/service}SendSms|



I don`t know if this is the correct usage pattern, or I should reuse the obtained Port.

I have browse the tests and examples, but I haven`t been able to get a conclusion.
Also, requests made to obtained port, must be done with different endpoint,timeout in some requests from other, so I don`t know If I should pool obtained port for every endpoint, and use pooled instances. Also, If I have 2 concurrent requests to send to same pooled port, is it going to have any problem, or it is thread safe?

Now I'm doing a static service, and using as this:

  | private String send(...params...){
  |    SendSmsService service = new SendSmsService(null, qname);
  |    SendSms stub = service.getSendSms();
  |    stub.getRequestContext().put(StubExt.PROPERTY_CLIENT_TIMEOUT,1000);
  | stub.getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY,  ...);
  | response = stub.sendSms(...params....);
  | return response;
  | }
  | ...
  | And, the getSendSms in the port is:
  | public class SendSmsService extends Service{
  |    ....
  |    public SendSms getSendSms() {
  |         return (SendSms)super.getPort(new QName("http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/service", "SendSms"), SendSms.class);
  |     }
  | }
  | 

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

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



From do-not-reply at jboss.com  Wed Oct  1 12:03:16 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Wed, 1 Oct 2008 12:03:16 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Not getting instance of Service
	object from a WSDL file.
Message-ID: <29123424.1222876996102.JavaMail.jboss@colo-br-02.atl.jboss.com>

Go back an read my previous reply, under item #1. You have to do your own searching for the correct set of JAR files. You will probably need to add about 12 JAR files to the classpath. If it were just one or two, I could tell you each time you get a CNFE which JAR you need to add, but doing this form a dozen JARs is too much work. One obvious shortcut is to include every JAR in the jboss_home/client directory in your client's classpath. (Though I vaguely recall that one or two if them are not there but in the server/xxx/lib directory. Anyway, if after adding all of the jboss_home/client jar files you still get a CNFE, post it and I will tell you which JAR it is in.)

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

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


From do-not-reply at jboss.com  Wed Oct  1 22:34:33 2008
From: do-not-reply at jboss.com (rishabh2u)
Date: Wed, 1 Oct 2008 22:34:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Cannot find port in wsdl (need help)
Message-ID: <17082291.1222914873463.JavaMail.jboss@colo-br-02.atl.jboss.com>

hi all,
this problem happens if u dont specify the name space in your WS implementation OR if u have specified the name space but its not the same as wsdl.

I ahve had this issue in JbossWS 423 which is jax-ws and fixed it by having the same name space in the WSDL and WS implementation.

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

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


From do-not-reply at jboss.com  Thu Oct  2 02:55:17 2008
From: do-not-reply at jboss.com (jopersson)
Date: Thu, 2 Oct 2008 02:55:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: jbossws remote ws
Message-ID: <25112130.1222930517943.JavaMail.jboss@colo-br-02.atl.jboss.com>

Had similar problem, found that our host name contains '_' cause the problem getting an output stream...

If you have underscore in hostname try to remove that (RFC 2396).

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

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


From do-not-reply at jboss.com  Thu Oct  2 03:54:23 2008
From: do-not-reply at jboss.com (bperchma)
Date: Thu, 2 Oct 2008 03:54:23 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: cxf does not work with JBOSS 4.2.3
	??
Message-ID: <15306942.1222934063138.JavaMail.jboss@colo-br-02.atl.jboss.com>

I got this to work by including the necessary cxf files in my ear file (
cxf-rt-frontend-jaxws*.jar), and then removing the following from jboss/lib/endorsed:

jboss-jaxws.jar,
joss-jaxws-ext.jar

For a convenient way to populate your ear file with the correct cxf jars, refer to http://cwiki.apache.org/CXF20DOC/maven-integration-and-plugin.html - but omit the dependency on the jetty transport.

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

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


From do-not-reply at jboss.com  Thu Oct  2 05:22:56 2008
From: do-not-reply at jboss.com (jopersson)
Date: Thu, 2 Oct 2008 05:22:56 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Are ports reusable/concurrent?
Message-ID: <13186741.1222939376338.JavaMail.jboss@colo-br-02.atl.jboss.com>

Bundled WSDL file in META-INF in client and loads it with classloader works fine and reduces network traffic.

URL wsdlURL = Resources.findFileAsURL(wsdlURLFileName);
String namespaceURI = Resources.getProperty("namespaceURI");
String localpart = Resources.getProperty("localpart");
service = new MyService(wsdlURL, new QName(namespaceURI, localpart));
port = service.getMyPort();  
((StubExt)port).setConfigName("Standard WSSecurity Client");

Port is reused (read somewhere port is not thread safe).

Otherwise proxy will use URL hardcoded from proxygenerator.

Works fine (for us). 
HTH.

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

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


From do-not-reply at jboss.com  Thu Oct  2 06:24:46 2008
From: do-not-reply at jboss.com (jorgemoralespou_2)
Date: Thu, 2 Oct 2008 06:24:46 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Are ports reusable/concurrent?
Message-ID: <21631034.1222943086251.JavaMail.jboss@colo-br-02.atl.jboss.com>

We have done this:


  |    // Static initialization of webservice client
  |    static protected SendSms stub;
  | 
  |    static{
  |       QName qname = new QName(
  |          "http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/service",
  |          "SendSms");
  |       SendSmsService service = new SendSmsService(null, qname);
  |       stub = service.getSendSms();
  |    }
  |    
  |    
  |    @Override
  |    protected String sendMessage(...params...) throws Exception {
  |       String response = null;
  | 
  |       if (stub==null){
  |          throw new Exception("There is no stub for SendSms PX 2.1 service created.");
  |       }
  | 
  |       //Configure stub 
  |       stub.getRequestContext().put(StubExt.PROPERTY_CLIENT_TIMEOUT,1000);
  |       stub.getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY,  ...);
  |       response = stub.sendSms(...params....);
  |       return response;
  |    }
  | 
  | 

But I doing tests to see if it is ThreadSafe to do this, or configuring an endpoint on the stub, will afect other clients sending messages to a previously configured stub in a previous (but concurrent) call.

In this cases I see that Stub generation only happens in the static initialization, and this way, performance is much more better.

Am I doing something wrong?

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

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


From do-not-reply at jboss.com  Thu Oct  2 07:09:06 2008
From: do-not-reply at jboss.com (jopersson)
Date: Thu, 2 Oct 2008 07:09:06 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Are ports reusable/concurrent?
Message-ID: <3460771.1222945746565.JavaMail.jboss@colo-br-02.atl.jboss.com>

(hope real experts can comment on this)

For being on the safe side you shold not use concurrent calls on the port from your client app.. Instead collect your client calls and run them in sequence to the server endpoint...my personal opinion.

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

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


From do-not-reply at jboss.com  Thu Oct  2 09:34:59 2008
From: do-not-reply at jboss.com (jorgemoralespou_2)
Date: Thu, 2 Oct 2008 09:34:59 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Are ports reusable/concurrent?
Message-ID: <8045051.1222954499533.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have thought on initially creating a pool of ports, to eache endpoint I must use, and use these instances from pool, this way preventing concurrency, but I'm not sure if this is efficient, or even, really needed. I wanted to know prior to develop, because it`s a lot of work, since I have lots of clients, and different endpoints.
Since my class is going to be invoked acting like a proxiing web service, I can't not guarantee there are not going to be concurrent invocations.

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

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


From razvan at anaconda.cs.pub.ro  Thu Oct  2 12:49:08 2008
From: razvan at anaconda.cs.pub.ro (Razvan Deaconescu)
Date: Thu, 02 Oct 2008 19:49:08 +0300
Subject: [jbossws-users] Accesing an EJB from a WS server endpoint
In-Reply-To: <1222859781.4626.174.camel@valhalla.cs.pub.ro>
References: <1222859781.4626.174.camel@valhalla.cs.pub.ro>
Message-ID: <1222966148.4626.323.camel@valhalla.cs.pub.ro>

On Wed, 2008-10-01 at 14:16 +0300, Razvan Deaconescu wrote:
> Hi!
> 
> I am trying (unsuccessfully) to acces an EJB from within a webservice
> endpoint in JBoss 4.2.3GA
> 
> The EJB is deployed within an ear. The WS endpoint is deployed in a war
> file. I am trying to access the WS endpoint using InitalContext's lookup
> method:
<snip>

Problem solved. I had forgotten to include jboss-web.xml in the war
file.

Razvan



From do-not-reply at jboss.com  Fri Oct  3 01:16:09 2008
From: do-not-reply at jboss.com (ajayks)
Date: Fri, 3 Oct 2008 01:16:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Not getting instance of Service
	object from a WSDL file.
Message-ID: <31448534.1223010969292.JavaMail.jboss@colo-br-02.atl.jboss.com>

Dear Peter,
I have  included all the  jars from  $JBOSS_HOME/client/lib directory  in the classpath of  client program of web service since begining and it is still not working.
Do  I need to  provide integration layer of  web service to the srever in  order to run the web service on  jboss 4.2.2 server.

with best regards,
Ajay

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

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


From do-not-reply at jboss.com  Fri Oct  3 01:41:52 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Fri, 3 Oct 2008 01:41:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Are ports reusable/concurrent?
Message-ID: <11321791.1223012512412.JavaMail.jboss@colo-br-02.atl.jboss.com>

Take a look what our FAQ says.
There's also JBWS-2324.

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

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


From do-not-reply at jboss.com  Fri Oct  3 02:36:32 2008
From: do-not-reply at jboss.com (navin_bhat)
Date: Fri, 3 Oct 2008 02:36:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Username token is not interoperable
	with gSOAP client
Message-ID: <23887404.1223015792390.JavaMail.jboss@colo-br-02.atl.jboss.com>

Environment:JBOSS AS 4.2.3,JBoss-native-3.0.3,JDK 5 update 15,Windows XP SP2,Eclipse 3.3.x. 

Description :
I generated service code from wsdl using wsconsume (contract first approach). I wrote the service skeleton code as a stateless EJB.I enabled WS-Security features as described in the user guide using the following two annotations.

//Enable the login module to verify the user name and password
@SecurityDomain("JBossWSDigest")
//Enable the WS_Security modules
@EndpointConfig(configName ="Standard WSSecurity Endpoint")

I deployed the service in JBoss Application server 4.2.3. The client is written in gSOAP framework (Running on linux) generated from the same wsdl file.WS-Security is enabled in the gSOAP client.When the gSOAP client sends a request, the JBoss service throws an exception, the stack trace is shown below.Let me know if more details are required to debug the issue.

NOTE: The same JBoss service works fine with JBoss client with the same setup as gSOAP client.

Stacktrace:
11:54:42,538 INFO  [ReceiveUsernameOperation] Username: PDC
11:54:42,538 INFO  [ReceiveUsernameOperation] Password: welcome
11:54:43,226 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
javax.ejb.EJBAccessException: Authentication failure
	at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.handleGeneralSecurityException(Ejb3AuthenticationInterceptor.java:68)
	at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:70)
	at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
	at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
	at org.jboss.wsf.container.jboss42.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:103)
	at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:219)
	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:476)
	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295)
	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205)
	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
	at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:81)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
	at java.lang.Thread.run(Thread.java:595)

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

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


From do-not-reply at jboss.com  Fri Oct  3 03:42:39 2008
From: do-not-reply at jboss.com (jopersson)
Date: Fri, 3 Oct 2008 03:42:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Username token is not interoperable
	with gSOAP client
Message-ID: <12812591.1223019759644.JavaMail.jboss@colo-br-02.atl.jboss.com>

If possible run Wireshark Network Analyzer with "capture filter" host 
and compare the two client messages sent to server...but this "debugger" does not work 
if you are running locally, then maybe tcpmon.


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

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


From do-not-reply at jboss.com  Fri Oct  3 04:34:03 2008
From: do-not-reply at jboss.com (jorgemoralespou_2)
Date: Fri, 3 Oct 2008 04:34:03 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Are ports reusable/concurrent?
Message-ID: <2984724.1223022843864.JavaMail.jboss@colo-br-02.atl.jboss.com>

I've seen the FAQ and the Jira request, and now my question is, how are users using JBossWS as a client for, for example, acting as a proxy?
I hope there is a large users community that can share experience with us.

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

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


From do-not-reply at jboss.com  Fri Oct  3 05:01:36 2008
From: do-not-reply at jboss.com (maffeis)
Date: Fri, 3 Oct 2008 05:01:36 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Jar file for
	org.jboss.ws.core.soap.SAAJMetaFactoryImpl.
Message-ID: <9658114.1223024496082.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi Thorsten

I had the same issue after installing jbossws-metro-3.0.3 into jboss-4.2.3.GA. I then copied jbossws-client.jar from the client directory of the original jboss-4.2.3.GA distribution, and placed it into the server/default/lib directory (after applying jbossws-metro-3.0.3). Then the 
SAAJMetaFactoryImpl ClassNotFoundException went away.

It seems that the metro installation will remove jbossws-client.jar.

But I actually haven't done much testing yet and I don't have a good feeling about all of this.

Silvano


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

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


From do-not-reply at jboss.com  Fri Oct  3 05:12:48 2008
From: do-not-reply at jboss.com (maffeis)
Date: Fri, 3 Oct 2008 05:12:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Jar file for
	org.jboss.ws.core.soap.SAAJMetaFactoryImpl.
Message-ID: <3323265.1223025169006.JavaMail.jboss@colo-br-02.atl.jboss.com>

I filed a JIRA ticket:
https://jira.jboss.org/jira/browse/JBWS-2335

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

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


From do-not-reply at jboss.com  Fri Oct  3 09:10:20 2008
From: do-not-reply at jboss.com (Marlboro)
Date: Fri, 3 Oct 2008 09:10:20 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS 3.0.3 with heavy load
Message-ID: <5825080.1223039420867.JavaMail.jboss@colo-br-02.atl.jboss.com>

For anybody who will have same troubles.
I fixed it by using wsdl file from local storage not from network.

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

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


From do-not-reply at jboss.com  Fri Oct  3 09:42:18 2008
From: do-not-reply at jboss.com (miketech)
Date: Fri, 3 Oct 2008 09:42:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Eclipse JEE and JAX WS 2
Message-ID: <19376269.1223041338854.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I want to write a webservice and deploy it to JBoss. There are several ways to do this. I can write a webservice as PoJo and with two clicks in Eclipse JEE the service is created and deployed.

But I wanna use JAX WS with the annotations WebService  and WebMethods. I've created the according java class. And now? When I choose the "create webservice" again the configuration for jboss is created without JAX WS. 

Any ideas?

Greetings

Mike

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

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


From do-not-reply at jboss.com  Fri Oct  3 12:19:11 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 3 Oct 2008 12:19:11 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Not getting instance of Service
	object from a WSDL file.
Message-ID: <30159743.1223050751162.JavaMail.jboss@colo-br-02.atl.jboss.com>

I hope this was a typo: $JBOSS_HOME/client/lib, and that you really meant $JBOSS_HOME/client.

As I mentioned before PeterJ wrote : (Though I vaguely recall that one or two of [the necessary JAR files] are not there but in the server/xxx/lib directory. Anyway, if after adding all of the jboss_home/client jar files you still get a CNFE, post [the CNFE stack trace] and I will tell you which JAR [the missing class] is in.)

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

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


From do-not-reply at jboss.com  Fri Oct  3 12:31:13 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 3 Oct 2008 12:31:13 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Not getting instance of Service
	object from a WSDL file.
Message-ID: <3666636.1223051473567.JavaMail.jboss@colo-br-02.atl.jboss.com>

I decided to deploy my simple hello EJB-based web service on 4.2.2. I used the wsrunclient to run my client and the only JAR files I had to add to the classpath were:

1 - the JAR file containing my client code and the subs generated by wsconsume
2 - jboss_home/client/jbossall-client.jar

Then the client ran without errors.

(Perhaps my recollection regarding using JAR files from server/xxx/lib is somewhat mistaken. After all, I did that well over a year ago.)

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

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


From do-not-reply at jboss.com  Fri Oct  3 14:14:55 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 3 Oct 2008 14:14:55 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Eclipse JEE and JAX WS 2
Message-ID: <12203018.1223057695401.JavaMail.jboss@colo-br-02.atl.jboss.com>

What do you mean by " the configuration for jboss is created without JAX WS."? How can you tell? What was it that you expected but was missing?

I have create JAX-WS POJO web services and there is little difference between the resulting WAR and that of a web application.

Finally, this could be an Eclipse packaging issue, in which case you should ask this in an Eclipse forum (or on the JBoss Tools forum if you are using JBoss Tools).

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

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


From do-not-reply at jboss.com  Mon Oct  6 11:02:13 2008
From: do-not-reply at jboss.com (bortx)
Date: Mon, 6 Oct 2008 11:02:13 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Open file descriptors to wsdl
Message-ID: <17139065.1223305333748.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi Richard,

Thanks for your fix, but I've been debuging the code and noticed that our problem was in other place.

On MessageContextJAXWS class, on its setOperationMetaData() method, an InputSource that references the wsdl file is stored inside the context. This input stream is never closed, so a file descriptor remains open on each request.

I've tried closing it on the finally section of the invoke() method on ServiceEndpointInvoker class and it works successfully without leaving open file descriptors.

I think you would like to know in order to fix this issue.

Thank you very much!

Bortx

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

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


From do-not-reply at jboss.com  Tue Oct  7 01:03:43 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Tue, 7 Oct 2008 01:03:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Open file descriptors to wsdl
Message-ID: <8945315.1223355823629.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi Bortx,

   thank you very much for this really useful input and your time to debug our code.
I fixed the MessageContextJAXWS problem. Thanks for pointing this problem out!

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

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


From do-not-reply at jboss.com  Tue Oct  7 06:16:36 2008
From: do-not-reply at jboss.com (agohar)
Date: Tue, 7 Oct 2008 06:16:36 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Hosting JBossWS and JBoss.NET
	webservices
Message-ID: <25314822.1223374596550.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

We are upgrading our application to Jboss-4.2.2 and we have a JBoss.NET web service in the application, which we can't upgrade to JbossWS because of client not in a position to change their code. 

Was just wondering is it possible to use Jboss.NET on jboss-4.2.2 and also, we will be adding a new webservice to the application as well. Is it possible to create that in JbossWS and deploy and run both JBoss.NET and JBossWS in parallel?

Any comments will be highly appreciated.

Thanks

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

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


From do-not-reply at jboss.com  Tue Oct  7 09:51:23 2008
From: do-not-reply at jboss.com (nias)
Date: Tue, 7 Oct 2008 09:51:23 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Share JSESSIONID between multiple
	services
Message-ID: <1793947.1223387483376.JavaMail.jboss@colo-br-02.atl.jboss.com>

i'm trying to share a session between more then one webservice endpoint for statefull webservices (via seam to use conversations).

i've tried to get each port via:


  | URL wsdlLocation = new URL("...");
  | QName serviceName = new QName(..., ...); 
  | Service service = Service.create(wsdlLocation, serviceName);
  | port1 res = (port1)service.getPort(port1.class);
  | BindingProvider bp = (BindingProvider)res;
  | bp.getRequestContext().put(BindingProvider.USERNAME_PROPERTY, "admin");
  | bp.getRequestContext().put(BindingProvider.PASSWORD_PROPERTY, "admin");
  | bp.getRequestContext().put(StubExt.PROPERTY_AUTH_TYPE, StubExt.PROPERTY_AUTH_TYPE_WSSE);
  | URL securityURL = new File("src/test/webservices/META-INF/jboss-wsse-client.xml").toURL();
  | ((StubExt)bp).setSecurityConfig(securityURL.toExternalForm());
  | ((StubExt)bp).setConfigName("Standard WSSecurity Client"); 	
  | bp.getRequestContext().put(BindingProvider.SESSION_MAINTAIN_PROPERTY, true);
  | 
all calls from one port are working fine inside the session but now i wan't to take the JSESSIONID from port1 after first call and use them for port2 with the following code:


  | final Map responseMap = ((BindingProvider)port1).getResponseContext();
  | final Map headerValues = (Map)responseMap.get(MessageContext.HTTP_RESPONSE_HEADERS);
  | final List<String> cookieHeaders = (List<String>) headerValues.get("Set-Cookie");
  | for(String x : cookieHeaders) {
  | if(xl[0].equals("JSESSIONID")) {
  |     Map<String, List<String>> headers = (Map<String, List<String>>) ((BindingProvider)port2).getRequestContext().get(MessageContext.HTTP_REQUEST_HEADERS);
  |     if (headers == null) {
  |         headers = new HashMap<String, List<String>>();
  | ((BindingProvider)port2).getRequestContext().put(MessageContext.HTTP_REQUEST_HEADERS, headers);
  |     } else { System.out.println("headers exists"); }
  | 
  |     List<String> cookie = headers.get("Cookie");
  |     if (cookie == null) {
  |         cookie = new ArrayList<String>();
  |         headers.put("Cookie", cookie);
  |     } else { System.out.println("cookies exists"); }
  |     cookie.add("JSESSIONID="+xl[1]);
  | 

The cookie would be extracted but ignored on first call for port2, therefore a new session starts on port2.
how can i solve this?



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

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


From do-not-reply at jboss.com  Tue Oct  7 14:13:08 2008
From: do-not-reply at jboss.com (bkenison)
Date: Tue, 7 Oct 2008 14:13:08 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Ant tests FAILED
Message-ID: <28285675.1223403188273.JavaMail.jboss@colo-br-02.atl.jboss.com>

I just installed jbossws-native-3.0.3.GA.  I'm using jboss 4.2.3.  I ran the "ant tests" and passed most of them, however, I'm failing on XOPBareTestCase and XOPHandlerTestCase


Here is the output from those tests:

[junit] Running org.jboss.test.ws.jaxws.samples.xop.doclit.XOPBareTestCase
[junit] Tests run: 7, Failures: 1, Errors: 0, Time elapsed: 8.48 sec
[junit] Corrupt JPEG DATA: 1 extraneous bytes before marker 0xc4
[junit] Corrupt JPEG DATA: 1 extraneous bytes before marker 0xc4
[junit] Test.org.jboss.test.ws.jaxws.samples.xop.doclit.XOPBareTestCase FAILED
[junit] Running org.jboss.test.ws.jaxws.samples.xop.doclit.XOPHandlerTestCase
[junit] Tests run: 7, Failures: 1, Errors: 0, Time elapsed: 8.516 sec
[junit] Corrupt JPEG DATA: 1 extraneous bytes before marker 0xc4
[junit] Corrupt JPEG DATA: 1 extraneous bytes before marker 0xc4
[junit] Test.org.jboss.test.ws.jaxws.samples.xop.doclit.XOPHandlerTestCase FAILED


In the output files, the following information was recorded:

Testsuite: org.jboss.test.ws.jaxws.samples.xop.doclit.XOPBareTestCase
Tests run: 7, Failures: 1, Errors: 0, Time elapsed: 8.485 sec

Testcase: testDataHandlerRoundtrip took 2.75 sec
Testcase: testDataHandlerResponseOptimzed took 0.453 sec
Testcase: testImgRoundtrip took 1.734 sec
Testcase: testImgResponseOptimized took 1.079 sec
Testcase: testSourceRoundtrip took 0.39 sec
Testcase: testSourceResponseOptimized took 0.547 sec
Testcase: testAttachmentpartSwap took 0.375 sec
	FAILED
Attachment part swap file does still exist: JBossWSattachment32227.dat
junit.framework.AssertionFailedError: Attachment part swap file does still exist: JBossWSattachment32227.dat
	at org.jboss.test.ws.jaxws.samples.xop.doclit.XOPBase.testAttachmentpartSwap(XOPBase.java:155)
	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
	at junit.extensions.TestSetup.run(TestSetup.java:23)

There was the same error for XOPHandlerTestCase.


We are planning to use XOP with these web services, so I am concerned about the test failure.  Can anyone give me more information on what I might do to pass these tests?



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

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


From do-not-reply at jboss.com  Wed Oct  8 00:12:50 2008
From: do-not-reply at jboss.com (pilocao)
Date: Wed, 8 Oct 2008 00:12:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - which tool to use to deploy standalone
	services as a webserv
Message-ID: <25180705.1223439170089.JavaMail.jboss@colo-br-02.atl.jboss.com>

In the past, people use:

java org.apache.soap.server.ServiceManagerClient
http://localhost:8080/soap/servlet/rpcrouter 

such kind of AXIS tool/way to generate WSDL base on config.xml

Now, the JBoss 4 boundled AXIS, Which tool can we use to deploy a standalone java? 

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

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


From do-not-reply at jboss.com  Wed Oct  8 02:13:58 2008
From: do-not-reply at jboss.com (alllle)
Date: Wed, 8 Oct 2008 02:13:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS client uses password from WSDL,
	ignoring client side
Message-ID: <15346479.1223446438648.JavaMail.jboss@colo-br-02.atl.jboss.com>

Just want to bump this, can someone from JBoss confirm if this is a bug? I can create a JIRA ticket for this so it can be fixed.

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

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


From do-not-reply at jboss.com  Wed Oct  8 03:05:10 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Wed, 8 Oct 2008 03:05:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Ant tests FAILED
Message-ID: <893281.1223449510886.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

   yes, we know about this windows only problem. The reason of failure is there are some tests that don't close the file streams and our attachments handler is unable to delete such files on windows platform in it's destroy() method. The solution is always ensure you're closing the data handler input streams in your web services.

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

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


From do-not-reply at jboss.com  Wed Oct  8 03:07:59 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 8 Oct 2008 03:07:59 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS client uses password from WSDL,
	ignoring client side
Message-ID: <27728263.1223449679116.JavaMail.jboss@colo-br-02.atl.jboss.com>

The policy for ws-security you're using was created to have an example of ws-policy working with something already implemented in the stack and has some issues, most probably one of them being what you describe. As a matter of fact, that policy does not conform to the ws-security policy specification.
This said, of course you can create a jira issue for this, perhaps this could be fixed before actually providing a compliant implementation of ws-security policy.

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

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


From do-not-reply at jboss.com  Wed Oct  8 12:32:31 2008
From: do-not-reply at jboss.com (pandatao)
Date: Wed, 8 Oct 2008 12:32:31 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Use "context listener" in Web Service
	as "ServletContextList
Message-ID: <32990161.1223483551256.JavaMail.jboss@colo-br-02.atl.jboss.com>

Dear forum,

Currently I am working on a J2EE/JBoss web service project. I'd like to use a simillar "context listener" in a web service project, just as the "ServletContextListener " has done in a web GUI application (WAR). The package structure of a web service project is different from a web application project. E.g. there is neither "web.xml" file nor "WEB-INF" folder in a web serivce project package.

I am new in JBoss web service, any help and response will be very appreciated!

Thanks in advance,

Tao

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

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


From do-not-reply at jboss.com  Wed Oct  8 13:44:13 2008
From: do-not-reply at jboss.com (ajay662)
Date: Wed, 8 Oct 2008 13:44:13 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - consume WS over https no longer works
	when upgraded to jboss
Message-ID: <28055035.1223487853509.JavaMail.jboss@colo-br-02.atl.jboss.com>

My web-service client application is running fine in jboss 4.0.5. I am accessing service over "https"  and am using my own KeyManager and TrustManager for SSL.

However when I upgraded to jboss 4.2.3, the client application stopped working and I get following exception

2008-10-08 13:24:35,057 INFO  [STDOUT] WorkManager(2)-8
  | 2008-10-08 13:24:35,057 INFO  [STDOUT] , SEND TLSv1 ALERT:  
  | 2008-10-08 13:24:35,057 INFO  [STDOUT] fatal, 
  | 2008-10-08 13:24:35,057 INFO  [STDOUT] description = certificate_unknown
  | 2008-10-08 13:24:35,057 INFO  [STDOUT] WorkManager(2)-8, WRITE: TLSv1 Alert, length = 2
  | 2008-10-08 13:24:35,057 INFO  [STDOUT] WorkManager(2)-8, called closeSocket()
  | 2008-10-08 13:24:35,057 INFO  [STDOUT] WorkManager(2)-8, handling exception: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found
  | 2008-10-08 13:24:35,057 DEBUG [org.jboss.remoting.transport.http.HTTPClientInvoker] Unable to retrieve response message
  | javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found
  | 	at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:150)
  | 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1518)
  | 	at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:174)
  | 	at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:168)
  | 	at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:848)
  | 	at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:106)
  | 	at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:495)
  | 	at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:433)
  | 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:818)
  | 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1030)
  | 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1057)
  | 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1041)
  | 	at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:402)
  | 	at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:170)
  | 	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:861)
  | 	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:920)
  | 	at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:367)
  | 	at java.net.HttpURLConnection.getResponseMessage(HttpURLConnection.java:433)
  | 	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseMessage(HttpsURLConnectionImpl.java:362)
  | 	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:340)
  | 	at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:137)
  | 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
  | 	at org.jboss.remoting.Client.invoke(Client.java:1634)
  | 	at org.jboss.remoting.Client.invoke(Client.java:548)
  | 	at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:233)
  | 	at org.jboss.ws.core.client.SOAPProtocolConnectionHTTP.invoke(SOAPProtocolConnectionHTTP.java:73)
  | 	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:339)
  | 	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
  | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
  | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
  | 	at $Proxy161.getBuildInfo(Unknown Source)
  | 	at com.covergence.enms.status.PollClusterMDB.pollCluster(PollClusterMDB.java:86)
  | 	at com.covergence.enms.status.PollClusterMDB.onMessage(PollClusterMDB.java:140)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:585)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
  | 	at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
  | 	at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.tx.BMTInterceptor.handleStateless(BMTInterceptor.java:71)
  | 	at org.jboss.ejb3.tx.BMTInterceptor.invoke(BMTInterceptor.java:131)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.security.RunAsSecurityInterceptor.invoke(RunAsSecurityInterceptor.java:83)
  | 	at org.jboss.ejb3.security.RunAsSecurityInterceptor.invoke(RunAsSecurityInterceptor.java:54)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
  | 	at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
  | 	at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
  | 	at $Proxy105.onMessage(Unknown Source)
  | 	at org.jboss.resource.adapter.jms.inflow.JmsServerSession.onMessage(JmsServerSession.java:178)
  | 	at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:906)
  | 	at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:170)
  | 	at org.jboss.mq.SpySession.run(SpySession.java:323)
  | 	at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:237)
  | 	at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
  | 	at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
  | 	at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756)
  | 	at java.lang.Thread.run(Thread.java:595)
  | Caused by: sun.security.validator.ValidatorException: No trusted certificate found
  | 	at sun.security.validator.SimpleValidator.buildTrustedChain(SimpleValidator.java:304)
  | 	at sun.security.validator.SimpleValidator.engineValidate(SimpleValidator.java:107)
  | 	at sun.security.validator.Validator.validate(Validator.java:203)
  | 	at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:172)
  | 	at com.sun.net.ssl.internal.ssl.JsseX509TrustManager.checkServerTrusted(SSLContextImpl.java:320)
  | 	at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:841)
  | 	... 61 more

I am using JDK 1.5.0_15. Has anything changed in jboss 4.2.3 (vs jboss 4.0.5) to explain above exception. Why is my TrustManager class not being called above to verify server certificate? Any help would be much appreciated.

Thanks.

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

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


From do-not-reply at jboss.com  Wed Oct  8 13:53:17 2008
From: do-not-reply at jboss.com (ajay662)
Date: Wed, 8 Oct 2008 13:53:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: consume WS over https no longer
	works when upgraded to j
Message-ID: <10904593.1223488397845.JavaMail.jboss@colo-br-02.atl.jboss.com>

Actually my TrustManager class do gets called. However the SSL handshake process seems to be quite length(and I don't understand much of the details) and eventually fails with above exception.

For WS stack, I am using whatever comes default with jboss 4.2.3. Am using "default" server configuration. My web-service client code runs from an MDB. If anybody is interested I can send the long "SSL,handshake" debug log. I really need help here. Have tried various things over last couple of days but without luck.

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

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


From do-not-reply at jboss.com  Thu Oct  9 02:16:07 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Thu, 9 Oct 2008 02:16:07 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: consume WS over https no longer
	works when upgraded to j
Message-ID: <30712650.1223532967305.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi Ajay,

   ensure your certificate didn't expire.

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

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


From do-not-reply at jboss.com  Thu Oct  9 02:40:40 2008
From: do-not-reply at jboss.com (haru01)
Date: Thu, 9 Oct 2008 02:40:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - ant tests fail  (jbossws-cxf)
Message-ID: <23453692.1223534440163.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi

I waint to use  jbossws-cxf-3.0.3.GA. 
installed jbossws-cxf-3.0.3.GA  with docs/Install.txt
jdk1.5 => Test is ok. 


But Jdk1.6 => Test is fail. 

Why?


-- test NG env -----
 * jdk1.6.0_07
 * jboss-4.2.3.GA-jdk6
 * jbossws-cxf-3.0.3.GA
----------------------

-- Error Stack trace  example --

Unable to load Provider: Failed to load javax.xml.ws.spi.Provider: org.jboss.ws.core.jaxws.spi.ProviderImpl
javax.xml.ws.WebServiceException: Unable to load Provider: Failed to load javax.xml.ws.spi.Provider: org.jboss.ws.core.jaxws.spi.ProviderImpl
	at javax.xml.ws.spi.Provider.provider(Provider.java:90)
	at javax.xml.ws.Service.(Service.java:81)
	at javax.xml.ws.Service.create(Service.java:98)
	at org.jboss.test.ws.jaxws.samples.soapbinding.SOAPBindingTestCase.testExampleService(SOAPBindingTestCase.java:64)
	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
	at junit.extensions.TestSetup.run(TestSetup.java:23)
Caused by: java.lang.IllegalStateException: Failed to load javax.xml.ws.spi.Provider: org.jboss.ws.core.jaxws.spi.ProviderImpl
	at javax.xml.ws.spi.ProviderLoader.loadProvider(ProviderLoader.java:96)
	at javax.xml.ws.spi.Provider.provider(Provider.java:82)
Caused by: java.lang.ClassNotFoundException: org.jboss.ws.core.jaxws.spi.ProviderImpl
	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 javax.xml.ws.spi.ProviderLoader.loadProvider(ProviderLoader.java:90)
----------------------


-- OK env --
 * jdk1.5.0_15
 * jboss-4.2.3.GA
 * jbossws-cxf-3.0.3.GA
----------------------

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

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


From do-not-reply at jboss.com  Thu Oct  9 02:42:16 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Thu, 9 Oct 2008 02:42:16 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: ant tests fail  (jbossws-cxf)
Message-ID: <7474252.1223534536760.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

   we don't support CXF integration on JDK6 at the moment :( You can fire a JIRA request for that.

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

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


From do-not-reply at jboss.com  Thu Oct  9 03:36:56 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Thu, 9 Oct 2008 03:36:56 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Use
Message-ID: <645067.1223537816623.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi pandatao,

   you have to specify the following context param in your webservice web.xml:

<context-param>
  |   <param-name>org.jboss.ws.webapp.ServletContextListener</param-name>
  |   <param-value>mycompany.ServletContextListenerImpl</param-value>
  | </context-param>

It is supported on each AS 4.2.x and above.

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

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


From do-not-reply at jboss.com  Thu Oct  9 04:31:29 2008
From: do-not-reply at jboss.com (agohar)
Date: Thu, 9 Oct 2008 04:31:29 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Hosting JBossWS and JBoss.NET
	webservices
Message-ID: <5863129.1223541089255.JavaMail.jboss@colo-br-02.atl.jboss.com>

Any one please?

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

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


From do-not-reply at jboss.com  Thu Oct  9 08:24:07 2008
From: do-not-reply at jboss.com (pandatao)
Date: Thu, 9 Oct 2008 08:24:07 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Use
Message-ID: <1892303.1223555047560.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi Richard,
Thank you for your reply!
I have two more questions:

1. In my current project package there is no "web.xml". Where should I put a new web.xml? The following is the structure of my ear file. I have tried to put the "WEB-INF/web.xml" on the same level of the two "META-INF" folders, but it does not work.

 
  | App.ear
  |     - META-INF/
  |         -application.xml
  |     - AppClient.jar
  |     - App.jar
  |          - META-INF/
  |             - wsdl/
  |                - App.wsdl
  |             - webservice.xml
  |             - mapping.xml
  |             - jboss.xml
  |             - ejb-jar.xml
  |          - classes/
  |          - saaj-impl.jar
  |          - jaxrpc-spi.jar
  |          - jaxrpc-impl.jar
  | 
   

2. Currently I am using the JBoss version 4.0.2 (with Patch 10). Due to several reasons I can't upgrade the JBoss server to version 4.2.x. Do you think the "context-param" will work in the verson 4.0.2? I tried the "ServletContextListener" in a WAR application in 4.0.2 und it works.
    



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

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


From do-not-reply at jboss.com  Thu Oct  9 09:42:11 2008
From: do-not-reply at jboss.com (ajay662)
Date: Thu, 9 Oct 2008 09:42:11 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: consume WS over https no longer
	works when upgraded to j
Message-ID: <17058909.1223559731440.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi Richard,

Thanks for your reply. The certificate is valid .... till 2015. Here is the complete relevant server.log. I apologize ... its kind of long.


  | 2008-10-09 09:26:46,176 DEBUG [org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder] END: rebuildMetaData
  | 
  | ServiceMetaData:
  |  qname={http://www.covergence.com/ws/enms}EnmsService
  |  refName=null
  |  wsdName=null
  |  wsdlFile=null
  |  wsdlLocation=https://172.30.3.165:8443/enms?wsdl
  |  jaxrpcMapping=null
  |  publishLocation=null
  |  securityConfig=null
  |  properties=null
  | 
  | TypesMetaData: 
  |  [types deleted to save space....]
  |   
  | 
  | 
  | ClientEndpointMetaData:
  |  type=JAXWS
  |  qname={http://www.covergence.com/ws/enms}EnmsPort
  |  address=https://172.30.3.165:8443/enms
  |  binding=http://schemas.xmlsoap.org/wsdl/soap/http
  |  seiName=com.covergence.enms.ws.enms.EnmsPortType
  |  configFile=META-INF/standard-jaxws-client-config.xml
  |  configName=Standard Client
  |  authMethod=null
  |  properties={}
  | 
  | OperationMetaData:
  | [ deleted to save space ...]
  |  
  | 2008-10-09 09:26:46,348 DEBUG [org.jboss.ws.metadata.umdm.EndpointMetaData] Configure SOAPBinding
  | 2008-10-09 09:26:46,348 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] initHandlerChain: PRE
  | 2008-10-09 09:26:46,348 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] initHandlerChain: ENDPOINT
  | 2008-10-09 09:26:46,348 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] initHandlerChain: POST
  | 2008-10-09 09:26:46,348 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] getHandlerChain: [type=PRE,info=[service={http://www.covergence.com/ws/enms}EnmsService,port={http://www.covergence.com/ws/enms}EnmsPort,binding=http://schemas.xmlsoap.org/wsdl/soap/http]]
  | 2008-10-09 09:26:46,348 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] getHandlerChain: [type=POST,info=[service={http://www.covergence.com/ws/enms}EnmsService,port={http://www.covergence.com/ws/enms}EnmsPort,binding=http://schemas.xmlsoap.org/wsdl/soap/http]]
  | 2008-10-09 09:26:46,348 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] getHandlerChain: [type=ENDPOINT,info=[service={http://www.covergence.com/ws/enms}EnmsService,port={http://www.covergence.com/ws/enms}EnmsPort,binding=http://schemas.xmlsoap.org/wsdl/soap/http]]
  | 2008-10-09 09:26:46,348 DEBUG [org.jboss.ws.core.jaxws.binding.BindingImpl] setHandlerChain: []
  | 2008-10-09 09:26:46,363 DEBUG [org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl] No port configuration for: {http://www.covergence.com/ws/enms}EnmsPort
  | 2008-10-09 09:26:46,379 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] pushMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at cc0376 (Thread WorkManager(2)-8)
  | 2008-10-09 09:26:46,379 DEBUG [org.jboss.ws.core.EndpointInvocation] setRequestParamValue: [name={http://www.covergence.com/ws/enms}BuildInfoRequest,value=null]
  | 2008-10-09 09:26:46,379 DEBUG [org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS] bindRequestMessage: {http://www.covergence.com/ws/enms}GetBuildInfo
  | 2008-10-09 09:26:46,426 DEBUG [org.jboss.ws.core.EndpointInvocation] getRequestParamValue: {http://www.covergence.com/ws/enms}BuildInfoRequest
  | 2008-10-09 09:26:46,426 DEBUG [org.jboss.ws.core.EndpointInvocation] transformPayloadValue: null -> null
  | 2008-10-09 09:26:46,441 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler executor: []
  | 2008-10-09 09:26:46,441 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler executor: []
  | 2008-10-09 09:26:46,441 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler executor: []
  | 2008-10-09 09:26:46,504 DEBUG [org.jboss.ws.core.client.HTTPRemotingConnection] Get locator for: [addr=https://172.30.3.165:8443/enms,props={javax.xml.ws.service.endpoint.address=https://172.30.3.165:8443/enms}]
  | 2008-10-09 09:26:46,551 INFO  [STDOUT] ***
  | 2008-10-09 09:26:46,551 INFO  [STDOUT] found key for : enms
  | 2008-10-09 09:26:46,551 INFO  [STDOUT] chain [0] = [
  | [
  |   Version: V1
  |   Subject: CN=Ajay Aggarwal, OU=Engineering, O=Covergence Inc, L=Maynard, ST=MA, C=US
  |   Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
  | 
  |   Key:  Sun RSA public key, 1024 bits
  |   modulus: 135336373136823284036573815484343342565008025374091814025204081683765445376230127674060547973736495472759099093817474775862932201444169160885284203104742050967946148405471545575409318866162796027331160691774263742127257067118949215056575262792961372351224424297146533971169358204696870250445354754030489634449
  |   public exponent: 65537
  |   Validity: [From: Wed Mar 05 14:53:54 EST 2008,
  |                To: Thu Mar 05 14:53:54 EST 2009]
  |   Issuer: CN=Ajay Aggarwal, OU=Engineering, O=Covergence Inc, L=Maynard, ST=MA, C=US
  |   SerialNumber: [    47cefa52]
  | 
  | ]
  |   Algorithm: [MD5withRSA]
  |   Signature:
  | 0000: B4 F4 95 BC 4E 67 A9 3E   A2 65 C4 14 23 A8 2D EA  ....Ng.>.e..#.-.
  | 0010: FE 68 14 DE 90 21 2A D9   8E 8A C3 73 29 AD 65 D5  .h...!*....s).e.
  | 0020: 67 CE ED C5 C7 C8 A5 27   7B 4A E6 7C 10 A9 7F 6F  g......'.J.....o
  | 0030: AB 4B 67 15 72 8F 1E 67   8F F4 AD 99 21 82 9F 00  .Kg.r..g....!...
  | 0040: F6 24 1A 2F 28 12 63 89   8C CA 8E 0C 2C AE 0E 86  .$./(.c.....,...
  | 0050: D6 34 BA 01 14 0A 96 4A   59 09 FF AA 6A 0E 5E E3  .4.....JY...j.^.
  | 0060: 7A 37 FD 40 06 A9 BC 2B   32 D8 DC F6 06 EB D5 1A  z7. at ...+2.......
  | 0070: 35 ED EC 69 D4 3A 13 34   45 4C D2 EB 99 36 0A 02  5..i.:.4EL...6..
  | 
  | ]
  | 2008-10-09 09:26:46,551 INFO  [STDOUT] ***
  | 2008-10-09 09:26:46,551 INFO  [STDOUT] adding as trusted cert:
  | 2008-10-09 09:26:46,551 INFO  [STDOUT]   Subject: CN=Ajay Aggarwal, OU=Engineering, O=Covergence Inc, L=Maynard, ST=MA, C=US
  | 2008-10-09 09:26:46,551 INFO  [STDOUT]   Issuer:  CN=Ajay Aggarwal, OU=Engineering, O=Covergence Inc, L=Maynard, ST=MA, C=US
  | 2008-10-09 09:26:46,551 INFO  [STDOUT]   Algorithm: RSA; Serial number: 0x47cefa52
  | 2008-10-09 09:26:46,551 INFO  [STDOUT]   Valid from Wed Mar 05 14:53:54 EST 2008 until Thu Mar 05 14:53:54 EST 2009
  | 2008-10-09 09:26:46,551 INFO  [STDOUT] trigger seeding of SecureRandom
  | 2008-10-09 09:26:46,551 INFO  [STDOUT] done seeding SecureRandom
  | 2008-10-09 09:26:46,551 DEBUG [org.jboss.remoting.MicroRemoteClientInvoker] org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker at ee90e9 connecting
  | 2008-10-09 09:26:46,551 DEBUG [org.jboss.remoting.MicroRemoteClientInvoker] org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker at ee90e9 connected
  | 2008-10-09 09:26:46,551 DEBUG [org.jboss.ws.core.client.HTTPRemotingConnection] Remoting metadata: {HEADER={SOAPAction="GetBuildInfo", Content-Type=text/xml; charset=UTF-8}, NoThrowOnError=true}
  | 2008-10-09 09:26:46,566 DEBUG [org.jboss.remoting.transport.http.HTTPClientInvoker] Setting request header with SOAPAction : "GetBuildInfo"
  | 2008-10-09 09:26:46,566 DEBUG [org.jboss.remoting.transport.http.HTTPClientInvoker] Setting request header with Content-Type : text/xml; charset=UTF-8
  | 2008-10-09 09:26:46,566 INFO  [STDOUT] %% No cached client session
  | 2008-10-09 09:26:46,566 INFO  [STDOUT] *** ClientHello, TLSv1
  | 2008-10-09 09:26:46,566 INFO  [STDOUT] RandomCookie:  
  | 2008-10-09 09:26:46,566 INFO  [STDOUT] GMT: 1206781334 
  | 2008-10-09 09:26:46,566 INFO  [STDOUT] bytes = { 
  | ... deleted ...
  | 2008-10-09 09:26:46,582 INFO  [STDOUT]  }
  | 2008-10-09 09:26:46,582 INFO  [STDOUT] Session ID:  
  | 2008-10-09 09:26:46,582 INFO  [STDOUT] {}
  | 2008-10-09 09:26:46,582 INFO  [STDOUT] Cipher Suites: [SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5, SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA]
  | 2008-10-09 09:26:46,582 INFO  [STDOUT] Compression Methods:  { 
  | 2008-10-09 09:26:46,582 INFO  [STDOUT] 0
  | 2008-10-09 09:26:46,582 INFO  [STDOUT]  }
  | 2008-10-09 09:26:46,582 INFO  [STDOUT] ***
  | 2008-10-09 09:26:46,582 INFO  [STDOUT] WorkManager(2)-8, WRITE: TLSv1 Handshake, length = 73
  | 2008-10-09 09:26:46,582 INFO  [STDOUT] WorkManager(2)-8, WRITE: SSLv2 client hello message, length = 98
  | 2008-10-09 09:26:46,582 INFO  [STDOUT] WorkManager(2)-8, READ: TLSv1 Handshake, length = 7766
  | 2008-10-09 09:26:46,582 INFO  [STDOUT] *** ServerHello, TLSv1
  | 2008-10-09 09:26:46,582 INFO  [STDOUT] RandomCookie:  
  | 2008-10-09 09:26:46,582 INFO  [STDOUT] GMT: 1206781333 
  | 2008-10-09 09:26:46,582 INFO  [STDOUT] bytes = { 
  | ...deleted ...
  | 2008-10-09 09:26:46,582 INFO  [STDOUT]  }
  | 2008-10-09 09:26:46,582 INFO  [STDOUT] Session ID:  
  | 2008-10-09 09:26:46,582 INFO  [STDOUT] {72, 238, 6, 149, 142, 184, 211, 58, 13, 163, 106, 88, 112, 192, 65, 139, 15, 77, 129, 169, 103, 187, 219, 24, 15, 173, 167, 164, 211, 84, 212, 184}
  | 2008-10-09 09:26:46,582 INFO  [STDOUT] Cipher Suite: SSL_RSA_WITH_RC4_128_MD5
  | 2008-10-09 09:26:46,582 INFO  [STDOUT] Compression Method: 0
  | 2008-10-09 09:26:46,582 INFO  [STDOUT] ***
  | 2008-10-09 09:26:46,582 INFO  [STDOUT] %% Created:  [Session-2, SSL_RSA_WITH_RC4_128_MD5]
  | 2008-10-09 09:26:46,582 INFO  [STDOUT] ** SSL_RSA_WITH_RC4_128_MD5
  | 2008-10-09 09:26:46,582 INFO  [STDOUT] *** Certificate chain
  | 2008-10-09 09:26:46,582 INFO  [STDOUT] chain [0] = [
  | [
  |   Version: V1
  |   Subject: CN=Covergence Inc, OU=covergence.com, O=covergence.com, L=Maynard, ST=MA, C=US
  |   Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
  | 
  |   Key:  Sun RSA public key, 1023 bits
  |   modulus: 81725270146334745875970522895234154947216516690920959125303823170348978811784807265895380886647633641629189766376106765112961237368821433143575600447558640161067575359884112030290494797031619076309724764611453890031396674059958758716180895503505104133773512431900120777464449650731492266954869988956381237691
  |   public exponent: 65537
  |   Validity: [From: Thu May 26 09:25:53 EDT 2005,
  |                To: Sun May 24 09:25:53 EDT 2015]
  |   Issuer: CN=Covergence Inc, OU=covergence.com, O=covergence.com, L=Maynard, ST=MA, C=US
  |   SerialNumber: [    4295ce61]
  | 
  | ]
  |   Algorithm: [MD5withRSA]
  |   Signature:
  | 0000: 33 5F 91 1E 19 E9 48 72   90 57 D0 11 62 A0 AD 63  3_....Hr.W..b..c
  | 0010: 39 4F 70 3E 01 A8 DC 7B   BC BC A3 85 22 C8 DE EB  9Op>........"...
  | 0020: E9 97 FD B1 9A 85 96 28   C6 38 03 67 45 ED 8E B4  .......(.8.gE...
  | 0030: D1 73 9B D8 B9 52 13 EF   1E 4A 3B C8 60 BD 4B 88  .s...R...J;.`.K.
  | 0040: 64 E2 A2 3E 33 F8 27 EB   13 DB 18 C7 F4 FC 80 80  d..>3.'.........
  | 0050: 75 39 E0 73 0A 97 59 A4   35 CE 38 F5 AD B4 C6 1B  u9.s..Y.5.8.....
  | 0060: 6A 47 E4 14 CB 4E A5 0D   F0 7A 90 26 5F 31 67 D5  jG...N...z.&_1g.
  | 0070: E2 2F 56 27 7F 54 77 46   84 DE C4 46 C1 85 B3 CD  ./V'.TwF...F....
  | 
  | ]
  | 2008-10-09 09:26:46,582 INFO  [STDOUT] ***
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] WorkManager(2)-8
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] , SEND TLSv1 ALERT:  
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] fatal, 
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] description = certificate_unknown
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] WorkManager(2)-8, WRITE: TLSv1 Alert, length = 2
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] WorkManager(2)-8, called closeSocket()
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] WorkManager(2)-8, handling exception: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] %% No cached client session
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] *** ClientHello, TLSv1
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] RandomCookie:  
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] GMT: 1206781334 
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] bytes = { 
  | ... deleted ...
  | 2008-10-09 09:26:46,598 INFO  [STDOUT]  }
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] Session ID:  
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] {}
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] Cipher Suites: [SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5, SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA]
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] Compression Methods:  { 
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] 0
  | 2008-10-09 09:26:46,598 INFO  [STDOUT]  }
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] ***
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] WorkManager(2)-8, WRITE: TLSv1 Handshake, length = 73
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] WorkManager(2)-8, WRITE: SSLv2 client hello message, length = 98
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] WorkManager(2)-8, READ: TLSv1 Handshake, length = 7766
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] *** ServerHello, TLSv1
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] RandomCookie:  
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] GMT: 1206781333 
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] bytes = { 
  | ... deleted
  | 2008-10-09 09:26:46,598 INFO  [STDOUT]  }
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] Session ID:  
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] {72, 238, 6, 149, 95, 90, 205, 55, 203, 44, 218, 25, 234, 101, 46, 18, 24, 174, 14, 29, 132, 6, 220, 153, 114, 234, 109, 25, 35, 90, 99, 85}
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] Cipher Suite: SSL_RSA_WITH_RC4_128_MD5
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] Compression Method: 0
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] ***
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] %% Created:  [Session-3, SSL_RSA_WITH_RC4_128_MD5]
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] ** SSL_RSA_WITH_RC4_128_MD5
  | 2008-10-09 09:26:46,598 INFO  [STDOUT] *** Certificate chain
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] chain [0] = [
  | [
  |   Version: V1
  |   Subject: CN=Covergence Inc, OU=covergence.com, O=covergence.com, L=Maynard, ST=MA, C=US
  |   Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
  | 
  |   Key:  Sun RSA public key, 1023 bits
  |   modulus: 81725270146334745875970522895234154947216516690920959125303823170348978811784807265895380886647633641629189766376106765112961237368821433143575600447558640161067575359884112030290494797031619076309724764611453890031396674059958758716180895503505104133773512431900120777464449650731492266954869988956381237691
  |   public exponent: 65537
  |   Validity: [From: Thu May 26 09:25:53 EDT 2005,
  |                To: Sun May 24 09:25:53 EDT 2015]
  |   Issuer: CN=Covergence Inc, OU=covergence.com, O=covergence.com, L=Maynard, ST=MA, C=US
  |   SerialNumber: [    4295ce61]
  | 
  | ]
  |   Algorithm: [MD5withRSA]
  |   Signature:
  | 0000: 33 5F 91 1E 19 E9 48 72   90 57 D0 11 62 A0 AD 63  3_....Hr.W..b..c
  | 0010: 39 4F 70 3E 01 A8 DC 7B   BC BC A3 85 22 C8 DE EB  9Op>........"...
  | 0020: E9 97 FD B1 9A 85 96 28   C6 38 03 67 45 ED 8E B4  .......(.8.gE...
  | 0030: D1 73 9B D8 B9 52 13 EF   1E 4A 3B C8 60 BD 4B 88  .s...R...J;.`.K.
  | 0040: 64 E2 A2 3E 33 F8 27 EB   13 DB 18 C7 F4 FC 80 80  d..>3.'.........
  | 0050: 75 39 E0 73 0A 97 59 A4   35 CE 38 F5 AD B4 C6 1B  u9.s..Y.5.8.....
  | 0060: 6A 47 E4 14 CB 4E A5 0D   F0 7A 90 26 5F 31 67 D5  jG...N...z.&_1g.
  | 0070: E2 2F 56 27 7F 54 77 46   84 DE C4 46 C1 85 B3 CD  ./V'.TwF...F....
  | 
  | ]
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] ***
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] WorkManager(2)-8
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] , SEND TLSv1 ALERT:  
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] fatal, 
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] description = certificate_unknown
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] WorkManager(2)-8, WRITE: TLSv1 Alert, length = 2
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] WorkManager(2)-8, called closeSocket()
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] WorkManager(2)-8, handling exception: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] %% No cached client session
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] *** ClientHello, TLSv1
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] RandomCookie:  
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] GMT: 1206781334 
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] bytes = { 
  | ... deleted ...
  | 2008-10-09 09:26:46,613 INFO  [STDOUT]  }
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] Session ID:  
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] {}
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] Cipher Suites: [SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5, SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA]
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] Compression Methods:  { 
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] 0
  | 2008-10-09 09:26:46,613 INFO  [STDOUT]  }
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] ***
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] WorkManager(2)-8, WRITE: TLSv1 Handshake, length = 73
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] WorkManager(2)-8, WRITE: SSLv2 client hello message, length = 98
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] WorkManager(2)-8, READ: TLSv1 Handshake, length = 7766
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] *** ServerHello, TLSv1
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] RandomCookie:  
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] GMT: 1206781333 
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] bytes = { 
  | ... deleted ...
  | 2008-10-09 09:26:46,613 INFO  [STDOUT]  }
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] Session ID:  
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] {72, 238, 6, 149, 78, 22, 88, 26, 187, 70, 119, 124, 52, 65, 74, 99, 40, 186, 13, 28, 49, 148, 169, 21, 158, 140, 159, 213, 203, 62, 252, 180}
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] Cipher Suite: SSL_RSA_WITH_RC4_128_MD5
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] Compression Method: 0
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] ***
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] %% Created:  [Session-4, SSL_RSA_WITH_RC4_128_MD5]
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] ** SSL_RSA_WITH_RC4_128_MD5
  | 2008-10-09 09:26:46,613 INFO  [STDOUT] *** Certificate chain
  | 2008-10-09 09:26:46,629 INFO  [STDOUT] chain [0] = [
  | [
  |   Version: V1
  |   Subject: CN=Covergence Inc, OU=covergence.com, O=covergence.com, L=Maynard, ST=MA, C=US
  |   Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
  | 
  |   Key:  Sun RSA public key, 1023 bits
  |   modulus: 81725270146334745875970522895234154947216516690920959125303823170348978811784807265895380886647633641629189766376106765112961237368821433143575600447558640161067575359884112030290494797031619076309724764611453890031396674059958758716180895503505104133773512431900120777464449650731492266954869988956381237691
  |   public exponent: 65537
  |   Validity: [From: Thu May 26 09:25:53 EDT 2005,
  |                To: Sun May 24 09:25:53 EDT 2015]
  |   Issuer: CN=Covergence Inc, OU=covergence.com, O=covergence.com, L=Maynard, ST=MA, C=US
  |   SerialNumber: [    4295ce61]
  | 
  | ]
  |   Algorithm: [MD5withRSA]
  |   Signature:
  | 0000: 33 5F 91 1E 19 E9 48 72   90 57 D0 11 62 A0 AD 63  3_....Hr.W..b..c
  | 0010: 39 4F 70 3E 01 A8 DC 7B   BC BC A3 85 22 C8 DE EB  9Op>........"...
  | 0020: E9 97 FD B1 9A 85 96 28   C6 38 03 67 45 ED 8E B4  .......(.8.gE...
  | 0030: D1 73 9B D8 B9 52 13 EF   1E 4A 3B C8 60 BD 4B 88  .s...R...J;.`.K.
  | 0040: 64 E2 A2 3E 33 F8 27 EB   13 DB 18 C7 F4 FC 80 80  d..>3.'.........
  | 0050: 75 39 E0 73 0A 97 59 A4   35 CE 38 F5 AD B4 C6 1B  u9.s..Y.5.8.....
  | 0060: 6A 47 E4 14 CB 4E A5 0D   F0 7A 90 26 5F 31 67 D5  jG...N...z.&_1g.
  | 0070: E2 2F 56 27 7F 54 77 46   84 DE C4 46 C1 85 B3 CD  ./V'.TwF...F....
  | 
  | ]
  | 2008-10-09 09:26:46,629 INFO  [STDOUT] ***
  | 2008-10-09 09:26:46,629 INFO  [STDOUT] WorkManager(2)-8
  | 2008-10-09 09:26:46,629 INFO  [STDOUT] , SEND TLSv1 ALERT:  
  | 2008-10-09 09:26:46,629 INFO  [STDOUT] fatal, 
  | 2008-10-09 09:26:46,629 INFO  [STDOUT] description = certificate_unknown
  | 2008-10-09 09:26:46,629 INFO  [STDOUT] WorkManager(2)-8, WRITE: TLSv1 Alert, length = 2
  | 2008-10-09 09:26:46,629 INFO  [STDOUT] WorkManager(2)-8, called closeSocket()
  | 2008-10-09 09:26:46,629 INFO  [STDOUT] WorkManager(2)-8, handling exception: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found
  | 2008-10-09 09:26:46,629 DEBUG [org.jboss.remoting.transport.http.HTTPClientInvoker] Unable to retrieve response message
  | javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found
  | 	at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:150)
  | 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1518)
  | 	at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:174)
  | 	at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:168)
  | 	at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:848)
  | 	at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:106)
  | 	at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:495)
  | 	at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:433)
  | 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:818)
  | 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1030)
  | 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1057)
  | 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1041)
  | 	at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:402)
  | 	at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:170)
  | 	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:861)
  | 	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:920)
  | 	at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:367)
  | 	at java.net.HttpURLConnection.getResponseMessage(HttpURLConnection.java:433)
  | 	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseMessage(HttpsURLConnectionImpl.java:362)
  | 	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:340)
  | 	at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:137)
  | 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
  | 	at org.jboss.remoting.Client.invoke(Client.java:1634)
  | 	at org.jboss.remoting.Client.invoke(Client.java:548)
  | 	at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:233)
  | 	at org.jboss.ws.core.client.SOAPProtocolConnectionHTTP.invoke(SOAPProtocolConnectionHTTP.java:73)
  | 	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:339)
  | 	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
  | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
  | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
  | 	at $Proxy161.getBuildInfo(Unknown Source)
  | 	at com.covergence.enms.status.PollClusterMDB.pollCluster(PollClusterMDB.java:86)
  | 	at com.covergence.enms.status.PollClusterMDB.onMessage(PollClusterMDB.java:140)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:585)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
  | 	at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
  | 	at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.tx.BMTInterceptor.handleStateless(BMTInterceptor.java:71)
  | 	at org.jboss.ejb3.tx.BMTInterceptor.invoke(BMTInterceptor.java:131)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.security.RunAsSecurityInterceptor.invoke(RunAsSecurityInterceptor.java:83)
  | 	at org.jboss.ejb3.security.RunAsSecurityInterceptor.invoke(RunAsSecurityInterceptor.java:54)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
  | 	at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
  | 	at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
  | 	at $Proxy105.onMessage(Unknown Source)
  | 	at org.jboss.resource.adapter.jms.inflow.JmsServerSession.onMessage(JmsServerSession.java:178)
  | 	at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:906)
  | 	at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:170)
  | 	at org.jboss.mq.SpySession.run(SpySession.java:323)
  | 	at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:237)
  | 	at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
  | 	at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
  | 	at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756)
  | 	at java.lang.Thread.run(Thread.java:595)
  | Caused by: sun.security.validator.ValidatorException: No trusted certificate found
  | 	at sun.security.validator.SimpleValidator.buildTrustedChain(SimpleValidator.java:304)
  | 	at sun.security.validator.SimpleValidator.engineValidate(SimpleValidator.java:107)
  | 	at sun.security.validator.Validator.validate(Validator.java:203)
  | 	at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:172)
  | 	at com.sun.net.ssl.internal.ssl.JsseX509TrustManager.checkServerTrusted(SSLContextImpl.java:320)
  | 	at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:841)
  | 	... 61 more
  | 2008-10-09 09:26:46,629 DEBUG [org.jboss.ws.core.jaxws.handler.MessageContextJAXWS] Begin response processing
  | 2008-10-09 09:26:46,629 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] popMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at cc0376 (Thread WorkManager(2)-8)
  | 2008-10-09 09:26:46,629 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] pushMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at 17e07ae (Thread WorkManager(2)-8)
  | 2008-10-09 09:26:46,629 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] close
  | 2008-10-09 09:26:46,629 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] close
  | 2008-10-09 09:26:46,629 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] close
  | 2008-10-09 09:26:46,629 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] popMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at 17e07ae (Thread WorkManager(2)-8)
  | 2008-10-09 09:26:46,629 INFO  [com.covergence.enms.status.PollClusterMDB] Cluster [aj.cluster] WebServiceException while polling cluster javax.xml.ws.WebServiceException: java.io.IOException: Could not transmit message


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

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


From do-not-reply at jboss.com  Thu Oct  9 11:39:59 2008
From: do-not-reply at jboss.com (ajay662)
Date: Thu, 9 Oct 2008 11:39:59 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Jar file for
	org.jboss.ws.core.soap.SAAJMetaFactoryImpl.
Message-ID: <13895855.1223566799335.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am seeing the same issue with 

1) jboss 4.2.3 + metro 3.0.3

as well as 

2) jboss 4.2.2 + metro 3.0.3

And I run into other issues after I copy the jbossws-client.jar into server/default/lib dir.

Has anybody been able to successfully use jboss-metro with jboss 4.2.x? What are the exact steps to get it working?


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

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


From do-not-reply at jboss.com  Thu Oct  9 11:51:17 2008
From: do-not-reply at jboss.com (ajay662)
Date: Thu, 9 Oct 2008 11:51:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Jar file for
	org.jboss.ws.core.soap.SAAJMetaFactoryImpl.
Message-ID: <27728886.1223567477069.JavaMail.jboss@colo-br-02.atl.jboss.com>

Now I am trying jboss-4.2.2 + metro 3.0.2. Saw the same error. Copied jbossws-client.jar over to server/default/lib dir. Now I get following class not found exception. Is there any brave soul here who has been able to get it working? We need help...



  | java.lang.RuntimeException: java.lang.NoClassDefFoundError: org/apache/ws/policy/Policy
  | 	at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:174)
  | 	at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.tx.BMTInterceptor.handleStateless(BMTInterceptor.java:71)
  | 	at org.jboss.ejb3.tx.BMTInterceptor.invoke(BMTInterceptor.java:131)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.aspects.security.RunAsSecurityInterceptor.invoke(RunAsSecurityInterceptor.java:83)
  | 	at org.jboss.ejb3.security.RunAsSecurityInterceptor.invoke(RunAsSecurityInterceptor.java:54)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
  | 	at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
  | 	at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
  | 	at $Proxy106.onMessage(Unknown Source)
  | 	at org.jboss.resource.adapter.jms.inflow.JmsServerSession.onMessage(JmsServerSession.java:178)
  | 	at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:891)
  | 	at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:170)
  | 	at org.jboss.mq.SpySession.run(SpySession.java:323)
  | 	at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:237)
  | 	at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
  | 	at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
  | 	at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756)
  | 	at java.lang.Thread.run(Thread.java:595)
  | Caused by: java.lang.NoClassDefFoundError: org/apache/ws/policy/Policy
  | 	at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.buildMetaData(JAXWSClientMetaDataBuilder.java:92)
  | 	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:56)
  | 	at com.covergence.enms.ws.enms.EnmsService.<init>(EnmsService.java:38)
  | 	at com.covergence.enms.utils.WSPortLocator.getEnmsPortType(WSPortLocator.java:56)
  | 	at com.covergence.enms.status.PollClusterMDB.pollCluster(PollClusterMDB.java:85)
  | 	at com.covergence.enms.status.PollClusterMDB.onMessage(PollClusterMDB.java:140)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:585)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
  | 	at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
  | 	... 27 more


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

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


From do-not-reply at jboss.com  Thu Oct  9 12:15:10 2008
From: do-not-reply at jboss.com (maffeis)
Date: Thu, 9 Oct 2008 12:15:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Jar file for
	org.jboss.ws.core.soap.SAAJMetaFactoryImpl.
Message-ID: <7294472.1223568910977.JavaMail.jboss@colo-br-02.atl.jboss.com>

May I suggest that you log into JIRA and vote for the ticket

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

So maybe somebody of the JBossWS team will work on this issue reasonably soon.

(the workaround I described above lead to new errors when I tried to call my web service).

Cheers,
Silvano

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

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


From do-not-reply at jboss.com  Thu Oct  9 13:21:57 2008
From: do-not-reply at jboss.com (ajay662)
Date: Thu, 9 Oct 2008 13:21:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: consume WS over https no longer
	works when upgraded to j
Message-ID: <29711371.1223572917218.JavaMail.jboss@colo-br-02.atl.jboss.com>

For others benefit, in case they are running into same issue:

My workaround: Since I am only consuming web-services and not hosting them, i was able to get my application working by compiling against jaxws RI jars (v 2.1.3) and then by copying these RI jars to server/default/lib for runtime.

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

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


From do-not-reply at jboss.com  Thu Oct  9 13:30:09 2008
From: do-not-reply at jboss.com (ajay662)
Date: Thu, 9 Oct 2008 13:30:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Jar file for
	org.jboss.ws.core.soap.SAAJMetaFactoryImpl.
Message-ID: <7429126.1223573409636.JavaMail.jboss@colo-br-02.atl.jboss.com>

Voted.

BTW, since I am only consuming web-services, following workaround worked for me: 

Workaround: compile against jaxws RI (version 2.1.3) jars and then copy these RI jars to server/default/lib dir. I haven't done any extensive testing so far, but application seems to be cruising so far.

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

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


From do-not-reply at jboss.com  Fri Oct 10 05:58:25 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Fri, 10 Oct 2008 05:58:25 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Use
Message-ID: <8435724.1223632705945.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi pandatao,

1.) You can use ServletContextListeners for JaxWS POJO endpoints (no EJB3). I see you're using ejb's. It will not work there.
2.) AFAIK JBossAS 4.0.2 webservice module is AXIS based. I have no idea, if it's supported there :(


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

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


From do-not-reply at jboss.com  Fri Oct 10 07:10:33 2008
From: do-not-reply at jboss.com (ajayks)
Date: Fri, 10 Oct 2008 07:10:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Unable to create instance of Service
	object from a WSDL file
Message-ID: <8734171.1223637033306.JavaMail.jboss@colo-br-02.atl.jboss.com>

Dear All,
I  am evaluating  JAX-WS using JBOSS 4.2.3. I have exposed a simple statetless  EJB3.0 as a web service which  echo back the argument sent to it.
The code of web service is as follows :


  | package ccc;
  | 
  | import javax.jws.*;
  | import javax.ejb.*;
  | @Stateless
  | @javax.jws.WebService
  | public class Greeting  implements RemoteServiceInterface
  | {
  | 	@WebMethod
  | 	public String echo(String input)
  | 	{
  | 	      return input;
  | 	}
  | 
  | }
  | 

I made the jar file and deployed it on the JBOSS4.2.3 server.It deployed succesfully and the following WSDL file is created by the application server:-


  | - <definitions name="GreetingService" targetNamespace="http://ccc/" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://ccc/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  | - <types>
  | - <xs:schema targetNamespace="http://ccc/" version="1.0" xmlns:tns="http://ccc/" xmlns:xs="http://www.w3.org/2001/XMLSchema">
  |   <xs:element name="echo" type="tns:echo" /> 
  |   <xs:element name="echoResponse" type="tns:echoResponse" /> 
  | - <xs:complexType name="echo">
  | - <xs:sequence>
  |   <xs:element minOccurs="0" name="arg0" type="xs:string" /> 
  |   </xs:sequence>
  |   </xs:complexType>
  | - <xs:complexType name="echoResponse">
  | - <xs:sequence>
  |   <xs:element minOccurs="0" name="return" type="xs:string" /> 
  |   </xs:sequence>
  |   </xs:complexType>
  |   </xs:schema>
  |   </types>
  | - <message name="Greeting_echoResponse">
  |   <part element="tns:echoResponse" name="echoResponse" /> 
  |   </message>
  | + <message name="Greeting_echo">
  |   <part element="tns:echo" name="echo" /> 
  |   </message>
  | - <portType name="Greeting">
  | - <operation name="echo" parameterOrder="echo">
  |   <input message="tns:Greeting_echo" /> 
  |   <output message="tns:Greeting_echoResponse" /> 
  |   </operation>
  |   </portType>
  | - <binding name="GreetingBinding" type="tns:Greeting">
  |   <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /> 
  | - <operation name="echo">
  |   <soap:operation soapAction="" /> 
  | - <input>
  |   <soap:body use="literal" /> 
  |   </input>
  | - <output>
  |   <soap:body use="literal" /> 
  |   </output>
  |   </operation>
  |   </binding>
  | - <service name="GreetingService">
  | - <port binding="tns:GreetingBinding" name="GreetingPort">
  |   <soap:address location="http://dlhlx09.dlh.st.com:20120/mywebservice/Greeting" /> 
  |   </port>
  |   </service>
  |   </definitions>
  | 

I tried to consume the web service deployed on  the JBOSS  server using java batch using following code :-

  | package ccc.client;
  | import javax.xml.ws.Service;
  | import javax.xml.ws.WebServiceException;
  | import javax.xml.namespace.QName;
  | import java.net.MalformedURLException;
  | import java.net.URL;
  | import ccc.RemoteServiceInterface;
  | import javax.xml.ws.Provider;
  | public class EchoClient
  | {
  | 
  | 
  | 	URL wsdlLocation ; 
  | 	QName serviceName; 
  | 	Service service;
  | 	public static void main(String[] args)
  | 	{
  | 		try {
  | 			EchoClient client = new EchoClient();
  | 			client.doTest("Ajay");
  | 		} catch(Exception e) {
  | 			e.printStackTrace();
  | 		}
  | 	}
  | 
  | 	public void doTest(String x) 
  | 	{
  | 		try {
  | 			wsdlLocation = new URL("http://dlhlx09.dlh.st.com:20120/mywebservice/Greeting?wsdl");
  | 			serviceName = new QName("http://ccc/", "GreetingService");
  | 			Service service = Service.create(wsdlLocation, serviceName);
  | 			RemoteServiceInterface port = service.getPort(RemoteServiceInterface.class);
  | 			System.out.println("Invoking the sayHello operation  on the port.");
  | 
  | 			String response = port.echo(x);
  | 			System.out.println(response);
  | 		} catch(Exception e) {
  | 			e.printStackTrace();
  | 		}
  | 	}
  | 
  | }
  | 

But I am not able to create instance of Service object and following exeption is  being thrown at runtime :-


  | java.lang.IllegalStateException: Failed to load javax.xml.ws.spi.Provider: org.jboss.ws.core.jaxws.spi.ProviderImpl
  | 	at javax.xml.ws.spi.ProviderLoader.loadProvider(ProviderLoader.java:94)
  | 	at javax.xml.ws.spi.Provider.provider(Provider.java:80)
  | 	at javax.xml.ws.Service.<init>(Service.java:79)
  | 	at javax.xml.ws.Service.create(Service.java:96)
  | 	at ccc.client.EchoClient.doTest(EchoClient.java:33)
  | 	at ccc.client.EchoClient.main(EchoClient.java:23)
  | Caused by: java.lang.NoClassDefFoundError: org/jboss/util/NotImplementedException
  | 	at java.lang.Class.getDeclaredConstructors0(Native Method)
  | 	at java.lang.Class.privateGetDeclaredConstructors(Class.java:2357)
  | 	at java.lang.Class.getConstructor0(Class.java:2671)
  | 	at java.lang.Class.newInstance0(Class.java:321)
  | 	at java.lang.Class.newInstance(Class.java:303)
  | 	at javax.xml.ws.spi.ProviderLoader.loadProvider(ProviderLoader.java:89)
  | 

Can any one please help me out what is the cause of the prolem and
why expetion is being thrown by the client application at the time of creating instance of  Service object for consuming web service depoyed on JBOSS4.2.3

best regards,
Ajay Kumar

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

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


From do-not-reply at jboss.com  Fri Oct 10 09:39:20 2008
From: do-not-reply at jboss.com (tomstrummer)
Date: Fri, 10 Oct 2008 09:39:20 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: javax.xml.ws.WebServiceException:
	Unable to create Provi
Message-ID: <4943454.1223645960919.JavaMail.jboss@colo-br-02.atl.jboss.com>

Anyone find a solution to this?  I get the same thing on JBoss4.2.3.  I tried upgrading to the latest jbossws-metro on the server but it did not seem to help.

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

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


From do-not-reply at jboss.com  Fri Oct 10 10:23:10 2008
From: do-not-reply at jboss.com (jopersson)
Date: Fri, 10 Oct 2008 10:23:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: javax.xml.ws.WebServiceException:
	Unable to create Provi
Message-ID: <16272791.1223648590335.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I'am run a java client with (also having the jboss ws client jar in cp) :
-Djava.endorsed.dirs=C:/jboss-4.2.3.GA/lib/endorsed

C:/jboss-4.2.3.GA/lib/endorsed :
=====================
jaxb-api.jar
jboss-jaxrpc.jar
jboss-jaxws-ext.jar
jboss-jaxws.jar
jboss-saaj.jar
serializer.jar
xalan.jar
xercesImpl.jar




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

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


From do-not-reply at jboss.com  Sat Oct 11 00:24:41 2008
From: do-not-reply at jboss.com (dineshatit)
Date: Sat, 11 Oct 2008 00:24:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Problem: Web Service fails when jboss
	started using wrapper
Message-ID: <6450745.1223699081878.JavaMail.jboss@colo-br-02.atl.jboss.com>

sir,
      If JBOSS Server is started using wrapper class, Web Service Application is fails . 
wrapper download from: 

http://wrapper.tanukisoftware.org/doc/english/download.jsp

Error follows 

2008-10-11 00:20:04,579 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception
java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
        at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:441)
        at org.jboss.ws.core.soap.SOAPMessageImpl.(SOAPMessageImpl.java:83)
        at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:217)
        at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:195)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:447)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:284)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:201)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:134)
        at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
        at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
        at java.lang.Thread.run(Thread.java:619)
2008-10-11 00:20:04,581 DEBUG [org.jboss.wsf.stack.jbws.RequestHandlerImpl] END handleRequest: jboss.ws:context=WebServiceApp-QA,endpoint=JOSWebService
2008-10-11 00:20:04,581 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] popMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at 40b718 (Thread http-0.0.0.0-8080-2)
2008-10-11 00:20:04,582 ERROR [org.jboss.wsf.stack.jbws.RequestHandlerImpl] Error processing web service request
org.jboss.ws.WSException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
        at org.jboss.ws.WSException.rethrow(WSException.java:68)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:325)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:201)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:134)
        at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
        at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
        at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
        at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:441)
        at org.jboss.ws.core.soap.SOAPMessageImpl.(SOAPMessageImpl.java:83)
        at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:171)
        at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:245)
        at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:174)
        at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:104)
        at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:671)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:488)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:284)
        ... 22 more
2008-10-11 00:20:04,583 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/WebServiceApp-QA].[JOSWebService]] Servlet.service() for servlet JOSWebService threw exception
java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
        at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:441)
        at org.jboss.ws.core.soap.SOAPMessageImpl.(SOAPMessageImpl.java:83)
        at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:171)
        at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:245)
        at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:174)
        at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:104)
        at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:671)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:488)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:284)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:201)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:134)
        at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
        at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
        at java.lang.Thread.run(Thread.java:619)


Please guide to solve the problem !!!!!!!!!!!!1

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

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


From do-not-reply at jboss.com  Sat Oct 11 00:36:17 2008
From: do-not-reply at jboss.com (dineshatit)
Date: Sat, 11 Oct 2008 00:36:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem: Web Service fails when
	jboss started using wrap
Message-ID: <16639799.1223699777476.JavaMail.jboss@colo-br-02.atl.jboss.com>

Note : if jboss started using ./run.sh (i .e without wrapper ) . web service application works fine !!!!

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

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


From do-not-reply at jboss.com  Sat Oct 11 09:15:17 2008
From: do-not-reply at jboss.com (betounisul)
Date: Sat, 11 Oct 2008 09:15:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WebService
Message-ID: <19488268.1223730917860.JavaMail.jboss@colo-br-02.atl.jboss.com>

I develop a WebService and I due configurations for signature. The service is shot in JBoss 4.2.2.GA 

Doubt: 

I made a customer with axis without informing the key / cryptography and even so the data are returnees. Where a service is available with a digital signature the client must not hold the key to access the data? Is this or I am mistaken? 

Thank you.

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

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


From do-not-reply at jboss.com  Sat Oct 11 13:13:02 2008
From: do-not-reply at jboss.com (amitru)
Date: Sat, 11 Oct 2008 13:13:02 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Error in calling webmethod by jbossws
	client in jboss4.2.3GA
Message-ID: <2781546.1223745182838.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello,

I am using jboss4.2.3 GA in my webproject, I am using wsconsume for creating web service client, the wsdl is successfully created, but when i called the webmethod i am getting the following error :- 

18:41:24,971 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
java.lang.reflect.UndeclaredThrowableException
       at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:225)
       at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:476)
       at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295)
       at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205)
       at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
       at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:81)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
       at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
       at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
       at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
       at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
       at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432)
       at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
       at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
       at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
       at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
       at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
       at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
       at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
       at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
       at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
       at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NoClassDefFoundError
       at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
       at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
       at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
       at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
       at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:588)
       at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.createProxy(ServiceDelegateImpl.java:398)
       at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortInternal(ServiceDelegateImpl.java:271)
       at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:198)
       at javax.xml.ws.Service.getPort(Service.java:141)


May be this problem is related to missing class, rite now I've put all the client jars in the classpath.  Thanks to please solve the problem. I also want to know which specific jars to put in the client classpath. I am using java 1.5 Ver.


Thanks,
Amit Ruwali


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

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


From do-not-reply at jboss.com  Sat Oct 11 13:35:02 2008
From: do-not-reply at jboss.com (amitru)
Date: Sat, 11 Oct 2008 13:35:02 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Unable to create instance of
	Service object from a WSDL
Message-ID: <28405471.1223746502699.JavaMail.jboss@colo-br-02.atl.jboss.com>

Ajay,

The same problem comes 2 me, i've just removed jaxws-rt.jar and jaxws-tools.jar & add xml parser jar (xmlapi) from jboss endoresd folder and my problem is solved may be this error is due to missing class in ur classpath OR jar conflict..

Regards,
Amit

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

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


From do-not-reply at jboss.com  Sun Oct 12 04:00:19 2008
From: do-not-reply at jboss.com (SameerGijare)
Date: Sun, 12 Oct 2008 04:00:19 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Installing jbossws 2.0.2GA in jboss
Message-ID: <11435935.1223798419132.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi 

How to install jbossws 2.0.2.GA in jboss-4.2.1GA or Jboss-4.2.2.GA?
I mean what is the procedure?If there is any documentaion on this please provide me link for the same.I have already downloaded jbossws-native-2.0.2.GA. Also does this version supports http://schemas.xmlsoap.org/wsdl/http bindings in WSDL?
Please guide me on this.

Thanks in advance and regards
-Sameer Gijare

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

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


From do-not-reply at jboss.com  Sun Oct 12 23:50:20 2008
From: do-not-reply at jboss.com (mimi_tan1985)
Date: Sun, 12 Oct 2008 23:50:20 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WSDL generation: use="literal" is
	generated instead of use"e
Message-ID: <1105830.1223869820560.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi all, 
In our code we need to use "encoded" as the SOAPBinding style. Everytime the jboss is started, it generate a wsdl file in the directory: JBOSS_HOME/server/default/data/wsdl/xxxx.jar/xxxx.wsdl.
The generated wsdl is always:
<input>
  | <soap:body namespace="http://xxxx.xxx.com/" use="literal"/>
  | </input>

which made the application doesn't run well because it should be like this instead:
<input>
  | <soap:body namespace="http://xxxx.xxx.com" use="encoded"/>
  | </input>

Is there a way to fix this problem? Because everytime the jboss is restarted, the generated wsdl need to be changed from literal into encoded which is a little annoying in the deployment process.

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

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


From do-not-reply at jboss.com  Mon Oct 13 02:55:43 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 13 Oct 2008 02:55:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSDL generation: use=
Message-ID: <9786048.1223880943611.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

   you have to specify 
@javax.jws.soap.SOAPBinding(style = SOAPBinding.Style.RPC)
annotation on your SEI and/or endpoint implementation.

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

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


From do-not-reply at jboss.com  Mon Oct 13 03:03:47 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 13 Oct 2008 03:03:47 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Installing jbossws 2.0.2GA in jboss
Message-ID: <25621080.1223881427378.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

   follow instructions here. In your case you will type:
ant deploy-jboss421
respectively
ant deploy-jboss422

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

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


From do-not-reply at jboss.com  Mon Oct 13 03:05:42 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 13 Oct 2008 03:05:42 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Error in calling webmethod by
	jbossws client in jboss4.2
Message-ID: <1816281.1223881542927.JavaMail.jboss@colo-br-02.atl.jboss.com>

Take a look to JBOSS_HOME/bin/wsrunclient shell script.
It should contain minimal client classpath necessary to run your clients.

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

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


From do-not-reply at jboss.com  Mon Oct 13 03:08:09 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 13 Oct 2008 03:08:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem: Web Service fails when
	jboss started using wrap
Message-ID: <12872353.1223881689307.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

   this is the question for project owner 

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

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


From do-not-reply at jboss.com  Mon Oct 13 03:09:37 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 13 Oct 2008 03:09:37 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem: Web Service fails when
	jboss started using wrap
Message-ID: <19145293.1223881777873.JavaMail.jboss@colo-br-02.atl.jboss.com>

Probably you will need to specify:
-Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS"
as run.sh shell script does

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

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


From do-not-reply at jboss.com  Mon Oct 13 04:07:05 2008
From: do-not-reply at jboss.com (mimi_tan1985)
Date: Mon, 13 Oct 2008 04:07:05 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSDL generation: use=
Message-ID: <9905846.1223885225998.JavaMail.jboss@colo-br-02.atl.jboss.com>

It's already there in the SEI:

  | @SOAPBinding(style=Style.RPC)
  | public interface abcRemote extends Remote{
  | 
  | }


Thanks!





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

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


From do-not-reply at jboss.com  Mon Oct 13 05:34:03 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 13 Oct 2008 05:34:03 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSDL generation: use=
Message-ID: <30178336.1223890443618.JavaMail.jboss@colo-br-02.atl.jboss.com>

And in service implementation?

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

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


From do-not-reply at jboss.com  Mon Oct 13 12:09:14 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 13 Oct 2008 12:09:14 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem: Web Service fails when
	jboss started using wrap
Message-ID: <31285233.1223914154499.JavaMail.jboss@colo-br-02.atl.jboss.com>

This exception typically happens when you run JBossAS with JDK6. Apparently, either the account used to run JBossAS as a service has JAVA_HOME set to JDK6, or Tanuki is configured to use JDK6.

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

I would point you to the wiki article that talks about this but the wiki changed last Friday, none of the links I saved are working any more, and I cannot seem to find the article.

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

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


From do-not-reply at jboss.com  Mon Oct 13 23:27:10 2008
From: do-not-reply at jboss.com (mimi_tan1985)
Date: Mon, 13 Oct 2008 23:27:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSDL generation: use=
Message-ID: <15428759.1223954830107.JavaMail.jboss@colo-br-02.atl.jboss.com>

I'm sorry, what do u mean by service implementation?

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

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


From do-not-reply at jboss.com  Tue Oct 14 02:29:46 2008
From: do-not-reply at jboss.com (dineshatit)
Date: Tue, 14 Oct 2008 02:29:46 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem: Web Service fails when
	jboss started using wrap
Message-ID: <14599878.1223965786327.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thanks for your guide !!!

-Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS" 

this could be the problem !!!!!

bec i have noticed this arguments not available while starting through wrapper 

but wrapper configuration , how to set -Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS" this arguments in wrapper.conf 

Any Idea !!!


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

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


From do-not-reply at jboss.com  Tue Oct 14 02:31:48 2008
From: do-not-reply at jboss.com (ryoung2504)
Date: Tue, 14 Oct 2008 02:31:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - @WebServiceRef not working in ear
Message-ID: <16859757.1223965908670.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have deployed a web service to my app server in a jar (simple echotest one).
I have created client classes using wsconsume and can access the client using @WebServiceRef injected onto an ejb3 stateless session bean when the bean is packaged in a jar.
However if I package a stateless (or stateful) ejb3 bean in a jar which is in my production ear then anything annotated with @WebServiceRef fails with the injected field being left as null.

I am using 
JBoss 4.2.2.GA
JBossWS-native 3.0.3
Seam 2.0.2.SP1

FYI I also have loadtime AOP weaving turned on.

Is there something I need to put on my annotations or xml file to make this work or is it simply not possible at present?

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

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


From do-not-reply at jboss.com  Tue Oct 14 10:42:29 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 14 Oct 2008 10:42:29 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem: Web Service fails when
	jboss started using wrap
Message-ID: <33532995.1223995349677.JavaMail.jboss@colo-br-02.atl.jboss.com>

Tanuki uses the wrapper.conf file to define both JVM and application arguments. You need to set the wrapper.java.additional.N property (where N is the next number - for example, if there are already wrapper.java.additional.1 and wrapper.java.additional.2, you should set wrapper.java.additional.3).

Here are the docs: http://wrapper.tanukisoftware.org/doc/english/properties.html

By the way, the multiple exclamation points are really irritating.

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

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


From do-not-reply at jboss.com  Tue Oct 14 11:16:38 2008
From: do-not-reply at jboss.com (tomstrummer)
Date: Tue, 14 Oct 2008 11:16:38 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Enable debug logging
Message-ID: <28440142.1223997398053.JavaMail.jboss@colo-br-02.atl.jboss.com>

I'd like to see the HTTP stream for a WS client using JBossWS-native v3.0.3 on JBossAS 4.2.3.  I've found this thread:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=126403
which mentions a log4j.properties file in the JAR, but that kinda sucks when I'm using Maven and don't really want to manually edit JARs in my repository.  

I also found this in the server's jboss-log4j.xml file:

  |    <!-- Enable JBossWS message tracing -->
  |    <category name="org.jboss.ws.core.MessageTrace">
  |     <priority value="TRACE"/>
  |    </category>
  | 

However this did not seem to have any effect.  I also tried setting "org.jboss.ws" to TRACE but that didn't seem to help either.  Any pointers?  

Thanks.


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

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


From do-not-reply at jboss.com  Tue Oct 14 12:40:53 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 14 Oct 2008 12:40:53 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Enable debug logging
Message-ID: <21753111.1224002453208.JavaMail.jboss@colo-br-02.atl.jboss.com>

The jboss-log4j.xml setting should work. When I uncomment it, I see entries like the following in the server.log file:

2008-09-29 13:45:04,899 TRACE [org.jboss.ws.core.MessageTrace] (http-127.0.0.1-8080-1) Incoming Request Message
  | <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>
  |  <env:Header/>
  |  <env:Body>
  |   <ns1:getRate xmlns:ns1='http://ws.jbia.org/'>
  |    <arg0>NH</arg0>
  |   </ns1:getRate>
  |  </env:Body>
  | </env:Envelope>
  | ...
  | 2008-09-29 13:45:04,914 TRACE [org.jboss.ws.core.MessageTrace] (http-127.0.0.1-8080-1) Outgoing Response Message
  | <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>
  |  <env:Header/>
  |  <env:Body>
  |   <ns1:getRateResponse xmlns:ns1='http://ws.jbia.org/'>
  |    <return>0.0</return>
  |   </ns1:getRateResponse>
  |  </env:Body>
  | </env:Envelope>

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

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


From do-not-reply at jboss.com  Tue Oct 14 14:18:30 2008
From: do-not-reply at jboss.com (tomstrummer)
Date: Tue, 14 Oct 2008 14:18:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - No Classloaders found for ProviderImpl
Message-ID: <24984002.1224008310863.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have a default JBossAS 4.2.3 server on which I've installed JBossWS-Metro 3.0.3.  I have an EAR which uses a web service client.  When I try to invoke the client I get this:


  | java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.ws.core.jaxws.spi.ProviderImpl
  |         at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212)
  |         at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:521)
  |         at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:415)
  |         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
  |         at javax.xml.ws.spi.ProviderLoader.loadProvider(ProviderLoader.java:90)
  |         at javax.xml.ws.spi.Provider.provider(Provider.java:82)
  |         at javax.xml.ws.Service.<init>(Service.java:81)
  |         at com.pjm.emkt.emkt.xml.wsdl.MarketQueryService.<init>(MarketQueryService.java:46)
  | 

Does this mean JBoss is trying to use the native implementation rather than Metro?  

Thanks.

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

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


From do-not-reply at jboss.com  Tue Oct 14 14:52:45 2008
From: do-not-reply at jboss.com (amitru)
Date: Tue, 14 Oct 2008 14:52:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Error in calling webmethod by
	jbossws client in jboss4.2
Message-ID: <23402375.1224010365202.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thanks Richard,

My problem is solved actually in my war file i remove jaxws.jar & saaj.jar n then i put the necessary client files as you mentioned .. n then its running well .... 

There is the problem related to missing jar's.  

Amit



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

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


From do-not-reply at jboss.com  Tue Oct 14 14:56:26 2008
From: do-not-reply at jboss.com (tomstrummer)
Date: Tue, 14 Oct 2008 14:56:26 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Enable debug logging
Message-ID: <2191793.1224010586068.JavaMail.jboss@colo-br-02.atl.jboss.com>

Is there any way to get logging at the HTTP level?  It looks like the server is throwing a nasty exception and it's not even returning a valid SOAP response.  So it's not being parsed and I never get the log output.  On top of that, the service is over HTTPS so I can't use WireShark to watch the traffic either...

Thanks again.

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

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


From do-not-reply at jboss.com  Wed Oct 15 07:49:34 2008
From: do-not-reply at jboss.com (juliofrancisco)
Date: Wed, 15 Oct 2008 07:49:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBoss&Axis2:
	getInboundFaultFromMessageContext Error!
Message-ID: <16726915.1224071374367.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have developped a webservice using Axis2. The webservice uses mtom in order to send large files.

When I call it from a client in a jboss server I am getting the following error:

org.apache.axis2.AxisFault: java.lang.NullPointerException
at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:486)
at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:343)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at hcdSns.notificaciones.envio.WSProxyAttachementsStub.recepcion(WSProxyAttachementsStub.java:151)
at hcdSns.notificaciones.envio.ClienteEnvioNotificacion.enviarMsgXL(ClienteEnvioNotificacion.java:80)
at hcdSns.ciudadano.model.VerInformeHelper.envioHC007RecepcionHC008(VerInformeHelper.java:99)
at hcdSns.ciudadano.action.VerInformeAction.doAction(VerInformeAction.java:40)

I am also testing it in a Weblogic Server and it works ok and I get the file without any problem.

Any idea?

Thanks!call 

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

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


From do-not-reply at jboss.com  Wed Oct 15 14:28:35 2008
From: do-not-reply at jboss.com (sreeramrt3)
Date: Wed, 15 Oct 2008 14:28:35 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - java.lang.NoSuchMethodError:
	org.jboss.ejb3.stateless.Statel
Message-ID: <3637847.1224095315929.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi

I have tried multiple ejb examples and I run into the same exception. The server is unable to invoke setWebServiceContext in the process chain. Please find attached my example. I am using all the libraries from client, server\lib, server\default\lib and server\lib\endorsed.

Thanks

>----------------------------------------------------------------------
package webservice;

import javax.ejb.Remote;
import javax.ejb.Stateless;
import javax.jws.WebMethod;
import javax.jws.WebService;

@Stateless
@WebService(endpointInterface = "webservice.HelloRemote")
@Remote(HelloRemote.class)
public class HelloBean {

	@WebMethod
	public String echo(String e) {
		return "Web Service Echo + " + e;
	}
}

>----------------------------------------------------------------------
package webservice;

import java.rmi.Remote;

import javax.jws.WebMethod;
import javax.jws.WebService;
import javax.jws.soap.SOAPBinding;
import javax.jws.soap.SOAPBinding.Style;

@WebService
@SOAPBinding(style = Style.RPC)
public interface HelloRemote extends Remote {
	
	@WebMethod
	public String echo(String e);
}

>----------------------------------------------------------------------

package client;

import java.net.URL;

import javax.xml.namespace.QName;
import javax.xml.rpc.Service;
import javax.xml.rpc.ServiceFactory;

import webservice.HelloRemote;

public class HelloBeanClient {
    public static void main(String[] args) throws Exception {
        System.out.println("Starting Test Client");
        URL wsdlUrl = new URL("http://127.0.0.1:8000/" +
        		"HelloBeanEAR-HelloBean/HelloBean?wsdl");
        QName qname = new QName("http://hello/", "HelloBeanService");

        System.out.println("Creating a service Using: \n\t" 
                                   + wsdlUrl + " \n\tand " + qname);
        ServiceFactory factory = ServiceFactory.newInstance();
        
        
        URL url = new URL("http://127.0.0.1:8000/" +
		"HelloBeanEAR-HelloBean/HelloBean");
        Service remote = factory.createService(wsdlUrl, qname);

        System.out.println("Obtaining reference to a proxy object");
        
        HelloRemote proxy = (HelloRemote) remote.getPort(HelloRemote.class);
        System.out.println("Accessed local proxy: " + proxy);
       
        String string = "John";
        System.out.println("Sending: " + string);
        
        System.out.println("Receiving: " + proxy.echo("John"));
    }
}


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

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


From do-not-reply at jboss.com  Wed Oct 15 15:19:37 2008
From: do-not-reply at jboss.com (pxstein)
Date: Wed, 15 Oct 2008 15:19:37 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - How do I find out the JBossWS version
	which is included in J
Message-ID: <22347235.1224098377497.JavaMail.jboss@colo-br-02.atl.jboss.com>

As far as I know JBoss AS contains JBossWS as well.

How do I find out which version in detail is included?

Read: In which readme file are the included parts and their release listed?

Peter

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

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


From do-not-reply at jboss.com  Wed Oct 15 15:53:16 2008
From: do-not-reply at jboss.com (egalych)
Date: Wed, 15 Oct 2008 15:53:16 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - .NET friendly Endpoint for EJB3 WS
Message-ID: <8071131.1224100396064.JavaMail.jboss@colo-br-02.atl.jboss.com>

Is there a way to specify config-name ".NET friendly Endpoint" without adding @EndPointConfig?
My web service is packaged as ejb module of ear. I tried to create jboss.xml and put it into META-INF of ejb jar but I still see "Standard Endpoint" in server log.

I am using: jbossws-native-3.0.3.GA 

jboss.xml:


<webservice-description>
   <webservice-description-name>MyService</webservice-description-name>
   <config-name>.NET friendly Endpoint</config-name>
</webservice-description>





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

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


From do-not-reply at jboss.com  Wed Oct 15 15:56:33 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Wed, 15 Oct 2008 15:56:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: How do I find out the JBossWS
	version which is included
Message-ID: <31358027.1224100593506.JavaMail.jboss@colo-br-02.atl.jboss.com>

You can look in two places:

a) docs/licenses/thirdparty-licenses.xml

b) the META-INF/MANIFEST.MF file of the JAR file

I usually prefer option "b".

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

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


From do-not-reply at jboss.com  Wed Oct 15 15:59:53 2008
From: do-not-reply at jboss.com (sreeramrt3)
Date: Wed, 15 Oct 2008 15:59:53 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: java.lang.NoSuchMethodError:
	org.jboss.ejb3.stateless.St
Message-ID: <14088890.1224100793176.JavaMail.jboss@colo-br-02.atl.jboss.com>

Here is the stack trace associated with the exception. 

15:54:18,190 ERROR [ContainerBase] Servlet.service() for servlet HelloBean threw
 exception
java.lang.NoSuchMethodError: org.jboss.ejb3.stateless.StatelessBeanContext.setWe
bServiceContext(Ljavax/xml/ws/WebServiceContext;)V
        at org.jboss.wsf.container.jboss42.InvocationHandlerEJB3$CallbackImpl.at
tached(InvocationHandlerEJB3.java:134)
        at org.jboss.ejb3.EJBContainerInvocation.setBeanContext(EJBContainerInvo
cation.java:77)
        at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(Stateles
sInstanceInterceptor.java:56)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
java:101)
        at org.jboss.aspects.security.AuthenticationInterceptor.invoke(Authentic
ationInterceptor.java:77)
        at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3Auth
enticationInterceptor.java:106)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
java:101)
        at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterce
ptor.java:46)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
java:101)
        at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(Asynchrono
usInterceptor.java:106)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
java:101)
        at org.jboss.wsf.container.jboss42.InvocationHandlerEJB3.invoke(Invocati
onHandlerEJB3.java:103)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpoin
tInvoker.java:219)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHan
dlerImpl.java:476)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHand
lerImpl.java:295)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl
.java:205)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(Request
HandlerImpl.java:131)
        at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java
:81)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
        at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi
lter.java:96)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:235)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:230)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:175)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit
yAssociationValve.java:179)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv
e.java:84)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:128)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:104)
        at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedC
onnectionValve.java:157)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:241)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:844)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ss(Http11Protocol.java:580)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:44
7)
        at java.lang.Thread.run(Thread.java:595)

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

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


From do-not-reply at jboss.com  Wed Oct 15 16:00:32 2008
From: do-not-reply at jboss.com (sreeramrt3)
Date: Wed, 15 Oct 2008 16:00:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: java.lang.NoSuchMethodError:
	org.jboss.ejb3.stateless.St
Message-ID: <16112527.1224100832295.JavaMail.jboss@colo-br-02.atl.jboss.com>

It appears that there could be two different web service stacks deployed on the server and that it is trying to point to the incorrect one. Any clues?

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

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


From do-not-reply at jboss.com  Wed Oct 15 16:52:07 2008
From: do-not-reply at jboss.com (joncmuniz)
Date: Wed, 15 Oct 2008 16:52:07 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JbossWS with OpenSOO?
Message-ID: <19443507.1224103927490.JavaMail.jboss@colo-br-02.atl.jboss.com>

someone could me respond if there is any example of JBoss Web Services with Opensso?
or someone could discuss here with me a way to do that?

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

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


From do-not-reply at jboss.com  Thu Oct 16 01:17:57 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Thu, 16 Oct 2008 01:17:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: .NET friendly Endpoint for EJB3 WS
Message-ID: <17565085.1224134277423.JavaMail.jboss@colo-br-02.atl.jboss.com>

For EJB endpoints you can use only @EndpointConfig annotation.
For POJO endpoints you have another one option. You can specify the following 
context parameter in your web.xml:

<context-param>
  |     <param-name>jbossws-config-name</param-name>
  |     <param-value>Standard WSSecurity Endpoint</param-value>
  | </context-param>

or if you have custom config file included in your POJO endpoint archive:

  |   <context-param>
  |     <param-name>jbossws-config-name</param-name>
  |     <param-value>Custom Endpoint Config</param-value>
  |   </context-param>
  |   <context-param>
  |     <param-name>jbossws-config-file</param-name>
  |     <param-value>WEB-INF/custom-endpoint-config.xml</param-value>
  |   </context-param>

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

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


From do-not-reply at jboss.com  Thu Oct 16 02:52:08 2008
From: do-not-reply at jboss.com (raam.chand)
Date: Thu, 16 Oct 2008 02:52:08 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - how to enable both WS Security and MTOM
Message-ID: <3373664.1224139928733.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am trying to call a web service running in JBoss. The web service is enabled with both ws security and MTOM as per the requirement. When i am trying to call the web method from my java client, i am getting the below exception

Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: Endpoint {http://wsg.hpos.om.hp.com/}HPOSGatewayPort does not contain operation meta data for: {http://www.w3.org/2001/04/xmlenc#}EncryptedData
        at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:72)
        at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:109)
        at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:579)
        at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:381)
        at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:300)
        at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:166)
        at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
        at $Proxy17.getName(Unknown Source)
        at wsclient.TestHPOSClient.main(TestHPOSClient.java:106)

my client code is:
URL endpoint_new = new URL("http://15.70.176.190:9000/HPOSGateway/HPOSGateway?wsdl");
        QName qname = new QName("http://wsg.hpos.om.hp.com/", "HPOSGatewayService");    
        HPOSGateway port = new HPOSGatewayService(endpoint_new,qname).getHPOSGatewayPort(); 
        BindingProvider bp=(BindingProvider)port;
        SOAPBinding binding = (SOAPBinding)bp.getBinding();       
        binding.setMTOMEnabled(true);
        Map<String,Object> map = bp.getRequestContext();
        map.put(BindingProvider.USERNAME_PROPERTY,"administrator");
        map.put(BindingProvider.PASSWORD_PROPERTY,"da1sy");
        URL securityURL = new File("c://jboss-wsse-client.xml").toURL();
        ((StubExt)port).setSecurityConfig(securityURL.toExternalForm());
        ((StubExt)port).setConfigName("Standard WSSecurity Client");
        map.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, "http://15.70.176.190:9000/HPOSGateway/HPOSGateway");
        System.setProperty("org.jboss.ws.wsse.keyStore", "c:\\wsse.keystore");
        System.setProperty("org.jboss.ws.wsse.trustStore", "c:\\wsse.truststore");
        System.setProperty("org.jboss.ws.wsse.keyStorePassword", "jbossws");
        System.setProperty("org.jboss.ws.wsse.trustStorePassword", "jbossws");
        System.setProperty("org.jboss.ws.wsse.keyStoreType", "jks");
        System.setProperty("org.jboss.ws.wsse.trustStoreType", "jks");
        System.out.println(port.getName("Welcome to this testing part."));

,, my jboss.wsse.client.xml is...

<?xml version="1.0" encoding="UTF-8" ?> 
 <jboss-ws-security xmlns="http://www.jboss.com/ws-security/config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/ws-security/config http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd">
 
   
 
  
  
  
  </jboss-ws-security>

and my jboss-wsse-server.xml is ...

<?xml version="1.0" encoding="UTF-8"?>
<jboss-ws-security xmlns="http://www.jboss.com/ws-security/config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.jboss.com/ws-security/config http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd">
  <key-store-file>WEB-INF/wsse.keystore</key-store-file>
  <key-store-password>jbossws</key-store-password>
  <trust-store-file>WEB-INF/wsse.truststore</trust-store-file>
  <trust-store-password>jbossws</trust-store-password>
  
    
    
      
    
  
</jboss-ws-security>

i have my web service annotations like below.

@WebService(name="HPOSGateway",targetNamespace="http://wsg.hpos.om.hp.com/")
@EndpointConfig(configName = "Standard WSSecurity Endpoint")
@BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_MTOM_BINDING)
@HandlerChain(name = "HPOSGateway_handlerChain", file = "HPOSGateway_handler.xml")
public class HPOSGateway{

Can any one help me what is the problem and where i need to change? Please it is very urgent.

Regards
Ramchand


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

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


From do-not-reply at jboss.com  Thu Oct 16 04:06:32 2008
From: do-not-reply at jboss.com (jopersson)
Date: Thu, 16 Oct 2008 04:06:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: @WebServiceRef not working in ear
Message-ID: <9885313.1224144392073.JavaMail.jboss@colo-br-02.atl.jboss.com>


Would also like to bundle in EAR, but did not succeed..found this:

"JBoss will not support the Java EE 5 EAR format until version JBoss 5.x."

Maybe we have to wait until 5 is GA?

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

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


From do-not-reply at jboss.com  Thu Oct 16 11:01:02 2008
From: do-not-reply at jboss.com (egalych)
Date: Thu, 16 Oct 2008 11:01:02 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: .NET friendly Endpoint for EJB3 WS
Message-ID: <20777315.1224169262282.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thank you for reply.

I do not want to introduce container extensions in code. Is there a way to globally set endpoint configuration for JBoss instance?


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

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


From do-not-reply at jboss.com  Thu Oct 16 13:38:56 2008
From: do-not-reply at jboss.com (tomstrummer)
Date: Thu, 16 Oct 2008 13:38:56 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: No Classloaders found for
	ProviderImpl
Message-ID: <29782275.1224178736623.JavaMail.jboss@colo-br-02.atl.jboss.com>

I've turned on classloader isolation and added all of the Metro JARs (jaxws-rt and jaxb-impl and api JARs) but JBoss is still trying to look for the jbossws-client JAR.  Any ideas?

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

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


From do-not-reply at jboss.com  Thu Oct 16 14:46:05 2008
From: do-not-reply at jboss.com (pxstein)
Date: Thu, 16 Oct 2008 14:46:05 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Several pictures on JBossWS doc page
	missing
Message-ID: <15521645.1224182765951.JavaMail.jboss@colo-br-02.atl.jboss.com>

On page

http://jbossws.jboss.org/mediawiki/index.php?title=JAX-WS_User_Guide

some pictures (e.g. a picture named "Binding-provider.gif" 1/3 top down of the whole page)
are missing. Only the place holders are visible in the browser.

Who can fix the broken links?

Peter

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

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


From do-not-reply at jboss.com  Thu Oct 16 14:58:49 2008
From: do-not-reply at jboss.com (pxstein)
Date: Thu, 16 Oct 2008 14:58:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Does using Webservices require an
	installed JBoss Messaging?
Message-ID: <11003574.1224183529612.JavaMail.jboss@colo-br-02.atl.jboss.com>

Assume I want to deploy and use WebServices on an JBossAS.
Is it required to have JBoss Messaging installed on that JBoss AS
or do WebServices work without this component?

Peter

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

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


From do-not-reply at jboss.com  Fri Oct 17 02:54:04 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Fri, 17 Oct 2008 02:54:04 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Does using Webservices require an
	installed JBoss Messag
Message-ID: <20712982.1224226444586.JavaMail.jboss@colo-br-02.atl.jboss.com>

If you won't use message driven beans you're ready to go ;)

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

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


From do-not-reply at jboss.com  Fri Oct 17 11:17:57 2008
From: do-not-reply at jboss.com (tomstrummer)
Date: Fri, 17 Oct 2008 11:17:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Client call fails using JBossWS
Message-ID: <21227062.1224256677524.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi, I have a client that causes a web service to throw a 500 error when it uses JBossWS to make the service call.  For some reason the same request succeeds when Metro is used.  I have WireShark captures of the failed and successful requests, and there are only a few very minor differences that I can find.

(captures are below).

Here are the differences I see:

1.  JBossWS streams the request body, so it sets Transfer-Encoding: chunked and does not set a Content-Length header.  Not that it's excusable for a server to barf over this sort of thing, but this seems like the biggest difference between the two.  Is it possible to make JBossWS _not_ stream the request?

2.  JBossWS adds a "Pragma" header and a custom "JBoss-Remoting-Version" header.  Can't imagine these are the problem.

3.  JBossWS omits the XML declaration header in the request body, and happens to use "env" for the SOAP namespace, while Metro uses "S."  Again, I don't imagine this is the problem, but just for kicks, can this be customized?  

I'm going to use curl to see if I can't narrow down the problem further.  Unfortunately the actual text message that the server responds with on the 500 error is generic and doesn't provide any insight into the problem.

Thanks for any insight.

Good request:

  | No.     Time        Source                Destination           Protocol Info
  |      11 8.719335    172.16.10.203         192.251.13.133        HTTP     POST /emkt/xml/query HTTP/1.1 
  | 
  | Frame 11 (393 bytes on wire, 393 bytes captured)
  | Ethernet II, Src: HewlettP_ad:42:c3 (00:1c:c4:ad:42:c3), Dst: Cisco_f9:55:ff (00:17:e0:f9:55:ff)
  | Internet Protocol, Src: 172.16.10.203 (172.16.10.203), Dst: 192.251.13.133 (192.251.13.133)
  | Transmission Control Protocol, Src Port: 49504 (49504), Dst Port: http (80), Seq: 1, Ack: 1, Len: 327
  | Hypertext Transfer Protocol
  |     POST /emkt/xml/query HTTP/1.1\r\n
  |         Request Method: POST
  |         Request URI: /emkt/xml/query
  |         Request Version: HTTP/1.1
  |     SOAPAction: "query"\r\n
  |     Accept: text/xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2\r\n
  |     Content-Type: text/xml; charset=utf-8\r\n
  |     User-Agent: Java/1.6.0_06\r\n
  |     Host: emkt.pjm.com\r\n
  |     Connection: keep-alive\r\n
  |     Content-Length: 244
  |     \r\n
  | 
  | No.     Time        Source                Destination           Protocol Info
  |      12 8.719374    172.16.10.203         192.251.13.133        HTTP     Continuation or non-HTTP traffic
  | 
  | Frame 12 (310 bytes on wire, 310 bytes captured)
  | Ethernet II, Src: HewlettP_ad:42:c3 (00:1c:c4:ad:42:c3), Dst: Cisco_f9:55:ff (00:17:e0:f9:55:ff)
  | Internet Protocol, Src: 172.16.10.203 (172.16.10.203), Dst: 192.251.13.133 (192.251.13.133)
  | Transmission Control Protocol, Src Port: 49504 (49504), Dst Port: http (80), Seq: 328, Ack: 1, Len: 244
  | Hypertext Transfer Protocol
  |     Data (244 bytes)
  | 
  | 0000  3c 3f 78 6d 6c 20 76 65 72 73 69 6f 6e 3d 22 31   <?xml version="1
  | 0010  2e 30 22 20 3f 3e 3c 53 3a 45 6e 76 65 6c 6f 70   .0" ?><S:Envelop
  | 0020  65 20 78 6d 6c 6e 73 3a 53 3d 22 68 74 74 70 3a   e xmlns:S="http:
  | 0030  2f 2f 73 63 68 65 6d 61 73 2e 78 6d 6c 73 6f 61   //schemas.xmlsoa
  | 0040  70 2e 6f 72 67 2f 73 6f 61 70 2f 65 6e 76 65 6c   p.org/soap/envel
  | 0050  6f 70 65 2f 22 3e 3c 53 3a 42 6f 64 79 3e 3c 51   ope/"><S:Body><Q
  | 0060  75 65 72 79 52 65 71 75 65 73 74 20 78 6d 6c 6e   ueryRequest xmln
  | 0070  73 3d 22 68 74 74 70 3a 2f 2f 65 6d 6b 74 2e 70   s="http://emkt.p
  | 0080  6a 6d 2e 63 6f 6d 2f 65 6d 6b 74 2f 78 6d 6c 22   jm.com/emkt/xml"
  | 0090  3e 3c 51 75 65 72 79 4c 6f 61 64 52 65 73 70 6f   ><QueryLoadRespo
  | 00a0  6e 73 65 20 64 61 79 3d 22 32 30 30 38 2d 31 30   nse day="2008-10
  | 00b0  2d 31 35 22 3e 3c 41 6c 6c 2f 3e 3c 2f 51 75 65   -15"><All/></Que
  | 00c0  72 79 4c 6f 61 64 52 65 73 70 6f 6e 73 65 3e 3c   ryLoadResponse><
  | 00d0  2f 51 75 65 72 79 52 65 71 75 65 73 74 3e 3c 2f   /QueryRequest></
  | 00e0  53 3a 42 6f 64 79 3e 3c 2f 53 3a 45 6e 76 65 6c   S:Body></S:Envel
  | 00f0  6f 70 65 3e                                       ope>
  |         Data: 3C3F786D6C2076657273696F6E3D22312E3022203F3E3C53...
  | 
  | No.     Time        Source                Destination           Protocol Info
  |     239 11.362093   192.251.13.133        172.16.10.203         HTTP/XML HTTP/1.1 200 OK 
  | 
  | Frame 239 (424 bytes on wire, 424 bytes captured)
  | Ethernet II, Src: Cisco_f9:55:ff (00:17:e0:f9:55:ff), Dst: HewlettP_ad:42:c3 (00:1c:c4:ad:42:c3)
  | Internet Protocol, Src: 192.251.13.133 (192.251.13.133), Dst: 172.16.10.203 (172.16.10.203)
  | Transmission Control Protocol, Src Port: http (80), Dst Port: 49504 (49504), Seq: 244782, Ack: 572, Len: 358
  | [Reassembled TCP Segments (245139 bytes): #14(1368), #15(389), #18(1368), #20(1368), #22(1368), #24(1368), #26(1368), #28(1368), #30(1368), #32(1368), #34(1368), #36(1368), #38(1368), #40(1368), #42(1368), #44(1368), #46(1368), #48(1368), #]
  | Hypertext Transfer Protocol
  |     HTTP/1.1 200 OK\r\n
  |         Request Version: HTTP/1.1
  |         Response Code: 200
  |     Date: Wed, 15 Oct 2008 16:59:57 GMT\r\n
  |     Content-Type: text/xml\r\n
  |     Set-Cookie: JSESSIONID=L2hNJGnpYndLmYMcwv58CN2pfqMfmPJghLPfSJwpZdBQnDzDJLnG!-697457095; path=/\r\n
  |     Transfer-Encoding: chunked\r\n
  |     Set-Cookie: BIGipServeremkt.pjm.com=361277632.25115.0000; expires=Wed, 15-Oct-2008 17:29:59 GMT; path=/\r\n
  |     \r\n
  |     HTTP chunked response
  | eXtensible Markup Language
  | 

Bad request:

  | No.     Time        Source                Destination           Protocol Info
  |      12 9.644348    172.16.10.203         192.251.13.133        HTTP     POST /emkt/xml/query HTTP/1.1 
  | 
  | Frame 12 (454 bytes on wire, 454 bytes captured)
  | Ethernet II, Src: HewlettP_ad:42:c3 (00:1c:c4:ad:42:c3), Dst: Cisco_f9:55:ff (00:17:e0:f9:55:ff)
  | Internet Protocol, Src: 172.16.10.203 (172.16.10.203), Dst: 192.251.13.133 (192.251.13.133)
  | Transmission Control Protocol, Src Port: 42670 (42670), Dst Port: http (80), Seq: 1, Ack: 1, Len: 388
  | Hypertext Transfer Protocol
  |     POST /emkt/xml/query HTTP/1.1\r\n
  |         Request Method: POST
  |         Request URI: /emkt/xml/query
  |         Request Version: HTTP/1.1
  |     SOAPAction: "query"\r\n
  |     Content-Type: text/xml; charset=UTF-8\r\n
  |     JBoss-Remoting-Version: 22\r\n
  |     User-Agent: JBossRemoting - 2.2.2.SP8\r\n
  |     Cache-Control: no-cache\r\n
  |     Pragma: no-cache\r\n
  |     Host: emkt.pjm.com\r\n
  |     Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2\r\n
  |     Connection: keep-alive\r\n
  |     Transfer-Encoding: chunked\r\n
  |     \r\n
  | 
  | No.     Time        Source                Destination           Protocol Info
  |      13 9.645404    172.16.10.203         192.251.13.133        HTTP     Continuation or non-HTTP traffic
  | 
  | Frame 13 (352 bytes on wire, 352 bytes captured)
  | Ethernet II, Src: HewlettP_ad:42:c3 (00:1c:c4:ad:42:c3), Dst: Cisco_f9:55:ff (00:17:e0:f9:55:ff)
  | Internet Protocol, Src: 172.16.10.203 (172.16.10.203), Dst: 192.251.13.133 (192.251.13.133)
  | Transmission Control Protocol, Src Port: 42670 (42670), Dst Port: http (80), Seq: 389, Ack: 1, Len: 286
  | Hypertext Transfer Protocol
  |     Data (286 bytes)
  | 
  | 0000  31 31 37 0d 0a 3c 65 6e 76 3a 45 6e 76 65 6c 6f   117..<env:Envelo
  | 0010  70 65 20 78 6d 6c 6e 73 3a 65 6e 76 3d 27 68 74   pe xmlns:env='ht
  | 0020  74 70 3a 2f 2f 73 63 68 65 6d 61 73 2e 78 6d 6c   tp://schemas.xml
  | 0030  73 6f 61 70 2e 6f 72 67 2f 73 6f 61 70 2f 65 6e   soap.org/soap/en
  | 0040  76 65 6c 6f 70 65 2f 27 3e 3c 65 6e 76 3a 48 65   velope/'><env:He
  | 0050  61 64 65 72 3e 3c 2f 65 6e 76 3a 48 65 61 64 65   ader></env:Heade
  | 0060  72 3e 3c 65 6e 76 3a 42 6f 64 79 3e 3c 51 75 65   r><env:Body><Que
  | 0070  72 79 52 65 71 75 65 73 74 20 78 6d 6c 6e 73 3d   ryRequest xmlns=
  | 0080  22 68 74 74 70 3a 2f 2f 65 6d 6b 74 2e 70 6a 6d   "http://emkt.pjm
  | 0090  2e 63 6f 6d 2f 65 6d 6b 74 2f 78 6d 6c 22 3e 3c   .com/emkt/xml"><
  | 00a0  51 75 65 72 79 4d 61 72 6b 65 74 52 65 73 75 6c   QueryMarketResul
  | 00b0  74 73 20 74 79 70 65 3d 22 4c 6f 61 64 52 65 73   ts type="LoadRes
  | 00c0  70 6f 6e 73 65 22 20 64 61 79 3d 22 32 30 30 38   ponse" day="2008
  | 00d0  2d 31 30 2d 31 35 22 3e 3c 41 6c 6c 2f 3e 3c 2f   -10-15"><All/></
  | 00e0  51 75 65 72 79 4d 61 72 6b 65 74 52 65 73 75 6c   QueryMarketResul
  | 00f0  74 73 3e 3c 2f 51 75 65 72 79 52 65 71 75 65 73   ts></QueryReques
  | 0100  74 3e 3c 2f 65 6e 76 3a 42 6f 64 79 3e 3c 2f 65   t></env:Body></e
  | 0110  6e 76 3a 45 6e 76 65 6c 6f 70 65 3e 0d 0a         nv:Envelope>..
  |         Data: 3131370D0A3C656E763A456E76656C6F706520786D6C6E73...
  | 
  | No.     Time        Source                Destination           Protocol Info
  |      15 9.662267    172.16.10.203         192.251.13.133        HTTP     Continuation or non-HTTP traffic
  | 
  | Frame 15 (71 bytes on wire, 71 bytes captured)
  | Ethernet II, Src: HewlettP_ad:42:c3 (00:1c:c4:ad:42:c3), Dst: Cisco_f9:55:ff (00:17:e0:f9:55:ff)
  | Internet Protocol, Src: 172.16.10.203 (172.16.10.203), Dst: 192.251.13.133 (192.251.13.133)
  | Transmission Control Protocol, Src Port: 42670 (42670), Dst Port: http (80), Seq: 675, Ack: 1, Len: 5
  | Hypertext Transfer Protocol
  |     Data (5 bytes)
  | 
  | 0000  30 0d 0a 0d 0a                                    0....
  |         Data: 300D0A0D0A
  | 
  | No.     Time        Source                Destination           Protocol Info
  |      20 9.865277    192.251.13.133        172.16.10.203         HTTP     [TCP Out-Of-Order] HTTP/1.1 500 Internal Server Error  (text/html)
  | 
  | Frame 20 (1290 bytes on wire, 1290 bytes captured)
  | Ethernet II, Src: Cisco_f9:55:ff (00:17:e0:f9:55:ff), Dst: HewlettP_ad:42:c3 (00:1c:c4:ad:42:c3)
  | Internet Protocol, Src: 192.251.13.133 (192.251.13.133), Dst: 172.16.10.203 (172.16.10.203)
  | Transmission Control Protocol, Src Port: http (80), Dst Port: 42670 (42670), Seq: 1, Ack: 680, Len: 1224
  | Hypertext Transfer Protocol
  |     HTTP/1.1 500 Internal Server Error\r\n
  |         Request Version: HTTP/1.1
  |         Response Code: 500
  |     Date: Wed, 15 Oct 2008 17:13:36 GMT\r\n
  |     Content-Length: 883
  |     Content-Type: text/html\r\n
  |     Set-Cookie: JSESSIONID=L2kQ8KWNVHbzBDbfcNRwQc1QvR5W6PyPFzyQ6F5PL7lYds0tG9dP!-330699111; path=/\r\n
  |     Connection: Close\r\n
  |     Set-Cookie: BIGipServeremkt.pjm.com=344500416.25115.0000; expires=Wed, 15-Oct-2008 17:43:36 GMT; path=/\r\n
  |     \r\n
  | Line-based text data: text/html
  | 

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

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


From do-not-reply at jboss.com  Fri Oct 17 11:53:48 2008
From: do-not-reply at jboss.com (tomstrummer)
Date: Fri, 17 Oct 2008 11:53:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Client call fails using JBossWS
Message-ID: <11723519.1224258828544.JavaMail.jboss@colo-br-02.atl.jboss.com>

It seems that my suspicions are right; when "Transfer-Encoding: chunked" is used, I get the 500 error.  So is there any way to make JBossWS _not_ stream the request body?

The server appears to be WebLogic if it makes any difference...

Thanks again.

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

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


From do-not-reply at jboss.com  Fri Oct 17 15:53:20 2008
From: do-not-reply at jboss.com (joncmuniz)
Date: Fri, 17 Oct 2008 15:53:20 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - How to implement wsecurity!
Message-ID: <15481935.1224273200157.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have download jbossws 3.02 run ant jboss42 and ant test not create jbossws-native-dist\tests\resources\jaxws\samples\wssecurity it's empty
there are just two files wsse.keystore and wsse.truststore
I think that will creae some examples, here Can I find examples?

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

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


From do-not-reply at jboss.com  Fri Oct 17 17:10:41 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 17 Oct 2008 17:10:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: How to implement wsecurity!
Message-ID: <21895839.1224277841291.JavaMail.jboss@colo-br-02.atl.jboss.com>

See this discussion: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=127824

Even though that discussion is old, all of the configuration stuff should still work.

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

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


From do-not-reply at jboss.com  Sun Oct 19 05:08:10 2008
From: do-not-reply at jboss.com (haru01)
Date: Sun, 19 Oct 2008 05:08:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - CXF UserException not support?
Message-ID: <22379291.1224407290739.JavaMail.jboss@colo-br-02.atl.jboss.com>

hi

I want to throw UserException from server to client
http://jbossws.jboss.org/mediawiki/index.php?title=User_Guide#Fault_Handling


but, can't throw UserException

exclude exception dir 
in jbossws-cxf/tests/resources/test-excludes-jboss423.txt

Not support UserException?
If not support, then alternative?

jbossws-cxf-3.03.G.A


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

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


From do-not-reply at jboss.com  Mon Oct 20 05:17:46 2008
From: do-not-reply at jboss.com (agori)
Date: Mon, 20 Oct 2008 05:17:46 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Sharing HttpSession between multiple
	webservices
Message-ID: <13021866.1224494266523.JavaMail.jboss@colo-br-02.atl.jboss.com>

Actually we have two or three webservices in the same EAR. 
They are also stateful webservices, because thought they are marked as @Statless, they should mantain some data between client calls using HttpSession.

First question: if we use HttpSession as data container, is possible to share this session among multiple webservices? We know about the SESSION_MANTAIN property, but it works only in case of a single WS. 
What should I do at client side?

Second question: we are using EJB Session bean. Is possible to share the HttpSession between two or more EAR or JVM? I mean, if we deploy our WS in different machines, how is possible to make them see the same HTTP session?



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

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


From do-not-reply at jboss.com  Mon Oct 20 08:47:44 2008
From: do-not-reply at jboss.com (riue)
Date: Mon, 20 Oct 2008 08:47:44 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: CXF UserException not support?
Message-ID: <11837343.1224506864702.JavaMail.jboss@colo-br-02.atl.jboss.com>

Maybe this is a JBossWS-CXF's bug. JBossWS-CXF wraps all Exception in a RuntimeException and throws it. CXF is catching it, but it can't do nothing.

I fixed this problem by modified jbossws-cxf-3.0.3.GA/modules/server/src/main/java/org/jboss/wsf/stack/cxf/AbstractInvoker.java like that. See below.

   protected void handleException(Exception ex, Exchange exchange, Method m)
  |    {
  |        Throwable th = ex;
  |        if (ex instanceof InvocationTargetException) {
  |            th = ((InvocationTargetException)ex).getTargetException();
  |            if (th != null) {
  |                for (Class<?> cl : m.getExceptionTypes()) {
  |                    if (cl.isInstance(th)) {
  |                        exchange.getInMessage().put(FaultMode.class,
  |                                                    FaultMode.CHECKED_APPLICATION_FAULT);
  |                        throw new Fault(th);
  |                    }
  |                }
  |                if (th instanceof Fault) {
  |                    exchange.getInMessage().put(FaultMode.class,
  |                                                FaultMode.CHECKED_APPLICATION_FAULT);
  |                    throw (Fault)th;
  |                }
  |            }
  |        }
  | 
  |        exchange.getInMessage().put(FaultMode.class, FaultMode.UNCHECKED_APPLICATION_FAULT);
  |        if (th instanceof Fault)
  |            throw (Fault)th;
  | 
  |        throw new Fault(th);
  |    }
  | 



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

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


From do-not-reply at jboss.com  Mon Oct 20 11:10:59 2008
From: do-not-reply at jboss.com (dineshatit)
Date: Mon, 20 Oct 2008 11:10:59 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem: Web Service fails when
	jboss started using wrap
Message-ID: <2220122.1224515460012.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thanks Friends

          I have got the solution by adding this line 
 
  -Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS"  in wrapper.conf (addtional opt.1)





 

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

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


From do-not-reply at jboss.com  Mon Oct 20 15:28:49 2008
From: do-not-reply at jboss.com (StoyanPetrov)
Date: Mon, 20 Oct 2008 15:28:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - SocketException
Message-ID: <31982298.1224530929205.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I have one java ws that communicate with some ejb's.. and one .Net client (asp.net application). Sometimes the JBOSS is slow (when many users are connected to server or they have executed some complex tasks) In similar cases sometimes the ws fails with next exception:

ERROR [org.jboss.ws.core.server.AbstractServiceEndpointServlet] Error processing web service request
ClientAbortException:  java.net.SocketException: Software caused connection abort: socket write error
	at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:358)
	at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434)
	at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:309)
	at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:288)
	at org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:98)
	at org.jboss.ws.core.server.ServiceEndpointManager.processRequest(ServiceEndpointManager.java:485)
	at org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPost(AbstractServiceEndpointServlet.java:114)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
	at org.jboss.ws.core.server.AbstractServiceEndpointServlet.service(AbstractServiceEndpointServlet.java:75)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
	at java.lang.Thread.run(Thread.java:595)
Caused by: java.net.SocketException: Software caused connection abort: socket write error
	at java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
	at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
	at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:764)
	at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(ChunkedOutputFilter.java:124)
	at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.java:570)
	at org.apache.coyote.Response.doWrite(Response.java:560)
	at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:353)
	... 27 more

ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/wfws].[WFEndpoint]] Servlet.service() for servlet WFEndpoint threw exception
java.net.SocketException: Software caused connection abort: socket write error
	at java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
	at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
	at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:764)
	at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(ChunkedOutputFilter.java:124)
	at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.java:570)
	at org.apache.coyote.Response.doWrite(Response.java:560)
	at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:353)
	at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434)
	at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:309)
	at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:288)
	at org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:98)
	at org.jboss.ws.core.server.ServiceEndpointManager.processRequest(ServiceEndpointManager.java:485)
	at org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPost(AbstractServiceEndpointServlet.java:114)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
	at org.jboss.ws.core.server.AbstractServiceEndpointServlet.service(AbstractServiceEndpointServlet.java:75)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
	at java.lang.Thread.run(Thread.java:595)

I'm a bit surprised of this problem, because till now it worked well, but when I try to use it(ws) for enterprise application it fail!

I really appreciate any help you could provide in this. Can someone please help me? Thanks.

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

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


From do-not-reply at jboss.com  Tue Oct 21 10:56:12 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Tue, 21 Oct 2008 10:56:12 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBossWS 3.0.4 Released
Message-ID: <30310982.1224600972689.JavaMail.jboss@colo-br-02.atl.jboss.com>

I'm happy to announce the release of JBossWS 3.0.4 GA which includes Native, Metro and Apache CXF integration.

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

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

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

Installation instructions can be found here:
http://jbossws.jboss.org/mediawiki/index.php/Main_Page

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

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

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

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

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


From do-not-reply at jboss.com  Tue Oct 21 13:16:59 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Tue, 21 Oct 2008 13:16:59 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Several pictures on JBossWS doc
	page missing
Message-ID: <10092439.1224609419355.JavaMail.jboss@colo-br-02.atl.jboss.com>

I've created a jira issue for this, thanks.
https://jira.jboss.org/jira/browse/JBWS-2366

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

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


From do-not-reply at jboss.com  Tue Oct 21 16:07:53 2008
From: do-not-reply at jboss.com (thoste)
Date: Tue, 21 Oct 2008 16:07:53 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Where can view the SOAP sample msgs?
Message-ID: <27006775.1224619673308.JavaMail.jboss@colo-br-02.atl.jboss.com>

Assume I deployed a Webservice. Ok I can view a WSDL on JBoss by calling the URI.

However, is there a way to view the refering, corresponding SOAP message (in XML format) ?

This SOAP message (with sample parameter values) varies depending on the WSDL style RPC/Document encoded/literal.

Thomas

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

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


From do-not-reply at jboss.com  Tue Oct 21 16:13:02 2008
From: do-not-reply at jboss.com (thoste)
Date: Tue, 21 Oct 2008 16:13:02 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Can I use WSDL with "document/literal
	wrapped" style with JB
Message-ID: <15119781.1224619982553.JavaMail.jboss@colo-br-02.atl.jboss.com>

AFAIK "document/literal wrapped" WSDLs as described here:

http://www.ibm.com/developerworks/webservices/library/ws-whichwsdl/

are unofficially introduced (only) by Microsoft.

Are these WSDLs supported by JBoss(WS)?

Do I have to configure something special in JBoss to get these type of
WSDLs running in JBossAS?

Thomas


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

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


From do-not-reply at jboss.com  Tue Oct 21 16:39:06 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 21 Oct 2008 16:39:06 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Where can view the SOAP sample msgs?
Message-ID: <18206074.1224621546860.JavaMail.jboss@colo-br-02.atl.jboss.com>

Uncomment the org.jboss.ws.core.MessageTrace category in the server/xxx/conf/jboss-log4j.xml file. The SOAP messages will then show up in the server/xxx/log/server.log file.

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

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


From do-not-reply at jboss.com  Tue Oct 21 22:23:29 2008
From: do-not-reply at jboss.com (rishabh2u)
Date: Tue, 21 Oct 2008 22:23:29 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WebServiceContext injection. Was it
	fixed or not?
Message-ID: <28689500.1224642209921.JavaMail.jboss@colo-br-02.atl.jboss.com>

ggary so did it work for you finally then ???
I am using jboss423 on java 5 and cant seem to get it to work.
Then because of the hug u mentioned, i also tried using 421 and jbossws 201 but still it  does not work.


@WebService(name = "CreditCard", serviceName = "CreditCard", 
  | 		wsdlLocation = "/WEB-INF/wsdl/CreditCard.wsdl", 
  | 		targetNamespace = "http://aig.al.com/APCWebServices/CreditCardService/", 
  | 		endpointInterface = "com.al.aig.apc.ws.creditcard.server.generated.CreditCard")
  | @SOAPBinding(style = Style.DOCUMENT)		
  | public class CreditCardService_Impl implements CreditCard{
  | 
  | 	@Resource
  | 	WebServiceContext wsContext;
  | 
  | 	Logger log = Logger.getLogger(CreditCardService_Impl.class);
  | 
  | 	@WebMethod(operationName = "createCreditCard")
  | 	public CreateCreditCardResponse createCreditCard(
  | 			@WebParam(name = "parameters") CreateCreditCardInput parameters) {
  | 
  | 		log.debug("createCreditCard:entering.");
  | 		CreateCreditCardResponse drResp = new CreateCreditCardResponse();
  | 		System.out.println("addSecondaryMsisdn() called..................");
  | 
  | 		if (wsContext == null) {
  | 			System.out.println("its NULLL..");
  | 		} else {
  | 			System.out.println("ITS NOT NULL");
  | 		}
  | 
  | 		log.debug("createCreditCard:exiting.");
  | 		return drResp;
  | 	}
  | 
This is the code that i ahve got, nothing special here.  I have handwritten the WSDL for this webservice. 
Does the WebServiceContext injection depend on the binding type or something.

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

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


From do-not-reply at jboss.com  Wed Oct 22 02:59:02 2008
From: do-not-reply at jboss.com (kr8m3r_78)
Date: Wed, 22 Oct 2008 02:59:02 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Mapping @WebContext in ejb jar to
	context path in war (singl
Message-ID: <14988987.1224658742252.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am using JBoss 4.2.3, with Java 1.5.

I have a war that is bundled inside an EAR, this context path is: /testWeb

This is defined in the jboss-web.xml under the WEB-INF directory of the war.

 <jboss-web>  
  |   <security-domain>java:/jaas/aipDBCheck</security-domain>  
  |   <context-root>/testWeb</context-root>
  |  </jboss-web>
  | 

However, I also have a web service I would like to be accessible via the same context path. I have the @WebContext annotation specifying the same context path as defined below. 


  | @javax.jws.WebService(
  | 		targetNamespace = 
  | 			"http://xxx.xxx.xxx.com/"
  | 		,
  | 		serviceName = 
  | 			"SupplierAccessService"
  | 		, 
  | 		portName =
  | 			"SupplierAccessPort"
  | 			,wsdlLocation = "META-INF/wsdl/SupplierAccessService.wsdl"
  | 		)
  | 		@Stateless
  | 		@WebContext(contextRoot = "/testWeb", urlPattern = "/SupplierAccessPort", authMethod = "BASIC", transportGuarantee = "NONE", secureWSDLAccess = false)
  | 		@RolesAllowed("supplier")
  | 		@SecurityDomain("aipDBCheck")
  | 
  | public class SupplierAccessDelegate implements SupplierAccessDelegateLocal,
  | 		SupplierAccessDelegateRemote {
  | 

However, if I access http://localhost:8080/testWeb/SupplierAccessPort I get a 404 error, presumably because the WAR has received precedence over the context in the EJB. 

I can see that the EJB creates its own deployment, and a new jboss-web.xml and web.xml file is created and exploded into the tmp directory as if it were a new web app. 

Even though both these exploded web apps have the same context path there are no errors during start up.

I can only get my web service to work if I define a separate context in the annotation.

Can someone please let me know if this is possible, or do I need to define two different context paths in order for my web service to be accessible?

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

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


From do-not-reply at jboss.com  Wed Oct 22 08:31:21 2008
From: do-not-reply at jboss.com (mpelze)
Date: Wed, 22 Oct 2008 08:31:21 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - custom java type mapping in WS in JBoss
Message-ID: <25170955.1224678681954.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello,

is it possible to customize the JAXB mapping Jboss uses when deserializing an incoming SOAP message for a web service or serializing an outgoing message?

My problem is that I want to send and receive maps containing lists over a web service (implemented as EJB stateless session bean annotated as @WebService) in JBoss. JBoss uses jax-ws for web services and jax-ws uses jaxb for mapping Java classes to XML structures. Jaxb is not able to handle maps containing lists, so I have to define a custom mapping providing custom serializers / deserializers. I found out that there is the possibility in jaxb to write a configuration file for custom mappings that can look like this:

<bindings xmlns="http://java.sun.com/xml/ns/jaxb" version="2.0" xmlns:xs="http://www.w3.org/2001/XMLSchema">
  | 	<globalBindings>
  | 		<javaType name="my.package.MyClas" xmlType="xs:someName"
  | 			parseMethod="my.package.MyParser.parse"
  | 			printMethod="my.package.MyParser.print"
  | 		/>
  | 	</globalBindings>
  | </bindings>

Ist there a possibility to provide such a file to JBoss so that it will be used when (de-)serializing SOAP messages for or from my web services?

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

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


From do-not-reply at jboss.com  Wed Oct 22 11:27:15 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 22 Oct 2008 11:27:15 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Where can view the SOAP sample msgs?
Message-ID: <17323640.1224689235584.JavaMail.jboss@colo-br-02.atl.jboss.com>

http://jbossws.jboss.org/mediawiki/index.php?title=Log4J

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

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


From do-not-reply at jboss.com  Wed Oct 22 11:37:20 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 22 Oct 2008 11:37:20 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Can I use WSDL with
Message-ID: <27738087.1224689841019.JavaMail.jboss@colo-br-02.atl.jboss.com>

Yes, JBossWS support document/literal binding styles, both with wrapped and base parameter style.

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

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


From do-not-reply at jboss.com  Wed Oct 22 11:40:43 2008
From: do-not-reply at jboss.com (jorgemoralespou_2)
Date: Wed, 22 Oct 2008 11:40:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - What does " Cannot get port meta data
	for...." mean?
Message-ID: <3634315.1224690045446.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have webservice deployed that acts as a ws client application running in my app. I create a pool of clients to invoke different endpoints, and when starting my app, I get the following trace:
anonymous wrote : 
  | 2008-10-22 17:02:29,744 WARN  [org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl] Cannot get port meta data for: {http://www.csapi.org/wsdl/parlayx/multimedia_messaging/send/v2_4/service}SendMessage
  | 

I create stubs like this:

  |       QName qname = new QName(
  |             "http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/service",
  |             "SendSmsService");
  |       SendSmsService service = new SendSmsService(null, qname);
  |       SendSms a = service.getSendSms();
  |       return a;
  | 

When I make a request, everything goes as expected. An error if backend is not reachable (backend app is stopped) or backend response if everything is fine, so I don't really know if this trace is relevant at all, or the real meaning for this trace.

I have tried to initialize the Service with a URL rather than null, with different behaviour.

If I set, like explained in the forums:
anonymous wrote : 
  |  new URL("WEB-INF/wsdl/parlayx_sms_send_service_2_2.wsdl");
  | 

A MalformedURLException is thrown:
anonymous wrote : 
  | java.net.MalformedURLException: no protocol: WEB-INF/wsdl/parlayx_sms_send_service_2_2.wsdl
  | 

If I set a protocol, like:
anonymous wrote : 
  | new URL("resource:WEB-INF/wsdl/parlayx_sms_send_service_2_2.wsdl");
  | 

The resource is not found, and the service is not started. 
anonymous wrote : 
  | [org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl] Cannot access wsdlURL: resource:WEB-INF/wsdl/parlayx_sms_send_service_2_2.wsdl
  | 

I have tried different locations, so, what is correct way of doing this for clients?


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

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


From do-not-reply at jboss.com  Wed Oct 22 11:47:44 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 22 Oct 2008 11:47:44 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Client call fails using JBossWS
Message-ID: <7946652.1224690464474.JavaMail.jboss@colo-br-02.atl.jboss.com>

The server might not be able to correctly handle http 1.1 connections using chuncked transfer-encoding. See here for possible solutions: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971616

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

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


From do-not-reply at jboss.com  Wed Oct 22 12:01:11 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 22 Oct 2008 12:01:11 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: No Classloaders found for
	ProviderImpl
Message-ID: <2763046.1224691271497.JavaMail.jboss@colo-br-02.atl.jboss.com>

First of all make sure you installed jbossws-metro properly using the provided Ant build.
This said, the Provider implementation you get at runtime is influenced by classpath you have for your webservice client. In particular, the process of looking for the right implementation to load includes scanning the jars in the classpath for META-INF/services/javax.xml.ws.spi.Provider files containing the qualified name of the class to load. In your case, you might have the jbossws-native-jaxws.jar before the jaxws-rt.jar in your classpath.

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

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


From do-not-reply at jboss.com  Wed Oct 22 12:22:40 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 22 Oct 2008 12:22:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: @WebServiceRef not working in ear
Message-ID: <31892697.1224692560370.JavaMail.jboss@colo-br-02.atl.jboss.com>

Please provide a minimal application showing this behaviour and attach it to a new jira issue so that we can look at it.

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

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


From do-not-reply at jboss.com  Wed Oct 22 12:24:09 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 22 Oct 2008 12:24:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: how to enable both WS Security and
	MTOM
Message-ID: <2977562.1224692649033.JavaMail.jboss@colo-br-02.atl.jboss.com>

Try searching this forum, this has been covered in the past.

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

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


From do-not-reply at jboss.com  Wed Oct 22 12:25:27 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 22 Oct 2008 12:25:27 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JbossWS with OpenSOO?
Message-ID: <23924124.1224692727823.JavaMail.jboss@colo-br-02.atl.jboss.com>

There's no example available afaik. Perhaps you could share your achievement on this with the community here or on the mediawiki at jbossws.jboss.org.
Thanks

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

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


From do-not-reply at jboss.com  Wed Oct 22 12:29:46 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 22 Oct 2008 12:29:46 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: java.lang.NoSuchMethodError:
	org.jboss.ejb3.stateless.St
Message-ID: <3681344.1224692986098.JavaMail.jboss@colo-br-02.atl.jboss.com>

Which version of jbossws and jboss application server are you using? Did you try with a fresh installation of both?

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

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


From do-not-reply at jboss.com  Wed Oct 22 12:31:49 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 22 Oct 2008 12:31:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: How do I find out the JBossWS
	version which is included
Message-ID: <22974564.1224693109467.JavaMail.jboss@colo-br-02.atl.jboss.com>

Or simply boot the application server and read in the log something like:

  | 18:30:59,170 INFO  [NativeServerConfig] JBoss Web Services - Stack Native Core
  | 18:30:59,170 INFO  [NativeServerConfig] 3.0.4.GA
  | 

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

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


From do-not-reply at jboss.com  Wed Oct 22 12:33:21 2008
From: do-not-reply at jboss.com (tomstrummer)
Date: Wed, 22 Oct 2008 12:33:21 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Client call fails using JBossWS
Message-ID: <30583295.1224693201143.JavaMail.jboss@colo-br-02.atl.jboss.com>

Right, after looking a bit I am thinking the same thing -- the server simply has a bug that prevents it from correctly handling chunked requests.  

Unfortunately, the link you provided didn't seem to lead me to any solution as far as JBossWS.  I am providing the web service client but the server is far outside of my control so I will have to work around their bug.  

So -- How can I force JBossWS to use HTTP 1.0 or a request with a fixed content-length?

Thanks again.

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

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


From do-not-reply at jboss.com  Wed Oct 22 12:33:58 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 22 Oct 2008 12:33:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBoss&Axis2:
	getInboundFaultFromMessageContext Error!
Message-ID: <30995893.1224693238737.JavaMail.jboss@colo-br-02.atl.jboss.com>

The axis exception does not help us a lot. I woud suggest you to capture the message that goes on the wire both when using the jboss client and the weblogic client. Then we could compare the messages and try to understand what's wrong.

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

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


From do-not-reply at jboss.com  Wed Oct 22 12:36:40 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 22 Oct 2008 12:36:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Enable debug logging
Message-ID: <27639625.1224693400119.JavaMail.jboss@colo-br-02.atl.jboss.com>

"tomstrummer" wrote : Is there any way to get logging at the HTTP level?  It looks like the server is throwing a nasty exception and it's not even returning a valid SOAP response.  So it's not being parsed and I never get the log output.  On top of that, the service is over HTTPS so I can't use WireShark to watch the traffic either...
  | 
  | Thanks again.

If an exception is reaised by jbossws you can enable the org.jboss.ws log4j category and you find that for sure in the logs.

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

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


From do-not-reply at jboss.com  Wed Oct 22 12:50:38 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 22 Oct 2008 12:50:38 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: which tool to use to deploy
	standalone services as a web
Message-ID: <6114289.1224694238494.JavaMail.jboss@colo-br-02.atl.jboss.com>

Please take a look at the documentation at jbossws.jboss.org.
http://jbossws.jboss.org/mediawiki/index.php?title=JAX-WS_User_Guide#Web_Service_Endpoints

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

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


From do-not-reply at jboss.com  Wed Oct 22 12:52:45 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 22 Oct 2008 12:52:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Hosting JBossWS and JBoss.NET
	webservices
Message-ID: <12423340.1224694365272.JavaMail.jboss@colo-br-02.atl.jboss.com>

I remember having both jboss.net and jbossws running on JBossAS 4.0.5 a lot of time ago. Don't know if that's actually still possible, jboss.net is deprecated/not supported since many years.

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

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


From do-not-reply at jboss.com  Wed Oct 22 13:01:55 2008
From: do-not-reply at jboss.com (sreeramrt3)
Date: Wed, 22 Oct 2008 13:01:55 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: java.lang.NoSuchMethodError:
	org.jboss.ejb3.stateless.St
Message-ID: <11790587.1224694916077.JavaMail.jboss@colo-br-02.atl.jboss.com>

This problem is fixed. The issue was that I was trying to install the WS Native 3.0.3 stack on Jboss 4.3 GA. I would recommend anyone using any stack to first run the tests using the "ant tests" before doing anything with it. It should ideally be required to verify successful installation.

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

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


From do-not-reply at jboss.com  Wed Oct 22 17:03:49 2008
From: do-not-reply at jboss.com (thoste)
Date: Wed, 22 Oct 2008 17:03:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Java WS development better with Eclipse
	or with Netbeans ?
Message-ID: <3108642.1224709429417.JavaMail.jboss@colo-br-02.atl.jboss.com>

Which Jav IDE is better suitable for Java WebService Development for JBoss:

Eclipse 
or 
NetBeans
or
....?

Thomas

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

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


From do-not-reply at jboss.com  Wed Oct 22 17:56:46 2008
From: do-not-reply at jboss.com (alllle)
Date: Wed, 22 Oct 2008 17:56:46 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS client uses password from WSDL,
	ignoring client side
Message-ID: <27172545.1224712606331.JavaMail.jboss@colo-br-02.atl.jboss.com>

JIRA ticket: https://jira.jboss.org/jira/browse/JBWS-2369

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

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


From do-not-reply at jboss.com  Wed Oct 22 18:06:24 2008
From: do-not-reply at jboss.com (alllle)
Date: Wed, 22 Oct 2008 18:06:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WS client retrieves WSDL many many
	times, performance proble
Message-ID: <29581649.1224713184103.JavaMail.jboss@colo-br-02.atl.jboss.com>

During my testing, I used smartsniff to check the HTTP requests / responses between my WS Client and the SOAP server. I was surprised to discover that the dynamic WS client would first download the remote WSDL multiple times to create the service object, which I use to get the port object, then for each operation invocation, it would retrieve the WSDL file again, even the same port object is used.

This is a huge performance slow down for dynamic client, as we all know there is lots of overhead to download something via the network. Plus that I suspect that the WSDL file is parsed again and again with each download (or otherwise why downloading it?), which also slows things down a lot.

Even for static generated client code, it would still download the WSDL again if I use the service constructor that takes the WSDL URL and serviceQName. Not much of difference compare with the dynamic client.

I am not sure if the WSDL file is locally available (via file system), the WS client would still load it / parse it multiple times. 


Anyone noticed this? Or have any comments? 

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

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


From do-not-reply at jboss.com  Thu Oct 23 03:56:14 2008
From: do-not-reply at jboss.com (pkorros)
Date: Thu, 23 Oct 2008 03:56:14 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Exception when I try to deploy a web
	service
Message-ID: <11216870.1224748574274.JavaMail.jboss@colo-br-02.atl.jboss.com>

When I try to deploy my web service I get the following error:


  | 10:43:01,536 INFO  [WSDLFilePublisher] WSDL published to: file:/C:/Projects/jboss-4.2.3.GA/server/default/data/wsdl/ROOT.war/SOAPSearchCustomers57095.wsdl
  | 10:43:08,833 ERROR [[SOAPSearchCustomers]] Servlet.service() for servlet SOAPSearchCustomers threw exception
  | javax.xml.ws.WebServiceException: Cannot obtain endpoint for: jboss.ws:context=,endpoint=SOAPSearchCustomers
  | 	at org.jboss.wsf.stack.jbws.EndpointServlet.initEndpoint(EndpointServlet.java:137)
  | 	at org.jboss.wsf.stack.jbws.EndpointServlet.initServiceEndpoint(EndpointServlet.java:93)
  | 	at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:74)
  | 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
  | 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
  | 

any idea on whats wrong? What can I do to debug this?

I am using JBoss 4.2.3 and JBossWS 3.0.3.

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

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


From do-not-reply at jboss.com  Thu Oct 23 04:12:57 2008
From: do-not-reply at jboss.com (kr8m3r_78)
Date: Thu, 23 Oct 2008 04:12:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WebContext annotation and
	contextRoot
Message-ID: <1026106.1224749577569.JavaMail.jboss@colo-br-02.atl.jboss.com>

Did you ever get this problem solved?

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

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


From do-not-reply at jboss.com  Thu Oct 23 04:36:58 2008
From: do-not-reply at jboss.com (kr8m3r_78)
Date: Thu, 23 Oct 2008 04:36:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: If I deploy more than one
	webservice I get
Message-ID: <28947254.1224751018962.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have a problem in that my EJB jar deploys a web service, which uses the @WebContext annotation, but the context root points to the same context root of one defined in my war, both of which are packaged inside an EAR. If I deploy the EAR everything defined in the web.xml inside the war is accessible, but accessing the web service using the same context gets a 404 error. 

For example, my webservice:


  | @WebContext(contextRoot = "/testWeb", urlPattern = "/SupplierAccessPort", authMethod = "BASIC", transportGuarantee = "NONE", secureWSDLAccess = false)
  | 

In my jboss-web.xml (inside the war):


  |  <jboss-web>  
  |   <security-domain>java:/jaas/aipDBCheck</security-domain>  
  |   <context-root>/testWeb</context-root>
  |  </jboss-web>
  | 

http://localhost:8080/testWeb/index.htm is found (as it is inside my war)
http://localhost:8080/testWeb/SupplierAccessPort gets a 404.


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

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


From do-not-reply at jboss.com  Thu Oct 23 04:53:18 2008
From: do-not-reply at jboss.com (kr8m3r_78)
Date: Thu, 23 Oct 2008 04:53:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WebContext annotation and
	contextRoot
Message-ID: <20281471.1224751998330.JavaMail.jboss@colo-br-02.atl.jboss.com>

I seem to have the same problem:

I have a problem in that my EJB jar deploys a web service, which uses the @WebContext annotation, but the context root points to the same context root of one defined in my war, both of which are packaged inside an EAR. If I deploy the EAR everything defined in the web.xml inside the war is accessible, but accessing the web service using the same context gets a 404 error.

For example, my webservice:

Code:

  | @WebContext(contextRoot = "/testWeb", urlPattern = "/SupplierAccessPort", authMethod = "BASIC", transportGuarantee = "NONE", secureWSDLAccess = false)
  | 

In my jboss-web.xml (inside the war):


  |  <jboss-web>  
  |   <security-domain>java:/jaas/aipDBCheck</security-domain>  
  |   <context-root>/testWeb</context-root>
  |  </jboss-web>
  | 

http://localhost:8080/testWeb/index.htm is found (as it is inside my war)
http://localhost:8080/testWeb/SupplierAccessPort gets a 404. 

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

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


From do-not-reply at jboss.com  Thu Oct 23 10:30:46 2008
From: do-not-reply at jboss.com (jeremyrd)
Date: Thu, 23 Oct 2008 10:30:46 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: TestSuite in Eclipse problem
Message-ID: <13069882.1224772246265.JavaMail.jboss@colo-br-02.atl.jboss.com>

I had the same problem - obligatory blog entry here : http://arrogantprogrammer.blogspot.com/2008/10/jbossws.html.

I haven't figured out why this is happening; however, the problem disappeared when I imported the project into a fresh Eclipse install.  I was running Eclipse 3.3 with JBossTools installed when the error was occurring.

I'll file a Jira issue if I can reproduce.

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

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


From do-not-reply at jboss.com  Thu Oct 23 10:37:46 2008
From: do-not-reply at jboss.com (adinn)
Date: Thu, 23 Oct 2008 10:37:46 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: NPE deploying web services in
	service archive in CR1 rel
Message-ID: <16019733.1224772666880.JavaMail.jboss@colo-br-02.atl.jboss.com>

I retried this with AS 5.0.0.CR2 and JBossWS 3.0.4 and it appears to work . . . most of the time.

The NPE is no longer generated if I restart with the war file still deployed However, two other things go wrong:

i)  I get the following warnings during booting as end points are published


  | . . .
  | 15:22:52,332 INFO  [DefaultEndpointRegistry] register: jboss.ws:context=ws-c11,endpoint=Activation Service
  | 15:22:52,335 INFO  [DefaultEndpointRegistry] register: jboss.ws:context=ws-c11,endpoint=Registration Service
  | 15:22:52,354 WARN  [AbstractServerConfig] Unable to calculate 'WebServicePort', using default '8080'
  | 15:22:52,358 WARN  [AbstractServerConfig] Unable to calculate 'WebServicePort', using default '8080'
  | . . .
  | 

A block of messages is generated for each war file ans there is one message ffor each end point.

ii) sometimes the server hangs during deployment of the end points and never reaches start up (well,I waited 5 minutes).


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

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


From do-not-reply at jboss.com  Thu Oct 23 10:56:20 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Thu, 23 Oct 2008 10:56:20 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Exception when I try to deploy a
	web service
Message-ID: <14876145.1224773780146.JavaMail.jboss@colo-br-02.atl.jboss.com>

Based on the MBean name in the error message, you did not provide a context. I am assuming that you are creating an EJB web service (POJO web services always(?) have a context). Did you provide an @WebContext annotation?

If this does not help, please post the web service code and any related configuration files.

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

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


From do-not-reply at jboss.com  Thu Oct 23 11:09:34 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Thu, 23 Oct 2008 11:09:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WebContext annotation and
	contextRoot
Message-ID: <31673714.1224774574721.JavaMail.jboss@colo-br-02.atl.jboss.com>

Here is my guess: 

Web apps and web services are handled by two entirely different components. Once the decision is made to pass the incoming message to the web app component (based on the context), that component will not afterwards pass the message on to the web services component.

I have never tried to place information about a web app and web service into the same web.xml file, and bundle them together into the same WAR file. It that works, perhaps that would suffice for what you want to do.

 

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

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


From do-not-reply at jboss.com  Thu Oct 23 11:12:39 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Thu, 23 Oct 2008 11:12:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: If I deploy more than one
	webservice I get
Message-ID: <27842183.1224774759722.JavaMail.jboss@colo-br-02.atl.jboss.com>

kr8m3r_78, please stop spamming a multitude of topics with the same question!!! You need ask only once, asking multiple times simply irritates the other readers of the forums.

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

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


From do-not-reply at jboss.com  Thu Oct 23 11:14:57 2008
From: do-not-reply at jboss.com (pkorros)
Date: Thu, 23 Oct 2008 11:14:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Exception when I try to deploy a
	web service
Message-ID: <24465365.1224774897506.JavaMail.jboss@colo-br-02.atl.jboss.com>

I can' find any @WebContext annotation available to annotate my web service.

What is the fully qualified name of the annotation @WebContext annotation?

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

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


From do-not-reply at jboss.com  Thu Oct 23 11:26:07 2008
From: do-not-reply at jboss.com (QPool.Char)
Date: Thu, 23 Oct 2008 11:26:07 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - ERROR without exception: JAX-WS context
	listener initializin
Message-ID: <683136.1224775567097.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello dear forum,

i follow the detailed descriptions to make a simple WebService with JDK 6 and JBoss 4.2.3 from this website: http://blog.vinodsingh.com/2008/09/jax-ws-web-service-and-jboss.html?showComment=1224766980000#c2556965947904510784

When i deploy the .war to JBoss, i get the following Errors:
  | 17:07:14,312 INFO  [TomcatDeployer] deploy, ctxPath=/HelloWorld, warUrl=.../tmp/deploy/tmp7738HelloWorld-exp.war/
  | 17:07:14,781 ERROR [STDERR] 23.10.2008 17:07:14 com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
  | INFO: WSSERVLET12: JAX-WS context listener initializing
  | 17:07:16,109 ERROR [STDERR] 23.10.2008 17:07:16 com.sun.xml.ws.transport.http.servlet.WSServletDelegate <init>
  | INFO: WSSERVLET14: JAX-WS servlet initializing
  | 17:07:17,000 INFO  [WSDLFilePublisher] WSDL published to: file:/C:/JavaStuff/jboss-4.2.3.GA/server/default/data/wsdl/HelloWorld.war/HelloWorldService7739.wsdl

Generating some client stubs worked, but trying to invoke a client, i get the following exception:

  | 17:14:38,093 ERROR [[HelloWorldWebService]] Servlet.service() for servlet HelloWorldWebService threw exception
  | java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl cannot be cast to org.jboss.ws.core.soap.SOAPMessageImpl
  | 	at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:245)

I have also tried JBoss 5.0 and the JBossWS-patches to jbossws 3.0.4.

I believe that there are some class-loading problems with Java 6, and filled the ${JBOSS_HOME}/lib/endorsed directory with jars mentioned on this page: http://thesmallpotato.blogspot.com/2007/06/jdk-16-jboss-420-ejb3-web-service-axis2.html ,but it did not help. I then added jboss-jaxws.jar and jboss-jaxws-ext.jar, but without success again...

So i thought maybe the error comes from my web.xml, which i have a question for:

  | <servlet>
  |     	<servlet-name>HelloWorldWebService</servlet-name>
  |     	<servlet-class>com.sun.xml.ws.transport.http.servlet.WSServlet</servlet-class>
  |     	<!-- servlet-class>biz.accelsis.helloworld.HelloWorldWS</servlet-class> -->
  | </servlet>
  | 
Can you tell me which value to put into the <servlet-class> tag?

Thx in advance for all the help, i am really stucked here.



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

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


From do-not-reply at jboss.com  Thu Oct 23 11:54:09 2008
From: do-not-reply at jboss.com (adinn)
Date: Thu, 23 Oct 2008 11:54:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: NPE deploying web services in
	service archive in CR1 rel
Message-ID: <22739454.1224777249395.JavaMail.jboss@colo-br-02.atl.jboss.com>

I had a little further look into this and found that the errors occur as follows:
During deployment of the endpoints declared in my wars a call is made to AbstractServerConfig.getConnectorPort(). This fetches the WS Server MBean and tries to lookup objects of type "jboss.web:type=Connector,*". At the point where the lookup fails the jboss.web MBean has only one entry for the WebServer.

In the run that I managed to debug the type=Connector entries were added at a later point. So, some of the subsequent calls to getConnectorPort() succeeded and also the AS bootstrap did not hang. I was unable to debug a case where the bootstrap did hang.

So, although this is a lot better than 3.0.3 it looks like there is still a race where the deployers may try to start the endpoints before everything they need is in place.

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

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


From do-not-reply at jboss.com  Thu Oct 23 12:23:50 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Thu, 23 Oct 2008 12:23:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Exception when I try to deploy a
	web service
Message-ID: <30923359.1224779030924.JavaMail.jboss@colo-br-02.atl.jboss.com>

org.jboss.wsf.spi.annotation.WebContext

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

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


From do-not-reply at jboss.com  Thu Oct 23 12:28:47 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Thu, 23 Oct 2008 12:28:47 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: ERROR without exception: JAX-WS
	context listener initial
Message-ID: <29272962.1224779327579.JavaMail.jboss@colo-br-02.atl.jboss.com>

There are two different 4.2.3 downloads, one for JDK 5 the other for JDK 6. Did you get the one for JDK 6? If so, then you do not need to mess around with endorsed directories because it is already done.

For the web.xml, is com.sun.xml.ws.transport.http.servlet.WSServlet your class that provides the web service? Or is it biz.accelsis.helloworld.HelloWorldWS? The servlet-class should be the class that implements the web service.

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

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


From do-not-reply at jboss.com  Thu Oct 23 17:50:34 2008
From: do-not-reply at jboss.com (kr8m3r_78)
Date: Thu, 23 Oct 2008 17:50:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: If I deploy more than one
	webservice I get
Message-ID: <31650612.1224798634959.JavaMail.jboss@colo-br-02.atl.jboss.com>

This isn't spam, and there wasnt a "multitude" of posts. I posted the same question to two different threads. I didnt realize they get pushed to the top of the list. I was expecting my reply to be flagged to the person who posted the original message. 

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

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


From do-not-reply at jboss.com  Fri Oct 24 02:45:33 2008
From: do-not-reply at jboss.com (rishabh2u)
Date: Fri, 24 Oct 2008 02:45:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS 3.0.4 Released
Message-ID: <29167145.1224830733216.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi alessio,
just had a quick question about this defect fixed in 3.0.4. 
https://jira.jboss.org/jira/browse/JBWS-2285

Is this defect about getting a class cast exception when casting a custom handler to the Generic Handler. ???
I am getting this issue in jb 423 and 421

Thanks.

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

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


From do-not-reply at jboss.com  Fri Oct 24 05:15:52 2008
From: do-not-reply at jboss.com (adinn)
Date: Fri, 24 Oct 2008 05:15:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: NPE deploying web services in
	service archive in CR1 rel
Message-ID: <5356276.1224839752454.JavaMail.jboss@colo-br-02.atl.jboss.com>

I managed to debug this a little further and have identified why the startup code is hanging -- it is because of something my code is doing (I'll come to that in a second). I still don't know why the WebService port is being looked up before it is defined so there is still an issue there.

The hang is because I am trying to coordinate initialization of my war apps and the XTS service which deploys them. The problem I face is that the listeners are run in an arbitrary order but the war apps have initialization dependencies. So, I make the war listeners register callbacks in a fixed sequence. If any of them finds that the sequence is complete after regsitering then it runs all the callbacks.

This was ok until I added transaction recovery which requires initialization in the XTS service start() routine before the wars can be initialized. I had assumed  that the XTS service start() call happened in parallel with the war listener calls so I added a latch in the callback runner which was released by the XTS service start(). If the runner gets there first it does a wait() and the start() call wakes it with a notfiy(). It appears that the start() and listener call actually run in the same thread in arbitrary order and up until now the start() call has always run first. Now, the sar start() call occasionally gets run last, resulting in a deadlock. I guess I need to make my war apps depend on the XTS service bean.


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

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


From do-not-reply at jboss.com  Fri Oct 24 05:39:30 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Fri, 24 Oct 2008 05:39:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: NPE deploying web services in
	service archive in CR1 rel
Message-ID: <19834448.1224841170395.JavaMail.jboss@colo-br-02.atl.jboss.com>

We know about all these problems adinn.

It should be fixed with next JBossWS release.
You can register for events here: JBWS-2332 and see the progress on this issue.

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

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


From do-not-reply at jboss.com  Fri Oct 24 06:53:52 2008
From: do-not-reply at jboss.com (agori)
Date: Fri, 24 Oct 2008 06:53:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Sharing HttpSession between
	multiple webservices
Message-ID: <14211334.1224845632427.JavaMail.jboss@colo-br-02.atl.jboss.com>

I found that this solution works:


  | MyService client1 = (MyService) service.getPort(...);
  | BindingProvider prov1 = (BindingProvider) client1;
  | Map<String, Object> request = prov1.getRequestContext();
  | request.put(BindingProvider.SESSION_MAINTAIN_PROPERTY, true);
  | client1.login("agori", "sfsfaf");
  | 
  | Object cookieJar = request.get("com.sun.xml.internal.ws.client.http.CookieJar");
  | 
  | MyService2 client2 = service.getPort('...');
  | BindingProvider prov2 = (BindingProvider) client2;
  | request = prov2.getRequestContext();
  | request.put(BindingProvider.SESSION_MAINTAIN_PROPERTY, true);
  | request.put("com.sun.xml.internal.ws.client.http.CookieJar", cookieJar);
  | 
  | client2.myMethod();
  | 
  | 

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

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


From do-not-reply at jboss.com  Fri Oct 24 11:37:08 2008
From: do-not-reply at jboss.com (jeckles933)
Date: Fri, 24 Oct 2008 11:37:08 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Full control of client and server
	certificates with a JB
Message-ID: <7119423.1224862628379.JavaMail.jboss@colo-br-02.atl.jboss.com>

Trying to do the same thing.  I can't understand what other people are doing to get around this problem.  We have multiple keystores, so i have to override the default behavior for the SSLContext...
This is what i need to do, but i can't figure out how/when to call this to set the socket factory.  




  | KeyStore ts = KeyStore.getInstance("JKS");
  | 		ts.load(new FileInputStream(trustStoreFullName), trustStorePassword.toCharArray());
  | 		TrustManager[] tm;
  | 		TrustManagerFactory tmf = TrustManagerFactory.getInstance(TrustManagerFactory.getDefaultAlgorithm());
  | 		tmf.init(ts);
  | 		tm = tmf.getTrustManagers();
  | 
  | 		SSLContext sslContext = SSLContext.getInstance("SSL");
  | 		sslContext.init(kmf.getKeyManagers(), tm, null);
  | 
  | 		SSLSocketFactory sslSocketFactory = sslContext.getSocketFactory();
  | 
  | 		HttpsURLConnection urlc = (HttpsURLConnection) url.openConnection();
  | 		urlc.setSSLSocketFactory(sslSocketFactory);
  | 

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

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


From do-not-reply at jboss.com  Fri Oct 24 12:02:58 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 24 Oct 2008 12:02:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS 3.0.4 Released
Message-ID: <14748421.1224864178350.JavaMail.jboss@colo-br-02.atl.jboss.com>

No, that's another issue I think. Please open another thread on this so that we can analyze it.

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

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


From do-not-reply at jboss.com  Fri Oct 24 12:09:36 2008
From: do-not-reply at jboss.com (jeckles933)
Date: Fri, 24 Oct 2008 12:09:36 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: SSL & Authorization
Message-ID: <33105190.1224864576078.JavaMail.jboss@colo-br-02.atl.jboss.com>

you need to create a truststore.  the exception is telling you that the server you are connecting to probably self gernerated it's certificate.  So you can setup a truststore, containing the public keys for anyone you trust.

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

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


From do-not-reply at jboss.com  Fri Oct 24 12:36:48 2008
From: do-not-reply at jboss.com (martin.capote)
Date: Fri, 24 Oct 2008 12:36:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: @WebService - Invalid byte 2 of
	2-byte UTF-8 sequence
Message-ID: <10077522.1224866208993.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi. I have the same problem. Do you found the solution? Thanks

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

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


From do-not-reply at jboss.com  Fri Oct 24 17:10:39 2008
From: do-not-reply at jboss.com (yhrn)
Date: Fri, 24 Oct 2008 17:10:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Full control of client and server
	certificates with a JB
Message-ID: <29810823.1224882639381.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi, 
When I posted this JBossWS did not yet support multiple JAX-WS implementations. When this feature came I solved the problem by switching to the  Metro flavor of JBossWS instead and then implement it as described in the initial post of this thread. 

This of course resulted in a set of other problems (which I can't even remember now) but I think they were all caused by bugs in an immature feature and are probably solved by now... 

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

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


From do-not-reply at jboss.com  Sat Oct 25 08:30:16 2008
From: do-not-reply at jboss.com (tomstrummer)
Date: Sat, 25 Oct 2008 08:30:16 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: No Classloaders found for
	ProviderImpl
Message-ID: <15117737.1224937816814.JavaMail.jboss@colo-br-02.atl.jboss.com>

Alessio --

Thanks for getting back to me.  I'm sure I don't have the JBossws JARs in my EAR (that's why it can't find ProviderImpl).  

I'll search my classpath to see where that javax.xml.ws.spi.Provider is being looked up from.  I'm afraid JBossWS-native might still be installed in the server classpath even though I did install jbossws-metro using the Ant build.  

I'll see if I can't track that down.  Is there any way to "query" the classpath for a given resource to find out what JAR it's coming from? :)

Thanks again.

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

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


From do-not-reply at jboss.com  Mon Oct 27 00:11:26 2008
From: do-not-reply at jboss.com (rishabh2u)
Date: Mon, 27 Oct 2008 00:11:26 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: ClassCastException in
	HandlerResolverImpl.addHandler
Message-ID: <5152650.1225080686295.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am getting this problem as well when implementing jaxws on jboss421 and 423. 
As per the java spec the handler class should either implement the javax.xml.ws.handler.LogicalHandler OR javax.xml.ws.handler.SOAPHandler.
 
I have a handler class that does this.
  | 
  | package handlertest.server;
  | 
  | import java.util.Set;
  | 
  | import javax.xml.namespace.QName;
  | import javax.xml.ws.handler.MessageContext;
  | import javax.xml.ws.handler.soap.SOAPHandler;
  | import javax.xml.ws.handler.soap.SOAPMessageContext;
  | 
  | public class ServerSOAPHandler implements SOAPHandler<SOAPMessageContext> {
  | 	private final String HANDLERNAME = "ServerSOAPHandler";
  | 
  | 	public ServerSOAPHandler() {
  | 		super();
  | 		System.out.println(HANDLERNAME + " ServerSOAPHandler():");
  | 	}
  | 
  | 	public Set<QName> getHeaders() {
  | 		System.out.println(HANDLERNAME + " getHeaders():");
  | 		return null;
  | 	}
  | 
  | 	public boolean handleFault(SOAPMessageContext arg0) {
  | 		System.out.println(HANDLERNAME + " handleFault():");
  | 		return false;
  | 	}
  | 
  | 	public boolean handleMessage(SOAPMessageContext arg0) {
  | 		System.out.println(HANDLERNAME + " handleMessage():");
  | 		return false;
  | 	}
  | 
  | 	public void close(MessageContext arg0) {
  | 		System.out.println(HANDLERNAME + " close():");
  | 	}
  | }
  | 

I get the same exception when this handler is loaded. This is the stacktrace.


  | java.lang.ClassCastException: handlertest.server.ServerSOAPHandler
  |         at org.jboss.ws.core.jaxws.handler.HandlerResolverImpl.addHandler(HandlerResolverImpl.java:148)
  |         at org.jboss.ws.core.jaxws.handler.HandlerResolverImpl.initHandlerChain(HandlerResolverImpl.java:134)
  |         at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:80)
  |         at org.jboss.ws.core.server.AbstractServiceEndpointInvoker.callRequestHandlerChain(AbstractServiceEndpointInvok
  |         at org.jboss.ws.core.server.AbstractServiceEndpointInvoker.invoke(AbstractServiceEndpointInvoker.java:162)
  |         at org.jboss.ws.core.server.ServiceEndpoint.processRequest(ServiceEndpoint.java:212)
  |         at org.jboss.ws.core.server.ServiceEndpointManager.processRequest(ServiceEndpointManager.java:448)
  |         at org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPost(AbstractServiceEndpointServlet.java:114)
  |         at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
  |         at org.jboss.ws.core.server.AbstractServiceEndpointServlet.service(AbstractServiceEndpointServlet.java:75)
  |         at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
  |         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
  |         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
  |         at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
  |         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
  |         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
  | 

The proposed solution of using Generic handler from Jboss works but this is not a proper solution. To be able to work with JAXws 2 spec I need to implement the javax.xml.ws.handler.LogicalHandler. Can you please suggest what can i do here ???

Also below are some links to jaxws 2 tutorials
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/twbs_jaxwshandler.html

http://java.sun.com/mailers/techtips/enterprise/2006/TechTips_June06.html#1
http://blogs.sun.com/sdimilla/entry/implementing_handlers_using_jaxws_2

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

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


From do-not-reply at jboss.com  Mon Oct 27 04:34:43 2008
From: do-not-reply at jboss.com (Christy)
Date: Mon, 27 Oct 2008 04:34:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-BPEL with JAX-WS services
Message-ID: <28746530.1225096483381.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,
I have the same question.


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

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


From do-not-reply at jboss.com  Mon Oct 27 06:08:11 2008
From: do-not-reply at jboss.com (Modiehi)
Date: Mon, 27 Oct 2008 06:08:11 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBoss Seam and web services
Message-ID: <18121210.1225102091460.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi, I'm new to seam and would like to invoke the web service using classes generate by wsconsume to invoke the webservices in eclipse. I'm using JBoss 4.2.2 and jboss-seam-2.0.2.SP1. I tried using s stateless session bean but I get a nullpointer exception.
Assistance will be higly appreciated.
Best Regards

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

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


From do-not-reply at jboss.com  Mon Oct 27 11:36:03 2008
From: do-not-reply at jboss.com (kevintaute)
Date: Mon, 27 Oct 2008 11:36:03 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Incomplete Deployment Listing Error
	in JBoss 4.0.4
Message-ID: <16919808.1225121763903.JavaMail.jboss@colo-br-02.atl.jboss.com>

The Jasper Reports API requires access to the text file definition (jrxml).  In order to deploy under jboss, you will need to include the jrxml file like any other text file being deployed (ie your html, jsp, etc), then use something like 

String dirName = getServletContext().getRealPath("/");

to get the root directory of your application.  If you chose to place them in a subfolder (such as reports) you would need to add that to the string above.

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

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


From do-not-reply at jboss.com  Mon Oct 27 11:37:37 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 27 Oct 2008 11:37:37 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: No Classloaders found for
	ProviderImpl
Message-ID: <13048582.1225121857280.JavaMail.jboss@colo-br-02.atl.jboss.com>

tomstrummer wrote :  Is there any way to "query" the classpath for a given resource to find out what JAR it's coming from?

I use a tool name JarFinder from http://www.isocra.com/2006/02/jarfinder/. It has saved my sanity countless times.

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

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


From do-not-reply at jboss.com  Mon Oct 27 11:39:18 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 27 Oct 2008 11:39:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: No Classloaders found for
	ProviderImpl
Message-ID: <26129222.1225121958244.JavaMail.jboss@colo-br-02.atl.jboss.com>

I read your post again and think that maybe what you are looking for is the  "-verbose:class" option to the JVM. This causes the JVM to print out each class file loaded and the location of the jar file from which the class was obtained.

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

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


From do-not-reply at jboss.com  Mon Oct 27 11:40:29 2008
From: do-not-reply at jboss.com (tomstrummer)
Date: Mon, 27 Oct 2008 11:40:29 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: No Classloaders found for
	ProviderImpl
Message-ID: <9010338.1225122029874.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thanks Peter, I'll try that.

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

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


From do-not-reply at jboss.com  Mon Oct 27 18:32:15 2008
From: do-not-reply at jboss.com (pxstein)
Date: Mon, 27 Oct 2008 18:32:15 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Which wconsume artefacts are for the
	test client?
Message-ID: <19616525.1225146735341.JavaMail.jboss@colo-br-02.atl.jboss.com>

I created a sample web service with the WSDL shown at the bottom of this post.

wsconsume now creates all relevant artefacts. In detail:

- Greet.java
- GreetResponse.java
- ObjectFactory.java
- package-info.java
- TestWs.java
- TestWsService.java

Which of these files (resp. the classes) should be put into the client *.jar file 
(which in turn call the web service later) ?

Are really all *.classes necessary FOR THE CLIENT?





<definitions name="TestWsService" targetNamespace="http://dhanago.test.com/" 
xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" 
xmlns:tns="http://dhanago.test.com/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                                                                                                                                                                                                                                                    
<xs:schema targetNamespace="http://dhanago.test.com/" version="1.0" 
xmlns:tns="http://dhanago.test.com/" xmlns:xs="http://www.w3.org/2001/XMLSchema">                                                                                                      
<xs:element name="greet" type="tns:greet" />                                                                                                                                                                                                               
<xs:element name="greetResponse" type="tns:greetResponse" />                                                                                                                                                                                               
<xs:complexType name="greet">                                                                                                                                                                                                                              
<xs:sequence>                                                                                                                                                                                                                                              
<xs:element minOccurs="0" name="name" type="xs:string" />                                                                                                                                                                                                  
</xs:sequence>                                                                                                                                                                                                                                             
</xs:complexType>                                                                                                                                                                                                                                          
<xs:complexType name="greetResponse">                                                                                                                                                                                                                      
<xs:sequence>                                                                                                                                                                                                                                              
<xs:element minOccurs="0" name="return" type="xs:string" />                                                                                                                                                                                                
</xs:sequence>                                                                                                                                                                                                                                             
</xs:complexType>                                                                                                                                                                                                                                          
</xs:schema>                                                                                                                                                                                                                                               
                                                                                                                                                                                                                                                   
                                                                                                                                                                                                                      
                                                                                                                                                                                                  
                                                                                                                                                                                                                                                 
                                                                                                                                                                                                                              
                                                                                                                                                                                                                  
                                                                                                                                                                                                                                                 
                                                                                                                                                                                                                                   
                                                                                                                                                                                                            
                                                                                                                                                                                                                       
                                                                                                                                                                                                              
                                                                                                                                                                                                                                               
                                                                                                                                                                                                                                                
                                                                                                                                                                                                           
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />                                                                                                                                                                         
                                                                                                                                                                                                                                   
<soap:operation soapAction="" />                                                                                                                                                                                                                           
                                                                                                                                                                                                                                                    
<soap:body use="literal" />                                                                                                                                                                                                                                
                                                                                                                                                                                                                                                   
                                                                                                                                                                                                                                                   
<soap:body use="literal" />                                                                                                                                                                                                                                
                                                                                                                                                                                                                                                  
                                                                                                                                                                                                                                               
                                                                                                                                                                                                                                                 
                                                                                                                                                                                                                             
                                                                                                                                                                                                       
<soap:address location="http://127.0.0.1:8080/testWsProject/TestWs" />                                                                                                                                                                                        
                                                                                                                                                                                                                                                    
                                                                                                                                                                                                                                                 
                            







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

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


From do-not-reply at jboss.com  Mon Oct 27 18:55:52 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 27 Oct 2008 18:55:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Which wconsume artefacts are for
	the test client?
Message-ID: <3264222.1225148152648.JavaMail.jboss@colo-br-02.atl.jboss.com>

All of the generated classes should be placed into your client's JAR file.

By the way, when posting XML source, enclose your XML text in UBBCode "code" tags  - you can do this by selecting the XML text and clicking the Code button above the editor window. Also, click the Preview button to ensure that the formatting is correct and the XML text shows up before posting

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

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


From do-not-reply at jboss.com  Tue Oct 28 04:04:51 2008
From: do-not-reply at jboss.com (jopersson)
Date: Tue, 28 Oct 2008 04:04:51 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - https jboss ws client
Message-ID: <109700.1225181091339.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

Trying to use https endpoint address in client proxy (Jboss-4.2.3.GA) from java swing client with endorsed liraries and WS-Security UsernameToken enabled.
Solution goes thru a Portwise security server like:
swingclient->https->portwise->http->jboss-in-dmz.

Code from Swing client:

  |     System.setProperty("javax.net.ssl.keyStore", "C:/k.jks");
  |     System.setProperty("javax.net.ssl.trustStore", "C:/Program/Java/jdk1.6.0_06/jre/lib/security/cacerts");
  |     System.setProperty("javax.net.ssl.keyStorePassword", "123456");
  |     System.setProperty("javax.net.ssl.trustStorePassword", "changeit");
  |     System.setProperty("javax.net.ssl.keyStoreType", "jks");
  |     System.setProperty("javax.net.ssl.trustStoreType", "jks");
  |     System.setProperty("org.jboss.security.ignoreHttpsHost","true");
  | 
  |            String wsdlURLFileName = Resources.getProperty("wsdlURL");
  |            URL wsdlURL = Resources.findFileAsURL(wsdlURLFileName);
  |            String namespaceURI = Resources.getProperty("namespaceURI");
  |            String localpart = Resources.getProperty("localpart");
  |            service = new KService(wsdlURL, new QName(namespaceURI, localpart));
  |        
  |            port = service.getKPort();  
  |         ((StubExt)port).setConfigName("Standard WSSecurity Client");        
  |         
  |         Map<String, Object> reqContext = ((BindingProvider) port).getRequestContext();
  |         
  |         reqContext.put(StubExt.PROPERTY_AUTH_TYPE, StubExt.PROPERTY_AUTH_TYPE_WSSE);
  |         
  |        String kEnpointAddress = "https://portwise.k.se/KService";
  |         ((BindingProvider) port).getRequestContext().put(
  |                 BindingProvider.ENDPOINT_ADDRESS_PROPERTY, 
  |                         kEnpointAddress);       
  | 
When invoking web service methods the call does not bring a valid certificate. Portwise says 'not a valid certificate' and the call does not reach to jboss in dmz.

Did some debugging on Jboss Remoting code and can see truststore and keystore being loaded correctly. Monitoring TLS protocol from client to portwise server seems ok with handshake.

Also trying to access Jboss in DMZ with plain Java code:

  | try {
  |     System.setProperty("javax.net.ssl.keyStore", "C:/k.jks");
  |     System.setProperty("javax.net.ssl.trustStore", "C:/Program/Java/jdk1.6.0_06/jre/lib/security/cacerts");
  |     System.setProperty("javax.net.ssl.keyStorePassword", "123456");
  |     System.setProperty("javax.net.ssl.trustStorePassword", "changeit");
  |     System.setProperty("javax.net.ssl.keyStoreType", "jks");
  |     System.setProperty("javax.net.ssl.trustStoreType", "jks");
  |     
  |     String  keyStorePath   = "C:/k.jks";
  |             String  trustStorePath = "C:/Program/Java/jdk1.6.0_06/jre/lib/security/cacerts";
  |             String  password       = "123456";
  |     
  |             String host = "https://portwise.k.se/KService?wsdl";
  |             KeyStore ks = KeyStore.getInstance("JKS");            
  |             FileInputStream keyStoreInput = new FileInputStream(keyStorePath);
  |             try {
  |                 ks.load(keyStoreInput, password.toCharArray());
  |             } finally { keyStoreInput.close(); }  
  |             
  |             KeyStore ts = KeyStore.getInstance("JKS");
  |             FileInputStream trustStoreInput = new FileInputStream(trustStorePath);
  |             try {
  |                 ts.load(trustStoreInput, "changeit".toCharArray());
  |             } finally { trustStoreInput.close(); } 
  |                
  |             TrustManagerFactory trustManagerFactory =
  |             TrustManagerFactory.getInstance(TrustManagerFactory.getDefaultAlgorithm());
  |             KeyManagerFactory keyManagerFactory =
  |             KeyManagerFactory.getInstance(KeyManagerFactory.getDefaultAlgorithm());
  |             trustManagerFactory.init(ts);
  |             keyManagerFactory.init(ks,password.toCharArray());
  |             
  |             SSLContext sslContext = SSLContext.getInstance("TLS");            
  |             sslContext.init(keyManagerFactory.getKeyManagers(), 
  |                     trustManagerFactory.getTrustManagers(), null);            
  |             SSLContext.setDefault(sslContext);
  | 
  |            HttpsURLConnection.setDefaultSSLSocketFactory(sslContext.getSocketFactory());
  |             HttpsURLConnection.setDefaultHostnameVerifier(new HostnameVerifier(){
  |                 public boolean verify(String arg0, SSLSession arg1) {
  |                     return true;
  |                 }
  |             });
  |             javax.net.ssl.HttpsURLConnection connection = 
  |                     (javax.net.ssl.HttpsURLConnection)url.openConnection();
  |             connection.setDoOutput(true);
  |             connection.setDoInput(true);
  |             connection.connect();
  |                     
  |             BufferedReader in = new BufferedReader(new InputStreamReader(
  |                     connection.getInputStream()));
  |             int c;
  |             while ((c = in.read()) != -1) {
  |                 System.out.write(c);
  |             }
  |             in.close();
  |         } catch (Exception ex) {
  |             ex.printStackTrace();
  |             return false;
  |         }
  | 
This code retrieve wsdl OK from jboss in DMZ thru Portwise.

Any ideas ?

tia
johan

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

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


From do-not-reply at jboss.com  Tue Oct 28 06:40:12 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Tue, 28 Oct 2008 06:40:12 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Client call fails using JBossWS
Message-ID: <12559109.1225190412796.JavaMail.jboss@colo-br-02.atl.jboss.com>

You can use the jaxws-config deployment descriptor and set the chunksize to 0, see the standard-jaxws-client-config.xml for instance:


  |   <client-config>
  |     <config-name>Standard Client</config-name>
  |     <feature>http://org.jboss.ws/dispatch/validate</feature>
  |     <property>
  |       <property-name>http://org.jboss.ws/http#chunksize</property-name>
  |       <property-value>2048</property-value>
  |     </property>
  |   </client-config>
  | 

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

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


From do-not-reply at jboss.com  Tue Oct 28 06:42:49 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Tue, 28 Oct 2008 06:42:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Client call fails using JBossWS
Message-ID: <20466836.1225190569070.JavaMail.jboss@colo-br-02.atl.jboss.com>

Or simply use the already provided HTTP 1.0 Client configuration:


  | <client-config>
  |     <config-name>HTTP 1.0 Client</config-name>
  |     <feature>http://org.jboss.ws/dispatch/validate</feature>
  |   </client-config>
  | 

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

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


From do-not-reply at jboss.com  Tue Oct 28 10:44:54 2008
From: do-not-reply at jboss.com (tomstrummer)
Date: Tue, 28 Oct 2008 10:44:54 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: No Classloaders found for
	ProviderImpl
Message-ID: <19375328.1225205094344.JavaMail.jboss@colo-br-02.atl.jboss.com>

That definitely helped me find my problem.  Apparently the JBossWS-native libs were still in jboss-4-2-3.GA/lib/endorsed.  I removed all of the jaxws_.jars from that directory and it got me a little futher at least.  

Then I battled my way through the forests of XML API versioning until I came to face a new beast when invoking the WS client:


  | com.sun.xml.ws.api.client.ServiceInterceptorFactory: Provider com.sun.xml.ws.policy.jaxws.client.PolicyServiceInterceptorFactory is specified in jar:file:/home/tnichols/dev/sandbox/jboss-4.2.3.GA-metro/server/default/deploy/jbossws.sar/jbossws-metro-wsit-rt.jar!/META-INF/services/com.sun.xml.ws.api.client.ServiceInterceptorFactorybut could not be instantiated: java.lang.ClassCastException (com.sun.xml.ws.util.ServiceConfigurationError)
  |   com.sun.xml.ws.util.ServiceFinder:233 (null)
  | java.lang.ClassCastException
  |         at java.lang.Class.cast(Class.java:2990)
  |         at com.sun.xml.ws.util.ServiceFinder$LazyIterator.next(ServiceFinder.java:374)
  |         at com.sun.xml.ws.api.client.ServiceInterceptorFactory.load(ServiceInterceptorFactory.java:80)
  |         at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:202)
  |         at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:175)
  |         at com.sun.xml.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:104)
  |         at javax.xml.ws.Service.<init>(Service.java:56)
  |         at com.pjm.emkt.emkt.xml.wsdl.MarketQueryService.<init>(MarketQueryService.java:46)
  | 

I'm using the jbossws-metro v3.0.4 (installed on the server) along with jaxws-api-2.1 and jaxws-rt-2.1.4 from Maven in my EAR classpath.

Thanks again for the help.

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

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


From do-not-reply at jboss.com  Tue Oct 28 11:07:34 2008
From: do-not-reply at jboss.com (tomstrummer)
Date: Tue, 28 Oct 2008 11:07:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Client call fails using JBossWS
Message-ID: <11121451.1225206454704.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thanks Alessio.  

I found this documentation which I think you're referring to:
http://jbossws.jboss.org/mediawiki/index.php?title=JAX-WS_Client_Configuration

So, can I define my own jaxws-client-config.xml that will by default be used by my WS client?  Or do I have to call the service.getPort... setConfigName call?

Thanks.

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

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


From do-not-reply at jboss.com  Tue Oct 28 12:19:32 2008
From: do-not-reply at jboss.com (tomstrummer)
Date: Tue, 28 Oct 2008 12:19:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: No Classloaders found for
	ProviderImpl
Message-ID: <14761621.1225210772746.JavaMail.jboss@colo-br-02.atl.jboss.com>

Ooh!  I changed the JAX-WS and JAXB JARs to "provided" dependencies and it looks like it's working now.  Yipee!

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

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


From do-not-reply at jboss.com  Tue Oct 28 15:47:47 2008
From: do-not-reply at jboss.com (pxstein)
Date: Tue, 28 Oct 2008 15:47:47 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - How to pass a web service client
	*.class (not jar) to wsrunc
Message-ID: <16201459.1225223267868.JavaMail.jboss@colo-br-02.atl.jboss.com>

I created a JBoss web service client and all the *.class files are located in a sub-directory

D:\mywork\test\aaa\bbb\ccc\*.class

where D:\mywork\test\aaa\bbb\ccc\mymain.class is the class with the main() procedure
and all classes are part of the package aaa.bbb.ccc

So alltogether there is NO *.jar file for the client.

How can I pass mymain.class to wsrunclient and let it run?

D:\mywork\test>D:\JBoss\bin\wsrunclient.bat aaa\bbb\ccc\mymain

does not work because of the error: Exception in thread "main" java.lang.NoClassDefFoundError: mymain

How else can I call the client?

Peter

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

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


From do-not-reply at jboss.com  Tue Oct 28 15:53:09 2008
From: do-not-reply at jboss.com (johndubchak)
Date: Tue, 28 Oct 2008 15:53:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBossWS-3.0.4 Spring version?
Message-ID: <7188434.1225223590015.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

Is there a document included with the distribution that lists what versions of the dependencies have been used to create this binary?

Specifically, what version of both CXF and Spring are included as part of the CXF bundle?

Thanks,
John

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

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


From do-not-reply at jboss.com  Tue Oct 28 16:05:58 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 28 Oct 2008 16:05:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: How to pass a web service client
	*.class (not jar) to ws
Message-ID: <10906067.1225224358961.JavaMail.jboss@colo-br-02.atl.jboss.com>

Try:

D:\JBoss\bin\wsrunclient.bat -classpath . aaa.bbb.ccc.mymain

Note the dots and the spaces...

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

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


From do-not-reply at jboss.com  Wed Oct 29 09:58:17 2008
From: do-not-reply at jboss.com (tonioc)
Date: Wed, 29 Oct 2008 09:58:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Design issue: packaging JAX-WS
	artifacts
Message-ID: <15506792.1225288698010.JavaMail.jboss@colo-br-02.atl.jboss.com>

Just thoughts:

If I use web-services I'm supposing that you don't know nothing about the client and viceversa except for the WSDL.

You may be tempted to add behavior to your generated classes, that won't be shown in the WSDL. 

A client that use your jar will have this behaviour added, but for example a .NET client won't know anything about that.

So probably I will just use two different jars, and make  sure that the client is just the WSDL mapped classes.

Hope it helps
tonioc at exeo.com.ar


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

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


From do-not-reply at jboss.com  Wed Oct 29 13:12:29 2008
From: do-not-reply at jboss.com (espinosa_cz)
Date: Wed, 29 Oct 2008 13:12:29 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WS client libraries from Maven
	frustration
Message-ID: <32282302.1225300349053.JavaMail.jboss@colo-br-02.atl.jboss.com>

Can someone reveal set of necessary library set for a standalone web service client? A set of libraries from Maven repository? JBoss Maven repository? 

I decided to use JBoss WS client implementation because there is a possibility that my standalone client will be soon integrated to our enterprise application running on JBoss.

Because all our projects are Maven based, and despite I am not a huge Maven fan, I respect Maven as a de-facto standard for Java project management; I would like to use only libraries provided by Maven repositories. JBoss provides its own Maven repository that sounds promising. But at this point all fun ends. This requirement seems to be impossible to fulfill.

For Eclipse project I use these libraries with success:
<classpathentry kind="var" path="JBOSS_HOME/client/jbossws-spi.jar"/>
  | <classpathentry kind="var" path="JBOSS_HOME/client/jaxb-api.jar" />
  | <classpathentry kind="var" path="JBOSS_HOME/client/jboss-jaxws.jar"/>
  | <classpathentry kind="var" path="JBOSS_HOME/client/jbossws-client.jar"/>
  | <classpathentry kind="var" path="JBOSS_HOME/client/jbossall-client.jar"/>
  | <classpathentry kind="var" path="JBOSS_HOME/client/jboss-saaj.jar"/>
  | <classpathentry kind="var" path="M2_REPO/xerces/xercesImpl/2.7.1/xercesImpl-2.7.1.jar"/>

I got close with Maven by:


  | <dependency>
  | 	<groupId>org.jboss.ws.native</groupId>
  | 	<artifactId>jbossws-native-client</artifactId>
  | 	<version>3.0.4.GA</version>
  | </dependency>
  | 

This add 13MB of dependent libraries to my single Jar application. It is quite a lot for a simple client, isn'????????????????????????????????????????????????????????????????t it? Anyway, at least it had compiled my source but test phase failed with:
java.lang.IllegalStateException: Failed to load javax.xml.ws.spi.Provider: 
  | org.jboss.ws.core.jaxws.spi.ProviderImpl
  | Caused by: java.lang.NoClassDefFoundError: 
  | org/jboss/util/NotImplementedException

I tried several other combinations, with aim to get close to JBoss 4.2.2 GA client libraries as possible (pom.xml):
		 
<dependency>
  | 	<groupId>jboss</groupId>
  | 	<artifactId>jbossws-spi</artifactId>
  | 	<version>1.0.0.GA</version>
  | </dependency>
  | <!-- JBoss 4.2.2/jbossws-spi.jar : Implementation-Version: 
  | jbossws-1.0.0.GA (build=200708171551) -->
  | 		
  | <dependency>
  | 	<groupId>javax.xml.bind</groupId>
  | 	<artifactId>jaxb-api</artifactId>
  | 	<version>2.1</version>
  | </dependency>
  | 		
  | <dependency>
  | 	<groupId>org.jboss</groupId>
  | 	<artifactId>jboss-jaxws</artifactId>
  | 	<version>2.0.1.SP2</version>
  | </dependency>
  | <!-- JBoss 4.2.2/jbossws-jaxws.jar : Implementation-Version: 
  | jbossws-native-2.0.1.SP2 (build=200710210837)  -->
  | 		
  | <dependency>
  | 	<groupId>org.jboss</groupId>
  | 	<artifactId>jbossws-client</artifactId>
  | 	<version>2.0.1.SP2</version>
  | </dependency>
  | <!-- JBoss 4.2.2/jbossws-client.jar: Implementation-Version: 
  | jbossws-native-2.0.1.SP2 (build=200710210837 -->
  | 				
  | <dependency>
  | 	<groupId>jboss</groupId>
  | 	<artifactId>jbossall-client</artifactId>
  | 	<version>4.2.2.GA</version>
  | </dependency>
  | <!-- JBoss 4.2.2/jbossall-client: Implementation-Version: 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139) -->
  | 		
  | <dependency>
  | 	<groupId>jboss.jbossws</groupId>
  | 	<artifactId>jboss-saaj</artifactId>
  | 	<version>2.0.3.GA</version>
  | </dependency>
  | <!-- JBoss 4.2.2/jboss-saaj : Implementation-Version: jbossws-native-2.0.1.SP2 (build=200710210837) -->
  | 		
  | <dependency>
  | 	<groupId>xerces</groupId>
  | 	<artifactId>xercesImpl</artifactId>
  | 	<version>2.7.1</version>
  | </dependency>
  | 
..but I ended with the same error message.
If I add jbossws-common dependency:

  | <!-- added to supply org.jboss.util.NotImplementedException -->
  | <dependency>
  | 	<groupId>org.jboss.ws</groupId>
  | 	<artifactId>jbossws-common</artifactId>
  | 	<version>1.0.0.GA</version>
  | 	<scope>compile</scope>
  | </dependency>
  | <!-- 
  | JBoss 4.2.2/jbossws-common: Implementation-Version: jbossws-native-2.0.1.SP2 (build=200710210837) 
  | But what vesion of jbossws-common? In repository there are versions from 1.0.0.GA to 1.0.7.GA. What version is really in JBoss 4.2.2.GA?? 
  | -->
  | 

I got:
java.lang.NoClassDefFoundError: javax/xml/rpc/encoding/TypeMappingRegistry
Well, you can add new libs for ever; it is hard to figure out which version of which library fits together :(

I use standard Maven repository and JBoss repository http://repository.jboss.org/maven2/. 

Why there is not a copy of JBoss libraries for all released version in the repository? Is it impossible to have something like   http://repository.jboss.com/maven2/org/jboss-4.2.2.GA/client? License issues? Lack of hard-drive space?

Thank you for any suggestions or comments
Espinosa




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

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



From do-not-reply at jboss.com  Wed Oct 29 14:40:05 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Wed, 29 Oct 2008 14:40:05 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS client libraries from Maven
	frustration
Message-ID: <21265015.1225305606086.JavaMail.jboss@colo-br-02.atl.jboss.com>

I would go with just the single dependency on jboss-native-client, but add a 'compile' scope to it. Then the jar is used to compile only. The client JAR file should then include only the client code. 

I would then use the wsrunclient script to run the client, since it (supposedly) includes all JAR files necessary to run a web services client.

Unfortunately, that does not solve the problems you ran into running your unit tests. Nor does it help if you plan to run your client from a machine that does not have JBossAS (unless you plan in shipping wsrunclient and the client directory with your app). But maybe what I mentioned will give you some other ideas to work around the issue.

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

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


From do-not-reply at jboss.com  Wed Oct 29 15:55:24 2008
From: do-not-reply at jboss.com (pxstein)
Date: Wed, 29 Oct 2008 15:55:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - How to generate the actual Client and
	WebService java Implem
Message-ID: <22700599.1225310124621.JavaMail.jboss@colo-br-02.atl.jboss.com>

As well known "wsconsume" creates all the necessary Stubs, interfaces and Wrapper beans
from a given WSDL of a WebService.

However what is NOT created is the skeleton of the final actual WebService Implementation and
the final WebService Client Implementation.

Is there a tool which can generate such a java source code skeleton as well from a WSDL?

Peter

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

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


From do-not-reply at jboss.com  Wed Oct 29 16:02:05 2008
From: do-not-reply at jboss.com (pxstein)
Date: Wed, 29 Oct 2008 16:02:05 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - How to pass whole ValueObjects as
	parameter to a webservice?
Message-ID: <32814752.1225310526181.JavaMail.jboss@colo-br-02.atl.jboss.com>

Nearly all of the web service examples show on how to pass single input parameters as "string" or "int" to a web service.

But what if I want to pass a whole Java class ValueObject like e.g.

public class MyValueObj {
    public String name;
    public int value;
    protected boolean result;  }
    
Is there somewhere an example (client and webservice implementation)
of passing such more complex ValueObjects to a web service?

Peter

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

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


From mike.saavedra at SirsiDynix.com  Wed Oct 29 18:46:44 2008
From: mike.saavedra at SirsiDynix.com (Mike Saavedra)
Date: Wed, 29 Oct 2008 16:46:44 -0600
Subject: [jbossws-users] Jira JBWS-1439 not fixed
Message-ID: <4908E7D4.8010901@sirsidynix.com>

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

From do-not-reply at jboss.com  Thu Oct 30 06:24:52 2008
From: do-not-reply at jboss.com (mignaak)
Date: Thu, 30 Oct 2008 06:24:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - jax-ws soap protocol handler and white
	space.
Message-ID: <30591521.1225362292939.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have an issue with a soap protocol handler that works fine in jbossws 2.0.3.
Since 2.0.4 it has stopped working because it seems every white space character is stripped away from the message by the runtime.

This handler adds a header to the soap envelope and fills this header with lines of text separated with a newline character.

Any hint as to what is happening?

Many thanks

Here is the source code.

public class MefHandlerClient implements SOAPHandler {

    public Set getHeaders() {
        return null;
    }

    public boolean handleMessage(SOAPMessageContext smc) {
        try {
            Boolean outboundProperty = (Boolean) smc.get(MessageContext.MESSAGE_OUTBOUND_PROPERTY);
            if (outboundProperty.booleanValue() == true) {
                SOAPMessage sm = smc.getMessage();
                SOAPPart part = sm.getSOAPPart();
                SOAPEnvelope envelope = part.getEnvelope();
                SOAPHeader sh = envelope.getHeader();
                if (sh == null)
                    sh = envelope.addHeader();
                QName n = new QName(
                        "http://schemas.xmlsoap.org/ws/2002/04/secext",
                        "BinarySecurityToken",
                        "wsse");
                envelope.addNamespaceDeclaration("wsse", "http://schemas.xmlsoap.org/ws/2002/04/secext");
                SOAPHeaderElement she = sh.addHeaderElement(n);
                QName id = new QName("Id");
                she.addAttribute(id, "SecurityToken");
                QName eType= new QName("EncodingType");
                she.addAttribute(eType, "wsse:Base64Binary");
                QName vType= new QName("ValueType");
                she.addAttribute(vType, "wsse:X509v3");
                InputStream firma = getClass().getClassLoader().getResourceAsStream("cert.pem");
                BufferedReader br = new  BufferedReader(new InputStreamReader(firma));
                String temp = br.readLine();
                while (temp != null) {
                    String temp2 = br.readLine();
                    if (!temp.contains("CERTIFICATE")) {
                        if (temp2 != null)
                            temp += System.getProperty("line.separator");
                        SOAPElement riga = she.addTextNode(temp);
                    }
                    temp = temp2;
                }
            }
        } catch(Throwable x) {
            System.out.println(x);
        }
        return true;
    }

    public boolean handleFault(SOAPMessageContext smc) {
        return true;
    }

    public void close(MessageContext messageContext) {
    }

}

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

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


From do-not-reply at jboss.com  Thu Oct 30 10:02:32 2008
From: do-not-reply at jboss.com (mignaak)
Date: Thu, 30 Oct 2008 10:02:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: jax-ws soap protocol handler and
	white space.
Message-ID: <19245677.1225375352891.JavaMail.jboss@colo-br-02.atl.jboss.com>

Anyone?

MuuuuuuuuuuuuuuuuuuuuublEEEEEEEEEEEEEEEEEEEE...

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

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


From do-not-reply at jboss.com  Thu Oct 30 11:33:09 2008
From: do-not-reply at jboss.com (tperrigo)
Date: Thu, 30 Oct 2008 11:33:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Stateless Session EJB Endpoint (JBossWS
	Native)
Message-ID: <21160562.1225380789284.JavaMail.jboss@colo-br-02.atl.jboss.com>

JBoss 5.0.0.CR2, JBossWS Native (latest distribution).   I've got a stateless session bean that I want to use as a web service endpoint.  I created an Eclipse project using the (very handy!) ant tasks provided by the JBossWS Native distribution.  I created my @Stateless-annotated implementation class, and specified (using @Remote) the remote interface for the class.

Using ant build file generated by the JBossWS ant tasks, I was able to build and deploy my jar file, although, both at app server startup and deployment time, I receive the following error:

  | /usr/local/jboss-5.0.0.CR2/server/logos/deploy/jbossws-container-jboss-beans.xml -> java.lang.IllegalStateException: WSKernelLocator is already installed.
  | 

The web service appears in the list of deployed services in the jbossws console, but I thought for my first test I would simply try to invoke the service as an EJB (through the Remote interface).  The JNDI lookup succeeds (it finds an object with the proper JNDI name), but when I try to cast it to the EJB's Remote Interface, I get a ClassCastException.  When I print out the actual type of the object returned from the JNDI lookup, I find that it is an instance of javax.naming.Reference.

So my questions are:
(1) Does anyone know what the startup / deployment error means?

(2) Why can't I seem to get a reference to my RemoteInterface via a JNDI lookup?  (Why the ClassCastException?)

Sorry for being so long-winded, I just wanted to include anything that might help.  Any advice would be very much appreciated!

Tim



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

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


From do-not-reply at jboss.com  Thu Oct 30 12:11:30 2008
From: do-not-reply at jboss.com (tonioc)
Date: Thu, 30 Oct 2008 12:11:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Jboss 4.2.2 hangs when after deploying
	a WAR
Message-ID: <3074040.1225383090632.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I'm using jbossws 3.0.4  in jboss 4.2.2, installation went good, and I
try my first EchoService as a webapp, all ok.

After that I added a method that returns a BizClass, 
   BizClass getBizClass() {
  |        return new BizClass();
  |    }

The BizClassTree is in an external jar.

This BizClass is the root of a tree of
about 500 classes all JAXB annotated, they work pretty well if I
generate the xml/schema using JAXB just in Java class main method.

When I deploy the WAR, the context is created, after a while the
WSDL is generated (I could see it in HTTP: and file:), and jboss continues working (100% of processor) and does not stop.

If I call the service an exception is thrown telling me:
 Endpoint cannot handle requests in state: CREATED

In JBossWs/services page,  Start Time has a value of null.

No log is shown (I added DEBUG to org.jboss.ws).

Any help  or ideas will be greatly welcomed
tonio




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

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


From do-not-reply at jboss.com  Thu Oct 30 13:30:41 2008
From: do-not-reply at jboss.com (tonioc)
Date: Thu, 30 Oct 2008 13:30:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS client libraries from Maven
	frustration
Message-ID: <19956359.1225387841402.JavaMail.jboss@colo-br-02.atl.jboss.com>

I had some similar problems, but constructing the server-side stuff.

I ended up only adding 
    org.jboss.ws/jbossws-jboss422/3.0.4.GA
dependency

Hope it helps

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

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


From do-not-reply at jboss.com  Thu Oct 30 13:34:59 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Thu, 30 Oct 2008 13:34:59 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Stateless Session EJB Endpoint
	(JBossWS Native)
Message-ID: <10210116.1225388099123.JavaMail.jboss@colo-br-02.atl.jboss.com>

1) There should be only one WSKernelLocatpor bean declared, and it should be in the jbossws-container-jboss-beans.xml file. It would appear that you have this bean also declared elsewhere. The best thing to to is a grep or text find to locate the extra declaration.

2) What JNDI name did you use? Have you used JNDIView to determine under what name the EJB was registered?  http://www.jboss.org/community/docs/DOC-9583

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

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


From do-not-reply at jboss.com  Thu Oct 30 13:47:03 2008
From: do-not-reply at jboss.com (tonioc)
Date: Thu, 30 Oct 2008 13:47:03 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Jboss 4.2.2 hangs when after
	deploying a WAR
Message-ID: <30240748.1225388823504.JavaMail.jboss@colo-br-02.atl.jboss.com>

hi,

I've now tested with jboss-4.2.3 / jbossws-3.0.4, the same problem.

thanks
tonioc

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

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


From do-not-reply at jboss.com  Thu Oct 30 13:55:08 2008
From: do-not-reply at jboss.com (tperrigo)
Date: Thu, 30 Oct 2008 13:55:08 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Stateless Session EJB Endpoint
	(JBossWS Native)
Message-ID: <1572974.1225389308589.JavaMail.jboss@colo-br-02.atl.jboss.com>

1)  You were right; there is an extra WSKernalLocator.  There is one defined in the deployers/jbossws.deployer/META-INF/jbossws-container-jboss-beans.xml file, and another in the deploy/jbossws-container-jboss-beans.xml file (so one under the deployers directory, and another in the deploy directory).  Which is the "correct" one to use?

2) For the JNDI name, I used "ProcessAdminEJB/remote"...The JNDI view from the JMXConsole shows the following:


  |   +- ProcessAdminEJB (class: org.jnp.interfaces.NamingContext)
  |   |   +- remote-werner.opt.process.admin.ProcessAdminRemote (class: Proxy for: werner.opt.process.admin.ProcessAdminRemote)
  |   |   +- remote (class: Proxy for: werner.opt.process.admin.ProcessAdminRemote)
  | 
  | 

Is this correct?

Thanks for your help!
Tim



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

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


From do-not-reply at jboss.com  Thu Oct 30 15:38:29 2008
From: do-not-reply at jboss.com (pxstein)
Date: Thu, 30 Oct 2008 15:38:29 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Chicken vs. Egg problem: Specifying URL
	for WSDL: file or ht
Message-ID: <3076999.1225395509425.JavaMail.jboss@colo-br-02.atl.jboss.com>

Assume I have a WSDL file onn C:\myproj\test\mytest.wsdl and generate all the necessary web service stuff from it with wsconsume.

Then one of the generated files contains a reference to the original WSDL file similar to:

public class myService     extends Service  {
    private final static URL CMPXWSSERVICE_WSDL_LOCATION;
    static {
        URL url = null;
        try {
            url = new URL("file:/C:/myproj/test/mytest.wsdl");
        } catch (MalformedURLException e) {
            e.printStackTrace();        }
        CMPXWSSERVICE_WSDL_LOCATION = url;
    }


Later, when I deploy this web service the main, one-and-only WSDL is visible on the server through the address

http://127.0.0.1:8080/pTestProj/mytest.wsdl

Should I replace now the "file:/...." reference by the later "http:...." address in the source code and re-compile and re-deploy it again?

How else can I make the wsdl file address more independent from origin?

Peter

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

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


From do-not-reply at jboss.com  Thu Oct 30 16:59:20 2008
From: do-not-reply at jboss.com (tonioc)
Date: Thu, 30 Oct 2008 16:59:20 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Jboss 4.2.2 hangs when after
	deploying a WAR
Message-ID: <3330467.1225400360531.JavaMail.jboss@colo-br-02.atl.jboss.com>

finally I obtained the log (which full filled my file-system)

It seems some recursive behavior is the cause of this
hanging.

here is the log:

2008-10-30 18:01:08,213 INFO  [org.jboss.wsf.stack.jbws.WSDLFilePublisher] WSDL published to: file:/home/xtra/u/jdesa/mccg/jboss-4.2.2.GA/server/default/data/wsdl/wstest.war/EchoService23289.wsdl
  | 2008-10-30 18:01:08,394 DEBUG [org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl] EagerInitializeDeploymentAspect:Start
  | 2008-10-30 18:01:08,394 DEBUG [org.jboss.ws.metadata.umdm.UnifiedMetaData] Eagerly initialize the meta data model
  | 2008-10-30 18:01:08,397 DEBUG [org.jboss.ws.metadata.wsdl.xmlschema.JBossXSModel] Registered as anon type: {http://www.mccg.net/xsd/phoenix/base-types/claim.xsd:>claimInvolvedParty>listOfExtraAttr} -> Complex type name='http://www.mccg.net/xsd/phoenix/base-types/basic.xsd,#AnonType_listOfExtraAttribsObject',  base type name='anyType',  content type='ELEMENT',  isAbstract='false',  hasTypeId='false',  final='0',  block='0',  particle='("http://www.mccg.net/xsd/phoenix/base-types/basic.xsd":extraAttr{0-UNBOUNDED})',  derivedBy='RESTRICTION'.
  | 

There are 20Gb similar to the last line, I was not able to
find out a pattern that let me understand what is happening
it seems that the JBossXSModel (not sure what it is) is not capable of managing some kind of recursive references (?) inside an schema.

I tried a basic example Contact->ListOfAddress and Address->ListOfContact and it worked ok.

Continue investigating....
thanks to anybody who bothers reading my-emails
tonio

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

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


From do-not-reply at jboss.com  Thu Oct 30 17:40:56 2008
From: do-not-reply at jboss.com (tonioc)
Date: Thu, 30 Oct 2008 17:40:56 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossXSModel goes into endless loop
Message-ID: <11041408.1225402856134.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I had similar problems, running Jboss 4.2.2.GA and jbossws 3.0.4.GA, but not trying to expose xhml.xsd, just a Tree of Classes (near 500) JAXB annotated.

If I use 4.2.3 there is a similar problem.

Any news on these  issue ?

I'm trying to create a simple test-case, 
but it's really difficult to find one.

thanks in advance
tonio





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

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


From do-not-reply at jboss.com  Thu Oct 30 17:51:36 2008
From: do-not-reply at jboss.com (tonioc)
Date: Thu, 30 Oct 2008 17:51:36 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Jboss 4.2.2 hangs when after
	deploying a WAR
Message-ID: <23875067.1225403496129.JavaMail.jboss@colo-br-02.atl.jboss.com>

This problem was also reported some time ago in:

JBossXSModel goes into endless loop
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=131673
 




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

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


From do-not-reply at jboss.com  Thu Oct 30 17:53:30 2008
From: do-not-reply at jboss.com (tonioc)
Date: Thu, 30 Oct 2008 17:53:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossXSModel goes into endless loop
Message-ID: <21492060.1225403610146.JavaMail.jboss@colo-br-02.atl.jboss.com>

If you like to see my post at

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

thanks 
tonio

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

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


From do-not-reply at jboss.com  Thu Oct 30 19:09:01 2008
From: do-not-reply at jboss.com (macmirror)
Date: Thu, 30 Oct 2008 19:09:01 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Problem accessing from Remote
Message-ID: <11267252.1225408141163.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have a simple Webservice which runs perfect local but if
deployed remotely, I have the problem that the generated
WSDL references the endpoint address 127.0.0.1 instead
of the hostname where the service is deployed:


  | [...]
  |        <service name="UpdateService">
  |        <port binding="tns:UpdateServiceBinding" name="UpdateServicePort">
  |        <soap:address location="http://127.0.0.1:9090/ws/ws-update"/>
  |      </port>
  |    </service>
  | </definitions>
  | 

Now as I outed myself as a WS-newbie, I hope someone can point me to
what I am doing wrong or should do differently.

As an example you can take the seambay example of Seam which has the
same "problem" if deployed non-local. I guess, I have simply a misunderstand
how things should work.

Ready for a lesson... ;)

Thanks,
mac


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

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


From do-not-reply at jboss.com  Thu Oct 30 19:38:05 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Thu, 30 Oct 2008 19:38:05 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem accessing from Remote
Message-ID: <4353499.1225409885454.JavaMail.jboss@colo-br-02.atl.jboss.com>

The URL for the web service should reflect the URL used to access the WSDL. Thus if you get the WSDL from localhost, the web service will indicate localhost. To get it to use the actual host name, access it using the hostname. But before you do this, make sure that you start the app server using the -b option (https://www.jboss.org/community/docs/DOC-10179)

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

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


From do-not-reply at jboss.com  Fri Oct 31 04:25:50 2008
From: do-not-reply at jboss.com (yousuf.raza)
Date: Fri, 31 Oct 2008 04:25:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Propagate security context to second
	webservice call
Message-ID: <32491481.1225441550749.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have configured a sample prototype application that deploys a WebService (EJB endpoint)  to JBoss 4.3 which is secured against my security domain using WS-Security (using UserNameToken.)

If the client provides the correct credentials the principal is set correctly. 

My question is if I want to make a second WebService call from the first one is there a way I can propagate the security context without having to provide some credential information like this:

((BindingProvider)webserviceApi).getRequestContext().put(BindingProvider.USERNAME_PROPERTY, WebServiceConstants.USERNAME);

((BindingProvider)webserviceApi).getRequestContext().put(BindingProvider.PASSWORD_PROPERTY, WebServiceConstants.PASSWORD);


Basically what I have in mind is something where the subsequent webservice call automatically adds the required ws-security header fields in the next request. 

For eg. This would be similar to the case where if I were to make a call on a EJB from the webservice that was protected against the same security domain the container would handle the propagation of the security context. 

Here is the flow I am talking about if I wasn't clear enough:

Client --> 1st Webservice --> 2nd Webservice


There is some documentation about doing this if using acegi security(spring security) but I was wondering if Jbossws does this somehow.

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

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


From do-not-reply at jboss.com  Fri Oct 31 04:31:40 2008
From: do-not-reply at jboss.com (yousuf.raza)
Date: Fri, 31 Oct 2008 04:31:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Propagate security context to
	second webservice call
Message-ID: <13138657.1225441900834.JavaMail.jboss@colo-br-02.atl.jboss.com>

Here is a link to acegi documentation I was talking about:

http://www.vorburger.ch/blog1/2006/10/propagating-acegis-security-context-in.html

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

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


From do-not-reply at jboss.com  Fri Oct 31 04:41:18 2008
From: do-not-reply at jboss.com (yousuf.raza)
Date: Fri, 31 Oct 2008 04:41:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Propagate security context to
	second webservice call
Message-ID: <17737992.1225442478377.JavaMail.jboss@colo-br-02.atl.jboss.com>

Continuing this discussion with myself.

"yousuf.raza" wrote : Here is a link to acegi documentation I was talking about:
  | 
  | http://www.vorburger.ch/blog1/2006/10/propagating-acegis-security-context-in.html

Actually this document is doing something different. Not what I initially thought it was doing. 

In any case my question remains.




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

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


From do-not-reply at jboss.com  Fri Oct 31 04:50:02 2008
From: do-not-reply at jboss.com (yousuf.raza)
Date: Fri, 31 Oct 2008 04:50:02 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Propagate security context to
	second webservice call
Message-ID: <31249073.1225443002755.JavaMail.jboss@colo-br-02.atl.jboss.com>

Again continuing this discussion with myself.

One way I guess to solve this issue would be to use handlers.

One picks up the credential information from the soap header and when the response is sent another handler adds the header fields.

This way the second webservice will try to authenticate against the headers added by my handler.

Would this be a correct solution?

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

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


From do-not-reply at jboss.com  Fri Oct 31 08:53:31 2008
From: do-not-reply at jboss.com (mignaak)
Date: Fri, 31 Oct 2008 08:53:31 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: jax-ws soap protocol handler and
	white space.
Message-ID: <31140182.1225457611375.JavaMail.jboss@colo-br-02.atl.jboss.com>

It works fine on websphere 6.1, which has axis2 jax-ws runtime.

Any help would be appreciated.

Thanks.

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

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


From do-not-reply at jboss.com  Fri Oct 31 11:38:56 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 31 Oct 2008 11:38:56 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Jar file for
	org.jboss.ws.core.soap.SAAJMetaFactoryImpl.
Message-ID: <32165984.1225467536648.JavaMail.jboss@colo-br-02.atl.jboss.com>

First of all, sorry for the late reply; btw this thread could have also be in the JBossWS-Metro forum. Anyway, I'm looking at this topic and the related issue (JBWS-2335):

- the jbossws-client.jar is correctly removed by the jbossws-metro installation script because that's the native stack client artifact. You should get a jbossws-metro-client.jar artifact both in client and server/default/deploy/jbossws.sar (assuming you're using jbossws-metro 3.0.3 and the default server configuration). Restoring the jbossws-client.jar to any position in the server cannot be a solution, as you mix different implementations of the same things

- the javax.xml.soap.MetaFactory implementation to be used with Metro stack is com.sun.xml.messaging.saaj.soap.SAAJMetaFactoryImpl . So the problem here is with the server trying to look for org.jboss.ws.core.soap.SAAJMetaFactoryImpl which of course is not available when the Metro stack is installed. You should not have the jboss-saaj.jar lib in you classpath as that pulls in the native soap MetaFactory through the META-INF/services provide system.

- the jboss-saaj.jar is correctly removed from the jboss server/default/lib by the JBossWS-Metro installation. The right SAAJ library for this stack is installed instead (saaj-impl.jar) under server/default/deploy/jbossws.sar/

This said, if you didn't do this way before, I suggest starting from a vanilla jboss-4.2 distribution and then run the installation script. I'd also suggest using the default configuration or checking the jbossws-deploy.conf file in the configuration you want to use before running the installation script because of this issue https://jira.jboss.org/jira/browse/JBWS-2377 .

If you still have the issue, could you please attach a small testcase to JBWS-2335 so that we can reproduce the problem? I suspect this can be related to JBWS-2377 as our Hudson instance daily runs the jbossws-framework testsuite against JBoss 4.2.3.GA after having installed the binary distribution (the one you get from the download page once the release is out) on its default configuration.

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

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


From do-not-reply at jboss.com  Fri Oct 31 12:58:53 2008
From: do-not-reply at jboss.com (jluna)
Date: Fri, 31 Oct 2008 12:58:53 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Hot deployment problems using XFire or
	Axis2
Message-ID: <16163871.1225472333027.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi, 
I'm deploying web services applications but the changes do not take effect until the JBoss is restarted. The JBoss I'm using is JBoss 4.0.4 with XFire 1.2 or Axis 2 for the services. 

This problem only happens to me only with web services. With others applications hot deployments are doing ok, so I know is something related to the soap stacks I'm using (XFire, Axis). 

Any idea how can I fix this? 
If I migrate my applications to EJB3 with JBoss 4.0.5 will this keep happening to me? 

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

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


From do-not-reply at jboss.com  Fri Oct 31 14:27:26 2008
From: do-not-reply at jboss.com (tperrigo)
Date: Fri, 31 Oct 2008 14:27:26 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Stateless Session EJB Endpoint
	(JBossWS Native)
Message-ID: <1703122.1225477646445.JavaMail.jboss@colo-br-02.atl.jboss.com>

I removed the duplicate jbossws-container-jboss-beans.xml from the deploy directory of my server and the "WSKernelLocator already installed" error went away, but I am still getting the ClassCastException when I do a JNDI lookup on my EJB.  I really have no idea what I'm doing wrong...everything seems to deploy without issue.  If anyone has any suggestions, I would be most appreciative!

Thanks,
Tim



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

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


From do-not-reply at jboss.com  Fri Oct 31 14:45:10 2008
From: do-not-reply at jboss.com (pxstein)
Date: Fri, 31 Oct 2008 14:45:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Error "Canot get target bean instance"
	when calling a web se
Message-ID: <13555314.1225478710085.JavaMail.jboss@colo-br-02.atl.jboss.com>

When I try to call a previously successful deployed web service then I get
an error:

Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: Canot get target bean instance
	at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:171)
	at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:94)
	at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:240)
	at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:210)
	at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:103)
	at $Proxy24.sendObj(Unknown Source)
	at com.mycomp.testWsServiceClient.main(testWsServiceClient.java:29)

What is the problem?

Peter

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

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


From do-not-reply at jboss.com  Fri Oct 31 14:57:44 2008
From: do-not-reply at jboss.com (pxstein)
Date: Fri, 31 Oct 2008 14:57:44 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Diff. between web.xml and web.xml.org?
Message-ID: <21648270.1225479464202.JavaMail.jboss@colo-br-02.atl.jboss.com>

When I deploy a web service then in the JBoss WAR directory there are suddenly 2 web.xml files:

- web.xml and 
- web.xml.org

The web.xml.org looks like my original descriptor while
web.xml changed significantly.

What is the difference?

Peter

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

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


From do-not-reply at jboss.com  Fri Oct 31 15:32:26 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 31 Oct 2008 15:32:26 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Stateless Session EJB Endpoint
	(JBossWS Native)
Message-ID: <24702219.1225481546411.JavaMail.jboss@colo-br-02.atl.jboss.com>

Looks like this discussion is being continued at: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186101

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

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


From do-not-reply at jboss.com  Fri Oct 31 15:40:36 2008
From: do-not-reply at jboss.com (tperrigo)
Date: Fri, 31 Oct 2008 15:40:36 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Stateless Session EJB Endpoint
	(JBossWS Native)
Message-ID: <13238513.1225482036283.JavaMail.jboss@colo-br-02.atl.jboss.com>

Yes, that's correct; sorry, I should have mentioned that I posted to the EJB3 forum.  Once the WSKernelLocator issue was resolved by the removal of one of the duplicate files, I tried removing the web service annotations from my EJB, making it just a simple stateless session bean, to see if I could then do a JNDI lookup.  I'm still getting a ClassCastException, though.  I left the topic open in this forum, though, just in case anyone knew of any EJB-related problems from projects created using the ant tasks provided with the JBossWS Native distribution.

Thanks,
Tim

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

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


From do-not-reply at jboss.com  Fri Oct 31 17:33:56 2008
From: do-not-reply at jboss.com (mjhammel)
Date: Fri, 31 Oct 2008 17:33:56 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Throws exception in WS (back to
	remote client) without g
Message-ID: <17043106.1225488836066.JavaMail.jboss@colo-br-02.atl.jboss.com>

A follow up, just in case anyone else needs the info.

I ignored this problem for quite some time and finally decided to return to it today.  I finally figured out how to tweak log4j to hide those soap fault messages that come from my application throwing an exception.  In the jboss-log4j.xml file (in my case, under server/default/conf), I added these lines at the bottom of the file:


  |    <category name="org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS">
  |       <priority value="FATAL"/>
  |    </category>
  | 

I just had to dig around to find the right category name for these messages.  It just took awhile before I could find it.

Hope that helps anyone with a similar concern.

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

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