Migration from Axis 1.4 to Axis2

[Matthias.Gaiser]

Hi group,

 

We are currently migrating our web services from Axis 1.4 to Axis 2.

 

In creating web services we start by writing the implementation class.
Then we run the java2wsdl tool to generate a wsdl file from our
implementation of the service in Axis 1.4. After this, we run the
wsdl2java tool to create all server-side code (Skeleton, MessageReceiver
and the classes used by message receiver).

 

Can we now somehow point Axis to our implementation of the service? In
Axis 1.4 our Implementation class implemented the Skeleton. In Axis2
there are comments in the generated Skeleton that we should put our
implementation right here. If we put the implementation there and
generate the web service again we will lose our implementation. Is there
a way to prevent this?

 

Alternatively, what do you suggest is the best way to create a web
service when we start with an implementation class?

 

Thanks,

Matthias.

Generating service.xml with wsdl2java

[Matthias.Gaiser]

Hi all,

 

I am generating the server-side code from a wsdl with wsdl2java which
generates the corresponding java classes and the service.xml.

Now I am changing the service.xml to add some handlers, messagereceiver,
etc.

 

When some methods are added to wsdl, I am generating the code again with
wsdl2java and it replaces my service.xml which means I lose all my
changes of it.

Is there a way to automatically synchronize the old service.xml with the
new one?

 

Thanks,

Matthias.

AW: Generating service.xml with wsdl2java

[Matthias.Gaiser]

Hello Dirk,

 

Thank you for your answer. That is exactly what I want to do. And I
think there are lots of other people out there which have the same
problem or am I wrong?

My question now is if there is a kind of standard way to alter the
default services.xml?

 

This altering of the services.xml may not be an easy task.

 

Regards,

Matthias.

 

 

Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Gesendet: Mittwoch, 20. Februar 2008 15:09
An: axis-user@ws.apache.org
Betreff: RE: Generating service.xml with wsdl2java

 

Hi,

 

I suggest to create an ant-script which alters the 'default'
services.xml so you don't have to change

This manually everytime.

For instance alter the call to the skelton to the implementation

 

Regards

Dirk 

 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: woensdag 20 februari 2008 14:29
To: axis-user@ws.apache.org
Subject: Generating service.xml with wsdl2java

 

Hi all,

 

I am generating the server-side code from a wsdl with wsdl2java which
generates the corresponding java classes and the service.xml.

Now I am changing the service.xml to add some handlers, messagereceiver,
etc.

 

When some methods are added to wsdl, I am generating the code again with
wsdl2java and it replaces my service.xml which means I lose all my
changes of it.

Is there a way to automatically synchronize the old service.xml with the
new one?

 

Thanks,

Matthias.

 

The information transmitted via this e-mail is intended only for the
person or entity to which it is addressed and may contain confidential
and/or privileged material.  Any review, retransmission, dissemination
or other use of, or taking of any action in reliance upon this
information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and
delete the material from any computer.

AW: Generating service.xml with wsdl2java

[Matthias.Gaiser]

Hi,

 

I thought about a solution with an ant script calling an XSLT
transformation to synchronize my old service.xml (with references to
modules) with my new generated one by wsdl2java.

Has anybody done this already? Is there an easier way to do this?

 

In order to provide a generic solution I'd need a xsd or a complete
description of the service.xml. Is there one available somewhere? I only
found some older threads in the mailing list pointing to some path in
the svn repo I couldn't find.

 

Thanks,

Matthias.

 

Von: Gaiser, Matthias 
Gesendet: Mittwoch, 20. Februar 2008 17:17
An: axis-user@ws.apache.org
Betreff: AW: Generating service.xml with wsdl2java

 

Hello Dirk,

 

Thank you for your answer. That is exactly what I want to do. And I
think there are lots of other people out there which have the same
problem or am I wrong?

My question now is if there is a kind of standard way to alter the
default services.xml?

 

This altering of the services.xml may not be an easy task.

 

Regards,

Matthias.

 

 

Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Gesendet: Mittwoch, 20. Februar 2008 15:09
An: axis-user@ws.apache.org
Betreff: RE: Generating service.xml with wsdl2java

 

Hi,

 

I suggest to create an ant-script which alters the 'default'
services.xml so you don't have to change

This manually everytime.

For instance alter the call to the skelton to the implementation

 

Regards

Dirk 

 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: woensdag 20 februari 2008 14:29
To: axis-user@ws.apache.org
Subject: Generating service.xml with wsdl2java

 

Hi all,

 

I am generating the server-side code from a wsdl with wsdl2java which
generates the corresponding java classes and the service.xml.

Now I am changing the service.xml to add some handlers, messagereceiver,
etc.

 

When some methods are added to wsdl, I am generating the code again with
wsdl2java and it replaces my service.xml which means I lose all my
changes of it.

Is there a way to automatically synchronize the old service.xml with the
new one?

 

Thanks,

Matthias.

 

The information transmitted via this e-mail is intended only for the
person or entity to which it is addressed and may contain confidential
and/or privileged material.  Any review, retransmission, dissemination
or other use of, or taking of any action in reliance upon this
information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and
delete the material from any computer.

[Axis2] Problem with handler and services.xml

[Matthias.Gaiser]

Hi all,

 

I am writing my own module, containing a handler.

 

For this, I have completed following steps.

- I have specified the handler for a custom phase (in the InFlow) in the
module.xml

- I have added the custom phase to the axis2.xml (in the InFlow)

- I have added a  to the services.xml

 

The module is being loaded, but the problem is that my handler is not
executed when I call my service.

 

It worked when I directly specified the handler in the custom phase in
the axis2.xml, but that is not the way it is supposed to be done, is it?

 

Any ideas?

 

Thanks,

Matthias.

 

AW: [Axis2] Problem with handler and services.xml

[Matthias.Gaiser]

Hi Deepal,

I have created an axis2 project with eclipse which arranged the axis2 folder 
structure for me. By placing my module in the "WEB-INF/modules"-folder I deploy 
it to axis2.
When I use the Axis2 Admin Console I can see my module engaged for my 
service.But it still does not work. That is the weird point I do not get in my 
mind, everything seems to be in place...

Any more help?

Thank you,
Matthias.

-Ursprüngliche Nachricht-
Von: Deepal jayasinghe [mailto:[EMAIL PROTECTED] 
Gesendet: Freitag, 7. März 2008 07:53
An: axis-user@ws.apache.org
Betreff: Re: [Axis2] Problem with handler and services.xml

[EMAIL PROTECTED] wrote:
>
> Hi all,
>
>  
>
> I am writing my own module, containing a handler.
>
>  
>
> For this, I have completed following steps.
>
> - I have specified the handler for a custom phase (in the InFlow) in 
> the module.xml
>
> - I have added the custom phase to the axis2.xml (in the InFlow)
>
> - I have added a  to the services.xml
>
>  
>
> The module is being loaded, but the problem is that my handler is not 
> executed when I call my service.
>
>  
>
> It worked when I directly specified the handler in the custom phase in 
> the axis2.xml, but that is not the way it is supposed to be done, is it?
>
>  
>
> Any ideas?
>
If you are using axis2.war as your deployment mechanism then  from the 
administration console you can see whether you handler is there or not. 
Please check that and confirm first , if it is there then let's see what 
we can do

Thank you,
Deepal
>
>  
>


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

AW: eclipse and axis2

[Matthias.Gaiser]

Hi Michael,

I am not using Axis2 for a long time, but I'm using eclipse for quite a while. 
So all other users, please correct me if I'm wrong.

What version of eclipse do you have installed? I assume it is a current version 
with Web Tools plugin. I installed the eclipse Version for Java EE Developers.

The easiest way I encountered to setup an axis2 eclipse project is first 
telling eclipse where your Axis2 distribution is. Therefore set the Axis2 
Runtime location to your axis2 installation directory (in eclipse: Window -> 
Preferences -> Web Services -> Axis2 Preferences).
Now you can create a new dynamic web project with an axis2 nature which 
arranges all necessary libraries for you.

The other problem why eclipse does not deploy your axis2.war is probably the 
feature of eclipse that it does not modify your tomcat installation in standard 
mode. Therefore it does not deploy your webapps installed to this tomcat.
You can change this setting when you doubleclick on your server and change the 
"Server Locations" to "Use Tomcat Installation". That way your axis2.war should 
be deployed.

HTH,
Matthias.

-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Michael Potter
Gesendet: Donnerstag, 6. März 2008 23:10
An: axis-user@ws.apache.org
Betreff: eclipse and axis2

Axis2 Crew,

I am trying to use Eclipse to edit existing webservices that are in
the form of .aar files.

At this point I have tomcat successfully installed and working with Eclipse.
The problem I am having is getting Axis2 installed and working with Eclipse.

I downloaded Axis2 and built the axis2.war file.
I moved the axis2.war into webapps directory.

I expected the .war file to expand when I started tomcat.  I start
tomcat using the context sensitive menu in Eclipse.

Is there something special about the way Eclipse starts tomcat where
it does not expand a .war file?

Can anyone give me some hints about other things I may run into when
using axis2 with Eclipse?

-- 
Michael Potter

-
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]

AW: AW: [Axis2] Problem with handler and services.xml

[Matthias.Gaiser]

Hi again,

Thank you for your efforts, Deepal.
Yes, I am sure the service is called. I placed a breakpoint in the called 
method and the breakpoint is reached. I even get the answer of my service. I 
also placed a breakpoint inside the handler and it is not reached, 
unfortunately.

I attached my axis2.xml, module.xml and services.xml. Maybe I misconfigured 
something you might check.

Thanks,
Matthias.


