From do-not-reply at jboss.com  Wed Apr  1 01:07:25 2009
From: do-not-reply at jboss.com (mobaxkrs)
Date: Wed, 1 Apr 2009 01:07:25 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-Addressing in native stack
Message-ID: <1690610.1238562445483.JavaMail.jboss@colo-br-02.atl.jboss.com>

I downloaded src distribution of jbossws 3.1.0 
and is working on sample from native-tests. 
org.jboss.test.ws.jaxws.samples.ws=addressing package. 

It is written as test case, which files are at server side and which files are to be at client end. 

the Clienthandler.java is reference to statefulendpointImpl.IQDN variable and should it be at server side?


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

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


From do-not-reply at jboss.com  Wed Apr  1 12:47:34 2009
From: do-not-reply at jboss.com (bartvh)
Date: Wed, 1 Apr 2009 12:47:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WebFault targetNamespace and
	document/literal
Message-ID: <29955319.1238604454603.JavaMail.jboss@colo-br-02.atl.jboss.com>

It looks like there is a problem with the namespace for web faults when this is not the same as the namespace of the service. The type definition of the web faults has the correct namespace, but the reference to the type from the messsage elements uses the name space of the service instead. 

For example:package zzz.ws.flt;
  | 
  | import javax.xml.bind.annotation.XmlType;
  | import javax.xml.ws.WebFault;
  | 
  | @WebFault(targetNamespace="zzz.ws.flt")
  | @XmlType(namespace="zzz.ws.flt")
  | public class ZZZException extends Exception {
  |   private String info;
  | 
  |   public ZZZException(String info) {
  |     this.setInfo(info);
  |   }
  | 
  |   public void setInfo(String info) {
  |     this.info = info;
  |   }
  | 
  |   public String getInfo() {
  |     return info;
  |   }
  | }
andpackage zzz.ws.srv.impl;
  | 
  | import javax.ejb.Remote;
  | import javax.ejb.Stateless;
  | import javax.jws.WebMethod;
  | import javax.jws.WebService;
  | import javax.jws.soap.SOAPBinding;
  | import javax.jws.soap.SOAPBinding.ParameterStyle;
  | import javax.jws.soap.SOAPBinding.Style;
  | import javax.jws.soap.SOAPBinding.Use;
  | 
  | import zzz.ws.flt.ZZZException;
  | import zzz.ws.srv.ZZZService;
  | 
  | @Stateless
  | @Remote(ZZZService.class)
  | @WebService(targetNamespace="zzz.ws.srv", name="ZZZService")
  | @SOAPBinding(style=Style.DOCUMENT, use=Use.LITERAL, parameterStyle=ParameterStyle.WRAPPED)
  | public class ZZZServiceImpl implements ZZZService {
  | 
  |   @WebMethod
  |   public String echo(String input) throws ZZZException {
  |     return input;
  |   }
  | }

generates

<?xml version="1.0" encoding="UTF-8"?>
  | <definitions name="ZZZServiceImplService" targetNamespace="zzz.ws.srv" xmlns:tns="zzz.ws.srv" xmlns:ns1="zzz.ws.flt" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/">
  |   <types>
  |     <xs:schema targetNamespace="zzz.ws.srv" version="1.0" xmlns:tns="zzz.ws.srv" 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>
  |     <xs:schema targetNamespace="zzz.ws.flt" version="1.0" xmlns:tns="zzz.ws.flt" xmlns:xs="http://www.w3.org/2001/XMLSchema">
  |    <xs:element name="ZZZException" type="tns:ZZZException"/>
  |    <xs:complexType name="ZZZException">
  |     <xs:sequence>
  |      <xs:element minOccurs="0" name="info" type="xs:string"/>
  |      <xs:element minOccurs="0" name="message" type="xs:string"/>
  |     </xs:sequence>
  |    </xs:complexType>
  |   </xs:schema>
  |   </types>
  |   <message name="ZZZService_echo">
  |     <part name="echo" element="tns:echo">
  |     </part>
  |   </message>
  |   <message name="ZZZException">
  |     <part name="ZZZException" element="tns:ZZZException">
  |     </part>
  |   </message>
  |   <message name="ZZZService_echoResponse">
  |     <part name="echoResponse" element="tns:echoResponse">
  |     </part>
  |   </message>
  |   <portType name="ZZZService">
  |     <operation name="echo" parameterOrder="echo">
  |       <input message="tns:ZZZService_echo">
  |     </input>
  |       <output message="tns:ZZZService_echoResponse">
  |     </output>
  |       <fault name="ZZZException" message="tns:ZZZException">
  |     </fault>
  |     </operation>
  |   </portType>
  |   <binding name="ZZZServiceBinding" type="tns:ZZZService">
  |     <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>
  |       <fault name="ZZZException">
  |         <soap:fault name="ZZZException" use="literal"/>
  |       </fault>
  |     </operation>
  |   </binding>
  |   <service name="ZZZServiceImplService">
  |     <port name="ZZZServicePort" binding="tns:ZZZServiceBinding">
  |       <soap:address location="http://jbossws.undefined.host:8080/zzz-zzzservice-ejb/ZZZServiceImpl"/>
  |     </port>
  |   </service>
  | </definitions>

Notice the element="tns:ZZZException" in the output.

This is running jbossws-native-3.1.0.GA on jboss-4.2.3.GA.

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

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


From do-not-reply at jboss.com  Thu Apr  2 02:14:42 2009
From: do-not-reply at jboss.com (mobaxkrs)
Date: Thu, 2 Apr 2009 02:14:42 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-Addressing in native stack
Message-ID: <25074028.1238652882528.JavaMail.jboss@colo-br-02.atl.jboss.com>

It worked. 

I made changes in sample web service as in addressing sample.
Changed Clienthandler,java IQDN instance

Now the request and response of web services are linked through a reference parameter in ws-addressing


Thanks for the support

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

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


From do-not-reply at jboss.com  Thu Apr  2 11:28:41 2009
From: do-not-reply at jboss.com (redCar)
Date: Thu, 2 Apr 2009 11:28:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Warning EJBTHREE-1337
Message-ID: <13602583.1238686121340.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hallo,

if I call my EJB3-Webservice I will get this warning:
[StatelessBeanContext] EJBTHREE-1337: do not get WebServiceContext property from stateless bean context, it should already have been injected

what do I have to do to avoid this warning in my code.

or

can I do something that I don't get the line in the logfile

Thank you,
Werner


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

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


From do-not-reply at jboss.com  Thu Apr  2 16:49:19 2009
From: do-not-reply at jboss.com (wilson.lists@gmail.com)
Date: Thu, 2 Apr 2009 16:49:19 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Implementing WS-Security Usename
	Token Profile Authentic
Message-ID: <18863407.1238705359592.JavaMail.jboss@colo-br-02.atl.jboss.com>

I've tried exactly these steps and the authentication is not working. I can send any combination of username/password and the server does not complains about wrong password.  

Does anyone was able to reproduce these steps? I am going crazy with this problem for 2 entire days.

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

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


From do-not-reply at jboss.com  Sat Apr  4 02:25:07 2009
From: do-not-reply at jboss.com (mobaxkrs)
Date: Sat, 4 Apr 2009 02:25:07 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WebServices logging
Message-ID: <11855792.1238826307158.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi 

I tried out the recording sample in jboss 3.1.0 WS. 
I just took out the recording sample alone 
from 
/root/jbossws-native-src-dist/modules/testsuite/framework-tests/src/test/java/org/jboss/test/ws/management/recording

It throws exception
java.lang.IllegalArgumentException: Cannot obtain 'null/management-recording-native.jar'. System property 'test.archive.directory' not set.
	at org.jboss.wsf.test.JBossWSTestHelper.getArchiveFile(JBossWSTestHelper.java:276)
	at org.jboss.wsf.test.JBossWSTestHelper.deploy(JBossWSTestHelper.java:66)

the property is set in the ant process. 
How can i run separately


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

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


From do-not-reply at jboss.com  Sat Apr  4 14:35:10 2009
From: do-not-reply at jboss.com (gopivm)
Date: Sat, 4 Apr 2009 14:35:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - faultString: Endpoint ... Port does not
	contain operation me
Message-ID: <6721920.1238870110490.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,
I am facing a problem while invoking the web service method which is exposed from stateless session bean (EJB3) by DII client.
This is my development environment.

Eclipse Version: 3.4.0
Jboss-4.3.2.GA
JRE 1.5.0_15
EJB 3.0

I "googled" a lot, but couldn't find any correct solution which actually works. But, there are a lot of people have faced the same problem.

Can somebody help me?

This is the error that I am getting : 

  | AxisFault
  |  faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client
  |  faultSubcode: 
  |  faultString: Endpoint {http://woss.appservice.nbric.nbpts.com/}WarehouseServiceBeanPort does not co
  | ntain operation meta data for: {http://schemas.xmlsoap.org/wsdl/}searchPersonsForWarehouseBatch
  |  faultActor: 
  |  faultNode: 
  |  faultDetail: 
  | 	{http://xml.apache.org/axis/}stackTrace:Endpoint {http://woss.appservice.nbric.nbpts.com/}Warehouse
  | ServiceBeanPort does not contain operation meta data for: {http://schemas.xmlsoap.org/wsdl/}searchPe
  | rsonsForWarehouseBatch
  | 	at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
  | 	at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
  | 	at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
  | 	
  | 
My client code DII: 

  | QName serviceName = new QName(
  | 					"http://localhost:8080/nbric-business-appservices/WarehouseServiceBean?wsdl",
  | 					"WarehouseServiceBeanService");
  | 			ServiceFactory factory = ServiceFactory.newInstance();
  | 			Service service = factory.createService(serviceName);
  | 			Call call = service.createCall();
  | 			QName operationName = new QName(BODY_NAMESPACE_VALUE,
  | 					"searchPersonsForWarehouseBatch");
  | 			call.setOperationName(operationName);
  | 			call.setTargetEndpointAddress(endpoint);
  | 			call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true));
  | 			// call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");
  | 			call.setProperty(ENCODING_STYLE_PROPERTY, URI_ENCODING);
  | 			QName QNAME_TYPE_STRING = new QName(NS_XSD, "string");
  | 			call.setReturnType(QNAME_TYPE_STRING);
  | 			call.setOperationName(new QName(BODY_NAMESPACE_VALUE,
  | 					"searchPersonsForWarehouseBatch"));
  | 
  | 			call.addParameter("String_1", QNAME_TYPE_STRING, ParameterMode.IN);
  | 			String[] params = { "DEFAULTS13330" };
  | 			// Invoke the WS operation using the JAX-RPC Call's invoke method
  | 			String result = (String) call.invoke(params);
  | 	
WSDL : 

  | - <definitions name="WarehouseServiceBeanService" targetNamespace="http://woss.appservice.nbric.nbpts.com/" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://woss.appservice.nbric.nbpts.com/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  | - <types>
  | - <xs:schema targetNamespace="http://woss.appservice.nbric.nbpts.com/" version="1.0" xmlns:tns="http://woss.appservice.nbric.nbpts.com/" xmlns:xs="http://www.w3.org/2001/XMLSchema">
  |   <xs:element name="NBRICApplicationException" type="tns:NBRICApplicationException" /> 
  |   <xs:element name="NBRICSystemException" type="tns:NBRICSystemException" /> 
  |   <xs:element name="searchPersonsForWarehouseBatch" type="tns:searchPersonsForWarehouseBatch" /> 
  |   <xs:element name="searchPersonsForWarehouseBatchResponse" type="tns:searchPersonsForWarehouseBatchResponse" /> 
  | - <xs:complexType name="searchPersonsForWarehouseBatch">
  | - <xs:sequence>
  |   <xs:element minOccurs="0" name="arg0" type="xs:string" /> 
  |   </xs:sequence>
  |   </xs:complexType>
  | - <xs:complexType name="searchPersonsForWarehouseBatchResponse">
  | - <xs:sequence>
  |   <xs:element minOccurs="0" name="return" type="xs:string" /> 
  |   </xs:sequence>
  |   </xs:complexType>
  | - <xs:complexType name="NBRICApplicationException">
  | - <xs:sequence>
  |   <xs:element minOccurs="0" name="errorCode" type="xs:string" /> 
  |   <xs:element minOccurs="0" name="message" type="xs:string" /> 
  |   </xs:sequence>
  |   </xs:complexType>
  | - <xs:complexType name="NBRICSystemException">
  | - <xs:sequence>
  |   <xs:element minOccurs="0" name="errorCode" type="xs:string" /> 
  |   <xs:element minOccurs="0" name="message" type="xs:string" /> 
  |   </xs:sequence>
  |   </xs:complexType>
  |   </xs:schema>
  |   </types>
  | - <message name="NBRICSystemException">
  |   <part element="tns:NBRICSystemException" name="NBRICSystemException" /> 
  |   </message>
  | - <message name="NBRICApplicationException">
  |   <part element="tns:NBRICApplicationException" name="NBRICApplicationException" /> 
  |   </message>
  | - <message name="WarehouseServiceBean_searchPersonsForWarehouseBatchResponse">
  |   <part element="tns:searchPersonsForWarehouseBatchResponse" name="searchPersonsForWarehouseBatchResponse" /> 
  |   </message>
  | - <message name="WarehouseServiceBean_searchPersonsForWarehouseBatch">
  |   <part element="tns:searchPersonsForWarehouseBatch" name="searchPersonsForWarehouseBatch" /> 
  |   </message>
  | - <portType name="WarehouseServiceBean">
  | - <operation name="searchPersonsForWarehouseBatch" parameterOrder="searchPersonsForWarehouseBatch">
  |   <input message="tns:WarehouseServiceBean_searchPersonsForWarehouseBatch" /> 
  |   <output message="tns:WarehouseServiceBean_searchPersonsForWarehouseBatchResponse" /> 
  |   <fault message="tns:NBRICSystemException" name="NBRICSystemException" /> 
  |   <fault message="tns:NBRICApplicationException" name="NBRICApplicationException" /> 
  |   </operation>
  |   </portType>
  | - <binding name="WarehouseServiceBeanBinding" type="tns:WarehouseServiceBean">
  |   <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /> 
  | - <operation name="searchPersonsForWarehouseBatch">
  |   <soap:operation soapAction="searchPersonsForWarehouseBatchAction" /> 
  | - <input>
  |   <soap:body use="literal" /> 
  |   </input>
  | - <output>
  |   <soap:body use="literal" /> 
  |   </output>
  | - <fault name="NBRICSystemException">
  |   <soap:fault name="NBRICSystemException" use="literal" /> 
  |   </fault>
  | - <fault name="NBRICApplicationException">
  |   <soap:fault name="NBRICApplicationException" use="literal" /> 
  |   </fault>
  |   </operation>
  |   </binding>
  | - <service name="WarehouseServiceBeanService">
  | - <port binding="tns:WarehouseServiceBeanBinding" name="WarehouseServiceBeanPort">
  |   <soap:address location="http://127.0.0.1:8080/nbric-business-appservices/WarehouseServiceBean" /> 
  |   </port>
  |   </service>
  |   </definitions>
  | 
The EJB 3 service: 

  | @Stateless(name = "WarehouseServiceBean", mappedName = "WarehouseServiceBean")
  | @TransactionManagement(TransactionManagementType.CONTAINER)
  | @TransactionAttribute(TransactionAttributeType.REQUIRED)
  | @WebService
  | public class WarehouseServiceBean implements /*WarehouseServiceInterface,*/ Serializable {
  | 
  | 	
  | 	/**
  | 	 * 
  | 	 */
  | 	private static final long serialVersionUID = 1L;
  | 	
  | 	public WarehouseServiceBean(){
  | 		
  | 	}
  | 	@WebMethod(action="searchPersonsForWarehouseBatchAction" )
  | 	public String searchPersonsForWarehouseBatch(
  | 			String searchString
  | 			)
  | 			throws NBRICApplicationException, NBRICSystemException {
  | 		List<Person> personList = null;
  | 
  | 		try {
  | 			
  | /* - Commented the DAO code for time being. 
  | 
  | 
  | 
  |                        final PersonDAO dao = DAOFactory.getDAOFactory(
  | 					ApplicationConstants.HIBERNATE_DAO_FACTORY).getPersonDAO();
  | 			// Compass Search * Starts
  | 			//personList = dao.searchPersonCompassPOC(searchString);
  | 			// Compass Search * Ends
  | 			
  | 			// Hibernate search 
  | 			personList = dao.searchUserPOC(searchString);
  | 			
  | 			int arrayLength = personList.size();
  | 			Person[] personArray = new Person[arrayLength];
  | 			for (int i = 0; i < personArray.length; i++) {
  | 				personArray
  |  = personList.get(i);
  | 			}*/
  | 		
  | 
  | 
  | 
  | 
  | 			return "hello";
  | 
  | 	
  | 	/*} catch (NBRICApplicationException e) {
  | 
  | 			throw e;
  | 		} catch (NBRICSystemException e) {
  | 			throw e;*/
  | 
  | 		} catch (Exception e) {
  | 			throw new NBRICSystemException(e, ErrorCode.S_SERVER_DOWN);
  | 		}
  | 	}
  | 
  | }
  | 

Any help is really appreciated.

Thanks in advance.
- Gopi


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

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


From do-not-reply at jboss.com  Mon Apr  6 08:32:42 2009
From: do-not-reply at jboss.com (joncmuniz)
Date: Mon, 6 Apr 2009 08:32:42 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - error with wssecurity!!!!
Message-ID: <17156416.1239021162207.JavaMail.jboss@colo-br-02.atl.jboss.com>

My webservice is working without the configuration wssecurity, 	 	
when I put the settings an error occurs
- put a annotation in webservices
    ----- at EndpointConfig(configName="Standard WSSecurity Endpoint")
- put the files in the web-inf
    ------jboss-wsse-server.xml and the jboss-wsse-client.xml in the client side together with the other files
    ------wsse.cer
    ------wsse.csr
    ------wsse.jks
	
my client is in the servlet

QName qName = new QName("http://coreo.com.br/teste", "Teste");
String serviceURL = "http://jon.ctbc.com.br:8080/jbossWebServiceSecurity-1.0.0/Teste?wsdl";
		Service service = null;
			URL url;
			try {
				url = new URL(serviceURL);
				service = Service.create(url,qName);
				ITeste s = service.getPort(ITeste.class);
				System.out.println(s.localizacao("jjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjj"));
			} catch (MalformedURLException e) {
				// TODO Auto-generated catch block
				e.printStackTrace();
			}


09:09:30,343 ERROR [[MyServlet]] Servlet.service() for servlet MyServlet threw exception
javax.xml.ws.soap.SOAPFaultException: This service requires <wsse:Security>, which is missing.
        at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:84)
        at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:107)
        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:290)
        at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
        at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
        at $Proxy82.localizacao(Unknown Source)
        at br.teste.client.MyServlet.executa(MyServlet.java:54)
        at br.teste.client.MyServlet.doGet(MyServlet.java:33)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java: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.org/index.html?module=bb&op=viewtopic&p=4223648#4223648

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


