From do-not-reply at jboss.com  Fri May  1 11:59:58 2009
From: do-not-reply at jboss.com (kyle.bober)
Date: Fri, 1 May 2009 11:59:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Issue using XmlMixed, XmlRefrences,
	XmlRefrence annotations
Message-ID: <23100292.1241193598439.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I am having an issue with the XmlMixed, XmlRefrences, XmlRefrence annotations... Or so that is what I think is causing the issue.

I have a base class called CriteriaSO


  | @XmlRootElement(name="Criteria")
  | @XmlType(propOrder = {"sortType"})
  | @XmlSeeAlso({IdCriteriaSO.class})
  | public abstract class CriteriaSO {
  | 
  | protected SortType theSortType;
  | 
  | public CriteriaSO() {
  | super();
  | this.theSortType = KeywordAnalysisSortType.ASCENDING;
  | }
  | 
  | @XmlElement(name="SortType", required=true, nillable=false)
  | public SortType getSortType() {
  | return theSortType;
  | }
  | 
  | public void setSortType(SortType aSortType) {
  | theSortType = aSortType;
  | }
  | 
  | }
  | 

I have a two classes that extend the CriteriaSO class ::


  | @XmlRootElement(name="IdCriteria")
  | @XmlType(propOrder = {"Ids"})
  | public class IdCriteriaSO extends CriteriaSO {
  | 
  | private static final long serialVersionUID = 20090430001L;
  | 
  | private List<Integer> theIds;
  | 
  | public IdCriteriaSO() {
  | super(SortType.ASCENDING);
  | this.theKeywordAnalysisIds = new ArrayList<Integer>();
  | }
  | 
  | 
  | @XmlElementWrapper(name = "Ids", nillable=false, required=true)
  | @XmlElement(name = "Id", required = true, nillable = false)
  | public List<Integer> getIds() {
  | return theIds;
  | }
  | 
  | public void setIds(List<Integer> aIds) {
  | theIds = aIds;
  | }
  | }
  | 
  | 
  | @XmlRootElement(name="UserIdCriteria")
  | @XmlType(propOrder = {"userIds"})
  | public class UserIdCriteriaSO extends CriteriaSO {
  | 
  | private static final long serialVersionUID = 20090430001L;
  | 
  | private List<Integer> theUserIds;
  | 
  | public UserIdCriteriaSO() {
  | super(KeywordAnalysisSortType.ASCENDING);
  | this.theUserIds = new ArrayList<Integer>();
  | }
  | 
  | 
  | @XmlElementWrapper(name = "userIds", nillable=false, required=true)
  | @XmlElement(name = "userId", required = true, nillable = false)
  | public List<Integer> getUserIds() {
  | return theUserIds;
  | }
  | 
  | public void setUserIds(List<Integer> anUserIds) {
  | theUserIds = anUserIds;
  | }
  | }
  | 

I then created a List wrapper to contain the CriteriaSO object instances like so ::


  | @XmlRootElement(name="CriteriaList")
  | @XmlSeeAlso({IdCriteriaSO.class, UserIdCriteriaSO.class})
  | public class CriteriaListSO {
  | 
  | private static final long serialVersionUID = 20090424001L;
  | 
  | private List<CriteriaSO> theCriteria;
  | 
  | public CriteriaListSO() {
  | super();
  | this.theCriteria = new ArrayList<KeywordAnalysisCriteriaSO>();
  | }
  | 
  | 
  | @XmlMixed
  | @XmlElementRefs( {
  | @XmlElementRef(name = "IdCriteria", type = IdCriteriaSO.class),
  | @XmlElementRef(name = "UserIdCriteria", type = UserIdCriteriaSO.class) })
  | public List<CriteriaSO> getCriteria() {
  | return theCriteria;
  | }
  | 
  | public void setCriteria(List<sCriteriaSO> anCriteria) {
  | theCriteria = anCriteria;
  | }
  | }
  | 

I have a web service method that takes a CriteriaListSO object as a parameter.


  | @WebService(name="testService", serviceName="testService")
  | @SOAPBinding(style=SOAPBinding.Style.DOCUMENT, use=SOAPBinding.Use.LITERAL, parameterStyle=SOAPBinding.ParameterStyle.WRAPPED)
  | public class TestService {
  | 
  | 
  | @WebMethod(operationName = "echoCriteria")
  | @WebResult(name = "CriteriaList")
  | @RequestWrapper(localName="echoCriteriaRequest")
  | @ResponseWrapper(localName="echoCriteriaResponse")
  | public CriteriaListSO echoCriteria(@WebParam(name = "CriteriaList")CriteriaListSO criteriaListSO) throws RemoteException {
  | 
  | return criteriaListSO;
  | }
  | }
  | 

My issue is everytime I send a web service request to the echoCriteria web method with some CriteriaSO objects it doesn't set them in the CriteriaList object.
What I do see is one of the CriteriaList - ArrayList element's is being set to an object of type java.lang.String. And the contents of the String is the following
"\n" For each CriteriaSO object I add to the SOAP request it will add an additional \n to the string contents.

I am using JBoss 4.2.1

Any help or guidance would be appreciated. I have spent a few hours now on diffrent annotation configurations trying to figure this out.

-Kyle 

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

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


From do-not-reply at jboss.com  Mon May  4 09:30:29 2009
From: do-not-reply at jboss.com (kyle.bober)
Date: Mon, 4 May 2009 09:30:29 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - How to use @XmlMixed,
	@XmlRefrences and @XmlRefrence annotat
Message-ID: <13145316.1241443829938.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Okay maybe a better question to ask is this. How do I properly use the @XmlMixed, @XmlRefrences and @XmlReference annotations? Is the way I have stated above in my code examples correct??? Someone out there has to be using these annotations successfully! Any examples would be appreciated!

-Kyle 

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

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


From do-not-reply at jboss.com  Tue May  5 04:33:28 2009
From: do-not-reply at jboss.com (wangzhao)
Date: Tue, 5 May 2009 04:33:28 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - jbossws-native-3.1.1.GA and jbossws-CXF
	incompatible error
Message-ID: <24433986.1241512408915.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

@WebMethod
    @WebResult(name = "Candidate", targetNamespace = "http://model.ontraq.nl")
	public CandidateDTO saveMyCandidate(
			@WebParam(partName = "candidate", name = "Candidate", targetNamespace="http://model.ontraq.nl")
			CandidateDTO candidate);

on jbossws-CXF the service runs ok, but on jbossws-native-3.1.1.GA  it runs error

error message:
16:29:18,700 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
org.jboss.ws.core.CommonSOAPFaultException: Endpoint {http://model.ontraq.nl}Can
didateModelServiceImplPort does not contain operation meta data for: saveMyCandi
date
        at org.jboss.ws.core.server.ServiceEndpointInvoker.getDispatchDestinatio
n(ServiceEndpointInvoker.java:476)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpoin
tInvoker.java:178)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHan
dlerImpl.java:474)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHand
lerImpl.java:295)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl
.java:205)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(Request
HandlerImpl.java:131)
        at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(Abstract
EndpointServlet.java:85)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
        at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi
lter.java:96)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:235)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:230)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:175)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit
yAssociationValve.java:182)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv
e.java:84)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:127)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:102)
        at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedC
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)
16:29:18,716 ERROR [SOAPFaultHelperJAXRPC] SOAP request exception
javax.xml.rpc.soap.SOAPFaultException: Endpoint {http://model.ontraq.nl}Candidat
eModelServiceImplPort does not contain operation meta data for: saveMyCandidate
        at org.jboss.ws.core.jaxrpc.SOAPFaultHelperJAXRPC.exceptionToFaultMessag
e(SOAPFaultHelperJAXRPC.java:189)
        at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(
SOAPFaultHelperJAXWS.java:183)
        at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessage
FromException(SOAP11BindingJAXWS.java:102)
        at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBindin
g.java:671)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpoin
tInvoker.java:285)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHan
dlerImpl.java:474)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHand
lerImpl.java:295)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl
.java:205)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(Request
HandlerImpl.java:131)
        at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(Abstract
EndpointServlet.java:85)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
        at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi
lter.java:96)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:235)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:230)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:175)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit
yAssociationValve.java:182)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv
e.java:84)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:127)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:102)
        at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedC
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=4228523#4228523

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


From do-not-reply at jboss.com  Tue May  5 04:43:44 2009
From: do-not-reply at jboss.com (angusm)
Date: Tue, 5 May 2009 04:43:44 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Obscure 'SAXParseException: Content is
	not allowed in prolog
Message-ID: <18251555.1241513024165.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I have a 'Content is not allowed in prolog' problem. But I am pretty sure that it is not any of the usual culprits (spaces or invalid characters where they should not be). 

I have a WSDL (below). This is for a document type WS, and the schema is at  http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4.xsd . 
I have verified that the WSDL is WSI Basic Profile 1.1 with soapUI and the WS-I Testing Tools V1.1. 
It is correctly parsed and treated by wsconsume. 
The server application is correctly deployed. But when I try to run the client I get (full stack trace below) 
WSDLException (at /definitions/types/xs:schema/xs:schema): faultCode=PARSER_ERROR: Problem parsing 'http://schemas.xmlsoap.orgsoap/envelope/'.: org.xml.sax.SAXParseException: Content is not allowed in prolog. It seems to get stuck parsing the soap envelope schema, which is imported into the 3GPP schema. (I have validated the 3GPP schema with  http://www.w3.org/2001/03/webdata/xsv).

JBossWS : version.id=3.0.1-native-2.0.4.GA.

As ever, any suggestions ideas infinitely appreciated.

WSDL:
(I changed the WSDL soap NS to soapx as I thought there might be conficts with the 3GPP NS soap, but it did not make any difference)
<?xml version="1.0" encoding="UTF-8"?>
  | <definitions name="MM7Service" targetNamespace="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4" xmlns:tns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapx="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/">
  |   <types>
  | <xs:schema targetNamespace="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4" xmlns:tns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" elementFormDefault="qualified" attributeFormDefault="unqualified">
  | 	<xs:include  schemaLocation="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4.xsd"/>
  | </xs:schema>
  |   </types>
  |   <message name="MM7_SubmitReq">
  |     <part name="SubmitReq" element="tns:SubmitReq">
  |     </part>
  |   </message>
  |   <message name="MM7_SubmitRsp">
  |     <part name="SubmitReq" element="tns:SubmitRsp">
  |     </part>
  |   </message>
  |   <portType name="MM7">
  |     <operation name="submit">
  |       <input message="tns:MM7_SubmitReq">
  |     </input>
  |       <output message="tns:MM7_SubmitRsp">
  |     </output>
  |     </operation>
  |   </portType>
  |   <binding name="MM7Binding" type="tns:MM7">
  |     <soapx:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
  |     <operation name="submit">
  |       <soapx:operation soapAction=""/>
  |       <input>
  |         <soapx:body use="literal"/>
  |       </input>
  |       <output>
  |         <soapx:body use="literal"/>
  |       </output>
  |     </operation>
  |   </binding>
  |   <service name="MM7Service">
  |     <port name="MM7Port" binding="tns:MM7Binding">
  |       <soapx:address location="REPLACE_WITH_ACTUAL_URL"/>
  |     </port>
  |   </service>
  | </definitions>
  | 

Stack Trace:
09:44:35,338 TRACE [JBossEntityResolver] Mapped systemId to filename: 
  | 09:44:35,338 TRACE [JBossEntityResolver]  maps to URL: file:/C:/Other/eclipseall/ws/hsi/mm7-client2/bin/
  | [Fatal Error] :1:1: Content is not allowed in prolog.
  | Exception in thread "main" org.jboss.ws.metadata.wsdl.WSDLException: javax.wsdl.WSDLException: WSDLException (at /definitions/types/xs:schema/xs:schema): faultCode=PARSER_ERROR: Problem parsing 'http://schemas.xmlsoap.org/soap/envelope/'.: org.xml.sax.SAXParseException: Content is not allowed in prolog.
  | 	at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:152)
  | 	at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:293)
  | 	at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.buildMetaData(JAXWSClientMetaDataBuilder.java:84)
  | 	at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.<init>(ServiceDelegateImpl.java:136)
  | 	at org.jboss.ws.core.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:63)
  | 	at javax.xml.ws.Service.<init>(Service.java:79)
  | 	at org._3gpp.ftp.specs.archive._23_series._23_140.schema.rel_6_mm7_1_4.MM7Service.<init>(MM7Service.java:41)
  | 	at test.client.MM7ClientTest2.main(MM7ClientTest2.java:25)
  | Caused by: javax.wsdl.WSDLException: WSDLException (at /definitions/types/xs:schema/xs:schema): faultCode=PARSER_ERROR: Problem parsing 'http://schemas.xmlsoap.org/soap/envelope/'.: org.xml.sax.SAXParseException: Content is not allowed in prolog.
  | 	at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.getDocument(JBossWSDLReaderImpl.java:2136)
  | 	at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.parseSchema(JBossWSDLReaderImpl.java:832)
  | 	at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.parseSchema(JBossWSDLReaderImpl.java:866)
  | 	at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.parseSchema(JBossWSDLReaderImpl.java:656)
  | 	at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.parseTypes(JBossWSDLReaderImpl.java:617)
  | 	at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.parseDefinitions(JBossWSDLReaderImpl.java:329)
  | 	at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.readWSDL(JBossWSDLReaderImpl.java:2290)
  | 	at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.readWSDL(JBossWSDLReaderImpl.java:2254)
  | 	at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.readWSDL(JBossWSDLReaderImpl.java:2307)
  | 	at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.readWSDL(JBossWSDLReaderImpl.java:2328)
  | 	at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.readWSDL(JBossWSDLReaderImpl.java:2360)
  | 	at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:125)
  | 	... 7 more
  | Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog.
  | 	at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
  | 	at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
  | 	at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.getDocument(JBossWSDLReaderImpl.java:2126)
  | 	... 18 more

Client program:
	private final static String WSDL_HTTP = "http://frpar-morisona1:8080/mm7/MM7Bean?wsdl";
  |     
  | 	private final static String NAMESPACE = "http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4";
  | 
  | 	
  | 	public static void main(String[] args) throws Exception {
  | 
  | 		MM7Service serv = new MM7Service(new URL(WSDL_HTTP), new QName(NAMESPACE, "MM7Service"));
  | 
  | 		MM7 port = serv.getMM7Port();
  | 
  | 		SubmitReqType submitReq = new SubmitReqType();
  | 
  | 		SubmitRspType submitRsp = port.submit(submitReq);
  | 	}

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

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


From do-not-reply at jboss.com  Tue May  5 12:29:37 2009
From: do-not-reply at jboss.com (angusm)
Date: Tue, 5 May 2009 12:29:37 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Obscure 'SAXParseException: Content
	is not allowed in pr
Message-ID: <30671752.1241540977703.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Looking further at this, I think the trace before it blows up is relevent. it is definitely parsing the soap envelope schema:

  | 2009-05-05 18:03:59,380 DEBUG [org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory] parse: http://frpar-morisona1:8080/mm7/MM7Bean?wsdl
  | 2009-05-05 18:03:59,568 TRACE [org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory] getBaseInputSource [wsdlUrl=http://frpar-morisona1:8080/mm7/MM7Bean?wsdl]
  | 2009-05-05 18:03:59,677 TRACE [org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory] getImportInputSource [parent=http://frpar-morisona1:8080/mm7/MM7Bean?wsdl,resource=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4.xsd]
  | 2009-05-05 18:03:59,677 TRACE [org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory] Trying to resolve: http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4.xsd
  | 2009-05-05 18:03:59,677 DEBUG [org.jboss.ws.core.utils.JBossWSEntityResolver] resolveEntity: [pub=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4.xsd,sysid=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4.xsd]
  | 2009-05-05 18:03:59,677 TRACE [org.jboss.util.xml.JBossEntityResolver] resolvePublicID, publicId=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4.xsd
  | 2009-05-05 18:03:59,677 TRACE [org.jboss.util.xml.JBossEntityResolver] resolveSystemID, systemId=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4.xsd
  | 2009-05-05 18:03:59,677 TRACE [org.jboss.util.xml.JBossEntityResolver] resolveClasspathName, systemId=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4.xsd
  | 2009-05-05 18:03:59,677 TRACE [org.jboss.util.xml.JBossEntityResolver] Mapped systemId to filename: REL-6-MM7-1-4.xsd
  | 2009-05-05 18:03:59,677 TRACE [org.jboss.util.xml.JBossEntityResolver] resolveSystemIDasURL, systemId=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4.xsd
  | 2009-05-05 18:03:59,677 TRACE [org.jboss.util.xml.JBossEntityResolver] Trying to resolve systemId as a URL
  | 2009-05-05 18:04:00,115 TRACE [org.jboss.util.xml.JBossEntityResolver] Resolved systemId as a URL
  | 2009-05-05 18:04:00,287 TRACE [org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory] getImportInputSource [parent=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4.xsd,resource=http://schemas.xmlsoap.org/soap/envelope/]
  | 2009-05-05 18:04:00,287 TRACE [org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory] Trying to resolve: http://schemas.xmlsoap.org/soap/envelope/
  | 2009-05-05 18:04:00,287 DEBUG [org.jboss.ws.core.utils.JBossWSEntityResolver] resolveEntity: [pub=http://schemas.xmlsoap.org/soap/envelope/,sysid=http://schemas.xmlsoap.org/soap/envelope/]
  | 2009-05-05 18:04:00,287 TRACE [org.jboss.util.xml.JBossEntityResolver] resolvePublicID, publicId=http://schemas.xmlsoap.org/soap/envelope/
  | 2009-05-05 18:04:00,287 TRACE [org.jboss.util.xml.JBossEntityResolver] resolveSystemID, systemId=http://schemas.xmlsoap.org/soap/envelope/
  | 2009-05-05 18:04:00,302 TRACE [org.jboss.util.xml.JBossEntityResolver] resolveClasspathName, systemId=http://schemas.xmlsoap.org/soap/envelope/
  | 2009-05-05 18:04:00,302 TRACE [org.jboss.util.xml.JBossEntityResolver] Mapped systemId to filename: 
  | 2009-05-05 18:04:00,302 TRACE [org.jboss.util.xml.JBossEntityResolver]  maps to URL: file:/C:/Other/eclipseall/ws/hsi/mm7-client2/bin/
  | 
  | 

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

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


From do-not-reply at jboss.com  Wed May  6 07:13:44 2009
From: do-not-reply at jboss.com (meet_ravip)
Date: Wed, 6 May 2009 07:13:44 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Jax-RPC WS Implementation in JBoss
Message-ID: <8910758.1241608424404.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi,
 We were using the Jax-RPC based Web Service Implementation in Sun Java Application Server.Now we are planning to port it to JBoss application server.So is there any limitation on using Jax-RPC webservice implementation in JBoss?.For wsdl2java approach can we use wsconsume tool for generating the jax-rpc-mapping,webservices.xml or we have to rely on sun wscompile tool?.Please give us some links or Samples,documentations.

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

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


From do-not-reply at jboss.com  Wed May  6 09:45:14 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Wed, 6 May 2009 09:45:14 -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: <20634833.1241617514789.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

The feature is implemented and will be available in next JBossWS/JBossAS release.

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

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


From do-not-reply at jboss.com  Wed May  6 12:05:38 2009
From: do-not-reply at jboss.com (goldberg.howard)
Date: Wed, 6 May 2009 12:05:38 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - client missing wrappers
Message-ID: <28274693.1241625938575.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

jboss 5.01GA
Eclipse 3.4

I've exposed a web service on an ejb3 bean, which also exposes local and remote interfaces.
The bean deploys correctly, I can access the wsdl, and exercise the remote interface from a test client.  However, the web service client gives the runtime modeler error below.  It's a vanilla client, in an enterprise app client project.  Can't figure out why the wrapper classes aren't being autogenerated, or what the problem is.  Let me know if I can provide any additional information.
Client Code:

	public static void main(String[] args) {
		// TODO Auto-generated method stub
		try {

			URL serviceUrl = new URL("http://localhost:8080/ecrs-droolsEAR-ecrs/ECRSImpl?wsdl");
			Service ECRSService = Service.create(serviceUrl, new QName("http://goldberg.org/ecrs","ECRSWsService"));
			ECRSWs ecrsWs = ECRSService.getPort(ECRSWs.class);

Exception: 

com.sun.xml.ws.model.RuntimeModelerException: runtime modeler error: Wrapper class org.goldberg.jaxws.ExecuteRules is not found. Have you run APT to generate them?
	at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:287)
	at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:596)
	at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:543)
	at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:371)
	at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:258)
	at com.sun.xml.ws.client.WSServiceDelegate.addSEI(WSServiceDelegate.java:633)
	at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:328)
	at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:311)
	at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:339)
	at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:343)
	at javax.xml.ws.Service.getPort(Service.java:161)
	at goldberg.org.test.TestECRSws.main(TestECRSws.java:86)

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

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


From do-not-reply at jboss.com  Thu May  7 00:34:00 2009
From: do-not-reply at jboss.com (goldberg.howard)
Date: Thu, 7 May 2009 00:34:00 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: client missing wrappers
Message-ID: <24859910.1241670840689.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Also getting a warning about not processing the deployment descriptor for the web context

00:27:27,235 INFO  [DefaultEndpointRegistry] register: jboss.ws:context=ecrs-droolsEAR-ecrs,endpoint=ECRSImpl
00:27:27,375 INFO  [WSDLFilePublisher] WSDL published to: file:/usr/local/jboss/jboss-5.0.1.GA/server/default/data/wsdl/ecrs-droolsEAR.ear/ecrs.jar/ECRSWsService42478.wsdl
00:27:27,401 INFO  [TomcatDeployment] deploy, ctxPath=/ecrs-droolsEAR-ecrs
00:27:27,445 WARN  [config] Unable to process deployment descriptor for context '/ecrs-droolsEAR-ecrs'

Here's the implementation annotations:

 @WebService (portName="ECRSPort",
		targetNamespace="http://goldberg.org/ecrs",
		serviceName="ECRSWsService",
		endpointInterface="org.goldberg.ECRSWs")
@Stateless
public class ECRSImpl implements ECRSRemote, ECRSLocal, ECRSWs {

Here is the interface:


@WebService (targetNamespace="http://goldberg.org/ecrs")
public interface ECRSWs {

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

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


From do-not-reply at jboss.com  Thu May  7 00:50:29 2009
From: do-not-reply at jboss.com (vinaykumaraitha)
Date: Thu, 7 May 2009 00:50:29 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Can anyone plzz explain hw to create a
	sample webservice for
Message-ID: <11383336.1241671829588.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Can anyone plzz explain hw to create a sample webservice for jBOSS (preferably with apache CXF webservice stack))

It can be with eclipse (3.4.1) or netbeans (6.5)
IDE.

Thanks,
Vinay



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

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


From do-not-reply at jboss.com  Thu May  7 05:07:55 2009
From: do-not-reply at jboss.com (angusm)
Date: Thu, 7 May 2009 05:07:55 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Tracing wsconsume
Message-ID: <17314923.1241687275259.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Can anybody kindly tell me how to turn on tracing in wsconsume?
wsconsume.bat runs WSConsume with
-Dlog4j.configuration=wstools-log4j.xml
According to the Jamae / Johnson book wstools-log4j.xm is now obsolete. But I have tried replacing it with a reference to another log4j.xml file. To no effect.
TIA.

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

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


From do-not-reply at jboss.com  Thu May  7 16:16:28 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Thu, 7 May 2009 16:16:28 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Tracing wsconsume
Message-ID: <10513037.1241727388048.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Please state exactly what you did (post the change). I modified wsconsume.bat, removing that clause from the java command line. Then it picks up the log4j.properties (or.xml) in my classpath.

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

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


From do-not-reply at jboss.com  Fri May  8 05:27:47 2009
From: do-not-reply at jboss.com (getaceres)
Date: Fri, 8 May 2009 05:27:47 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Jar file for
	org.jboss.ws.core.soap.SAAJMetaFactoryImpl.
Message-ID: <8287667.1241774867846.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I'm having the same issue with JBossWS Metro 3.1.1 over a new installed JBoss 4.2.3. I deploy the Metro stack and then I try to deploy my EJB3 services (each one in a different jar). The first one gives this exception:


  | 11:21:42,907 ERROR [MainDeployer] Could not start deployment: file:/home/jsanchez/apps/jboss/jboss-4.2.3.GA/server/default/deploy/OHA/OHA-provisioning-service-1.0-SNAPSHOT.jar
  | javax.xml.ws.WebServiceException: Failed to build METRO runtime model
  | 	at org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect.start(RuntimeModelDeploymentAspect.java:133)
  | 	at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:129)
  | 	at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:95)
  | 	at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:88)
  | 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
  | 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy34.start(Unknown Source)
  | 	at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
  | 	at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy9.deploy(Unknown Source)
  | 	at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
  | 	at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
  | 	at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
  | 	at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
  | 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
  | 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
  | 	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
  | 	at $Proxy0.start(Unknown Source)
  | 	at org.jboss.system.ServiceController.start(ServiceController.java:417)
  | 	at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy4.start(Unknown Source)
  | 	at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304)
  | 	at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy5.deploy(Unknown Source)
  | 	at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
  | 	at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
  | 	at org.jboss.Main.boot(Main.java:200)
  | 	at org.jboss.Main$1.run(Main.java:508)
  | 	at java.lang.Thread.run(Thread.java:619)
  | Caused by: java.lang.ExceptionInInitializerError
  | 	at com.sun.xml.ws.api.BindingID.<clinit>(BindingID.java:321)
  | 	at org.jboss.wsf.stack.metro.DeploymentDescriptorParserExt.createBinding(DeploymentDescriptorParserExt.java:350)
  | 	at org.jboss.wsf.stack.metro.DeploymentDescriptorParserExt.parseAdapters(DeploymentDescriptorParserExt.java:285)
  | 	at org.jboss.wsf.stack.metro.DeploymentDescriptorParserExt.parse(DeploymentDescriptorParserExt.java:171)
  | 	at org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect.start(RuntimeModelDeploymentAspect.java:109)
  | 	... 77 more
  | Caused by: java.lang.IllegalStateException: Failed to load javax.xml.soap.MetaFactory: org.jboss.ws.core.soap.SAAJMetaFactoryImpl
  | 	at javax.xml.soap.SAAJFactoryLoader.loadFactory(SAAJFactoryLoader.java:131)
  | 	at javax.xml.soap.SAAJMetaFactory.getInstance(SAAJMetaFactory.java:60)
  | 	at javax.xml.soap.MessageFactory.newInstance(MessageFactory.java:106)
  | 	at com.sun.xml.ws.api.SOAPVersion.<init>(SOAPVersion.java:178)
  | 	at com.sun.xml.ws.api.SOAPVersion.<clinit>(SOAPVersion.java:83)
  | 	... 82 more
  | Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.ws.core.soap.SAAJMetaFactoryImpl
  | 	at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212)
  | 	at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:521)
  | 	at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:415)
  | 	at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
  | 	at javax.xml.soap.SAAJFactoryLoader.loadFactory(SAAJFactoryLoader.java:125)
  | 	... 86 more

The next ones give this exception:

11:21:44,128 ERROR [MainDeployer] Could not start deployment: file:/home/jsanchez/apps/jboss/jboss-4.2.3.GA/server/default/deploy/OHA/datasource-common-1.0-SNAPSHOT.jar
  | javax.xml.ws.WebServiceException: Failed to build METRO runtime model
  | 	at org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect.start(RuntimeModelDeploymentAspect.java:133)
  | 	at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:129)
  | 	at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:95)
  | 	at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:88)
  | 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
  | 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy34.start(Unknown Source)
  | 	at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
  | 	at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy9.deploy(Unknown Source)
  | 	at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
  | 	at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
  | 	at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
  | 	at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
  | 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
  | 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
  | 	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
  | 	at $Proxy0.start(Unknown Source)
  | 	at org.jboss.system.ServiceController.start(ServiceController.java:417)
  | 	at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy4.start(Unknown Source)
  | 	at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304)
  | 	at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
  | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  | 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
  | 	at $Proxy5.deploy(Unknown Source)
  | 	at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
  | 	at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
  | 	at org.jboss.Main.boot(Main.java:200)
  | 	at org.jboss.Main$1.run(Main.java:508)
  | 	at java.lang.Thread.run(Thread.java:619)
  | Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.sun.xml.ws.api.BindingID
  | 	at org.jboss.wsf.stack.metro.DeploymentDescriptorParserExt.createBinding(DeploymentDescriptorParserExt.java:350)
  | 	at org.jboss.wsf.stack.metro.DeploymentDescriptorParserExt.parseAdapters(DeploymentDescriptorParserExt.java:285)
  | 	at org.jboss.wsf.stack.metro.DeploymentDescriptorParserExt.parse(DeploymentDescriptorParserExt.java:171)
  | 	at org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect.start(RuntimeModelDeploymentAspect.java:109)
  | 	... 77 more

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

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


From do-not-reply at jboss.com  Fri May  8 09:25:59 2009
From: do-not-reply at jboss.com (mudgalc)
Date: Fri, 8 May 2009 09:25:59 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - username token authentication using
	jbossws-native
Message-ID: <21251307.1241789159231.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi,

I am trying to use jbossws-native to do username token authentication.
I am following the steps given in link
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=151752

but i am getting 
java.lang.ClassCastException: $Proxy25 cannot be cast to org.jboss.ws.core.StubExt

Can you please let me know what do i need to do to fix this? or if there is another way to handle username token authentication?

Any help will be highly appreciated.
thanks, 
Chhaya

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

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


From do-not-reply at jboss.com  Fri May  8 11:51:17 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 8 May 2009 11:51:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBossWS 3.1.2 (Native) released
Message-ID: <14171345.1241797877666.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I'm happy to announce the release of JBossWS-Native 3.1.2 GA.

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

The supported target containers for this release are JBoss 5.0.0.GA and JBoss 5.0.1.GA. 

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

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

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

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

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

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


From do-not-reply at jboss.com  Fri May  8 12:04:09 2009
From: do-not-reply at jboss.com (cliffs)
Date: Fri, 8 May 2009 12:04:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - RestEasy and JNDI datasource lookup
	problem, datasource come
Message-ID: <21053681.1241798649686.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi All,
  I have a quick question regarding a problem I had been experiencing with RestEasy 1.1-RC2 and looking up a datasource in JNDI.  I don't believe this is a RestEasy bug,   it seems to be related to one of the jar files that ships with resteasy.

I have a resteasy easy servlet that I deploy onto JBOSS 5.0.1GA.  At some point in my resteasy application I go and lookup my datasource using:


  | InitialContext ctx = new InitialContext();
  | 	        DataSource ds = (DataSource)ctx.lookup( "java:comp/env/jdbc/SomeDataSource" );
  | 

However, the datasource is coming back as null.  I did a listing of the JNDI jdbc context, and I see the DS in the context, it's just coming back at null.
I know the datasource is there (configured in JBOSS) because I can get it, and use it via other non-resteasy servlets.

I was able to fix this, be removing multiple .jar files that ships with RestEasy, ( by remove, I mean not deploying some jars with my webapp).  I basically tried to guess which jars were already included with JBOSS 5. 

My question is: Does anyone know what jar file may have caused this? So that I don't deploy it in the future.  I'm guessing this may have occured with other JBoss projects but I was unable to find the correct search words to look this up.

Also, can anyone recommend, a minimum set of jars to include, assuming I will be running on Jboss 5.0.1?


FYI, here are the jars that ship with RestEasy 5.0.1:
-----------------------------------------------------------
activation-1.1.jar
async-http-jbossweb-1.1-RC2.jar
async-http-servlet-3.0-1.1-RC2.jar
async-http-tomcat6-1.1-RC2.jar
commons-codec-1.2.jar
commons-httpclient-3.1.jar
commons-logging-1.0.4.jar
FastInfoset-1.2.2.jar
javassist-3.6.0.GA.jar
jaxb-api-2.1.jar
jaxb-impl-2.1.8.jar
jaxrs-api-1.1-RC2.jar
jboss-common-core-2.2.10.GA.jar
jboss-logging-spi-2.0.5.GA.jar
jbosscache-core-3.0.3.GA.jar
jettison-1.0.1.jar
jetty-6.1.15.jar
jetty-util-6.1.15.jar
jgroups-2.6.7.GA.jar
jsr250-api-1.0.jar
jta-1.1.jar
jyaml-1.3.jar
mail-1.4.jar
resteasy-atom-provider-1.1-RC2.jar
resteasy-cache-core-1.1-RC2.jar
resteasy-jaxb-provider-1.1-RC2.jar
resteasy-jaxrs-1.1-RC2.jar
resteasy-multipart-provider-1.1-RC2.jar
resteasy-spring-1.1-RC2.jar
resteasy-yaml-provider-1.1-RC2.jar
scannotation-1.0.2.jar
servlet-api-2.5-20081211.jar
servlet-api-2.5.jar
sjsxp-1.0.1.jar
slf4j-api-1.5.2.jar
slf4j-simple-1.5.2.jar
stax-api-1.0.jar
webserver-1.3.3.jar


Thanks for any help

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

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


From do-not-reply at jboss.com  Fri May  8 14:00:32 2009
From: do-not-reply at jboss.com (gmills)
Date: Fri, 8 May 2009 14:00:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Recomended way to build server and
	client with maven?
Message-ID: <17393898.1241805632284.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Do you have an example of using wsconsume within a maven pom file to generate the client stub?

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

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


From do-not-reply at jboss.com  Sun May 10 14:33:33 2009
From: do-not-reply at jboss.com (daoudadhoc)
Date: Sun, 10 May 2009 14:33:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - secure hello world exemple
Message-ID: <10532042.1241980413781.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

hi every body
I want to secure a web service using jboss 4.2.2 and metro 3.0.5
can any body give me a secure hello world sample and tell me the required configuration.
thanks

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

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


From do-not-reply at jboss.com  Mon May 11 03:37:28 2009
From: do-not-reply at jboss.com (lixun)
Date: Mon, 11 May 2009 03:37:28 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Help! Call Web service error!
Message-ID: <4418391.1242027448732.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

My developping enviroment is JBoss 5.0.1 GA, jbossws-native-3.0.5

First, I define a web service implementation
then I use wsconsume to generate stub Java Code
If I Call web service with Java Application, that's OK!


But when I put the same code in web application, error happened!


javax.xml.rpc.soap.SOAPFaultException: org.xml.sax.SAXParseException: Premature end of file.
	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.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:496)
	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295)
	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205)
	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
	at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

Anyone tell me why?

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

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


From do-not-reply at jboss.com  Mon May 11 04:42:09 2009
From: do-not-reply at jboss.com (angusm)
Date: Mon, 11 May 2009 04:42:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Tracing wsconsume
Message-ID: <15737530.1242031329918.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Peter,
Contents of myconsume.bat:

  | @echo off
  | 
  | @if not "%ECHO%" == ""  echo %ECHO%
  | @if "%OS%" == "Windows_NT"  setlocal
  | 
  | set DIRNAME=.\
  | if "%OS%" == "Windows_NT" set DIRNAME=%~dp0%
  | set PROGNAME=run.bat
  | if "%OS%" == "Windows_NT" set PROGNAME=%~nx0%
  | 
  | set JAVA=%JAVA_HOME%\bin\java
  | set JBOSS_HOME=C:/jboss/jboss-4.2.2.GA
  | 
  | rem Setup the java endorsed dirs
  | set JBOSS_ENDORSED_DIRS=%JBOSS_HOME%\lib\endorsed
  | 
  | rem Shared libs
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;C:/Other/eclipseall/ws/hsi/mm7-client2/work
  | 
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JAVA_HOME%/lib/tools.jar
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/activation.jar
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/getopt.jar
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/wstx.jar
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jbossall-client.jar
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/log4j.jar
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/mail.jar
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jbossws-spi.jar
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jbossws-common.jar
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jbossws-framework.jar
  | 
  | rem Shared jaxws libs
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jaxws-tools.jar
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jaxws-rt.jar
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/stax-api.jar
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jaxb-api.jar
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jaxb-impl.jar
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jaxb-xjc.jar
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/streambuffer.jar
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/stax-ex.jar
  | 
  | rem Stack specific dependencies
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/javassist.jar
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jboss-xml-binding.jar
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jbossws-native-client.jar
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jbossws-native-core.jar
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jbossws-native-jaxws.jar
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jbossws-native-jaxws-ext.jar
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jbossws-native-jaxrpc.jar
  | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jbossws-native-saaj.jar
  | 
  | rem Execute the JVM
  | "%JAVA%" %JAVA_OPTS% -Djava.endorsed.dirs="%JBOSS_ENDORSED_DIRS%" -Dlog4j.configuration=mylog4j.xml -classpath "%WSCONSUME_CLASSPATH%" org.jboss.wsf.spi.tools.cmd.WSConsume %*
  | 

Contents of myrun.bat:

  | myconsume -k -s ../src -o tmp mm7.wsdl

All relevant files (mylog4j.xml, mm7,wsdl ..) are in the folder anonymous wrote : C:\Other\eclipseall\ws\hsi\mm7-client2\work

That's kind of you,
Angus

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

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


From do-not-reply at jboss.com  Mon May 11 04:45:03 2009
From: do-not-reply at jboss.com (anders.andersen)
Date: Mon, 11 May 2009 04:45:03 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Runtime classloader cannot be null
Message-ID: <33322983.1242031503239.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi,

We have the exact same problem with jbossws-native-2.0.1.SP2_CP03 (included with the jboss-soa-p-standalone.4.3.0). Has anyone found a solution to this issue?


Kind regards,

Anders.

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

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


From do-not-reply at jboss.com  Mon May 11 05:50:31 2009
From: do-not-reply at jboss.com (p_repetti)
Date: Mon, 11 May 2009 05:50:31 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Deployment has no classloader
	associated exception
Message-ID: <29494130.1242035431219.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hello

I applied JBossWS Native 2.0.3 GA over JBoss AS 4.2.2 GA to solve an interaction problem with a remote Axis2 WS.

As a side effect one of my other WSs does not work any more. When one of its operations is invoked it fails with the following exception:

java.lang.IllegalStateException: Deployment has no classloader associated
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:183)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:124)
        at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
        at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
        at java.lang.Thread.run(Thread.java:619)

ANy help will be highly valuable.
Thanks


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

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


From do-not-reply at jboss.com  Mon May 11 07:14:09 2009
From: do-not-reply at jboss.com (p_repetti)
Date: Mon, 11 May 2009 07:14:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Deployment has no classloader
	associated exception
Message-ID: <22970961.1242040450125.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Some more details about the installation.

[Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)

installed on a linux box

2.6.18-53.el5 #1 SMP Wed Oct 10 16:34:19 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux

Please note that the same Jboss4.2.2+JbossWS 2.0.3 installed on a Win Vista Business SP1 works OK and does not throw any exception.

I thought there might be different JbossWS packages for win and linux but the web site has just the same .zip for download

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

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


From do-not-reply at jboss.com  Mon May 11 07:14:48 2009
From: do-not-reply at jboss.com (kazcor)
Date: Mon, 11 May 2009 07:14:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - MTOM enabled WS using SSB throws OOME
Message-ID: <23564419.1242040488309.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Dear all,

I'm trying to get a webservice up an running that is capable of receiving large documents, so I decided to give MTOM/XOP a try. Although I seem to have done everything necessary, I still get OutOfMemoryExceptions on both, client and server side.
Here is what I've done so far:
The service:

  | @WebService
  | @BindingType(value = SOAPBinding.SOAP11HTTP_MTOM_BINDING)
  | @MTOM(enabled = true)
  | @Stateless
  | public class SampleService {
  | 
  | 	public void sendDocument(@XmlMimeType(value = "application/octet-stream") DataHandler document) {
  | 
  | 		if (document != null) {
  | 			try {
  | 				InputStream in = document.getInputStream();
  | 				File f = File.createTempFile("mtom", ".dat", new File("/tmp"));
  | 				if (f.exists() && f.canWrite()) {
  | 					FileOutputStream fout = new FileOutputStream(f);
  | 					byte[] buffer = new byte[4096];
  | 					int rLines = -1;
  | 					while ((rLines = in.read(buffer)) > 0) {
  | 						fout.write(buffer, 0, rLines);
  | 					}
  | 					fout.close();
  | 					in.close();
  | 				}
  | 			} catch (Exception e) {
  | 				e.printStackTrace();
  | 			}
  | 		}
  | 	}
  | 
  | }
  | 
Deploys fine. After doing wsconsume on the WSDL I end up with this client:

  | public class TestClient {
  | 
  | 	public static void main(String[] args) {
  | 		
  | 		if (args.length != 1) {
  | 			System.err.println("usage: java -jar TestMTOM-client.jar <fileToSend>");
  | 			return;
  | 		}
  | 		
  | 		File fin = new File(args[0]);
  | 		if (!fin.exists()) {
  | 			System.err.println("No such file: "+args[0]);
  | 			return;
  | 		}
  | 		
  | 		SampleServiceService service = new SampleServiceService();
  | 		SampleService port = service.getSampleServicePort();
  | 		SOAPBinding binding = (SOAPBinding)((BindingProvider)port).getBinding();
  | 		binding.setMTOMEnabled(true);
  | 		
  | 		DataHandler handler = new DataHandler(new FileDataSource(fin));
  | 		port.sendDocument(handler);
  | 	}	
  | }
  | 