-Ursprüngliche Nachricht-
Von: Deepal Jayasinghe [mailto:[EMAIL PROTECTED] 
Gesendet: Freitag, 7. März 2008 09:28
An: axis-user@ws.apache.org
Betreff: Re: AW: [Axis2] Problem with handler and services.xml


> Hi Deepal,
>
> I have created an axis2 project with eclipse which arranged the axis2 folder 
> structure for me. By placing my module in the "WEB-INF/modules"-folder I 
> deploy it to axis2.
> When I use the Axis2 Admin Console I can see my module engaged for my 
> service.But it still does not work. That is the weird point I do not get in 
> my mind, everything seems to be in place...
>
> Any more help?
>   
Are you sure you are invoking the service , may be something else is 
happening (throwing an exception before reaching your handler).

Thank you,
Deepal



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







true
false
false
false





3



false





false

admin
axis2
























true


false
























 
http://www.w3.org/2004/08/wsdl/in-only";
 class="org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver"/>
http://www.w3.org/2004/08/wsdl/in-out";
 class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
http://www.w3.org/2006/01/wsdl/in-only";
 class="org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver"/>
http://www.w3.org/2006/01/wsdl/in-out";
 class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>




























8080




























	
>












HTTP/1.1
chunked






HTTP/1.1
chunked


 














   
































 
 















>
















 
 



























   



   

   

   

   

   

   

   





		

http://www.w3.org/ns/wsdl/in-out"; class="com.xxx.TESTServiceMessageReceiverInOut"/>

com.xxx.TESTServiceSkeleton
true
true
http://www.w3.org/ns/wsdl/in-out";>
urn:login
urn:loginResponse

http://www.w3.org/ns/wsdl/in-out";>
urn:invoke
urn:invokeResponse

http://www.w3.org/ns/wsdl/in-out";>
urn:logout
urn:logoutResponse



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

AW: [Axis2] Problem with handler and services.xml

[Matthias.Gaiser]

Hi,

Thanks for checking my description.
I tried engaging it globally with a  in the axis2.xml, but it 
is still not working.
The only way it worked was when I specified it directly in the phase (in 
axis2.xml) like:

... other phases ...






I also compared my handler again to the handler of the SOAPMonitor module and 
did discover that in the axis admin console, my module is recognized correctly, 
but there is no handler if I click on "Operation Specific Chains" to view all 
the handlers my service is using.
Does this give any more clues to you?

Otherwise I create a JIRA, would you tell me please what files I shall include 
for this?

Thanks,
Matthias.


> Hi ,
> 
> I looked your description carefully but I did not find any problem on
> those files. Shall I suggest you one more thing , rather than engaging
> the module to the service try to engage globally and see whether it
> works. Or else please create a JIRA and attach all the necessary stuff
> for me to regenerate the issue.
> 
> Thank you,
> Deepal
> > Hi again,
> >
> > Thank you for your efforts, Deepal.
> > Yes, I am sure the service is called. I placed a breakpoint in the
> called method and the breakpoint is reached. I even get the answer of
> my service. I also placed a breakpoint inside the handler and it is not
> reached, unfortunately.
> >
> > I attached my axis2.xml, module.xml and services.xml. Maybe I
> misconfigured something you might check.
> >
> > Thanks,
> > Matthias.
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]
> > Gesendet: Freitag, 7. März 2008 09:28
> > An: axis-user@ws.apache.org
> > Betreff: Re: AW: [Axis2] Problem with handler and services.xml
> >
> >
> >
> >> Hi Deepal,
> >>
> >> I have created an axis2 project with eclipse which arranged the
> axis2 folder structure for me. By placing my module in the "WEB-
> INF/modules"-folder I deploy it to axis2.
> >> When I use the Axis2 Admin Console I can see my module engaged for
> my service.But it still does not work. That is the weird point I do not
> get in my mind, everything seems to be in place...
> >>
> >> Any more help?
> >>
> >>
> > Are you sure you are invoking the service , may be something else is
> > happening (throwing an exception before reaching your handler).
> >
> > Thank you,
> > Deepal
> >
> >
> >
> > -
> > 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]

AW: [Axis2] Problem with handler and services.xml

[Matthias.Gaiser]

Hi Martin,

I can confirm all your questions, but still do not have a working handler.
I am happy to provide you with any more details, if it helps.

Thanks,
Matthias.