From do-not-reply at jboss.com  Mon Apr  6 21:03:58 2009
From: do-not-reply at jboss.com (cshannon)
Date: Mon, 6 Apr 2009 21:03:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Can't use MySql under JBOSSWS (Works
	under JBOSS)
Message-ID: <6194779.1239066238530.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have successfully deployed a MySql connection under JBoss, but when trying to reference the same connection under a JBoss-WS I get the error:

java.lang.RuntimeException: mapped-name is required for jdbc/MySqlDS of deployment xxxx.war

I have added the resource information to the web.xml and the jboss-web.xml files in the jbossws-sar but it doesnt work, the service still fails to deploy.

Does anyone know how to set up MySql under JBossWS?

Currently using JBOSS 5.0.1.GA and JBOSSWS 3.1.0.GA on Ubuntu and Java 6

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

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


From do-not-reply at jboss.com  Tue Apr  7 03:40:14 2009
From: do-not-reply at jboss.com (dhanushgopinath)
Date: Tue, 7 Apr 2009 03:40:14 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Getting Soap Header from
	WebServiceContext's MessageContext
Message-ID: <12527850.1239090014949.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I want to access some SOAP Header values inside the WebService when it is called. 

(I know I can use server side handlers fro this, but I do not want to use it as I want the header values for some application inside the web service)

So I use the injection using WebServiceContext, and then get the SOAPMessageCotnext by 
SOAPMessageContext soapMsgContext = (SOAPMessageContext) context.getMessageContext();

And then I get the SoapMessage and Soap Header
 
  | SOAPEnvelope envelope = soapMessageContext.getMessage().getSOAPPart()
  |               .getEnvelope();
  | 
  |         SOAPHeader soapHeader = envelope.getHeader();
  |         // Extract All header elements.       
  |         Iterator headerElements = soapHeader.extractAllHeaderElements();      

The Iterator headerElements, doesnt have any values in it. 

Why is this happening? Doesn't the WebServiceContext return the SoapHeaders.

I checked the rest of the SOAP Message and Soap Body is having only the body elements, it doesn't have any values.

Please let me know in case anyone of u faced the same problems

Thanks 
Dhanush 

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

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


From do-not-reply at jboss.com  Tue Apr  7 04:55:18 2009
From: do-not-reply at jboss.com (srahaingoson)
Date: Tue, 7 Apr 2009 04:55:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Easier RESTeasy
Message-ID: <11198242.1239094518568.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,


I'm very new to server-side development and I'm having a difficult time making out exactly where to put what file when using RESTEasy. 

I would appreciate if someone could point me to a more accessible tutorial or give a brief overview of the installation and configuration. For a beginner, the official documentation doesn't really linger on these parts and comprehending the examples is even steeper an obective.

Any help would be appreciated.

Thanks

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

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


From do-not-reply at jboss.com  Tue Apr  7 06:10:32 2009
From: do-not-reply at jboss.com (derarne)
Date: Tue, 7 Apr 2009 06:10:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - how to use jaxws offline
Message-ID: <738530.1239099032098.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,
I try to call a WS with a jaxws-client. The machine has no connection to the internet. 
The creation of the port takes tries to contact http://schemas.xmlsoap.org/wsdl/ to validate the wsdl.
Is it possible to turn of the validation or is there a (fast) workaround? 

Yours
 Arne

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

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


From do-not-reply at jboss.com  Tue Apr  7 06:13:45 2009
From: do-not-reply at jboss.com (abichap)
Date: Tue, 7 Apr 2009 06:13:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Error in Invoking Webservice
Message-ID: <14453859.1239099225536.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello All,

I'm new to JBoss and have recently followed this link: http://www.jboss.org/community/wiki/JBWS181HelloWorld;jsessionid=CC4553064155592DD301569406F64F5C  to successfully create a webservice.

However, I face problem when I try to invoke the webservice using a Microsoft.Net client which I created. The following is the error which I got: org.jboss.ws.WSException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage

Could someone help me out on this? Anyway, I am running JBoss Version 5.0.1 and I am using JDK6. 

Thanks for all your help. 

Regards,
Abichap



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

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


From do-not-reply at jboss.com  Tue Apr  7 06:57:53 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Tue, 7 Apr 2009 06:57:53 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: how to use jaxws offline
Message-ID: <20246401.1239101874302.JavaMail.jboss@colo-br-02.atl.jboss.com>

Upgrade to the latest JBossWS Native 3.1.0 (the bug is fixed there).

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

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


From do-not-reply at jboss.com  Tue Apr  7 07:25:43 2009
From: do-not-reply at jboss.com (derarne)
Date: Tue, 7 Apr 2009 07:25:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: how to use jaxws offline
Message-ID: <30534729.1239103543540.JavaMail.jboss@colo-br-02.atl.jboss.com>

HI Richard,
I am sorry, but the update to JBossWS Native 3.1.0 (downloaded at http://www.jboss.org/downloading/?projectId=jbossws&url=/jbossws/downloads/jbossws-native-3.1.0.GA.zip) didn't help. 
These files are changed in the update in the server lib folder:

  | jbossws-spi.jar
  | jbossws-native-saaj.jar
  | jbossws-native-jaxws.jar
  | jbossws-native-jaxws-ext.jar
  | jbossws-native-jaxrpc.jar
  | jbossws-jboss423.jar
  | jbossws-framework.jar
  | jbossws-common.jar
  | 
  | Is there something missing? Can I turn off validation?
  | 
  | Yours 
  |  Arne[/img]

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

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


From do-not-reply at jboss.com  Tue Apr  7 08:12:28 2009
From: do-not-reply at jboss.com (gakins)
Date: Tue, 7 Apr 2009 08:12:28 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Easier RESTeasy
Message-ID: <16752577.1239106348231.JavaMail.jboss@colo-br-02.atl.jboss.com>

What have you done so far?  I agree that getting RESTeasy working isn't that easy, but following some simple examples from the Wiki was enough to get my started.

You also might try the resteasy-developers list

I followed this site to get my first RESTeasy app working

http://www.assertionerror.com/2009/02/26/restful-web-services-with-resteasy/

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

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


From do-not-reply at jboss.com  Tue Apr  7 09:21:17 2009
From: do-not-reply at jboss.com (derarne)
Date: Tue, 7 Apr 2009 09:21:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: how to use jaxws offline
Message-ID: <21845406.1239110477827.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,
just to explain, what happens I made a screen shot:
[img]http://ews.tu-dortmund.de/installation/ImWaiting.png[/img]

Hope that gives a hint...

Yours 
 Arne

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

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


From do-not-reply at jboss.com  Tue Apr  7 09:27:37 2009
From: do-not-reply at jboss.com (srahaingoson)
Date: Tue, 7 Apr 2009 09:27:37 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Easier RESTeasy
Message-ID: <24016397.1239110857480.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi, thanks for your response. I have also been following that one. I finally managed to get some basic behaviour working. 

As I said I am quite new to server-side dev so it was quite easy to miss the fact that I dropped out the name of my servlet during my tests.

Right now I'm trying to figure out why it won't work when I'm using the @PathParam and hopefully I'll be able to move on to a full EJB3 integration soon.

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

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


From do-not-reply at jboss.com  Tue Apr  7 10:17:43 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Tue, 7 Apr 2009 10:17:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: how to use jaxws offline
Message-ID: <23652292.1239113863616.JavaMail.jboss@colo-br-02.atl.jboss.com>

Did you update your IDE environment to reference JBossWS 3.1.0 jar files?

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

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


From do-not-reply at jboss.com  Tue Apr  7 10:51:10 2009
From: do-not-reply at jboss.com (derarne)
Date: Tue, 7 Apr 2009 10:51:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: how to use jaxws offline
Message-ID: <21910797.1239115870384.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi Richard,
this was a remote debugging session. I paused the thread that is waiting. The server is running a jboss 4.2.3 jdk 1.6 with the updated JBossWS as you recommended.
Does the "stacktrace" gives you the assumption that the wrong (old) jars are used?

Yours 
 Arne
 

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

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


From do-not-reply at jboss.com  Tue Apr  7 11:23:21 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 7 Apr 2009 11:23:21 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Can't use MySql under JBOSSWS
	(Works under JBOSS)
Message-ID: <22370267.1239117801440.JavaMail.jboss@colo-br-02.atl.jboss.com>

anonymous wrote :  have added the resource information to the web.xml and the jboss-web.xml files in the jbossws-sar 

Try adding it to the WEB-INF directory in your WAR file. (I assume you have a POJO-based web service and not an EJB-based web service.)

If that doesn't work, post the full stack trace and the contents of the web.xml and jboss-web.xml file. And let us know what kind of web service you have. 

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

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


From do-not-reply at jboss.com  Tue Apr  7 11:48:04 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 7 Apr 2009 11:48:04 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Error in Invoking Webservice
Message-ID: <18276647.1239119284060.JavaMail.jboss@colo-br-02.atl.jboss.com>

And you didn't do a search of the forums on "setProperty"? If you did, you might have found various posts like these:

http://www.jboss.org/index.html?module=bb&op=viewtopic&t=152460
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=147781
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=102355  (my take on why this happens is on the second page)

Basically - you are JDK6 but you did not download the JDK6-variant of JBoss AS.

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

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


From do-not-reply at jboss.com  Tue Apr  7 20:18:57 2009
From: do-not-reply at jboss.com (cshannon)
Date: Tue, 7 Apr 2009 20:18:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Can't use MySql under JBOSSWS
	(Works under JBOSS)
Message-ID: <33289597.1239149937222.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thanks for taking a look at this. The resource ref is in my web.xml file, like I said it works perfectly under JBOSS, the webservice I am doing is just a helloworld, the only difference is that I try to connect to the database. All code that works fine. It is some kind of configuration problem. 

web.xml
<web-app>
  | <resource-ref>  
  |           <description>MySql Dataset Definition</description>
  | 	  <res-ref-name>jdbc/MySqlDS</res-ref-name>  
  | 		<jndi-name>java:/MySqlDS</jndi-name>
  |           <res-type>javax.sql.DataSource</res-type>  
  |           <res-auth>Container</res-auth>  
  | </resource-ref>
  | <display-name>postSubmission</display-name>
  | </web-app>

and my jboss-web.xml
<?xml version="1.0" encoding="ISO-8859-1"?>
  | <!DOCTYPE jboss-web
  |     PUBLIC "-//JBoss//DTD Web Application 2.3V2//EN"
  |     "http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd">
  | <jboss-web>
  | 
  |   <!-- A security domain that restricts access
  |   <security-domain>java:/jaas/JBossWS</security-domain>
  |   --> 
  |   <context-root>jbossws</context-root>
  | <resource-ref>
  | 	<res-ref-name>jdbc/MySqlDS</res-ref-name>
  | 	<jndi-name>java:/MySqlDS</jndi-name>
  | </resource-ref>
  | </jboss-web>

It's like JBOSSWS cant find the mysql-ds.xml or something. I tried to copy that into the jbossws deployment folder but then it error-ed out saying that it was already defined. 


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

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


From do-not-reply at jboss.com  Tue Apr  7 22:16:13 2009
From: do-not-reply at jboss.com (abichap)
Date: Tue, 7 Apr 2009 22:16:13 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Error in Invoking Webservice
Message-ID: <30425807.1239156973454.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello Johnson,

Thanks for your reply and help. I actually resolved the problem by using JBoss 4.2.3 

Regards,
Abichap

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

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


From do-not-reply at jboss.com  Wed Apr  8 02:56:17 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Wed, 8 Apr 2009 02:56:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: how to use jaxws offline
Message-ID: <30214480.1239173777666.JavaMail.jboss@colo-br-02.atl.jboss.com>

Cross reference: JBWS-2598

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

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


From do-not-reply at jboss.com  Wed Apr  8 03:03:21 2009
From: do-not-reply at jboss.com (mobaxkrs)
Date: Wed, 8 Apr 2009 03:03:21 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Records Management Framework Samples
Message-ID: <3788599.1239174201639.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi

I need simple separate samples on Records management. 

I could see samples in Test Cases, but the samples throw error.. It cannot be run separately.

The documentation says great features in framework.. But we could not use it:-(

regards
KRS

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

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


From do-not-reply at jboss.com  Wed Apr  8 06:57:13 2009
From: do-not-reply at jboss.com (PedroSena)
Date: Wed, 8 Apr 2009 06:57:13 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS with JBoss Embedded
Message-ID: <27119988.1239188233017.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi Ted,

Did it work? I'm facing the same problem here. 

Regards,

Pedro Sena

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

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


From do-not-reply at jboss.com  Wed Apr  8 07:08:58 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Wed, 8 Apr 2009 07:08:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: how to use jaxws offline
Message-ID: <17970357.1239188939053.JavaMail.jboss@colo-br-02.atl.jboss.com>

The fix will be available in next JBossWS 3.1.1 release (end of this month).

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

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


From do-not-reply at jboss.com  Wed Apr  8 07:36:15 2009
From: do-not-reply at jboss.com (derarne)
Date: Wed, 8 Apr 2009 07:36:15 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: how to use jaxws offline
Message-ID: <20948519.1239190575698.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thanks Richard. I'll try it than.

Yours 
 Arne

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

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


From do-not-reply at jboss.com  Wed Apr  8 09:10:30 2009
From: do-not-reply at jboss.com (joncmuniz)
Date: Wed, 8 Apr 2009 09:10:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: error with wssecurity!!!!
Message-ID: <10541002.1239196230467.JavaMail.jboss@colo-br-02.atl.jboss.com>

	
someone to help?

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

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


From do-not-reply at jboss.com  Wed Apr  8 10:10:45 2009
From: do-not-reply at jboss.com (roberto)
Date: Wed, 8 Apr 2009 10:10:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Another issue with JBOSS WS and
	inheritance
Message-ID: <30641095.1239199845282.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi

I have an issue using a 3 level java bean as argument of a web service operation.


  | public class A
  | {
  |    protected String iA;
  |    public String getA()
  |    {
  |       return iA;
  |    }
  |    public void setA(String aA)
  |    {
  |       iA = aA;
  |    }
  | }
  | 
  | public class B extends A
  | {
  |    protected String iB;
  |    protected String getB()
  |    {
  |       return iB;
  |    }
  |    protected void setB(String aB)
  |    {
  |       iB = aB;
  |    }
  | }
  | 
  | public class C extends B
  | {
  |    protected String iC;
  |    public String getC()
  |    {
  |       return iC;
  |    }
  |    public void setC(String aC)
  |    {
  |       iC = aC;
  |    }
  | }
  | 

Warning: Class "B" contains protected Field and Method!

I publish a web service (based on a stateless EJB 2.1 session bean) that recieve an object of class "C".

Deploy works fine. I can see the WSDL published and I can parse it from a client.

Now, I'm writing a java client using a Dynamic Invocation Interface Model.

I'm using it to avoid to create proxy classes.... and I don't want to use a wsdl2java tool.

My client create a new instance of "C" and pass it as a parameter of my ws.

But when the client serialize/prepare the SOAP message, it build a wrong message: "A" field is present 2 times!!
I discover that the client (using all jboss jars) work by reflection in order to build the soap message.. but it seems to get 2 times the "A" field (maybe the first time from the class "B" and after from the class "A".

In this way when the server recieve that message, of couse an exception is throws 

I believe this is a bug into dynamic javabean serialization model..
I remove 1 level.. and now all works fine... but maybe in the furure I will need again to use another level.

I'm using JBOSS 5.0.1 GA and also upgrade the JBoss WS to 3.1.0 GA (I try it because maybe this issue was just fixed) and Sun JDK  1.5.0_17-b04

I read on previous post a lot of issue related to inheritance . Maybe this is a new one.

Thanks
Roberto




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

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


From do-not-reply at jboss.com  Wed Apr  8 10:46:04 2009
From: do-not-reply at jboss.com (joncmuniz)
Date: Wed, 8 Apr 2009 10:46:04 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - doubts about the JBOSSWS
Message-ID: <10008008.1239201964932.JavaMail.jboss@colo-br-02.atl.jboss.com>

1-because often I see the same problems in several places, that the libs related to JBoss, to work to take the client lib x and put in endorsed, things like that! when we need something that does not change the place these libs?

2- steps to make security-ws - I followed the links that show how to be made, but I'm still having problems:
http://www.jboss.org/community/docs/DOC-12644
http://www.jboss.org/community/wiki/WSSecurityEncryptExample
http://www.jboss.org/community/wiki/WSSecuritySignExample
http://www.jboss.org/community/wiki/WSSecurityConfig

Things are even simpler as shown in these examples, put the jboss-wsse-server.xml and jboss-wsse-client.xml in their due places, and inform in the webServices EndpointConfig Server @ (configName = "Standard Endpoint WSSecurity"), finally make it as described in steps. 
It is my impression or have gaps in documentation? Such as the client side to call a particular service is only necessary to the xml file and inform the settings below:
System.setProperty("org.jboss.ws.wsse.keyStore", "E:/wsse/wsse.jks" );
system.setProperty("org.jboss.ws.wsse.keyStorePassword", "senha_client" );
System.setProperty("org.jboss.ws.wsse.keyStoreType", "jks" );
System.setProperty("org.jboss.ws.wsse.trustStore", "E:/wsse/wsse.csr" );
System.setProperty("org.jboss.ws.wsse.trustStorePassword", "senha_client" );
System.setProperty("org.jboss.ws.wsse.trustStoreType", "jks" );

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

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


From do-not-reply at jboss.com  Wed Apr  8 11:24:51 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 8 Apr 2009 11:24:51 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: doubts about the JBOSSWS
Message-ID: <4536476.1239204291413.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,
I'm not sure to get what you mean exactly, anyway the documentation you should refer to for WS-Security is the following:

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

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

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


From do-not-reply at jboss.com  Wed Apr  8 12:50:01 2009
From: do-not-reply at jboss.com (joncmuniz)
Date: Wed, 8 Apr 2009 12:50:01 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: doubts about the JBOSSWS
Message-ID: <13815822.1239209401574.JavaMail.jboss@colo-br-02.atl.jboss.com>

hi alessio, you are sure that this documentation is complete. because I did all the steps and my example is in error.

09:51:31,250 ERROR [HandlerChainExecutor] Exception during handler processing
org.jboss.ws.core.CommonSOAPFaultException: This service requires <wsse:Security>, which is missing.
        at org.jboss.ws.extensions.security.WSSecurityDispatcher.convertToFault(WSSecurityDispatcher.java:264)
        at org.jboss.ws.extensions.security.WSSecurityDispatcher.decodeMessage(WSSecurityDispatcher.java:94)
        at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:81)
        at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:39)
        at org.jboss.wsf.common.handler.GenericHandler.handleMessage(GenericHandler.java:53)
        at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:305)
        at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:142)
        at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:97)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:125)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:169)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:474)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
        at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java: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)
