RE: How to enable log4j logging in axis2

[schalk]

Yes, everything is there. All you need do is drop your log4j.properties file
into the classes directory and then you should be good to go.

> Someone please help me to setup log4j logging in axis2. Does the axis2.war 
> distribution include all the necessary jar to enable log4j logging?
> falom

--
Open WebMail Project (http://openwebmail.org)


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2]Re: MTOM and content-type

[Stefan Kok]

Hi Thilina

Thanks. Disabling MTOM and enabling SWA did work great. 

Please see the exert from EtherReal below. Note that the attachment is
placed in the  as base64 string.

.
.
.
/9j/4AAQSkZJRgABAgIAAAD/4QA
+RXhpZgAASUkqAAgBAAsAAgAcGgBBQ0QgU3lzdGVtcyBEaWdpdGFsIEltYWdpbmcA//4AHkFDRCBTeXN0ZW1zIERpZ2l0YWwgSW1hZ2luZwD/wAARCABkAJYDASIAAhEBAxEB/9sAhAAHBAUGBQQHBgUGBwcHCAoRCwoJCQoVDxAMERkWGhoYFhgYHB8oIhwdJh4YGCMvIyYpKi0tLRshMTQxKzQoLC0rAQsLCw8NDx4RER5AKyQrQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQED/xACdAAACAwEBAQAEBQIDBgcBABAAAgEDAgIGBgUHCAgHAQIDAAQRBSESMQYTIkFRYQcUMnGBkSNCodHwFTNSU3KxwSQ0NWJ0gpKzFkNUc4OTsuEXJTY3VaLSAQADAQEBAAABAgMABAURAAICAQQCAgMBAhFBAxIhMRNRBCIUQnH/2gAMAwEAAhEDEQA/AOn9RZ6kzSzQoW8ScGk99ZyWUpeBg0Y7uLcUC011bDCzZA7vCqpNUdhiVQfOvRjBolKSGkWrRtGY7hTVUjw+1A7ZPcaTPMrNkAirIJyrDBqm0TcN4IpJj2VLHyotbCUbPE
.
.
/9k=




The server I am sending to, requires that I send it as 




Kind regards
Stefan.


On Sun, 2006-12-31 at 07:35 +0600, Thilina Gunarathne wrote:
> Stefan,
> Please use Soap with Attachments only.. Then it'll be text/xml..
> Make sure *not* to enable MTOM at the same time, cause then MTOM will
> get priority and the message will be MTOM..
> 
> See here [1] for more detials...
> 
> Thilina
> [1] http://wso2.org/library/264
> 
> On 12/29/06, Stefan Kok <[EMAIL PROTECTED]> wrote:
> > Hi All
> >
> > I have got axis2 to generate the following for me:
> >
> > POST /some HTTP/1.1
> > SOAPAction: ""
> > User-Agent: Axis2
> > Content-Length: 5790
> > Content-Type: multipart/related;
> > boundary=MIMEBoundaryurn_uuid_D71D1475B0136C8FED11673898742622;
> > type="application/xop+xml";
> > start="<0.urn:uuid:[EMAIL PROTECTED]>";
> > start-info="text/xml"; charset=UTF-8
> > Authorization: Digest username="username", realm="somerealm",
> > nonce="RZTzxw==028733d3cb3ad64a414de383d252b679e8969982", uri="/some",
> > response="427csaasaawqwqee6be586508c8e91b4", qop=auth, nc=0001,
> > cnonce="61849b59f21f00e0ac46d38f9be4f1b2", algorithm="MD5"
> > Host: fqdn:8082
> >
> > --MIMEBoundaryurn_uuid_D71D1475B0136C8FED11673898742622
> > content-type: application/xop+xml; charset=UTF-8; type="text/xml";
> > content-transfer-encoding: binary
> > content-id: <0.urn:uuid:[EMAIL PROTECTED]>
> >
> >  > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> >  
> > xmlns:ns1="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2";
> >  
> > ns1:mustUnderstand="1">MyTransaction >  
> > xmlns:ns1="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2";> >  href="cid:1.urn:uuid:[EMAIL PROTECTED]" 
> > xmlns:xop="http://www.w3.org/2004/08/xop/include"; 
> > />
> > --MIMEBoundaryurn_uuid_D71D1475B0136C8FED11673898742622
> >
> > The server that I send this to, requires that the content-type must be:
> >
> > text/xml; charset="utf-8"
> >
> > and not
> >
> > content-type: application/xop+xml; charset=UTF-8; type="text/xml";
> >
> > I have been searching the web for ideas but have not found much. It must
> > be multipart/related so I cannot turn off MTOM.
> >
> >
> >
> > Kind regards
> > Stefan.
> >
> >
> >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> 
> 
-- 
Stefan Kok <[EMAIL PROTECTED]>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] what's the diff between RPCMsgReceiver and RawXMLMsgReceiver

