[JBossWS] - No jboss.xml equivalent for @EndpointConfig in JBoss 4.2.3
by hoogenbj
Hi Everyone,
In addition to expanding the JBoss installed base of our product, we want to expand into the SAP NetWeaver 7.1 sphere of influence. Part of the porting exercise involves finding equivalent jboss.xml entries for proprietary JBoss annotations.
The only annotation I have been unable to find an equivalent for is @EndPointConfig used in some of our EJB3 SLSB-based web services.
Googling located some hints in the JBossWS JIRA of this having been raised before, but I have been unable to find specifics. Besides, the JIRA site is horribly slow. I also found some reference to config-name in the jboss_4_2.dtd in the docs/dtd subfolder for my JBoss installation, but this appears to be incomplete. After using the hints I found in the dtd, I deployed my application with a config-name element inside the webservices element of jboss.xml. This resulted in deployment errors. Which I expected since the dtd appears to be incomplete.
Can anyone confirm if this has been raised before and if so, the outcome thereof?
Having a single codebase for all the platforms our product will run on has obvious advantages...
I upgraded my JBoss4.2.3 to the latest JBossWS native version - 3.1.1.
Regards,
Johan
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227099#4227099
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227099
16 years, 6 months
[JBossWS] - Does not recognize xsd:datetime
by uannight
I have a webservice with integer,string and Date, the wsdl generate a xsd:datetime but when i am trying to launch the webservice i am having this error.
arguments java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang. String,java.lang.String,java.lang.String,java.util.GregorianCalendar. The arguments do not match the signature.; nested exception is: java.lang.IllegalArgumentException: ComponentManager:getService service alarm service not found!
This error is changing the Date by Calendar (both have the same error). If I remove the element with Date or Calendar the webservice is working.
This is the wsdl:
<?xml version="1.0" encoding="UTF-8"?>
| <wsdl:definitions targetNamespace="http://ws.alarm.services.mmplat"
| xmlns:apachesoap="http://xml.apache.org/xml-soap"
| xmlns:impl="http://ws.alarm.services.mmplat"
| xmlns:intf="http://ws.alarm.services.mmplat"
| xmlns:tns2="http://types.alarm.services.mmplat"
| xmlns:tns3="http://to.pegasus.db.mmplat" xmlns:tns4="http://types.pegasus.db.mmplat"
| xmlns:tns5="http://enumeration.types.alarm.services.mmplat"
| xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
| xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org
| /2001/XMLSchema">
| <!--WSDL created by Apache Axis version: 1.4
| Built on Apr 22, 2006 (06:55:48 PDT)-->
| <wsdl:types>
| <schema targetNamespace="http://types.pegasus.db.mmplat" xmlns="http://www.w3.org/2001/XMLSchema">
| <import namespace="http://types.alarm.services.mmplat"/>
| <import namespace="http://to.pegasus.db.mmplat"/>
| <import namespace="http://enumeration.types.alarm.services.mmplat"/>
| <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
| <complexType name="GenericType">
| <sequence/>
| </complexType>
| <complexType name="ObjectID">
| <sequence>
| <element name="objectValue" nillable="true" type="xsd:long"/>
| <element name="value" type="xsd:long"/>
| </sequence>
| </complexType>
| </schema>
| <schema targetNamespace="http://to.pegasus.db.mmplat" xmlns="http://www.w3.org/2001/XMLSchema">
| <import namespace="http://types.alarm.services.mmplat"/>
| <import namespace="http://types.pegasus.db.mmplat"/>
| <import namespace="http://enumeration.types.alarm.services.mmplat"/>
| <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
| <complexType name="GenericTO">
| <complexContent>
| <extension base="tns4:GenericType">
| <sequence>
| <element name="id" nillable="true" type="tns4:ObjectID"/>
| </sequence>
| </extension>
| </complexContent>
| </complexType>
| </schema>
| <schema targetNamespace="http://enumeration.types.alarm.services.mmplat" xmlns="http://www.w3.org/2001/XMLSchema">
| <import namespace="http://types.alarm.services.mmplat"/>
| <import namespace="http://types.pegasus.db.mmplat"/>
| <import namespace="http://to.pegasus.db.mmplat"/>
| <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
| <complexType name="StateAlarmType">
| <sequence/>
| </complexType>
| <complexType name="SendType">
| <sequence/>
| </complexType>
| </schema>
| <schema targetNamespace="http://types.alarm.services.mmplat" xmlns="http://www.w3.org/2001/XMLSchema">
| <import namespace="http://types.pegasus.db.mmplat"/>
| <import namespace="http://to.pegasus.db.mmplat"/>
| <import namespace="http://enumeration.types.alarm.services.mmplat"/>
| <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
| <complexType name="AlarmTO">
| <complexContent>
| <extension base="tns3:GenericTO">
| <sequence>
| <element name="alarmType" nillable="true" type="xsd:string"/>
| <element name="dateCreated" nillable="true" type="xsd:dateTime"/>
| <element name="dateOperation" nillable="true" type="xsd:string"/>
| <element name="dateSend" nillable="true" type="xsd:dateTime"/>
| <element name="dateSent" nillable="true" type="xsd:dateTime"/>
| <element name="dateUpdated" nillable="true" type="xsd:dateTime"/>
| <element name="descripcion" nillable="true" type="xsd:string"/>
| <element name="idTraffic" nillable="true" type="tns4:ObjectID"/>
| <element name="msisdn" nillable="true" type="xsd:string"/>
| <element name="name" nillable="true" type="xsd:string"/>
| <element name="nameCatAlert" nillable="true" type="xsd:string"/>
| <element name="operation" nillable="true" type="xsd:string"/>
| <element name="reference" nillable="true" type="xsd:string"/>
| <element name="serviceID" nillable="true" type="tns4:ObjectID"/>
| <element name="state" nillable="true" type="tns5:StateAlarmType"/>
| <element name="type" nillable="true" type="tns5:SendType"/>
| </sequence>
| </extension>
| </complexContent>
| </complexType>
| </schema>
| </wsdl:types>
|
| <wsdl:message name="invokeSMSAlarmResponse">
|
| <wsdl:part name="invokeSMSAlarmReturn" type="xsd:int"/>
|
| </wsdl:message>
|
| <wsdl:message name="invokeSMSAlarmRequest">
|
| <wsdl:part name="in0" type="xsd:string"/>
|
| <wsdl:part name="in1" type="xsd:string"/>
|
| <wsdl:part name="in2" type="xsd:string"/>
|
| <wsdl:part name="in3" type="xsd:string"/>
|
| <wsdl:part name="in4" type="xsd:string"/>
|
| <wsdl:part name="in5" type="xsd:string"/>
|
| <wsdl:part name="in6" type="xsd:string"/>
|
| <wsdl:part name="in7" type="xsd:dateTime"/>
|
| </wsdl:message>
|
| <wsdl:message name="triggerAlarmResponse">
|
| <wsdl:part name="triggerAlarmReturn" type="xsd:boolean"/>
|
| </wsdl:message>
|
| <wsdl:message name="registerPaymentRequest">
|
| <wsdl:part name="in0" type="xsd:string"/>
|
| <wsdl:part name="in1" type="xsd:string"/>
|
| <wsdl:part name="in2" type="xsd:string"/>
|
| <wsdl:part name="in3" type="xsd:string"/>
|
| <wsdl:part name="in4" type="xsd:string"/>
|
| </wsdl:message>
|
| <wsdl:message name="pruebaResponse">
|
| </wsdl:message>
|
| <wsdl:message name="invokeSMSAlarm2Request">
|
| <wsdl:part name="in0" type="xsd:string"/>
|
| <wsdl:part name="in1" type="xsd:string"/>
|
| <wsdl:part name="in2" type="xsd:string"/>
|
| <wsdl:part name="in3" type="xsd:string"/>
|
| <wsdl:part name="in4" type="xsd:string"/>
|
| <wsdl:part name="in5" type="xsd:string"/>
|
| <wsdl:part name="in6" type="xsd:string"/>
|
| </wsdl:message>
|
| <wsdl:message name="prueba2Request">
|
| <wsdl:part name="in0" type="xsd:int"/>
|
| </wsdl:message>
|
| <wsdl:message name="pruebaRequest">
|
| </wsdl:message>
|
| <wsdl:message name="registerPaymentResponse">
|
| </wsdl:message>
|
| <wsdl:message name="invokeSMSAlarm2Response">
|
| <wsdl:part name="invokeSMSAlarm2Return" type="xsd:int"/>
|
| </wsdl:message>
|
| <wsdl:message name="prueba2Response">
|
| </wsdl:message>
|
| <wsdl:message name="triggerAlarmRequest">
|
| <wsdl:part name="in0" type="tns2:AlarmTO"/>
|
| </wsdl:message>
|
| <wsdl:portType name="AlarmService">
|
| <wsdl:operation name="prueba">
|
| <wsdl:input message="impl:pruebaRequest" name="pruebaRequest"/>
|
| <wsdl:output message="impl:pruebaResponse" name="pruebaResponse"/>
|
| </wsdl:operation>
|
| <wsdl:operation name="prueba2" parameterOrder="in0">
|
| <wsdl:input message="impl:prueba2Request" name="prueba2Request"/>
|
| <wsdl:output message="impl:prueba2Response" name="prueba2Response"/>
|
| </wsdl:operation>
|
| <wsdl:operation name="triggerAlarm" parameterOrder="in0">
|
| <wsdl:input message="impl:triggerAlarmRequest" name="triggerAlarmRequest"/>
|
| <wsdl:output message="impl:triggerAlarmResponse" name="triggerAlarmResponse"/>
|
| </wsdl:operation>
|
| <wsdl:operation name="invokeSMSAlarm" parameterOrder="in0 in1 in2 in3 in4 in5 in6 in7">
|
| <wsdl:input message="impl:invokeSMSAlarmRequest" name="invokeSMSAlarmRequest"/>
|
| <wsdl:output message="impl:invokeSMSAlarmResponse" name="invokeSMSAlarmResponse"/>
|
| </wsdl:operation>
|
| <wsdl:operation name="invokeSMSAlarm2" parameterOrder="in0 in1 in2 in3 in4 in5 in6">
|
| <wsdl:input message="impl:invokeSMSAlarm2Request" name="invokeSMSAlarm2Request"/>
|
| <wsdl:output message="impl:invokeSMSAlarm2Response" name="invokeSMSAlarm2Response"/>
|
| </wsdl:operation>
|
| <wsdl:operation name="registerPayment" parameterOrder="in0 in1 in2 in3 in4">
|
| <wsdl:input message="impl:registerPaymentRequest" name="registerPaymentRequest"/>
|
| <wsdl:output message="impl:registerPaymentResponse" name="registerPaymentResponse"/>
|
| </wsdl:operation>
|
| </wsdl:portType>
|
| <wsdl:binding name="AlarmServiceSoapBinding" type="impl:AlarmService">
|
| <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
|
| <wsdl:operation name="prueba">
|
| <wsdlsoap:operation soapAction=""/>
|
| <wsdl:input name="pruebaRequest">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:input>
|
| <wsdl:output name="pruebaResponse">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:output>
|
| </wsdl:operation>
|
| <wsdl:operation name="prueba2">
|
| <wsdlsoap:operation soapAction=""/>
|
| <wsdl:input name="prueba2Request">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:input>
|
| <wsdl:output name="prueba2Response">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:output>
|
| </wsdl:operation>
|
| <wsdl:operation name="triggerAlarm">
|
| <wsdlsoap:operation soapAction=""/>
|
| <wsdl:input name="triggerAlarmRequest">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:input>
|
| <wsdl:output name="triggerAlarmResponse">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:output>
|
| </wsdl:operation>
|
| <wsdl:operation name="invokeSMSAlarm">
|
| <wsdlsoap:operation soapAction=""/>
|
| <wsdl:input name="invokeSMSAlarmRequest">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:input>
|
| <wsdl:output name="invokeSMSAlarmResponse">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:output>
|
| </wsdl:operation>
|
| <wsdl:operation name="invokeSMSAlarm2">
|
| <wsdlsoap:operation soapAction=""/>
|
| <wsdl:input name="invokeSMSAlarm2Request">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:input>
|
| <wsdl:output name="invokeSMSAlarm2Response">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:output>
|
| </wsdl:operation>
|
| <wsdl:operation name="registerPayment">
|
| <wsdlsoap:operation soapAction=""/>
|
| <wsdl:input name="registerPaymentRequest">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:input>
|
| <wsdl:output name="registerPaymentResponse">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:output>
|
| </wsdl:operation>
|
| </wsdl:binding>
|
| <wsdl:service name="AlarmServiceService">
|
| <wsdl:port binding="impl:AlarmServiceSoapBinding" name="AlarmService">
|
| <wsdlsoap:address location="http://localhost:8080/services/AlarmService"/>
|
| </wsdl:port>
|
| </wsdl:service>
|
| </wsdl:definitions>
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226899#4226899
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226899
16 years, 6 months
[JBossWS] - http proxy error profile
by zurchman
Does this error profile suggest anything to anyone?
The program sets endpoints dynamically and works correctly with two of four endpoints. The trace below is from one of the endpoints that fails.
I don't recall seeing the "Squid" message on the endpoints that work. It appears that the client fails immediately without waiting for a response from the service.
This is the latest JBossWS native stack installed in jboss-4.2.3.GA.
16:45:16,158 TRACE SOAPMessageUnMarshallerHTTP:62 - Read input tream with metadata={Proxy-Connection=[close], Date=[Sun, 26 Apr 2009 20:44:35 GMT], Content-Type=[text/html], NoThrowOnError=true, ResponseCode=501, Content-Length=[1206], Expires=[Sun, 26 Apr 2009 20:44:35 GMT], ResponseCodeMessage=Not Implemented, X-Cache-Lookup=[NONE from [default_router]:3128], X-Squid-Error=[ERR_UNSUP_REQ 0], HEADER={SOAPAction="http://[service_Qname]", Content-Type=text/xml; charset=UTF-8}, Server=[squid/2.5.STABLE9], Mime-Version=[1.0], X-Cache=[MISS from [default_router]]}
| 16:45:16,174 ERROR CommonClient:404 - Exception caught while preparing for) performing the invocation:
| java.io.IOException: Could not transmit message
| at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:265)
| at org.jboss.ws.core.client.SOAPProtocolConnectionHTTP.invoke(SOAPProtocolConnectionHTTP.java:71)
| at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:340)
| at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:290)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
| at $Proxy26.quote(Unknown Source)
| at [test_op]([test_program].java:386)
| at ...
| Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker. Invalid HTTP server response [501] - Not Implemented. Response: Not Implemented/501.
| at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:348)
| at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:137)
| at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
| at org.jboss.remoting.Client.invoke(Client.java:1634)
| at org.jboss.remoting.Client.invoke(Client.java:548)
| at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:243)
| ... 9 more
| Caused by: org.jboss.ws.WSException: Invalid HTTP server response [501] - Not Implemented
| at org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP.read(SOAPMessageUnMarshallerHTTP.java:75)
| at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:518)
| at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:307)
| ... 14 more
| 16:45:16,177 DEBUG MessageContextJAXWS:106 - Begin response processing
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226801#4226801
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226801
16 years, 6 months