09:51:31,250 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
org.jboss.ws.core.CommonSOAPFaultException: This service requires <wsse:Security>, which is missing.
        at org.jboss.ws.extensions.security.WSSecurityDispatcher.convertToFault(WSSecurityDispatcher.java:264)
        at org.jboss.ws.extensions.security.WSSecurityDispatcher.decodeMessage(WSSecurityDispatcher.java:94)
        at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:81)
        at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:39)
        at org.jboss.wsf.common.handler.GenericHandler.handleMessage(GenericHandler.java:53)
        at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:305)
        at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:142)
        at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:97)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:125)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:169)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:474)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
        at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java: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)
09:51:31,250 ERROR [SOAPFaultHelperJAXRPC] SOAP request exception
javax.xml.rpc.soap.SOAPFaultException: This service requires <wsse:Security>, which is missing.
        at org.jboss.ws.core.jaxrpc.SOAPFaultHelperJAXRPC.exceptionToFaultMessage(SOAPFaultHelperJAXRPC.java:189)
        at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:183)
        at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:102)
        at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:671)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:277)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:474)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
        at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java: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)
09:51:31,265 ERROR [CommonClient] Exception caught while (preparing for) performing the invocation:
javax.xml.ws.soap.SOAPFaultException: This service requires <wsse:Security>, which is missing.
        at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:84)
        at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:107)
        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:290)
        at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
        at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
        at $Proxy79.localizacao(Unknown Source)
        at br.teste.client.MyServlet.executa(MyServlet.java:82)
        at br.teste.client.MyServlet.doGet(MyServlet.java:36)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java: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)
09:51:31,265 ERROR [[MyServlet]] Servlet.service() for servlet MyServlet threw exception
javax.xml.ws.soap.SOAPFaultException: This service requires <wsse:Security>, which is missing.
        at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:84)
        at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:107)
        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:290)
        at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
        at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
        at $Proxy79.localizacao(Unknown Source)
        at br.teste.client.MyServlet.executa(MyServlet.java:82)
        at br.teste.client.MyServlet.doGet(MyServlet.java:36)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java: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.org/index.html?module=bb&op=viewtopic&p=4224426#4224426

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


From do-not-reply at jboss.com  Wed Apr  8 13:51:09 2009
From: do-not-reply at jboss.com (jeljo)
Date: Wed, 8 Apr 2009 13:51:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Deployment fails with 1.0.4 - NPE
	in DeployerInterceptor
Message-ID: <5362625.1239213069957.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi Everyone,

I know am replying to an old post here.
But just wanted to list it here for someone who might need help for similar errors that might be caused for a different reason.

While troubeshooting, we stumbled upon similar error that was caused by misconfiguration.

Before fix in all/conf/jboss-service.xml


             deploy,/opt/shared_data/snas/deploy
      



After fix in jboss-service.xml


             deploy/,/opt/shared_data/snas/deploy/
      

If you observe, the comma immediatley after deploy and no "/" after "/opt/shared_data/snas/deploy"  reproduced similar NullPointer Exception

Cheers
Jeljo

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

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


From do-not-reply at jboss.com  Wed Apr  8 15:08:41 2009
From: do-not-reply at jboss.com (bhuwanpatel)
Date: Wed, 8 Apr 2009 15:08:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBoss WS error while throwing fault
	code from method with ze
Message-ID: <7278186.1239217721626.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am using JBoss 4.2.3 (Jboss WS 3.0.3) and have the following method exposed through the web service:

@WebMethod
public @WebResult(name = "id") String start() throws WSException
{
  try 
 {
          .......
          .......
 }
 catch(Exception e)
 {
   throw new WSException (faultCode, "Message : " + e.getMessage());
 }

}


The method takes no parameters as in input and returns a string.
I am throwing a fault code to the client if there is any exception. However, I get the following error on the client side:

<env:Fault>
         env:Server
         java.lang.NullPointerException
</env:Fault>

Following is the stack trace:

15:03:15,794 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
com.neustar.ultra.api.webservice.exception.UltraWSException
        at com.neustar.ultra.api.webservice.UltraWebService.startTransaction(UltraWebService.java:89)
        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.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
        at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
        at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
        at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
        at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:166)
        at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:115)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
        at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
        at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
        at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
        at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
        at org.jboss.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.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
        at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
        at java.lang.Thread.run(Thread.java:595)
15:03:16,216 WARN  [ServiceEndpointInvoker] Exception while processing handleFault:
com.neustar.ultra.api.webservice.exception.UltraWSException
        at com.neustar.ultra.api.webservice.UltraWebService.startTransaction(UltraWebService.java:89)
        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.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
        at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
        at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
        at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
        at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:166)
        at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:115)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
        at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
        at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
        at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
        at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
        at org.jboss.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.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
        at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
        at java.lang.Thread.run(Thread.java:595)
15:03:16,310 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
javax.xml.ws.WebServiceException: java.lang.NullPointerException
        at org.jboss.ws.core.jaxws.JAXBSerializer.handleMarshallException(JAXBSerializer.java:143)
        at org.jboss.ws.core.jaxws.JAXBSerializer.serialize(JAXBSerializer.java:86)
        at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toDetailEntry(SOAPFaultHelperJAXWS.java:352)
        at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:270)
        at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:180)
        at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:102)
        at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:669)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:277)
        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:524)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
        at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
        at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
        at java.util.Arrays$ArrayList.(Arrays.java:2355)
        at java.util.Arrays.asList(Arrays.java:2341)
        at org.jboss.ws.core.jaxws.JAXBSerializer.getClassesForContextCreation(JAXBSerializer.java:108)
        at org.jboss.ws.core.jaxws.JAXBSerializer.serialize(JAXBSerializer.java:68)
        ... 31 more



When I add one parameter to the method, everything works fine and the method throws the fault code appropriately.

Is this a bug or am I missing something?? 

I also found another bug and suspect that this one is related to it:
https://jira.jboss.org/jira/browse/JBWS-806

Thanks,
Bhuwan.


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

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


From do-not-reply at jboss.com  Wed Apr  8 15:18:46 2009
From: do-not-reply at jboss.com (joncmuniz)
Date: Wed, 8 Apr 2009 15:18:46 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: doubts about the JBOSSWS
Message-ID: <14614852.1239218326207.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi, I added this bit of code in my client:
((StubExt) s).setConfigName("Standard WSSecurity Client");
The error has change:
15:58:35,375 INFO  [Reference] Verification successful for URI "#element-7-1239217115328-33467208"
15:58:35,375 INFO  [Reference] Verification successful for URI "#timestamp"
15:58:35,375 ERROR [WSSecurityDispatcher] Internal error occured handling inbound message:
org.jboss.ws.extensions.security.exception.FailedCheckException: Required elements for encryption and or signing are not all present.
        at org.jboss.ws.extensions.security.operation.RequireTargetableOperation.process(RequireTargetableOperation.java:96)
        at org.jboss.ws.extensions.security.SecurityDecoder.verify(SecurityDecoder.java:180)
        at org.jboss.ws.extensions.security.WSSecurityDispatcher.decodeHeader(WSSecurityDispatcher.java:140)
        at org.jboss.ws.extensions.security.WSSecurityDispatcher.decodeMessage(WSSecurityDispatcher.java:101)
        at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:81)
        at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:39)
        at org.jboss.wsf.common.handler.GenericHandler.handleMessage(GenericHandler.java:53)
        at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:305)
        at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:142)
        at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:97)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:125)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:169)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:474)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
        at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java: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)
15:58:35,437 ERROR [HandlerChainExecutor] Exception during handler processing
org.jboss.ws.core.CommonSOAPFaultException: Required elements for encryption and or signing are not all present.
        at org.jboss.ws.extensions.security.WSSecurityDispatcher.convertToFault(WSSecurityDispatcher.java:264)
        at org.jboss.ws.extensions.security.WSSecurityDispatcher.decodeMessage(WSSecurityDispatcher.java:113)
        at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:81)
        at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:39)
        at org.jboss.wsf.common.handler.GenericHandler.handleMessage(GenericHandler.java:53)
        at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:305)
        at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:142)
        at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:97)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:125)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:169)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:474)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
        at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java: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)
15:58:35,500 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
org.jboss.ws.core.CommonSOAPFaultException: Required elements for encryption and or signing are not all present.
        at org.jboss.ws.extensions.security.WSSecurityDispatcher.convertToFault(WSSecurityDispatcher.java:264)
        at org.jboss.ws.extensions.security.WSSecurityDispatcher.decodeMessage(WSSecurityDispatcher.java:113)
        at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:81)
        at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:39)
        at org.jboss.wsf.common.handler.GenericHandler.handleMessage(GenericHandler.java:53)
        at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:305)
        at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:142)
        at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:97)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:125)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:169)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:474)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
        at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java: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)