Logfile and final exception with DEBUG set on org.jboss and org.jboss.management after the client was invoked with a 100MB file (and using -Xmx512m to prevent OOME on client-side):
anonymous wrote : 
  | 13:05:45,032 DEBUG [DefaultSPIProvider] provide SPI 'class org.jboss.wsf.spi.management.EndpointRegistryFactory'
  | 13:05:45,033 DEBUG [DefaultSPIProvider] class org.jboss.wsf.spi.management.EndpointRegistryFactory Implementation: org.jboss.wsf.stack.jbws.EndpointRegistryFactoryImpl at 4d4f6e
  | 13:05:45,049 DEBUG [RequestHandlerImpl] doPost: /TestMTOM/SampleService
  | 13:05:45,050 DEBUG [RequestHandlerImpl] handleRequest: jboss.ws:context=TestMTOM,endpoint=SampleService
  | 13:05:45,070 DEBUG [MessageContextAssociation] pushMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at 104f889 (Thread http-127.0.0.1-8080-1)
  | 13:05:45,080 DEBUG [RequestHandlerImpl] BEGIN handleRequest: jboss.ws:context=TestMTOM,endpoint=SampleService
  | 13:05:45,130 DEBUG [MessageFactoryImpl] createMessage: [contentType=multipart/related;
  |   start="<rootpart*16c428f3-1021-43de-af64-aecc25b7fe93 at example.jaxws.sun.com>";
  |   type="application/xop+xml";
  |   boundary="uuid:16c428f3-1021-43de-af64-aecc25b7fe93";
  |   start-info="text/xml"]
  | 13:05:45,740 DEBUG [DefaultSPIProvider] provide SPI 'class org.jboss.wsf.spi.management.ServerConfigFactory'
  | 13:05:45,748 DEBUG [DefaultSPIProvider] class org.jboss.wsf.spi.management.ServerConfigFactory Implementation: org.jboss.wsf.framework.management.ServerConfigFactoryImpl at 8fc809
  | 13:05:53,229 DEBUG [SwapableMemoryDataSource] Using swap file, location = file:/usr/home/kazcor/Apps/jboss-4.2.3.GA/server/default/tmp/jbossws/JBossWSattachment52750.dat size = 139810362
  | 13:05:58,690 DEBUG [HandlerDelegateJAXWS] callRequestHandlerChain: POST
  | 13:05:58,697 DEBUG [HandlerResolverImpl] initHandlerChain: PRE
  | 13:05:58,777 DEBUG [HandlerResolverImpl] addHandler:
  | HandlerMetaDataJAXWS:
  |  type=PRE
  |  name=Recording Handler
  |  class=class org.jboss.wsf.framework.invocation.RecordingServerHandler
  |  params=[]
  |  protocols=##SOAP11_HTTP
  |  services=null
  |  ports=null
  | 13:05:58,786 DEBUG [HandlerResolverImpl] initHandlerChain: ENDPOINT
  | 13:05:58,794 DEBUG [HandlerResolverImpl] initHandlerChain: POST
  | 13:05:58,808 DEBUG [HandlerResolverImpl] getHandlerChain: [type=POST,info=[service={http://mtom.test.openlimit.com/}SampleServiceService,port={http://mtom.test.openlimit.com/}SampleServicePort,binding=http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true]]
  | 13:05:58,816 DEBUG [HandlerChainExecutor] Create a handler executor: []
  | 13:05:58,826 DEBUG [SOAPMessageDispatcher] getDispatchDestination: {http://mtom.test.openlimit.com/}sendDocument
  | 13:05:58,834 DEBUG [SOAP11BindingJAXWS] unbindRequestMessage: {http://mtom.test.openlimit.com/}sendDocument
  | 13:05:58,846 DEBUG [EndpointInvocation] setRequestParamValue: [name={http://mtom.test.openlimit.com/}sendDocument,value=org.jboss.ws.core.soap.SOAPBodyElementDoc]
  | 13:05:58,861 DEBUG [HandlerDelegateJAXWS] callRequestHandlerChain: ENDPOINT
  | 13:05:58,868 DEBUG [HandlerResolverImpl] getHandlerChain: [type=ENDPOINT,info=[service={http://mtom.test.openlimit.com/}SampleServiceService,port={http://mtom.test.openlimit.com/}SampleServicePort,binding=http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true]]
  | 13:05:58,876 DEBUG [HandlerChainExecutor] Create a handler executor: []
  | 13:05:58,883 DEBUG [HandlerDelegateJAXWS] callRequestHandlerChain: PRE
  | 13:05:58,890 DEBUG [HandlerResolverImpl] getHandlerChain: [type=PRE,info=[service={http://mtom.test.openlimit.com/}SampleServiceService,port={http://mtom.test.openlimit.com/}SampleServicePort,binding=http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true]]
  | 13:05:58,897 DEBUG [HandlerChainExecutor] Create a handler executor: []
  | 13:05:58,907 DEBUG [EndpointInvocation] getRequestPayload
  | 13:05:58,914 DEBUG [EndpointInvocation] getRequestParamValue: {http://mtom.test.openlimit.com/}sendDocument
  | 13:05:58,922 DEBUG [SOAPContentElement] -----------------------------------
  | 13:05:58,929 DEBUG [SOAPContentElement] Transitioning from XML_VALID to OBJECT_VALID
  | 13:05:58,936 DEBUG [XMLContent] getObjectValue [xmlType={http://mtom.test.openlimit.com/}sendDocument,javaType=class com.openlimit.test.mtom.jaxws.SendDocument]
  | 13:05:58,949 DEBUG [JAXBDeserializer] deserialize: [xmlName={http://mtom.test.openlimit.com/}sendDocument,xmlType={http://mtom.test.openlimit.com/}sendDocument]
  | 13:06:03,792 DEBUG [HandlerDelegateJAXWS] closeHandlerChain
  | 13:06:03,800 DEBUG [HandlerChainExecutor] close
  | 13:06:03,807 DEBUG [HandlerDelegateJAXWS] closeHandlerChain
  | 13:06:03,814 DEBUG [HandlerChainExecutor] close
  | 13:06:03,821 DEBUG [HandlerDelegateJAXWS] closeHandlerChain
  | 13:06:03,829 DEBUG [HandlerChainExecutor] close
  | 13:06:03,836 DEBUG [RequestHandlerImpl] END handleRequest: jboss.ws:context=TestMTOM,endpoint=SampleService
  | 13:06:03,844 DEBUG [MessageContextAssociation] popMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at 104f889 (Thread http-127.0.0.1-8080-1)
  | 13:06:04,179 ERROR [[SampleService]] Servlet.service() for servlet SampleService threw exception
  | java.lang.OutOfMemoryError: Java heap space
  | 
Seems to me like it is indeed transferred using XOP and that a swapfile is generated for the incoming request. However, afterwards on deserialization something goes wrong - I hope the former swapped attachment doesn't get deserialized in memory at this point?

Tested with:
JBoss 4.2.3GA (default settings -Xms128m -Xmx512m)
JDK 1.5.0_14-p8
JBossWS (native) 3.1.1GA

Any ideas what I've missed?

Thanks in advance,
Max

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

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


From do-not-reply at jboss.com  Mon May 11 10:00:17 2009
From: do-not-reply at jboss.com (p_repetti)
Date: Mon, 11 May 2009 10:00:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Deployment has no classloader
	associated exception
Message-ID: <4604578.1242050417784.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

OK I found the problem: I was exposing both JAX-RPC and JAX-WS web services in the same WAR and for some reason JBoss does not like it.



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

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


From do-not-reply at jboss.com  Mon May 11 11:31:17 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 11 May 2009 11:31:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Help! Call Web service error!
Message-ID: <2891890.1242055877273.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

The stack trace you posted looks like it came from the browser. Is there one or more corresponding stack traces in the console log? If so, please post those, they are usually more helpful.

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

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


From do-not-reply at jboss.com  Mon May 11 11:58:32 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 11 May 2009 11:58:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Tracing wsconsume
Message-ID: <1055759.1242057512567.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

This looks OK to me. So let's double-check a few things.

First, please verify that the log4j config file is located at: C:\Other\eclipseall\ws\hsi\mm7-client2\work\mylog4j.xml

Second, replace the last line in mywsconsume.bat with:

set APP="%JAVA%" %JAVA_OPTS% -Djava.endorsed.dirs="%JBOSS_ENDORSED_DIRS%" -Dlog4j.configuration=mylog4j.xml -classpath "%WSCONSUME_CLASSPATH%" org.jboss.wsf.spi.tools.cmd.WSConsume %*
  | echo %APP%
  | %APP%

The above code will echo the full java command before running it.

Third, after making the above change, run wsconsume and post the console output, including the command line entered. 

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

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


From do-not-reply at jboss.com  Mon May 11 11:59:30 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 11 May 2009 11:59:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Tracing wsconsume
Message-ID: <31565103.1242057570800.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Oh, and post the mylog4j.xml file.

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

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


From do-not-reply at jboss.com  Mon May 11 12:13:53 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 11 May 2009 12:13:53 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: MTOM enabled WS using SSB throws
	OOME
Message-ID: <23757694.1242058433129.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Sounds like you need a larger heap for JBoss AS than 512m to handle the 100MB file. Try increasing -Xmx (I would try -Xmx1024m).

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

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


From do-not-reply at jboss.com  Mon May 11 12:47:08 2009
From: do-not-reply at jboss.com (kazcor)
Date: Mon, 11 May 2009 12:47:08 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: MTOM enabled WS using SSB throws
	OOME
Message-ID: <22581671.1242060428299.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Sure, that's one way to deal with that issue. Non the less, it's no solution and as soon as I'm going to send a file with lets say 1GB, I'll have the same problem.

As far as I understood one benefit of using MTOM (in case of JAX-WS) is, that there is no serialization/deserialization of the attached data taking place, actually providing in-/output as streams and not allocating a new object for the whole data structure. Why else would JBoss use a swapfile for the incoming request if at the same time the whole bunch of incoming data is stored in memory as well? But maybe I'm completely wrong here - that's why I'm asking :-)
Well, in the later case - what would be a proper workaround? Provide a handler which parses the incoming SOAPMessage and extracts (or cuts out) the attached data providing a unique identifier that might be used to access this data from somewhere else, once the webservice method is invoked and all deserialization has been done?

And yes, I'm aware that a web service is not the right solution for sending such huge documents, but by thinking about a middleware connected to a CMS backend, files (e.g. PDFs) with about 20-50MB are quite normal and should not result in a DoS ;-)

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

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


From do-not-reply at jboss.com  Mon May 11 14:04:41 2009
From: do-not-reply at jboss.com (jlankfo)
Date: Mon, 11 May 2009 14:04:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Global client handler chain
Message-ID: <24902259.1242065081455.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I was wondering if there exists a global handler chain for a client side handler? I was able to implement a global server-side handler by placing my handler in the standard-jaxws-endpoint-config.xml and I was curious if there was something similar I could do for clients hosted on a jboss server. If this is not possible what would be the easiest way to configure a client side handler for a simple web service? Thanks in advance.

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

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


From do-not-reply at jboss.com  Mon May 11 15:27:09 2009
From: do-not-reply at jboss.com (sebastiendeg)
Date: Mon, 11 May 2009 15:27:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - EJB3 WS endpoint generates a weird WSDL
Message-ID: <3571557.1242070029261.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi,

I'm using EJB3.0 on JBoss 4.2.2.

When my WSDL get generated, it contains unnecessary layer for input and output paramters.

For example, for a Service :


public UserAccount login (String login, String password);

The WSDL will have 2 object that represents the return UserAccount :


<xs:complexType name="loginResponse">
  | 
  | <xs:sequence>
  | <xs:element minOccurs="0" name="return" type="tns:userAccount"/>
  | </xs:sequence>
  | </xs:complexType>
  | 
  | 
  | <xs:complexType name="userAccount">
  | </xs/complexType>
  | 


As you can see the "loginResponse" is just a uneeded wrapper around the UserAccount return type.

I'm just lookign for a way of avoiding that, of maybe if someone can explain how I could generate the EJB impl from a WSDL.

Thanks


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

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


From do-not-reply at jboss.com  Mon May 11 19:44:09 2009
From: do-not-reply at jboss.com (Jonas123)
Date: Mon, 11 May 2009 19:44:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WS-Security EJB / Spring WS
Message-ID: <21881797.1242085449345.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi , I'm going to start a web service project in my organization and I'm considering the possible technologies to use.  I used the JBossWS implementation and it worked just fine but when it came to implementing the WS-Security specs I saw that it involves using specific configuration files and annotations from JBoss. One of the major concerns I'm having is to not get coupled to a specific App server, thats because my company has alreadly changed from other servers in the past and it involved serious re-work because most projects were coupled to specific details of them. So I'm tempted to abandon using the JBossWS implementation and use SpringWS with is also JAX-WS compliant (including a WS-Security imp) and makes all configuration be inside the application, not getting specific to some appserver. I'll eventualy end up using the Spring over JBoss's EJB3 for simplicity (I'm trying to minimize the mix of technologies). I would like to ask your opinion about these decisions and if it make sense to you, since i'm kinda newbie at these techs! 
Thank you

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

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



From do-not-reply at jboss.com  Mon May 11 22:53:02 2009
From: do-not-reply at jboss.com (lixun)
Date: Mon, 11 May 2009 22:53:02 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Help! Call Web service error!
Message-ID: <2651169.1242096782531.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Brower error message:

javax.servlet.ServletException: #{applyConsignBean.create}: javax.xml.ws.soap.SOAPFaultException: org.xml.sax.SAXParseException: Premature end of file.
	javax.faces.webapp.FacesServlet.service(FacesServlet.java:277)
	org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
	org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
	org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
	org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

root cause

javax.faces.FacesException: #{applyConsignBean.create}: javax.xml.ws.soap.SOAPFaultException: org.xml.sax.SAXParseException: Premature end of file.
	com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:118)
	javax.faces.component.UICommand.broadcast(UICommand.java:387)
	org.ajax4jsf.component.AjaxActionComponent.broadcast(AjaxActionComponent.java:55)
	org.ajax4jsf.component.AjaxViewRoot.processEvents(AjaxViewRoot.java:321)
	org.ajax4jsf.component.AjaxViewRoot.broadcastEvents(AjaxViewRoot.java:296)
	org.ajax4jsf.component.AjaxViewRoot.processPhase(AjaxViewRoot.java:253)
	org.ajax4jsf.component.AjaxViewRoot.processApplication(AjaxViewRoot.java:466)
	com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:82)
	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
	com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
	javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
	org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
	org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
	org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
	org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

root cause

javax.faces.el.EvaluationException: javax.xml.ws.soap.SOAPFaultException: org.xml.sax.SAXParseException: Premature end of file.
	javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102)
	com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
	javax.faces.component.UICommand.broadcast(UICommand.java:387)
	org.ajax4jsf.component.AjaxActionComponent.broadcast(AjaxActionComponent.java:55)
	org.ajax4jsf.component.AjaxViewRoot.processEvents(AjaxViewRoot.java:321)
	org.ajax4jsf.component.AjaxViewRoot.broadcastEvents(AjaxViewRoot.java:296)
	org.ajax4jsf.component.AjaxViewRoot.processPhase(AjaxViewRoot.java:253)
	org.ajax4jsf.component.AjaxViewRoot.processApplication(AjaxViewRoot.java:466)
	com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:82)
	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
	com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
	javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
	org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
	org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
	org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
	org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

root cause

javax.xml.ws.soap.SOAPFaultException: org.xml.sax.SAXParseException: Premature end of file.
	org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:84)
	org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:107)
	org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:579)
	org.jboss.ws.core.CommonClient.invoke(CommonClient.java:381)
	org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:291)
	org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
	org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
	$Proxy220.requestJudicialConsign(Unknown Source)
	org.trimps.consign.bean.ApplyConsignBean.create(ApplyConsignBean.java:32)
	sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	java.lang.reflect.Method.invoke(Method.java:597)
	org.apache.el.parser.AstValue.invoke(AstValue.java:170)
	org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276)
	org.apache.jasper.el.JspMethodExpression.invoke(JspMethodExpression.java:68)
	javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
	com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
	javax.faces.component.UICommand.broadcast(UICommand.java:387)
	org.ajax4jsf.component.AjaxActionComponent.broadcast(AjaxActionComponent.java:55)
	org.ajax4jsf.component.AjaxViewRoot.processEvents(AjaxViewRoot.java:321)
	org.ajax4jsf.component.AjaxViewRoot.broadcastEvents(AjaxViewRoot.java:296)
	org.ajax4jsf.component.AjaxViewRoot.processPhase(AjaxViewRoot.java:253)
	org.ajax4jsf.component.AjaxViewRoot.processApplication(AjaxViewRoot.java:466)
	com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:82)
	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
	com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
	javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
	org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
	org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
	org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
	org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

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

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


From do-not-reply at jboss.com  Mon May 11 22:53:58 2009
From: do-not-reply at jboss.com (lixun)
Date: Mon, 11 May 2009 22:53:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Help! Call Web service error!
Message-ID: <13509386.1242096838142.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Server log:


2009-05-12 10:27:43,296 DEBUG [org.jboss.wsf.stack.jbws.RequestHandlerImpl] (http-127.0.0.1-8080-1) BEGIN handleRequest: jboss.ws:context=trimps-case-intra-webservices,endpoint=TrimpsNewConsign
2009-05-12 10:27:43,296 DEBUG [org.jboss.ws.core.soap.MessageFactoryImpl] (http-127.0.0.1-8080-1) createMessage: [contentType=text/xml; charset=UTF-8]
2009-05-12 10:27:43,296 ERROR [STDERR] (http-127.0.0.1-8080-1) [Fatal Error] :-1:-1: Premature end of file.
2009-05-12 10:27:43,296 DEBUG [org.jboss.ws.metadata.umdm.EndpointMetaData] (http-127.0.0.1-8080-1) Configure SOAPBinding
2009-05-12 10:27:43,296 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] (http-127.0.0.1-8080-1) SOAP request exception
org.jboss.ws.core.CommonSOAPFaultException: org.xml.sax.SAXParseException: Premature end of file.
	at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:93)
	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:283)
	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:193)
	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:455)
	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295)
	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205)
	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
	at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
	at java.lang.Thread.run(Thread.java:619)
2009-05-12 10:27:43,296 ERROR [org.jboss.ws.core.jaxrpc.SOAPFaultHelperJAXRPC] (http-127.0.0.1-8080-1) SOAP request exception
javax.xml.rpc.soap.SOAPFaultException: org.xml.sax.SAXParseException: Premature end of file.
	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.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:496)
	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295)
	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205)
	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
	at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
	at java.lang.Thread.run(Thread.java:619)
2009-05-12 10:27:43,296 DEBUG [org.jboss.wsf.stack.jbws.RequestHandlerImpl] (http-127.0.0.1-8080-1) END handleRequest: jboss.ws:context=trimps-case-intra-webservices,endpoint=TrimpsNewConsign
2009-05-12 10:27:43,312 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] (http-127.0.0.1-8080-1) popMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at af0838 (Thread http-127.0.0.1-8080-1)
2009-05-12 10:27:43,328 DEBUG [org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP] (http-127.0.0.1-8080-2) getMimeHeaders from: {Date=[Tue, 12 May 2009 02:27:43 GMT], Transfer-Encoding=[chunked], NoThrowOnError=true, HEADER={SOAPAction="requestJudicialConsign", Content-Type=text/xml; charset=UTF-8}, ResponseCode=500, ResponseCodeMessage=Internal Server Error, ResponseHeaders={null=[HTTP/1.1 500 Internal Server Error], Transfer-Encoding=[chunked], Date=[Tue, 12 May 2009 02:27:43 GMT], Content-Type=[text/xml;charset=UTF-8], Connection=[close], Server=[Apache-Coyote/1.1], X-Powered-By=[Servlet 2.5; JBoss-5.0/JBossWeb-2.1]}, Connection=[close], Content-Type=[text/xml;charset=UTF-8], X-Powered-By=[Servlet 2.5; JBoss-5.0/JBossWeb-2.1], Server=[Apache-Coyote/1.1]}
2009-05-12 10:27:43,328 DEBUG [org.jboss.ws.core.soap.MessageFactoryImpl] (http-127.0.0.1-8080-2) createMessage: [contentType=text/xml; charset=UTF-8]
2009-05-12 10:27:43,328 DEBUG [org.jboss.remoting.InvokerRegistry] (http-127.0.0.1-8080-2) removed org.jboss.remoting.transport.http.HTTPClientInvoker at 15dc5d3 from registry
2009-05-12 10:27:43,328 DEBUG [org.jboss.ws.core.jaxws.handler.MessageContextJAXWS] (http-127.0.0.1-8080-2) Begin response processing
2009-05-12 10:27:43,328 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] (http-127.0.0.1-8080-2) popMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at b5cd50 (Thread http-127.0.0.1-8080-2)
2009-05-12 10:27:43,328 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] (http-127.0.0.1-8080-2) pushMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at 66aeb5 (Thread http-127.0.0.1-8080-2)
2009-05-12 10:27:43,328 DEBUG [org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS] (http-127.0.0.1-8080-2) unbindResponseMessage: {http://consign.trimps.org}requestJudicialConsign
2009-05-12 10:27:43,328 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] (http-127.0.0.1-8080-2) -----------------------------------
2009-05-12 10:27:43,328 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] (http-127.0.0.1-8080-2) Transitioning from XML_VALID to DOM_VALID
2009-05-12 10:27:43,328 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] (http-127.0.0.1-8080-2) -----------------------------------
2009-05-12 10:27:43,328 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] (http-127.0.0.1-8080-2) close
2009-05-12 10:27:43,328 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] (http-127.0.0.1-8080-2) close
2009-05-12 10:27:43,328 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] (http-127.0.0.1-8080-2) close
2009-05-12 10:27:43,328 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] (http-127.0.0.1-8080-2) popMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at 66aeb5 (Thread http-127.0.0.1-8080-2)
2009-05-12 10:27:43,328 ERROR [javax.enterprise.resource.webcontainer.jsf.application] (http-127.0.0.1-8080-2) javax.xml.ws.soap.SOAPFaultException: org.xml.sax.SAXParseException: Premature end of file.
javax.faces.el.EvaluationException: javax.xml.ws.soap.SOAPFaultException: org.xml.sax.SAXParseException: Premature end of file.
	at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102)
	at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
	at javax.faces.component.UICommand.broadcast(UICommand.java:387)
	at org.ajax4jsf.component.AjaxActionComponent.broadcast(AjaxActionComponent.java:55)
	at org.ajax4jsf.component.AjaxViewRoot.processEvents(AjaxViewRoot.java:321)
	at org.ajax4jsf.component.AjaxViewRoot.broadcastEvents(AjaxViewRoot.java:296)
	at org.ajax4jsf.component.AjaxViewRoot.processPhase(AjaxViewRoot.java:253)
	at org.ajax4jsf.component.AjaxViewRoot.processApplication(AjaxViewRoot.java:466)
	at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:82)
	at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
	at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
	at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
	at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
	at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
	at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
	at java.lang.Thread.run(Thread.java:619)
Caused by: javax.xml.ws.soap.SOAPFaultException: org.xml.sax.SAXParseException: Premature end of file.
	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:291)
	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
	at $Proxy220.requestJudicialConsign(Unknown Source)
	at org.trimps.consign.bean.ApplyConsignBean.create(ApplyConsignBean.java:32)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.apache.el.parser.AstValue.invoke(AstValue.java:170)
	at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276)
	at org.apache.jasper.el.JspMethodExpression.invoke(JspMethodExpression.java:68)
	at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
	... 37 more
2009-05-12 10:27:43,343 WARN  [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http-127.0.0.1-8080-2) #{applyConsignBean.create}: javax.xml.ws.soap.SOAPFaultException: org.xml.sax.SAXParseException: Premature end of file.
javax.faces.FacesException: #{applyConsignBean.create}: javax.xml.ws.soap.SOAPFaultException: org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:118)
	at javax.faces.component.UICommand.broadcast(UICommand.java:387)
	at org.ajax4jsf.component.AjaxActionComponent.broadcast(AjaxActionComponent.java:55)
	at org.ajax4jsf.component.AjaxViewRoot.processEvents(AjaxViewRoot.java:321)
	at org.ajax4jsf.component.AjaxViewRoot.broadcastEvents(AjaxViewRoot.java:296)
	at org.ajax4jsf.component.AjaxViewRoot.processPhase(AjaxViewRoot.java:253)
	at org.ajax4jsf.component.AjaxViewRoot.processApplication(AjaxViewRoot.java:466)
	at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:82)
	at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
	at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
	at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
	at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
	at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
	at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
	at java.lang.Thread.run(Thread.java:619)
Caused by: javax.faces.el.EvaluationException: javax.xml.ws.soap.SOAPFaultException: org.xml.sax.SAXParseException: Premature end of file.
	at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102)
	at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
	... 36 more
Caused by: javax.xml.ws.soap.SOAPFaultException: org.xml.sax.SAXParseException: Premature end of file.
	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:291)
	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
	at $Proxy220.requestJudicialConsign(Unknown Source)
	at org.trimps.consign.bean.ApplyConsignBean.create(ApplyConsignBean.java:32)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.apache.el.parser.AstValue.invoke(AstValue.java:170)
	at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276)
	at org.apache.jasper.el.JspMethodExpression.invoke(JspMethodExpression.java:68)
	at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
	... 37 more
2009-05-12 10:27:43,343 ERROR [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http-127.0.0.1-8080-2) JSF1054: (Phase ID: INVOKE_APPLICATION 5, View ID: /jsf/applyConsign.jsp) Exception thrown during phase execution: javax.faces.event.PhaseEvent[source=com.sun.faces.lifecycle.LifecycleImpl at f3db02]
2009-05-12 10:27:43,343 DEBUG [org.ajax4jsf.event.AjaxPhaseListener] (http-127.0.0.1-8080-2) Process after phase INVOKE_APPLICATION 5
2009-05-12 10:27:43,343 ERROR [org.ajax4jsf.webapp.BaseXMLFilter] (http-127.0.0.1-8080-2) Exception in the filter chain
javax.servlet.ServletException: #{applyConsignBean.create}: javax.xml.ws.soap.SOAPFaultException: org.xml.sax.SAXParseException: Premature end of file.
	at javax.faces.webapp.FacesServlet.service(FacesServlet.java:277)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
	at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
	at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
	at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
	at java.lang.Thread.run(Thread.java:619)
Caused by: javax.faces.FacesException: #{applyConsignBean.create}: javax.xml.ws.soap.SOAPFaultException: org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:118)
	at javax.faces.component.UICommand.broadcast(UICommand.java:387)
	at org.ajax4jsf.component.AjaxActionComponent.broadcast(AjaxActionComponent.java:55)
	at org.ajax4jsf.component.AjaxViewRoot.processEvents(AjaxViewRoot.java:321)
	at org.ajax4jsf.component.AjaxViewRoot.broadcastEvents(AjaxViewRoot.java:296)
	at org.ajax4jsf.component.AjaxViewRoot.processPhase(AjaxViewRoot.java:253)
	at org.ajax4jsf.component.AjaxViewRoot.processApplication(AjaxViewRoot.java:466)
	at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:82)
	at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
	at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
	at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
	... 26 more
Caused by: javax.faces.el.EvaluationException: javax.xml.ws.soap.SOAPFaultException: org.xml.sax.SAXParseException: Premature end of file.
	at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102)
	at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
	... 36 more
Caused by: javax.xml.ws.soap.SOAPFaultException: org.xml.sax.SAXParseException: Premature end of file.
	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:291)
	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
	at $Proxy220.requestJudicialConsign(Unknown Source)
	at org.trimps.consign.bean.ApplyConsignBean.create(ApplyConsignBean.java:32)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.apache.el.parser.AstValue.invoke(AstValue.java:170)
	at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276)
	at org.apache.jasper.el.JspMethodExpression.invoke(JspMethodExpression.java:68)
	at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
	... 37 more
2009-05-12 10:27:43,343 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/trimps-consign-app].[Faces Servlet]] (http-127.0.0.1-8080-2) Servlet.service() for servlet Faces Servlet threw exception
javax.xml.ws.soap.SOAPFaultException: org.xml.sax.SAXParseException: Premature end of file.
	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:291)
	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
	at $Proxy220.requestJudicialConsign(Unknown Source)
	at org.trimps.consign.bean.ApplyConsignBean.create(ApplyConsignBean.java:32)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.apache.el.parser.AstValue.invoke(AstValue.java:170)
	at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276)
	at org.apache.jasper.el.JspMethodExpression.invoke(JspMethodExpression.java:68)
	at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
	at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
	at javax.faces.component.UICommand.broadcast(UICommand.java:387)
	at org.ajax4jsf.component.AjaxActionComponent.broadcast(AjaxActionComponent.java:55)
	at org.ajax4jsf.component.AjaxViewRoot.processEvents(AjaxViewRoot.java:321)
	at org.ajax4jsf.component.AjaxViewRoot.broadcastEvents(AjaxViewRoot.java:296)
	at org.ajax4jsf.component.AjaxViewRoot.processPhase(AjaxViewRoot.java:253)
	at org.ajax4jsf.component.AjaxViewRoot.processApplication(AjaxViewRoot.java:466)
	at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:82)
	at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
	at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
	at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
	at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
	at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
	at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
	at java.lang.Thread.run(Thread.java:619)

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

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