[Chatra Nakkawita]

Hi,

I corrected the issue and committed to site. When the root html tag is a pre
tag, at maven site build any html tags inside pre tags are removed with the
content inside. That's why the missing bold font.

I opened a paragraph tag before the pre tag. Issue is fixed.

Thanks,
Chatra

On 12/31/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:


Thilina,

I noticed that there is an error in the POJO guide in code listing 4:
Setting the weather. The code says:

EndpointReference targetEPR = new EndpointReference(

options.setTo(targetEPR);

The following text says:

The most interesting code to note is in bold font. Notice the
targetEPR variable
you create, setting the endpoint reference to
http://localhost:8080/axis2/services/WeatherService.

1. there is no bold font.
2. the code that sets the targetEPR is missing.

Anne

On 12/30/06, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
> RPCMessageReceiver is used for simply deploying POJO(plain old java
> objects) as services..See here[1] for more details.
> RawXMLMR can be used when you want to receive the plain XML message to
> your service. This could only handle OMElements as parameters. See
> here [2] more details.
>
> You can extend any of the Abstract*in/outMR's [3] depending on your
> MEP (Message exchange pattern)... or you can simply extend the
> AbstractMessageReceiver..
>
> Thanks,
> Thilina
>
> [1] http://ws.apache.org/axis2/1_1/pojoguide.html
> [2] http://ws.apache.org/axis2/1_1/xmlbased-server.html
>
[3]http://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_1/modules/kernel/src/org/apache/axis2/receivers/
>
> On 12/31/06, falom <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > What is the fundemental difference between RPCMessageReceiver and
> > RawXMLMessageReceiver? How should i choose to use them, and if i want
to
> > write my own msgreceiver then which one i should derive from?
> >
> > falom
> >
> >
> >  __
> > 赶快注册雅虎超大容量免费邮箱?
> > http://cn.mail.yahoo.com
>
>
> --
> Thilina Gunarathne
> WSO2, Inc.; http://www.wso2.com/
> Home page: http://webservices.apache.org/~thilina/
> Blog: http://thilinag.blogspot.com/
>

[Axis2] How to enable log4j logging in axis2

[falom]

Someone please help me to setup log4j logging in axis2. Does the axis2.war 
distribution include all the necessary jar to enable log4j logging?

falom

 __
赶快注册雅虎超大容量免费邮箱?
http://cn.mail.yahoo.com

Re: MTOM

[Stefan Kok]

Thanks Thilina

Will try your advice will let you know what the outcome is.

Regards
Stefan.


On Sat, 2006-12-30 at 08:58 +0600, Thilina Gunarathne wrote:
> Thilina
-- 
Stefan Kok <[EMAIL PROTECTED]>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: No REST for axis2 v1.1

[Deepal Jayasinghe]

None of the phases are hard coded , all of them are listed in axis2.xml.
You can change or add phases using the axis2.xml

Thanks
Deepal

Martin Gainty wrote:

> Hi Manoj
>  
> I looked in org.apache.axis2.phasereolver.PhaseMetaData.java
> and could'nt see accomodation for the phases
> Security
> Transport (although I see accomodation for uppercase TRANSPORT)
> OperationInPhase
> OperationOutPhase
> soapMonitorPhase
>  
> (these phases are defined in my copy of axis2.xml)
>  
> Thanks!
> ---
>
> 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:* Manoj Khangaonkar 
> *To:* Martin Gainty 
> *Sent:* Sunday, December 31, 2006 6:10 PM
> *Subject:* Re: No REST for axis2 v1.1
>
> Actually the URL is case sensitive
>  
> It should be
>
> http://127.0.0.1:8080/axis2/rest/Version/getVersion
>  
> Version is with a capital V.
>  
> There will not be a rest folder.
>  
> But if you look in the web.xml for axis2.war, you will notice that
>  
> the url /rest/*
> is handled by AxisRESTServlet.
>  
> Mj
>
>  
> On 12/31/06, *Martin Gainty* <[EMAIL PROTECTED]
> > wrote:
>
> yes I Grabbed the latest war and thankfully it deploys and
> lists version as 'available service'
> I am curious of the folder name axis2- (instead of axis2) for
> the Axis2 webapp. Is there a reason for this?
>  
> Also there is no 'rest' folder which is created with this new
> webapp (so http://127.0.0.1:8080/axis2/rest/version/getVersion 
> so it fails with
> Dec 31, 2006 3:25:47 PM
> org.apache.axis2.transport.http.AxisRESTServlet doGet
> SEVERE: org.apache.axis2.AxisFault: I can not find a service
> for this request to be serviced. Check the WSDL and the
> request URI;
>  
> Thx,
> M-
> 
> ---
>
> 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:* Manoj Khangaonkar 
> *To:* axis-user@ws.apache.org
>  ; Martin Gainty
> 
> *Sent:* Sunday, December 31, 2006 12:04 PM
> *Subject:* Re: No REST for axis2 v1.1
>
>  
> Martin,
>  
> What exactly are you trying to do ?
>  
> According to the user guide ,
>  
> "Web service request arriving via GET assumes REST."
>  
> and if you invoke the default version web services as
>  
> http://127.00.1:8080/axis2/rest/version/getVersion
>  from
> your browser , you should see a response as shown
> in the user guide.
>  
> This needs to work right out of the box with no configuration.
>  
> On app

Re: services.xml

[Deepal Jayasinghe]

Hi Vasil ;

We have a schema file for services.xml in the xdoc directory in the svn
(xdocs\1_1\resources\schemas) , but it is not up to date with the recent
changes. I will make those changes and commit them.

Thanks
Deepal

> Hi Yamini,
>
> Thank You for the reply.
>
> What I am looking for is a really complete services.xml spec or a
> schema definition.
>
> Best regards,
>   Vasil
>
> On 12/28/06, * Hemanth, Yamini (MSAS Sys Dev IBD)*
> <[EMAIL PROTECTED]
> > wrote:
>
>
> Hi Vasil,
>
>
> Please find below the description of services.xml file.
>
>
>  
>
> * Writing services.xml
>
> The description of services are specified using services.xml. Each
> service archive file needs to have a services.xml in order to be a
> valid service and it should be available in the META-INF directory
> of the archive file. A very simple services.xml is shown below:
>
>
>
> The description of the service
>
> 
>   HTTP
>
>
> 
>
> 
>
>http://www.w3.org/2004/08/wsdl/in-out
> "
> 
> class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
>
> 
> 
>org.apache.axis2.sample.echo.EchoImpl
>
> 
>Mapping to action
>
>
> class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
>
>  
>
> *name*: The service name will be the name of the archive file, if
> the .aar file contains only one service, or else the name of the
> service will be the name given by the name attribute.
>
> *scope*: (Optional Attribute) The time period in which runtime
> information of deployed services will be available. Scope is of
> several types- "Application", "SOAPSession", "TransportSession",
> "Request". The default value (if you dont put any value) will be
> "Request"
>
> *class*: (Optional attribute) To specify the full qualified name
> of the service lifecycle implementation class. ServiceLifeCycle
> class is usefull when you want to do some tasks when the system
> start and when it shutdowns.
>
> *targetNamespace*: (Optional Attribute) Target name space of the
> service, and this value will be used when generating the wsdl , if
> you do not specify this value , then the value will be calculated
> from the package name of the service impl class
>
> *description*: This is an optional element if you want to display
> any description about the service via Axis2 web-admin module, then
> the description can be specified here.
>
> *transports* : The transports that the service is going to be
> exposed to. This is an optional element. If the transport element
> is not present then the service will be exposed in all the
> transports available in the system. The transport child element is
> there to specify the transport prefix (the name of the transport
> specified in axis2.xml).
>
> *parameters:* A services.xml can have any number of top level
> parameters and all the specified parameters will be transformed
> into service properties in the corresponding AxisService. There is
> a compulsory parameter in a services.xml called ServiceClass which
> specifies the java class which really does the job and the class
> will be loaded by the MessageReceiver.
>
> *operations :* If the service impl class is java, then all the
> public methods in that service will be exposed and if the user
> wants to override it then he has to add the "operation" tag and
> override it. In the case of non-Java or if you do not have a
> service class, then all the operations the user wants to expose by
> the service has to be indicated in the services.xml and the
> correct way of specifying is as follows:
>
>
>
> class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver
>"/>
>
>
> The only compulsory attribute here is "name", which represents the
> operation name that is going to be exposed. Any operation can
> contain module references as well as any number of parameters. The
> most interesting thing is that one can register custom message
> receivers per operation, then the registered message receiver will
> be the message receiver for the corresponding operation. If one
> does not specify the message receiver, then the default message
> receiver will do the job.
>
>  
> Regards,
> ** 
> *Yamini Hemanth *
> 
>  
>
> 
> *From:* Vasil Benov [mailto:[EMAIL PROTECTED]
> ]
> *Sent:* Wednesday, December 27, 2006 2:41 PM
> *To:* axis-user@ws.apache.org 
> *Subject:* services.xml
>
> Hello,
>
> is there a thorough description of the  file.

Re: soap address location

[Deepal Jayasinghe]

Hi Nuno ;

add the following parameter into your services.xml;
true

Thanks
Deepal

> Hi,
>
> The problem is that https was changed to http and  I forgot to tell 
> another thing
>
> https://www.test.com/axis2/services/Test1?wsdl
>
> was  changed to
>
> http://www.test.com*:8080*/axis2/services/Test1
>
> How can I force that wsdl in run time is the same that I created?
>
> Regards
>
>
>
>
> Thilina Gunarathne wrote:
>
>> If the following is what you are getting, then I feel like it's
>> correct..
>> http://www.test.com/axis2/services/Test1
>>
>> What's your desired address location and what you are getting now...
>>
>> Thanks,
>> Thilina
>>
>> On 12/27/06, Nuno Martins <[EMAIL PROTECTED]> wrote:
>>
>>>
>>>  Hi,
>>>
>>> I have deployed some sample secure service in Axis2 in Tomcat.
>>>
>>> When I try to generate WSDL for the service, I find that the soap
>>> address
>>> location is incorrect.
>>>
>>> The query URL is
>>> https://www.test.com/axis2/services/Test1?wsdl
>>> The soap address location is
>>> http://www.test.com/axis2/services/Test1
>>>
>>> How can I change soap address location? Why is changed?
>>>
>>>
>>> Regards
>>>
>>>
>>>
>>>
>>>
>>
>>  
>
>

-- 
Thanks,
Deepal

"The highest tower is built one brick at a time"




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: axis1.2.1 vs axis1.4

[Anne Thomas Manes]

As I said, make sure you run java2wsdl on a class that has debug turned on.

On 12/31/06, Ravi Krishnamurthy <[EMAIL PROTECTED]> wrote:

Hello:
I figured out why I had the problem and it is because in the latest
version I had used axis java2wsdl to get the .wsdd and wsdl files and
that contained element names to be in0, in1.

Wondering what should be done when the java2wsdl is invoked to print the
parameter names as userId, password etc instead of in0, in1. Somehow
both the wsdl and the deploy.wsdd containes in0, in1 instead of the
field names of each element . Would appreciate if someone could give
some pointers on this.

Thanks,
Ravi

Ravi Krishnamurthy wrote:
> Could someone give some pointers on this.
>
> Thanks,
> Ravi
> Ravi Krishnamurthy wrote:
>> Could someone give some pointers on this.
>>
>> Thanks,
>> Ravi
>>
>> Ravi Krishnamurthy wrote:
>>> Hello;
>>> I had published the same webservice in axis 1.2.1 ans now trying it
>>> out with axis 1.4
>>>
>>> The wsdl in 1.2.1 says for a complex type as below in 1.2.1
>>> 
>>>
>>>
>>>
>>>
>>>
>>>   
>>> 
>>>
>>> in 1.4 it shows as below:
>>>
>>> 
>>>
>>>
>>>
>>>
>>>
>>>
>>> 
>>>
>>> What should be done in the service deployment to make sure the
>>> element name is shown as userId and not as in0, in1 etc
>>>
>>> Thanks for your help,
>>> regards,
>>> Ravi
>>>
>>>
>>> -
>>> 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]
>>
>
>
>
> -
> 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]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Modify the SOAP Body before a Stub send it