15:58:35,562 ERROR [SOAPFaultHelperJAXRPC] SOAP request exception
javax.xml.rpc.soap.SOAPFaultException: Required elements for encryption and or signing are not all present.
        at org.jboss.ws.core.jaxrpc.SOAPFaultHelperJAXRPC.exceptionToFaultMessage(SOAPFaultHelperJAXRPC.java:189)
        at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:183)
        at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:102)
        at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:671)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:277)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:474)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
        at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java: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)
15:58:35,625 ERROR [CommonClient] Exception caught while (preparing for) performing the invocation:
javax.xml.ws.soap.SOAPFaultException: Required elements for encryption and or signing are not all present.
        at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:84)
        at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:107)
        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:290)
        at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
        at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
        at $Proxy84.localizacao(Unknown Source)
        at br.teste.client.MyServlet.executa(MyServlet.java:88)
        at br.teste.client.MyServlet.doGet(MyServlet.java:38)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java: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)
15:58:35,671 ERROR [[MyServlet]] Servlet.service() for servlet MyServlet threw exception
javax.xml.ws.soap.SOAPFaultException: Required elements for encryption and or signing are not all present.
        at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:84)
        at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:107)
        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:290)
        at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
        at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
        at $Proxy84.localizacao(Unknown Source)
        at br.teste.client.MyServlet.executa(MyServlet.java:88)
        at br.teste.client.MyServlet.doGet(MyServlet.java:38)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java: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.org/index.html?module=bb&op=viewtopic&p=4224470#4224470

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


From do-not-reply at jboss.com  Thu Apr  9 08:19:47 2009
From: do-not-reply at jboss.com (joncmuniz)
Date: Thu, 9 Apr 2009 08:19:47 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - how to configure the client side?
Message-ID: <17062058.1239279587153.JavaMail.jboss@colo-br-02.atl.jboss.com>

I'm calling my Webservices sample from a servlet and put the settings in several places:
	
jboss-wsse-client.xml goes on within the web-inf
<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>E:\wsse\wsse.jks</key-store-file>
  <key-store-password>senha_client</key-store-password>
  <trust-store-file>E:\wsse\wsse.csr</trust-store-file>
  <trust-store-password>senha_client</trust-store-password>
  
      
      
      
      
      
  
    
    
      
     





</jboss-ws-security>


in code
protected void executa() {

System.setProperty("org.jboss.ws.wsse.keyStore", "E:/wsse/wsse.jks" );
System.setProperty("org.jboss.ws.wsse.keyStorePassword", "senha_client" );
System.setProperty("org.jboss.ws.wsse.keyStoreType", "jks" );
System.setProperty("org.jboss.ws.wsse.trustStore", "E:/wsse/wsse.csr" );
System.setProperty("org.jboss.ws.wsse.trustStorePassword", "senha_client" );
System.setProperty("org.jboss.ws.wsse.trustStoreType", "jks" );
QName qName = new QName("http://coreo.com.br/teste", "Teste");
String serviceURL = "http://jon.ctbc.com.br:8080/jbossWebServiceSecurity-1.0.0/Teste?wsdl";
Service service = null;
URL url;
url = new URL(serviceURL);
service = Service.create(url,qName);
ITeste s = service.getPort(ITeste.class);
((StubExt) s).setConfigName("Standard WSSecurity Client");
((BindingProvider) s).getRequestContext().put("org.jboss.ws.wsse.keyStore", "e:\\wsse\\wsse.jks");
((BindingProvider) s).getRequestContext().put("org.jboss.ws.wsse.keyStorePassword", "senha_client");
((BindingProvider) s).getRequestContext().put("org.jboss.ws.wsse.keyStoreType", "jks");
((BindingProvider) s).getRequestContext().put("org.jboss.ws.wsse.trustStore", "E:\\wsse\\wsse.csr");
((BindingProvider) s).getRequestContext().put("org.jboss.ws.wsse.trustStorePassword", "senha_client");
((BindingProvider) s).getRequestContext().put("org.jboss.ws.wsse.trustStoreType", "jks");

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

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


From do-not-reply at jboss.com  Thu Apr  9 08:25:50 2009
From: do-not-reply at jboss.com (joncmuniz)
Date: Thu, 9 Apr 2009 08:25:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: how to configure the client side?
Message-ID: <2305125.1239279950754.JavaMail.jboss@colo-br-02.atl.jboss.com>

sorry was very messy

I'm calling my Webservices sample from a servlet and put the settings in several places:

jboss-wsse-client.xml goes on within the web-inf

<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>E:\wsse\wsse.jks</key-store-file>
<key-store-password>senha_client</key-store-password>
<trust-store-file>E:\wsse\wsse.csr</trust-store-file>
<trust-store-password>senha_client</trust-store-password>
</jboss-ws-security>
in code

  | protected void executa() {
  | 
  | System.setProperty("org.jboss.ws.wsse.keyStore", "E:/wsse/wsse.jks" );
  | System.setProperty("org.jboss.ws.wsse.keyStorePassword", "senha_client" );
  | System.setProperty("org.jboss.ws.wsse.keyStoreType", "jks" );
  | System.setProperty("org.jboss.ws.wsse.trustStore", "E:/wsse/wsse.csr" );
  | System.setProperty("org.jboss.ws.wsse.trustStorePassword", "senha_client" );
  | System.setProperty("org.jboss.ws.wsse.trustStoreType", "jks" );
  | QName qName = new QName("http://coreo.com.br/teste", "Teste");
  | String serviceURL = "http://jon.ctbc.com.br:8080/jbossWebServiceSecurity-1.0.0/Teste?wsdl";
  | Service service = null;
  | URL url;
  | url = new URL(serviceURL);
  | service = Service.create(url,qName);
  | ITeste s = service.getPort(ITeste.class);
  | ((StubExt) s).setConfigName("Standard WSSecurity Client");
  | ((BindingProvider) s).getRequestContext().put("org.jboss.ws.wsse.keyStore", "e:\\wsse\\wsse.jks");
  | ((BindingProvider) s).getRequestContext().put("org.jboss.ws.wsse.keyStorePassword", "senha_client");
  | ((BindingProvider) s).getRequestContext().put("org.jboss.ws.wsse.keyStoreType", "jks");
  | ((BindingProvider) s).getRequestContext().put("org.jboss.ws.wsse.trustStore", "E:\\wsse\\wsse.csr");
  | ((BindingProvider) s).getRequestContext().put("org.jboss.ws.wsse.trustStorePassword", "senha_client");
  | ((BindingProvider) s).getRequestContext().put("org.jboss.ws.wsse.trustStoreType", "jks");

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

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


From do-not-reply at jboss.com  Thu Apr  9 08:26:23 2009
From: do-not-reply at jboss.com (m.a.g)
Date: Thu, 9 Apr 2009 08:26:23 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS JAX-WS question using
	stateful
Message-ID: <365631.1239279983207.JavaMail.jboss@colo-br-02.atl.jboss.com>

"alessio.soldano at jboss.com" wrote : @javax.xml.ws.soap.Addressing will be supported starting from JBossWS-Native 3.1.0.GA, that's scheduled for the end of February 2009.

JBossWS-Native 3.1.0.GA released. Is @javax.xml.ws.soap.Addressing supported in JBossWS-Native 3.1.0.GA

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

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


From do-not-reply at jboss.com  Thu Apr  9 09:42:02 2009
From: do-not-reply at jboss.com (m.a.g)
Date: Thu, 9 Apr 2009 09:42:02 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Statefull web service: how to configure
	inactivity timeout (
Message-ID: <14653222.1239284522575.JavaMail.jboss@colo-br-02.atl.jboss.com>

1) How statefull WS instances are released?
2) How to perform custom actions (close resources) on statefull WS destroy?
3) I know how to configure HTTP session timeout for web server but I don't know how to configure inactivity timeout for statefull WS. How can I do it? I would like to note that statefull WS can't be implemented as SFSB.

I'm going to use JBoss5 with JBossWS Native 3.0.5.GA to implement statefull web service. I need statefull, because WS creates personified RMI session to third-party server for each WS client. I found an example how to use WS-Addressing to create statefull WS, but I don't understand some aspects.


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

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


From do-not-reply at jboss.com  Fri Apr 10 11:46:05 2009
From: do-not-reply at jboss.com (bhuwanpatel)
Date: Fri, 10 Apr 2009 11:46:05 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBoss WS error while throwing fault
	code from method with ze
Message-ID: <5423593.1239378365232.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am using JBoss 4.2.3 (Jboss WS 3.0.3) and have the following method exposed through the web service:

@WebMethod
public @WebResult(name = "id") String start() throws WSException
{
try
{
.......
.......
}
catch(Exception e)
{
throw new WSException (faultCode, "Message : " + e.getMessage());
}

}


The method takes no parameters as in input and returns a string.
I am throwing a fault code to the client if there is any exception. However, I get the following error on the client side:

<env:Fault>
env:Server
java.lang.NullPointerException
</env:Fault>

Following is the stack trace on the server side:

15:03:15,794 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
com.neustar.ultra.api.webservice.exception.UltraWSException
at com.neustar.ultra.api.webservice.UltraWebService.startTransaction(UltraWebService.java:89)
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.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:166)
at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:115)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.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.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:595)
15:03:16,216 WARN [ServiceEndpointInvoker] Exception while processing handleFault:
com.neustar.ultra.api.webservice.exception.UltraWSException
at com.neustar.ultra.api.webservice.UltraWebService.startTransaction(UltraWebService.java:89)
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.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:166)
at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:115)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.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.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:595)
15:03:16,310 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
javax.xml.ws.WebServiceException: java.lang.NullPointerException
at org.jboss.ws.core.jaxws.JAXBSerializer.handleMarshallException(JAXBSerializer.java:143)
at org.jboss.ws.core.jaxws.JAXBSerializer.serialize(JAXBSerializer.java:86)
at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toDetailEntry(SOAPFaultHelperJAXWS.java:352)
at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:270)
at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:180)
at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:102)
at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:669)
at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:277)
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:524)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
at java.util.Arrays$ArrayList.(Arrays.java:2355)
at java.util.Arrays.asList(Arrays.java:2341)
at org.jboss.ws.core.jaxws.JAXBSerializer.getClassesForContextCreation(JAXBSerializer.java:108)
at org.jboss.ws.core.jaxws.JAXBSerializer.serialize(JAXBSerializer.java:68)
... 31 more



When I add one parameter to the method, everything works fine and the method throws the fault code appropriately:

public @WebResult(name = "id") String start(@WebParam(name = "param1") String param1) throws WSException


Is this a bug in JBoss WS or am I missing something??

I also found another bug and suspect that this one is related to it:
https://jira.jboss.org/jira/browse/JBWS-806

Thanks,
Bhuwan. 

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

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


From do-not-reply at jboss.com  Sun Apr 12 23:05:30 2009
From: do-not-reply at jboss.com (FuinhaAzul)
Date: Sun, 12 Apr 2009 23:05:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - malformed ut-8 character when
	generating clitn web service
Message-ID: <17533037.1239591930031.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have tried to search the web to find some answer about the exported wsdl by jboss when we use the wsdLocation property in @WebService annotation.


My problem is when i try to use some tool to generate web service client ( like eclipse axis client or soapui) they point the error:

Error importing wsdl: java.io.CharConvertionException: Malformed UTF-8 character: 0xe7 0xf5 0x65.


After some testes I found the problem on the import clause of XML Schema on the wsdl. When i remove the "?wsdl&resource= ..." all start to work again.

Any suggestions? Looks like the "&amp;" html character are blocking theses tools...

 

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

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


From do-not-reply at jboss.com  Sun Apr 12 23:18:00 2009
From: do-not-reply at jboss.com (FuinhaAzul)
Date: Sun, 12 Apr 2009 23:18:00 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: malformed ut-8 character when
	generating clitn web servi
Message-ID: <18859352.1239592680416.JavaMail.jboss@colo-br-02.atl.jboss.com>

Sorry :

I'm running Jboss 4.2.3 on windows vista.  
Thanks!

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

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


From do-not-reply at jboss.com  Sun Apr 12 23:38:13 2009
From: do-not-reply at jboss.com (FuinhaAzul)
Date: Sun, 12 Apr 2009 23:38:13 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: malformed ut-8 character when
	generating clitn web servi
Message-ID: <14506029.1239593893598.JavaMail.jboss@colo-br-02.atl.jboss.com>

Problem solved. (for now at least) ... One of my sub-imported schemas has used one non utf-8 character ("??"). I will see how to handle this, because I will need a nice doc. about the schemas.


Thanks anyway!

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

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


From do-not-reply at jboss.com  Mon Apr 13 00:06:13 2009
From: do-not-reply at jboss.com (FuinhaAzul)
Date: Mon, 13 Apr 2009 00:06:13 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Schema Validation - Failed to read
	schema document
Message-ID: <20357542.1239595573450.JavaMail.jboss@colo-br-02.atl.jboss.com>

Any notice about thios issue ?  The jira dont have any changes too...

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

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


From do-not-reply at jboss.com  Mon Apr 13 07:01:50 2009
From: do-not-reply at jboss.com (Sancheski)
Date: Mon, 13 Apr 2009 07:01:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: java.lang.ClassCastException:
	org.jboss.ws.core.jaxws.sp
Message-ID: <12325156.1239620510524.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi again, 

Does anyone solve this problem? I am still looking for a solution. I tried what I found in Jboss forums and I did not make it work. 
This is what I get when using my web service client:
Caused by: java.lang.ClassCastException: org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl
  |         at javax.xml.ws.Service.<init>(Service.java:81)
  | 

The only thing I did was upgrade jbossws version from 3.0.4 (it worked perfectly) to 3.1.0

Thanks in advance!



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

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


From do-not-reply at jboss.com  Mon Apr 13 17:55:01 2009
From: do-not-reply at jboss.com (randhawag)
Date: Mon, 13 Apr 2009 17:55:01 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Caused by:
	org.jboss.remoting.CannotConnectException: Can no
Message-ID: <17094164.1239659701858.JavaMail.jboss@colo-br-02.atl.jboss.com>

We are running JBoss 4.3 EAP CP02, on Java 6u7 and running into a connectivity issue. Has anyone encountered this problem? We are using JAX WS 2.* libraries.

C:\wstest\wstest>java -Djava.endorsed.dirs="C:\servers\jboss-eap-4.3.0.GA_CP02\jboss-as\lib\endorsed
" -Dsun.lang.ClassLoader.allowArraySyntax=true com.owa.ws.client.WsTest
Exception in thread "main" java.rmi.RemoteException: Call invocation failed; nested exception is:
        java.io.IOException: Could not transmit message
        at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:536)
        at org.jboss.ws.core.jaxrpc.client.CallImpl.invoke(CallImpl.java:277)
        at org.jboss.ws.core.jaxrpc.client.PortProxy.invoke(PortProxy.java:156)
        at $Proxy0.sayHello(Unknown Source)
        at com.owa.ws.client.WsTest.main(WsTest.java:33)
Caused by: java.io.IOException: Could not transmit message
        at org.jboss.ws.core.client.RemotingConnectionImpl.invoke(RemotingConnectionImpl.java:210)
        at org.jboss.ws.core.client.SOAPRemotingConnection.invoke(SOAPRemotingConnection.java:77)
        at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:337)
        at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:517)
        ... 4 more
Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker. Connectio
n refused: connect.
        at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoke
r.java:348)
        at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:137)

        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.Client.invoke(Client.java:1634)
        at org.jboss.remoting.Client.invoke(Client.java:548)
        at org.jboss.ws.core.client.RemotingConnectionImpl.invoke(RemotingConnectionImpl.java:189)
        ... 7 more