> Von: Martin Gainty [mailto:[EMAIL PROTECTED]
> Gesendet: Freitag, 7. März 2008 14:45
> An: Gaiser, Matthias
> Cc: axis-user@ws.apache.org
> Betreff: Re: [Axis2] Problem with handler and services.xml
> 
> Good Morning Matthias
> 
> Can you confirm the module is located in /WEB-INF/modules folder?
Yes.

> can you confirm the modules.list contains the entry for the name of
> module?
Yes.

> 
> Module Engaged to service
> In the /META-INF/services.xml can you view the service entry to include
> the
> module name e.g.   ?
Yes.

> 
> Global available Modules
> Can you see your module ref  in
> /WEB-INF/conf/axis2.xml ?
Yes.

> 
> ?
> Martin-
> - Original Message -
> From: <[EMAIL PROTECTED]>
> To: 
> Sent: Friday, March 07, 2008 2:50 AM
> Subject: AW: [Axis2] Problem with handler and services.xml
> 
> 
> > Hi Deepal,
> >
> > I have created an axis2 project with eclipse which arranged the axis2
> folder structure for me. By placing my module in the
> "WEB-INF/modules"-folder I deploy it to axis2.
> > When I use the Axis2 Admin Console I can see my module engaged for my
> service.But it still does not work. That is the weird point I do not
> get in
> my mind, everything seems to be in place...
> >
> > Any more help?
> >
> > Thank you,
> > Matthias.
> >
> > -Ursprüngliche Nachricht-
> > Von: Deepal jayasinghe [mailto:[EMAIL PROTECTED]
> > Gesendet: Freitag, 7. März 2008 07:53
> > An: axis-user@ws.apache.org
> > Betreff: Re: [Axis2] Problem with handler and services.xml
> >
> > [EMAIL PROTECTED] wrote:
> > >
> > > Hi all,
> > >
> > >
> > >
> > > I am writing my own module, containing a handler.
> > >
> > >
> > >
> > > For this, I have completed following steps.
> > >
> > > - I have specified the handler for a custom phase (in the InFlow)
> in
> > > the module.xml
> > >
> > > - I have added the custom phase to the axis2.xml (in the InFlow)
> > >
> > > - I have added a  to the services.xml
> > >
> > >
> > >
> > > The module is being loaded, but the problem is that my handler is
> not
> > > executed when I call my service.
> > >
> > >
> > >
> > > It worked when I directly specified the handler in the custom phase
> in
> > > the axis2.xml, but that is not the way it is supposed to be done,
> is it?
> > >
> > >
> > >
> > > Any ideas?
> > >
> > If you are using axis2.war as your deployment mechanism then  from
> the
> > administration console you can see whether you handler is there or
> not.
> > Please check that and confirm first , if it is there then let's see
> what
> > we can do
> >
> > Thank you,
> > Deepal
> > >
> > >
> > >
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >

AW: [Axis2] Problem with handler and services.xml

[Matthias.Gaiser]

Hello again,

I now created an issue in JIRA with my module to try and the axis2.xml 
configuration.
https://issues.apache.org/jira/browse/AXIS2-3588

Could please someone of you test my module or have a look at it what I am doing 
wrong?
The module is being loaded, but the handler is never being invoked.

Thanks,
Matthias.

> -Ursprüngliche Nachricht-
> Von: Gaiser, Matthias
> Gesendet: Freitag, 7. März 2008 16:41
> An: 'axis-user@ws.apache.org'
> Betreff: AW: [Axis2] Problem with handler and services.xml
> 
> Hi Martin,
> 
> I can confirm all your questions, but still do not have a working
> handler.
> I am happy to provide you with any more details, if it helps.
> 
> Thanks,
> Matthias.
> 
> > Von: Martin Gainty [mailto:[EMAIL PROTECTED]
> > Gesendet: Freitag, 7. März 2008 14:45
> > An: Gaiser, Matthias
> > Cc: axis-user@ws.apache.org
> > Betreff: Re: [Axis2] Problem with handler and services.xml
> >
> > Good Morning Matthias
> >
> > Can you confirm the module is located in /WEB-INF/modules folder?
> Yes.
> 
> > can you confirm the modules.list contains the entry for the name of
> > module?
> Yes.
> 
> >
> > Module Engaged to service
> > In the /META-INF/services.xml can you view the service entry to
> include
> > the
> > module name e.g.   ?
> Yes.
> 
> >
> > Global available Modules
> > Can you see your module ref  in
> > /WEB-INF/conf/axis2.xml ?
> Yes.
> 
> >
> > ?
> > Martin-
> > - Original Message -
> > From: <[EMAIL PROTECTED]>
> > To: 
> > Sent: Friday, March 07, 2008 2:50 AM
> > Subject: AW: [Axis2] Problem with handler and services.xml
> >
> >
> > > Hi Deepal,
> > >
> > > I have created an axis2 project with eclipse which arranged the
> axis2
> > folder structure for me. By placing my module in the
> > "WEB-INF/modules"-folder I deploy it to axis2.
> > > When I use the Axis2 Admin Console I can see my module engaged for
> my
> > service.But it still does not work. That is the weird point I do not
> > get in
> > my mind, everything seems to be in place...
> > >
> > > Any more help?
> > >
> > > Thank you,
> > > Matthias.
> > >
> > > -Ursprüngliche Nachricht-
> > > Von: Deepal jayasinghe [mailto:[EMAIL PROTECTED]
> > > Gesendet: Freitag, 7. März 2008 07:53
> > > An: axis-user@ws.apache.org
> > > Betreff: Re: [Axis2] Problem with handler and services.xml
> > >
> > > [EMAIL PROTECTED] wrote:
> > > >
> > > > Hi all,
> > > >
> > > >
> > > >
> > > > I am writing my own module, containing a handler.
> > > >
> > > >
> > > >
> > > > For this, I have completed following steps.
> > > >
> > > > - I have specified the handler for a custom phase (in the InFlow)
> > in
> > > > the module.xml
> > > >
> > > > - I have added the custom phase to the axis2.xml (in the InFlow)
> > > >
> > > > - I have added a  to the services.xml
> > > >
> > > >
> > > >
> > > > The module is being loaded, but the problem is that my handler is
> > not
> > > > executed when I call my service.
> > > >
> > > >
> > > >
> > > > It worked when I directly specified the handler in the custom
> phase
> > in
> > > > the axis2.xml, but that is not the way it is supposed to be done,
> > is it?
> > > >
> > > >
> > > >
> > > > Any ideas?
> > > >
> > > If you are using axis2.war as your deployment mechanism then  from
> > the
> > > administration console you can see whether you handler is there or
> > not.
> > > Please check that and confirm first , if it is there then let's see
> > what
> > > we can do
> > >
> > > Thank you,
> > > Deepal
> > > >
> > > >
> > > >
> > >
> > >
> > > ---
> --
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >

AW: [Axis2] Problem with handler and services.xml

[Matthias.Gaiser]

Hello,

I just want to post the solution of my issue.
I configured everything in the right places, but my module.xml was incorrect. I 
did not pay enough attention to the case sensitivity of the tag names for 
"InFlow", "OutFlow", "InFaultFlow" and "OutFaultFlow".
I followed the axis2 1.2 module guide which used slightly different tags for 
this instead of the axis2 1.3 module guide.

Thanks for your help, guys (especially Michele).
Matthias.

> -Ursprüngliche Nachricht-
> Von: Gaiser, Matthias
> Gesendet: Montag, 10. März 2008 15:55
> An: axis-user@ws.apache.org
> Betreff: AW: [Axis2] Problem with handler and services.xml
> 
> Hello again,
> 
> I now created an issue in JIRA with my module to try and the axis2.xml
> configuration.
> https://issues.apache.org/jira/browse/AXIS2-3588
> 
> Could please someone of you test my module or have a look at it what I
> am doing wrong?
> The module is being loaded, but the handler is never being invoked.
> 
> Thanks,
> Matthias.
> 
> > -Ursprüngliche Nachricht-
> > Von: Gaiser, Matthias
> > Gesendet: Freitag, 7. März 2008 16:41
> > An: 'axis-user@ws.apache.org'
> > Betreff: AW: [Axis2] Problem with handler and services.xml
> >
> > Hi Martin,
> >
> > I can confirm all your questions, but still do not have a working
> > handler.
> > I am happy to provide you with any more details, if it helps.
> >
> > Thanks,
> > Matthias.
> >
> > > Von: Martin Gainty [mailto:[EMAIL PROTECTED]
> > > Gesendet: Freitag, 7. März 2008 14:45
> > > An: Gaiser, Matthias
> > > Cc: axis-user@ws.apache.org
> > > Betreff: Re: [Axis2] Problem with handler and services.xml
> > >
> > > Good Morning Matthias
> > >
> > > Can you confirm the module is located in /WEB-INF/modules folder?
> > Yes.
> >
> > > can you confirm the modules.list contains the entry for the name of
> > > module?
> > Yes.
> >
> > >
> > > Module Engaged to service
> > > In the /META-INF/services.xml can you view the service entry to
> > include
> > > the
> > > module name e.g.   ?
> > Yes.
> >
> > >
> > > Global available Modules
> > > Can you see your module ref  in
> > > /WEB-INF/conf/axis2.xml ?
> > Yes.
> >
> > >
> > > ?
> > > Martin-
> > > - Original Message -
> > > From: <[EMAIL PROTECTED]>
> > > To: 
> > > Sent: Friday, March 07, 2008 2:50 AM
> > > Subject: AW: [Axis2] Problem with handler and services.xml
> > >
> > >
> > > > Hi Deepal,
> > > >
> > > > I have created an axis2 project with eclipse which arranged the
> > axis2
> > > folder structure for me. By placing my module in the
> > > "WEB-INF/modules"-folder I deploy it to axis2.
> > > > When I use the Axis2 Admin Console I can see my module engaged
> for
> > my
> > > service.But it still does not work. That is the weird point I do
> not
> > > get in
> > > my mind, everything seems to be in place...
> > > >
> > > > Any more help?
> > > >
> > > > Thank you,
> > > > Matthias.
> > > >
> > > > -Ursprüngliche Nachricht-
> > > > Von: Deepal jayasinghe [mailto:[EMAIL PROTECTED]
> > > > Gesendet: Freitag, 7. März 2008 07:53
> > > > An: axis-user@ws.apache.org
> > > > Betreff: Re: [Axis2] Problem with handler and services.xml
> > > >
> > > > [EMAIL PROTECTED] wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > >
> > > > >
> > > > > I am writing my own module, containing a handler.
> > > > >
> > > > >
> > > > >
> > > > > For this, I have completed following steps.
> > > > >
> > > > > - I have specified the handler for a custom phase (in the
> InFlow)
> > > in
> > > > > the module.xml
> > > > >
> > > > > - I have added the custom phase to the axis2.xml (in the
> InFlow)
> > > > >
> > > > > - I have added a  to the services.xml
> > > > >
> > > > >
> > > > >
> > > > > The module is being loaded, but the problem is that my handler
> is
> > > not
> > > > > executed when I call my service.
> > > > >
> > > > >
> > > > >
> > > > > It worked when I directly specified the handler in the custom
> > phase
> > > in
> > > > > the axis2.xml, but that is not the way it is supposed to be
> done,
> > > is it?
> > > > >
> > > > >
> > > > >
> > > > > Any ideas?
> > > > >
> > > > If you are using axis2.war as your deployment mechanism then
> from
> > > the
> > > > administration console you can see whether you handler is there
> or
> > > not.
> > > > Please check that and confirm first , if it is there then let's
> see
> > > what
> > > > we can do
> > > >
> > > > Thank you,
> > > > Deepal
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > -
> --
> > --
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >

RE: How do I learn which Axis2 JARs have which classes?

[Matthias.Gaiser]

If it is still valuable to anyone. If you use eclipse as your developing IDE. 
It has a nice feature how you can lookup classes.
Just press the keys Strg+Shift+T (alternatively open the Menu "Navigate" --> 
"Open Type") and eclipse opens a "Open Type" dialog. There you can start typing 
your classname and see all matching classes, including their full qualified 
name and the jar they belong to.

Matthias.

> -Ursprüngliche Nachricht-
> Von: Nate Roe [mailto:[EMAIL PROTECTED]
> Gesendet: Freitag, 14. März 2008 19:36
> An: 'axis-user@ws.apache.org'
> Betreff: RE: How do I learn which Axis2 JARs have which classes?
> 
> 
> The difficulty is in finding a file from amongst several JARs.
> (basically foreach a directory's JARs, and then -tvf them.)
> 
> I've written a small utility that serves me for this.  See the attached
> file.
> 
> - Nate
> 
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
> Jeff Greif
> Sent: Friday, March 14, 2008 10:52 AM
> To: axis-user@ws.apache.org
> Subject: Re: How do I learn which Axis2 JARs have which classes?
> 
> Use the jar tool that comes with (Sun) java:
> 
> jar tvf xxx.jar
> 
> and is documented via a on the main page of the JDK documentation
> (under Tools).
> 
> You can combine this with other Unix-style shell tools if you have the
> cygwin tools on your windows box:
> 
> jar tvf xxx.jar | grep '*MetaData*
> 
> to look for certain classes or packages by some part of their name.
> 
> You can also edit the jar with the Emacs editor, which shows you a
> listing of files.
> 
> Jeff
> 
> On Fri, Mar 14, 2008 at 10:17 AM, Kraus, David
> <[EMAIL PROTECTED]> wrote:
> > I haven't hacked the registry. I have used WinZip to open jar files
> as
> > zip files. Not sure whether this creates a file association which
> helps.
> >
> >  -Original Message-
> >  From: Nate Roe [mailto:[EMAIL PROTECTED]
> >  Sent: Friday, March 14, 2008 10:04 AM
> >  To: 'axis-user@ws.apache.org'
> >  Subject: RE: How do I learn which Axis2 JARs have which classes?
> >
> >
> >  I don't think this method will work unless you hack the Windows
> > registry  to tell it that a JAR is a ZIP.  Maybe.
> >
> >  I guess another way is to build a script (or a Java program) to do
> > the  looking.
> >
> >  - Nate
> >
> >  -Original Message-
> >  From: Kraus, David [mailto:[EMAIL PROTECTED]
> >  Sent: Friday, March 14, 2008 8:57 AM
> >  To: axis-user@ws.apache.org
> >  Subject: RE: How do I learn which Axis2 JARs have which classes?
> >
> >  Hmmm...I didn't start using this method until about a year ago. My
> OS
> > is  Windows XP Professional. Not sure if previous windows platforms
> > worked  in the same way when doing file searches.
> >
> >  I tried the same thing you mentioned:
> >
> >  Navigated to: D:\axis2-1.2\lib
> >  all files and folders: *.jar
> >  a word or phrase in the file file: org/apache
> >
> >  ...and I got a match on a large number of jar files...
> >
> >  The jarfinder website also provides a way to look up jar files, but
> > didn't seem to know axis2 jars.
> >
> >
> >  -Original Message-
> >  From: learn_n_share [mailto:[EMAIL PROTECTED]
> >  Sent: Thursday, March 13, 2008 10:35 PM
> >  To: axis-user@ws.apache.org
> >  Subject: RE: How do I learn which Axis2 JARs have which classes?
> >
> >
> >  Hi Dave
> >
> >  I have the same doubt. I tried using your guidelines but couldn't
> > succeed.
> >  Please guide me where i m wrong.
> >
> >  i opened the C:\axis2\lib folder.
> >  i pressed the serach button on the tool bar to open the search
> window
> > on  the  left hand side of the current window.
> >  clicked the "all files and folders" option  entered "*.jar" in "all
> > or part of filename"
> >  entered "org/apache" in "a word or phrase in the file file"
> >  "look in" to be "axis2\lib"
> >  but couldn't get the results
> >  guide me the correct way
> >
> >  regards
> >  --
> >  View this message in context:
> >
> > http://www.nabble.com/How-do-I-learn-which-Axis2-JARs-have-which-
> class
> > es
> >  --tp16042438p16044726.html
> >  Sent from the Axis - User mailing list archive at Nabble.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]
> >
> >
> >  
> -
> >  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 unsu

[Axis2] Renaming ServiceGroupId

[Matthias.Gaiser]

Hi all,

 

I am currently getting started in the session handling with axis2. When
I am using the soapsession approach, axis2 generates the following
header in the SOAP response.

http://ws.apache.org/namespaces/axis2";>...

 

Now what I want to do is customizing this tag in order to reflect that
this Id belongs to my application. I want to rename it  to eg:

http://example.com";>...

 

Is there any configurative way to do this which does not involve
actually changing the axis2 sources?

 

Thanks in advance,

Matthias.

[Axis2][1.3] soapsession management with serviceGroup

[Matthias.Gaiser]

Hi all,

I have read different mailings in this list, but they did not answer my
questions about soapsessions.

Here is my scenario. I have two services deployed in a single
servicegroup. I now have setup a client which calls the services and I
can see that the ServiceGroupContext stays the same in the different
services.

So here are my two questions:
1. Where am I supposed to store my session information? Is it the
ServiceGroupContext? Am I supposed to create a SessionContext and store
in the ServiceGroupContext?

2. I want to do some tidying up at the termination of the soapsession. I
could use the destroy() methods in each service for the service-related
stuff. But where is the right place to tidy up resources belonging to
the whole serviceGroup, eg. database connections used by both services*?
Similarly, I want to do some initialization for the whole service group.

Can someone please help me or point me to a good session handling
description?

Thanks,
Matthias.

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

RE: [Axis2][1.3] soapsession management with serviceGroup

[Matthias.Gaiser]

Thanks for the fast answer, Deepal.
> > Hi all,
> >
> > I have read different mailings in this list, but they did not answer
my
> > questions about soapsessions.
> >
> 
> > Here is my scenario. I have two services deployed in a single
> > servicegroup. I now have setup a client which calls the services and
I
> > can see that the ServiceGroupContext stays the same in the different
> > services.
> >
> Ok.
> > So here are my two questions:
> > 1. Where am I supposed to store my session information?
> It depends , if you want to share resources across your services in
the
> service group then store in the servicegroupcontext else store in the
> service context.
> > Is it the
> > ServiceGroupContext? Am I supposed to create a SessionContext and
store
> > in the ServiceGroupContext?
> >
> If you store in ServiceGroupContext the all the services in that group
> can access that , where as if you store that in ServiceContext only
> that
> corresponding service can access that. SessionContext is totally
> different thing it only uses for transport session , for soap session
> you get NULL as SessionContext value.

Thank you for clarifying that the SessionContext only belongs to the
transport session scope. In order to store information
servicegroup-wide, I'll now use the ServiceGroupContext.

> > 2. I want to do some tidying up at the termination of the
soapsession.
> At the moment we do not have a way to do that. Your session get
> terminated automatically unless you touch your services for sometime
> (that time is configurable in axis2.xml)

Ok, this would be a very practicable feature for a newer release. I'll
open a feature request in JIRA or have a look if there is already one.

> > I
> > could use the destroy() methods in each service for the service-
related
> > stuff. But where is the right place to tidy up resources belonging
to
> > the whole serviceGroup, eg. database connections used by both
services*?
> > Similarly, I want to do some initialization for the whole service
group.
> >
> For that there is something called ServiceLifeCycle class , that will
> help you to do that , please have a following article to get some
> understanding about that.
> 
> http://www.developer.com/db/article.php/3735771

Thank you for your article. It might be helpful in scenarios where I
need initialization for a service which is meant to be application-wide.
In order to solve my problem with tidying up session-related resources
for a servicegroup, I am thinking about calling an external tidyUp()
method in the destroy() method of each service and store in the
serviceGroupContext if it is still necessary to call the tidyUp()
method, so that this is called only once.
What do you think about it? Would that be a good solution? How are other
people out there realizing such scenarios?

Thanks,
Matthias.




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

[Axis 2.1.3] Session gets destroyed in soapsession scope

[Matthias.Gaiser]

Hi group,

 

I am currently implementing a stateful web service based on the
soapsession scope configuration.

 

Now, I can call my webservice and it returns a sessionid. When I call
the webservice a second time with this session id. Then at first the
current session (the one I want to get) is destroyed and I get a SOAP
fault, telling me:

"Unable to find corresponding context for the serviceGroupId:
urn:uuid:36645CAA76105FFF541211205513801".

 

Why does it destroy the session at first hand? Does anybody have some
hints about or a solution for this?

 

Thank you,

Matthias.

AW: [Axis 2.1.3] Session gets destroyed in soapsession scope

[Matthias.Gaiser]

Hi Mikelantonio,

 

Thanks for answering.

I am sending a SOAP message (with a WS-Adressing header) to the server
and it returns me a service group id in the WS-Adressing-SOAP-Header.
That is how I retrieve the service group id and I send it then with the
following messages.

The actual retrieval of the servicegroupid when a message arrives is
done through axis2, but somehow my session always gets destroyed.

 

My timeout in the axis2.xml is configured as you described.. 3ms. I
call the service again right after it has been finished, so it can't be
the usual timeout. Any ideas what I have might forgotten?

 

Thanks,

Matthias.

 

Von: Michelantonio Trizio [mailto:[EMAIL PROTECTED] 
Gesendet: Montag, 19. Mai 2008 17:15
An: axis-user@ws.apache.org
Betreff: Re: [Axis 2.1.3] Session gets destroyed in soapsession scope

 

Hi,

how do you retrieve the servicegroupid?
However you must control the following parameter in axis2.xml
3
The value is in milliseconds.

   Mikelantonio

2008/5/19 <[EMAIL PROTECTED]>:

Hi group,

 

I am currently implementing a stateful web service based on the
soapsession scope configuration.

 

Now, I can call my webservice and it returns a sessionid. When I call
the webservice a second time with this session id. Then at first the
current session (the one I want to get) is destroyed and I get a SOAP
fault, telling me:

"Unable to find corresponding context for the serviceGroupId:
urn:uuid:36645CAA76105FFF541211205513801".

 

Why does it destroy the session at first hand? Does anybody have some
hints about or a solution for this?

 

Thank you,

Matthias.




-- 
It's creepy, but here we are, the Pilgrims, the crackpots of our time,
trying to establish our own alternate reality. To build a world out of
rocks and chaos. What it's going to be, I don't know. Even after all
that rushing around, where we've ended up is the middle of nowhere in
the middle of the night. And maybe knowing isn't the point. Where we're
standing right now, in the ruins in the dark, what we build could be
anything. [Choke - Chuck Palahniuk] 

AW: service language

[Matthias.Gaiser]

Hi Christian,

I would also go the same way of the solution. I am a German as well and we had 
the same thing to do with one of our services. I just changed the existing 
service by renaming the classes and methods and every language specific part.

And in the future, I would try to produce always english services unless the 
customer explicitly states that he wants to have that service in German. The 
result of the called methods (e.g. a message) could, of course, still be in 
German.

HTH,
Matthias.

> -Ursprüngliche Nachricht-
> Von: Christian Lipp [mailto:[EMAIL PROTECTED]
> Gesendet: Freitag, 6. Juni 2008 13:56
> An: axis-user@ws.apache.org
> Betreff: service language
> 
> Hello!
> 
> We are using Axis V1.x and have some services implemented in German
> language.
> Now we have a new project in a foreign country, so we are forced to
> translate our interfaces to the English language.
> 
> In my understanding I have to
> - change the interface to English
> - generate classes (also with English names and attributes)
> - refactor the application from the usage of the german classes to the
> usage
> of the english classes
> 
> Is the solution the same when using Axis V2.x?
> Or is there a possibility to map two interfaces with the same structure
> but
> with different languages to the same class?
> If yes, how is this done?
> 
> Thanks for your help in advance,
> CL
> 
> 
> -
> 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]

Websphere MQ configuration

[Matthias.Gaiser]

Hi,

 

I am trying to publish a web service via WebSphere MQ and I am
encountering some problems.

My steps so far included:

 

1. Created a WebService named "TestService".

 

2. Added in the axis2.xml the section:





org.apache.naming.java.javaURLContext
Factory

java:comp/env/jms/BrokerQ
ueueManagerWindows





 

3. Added to Tomcat a context.xml, containing:



 

 

Now I know that the second resource should not be of an ActiveMQ-Type..
but I don't know which type it should be for WebsphereMQ. Additionally I
get some errors when I start up the tomcat:

[WARN] Error looking up destination with JNDI name : TestService to map
its corresponding provider specific Destination name

[WARN] JMS Destination with JNDI name : TestService does not exist

[ERROR] StandardWrapper.Throwable

java.lang.NoSuchMethodError:
javax.jms.ConnectionFactory.createConnection()Ljavax/jms/Connection;

  at
org.apache.axis2.transport.jms.JMSConnectionFactory.addDestination(JMSCo
nnectionFactory.java:245)

  at
org.apache.axis2.transport.jms.JMSListener.processService(JMSListener.ja
va:174)

  at
org.apache.axis2.transport.jms.JMSListener.init(JMSListener.java:138)

  at
org.apache.axis2.engine.ListenerManager.start(ListenerManager.java:125)

  at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:442)

  at
org.apache.axis2.transport.http.AxisAdminServlet.init(AxisAdminServlet.j
ava:55)

  at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.jav
a:1139)

  at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:966)

  at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.j
ava:3956)

  at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4230
)

  at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)

  at
org.apache.catalina.core.StandardHost.start(StandardHost.java:736)

  at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)

  at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)

  at
org.apache.catalina.core.StandardService.start(StandardService.java:448)

  at
org.apache.catalina.core.StandardServer.start(StandardServer.java:700)

  at org.apache.catalina.startup.Catalina.start(Catalina.java:552)

  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

  at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)

  at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)

  at java.lang.reflect.Method.invoke(Method.java:597)

  at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)

  at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433)

 