[Antonio Iossa]

Hi all!

 

I'm new to Axis. I would modify the body of a SOAP message *before* axis 
(client-side) send it to a Web Service.

 

 

First of all, I wrote a simple Echo WS:

 

public class MyServerOne {

 

public String echo(String msg) {

System.out.println("In the WS - Server Side");

return "ECHO: % " + msg + " %";

}

} 

and I deployed it with the following WSDD:

 

http://xml.apache.org/axis/wsdd/"; 
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>

 

  







  



 

 

Further, I developed a simple client-side handler:

 

public class myClientHandler extends BasicHandler {

public void invoke(MessageContext msgContext) throws AxisFault {

try {

SOAPEnvelope env = msgContext.getRequestMessage().

getSOAPEnvelope();



SOAPBody body = env.getBody();



System.out.println("VALUE before: " + 

   body.

  getFirstChild().

  getFirstChild().

  getFirstChild().

  getNodeValue() );

 

//set the new value:

   body.

   getFirstChild().

   getFirstChild().

   getFirstChild().

   setNodeValue("new value");

 

System.out.println("VALUE AFTER: " + 

   body.

  getFirstChild().

  getFirstChild().

  getFirstChild().

  getNodeValue() );

  

} catch (SOAPException ex) {

ex.printStackTrace();

throw new AxisFault("myClientHandler",ex);

} catch (DOMException ex) {

ex.printStackTrace();

 throw new AxisFault("myClientHandler",ex);

}

}

}

 