Caused by: java.net.ConnectException: Connection refused: connect
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
        at java.net.Socket.connect(Socket.java:519)
        at sun.net.NetworkClient.doConnect(NetworkClient.java:152)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:394)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:529)
        at sun.net.www.http.HttpClient.(HttpClient.java:233)
        at sun.net.www.http.HttpClient.New(HttpClient.java:306)
        at sun.net.www.http.HttpClient.New(HttpClient.java:323)
        at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:788)
        at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:729)
        at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:654)
        at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:832)
        at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoke
r.java:277)
        ... 12 more

C:\wstest\wstest>echo "Test completed"
"Test completed"

C:\wstest\wstest>

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

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


From do-not-reply at jboss.com  Tue Apr 14 01:22:06 2009
From: do-not-reply at jboss.com (ravikb_jboss)
Date: Tue, 14 Apr 2009 01:22:06 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WS Security - Identity propagation
	between web services.
Message-ID: <17497764.1239686526031.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I have  two WebServices with EJB Endpoints. (EJBWS1 and WJBWS2). Both are secure web services and the methods in those web services has restricted access by specifying the roles using &RolesAllowed annotation.

For example:

@RolesAllowed("Role1")
public String method1(){}

EJBWS1 is configured to receive the user credentials using WS-Security - User name token (using @EndpointConfig) and EJB2WS is configured to receive credentials using Basic authentication.

Both EJB's are in the same security Domain and also in the same JAR file.

I wrote a client to pass WS-Security credentials to EJBWS1 and it works. In EJBWS1, I called a method in EJBWS2 using EJB way (got a EJB object reference and invoke operation). Identity get propagated and the method call in EJBWS2 gets invoked.

But when i invoke the same using webservice way, i.e in EJBWS1 method, i get a webserviceref (static proxy) for EJJBWS2, get port and invoke operation, i am getting unauthorized error. Identity is not getting propagated from Webservice1 to web service 2

does identity propagation concept not exist in webservice invocations? or am i making any mistake here?

Appreciate your help.

I have included the code in the note:
Thanks in advance
Ravi.


NOTE:
My code for invoking webservice is as follows:
1) Invoking EJBWS 2:

       @WebServiceRef
   static TestBean1WSClient service3;
public void insert(Agent object) {
....

 TestBean1Local tblocal = service3.getEndpointPort();
  tblocal.insert(object);
}
2) 

Created a WebService client using @WebServiceClient annotation:
@WebServiceClient(name = "TestBean1Service", targetNamespace = "http://service.ri.com/", wsdlLocation = "META-INF/wsdl/TestBean1Bean.wsdl")
public class TestBean1WSClient extends Service
{

    private final static URL WSDL_LOCATION;
    private final static QName TESTENDPOINTSERVICE = new QName("http://service.ri.com/", "TestBean1Service");
    private final static QName TESTENDPOINTPORT = new QName("http://service.ri.com/", "TestBean1BeanPort");

    static {
        System.out.println("TestBean1WSClient static block");
        URL url = null;
        try {
                  URL baseUrl = com.hex.ffm.ri.service.TestBean1Local.class.getResource(".");
                  System.out.println(" baseURL "+baseUrl);
            url = new URL("http://127.0.0.1:7000/Practice/TestBean1Bean?wsdl");
        } catch (MalformedURLException e) {
            e.printStackTrace();
        }
        WSDL_LOCATION = url;
    }

   public TestBean1WSClient(URL wsdlLocation, QName serviceName) {
      
        super(wsdlLocation, serviceName);
    
    }

    public TestBean1WSClient() {
        super(WSDL_LOCATION, TESTENDPOINTSERVICE);

    }

    
    @WebEndpoint(name = "TestBean1BeanPort")
    public TestBean1Local getEndpointPort() {
        return (TestBean1Local)super.getPort(TESTENDPOINTPORT, TestBean1Local.class);
    }

}



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

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


From do-not-reply at jboss.com  Tue Apr 14 08:15:44 2009
From: do-not-reply at jboss.com (joncmuniz)
Date: Tue, 14 Apr 2009 08:15:44 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS Security - Identity propagation
	between web services.
Message-ID: <19624750.1239711344746.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi, I can not answer your question!
Because it is a necessity that we have here in my company too! I am studying a way to use OpenSSO in this environment to be my server identity! So is he who knows who has access to the webservices, you need log on again, these things.

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

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


From do-not-reply at jboss.com  Tue Apr 14 18:40:45 2009
From: do-not-reply at jboss.com (zurchman)
Date: Tue, 14 Apr 2009 18:40:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - SSL Client truststore
Message-ID: <1720619.1239748845667.JavaMail.jboss@colo-br-02.atl.jboss.com>

Is there any way to way to dynamically define a JBossWS client truststore?

I'm trying to run a standalone secure webservice client that was originally developed using a JAX-WS RI.

Using the RI, it was a simple matter to specify the truststore:


  | System.setProperty("javax.net.ssl.trustStore",  "path_to_my_store");
  | 

I've rebuilt the artifacts and application against the jbossesb-server-4.5.GA and do not seem to be able to get the client to connect to a secure endpoint.
http endpoints work fine.

Using JBossWS, I seem to get farther setting the "org.jboss.ws.wsse.trustStore" property.

The client was built from a WSDL file, and the endpoint is changed dynamically:


  | BindingProvider bp = (BindingProvider) default_webservice;
  | Map<String, Object> context = bp.getRequestContext();
  | Object oldAddress = context.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, endpoint);
  | System.out.println("new endpoint: " + endpoint);
  | 
The application fails parsing the Web service response, and I question if the request is actually connecting to service provider's SSL port.


  | 2009-04-13 18:33:16,747 DEBUG [org.jboss.ws.core.EndpointInvocation] transformPayloadValue: com.autowares.ipotest.Quote -> com.autowares.ipotest.Quote
  | 2009-04-13 18:33:16,785 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler executor: []
  | 2009-04-13 18:33:16,785 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler executor: []
  | 2009-04-13 18:33:16,785 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler executor: []
  | 2009-04-13 18:33:16,836 DEBUG [org.jboss.ws.core.client.HTTPRemotingConnection] Get locator for: [addr=https://service-provider-url/service-name,etc
  | name={javax.xml.ws.service.endpoint.address=https://service-provider-name/service}]
  | 2009-04-13 18:33:16,933 DEBUG [org.jboss.remoting.security.SSLSocketBuilder] Could not find keystore url.  Can not find store file for url because store url is null.
  | 2009-04-13 18:33:16,965 DEBUG [org.jboss.remoting.MicroRemoteClientInvoker] org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker at 67f39 connecting
  | 2009-04-13 18:33:16,965 DEBUG [org.jboss.remoting.MicroRemoteClientInvoker] org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker at 67f39 connected
  | 2009-04-13 18:33:16,965 DEBUG [org.jboss.ws.core.client.HTTPRemotingConnection] Remoting metadata: {HEADER={SOAPAction="http://qname", Content-Type=text/xml; charset=UTF-8}, NoThrowOnError=true}
  | 2009-04-13 18:33:16,977 DEBUG [org.jboss.ws.core.soap.SOAPContentElement]
  | -----------------------------------
  | 2009-04-13 18:33:16,977 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] Transitioning from OBJECT_VALID to XML_VALID
  | 2009-04-13 18:33:16,977 DEBUG [org.jboss.ws.core.soap.ObjectContent] getXMLFragment from Object [xmlType={http://qname},javaType=class ]
  | 


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

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


From do-not-reply at jboss.com  Wed Apr 15 08:56:34 2009
From: do-not-reply at jboss.com (skajotde)
Date: Wed, 15 Apr 2009 08:56:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS with JBoss Embedded
Message-ID: <31770591.1239800198625.JavaMail.jboss@colo-br-02.atl.jboss.com>

I'm also curious results.

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

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


From do-not-reply at jboss.com  Wed Apr 15 09:23:56 2009
From: do-not-reply at jboss.com (joncmuniz)
Date: Wed, 15 Apr 2009 09:23:56 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - How to configure <application-policy
	name="JBossWS"> to sup
Message-ID: <8487913.1239801839702.JavaMail.jboss@colo-br-02.atl.jboss.com>

How to configure  <application-policy name="JBossWS"> to support LDAP?

The file login-config.xml has a setting where I get User and roles from a file properties (jbossws-roles.properties,jbossws-users.properties), how do I get these users and roles of an LDAP repository?


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

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


From do-not-reply at jboss.com  Wed Apr 15 09:56:39 2009
From: do-not-reply at jboss.com (joncmuniz)
Date: Wed, 15 Apr 2009 09:56:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: How to configure
	<application-policy name=
Message-ID: <15670459.1239803799737.JavaMail.jboss@colo-br-02.atl.jboss.com>

It's very very easy!!!!!!!!!!!!!

  |   <!--
  |       A template configuration for the JBossWS security domain.
  |       This defaults to the UsersRolesLoginModule the same as other and should be
  |       changed to a stronger authentication mechanism as required.
  |     
  |     <application-policy name="JBossWS">
  |       <authentication>
  |         <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule"
  |           flag="required">
  |           <module-option name="usersProperties">props/jbossws-users.properties</module-option>
  |           <module-option name="rolesProperties">props/jbossws-roles.properties</module-option>
  |           <module-option name="unauthenticatedIdentity">anonymous</module-option>
  |         </login-module>
  |       </authentication>
  |     </application-policy>
  | -->
  | 
CHANGE FOR THIS ----------

  | <application-policy name="JBossWS">
  |     <authentication>
  |         <login-module code="org.jboss.security.auth.spi.LdapLoginModule"
  |                       flag="required">
  |             <module-option name="java.naming.factory.initial">
  |                 com.sun.jndi.ldap.LdapCtxFactory
  |             </module-option>
  |             <module-option name="java.naming.provider.url">
  |                 ldap://YOUR IP:PORT LDAP/
  |             </module-option>
  |             <module-option name="java.naming.security.authentication">
  |                 simple
  |             </module-option>
  |             <module-option name="principalDNPrefix">uid=</module-option>
  |             <module-option name="principalDNSuffix">
  |                 ,ou=users,dc=cds,dc=com
  |             </module-option>
  | 
  |             <module-option name="rolesCtxDN">
  |                 ou=groups,dc=cds,dc=com
  |             </module-option>
  |             <module-option name="uidAttributeID">member</module-option>
  |             <module-option name="matchOnUserDN">true</module-option>
  | 
  |             <module-option name="roleAttributeID">cn</module-option>
  |             <module-option name="roleAttributeIsDN">false </module-option>
  |         </login-module>
  |     </authentication>
  | </application-policy>    
  | 

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

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


From do-not-reply at jboss.com  Wed Apr 15 20:45:40 2009
From: do-not-reply at jboss.com (zurchman)
Date: Wed, 15 Apr 2009 20:45:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: SSL Client truststore
Message-ID: <22830296.1239842740084.JavaMail.jboss@colo-br-02.atl.jboss.com>

Here's what it took to run a JAX-WS RI SSL client with the JBossWS 3.0.1-native-2.0.4.GA delivered with jbossesb-server-4.5.GA.

The post that made the difference was the one by Alessio at the end of this topic: 

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

I don't recommend doing it this way, but all the artifacts were built with the RI.  The only class compiled against the JBoss classes was the service mainline.

1) Set the truststore in the javax.net.ssl.trustStore property

2) Include org.jboss.ws.core.StubExt

3) Set the "Config" name to "Standard WSSecurity Client"


  | 	System.setProperty("javax.net.ssl.trustStore", 
  |   					"path-to-my-truststore");
  | 	BindingProvider bp = (BindingProvider) default_webservice;
  | 	Map<String, Object> context = bp.getRequestContext();
  | 	context.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, 
  |           endpoint);
  | 	System.out.println("new endpoint: " + endpoint);
  | 	((StubExt)default_webservice).setConfigName("Standard WSSecurity Client");
  | 

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

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


From do-not-reply at jboss.com  Thu Apr 16 09:16:01 2009
From: do-not-reply at jboss.com (skajotde)
Date: Thu, 16 Apr 2009 09:16:01 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WebFault and Declared RuntimeException
	is wrapped by SOAPFau
Message-ID: <25065407.1239887761687.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi All !

I'm writing webservice with JBoss 4.2.3 and jbossws-native-3.0.3.GA. When I declare checked exception, client can catch right unbinded exception.

    @WebMethod
  |     public String testWyjatek003(@WebParam(name = "paramString") String paramString) throws WyjatekTestowy,
  |             WyjatekTestowyDziedziczacy;

When I declare runtime exception, exception is right unmarshalled as cause of SOAPFaultException but is not unwrapped.

  |     @WebMethod
  |     public String testWyjatekRuntime005(@WebParam(name = "paramString") String paramString)
  |             throws WyjatekTestowyRuntime02;
  | 
  |     @WebFault
  |     @ApplicationException(rollback = true)
  |     public class WyjatekTestowyRuntime02 extends RuntimeException {
  |         [...]
  |     }
  | 

I was investigating this case and I found ClientProxy.handleException(Exception ex)

   private void handleException(Exception ex) throws Throwable
  |    {
  |       if (ex instanceof SOAPFaultException)
  |       {
  |          // Unwrap the cause if it is an Application Exception, otherwise use a protocol exception
  |          Throwable cause = ex.getCause();
  |          if (cause instanceof Exception)
  |          {
  |             // Throw unwrapped WebServiceException
  |             if (cause instanceof WebServiceException)
  |                throw (WebServiceException)cause;
  | 
  |             // Throw wrapped SOAPException
  |             if (cause instanceof SOAPException)
  |                throw (SOAPFaultException)ex;
  | 
  |             // Throw wrapped RuntimeException
  |             if (cause instanceof RuntimeException)
  |                throw (SOAPFaultException)ex;
  | 
  |             // Throw all other causes
  |             throw (Exception)cause;
  |          }
  |       }
  |       throw ex;
  |    }

So RuntimeException is wrapped with SOAPFaultException. 

Is there way to write transparent code with declaring RuntimException and services with JBossWS ?

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

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


From do-not-reply at jboss.com  Fri Apr 17 05:18:27 2009
From: do-not-reply at jboss.com (vladimirbezugliy)
Date: Fri, 17 Apr 2009 05:18:27 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problems with Jboss and Sun's 1.6
	JDK
Message-ID: <23649133.1239959907922.JavaMail.jboss@colo-br-02.atl.jboss.com>