Can anybody give me some hints, a sample for websphere mq or a solution
for my problem?

Thank you for any help.

 

Kind Regards

Matthias Gaiser

 

AW: Websphere MQ configuration

[Matthias.Gaiser]

Hi Upul,

 

Thanks a lot for the fast answer. I tried out the Synapse JMS Listener,
which somehow solved one part of the problem, but I still get another
error message, I am not sure about how to resolve it.

 

[INFO] JMS Transport Receiver/Listener initialized...

[INFO] Connected to the JMS connection factory :
java:comp/env/jms/BrokerQueueManagerWindows

[ERROR] Unable to determine type of Connection Factory - i.e.
Queue/Topic

[INFO] Unable to determine type of Connection Factory - i.e. Queue/Topic

org.apache.synapse.transport.jms.AxisJMSException: Unable to determine
type of Connection Factory - i.e. Queue/Topic

  at
org.apache.synapse.transport.jms.JMSConnectionFactory.handleException(JM
SConnectionFactory.java:590)

  at
org.apache.synapse.transport.jms.JMSConnectionFactory.connectAndListen(J
MSConnectionFactory.java:230)

  at
org.apache.synapse.transport.jms.JMSListener.start(JMSListener.java:104)

  at
org.apache.axis2.engine.ListenerManager.start(ListenerManager.java:126)

  at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:442)

  at
org.apache.axis2.transport.http.AxisAdminServlet.init(AxisAdminServlet.j
ava:55)

  at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.jav
a:1139)

  at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:966)

  at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.j
ava:3956)

  at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4230
)

  at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)

  at
org.apache.catalina.core.StandardHost.start(StandardHost.java:736)

  at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)

  at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)

  at
org.apache.catalina.core.StandardService.start(StandardService.java:448)

  at
org.apache.catalina.core.StandardServer.start(StandardServer.java:700)

  at org.apache.catalina.startup.Catalina.start(Catalina.java:552)

  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

  at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)

  at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)

  at java.lang.reflect.Method.invoke(Method.java:597)

  at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)

  at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433)

 

I am not so familiar with MQ Series and the Queue and Topic terms. Since
there are not many hits for "Unable to determine type of Connection
Factory", I am quite helpless and would be very grateful for any help.

 

Thanks,

Matthias.

 

 

Von: Upul Godage [mailto:[EMAIL PROTECTED] 
Gesendet: Dienstag, 22. Juli 2008 12:03
An: axis-user@ws.apache.org
Betreff: Re: Websphere MQ configuration

 

Most probably WebSphere MQ is JMS 1.0 compliant. But the Axis2's JMS
listener is written for JMS 1.1. The given method,
javax.jms.ConnectionFactory.createConnection()Ljavax/jms/Connection, was
introduced in JMS 1.1.
Instead you can try the Apache Synapse's (http://synapse.apache.org/)
JMS transport listener (which is compliant with JMS 1.0) with Axis2 by
taking the synapse transports jar and changing the Axis2's axis2.xml
pointing to synapse's JMS listener class.

Upul

On Tue, Jul 22, 2008 at 2:54 PM, <[EMAIL PROTECTED]> wrote:

Hi,

 

I am trying to publish a web service via WebSphere MQ and I am
encountering some problems.

My steps so far included:

 

1. Created a WebService named "TestService".

 

2. Added in the axis2.xml the section:





org.apache.naming.java.javaURLContext
Factory

java:comp/env/jms/BrokerQ
ueueManagerWindows





 

3. Added to Tomcat a context.xml, containing:



 

 

Now I know that the second resource should not be of an ActiveMQ-Type..
but I don't know which type it should be for WebsphereMQ. Additionally I
get some errors when I start up the tomcat:

[WARN] Error looking up destination with JNDI name : TestService to map
its corresponding provider specific Destination name

[WARN] JMS Destination with JNDI name : TestService does not exist

[ERROR] StandardWrapper.Throwable

java.lang.NoSuchMethodError:
javax.jms.ConnectionFactory.createConnection()Ljavax/jms/Connection;

  at
org.apache.axis2.transport.jms.JMSConnectionFactory.addDestination(JMSCo
nnectionFactory.java:245)

  at
org.apache.axis2.transport.jms.JMSListener.processService(JMSListener.ja
va:174)

  at
org.apache.axis2.transport.jms.JMSListener.init(JMSListener.java:138)

  at
org.apache.axis2.engine.ListenerManager.start(ListenerManager.java:125)

  at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:442)

  at