From do-not-reply at jboss.com  Tue May 12 01:45:26 2009
From: do-not-reply at jboss.com (meet_ravip)
Date: Tue, 12 May 2009 01:45:26 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - how to make webservice interface method
	to refer the fault c
Message-ID: <22335414.1242107126240.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi,
We are doing the parlay-x webservice development for its sendsms api using topdown approach(wsdl to java) with jboss jax-ws tools(wsconsume).This particular wsdl files splitted into interface file,service file,some common xsds and all.
When we run the wsconsume tool with jax-ws binding file it generates the classes on the specified packages.But the generated webservice interface class referring the fault classes on the same package instead of referring our custom package.i can able to rename the fault classes using jax-ws binding file,but i couldn't stop it creating the fault classes and refer it to other package class.
 Is there any way to resolve this?.

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

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


From do-not-reply at jboss.com  Tue May 12 07:00:44 2009
From: do-not-reply at jboss.com (jarkko@jab.fi)
Date: Tue, 12 May 2009 07:00:44 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: java.lang.LinkageError: loader
	constraint violation:(In
Message-ID: <14054948.1242126044901.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I'm too having this problem.
 I'm using old project infrastructure which used work ok on JBoss 4.2.x, but now with JBoss as 5.0 the web service call fails;

13:55:58,350 ERROR [STDERR] Exception in thread "Thread-32" 
13:55:58,350 ERROR [STDERR] java.lang.LinkageError: loader constraint violation: when resolving method "javax.xml.ws.Service.(Ljava/net/URL;Ljavax/xml/namespace/QName;)V" the class loader (instance of org/jboss/classloader/spi/base/BaseClassLoader) of the current class, XYZ_Service, and the class loader (instance of ) for resolved class, javax/xml/ws/Service, have different Class objects for the type javax/xml/namespace/QName used in the signature
1

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

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


From do-not-reply at jboss.com  Tue May 12 07:07:37 2009
From: do-not-reply at jboss.com (GajananM)
Date: Tue, 12 May 2009 07:07:37 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: java.lang.LinkageError: loader
	constraint violation:(In
Message-ID: <22582720.1242126457828.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Dowload the Jaxws API from 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230413#4230413
and run the ant as per the instruction.
using this i am able to run the jaxws webservices.

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

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


From do-not-reply at jboss.com  Tue May 12 10:11:02 2009
From: do-not-reply at jboss.com (brainiac)
Date: Tue, 12 May 2009 10:11:02 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Using Jax-WS RI with JBoss AS 4.2.3.GA
Message-ID: <32780930.1242137464157.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I have a webapp, deployed as a war, which exposed a Web Service implementing jaxws standard. A requirement for my webapp is deploy on multiple AS (Tomcat, JBoss and WAS).
In my war i have jax-ws ri distribution (into WEB-INF/lib).
web.xml contains the jaxws listener:
    
        <listener-class>com.sun.xml.ws.transport.http.servlet.WSServletContextListener</listener-class>
    

When i deploy my webapp on JBOSS (v.4.2.3.GA) i have the following error:

2009-05-12 15:15:38,608 ERROR [STDERR] 12-mag-2009 15.15.38 com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
INFO: WSSERVLET12: JAX-WS context listener initializing
2009-05-12 15:15:44,311 ERROR [STDERR] 12-mag-2009 15.15.44 com.sun.xml.ws.transport.http.servlet.WSServletDelegate 
INFO: WSSERVLET14: JAX-WS servlet initializing

If I remove the Ws Listener from web.xml the errror disappears, but the war does not deploy on Tomcat

Any suggestion?

Thanks in advance


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

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


From koxkorrita at laudio.info  Tue May 12 14:03:05 2009
From: koxkorrita at laudio.info (Koxkorrita)
Date: Tue, 12 May 2009 20:03:05 +0200
Subject: [jbossws-users] I cannot load my server if i dont get localhost
In-Reply-To: <22335414.1242107126240.JavaMail.jboss@tmp3.prod.atl2.jboss.com>
References: <22335414.1242107126240.JavaMail.jboss@tmp3.prod.atl2.jboss.com>
Message-ID: <006e01c9d32b$e6719e30$b354da90$@info>

Hello

I have one configuration problem.

i have into one linux one jboss 4.2
if i load my ws or application calling to the localhost the servers (jboss)
shows me but if i try to get the applications or WSs from other pc the jboss
doesn't serve them.

When i start my jboss apears that it is listened into tje 127.0.0.1 8080.
how can i made (what and into which file must i configure) for my jboss
listen into all ips ?

thanks






From do-not-reply at jboss.com  Tue May 12 17:52:57 2009
From: do-not-reply at jboss.com (prince_amit)
Date: Tue, 12 May 2009 17:52:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - How to create webservice soap over JMS
	using jboss messaging
Message-ID: <2686566.1242165177903.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

can anyone send me how to create webservice soap over JMS

and if possible scrrenshot

thanx regards

amit

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

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


From do-not-reply at jboss.com  Tue May 12 22:15:09 2009
From: do-not-reply at jboss.com (lixun)
Date: Tue, 12 May 2009 22:15:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Help! Call Web service error!
Message-ID: <44362.1242180909838.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I migrate the Jboss platform to Linux, Bug fixed!

Any one tell me why?


How to fix this bug in windows platform?

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

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


From do-not-reply at jboss.com  Tue May 12 23:08:10 2009
From: do-not-reply at jboss.com (goldberg.howard)
Date: Tue, 12 May 2009 23:08:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - dynamic proxy client fails
Message-ID: <1236101.1242184090170.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

AS 5.01
Jdk 1.60_13
eclipse 3.4 with jboss tools 3.01
centos 5.2

I can't get a dynamic proxy client to work--fails with the infamous runtime modeler     error.  See service and client source below.  Deploys without problems, 1 warning about deployment descriptor for context.  In log file, proxy classes are generated.  If I create a client with static stubs using wsconsume, client succeeds.

Can someone verify for me that service and client work.  This was a clean install, and code fails on a separate machine and under 5.1.  Haven't seen any similar issues via Google or in the user forum.  Am I missing a configuration step, or is there some kind of classloader issue?  This is pretty vanilla.  Thanks for your help!

Interface:

package org.goldberg;

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

@WebService(targetNamespace="http://goldberg.org/hello")
@Remote
public interface Hello {
	String echo(String source);
}

Implementation:

package org.goldberg;

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

import org.goldberg.Hello;

public 
@WebService(targetNamespace="http://goldberg.org/hello",
		endpointInterface="org.goldberg.Hello")
@Stateless class HelloBean implements Hello {

	public String echo(String source) {
		// TODO Auto-generated method stub
		return source;
	}

}
Dynamic Proxy Client--fails at getPort

package org.goldberg.test;

import java.net.URL;

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

import org.goldberg.Hello;

public class TestWS {

	/**
	 * @param args
	 */
	public static void main(String[] args) {
		// TODO Auto-generated method stub
		 String wsdlURLString = "http://localhost:8080/HelloWS/HelloBean?wsdl";  
		 String serviceName = "HelloBeanService";  
		 String nameSpaceURI = "http://goldberg.org/hello";  
		 //String portName = "HelloPort";
		 try {
		 URL wsdlURL = new URL(wsdlURLString);  
		 Service HelloService = Service.create(wsdlURL, new QName(nameSpaceURI,serviceName));
		 Hello hello = HelloService.getPort(Hello.class);
		 System.out.println(hello.echo("I'm working!"));
		 } catch (Exception e) {e.printStackTrace();}
	}

}


Deployment warning
22:34:57,486 INFO  [DefaultEndpointRegistry] register: jboss.ws:context=HelloWS,endpoint=HelloBean
22:34:59,939 INFO  [WSDLFilePublisher] WSDL published to: file:/usr/local/jboss/jboss-5.0.1.GA/server/default/data/wsdl/HelloWS.jar/HelloBeanService6116139100620733119.wsdl
22:34:59,972 INFO  [TomcatDeployment] deploy, ctxPath=/HelloWS
22:35:00,034 WARN  [config] Unable to process deployment descriptor for context '/HelloWS'
22:35:01,023 INFO  [Http11Protocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080
22:35:01,064 INFO  [AjpProtocol] Starting Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009
22:35:01,075 INFO  [ServerImpl] JBoss (Microcontainer) [5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902232048)] Started in 49s:915ms

Proxy Classes generated from log file
2009-05-12 22:34:58,776 DEBUG [org.jboss.ws.core.jaxws.DynamicWrapperGenerator] (main) Generating wrapper: org.goldberg.jaxws.Echo
2009-05-12 22:34:58,788 DEBUG [org.jboss.ws.core.jaxws.DynamicWrapperGenerator] (main) Generating wrapper: org.goldberg.jaxws.EchoResponse
2009-05-12 22:34:58,802 DEBUG [org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder] (main) JAXBContext [types=[class org.goldberg.jaxws.Echo, class org.goldberg.jaxws.EchoResponse],tns=http://goldberg.org/hello]

Client error:  Wrapper class not found
com.sun.xml.ws.model.RuntimeModelerException: runtime modeler error: Wrapper class org.goldberg.jaxws.Echo is not found. Have you run APT to generate them?
	at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:287)
	at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:596)
	at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:543)
	at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:371)
	at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:258)
	at com.sun.xml.ws.client.WSServiceDelegate.addSEI(WSServiceDelegate.java:633)
	at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:328)
	at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:311)
	at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:339)
	at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:343)
	at javax.xml.ws.Service.getPort(Service.java:161)
	at org.goldberg.test.TestWS.main(TestWS.java:25)


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

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


From do-not-reply at jboss.com  Wed May 13 05:34:44 2009
From: do-not-reply at jboss.com (alkahere)
Date: Wed, 13 May 2009 05:34:44 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Trouble mapping xsd to package in a
	binding file
Message-ID: <32465730.1242207284664.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

In my web services implementation I have wsdl definition which are divided into three files for each service. For example a AAA service wsdl is defined by aaa_service.wsdl, aaa_interface.wsdl and aaa_types.xsd files. As the names suggest aaa_service.wsdl contains binding and port details,  aaa_interface.wsdl contains types and messages information and aaa_types.xsd contains object definitions. Also aaa_interface.wsdl imports  aaa_types.xsd, which intern gets imported by aaa_service.wsdl We are using wsconsume to generate artifacts for both client and server side. Having said that,
1) If I create binding file to keep all the classes of aaa_types.xsd in common package I get the following error "aaa_types.xsd is not a part of this compilation.". Is there anyway I can resolve this problem without changing my wsdl?
2) Is there a way I can generate client-side and server-side artifacts separately, like it is in wscompile?


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

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


From do-not-reply at jboss.com  Wed May 13 09:25:58 2009
From: do-not-reply at jboss.com (ewinston)
Date: Wed, 13 May 2009 09:25:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Cannot find service endpoint error when
	deploying ear with w
Message-ID: <27136752.1242221159005.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi, I am having a problem when I try to deploy an ear that conatins stateless session beans exposed as web services on JBoss 4.2.3.  The problem only arises however if I attempt to inject an entity manager or entity manager factory into the session bean, or if I inject anything that has a dependency on that into the session bean.  If I take it out, all works fine.  Also, if I leave in the injection of the entity manager and take out the @WebService annotation the bean deploys fine.

I have tried injecting via a setter and also injecting into the JNDI context for the bean but I still get the same thing.

The ear is totally self contained, so the datasource definition resides in the ear.  And the ear is made up of 1 ejb module, 1 war module, and common logic packaged as a jar in the ear/lib directory.

Is this a known problem or is there a workaround?  I did try doing some searches but I didn't have much luck in finding a solution.  I need to be able to persist data based on the web service request.

Thanks,
Edward

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

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


From do-not-reply at jboss.com  Wed May 13 10:22:54 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Wed, 13 May 2009 10:22:54 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Help! Call Web service error!
Message-ID: <25116203.1242224574972.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Perhaps you are picking up a stray JAR file on Windows. Do you have CLASSPATH set? You could try adding the -verbose:gc JVM option to the JAVA_OPTS in run.bat. This option prints the JAR file location for each class loaded - look for JAR files that are not in the jboss_home directory.

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

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


From do-not-reply at jboss.com  Thu May 14 03:44:51 2009
From: do-not-reply at jboss.com (angusm)
Date: Thu, 14 May 2009 03:44:51 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Tracing wsconsume
Message-ID: <8072813.1242287091598.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Peter:
(this is going to be a little long :-))


  | C:\Other\eclipseall\ws\hsi\mm7-client2\work>myrun
  | 
  | C:\Other\eclipseall\ws\hsi\mm7-client2\work>myconsume -k -s ../src -o tmp mm7.wsdl
  | "C:\Sun\AppServer\jdk\bin\java"  -Djava.endorsed.dirs="C:/jboss/jboss-4.2.2.GA\lib\endorsed" -Dlog4j.configura
  | tion=mylog4j.xml -classpath ";C:/Other/eclipseall/ws/hsi/mm7-client2/work;C:\Sun\AppServer\jdk/lib/tools.jar;C
  | :/jboss/jboss-4.2.2.GA/client/activation.jar;C:/jboss/jboss-4.2.2.GA/client/getopt.jar;C:/jboss/jboss-4.2.2.GA
  | /client/wstx.jar;C:/jboss/jboss-4.2.2.GA/client/jbossall-client.jar;C:/jboss/jboss-4.2.2.GA/client/log4j.jar;C
  | :/jboss/jboss-4.2.2.GA/client/mail.jar;C:/jboss/jboss-4.2.2.GA/client/jbossws-spi.jar;C:/jboss/jboss-4.2.2.GA/
  | client/jbossws-common.jar;C:/jboss/jboss-4.2.2.GA/client/jbossws-framework.jar;C:/jboss/jboss-4.2.2.GA/client/
  | jaxws-tools.jar;C:/jboss/jboss-4.2.2.GA/client/jaxws-rt.jar;C:/jboss/jboss-4.2.2.GA/client/stax-api.jar;C:/jbo
  | ss/jboss-4.2.2.GA/client/jaxb-api.jar;C:/jboss/jboss-4.2.2.GA/client/jaxb-impl.jar;C:/jboss/jboss-4.2.2.GA/cli
  | ent/jaxb-xjc.jar;C:/jboss/jboss-4.2.2.GA/client/streambuffer.jar;C:/jboss/jboss-4.2.2.GA/client/stax-ex.jar;C:
  | /jboss/jboss-4.2.2.GA/client/javassist.jar;C:/jboss/jboss-4.2.2.GA/client/jboss-xml-binding.jar;C:/jboss/jboss
  | -4.2.2.GA/client/jbossws-native-client.jar;C:/jboss/jboss-4.2.2.GA/client/jbossws-native-core.jar;C:/jboss/jbo
  | ss-4.2.2.GA/client/jbossws-native-jaxws.jar;C:/jboss/jboss-4.2.2.GA/client/jbossws-native-jaxws-ext.jar;C:/jbo
  | ss/jboss-4.2.2.GA/client/jbossws-native-jaxrpc.jar;C:/jboss/jboss-4.2.2.GA/client/jbossws-native-saaj.jar" org
  | .jboss.wsf.spi.tools.cmd.WSConsume -k -s ../src -o tmp mm7.wsdl
  | parsing WSDL...
  | 
  | 
  | generating code...
  | 
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\AddressCodingType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\AddressType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\AnyDataType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\CancelReqType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\CapabilitiesType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ChargedPartyType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ContentClassType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ContentReferenceType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\DeliverReqType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\DeliverRspType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\DeliveryConditionType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\DeliveryReportReqType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ExtendedcancelReqType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ExtendedcancelRspType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ExtendedcancelresponseStatusType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ExtendedreplaceReqType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ExtendedreplaceRspType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\GenericRSReqType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\GenericResponseType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\GenericVASPRequestType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\MM7.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\MM7Service.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\MMStatusExtensionType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\MessageClassType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\MmDeliveryStatusType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\MmReadStatusType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\MultiAddressType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ObjectFactory.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\PreviouslySentByDateTime.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\PreviouslySentByType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\PriorityType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ReadReplyReqType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\RecipientsType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ReplaceReqType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ResponseStatusType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\SenderIDType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ServiceCodeType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\SubmitReqType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\SubmitRspType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\TransactionID.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\UserAgentDateTimeType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\UserAgentInfoType.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\package-info.java
  | org\xmlsoap\schemas\soap\envelope\Body.java
  | org\xmlsoap\schemas\soap\envelope\Detail.java
  | org\xmlsoap\schemas\soap\envelope\Envelope.java
  | org\xmlsoap\schemas\soap\envelope\Fault.java
  | org\xmlsoap\schemas\soap\envelope\Header.java
  | org\xmlsoap\schemas\soap\envelope\ObjectFactory.java
  | org\xmlsoap\schemas\soap\envelope\package-info.java
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\runtime\ZeroOneBooleanAdapter.java
  | 
  | compiling code...
  | 
  | javac -d C:\Other\eclipseall\ws\hsi\mm7-client2\work\tmp -classpath ;C:/Other/eclipseall/ws/hsi/mm7-client2/wo
  | rk;C:\Sun\AppServer\jdk/lib/tools.jar;C:/jboss/jboss-4.2.2.GA/client/activation.jar;C:/jboss/jboss-4.2.2.GA/cl
  | ient/getopt.jar;C:/jboss/jboss-4.2.2.GA/client/wstx.jar;C:/jboss/jboss-4.2.2.GA/client/jbossall-client.jar;C:/
  | jboss/jboss-4.2.2.GA/client/log4j.jar;C:/jboss/jboss-4.2.2.GA/client/mail.jar;C:/jboss/jboss-4.2.2.GA/client/j
  | bossws-spi.jar;C:/jboss/jboss-4.2.2.GA/client/jbossws-common.jar;C:/jboss/jboss-4.2.2.GA/client/jbossws-framew
  | ork.jar;C:/jboss/jboss-4.2.2.GA/client/jaxws-tools.jar;C:/jboss/jboss-4.2.2.GA/client/jaxws-rt.jar;C:/jboss/jb
  | oss-4.2.2.GA/client/stax-api.jar;C:/jboss/jboss-4.2.2.GA/client/jaxb-api.jar;C:/jboss/jboss-4.2.2.GA/client/ja
  | xb-impl.jar;C:/jboss/jboss-4.2.2.GA/client/jaxb-xjc.jar;C:/jboss/jboss-4.2.2.GA/client/streambuffer.jar;C:/jbo
  | ss/jboss-4.2.2.GA/client/stax-ex.jar;C:/jboss/jboss-4.2.2.GA/client/javassist.jar;C:/jboss/jboss-4.2.2.GA/clie
  | nt/jboss-xml-binding.jar;C:/jboss/jboss-4.2.2.GA/client/jbossws-native-client.jar;C:/jboss/jboss-4.2.2.GA/clie
  | nt/jbossws-native-core.jar;C:/jboss/jboss-4.2.2.GA/client/jbossws-native-jaxws.jar;C:/jboss/jboss-4.2.2.GA/cli
  | ent/jbossws-native-jaxws-ext.jar;C:/jboss/jboss-4.2.2.GA/client/jbossws-native-jaxrpc.jar;C:/jboss/jboss-4.2.2
  | .GA/client/jbossws-native-saaj.jar -Xbootclasspath/p:C:\jboss\jboss-4.2.2.GA\client\jbossws-native-jaxws-ext.j
  | ar;C:\jboss\jboss-4.2.2.GA\client\jaxb-api.jar C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ft
  | p\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\AddressCodingType.java C:\Other\eclipseall\ws\hsi\mm7-
  | client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\AddressType.java C:\Ot
  | her\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_
  | 1_4\AnyDataType.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series
  | \_23_140\schema\rel_6_mm7_1_4\CancelReqType.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\
  | ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\CapabilitiesType.java C:\Other\eclipseall\ws\hsi\mm7
  | -client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ChargedPartyType.java
  |  C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_
  | 6_mm7_1_4\ContentClassType.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive
  | \_23_series\_23_140\schema\rel_6_mm7_1_4\ContentReferenceType.java C:\Other\eclipseall\ws\hsi\mm7-client2\work
  | \..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\DeliverReqType.java C:\Other\eclip
  | seall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\Deliv
  | erRspType.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_1
  | 40\schema\rel_6_mm7_1_4\DeliveryConditionType.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gp
  | p\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\DeliveryReportReqType.java C:\Other\eclipseall\ws\
  | hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\Extendedcancel
  | ReqType.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_140
  | \schema\rel_6_mm7_1_4\ExtendedcancelRspType.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\
  | ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ExtendedcancelresponseStatusType.java C:\Other\eclip
  | seall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\Exten
  | dedreplaceReqType.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_seri
  | es\_23_140\schema\rel_6_mm7_1_4\ExtendedreplaceRspType.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src
  | \org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\GenericRSReqType.java C:\Other\eclipseall
  | \ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\GenericRes
  | ponseType.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_1
  | 40\schema\rel_6_mm7_1_4\GenericVASPRequestType.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3g
  | pp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\MM7.java C:\Other\eclipseall\ws\hsi\mm7-client2\w
  | ork\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\MM7Service.java C:\Other\eclips
  | eall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\MMStat
  | usExtensionType.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series
  | \_23_140\schema\rel_6_mm7_1_4\MessageClassType.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3g
  | pp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\MmDeliveryStatusType.java C:\Other\eclipseall\ws\
  | hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\MmReadStatusTy
  | pe.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_140\sche
  | ma\rel_6_mm7_1_4\MultiAddressType.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\
  | archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ObjectFactory.java C:\Other\eclipseall\ws\hsi\mm7-client2\work
  | \..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\PreviouslySentByDateTime.java C:\O
  | ther\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7
  | _1_4\PreviouslySentByType.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\
  | _23_series\_23_140\schema\rel_6_mm7_1_4\PriorityType.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\o
  | rg\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ReadReplyReqType.java C:\Other\eclipseall\w
  | s\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\RecipientsTy
  | pe.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_140\sche
  | ma\rel_6_mm7_1_4\ReplaceReqType.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\ar
  | chive\_23_series\_23_140\schema\rel_6_mm7_1_4\ResponseStatusType.java C:\Other\eclipseall\ws\hsi\mm7-client2\w
  | ork\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\SenderIDType.java C:\Other\ecli
  | pseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\Serv
  | iceCodeType.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23
  | _140\schema\rel_6_mm7_1_4\SubmitReqType.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\
  | specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\SubmitRspType.java C:\Other\eclipseall\ws\hsi\mm7-client
  | 2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\TransactionID.java C:\Other\
  | eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\
  | UserAgentDateTimeType.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_
  | series\_23_140\schema\rel_6_mm7_1_4\UserAgentInfoType.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\
  | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\package-info.java C:\Other\eclipseall\ws\h
  | si\mm7-client2\work\..\src\org\xmlsoap\schemas\soap\envelope\Body.java C:\Other\eclipseall\ws\hsi\mm7-client2\
  | work\..\src\org\xmlsoap\schemas\soap\envelope\Detail.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\o
  | rg\xmlsoap\schemas\soap\envelope\Envelope.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\xmlsoap\
  | schemas\soap\envelope\Fault.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\xmlsoap\schemas\soap\e
  | nvelope\Header.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\xmlsoap\schemas\soap\envelope\Objec
  | tFactory.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\xmlsoap\schemas\soap\envelope\package-inf
  | o.java C:\Other\eclipseall\ws\hsi\mm7-client2\work\..\src\org\_3gpp\ftp\specs\archive\_23_series\_23_140\schem
  | a\rel_6_mm7_1_4\runtime\ZeroOneBooleanAdapter.java
  | 
  | C:\Other\eclipseall\ws\hsi\mm7-client2\work>


  | C:\Other\eclipseall\ws\hsi\mm7-client2\work>dir
  |  Le volume dans le lecteur C n'a pas de nom.
  |  Le num????ro de s????rie du volume est D095-6491
  | 
  |  R????pertoire de C:\Other\eclipseall\ws\hsi\mm7-client2\work
  | 
  | 14/05/2009  09:35    <REP>          .
  | 14/05/2009  09:35    <REP>          ..
  | 07/05/2009  09:14                78 Copy of myrun.bat
  | 05/05/2009  09:39             1????897 mm7.wsdl
  | 14/05/2009  09:32             2????905 myconsume.bat
  | 07/05/2009  09:22             2????742 mylog4j.xml
  | 14/05/2009  09:35                38 myrun.bat
  | 04/05/2009  19:13                78 run-mm7-wsconsume.bat
  | 04/05/2009  19:12    <REP>          tmp
  | 30/12/2008  15:08             2????796 wsconsume.bat
  | 30/12/2008  15:05             2????895 wsprovide.bat
  | 30/12/2008  15:05             3????036 wsrunclient.bat
  | 30/12/2008  15:05             2????414 wstools.bat
  |               10 fichier(s)           18????879 octets
  |                3 R????p(s)  41????912????639????488 octets libres