I had the same problem with jboss-5.0.1.GA and jdk1.5.0_11.
And I just copied jboss-saaj.jar  from jbossws-native-2.0.2.GA(http://www.jboss.org/jbossws/downloads/) package and now all is ok.

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

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


From do-not-reply at jboss.com  Fri Apr 17 05:18:57 2009
From: do-not-reply at jboss.com (jorgemoralespou_2)
Date: Fri, 17 Apr 2009 05:18:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: java.lang.ClassCastException:
	org.jboss.ws.core.jaxws.sp
Message-ID: <30775971.1239959937951.JavaMail.jboss@colo-br-02.atl.jboss.com>

When upgrading to a new version of JBossWS remove all previous JBossWS libraries.
We found that some libraries changed names, so we were not overwriting them. 
These libraries were:

jboss-jaxrpc.jar
jboss-jaxws-ext.jar
jboss-jaxws.jar
jboss-saaj.jar


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

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


From do-not-reply at jboss.com  Fri Apr 17 08:28:36 2009
From: do-not-reply at jboss.com (japase)
Date: Fri, 17 Apr 2009 08:28:36 -0400 (EDT)
Subject: [jbossws-users] =?utf-8?q?=5BJBossWS=5D_-_EJB_injection_doesn?=
 =?utf-8?b?w4PCosOCwoDDgsKZdCB3b3JrIGluIFdlYiBTZXJ2aWNlcyBpbiBKQm9zcyA1?=
 =?utf-8?q?=2E1?=
Message-ID: <25327557.1239971316666.JavaMail.jboss@colo-br-02.atl.jboss.com>

In the EJB3 topic http://www.jboss.org/index.html?module=bb&op=viewtopic&t=153488 I've been told to create a separate topic in this forum regarding one of my problems.

According to JEE 5 specification (http://www.onjava.com/pub/a/onjava/2006/01/04/dependency-injection-java-ee-5.html) EJB injection should work not only in servlets, but also in web services, but it doesn't in JBoss 5.1.x.

Example code for a web service (works in other containers, like GlassFish, WebLogic):


  | @WebService
  | public class Ws2Stateless
  | {
  |    @EJB private StatelessSession sless;
  | 
  |    @WebMethod
  |    public String sayHello( @WebParam(name="yourName") String name )
  |    {
  |       return "Greeting from StatelessSessionBean: " + sless.sayHello(name);
  |    }
  | }
  | 

This example is based on an example from Sun (I can supply a complete example application that shows the problem).


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

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


From do-not-reply at jboss.com  Fri Apr 17 10:00:18 2009
From: do-not-reply at jboss.com (gautamz)
Date: Fri, 17 Apr 2009 10:00:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - org.jboss.ws.WSException: Cannot write
	generated wsdl
Message-ID: <9604131.1239976818846.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello,

I have a wsdl that imports hr-xml elements as below.  I use wsconsume to generate the server interfaces and then implement the interface in my class.  Compiled the code; and created a war
(War has WEB-INF/web.xml.  Classes moved to WEB-INF/classes)
When deploying to jboss, wsdl get emitted and then deployment fails with org.jboss.ws.WSException: Cannot write generated wsdl (more of the stacktrace at the bottom of this post)

Any ideas of what may be happening, and, how to resolve this?  I tried the same through eclipse - and same error.  I'm using JBossAS 4.2.3/jbossws 3.1.1

Thanks!


  | <?xml version="1.0" encoding="UTF-8"?>
  | <wsdl:definitions name="BackgroundCheckService"
  | 	xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:hr="http://ns.hr-xml.org/2007-04-15"
  | 	xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
  | 	xmlns:messages="http://www.testcompany.com/ws/hrxml/Screening/1.0"
  | 	xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.testcompany.com/ws/hrxml/Screening/1.0">
  | 	<wsdl:types>
  | 		<xs:schema attributeFormDefault="qualified"
  | 			elementFormDefault="qualified"
  | 			targetNamespace="http://www.testcompany.com/ws/hrxml/Screening/1.0">
  | 			<xs:import namespace="http://ns.hr-xml.org/2007-04-15"
  | 				schemaLocation="http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/ApplicationAcknowledgement.xsd" />
  | 			<xs:import namespace="http://ns.hr-xml.org/2007-04-15"
  | 				schemaLocation="http://ns.hr-xml.org/2_5/HR-XML-2_5/Screening/US/BackgroundCheck.xsd" />
  | 			<xs:include schemaLocation="CommonServicesTypes.xsd" />
  | 		</xs:schema>
  | 	</wsdl:types>
  | 
  | 	<wsdl:message name="BackgroundCheckRequest">
  | 		<wsdl:part element="hr:BackgroundCheck" name="BackgroundCheckRequest" />
  | 	</wsdl:message>
  | 	<wsdl:message name="Acknowledge">
  | 		<wsdl:part element="hr:ApplicationAcknowledgement" name="Acknowledge" />
  | 	</wsdl:message>
  | 
  | 	<wsdl:portType name="BackgroundCheckPort">
  | 		<wsdl:operation name="CreateBackgroundCheck">
  | 			<wsdl:input message="messages:BackgroundCheckRequest" />
  | 			<wsdl:output message="messages:Acknowledge" />
  | 		</wsdl:operation>
  | 	</wsdl:portType>
  | 
  | 	<wsdl:binding name="BackgroundCheckBinding" type="messages:BackgroundCheckPort">
  | 		<soap:binding style="document"
  | 			transport="http://schemas.xmlsoap.org/soap/http" />
  | 		<wsdl:operation name="CreateBackgroundCheck">
  | 			<soap:operation style="document" soapAction="" />
  | 			<wsdl:input>
  | 				<soap:body use="literal" />
  | 			</wsdl:input>
  | 			<wsdl:output>
  | 				<soap:body use="literal" />
  | 			</wsdl:output>
  | 		</wsdl:operation>
  | 	</wsdl:binding>
  | 
  | 	<wsdl:service name="BackgroundCheckService">
  | 		<wsdl:port binding="messages:BackgroundCheckBinding" name="BackgroundCheckPort">
  | 			<soap:address location="REPLACE_WITH_ACTUAL_URL" />
  | 		</wsdl:port>
  | 	</wsdl:service>
  | </wsdl:definitions>
  | 




  | ERROR [MainDeployer] Could not start deployment: file:/C:/Java/jbos
  | 
  | s-4.2.2.GA/server/default/deploy/backgroundcheckws.war
  | 
  | org.jboss.ws.WSException: Cannot write generated wsdl
  | 
  |         at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.pr
  | 
  | ocessOrGenerateWSDL(JAXWSWebServiceMetaDataBuilder.java:391)
  | 
  |         at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.bu
  | 
  | ildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:158)
  | 
  |         at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupP
  | 
  | roviderOrWebService(JAXWSServerMetaDataBuilder.java:50)
  | 
  |         at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderJSE.buildMeta
  | 
  | Data(JAXWSMetaDataBuilderJSE.java:63)
  | 
  |         at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.create(Unifi
  | 
  | edMetaDataDeploymentAspect.java:66)
  | 
  |         at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy
  | 
  | (DeploymentAspectManagerImpl.java:115)
  | 
  |         at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDep
  | 
  | loyerHook.java:97)
  | 
  |         at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInt
  | 
  | erceptor.java:90)
  | 
  |         at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.
  | 
  | start(SubDeployerInterceptorSupport.java:188)
  | 
  |         at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterce
  | 
  | ptor.java:95)
  | 
  |         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 
  |         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
  | 
  | java:264)
  | 
  |         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 
  |         at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 
  |         at $Proxy45.start(Unknown Source)
  | 
  |         at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
  | 
  |         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
  | 
  |         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
  | 
  |         at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
  | 
  |         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
  | 
  | sorImpl.java:25)
  | 
  |         at java.lang.reflect.Method.invoke(Method.java:585)
  | 
  |         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
  | 
  | er.java:155)
  | 
  |         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 
  |         at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
  | 
  | or.java:133)
  | 
  |         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 
  |         at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
  | 
  | BeanOperationInterceptor.java:142)
  | 
  |         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 
  |         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
  | 
  | java:264)
  | 
  |         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 
  |         at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 
  |         at $Proxy9.deploy(Unknown Source)
  | 
  |         at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
  | 
  | tScanner.java:421)
  | 
  |         at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
  | 
  | canner.java:634)
  | 
  |         at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
  | 
  | doScan(AbstractDeploymentScanner.java:263)
  | 
  |         at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
  | 
  | loop(AbstractDeploymentScanner.java:274)
  | 
  |         at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
  | 
  | run(AbstractDeploymentScanner.java:225)
  | 
  | Caused by: java.io.IOException: org.xml.sax.SAXParseException: The prefix "xml"
  | 
  | cannot be bound to any namespace other than its usual namespace; neither can the
  | 
  |  namespace for "xml" be bound to any prefix other than "xml".
  | 
  |         at org.jboss.wsf.common.DOMUtils.parse(DOMUtils.java:156)
  | 
  |         at org.jboss.wsf.common.DOMUtils.parse(DOMUtils.java:135)
  | 
  |         at org.jboss.ws.tools.wsdl.WSDL11Writer.writeBuilder(WSDL11Writer.java:1
  | 
  | 56)
  | 
  |         at org.jboss.ws.tools.wsdl.WSDL11Writer.write(WSDL11Writer.java:140)
  | 
  |         at org.jboss.ws.tools.wsdl.WSDLWriter.write(WSDLWriter.java:90)
  | 
  |         at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.wr
  | 
  | iteWsdl(JAXWSWebServiceMetaDataBuilder.java:418)
  | 
  |         at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.pr
  | 
  | ocessOrGenerateWSDL(JAXWSWebServiceMetaDataBuilder.java:382)
  | 
  |         ... 35 more
  | 
  | 09:40:53,549 ERROR [RequestHandlerImpl] Error processing web service request
  | 
  | java.lang.IllegalStateException: Cannot obtain endpoint meta data
  | 
  |         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleWSDLRequest(Request
  | 
  | HandlerImpl.java:520)
  | 
  |         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doGet(RequestHandlerImpl.
  | 
  | java:144)
  | 
  |         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(Request
  | 
  | HandlerImpl.java:126)
  | 
  |         at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java
  | 
  | :84)
  | 
  |         at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
  | 
  |         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(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:127)
  | 
  |         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
  | 
  | ava:102)
  | 
  |         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:262)
  | 
  |         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
  | 
  | :844)
  | 
  |         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
  | 
  | ss(Http11Protocol.java:583)
  | 
  |         at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:44
  | 
  | 6)
  | 
  |         at java.lang.Thread.run(Thread.java:595)
  | 
  | 09:40:53,549 ERROR [[BackgroundCheck]] Servlet.service() for servlet BackgroundC
  | 
  | heck threw exception
  | 
  | java.lang.IllegalStateException: Cannot obtain endpoint meta data
  | 
  |         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleWSDLRequest(Request
  | 
  | HandlerImpl.java:520)
  | 
  |         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doGet(RequestHandlerImpl.
  | 
  | java:144)
  | 
  |         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(Request
  | 
  | HandlerImpl.java:126)
  | 
  |         at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java
  | 
  | :84)
  | 
  |         at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
  | 
  |         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(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:127)
  | 
  |         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
  | 
  | ava:102)
  | 
  |         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:262)
  | 
  |         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
  | 
  | :844)
  | 
  |         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
  | 
  | ss(Http11Protocol.java:583)
  | 
  |         at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:44
  | 
  | 6)
  | 
  |         at java.lang.Thread.run(Thread.java:595)
  | 
  | 

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

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


From do-not-reply at jboss.com  Fri Apr 17 10:34:50 2009
From: do-not-reply at jboss.com (ivlcic)
Date: Fri, 17 Apr 2009 10:34:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Specify WS-Security Handler using
	JEE standards
Message-ID: <16101602.1239978890889.JavaMail.jboss@colo-br-02.atl.jboss.com>

I've been looking for the same sollution and found this workaround:

I replaced standard client conf with secure one so everything in your app will be under WS-Security. (If you dont need everything encrypted use the wiki instructions) 

Write your own "endpoint-config" and place it in war 
META-INF/standard-jaxws-endpoint-config.xml:

  | <?xml version="1.0" encoding="UTF-8"?>
  | <jaxws-config	xmlns="urn:jboss:jaxws-config:2.0"
  | 		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  | 		xmlns:javaee="http://java.sun.com/xml/ns/javaee"
  | 		xsi:schemaLocation="urn:jboss:jaxws-config:2.0 jaxws-config_2_0.xsd">
  |   
  | <endpoint-config>
  | 	<config-name>Standard Endpoint</config-name>
  | 	<post-handler-chains>
  | 		<javaee:handler-chain>
  | 			<javaee:protocol-bindings>##SOAP11_HTTP ##SOAP11_HTTP_MTOM</javaee:protocol-bindings>
  | 			<javaee:handler>
  | 				<javaee:handler-name>WSSecurity Handler</javaee:handler-name>
  | 				<javaee:handler-class>org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer</javaee:handler-class>
  | 			</javaee:handler>
  | 			<javaee:handler>
  | 				<javaee:handler-name>Recording Handler</javaee:handler-name>
  | 				<javaee:handler-class>org.jboss.wsf.framework.invocation.RecordingServerHandler</javaee:handler-class>
  | 			</javaee:handler>
  | 			<javaee:handler>
  | 				<!-- YOUR OWN HANDLERS IN POST CHAIN -->
  | 				<javaee:handler-name>Encrypted Request Logger</javaee:handler-name>
  | 				<javaee:handler-class>org.dropchop.mpg.ws.RequestLogger</javaee:handler-class>
  | 			</javaee:handler>
  | 		</javaee:handler-chain>
  | 	</post-handler-chains>
  | </endpoint-config>
  |   
  | </jaxws-config>
  | 


and client side .jar (or just in class path) META-INF/standard-jaxws-client-config.xml:


  | <?xml version="1.0" encoding="UTF-8"?>
  | <jaxws-config xmlns="urn:jboss:jaxws-config:2.0" 
  | 		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  | 		xmlns:javaee="http://java.sun.com/xml/ns/javaee"
  | 		xsi:schemaLocation="urn:jboss:jaxws-config:2.0 jaxws-config_2_0.xsd">
  |   
  | <client-config>
  | 	<config-name>Standard Client</config-name>
  | 	<post-handler-chains>
  | 	  <javaee:handler-chain>
  | 		<javaee:protocol-bindings>##SOAP11_HTTP ##SOAP11_HTTP_MTOM</javaee:protocol-bindings>
  | 		<javaee:handler>
  | 		  <javaee:handler-name>WSSecurityHandlerOutbound</javaee:handler-name>
  | 		  <javaee:handler-class>org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerClient</javaee:handler-class>
  | 		</javaee:handler>
  | 	  </javaee:handler-chain>
  | 	</post-handler-chains>
  | 	<property>
  | 	  <property-name>http://org.jboss.ws/http#chunksize</property-name>
  | 	  <property-value>2048</property-value>
  | 	</property>
  | </client-config>
  | </jaxws-config>
  | 
Your files will be loaded before the ones from jboss libs and you can delete all references to jboss libs from your source code.

I guess its a hack, but in my humble opinion after reading a spec (JAX-WS 2.1), user of native stack should be able to add his(hers) processing logic before SOAP protocol handling. With current jbossws (in AS 5.0.0GA) this is imposible since POST chains are delgated to execution before ENDPOINT.