org.apache.axis2.transport.http.AxisAdminServlet.init(AxisAdminServlet.j
ava:55)

  at
org.apache.catalina.core.StandardWrapper.

AW: SOAP-Session management; terminate session.

[Matthias.Gaiser]

Hi group,

 

I've found this old message in the mailing list about a topic which I also have 
to think about again.

 

Is there a nicer, maybe standard, way to end a soapsession? What is the best 
way to destroy a session and all related resources, like eg. licenses?

 

Hoping for your help,

Matthias.

 

Von: LIE Jorund [mailto:[EMAIL PROTECTED] 
Gesendet: Mittwoch, 2. April 2008 17:07
An: axis-user@ws.apache.org
Betreff: RE: SOAP-Session management; terminate session.

 

I found a workaround for (2.) by setting the lastTouchedTime for the service 
group context to 0, the next cleanup will then destroy the session context. In 
the service class there is a method like this:

 

public void endSession()

{

ServiceGroupContext serviceGroupContext = 
MessageContext.getCurrentMessageContext().getServiceGroupContext();

serviceGroupContext.setLastTouchedTime(0);

}

 

This seems to do the trick, although I do not feel that the solution is very 
clean.

 

Jørund

 



From: LIE Jorund 
Sent: Tuesday, April 01, 2008 11:12 AM
To: axis-user@ws.apache.org
Subject: SOAP-Session management; terminate session.

I would need to use the SOAP session management facilities in Axis2-1.3, and I 
have a question about terminating a session.

 

Following the description for session management I have prepared a small 
prototype web service that initiates the session, returns the service group ID 
for the session to the client, and receives subsequent requests using the 
session ID. If there are no requests for a session-ID during a context timeout 
interval (set to 30 sec) the session becomes inactive. So far so good, this 
works fine, but I have 2 questions tough.

 

1. From tracing the destroy() method of my web service class I see that the 
object instance is not destroyed immediately after the context timeout. It 
seems like the session becomes stale, and that the object instance 
corresponding to stale sessions are destroyed after any new request to the web 
service. Is this correct?

 

2. I would like to find a way to terminate the sessions triggered by a certain 
operation (e.g. by a logout), not by the inactivity timeout. How can this be 
achieved in a clean way?

 

Thanks and Regards.

Jørund Lie

AW: Axis 1.4 and MTOM

[Matthias.Gaiser]

Hi Aki,

I am using Axis 1.4 (not Axis2) for the client and the server and I am 
wondering if it is possible at all to implement the scenario to transmit 
attachments using MTOM? You said you have some scenarios.. could you point me 
to them?

> I don't know how you captured the message (response.txt).
> The message seems to be corrupt with its MIME headers (there is no
> line delimiter in the first few lines).
I captured the message using a TCP-monitor tool and I agree that the HTTP/MIME 
headers look quite odd.

> Is it also not working if your client is talking to the Axis 1.4
> server talking MTOM?
I did not really get that question. It is working when I transmit the 
attachments via MIME, but it does not work when I switch to MTOM on the server 
side. Is there maybe an option to switch the client to MTOM as well?

Thanks for your help,
Matthias.

> -Ursprüngliche Nachricht-
> Von: Akitoshi Yoshida [mailto:[EMAIL PROTECTED]
> Gesendet: Freitag, 15. August 2008 14:54
> An: Gaiser, Matthias
> Cc: axis-user@ws.apache.org
> Betreff: Re: Axis 1.4 and MTOM
> 
> Hi,
> I don't know how you captured the message (response.txt).
> The message seems to be corrupt with its MIME headers (there is no
> line delimiter in the first few lines).
> I don't know if there is some interoperability problem in the Axis 1.4
> implementation.
> Is it also not working if your client is talking to the Axis 1.4
> server talking MTOM?
> 
> We have some MTOM scenarios with Axis 1.4.
> 
> Regards, Aki
> 
> 2008/8/14  <[EMAIL PROTECTED]>:
> > Hi group,
> >
> >
> >
> > I am currently trying to implement an axis 1.4 web service (with a
> client)
> > with attachments using MTOM.
> >
> >
> >
> > Somewhere it was said, that this is also possible with axis 1.4. But
> > unfortunately I don't get it working. I'm sending the attachments
> from the
> > server side via MTOM, but I can't receive them on the client.
> >
> > The problem seems to be on the client side. On the client I get this
> error:
> > [#text: Error in parsing mime data stream:  null
> >
> > I included the stacktrace and the response message as attachments.
> >
> >
> >
> > My questions:
> >
> > · Is it possible to implement a Web Service with Attachments
> using
> > MTOM and Axis 1.4?
> >
> > · Do I have to tell the client somehow that MTOM is being
> used?
> >
> > · Can you provide some help to my issue?
> >
> >
> >
> > The future plan is to migrate to axis2, but this would take too long
> for my
> > current issue.
> >
> > Hopefully waiting for your answers.
> >
> >
> >
> > Matthias.
> >
> > -
> > 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]

soap headers not present in handler

[Matthias.Gaiser]

Hi group,

 

I have a weird phenomenon.

I have implemented a compatibility header which adds the ws-adressing
headers to non-ws-adressing-requests. I need this in order to use the
soapsession id (servicegroupid) for my soapsession based service.

Now I can call my service with a request without the wsa-headers and it
works, I can find my additional headers in the request and process them.

When I send a wsa request, I am not able to access the soap headers from
a handler. In the handler I can't find any soap headers in the request
message.

Can somebody give me a hint what the reason might be? I'd be very glad
about it..

 

Thank you,

Matthias Gaiser

 

AW: soap headers not present in handler

[Matthias.Gaiser]

Thanky you for your answer Deepal.

I understand this. That's why I add the wsa-headers before the wsa-headers are 
handled which works quite good.
But my problem is that when my client sends the wsa-headers, I cannot access 
the headers from my handler. It is just like I won't send it, but I definitely 
do, I have traced it via tcpmon.

An example request is here, maybe something is wrong with this. I want to 
access the someID-header.
http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:pwc="http://pwc.t-systems.de/pwc";>   
 
  
http://example.com/6B29FC40-CA47-1067-B31D-00DD010662DA
  
  
 
http://www.w3.org/2005/08/addressing/anonymous  

  http://localhost:8080/PWCNG/services/PWCService  
  urn:login 
  http://someIDnamespace";>12345   
  
 
   
 test 
 test 
 DE  
 
   


Thanks for any help,
Matthias.

> -Ursprüngliche Nachricht-
> Von: Deepal jayasinghe [mailto:[EMAIL PROTECTED]
> Gesendet: Mittwoch, 17. September 2008 14:48
> An: axis-user@ws.apache.org
> Betreff: Re: soap headers not present in handler
> 
> The problem is Axis2 server only send the wsa- headers if any only if
> you send request with wsa.
> 
> Thank you!
> Deepal
> >
> > Hi group,
> >
> > I have a weird phenomenon.
> >
> > I have implemented a compatibility header which adds the ws-adressing
> > headers to non-ws-adressing-requests. I need this in order to use the
> > soapsession id (servicegroupid) for my soapsession based service.
> >
> > Now I can call my service with a request without the wsa-headers and
> > it works, I can find my additional headers in the request and process
> > them.
> >
> > When I send a wsa request, I am not able to access the soap headers
> > from a handler. In the handler I can't find any soap headers in the
> > request message.
> >
> > Can somebody give me a hint what the reason might be? I'd be very
> glad
> > about it..
> >
> > Thank you,
> >
> > Matthias Gaiser
> >
> 
> 
> --
> Thank you!
> 
> 
> http://blogs.deepal.org
> 
> 
> -
> 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]

AW: soap headers not present in handler

[Matthias.Gaiser]

I solved it and it is just a stupid fault.
I forgot to declare the wsa namespace and just used the prefix. The usual 
copy&paste- problem. :)

Maybe there could be an error message from Axis telling me that a prefix isn't 
declared in the request message. That would be very helpful.

Hope this helps anybody else as well,
Matthias.


> -Ursprüngliche Nachricht-
> Von: Gaiser, Matthias
> Gesendet: Donnerstag, 18. September 2008 09:33
> An: axis-user@ws.apache.org
> Betreff: AW: soap headers not present in handler
> 
> Thanky you for your answer Deepal.
> 
> I understand this. That's why I add the wsa-headers before the wsa-
> headers are handled which works quite good.
> But my problem is that when my client sends the wsa-headers, I cannot
> access the headers from my handler. It is just like I won't send it,
> but I definitely do, I have traced it via tcpmon.
> 
> An example request is here, maybe something is wrong with this. I want
> to access the someID-header.
>  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:pwc="http://pwc.t-systems.de/pwc";>
>
>   http://example.com/6B29FC40-CA47-1067-B31D-
> 00DD010662DA
>   
> 
> http://www.w3.org/2005/08/addressing/anonymous s>
>   
>   http://localhost:8080/PWCNG/services/PWCService
>   urn:login
>   http://someIDnamespace";>12345
>
>
>   
>  test
>  test
>  DE
>   
>
> 
> 
> Thanks for any help,
> Matthias.
> 
> > -Ursprüngliche Nachricht-
> > Von: Deepal jayasinghe [mailto:[EMAIL PROTECTED]
> > Gesendet: Mittwoch, 17. September 2008 14:48
> > An: axis-user@ws.apache.org
> > Betreff: Re: soap headers not present in handler
> >
> > The problem is Axis2 server only send the wsa- headers if any only if
> > you send request with wsa.
> >
> > Thank you!
> > Deepal
> > >
> > > Hi group,
> > >
> > > I have a weird phenomenon.
> > >
> > > I have implemented a compatibility header which adds the ws-
> adressing
> > > headers to non-ws-adressing-requests. I need this in order to use
> the
> > > soapsession id (servicegroupid) for my soapsession based service.
> > >
> > > Now I can call my service with a request without the wsa-headers
> and
> > > it works, I can find my additional headers in the request and
> process
> > > them.
> > >
> > > When I send a wsa request, I am not able to access the soap headers
> > > from a handler. In the handler I can't find any soap headers in the
> > > request message.
> > >
> > > Can somebody give me a hint what the reason might be? I'd be very
> > glad
> > > about it..
> > >
> > > Thank you,
> > >
> > > Matthias Gaiser
> > >
> >
> >
> > --
> > Thank you!
> >
> >
> > http://blogs.deepal.org
> >
> >
> > -
> > 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]

AW: soapUI and Apache Axis

[Matthias.Gaiser]

Hi Frank,

I use soapUI regularly to test my Axis web services and it works really good. I 
can recommend this tool to everyone for testing. You can get it here 
http://www.soapui.org

Matthias.

> -Ursprüngliche Nachricht-
> Von: Chen, Lizhao [mailto:[EMAIL PROTECTED]
> Gesendet: Mittwoch, 24. September 2008 11:11
> An: axis-user@ws.apache.org
> Betreff: RE: soapUI and Apache Axis
> 
> Frank,
> 
> I think they are separate tools for Web Service, SoapUI is on front
> end,
> and Axis is on back end.
> 
> 
> 
> -Original Message-
> From: Frank Cohen [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 24, 2008 09:08 AM
> To: axis-user@ws.apache.org
> Subject: soapUI and Apache Axis
> 
> Hi Everyone:
> 
> Any opinions about using soapUI with Axis?
> 
> -Frank
> 
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> The information contained in this message may be privileged
> and confidential and protected from disclosure. If the reader
> of this message is not the intended recipient, or an employee
> or agent responsible for delivering this message to the
> intended recipient, you are hereby notified that any reproduction,
> dissemination or distribution of this communication is strictly
> prohibited. If you have received this communication in error,
> please notify us immediately by replying to the message and
> deleting it from your computer. Thank you. Tellabs
> 
> 
> -
> 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]

Large xml response

[Matthias.Gaiser]

Hi group,

 

I have read some earlier threads but haven't found an answer there.

I want to implement a web service which will forward large xml strings
which it receives via backend services. I have a few points where I want
to ask if there is a standard solution.

 

- Does Axis offer some standard mechanism to compress the contents which
it delivers back? The packed size of the xml might be around 5mb which
should be ok to return.

- Is there a way to make Axis not (de)serializing the whole xml? AXIOM
is going in that direction that it parses on demand, so I might save
memory if I just take the OMElement I get via the backend services and
return it with my service. What do you think?

 

I am helpful for any hints to a solution.

 

Matthias.

 

AW: Large xml response

[Matthias.Gaiser]

I thought into the same direction that not the SOAP framework but the
underlying transport framework should take care of this, e.g. like the
tomcat my webapp is running on. Is there somehow an option to do this?

 

With such an option I then might run into interoperability issues on the
other hand or is there a standard solution for such an issue?

 

Matthias.

 

 

I believe this would be a configuration option in Apache to gzip
responses.

 

From: matthias.gai...@t-systems.com
[mailto:matthias.gai...@t-systems.com] 
Sent: Thursday, December 18, 2008 9:38 AM
To: axis-user@ws.apache.org
Subject: Large xml response

 

Hi group,

 

I have read some earlier threads but haven't found an answer there.

I want to implement a web service which will forward large xml strings
which it receives via backend services. I have a few points where I want
to ask if there is a standard solution.

 

- Does Axis offer some standard mechanism to compress the contents which
it delivers back? The packed size of the xml might be around 5mb which
should be ok to return.

- Is there a way to make Axis not (de)serializing the whole xml? AXIOM
is going in that direction that it parses on demand, so I might save
memory if I just take the OMElement I get via the backend services and
return it with my service. What do you think?

 

I am helpful for any hints to a solution.

 

Matthias.

 

AW: Large xml response

[Matthias.Gaiser]

I probably should have invested more time into research myself. I have
found an option in the tomcat configuration. I haven't tried it yet, but
it looks promising. You can configure the HTTP connector of your tomcat
(or similar server) to use HTTP compression.

For more details on HTTP compression have a look at:

http://www.websiteoptimization.com/speed/tweak/compress/
 

http://en.wikipedia.org/wiki/HTTP_compression
 

http://tomcat.apache.org/tomcat-6.0-doc/config/http.html

 

Matthias.

 

I thought into the same direction that not the SOAP framework but the
underlying transport framework should take care of this, e.g. like the
tomcat my webapp is running on. Is there somehow an option to do this?

 

With such an option I then might run into interoperability issues on the
other hand or is there a standard solution for such an issue?

 

Matthias.

 

 

I believe this would be a configuration option in Apache to gzip
responses.

 

From: matthias.gai...@t-systems.com
[mailto:matthias.gai...@t-systems.com] 
Sent: Thursday, December 18, 2008 9:38 AM
To: axis-user@ws.apache.org
Subject: Large xml response

 

Hi group,

 

I have read some earlier threads but haven't found an answer there.

I want to implement a web service which will forward large xml strings
which it receives via backend services. I have a few points where I want
to ask if there is a standard solution.

 

- Does Axis offer some standard mechanism to compress the contents which
it delivers back? The packed size of the xml might be around 5mb which
should be ok to return.

- Is there a way to make Axis not (de)serializing the whole xml? AXIOM
is going in that direction that it parses on demand, so I might save
memory if I just take the OMElement I get via the backend services and
return it with my service. What do you think?

 

I am helpful for any hints to a solution.

 

Matthias.

 

AW: Axis2 consumer within Axis2 provider classpath issue

[Matthias.Gaiser]

Hi group,

 

I am jumping in as well.. I got the same question what the recommended
way is in such a case? I got problems that the handlers were used for my
service and my stub communications which confused me.

 

Any standard ways here?

 

Matthias.

 

Von: Paul French [mailto:paul.fre...@kirona.com] 
Gesendet: Mittwoch, 14. Januar 2009 10:41
An: axis-user@ws.apache.org
Betreff: RE: Axis2 consumer within Axis2 provider classpath issue

 

Apologies for jumping in on this thread but I too would be very
interested in the recommended way to provide an AXIS2 web service which
may contain AXIS2 client stubs to other web services.

 

I believe I read some where that you need to use the same
ConfigurationContext for both? This would only make sense to me if you
plan to provide the same handlers and modules for both.

 

For example I have a web service client stub that works great (as a jar
file) - the axis2.xml file is in the classpath

 

I have an AXIS2 web service which works great where the axis2.xml file
is in the WEB-INF directory. (axis2 included as part of the web
application)

 

How would you combine the two?

 



From: Hundtofte, Rex A [mailto:rex.hundto...@eds.com] 
Sent: 14 January 2009 05:43
To: axis-user@ws.apache.org
Subject: Axis2 consumer within Axis2 provider classpath issue

I am getting a NoClassDefFoundError when my Axis2 consumer code is
executed inside of an Axis2 provided web service.  I have an aar file
deployed to my web server, the consumer code and generated client stub
classes are in separate jar files under the WEB-INF/lib directory.  The
incoming request processes fine but apparently the classloader that
needs to load the consumer Axis2 classes cannot find the Axis2 classes.
I appreciate any tips on how I might resolve this issue?

Thanks, 
Rex Hundtofte 



__ NOD32 3763 (20090113) Information __

This message was checked by NOD32 antivirus system.
http://www.eset.com

TypeDesc in Axis2 and ADB

[Matthias.Gaiser]

Hi all,

 

I am currently involved in migrating Axis1 code to Axis2. In our Axis1
code, we used the TypeDesc class to analyze the complex classes to check
for e.g. the minOccurs or maxOccurs settings in order to do something
specific in our Java code.

 

Now we are using Axis2 with ADB and we found out that there is no
TypeDesc left there. Can you recommend me some other way how to get this
information? Why is the TypeDesc not included anymore in ADB?

 

Thanks in advance,

Matthias.

 

Receiving swa attachments

[Matthias.Gaiser]

Hi group,

 

I am getting a bit frustrated with swa attachments. For reason of
compatibility I have to support them. I am trying to upload a file with
swa to a service. I can see via tcpmon that my file is being sent, but
on the server side I can't see the file in the attachments map. It is
just not there. I have compared my coe with the swa example and also
changed the swa example with my code, but I had no success.

 

The code on the server side looks like this:

MessageContext mctx = MessageContext.getCurrentMessageContext();

Attachments attachs = mctx.getAttachmentMap();

List cids = attachs.getContentIDList();

String soapCid = attachs.getSOAPPartContentID();

 

String url = "not stored";

for (String cid : cids) {

if (!cid.equals(soapCid)) {

url = writeAttachmentToDisk(mctx.getAttachment(cid), cid);

}

}

 

I filter out the soap part which is also listed in the attachments, but
the list cids always only contains the soapPartContentID.

 

In the articles on ws02 they always mention that you don't have to
specify a special option to receive swa attachments. I am probably
missing sth. out. Can anybody help me here?

 

Thanks in advance,

Matthias.

AW: Receiving swa attachments

[Matthias.Gaiser]

Hi Chinmoy,

 

thanks for your answer. It gave me a hint into the right direction. Now
it is working.

 

Yes, I did enable the SwA property, but it is only necessary to enable
it on the client side, not on the server side as other tutorials mention
as well.

My problem was that I tried to get the content ids via the
getContentIDList() method. This method only returns the content ids
which have been parsed already. If I take the method you mention
getAllContentIDs() or getContentIDSet(), then Axis parses the other
attachments and returns a complete list of the content ids.

 

@Axis2-Team: Please reflect this behavior in the javadoc that only the
parsed content ids are returned by the getContentIDList().

 

Maybe I can help some other people with the same problem. J

 

Matthias.

 

Von: Chinmoy Chakraborty [mailto:cch...@gmail.com] 
Gesendet: Mittwoch, 13. Mai 2009 17:43
An: axis-user@ws.apache.org
Betreff: Re: Receiving swa attachments

 

Hi Matthias,

 

You need to set 'enableSwA' property to true in client and server side
in order to work with SwA. I am assuming that you have done this. I
tried with Axis2 1.4 and it works fine. You can try following code
sample while receving the SwA attachment in the client side:

 

  ...

  mepClient.execute(true);


  MessageContext response =
mepClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
  Attachments attachments = response.getAttachmentMap();
  if (attachments == null) {
  return "No attachment";
  }
  String[] attachmentIDs = attachments.getAllContentIDs();
  for(int i = 0; i < attachmentIDs.length; i++){
 
if(!attachments.getSOAPPartContentID().equals(attachmentIDs[i])){
  return attachments.getDataHandler(attachmentIDs[i]);
  }
  }

 

 

Chinmoy

On Wed, May 13, 2009 at 8:15 PM,  wrote:

Hi group,

 

I am getting a bit frustrated with swa attachments. For reason of
compatibility I have to support them. I am trying to upload a file with
swa to a service. I can see via tcpmon that my file is being sent, but
on the server side I can't see the file in the attachments map. It is
just not there. I have compared my coe with the swa example and also
changed the swa example with my code, but I had no success.

 

The code on the server side looks like this:

MessageContext mctx = MessageContext.getCurrentMessageContext();

Attachments attachs = mctx.getAttachmentMap();

List cids = attachs.getContentIDList();

String soapCid = attachs.getSOAPPartContentID();

 

String url = "not stored";

for (String cid : cids) {

if (!cid.equals(soapCid)) {

url = writeAttachmentToDisk(mctx.getAttachment(cid), cid);

}

}

 

I filter out the soap part which is also listed in the attachments, but
the list cids always only contains the soapPartContentID.

 

In the articles on ws02 they always mention that you don't have to
specify a special option to receive swa attachments. I am probably
missing sth. out. Can anybody help me here?

 

Thanks in advance,

Matthias.

 

Attachments are incomplete

[Matthias.Gaiser]

Hi group,

 

I am receiving attachments via MTOM and SwA. I could watch via tcpmon
that the complete files were being transferred. But when I saved the
files on the receiver side, in the middle of the file data was lost. I
tested this also without tcpmon because I know that tcpmon does
something weird things with attachments, but nothing changed.

Now I solved the problem myself which by disabling the cache on the
receiver side.

 

I just wonder why the attachment cache kicked some of my data? Can
anybody give me hints? I think this behavior is more than curios. Is
this a bug?

 

Matthias.

 

AW: AW: Receiving swa attachments

[Matthias.Gaiser]

Hi Martin,

 

I have now this code which works fine for me for receiving SwA attachments. 
Feel free to include this code into the mtom-user-guide (which should maybe 
named attachment-user-guide).

List attList = new ArrayList();

MessageContext mctx = MessageContext.getCurrentMessageContext();

Attachments attachs = mctx.getAttachmentMap();

Set cids = attachs.getContentIDSet();

if (cids != null && cids.size() > 1) {

   String attType = attachs.getAttachmentSpecType();

   if (attType.equals(MTOMConstants.SWA_TYPE) || 
attType.equals(MTOMConstants.SWA_TYPE_12)) {

  String soapCid = attachs.getSOAPPartContentID();

  File file;

  for (String cid : cids) {

 if (!cid.equals(soapCid)) {

file = new File(UUID.randomUUID().toString()); //the cid might not 
be a good name to save the file.

FileOutputStream fileOutputStream = new FileOutputStream(file);

mctx.getAttachment(cid).writeTo(fileOutputStream);

fileOutputStream.flush();

fileOutputStream.close();

attList.add(file);

 }

  }

   }

}

 

I assume Axis2 sends the attachments as mime attachments, if they are sent via 
SwA. This code also worked for me for an Axis1 1.4 client uploading a file as a 
MIME attachment to my Axis2 Service. DIME Attachments can not be received so 
far. I'll have a look what I still have to do.

 

Matthias.

 

 

Von: Martin Gainty [mailto:mgai...@hotmail.com] 
Gesendet: Donnerstag, 14. Mai 2009 15:35
An: axis-user@ws.apache.org
Betreff: RE: AW: Receiving swa attachments

 

Matthias
i would suggest editting mtom-user-guide to demonstrate actual usage for 
axis2-1.4.1 specifically

public class SwA {

private OperationContext operationContext;



public SwA() {

}



public void setOperationContext(OperationContext oc) throws AxisFault {

operationContext = oc;

}



public void uploadAttachment(OMElement omEle) throws AxisFault {

OMElement child = (OMElement) omEle.getFirstOMChild();

OMAttribute attr = child.getAttribute(new QName("href"));



//Content ID processing

String contentID = attr.getAttributeValue();

contentID = contentID.trim();

if (contentID.substring(0, 3).equalsIgnoreCase("cid")) {

contentID = contentID.substring(4);

}

  //contentId of cid is assumed   

Attachments attachment = (Attachments) 
(operationContext.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE)).getAttachmentMap();

//DataHandler dataHandler = attachment.getDataHandler(contentID);

java.util.Iterator iter;

try

{

 iter=attachment.getAttachments().iterator();

}

catch(AxisFault axis_fault)

{

  log.debug("AxisFault produced for 
attachment.getAttachments().iterator()");

}

String[] attachmentIDs;

int attachementCtr=0;

while(iter.hasNext()

{

 attachmentIDs[attachmentCtr++]= iter.next();

}

}

}
public static final java.lang.String

ATTACHMENT_ENCAPSULATION_FORMAT_DIME 

 

"axis.attachment.style.dime"

public static final java.lang.String

ATTACHMENT_ENCAPSULATION_FORMAT_MIME 

 

"axis.attachment.style.mime"

public static final java.lang.String

ATTACHMENT_ENCAPSULATION_FORMAT_MTOM 

 

"axis.attachment.style.mtom"


this only covers attachment style of 'mtom'
would need to refactor for both mime and dime attachment styles

suggestions?
Martin Gainty 
__ 
Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung/Note de 
déni et de confidentialité

This message is confidential. If you should not be the intended receiver, then 
we ask politely to report. Each unauthorized forwarding or manufacturing of a 
copy is inadmissible. This message serves only for the exchange of information 
and has no legal binding effect. Due to the easy manipulation of emails we 
cannot take responsibility over the the contents.

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.

Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.

AW: AW: Receiving swa attachments

[Matthias.Gaiser]

Martin,

 

Bitteschön, I'm happy that I can contribute a little bit back to Axis since it 
helped me so much in implementing web services.

Thanks also for clarifying once more that DIME is not supported by Axis2. I had 
this already in mind somewhere and a search in the mailing list convinced me to 
better try another way for my old clients with DIME attachments.

I only found one older post by you, Martin, where you mentioned that DIME 
attachments could be supported somehow. Did you realize it with that?

you have to set chunkedEncoding here is a quick example import 
org.globus.axis.transport.HTTPUtils;//assume your service is called 
'MyService' URL url = new 
URL("local:///localhost:8080/axis/services/MyService"); 
MyServiceAddressingLocator locator = new MyServiceAddressingLocator(); 
MyService port = locator.getMyServicePort(url); 

// force HTTP 1.1 (why dont we have a method which setHTTP11Version(port,true) 
? HTTPUtils.setHTTP10Version((Stub)port, false); //set 
chunkedEncodingHTTPUtils.setChunkedEncoding((Stub)port, true); //Call the hello 
method from the discovered service port.hello();for more info please look at 
http://www.globus.org/toolkit/docs/development/4.1.0/common/javawscore/developer/index.html
 

  

M-

Thanks,

Matthias.

 

Von: Martin Gainty [mailto:mgai...@hotmail.com] 
Gesendet: Freitag, 15. Mai 2009 02:57
An: axis-user@ws.apache.org
Betreff: RE: AW: Receiving swa attachments

 

frist heard of DIME in 02 but havent seen any implementation since that 02
thanks for the code matthias!
Vielen Danke,
Martin  
__ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.

Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.






> Date: Fri, 15 May 2009 00:45:43 +0200
> Subject: Re: AW: Receiving swa attachments
> From: andreas.veit...@gmail.com
> To: axis-user@ws.apache.org
> 
> Matthias,
> 
> I'm pretty sure DIME is not supported by Axiom.
> 
> Andreas
> 
> On Thu, May 14, 2009 at 17:16,  wrote:
> > Hi Martin,
> >
> >
> >
> > I have now this code which works fine for me for receiving SwA attachments.
> > Feel free to include this code into the mtom-user-guide (which should maybe
> > named attachment-user-guide).
> >
> > List attList = new ArrayList();
> >
> > MessageContext mctx = MessageContext.getCurrentMessageContext();
> >
> > Attachments attachs = mctx.getAttachmentMap();
> >
> > Set cids = attachs.getContentIDSet();
> >
> > if (cids != null && cids.size() > 1) {
> >
> >String attType = attachs.getAttachmentSpecType();
> >
> >if (attType.equals(MTOMConstants.SWA_TYPE) ||
> > attType.equals(MTOMConstants.SWA_TYPE_12)) {
> >
> >   String soapCid = attachs.getSOAPPartContentID();
> >
> >   File file;
> >
> >   for (String cid : cids) {
> >
> >  if (!cid.equals(soapCid)) {
> >
> > file = new File(UUID.randomUUID().toString()); //the cid might
> > not be a good name to save the file.
> >
> > FileOutputStream fileOutputStream = new FileOutputStream(file);
> >
> > mctx.getAttachment(cid).writeTo(fileOutputStream);
> >
> > fileOutputStream.flush();
> >
> > fileOutputStream.close();
> >
> > attList.add(file);
> >
> >  }
> >
> >   }
> >
> >}
> >
> > }
> >
> >
> >
> > I assume Axis2 sends the attachments as mime attachments, if they are sent
> > via SwA. This code also worked for me for an Axis1 1.4 client uploading a
> > file as a MIME attachment to my Axis2 Service. DIME Attachments can not be
> > received so far. I'll have a look what I still have to do.
> >
> >
> >
> > Matthias.
> >
> >
> >
> >
> >
> > Von: Martin Gainty [mailto:mgai...@hotmail.com]
> > Gesendet: Donnerstag, 14. Mai 2009 15:35
> > An: axis-user@ws.apache.org
> > Betreff: RE: AW: Receiving swa attachments
> >
> >
> >
> > Matthias
> > i would suggest editting mtom-user-guide to demonstrate actual usage for
> > axis2-1.4.1 specifically
> >
> > public class SwA {
> >
> > private OperationContext

Provider com.bea.xml.stream.MXParserFactory not found & stax-1.2.0

[Matthias.Gaiser]

Hi group,

 

I am encountering some curious problem. I am developing an application
with axis2 v1.4.1. I develop the client and the server side. I use
eclipse for programming. Last week I had to create a new eclipse
workspace, but with the same sources. I also created therefore a new
server in eclipse based on my server executables I used before. (Tomcat
5.5).

Now when I create a ConfigurationContext on the client side, I get the
exception:

javax.xml.stream.FactoryConfigurationError: Provider
com.bea.xml.stream.MXParserFactory not found

 

I found a solution in the internet that I should add the stax-1.2.0.jar.
It is gone with this jar, but I wonder how this can happen? My
colleagues are working without that jar and the same code and they have
no problems at all.

 

Any insights would be appreciated!!

 

Matthias.

AW: Provider com.bea.xml.stream.MXParserFactory not found & stax-1.2.0

[Matthias.Gaiser]

Thanks a lot for your fast answers. It is still weird that it works for my 
colleagues and not for me. I think I got the same jars in my classpath, but I'm 
probably missing something out I cannot find.. I think I'm done for today.. :o)

Thank you, Andreas & Martin!!

Matthias. 
 
-Ursprüngliche Nachricht-
Von: Andreas Veithen [mailto:andreas.veit...@gmail.com] 
Gesendet: Mittwoch, 3. Juni 2009 16:21
An: axis-user@ws.apache.org
Betreff: Re: Provider com.bea.xml.stream.MXParserFactory not found & stax-1.2.0

I would not recommend adding sjsxp.jar. The reason is that Axis2 is
best tested with Woodstox as StAX parser implementation. Replacing it
by Sun's implementation may cause subtle issues.

Andreas

On Wed, Jun 3, 2009 at 16:03, Martin Gainty  wrote:
> bea vendor specific problem
> http://forums.java.net/jive/thread.jspa?messageID=117971
>
> available stax jars are described at
> http://www.j2ee.me/webservices/docs/1.6/tutorial/doc/SJSXP-jars.html
>
> here is the response from the bea release engineer for not including stax
> jar (sjsxp.jar)
>
> http://forums.java.net/jive/thread.jspa?messageID=117971
>
> "Any sjsxp.jar would do. The one in the JAX-WS RI would be just fine.
> The reason we don't ship sjsxp.jar in the JAXB RI is that we don't want
> people to think that it's a required part of the JAXB"
>
> HTH
> Martin Gainty
> __
> Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
>
> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
> Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte
> Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht
> dient lediglich dem Austausch von Informationen und entfaltet keine
> rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
> E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
>
> Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
> destinataire prévu, nous te demandons avec bonté que pour satisfaire
> informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie
> de ceci est interdite. Ce message sert à l'information seulement et n'aura
> pas n'importe quel effet légalement obligatoire. Étant donné que les email
> peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
> aucune responsabilité pour le contenu fourni.
>
>
>
>
> 
> Subject: Provider com.bea.xml.stream.MXParserFactory not found & stax-1.2.0
> Date: Wed, 3 Jun 2009 15:21:43 +0200
> From: matthias.gai...@t-systems.com
> To: axis-user@ws.apache.org
>
> Hi group,
>
>
>
> I am encountering some curious problem. I am developing an application with
> axis2 v1.4.1. I develop the client and the server side. I use eclipse for
> programming. Last week I had to create a new eclipse workspace, but with the
> same sources. I also created therefore a new server in eclipse based on my
> server executables I used before. (Tomcat 5.5).
>
> Now when I create a ConfigurationContext on the client side, I get the
> exception:
>
> javax.xml.stream.FactoryConfigurationError: Provider
> com.bea.xml.stream.MXParserFactory not found
>
>
>
> I found a solution in the internet that I should add the stax-1.2.0.jar. It
> is gone with this jar, but I wonder how this can happen? My colleagues are
> working without that jar and the same code and they have no problems at all.
>
>
>
> Any insights would be appreciated!!
>
>
>
> Matthias.
>
> 
> Hotmail® has ever-growing storage! Don't worry about storage limits. Check
> it out.

Custom module in serviceGroup

[Matthias.Gaiser]

Hi group,

 

I have had the same problem like Florian described here
(http://markmail.org/message/apoieprt4bz7teyd) that my custom module was
activated for every service although I configured it only for a single
operation. I've found the same solution like he did:

 

public InvocationResponse invoke(MessageContext ctx) throws AxisFault {

   if(ctx.isEngaged("mymodulename"))

  {

  return this.processMessage(ctx);

   }

   return InvocationResponse.CONTINUE;

} 

 

I wonder now why I have to check if the module is engaged in my handler.
Is not Axis supposed to do this? It has got all the informations in my
services.xml.

 

Matthias.

 

[Axis 2.1.5] Addressing module not found on Websphere

[Matthias.Gaiser]

Hello,

 

we are using Axis2 1.5 on WebSphere Application Server 6.1.0.13 on
Windows XP. While it works on one machine it doesn't work on another
machine with the same configuration. The only difference is that we
installed the Websphere with administration security on the machine
where it is not working. We have deactivated it for testing.

 

We get the error message. It seems that the AdminAxisServlet can't be
initialized. At both installations we have the addressing module in the
same directory ("WEB-INF/modules" in our web application).

 

[14.10.09 10:00:30:655 CEST] 0015 ServletWrappe E   Uncaught init()
exception thrown by servlet AxisAdminServlet

[14.10.09 10:00:30:655 CEST] 0015 ServletWrappe E   Deregister the
mbean because of uncaught init() exception thrown by servlet
AxisAdminServlet: javax.servlet.ServletException: The system is
attempting to engage a module that is not available: addressing

at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:449)

at
org.apache.axis2.webapp.AxisAdminServlet.init(AxisAdminServlet.java:56)

at
com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:
190)

at
com.ibm.ws.wswebcontainer.servlet.ServletWrapper.init(ServletWrapper.jav
a:317)

at
com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper
.java:1142)

at
com.ibm.ws.wswebcontainer.servlet.ServletWrapper.initialize(ServletWrapp
er.java:150)

at
com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServlet
Wrapper(WebExtensionProcessor.java:99)

at
com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:790)

at
com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.ja
va:470)