<?xml version="1.0" encoding="UTF-8"?>
  | <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
  | 
  | <!-- ===================================================================== -->
  | <!--                                                                       -->
  | <!--  Log4j Configuration                                                  -->
  | <!--                                                                       -->
  | <!-- ===================================================================== -->
  | 
  | <!-- $Id: log4j.xml,v 1.1 2007/07/25 13:19:52 bwalpole Exp $ -->
  | 
  | <!--
  |    | For more configuration infromation and examples see the Jakarta Log4j
  |    | owebsite: http://jakarta.apache.org/log4j
  |  -->
  | 
  | <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/" debug="false">
  | 
  | 
  | 
  |    <!-- ============================== -->
  |    <!-- Append messages to the console -->
  |    <!-- ============================== -->
  | 
  |    <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
  |       <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
  |       <param name="Target" value="System.out"/>
  |       <param name="Threshold" value="TRACE"/>
  | 
  |       <layout class="org.apache.log4j.PatternLayout">
  |          <!-- The default pattern: Date Priority [Category] Message\n -->
  |          <param name="ConversionPattern" value="%d{ABSOLUTE} %-5p [%c{1}] %m%n"/>
  |       </layout>
  |    </appender>
  |    
  |    
  |       <appender name="FILE" class="org.jboss.logging.appender.DailyRollingFileAppender">
  |       <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
  |       <param name="File" value="C:/TempAm/wsconsume.log"/>
  |       <param name="Append" value="false"/>
  | 
  |       <!-- Rollover at midnight each day -->
  |       <param name="DatePattern" value="'.'yyyy-MM-dd"/>
  | 
  |       <!-- Rollover at the top of each hour
  |       <param name="DatePattern" value="'.'yyyy-MM-dd-HH"/>
  |       -->
  | 
  |       <layout class="org.apache.log4j.PatternLayout">
  |          <!-- The default pattern: Date Priority [Category] Message\n -->
  |          <param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
  | 
  |          <!-- The full pattern: Date MS Priority [Category] (Thread:NDC) Message\n
  |          <param name="ConversionPattern" value="%d %-5r %-5p [%c] (%t:%x) %m%n"/>
  |           -->
  |       </layout>
  |    </appender>
  | 
  |     
  |    <category name="org">
  |      <priority value="TRACE" />
  |    </category>
  |    
  |    <category name="com">
  |      <priority value="INFO" />
  |    </category>
  |   
  |   
  | 
  |    <!-- ======================= -->
  |    <!-- Setup the Root category -->
  |    <!-- ======================= -->
  | 
  |    <root>
  |       <appender-ref ref="CONSOLE"/>
  | 	  <appender-ref ref="FILE"/>
  |    </root>
  | 
  | 
  | 
  | </log4j:configuration>
  | 

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

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



From do-not-reply at jboss.com  Thu May 14 05:02:14 2009
From: do-not-reply at jboss.com (meet_ravip)
Date: Thu, 14 May 2009 05:02:14 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JAXWS WSConsume Custom Defined Package
	Code Generation Issue
Message-ID: <5701283.1242291734175.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi,
We are doing the webservice development using topdown approach(wsdl to java) with jboss jax-ws tools(wsconsume).This particular wsdl files splitted into interface file,service file,some common xsds and all.
When we run the wsconsume tool with jax-ws binding file it generates the classes on the specified packages.But whichever the xsd or wsdl files imported from outside of the service wsdl file we couldn't specify to generate the custom package classes.
Please let me know how to resolve this.

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

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


From do-not-reply at jboss.com  Thu May 14 08:00:20 2009
From: do-not-reply at jboss.com (prince_amit)
Date: Thu, 14 May 2009 08:00:20 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - problem while running jboss quickstart
	webservice_producer
Message-ID: <21621410.1242302420445.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

hi, can anyone tell me why this example not giving any output for JMS endpoint expose by the webservice.

rest is working[Http,Socket]

only problem with JMS

when I started exploring the code give sendMessage.java
I found output is directed toward file
but no code which call the output from the file to display on console.


thanx with

regards

amit

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

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


From do-not-reply at jboss.com  Thu May 14 09:48:20 2009
From: do-not-reply at jboss.com (veneetr)
Date: Thu, 14 May 2009 09:48:20 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - [Urgent]: EJBs and web services in
	Jboss a/s 4.2.2 GA
Message-ID: <11103768.1242308900105.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi all,


I just wanted to ask for a help in a scenario that i am facing:

I have a Application that relies on EJBs for Business Logic

I basically use the Jboss A/s[4.2.2 GA] server for the same and now there is a need to Expose these bean methods through a web service
so that our web team can make use of the same Business logic.


Currently i have implemented a End point interface that my Bean class implements so that i can expose
my bean methods to the web team

Req:
I want to create a separate Enterprise Bean which resides in the same JVM as my Application bean , and acts as a wrapper for my application bean


Also,
Further elaboration of the problem is as follows:

THE existing Application beans Remote interface has all the business methods that i want to expose.

The new bean should act as a delegate which intercepts the web clients call extracts the request from the call
and passes it to the application bean methods.



So this basically requires that new bean should be able to communicate with my application bean (Which is BTW a stateless session bean)
and pass on clients requests to the same.


Kindly provide suggestion for the same or any ideas as soon as possible


-- 
thanks again
veneet

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

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


From do-not-reply at jboss.com  Thu May 14 10:14:50 2009
From: do-not-reply at jboss.com (jayblanc54)
Date: Thu, 14 May 2009 10:14:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Implementing WS-Security Usename
	Token Profile Authentic
Message-ID: <33441505.1242310490113.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi, 

I've tested the authentication using Digest Password

1. JBoss AS 5.0.1.GA
2. JBOSS WS native 3.0.5.GA
3. WebService is implemented using an EJB3 Endpoint.
4. Client is generated using standard JAXWS (with maven) but executed using jbossws-native-client
5. JDK 6 (using -Djava.endorsed.dirs=${jboss.home}/lib/endorsed during client execution)
6. Username Token is configured to produce a PasswordDigest and not a clear password.

Everything works fine using the jboss-native-client 

2 problems appears also :

1. If I'm using SOAPUI to generate a SOAP call, in the server side, password does not match. (If I'm using a configuration with no digest, the SOAPUI call works fine). I assume there is a difference between the SOAPUI generated Digest and the JBoss generated Digest but what is this difference ?

2. The way to put UserName and Password on the client side is : 

 
  | AuthenticationService_Service service = new AuthenticationService_Service();
  | AuthenticationService port = service.getAuthenticationService();
  | 
  | ((StubExt) port).setConfigName("Standard WSSecurity Client");
  | 
  | Map<String, Object> reqContext = ((BindingProvider)port).getRequestContext();
  | reqContext.put(BindingProvider.USERNAME_PROPERTY, "kermit");
  | reqContext.put(BindingProvider.PASSWORD_PROPERTY, "thefrog");
  | 
  | String connectedUser = port.getConnectedUserIdentifier();
  | logger.info("Connected user : " + connectedUser);
  | assertTrue(connectedUser.equals("kermit"));
  | 

Then the WSSecurityHandlerClient take this HTTP header information to generate the correct wsse SAOP header assertion, calculating a password digest of the clear password provided. The problem is that the HTTP header information is not removed and is visible clearely in the HTTP header... So the password is well encoded using a digest in the SOAP header but not in the HTTP header. Is it an issue or is there any other way to give Username/Password information to the WSSecurityHandlerClient ?

3. Is there is some code sample that show how to use SAML instead of Usernam/Token ?

If you capture trames using Wireshar

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

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


From do-not-reply at jboss.com  Thu May 14 16:37:19 2009
From: do-not-reply at jboss.com (ewinston)
Date: Thu, 14 May 2009 16:37:19 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Cannot find service endpoint error
	when deploying ear wi
Message-ID: <5925645.1242333439716.JavaMail.jboss@tmp3.prod.atl2.jboss.com>


  | 15:15:51,330 INFO  [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.entity.PersistenceUnitDeployment
  | 15:15:51,345 INFO  [JmxKernelAbstraction] installing MBean: persistence.units:ear=WebAlertDataCollection-0.2.2-SNAPSHOT.ear,jar=ejb-0.2.2-SNAPSHOT.jar,unitName=WebAlertDataCollection-PU with dependencies:
  | 15:15:51,346 INFO  [JmxKernelAbstraction] 	jboss.jca:name=WebAlertDataCollectionXADS,service=DataSourceBinding
  | 15:15:51,742 INFO  [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer
  | 15:15:51,765 INFO  [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=WebAlertDataCollection-0.2.2-SNAPSHOT.ear,jar=ejb-0.2.2-SNAPSHOT.jar,name=VSMAlertRegistration,service=EJB3 with dependencies:
  | 15:15:51,765 INFO  [JmxKernelAbstraction] 	persistence.units:ear=WebAlertDataCollection-0.2.2-SNAPSHOT.ear,jar=ejb-0.2.2-SNAPSHOT.jar,unitName=WebAlertDataCollection-PU
  | 15:15:51,765 INFO  [JmxKernelAbstraction] 	jboss.j2ee:ear=WebAlertDataCollection-0.2.2-SNAPSHOT.ear,jar=ejb-0.2.2-SNAPSHOT.jar,name=SubscriptionMaintenance,service=EJB3
  | 15:15:51,767 INFO  [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer
  | 15:15:51,767 INFO  [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=WebAlertDataCollection-0.2.2-SNAPSHOT.ear,jar=ejb-0.2.2-SNAPSHOT.jar,name=VSMDataFilter,service=EJB3 with dependencies:
  | 15:15:51,832 INFO  [EJBContainer] STARTED EJB: com.vzw.vsm.opalarm.webalert.session.VSMFilter ejbName: VSMDataFilter
  | 15:15:51,892 INFO  [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer
  | 15:15:51,892 INFO  [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=WebAlertDataCollection-0.2.2-SNAPSHOT.ear,jar=ejb-0.2.2-SNAPSHOT.jar,name=SubscriptionMaintenance,service=EJB3 with dependencies:
  | 15:15:51,897 INFO  [EJBContainer] STARTED EJB: com.vzw.vsm.opalarm.webalert.session.SubscriptionScheduledAction ejbName: SubscriptionMaintenance
  | 15:15:52,585 INFO  [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer
  | 15:15:52,586 INFO  [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=WebAlertDataCollection-0.2.2-SNAPSHOT.ear,jar=ejb-0.2.2-SNAPSHOT.jar,name=ObjectPersister,service=EJB3 with dependencies:
  | 15:15:52,590 INFO  [EJBContainer] STARTED EJB: com.vzw.vsm.opalarm.webalert.session.ObjectPersister ejbName: ObjectPersister
  | 15:15:52,610 INFO  [EJB3Deployer] Deployed: file:/work/edward/vzw/environment/jboss-4.2.3.GA/server/vzw/tmp/deploy/tmp39565WebAlertDataCollection-0.2.2-SNAPSHOT.ear-contents/ejb-0.2.2-SNAPSHOT.jar
  | 15:15:52,834 INFO  [DefaultEndpointRegistry] register: jboss.ws:context=WebAlertDataCollection-0.2.2-SNAPSHOT-ejb-0.2.2-SNAPSHOT,endpoint=VSMAlertRegistration
  | 15:15:52,842 INFO  [DefaultEndpointRegistry] register: jboss.ws:context=WebAlertDataCollection-0.2.2-SNAPSHOT-ejb-0.2.2-SNAPSHOT,endpoint=VSMDataFilter
  | 15:15:52,979 INFO  [TomcatDeployer] deploy, ctxPath=/WebAlertDataCollection-0.2.2-SNAPSHOT-ejb-0.2.2-SNAPSHOT, warUrl=.../tmp/deploy/WebAlertDataCollection-0.2.2-SNAPSHOT.ear-ejb-0.2.2-SNAPSHOT.jar39566.war/
  | 15:15:56,320 INFO  [WSDLFilePublisher] WSDL published to: file:/work/edward/vzw/environment/jboss-4.2.3.GA/server/vzw/data/wsdl/WebAlertDataCollection-0.2.2-SNAPSHOT.ear/ejb-0.2.2-SNAPSHOT.jar/AlertRegistrationService39567.wsdl
  | 15:15:56,337 INFO  [WSDLFilePublisher] WSDL published to: file:/work/edward/vzw/environment/jboss-4.2.3.GA/server/vzw/data/wsdl/WebAlertDataCollection-0.2.2-SNAPSHOT.ear/ejb-0.2.2-SNAPSHOT.jar/VSMFilterService39570.wsdl
  | 15:15:56,625 ERROR [MainDeployer] Could not start deployment: file:/work/edward/vzw/environment/jboss-4.2.3.GA/server/vzw/tmp/deploy/tmp39565WebAlertDataCollection-0.2.2-SNAPSHOT.ear-contents/ejb-0.2.2-SNAPSHOT.jar
  | javax.xml.ws.WebServiceException: Cannot find service endpoint target: jboss.j2ee:name=VSMAlertRegistration,service=EJB3,jar=ejb-0.2.2-SNAPSHOT.jar,ear=WebAlertDataCollection-0.2.2-SNAPSHOT.ear
  | 	at org.jboss.wsf.container.jboss42.InvocationHandlerEJB3.init(InvocationHandlerEJB3.java:83)
  | 	at org.jboss.wsf.framework.deployment.DefaultLifecycleHandler.create(DefaultLifecycleHandler.java:51)
  | 	at org.jboss.wsf.framework.deployment.EndpointLifecycleDeploymentAspect.create(EndpointLifecycleDeploymentAspect.java:42)
  | 	at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:118)
  | 	at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97)
  | 	at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90)
  | 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
  | 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
  | 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  | 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
  | 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  | 

Here is part of the sack trace.  I will create a sample project that shows this problem.  It looks like the service gets installed but it isn't ready for use the first time it is accessed.  I have gotten around the injection problem by looking up the entity manager in JNDI, but it looks like now the entity manager is not cognizant of the injected USerTransaction and the fact that I have started a transaction there.  

I am using the JTA transaction type because elsewhere I need it.

Thanks again.
Edward

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

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


From do-not-reply at jboss.com  Thu May 14 21:58:33 2009
From: do-not-reply at jboss.com (goldberg.howard)
Date: Thu, 14 May 2009 21:58:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: dynamic proxy client fails
Message-ID: <2983206.1242352713879.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

After scanning the posts, I finally figured out I forgot to set endorsed library when executing the client:  
JDK 6 (using -Djava.endorsed.dirs=${jboss.home}/lib/endorsed during client execution)

You might consider putting this into the FAQ.

Howard

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

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


From do-not-reply at jboss.com  Fri May 15 12:15:42 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 15 May 2009 12:15:42 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Tracing wsconsume
Message-ID: <29024605.1242404142704.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Interesting. I don't get any log output either. This leads to two possibilities:

1) There is no logging code being performed in the classes used by wsconsume

2) One of the classes used by wsconsume is changing the logging settings, thus overriding the log4j.configuration setting.

My bet would be with option 1.

Back in the book, the tip on page 244 that you referred to specifically calls out issues with logging when running your client app, using wsrunclient.

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

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


From do-not-reply at jboss.com  Sun May 17 07:40:50 2009
From: do-not-reply at jboss.com (lixun)
Date: Sun, 17 May 2009 07:40:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Help! Call Web service error!
Message-ID: <1432246.1242560450688.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Thank you Peter, you give me some instructions! But I don't think my classpath error!

In my windows platform, Jboss 4.2.2 runs OK!

But Jboss 4.2.3 and Jboss 5.0.* runs error!

Follow your instruction, I add option -verbose:gc to JAVA_OPTS in run.bat, and I find following information in server.log:


sun.boot.class.path=D:\jboss\lib\endorsed\activation.jar;D:\jboss\lib\endorsed\jaxb-api.jar;D:\jboss\lib\endorsed\jbossws-native-jaxws-ext.jar;D:\jboss\lib\endorsed\jbossws-native-jaxws.jar;D:\jboss\lib\endorsed\jbossws-native-saaj.jar;D:\jboss\lib\endorsed\resolver.jar;D:\jboss\lib\endorsed\serializer.jar;D:\jboss\lib\endorsed\stax-api.jar;D:\jboss\lib\endorsed\xalan.jar;D:\jboss\lib\endorsed\xercesImpl.jar;C:\Program Files\Java\jdk1.6.0_04\jre\lib\resources.jar;C:\Program Files\Java\jdk1.6.0_04\jre\lib\rt.jar;C:\Program Files\Java\jdk1.6.0_04\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.6.0_04\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.6.0_04\jre\lib\jce.jar;C:\Program Files\Java\jdk1.6.0_04\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.6.0_04\jre\classes


I think all is OK!
Can you find sth wrong! Peter? 

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

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


From do-not-reply at jboss.com  Sun May 17 17:08:31 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Sun, 17 May 2009 17:08:31 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Help! Call Web service error!
Message-ID: <11621599.1242594511608.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

The info you posted does not have anything to do with this issue.

4.2.2 will run fine *IF* the stray JAR file matches what 4.2.2 uses.  The -verbose:class option is still the best way to track this down.

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

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


From do-not-reply at jboss.com  Mon May 18 02:27:06 2009
From: do-not-reply at jboss.com (naveen.sachar)
Date: Mon, 18 May 2009 02:27:06 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: ERROR [STDERR]
	javax.naming.NameNotFoundException: RuleE
Message-ID: <15537448.1242628026019.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi Raj,

Are you able to resolve this error? I am stuck on the same error when I try to deploy  my .ear package on 5.0.1 GA JBOSS. This package gets successfully deployed on jboss 4.3.x.

Thanks in advance.

- Naveen

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

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


From do-not-reply at jboss.com  Mon May 18 04:17:10 2009
From: do-not-reply at jboss.com (lixun)
Date: Mon, 18 May 2009 04:17:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Help! Call Web service error!
Message-ID: <2941589.1242634630415.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Thank you Peter!

Follow your instruction, I add -verbose:class to JAVA_OPTS to run.bat, when jboss starts, I get a long class load list,
In this list, I find these classes either loaded from jboss_home or java_home, and not know whick one is the stray JAR file.

With no solution, I copy the whole jboss directory to other windows platform, On new windows platform, I call web service successfully!

But On first windows platform, exception still occurs.

My two windows platform have similar Enviroment Setting, and I still in doubt what's the root cause of the exception.

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

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


From do-not-reply at jboss.com  Mon May 18 04:21:13 2009
From: do-not-reply at jboss.com (smartz)
Date: Mon, 18 May 2009 04:21:13 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - [ERROR] Invalid header
Message-ID: <25613845.1242634873906.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I am trying to consume a WSDL using wsconsume from JBossWS-3.1.2.GA, but I am unable to do so, if a wsdl:message/wsdl:part node defines a "type" instead of an "element".

The error I get is:

[wsconsume] Command invoked: org.jboss.wsf.spi.tools.cmd.WSConsume -k -o generated\classes -s generated\src -v wsdl.wsdl
  | [wsconsume] parsing WSDL...
  | [wsconsume] [ERROR] Invalid header "SoapHeader" in operation Operation: part must specify a "element" attribute
  | [wsconsume]   line 40 of file:/wsdl.wsdl

Please find the WSDL below. Please note it is a perfectly legal WSDL as per W3C http://www.w3.org/TR/wsdl#_message, and relative XSD, and that other JAX-WS implementations (CXF) consume the WSDL correctly.

<?xml version="1.0" encoding="UTF-8"?>
  | <definitions name="wsdl" targetNamespace="http://localhost/service/"
  | 	xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://localhost/service/"
  | 	xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
  | 
  | 	<types>
  | 		<schema xmlns="http://www.w3.org/2001/XMLSchema"
  | 			targetNamespace="http://localhost/service/">
  | 			<element name="OperationRequest">
  | 				<complexType>
  | 					<sequence>
  | 						<element name="request" type="string"></element>
  | 					</sequence>
  | 				</complexType>
  | 			</element>
  | 			<element name="OperationResponse">
  | 				<complexType>
  | 					<sequence>
  | 						<element name="response" type="string"></element>
  | 					</sequence>
  | 				</complexType>
  | 			</element>
  | 			<element name="SoapHeader">
  | 				<complexType>
  | 					<sequence>
  | 						<element name="transactionID" type="string" />
  | 					</sequence>
  | 				</complexType>
  | 			</element>
  | 		</schema>
  | 	</types>
  | 
  | 	<message name="OperationRequest">
  | 		<part name="parameters" element="tns:OperationRequest"></part>
  | 	</message>
  | 	<message name="OperationResponse">
  | 		<part name="parameters" element="tns:OperationResponse"></part>
  | 	</message>
  | 	<message name="SoapHeader">
  | 		<part name="SoapHeader" type="tns:SoapHeader" />
  | 	</message>
  | 
  | 	<portType name="ServicePort">
  | 		<operation name="Operation">
  | 			<input name="operationRequest" message="tns:OperationRequest" />
  | 			<output name="operationResponse" message="tns:OperationResponse" />
  | 		</operation>
  | 	</portType>
  | 
  | 	<binding name="Binding" type="tns:ServicePort">
  | 		<soap:binding style="document"
  | 			transport="http://schemas.xmlsoap.org/soap/http" />
  | 		<operation name="Operation">
  | 			<soap:operation soapAction="http://localhost/service/Operation" />
  | 			<input name="operationRequest">
  | 				<soap:body use="literal" />
  | 				<soap:header message="tns:SoapHeader" part="SoapHeader"
  | 					use="literal" />
  | 			</input>
  | 			<output name="operationResponse">
  | 				<soap:body use="literal" />
  | 				<soap:header message="tns:SoapHeader" part="SoapHeader"
  | 					use="literal" />
  | 			</output>
  | 		</operation>
  | 	</binding>
  | 
  | 	<service name="Service">
  | 		<port name="Port" binding="tns:Binding">
  | 			<soap:address location="http://localhost/service" />
  | 		</port>
  | 	</service>
  | 
  | </definitions>

Is this a bug? Shall I open a JIRA for JBWS?
Thanks in advance for any advice, and kind regards.

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

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


From do-not-reply at jboss.com  Mon May 18 04:22:17 2009
From: do-not-reply at jboss.com (gandulf.k)
Date: Mon, 18 May 2009 04:22:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Getting ClassCast Exception in case of
	malformed webservice
Message-ID: <7138305.1242634937314.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi, i'm using jbowss ws native with validation turned on to ensure the requests and responses are valid. In case of a xml-valid document the validation is working fine and I'm getting validation errors from the validator. But if i'm sending back a totally corrupt xml message, missing closing tags, etc. then i'm getting the following exception which is not very intuitive:


  | Caused by: javax.xml.ws.WebServiceException: java.lang.ClassCastException: org.jboss.ws.core.soap.TextImpl cannot be cast to org.jboss.ws.core.soap.SOAPElementI
  | mpl
  |         at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404)
  |         at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314)
  |         at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
  |         at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
  |         at $Proxy311.bookOrders(Unknown Source)
  |         at com.skidata.dta.server.co.v3_0.classic.impl.BookOrdersHelper.invoke(BookOrdersHelper.java:46)
  |         ... 12 more
  | Caused by: java.lang.ClassCastException: org.jboss.ws.core.soap.TextImpl cannot be cast to org.jboss.ws.core.soap.SOAPElementImpl
  |         at org.jboss.ws.core.CommonSOAPBinding.getParameterFromMessage(CommonSOAPBinding.java:894)
  |         at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:634)
  |         at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:380)
  |         at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
  |         ... 16 more
  | 