I tested it so it works for me. (use it at your own risk since I'm not sure its ok)...


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

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


From do-not-reply at jboss.com  Sun Apr 19 10:38:58 2009
From: do-not-reply at jboss.com (MOUAKHARKHALIL)
Date: Sun, 19 Apr 2009 10:38:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - how to weave aspect with a jbossws web
	service ??? HELP PLZ
Message-ID: <20941565.1240151938536.JavaMail.jboss@colo-br-02.atl.jboss.com>

im a student in INSA-LYON FRANCE and i have to realize an aspect weaving in web service to adapt web service for context change...
i used jbossws to deploy my web service...it's OKI
i deployed my interceptor TraceInterceptor in jboss aspect deployer ...it's OKI too
but now my problem that when i consume mymy web service with a client the weaving do not work...
so, how can i do weaving with a web service deployed in jbossws.
plz help me...must i add some think other to work....
HEEEEEEEEEEELLLLLLLLLLLLPPPPPPPPPPPPPP PLZ

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

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


From do-not-reply at jboss.com  Sun Apr 19 17:32:21 2009
From: do-not-reply at jboss.com (alfred.graber@aloba.ch)
Date: Sun, 19 Apr 2009 17:32:21 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Diff. between web.xml and
	web.xml.org?
Message-ID: <21206540.1240176741890.JavaMail.jboss@colo-br-02.atl.jboss.com>

... but the problem is, that the original web.xml is modified - so when i want to use the same (exploded) war (directory) for distribution on a different app-server, it won't work....

Why can't you use the web.xml.org instead and leave the web.xml unchanged??

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

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


From do-not-reply at jboss.com  Fri Apr 24 08:11:13 2009
From: do-not-reply at jboss.com (snair33)
Date: Fri, 24 Apr 2009 08:11:13 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Abstract class as input Parameter
	in WebService
Message-ID: <13057663.1240575073823.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I used SOAP UI (soapui.org) to send the web service requests and following code worked for me


  | 
  | <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://www.searchforce.net/oneplace-ws/services">
  |    <soapenv:Header/>
  |    <soapenv:Body>
  |       <ser:showItem>
  |          <!--Optional:-->
  |          <Item xsi:type="Tower" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  |                <!--Optional:-->
  |                <itemName>Test items</itemName>
  |             </Item>
  |       </ser:showItem>
  |    </soapenv:Body>
  | </soapenv:Envelope>
  | 

This code worked with JBOSS 4.0.5 as well as JBOSS 4.2.3.
I do receive this exception on first try. I think the problem was in setting xsi:type correctly. 

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

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


From do-not-reply at jboss.com  Sun Apr 26 13:00:57 2009
From: do-not-reply at jboss.com (zurchman)
Date: Sun, 26 Apr 2009 13:00:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - http proxy error profile
Message-ID: <6243743.1240765257426.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Does this error profile suggest anything to anyone?

The program sets endpoints dynamically and works correctly with two of four endpoints.  The trace below is from one of the endpoints that fails.

I don't recall seeing the "Squid" message on the endpoints that work.  It appears that the client fails immediately without waiting for a response from the service.

This is the latest JBossWS native stack installed in jboss-4.2.3.GA.

16:45:16,158 TRACE SOAPMessageUnMarshallerHTTP:62 - Read input tream with metadata={Proxy-Connection=[close], Date=[Sun, 26 Apr 2009 20:44:35 GMT], Content-Type=[text/html], NoThrowOnError=true, ResponseCode=501, Content-Length=[1206], Expires=[Sun, 26 Apr 2009 20:44:35 GMT], ResponseCodeMessage=Not Implemented, X-Cache-Lookup=[NONE from [default_router]:3128], X-Squid-Error=[ERR_UNSUP_REQ 0], HEADER={SOAPAction="http://[service_Qname]", Content-Type=text/xml; charset=UTF-8}, Server=[squid/2.5.STABLE9], Mime-Version=[1.0], X-Cache=[MISS from [default_router]]}
  | 16:45:16,174 ERROR CommonClient:404 - Exception caught while preparing for) performing the invocation: 
  | java.io.IOException: Could not transmit message
  | 	at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:265)
  | 	at org.jboss.ws.core.client.SOAPProtocolConnectionHTTP.invoke(SOAPProtocolConnectionHTTP.java:71)
  | 	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:340)
  | 	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:290)
  | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
  | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
  | 	at $Proxy26.quote(Unknown Source)
  | 	at [test_op]([test_program].java:386)
  | 	at ...
  | Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker. Invalid HTTP server response [501] - Not Implemented. Response: Not Implemented/501.
  | 	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:348)
  | 	at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:137)
  | 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
  | 	at org.jboss.remoting.Client.invoke(Client.java:1634)
  | 	at org.jboss.remoting.Client.invoke(Client.java:548)
  | 	at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:243)
  | 	... 9 more
  | Caused by: org.jboss.ws.WSException: Invalid HTTP server response [501] - Not Implemented
  | 	at org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP.read(SOAPMessageUnMarshallerHTTP.java:75)
  | 	at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:518)
  | 	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:307)
  | 	... 14 more
  | 16:45:16,177 DEBUG MessageContextJAXWS:106 - Begin response processing

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

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


From do-not-reply at jboss.com  Mon Apr 27 02:52:59 2009
From: do-not-reply at jboss.com (uannight)
Date: Mon, 27 Apr 2009 02:52:59 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Does not recognize xsd:datetime
Message-ID: <25637006.1240815179471.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I have a webservice with integer,string and Date, the wsdl generate a xsd:datetime but when i am trying to launch the webservice i am having this error.

arguments java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang. String,java.lang.String,java.lang.String,java.util.GregorianCalendar.  The arguments do not match the signature.; nested exception is: 	java.lang.IllegalArgumentException: ComponentManager:getService service alarm service not found!
 
This error is changing the Date by Calendar (both have the same error). If I remove the element with Date or Calendar the webservice is working.

This is the wsdl:

<?xml version="1.0" encoding="UTF-8"?>
  | <wsdl:definitions targetNamespace="http://ws.alarm.services.mmplat" 
  | xmlns:apachesoap="http://xml.apache.org/xml-soap" 
  | xmlns:impl="http://ws.alarm.services.mmplat" 
  | xmlns:intf="http://ws.alarm.services.mmplat" 
  | xmlns:tns2="http://types.alarm.services.mmplat" 
  | xmlns:tns3="http://to.pegasus.db.mmplat" xmlns:tns4="http://types.pegasus.db.mmplat" 
  | xmlns:tns5="http://enumeration.types.alarm.services.mmplat" 
  | xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" 
  | xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org
  | /2001/XMLSchema">
  | <!--WSDL created by Apache Axis version: 1.4
  | Built on Apr 22, 2006 (06:55:48 PDT)-->
  |  <wsdl:types>
  |   <schema targetNamespace="http://types.pegasus.db.mmplat" xmlns="http://www.w3.org/2001/XMLSchema">
  |    <import namespace="http://types.alarm.services.mmplat"/>
  |    <import namespace="http://to.pegasus.db.mmplat"/>
  |    <import namespace="http://enumeration.types.alarm.services.mmplat"/>
  |    <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
  |    <complexType name="GenericType">
  |     <sequence/>
  |    </complexType>
  |    <complexType name="ObjectID">
  |     <sequence>
  |      <element name="objectValue" nillable="true" type="xsd:long"/>
  |      <element name="value" type="xsd:long"/>
  |     </sequence>
  |    </complexType>
  |   </schema>
  |   <schema targetNamespace="http://to.pegasus.db.mmplat" xmlns="http://www.w3.org/2001/XMLSchema">
  |    <import namespace="http://types.alarm.services.mmplat"/>
  |    <import namespace="http://types.pegasus.db.mmplat"/>
  |    <import namespace="http://enumeration.types.alarm.services.mmplat"/>
  |    <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
  |    <complexType name="GenericTO">
  |     <complexContent>
  |      <extension base="tns4:GenericType">
  |       <sequence>
  |        <element name="id" nillable="true" type="tns4:ObjectID"/>
  |       </sequence>
  |      </extension>
  |     </complexContent>
  |    </complexType>
  |   </schema>
  |   <schema targetNamespace="http://enumeration.types.alarm.services.mmplat" xmlns="http://www.w3.org/2001/XMLSchema">
  |    <import namespace="http://types.alarm.services.mmplat"/>
  |    <import namespace="http://types.pegasus.db.mmplat"/>
  |    <import namespace="http://to.pegasus.db.mmplat"/>
  |    <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
  |    <complexType name="StateAlarmType">
  |     <sequence/>
  |    </complexType>
  |    <complexType name="SendType">
  |     <sequence/>
  |    </complexType>
  |   </schema>
  |   <schema targetNamespace="http://types.alarm.services.mmplat" xmlns="http://www.w3.org/2001/XMLSchema">
  |    <import namespace="http://types.pegasus.db.mmplat"/>
  |    <import namespace="http://to.pegasus.db.mmplat"/>
  |    <import namespace="http://enumeration.types.alarm.services.mmplat"/>
  |    <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
  |    <complexType name="AlarmTO">
  |     <complexContent>
  |      <extension base="tns3:GenericTO">
  |       <sequence>
  |        <element name="alarmType" nillable="true" type="xsd:string"/>
  |        <element name="dateCreated" nillable="true" type="xsd:dateTime"/>
  |        <element name="dateOperation" nillable="true" type="xsd:string"/>
  |        <element name="dateSend" nillable="true" type="xsd:dateTime"/>
  |        <element name="dateSent" nillable="true" type="xsd:dateTime"/>
  |        <element name="dateUpdated" nillable="true" type="xsd:dateTime"/>
  |        <element name="descripcion" nillable="true" type="xsd:string"/>
  |        <element name="idTraffic" nillable="true" type="tns4:ObjectID"/>
  |        <element name="msisdn" nillable="true" type="xsd:string"/>
  |        <element name="name" nillable="true" type="xsd:string"/>
  |        <element name="nameCatAlert" nillable="true" type="xsd:string"/>
  |        <element name="operation" nillable="true" type="xsd:string"/>
  |        <element name="reference" nillable="true" type="xsd:string"/>
  |        <element name="serviceID" nillable="true" type="tns4:ObjectID"/>
  |        <element name="state" nillable="true" type="tns5:StateAlarmType"/>
  |        <element name="type" nillable="true" type="tns5:SendType"/>
  |       </sequence>
  |      </extension>
  |     </complexContent>
  |    </complexType>
  |   </schema>
  |  </wsdl:types>
  | 
  |    <wsdl:message name="invokeSMSAlarmResponse">
  | 
  |       <wsdl:part name="invokeSMSAlarmReturn" type="xsd:int"/>
  | 
  |    </wsdl:message>
  | 
  |    <wsdl:message name="invokeSMSAlarmRequest">
  | 
  |       <wsdl:part name="in0" type="xsd:string"/>
  | 
  |       <wsdl:part name="in1" type="xsd:string"/>
  | 
  |       <wsdl:part name="in2" type="xsd:string"/>
  | 
  |       <wsdl:part name="in3" type="xsd:string"/>
  | 
  |       <wsdl:part name="in4" type="xsd:string"/>
  | 
  |       <wsdl:part name="in5" type="xsd:string"/>
  | 
  |       <wsdl:part name="in6" type="xsd:string"/>
  | 
  |       <wsdl:part name="in7" type="xsd:dateTime"/>
  | 
  |    </wsdl:message>
  | 
  |    <wsdl:message name="triggerAlarmResponse">
  | 
  |       <wsdl:part name="triggerAlarmReturn" type="xsd:boolean"/>
  | 
  |    </wsdl:message>
  | 
  |    <wsdl:message name="registerPaymentRequest">
  | 
  |       <wsdl:part name="in0" type="xsd:string"/>
  | 
  |       <wsdl:part name="in1" type="xsd:string"/>
  | 
  |       <wsdl:part name="in2" type="xsd:string"/>
  | 
  |       <wsdl:part name="in3" type="xsd:string"/>
  | 
  |       <wsdl:part name="in4" type="xsd:string"/>
  | 
  |    </wsdl:message>
  | 
  |    <wsdl:message name="pruebaResponse">
  | 
  |    </wsdl:message>
  | 
  |    <wsdl:message name="invokeSMSAlarm2Request">
  | 
  |       <wsdl:part name="in0" type="xsd:string"/>
  | 
  |       <wsdl:part name="in1" type="xsd:string"/>
  | 
  |       <wsdl:part name="in2" type="xsd:string"/>
  | 
  |       <wsdl:part name="in3" type="xsd:string"/>
  | 
  |       <wsdl:part name="in4" type="xsd:string"/>
  | 
  |       <wsdl:part name="in5" type="xsd:string"/>
  | 
  |       <wsdl:part name="in6" type="xsd:string"/>
  | 
  |    </wsdl:message>
  | 
  |    <wsdl:message name="prueba2Request">
  | 
  |       <wsdl:part name="in0" type="xsd:int"/>
  | 
  |    </wsdl:message>
  | 
  |    <wsdl:message name="pruebaRequest">
  | 
  |    </wsdl:message>
  | 
  |    <wsdl:message name="registerPaymentResponse">
  | 
  |    </wsdl:message>
  | 
  |    <wsdl:message name="invokeSMSAlarm2Response">
  | 
  |       <wsdl:part name="invokeSMSAlarm2Return" type="xsd:int"/>
  | 
  |    </wsdl:message>
  | 
  |    <wsdl:message name="prueba2Response">
  | 
  |    </wsdl:message>
  | 
  |    <wsdl:message name="triggerAlarmRequest">
  | 
  |       <wsdl:part name="in0" type="tns2:AlarmTO"/>
  | 
  |    </wsdl:message>
  | 
  |    <wsdl:portType name="AlarmService">
  | 
  |       <wsdl:operation name="prueba">
  | 
  |          <wsdl:input message="impl:pruebaRequest" name="pruebaRequest"/>
  | 
  |          <wsdl:output message="impl:pruebaResponse" name="pruebaResponse"/>
  | 
  |       </wsdl:operation>
  | 
  |       <wsdl:operation name="prueba2" parameterOrder="in0">
  | 
  |          <wsdl:input message="impl:prueba2Request" name="prueba2Request"/>
  | 
  |          <wsdl:output message="impl:prueba2Response" name="prueba2Response"/>
  | 
  |       </wsdl:operation>
  | 
  |       <wsdl:operation name="triggerAlarm" parameterOrder="in0">
  | 
  |          <wsdl:input message="impl:triggerAlarmRequest" name="triggerAlarmRequest"/>
  | 
  |          <wsdl:output message="impl:triggerAlarmResponse" name="triggerAlarmResponse"/>
  | 
  |       </wsdl:operation>
  | 
  |       <wsdl:operation name="invokeSMSAlarm" parameterOrder="in0 in1 in2 in3 in4 in5 in6 in7">
  | 
  |          <wsdl:input message="impl:invokeSMSAlarmRequest" name="invokeSMSAlarmRequest"/>
  | 
  |          <wsdl:output message="impl:invokeSMSAlarmResponse" name="invokeSMSAlarmResponse"/>
  | 
  |       </wsdl:operation>
  | 
  |       <wsdl:operation name="invokeSMSAlarm2" parameterOrder="in0 in1 in2 in3 in4 in5 in6">
  | 
  |          <wsdl:input message="impl:invokeSMSAlarm2Request" name="invokeSMSAlarm2Request"/>
  | 
  |          <wsdl:output message="impl:invokeSMSAlarm2Response" name="invokeSMSAlarm2Response"/>
  | 
  |       </wsdl:operation>
  | 
  |       <wsdl:operation name="registerPayment" parameterOrder="in0 in1 in2 in3 in4">
  | 
  |          <wsdl:input message="impl:registerPaymentRequest" name="registerPaymentRequest"/>
  | 
  |          <wsdl:output message="impl:registerPaymentResponse" name="registerPaymentResponse"/>
  | 
  |       </wsdl:operation>
  | 
  |    </wsdl:portType>
  | 
  |    <wsdl:binding name="AlarmServiceSoapBinding" type="impl:AlarmService">
  | 
  |       <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
  | 
  |       <wsdl:operation name="prueba">
  | 
  |          <wsdlsoap:operation soapAction=""/>
  | 
  |          <wsdl:input name="pruebaRequest">
  | 
  |             <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
  | 
  |          </wsdl:input>
  | 
  |          <wsdl:output name="pruebaResponse">
  | 
  |             <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
  | 
  |          </wsdl:output>
  | 
  |       </wsdl:operation>
  | 
  |       <wsdl:operation name="prueba2">
  | 
  |          <wsdlsoap:operation soapAction=""/>
  | 
  |          <wsdl:input name="prueba2Request">
  | 
  |             <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
  | 
  |          </wsdl:input>
  | 
  |          <wsdl:output name="prueba2Response">
  | 
  |             <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
  | 
  |          </wsdl:output>
  | 
  |       </wsdl:operation>
  | 
  |       <wsdl:operation name="triggerAlarm">
  | 
  |          <wsdlsoap:operation soapAction=""/>
  | 
  |          <wsdl:input name="triggerAlarmRequest">
  | 
  |             <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
  | 
  |          </wsdl:input>
  | 
  |          <wsdl:output name="triggerAlarmResponse">
  | 
  |             <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
  | 
  |          </wsdl:output>
  | 
  |       </wsdl:operation>
  | 
  |       <wsdl:operation name="invokeSMSAlarm">
  | 
  |          <wsdlsoap:operation soapAction=""/>
  | 
  |          <wsdl:input name="invokeSMSAlarmRequest">
  | 
  |             <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
  | 
  |          </wsdl:input>
  | 
  |          <wsdl:output name="invokeSMSAlarmResponse">
  | 
  |             <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
  | 
  |          </wsdl:output>
  | 
  |       </wsdl:operation>
  | 
  |       <wsdl:operation name="invokeSMSAlarm2">
  | 
  |          <wsdlsoap:operation soapAction=""/>
  | 
  |          <wsdl:input name="invokeSMSAlarm2Request">
  | 
  |             <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
  | 
  |          </wsdl:input>
  | 
  |          <wsdl:output name="invokeSMSAlarm2Response">
  | 
  |             <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
  | 
  |          </wsdl:output>
  | 
  |       </wsdl:operation>
  | 
  |       <wsdl:operation name="registerPayment">
  | 
  |          <wsdlsoap:operation soapAction=""/>
  | 
  |          <wsdl:input name="registerPaymentRequest">
  | 
  |             <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
  | 
  |          </wsdl:input>
  | 
  |          <wsdl:output name="registerPaymentResponse">
  | 
  |             <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
  | 
  |          </wsdl:output>
  | 
  |       </wsdl:operation>
  | 
  |    </wsdl:binding>
  | 
  |    <wsdl:service name="AlarmServiceService">
  | 
  |       <wsdl:port binding="impl:AlarmServiceSoapBinding" name="AlarmService">
  | 
  |          <wsdlsoap:address location="http://localhost:8080/services/AlarmService"/>
  | 
  |       </wsdl:port>
  | 
  |    </wsdl:service>
  | 
  | </wsdl:definitions>
  | 


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

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


