axis2c - generated skeleton files using WSDL2C for array of structure having a RESET function. how to use it?
Hi, generated skeleton files using WSDL2C for array structures. Request and response generated files for the unbounded structure data type has a RESET function. how to use it? any help who have used the Structure array will be helpful. -Viji. -- View this message in context: http://www.nabble.com/axis2c---generated-skeleton-files-using-WSDL2C-for-array-of-structure-having-a-RESET-function.-how-to-use-it--tf3471795.html#a9688599 Sent from the Axis - C++ - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2c - generated skeleton files using WSDL2C for array of structure having a RESET function. how to use it?
Hi,
Consider a echo example which echo incoming array of integers like this:
Request Structure:
struct axis2_echoInts
{
axis2_qname_t* qname;
axis2_array_list_t* attrib_input;
};
Response Structure:
struct axis2_echoIntsResponse
{
axis2_qname_t* qname;
axis2_array_list_t* attrib_echoIntsReturn;
};
Business Logic Implementation:
axis2_echoIntsResponse_t* axis2_skel_Benchmark_echoInts (const axis2_env_t
*env ,
axis2_echoInts_t*
echoInts )
{
/* TODO fill this with the necessary business logic */
axis2_echoIntsResponse_t *response = NULL;
axis2_array_list_t *input = NULL;
response = axis2_echoIntsResponse_create(env);
input = AXIS2_ECHOINTS_GET_INPUT(echoInts, env);
AXIS2_ECHOINTSRESPONSE_SET_ECHOINTSRETURN(response, env, input);
AXIS2_ECHOINTS_RESET_INPUT(echoInts, env);
return response;
}
Code that select correct operation inside service skeleton's invoke
function:
if ( AXIS2_STRCMP(op_name, echoInts) == 0 )
{
input_val11_1 =
axis2_echoInts_create( env);
AXIS2_ECHOINTS_DESERIALIZE(input_val11_1, env,
content_node );
ret_val11 = axis2_skel_Benchmark_echoInts(env,
input_val11_1 );
if ( NULL == ret_val11 )
{
AXIS2_LOG_ERROR( env-log, AXIS2_LOG_SI, NULL
returnted from the business logic from echoInts
%d :: %s,
env-error-error_number,
AXIS2_ERROR_GET_MESSAGE(env-error));
return axis2_svc_skel_Benchmark_on_fault(
svc_skeleton, env, NULL);
}
ret_node =
AXIS2_ECHOINTSRESPONSE_SERIALIZE(ret_val11,
env, NULL, AXIS2_FALSE);
AXIS2_ECHOINTSRESPONSE_FREE(ret_val11, env);
AXIS2_ECHOINTS_FREE(input_val11_1, env);
return ret_node;
}
In the service skeleton's invoke function we get payload(axiom_node) of the
incoming request as parameter. After that we check which operation we have
to execute.
After selecting correct operation we desirialize the incoming payload to
echoInts structure and give it as a parameter to the
axis2_skel_Benchmark_echoInts
function.
input_val11_1 = axis2_echoInts_create( env);
AXIS2_ECHOINTS_DESERIALIZE(input_val11_1, env,
content_node );
ret_val11 = axis2_skel_Benchmark_echoInts(env,
input_val11_1 );
Inside this function we extract the data inside structure and assign it to
the response structure.
input = AXIS2_ECHOINTS_GET_INPUT(echoInts, env);
AXIS2_ECHOINTSRESPONSE_SET_ECHOINTSRETURN(response, env, input);
after that we reset the echoInts structure.
AXIS2_ECHOINTS_RESET_INPUT(echoInts, env);
This reseting done because inside invoke function we free the two structures
created after serving for the request. Inside the logic of free function we
free all the elements inside array lists. In this free process, problem
occurs when we trying to free bot h structures . Because we share same
elements between two structures using pointers. Therefore we have to remove
one pointer from pointing to same array lists. After that no double freeing
occur, because we remove the reference to that memory location from one
structure. Please go through code inside free logics, then you will be able
to understand the situation. This reseting mechanism does not require if we
don't assign the same attributes to the response structure.
Thanks
Milinda
On 3/27/07, Prem [EMAIL PROTECTED] wrote:
Hi,
generated skeleton files using WSDL2C for array structures.
Request and response generated files for the unbounded structure data type
has a RESET function. how to use it?
any help who have used the Structure array will be helpful.
-Viji.
--
View this message in context:
http://www.nabble.com/axis2c---generated-skeleton-files-using-WSDL2C-for-array-of-structure-having-a-RESET-function.-how-to-use-it--tf3471795.html#a9688599
Sent from the Axis - C++ - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
[EMAIL PROTECTED]
WSO2, Inc: http://www.wso2.com Oxygenating the Web Service Platform
http://www.milindalakmal.wordpress.com
Axis2 XMLBeans,JAXB validation?
Hi all,
I am using Axis2 WSDL2Java and generate java classes from wsdl.
In the generated java classes I can't see any validation code for patterns
maping from my schema.
I tried JAXB, XMLBean as binding options.
How can I handle validation for restrictions when using JAXB or XMLBeans as a
databinding in Axis2?
Here is my schema file:
?xml version=1.0 encoding=UTF-8?
xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema;
elementFormDefault=qualified attributeFormDefault=unqualified
xs:element name=myElement
xs:complexType
xs:sequence
xs:element name=element1 minOccurs=0
xs:annotation
xs:documentationUsed as ID. Account
code/xs:documentation
/xs:annotation
xs:simpleType
xs:restriction base=xs:string
xs:pattern
value=^((([1-9][0-9]{0,14},)|([1-9][0-9]{0,14}-[1-9][0-9]{0,14},))*([1-9][0-9]{0,14}|([1-9][0-9]{0,14}-[1-9][0-9]{0,14})))$|^([Aa][Ll][Ll])$|^([][1-9][0-9]{0,14})$/
/xs:restriction
/xs:simpleType
/xs:element
/xs:sequence
/xs:complexType
/xs:element
xs:element name=myElement1
xs:complexType
xs:sequence
xs:element ref=tns:myElement minOccurs=0
maxOccurs=4000/
/xs:sequence
/xs:complexType
/xs:element
/xs:schema
Reneta
AXIS2-1.2RC1 still not fully support XML schema
When I develop a POJO web service, AXIS2-1.2RC1 sill can not map some java data types[1] to corresponding XML data type and serialize/deserialize them. I have log this bug in AXIS2-2253. As Dim said, this will be solved in AXIS1.2. May I know if this will be solved in the axis2-1.2 final release? best regards donald [1] java data types that AXIS2-1.2RC1 can not deal with java.math.BigDecimal; java.math.BigInteger; javax.xml.namespace.QName; org.apache.axis.types.Day; org.apache.axis.types.Duration; org.apache.axis.types.Month; org.apache.axis.types.MonthDay; org.apache.axis.types.NegativeInteger; org.apache.axis.types.NonNegativeInteger; org.apache.axis.types.NonPositiveInteger; org.apache.axis.types.PositiveInteger; org.apache.axis.types.Time; org.apache.axis.types.UnsignedByte; org.apache.axis.types.UnsignedInt; org.apache.axis.types.UnsignedLong; org.apache.axis.types.UnsignedShort; org.apache.axis.types.Year; org.apache.axis.types.YearMonth;
Re: [AXIS2] - Engaging addressing module on client
Hello, I have further noticed that if i only include the addressing .mar file in the classpath (without changing any code), i get the exception org.apache.axis2.AxisFault: A required header representing a Message Addressing Property is not present at org.apache.axis2.util.CallbackReceiver.receive(CallbackReceiver.java:65) at org.apache.axis2.engine.AxisEngine.receiveFault(AxisEngine.java:610) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:326) at org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:230) at ... My soap reqest is being sent but i get an Error in the reply Here is my soap request caught using TCP Monitor: POST /axis2/services/OwnService HTTP/1.1 SOAPAction: urn:anonOutInOp User-Agent: Axis2 Host: 127.0.0.1:9000 Transfer-Encoding: chunked Content-Type: text/xml; charset=UTF-8 27e ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header wsa:Tohttp://localhost:9000/axis2/services/OwnService/wsa:To wsa:ReplyTo wsa:Addresshttp://www.w3.org/2005/08/addressing/anonymous/wsa:Address /wsa:ReplyTo wsa:MessageIDurn:uuid:9B8FDACFBCA1263A121174999707376/wsa:MessageID /soapenv:Header soapenv:Body example1:tryEcho xmlns:example1=http://example1.org/example1; sleepTime=4000 code=0 example1:TextPayload echo string/example1:Text /example1:tryEcho /soapenv:Body /soapenv:Envelope0 Here is my soap response : HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Content-Type: text/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Tue, 27 Mar 2007 12:48:28 GMT Connection: close 3cc ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header wsa:Tohttp://www.w3.org/2005/08/addressing/anonymous/wsa:To wsa:ReplyTo wsa:Addresshttp://www.w3.org/2005/08/addressing/none/wsa:Address /wsa:ReplyTo wsa:MessageIDurn:uuid:AF393873831A7C3EF31174999708410/wsa:MessageID wsa:Actionhttp://www.w3.org/2005/08/addressing/fault/wsa:Action wsa:RelatesTo wsa:RelationshipType=http://www.w3.org/2005/08/addressing/reply;urn:uuid:9B8FDACFBCA1263A121174999707376/wsa:RelatesTo wsa:FaultDetail wsa:ProblemHeaderQNamewsa:Action/wsa:ProblemHeaderQName /wsa:FaultDetail /soapenv:Header soapenv:Body soapenv:Fault faultcodewsa:MessageAddressingHeaderRequired/faultcode faultstringA required header representing a Message Addressing Property is not present/faultstring detail / /soapenv:Fault /soapenv:Body /soapenv:Envelope0 I have engaged the addressing module on the server side. Kindly help. Regards, Sagar M. Yerunkar Thilina Gunarathne [EMAIL PROTECTED] 03/25/2007 10:13 AM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: [AXIS2] - Engaging addressing module on client How do i specify a .mar file in the classpath? Eclipse allows me to add no files other than jars and zips to the classpath. Yes.. If you are using Eclipse your choices are limited to the second option... ConfigurationContext configContext = ConfigurationContextFactory.createConfigurationContextFromFileSystem(repository,path to axis2.xml or null); ServiceClient sender = new ServiceClient(configContext, null); ~Thilina Please can someone guide me? Regards, Sagar M. Yerunkar __ -- Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ __
Re: Receiving complex return values when using ServiceClient.sendReceive(...)
Hi! Unfortunately, I have no answer for you, but I just encountered the same problem today. I opened an issue on Axis2 bugtracker : https://issues.apache.org/jira/browse/AXIS2-2408 Wait and see... Philipp Leitner-2 wrote: Hi all, let me apologize in advance for asking a very simple question on this list: I am using the Axis2 ServiceClient interface to do a blocking IN-OUT call to a Web Service: snip ServiceClient sender = new ServiceClient(); sender.setOptions(axis2Options); OMElement result = sender.sendReceive(axisOp); System.out.println(result); /snip This will print a result of snip getMyAddressResponse xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; getMyAddressReturn href=#id0 / /getMyAddressResponse /snip . The obvious question now is: how do I get the actual response (the type with the id 'id0') from this OMElement? What kind of surprises me is that an asynchronous call (using ServiceClient.sendReceiveNonBlocking(...) ) returns a full SOAP message as Axiom model, including the 'multiref' elements which contain the complex type responses. What is the reason for the blocking call behaving differently? The behavior of the non-blocking call seems a lot more natural to me ... I am using Axis2 1.1.1 on the client side, and Axis1 (yes, the original Axis, not Axis2 1.0!) on the server side. I would very much appreciate a little help or a documentation pointer on this issue (I would not call it a problem, since it is obviously just me not understanding how Axis2 works :-) )! /philipp -- Philipp Wolfgang Leitner, Bakk.rer.soc.oec. 0225511 Vienna University of Technology Data Mining is the art of torturing the Enterprise Data until it confesses ... but if you torture the data long enough it will confess to anything. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Receiving-complex-return-values-when-using-ServiceClient.sendReceive%28...%29-tf3458452.html#a9692207 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Receiving complex return values when using ServiceClient.sendReceive(...)
thank you for the info ... I would not have expected this to be a bug, but rather wrong usage on my side ... /philipp Cédric Girodengo schrieb: Hi! Unfortunately, I have no answer for you, but I just encountered the same problem today. I opened an issue on Axis2 bugtracker : https://issues.apache.org/jira/browse/AXIS2-2408 Wait and see... Philipp Leitner-2 wrote: Hi all, let me apologize in advance for asking a very simple question on this list: I am using the Axis2 ServiceClient interface to do a blocking IN-OUT call to a Web Service: snip ServiceClient sender = new ServiceClient(); sender.setOptions(axis2Options); OMElement result = sender.sendReceive(axisOp); System.out.println(result); /snip This will print a result of snip getMyAddressResponse xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; getMyAddressReturn href=#id0 / /getMyAddressResponse /snip . The obvious question now is: how do I get the actual response (the type with the id 'id0') from this OMElement? What kind of surprises me is that an asynchronous call (using ServiceClient.sendReceiveNonBlocking(...) ) returns a full SOAP message as Axiom model, including the 'multiref' elements which contain the complex type responses. What is the reason for the blocking call behaving differently? The behavior of the non-blocking call seems a lot more natural to me ... I am using Axis2 1.1.1 on the client side, and Axis1 (yes, the original Axis, not Axis2 1.0!) on the server side. I would very much appreciate a little help or a documentation pointer on this issue (I would not call it a problem, since it is obviously just me not understanding how Axis2 works :-) )! /philipp -- Philipp Wolfgang Leitner, Bakk.rer.soc.oec. 0225511 Vienna University of Technology Data Mining is the art of torturing the Enterprise Data until it confesses ... but if you torture the data long enough it will confess to anything. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JIBX Mapping Question - Void response message?
Dennis, To be clear, does this marker class need to physically exist? Josh On 3/26/07, Dennis Sosnoski [EMAIL PROTECTED] wrote: Hi Josh, If you're using unwrapped you shouldn't need to map this at all. If you're using wrapped handling you'd just have a marker class with an empty mapping: mapping class=updateResponse name=updateResponse/ You can see an example of the unwrapped handling for this at http://www.sosnoski.com/jibx-wiki/space/axis2-jibx/example (with the WSDL and code at http://www.sosnoski.com/jibx-wiki/space/axis2-jibx/example/library-service ). - Dennis Dennis M. Sosnoski SOA and Web Services in Java Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 Josh wrote: All, I am having difficulting dealing with an existing WSDL which declares a void response message. I have the following in my wsdl: element name=updateResponse complexType/ /element wsdl:message name=updateResponse wsdl:part element=impl:updateResponse name=parameters/ /wsdl:message Because this is really a void return, how would I map this using JiBX? Regards, Joshua - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Problems invoking Version.getVersion in 1.2 RC1
Hi,
I have the following problem using the SimpleAxis2Server and the
version.aar from the Axis2 1.2 RC1.
If I call the operation getVersion two times, the following AxisFault
is thrown.
A message was added that is not valid. However, the operation context
was complete.
The fault is generated at the following lines in the InOutAxisOperation
class
if ((inMsgContext != null) (outmsgContext != null)) {
throw new AxisFault(Messages.getMessage(mepcompleted));
With Axis2 1.1.1 everything works fine.
Any ideas?
Thanks
Tobias
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Change in wsdl2java between Axis 1.1 and 1.1.1?
Sorry, wasn't clear, I meant *Axis2* 1.1 to 1.1.1... Glen Am Dienstag, den 27.03.2007, 10:35 -0400 schrieb Glen Mazza: Hello, In upgrading from Axis 1.1 to Axis 1.1.1, I think I noticed a change in how wsdl2java works, but I'm unsure if it was something else I had done to cause this to happen. Running wsdl2java, for both serverside=true and false (using the Ant script) on this WSDL[1] (for a simple math calculator), created the following package structure: src-com-mycompany-mywebservice: - MathQandAServiceCallbackHandler.java MathQandAServiceMessageReceiverInOut.java MathQandAServiceSkeleton.java MathQandAServiceStub.java src-com-mycompany-www-schema-mathqanda: ExtensionMapper.java OperatorType.java SolveMathProblemRequest.java SolveMathProblemResponse.java The difference I noted between Axis 1.1 and 1.1.1 was that MathQandAServiceStub.java links to the classes in www.schema.mathqanda in Axis 1.1 but directly incorporates similar versions of them in Axis 1.1.1 instead. MathQandAServiceStub.java jumped from 380 lines to about 1580 as a result. Am I correct, was there a change between Axis 1.1 and 1.1.1 for the client stub class to no longer reference the classes in the wsdl:types package? (Why?) Or was there something else I had done to cause this to occur? Also, one more question, what term do people generally use to refer to the classes in www.schema.mathqanda above: the wsdl type classes? I don't know what they are normally called. Thanks, Glen [1] http://marc.info/?l=axis-userm=117394780408840w=2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 JMS samples?
I am now trying to get this thing to work against the Axis2 standalone
server. I am still getting the same exception. I am still using Axis2 1.1.1.
So I turned the debug on using LOG4J and this part of the logging messages.
Hope this helps to figure out my problem. My guess is that my client program
is able to establish a connection to ActiveMQ but it is not getting any
response. Also I attached the Simple Client I am using to test the JMS
stuff.
Thanks
[DEBUG] 55:22 (JMSSender.java:invoke:49)JMSSender invoke()
[ WARN] 55:22 (JMSOutTransportInfo.java:getDestination:108)Cannot get or
lookup JMS destination : echo from url :
jms:/echo?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryjava.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactoryjava.naming.provider.url=tcp://localhost:61616
: echo
[DEBUG] 55:23 (WireFormatNegotiator.java:start:71)Sending: WireFormatInfo {
version=2, properties={TightEncodingEnabled=true, CacheSize=1024,
TcpNoDelayEnabled=true, SizePrefixDisabled=false, StackTraceEnabled=true,
MaxInactivityDuration=3, CacheEnabled=true}, magic=[A,c,t,i,v,e,M,Q]}
[DEBUG] 55:23 (WireFormatNegotiator.java:onCommand:102)Received WireFormat:
WireFormatInfo { version=2, properties={TightEncodingEnabled=true,
CacheSize=1024, TcpNoDelayEnabled=true, SizePrefixDisabled=false,
StackTraceEnabled=true, MaxInactivityDuration=3, CacheEnabled=true},
magic=[A,c,t,i,v,e,M,Q]}
[DEBUG] 55:23
(WireFormatNegotiator.java:onCommand:109)tcp://localhost/127.0.0.1:61616
before negotiation: OpenWireFormat{version=2, cacheEnabled=false,
stackTraceEnabled=false, tightEncodingEnabled=false,
sizePrefixDisabled=false}
[DEBUG] 55:23
(WireFormatNegotiator.java:onCommand:120)tcp://localhost/127.0.0.1:61616
after negotiation: OpenWireFormat{version=2, cacheEnabled=true,
stackTraceEnabled=true, tightEncodingEnabled=true, sizePrefixDisabled=false}
[DEBUG] 55:24 (StAXUtils.java:createXMLStreamWriter:205)XMLStreamWriter is
com.ctc.wstx.sw.SimpleNsStreamWriter
[DEBUG] 55:24 (JMSSender.java:invoke:126)[Client]Sending message to
destination : queue://echo
[DEBUG] 55:24 (ActiveMQSession.java:send:1542)Sending message:
ActiveMQTextMessage {commandId = 0, responseRequired = false, messageId =
ID:UNIVERSI-D25BF5-3730-1175007323030-1:0:1:1:1, originalDestination = null,
originalTransactionId = null, producerId =
ID:UNIVERSI-D25BF5-3730-1175007323030-1:0:1:1, destination = queue://echo,
transactionId = null, expiration = 0, timestamp = 1175007324093, arrival =
0, correlationId = null, replyTo =
temp-queue://ID:UNIVERSI-D25BF5-3730-1175007323030-1:0:1, persistent = true,
type = null, priority = 4, groupID = null, groupSequence = 0,
targetConsumerId = null, compressed = false, userID = null, content = null,
marshalledProperties = null, dataStructure = null, redeliveryCounter = 0,
size = 0, properties = null, readOnlyProperties = true, readOnlyBody = true,
droppable = false, text = ?xml version='1.0'
encoding='utf-8'?soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Header
/soapenv:BodyechoString:echoString xmlns:echoString=
http://echo/jms/samples/axis2/apache/org;echoString:TextIsaac Asimov, The
Foundation
Trilogy/echoString:Text/echoString:echoString/soapenv:Body/soapenv:Envelope}
[DEBUG] 55:24 (JMSSender.java:invoke:147)Waiting for a maximum of 3ms
for a response message to destination :
temp-queue://ID:UNIVERSI-D25BF5-3730-1175007323030-1:0:1
asankha wrote:
Yes, I think there was some confusion as to which build the patch for
the particular JIRA went in.. so could you try with the 1.2 RC1 or the
latest nighly build and let me know? The information in the general JMS
transport configuration should suffice for you to get it started
asankha
lee hanu wrote:
Thanks Asanka,
I don't see the INFO message for tomcat.
I am using Tomcat 5.5(not the axis2 standalone). I am doing this against
axis2 1.1.1. Do I have to use the latest nightlies for this to work? Can I
use Axis2 1.2 RC1?
Thanks
asankha wrote:
I assume you are running a standalone client against your JMS web
service echo. However it seems like your echo service is not correctly
deployed for JMS.
Can you confirm that the JMS transport has started in your Axis2
deployment on Tomcat? You should see an [INFO] JMS Transport Receiver
(Listener) initialized... if it has. If you do not see this message,
please read https://issues.apache.org/jira/browse/AXIS2-1488
Also let me know if you are trying this on the latest trunk or on a
release - if so which version
asankha
lee hanu wrote:
I did all the steps mentioned in the JMS axis2 tutorial. I get the
following
exception. Any suggestions what I am doing wrong here. I am using Tomcat
5.5
and ActiveMQ. Do I need to do any additional configuration in the tomcat
other than the steps mentioned in the Axis2 JMS User Guide.
WARNING: Cannot get or lookup JMS destination
AW: [AXIS2] - Engaging addressing module on client
Hi Sagar in your reply message you find wsa:Actionhttp://www.w3.org/2005/08/addressing/fault/wsa:Action Axis2 intends to say in conjuntion with wsa:FaultDetail wsa:ProblemHeaderQNamewsa:Action/wsa:ProblemHeaderQName /wsa:FaultDetail and soapenv:Fault faultcodewsa:MessageAddressingHeaderRequired/faultcode faultstringA required header representing a Message Addressing Property is not present/faultstring detail / /soapenv:Fault that you did not send a wsa:Action header Try adding an wsa:Action Header as shown below in the request message. This header is missing, and that is what axis2 intends to say you. Check for ActionMapping in your service.xml, add it if not there, then you migth have something like .. file:///C:/axis2-1.1/samples/userguide/src/userguide/example5/META-INF/services.xml# - operation name=echo messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver / actionMappingurn:echo/actionMapping /operation . So yopur actionMaping wanted has to go into a SoapHeader wsa:Actionurn:echo/wsa:Action Regards Josef -Ursprüngliche Nachricht- Von: Sagar Yerunkar [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 27. März 2007 14:56 An: axis-user@ws.apache.org Betreff: Re: [AXIS2] - Engaging addressing module on client Hello, I have further noticed that if i only include the addressing .mar file in the classpath (without changing any code), i get the exception org.apache.axis2.AxisFault: A required header representing a Message Addressing Property is not present at org.apache.axis2.util.CallbackReceiver.receive(CallbackReceiver.java:65) at org.apache.axis2.engine.AxisEngine.receiveFault(AxisEngine.java:610) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:326) at org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:230) at ... My soap reqest is being sent but i get an Error in the reply Here is my soap request caught using TCP Monitor: POST /axis2/services/OwnService HTTP/1.1 SOAPAction: urn:anonOutInOp User-Agent: Axis2 Host: 127.0.0.1:9000 Transfer-Encoding: chunked Content-Type: text/xml; charset=UTF-8 27e ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header wsa:Tohttp://localhost:9000/axis2/services/OwnService/wsa:To wsa:ReplyTo wsa:Addresshttp://www.w3.org/2005/08/addressing/anonymous/wsa:Address /wsa:ReplyTo wsa:MessageIDurn:uuid:9B8FDACFBCA1263A121174999707376/wsa:MessageID wsa:Actionurn:echo/wsa:Action !!! depends on what you have in service.xml as ActionMapping for the method wanted, I asume urn:echo /soapenv:Header soapenv:Body example1:tryEcho xmlns:example1=http://example1.org/example1; sleepTime=4000 code=0 example1:TextPayload echo string/example1:Text /example1:tryEcho /soapenv:Body /soapenv:Envelope0 Here is my soap response : HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Content-Type: text/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Tue, 27 Mar 2007 12:48:28 GMT Connection: close 3cc ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header wsa:Tohttp://www.w3.org/2005/08/addressing/anonymous/wsa:To wsa:ReplyTo wsa:Addresshttp://www.w3.org/2005/08/addressing/none/wsa:Address /wsa:ReplyTo wsa:MessageIDurn:uuid:AF393873831A7C3EF31174999708410/wsa:MessageID wsa:Actionhttp://www.w3.org/2005/08/addressing/fault/wsa:Action wsa:RelatesTo wsa:RelationshipType=http://www.w3.org/2005/08/addressing/reply;urn:uuid:9B8FDACFBCA1263A121174999707376/wsa:RelatesTo wsa:FaultDetail wsa:ProblemHeaderQNamewsa:Action/wsa:ProblemHeaderQName /wsa:FaultDetail /soapenv:Header soapenv:Body soapenv:Fault faultcodewsa:MessageAddressingHeaderRequired/faultcode faultstringA required header representing a Message Addressing Property is not present/faultstring detail / /soapenv:Fault /soapenv:Body /soapenv:Envelope0 I have engaged the addressing module on the server side. Kindly help. Regards, Sagar M. Yerunkar Thilina Gunarathne [EMAIL PROTECTED] 03/25/2007 10:13 AM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: [AXIS2] - Engaging addressing module on client How do i specify a .mar file in the classpath? Eclipse allows me to add no
Re: Axis2 JMS samples?
Still.. you haven't confirmed this from my previous email:
I assume you are running a standalone client against your JMS web
service echo. However it seems like your echo service is not correctly
deployed for JMS.
Can you confirm that the JMS transport has started in your Axis2
deployment on Tomcat? You should see an "[INFO] JMS Transport Receiver
(Listener) initialized..." if it has.
Your JMS transport doesn't seem like it started properly.. do you see
the above log message on your Axis2 when it starts?
asankha
lee hanu wrote:
I am now trying to get this thing to work against the Axis2 standalone
server. I am still getting the same exception. I am still using Axis2 1.1.1.
So I turned the debug on using LOG4J and this part of the logging messages.
Hope this helps to figure out my problem. My guess is that my client program
is able to establish a connection to ActiveMQ but it is not getting any
response. Also I attached the Simple Client I am using to test the JMS
stuff.
Thanks
[DEBUG] 55:22 (JMSSender.java:invoke:49)JMSSender invoke()
[ WARN] 55:22 (JMSOutTransportInfo.java:getDestination:108)Cannot get or
lookup JMS destination : echo from url :
jms:/echo?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryjava.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactoryjava.naming.provider.url=""
: echo
[DEBUG] 55:23 (WireFormatNegotiator.java:start:71)Sending: WireFormatInfo {
version=2, properties={TightEncodingEnabled=true, CacheSize=1024,
TcpNoDelayEnabled=true, SizePrefixDisabled=false, StackTraceEnabled=true,
MaxInactivityDuration=3, CacheEnabled=true}, magic=[A,c,t,i,v,e,M,Q]}
[DEBUG] 55:23 (WireFormatNegotiator.java:onCommand:102)Received WireFormat:
WireFormatInfo { version=2, properties={TightEncodingEnabled=true,
CacheSize=1024, TcpNoDelayEnabled=true, SizePrefixDisabled=false,
StackTraceEnabled=true, MaxInactivityDuration=3, CacheEnabled=true},
magic=[A,c,t,i,v,e,M,Q]}
[DEBUG] 55:23
(WireFormatNegotiator.java:onCommand:109)tcp://localhost/127.0.0.1:61616
before negotiation: OpenWireFormat{version=2, cacheEnabled=false,
stackTraceEnabled=false, tightEncodingEnabled=false,
sizePrefixDisabled=false}
[DEBUG] 55:23
(WireFormatNegotiator.java:onCommand:120)tcp://localhost/127.0.0.1:61616
after negotiation: OpenWireFormat{version=2, cacheEnabled=true,
stackTraceEnabled=true, tightEncodingEnabled=true, sizePrefixDisabled=false}
[DEBUG] 55:24 (StAXUtils.java:createXMLStreamWriter:205)XMLStreamWriter is
com.ctc.wstx.sw.SimpleNsStreamWriter
[DEBUG] 55:24 (JMSSender.java:invoke:126)[Client]Sending message to
destination : queue://echo
[DEBUG] 55:24 (ActiveMQSession.java:send:1542)Sending message:
ActiveMQTextMessage {commandId = 0, responseRequired = false, messageId =
ID:UNIVERSI-D25BF5-3730-1175007323030-1:0:1:1:1, originalDestination = null,
originalTransactionId = null, producerId =
ID:UNIVERSI-D25BF5-3730-1175007323030-1:0:1:1, destination = queue://echo,
transactionId = null, expiration = 0, timestamp = 1175007324093, arrival =
0, correlationId = null, replyTo =
temp-queue://ID:UNIVERSI-D25BF5-3730-1175007323030-1:0:1, persistent = true,
type = null, priority = 4, groupID = null, groupSequence = 0,
targetConsumerId = null, compressed = false, userID = null, content = null,
marshalledProperties = null, dataStructure = null, redeliveryCounter = 0,
size = 0, properties = null, readOnlyProperties = true, readOnlyBody = true,
droppable = false, text = ?xml version='1.0'
encoding='utf-8'?soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"soapenv:Header
/soapenv:BodyechoString:echoString xmlns:echoString="
http://echo/jms/samples/axis2/apache/org"echoString:TextIsaac Asimov, The
Foundation
Trilogy/echoString:Text/echoString:echoString/soapenv:Body/soapenv:Envelope}
[DEBUG] 55:24 (JMSSender.java:invoke:147)Waiting for a maximum of 3ms
for a response message to destination :
temp-queue://ID:UNIVERSI-D25BF5-3730-1175007323030-1:0:1
asankha wrote:
Yes, I think there was some confusion as to which build the patch for
the particular JIRA went in.. so could you try with the 1.2 RC1 or the
latest nighly build and let me know? The information in the general JMS
transport configuration should suffice for you to get it started
asankha
lee hanu wrote:
Thanks Asanka,
I don't see the INFO message for tomcat.
I am using Tomcat 5.5(not the axis2 standalone). I am doing this against
axis2 1.1.1. Do I have to use the latest nightlies for this to work? Can I
use Axis2 1.2 RC1?
Thanks
asankha wrote:
I assume you are running a standalone client against your JMS web
service echo. However it seems like your echo service is not correctly
deployed for JMS.
Can you confirm that the JMS transport has started in your Axis2
deployment on Tomcat? You should see an "[INFO] JMS Transport Receiver
(Listener) initialized..." if it has. If you do not see this message,
please read
Re: Problem deploying example app on Weblogic 8.1, works on tomcat 5.5.20 though...
Is this somehow related to resolved issue AXIS2-577 ( http://issues.apache.org/jira/browse/AXIS2-577)? Josh On 3/27/07, Josh [EMAIL PROTECTED] wrote: All, I read through the Article How to Embed an Axis2 based Web Service in you Webapp? (http://wso2.org/library/90) and downloaded the sample code. When I deploy this sample code on Tomcat 5.5.20, it works fine. If I visit http://localhost:8080/axis2/services/BookService?wsdl, I am presented with the WSDL for the service mentioned in the article. I deployed the same war file (I added a weblogic.xml file with the prefer-web-inf-classes option set to true) to weblogic 8.1 sp4. When I hit http://localhost:7001/axis2/services/BookService?wsdl , I receive the following error: Error HTTP BEA-101214 Included resource or file /axis2/axis2-web/listSingleService.jsp not found from requested resource /axis2/services/BookService. Why would axis be looking for this file when deploying on Weblogic and not Tomcat? Any ideas? Joshua
Re: Axis2 JMS samples?
Ok cool.. so now it seems like you are trying to reach a service
through the Queue 'echo' but I am not sure if a service is deployed
against that Queue. Could you share the services.xml of the 'echo'
service? I can see the 'Version', 'MyService' and 'WsaMappingTest'
starting up...
asankha
lee hanu wrote:
Yes it has started. I am now using the Axis2 standalone server and I am using
Axis2 1.1.1. The follwoing is the console display.
Mar 27, 2007 11:08:55 AM
org.apache.axis2.transport.http.server.DefaultConnectionListener run
INFO: Listening on port 8080
Mar 27, 2007 11:08:56 AM org.apache.axis2.transport.jms.JMSListener init
INFO: JMS Transport Receiver (Listener) initialized...
Mar 27, 2007 11:08:56 AM org.apache.axis2.transport.jms.JMSConnectionFactory
listen
INFO: Connection factory : myTopicConnectionFactory initialized...
Mar 27, 2007 11:08:56 AM org.apache.axis2.transport.jms.JMSConnectionFactory
listen
INFO: Connection factory : myQueueConnectionFactory initialized...
Mar 27, 2007 11:08:56 AM org.apache.axis2.transport.jms.JMSConnectionFactory
listenOnDestination
WARNING: Cannot find destination : Version Creating a Queue with this name
Mar 27, 2007 11:08:56 AM org.apache.axis2.transport.jms.JMSConnectionFactory
listenOnDestination
WARNING: Cannot find destination : WsaMappingTest Creating a Queue with this
name
Mar 27, 2007 11:08:56 AM org.apache.axis2.transport.jms.JMSConnectionFactory
listenOnDestination
WARNING: Cannot find destination : MyService Creating a Queue with this name
Mar 27, 2007 11:08:57 AM org.apache.axis2.transport.jms.JMSConnectionFactory
listen
INFO: Connection factory : default initialized...
Mar 27, 2007 11:08:57 AM org.apache.axis2.transport.SimpleAxis2Server main
INFO: [SimpleAxisServer] Started
asankha wrote:
Still.. you haven't confirmed this from my previous email:
I assume you are running a standalone client against your JMS web
gt; service echo. However it seems like your echo service is not
correctly
gt; deployed for JMS.
gt;
gt; Can you confirm that the JMS transport has started in your Axis2
gt; deployment on Tomcat? You should see an "[INFO] JMS Transport
Receiver
gt; (Listener) initialized..." if it has.
Your JMS transport doesn't seem like it started properly.. do you see
the above log message on your Axis2 when it starts?
asankha
lee hanu wrote:
I am now trying to get this thing to work against the Axis2 standalone
server. I am still getting the same exception. I am still using Axis2
1.1.1.
So I turned the debug on using LOG4J and this part of the logging
messages.
Hope this helps to figure out my problem. My guess is that my client
program
is able to establish a connection to ActiveMQ but it is not getting any
response. Also I attached the Simple Client I am using to test the JMS
stuff.
Thanks
[DEBUG] 55:22 (JMSSender.java:invoke:49)JMSSender invoke()
[ WARN] 55:22 (JMSOutTransportInfo.java:getDestination:108)Cannot get or
lookup JMS destination : echo from url :
jms:/echo?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryamp;java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactoryamp;java.naming.provider.url=""
: echo
[DEBUG] 55:23 (WireFormatNegotiator.java:start:71)Sending: WireFormatInfo
{
version=2, properties={TightEncodingEnabled=true, CacheSize=1024,
TcpNoDelayEnabled=true, SizePrefixDisabled=false, StackTraceEnabled=true,
MaxInactivityDuration=3, CacheEnabled=true}, magic=[A,c,t,i,v,e,M,Q]}
[DEBUG] 55:23 (WireFormatNegotiator.java:onCommand:102)Received
WireFormat:
WireFormatInfo { version=2, properties={TightEncodingEnabled=true,
CacheSize=1024, TcpNoDelayEnabled=true, SizePrefixDisabled=false,
StackTraceEnabled=true, MaxInactivityDuration=3, CacheEnabled=true},
magic=[A,c,t,i,v,e,M,Q]}
[DEBUG] 55:23
(WireFormatNegotiator.java:onCommand:109)tcp://localhost/127.0.0.1:61616
before negotiation: OpenWireFormat{version=2, cacheEnabled=false,
stackTraceEnabled=false, tightEncodingEnabled=false,
sizePrefixDisabled=false}
[DEBUG] 55:23
(WireFormatNegotiator.java:onCommand:120)tcp://localhost/127.0.0.1:61616
after negotiation: OpenWireFormat{version=2, cacheEnabled=true,
stackTraceEnabled=true, tightEncodingEnabled=true,
sizePrefixDisabled=false}
[DEBUG] 55:24 (StAXUtils.java:createXMLStreamWriter:205)XMLStreamWriter is
com.ctc.wstx.sw.SimpleNsStreamWriter
[DEBUG] 55:24 (JMSSender.java:invoke:126)[Client]Sending message to
destination : queue://echo
[DEBUG] 55:24 (ActiveMQSession.java:send:1542)Sending message:
ActiveMQTextMessage {commandId = 0, responseRequired = false, messageId =
ID:UNIVERSI-D25BF5-3730-1175007323030-1:0:1:1:1, originalDestination =
null,
originalTransactionId = null, producerId =
ID:UNIVERSI-D25BF5-3730-1175007323030-1:0:1:1, destination = queue://echo,
transactionId = null, expiration = 0, timestamp = 1175007324093, arrival =
0, correlationId = null, replyTo =
temp-queue://ID:UNIVERSI-D25BF5-3730-1175007323030-1:0:1, persistent =
true,
type =
Re: Axis2 JMS samples?
Asanka,
The follwoing is the service.xml for the Echo Webservice.
?xml version=1.0 encoding=UTF-8?
service name=echo
descriptionEcho Service/description
messageReceivers
messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-only;
class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver /
messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out;
class=org.apache.axis2.rpc.receivers.RPCMessageReceiver /
/messageReceivers
parameter name=ServiceClass
locked=trueorg.apache.axis2.samples.jms.echo.Echo/parameter
/service
Thanks for your patience and for all the help so far.
asankha wrote:
Ok cool.. so now it seems like you are trying to reach a service
through the Queue 'echo' but I am not sure if a service is deployed
against that Queue. Could you share the services.xml of the 'echo'
service? I can see the 'Version', 'MyService' and 'WsaMappingTest'
starting up...
asankha
lee hanu wrote:
Yes it has started. I am now using the Axis2 standalone server and I am
using
Axis2 1.1.1. The follwoing is the console display.
Mar 27, 2007 11:08:55 AM
org.apache.axis2.transport.http.server.DefaultConnectionListener run
INFO: Listening on port 8080
Mar 27, 2007 11:08:56 AM org.apache.axis2.transport.jms.JMSListener init
INFO: JMS Transport Receiver (Listener) initialized...
Mar 27, 2007 11:08:56 AM
org.apache.axis2.transport.jms.JMSConnectionFactory
listen
INFO: Connection factory : myTopicConnectionFactory initialized...
Mar 27, 2007 11:08:56 AM
org.apache.axis2.transport.jms.JMSConnectionFactory
listen
INFO: Connection factory : myQueueConnectionFactory initialized...
Mar 27, 2007 11:08:56 AM
org.apache.axis2.transport.jms.JMSConnectionFactory
listenOnDestination
WARNING: Cannot find destination : Version Creating a Queue with this name
Mar 27, 2007 11:08:56 AM
org.apache.axis2.transport.jms.JMSConnectionFactory
listenOnDestination
WARNING: Cannot find destination : WsaMappingTest Creating a Queue with
this
name
Mar 27, 2007 11:08:56 AM
org.apache.axis2.transport.jms.JMSConnectionFactory
listenOnDestination
WARNING: Cannot find destination : MyService Creating a Queue with this
name
Mar 27, 2007 11:08:57 AM
org.apache.axis2.transport.jms.JMSConnectionFactory
listen
INFO: Connection factory : default initialized...
Mar 27, 2007 11:08:57 AM org.apache.axis2.transport.SimpleAxis2Server main
INFO: [SimpleAxisServer] Started
asankha wrote:
Still.. you haven't confirmed this from my previous email:
I assume you are running a standalone client against your JMS web
amp;gt; service echo. However it seems like your echo service is not
correctly
amp;gt; deployed for JMS.
amp;gt;
amp;gt; Can you confirm that the JMS transport has started in your Axis2
amp;gt; deployment on Tomcat? You should see an [INFO] JMS Transport
Receiver
amp;gt; (Listener) initialized... if it has.
Your JMS transport doesn't seem like it started properly.. do you see
the above log message on your Axis2 when it starts?
asankha
lee hanu wrote:
I am now trying to get this thing to work against the Axis2 standalone
server. I am still getting the same exception. I am still using Axis2
1.1.1.
So I turned the debug on using LOG4J and this part of the logging
messages.
Hope this helps to figure out my problem. My guess is that my client
program
is able to establish a connection to ActiveMQ but it is not getting any
response. Also I attached the Simple Client I am using to test the JMS
stuff.
Thanks
[DEBUG] 55:22 (JMSSender.java:invoke:49)JMSSender invoke()
[ WARN] 55:22 (JMSOutTransportInfo.java:getDestination:108)Cannot get or
lookup JMS destination : echo from url :
jms:/echo?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryamp;amp;java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactoryamp;amp;java.naming.provider.url=tcp://localhost:61616
: echo
[DEBUG] 55:23 (WireFormatNegotiator.java:start:71)Sending: WireFormatInfo
{
version=2, properties={TightEncodingEnabled=true, CacheSize=1024,
TcpNoDelayEnabled=true, SizePrefixDisabled=false, StackTraceEnabled=true,
MaxInactivityDuration=3, CacheEnabled=true}, magic=[A,c,t,i,v,e,M,Q]}
[DEBUG] 55:23 (WireFormatNegotiator.java:onCommand:102)Received
WireFormat:
WireFormatInfo { version=2, properties={TightEncodingEnabled=true,
CacheSize=1024, TcpNoDelayEnabled=true, SizePrefixDisabled=false,
StackTraceEnabled=true, MaxInactivityDuration=3, CacheEnabled=true},
magic=[A,c,t,i,v,e,M,Q]}
[DEBUG] 55:23
(WireFormatNegotiator.java:onCommand:109)tcp://localhost/127.0.0.1:61616
before negotiation: OpenWireFormat{version=2, cacheEnabled=false,
stackTraceEnabled=false, tightEncodingEnabled=false,
sizePrefixDisabled=false}
[DEBUG] 55:23
Re: Axis2 JMS samples?
Also here is my Client http://www.nabble.com/file/7460/ClientOne.java ClientOne.java -- View this message in context: http://www.nabble.com/Axis2-JMS-samples--tf3449408.html#a9697757 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 JMS samples?
Yes it has started. I am now using the Axis2 standalone server and I am using
Axis2 1.1.1. The follwoing is the console display.
Mar 27, 2007 11:08:55 AM
org.apache.axis2.transport.http.server.DefaultConnectionListener run
INFO: Listening on port 8080
Mar 27, 2007 11:08:56 AM org.apache.axis2.transport.jms.JMSListener init
INFO: JMS Transport Receiver (Listener) initialized...
Mar 27, 2007 11:08:56 AM org.apache.axis2.transport.jms.JMSConnectionFactory
listen
INFO: Connection factory : myTopicConnectionFactory initialized...
Mar 27, 2007 11:08:56 AM org.apache.axis2.transport.jms.JMSConnectionFactory
listen
INFO: Connection factory : myQueueConnectionFactory initialized...
Mar 27, 2007 11:08:56 AM org.apache.axis2.transport.jms.JMSConnectionFactory
listenOnDestination
WARNING: Cannot find destination : Version Creating a Queue with this name
Mar 27, 2007 11:08:56 AM org.apache.axis2.transport.jms.JMSConnectionFactory
listenOnDestination
WARNING: Cannot find destination : WsaMappingTest Creating a Queue with this
name
Mar 27, 2007 11:08:56 AM org.apache.axis2.transport.jms.JMSConnectionFactory
listenOnDestination
WARNING: Cannot find destination : MyService Creating a Queue with this name
Mar 27, 2007 11:08:57 AM org.apache.axis2.transport.jms.JMSConnectionFactory
listen
INFO: Connection factory : default initialized...
Mar 27, 2007 11:08:57 AM org.apache.axis2.transport.SimpleAxis2Server main
INFO: [SimpleAxisServer] Started
asankha wrote:
Still.. you haven't confirmed this from my previous email:
I assume you are running a standalone client against your JMS web
gt; service echo. However it seems like your echo service is not
correctly
gt; deployed for JMS.
gt;
gt; Can you confirm that the JMS transport has started in your Axis2
gt; deployment on Tomcat? You should see an [INFO] JMS Transport
Receiver
gt; (Listener) initialized... if it has.
Your JMS transport doesn't seem like it started properly.. do you see
the above log message on your Axis2 when it starts?
asankha
lee hanu wrote:
I am now trying to get this thing to work against the Axis2 standalone
server. I am still getting the same exception. I am still using Axis2
1.1.1.
So I turned the debug on using LOG4J and this part of the logging
messages.
Hope this helps to figure out my problem. My guess is that my client
program
is able to establish a connection to ActiveMQ but it is not getting any
response. Also I attached the Simple Client I am using to test the JMS
stuff.
Thanks
[DEBUG] 55:22 (JMSSender.java:invoke:49)JMSSender invoke()
[ WARN] 55:22 (JMSOutTransportInfo.java:getDestination:108)Cannot get or
lookup JMS destination : echo from url :
jms:/echo?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryamp;java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactoryamp;java.naming.provider.url=tcp://localhost:61616
: echo
[DEBUG] 55:23 (WireFormatNegotiator.java:start:71)Sending: WireFormatInfo
{
version=2, properties={TightEncodingEnabled=true, CacheSize=1024,
TcpNoDelayEnabled=true, SizePrefixDisabled=false, StackTraceEnabled=true,
MaxInactivityDuration=3, CacheEnabled=true}, magic=[A,c,t,i,v,e,M,Q]}
[DEBUG] 55:23 (WireFormatNegotiator.java:onCommand:102)Received
WireFormat:
WireFormatInfo { version=2, properties={TightEncodingEnabled=true,
CacheSize=1024, TcpNoDelayEnabled=true, SizePrefixDisabled=false,
StackTraceEnabled=true, MaxInactivityDuration=3, CacheEnabled=true},
magic=[A,c,t,i,v,e,M,Q]}
[DEBUG] 55:23
(WireFormatNegotiator.java:onCommand:109)tcp://localhost/127.0.0.1:61616
before negotiation: OpenWireFormat{version=2, cacheEnabled=false,
stackTraceEnabled=false, tightEncodingEnabled=false,
sizePrefixDisabled=false}
[DEBUG] 55:23
(WireFormatNegotiator.java:onCommand:120)tcp://localhost/127.0.0.1:61616
after negotiation: OpenWireFormat{version=2, cacheEnabled=true,
stackTraceEnabled=true, tightEncodingEnabled=true,
sizePrefixDisabled=false}
[DEBUG] 55:24 (StAXUtils.java:createXMLStreamWriter:205)XMLStreamWriter is
com.ctc.wstx.sw.SimpleNsStreamWriter
[DEBUG] 55:24 (JMSSender.java:invoke:126)[Client]Sending message to
destination : queue://echo
[DEBUG] 55:24 (ActiveMQSession.java:send:1542)Sending message:
ActiveMQTextMessage {commandId = 0, responseRequired = false, messageId =
ID:UNIVERSI-D25BF5-3730-1175007323030-1:0:1:1:1, originalDestination =
null,
originalTransactionId = null, producerId =
ID:UNIVERSI-D25BF5-3730-1175007323030-1:0:1:1, destination = queue://echo,
transactionId = null, expiration = 0, timestamp = 1175007324093, arrival =
0, correlationId = null, replyTo =
temp-queue://ID:UNIVERSI-D25BF5-3730-1175007323030-1:0:1, persistent =
true,
type = null, priority = 4, groupID = null, groupSequence = 0,
targetConsumerId = null, compressed = false, userID = null, content =
null,
marshalledProperties = null, dataStructure = null, redeliveryCounter = 0,
size = 0,
Question on passing configurariont parameter to a web service
Hi, What's the best way to pass a configuration parameter to web service? I'm interesting in specifying the name of directory. thanks, Mark No need to miss a message. Get email on-the-go with Yahoo! Mail for Mobile. Get started. http://mobile.yahoo.com/mail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: stand-alone SOAP server with Axis
Hakan, (Assuming you are talking about Axis2...) Embedding an HTTP Server like Jetty (http://www.ebmwebsourcing.net/blog/page/christophehamerling/20070307?catname =%2FPEtALS) might be a better solution in terms of scalability. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Sunday, March 25, 2007 10:24 PM To: axis-user@ws.apache.org Subject: Re: stand-alone SOAP server with Axis Hi Martin, Thank you for the information. I guess I forgot to metioned that I might have to use Java. Is there still chance to use simple_axis_server ? Regards Hakan Martin Gainty [EMAIL PROTECTED] 26/03/2007 10:46 AM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: stand-alone SOAP server with Axis http://ws.apache.org/axis/cpp/index.html http://ws.apache.org/axis/cpp/index.html Bon Chance! Martin-- --- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. --- Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire. - Original Message - From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Sunday, March 25, 2007 8:38 PM Subject: stand-alone SOAP server with Axis Hi, Are there any documentation on how to build a standan-alone SOAP server without using Tomcat or JBOSS. Thanks Hakan This email may contain privileged/confidential information. You may not copy or disclose this email to anyone without the written permission of the sender. If you have received this email in error please kindly delete this message and notify the sender. Opinions expressed in this email are those of the sender and not necessarily the opinions of the employer. This email and any attached files should be scanned to detect viruses. No liability will be accepted by the employer for loss or damage (whether caused by negligence or not) as a result of email transmission. This email may contain privileged/confidential information. You may not copy or disclose this email to anyone without the written permission of the sender. If you have received this email in error please kindly delete this message and notify the sender. Opinions expressed in this email are those of the sender and not necessarily the opinions of the employer. This email and any attached files should be scanned to detect viruses. No liability will be accepted by the employer for loss or damage (whether caused by negligence or not) as a result of email transmission.
Re: JIBX Mapping Question - Void response message?
Yes, the class has to exist (though it can be just an empty public
class UpdateResponse {} - where I capitalized according to Java naming
conventions, which means that class=updateResponse I used in the last
email should really be class=UpdateResponse). Wrapped requires a
separate class for each operation's input and output.
- Dennis
Josh wrote:
Dennis,
To be clear, does this marker class need to physically exist?
Josh
On 3/26/07, *Dennis Sosnoski* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi Josh,
If you're using unwrapped you shouldn't need to map this at all. If
you're using wrapped handling you'd just have a marker class
with an
empty mapping:
mapping class=updateResponse name=updateResponse/
You can see an example of the unwrapped handling for this at
http://www.sosnoski.com/jibx-wiki/space/axis2-jibx/example (with the
WSDL and code at
http://www.sosnoski.com/jibx-wiki/space/axis2-jibx/example/library-service
http://www.sosnoski.com/jibx-wiki/space/axis2-jibx/example/library-service).
- Dennis
Dennis M. Sosnoski
SOA and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
Josh wrote:
All,
I am having difficulting dealing with an existing WSDL which
declares
a void response message. I have the following in my wsdl:
element name=updateResponse
complexType/
/element
wsdl:message name=updateResponse
wsdl:part element=impl:updateResponse name=parameters/
/wsdl:message
Because this is really a void return, how would I map this using
JiBX?
Regards,
Joshua
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[AXIS2] MTOM problems
I have some MTOM sample code in which a client sends all files in its transfer directory to a service. The server sends the files back to the client, which stores them in its received directory, and does a byte-to-byte compare to make sure the files in the two directories match. 1. Sometimes 1 extra byte is received. This is a 255 (0xff). 2. When I set the client option CACHE_ATTACHMENTS to true, a client-side thread loops, appending bytes of 0xff to a .ATT file in the attachments directory. The problems occur in both 1.1.1 and in 1.2 RC1. My guess is both problems might have the same cause: an incorrect cast of an int to a byte, and then testing for -1 (eof); bytes have value 0 to 255, not -1. Are these known problems? Thanks, Betsy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2] MTOM problems
Hi, 1. Sometimes 1 extra byte is received. This is a 255 (0xff). It would be great if you can isolate the failing scenario and log a Jira with a test case.. 2. When I set the client option CACHE_ATTACHMENTS to true, a client-side thread loops, appending bytes of 0xff to a .ATT file in the attachments directory. I did some fixes to the Attachment caching after the 1.1 release.. They are available in the latest svn head of Axiom.. And should be available with the Axis2-1.2-RC1.. Can you please retest the 2 with Axis2-1.2-RC1.. Make sure to replace each and every jar with the once that came with 1.2-rc1, specially the Axiom jars.. -- Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
version 1.2 missing?
Is there any where I can download Axis Final Version 1.2? I've tried a bunch of mirrors on this page: http://www.apache.org/dyn/closer.cgi/ws/axis/1_2/ but they all return not found. -- Jared Nedzel Cancer Genomics Informatics Broad Institute 7 Cambridge Center Cambridge, MA 02142 617-324-4825 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis2 not putting binary attachment on the wire
My webservice returns a binary document which I declare in my wsdl as base64Binary. Using SOAPMonitor I see my document in the returned soap message. However, tcpmon shows that the document is empty. I have tried this both with and without MTOM. Without MTOM here is the soap from SOAPMonitor... ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/ soapenv:Header / soapenv:Body ns1:getDocumentResponse xmlns:ns1=urn:webservices.docharbor.com ns1:return ns1:documentSize198/ns1:documentSize ns1:documente1xydGYxXGFuc2lcYW5zaWNwZzEyNTJcZGVmZjBcZGVmbGFuZzEwMzN7XG ZvbnR0Ymx7XGYwXGZzd2lzc1xmY2hhcnNldDAgQXJpYWw7fX0NCntcKlxnZW5lcmF0b3IgTX NmdGVkaXQgNS40MS4xNS4xNTA3O31cdmlld2tpbmQ0XHVjMVxwYXJkXGYwXGZzMjAgSSdtIH RoZSBkZWZhdWx0IGRvY3VtZW50IGZvciBpbXBvcnRhdGlvbi5ccGFyDQp9DQoA/ns1:docu ment /ns1:return /ns1:getDocumentResponse /soapenv:Body /soapenv:Envelope ... and here is the output of tcpmon HTTP/1.1 200 OK Server: Date: Tue, 27 Mar 2007 18:26:12 GMT Content-type: text/xml; charset=UTF-8 Transfer-encoding: chunked 016f ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/ soapenv:Header / soapenv:Body ns1:getDocumentResponse xmlns:ns1=urn:webservices.docharbor.com ns1:return ns1:documentSize198/ns1:documentSize ns1:document/ns1:document notice the empty document /ns1:return /ns1:getDocumentResponse /soapenv:Body /soapenv:Envelope 0 Does anyone know why this is happening? Thanks, Valerie
Re: [Axis2] AXIOM or JBIX
Hi Nilesh, Thanks for detailed response. So, the AddressBookService example (at http://people.apache.org/~thilina/axis2/docs/jibx/jibx-unwrapped-example.html) which uses POJO as a data transfer object, can be implemented using any Data binding framework (JIBX or ADB) to create Java classes. What is JiBX binding definition, is this property only applicable to JiBX framework -EbindingFile /resources/jibxbindingFile.xml And also, can we send the client request using SOAP (instead of writing Java Client) and get the response back in SOAP? In which case, this type of scenario comes in. Thanks, Anil Nilesh Ghorpade wrote: Hi Anil, The Data binding frameworks come into picture when you are generating the Java code artifacts from WSDL. If you observe the wsdl2java command there is a command line argument namely -d with which you can specify the Data binding framework which you want to use. In case u want to use JiBX you would be specifying something like $ wsdl2java -o /outputDir -d jibx -EbindingFile /resources/jibxbindingFile.xml -uri MyWebService.wsdl The above command is just for making things more simpler. Also if there are no schema references in the WSDL or if the WSDL is not having any schema types then the Data binding framework would not be coming into picture. (Others Please correct me if I am wrong.) You would just be deciding which Data binding framework you should be using. AXIS 2 would internally be using the same and generating the Java classes for you. Do not get confused by the approach which you are choosing to build the web service and the data binding framework. The data binding framework is just to map the schema which is defined in the WSDL to Java classes. Thats the only purpose of the data binding framework. Using POJO's for web services means you would be writing a POJO class which would be capturing all the information you need for invoking the particular web service operation. For example if you see the AddressBookService in the AXIS 2 samples you can see that the addEntry method takes in a POJO as its input parameter namely Entry. Regarding your second question I am not able to understand it correctly. Also the flow which you have mentioned from the Client to the Service is correct and it would remain the same for any Web service for that matter i.e. not only AXIS 2 but any web service which is developed using any other framework. Hope that answers your queries. Regards Nilesh - Original Message From: Anil VVNN [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Monday, March 26, 2007 7:56:35 PM Subject: Re: [Axis2] AXIOM or JBIX Hi Niles, Thanks for answering my questions. As I said I'm a beginner, I have few more questions related to previous one. (1) When exactly do we use Binding frameworks (JIBX, ADB or XMLBeans) ? For instance, the examples given in Axis2 website (i.e. StockQuoteService) referring to simple method call, client calling WS for getPrice/update operations but there's no XSD involved, I think this kind of operations can be easily accomplished using POJO option. But I'm confused when to use POJO or anyother Binding framework(JIBX). (2) What is the difference between XML Processing Model and SOAP Processing Model, when do we use these models independently. To my understanding, this is the typical flow of Axis2 services, Client calls--- Stub (generated by wsdl2java) calls[SOAP request]--- Skeleton Interface (generated by wsdl2java) --Business Logic And this SOAP request can be handled using any transport (eg. TCP, JMS etc.) Please correct me if I'm wrong. Thanks. - Anil Nilesh Ghorpade wrote: Hi, As per my understanding AXIS 2 uses AXIOM API's internally for any XML related activities. Hence as you have mentioned that you are confused to choose between POJO, AXIOM, JIBX, ADB or XMLBeans, the AXIOM is an invalid option here. Secondly in AXIS 2 you can create web services using either the Spring Framework or POJO. JiBX, XMLBeans and ADB are more related to the data binding frameworks which AXIS 2 supports. Hence it depends on your schema on which data binding framework you would want to select. As per my knowledge XMLBeans is the best when it comes to complex schemas. This is because XMLBeans implementation can understand all the XSD (i.e. schema) constructs. To answer your second question, the answer is YES. If you want to use the wsdl2java command from AXIS2 for generating your stubs and skeletons you will need the WSDL. Generating a WSDL is also not a diccficult task. YOu can have your SEI defined i.e. the Service Endpoint Interface with all the method signatures which you want to expose as web service operations. On executing the java2wsdl command from AXIS2 you would be able to get the WSDL. And using this WSDL you can generate the remaining artifacts of your web service. WSDL is nothing but
Re: [Axis2] Support of ws-policy?
Sanka:
I've been trying to do this exact thing and when notifiing wsdl2java about
the repository (axis2, it has rampart mar in it) it tells me policy will
not be supported.
Any ideas why?
WSDL2Java (using axis2.sh) cmd:
sh ${AXIS2_HOME}/bin/axis2.sh \
org.apache.axis2.wsdl.WSDL2Java \
-uri wsdl url \
-d xmlbeans -s -r $AXIS2_HOME/repository
I get:
...
Mar 27, 2007 4:48:06 PM org.apache.axis2.deployment.DeploymentEngine
doDeploy
INFO: Deploying Web service version.aar
cannot create repository : policy will not be supported
cannot find a PolicyExtension to process
http://schemas.xmlsoap.org/ws/2005/07/securitypolicytype assertions
cannot find a PolicyExtension to process
http://schemas.xmlsoap.org/ws/2005/07/securitypolicytype assertions
Mar 27, 2007 4:48:07 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter
createOutFile
INFO: File ./src/com/nortel/va/beta/ClaimProcessorStub.java will not be
overwritten.
Sanka Samaranayke wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Carsten,
Right now we do have we a limited support for WSSecurity Policies in
Axis2. For instance If you attach a policy with a Username token
assertion then the wsdl2java will generate a stub with two utility
methods to set username and the password.
e.g.
wsp:Policy
xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy;
xmlns:wsp=http://schemas.xmlsoap.org/ws/2004/09/policy;
sp:SignedSupportingTokens
wsp:Policy
sp:UsernameToken
sp:IncludeToken=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient;
/
/wsp:Policy
/sp:SignedSupportingTokens
/wsp:Policy
You need to specify an axis2 repository with rampart module in it both
at codegen time and runtime. At the codegen time you could specify
the repository as the following codegen option.
-r path to the repostiory.
And when you creating the stub instance you need to pass a
ConfigurationContext created using that repository. If do those two
steps if will get a stub that has the above methods. Plus at the
runtime the stub will automatically engage the security module and do
whatever necessary.
e.g.
Stub stub = new Stub(.);
..
stub.setUsername(...);
stub.setPassword(...);
stub.sendAndReceive(..);
At the moment we are adding a new codebase to Apache Neethi project
which is based on a much improved architecture. And based on that new
implementation we will improve the support for WS Policy plus its
extensions for Security, Reliable Messaging .. etc pretty soon.
Keep in touch ..
- --Sanka
Carsten Ziegeler wrote:
Can someone please give me a hint on how to turn on ws policy validation
with Axis2? I already installed the rampart module.
Will the wsdl2java code generator generate the necessary bit?
Thanks
Carsten
- --
Sanka Samaranayake
WSO2 Inc.
http://sankas.blogspot.com/ - http://www.wso2.net/
T:+94-77-3506382 F:+94-11-2424304
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (GNU/Linux)
iD8DBQFEtQfV/Hd0ETKdgNIRAoqbAJ9AQA9Tr0DFMBHyOtFXnBRwRejhrACglquN
gZNZLtiVjSGnSxW8Dd3dccI=
=vkyN
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/-Axis2--Support-of-ws-policy--tf1930928.html#a9701947
Sent from the Axis - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 not putting binary attachment on the wire
Opps... Sounds like a bug to me.. Please log a JIRA with more details.. Some source code would be actually better... Then in order to get through this you can try enablingMTOM in your Axis2.xml.. Thanks, Thilina On 3/28/07, Masin, Valerie [EMAIL PROTECTED] wrote: My webservice returns a binary document which I declare in my wsdl as base64Binary. Using SOAPMonitor I see my document in the returned soap message. However, tcpmon shows that the document is empty. I have tried this both with and without MTOM. Without MTOM here is the soap from SOAPMonitor... ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header / soapenv:Body ns1:getDocumentResponse xmlns:ns1=urn:webservices.docharbor.com ns1:return ns1:documentSize198/ns1:documentSize ns1:documente1xydGYxXGFuc2lcYW5zaWNwZzEyNTJcZGVmZjBcZGVmbGFuZzEwMzN7XGZvbnR0Ymx7XGYwXGZzd2lzc1xmY2hhcnNldDAgQXJpYWw7fX0NCntcKlxnZW5lcmF0b3IgTXNmdGVkaXQgNS40MS4xNS4xNTA3O31cdmlld2tpbmQ0XHVjMVxwYXJkXGYwXGZzMjAgSSdtIHRoZSBkZWZhdWx0IGRvY3VtZW50IGZvciBpbXBvcnRhdGlvbi5ccGFyDQp9DQoA/ns1:document /ns1:return /ns1:getDocumentResponse /soapenv:Body /soapenv:Envelope ... and here is the output of tcpmon HTTP/1.1 200 OK Server: Date: Tue, 27 Mar 2007 18:26:12 GMT Content-type: text/xml; charset=UTF-8 Transfer-encoding: chunked 016f ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header / soapenv:Body ns1:getDocumentResponse xmlns:ns1=urn:webservices.docharbor.com ns1:return ns1:documentSize198/ns1:documentSize ns1:document/ns1:document notice the empty document /ns1:return /ns1:getDocumentResponse /soapenv:Body /soapenv:Envelope 0 Does anyone know why this is happening? Thanks, Valerie -- Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: stand-alone SOAP server with Axis
Thank you very much Brennan. It is really critiical information for me. Regards Hakan Spies, Brennan [EMAIL PROTECTED] 28/03/2007 02:41 AM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject RE: stand-alone SOAP server with Axis Hakan, (Assuming you are talking about Axis2…) Embedding an HTTP Server like Jetty ( http://www.ebmwebsourcing.net/blog/page/christophehamerling/20070307?catname=%2FPEtALS ) might be a better solution in terms of scalability. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Sunday, March 25, 2007 10:24 PM To: axis-user@ws.apache.org Subject: Re: stand-alone SOAP server with Axis Hi Martin, Thank you for the information. I guess I forgot to metioned that I might have to use Java. Is there still chance to use simple_axis_server ? Regards Hakan Martin Gainty [EMAIL PROTECTED] 26/03/2007 10:46 AM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: stand-alone SOAP server with Axis http://ws.apache.org/axis/cpp/index.html Bon Chance! Martin-- --- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. --- Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire. - Original Message - From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Sunday, March 25, 2007 8:38 PM Subject: stand-alone SOAP server with Axis Hi, Are there any documentation on how to build a standan-alone SOAP server without using Tomcat or JBOSS. Thanks Hakan This email may contain privileged/confidential information. You may not copy or disclose this email to anyone without the written permission of the sender. If you have received this email in error please kindly delete this message and notify the sender. Opinions expressed in this email are those of the sender and not necessarily the opinions of the employer. This email and any attached files should be scanned to detect viruses. No liability will be accepted by the employer for loss or damage (whether caused by negligence or not) as a result of email transmission. This email may contain privileged/confidential information. You may not copy or disclose this email to anyone without the written permission of the sender. If you have received this email in error please kindly delete this message and notify the sender. Opinions expressed in this email are those of the sender and not necessarily the opinions of the employer. This email and any attached files should be scanned to detect viruses. No liability will be accepted by the employer for loss or damage (whether caused by negligence or not) as a result of email transmission. This email may contain privileged/confidential information. You may not copy or disclose this email to anyone without the written permission of the sender. If you have received this email in error please kindly delete this message and notify the sender. Opinions expressed in this email are those of the sender and not necessarily the opinions of the employer. This email and any attached files should be scanned to detect viruses. No liability will be accepted by the employer for loss or damage (whether caused by negligence or not) as a result of email transmission.
RE: Axis2 not putting binary attachment on the wire
I did try it with MTOM enabled too and got the same (equivalent) result... an empty document (see below). Not sure what other workarounds are available to me. Thanks From SOAPMonitor... ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header / soapenv:Body ns1:getDocumentResponse xmlns:ns1=urn:webservices.docharbor.com ns1:return ns1:documentSize198/ns1:documentSize ns1:documente1xydGYxXGFuc2lcYW5zaWNwZzEyNTJcZGVmZjBcZGVmbGFuZzEwMzN7XG ZvbnR0Ymx7XGYwXGZzd2lzc1xmY2hhcnNldDAgQXJpYWw7fX0NCntcKlxnZW5lcmF0b3IgTX NmdGVkaXQgNS40MS4xNS4xNTA3O31cdmlld2tpbmQ0XHVjMVxwYXJkXGYwXGZzMjAgSSdtIH RoZSBkZWZhdWx0IGRvY3VtZW50IGZvciBpbXBvcnRhdGlvbi5ccGFyDQp9DQoA/ns1:docu ment /ns1:return /ns1:getDocumentResponse /soapenv:Body /soapenv:Envelope From tcpmon HTTP/1.1 200 OK Server: Date: Tue, 27 Mar 2007 13:30:16 GMT Content-type: multipart/related; boundary=MIMEBoundaryurn_uuid_E612E8E634E97EAEE61175002216495; type=application/xop+xml; start=0.urn:uuid:[EMAIL PROTECTED]; start-info=text/xml; charset=UTF-8Transfer-encoding: chunked02d7--MIMEBoundaryurn_uuid_E612E8E634E97EAEE61175002216495content -type: application/xop+xml; charset=UTF-8; type=text/xml;content-transfer-encoding: binarycontent-id: 0.urn:uuid:[EMAIL PROTECTED] ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header / soapenv:Body ns1:getDocumentResponse xmlns:ns1=urn:webservices.docharbor.com ns1:return ns1:documentSize198/ns1:documentSize ns1:document xop:Include href=cid:1.urn:uuid:[EMAIL PROTECTED] xmlns:xop=http://www.w3.org/2004/08/xop/include; / /ns1:document /ns1:return /ns1:getDocumentResponse /soapenv:Body /soapenv:Envelope 00cc --MIMEBoundaryurn_uuid_E612E8E634E97EAEE61175002216495 content-type: application/octet-stream content-transfer-encoding: binary content-id: 1.urn:uuid:[EMAIL PROTECTED]0 -Original Message- From: Thilina Gunarathne [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 27, 2007 5:54 PM To: axis-user@ws.apache.org Subject: Re: Axis2 not putting binary attachment on the wire Opps... Sounds like a bug to me.. Please log a JIRA with more details.. Some source code would be actually better... Then in order to get through this you can try enablingMTOM in your Axis2.xml.. Thanks, Thilina On 3/28/07, Masin, Valerie [EMAIL PROTECTED] wrote: My webservice returns a binary document which I declare in my wsdl as base64Binary. Using SOAPMonitor I see my document in the returned soap message. However, tcpmon shows that the document is empty. I have tried this both with and without MTOM. Without MTOM here is the soap from SOAPMonitor... ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header / soapenv:Body ns1:getDocumentResponse xmlns:ns1=urn:webservices.docharbor.com ns1:return ns1:documentSize198/ns1:documentSize ns1:documente1xydGYxXGFuc2lcYW5zaWNwZzEyNTJcZGVmZjBcZGVmbGFuZzEwMzN7XG ZvbnR0Ymx7XGYwXGZzd2lzc1xmY2hhcnNldDAgQXJpYWw7fX0NCntcKlxnZW5lcmF0b3IgTX NmdGVkaXQgNS40MS4xNS4xNTA3O31cdmlld2tpbmQ0XHVjMVxwYXJkXGYwXGZzMjAgSSdtIH RoZSBkZWZhdWx0IGRvY3VtZW50IGZvciBpbXBvcnRhdGlvbi5ccGFyDQp9DQoA/ns1:docu ment /ns1:return /ns1:getDocumentResponse /soapenv:Body /soapenv:Envelope ... and here is the output of tcpmon HTTP/1.1 200 OK Server: Date: Tue, 27 Mar 2007 18:26:12 GMT Content-type: text/xml; charset=UTF-8 Transfer-encoding: chunked 016f ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header / soapenv:Body ns1:getDocumentResponse xmlns:ns1=urn:webservices.docharbor.com ns1:return ns1:documentSize198/ns1:documentSize ns1:document/ns1:document notice the empty document /ns1:return /ns1:getDocumentResponse /soapenv:Body /soapenv:Envelope 0 Does anyone know why this is happening? Thanks, Valerie -- Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 with Spring
Where should the aar file be placed. I am using Jetty server from eclipse to test. After the server startup, while checking for services, I get the exception: I can not find a service for this request to be serviced. Check the WSDL and the request URI. Thanks robert lazarski [EMAIL PROTECTED] wrote: http://ws.apache.org/axis2/1_1_1/spring.html#24 points to the without a servlet context section , yet you have a web.xml and are loading spring there. That's fine, but you need to have an AAR file with just the services.xml file in it. Try http://ws.apache.org/axis2/1_1_1/spring.html#23 and see how that goes. As shown further down in the same docs, the structure of your AAR in this case will be like: ./springExample.aar ./META-INF ./META-INF/MANIFEST.MF ./META-INF/services.xml Further hint: look at the Axis2 Web Application Home Page section in this link where you can see a list of your services: http://ws.apache.org/axis2/1_1_1/installationguide.html HTH, Robert On 3/27/07, Rosan Roche wrote: I am trying to integrate the existing Spring application I have with axis2. I am following the example from http://ws.apache.org/axis2/1_1_1/spring.html#24. I have added the Axis servlet to my web.xml file along with the existing servlet that is being used by the main application. When I try to access the service at http://localhost:8080/mm/services/SpringAwareService, I get an exception: org.apache.axis2.AxisFault: I can not find a service for this request to be serviced. Check the WSDL and the request URI How does the services.xml get loaded? Should it be explicitly loaded while startup? Should I create a WSDL? web.xml PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN http://java.sun.com/dtd/web-app_2_3.dtd; Media Management contextConfigLocation classpath:applicationContext.xml configuration deployment development -- org.springframework.web.context.ContextLoaderListener mm wicket.protocol.http.WicketServlet applicationFactoryClassName wicket.spring.SpringWebApplicationFactory 1 axis org.apache.axis2.transport.http.AxisServlet 5 axis /services/* Thanks Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list.
Re: version 1.2 missing?
http://archive.apache.org/ On 3/27/07, jnedzel [EMAIL PROTECTED] wrote: Is there any where I can download Axis Final Version 1.2? I've tried a bunch of mirrors on this page: http://www.apache.org/dyn/closer.cgi/ws/axis/1_2/ but they all return not found. -- Jared Nedzel Cancer Genomics Informatics Broad Institute 7 Cambridge Center Cambridge, MA 02142 617-324-4825 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Axis2 Client Stub not Generating WS-Security Headers
I'm thinking this is due to not using the -r in my WSDL2JAVA command to include my client repository? I added this and now I am getting the following: java.lang.IllegalStateException: No valid ObjectCreator found. Threads I have come across indicate that this error is caused by an incorrect version of the STAX jar, but it is the one that came with Axis2 1.1.1. My classpath does not include any jars that are not part of the Axis2 1.1.1 distribution. Any ideas? Thanks, Ted From: Ted Jones [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 27, 2007 3:04 PM To: axis-user@ws.apache.org Subject: Axis2 Client Stub not Generating WS-Security Headers I have an Axis2 1.1.1 ADB generated client stub that is instantiated using a client axis2.xml config and pointing to a client repository that has the rampart and addressing mar files. The config file and repository location are loaded via URL. In debug, I can see the rampart and addressing modules are engaged. In my client code, I have added the following properties to the serviceclient's options instance: options.setProperty(WSConstants.WSSE_NS , WSConstants.USERNAME_TOKEN_LN); options.setProperty(WSConstants.USERNAME_LN,getConnectionProperties().ge tUserid()); options.setProperty(WSConstants.PASSWORD_LN,getConnectionProperties().ge tPassword()); options.setProperty(WSConstants.PASSWORD_TYPE_ATTR, WSConstants.PASSWORD_TEXT); The WS-Security headers are never inserted into the soap request and I receive the ever-popular org.apache.axis2.AxisFault: WSDoAllReceiver: Incoming message does not contain required Security header. This web service and the ws-security logic works using soapUI (a great *free* tool by the way). Is there some other property I need to set in the options or something else I need to be doing? Thanks Ted
Re: Change in wsdl2java between Axis 1.1 and 1.1.1?
Never mind, difference found: I was using the default adb databinding framework in 1.1.1, xmlbeans in 1.1. Adding a databindingName=xmlbeans to the Ant task[1] fixed it for me. Glen [1] http://ws.apache.org/axis2/tools/1_1/CodegenToolReference.html Am Dienstag, den 27.03.2007, 10:38 -0400 schrieb Glen Mazza: Sorry, wasn't clear, I meant *Axis2* 1.1 to 1.1.1... Glen Am Dienstag, den 27.03.2007, 10:35 -0400 schrieb Glen Mazza: Hello, In upgrading from Axis 1.1 to Axis 1.1.1, I think I noticed a change in how wsdl2java works, but I'm unsure if it was something else I had done to cause this to happen. Running wsdl2java, for both serverside=true and false (using the Ant script) on this WSDL[1] (for a simple math calculator), created the following package structure: src-com-mycompany-mywebservice: - MathQandAServiceCallbackHandler.java MathQandAServiceMessageReceiverInOut.java MathQandAServiceSkeleton.java MathQandAServiceStub.java src-com-mycompany-www-schema-mathqanda: ExtensionMapper.java OperatorType.java SolveMathProblemRequest.java SolveMathProblemResponse.java The difference I noted between Axis 1.1 and 1.1.1 was that MathQandAServiceStub.java links to the classes in www.schema.mathqanda in Axis 1.1 but directly incorporates similar versions of them in Axis 1.1.1 instead. MathQandAServiceStub.java jumped from 380 lines to about 1580 as a result. Am I correct, was there a change between Axis 1.1 and 1.1.1 for the client stub class to no longer reference the classes in the wsdl:types package? (Why?) Or was there something else I had done to cause this to occur? Also, one more question, what term do people generally use to refer to the classes in www.schema.mathqanda above: the wsdl type classes? I don't know what they are normally called. Thanks, Glen [1] http://marc.info/?l=axis-userm=117394780408840w=2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 with Spring
Jetty should be ok. I assume since you got this far that all the axis2 jars are under WEB-INF/lib. If you look at the expanded axis2.war via 'jar xf axis2.war', you'll see the services dir and also a modules dir. I suggest simply copying in its entirety the services and modules directory to your expanded war. Then place your new aar, with the services.xml configured for spring, under the services dir. From that point, let us know if you still have problems. Robert On 3/27/07, Rosan Roche [EMAIL PROTECTED] wrote: Where should the aar file be placed. I am using Jetty server from eclipse to test. After the server startup, while checking for services, I get the exception: I can not find a service for this request to be serviced. Check the WSDL and the request URI. Thanks robert lazarski [EMAIL PROTECTED] wrote: http://ws.apache.org/axis2/1_1_1/spring.html#24 points to the without a servlet context section , yet you have a web.xml and are loading spring there. That's fine, but you need to have an AAR file with just the services.xml file in it. Try http://ws.apache.org/axis2/1_1_1/spring.html#23 and see how that goes. As shown further down in the same docs, the structure of your AAR in this case will be like: ./springExample.aar ./META-INF ./META-INF/MANIFEST.MF ./META-INF/services.xml Further hint: look at the Axis2 Web Application Home Page section in this link where you can see a list of your services: http://ws.apache.org/axis2/1_1_1/installationguide.html HTH, Robert On 3/27/07, Rosan Roche wrote: I am trying to integrate the existing Spring application I have with axis2. I am following the example from http://ws.apache.org/axis2/1_1_1/spring.html#24. I have added the Axis servlet to my web.xml file along with the existing servlet that is being used by the main application. When I try to access the service at http://localhost:8080/mm/services/SpringAwareService, I get an exception: org.apache.axis2.AxisFault: I can not find a service for this request to be serviced. Check the WSDL and the request URI How does the services.xml get loaded? Should it be explicitly loaded while startup? Should I create a WSDL? web.xml PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN http://java.sun.com/dtd/web-app_2_3.dtd; Media Management contextConfigLocation classpath:applicationContext.xml configuration deployment org.springframework.web.context.ContextLoaderListener mm wicket.protocol.http.WicketServlet applicationFactoryClassName wicket.spring.SpringWebApplicationFactory 1 axis org.apache.axis2.transport.http.AxisServlet 5 axis /services/* Thanks Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 not putting binary attachment on the wire
It seems it works fine when MTOM is enabled... From tcpmon HTTP/1.1 200 OK Server: Date: Tue, 27 Mar 2007 13:30:16 GMT Content-type: multipart/related; boundary=MIMEBoundaryurn_uuid_E612E8E634E97EAEE61175002216495; type=application/xop+xml; start=0.urn:uuid:[EMAIL PROTECTED]; start-info=text/xml; charset=UTF-8Transfer-encoding: chunked02d7--MIMEBoundaryurn_uuid_E612E8E634E97EAEE61175002216495content -type: application/xop+xml; charset=UTF-8; type=text/xml;content-transfer-encoding: binarycontent-id: 0.urn:uuid:[EMAIL PROTECTED] ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header / soapenv:Body ns1:getDocumentResponse xmlns:ns1=urn:webservices.docharbor.com ns1:return ns1:documentSize198/ns1:documentSize ns1:document xop:Include href=cid:1.urn:uuid:[EMAIL PROTECTED] xmlns:xop=http://www.w3.org/2004/08/xop/include; / /ns1:document /ns1:return /ns1:getDocumentResponse /soapenv:Body /soapenv:Envelope 00cc --MIMEBoundaryurn_uuid_E612E8E634E97EAEE61175002216495 content-type: application/octet-stream content-transfer-encoding: binary content-id: 1.urn:uuid:[EMAIL PROTECTED]0 Hope you had your binary date here... ~Thilina PS: Please use TCPMON when sniffing messages with attachments.. SOAPMonitor will not show you the attachments... -Original Message- From: Thilina Gunarathne [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 27, 2007 5:54 PM To: axis-user@ws.apache.org Subject: Re: Axis2 not putting binary attachment on the wire Opps... Sounds like a bug to me.. Please log a JIRA with more details.. Some source code would be actually better... Then in order to get through this you can try enablingMTOM in your Axis2.xml.. Thanks, Thilina On 3/28/07, Masin, Valerie [EMAIL PROTECTED] wrote: My webservice returns a binary document which I declare in my wsdl as base64Binary. Using SOAPMonitor I see my document in the returned soap message. However, tcpmon shows that the document is empty. I have tried this both with and without MTOM. Without MTOM here is the soap from SOAPMonitor... ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header / soapenv:Body ns1:getDocumentResponse xmlns:ns1=urn:webservices.docharbor.com ns1:return ns1:documentSize198/ns1:documentSize ns1:documente1xydGYxXGFuc2lcYW5zaWNwZzEyNTJcZGVmZjBcZGVmbGFuZzEwMzN7XG ZvbnR0Ymx7XGYwXGZzd2lzc1xmY2hhcnNldDAgQXJpYWw7fX0NCntcKlxnZW5lcmF0b3IgTX NmdGVkaXQgNS40MS4xNS4xNTA3O31cdmlld2tpbmQ0XHVjMVxwYXJkXGYwXGZzMjAgSSdtIH RoZSBkZWZhdWx0IGRvY3VtZW50IGZvciBpbXBvcnRhdGlvbi5ccGFyDQp9DQoA/ns1:docu ment /ns1:return /ns1:getDocumentResponse /soapenv:Body /soapenv:Envelope ... and here is the output of tcpmon HTTP/1.1 200 OK Server: Date: Tue, 27 Mar 2007 18:26:12 GMT Content-type: text/xml; charset=UTF-8 Transfer-encoding: chunked 016f ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header / soapenv:Body ns1:getDocumentResponse xmlns:ns1=urn:webservices.docharbor.com ns1:return ns1:documentSize198/ns1:documentSize ns1:document/ns1:document notice the empty document /ns1:return /ns1:getDocumentResponse /soapenv:Body /soapenv:Envelope 0 Does anyone know why this is happening? Thanks, Valerie -- Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2: soap/jms question
Asankha,
I pulled the code from the trunk yesterday and now jms binding is working fine
on jboss. Thanks for the fix.
Two questions:
1. Is there a way to specify the temporary queue jndi name for blocking calls
using the jms transport?
2. For non-blocking two way operations how can we specify that the response
should be published to a separate queue? I did not try this, but if I set the
wsa:replyTo from the client, with a jms specific url that specifies the
response queue jndi name, will the service pick this up from the wsa:replyTo
and publish the response to this queue using the specified url?
Thanks,
Shantanu
- Original Message
From: Asankha C. Perera [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Saturday, March 24, 2007 11:58:33 AM
Subject: Re: Axis2: soap/jms question
Shantanu / John Turner
I have reapplied the fixes for 2030 and 2277 and fixed the unit tests,
as I had to revert them last week due to test failures. Would be great
if you could verify this with JBoss or other implementations. The
changes are all in the o.a.a.transport.jms package (3 files)
asankha
Shantanu Sen wrote:
Hi Asankha,
Sounds good. Please let me know the specific file that you patch so that I do
not have to update the whole tree again.
Thanks,
Shantanu
- Original Message
From: Asankha C. Perera [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Thursday, March 22, 2007 9:54:49 PM
Subject: Re: Axis2: soap/jms question
Hi Shantanu
17:12:30,812 ERROR [JMSMessageReceiver] JMS Worker [JMSWorker-1]
Encountered an
Axis Fault : The [action] cannot be processed at the receiver.
org.apache.axis2.AxisFault: The [action] cannot be processed at the receiver.
at org.apache.axis2.addressing.AddressingFaultsHelper.triggerAddressingF
ault(AddressingFaultsHelper.java:346)
at org.apache.axis2.addressing.AddressingFaultsHelper.triggerActionNotSu
pportedFault(AddressingFaultsHelper.java:311)
at org.apache.axis2.handlers.addressing.AddressingValidationHandler.chec
kAction(AddressingValidationHandler.java:137)
at org.apache.axis2.handlers.addressing.AddressingValidationHandler.invo
ke(AddressingValidationHandler.java:50)
at org.apache.axis2.engine.Phase.invoke(Phase.java:383)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203)
...
On investigating, it seems that the AddressValidationHandler.checkAction will
always throw this exception as the following code indicated if the operation
and service values are null.
---
if ((msgContext.getAxisService() == null) || (msgContext.getAxisOperation()
== null)) {
AddressingFaultsHelper
.triggerActionNotSupportedFault(msgContext,
msgContext.getWSAAction());
}
Now here is the envelope that is generated by the stub and published in the JMS
message:
---
?xml version=1.0 encoding=utf-8?
soapenv:Header
wsa:Tojms:/queue/requestQ?transport.jms.ConnectionFactoryJNDIName=ConnectionFactoryamp;java.naming.factory.initial=org.jnp.interfaces.NamingContextFactoryamp;java.naming.provider.url=jnp://localhost:1099/wsa:To
wsa:ReplyTo
http://www.w3.org/2005/08/addressing/anonymous
/wsa:ReplyTo
wsa:MessageIDurn:uuid:6EE9E1632283F7F99D1174613253567/wsa:MessageID
wsa:Actionurn:getPrice/wsa:Action
/soapenv:Header
soapenv:Body
ns1:symbolMSFT/ns1:symbol
/ns1:getPrice
/soapenv:Body
/soapenv:Envelope
--
I also noted that previous to invoking the handlers in the dispatch phase (i.e.
in the pre-dispatch phase), the AddressingInHandler successfully parses the
wsa:Action info from the soap headers. Should'nt this be responsible for
setting the operation (getPrice) in this case?
I tried to find out why the messageContext was not getting filled with the
serviceName. It seems that in JMSMessageReceiver.createMessageContext, it looks
for the servicename based on the destinationName as shown in the following code:
--
Destination dest = message.getJMSDestination();
String destinationName = null;
if (dest instanceof Queue) {
destinationName = ((Queue) dest).getQueueName();
} else if (dest instanceof Topic) {
destinationName = ((Topic) dest).getTopicName();
}
String serviceName =
jmsConFac.getServiceNameForDestination(destinationName);
---
However, the destination name in this case (JBOSS MQ) is 'requestQ'. Note that
the services.xml contains the following as the parameter:
parameter name=transport.jms.Destination
locked=truequeue/requestQ/parameter
And the JMSConnectionFactory stores the mapping as follows in the destinations
variable:
{queue/requestQ=StockQuoteService}
Hence the serviceName is returned as null since JBOSS returns requestQ and not
queue/requestQ as the destination name.
You are spot on correct in your analysis, and earlier
Running multiple instances of axis2 in same Tomcat
I've a few posts that touched on this, but no answers. We have a web application that is deployed multiple times as separate Tomcat virtual hosts. We would like to structure our axis2 web services in a similar way. For example, - webapp #1 is accessed as http://webapp1.myhost.com - webapp #2 is accessed as http://webapp2.myhost.com We would like to be able to access the web services as: - http://webapp1.myhost.com:9191/axis2/MyApplicationService?... - http://webapp2.myhost.com:9292/axis2/MyApplicationService?... Can axis2 be loaded as multiple webapplications in Tomcat 5.5? Should there be any classloading issues? Or maybe there is an alternate way of doing this - maybe using a different namespace mechanism that axis2 provides that I have not discovered/learned yet? Thanks. -- View this message in context: http://www.nabble.com/Running-multiple-instances-of-axis2-in-same-Tomcat-tf3476920.html#a9705315 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to get parameter name of a method in a class compiled with -g option
Hi Axis users and developers, This question is about Axis 1.4. I know Axis can extract the parameter names of a method in a class compiled with -g option. During Java2WSDL, Axis does extract the parameter names to generate WSDL. Does anyone know how Axis achieve this? Regards, Xinjun
Re: Running multiple instances of axis2 in same Tomcat
multiple webapps in same tomcat is possible. thanks, dims On 3/27/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I've a few posts that touched on this, but no answers. We have a web application that is deployed multiple times as separate Tomcat virtual hosts. We would like to structure our axis2 web services in a similar way. For example, - webapp #1 is accessed as http://webapp1.myhost.com - webapp #2 is accessed as http://webapp2.myhost.com We would like to be able to access the web services as: - http://webapp1.myhost.com:9191/axis2/MyApplicationService?... - http://webapp2.myhost.com:9292/axis2/MyApplicationService?... Can axis2 be loaded as multiple webapplications in Tomcat 5.5? Should there be any classloading issues? Or maybe there is an alternate way of doing this - maybe using a different namespace mechanism that axis2 provides that I have not discovered/learned yet? Thanks. -- View this message in context: http://www.nabble.com/Running-multiple-instances-of-axis2-in-same-Tomcat-tf3476920.html#a9705315 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running multiple instances of axis2 in same Tomcat
Hi, is it the same webapp that is reloaded and available through different virtual hosts ? I mean would they have different configurations but the same libraries ? AFAIS Axis2 should have no problem in this. Ajith On 3/27/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I've a few posts that touched on this, but no answers. We have a web application that is deployed multiple times as separate Tomcat virtual hosts. We would like to structure our axis2 web services in a similar way. For example, - webapp #1 is accessed as http://webapp1.myhost.com - webapp #2 is accessed as http://webapp2.myhost.com We would like to be able to access the web services as: - http://webapp1.myhost.com:9191/axis2/MyApplicationService?... - http://webapp2.myhost.com:9292/axis2/MyApplicationService?... Can axis2 be loaded as multiple webapplications in Tomcat 5.5? Should there be any classloading issues? Or maybe there is an alternate way of doing this - maybe using a different namespace mechanism that axis2 provides that I have not discovered/learned yet? Thanks. -- View this message in context: http://www.nabble.com/Running-multiple-instances-of-axis2-in-same-Tomcat-tf3476920.html#a9705315 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ajith Ranabahu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: base href problems
Nobody has anything to add about this? Should i be more specific in my question? Thanks, Jon On 3/27/07, Jon Horsman [EMAIL PROTECTED] wrote: Hello, I'm trying to run the axis server in tomcat behind an apache webserver. Our app will be deployed on a LAN where DNS servers may not be present. The problem i'm having is that when i go to the axis2 start page https://ipaddress/axis2/ the images and links aren't working even though they are relative links. I get links like https://localhost/axis2/axis2-web/HappyAxis.jsp; when in fact it should be https://server ip address or hostname/axis2/axis2-web/HappyAxis.jsp. After viewing the source of the index page I noticed the following line base href=https://localhost/axis2//. This explains why the links and images are going to localhost instead of the IP or hostname that was originally requested. I can change this behavior by setting the proxyName property in tomcat's server.xml file but if i change it to use the hostname this then fails on networks that don't have a DNS server. If i change it to include the IP address this then screws up certificates when someone accesses the page like https://hostname/axis2/ since they get a certificate back with an IP instead of the hostname. Ideally asis2 wouldn't make assumptions and it would return the IP address if it was requested or return the hostname if it was requested. Is there a way to set up axis so that this is the case? Thanks, Jon. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 Client Stub not Generating WS-Security Headers
Hi Ted, Please see this : http://www.wso2.org/library/240 Thanks, Ruchith On 3/28/07, Ted Jones [EMAIL PROTECTED] wrote: I have an Axis2 1.1.1 ADB generated client stub that is instantiated using a client axis2.xml config and pointing to a client repository that has the rampart and addressing mar files. The config file and repository location are loaded via URL. In debug, I can see the rampart and addressing modules are engaged. In my client code, I have added the following properties to the serviceclient's options instance: options.setProperty(WSConstants.WSSE_NS , WSConstants.USERNAME_TOKEN_LN); options.setProperty(WSConstants.USERNAME_LN,getConnectionProperties().getUserid()); options.setProperty(WSConstants.PASSWORD_LN,getConnectionProperties().getPassword()); options.setProperty(WSConstants.PASSWORD_TYPE_ATTR, WSConstants.PASSWORD_TEXT); The WS-Security headers are never inserted into the soap request and I receive the ever-popular org.apache.axis2.AxisFault: WSDoAllReceiver: Incoming message does not contain required Security header. This web service and the ws-security logic works using soapUI (a great *free* tool by the way). Is there some other property I need to set in the options or something else I need to be doing? Thanks Ted -- www.ruchith.org www.wso2.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: base href problems
Please try to set the httpFrontendHostUrl parameter in the axis2.xml (axis2/WEB-INF/conf/axis2.xml) thanks, dims On 3/27/07, Jon Horsman [EMAIL PROTECTED] wrote: Nobody has anything to add about this? Should i be more specific in my question? Thanks, Jon On 3/27/07, Jon Horsman [EMAIL PROTECTED] wrote: Hello, I'm trying to run the axis server in tomcat behind an apache webserver. Our app will be deployed on a LAN where DNS servers may not be present. The problem i'm having is that when i go to the axis2 start page https://ipaddress/axis2/ the images and links aren't working even though they are relative links. I get links like https://localhost/axis2/axis2-web/HappyAxis.jsp; when in fact it should be https://server ip address or hostname/axis2/axis2-web/HappyAxis.jsp. After viewing the source of the index page I noticed the following line base href=https://localhost/axis2//. This explains why the links and images are going to localhost instead of the IP or hostname that was originally requested. I can change this behavior by setting the proxyName property in tomcat's server.xml file but if i change it to use the hostname this then fails on networks that don't have a DNS server. If i change it to include the IP address this then screws up certificates when someone accesses the page like https://hostname/axis2/ since they get a certificate back with an IP instead of the hostname. Ideally asis2 wouldn't make assumptions and it would return the IP address if it was requested or return the hostname if it was requested. Is there a way to set up axis so that this is the case? Thanks, Jon. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Axis2 not putting binary attachment on the wire
No it is not working fine with mtom, there is no data attached. Where you said Hope you had your binary data here... there was no data. There was just the 0. I show the soapmonitor output to show that there had been data in the soap message before it was optimized to mtom. From: Thilina Gunarathne [mailto:[EMAIL PROTECTED] Sent: Tue 3/27/2007 9:29 PM To: axis-user@ws.apache.org Subject: Re: Axis2 not putting binary attachment on the wire It seems it works fine when MTOM is enabled... From tcpmon HTTP/1.1 200 OK Server: Date: Tue, 27 Mar 2007 13:30:16 GMT Content-type: multipart/related; boundary=MIMEBoundaryurn_uuid_E612E8E634E97EAEE61175002216495; type=application/xop+xml; start=0.urn:uuid:[EMAIL PROTECTED]; start-info=text/xml; charset=UTF-8Transfer-encoding: chunked02d7--MIMEBoundaryurn_uuid_E612E8E634E97EAEE61175002216495content -type: application/xop+xml; charset=UTF-8; type=text/xml;content-transfer-encoding: binarycontent-id: 0.urn:uuid:[EMAIL PROTECTED] ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header / soapenv:Body ns1:getDocumentResponse xmlns:ns1=urn:webservices.docharbor.com ns1:return ns1:documentSize198/ns1:documentSize ns1:document xop:Include href=cid:1.urn:uuid:[EMAIL PROTECTED] xmlns:xop=http://www.w3.org/2004/08/xop/include; / /ns1:document /ns1:return /ns1:getDocumentResponse /soapenv:Body /soapenv:Envelope 00cc --MIMEBoundaryurn_uuid_E612E8E634E97EAEE61175002216495 content-type: application/octet-stream content-transfer-encoding: binary content-id: 1.urn:uuid:[EMAIL PROTECTED]0 Hope you had your binary date here... ~Thilina PS: Please use TCPMON when sniffing messages with attachments.. SOAPMonitor will not show you the attachments... -Original Message- From: Thilina Gunarathne [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 27, 2007 5:54 PM To: axis-user@ws.apache.org Subject: Re: Axis2 not putting binary attachment on the wire Opps... Sounds like a bug to me.. Please log a JIRA with more details.. Some source code would be actually better... Then in order to get through this you can try enablingMTOM in your Axis2.xml.. Thanks, Thilina On 3/28/07, Masin, Valerie [EMAIL PROTECTED] wrote: My webservice returns a binary document which I declare in my wsdl as base64Binary. Using SOAPMonitor I see my document in the returned soap message. However, tcpmon shows that the document is empty. I have tried this both with and without MTOM. Without MTOM here is the soap from SOAPMonitor... ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header / soapenv:Body ns1:getDocumentResponse xmlns:ns1=urn:webservices.docharbor.com ns1:return ns1:documentSize198/ns1:documentSize ns1:documente1xydGYxXGFuc2lcYW5zaWNwZzEyNTJcZGVmZjBcZGVmbGFuZzEwMzN7XG ZvbnR0Ymx7XGYwXGZzd2lzc1xmY2hhcnNldDAgQXJpYWw7fX0NCntcKlxnZW5lcmF0b3IgTX NmdGVkaXQgNS40MS4xNS4xNTA3O31cdmlld2tpbmQ0XHVjMVxwYXJkXGYwXGZzMjAgSSdtIH RoZSBkZWZhdWx0IGRvY3VtZW50IGZvciBpbXBvcnRhdGlvbi5ccGFyDQp9DQoA/ns1:docu ment /ns1:return /ns1:getDocumentResponse /soapenv:Body /soapenv:Envelope ... and here is the output of tcpmon HTTP/1.1 200 OK Server: Date: Tue, 27 Mar 2007 18:26:12 GMT Content-type: text/xml; charset=UTF-8 Transfer-encoding: chunked 016f ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header / soapenv:Body ns1:getDocumentResponse xmlns:ns1=urn:webservices.docharbor.com ns1:return ns1:documentSize198/ns1:documentSize ns1:document/ns1:document notice the empty document /ns1:return /ns1:getDocumentResponse /soapenv:Body /soapenv:Envelope 0 Does anyone know why this is happening? Thanks, Valerie -- Thilina Gunarathne - http://www.wso2.com http://www.wso2.com/ - http://thilinag.blogspot.com http://thilinag.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thilina Gunarathne - http://www.wso2.com http://www.wso2.com/ - http://thilinag.blogspot.com http://thilinag.blogspot.com/ - To unsubscribe,
Re: AW: [AXIS2] - Engaging addressing module on client
Hello, I checked my services.xml. It already has the actionMapping tag. However, the wsa:Action header is not being added to the soap message. serviceGroup service name=OwnService description Own WS, two methods: tryPing and tryEcho /description parameter name=ServiceClass locked=falseuserguide.OwnService/parameter operation name=tryEcho messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/\ actionMappingurn:tryEcho/actionMapping /operation operation name=tryPing messageReceiver class=org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver/ actionMappingurn:tryPing/actionMapping /operation /service /serviceGroup Regards, Sagar M. Yerunkar Stadelmann Josef [EMAIL PROTECTED] 03/27/2007 08:28 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject AW: [AXIS2] - Engaging addressing module on client Hi Sagar in your reply message you find wsa:Actionhttp://www.w3.org/2005/08/addressing/fault/wsa:Action Axis2 intends to say in conjuntion with wsa:FaultDetail wsa:ProblemHeaderQNamewsa:Action/wsa:ProblemHeaderQName /wsa:FaultDetail and soapenv:Fault faultcodewsa:MessageAddressingHeaderRequired/faultcode faultstringA required header representing a Message Addressing Property is not present/faultstring detail / /soapenv:Fault that you did not send a wsa:Action header Try adding an wsa:Action Header as shown below in the request message. This header is missing, and that is what axis2 intends to say you. Check for ActionMapping in your service.xml, add it if not there, then you migth have something like .. - operation name=echo messageReceiver class= org.apache.axis2.receivers.RawXMLINOutMessageReceiver / actionMappingurn:echo/actionMapping /operation . So yopur actionMaping wanted has to go into a SoapHeader wsa:Actionurn:echo/wsa:Action Regards Josef -Ursprüngliche Nachricht- Von: Sagar Yerunkar [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 27. März 2007 14:56 An: axis-user@ws.apache.org Betreff: Re: [AXIS2] - Engaging addressing module on client Hello, I have further noticed that if i only include the addressing .mar file in the classpath (without changing any code), i get the exception org.apache.axis2.AxisFault: A required header representing a Message Addressing Property is not present at org.apache.axis2.util.CallbackReceiver.receive(CallbackReceiver.java:65) at org.apache.axis2.engine.AxisEngine.receiveFault(AxisEngine.java:610) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:326) at org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:230) at ... My soap reqest is being sent but i get an Error in the reply Here is my soap request caught using TCP Monitor: POST /axis2/services/OwnService HTTP/1.1 SOAPAction: urn:anonOutInOp User-Agent: Axis2 Host: 127.0.0.1:9000 Transfer-Encoding: chunked Content-Type: text/xml; charset=UTF-8 27e ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header wsa:Tohttp://localhost:9000/axis2/services/OwnService/wsa:To wsa:ReplyTo wsa:Addresshttp://www.w3.org/2005/08/addressing/anonymous/wsa:Address /wsa:ReplyTo wsa:MessageIDurn:uuid:9B8FDACFBCA1263A121174999707376/wsa:MessageID wsa:Actionurn:echo/wsa:Action !!! depends on what you have in service.xml as ActionMapping for the method wanted, I asume urn:echo /soapenv:Header soapenv:Body example1:tryEcho xmlns:example1=http://example1.org/example1; sleepTime=4000 code=0 example1:TextPayload echo string/example1:Text /example1:tryEcho /soapenv:Body /soapenv:Envelope0 Here is my soap response : HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Content-Type: text/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Tue, 27 Mar 2007 12:48:28 GMT Connection: close 3cc ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header wsa:Tohttp://www.w3.org/2005/08/addressing/anonymous/wsa:To wsa:ReplyTo wsa:Addresshttp://www.w3.org/2005/08/addressing/none/wsa:Address /wsa:ReplyTo wsa:MessageIDurn:uuid:AF393873831A7C3EF31174999708410/wsa:MessageID wsa:Actionhttp://www.w3.org/2005/08/addressing/fault/wsa:Action wsa:RelatesTo wsa:RelationshipType= http://www.w3.org/2005/08/addressing/reply urn:uuid:9B8FDACFBCA1263A121174999707376/wsa:RelatesTo wsa:FaultDetail
AW: AW: [AXIS2] - Engaging addressing module on client
Hello Sagar, Is the addressing module deployed and ENGAGED both on client and server? Josef -Ursprüngliche Nachricht- Von: Sagar Yerunkar [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 28. März 2007 06:24 An: axis-user@ws.apache.org Betreff: Re: AW: [AXIS2] - Engaging addressing module on client Hello, I checked my services.xml. It already has the actionMapping tag. However, the wsa:Action header is not being added to the soap message. serviceGroup service name=OwnService description Own WS, two methods: tryPing and tryEcho /description parameter name=ServiceClass locked=falseuserguide.OwnService/parameter operation name=tryEcho messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/\ actionMappingurn:tryEcho/actionMapping /operation operation name=tryPing messageReceiver class=org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver/ actionMappingurn:tryPing/actionMapping /operation /service /serviceGroup Regards, Sagar M. Yerunkar Stadelmann Josef [EMAIL PROTECTED] 03/27/2007 08:28 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject AW: [AXIS2] - Engaging addressing module on client Hi Sagar in your reply message you find wsa:Actionhttp://www.w3.org/2005/08/addressing/fault/wsa:Action Axis2 intends to say in conjuntion with wsa:FaultDetail wsa:ProblemHeaderQNamewsa:Action/wsa:ProblemHeaderQName /wsa:FaultDetail and soapenv:Fault faultcodewsa:MessageAddressingHeaderRequired/faultcode faultstringA required header representing a Message Addressing Property is not present/faultstring detail / /soapenv:Fault that you did not send a wsa:Action header Try adding an wsa:Action Header as shown below in the request message. This header is missing, and that is what axis2 intends to say you. Check for ActionMapping in your service.xml, add it if not there, then you migth have something like .. file:///C:/axis2-1.1/samples/userguide/src/userguide/example5/META-INF/services.xml# - operation name=echo messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver / actionMappingurn:echo/actionMapping /operation . So yopur actionMaping wanted has to go into a SoapHeader wsa:Actionurn:echo/wsa:Action Regards Josef -Ursprüngliche Nachricht- Von: Sagar Yerunkar [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 27. März 2007 14:56 An: axis-user@ws.apache.org Betreff: Re: [AXIS2] - Engaging addressing module on client Hello, I have further noticed that if i only include the addressing .mar file in the classpath (without changing any code), i get the exception org.apache.axis2.AxisFault: A required header representing a Message Addressing Property is not present at org.apache.axis2.util.CallbackReceiver.receive(CallbackReceiver.java:65) at org.apache.axis2.engine.AxisEngine.receiveFault(AxisEngine.java:610) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:326) at org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:230) at ... My soap reqest is being sent but i get an Error in the reply Here is my soap request caught using TCP Monitor: POST /axis2/services/OwnService HTTP/1.1 SOAPAction: urn:anonOutInOp User-Agent: Axis2 Host: 127.0.0.1:9000 Transfer-Encoding: chunked Content-Type: text/xml; charset=UTF-8 27e ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header wsa:Tohttp://localhost:9000/axis2/services/OwnService/wsa:To wsa:ReplyTo wsa:Addresshttp://www.w3.org/2005/08/addressing/anonymous/wsa:Address /wsa:ReplyTo wsa:MessageIDurn:uuid:9B8FDACFBCA1263A121174999707376/wsa:MessageID wsa:Actionurn:echo/wsa:Action !!! depends on what you have in service.xml as ActionMapping for the method wanted, I asume urn:echo /soapenv:Header soapenv:Body example1:tryEcho xmlns:example1=http://example1.org/example1; sleepTime=4000 code=0 example1:TextPayload echo string/example1:Text /example1:tryEcho /soapenv:Body /soapenv:Envelope0 Here is my soap response : HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Content-Type: text/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Tue, 27 Mar 2007 12:48:28 GMT Connection: close 3cc ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header
AW: AW: [AXIS2] - Engaging addressing module on client
Hello Sagar,
Here is my SOAPClient.java code main() only, which engages 3 modules,
Also I run my client and server in scope=soapsession. Therefore
MyService5.java has a service.xml which defines
service name=MyService5 scope=soapsession
It works for me, and hope you can say the same now.
Josef
public static void main(String[] args) throws AxisFault {
try {
Options options = new Options();
options.setManageSession(true);
options.setTo(new EndpointReference(toEpr));
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
String home = System.getProperty(user.home);
// create this folder at your home. This folder could be anything
//then create the modules folder
//copy the LoggingModule.mar to modules folder.
//copy the axis2.xml to the client-repository
File repository = new File(home + File.separator +
client-repository);
if (!repository.exists()) {
throw new FileNotFoundException(repository.getAbsolutePath() +
does not Exist);
};
String str_axis2xml = repository.getAbsolutePath() + File.separator
+ axis2.xml;
File axis2_xml = new File(str_axis2xml);
if (!axis2_xml.exists()) {
throw new FileNotFoundException(axis2_xml.getAbsolutePath() +
does not Exist);
};
FileSystemConfigurator fsc = new FileSystemConfigurator(
repository.getAbsolutePath(),
axis2_xml.getAbsolutePath());
AxisConfiguration er = fsc.getAxisConfig();
ConfigurationContext configContext =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(
repository.getAbsolutePath(),
axis2_xml.getAbsolutePath()
);
//ServiceClient sender = new ServiceClient();
ServiceClient sender = new ServiceClient(configContext,null);
//sender.engageModule(new QName(Constants.MODULE_LOGGING));
sender.engageModule(new QName(logging));
+++ Sagar, do you have something like that in your code?
//sender.engageModule(new QName(Constants.MODULE_ADDRESSING));
sender.engageModule(new QName(addressing-1.1));
//sender.engageModule(new QName(Constants.MODULE_SOAPMONITOR));
sender.engageModule(new QName(soapmonitor-1.1));
+++ Sagar, do you have something like that in your code?
// invoke the start method first using it's StartPaylod
options.setAction(urn:start);
sender.setOptions(options);
OMElement start = sender.sendReceive(getStartPayload());
// from now on use this sender so that WS-address stuff i.e.
ServiceGroupeContextID info is sent
// where in the dark of the code is that?
String s = intObj.toString(i);
System.out.print(No+s);
XMLStreamWriter startWriter =
XMLOutputFactory.newInstance().createXMLStreamWriter(System.out);
start.serialize(startWriter);
startWriter.flush();// write every-thing out
System.out.println(); // and add a CRLF
+++ Sagar, do you have something like that in your code?start was the
initial method called, now lets use echo
options.setAction(urn:echo);
sender.setOptions(options);
for(int i=0;i500;i++){
OMElement result = sender.sendReceive(getPayload());
Thread.sleep(4000);
s = intObj.toString(i);
System.out.print(No+s);
XMLStreamWriter writer =
XMLOutputFactory.newInstance().createXMLStreamWriter(System.out);
result.serialize(writer);
writer.flush(); // write every-thing out
System.out.println(); // and add a CRLF
if (i==100){
System.gc();// do an explicit Garbage Collection and
get it all back
}
if (0 == i % 100){
System.gc();// do an explicit Garbage Collection once
evry 100 loops-through
}
} // end-for - so do a cleanup now to give up sender resource
sender.cleanup(); // return resources .finalize would do more but
is protected
} catch (FileNotFoundException e) {
Re: AW: AW: [AXIS2] - Engaging addressing module on client
Hello,
I have engaged the addressing module on the cliente as well as the
service.
For the service, i checked the admin page and confirmed that the
addressing module has been engaged.
On the client side, i have included the addressing .mar file in my
classpath. Hence i got this in my output
Mar 28, 2007 10:39:41 AM org.apache.axis2.deployment.DeploymentEngine
doDeploy
INFO: Deploying module : addressing-1.1.1
and the following code did not throw any exceptions
try {
serviceClient.engageModule(new
QName(addressing));
} catch (AxisFault e) {
e.printStackTrace();
}
Regards,
Sagar M. Yerunkar
Stadelmann Josef [EMAIL PROTECTED]
03/28/2007 10:20 AM
Please respond to
axis-user@ws.apache.org
To
axis-user@ws.apache.org
cc
Subject
AW: AW: [AXIS2] - Engaging addressing module on client
Hello Sagar,
Is the addressing module deployed and ENGAGED both on client and
server?
Josef
-Ursprüngliche Nachricht-
Von: Sagar Yerunkar [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 28. März 2007 06:24
An: axis-user@ws.apache.org
Betreff: Re: AW: [AXIS2] - Engaging addressing module on client
Hello,
I checked my services.xml. It already has the actionMapping tag. However,
the wsa:Action header is not being added to the soap message.
serviceGroup
service name=OwnService
description
Own WS, two methods: tryPing and tryEcho
/description
parameter name=ServiceClass
locked=falseuserguide.OwnService/parameter
operation name=tryEcho
messageReceiver
class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/\
actionMappingurn:tryEcho/actionMapping
/operation
operation name=tryPing
messageReceiver
class=org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver/
actionMappingurn:tryPing/actionMapping
/operation
/service
/serviceGroup
Regards,
Sagar M. Yerunkar
Stadelmann Josef [EMAIL PROTECTED]
03/27/2007 08:28 PM
Please respond to
axis-user@ws.apache.org
To
axis-user@ws.apache.org
cc
Subject
AW: [AXIS2] - Engaging addressing module on client
Hi Sagar
in your reply message you find
wsa:Actionhttp://www.w3.org/2005/08/addressing/fault/wsa:Action
Axis2 intends to say in conjuntion with
wsa:FaultDetail
wsa:ProblemHeaderQNamewsa:Action/wsa:ProblemHeaderQName
/wsa:FaultDetail
and
soapenv:Fault
faultcodewsa:MessageAddressingHeaderRequired/faultcode
faultstringA required header representing a Message
Addressing Property is not present/faultstring
detail /
/soapenv:Fault
that you did not send a wsa:Action header
Try adding an wsa:Action Header as shown below in the request message.
This header is missing, and that is what
axis2 intends to say you.
Check for ActionMapping in your service.xml, add it if not there, then you
migth have something like
..
- operation name=echo
messageReceiver class=
org.apache.axis2.receivers.RawXMLINOutMessageReceiver /
actionMappingurn:echo/actionMapping
/operation
.
So yopur actionMaping wanted has to go into a SoapHeader
wsa:Actionurn:echo/wsa:Action
Regards
Josef
-Ursprüngliche Nachricht-
Von: Sagar Yerunkar [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 27. März 2007 14:56
An: axis-user@ws.apache.org
Betreff: Re: [AXIS2] - Engaging addressing module on client
Hello,
I have further noticed that if i only include the addressing .mar file in
the classpath (without changing any code), i get the exception
org.apache.axis2.AxisFault: A required header representing a Message
Addressing
Property is not present
at
org.apache.axis2.util.CallbackReceiver.receive(CallbackReceiver.java:65)
at
org.apache.axis2.engine.AxisEngine.receiveFault(AxisEngine.java:610)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:326)
at
org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:230)
at ...
My soap reqest is being sent but i get an Error in the reply
Here is my soap request caught using TCP Monitor:
POST /axis2/services/OwnService HTTP/1.1
SOAPAction: urn:anonOutInOp
User-Agent: Axis2
Host: 127.0.0.1:9000
Transfer-Encoding: chunked
Content-Type: text/xml; charset=UTF-8
27e
?xml version='1.0' encoding='UTF-8'?
soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing;
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Header
wsa:Tohttp://localhost:9000/axis2/services/OwnService/wsa:To
wsa:ReplyTo
wsa:Addresshttp://www.w3.org/2005/08/addressing/anonymous/wsa:Address
/wsa:ReplyTo
wsa:MessageIDurn:uuid:9B8FDACFBCA1263A121174999707376/wsa:MessageID
wsa:Actionurn:echo/wsa:Action !!! depends on what you
have in service.xml as
AW: AW: AW: [AXIS2] - Engaging addressing module on client
Hello Sagar
But are this lines present before you call the sender
// invoke the start method first using it's StartPaylod
options.setAction(urn:tryEcho);// this should add
the wsa:Action to your request message
sender.setOptions(options);
Regards
Josef Stadelmann
-Ursprüngliche Nachricht-
Von: Sagar Yerunkar [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 28. März 2007 07:15
An: axis-user@ws.apache.org
Betreff: Re: AW: AW: [AXIS2] - Engaging addressing module on client
Hello,
I have engaged the addressing module on the cliente as well as the service.
For the service, i checked the admin page and confirmed that the addressing
module has been engaged.
On the client side, i have included the addressing .mar file in my classpath.
Hence i got this in my output
Mar 28, 2007 10:39:41 AM org.apache.axis2.deployment.DeploymentEngine doDeploy
INFO: Deploying module : addressing-1.1.1
and the following code did not throw any exceptions
try {
serviceClient.engageModule(new QName(addressing));
} catch (AxisFault e) {
e.printStackTrace();
}
Regards,
Sagar M. Yerunkar
Stadelmann Josef [EMAIL PROTECTED]
03/28/2007 10:20 AM
Please respond to
axis-user@ws.apache.org
To
axis-user@ws.apache.org
cc
Subject
AW: AW: [AXIS2] - Engaging addressing module on client
Hello Sagar,
Is the addressing module deployed and ENGAGED both on client and server?
Josef
-Ursprüngliche Nachricht-
Von: Sagar Yerunkar [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 28. März 2007 06:24
An: axis-user@ws.apache.org
Betreff: Re: AW: [AXIS2] - Engaging addressing module on client
Hello,
I checked my services.xml. It already has the actionMapping tag. However, the
wsa:Action header is not being added to the soap message.
serviceGroup
service name=OwnService
description
Own WS, two methods: tryPing and tryEcho
/description
parameter name=ServiceClass
locked=falseuserguide.OwnService/parameter
operation name=tryEcho
messageReceiver
class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/\
actionMappingurn:tryEcho/actionMapping
/operation
operation name=tryPing
messageReceiver
class=org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver/
actionMappingurn:tryPing/actionMapping
/operation
/service
/serviceGroup
Regards,
Sagar M. Yerunkar
Stadelmann Josef [EMAIL PROTECTED]
03/27/2007 08:28 PM
Please respond to
axis-user@ws.apache.org
To
axis-user@ws.apache.org
cc
Subject
AW: [AXIS2] - Engaging addressing module on client
Hi Sagar
in your reply message you find
wsa:Actionhttp://www.w3.org/2005/08/addressing/fault/wsa:Action
Axis2 intends to say in conjuntion with
wsa:FaultDetail
wsa:ProblemHeaderQNamewsa:Action/wsa:ProblemHeaderQName
/wsa:FaultDetail
and
soapenv:Fault
faultcodewsa:MessageAddressingHeaderRequired/faultcode
faultstringA required header representing a Message Addressing
Property is not present/faultstring
detail /
/soapenv:Fault
that you did not send a wsa:Action header
Try adding an wsa:Action Header as shown below in the request message. This
header is missing, and that is what
axis2 intends to say you.
Check for ActionMapping in your service.xml, add it if not there, then you
migth have something like
..
file:///C:/axis2-1.1/samples/userguide/src/userguide/example5/META-INF/services.xml#
- operation name=echo
messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver
/
actionMappingurn:echo/actionMapping
/operation
.
So yopur actionMaping wanted has to go into a SoapHeader
wsa:Actionurn:echo/wsa:Action
Regards
Josef
-Ursprüngliche Nachricht-
Von: Sagar Yerunkar [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 27. März 2007 14:56
An: axis-user@ws.apache.org
Betreff: Re: [AXIS2] - Engaging addressing module on client
Hello,
I have further noticed that if i only include the addressing .mar file in the
classpath (without changing any code), i get the exception
org.apache.axis2.AxisFault: A required header representing a Message Addressing
Property is not present
at
org.apache.axis2.util.CallbackReceiver.receive(CallbackReceiver.java:65)
at org.apache.axis2.engine.AxisEngine.receiveFault(AxisEngine.java:610)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:326)
at
org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:230)
at ...
My soap reqest is being sent but i get an Error in the reply
Here is my soap request caught using TCP Monitor:
POST
Re: [Axis2] AXIOM or JBIX
Hi Anil, The JiBX XML file which I had mentioned contains the mapping between XML and the Java classes. You can generate this file using the jibx commands. Please refer the JiBX documentation for more details. Secondly your question related to sending a SOAP request. We always send a SOAP request to a Web Service. I mean even if we have a Java client written what we do is create a SOAP request and then send the same over HTTP or any other transport protocol to the Web Service endpoint. So the Client request would always be in SOAP whether you have a java/.NET/C/C++ client accessing the web service. Regards Nilesh Anil VVNN [EMAIL PROTECTED] wrote: Hi Nilesh, Thanks for detailed response. So, the AddressBookService example (at http://people.apache.org/~thilina/axis2/docs/jibx/jibx-unwrapped-example.html) which uses POJO as a data transfer object, can be implemented using any Data binding framework (JIBX or ADB) to create Java classes. What is JiBX binding definition, is this property only applicable to JiBX framework -EbindingFile /resources/jibxbindingFile.xml And also, can we send the client request using SOAP (instead of writing Java Client) and get the response back in SOAP? In which case, this type of scenario comes in. Thanks, Anil Nilesh Ghorpade wrote: Hi Anil, The Data binding frameworks come into picture when you are generating the Java code artifacts from WSDL. If you observe the wsdl2java command there is a command line argument namely -d with which you can specify the Data binding framework which you want to use. In case u want to use JiBX you would be specifying something like $ wsdl2java -o /outputDir -d jibx -EbindingFile /resources/jibxbindingFile.xml -uri MyWebService.wsdl The above command is just for making things more simpler. Also if there are no schema references in the WSDL or if the WSDL is not having any schema types then the Data binding framework would not be coming into picture. (Others Please correct me if I am wrong.) You would just be deciding which Data binding framework you should be using. AXIS 2 would internally be using the same and generating the Java classes for you. Do not get confused by the approach which you are choosing to build the web service and the data binding framework. The data binding framework is just to map the schema which is defined in the WSDL to Java classes. Thats the only purpose of the data binding framework. Using POJO's for web services means you would be writing a POJO class which would be capturing all the information you need for invoking the particular web service operation. For example if you see the AddressBookService in the AXIS 2 samples you can see that the addEntry method takes in a POJO as its input parameter namely Entry. Regarding your second question I am not able to understand it correctly. Also the flow which you have mentioned from the Client to the Service is correct and it would remain the same for any Web service for that matter i.e. not only AXIS 2 but any web service which is developed using any other framework. Hope that answers your queries. Regards Nilesh - Original Message From: Anil VVNN To: axis-user@ws.apache.org Sent: Monday, March 26, 2007 7:56:35 PM Subject: Re: [Axis2] AXIOM or JBIX Hi Niles, Thanks for answering my questions. As I said I'm a beginner, I have few more questions related to previous one. (1) When exactly do we use Binding frameworks (JIBX, ADB or XMLBeans) ? For instance, the examples given in Axis2 website (i.e. StockQuoteService) referring to simple method call, client calling WS for getPrice/update operations but there's no XSD involved, I think this kind of operations can be easily accomplished using POJO option. But I'm confused when to use POJO or anyother Binding framework(JIBX). (2) What is the difference between XML Processing Model and SOAP Processing Model, when do we use these models independently. To my understanding, this is the typical flow of Axis2 services, Client calls--- Stub (generated by wsdl2java) calls[SOAP request]--- Skeleton Interface (generated by wsdl2java) --Business Logic And this SOAP request can be handled using any transport (eg. TCP, JMS etc.) Please correct me if I'm wrong. Thanks. - Anil Nilesh Ghorpade wrote: Hi, As per my understanding AXIS 2 uses AXIOM API's internally for any XML related activities. Hence as you have mentioned that you are confused to choose between POJO, AXIOM, JIBX, ADB or XMLBeans, the AXIOM is an invalid option here. Secondly in AXIS 2 you can create web services using either the Spring Framework or POJO. JiBX, XMLBeans and ADB are more related to the data binding frameworks which AXIS 2 supports. Hence it depends on your schema on which data binding framework you would want to select. As per my knowledge XMLBeans is the
Re: [Axis2] AXIOM or JBIX
Hi Anil, The JiBX XML file which I had mentioned contains the mapping between XML and the Java classes. You can generate this file using the jibx commands. Please refer the JiBX documentation for more details. Secondly your question related to sending a SOAP request. We always send a SOAP request to a Web Service. I mean even if we have a Java client written what we do is create a SOAP request and then send the same over HTTP or any other transport protocol to the Web Service endpoint. So the Client request would always be in SOAP whether you have a java/.NET/C/C++ client accessing the web service. Regards Nilesh Anil VVNN [EMAIL PROTECTED] wrote: Hi Nilesh, Thanks for detailed response. So, the AddressBookService example (at http://people.apache.org/~thilina/axis2/docs/jibx/jibx-unwrapped-example.html) which uses POJO as a data transfer object, can be implemented using any Data binding framework (JIBX or ADB) to create Java classes. What is JiBX binding definition, is this property only applicable to JiBX framework -EbindingFile /resources/jibxbindingFile.xml And also, can we send the client request using SOAP (instead of writing Java Client) and get the response back in SOAP? In which case, this type of scenario comes in. Thanks, Anil Nilesh Ghorpade wrote: Hi Anil, The Data binding frameworks come into picture when you are generating the Java code artifacts from WSDL. If you observe the wsdl2java command there is a command line argument namely -d with which you can specify the Data binding framework which you want to use. In case u want to use JiBX you would be specifying something like $ wsdl2java -o /outputDir -d jibx -EbindingFile /resources/jibxbindingFile.xml -uri MyWebService.wsdl The above command is just for making things more simpler. Also if there are no schema references in the WSDL or if the WSDL is not having any schema types then the Data binding framework would not be coming into picture. (Others Please correct me if I am wrong.) You would just be deciding which Data binding framework you should be using. AXIS 2 would internally be using the same and generating the Java classes for you. Do not get confused by the approach which you are choosing to build the web service and the data binding framework. The data binding framework is just to map the schema which is defined in the WSDL to Java classes. Thats the only purpose of the data binding framework. Using POJO's for web services means you would be writing a POJO class which would be capturing all the information you need for invoking the particular web service operation. For example if you see the AddressBookService in the AXIS 2 samples you can see that the addEntry method takes in a POJO as its input parameter namely Entry. Regarding your second question I am not able to understand it correctly. Also the flow which you have mentioned from the Client to the Service is correct and it would remain the same for any Web service for that matter i.e. not only AXIS 2 but any web service which is developed using any other framework. Hope that answers your queries. Regards Nilesh - Original Message From: Anil VVNN To: axis-user@ws.apache.org Sent: Monday, March 26, 2007 7:56:35 PM Subject: Re: [Axis2] AXIOM or JBIX Hi Niles, Thanks for answering my questions. As I said I'm a beginner, I have few more questions related to previous one. (1) When exactly do we use Binding frameworks (JIBX, ADB or XMLBeans) ? For instance, the examples given in Axis2 website (i.e. StockQuoteService) referring to simple method call, client calling WS for getPrice/update operations but there's no XSD involved, I think this kind of operations can be easily accomplished using POJO option. But I'm confused when to use POJO or anyother Binding framework(JIBX). (2) What is the difference between XML Processing Model and SOAP Processing Model, when do we use these models independently. To my understanding, this is the typical flow of Axis2 services, Client calls--- Stub (generated by wsdl2java) calls[SOAP request]--- Skeleton Interface (generated by wsdl2java) --Business Logic And this SOAP request can be handled using any transport (eg. TCP, JMS etc.) Please correct me if I'm wrong. Thanks. - Anil Nilesh Ghorpade wrote: Hi, As per my understanding AXIS 2 uses AXIOM API's internally for any XML related activities. Hence as you have mentioned that you are confused to choose between POJO, AXIOM, JIBX, ADB or XMLBeans, the AXIOM is an invalid option here. Secondly in AXIS 2 you can create web services using either the Spring Framework or POJO. JiBX, XMLBeans and ADB are more related to the data binding frameworks which AXIS 2 supports. Hence it depends on your schema on which data binding framework you would want to select. As per my knowledge XMLBeans is the
Re: [Axis2] AXIOM or JBIX
Hi Anil, The JiBX XML file which I had mentioned contains the mapping between XML and the Java classes. You can generate this file using the jibx commands. Please refer the JiBX documentation for more details. Secondly your question related to sending a SOAP request. We always send a SOAP request to a Web Service. I mean even if we have a Java client written what we do is create a SOAP request and then send the same over HTTP or any other transport protocol to the Web Service endpoint. So the Client request would always be in SOAP whether you have a java/.NET/C/C++ client accessing the web service. Regards Nilesh - Original Message From: Anil VVNN [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Wednesday, March 28, 2007 2:53:58 AM Subject: Re: [Axis2] AXIOM or JBIX Hi Nilesh, Thanks for detailed response. So, the AddressBookService example (at http://people.apache.org/~thilina/axis2/docs/jibx/jibx-unwrapped-example.html) which uses POJO as a data transfer object, can be implemented using any Data binding framework (JIBX or ADB) to create Java classes. What is JiBX binding definition, is this property only applicable to JiBX framework -EbindingFile /resources/jibxbindingFile.xml And also, can we send the client request using SOAP (instead of writing Java Client) and get the response back in SOAP? In which case, this type of scenario comes in. Thanks, Anil Nilesh Ghorpade wrote: Hi Anil, The Data binding frameworks come into picture when you are generating the Java code artifacts from WSDL. If you observe the wsdl2java command there is a command line argument namely -d with which you can specify the Data binding framework which you want to use. In case u want to use JiBX you would be specifying something like $ wsdl2java -o /outputDir -d jibx -EbindingFile /resources/jibxbindingFile.xml -uri MyWebService.wsdl The above command is just for making things more simpler. Also if there are no schema references in the WSDL or if the WSDL is not having any schema types then the Data binding framework would not be coming into picture. (Others Please correct me if I am wrong.) You would just be deciding which Data binding framework you should be using. AXIS 2 would internally be using the same and generating the Java classes for you. Do not get confused by the approach which you are choosing to build the web service and the data binding framework. The data binding framework is just to map the schema which is defined in the WSDL to Java classes. Thats the only purpose of the data binding framework. Using POJO's for web services means you would be writing a POJO class which would be capturing all the information you need for invoking the particular web service operation. For example if you see the AddressBookService in the AXIS 2 samples you can see that the addEntry method takes in a POJO as its input parameter namely Entry. Regarding your second question I am not able to understand it correctly. Also the flow which you have mentioned from the Client to the Service is correct and it would remain the same for any Web service for that matter i.e. not only AXIS 2 but any web service which is developed using any other framework. Hope that answers your queries. Regards Nilesh - Original Message From: Anil VVNN [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Monday, March 26, 2007 7:56:35 PM Subject: Re: [Axis2] AXIOM or JBIX Hi Niles, Thanks for answering my questions. As I said I'm a beginner, I have few more questions related to previous one. (1) When exactly do we use Binding frameworks (JIBX, ADB or XMLBeans) ? For instance, the examples given in Axis2 website (i.e. StockQuoteService) referring to simple method call, client calling WS for getPrice/update operations but there's no XSD involved, I think this kind of operations can be easily accomplished using POJO option. But I'm confused when to use POJO or anyother Binding framework(JIBX). (2) What is the difference between XML Processing Model and SOAP Processing Model, when do we use these models independently. To my understanding, this is the typical flow of Axis2 services, Client calls--- Stub (generated by wsdl2java) calls[SOAP request]--- Skeleton Interface (generated by wsdl2java) --Business Logic And this SOAP request can be handled using any transport (eg. TCP, JMS etc.) Please correct me if I'm wrong. Thanks. - Anil Nilesh Ghorpade wrote: Hi, As per my understanding AXIS 2 uses AXIOM API's internally for any XML related activities. Hence as you have mentioned that you are confused to choose between POJO, AXIOM, JIBX, ADB or XMLBeans, the AXIOM is an invalid option here. Secondly in AXIS 2 you can create web services using either the Spring Framework or POJO. JiBX, XMLBeans and ADB are more related to the data binding frameworks which AXIS 2 supports. Hence it
Axis 1.4 Java2WSDL
Hi Axis users and developers, I cannot understand one thing about Axis 1.4's Java2WSDL. When I use Java2WSDL, my class file is a concrete class compiled with -g option. Then in the generated WSDL, I now do not see those meaningless in0, in1, and etc. Thanks Axis developers! But I don't understand how Axis extracts the parameter names of a method from a class file. I have this question because I want to extract parameter names of a method from a class file using my own program. I googled and two options are using either JDI or BCEL. I searched Axis source but do not see these two APIs. I want to learn from Axis Java2WSDL to get parameter names of a class file. Could any Axis developer or expert user explain the concept how Axis get the parameter names of a method from a class file? Currently I want to choose BCEL to achieve the purpose, but I still want to understand how Axis does it. Regards, Xinjun