at
com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.
java:307)

at
com.ibm.ws.wswebcontainer.webapp.WebApp.initialize(WebApp.java:289)

at
com.ibm.ws.wswebcontainer.webapp.WebGroup.addWebApplication(WebGroup.jav
a:90)

at
com.ibm.ws.wswebcontainer.VirtualHost.addWebApplication(VirtualHost.java
:157)

at
com.ibm.ws.wswebcontainer.WebContainer.addWebApp(WebContainer.java:665)

at
com.ibm.ws.wswebcontainer.WebContainer.addWebApplication(WebContainer.ja
va:618)

at
com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerI
mpl.java:335)

at
com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImp
l.java:551)

at
com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl
.java:1301)

at
com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectS
tart(DeployedApplicationImpl.java:1138)

at
com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl
.java:569)

at
com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedAppli
cationImpl.java:817)

at
com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(Applica
tionMgrImpl.java:950)

at
com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(Appli
cationMgrImpl.java:2120)

at
com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(W
sComponentImpl.java:342)

at
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)

 

Thank you in advance,

 

Matthias.

AW: [Axis 2.1.5] Addressing module not found on Websphere

[Matthias.Gaiser]

Hello again,

 

it turned out that the error came from installating WebSphere
Application Server with administration security on. So I deinstalled it
and installed it again without administration security. It could be
switched on after the installation without any problem.

 