I digged into the code a little bit and found out that the actual XML parser exception which i'd like to get is ignored because the SOAPMessageUnMarshallerHTTP is creating a MessageFactory with ignoreParseErrors = true. (line 82 in 3.1.1 source)

  |    MimeHeaders mimeHeaders = getMimeHeaders(metadata);
  |             soapMsg = getMessageFactory().createMessage(mimeHeaders, inputStream, true);
  | 
Which catches the Parse Excpetion and simply returns null in case of a parse error. 

Is there another way than changing the source code to change this behaviour, because i'd like to use the original distribution and not apatched one which will be a mess to update later...

thanks gandulf


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

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


From do-not-reply at jboss.com  Mon May 18 04:52:40 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 18 May 2009 04:52:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Implementing WS-Security Usename
	Token Profile Authentic
Message-ID: <11645854.1242636760853.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

The Username Token Profile is about setting username/pwd through SOAP Headers. Specify the property auth type to prevent the username from being used in the HTTP header:
((BindingProvider)port).getRequestContext().put(StubExt.PROPERTY_AUTH_TYPE, StubExt.PROPERTY_AUTH_TYPE_WSSE);

SAML tokens not supported yet.

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

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


From do-not-reply at jboss.com  Mon May 18 04:57:37 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 18 May 2009 04:57:37 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Recomended way to build server and
	client with maven?
Message-ID: <17991480.1242637057885.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

wsconsume is currently called in the jbossws-framework build to generate classes for a couple of tests. Take a look at the sources.
Besides that, I've filled this: https://jira.jboss.org/jira/browse/JBWS-2650

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

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


From do-not-reply at jboss.com  Mon May 18 05:00:53 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 18 May 2009 05:00:53 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: secure hello world exemple
Message-ID: <28904183.1242637253827.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Take a look at the src distribution; there're both tests using ws-security and basic http auth.

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

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


From do-not-reply at jboss.com  Mon May 18 05:02:04 2009
From: do-not-reply at jboss.com (lixun)
Date: Mon, 18 May 2009 05:02:04 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Help! Call Web service error!
Message-ID: <26534054.1242637324798.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

My First Windows is XP , and the later is Server 2003, is that the root cause?

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

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


From do-not-reply at jboss.com  Mon May 18 05:14:54 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 18 May 2009 05:14:54 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: MTOM enabled WS using SSB throws
	OOME
Message-ID: <20245061.1242638094927.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Please fill in a JIRA for this. Also trying with jbossws-cxf would be interesting.
Afaik the MTOM spec is about optmizing what goes to the wire, but generally speaking I agree on what you say regarding the way attachment are handled by the stack.

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

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


From do-not-reply at jboss.com  Mon May 18 05:17:23 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 18 May 2009 05:17:23 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Global client handler chain
Message-ID: <2454689.1242638244009.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Take a look at the JAX-WS spec regarding programmatically setting handlers on client side.
Besides that, there's standand-jaxws-client-config-xml that can be used (as well as any custom configuration file similar to that) to configure handlers on client side.

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

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


From do-not-reply at jboss.com  Mon May 18 05:26:04 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 18 May 2009 05:26:04 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-Security EJB / Spring WS
Message-ID: <18317378.1242638764621.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Evaluate using JBossWS-CXF or JBossWS-Metro which support WS-SecurityPolicy. That's currently the standard way of configuring and using WS-Security.

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

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


From do-not-reply at jboss.com  Mon May 18 05:35:22 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 18 May 2009 05:35:22 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: dynamic proxy client fails
Message-ID: <29988388.1242639322502.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

The need for setting the endorsed dir is already mentione din the doc, perhaps we should clarify this better when talking about client side, thanks.

Btw the Sun's exception should generally a pointer to the fact the Sun's jaxws impl is being used instead of the native one.

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

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