I deployed the previous handler on the flow with the following WSDD:

 

http://xml.apache.org/axis/wsdd/"; 
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>

 





  





  







 



 

 

 

The output of the client-side handler is the following:

 

VALUE before: Original value

VALUE after: new value

But the SOAP message sent is the following:

 



   http://schemas.xmlsoap.org/soap/envelope/";  
xmlns:xsd="http://www.w3.org/2001/XMLSchema";   
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>

 

http://schemas.xmlsoap.org/soap/encoding/"; 
xmlns:ns1="http://server.wsSamlTest";>

   http://schemas.xmlsoap.org/soap/encoding/";>

 Original value

   



 



 

 

Where I mistake?

 

Thanks all in advance... and happy new year!

 

Antonio

Re: [Axis2] building Axis2

[Deepal Jayasinghe]

Hi Lin ;
Why dont you try again :)
any way pls send me the error report , I can have a look at that.

Thanks
Deepal

>Hello there,
>
>I am new to the list and I just checked out Axis2\trunk\java.   I followed
>this Axis2 development page (http://ws.apache.org/axis2/svn.html) and typed
>'maven' to kick off the build.I am getting the following error when
>attempting to build Axis2 using Maven1.
> 
>
>BUILD FAILED
>
>File.. C:\Documents and
>Settings\Administrator\.maven\cache\maven-multiproje
>
>ct-plugin-1.5-SNAPSHOT\plugin.jelly
>
>Element... maven:reactor
>
>Line.. 227
>
>Column -1
>
>Unable to obtain goal [multiproject:install-callback] -- C:\Documents and
>Settin
>
>gs\Administrator\.maven\cache\maven-test-plugin-1.8.1-SNAPSHOT\plugin.jelly:
>155:
>
>-1:  Test org.apache.axis2.engine.EchoRawXMLMultipleTest failed
>
>Total time   : 17 minutes 47 seconds
>
>Finished at  : Friday, December 22, 2006 1:10:45 PM EST
>
> 
>
>Should I skip test during the build?  Thanks, Lin
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>  
>

-- 
Thanks,
Deepal

"The highest tower is built one brick at a time"



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]