Hope it helps anyone else,

 

Matthias.

 

Von: Gaiser, Matthias 
Gesendet: Mittwoch, 14. Oktober 2009 10:32
An: axis-user@ws.apache.org
Betreff: [Axis 2.1.5] Addressing module not found on Websphere

 

Hello,

 

we are using Axis2 1.5 on WebSphere Application Server 6.1.0.13 on
Windows XP. While it works on one machine it doesn't work on another
machine with the same configuration. The only difference is that we
installed the Websphere with administration security on the machine
where it is not working. We have deactivated it for testing.

 

We get the error message. It seems that the AdminAxisServlet can't be
initialized. At both installations we have the addressing module in the
same directory ("WEB-INF/modules" in our web application).

 

[14.10.09 10:00:30:655 CEST] 0015 ServletWrappe E   Uncaught init()
exception thrown by servlet AxisAdminServlet

[14.10.09 10:00:30:655 CEST] 0015 ServletWrappe E   Deregister the
mbean because of uncaught init() exception thrown by servlet
AxisAdminServlet: javax.servlet.ServletException: The system is
attempting to engage a module that is not available: addressing

at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:449)

at
org.apache.axis2.webapp.AxisAdminServlet.init(AxisAdminServlet.java:56)

at
com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:
190)

at
com.ibm.ws.wswebcontainer.servlet.ServletWrapper.init(ServletWrapper.jav
a:317)