From do-not-reply at jboss.com  Mon Apr 27 15:13:33 2009
From: do-not-reply at jboss.com (Priyajeet)
Date: Mon, 27 Apr 2009 15:13:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Tool to generate wsdl from a java
	file...
Message-ID: <13807356.1240859613679.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I am trying to find a tool to generate wsdl artifacts from a given java file. This file is a .java file and not it's compiled .class.

I wanted to use wsprovide, but that doesn't take in a java file but rather wants the class. I want to run the tool programatically from a code generator that generates properly annotated java class/interface for web services.

Anyone have an idea of a tool that does this, or can wsprovide/something else be used for this in some way?

Thanks.

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

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


From do-not-reply at jboss.com  Mon Apr 27 21:40:41 2009
From: do-not-reply at jboss.com (hoogenbj)
Date: Mon, 27 Apr 2009 21:40:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - No jboss.xml equivalent for
	@EndpointConfig in JBoss 4.2.3
Message-ID: <12354564.1240882841861.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi Everyone, 
In addition to expanding the JBoss installed base of our product, we want to expand into the SAP NetWeaver 7.1 sphere of influence. Part of the porting exercise involves finding equivalent jboss.xml entries for proprietary JBoss annotations. 
The only annotation I have been unable to find an equivalent for is @EndPointConfig used in some of our EJB3 SLSB-based web services. 
Googling located some hints in the JBossWS JIRA of this having been raised before, but I have been unable to find specifics. Besides, the JIRA site is horribly slow. I also found some reference to config-name in the jboss_4_2.dtd in the docs/dtd subfolder for my JBoss installation, but this appears to be incomplete. After using the hints I found in the dtd, I deployed my application with a config-name element inside the webservices element of jboss.xml. This resulted in deployment errors. Which I expected since the dtd appears to be incomplete. 
Can anyone confirm if this has been raised before and if so, the outcome thereof? 
Having a single codebase for all the platforms our product will run on has obvious advantages... 
I upgraded my JBoss4.2.3 to the latest JBossWS native version - 3.1.1. 
Regards, 
Johan

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

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


From do-not-reply at jboss.com  Tue Apr 28 00:13:45 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Tue, 28 Apr 2009 00:13:45 -0400 (EDT)
Subject: [jbossws-users] =?utf-8?q?=5BJBossWS=5D_-_Re=3A_EJB_injection_do?=
 =?utf-8?b?ZXNuw4PCg8OCwqLDg8KCw4LCgMODwoLDgsKZdCB3b3JrIGluIFdlYiBTZXJ2?=
 =?utf-8?q?ices_in?=
Message-ID: <14587111.1240892025228.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

The fix will be available since JBossAS 5.1.0.GA release, see JBWS-2074 for more info.

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

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


From do-not-reply at jboss.com  Tue Apr 28 00:48:43 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Tue, 28 Apr 2009 00:48:43 -0400 (EDT)
Subject: [jbossws-users] =?utf-8?q?=5BJBossWS=5D_-_Re=3A_EJB_injection_do?=
 =?utf-8?b?ZXNuw4PCg8OCwqLDg8KCw4LCgMODwoLDgsKZdCB3b3JrIGluIFdlYiBTZXJ2?=
 =?utf-8?q?ices_in?=
Message-ID: <27239484.1240894123358.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

"japase" wrote : EJB injection should work not only in servlets, but also in web services, but it doesn't in JBoss 5.1.x.
Which J2EE JCP specification defines this requirement? I can't find it :(

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

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


From do-not-reply at jboss.com  Tue Apr 28 01:16:02 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Tue, 28 Apr 2009 01:16:02 -0400 (EDT)
Subject: [jbossws-users] =?utf-8?q?=5BJBossWS=5D_-_Re=3A_EJB_injection_do?=
 =?utf-8?b?ZXNuw4PCg8OCwqLDg8KCw4LCgMODwoLDgsKZdCB3b3JrIGluIFdlYiBTZXJ2?=
 =?utf-8?q?ices_in?=
Message-ID: <33232138.1240895762124.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Cross reference: JBWS-2634

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

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


From do-not-reply at jboss.com  Tue Apr 28 01:29:47 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Tue, 28 Apr 2009 01:29:47 -0400 (EDT)
Subject: [jbossws-users] =?utf-8?q?=5BJBossWS=5D_-_Re=3A_EJB_injection_do?=
 =?utf-8?b?ZXNuw4PCg8OCwqLDg8KCw4LCgMODwoLDgsKZdCB3b3JrIGluIFdlYiBTZXJ2?=
 =?utf-8?q?ices_in?=
Message-ID: <31394022.1240896587287.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

"japase" wrote : 
  | This example is based on an example from Sun (I can supply a complete example application that shows the problem).
  | 
Could you provide the test case? It would speed up the fixing process ;)

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

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


From do-not-reply at jboss.com  Tue Apr 28 03:42:19 2009
From: do-not-reply at jboss.com (japase)
Date: Tue, 28 Apr 2009 03:42:19 -0400 (EDT)
Subject: [jbossws-users] =?utf-8?q?=5BJBossWS=5D_-_Re=3A_EJB_injection_do?=
 =?utf-8?b?ZXNuw4PCg8OCwoPDg8KCw4LCosODwoPDgsKCw4PCgsOCwoDDg8KDw4LCgsOD?=
 =?utf-8?b?woLDgsKZdCB3b3JrIGluIFdlYg==?=
Message-ID: <18772543.1240904539752.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Sure. I have a test case. Which JBWS shall I attach the file to?

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

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


From do-not-reply at jboss.com  Tue Apr 28 05:24:58 2009
From: do-not-reply at jboss.com (joshua.dev)
Date: Tue, 28 Apr 2009 05:24:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WSConsume does not support JAX-WS 2.1
	with JBossWS 3.0.5 Nat
Message-ID: <16993729.1240910698360.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I upgraded JBoss-WS stack that was in the JBoss AS 4.2.2.GA to JBossWS 3.0.5 Native because the supplied version had issues with deploying WebServices over SSL connectors.

3.0.5 deploys them fine, but I just noticed that WSConsume stopped working using parameters I used with the AS 4.2.2.GA standard JBossWS stack:
wsconsume.bat -k -s src -p dummy.package.ws -t 2.1 -o bin --binding=ws-gen\simple.xjb http://127.0.0.1:8080/dummy-context/TestBean?wsdl
3.0.5 complains that
Error: WSConsume (native) only supports JAX-WS 2.0
How is it possible that the earlier version (the default in AS 4.2.2.GA) supported "--target=2.1" for JAX-WS 2.1 and the newer version does not?

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

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


From do-not-reply at jboss.com  Tue Apr 28 23:58:38 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Tue, 28 Apr 2009 23:58:38 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSConsume does not support JAX-WS
	2.1 with JBossWS 3.0.5
Message-ID: <27814038.1240977518963.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I'd need to double check what was available in AS 4.2.2, I think the -t 2.1 option was later disabled because the implementation of JAX-WS 2.1 was not complete yet.
For sure you can use the 2.1 target starting from JBossWS Native 3.1.0.GA as the JAX-WS 2.1 has been completed there.
Otherwise (if you cant move to AS 4.2.3 which is the oldest target container supported by JBossWS 3.1.0) try with JBossWS-Metro 3.0.5, which already had full JAX-WS 2.1 impl.

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

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


From do-not-reply at jboss.com  Wed Apr 29 02:04:58 2009
From: do-not-reply at jboss.com (jaikiran)
Date: Wed, 29 Apr 2009 02:04:58 -0400 (EDT)
Subject: [jbossws-users] =?utf-8?q?=5BJBossWS=5D_-_Re=3A_EJB_injection_do?=
 =?utf-8?b?ZXNuw4PCg8OCwqLDg8KCw4LCgMODwoLDgsKZdCB3b3JrIGluIFdlYiBTZXJ2?=
 =?utf-8?q?ices_in?=
Message-ID: <16550692.1240985098904.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Please attach it here https://jira.jboss.org/jira/browse/JBWS-2634

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

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


From do-not-reply at jboss.com  Wed Apr 29 02:13:40 2009
From: do-not-reply at jboss.com (joshua.dev)
Date: Wed, 29 Apr 2009 02:13:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WSConsume does not support JAX-WS
	2.1 with JBossWS 3.0.5
Message-ID: <14419544.1240985620798.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Thank you for the answers. I've decided to step back and use JAX-WS 2.0, hopefully integration with external parties won't be a problem.
"alessio.soldano at jboss.com" wrote : I'd need to double check what was available in AS 4.2.2, I think the -t 2.1 option was later disabled because the implementation of JAX-WS 2.1 was not complete yet.
I am sure I used the "-t 2.1" switch on default install of AS 4.2.2.GA.

"alessio.soldano at jboss.com" wrote : For sure you can use the 2.1 target starting from JBossWS Native 3.1.0.GA as the JAX-WS 2.1 has been completed there.
  | Otherwise (if you cant move to AS 4.2.3 which is the oldest target container supported by JBossWS 3.1.0) try with JBossWS-Metro 3.0.5, which already had full JAX-WS 2.1 impl.
I'll probably have to stay with 4.2.2 now, but I'll take the information about working WS 3.1.0 and JAX-WS 2.1 into accound when I'll be considering AS upgrade.

The Metro stack was giving me some problems after deployment, I briefly went through the exceptions' stacks but had no time to figure out what exactly went wrong.

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

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


From do-not-reply at jboss.com  Wed Apr 29 04:00:58 2009
From: do-not-reply at jboss.com (abdujaparov)
Date: Wed, 29 Apr 2009 04:00:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Tutorial web service with eclipse
Message-ID: <61028.1240992058444.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi,
I am new in JBoss5 and in ws could someone suggest me a tutorial to create a web service with eclipse on jboss5?
Thanks, bye bye.

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

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


From do-not-reply at jboss.com  Wed Apr 29 04:47:39 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Wed, 29 Apr 2009 04:47:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Tutorial web service with eclipse
Message-ID: <5311166.1240994859682.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Install JBoss Tools into Eclipse and then follow this tutorial: http://docs.jboss.org/tools/3.0.0.GA/en/ws_ref_guide/html/topdown.html

The JBoss Tools documentation contains many helpful tutorials.

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

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


From do-not-reply at jboss.com  Thu Apr 30 01:06:51 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Thu, 30 Apr 2009 01:06:51 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Tutorial web service with eclipse
Message-ID: <28414793.1241068011887.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

This might be useful too: http://www.jboss.org/community/wiki/JBossWS-SetupYourIDE

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

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


From do-not-reply at jboss.com  Thu Apr 30 08:51:10 2009
From: do-not-reply at jboss.com (jamesjoh)
Date: Thu, 30 Apr 2009 08:51:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Using StubExt.PROPERTY_CLIENT_TIMEOUT
	to control timeout of
Message-ID: <14104089.1241095870429.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I'm using the native jbossws jax-ws 2.0 implementation.  I want to control the timeout on a request I am making to a customer's web service.  After searching I found out about setting the property 

StubExt.PROPERTY_CLIENT_TIMEOUT

on the request context, which I get from my Dispatch object.  I set the timeout to 120 seconds (120000 milliseconds).  Though my request timed out much quicker than the default timeout, it actually took about 5 minutes for it to time out.  The exception thrown said it timed out after "120000ms" but the log entries for the request start & timeout exception are 5 minutes apart.  I dropped it down to 90 seconds and it took roughly 4 minutes to time out.  Is there something magic about this property that the desired timeout is not being honored?  Clearly the property is being used in SOME capacity to control the timeout, it just isn't actually timing out at the desired time.  Does anyone have any insight into why this is?  Thank you in advance for your time.

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

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


From do-not-reply at jboss.com  Thu Apr 30 06:39:48 2009
From: do-not-reply at jboss.com (bartvh)
Date: Thu, 30 Apr 2009 06:39:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WebFault targetNamespace and
	document/literal
Message-ID: <4775490.1241087988931.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

This bug has been reverified on jbossws-native-3.1.1. 

See https://jira.jboss.org/jira/browse/JBWS-2637

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

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


From do-not-reply at jboss.com  Thu Apr 30 17:09:53 2009
From: do-not-reply at jboss.com (jamesjoh)
Date: Thu, 30 Apr 2009 17:09:53 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Using
	StubExt.PROPERTY_CLIENT_TIMEOUT to control timeout
Message-ID: <12869450.1241125793711.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

After a lot of time in the debugger I have figured out my issue.  I don't think there is a great way to 'solve' it.  Basically it looks like there are 3 seperate attempts to 'connect' to the endpoint, each one which honors the timeout.  I set my timeout to 45 seconds and it will consistently return from my dispatch.invoke call 2 minutes & 15 seconds later (45 * 3).  

First attempt: org.jboss.remoting.transport.http.HttpClientInvoker.useHttpURLConnection.  The call to conn.getOutputStream takes 45 seconds to timeout if the endpoint its trying to connect to is unavailable.  This throws an exception that is caught.  In the exception handling block there is a call to HttpUrlConnection.getResponseMessage(), which chains to HttpUrlConnection.getResponseCode().  In HttpUrlConnection.getResponseCode() there is a call to HttpUrlConnection.getInputStream() which takes 45 seconds to timeout.  After that times out it attempts to call HttpUrlConnection.getHeaderField(0) which also takes 45 seconds to time out.  Finally control returns up the stack to my dispatch call where I can deal with the timeout.

Seems pretty crappy but there doesn't appear to be anything I can do about it.  The actual code for HttpUrlConnection leads into closed source SUN code so I've hit a wall for figuring out if there's anything I can do.  Anyway hope this info helps someone, maybe someone will read this and have an idea on how to get a true 45 second timeout.

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

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