From do-not-reply at jboss.com  Mon May 18 05:40:58 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 18 May 2009 05:40:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: [ERROR] Invalid header
Message-ID: <13430645.1242639658197.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Please try directly using the Sun's tools. The exception you get comes from the Sun's impl (the jbossws-native jaxws tooling is basically wrapper of the Sun's one). If you still get the exception, please fill it directly to Sun. Othere wise post here again and create the jira on the JBWS project JIRA. Thanks.

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

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


From do-not-reply at jboss.com  Mon May 18 05:44:06 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 18 May 2009 05:44:06 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Getting ClassCast Exception in case
	of malformed webserv
Message-ID: <4251036.1242639846742.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

The validation you turn on is a schema validation. Catching exception regarding bad xml is something different. This said, please fill in a jira about this, we might evaluate removing the ignoreParseErrors=true flag.

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

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


From do-not-reply at jboss.com  Mon May 18 06:03:56 2009
From: do-not-reply at jboss.com (gandulf.k)
Date: Mon, 18 May 2009 06:03:56 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Getting ClassCast Exception in case
	of malformed webserv
Message-ID: <29696330.1242641036423.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

ok i reported an issue for it:

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

thanks gandulf[/url]

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

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


From do-not-reply at jboss.com  Mon May 18 08:55:42 2009
From: do-not-reply at jboss.com (meet_ravip)
Date: Mon, 18 May 2009 08:55:42 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JAXWS WSConsume Custom Defined
	Package Code Generation I
Message-ID: <27503235.1242651342516.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hellllllllllllo,
  Can some one reply back,I ammmmmmmm stuck with this issue

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

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


From do-not-reply at jboss.com  Mon May 18 11:01:55 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 18 May 2009 11:01:55 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Help! Call Web service error!
Message-ID: <16898416.1242658915508.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

You have he perfect setup to track down the issue.  Add -verbose:gc to both run.bat files and then compare the results, you should find that on XP some of the classes are being loaded from somewhere different that where they are being loaded on Server 2003.

I assume you are using the exact same version of the JDK on both platforms.

And here is an interesting thing to try: install the latest patch level for your JDK on XP and see if that works. When I ran into a similar issue several years ago, though in a build environment instead of a run environment, it turned out that some other group was being lazy and copied a JAR file int the JDK's endorsed directory. The build guy could never figure out why the problem always got fixed when he installed a new JDK.

I run on XP and Server 2003 without any issues.

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

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


From do-not-reply at jboss.com  Mon May 18 21:30:47 2009
From: do-not-reply at jboss.com (smartz)
Date: Mon, 18 May 2009 21:30:47 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: [ERROR] Invalid header
Message-ID: <23330711.1242696647345.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

"alessio.soldano at jboss.com" wrote : Please try directly using the Sun's tools. The exception you get comes from the Sun's impl (the jbossws-native jaxws tooling is basically wrapper of the Sun's one). If you still get the exception, please fill it directly to Sun. Othere wise post here again and create the jira on the JBWS project JIRA. Thanks.

Ciao Alessio,

and thanks for your response.
I have followed your suggestion, and tried using wsimport both from JDK6's JAX-WS RI 2.1.1 and from the latest RI 2.1.7, and both have the issue.

For future reference, I have opened a discussion on Sun's forums:
http://forums.sun.com/thread.jspa?threadID=5387214
http://forums.java.net/jive/message.jspa?messageID=346709

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

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


From do-not-reply at jboss.com  Mon May 18 22:04:12 2009
From: do-not-reply at jboss.com (lixun)
Date: Mon, 18 May 2009 22:04:12 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Help! Call Web service error!
Message-ID: <20951226.1242698652690.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Thank you, Peter!

I fixed this issue???when I stop my kaspersky!

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

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



From do-not-reply at jboss.com  Tue May 19 02:50:17 2009
From: do-not-reply at jboss.com (smartz)
Date: Tue, 19 May 2009 02:50:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: [ERROR] Invalid header
Message-ID: <1149231.1242715817643.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

https://jax-ws.dev.java.net/issues/show_bug.cgi?id=692

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

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


From do-not-reply at jboss.com  Tue May 19 08:00:59 2009
From: do-not-reply at jboss.com (sedavhikh)
Date: Tue, 19 May 2009 08:00:59 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - jbossws-3.x.x with jboss-4.0.5
Message-ID: <168597.1242734459466.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi!

Is it possible to install jbossws-3.x.x on jboss-4.0.5GA.
If yes, how can I do it?

Thanks!

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

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


From do-not-reply at jboss.com  Tue May 19 08:22:33 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Tue, 19 May 2009 08:22:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: jbossws-3.x.x with jboss-4.0.5
Message-ID: <20292217.1242735753029.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

No, see Supported Target Containers Matrix

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

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


From do-not-reply at jboss.com  Tue May 19 10:55:57 2009
From: do-not-reply at jboss.com (sedavhikh)
Date: Tue, 19 May 2009 10:55:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: jbossws-3.x.x with jboss-4.0.5
Message-ID: <28165406.1242744957528.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Thak you!

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

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


From do-not-reply at jboss.com  Tue May 19 11:23:10 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 19 May 2009 11:23:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Help! Call Web service error!
Message-ID: <32700580.1242746591011.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Ah, once again someone gets bit by a firewall/virus scanner.

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

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


From do-not-reply at jboss.com  Tue May 19 16:37:36 2009
From: do-not-reply at jboss.com (charitykey)
Date: Tue, 19 May 2009 16:37:36 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Client call fails using JBossWS
Message-ID: <20184730.1242765456303.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Did you ever get this resolved, tomstrummer?  I'm having the same issue and can't seem to get it corrected.

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

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


From do-not-reply at jboss.com  Thu May 21 06:13:38 2009
From: do-not-reply at jboss.com (Sintetik7)
Date: Thu, 21 May 2009 06:13:38 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Memory leak with Provider<Source>
	webservice implementation
Message-ID: <33061278.1242900818708.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi,

I have a problem running my app that implements webservice using Provider api. After ~4hrs of mild load AS goes out of memory.

I'm using JBoss 5.0.1 with sun jdk 1.6.0_14. Configuration is
-Xms256m -Xmx1024m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -XX:+UseConcMarkSweepGC -Dsun.rmi.dgc.client.gcInterval=1800000 -Dsun.rmi.dgc.server.gcInterval=1800000

My endpoints defined as follows:


  | @WebServiceProvider(serviceName = "StorageService", portName = "External", wsdlLocation = "WEB-INF/wsdl/storage.wsdl")
  | @BindingType(value = HTTPBinding.HTTP_BINDING)
  | @ServiceMode(value = Service.Mode.PAYLOAD)
  | public class StorageServiceExternalProvider extends AbstractServiceProvider implements Provider<Source> {
  | 	
  | 	@Resource(type = Object.class)
  | 	protected WebServiceContext wsContext;
  | 
  | 	public Source invoke(Source req) {
  | 		MessageContext mc = wsContext.getMessageContext();
  | 		String path = ((String) mc.get(MessageContext.PATH_INFO)).substring(1);
  | 		return invoke(path, req);
  | 	}
  | 
  | 	protected String getJndiNameSLSB() {
  | 		return "StorageExternalSarco/local";
  | 	}
  | }
  | 
  | 


  | public abstract class AbstractServiceProvider {
  | private static Logger log = Logger.getLogger(AbstractServiceProvider.class);
  | 	
  | 	protected abstract String getJndiNameSLSB();
  | 	
  | 	public Source invoke(String path, Source req) {
  | 		
  | 		JAXBContext jc = null;
  | 		Object local;
  | 		Method[] localMethods;
  | 		
  | 		try {
  | 			InitialContext ic = new InitialContext();
  | 			local = ic.lookup(getJndiNameSLSB());
  | 			ic.close();
  | 			localMethods = local.getClass().getMethods();
  | 
  | 			jc = StorageJAXBContext.getContext();
  | 
  | 		} catch (Throwable t) {
  | 			log.error("Unable to initialize", t);
  | 			return new DOMSource();
  | 		}
  | 		
  | 		Reader decoded;
  | 		Object in = null;
  | 		try {
  | 
  | 			decoded = new StringReader(URLDecoder.decode(req.toString(), "utf8"));
  | 			in = jc.createUnmarshaller().unmarshal(decoded);
  | 			
  | 			if (in instanceof JAXBElement<?>)
  | 				in = ((JAXBElement<?>)in).getValue();
  | 			
  | 			for (Method m : localMethods)
  | 				if (m.getName().equals(path))
  | 				{
  | 					Object result = m.invoke(local, in);
  | 					Class<?> retType = m.getReturnType();
  | 					if (retType == Void.TYPE)
  | 						return new DOMSource();
  | 					else
  | 						return new JAXBSource(jc, result);
  | 				}
  | 
  | 			throw new Exception("Accessing invalid path: " + path);
  | 
  | 		} catch (Throwable e) {
  | 			log.error("Error processing invocation for path: " + path + ", input type is: " + (in == null ? "NULL" : in.getClass()), e);
  | 			return new DOMSource();
  | 		}		
  | 	}
  | 

web.xml:

  <servlet>
  |     <servlet-name>StorageServiceExternalProvider</servlet-name>
  |     <servlet-class>com.photoholding.storage.StorageServiceExternalProvider</servlet-class>
  |   </servlet>
  |   <servlet-mapping>
  |     <servlet-name>StorageServiceExternalProvider</servlet-name>
  |     <url-pattern>/External/*</url-pattern>
  |   </servlet-mapping>


I tried to do jmap profiling and it shows lots of B[ and C[ objects growing with time. Looks like "Provider" instance is never released and GC skips it - size of the OldGen grows until GC can't handle it.

Any help is appreciated.


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

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


From do-not-reply at jboss.com  Thu May 21 16:46:06 2009
From: do-not-reply at jboss.com (lafr)
Date: Thu, 21 May 2009 16:46:06 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Getting IAE using JBossWS to access MS
	Dynamics AX
Message-ID: <18626605.1242938766807.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Server: JBoss-4.2.4GA with jbossws-3.0.1-native-2.0.4.GA.
I used wsconsume to generate the client artefacts from an MS Dynamics Axapta 2009 instance.
When trying to use one of them I get
Caused by: java.lang.IllegalArgumentException: Illegal null argument:ns
  |     at org.jboss.ws.metadata.wsdl.xmlschema.JBossXSModel.createNamespaceItemIfNotExistent(JBossXSModel.java:511)
  |     at org.jboss.ws.metadata.wsdl.xmlschema.JBossXSModel.addXSElementDeclaration(JBossXSModel.java:351)
  |     at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.copyXSModel(WSSchemaUtils.java:707)
  |     at org.jboss.ws.tools.JavaToXSD.parseSchema(JavaToXSD.java:202)
  |     at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:401)
  |     at org.jboss.ws.tools.wsdl.WSDL11Reader.processDefinition(WSDL11Reader.java:178)
  |     at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:128)
  |     at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:295)
  |     at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.buildMetaData(JAXWSClientMetaDataBuilder.java:86)
  |     at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.<init>(ServiceDelegateImpl.java:140)
  |     at org.jboss.ws.core.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:64)
  |     at javax.xml.ws.Service.<init>(Service.java:81)
  |     at com.microsoft.schemas.dynamics._2008._01.services.GeneralJournalService_Service.<init>(GeneralJournalService_Service.java:40)    at biz.mbisoftware.fn.ejb.session.inventory.GeneralLedgerIfAx2009.sendAggregatedValues(GeneralLedgerIfAx2009.java:36)
  | 
I found https://jira.jboss.org/jira/browse/JBWS-686 which is solved, but studying the wsdl a question came up to my mind.
The wsdl contains an import without namespace. Can this cause the exception?
If yes, what can I do?

First lines of WSDL:

  | <wsdl:definitions name="GeneralJournalService" targetNamespace="http://schemas.microsoft.com/dynamics/2008/01/services">
  | <wsp:Policy wsu:Id="BasicHttpBinding_GeneralJournalService_policy">
  | <wsp:ExactlyOne>
  | <wsp:All>
  | <http:NegotiateAuthentication/>
  | </wsp:All>
  | </wsp:ExactlyOne>
  | </wsp:Policy>
  | <wsdl:types>
  | <xsd:schema targetNamespace="http://schemas.microsoft.com/dynamics/2008/01/services/Imports">
  | <xsd:import schemaLocation="http://ax-srv-01.contoso.com/MicrosoftDynamicsAXAif50/generaljournalservice.svc?xsd=xsd0" namespace="http://schemas.microsoft.com/dynamics/2008/01/services"/>
  | <xsd:import schemaLocation="http://ax-srv-01.contoso.com/MicrosoftDynamicsAXAif50/generaljournalservice.svc?xsd=xsd6" namespace="http://schemas.microsoft.com/dynamics/2008/01/documents/Fault"/>
  | <xsd:import schemaLocation="http://ax-srv-01.contoso.com/MicrosoftDynamicsAXAif50/generaljournalservice.svc?xsd=xsd1" namespace="http://schemas.microsoft.com/2003/10/Serialization/"/>
  | <xsd:import schemaLocation="http://ax-srv-01.contoso.com/MicrosoftDynamicsAXAif50/generaljournalservice.svc?xsd=xsd2" namespace="http://schemas.microsoft.com/dynamics/2008/01/documents/LedgerGeneralJournal"/>
  | <xsd:import schemaLocation="http://ax-srv-01.contoso.com/MicrosoftDynamicsAXAif50/generaljournalservice.svc?xsd=xsd3"/>
  | <xsd:import schemaLocation="http://ax-srv-01.contoso.com/MicrosoftDynamicsAXAif50/generaljournalservice.svc?xsd=xsd4" namespace="http://schemas.microsoft.com/dynamics/2006/02/documents/EntityKeyList"/>
  | <xsd:import schemaLocation="http://ax-srv-01.contoso.com/MicrosoftDynamicsAXAif50/generaljournalservice.svc?xsd=xsd5" namespace="http://schemas.microsoft.com/dynamics/2006/02/documents/EntityKey"/>
  | <xsd:import schemaLocation="http://ax-srv-01.contoso.com/MicrosoftDynamicsAXAif50/generaljournalservice.svc?xsd=xsd7" namespace="http://schemas.microsoft.com/dynamics/2006/02/documents/QueryCriteria"/>
  | </xsd:schema>
  | </wsdl:types>


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

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


From do-not-reply at jboss.com  Thu May 21 17:22:07 2009
From: do-not-reply at jboss.com (leobaz2)
Date: Thu, 21 May 2009 17:22:07 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBossWS client not sending Basic
	Authentication
Message-ID: <15663305.1242940927265.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi, I have a web service client that is trying to call a webservice secured with basic authentication.  I had this working with JAVA 6 but not with JAVA 5.  

I am setting the username and password correctly as seen below but I am still getting a 401 error code back.  When I used tcpmon to inspect the request\response, I can see that the username and password is not being passed to the client.


  | Map requestContext = ((BindingProvider) manager).getRequestContext();
  | requestContext.put(BindingProvider.USERNAME_PROPERTY, username);
  | requestContext.put(BindingProvider.PASSWORD_PROPERTY, password);
  | 

When I debug, I can see that the web service proxy has the username and password in its Map. So why are they not being sent along with the webservice call?  Does it have something to do with the versions of the Jars I am using?  I am using JBoss 4.2.3 and the jars are.


  | jboss\client\xmlsec.jar
  | jboss\client\jboss-jaxws.jar
  | jboss\client\jbossws-client.jar
  | jboss\client\jboss-common-client.jar
  | jboss\lib\endorsed\serializer.jar
  | jboss\lib\endorsed\xalan.jar
  | jboss\lib\endorsed\xercesImpl.jar
  | commons-validator
  | commons-logging-api
  | <my client stubs jar> created using jwsc ant task
  | 

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

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


From do-not-reply at jboss.com  Fri May 22 05:28:41 2009
From: do-not-reply at jboss.com (sbatra23)
Date: Fri, 22 May 2009 05:28:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: java.lang.LinkageError: loader
	constraint violation:(In
Message-ID: <19451014.1242984521510.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Please help me the solution of this isssue. I'm fcaing the same issue.

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

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


From do-not-reply at jboss.com  Fri May 22 08:40:34 2009
From: do-not-reply at jboss.com (GajananM)
Date: Fri, 22 May 2009 08:40:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: java.lang.LinkageError: loader
	constraint violation:(In
Message-ID: <1467334.1242996034637.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

dowload JAXWS patch for JAXWS webservices and run the ant file then u will be able to call the client

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

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


From do-not-reply at jboss.com  Fri May 22 09:15:52 2009
From: do-not-reply at jboss.com (SARA1232007)
Date: Fri, 22 May 2009 09:15:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Eorros of creating WS client stub class
Message-ID: <252190.1242998152396.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi,

I'm using jboss-4.2.2.GA and jbossws-native-3.0.5.GA. I create the WS client using jbossws. But when I run WS client, I get the excpetions when I invoke the creation of WS client stub class. The exceptions are as following:

Exception in thread "main" java.lang.IllegalStateException: Failed to load javax.xml.ws.spi.Provider: com.sun.xml.ws.spi.ProviderImpl
  | 	at javax.xml.ws.spi.ProviderLoader.loadProvider(ProviderLoader.java:94)
  | 	at javax.xml.ws.spi.Provider.provider(Provider.java:80)
  | 	at javax.xml.ws.Service.<init>(Service.java:79)
  | 	at org.openuri._2004._04.helloworld.HelloWorldPOJOService.<init>(HelloWorldPOJOService.java:45)
  | 	at samples.webservice.ClientTester.main(ClientTester.java:8)
  | Caused by: java.lang.ExceptionInInitializerError
  | 	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
  | 	at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
  | 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
  | 	at java.lang.reflect.Constructor.newInstance(Unknown Source)
  | 	at java.lang.Class.newInstance0(Unknown Source)
  | 	at java.lang.Class.newInstance(Unknown Source)
  | 	at javax.xml.ws.spi.ProviderLoader.loadProvider(ProviderLoader.java:89)
  | 	... 4 more
  | Caused by: javax.xml.ws.WebServiceException: Error creating JAXBContext for W3CEndpointReference. 
  | 	at com.sun.xml.ws.spi.ProviderImpl$2.run(ProviderImpl.java:222)
  | 	at com.sun.xml.ws.spi.ProviderImpl$2.run(ProviderImpl.java:218)
  | 	at java.security.AccessController.doPrivileged(Native Method)
  | 	at com.sun.xml.ws.spi.ProviderImpl.getEPRJaxbContext(ProviderImpl.java:217)
  | 	at com.sun.xml.ws.spi.ProviderImpl.<clinit>(ProviderImpl.java:88)
  | 	... 11 more
  | Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 2 counts of IllegalAnnotationExceptions
  | Two classes have the same XML type name "address". Use @XmlType.name and @XmlType.namespace to assign different names to them.
  | 	this problem is related to the following location:
  | 		at com.sun.xml.ws.developer.MemberSubmissionEndpointReference$Address
  | 		at public com.sun.xml.ws.developer.MemberSubmissionEndpointReference$Address com.sun.xml.ws.developer.MemberSubmissionEndpointReference.addr
  | 		at com.sun.xml.ws.developer.MemberSubmissionEndpointReference
  | 	this problem is related to the following location:
  | 		at javax.xml.ws.wsaddressing.W3CEndpointReference$Address
  | 		at private javax.xml.ws.wsaddressing.W3CEndpointReference$Address javax.xml.ws.wsaddressing.W3CEndpointReference.address
  | 		at javax.xml.ws.wsaddressing.W3CEndpointReference
  | Two classes have the same XML type name "elements". Use @XmlType.name and @XmlType.namespace to assign different names to them.
  | 	this problem is related to the following location:
  | 		at com.sun.xml.ws.developer.MemberSubmissionEndpointReference$Elements
  | 		at public com.sun.xml.ws.developer.MemberSubmissionEndpointReference$Elements com.sun.xml.ws.developer.MemberSubmissionEndpointReference.referenceProperties
  | 		at com.sun.xml.ws.developer.MemberSubmissionEndpointReference
  | 	this problem is related to the following location:
  | 		at javax.xml.ws.wsaddressing.W3CEndpointReference$Elements
  | 		at private javax.xml.ws.wsaddressing.W3CEndpointReference$Elements javax.xml.ws.wsaddressing.W3CEndpointReference.referenceParameters
  | 		at javax.xml.ws.wsaddressing.W3CEndpointReference
  | 
  | 	at com.sun.xml.bind.v2.runtime.IllegalAnnotationsException$Builder.check(IllegalAnnotationsException.java:102)
  | 	at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:438)
  | 	at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:286)
  | 	at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
  | 	at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:117)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
  | 	at java.lang.reflect.Method.invoke(Unknown Source)
  | 	at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:211)
  | 	at javax.xml.bind.ContextFinder.find(ContextFinder.java:372)
  | 	at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)
  | 	at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:522)
  | 	at com.sun.xml.ws.spi.ProviderImpl$2.run(ProviderImpl.java:220)
  | 	... 15 more
  | 
  | 
  | 
Can anyone tell me what's wrong?

Thanks.

Sara

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

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


From do-not-reply at jboss.com  Sat May 23 06:04:54 2009
From: do-not-reply at jboss.com (lafr)
Date: Sat, 23 May 2009 06:04:54 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - NotSerializableException:
	org.jboss.ws.core.soap.SOAPFaultIm
Message-ID: <32401034.1243073095043.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I'm using JBoss-4.2.4GA with jbossws-3.0.1-native-2.0.4.GA.

I used wsconsume to generate the client artefacts from an MS Dynamics Axapta 2009 instance.
Calling a Webservice I get this exception:
java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.jboss.ws.core.soap.SOAPFaultImpl
  |     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1333)
  |     at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)
  |     at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
  |     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
  |     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
  |     at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)
  |     at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
  |     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
  |     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
  |     at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)
  |     at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
  |     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
  |     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
  |     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
  |     at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObjectVersion2_2(JavaSerializationManager.java:239)
  |     at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:133)
  |     at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:120)
  |     at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedRead(MicroSocketClientInvoker.java:945)
  |     at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:633)
  |     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.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
  |     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |     at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
  |     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |     at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
  |     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |     at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
  |     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |     at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)
  |     at $Proxy3.sendAggregatedValues(Unknown Source)
  | ...
  | Caused by: java.io.NotSerializableException: org.jboss.ws.core.soap.SOAPFaultImpl
  |     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156)
  |     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
  |     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
  |     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
  |     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
  |     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
  |     at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:416)
  |     at java.lang.Throwable.writeObject(Throwable.java:648)
  |     at sun.reflect.GeneratedMethodAccessor206.invoke(Unknown Source)
  |     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  |     at java.lang.reflect.Method.invoke(Method.java:597)
  |     at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
  |     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461)
  |     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
  |     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
  |     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
  |     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
  |     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
  |     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
  |     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
  |     at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.sendObjectVersion2_2(JavaSerializationManager.java:120)
  |     at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.sendObject(JavaSerializationManager.java:95)
  |     at org.jboss.remoting.marshal.serializable.SerializableMarshaller.write(SerializableMarshaller.java:120)
  |     at org.jboss.remoting.transport.socket.ServerThread.versionedWrite(ServerThread.java:841)
  |     at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:641)
  |     at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:406)
  |     at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173)
  | 
All operations have a Fault message
<wsdl:binding name="BasicHttpBinding_GeneralJournalService" type="tns:GeneralJournalService">
  |         <soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>
  |         <wsdl:operation name="create">
  |             <soap:operation soapAction="http://schemas.microsoft.com/dynamics/2008/01/services/GeneralJournalService/create"
  |                 style="document"/>
  |             <wsdl:input name="GeneralJournalServiceCreateRequest">
  |                 <soap:body use="literal"/>
  |             </wsdl:input>
  |             <wsdl:output name="GeneralJournalServiceCreateResponse">
  |                 <soap:body use="literal"/>
  |             </wsdl:output>
  |             <wsdl:fault name="AifFaultFault">
  |                 <soap:fault name="AifFaultFault" use="literal"/>
  |             </wsdl:fault>
  |         </wsdl:operation>
  |         <wsdl:operation name="find">
  |             <soap:operation soapAction="http://schemas.microsoft.com/dynamics/2008/01/services/GeneralJournalService/find"
  |                 style="document"/>
  |             <wsdl:input name="GeneralJournalServiceFindRequest">
  |                 <soap:body use="literal"/>
  |             </wsdl:input>
  |             <wsdl:output name="GeneralJournalServiceFindResponse">
  |                 <soap:body use="literal"/>
  |             </wsdl:output>
  |             <wsdl:fault name="AifFaultFault">
  |                 <soap:fault name="AifFaultFault" use="literal"/>
  |             </wsdl:fault>
  |         </wsdl:operation>
  |         <wsdl:operation name="read">
  |             <soap:operation soapAction="http://schemas.microsoft.com/dynamics/2008/01/services/GeneralJournalService/read"
  |                 style="document"/>
  |             <wsdl:input name="GeneralJournalServiceReadRequest">
  |                 <soap:body use="literal"/>
  |             </wsdl:input>
  |             <wsdl:output name="GeneralJournalServiceReadResponse">
  |                 <soap:body use="literal"/>
  |             </wsdl:output>
  |             <wsdl:fault name="AifFaultFault">
  |                 <soap:fault name="AifFaultFault" use="literal"/>
  |             </wsdl:fault>
  |         </wsdl:operation>
  |     </wsdl:binding>
  |  which probably is part of the problem.
It's the first time I try to consume a WS defined this way.

What's missing or wrong here?

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

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


From do-not-reply at jboss.com  Tue May 26 17:19:10 2009
From: do-not-reply at jboss.com (worldofnic)
Date: Tue, 26 May 2009 17:19:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Disabling Transfer-Encoding: chunked in
	a client
Message-ID: <27200445.1243372750839.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

All, I'm writing a client that goes via a dodgy web proxy that can't proxy Transfer-Encoding: chunked data.

 I thought from perusing the web that in JBossWS-Native and/or JBossWS-Metro you could disable this behaviour by editing:

/opt/jboss-5.1.0.GA/server/default/deployers/jbossws.deployer/META-INF/standard-jaxws-client-config.xml

and setting http://org.jboss.ws/http#chunksize to 0 in Standard Client.

Is that not right?

Any help from anyone who's done this before would be greatly appreciated.

Cheers,
nic

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

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


From do-not-reply at jboss.com  Wed May 27 09:13:02 2009
From: do-not-reply at jboss.com (Sintetik7)
Date: Wed, 27 May 2009 09:13:02 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Memory leak with Provider<Source>
	webservice implementat
Message-ID: <29881026.1243429986615.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Resolved problem by settings injected wsContext to null

now looks like

	public Source invoke(Source req) {
		MessageContext mc = wsContext.getMessageContext();
		String path = ((String) mc.get(MessageContext.PATH_INFO)).substring(1);
                wsContext = null;
		return invoke(path, req);
	}

I'm not sure if this kind of modification should be needed. Should I report a bug?


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

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


From do-not-reply at jboss.com  Wed May 27 09:17:35 2009
From: do-not-reply at jboss.com (Sintetik7)
Date: Wed, 27 May 2009 09:17:35 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS 3.0.3 memory leak
Message-ID: <25902347.1243430255206.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

"richard.opalka at jboss.com" wrote : And AS 5.0.1 GA + JBossWS 3.1.0?

I had similar problems wtih AS 5.0.1 GA (see http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233605). Found some kinda solution but not sure if good one.



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

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


From do-not-reply at jboss.com  Wed May 27 13:04:24 2009
From: do-not-reply at jboss.com (ivan.indrawan)
Date: Wed, 27 May 2009 13:04:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: NotSerializableException:
	org.jboss.ws.core.soap.SOAPFau
Message-ID: <6096134.1243443864380.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Do you mean the SOAPFault is generated on the server side? The fault cant be generated on the client side.

If you are controlling the server side code, make sure that the member properties of the exception that you are throwing (wrapped by the SOAPFaultException) are all serializable. 

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

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


From do-not-reply at jboss.com  Wed May 27 15:52:09 2009
From: do-not-reply at jboss.com (lafr)
Date: Wed, 27 May 2009 15:52:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: NotSerializableException:
	org.jboss.ws.core.soap.SOAPFau
Message-ID: <4372010.1243453929922.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

A Fault occurs on the server side while executing the webservice request from my client.
The server side code is not under my control, its under the control of Microsoft.
They give back a soap message containing a fault like it is defined in the wsdl contract.
Example:
2009-05-27 21:40:22,329 TRACE [org.jboss.ws.core.MessageTrace#traceMessage] Incoming Response Message
  | <s:Envelope xmlns:s='http://schemas.xmlsoap.org/soap/envelope/'>
  |  <s:Body>
  |   <s:Fault xmlns:s='http://schemas.xmlsoap.org/soap/envelope/'>
  |    <faultcode>s:Client</faultcode>
  |    <faultstring xml:lang='en-US'>Request Failed. See the Exception Log for details.</faultstring>
  |    <detail>
  |     <AifFault xmlns='http://schemas.microsoft.com/dynamics/2008/01/documents/Fault' xmlns:i='http://www.w3.org/2001/XMLSchema-instance'>
  |      <CustomDetailXml i:nil='true'/>
  |      <FaultMessageListArray i:nil='true'/>
  |     </AifFault>
  |    </detail>
  |   </s:Fault>
  |  </s:Body>
  | </s:Envelope>
  | 

JBossWS was not able to read or unmarshal such a message into the corresponding objects.
I downloaded the the code and added "implements Serializable" to SOAPFaultImpl and a few others and now the communication between JBossWS-Client and the MS software based on WCF (Windows Communication Foundation) on the server side.

I wonder that nobody had the problem before and that the released versions of JBossWS are not capable of reading answers like the one above.


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

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


From do-not-reply at jboss.com  Wed May 27 18:06:24 2009
From: do-not-reply at jboss.com (RichardTaylor)
Date: Wed, 27 May 2009 18:06:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBossWS Metro 3.1.1 on AS 5.1.0 Startup
	errors?
Message-ID: <30747740.1243461984157.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I'm getting errors after installing the latest JBossWS Metro (3.1.1.GA) into JBoss 5.1.0.GA-jdk6.  Are there any know issues that I should be aware of?  Has anyone else had any luck with this combination?  I've read all the readmes that I'm aware of and looked for jira issues.  

1. Clean copy of JBoss 5.1.0.GA-jdk6, both the "default" and "all" servers start and run without error.
2. Downloaded the latest JBossWS Metro Binaries (3.1.1.GA) from http://www.jboss.org/jbossws/downloads/
3. Went through the installation instructions here http://jbossws.jboss.org/mediawiki/index.php?title=Installation
4. Now I get the following upon startup.   
=========================================================================
  | 
  |   JBoss Bootstrap Environment
  | 
  |   JBOSS_HOME: /Applications/jboss-5.1.0.GA-metro
  | 
  |   JAVA: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home//bin/java
  | 
  |   JAVA_OPTS: -Dprogram.name=run.sh -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
  | 
  |   CLASSPATH: /Applications/jboss-5.1.0.GA-metro/bin/run.jar
  | 
  | =========================================================================
  | 
  | 14:58:10,666 INFO  [ServerImpl] Starting JBoss (Microcontainer)...
  | 14:58:10,667 INFO  [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)
  | 14:58:10,667 INFO  [ServerImpl] Bootstrap URL: null
  | 14:58:10,667 INFO  [ServerImpl] Home Dir: /Applications/jboss-5.1.0.GA-metro
  | 14:58:10,667 INFO  [ServerImpl] Home URL: file:/Applications/jboss-5.1.0.GA-metro/
  | 14:58:10,668 INFO  [ServerImpl] Library URL: file:/Applications/jboss-5.1.0.GA-metro/lib/
  | 14:58:10,668 INFO  [ServerImpl] Patch URL: null
  | 14:58:10,668 INFO  [ServerImpl] Common Base URL: file:/Applications/jboss-5.1.0.GA-metro/common/
  | 14:58:10,669 INFO  [ServerImpl] Common Library URL: file:/Applications/jboss-5.1.0.GA-metro/common/lib/
  | 14:58:10,669 INFO  [ServerImpl] Server Name: default
  | 14:58:10,669 INFO  [ServerImpl] Server Base Dir: /Applications/jboss-5.1.0.GA-metro/server
  | 14:58:10,669 INFO  [ServerImpl] Server Base URL: file:/Applications/jboss-5.1.0.GA-metro/server/
  | 14:58:10,669 INFO  [ServerImpl] Server Config URL: file:/Applications/jboss-5.1.0.GA-metro/server/default/conf/
  | 14:58:10,669 INFO  [ServerImpl] Server Home Dir: /Applications/jboss-5.1.0.GA-metro/server/default
  | 14:58:10,670 INFO  [ServerImpl] Server Home URL: file:/Applications/jboss-5.1.0.GA-metro/server/default/
  | 14:58:10,670 INFO  [ServerImpl] Server Data Dir: /Applications/jboss-5.1.0.GA-metro/server/default/data
  | 14:58:10,670 INFO  [ServerImpl] Server Library URL: file:/Applications/jboss-5.1.0.GA-metro/server/default/lib/
  | 14:58:10,670 INFO  [ServerImpl] Server Log Dir: /Applications/jboss-5.1.0.GA-metro/server/default/log
  | 14:58:10,670 INFO  [ServerImpl] Server Native Dir: /Applications/jboss-5.1.0.GA-metro/server/default/tmp/native
  | 14:58:10,671 INFO  [ServerImpl] Server Temp Dir: /Applications/jboss-5.1.0.GA-metro/server/default/tmp
  | 14:58:10,671 INFO  [ServerImpl] Server Temp Deploy Dir: /Applications/jboss-5.1.0.GA-metro/server/default/tmp/deploy
  | 14:58:11,342 INFO  [ServerImpl] Starting Microcontainer, bootstrapURL=file:/Applications/jboss-5.1.0.GA-metro/server/default/conf/bootstrap.xml
  | 14:58:11,872 INFO  [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache]
  | 14:58:11,875 INFO  [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]
  | 14:58:12,138 INFO  [CopyMechanism] VFS temp dir: /Applications/jboss-5.1.0.GA-metro/server/default/tmp
  | 14:58:12,139 INFO  [ZipEntryContext] VFS force nested jars copy-mode is enabled.
  | 14:58:13,404 INFO  [ServerInfo] Java version: 1.6.0_07,Apple Inc.
  | 14:58:13,405 INFO  [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_07-b06-153)
  | 14:58:13,405 INFO  [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM 1.6.0_07-b06-57,Apple Inc.
  | 14:58:13,405 INFO  [ServerInfo] OS-System: Mac OS X 10.5.7,x86_64
  | 14:58:13,407 INFO  [ServerInfo] VM arguments: -Dprogram.name=run.sh -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.endorsed.dirs=/Applications/jboss-5.1.0.GA-metro/lib/endorsed 
  | 14:58:13,472 INFO  [JMXKernel] Legacy JMX core initialized
  | 14:58:16,533 INFO  [ProfileServiceBootstrap] Loading profile: ProfileKey at e2a3881[domain=default, server=default, name=default]
  | 14:58:18,097 INFO  [WebService] Using RMI server codebase: http://mycompany.com:8083/
  | 14:58:28,579 INFO  [MetroServerConfig] JBoss Web Services - Stack Metro Runtime Server
  | 14:58:28,579 INFO  [MetroServerConfig] 3.1.1.GA
  | 14:58:28,836 ERROR [AbstractKernelController] Error installing to PreInstall: name=WSInjectionMetaDataDeploymentAspect state=Real
  | java.lang.NoClassDefFoundError: org/jboss/wsf/spi/metadata/injection/ReferenceResolver
  | 	at java.lang.Class.getDeclaredConstructors0(Native Method)
  | 	at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
  | 	at java.lang.Class.getDeclaredConstructors(Class.java:1836)
  | 	at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl.getDeclaredConstructors(IntrospectionTypeInfoFactoryImpl.java:489)
  | 	at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl.getConstructors(IntrospectionTypeInfoFactoryImpl.java:146)
  | 	at org.jboss.reflect.plugins.ClassInfoImpl.getDeclaredConstructors(ClassInfoImpl.java:424)
  | 	at org.jboss.beans.info.plugins.AbstractBeanInfoFactory.getConstructors(AbstractBeanInfoFactory.java:206)
  | 	at org.jboss.beans.info.plugins.AbstractBeanInfoFactory.getBeanInfo(AbstractBeanInfoFactory.java:151)
  | 	at org.jboss.config.plugins.AbstractConfiguration.getBeanInfo(AbstractConfiguration.java:87)
  | 	at org.jboss.kernel.plugins.config.AbstractKernelConfig.getBeanInfo(AbstractKernelConfig.java:80)
  | 	at org.jboss.kernel.plugins.config.AbstractKernelConfigurator.getBeanInfo(AbstractKernelConfigurator.java:77)
  | 	at org.jboss.kernel.plugins.config.AbstractKernelConfigurator.getBeanInfo(AbstractKernelConfigurator.java:96)
  | 	at org.jboss.kernel.plugins.dependency.PreInstallAction.installActionInternal(PreInstallAction.java:90)
  | 	at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)
  | 	at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)
  | 	at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
  | 	at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
  | 	at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
  | 	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
  | 	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
  | 	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
  | 	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
  | 	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
  | 	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:774)
  | 	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)
  | 	at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:121)
  | 	at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:51)
  | 	at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
  | 	at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
  | 	at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
  | 	at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
  | 	at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
  | 	at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
  | 	at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
  | 	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
  | 	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
  | 	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
  | 	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
  | 	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
  | 	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
  | 	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
  | 	at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
  | 	at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
  | 	at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
  | 	at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
  | 	at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
  | 	at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
  | 	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
  | 	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
  | 	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
  | 	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
  | 	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
  | 	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
  | 	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
  | 	at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
  | 	at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
  | 	at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
  | 	at org.jboss.Main.boot(Main.java:221)
  | 	at org.jboss.Main$1.run(Main.java:556)
  | 	at java.lang.Thread.run(Thread.java:637)
  | Caused by: java.lang.ClassNotFoundException: org.jboss.wsf.spi.metadata.injection.ReferenceResolver
  | 	at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
  | 	at java.security.AccessController.doPrivileged(Native Method)
  | 	at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
  | 	at java.lang.ClassLoader.loadClass(ClassLoader.java:316)
  | 	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:288)
  | 	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
  | 	at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:374)
  | 	at java.lang.Class.forName0(Native Method)
  | 	at java.lang.Class.forName(Class.java:247)
  | 	at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:292)
  | 	at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1119)
  | 	at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:798)
  | 	at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:441)
  | 	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
  | 	at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:374)
  | 	... 60 more
  | 14:58:29,471 ERROR [DeploymentAspectInstaller] Cannot add deployment aspect(s)
  | WSDeploymentAspectManagerPreJSE provides: []
  | WSDeploymentAspectManagerPostJSE provides: []
  |    org.jboss.wsf.container.jboss50.deployment.RuntimeLoaderDeploymentAspect, requires: ContainerMetaData
  |    org.jboss.wsf.framework.deployment.EndpointRecordProcessorDeploymentAspect, requires: RegisteredEndpoint
  |    org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect, requires: RuntimeLoader, StackDescriptor
  |    org.jboss.wsf.framework.deployment.EndpointHandlerDeploymentAspect, requires: ContainerEndpointHandler
  | 14:58:29,473 ERROR [AbstractKernelController] Error installing to Create: name=WSMetroDeploymentAspectInstallerPostJSE state=Configured
  | java.lang.IllegalStateException: Cannot add deployment aspect(s)
  | WSDeploymentAspectManagerPreJSE provides: []
  | WSDeploymentAspectManagerPostJSE provides: []
  |    org.jboss.wsf.container.jboss50.deployment.RuntimeLoaderDeploymentAspect, requires: ContainerMetaData
  |    org.jboss.wsf.framework.deployment.EndpointRecordProcessorDeploymentAspect, requires: RegisteredEndpoint
  |    org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect, requires: RuntimeLoader, StackDescriptor
  |    org.jboss.wsf.framework.deployment.EndpointHandlerDeploymentAspect, requires: ContainerEndpointHandler
  | 	at org.jboss.wsf.framework.deployment.DeploymentAspectInstaller.throwSortException(DeploymentAspectInstaller.java:170)
  | 	at org.jboss.wsf.framework.deployment.DeploymentAspectInstaller.create(DeploymentAspectInstaller.java:129)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:597)
  | 	at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
  | 	at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
  | 	at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
  | 	at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:241)
  | 	at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)
  | 	at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:109)
  | 	at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:70)
  | 	at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221)
  | 	at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)
  | 	at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)
  | 	at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
  | 	at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
  | 	at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
  | 	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
  | 	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
  | 	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
  | 	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
  | 	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
  | 	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:774)
  | 	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)
  | 	at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:121)
  | 	at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:51)
  | 	at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
  | 	at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
  | 	at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
  | 	at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
  | 	at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
  | 	at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
  | 	at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
  | 	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
  | 	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
  | 	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
  | 	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
  | 	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
  | 	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
  | 	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
  | 	at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
  | 	at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
  | 	at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
  | 	at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
  | 	at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
  | 	at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
  | 	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
  | 	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
  | 	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
  | 	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
  | 	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
  | 	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
  | 	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
  | 	at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
  | 	at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
  | 	at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
  | 	at org.jboss.Main.boot(Main.java:221)
  | 	at org.jboss.Main$1.run(Main.java:556)
  | 	at java.lang.Thread.run(Thread.java:637)
  | 14:58:29,982 INFO  [AttributeCallbackItem] Owner callback not implemented.
  | 14:58:30,953 INFO  [LogNotificationListener] Adding notification listener for logging mbean "jboss.system:service=Logging,type=Log4jService" to server org.jboss.mx.server.MBeanServerImpl at 584ca76[ defaultDomain='jboss' ]
  | 14:58:41,879 INFO  [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext at 20257662{vfsfile:/Applications/jboss-5.1.0.GA-metro/server/default/deploy/profileservice-secured.jar/}
  | 14:58:41,880 INFO  [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext at 20257662{vfsfile:/Applications/jboss-5.1.0.GA-metro/server/default/deploy/profileservice-secured.jar/}
  | 14:58:41,880 INFO  [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext at 20257662{vfsfile:/Applications/jboss-5.1.0.GA-metro/server/default/deploy/profileservice-secured.jar/}
  | 14:58:41,881 INFO  [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext at 20257662{vfsfile:/Applications/jboss-5.1.0.GA-metro/server/default/deploy/profileservice-secured.jar/}
  | 14:58:43,493 INFO  [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://rtaylor.companysystems.com/jndi/rmi://rtaylor.companysystems.com:1090/jmxconnector
  | 14:58:43,727 INFO  [MailService] Mail Service bound to java:/Mail
  | 14:58:46,231 WARN  [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
  | 14:58:46,247 WARN  [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
  | 14:58:46,321 WARN  [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
  | 14:58:46,378 INFO  [TransactionManagerService] JBossTS Transaction Service (JTA version - tag:JBOSSTS_4_6_1_GA) - JBoss Inc.
  | 14:58:46,379 INFO  [TransactionManagerService] Setting up property manager MBean and JMX layer
  | 14:58:46,659 INFO  [TransactionManagerService] Initializing recovery manager
  | 14:58:46,800 INFO  [TransactionManagerService] Recovery manager configured
  | 14:58:46,804 INFO  [TransactionManagerService] Binding TransactionManager JNDI Reference
  | 14:58:46,830 INFO  [TransactionManagerService] Starting transaction recovery manager
  | 14:58:48,072 INFO  [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: .:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java
  | 14:58:48,128 INFO  [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
  | 14:58:48,129 INFO  [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-0.0.0.0-8009
  | 14:58:48,157 INFO  [StandardService] Starting service jboss.web
  | 14:58:48,159 INFO  [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.3.GA
  | 14:58:48,222 INFO  [Catalina] Server startup in 91 ms
  | 14:58:48,252 INFO  [TomcatDeployment] deploy, ctxPath=/jbossws
  | 14:58:48,763 INFO  [TomcatDeployment] deploy, ctxPath=/juddi
  | 14:58:48,796 INFO  [RegistryServlet] Loading jUDDI configuration.
  | 14:58:48,796 INFO  [RegistryServlet] Resources loaded from: /WEB-INF/juddi.properties
  | 14:58:48,796 INFO  [RegistryServlet] Initializing jUDDI components.
  | 14:58:48,941 INFO  [TomcatDeployment] deploy, ctxPath=/web-console
  | 14:58:49,244 INFO  [TomcatDeployment] deploy, ctxPath=/invoker
  | 14:58:49,354 INFO  [RARDeployment] Required license terms exist, view vfszip:/Applications/jboss-5.1.0.GA-metro/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
  | 14:58:49,370 INFO  [RARDeployment] Required license terms exist, view vfszip:/Applications/jboss-5.1.0.GA-metro/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
  | 14:58:49,394 INFO  [RARDeployment] Required license terms exist, view vfszip:/Applications/jboss-5.1.0.GA-metro/server/default/deploy/jms-ra.rar/META-INF/ra.xml
  | 14:58:49,412 INFO  [RARDeployment] Required license terms exist, view vfszip:/Applications/jboss-5.1.0.GA-metro/server/default/deploy/mail-ra.rar/META-INF/ra.xml
  | 14:58:49,432 INFO  [RARDeployment] Required license terms exist, view vfszip:/Applications/jboss-5.1.0.GA-metro/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
  | 14:58:49,500 INFO  [SimpleThreadPool] Job execution threads will use class loader of thread: main
  | 14:58:49,526 INFO  [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
  | 14:58:49,528 INFO  [RAMJobStore] RAMJobStore initialized.
  | 14:58:49,529 INFO  [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
  | 14:58:49,529 INFO  [StdSchedulerFactory] Quartz scheduler version: 1.5.2
  | 14:58:49,529 INFO  [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
  | 14:58:50,727 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
  | 14:58:51,258 INFO  [ServerPeer] JBoss Messaging 1.4.3.GA server [0] started
  | 14:58:51,342 INFO  [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
  | 14:58:51,393 INFO  [ConnectionFactory] Connector bisocket://rtaylor.companysystems.com:4457 has leasing enabled, lease period 10000 milliseconds
  | 14:58:51,393 INFO  [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory at 2bed823c started
  | 14:58:51,395 INFO  [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
  | 14:58:51,395 INFO  [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover
  | 14:58:51,395 INFO  [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing
  | 14:58:51,401 INFO  [ConnectionFactory] Connector bisocket://rtaylor.companysystems.com:4457 has leasing enabled, lease period 10000 milliseconds
  | 14:58:51,401 INFO  [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory at 4d9e5465 started
  | 14:58:51,403 INFO  [ConnectionFactory] Connector bisocket://rtaylor.companysystems.com:4457 has leasing enabled, lease period 10000 milliseconds
  | 14:58:51,403 INFO  [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory at 3e67f896 started
  | 14:58:51,497 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
  | 14:58:53,239 INFO  [JBossASKernel] Created KernelDeployment for: profileservice-secured.jar
  | 14:58:53,244 INFO  [JBossASKernel] installing bean: jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3
  | 14:58:53,245 INFO  [JBossASKernel]   with dependencies:
  | 14:58:53,245 INFO  [JBossASKernel]   and demands:
  | 14:58:53,250 INFO  [JBossASKernel] 	jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView
  | 14:58:53,250 INFO  [JBossASKernel] 	jboss.ejb:service=EJBTimerService
  | 14:58:53,251 INFO  [JBossASKernel]   and supplies:
  | 14:58:53,251 INFO  [JBossASKernel] 	Class:org.jboss.profileservice.spi.ProfileService
  | 14:58:53,251 INFO  [JBossASKernel] 	jndi:SecureProfileService/remote
  | 14:58:53,251 INFO  [JBossASKernel] 	jndi:SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService
  | 14:58:53,252 INFO  [JBossASKernel] Added bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3) to KernelDeployment of: profileservice-secured.jar
  | 14:58:53,253 INFO  [JBossASKernel] installing bean: jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3
  | 14:58:53,253 INFO  [JBossASKernel]   with dependencies:
  | 14:58:53,253 INFO  [JBossASKernel]   and demands:
  | 14:58:53,253 INFO  [JBossASKernel] 	jboss.ejb:service=EJBTimerService
  | 14:58:53,254 INFO  [JBossASKernel]   and supplies:
  | 14:58:53,254 INFO  [JBossASKernel] 	jndi:SecureDeploymentManager/remote-org.jboss.deployers.spi.management.deploy.DeploymentManager
  | 14:58:53,254 INFO  [JBossASKernel] 	Class:org.jboss.deployers.spi.management.deploy.DeploymentManager
  | 14:58:53,254 INFO  [JBossASKernel] 	jndi:SecureDeploymentManager/remote
  | 14:58:53,254 INFO  [JBossASKernel] Added bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3) to KernelDeployment of: profileservice-secured.jar
  | 14:58:53,255 INFO  [JBossASKernel] installing bean: jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3
  | 14:58:53,255 INFO  [JBossASKernel]   with dependencies:
  | 14:58:53,255 INFO  [JBossASKernel]   and demands:
  | 14:58:53,255 INFO  [JBossASKernel] 	jboss.ejb:service=EJBTimerService
  | 14:58:53,256 INFO  [JBossASKernel]   and supplies:
  | 14:58:53,256 INFO  [JBossASKernel] 	jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView
  | 14:58:53,256 INFO  [JBossASKernel] 	Class:org.jboss.deployers.spi.management.ManagementView
  | 14:58:53,256 INFO  [JBossASKernel] 	jndi:SecureManagementView/remote
  | 14:58:53,256 INFO  [JBossASKernel] Added bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3) to KernelDeployment of: profileservice-secured.jar
  | 14:58:53,264 INFO  [EJB3EndpointDeployer] Deploy AbstractBeanMetaData at 4549567c{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true}
  | 14:58:53,264 INFO  [EJB3EndpointDeployer] Deploy AbstractBeanMetaData at 3eb66e52{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true}
  | 14:58:53,264 INFO  [EJB3EndpointDeployer] Deploy AbstractBeanMetaData at 7d74f5f{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true}
  | 14:58:53,600 INFO  [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3
  | 14:58:53,621 INFO  [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureDeploymentManager ejbName: SecureDeploymentManager
  | 14:58:53,759 INFO  [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:
  | 
  | 	SecureDeploymentManager/remote - EJB3.x Default Remote Business Interface
  | 	SecureDeploymentManager/remote-org.jboss.deployers.spi.management.deploy.DeploymentManager - EJB3.x Remote Business Interface
  | 
  | 14:58:53,904 INFO  [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3
  | 14:58:53,906 INFO  [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureManagementView ejbName: SecureManagementView
  | 14:58:53,922 INFO  [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:
  | 
  | 	SecureManagementView/remote - EJB3.x Default Remote Business Interface
  | 	SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView - EJB3.x Remote Business Interface
  | 
  | 14:58:53,983 INFO  [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3
  | 14:58:54,005 INFO  [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureProfileServiceBean ejbName: SecureProfileService
  | 14:58:54,045 INFO  [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:
  | 
  | 	SecureProfileService/remote - EJB3.x Default Remote Business Interface
  | 	SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService - EJB3.x Remote Business Interface
  | 
  | 14:58:54,261 INFO  [TomcatDeployment] deploy, ctxPath=/admin-console
  | 14:58:54,401 INFO  [config] Initializing Mojarra (1.2_12-b01-FCS) for context '/admin-console'
  | 14:58:57,751 INFO  [TomcatDeployment] deploy, ctxPath=/
  | 14:58:57,828 INFO  [TomcatDeployment] deploy, ctxPath=/jmx-console
  | 14:58:57,991 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
  | 
  | DEPLOYMENTS MISSING DEPENDENCIES:
  |   Deployment "WSDeploymentAspectInstallerEJB" is missing the following dependencies:
  |     Dependency "WSInjectionMetaDataDeploymentAspect" (should be in state "Configured", but is actually in state "**ERROR**")
  |   Deployment "WSDeploymentAspectInstallerPreJSE" is missing the following dependencies:
  |     Dependency "WSInjectionMetaDataDeploymentAspect" (should be in state "Configured", but is actually in state "**ERROR**")
  |   Deployment "WSMetroDeploymentAspectInstallerEJB" is missing the following dependencies:
  |     Dependency "WSDeploymentAspectInstallerEJB" (should be in state "Create", but is actually in state "Instantiated")
  |   Deployment "WSMetroDeploymentAspectInstallerPreJSE" is missing the following dependencies:
  |     Dependency "WSDeploymentAspectInstallerPreJSE" (should be in state "Create", but is actually in state "Instantiated")
  | 
  | DEPLOYMENTS IN ERROR:
  |   Deployment "WSInjectionMetaDataDeploymentAspect" is in error due to the following reason(s): java.lang.ClassNotFoundException: org.jboss.wsf.spi.metadata.injection.ReferenceResolver, **ERROR**
  |   Deployment "WSMetroDeploymentAspectInstallerPostJSE" is in error due to the following reason(s): java.lang.IllegalStateException: Cannot add deployment aspect(s)
  | WSDeploymentAspectManagerPreJSE provides: []
  | WSDeploymentAspectManagerPostJSE provides: []
  |    org.jboss.wsf.container.jboss50.deployment.RuntimeLoaderDeploymentAspect, requires: ContainerMetaData
  |    org.jboss.wsf.framework.deployment.EndpointRecordProcessorDeploymentAspect, requires: RegisteredEndpoint
  |    org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect, requires: RuntimeLoader, StackDescriptor
  |    org.jboss.wsf.framework.deployment.EndpointHandlerDeploymentAspect, requires: ContainerEndpointHandler
  | 
  | 14:58:58,057 INFO  [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
  | 14:58:58,089 INFO  [AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009
  | 14:58:58,100 INFO  [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] Started in 47s:428ms

[/url]

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

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


From do-not-reply at jboss.com  Wed May 27 18:18:51 2009
From: do-not-reply at jboss.com (RichardTaylor)
Date: Wed, 27 May 2009 18:18:51 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS Metro 3.1.1 on AS 5.1.0
	Startup errors?
Message-ID: <21302178.1243462731635.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I just realized that there is a JBossWS Metro specific forum.  Could you please move this to that forum.  Thanks.

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

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


From do-not-reply at jboss.com  Thu May 28 01:53:40 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Thu, 28 May 2009 01:53:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS Metro 3.1.1 on AS 5.1.0
	Startup errors?
Message-ID: <29706516.1243490020357.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Please all jbossws-spi.jar if they contain org/jboss/wsf/spi/metadata/injection/ReferenceResolver
If not, please copy/paste META-INF/MANIFEST.MF here.

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

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


From do-not-reply at jboss.com  Thu May 28 01:55:06 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Thu, 28 May 2009 01:55:06 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS Metro 3.1.1 on AS 5.1.0
	Startup errors?
Message-ID: <18703916.1243490106779.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Here are the files locations:

$JBOSS_HOME/common/lib/jbossws-spi.jar
$JBOSS_HOME/client/jbossws-spi.jar


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

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


From do-not-reply at jboss.com  Thu May 28 02:12:07 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Thu, 28 May 2009 02:12:07 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS Metro 3.1.1 on AS 5.1.0
	Startup errors?
Message-ID: <30083924.1243491127976.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Aha, already see your problem. Note that JBossWS-Metro 3.1.1 cannot run on AS 5.1.0.GA, see Supported Target Containers

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

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


From do-not-reply at jboss.com  Thu May 28 06:38:15 2009
From: do-not-reply at jboss.com (Deepz)
Date: Thu, 28 May 2009 06:38:15 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: org.jboss.ws.WSException: Cannot
	obtain java type mappin
Message-ID: <22420702.1243507095244.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I am getting this when I try to enter a website whci is being hosted in my machine? has anybody got an answer for this ?

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

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


From do-not-reply at jboss.com  Thu May 28 08:40:09 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Thu, 28 May 2009 08:40:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: org.jboss.ws.WSException: Cannot
	obtain java type mappin
Message-ID: <14079933.1243514409225.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

This thread and its contents are years old; please move to JAX-WS and follow the user guide.

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

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


From do-not-reply at jboss.com  Thu May 28 08:43:13 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Thu, 28 May 2009 08:43:13 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS Metro 3.1.1 on AS 5.1.0
	Startup errors?
Message-ID: <31827146.1243514593930.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

If you want to run the Metro stack on AS 5.1.0.GA, either compile JBossWS-Metro 3.2.0-SNAPSHOT from sources or please wait for the 3.2.0.GA release.

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

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


From do-not-reply at jboss.com  Thu May 28 08:52:37 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Thu, 28 May 2009 08:52:37 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: NotSerializableException:
	org.jboss.ws.core.soap.SOAPFau
Message-ID: <26865079.1243515157978.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi lafr,
first of all thanks for posting this. Is the exception stacktrace you posted here complete? It's not clear to me when that serialization actually happen.
Knowing a bit more about the ws client might help understanding your specific issue.
Also knowing what else you changed in the sources to solve the serialization issue would help.
thanks

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

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


From do-not-reply at jboss.com  Thu May 28 08:55:00 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Thu, 28 May 2009 08:55:00 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Memory leak with Provider<Source>
	webservice implementat
Message-ID: <19112900.1243515300772.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Yes please, and link it to this thread. Thanks a lot for the analysis.

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

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


From do-not-reply at jboss.com  Thu May 28 08:59:27 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Thu, 28 May 2009 08:59:27 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Eorros of creating WS client stub
	class
Message-ID: <27166514.1243515567116.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Basically, you need to check your classpath: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=136698

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

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


From do-not-reply at jboss.com  Thu May 28 09:06:07 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Thu, 28 May 2009 09:06:07 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS client not sending Basic
	Authentication
Message-ID: <5289138.1243515967329.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Which version of JBossWS are you using? Given the current lib configuration, you're using the different jax-ws implementation when switching from JDK 1.5 to 1.6 (more specifically you use the Sun's one with JDK6 as you don't have jbossws specific jars in endorsed dir).
Perhaps you might want to try with more recent jbossws version?

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

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


From do-not-reply at jboss.com  Thu May 28 13:08:02 2009
From: do-not-reply at jboss.com (jrinderle)
Date: Thu, 28 May 2009 13:08:02 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Resteasy,
	handling and logging of WebApplicationException
Message-ID: <8358661.1243530482760.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Resteasy logs a stracktrace for all WebApplicationExceptions, which is not what I was expecting. My expectation was that Resteasy would catch this exception and return an appropriate response, but not log the exception. This creates a lot of output in the server logs.

* What is the most appropriate way to specify a response status? I could return Response but it seems cleaner to return a specific type and throw WebApplicationException for errors.

I created the following test case:


  | 	@GET
  | 	@Path("/status/{code}")
  | 	public String getStatus(@PathParam("code") int statusCode) {
  | 		throw new WebApplicationException(statusCode);
  | 	}
  | 

No matter what code I specify, the exception stack trace is logged to STDERR and I get the JBossWeb default error page back (even if I modify the code to specify no content).

* This behavior caused me to question my understanding. Should I not specify a response status by throwing a WebApplicationException? Should I instead return Response or use a custom exception with an exception mapper? In a production environment I do not need to log a stack trace for 401, 404, etc.

* Is it possible to disable the default error page and return an empty response? I tried changing the test case to throw new WebApplicationException(Response.noContent().status(statusCode).build()); but I still get default error page.

* I was also surprised to see the exception logged to STDERR. The documentation says that Resteasy uses slf4j configured or log4j. Perhaps I have something configured incorrectly?

I have tested this behavior with Resteasy 1.0.2GA and 1.1RC2. I am running on JBoss 4.2.3.GA. 

When I request this resource with /status/401, I get the following response (output is from curl). 


  | < HTTP/1.1 401 Unauthorized
  | < Date: Thu, 28 May 2009 16:36:38 GMT
  | < Server: Apache
  | < Content-Length: 948
  | < Content-Type: text/html;charset=utf-8
  | * Connection #0 to host localhost left intact
  | * Closing connection #0
  | <html><head><title>JBossWeb/2.0.1.GA - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 401 - </h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u></u></p><p><b>description</b> <u>This request requires HTTP authentication ().</u></p><HR size="1" noshade="noshade"><h3>JBossWeb/2.0.1.GA</h3></body></html>
  | 

And the following exception is logged (I sanitized my class and package name, line 74 corresponds to the exception thrown above):


  | 2009-05-28 12:38:42,883 ERROR [STDERR] 147486 [ajp-127.0.0.1-8009-11] ERROR org.jboss.resteasy.core.SynchronousDispatcher - failed t
  | o execute
  | 2009-05-28 12:38:42,883 ERROR [STDERR] javax.ws.rs.WebApplicationException
  | 2009-05-28 12:38:42,883 ERROR [STDERR]  at my.test.app.MyResource.getSessionDetails(MyResource.ja
  | va:74)
  | 2009-05-28 12:38:42,883 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 2009-05-28 12:38:42,884 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | 2009-05-28 12:38:42,884 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 2009-05-28 12:38:42,884 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:597)
  | 2009-05-28 12:38:42,884 ERROR [STDERR]  at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:119)
  | 2009-05-28 12:38:42,884 ERROR [STDERR]  at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:211)
  | 2009-05-28 12:38:42,884 ERROR [STDERR]  at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:176)
  | 2009-05-28 12:38:42,884 ERROR [STDERR]  at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:166)
  | 2009-05-28 12:38:42,884 ERROR [STDERR]  at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356)
  | 2009-05-28 12:38:42,884 ERROR [STDERR]  at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:160)
  | 2009-05-28 12:38:42,885 ERROR [STDERR]  at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispat
  | cher.java:113)
  | 2009-05-28 12:38:42,885 ERROR [STDERR]  at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispat
  | cher.java:69)
  | 2009-05-28 12:38:42,885 ERROR [STDERR]  at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
  | 2009-05-28 12:38:42,885 ERROR [STDERR]  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j
  | ava:290)
  | 2009-05-28 12:38:42,885 ERROR [STDERR]  at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
  | 2009-05-28 12:38:42,885 ERROR [STDERR]  at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
  | 2009-05-28 12:38:42,885 ERROR [STDERR]  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j
  | ava:235)
  | 2009-05-28 12:38:42,885 ERROR [STDERR]  at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
  | 2009-05-28 12:38:42,886 ERROR [STDERR]  at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
  | 2009-05-28 12:38:42,886 ERROR [STDERR]  at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
  | 2009-05-28 12:38:42,886 ERROR [STDERR]  at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.ja
  | va:182)
  | 2009-05-28 12:38:42,886 ERROR [STDERR]  at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
  | 2009-05-28 12:38:42,886 ERROR [STDERR]  at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
  | 2009-05-28 12:38:42,886 ERROR [STDERR]  at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
  | 2009-05-28 12:38:42,886 ERROR [STDERR]  at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:
  | 157)
  | 2009-05-28 12:38:42,886 ERROR [STDERR]  at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
  | 2009-05-28 12:38:42,886 ERROR [STDERR]  at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
  | 2009-05-28 12:38:42,887 ERROR [STDERR]  at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437)
  | 2009-05-28 12:38:42,887 ERROR [STDERR]  at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:366)
  | 2009-05-28 12:38:42,887 ERROR [STDERR]  at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
  | 2009-05-28 12:38:42,887 ERROR [STDERR]  at java.lang.Thread.run(Thread.java:619)
  | 

SynchronousDispatcher.java:324:

if (!(wae instanceof NoLogWebApplicationException)) logger.error("failed to execute", wae);

My web.xml is as follows:


  | <?xml version="1.0" encoding="UTF-8"?>
  | <web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
  | 	<context-param>
  | 		<param-name>resteasy.scan</param-name>
  | 		<param-value>true</param-value>
  | 	</context-param>
  | 	<listener>
  | 		<listener-class>org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap</listener-class>
  | 	</listener>
  | 	<servlet>
  | 		<servlet-name>RESTeasy</servlet-name>
  | 		<servlet-class>org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher</servlet-class>
  | 	</servlet>
  | 	<servlet-mapping>
  | 		<servlet-name>RESTeasy</servlet-name>
  | 		<url-pattern>/*</url-pattern>
  | 	</servlet-mapping>
  | </web-app>
  | 

Thank you for your help!

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

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


From do-not-reply at jboss.com  Fri May 29 12:53:24 2009
From: do-not-reply at jboss.com (RichardTaylor)
Date: Fri, 29 May 2009 12:53:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS Metro 3.1.1 on AS 5.1.0
	Startup errors?
Message-ID: <22124528.1243616004753.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Thanks, hadn't come across the Supported Target Containers page.  We're working on getting JBoss Native going, it looks like a few issues have been fixed that were blockers for us.  Will build Metro 3.2.0 as needed.   Cheers

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

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


From do-not-reply at jboss.com  Sat May 30 21:42:06 2009
From: do-not-reply at jboss.com (echofrank)
Date: Sat, 30 May 2009 21:42:06 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Receiving Compressed WebService
	Requests
Message-ID: <14987019.1243734126874.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I also got stuck on this. Any suggestions? Please help. Thanks.

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

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