at
com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper
.java:1142)

at
com.ibm.ws.wswebcontainer.servlet.ServletWrapper.initialize(ServletWrapp
er.java:150)

at
com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServlet
Wrapper(WebExtensionProcessor.java:99)

at
com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:790)

at
com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.ja
va:470)

at
com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.
java:307)

at
com.ibm.ws.wswebcontainer.webapp.WebApp.initialize(WebApp.java:289)

at
com.ibm.ws.wswebcontainer.webapp.WebGroup.addWebApplication(WebGroup.jav
a:90)

at
com.ibm.ws.wswebcontainer.VirtualHost.addWebApplication(VirtualHost.java
:157)

at
com.ibm.ws.wswebcontainer.WebContainer.addWebApp(WebContainer.java:665)

at
com.ibm.ws.wswebcontainer.WebContainer.addWebApplication(WebContainer.ja
va:618)

at
com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerI
mpl.java:335)

at
com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImp
l.java:551)

at
com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl
.java:1301)

at
com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectS
tart(DeployedApplicationImpl.java:1138)

at
com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl
.java:569)

at
com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedAppli
cationImpl.java:817)

at
com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(Applica
tionMgrImpl.java:950)

at
com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(Appli
cationMgrImpl.java:2120)

at
com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(W
sComponentImpl.java:342)

at
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)

 

Thank you in advance,

 

Matthias.

AW: OutOfMemoryError at WS call client side

[Matthias.Gaiser]

Hi,

I like to share the solution I have so far.

I am involved in implementing a middleware which has to perform lots of web 
service calls, also in parallel. This means we cannot just share a service 
client for all our requests.

I've found through debugging axis2 code that calling serviceClient.cleanup(), 
after I performed my web service call, removes the generated anonymous 
AxisService from the AxisConfiguration. I am assuming that this will prevent 
the OutOfMemoryError, but I could not verify it in tests yet.
Can someone confirm that using the serviceClient this way is a good idea?

Thank you,
Matthias.

-Ursprüngliche Nachricht-
Von: Deepal jayasinghe [mailto:deep...@gmail.com] 
Gesendet: Samstag, 7. November 2009 01:42
An: axis-user@ws.apache.org
Betreff: Re: OutOfMemoryError at WS call client side

Hi,
This is one of the common problem most of the users usually face. The
reason behind this is whenever you create a serviceClient, it creates an
AxisService and added to AxisConfiguration. In order to overcome this
issues, create one service client and reuse that.

Thanks,
Deepal
>
> Dear Axis users,
>
>  
>
> I currently have a memory problem when using Axis2. I implement a
> client for web service calls in a generic way, so that I can use my
> client for different types of services. My code to call the service
> generally looks like this:
>
>  
>
> ServiceClient sender = *new* ServiceClient(/confContext/, *null*);
>
> setHeadersAndOptions(sender); //engaging modules and setting endpoint,
> etc.
>
> MessageContext reqMctx = createPayload(sender); //creating the request
> MessageContext
>
> OperationClient oc = sender.createClient(ServiceClient./ANON_OUT_IN_OP/);
>
> oc.addMessageContext(reqMctx);
>
> oc.execute(*true*);
>
>  
>
> Through analyzing the heapdump I saw that inside the
> AxisConfiguration, a lot of AxisService instances are stored in a
> HashMap, around 10.000 in my case. I am using my AxisConfiguration as
> a static object for all calls since the Configuration does not change.
> Is it not a good idea to handle it thias way?
>
>  
>
> I am thankful for any advise.
>
>  
>
> Matthias.
>


-- 
Thank you!


http://blogs.deepal.org
http://deepal.org

Jar/Mar files in temp directory are not getting deleted

[Matthias.Gaiser]

Hi all,

 

after using Axis2 for about a year, I have discovered that Axis2 creates
a lot of temporary jar/mar/aar copies on my temp folder. That way in the
last 7 months 1256 folders with 18722 files were created which now use
about 4GB of my disk space. It seems to me that every time I restart my
Tomcat the files are generated again.

 

I have read now in several older posts that others also have the
problem. I understand that Axis2 generates these temp files for
performance reasons, but why does it not  delete them afterwards? Is
this fixed in the current Axis version?

I am using Axis2 version 1.5.

 

Hoping for help,

Matthias

 

Users with the same problem:

http://markmail.org/message/bo77yh2kvlb7k6fe?q=list:org.apache.ws.axis-u
ser+temp+mar

http://markmail.org/message/yv5b2lf6jasabsh2?q=list:org.apache.ws.axis-u
ser+temp+mar

http://markmail.org/message/kknpneit4ojlvgzg?q=list:org.apache.ws.axis-u
ser+temp+jar

http://markmail.org/message/nvyt4xsf54yefosn?q=list:org.apache.ws.axis-u
ser+cached+archives