Re: newbie to Axis2

[Anne Thomas Manes]

The W3C has only just recently published the Candidate Recommendation
for WSDL 2.0. They have just issued a call for implementations -- but
it will take a while for folks to build them. The Apache Woden
incubator project is working on it: http://incubator.apache.org/woden/.


If you would like to participate in building a WSDL 2.0 implementation,
please join in, but I'd say that it's still a little early to try using
WSDL 2.0 for building apps.

AnneOn 2/2/06, anshuk pal chaudhuri <[EMAIL PROTECTED]> wrote:
ok.But actualli I am trying any of the soap enginespresent generate WSDL2.0 compliant.If any can youplease let me know.Thanks,Anshuk--- Deepal Jayasinghe <
[EMAIL PROTECTED]> wrote:> well WSDL 2.0 support is not fully completed , Axis2> can read WSDL 2.0 but> the writing part is not complete , since we are> using WSDL 1.1 writer you
> only get WSDL 1.1 doc when you ask for wsdl from> axis2 :)>> Thanks,>  Deepal>> ~Future is Open~>
> - Original Message -> From: "anshuk pal chaudhuri" <[EMAIL PROTECTED]>> To: > Sent: Wednesday, February 01, 2006 8:30 PM> Subject: Re: newbie to Axis2>>> > Ajith,> >> > Sorry for the trouble.It must have been some other> > release which I was 
using.I downloaded the 0.94> > version and its working ok.I have tried the> > MyService.aar services and its working fine.The> wsdl> > is also generated properly.But the wsdl that is
> > generated is compliant to 1.1.> > Axis 2 supports WSDL 2.0.rite??How will one> service> > (say the sample web services)generate a WSDL 2.0> > compliant wsdl?> > Can you please let me know.
> >> > Anshuk> >> > --- Ajith Ranabahu <[EMAIL PROTECTED]>> wrote:> >> >> Hmm..> >> We've checked and verified that all these
> features> >> are available. Is this> >> surely the 0.94 release ?> >>> >> On 2/1/06, anshuk pal chaudhuri> <[EMAIL PROTECTED]
>> >> wrote:> >> >> >> > yah Ajith,> >> >> >> > I have got one temporary solution to it.The> >> problem> >> > what i thot was that the servlet getting
> created> >> for> >> > the HappyAxis.jsp was happaxis_jsp.java.Check> the> >> name> >> > caps in both the cases.I changed the> HappyAxis.jsp
> >> in> >> > the axis2 to happaxis.jsp.Also changed the> >> > corresponding urlin the index.jsp page for the> >> > Validate Link.> >> >> >> > Now the axis is properly as its getting all the
> >> the> >> > componenents.> >> > Now The problem that I am still facing is that> the> >> > service which I have deployed (the one with> echo
> >> and> >> > ping operations, the userguide examples one),I> am> >> not> >> > able to see the wsdl of the service.> >> > Someone said that the web page where the list
> of> >> > services is being displayed, the service name> >> > (MYService in this case) is a hyperlink which> will> >> > lead to the wsdl page.But my Sevice Name is not
> >> any> >> > link.So how do I view the wsdl of my service> >> deployed> >> > in axis2 ???> >> >> >> > Anshuk> >> >
> >> >> >> >> >> > --- Ajith Ranabahu <[EMAIL PROTECTED]>> >> wrote:> >> >> >> > > Hmmm... Is this in the 
0.94 release ?  I'm> >> thinking> >> > > that it's something to> >> > > do with the servlet container setup but need> >> more> >> > > info to confirm.
> >> > > You can try deleting the work directory if> you> >> are> >> > > using tomcat.> >> > > BTW can you post the details about your> servlet
> >> > > container setup, OS and the> >> > > rest of the environment ?> >> > >> >> > > On 2/1/06, anshuk pal chaudhuri> >> <
[EMAIL PROTECTED]>> >> > > wrote:> >> > > >> >> > > > Hi,> >> > > >> >> > > > I have installed axis2 web application but
> >> when I> >> > > am> >> > > > trying to view the Axis Happiness Page> using> >> the> >> > > > Validate Link in order to know that whether
> >> all> >> > > the> >> > > > componenets are properly installed or> not,its> >> > > throwing> >> > > > an error.> >> > > >
> >> > > > java.lang.NoClassDefFoundError:> >> > > > org/apache/jsp/HappyAxis_jsp (wrong name:> >> > > > org/apache/jsp/happyaxis_jsp)> >> > > >
> >> java.lang.ClassLoader.defineClass0(Native> >> > > Method)> >> > > >> >> > > >> >> > >> >> >> >>
> >>java.lang.ClassLoader.defineClass(ClassLoader.java:537)> >> > > >> >> > > >> >> > >> >> >> >>> >
>java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)> >> > > >> >> > > >> >> > >> >> >> >>> >
>java.net.URLClassLoader.defineClass(URLClassLoader.java:251)> >> > > >> >> > > >> >> > >> >> >> >>> >>
java.net.URLClassLoader.access$100(URLClassLoader.java:55)> >> > > >> >> > > >> >> > >> >> >> >>> >>java.net.URLClassLoader$1.run
(URLClassLoader.java:194)> >> > > >> >> > >> >>> java.security.AccessController.doPrivileged(Native> >> > > > Method)> >> > > >
> >> > > >> >> > >> >> >> >>> >>java.net.URLClassLoader.findClass(URLClassLoader.java:187)> >> > > >> >> > > >
> >> > >> >> >> >>> >>org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:156)> >> > > >> >> > > >
> >> > >> >> >> >>> >>org.apa

Re: Document Literal vs Document Wrapped vs RPC Encoding

[Anne Thomas Manes]

Quite a few SOAP engines don't support rpc/literal, therefore
doc/literal (wrapped or unwrapped) is a better idea than rpc/literal. I
generally recommend using wrapped doc/literal for best interop and
easiest development and configuration. Note that .NET supports wrapped
doc/literal by default. 

AnneOn 2/2/06, Cyrille Le Clerc <[EMAIL PROTECTED]> wrote:
WS-I Basic Profile, the reference for SOAP interoperability, says itprefers "literal" rather than "encoded" :  Extract : "As a result, the Profile prefers the use of literal,non-encoded XML."
  Chapter : "4.1.7 SOAP encodingStyle Attribute"  URL : http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16448072
Unfortunately, I did not find in this spec any clear statement sayingthat "document" (in a wrapped style) is preferred to "rpc".However, you will find many articles that say "document" is preferred to "rpc".
Cyrille--Cyrille Le Clerc[EMAIL PROTECTED][EMAIL PROTECTED]
http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.htmlOn 2/2/06, Jyotishman Pathak <[EMAIL PROTECTED]> wrote:> Dov,>>  I
found this article [1] from IBM to be quite useful. At the same time, I
am interested in knowing more about your investigation.>>  Thanks,>  - Jyoti>>  [1] 
http://www.ibm.com/developerworks/webservices/library/ws-whichwsdl/?ca=dgr-devx-WebServicesMVP03>> On 2/2/06, Balaji D L <[EMAIL PROTECTED]
> wrote:> >> >> >> > Can you share your analyse with us ??> > It will be very useful.> > Regards> > Balaji> >> > - Original Message 
> > From: Dov Rosenberg <[EMAIL PROTECTED]>> > To:  axis-user@ws.apache.org> > Sent: 02 February 2006 14:21:37
> > Subject: Document Literal vs Document Wrapped vs RPC Encoding> >> > I have done a bunch of investigating to determine the differences/benefits/limitations
of the 3 styles of WSDL generation. In general it seems that the
preferred version is Document Literal. Are there any other opinions as
to the most popular version?> >> > Thanks in advance> >> >> > --> > Dov Rosenberg> > Inquira Inc> > 370 Centerpointe Circle, ste 1178> > Altamonte Springs, FL 32701
> > (407) 339-1177 x 102> > (407) 339-6704 (fax)> >  [EMAIL PROTECTED]> > AOL IM: dovrosenberg> >> >>
>>> --> Jyotishman Pathak> WWW: http://www.cs.iastate.edu/~jpathak

Regarding WSDL2Java

[anshuk pal chaudhuri]

Ajith,

Thanks a lot about the information regarding the
Java2WSDL tool.

I have few queries about the present WSDL2Java tool
that is already bing released in the 0.94 version in
axis2.
I am having some issues with it.
I want to know the WSDL2Java takes input the wsdl
specfic to which spec 1.1 or 2.0??
I am giving a wsdl according to WSDL 1.1 (which is
running fine with the WSDL2Java of Axis 1.2.1 and
generating client stubs)
But in this case of WSDL2Java of Axis2 its throwing an
error:

C:\WSDLS>java org.apache.axis.wsdl.WSDL2Java -uri
RPCServices.wsdl

Exception in thread "main"
java.lang.NullPointerException
at
org.apache.axis.wsdl.codegen.CodeGenConfiguration.(CodeGenConfi
guration.java:57)
at
org.apache.axis.wsdl.codegen.CodeGenConfiguration.(CodeGenConfi
guration.java:50)
at
org.apache.axis.wsdl.codegen.CodeGenerationEngine.(CodeGenerati
onEngine.java:66)
at
org.apache.axis.wsdl.WSDL2Code.main(WSDL2Code.java:28)
at
org.apache.axis.wsdl.WSDL2Java.main(WSDL2Java.java:22)


Can you let me know what is the problem???

Anshuk 

--- Ajith Ranabahu <[EMAIL PROTECTED]> wrote:

> hi,
> there were some code in 0.94 that did this WSDL
> generation but it was not
> really tested and was not made into a tool. But
> recently we've added the
> commandline tool support for this tool. You are
> welcome to test out
> Java2WSDL in the latest codebase.
> BTW we only generate doc/lit WSDL's :)
> 
> On 2/2/06, anshuk pal chaudhuri <[EMAIL PROTECTED]>
> wrote:
> >
> > Hi,
> >
> > In Axis2 to generate a wsdl from the interfaces
> and
> > different command line parameters (likewise in
> > previous axis versions using Java2WSDL) what is
> the
> > tool that is being used?
> >
> > Anshuk
> >
> > __
> > Do You Yahoo!?
> > Tired of spam?  Yahoo! Mail has the best spam
> protection around
> > http://mail.yahoo.com
> >
> 
> 
> 
> --
> Ajith Ranabahu
> 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: Adding AXIS2 Web Service to >NET

[Eran Chinthaka]

Hi Wasana,

You don't need to worry about FnRequest or FnResponse (or any other MSFT
crap ;) ). Just get the WSDL from the web service you want to invoke,
thats all you want.
You can code gen (or use OM) using that WSDL and can (hopefully) access
your .web services written using .net.

-- Chinthaka



Wasana Delpage wrote:

>Hi All,
>
>With axis2.0.94 i could able to attach the web reference.
>But I could not send any data to it and take them back.
>Because I dont have Idea on using of FnRequest and fnResponse how they works.
>
>Could anybody tell me how to do it
>
>regards
>
>Wasana
>
>  
>


signature.asc
Description: OpenPGP digital signature

Re: ServiceFactory in Axis2?

[Deepal Jayasinghe]

hmm , we don't have such a thing in Axis2 

 
you have to do the following
 
1. to create a service client ; ServiceCliet sc= 
new ServiceClinet();
2. To get operation client form service client ; 
sc.createClinet(opName);
 
Thanks, Deepal~Future 
is Open~

  - Original Message - 
  From: 
  [EMAIL PROTECTED] 
  
  To: axis-user@ws.apache.org 
  Sent: Thursday, February 02, 2006 10:04 
  PM
  Subject: ServiceFactory in Axis2?
  
  
  What is the equivalent of 
  org.apache.axis.client.ServiceFactory in Axis2 so that it can be plugged into 
  a Spring-based client?
   
  Thanks

Adding AXIS2 Web Service to >NET

[Wasana Delpage]

Hi All,

With axis2.0.94 i could able to attach the web reference.
But I could not send any data to it and take them back.
Because I dont have Idea on using of FnRequest and fnResponse how they works.

Could anybody tell me how to do it

regards

Wasana

Re: [Axis2].0.94 Isuue on Examples

[Ajith Ranabahu]

Hi Wasana,
If you can point out the exact problems it will be really helpful for us to fix the documentationOn 2/3/06, Wasana Delpage <
[EMAIL PROTECTED]> wrote:To whom it may concernThere is a differet between axis 
2.0.94Examples and user guide.If somebody responsible pls do the necessary corrections.RegardsWasana-- Ajith Ranabahu

[Axis2].0.94 Isuue on Examples

[Wasana Delpage]

To whom it may concern

There is a differet between axis 2.0.94
Examples and user guide.

If somebody responsible pls do the necessary corrections.

Regards

Wasana

Re: Axis 1.1 Compatability Question

[Mukesh Kumar Maniraj]

Hi,
Axis 1.1  is not compatible with jdk 1.5, we had to migrate to Axis 1.2.1,
-MukeshOn 2/2/06, Pat Young <[EMAIL PROTECTED]> wrote:
I'm trying to run Axis 1.1 under Java 1.5 and I am getting errors
out of my Axis libraries.  Is Axis 1.1 consider to be compatable
with Java 1.5 or is Java 1.4 the last version it is certified to run
with?Thanks,Pat Young
		  
What are the most popular cars? Find out at 
Yahoo! Autos 

Re: Digital signatures on AXIS?

[Hernan Bay Area Guy]

Thanks for the replies, will check the links you sent!

-- Hernan



__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: Status w/r/t memory leaks...

[Jesse Sightler]

Never mind... I figured it out.  We were (incorrectly) trying to use method overloading in a web service.I'm running the memory leak tests for this now.Thanks,Jess
On 2/2/06, Jesse Sightler <[EMAIL PROTECTED]> wrote:
Have there been significant changes on the trunk related to .jws files?  My calls to one are now failing with:Caused by: java.lang.ArrayIndexOutOfBoundsException    at org.apache.axis.providers.java.RPCProvider.processMessage

(RPCProvider.java:129)    at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:327)    at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)    at org.apache.axis.SimpleChain.doVisiting

(SimpleChain.java:118)    at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)    at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)    at org.apache.axis.server.AxisServer.invokeService

(AxisServer.java:239)    at org.apache.axis.server.AxisServer.invoke(AxisServer.java:380)    at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)    at javax.servlet.http.HttpServlet.service

(HttpServlet.java:717)    at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)    at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter

(ApplicationFilterChain.java:252)    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)    at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java

:81)    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)

    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)    at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke

(CustomPrincipalValve.java:39)    at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)    at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java

:59)    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)    at org.apache.catalina.valves.FastCommonAccessLogValve.invoke

(FastCommonAccessLogValve.java:481)    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)    at 
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)    at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)    at java.lang.Thread.run
()V(Unknown Source)
However, this had worked perfectly with the 1.3 binaries.Thanks,JessOn 2/1/06, 
Davanum Srinivas <
[EMAIL PROTECTED]> wrote:plz use the trunk.On 2/1/06, Jared Klett <
[EMAIL PROTECTED]> wrote:> hi Dims,>> ok, the SVN checkout is proceeding - I'm looking in the branches/
> subdir - should I build "AXIS_1_4_FINAL" to get those 3 fixes, or
> should I be in the trunk, or something else? thanks!>> cheers,>> - Jared>> On 2/1/06, Davanum Srinivas <
[EMAIL PROTECTED]> wrote:
> > "svn co http://svn.apache.org/repos/asf/webservices/axis/ axis"
> >> > -- dims> >> > On 2/1/06, Jared Klett <
[EMAIL PROTECTED]> wrote:> > > greetings all,> > >> > > That's funny, I was just working on composing a long message
> > > describing the memory issue I'm having with Axis+Tomcat that I haven't
> > > been able to solve by tweaking JVM memory or GC parameters or by> > > upgrading to Axis 1.3.> > >> > > So Dims, you're saying to do a checkout of the latest CVS according to
> > > this page:> > >> > > http://ws.apache.org/axis/cvs.html
> > >> > > and do our own build, which will give us 
1.3 + the 3 fixes detailed in JIRA?> > >> > > just want to confirm... thanks!> > >> > > cheers,> > >> > > - Jared> > >> > > On 2/1/06, Davanum Srinivas <
[EMAIL PROTECTED]> wrote:> > > > All 3 are fixed in latest SVN.> > > >> > > > thanks,
> > > > dims> > > >
> > > > On 2/1/06, Jesse Sightler <[EMAIL PROTECTED]> wrote:> > > > > I've seen several issues in JIRA relating to memory leaks on the server-side
> > > > > of Axis recently.> > > > >> > > > > Specifically, I've noticed:> > > > > 
http://issues.apache.org/jira/browse/AXIS-2278
> > > > > https://issues.apache.org/jira/browse/AXIS-2266> > > > > 

https://issues.apache.org/jira/browse/AXIS-2185> > > > >> > > > > What ar

Re: Status w/r/t memory leaks...

[Jesse Sightler]

Have there been significant changes on the trunk related to .jws files?  My calls to one are now failing with:Caused by: java.lang.ArrayIndexOutOfBoundsException    at org.apache.axis.providers.java.RPCProvider.processMessage
(RPCProvider.java:129)    at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:327)    at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)    at org.apache.axis.SimpleChain.doVisiting
(SimpleChain.java:118)    at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)    at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)    at org.apache.axis.server.AxisServer.invokeService
(AxisServer.java:239)    at org.apache.axis.server.AxisServer.invoke(AxisServer.java:380)    at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)    at javax.servlet.http.HttpServlet.service
(HttpServlet.java:717)    at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)    at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:252)    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)    at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java
:81)    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)    at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke
(CustomPrincipalValve.java:39)    at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)    at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java
:59)    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)    at org.apache.catalina.valves.FastCommonAccessLogValve.invoke
(FastCommonAccessLogValve.java:481)    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)    at 
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)    at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)    at java.lang.Thread.run()V(Unknown Source)
However, this had worked perfectly with the 1.3 binaries.Thanks,JessOn 2/1/06, Davanum Srinivas <
[EMAIL PROTECTED]> wrote:plz use the trunk.On 2/1/06, Jared Klett <
[EMAIL PROTECTED]> wrote:> hi Dims,>> ok, the SVN checkout is proceeding - I'm looking in the branches/> subdir - should I build "AXIS_1_4_FINAL" to get those 3 fixes, or
> should I be in the trunk, or something else? thanks!>> cheers,>> - Jared>> On 2/1/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> > "svn co http://svn.apache.org/repos/asf/webservices/axis/ axis"> >> > -- dims> >> > On 2/1/06, Jared Klett <
[EMAIL PROTECTED]> wrote:> > > greetings all,> > >> > > That's funny, I was just working on composing a long message> > > describing the memory issue I'm having with Axis+Tomcat that I haven't
> > > been able to solve by tweaking JVM memory or GC parameters or by> > > upgrading to Axis 1.3.> > >> > > So Dims, you're saying to do a checkout of the latest CVS according to
> > > this page:> > >> > > http://ws.apache.org/axis/cvs.html> > >> > > and do our own build, which will give us 
1.3 + the 3 fixes detailed in JIRA?> > >> > > just want to confirm... thanks!> > >> > > cheers,> > >> > > - Jared> > >> > > On 2/1/06, Davanum Srinivas <
[EMAIL PROTECTED]> wrote:> > > > All 3 are fixed in latest SVN.> > > >> > > > thanks,> > > > dims> > > >
> > > > On 2/1/06, Jesse Sightler <[EMAIL PROTECTED]> wrote:> > > > > I've seen several issues in JIRA relating to memory leaks on the server-side
> > > > > of Axis recently.> > > > >> > > > > Specifically, I've noticed:> > > > > http://issues.apache.org/jira/browse/AXIS-2278
> > > > > https://issues.apache.org/jira/browse/AXIS-2266> > > > > 
https://issues.apache.org/jira/browse/AXIS-2185> > > > >> > > > > What are peoples current experiences with memory leaks in Axis1?  Is the CVS> > > > > version significantly more stable than the current release version?  Is a
> > > > > 1.4 release forthcoming to resolve the issues?> > > > >> > > > > Thanks,> 

Re: [axis2]module.xml not found for the module

[Aaron Evans]

Aaron Evans  yahoo.ca> writes:

> 
> I had solved this problem when running stand-alone (client stub) by re-naming 
> addressing.mar to axis-addressing-module.jar and putting in my classpath.
> 
> It works great until I deploy my WS client code as part of a servlet app in 
> tomcat and all of a sudden it doesn't work and i get the error above.
> 
> I looked at some of the code in the DeploymentEngine and it seems as though
> the class loaders are getting mucked around with and perhaps that is the 
> problem.
> 
> I am really at a loss here because it wouldn't be my home directory but 
> rather tomcat's.  I am running tomcat 5.5 on windows, so who knows where
> the "home directory" will be...
> 
>

Ok, so I bit the bullet and created a configurable "axis home" in my web app.

You can then use any location on your file system as axis home.  For example,
create a directory called axis-home in /tmp.  Then your axis home path is
/tmp/axis-home.

Put the modules directory in there and addressing.mar in the modules directory.

Then, make a constructor like this for your client:

public WSClientStub(String targetEndpoint, String axisHome) throws 
java.lang.Exception
{
   this(new 
org.apache.axis2.context.ConfigurationContextFactory().
createConfigurationContextFromFileSystem(axisHome),
 targetEndpoint);
}

And pass in your ws endpoint and axis home to construct an instance of the
client.

I hope this helps someone else.  But I think it is somewhat rediculous
to have to have external file resources etc for simply using the client API!

BTW, windows STILL won't let me delete the .axis2 directory in my home 
directory.  I get "Access Denied" not matter what.  I have tried everything.
At some point, I will create a boot cd to boot my laptop into dos and delete
it that way I guess...

aaron

OMElement and XML namespaces

[Randy Hoffman]

I have a question about the way axis2 handles XML namespaces.  I create
three namespaces and then declare them at the root OMElement.  I then
create child OMElements using the namespaces declared in the root element.
Upon the first reference of a prefix in a child element, a xmlns:"mynamespace" 
gets created on that element.  Further use of the prefix does not generate the

xmlns: attribute.  Shouldn't the element be able to reference the declared
namespace in the root element?  Here is an example.

This is what i would expect by declaring ord, prd and ven namespaces:

http://order/"; xmlns:prd="http://product/"; 
xmlns:ven="http://vendor/";>
 12345
 54321
 123
 1


This is what i get when i build the OMElement:

http://order/"; xmlns:prd="http://product/"; 
xmlns:ven="http://vendor/";>
 http://product/";>12345
 54321
 http://vendor/";>123
 1


I would expect the namespace definition would not have to be repeated in 
the first reference.


Am i doing something wrong, or is this intentional, or possibly a bug?

Thanks,
randy

Re: Axis Bug ?- Unable to download large files using Axis Attachments-Need Help

[Pradeep Reddy]

			Hi all,I am hitting the same exception with Axis 1.2 RC2. Has any one else seen this error?Any Help would be greatly appreciated!Pradeep
			Mukesh Kumar Maniraj
			Thu, 02 Feb 2006 10:20:35 -0800
		







Hi,

I am using Axis 1.2.1 and trying to pass files, using the axis attachment support,

I works fine for  small files, but when I try to pass 3MB file, I am getting and exception from Axis on the server side,

Please note that, when I use Axis 1.1  there is no problem sending large files(I tested upto 50 MB).

This exception happens only in Axis 1.2.1 and also Axis 1.3.

I cannot go back to Axis 1.1 because we have upgraded to jdk1.5,

Any help to solve this problem  is very much appreciated ,

Thanks,

-Mukesh Kumar


Stack trace Snippet:(Please see full stack trace, client and server side code attached)

===

AxisFault

 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException




 faultSubcode:

 faultString: java.io.IOException: End of physical stream detected when 133 more bytes expected.

 faultActor:

 faultNode:

 faultDetail:

   
{http://xml.apache.org/axis/}stackTrace:java.io.IOException: End of
physical stream detected when 133 more bytes expected.

   
at
org.apache.axis.attachments.DimeDelimitedInputStream._read(DimeDelimitedInputStream.java:273)

   
at
org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:201)

   
at
org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:445)

   
at
org.apache.axis.attachments.ManagedMemoryDataSource.(ManagedMemoryDataSource.java:146)

   
at
org.apache.axis.attachments.MultiPartDimeInputStream.readTillFound(MultiPartDimeInputStream.java:163)

   
at
org.apache.axis.attachments.MultiPartDimeInputStream.readAll(MultiPartDimeInputStream.java:100)

   
at
org.apache.axis.attachments.MultiPartDimeInputStream.getAttachments(MultiPartDimeInputStream.java:108)

   
at
org.apache.axis.attachments.AttachmentsImpl.mergeinAttachments(AttachmentsImpl.java:156)

   
at
org.apache.axis.attachments.AttachmentsImpl.getAttachmentCount(AttachmentsImpl.java:515)

   
at
com.cisco.aons.ama.provision.ExtensionPackageManager.downloadExtensionPackage(ExtensionPackageManager.java:8



CompleteStack Trace of the Axis excption thrown on the server side.text

Description: Binary data
Server side Code to download the attched file:===public static void downloadExtensionPackage() throws Exception  {Attachments atchmts = CurrentAttachment.getAttachment
();MessageContext messageContext=MessageContext.getCurrentContext();if (messageContext != null) {Message message = messageContext.getRequestMessage();Attachments messageAttachments = 
message.getAttachmentsImpl();   if(messageAttachments != null && messageAttachments.getAttachmentCount() > 0 ){atchmts = messageAttachments;   }   }if (atchmts == null || 
atchmts.getAttachmentCount() == 0 ) return;   try{File dest = new File(extPackagePath);if (dest.exists()) {assert(dest.isDirectory());} else {
dest.mkdirs();}//int attachmentcount=atchmts.getAttachmentCount();//log.info("YES  attachments support, attachment count : "+attachmentcount);String extPackageName = "ext-bundle" + 
aonsBundle.getId() + ".zip";Iterator iterator=atchmts.getAttachments().iterator();while(iterator.hasNext()){AttachmentPart part=(AttachmentPart)iterator.next();DataHandlerdataHandler   = 
part.getDataHandler();log.info("Attachment file name :"+dataHandler.getName());dataHandler.writeTo(new java.io.FileOutputStream( extPackagePath+ File.separator +extPackageName));
part.dispose();}log.info("YES  successfully executed attachment download");CurrentAttachment.clear();}catch (AxisFault axisFaultException){
log.error("AxisFaultException thrown :" + axisFaultException.dumpToString());}catch (Exception exception){log.error("Exception thrown : ", exception);}
  //new code added by mukesh ends  here //}  }Client side Code to attach the file:Service service = new Service();Call call = (Call) 
service.createCall();..   if (aonsBundle != null &&aonsBundle.getExtensionsZipArchiveFullPath() != null) {
call.setProperty(Call.ATTACHMENT_ENCAPSULATION_FORMAT, Call.ATTACHMENT_ENCAPSULATION_FORMAT_DIME);   AttachmentPart attachmentPart = new AttachmentPart(new
   DataHandler(new  

Re: Can't find module.xml

[Aaron Evans]

Bryan Allen  sas.com> writes:

> 
> Look in:  %UserProfile%.  This is where my .axis2 folder was located when I
had this problem.
> 
> If your username is gikxh06, that should resolve to something like
C:\Documents and Settings\gikxh06 on XP.
> 
> Bryan Allen
> SAS Institute

Windows won't let me delete it! I get access denied no matter what!
Any suggestions?

Re: [axis2]module.xml not found for the module

[Aaron Evans]

Ruchith Fernando  gmail.com> writes:

> 
> Hi,
> 
> This is because addressing.mar cannot be found and this is a known
> issue with the 0.94 release.
> Solution From:  http://ws.apache.org/axis2/download.cgi


I had solved this problem when running stand-alone (client stub) by re-naming 
addressing.mar to axis-addressing-module.jar and putting in my classpath.

It works great until I deploy my WS client code as part of a servlet app in 
tomcat and all of a sudden it doesn't work and i get the error above.

I looked at some of the code in the DeploymentEngine and it seems as though
the class loaders are getting mucked around with and perhaps that is the 
problem.

I am really at a loss here because it wouldn't be my home directory but 
rather tomcat's.  I am running tomcat 5.5 on windows, so who knows where
the "home directory" will be...

RE: (Axis 1.3) Our app includes 2 clients; how do I specify different handlers for each?

[Olano, Ever]

I don't know if this applies to you but there was one time when I was
experimenting with the config file too and I found that I could specify
the filename either via the System.property "axis.ClientConfigFile" or
by doing the following in your code:

org.apache.axis.EngineConfiguration config
= new org.apache.axis.configuration.FileProvider(
"/my_path_to/client-config.wsdd" );
MyLocator service   = new MyLocator( config );

where MyLocator is a placeholder for the locator class generated for you
by WSDL2Java.

Hope that helps.
Ever

-Original Message-
From: GEORGE MCKINNEY [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 02, 2006 1:16 PM
To: Axis Users
Subject: (Axis 1.3) Our app includes 2 clients; how do I specify
different handlers for each?

We've got two different webservices that we want to be able to call with
clients generated by Axis 1.3, and use slightly different handlers for
each (but with more than one request handler in each case ). Because it
is likely that "two" will change over time, I'd like to make each
client's handler chain independent. What's the best way to do that?

Some experimentation leads me to believe that Axis can find a
"client-config.wsdd" anywhere in the classpath. Trying to decipher the
source leads me to believe that I could set a configuration property on
each service to specify the name of that file, but I'm in a fog about
the details. That would be my preferred option, because the client for
each service could use a uniquely named ( or located, and have the
configuration specify the package  ) config file. How?

I also see a getHandlerRegistry().getHandlerChain() - which makes sense
to me from similar work with WebLogic's SOAP tools, but it isn't clear
how the org.apache.axis.handlers.BasicHandler maps to the handlers those
tools work with. Can someone explain?

Finally, there is a service element available for the .wsdd ( in
http://wiki.apache.org/ws/FrontPage/Axis/WSDDReferences/WSDD_XSD  ) that
appears to be parallel to the  we use now, but the
documentation seems to suggest that it is for use server-side, rather
than for a client that is going to be using the specified Service. Am I
misunderstanding?

Thanks for your time,
George McKinney

Re: OutOfMemoryError when submitting large SOAP requests to Axis

[Linus Kamb]

Hi, Jared.

doc/lit wrapped is the web service "style".  There are various styles:
primarily RPC-encoded, document/literal, and "wrapped" which is a
variation on document/literal.  Much information available about that. 
The following is probably not the best introductory information, but I
happened to see it this morning:

http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/

I guess I was just wondering if your web service was trying to parse
the SOAP msg XML into a DOM Element.

I haven't tried mulitple simultaneous submits.  I suppose my service
might run out of memory too. 

I have my java startup params set to -Xmx768m, and I currently reject
messages over 2MB (rather than trying to parse the XML.)

I suppose this isn't going to help your situation.   I'm going to look
into the attachment streaming that Dims mentioned for my app.

Linus


Jared Klett wrote:

  hi Linus,

I can send a single request at a time of the required size, and it
will succeed. However, when I start more simultaneous requests beyond
the first one, they invariably fail with OutOfMemoryErrors. The OOM
occurs somewhere inside of Axis.

The web service works like this: it runs inside Tomcat, and passes
through a couple of Tomcat filters before reaching the AxisServlet.
I've monitored the logging, and all simultaneous requests make it
through the filters with no problem. Once the flow passes into the
AxisServlet, and subsequently to SOAPMonitor, the OOM's start to
occur.

I attached a debug log snippet to the initial message in this thread.

Also, what do you mean by "doc/lit wrapped"?

cheers,

- Jared

On 2/2/06, Linus Kamb <[EMAIL PROTECTED]> wrote:
  
  
What "style" of web service are  you using?

I have successfully sent attachments of > 200MB using doc/lit wrapped,
and I'm sure I could send larger ones.
The trouble I run into is when I try to parse the attachments (they are
XML,) but that is outside of Axis/SOAP.


Jared Klett wrote:



  greetings all,

I've taken a contract job to improve the performance of a Java Web
Service based on Axis. The service is required to handle multiple
simultaneous SOAP requests that can be anywhere from  two to 100 MB in
size. So far, the service fails with an OutOfMemoryError when I submit
any more than one simultaneous request at a time.

I participated in a previous thread entitled "Status w/r/t memory
leaks..." started by Jesse Sightler. I've tried the Axis 1.3 final
release, as well as a version built from the trunk of the latest (as
of yesterday) SVN source tree.

The SOAP requests have a number of attachments in the form of
base64-encoded data, which look something like this:


spacer.gif
R0lGODlhAQABAIAAACH5BAEALAABAAEAAAICRAEAOw==


The content inside the  tag can be extremely large - as I
mentioned, these requests can be upwards of 100 MB in size.

I've tweaked the JVM parameters, setting the max and initial heap
sizes, the perm gen heap size, as well as trying several different
options to change the behavior of the garbage collector - all to no
avail.

I've narrowed down the problem down to the point where I'm sure it's
happening somewhere inside of Axis - the request is submitted to
AxisServlet, then passed to SOAPMonitor via an invoke() call.

Here is a snippet of the debug log output before the OOM happens:

[] [2006-01-30 15:45:23,404] SAXOutputter - SAXOutputter.endElement
['' reporterCcc]
[] [2006-01-30 15:45:23,404] ProjectResourceBundle -
org.apache.axis.i18n.resource::handleGetObject(endElem00)
[] [2006-01-30 15:45:23,404] SerializationContext - End element reporterCcc
[] [2006-01-30 15:45:23,404] NSStack - NSPop (32)
[] [2006-01-30 15:45:23,404] SAXOutputter - SAXOutputter.endElement
['http://.yyy.com' fileTestSubmission]
[] [2006-01-30 15:45:23,404] ProjectResourceBundle -
org.apache.axis.i18n.resource::handleGetObject(endElem00)
[] [2006-01-30 15:45:23,404] SerializationContext - End element
q1:fileTestSubmission
[] [2006-01-30 15:45:23,404] NSStack - NSPop (32)
[] [2006-01-30 15:45:23,404] SAXOutputter - SAXOutputter.endElement
['http://schemas.xmlsoap.org/soap/envelope/' Body]
[] [2006-01-30 15:45:23,404] ProjectResourceBundle -
org.apache.axis.i18n.resource::handleGetObject(endElem00)
[] [2006-01-30 15:45:23,404] SerializationContext - End element soap:Body
[] [2006-01-30 15:45:23,404] NSStack - NSPop (32)
[] [2006-01-30 15:45:23,404] SAXOutputter - SAXOutputter.endElement
['http://schemas.xmlsoap.org/soap/envelope/' Envelope]
[] [2006-01-30 15:45:23,404] ProjectResourceBundle -
org.apache.axis.i18n.resource::handleGetObject(endElem00)
[] [2006-01-30 15:45:23,404] SerializationContext - End element soap:Envelope
[] [2006-01-30 15:45:23,404] ProjectResourceBundle -
org.apache.axis.i18n.resource::handleGetObject(empty00)
[] [2006-01-30 15:45:23,405] NSStack - NSPop (empty)
[] [2006-01-30 15:45:23,405] SAXOutputter - SAXOutputter.endDocument
[] [2006-01-30 15:45:38,782] ProjectResourceBundle -
org.apache

(Axis 1.3) Our app includes 2 clients; how do I specify different handlers for each?

[GEORGE MCKINNEY]

We've got two different webservices that we want to be able to call with 
clients generated by Axis 1.3, and use slightly different handlers for each 
(but with more than one request handler in each case ). Because it is likely 
that "two" will change over time, I'd like to make each client's handler chain 
independent. What's the best way to do that?

Some experimentation leads me to believe that Axis can find a 
"client-config.wsdd" anywhere in the classpath. Trying to decipher the source 
leads me to believe that I could set a configuration property on each service 
to specify the name of that file, but I'm in a fog about the details. That 
would be my preferred option, because the client for each service could use a 
uniquely named ( or located, and have the configuration specify the package  ) 
config file. How?

I also see a getHandlerRegistry().getHandlerChain() - which makes sense to me 
from similar work with WebLogic's SOAP tools, but it isn't clear how the 
org.apache.axis.handlers.BasicHandler maps to the handlers those tools work 
with. Can someone explain?

Finally, there is a service element available for the .wsdd ( in 
http://wiki.apache.org/ws/FrontPage/Axis/WSDDReferences/WSDD_XSD  ) that 
appears to be parallel to the  we use now, but the 
documentation seems to suggest that it is for use server-side, rather than for 
a client that is going to be using the specified Service. Am I misunderstanding?

Thanks for your time,
George McKinney

Axis 1.1 Compatability Question

[Pat Young]

I'm trying to run Axis 1.1 under Java 1.5 and I am getting errors out of my Axis libraries.  Is Axis 1.1 consider to be compatable with Java 1.5 or is Java 1.4 the last version it is certified to run with?Thanks,Pat Young
		  
What are the most popular cars? Find out at Yahoo! Autos 

axis client on CDC/PP application

[Lucas de Oliveira]

Hello!Is it possible to run an axis client on a CDC/PP application that use the IBM j9 virtual machine?
I need to acces a web service from the PDA and it looks like the stub generated by WSDL2Java is not good for the vm on the PDA.
 
many thanks!
 
 

Re: OutOfMemoryError when submitting large SOAP requests to Axis

[Jared Klett]

hi Linus,

I can send a single request at a time of the required size, and it
will succeed. However, when I start more simultaneous requests beyond
the first one, they invariably fail with OutOfMemoryErrors. The OOM
occurs somewhere inside of Axis.

The web service works like this: it runs inside Tomcat, and passes
through a couple of Tomcat filters before reaching the AxisServlet.
I've monitored the logging, and all simultaneous requests make it
through the filters with no problem. Once the flow passes into the
AxisServlet, and subsequently to SOAPMonitor, the OOM's start to
occur.

I attached a debug log snippet to the initial message in this thread.

Also, what do you mean by "doc/lit wrapped"?

cheers,

- Jared

On 2/2/06, Linus Kamb <[EMAIL PROTECTED]> wrote:
> What "style" of web service are  you using?
>
> I have successfully sent attachments of > 200MB using doc/lit wrapped,
> and I'm sure I could send larger ones.
> The trouble I run into is when I try to parse the attachments (they are
> XML,) but that is outside of Axis/SOAP.
>
>
> Jared Klett wrote:
>
> >greetings all,
> >
> >I've taken a contract job to improve the performance of a Java Web
> >Service based on Axis. The service is required to handle multiple
> >simultaneous SOAP requests that can be anywhere from  two to 100 MB in
> >size. So far, the service fails with an OutOfMemoryError when I submit
> >any more than one simultaneous request at a time.
> >
> >I participated in a previous thread entitled "Status w/r/t memory
> >leaks..." started by Jesse Sightler. I've tried the Axis 1.3 final
> >release, as well as a version built from the trunk of the latest (as
> >of yesterday) SVN source tree.
> >
> >The SOAP requests have a number of attachments in the form of
> >base64-encoded data, which look something like this:
> >
> >
> >spacer.gif
> >R0lGODlhAQABAIAAACH5BAEALAABAAEAAAICRAEAOw==
> >
> >
> >The content inside the  tag can be extremely large - as I
> >mentioned, these requests can be upwards of 100 MB in size.
> >
> >I've tweaked the JVM parameters, setting the max and initial heap
> >sizes, the perm gen heap size, as well as trying several different
> >options to change the behavior of the garbage collector - all to no
> >avail.
> >
> >I've narrowed down the problem down to the point where I'm sure it's
> >happening somewhere inside of Axis - the request is submitted to
> >AxisServlet, then passed to SOAPMonitor via an invoke() call.
> >
> >Here is a snippet of the debug log output before the OOM happens:
> >
> >[] [2006-01-30 15:45:23,404] SAXOutputter - SAXOutputter.endElement
> >['' reporterCcc]
> >[] [2006-01-30 15:45:23,404] ProjectResourceBundle -
> >org.apache.axis.i18n.resource::handleGetObject(endElem00)
> >[] [2006-01-30 15:45:23,404] SerializationContext - End element reporterCcc
> >[] [2006-01-30 15:45:23,404] NSStack - NSPop (32)
> >[] [2006-01-30 15:45:23,404] SAXOutputter - SAXOutputter.endElement
> >['http://.yyy.com' fileTestSubmission]
> >[] [2006-01-30 15:45:23,404] ProjectResourceBundle -
> >org.apache.axis.i18n.resource::handleGetObject(endElem00)
> >[] [2006-01-30 15:45:23,404] SerializationContext - End element
> >q1:fileTestSubmission
> >[] [2006-01-30 15:45:23,404] NSStack - NSPop (32)
> >[] [2006-01-30 15:45:23,404] SAXOutputter - SAXOutputter.endElement
> >['http://schemas.xmlsoap.org/soap/envelope/' Body]
> >[] [2006-01-30 15:45:23,404] ProjectResourceBundle -
> >org.apache.axis.i18n.resource::handleGetObject(endElem00)
> >[] [2006-01-30 15:45:23,404] SerializationContext - End element soap:Body
> >[] [2006-01-30 15:45:23,404] NSStack - NSPop (32)
> >[] [2006-01-30 15:45:23,404] SAXOutputter - SAXOutputter.endElement
> >['http://schemas.xmlsoap.org/soap/envelope/' Envelope]
> >[] [2006-01-30 15:45:23,404] ProjectResourceBundle -
> >org.apache.axis.i18n.resource::handleGetObject(endElem00)
> >[] [2006-01-30 15:45:23,404] SerializationContext - End element soap:Envelope
> >[] [2006-01-30 15:45:23,404] ProjectResourceBundle -
> >org.apache.axis.i18n.resource::handleGetObject(empty00)
> >[] [2006-01-30 15:45:23,405] NSStack - NSPop (empty)
> >[] [2006-01-30 15:45:23,405] SAXOutputter - SAXOutputter.endDocument
> >[] [2006-01-30 15:45:38,782] ProjectResourceBundle -
> >org.apache.axis.i18n.resource::handleGetObject(exception00)
> >[] [2006-01-30 15:45:38,782] EXCEPTIONS - Exception:
> >java.lang.OutOfMemoryError: Java heap space
> >
> >I have been looking at the source code to Axis, and I note that in
> >SOAPPart, around line 444, data is loaded via an InputStream into a
> >memory-resident byte array. So far that's the only place I can find
> >that might actually be causing the problem.
> >
> >It seems logical that a large SOAP request that is separated into
> >attachments should be written to disk, and then parsed inside of a
> >buffer. Here is a link to an article with such a code example (under
> >"Receive and process a SOAP message with SAAJ", a little more than
> >halfway down 

Re: wss4j and axis2

[Brian Shields]

Thanks Ruchith, That worked. I had the module installed correctly but 
the client was not aware of the axis2.xml file. creating a ServiceClient 
with custom repository worked.
I am aware that for service specific settings i will have to configure 
the services.xml file, that will be done in due course. For now I am 
going to get encryption and signatures working at a global!

Thanks again,
Brian.

Ruchith Fernando wrote:


If you are using the axis2.xml file to configure security module
parameters in the server side, please note that those configurations
will be applicable to ALL the services in that axis2 repository.
Therefore if you want to configure security on a per service basis you
MUST use the services.xml file to configure the parameters.

Thanks,
Ruchith

On 2/2/06, Ruchith Fernando <[EMAIL PROTECTED]> wrote:
 


Hi Brian,

If you get "the request does not contain the required Security
headers" then it seems like the security module is not deployed at the
client side OR the configured axis2.xml file is not picked up by the
client. You MUST provide this configured axis2.xml file along with a
repository containing the security.mar in the 'modules' directory. [1]

- Are you providing the repository location to the ServiceClient?

  - If NOT, please provide an axis2 repository with the 'modules'
directory as as sub directory and make sure you have security
configured [2] axis2.xml file in the repo directory (if you are using
the SVN HEAD axis2.xml file should be in the 'conf' directory in the
repo direcotry).

 - If YES, the please check whether you have the security.mar file in
the 'modules' directory of the repo.

Thanks,
Ruchith

Notes:
[1] Creating a ServiceClient with a custom repository:

ConfigurationContext ctx =
ConfigurationContextFactory.createConfigurationContextFromFileSystem("/path/to/axis2/repo",
"path/to/configured/axis2.xml");
   ServiceClient serviceClient = new ServiceClient(ctx, null);


[2] Security configured mean that you must have the  entry in axis2.xml along with the required
inflow/outflow parameters. But if you don't have the  entry in the axis2.xml you can engage the security
module using the ServiceClient object as shown beow:

   serviceClient.engageModule(new QName("security"));

[3] Make sure you include the commons-codec.jar in the client's and
server's classpath (in WEB-INF/lib directory in the case of Tomcat)

On 2/2/06, Brian Shields <[EMAIL PROTECTED]> wrote:
   


Thanks for the reply Ruchith,
What do you mean by the axis2.xml file of the client? Is this the same
axis2.xml file as that of the server if one is calling a service from
localhost? I am using 2 deployments of axis2 on two different machines,
one of which i have the two parameters below included in the axis2. This
is my server. My client machine on the other hand has the same
configurations all down to the axis2.xml file where i have only the
OutflowSecurity parameter included.
When calling the service i get an error saying that the request does not
contain the required Security headers!! I have used tcpmon and the
message is being sent successfully, without the security header! Is it
possible that the client is ignoring the axis2.xml configurations when
calling the service? I presume the axis2.xml replaces the
client_deploy.wsdd file!
Thanks,
Brian.

Ruchith Fernando wrote:

 


Hi Brian,

Please see my comments below:

On 2/2/06, Brian Shields <[EMAIL PROTECTED]> wrote:


   


Hello,
I am deploying security handlers in axis2. My question may be very
simple, apologies if the answer is staring me in the face!!
Where is the best place to include security tokens in the client? I have
altered the axis2.xml file to include a parameters in the inflow and
outflow..

  
  Timestamp
  
  

  
  
  Timestamp
  
  
From what i can make out, the outflowsecurity parmeter refers to any
security tokens which will be added in the outflow of a service request
and the inflowsecurity parameters are parameters which are expected for
the service to be invoked?!?


 


Correct !!!

The above configuration will ensure that a Timestamp is added to the
outgoing message and it will require all incoming messages to contain
a Timestamp header.



   


Where then are they applied to the client? Using the Options parameters?


 


With the Axis2-0.94 release we support setting the client parameters
in the axis2.xml of the client. And from the next release you will be
able to set the configuration via Options parameters (Using
org.apache.axis2.security.handler.config.InflowConfiguration and
org.apache.axis2.security.handler.config.OutflowConfiguration). This
feature is already available in the SVN HEAD.

Thanks,
Ruchith



   


Thanks,
Brian.

--
Brian Shields BSc. MSc.,
PhD Candidate,
Department of Information Technology,
National University of Ireland,
Galway,
Ireland.



 




   


--
Brian Shields BSc. MSc.,
PhD Candidate,
Department of Infor

Axis Bug ?- Unable to download large files using Axis Attachments-Need Help

[Mukesh Kumar Maniraj]

Hi,

I am using Axis 1.2.1 and trying to pass files, using the axis attachment support,

I works fine for  small files, but when I try to pass 3MB file, I am getting and exception from Axis on the server side,

Please note that, when I use Axis 1.1  there is no problem sending large files(I tested upto 50 MB).

This exception happens only in Axis 1.2.1 and also Axis 1.3.

I cannot go back to Axis 1.1 because we have upgraded to jdk1.5,

Any help to solve this problem  is very much appreciated ,

Thanks,

-Mukesh Kumar


Stack trace Snippet:(Please see full stack trace, client and server side code attached)

===

AxisFault

 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException



 faultSubcode:

 faultString: java.io.IOException: End of physical stream detected when 133 more bytes expected.

 faultActor:

 faultNode:

 faultDetail:

   
{http://xml.apache.org/axis/}stackTrace:java.io.IOException: End of
physical stream detected when 133 more bytes expected.

   
at
org.apache.axis.attachments.DimeDelimitedInputStream._read(DimeDelimitedInputStream.java:273)

   
at
org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:201)

   
at
org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:445)

   
at
org.apache.axis.attachments.ManagedMemoryDataSource.(ManagedMemoryDataSource.java:146)

   
at
org.apache.axis.attachments.MultiPartDimeInputStream.readTillFound(MultiPartDimeInputStream.java:163)

   
at
org.apache.axis.attachments.MultiPartDimeInputStream.readAll(MultiPartDimeInputStream.java:100)

   
at
org.apache.axis.attachments.MultiPartDimeInputStream.getAttachments(MultiPartDimeInputStream.java:108)

   
at
org.apache.axis.attachments.AttachmentsImpl.mergeinAttachments(AttachmentsImpl.java:156)

   
at
org.apache.axis.attachments.AttachmentsImpl.getAttachmentCount(AttachmentsImpl.java:515)

   
at
com.cisco.aons.ama.provision.ExtensionPackageManager.downloadExtensionPackage(ExtensionPackageManager.java:8


CompleteStack Trace of the Axis excption thrown on the server side.text
Description: Binary data

Server side Code to download the attched file:
===
public static void downloadExtensionPackage() throws Exception
  {


Attachments atchmts = CurrentAttachment.getAttachment();
MessageContext messageContext=MessageContext.getCurrentContext();
if (messageContext != null) {
Message message = messageContext.getRequestMessage();
Attachments messageAttachments = message.getAttachmentsImpl();
   if(messageAttachments != null && messageAttachments.getAttachmentCount() 
> 0 ){
atchmts = messageAttachments;
   }
   
}
if (atchmts == null || atchmts.getAttachmentCount() == 0 ) return;
   
try{
File dest = new File(extPackagePath);
if (dest.exists()) {
assert(dest.isDirectory());
} else {
dest.mkdirs();
}
//int attachmentcount=atchmts.getAttachmentCount();
//log.info("YES  attachments support, attachment count : 
"+attachmentcount);
String extPackageName = "ext-bundle" + aonsBundle.getId() + ".zip";
Iterator iterator=atchmts.getAttachments().iterator();
while(iterator.hasNext()){
AttachmentPart part=(AttachmentPart)iterator.next();
DataHandlerdataHandler   = part.getDataHandler();
log.info("Attachment file name :"+dataHandler.getName());
dataHandler.writeTo(new java.io.FileOutputStream( extPackagePath+ 
File.separator +extPackageName));
part.dispose();
}

log.info("YES  successfully executed attachment download");
CurrentAttachment.clear();
}
catch (AxisFault axisFaultException){
log.error("AxisFaultException thrown :" + 
axisFaultException.dumpToString());
}
catch (Exception exception){
log.error("Exception thrown : ", exception);
}
  //new code added by mukesh ends  here
 //}

  }
Client side Code to attach the file:

Service service = new Service();
Call call = (Call) service.createCall();

..

   
if (aonsBundle != null &&
aonsBundle.getExtensionsZipArchiveFullPath() != null) {

call.setProperty(Call.ATTACHMENT_ENCAPSULATION_FORMAT,
 Call.ATTACHMENT_ENCAPSULATION_FORMAT_DIME);
   
AttachmentPart attachmentPart = new AttachmentPart(new
   
DataHandler(new
   
FileDataSource(aonsBundle.
getExtensionsZipArchiveFullPath(;
call.addAttachmentPart(attachmentP

Re: already contains type 'string;

[Davanum Srinivas]

Could u please log a bug with your wsdl?

thanks,
dims

On 2/2/06, Axel Bernard <[EMAIL PROTECTED]> wrote:
>
> On 2 of February of 2006, Davanum Srinivas wrote:
>
> Dims,
>
> I build Axis2 from the latest SVN trunk but I still experience the same error.
> Do you need more details to figure-out what's happening ?
>
> Thanks,
>
> Axel
>
>
> > It has been fixed in latest SVN 
> > (http://issues.apache.org/jira/browse/AXIS2-382)
> >
> > thanks,
> > dims
> >
> > On 2/1/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
> > > It's a bug -- known problem, but I don't think it's been fixed yet.
> > >
> > >
> > > On 2/1/06, Axel Bernard <[EMAIL PROTECTED] > wrote:
> > > >
> > > > Gentlemen,
> > > >
> > > > I have a RuntimeException while trying to view the WSDL of a deployed
> > > service on axis2 - version 0.94
> > > >  [java]
> > > org.apache.axis2.wsdl.codegen.CodeGenerationException:
> > > java.lang.RuntimeException: java.lang.RuntimeException: Schema for 
> > > namespace
> > > 'http://wpm.accelior.com/v2/core/common/i18N/bo' already
> > > contains type 'string
> > > >  [java]
> > > org.apache.axis2.wsdl.codegen.CodeGenerationException:
> > > java.lang.RuntimeException: java.lang.RuntimeException: Schema for 
> > > namespace
> > > 'http://wpm.accelior.com/v2/core/common/i18N/bo' already
> > > contains type 'string
> > > >  [java] at
> > > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate
> > > (CodeGenerationEngine.java:118)
> > > >  [java] at
> > > org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:31)
> > > >  [java] at
> > > org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
> > > >  [java] Caused by: java.lang.RuntimeException:
> > > java.lang.RuntimeException: Schema for namespace
> > > 'http://wpm.accelior.com/v2/core/common/i18N/bo' already
> > > contains type 'string
> > > >  [java] at
> > > org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage
> > > (SimpleDBExtension.java:152)
> > > >  [java] at
> > > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:80)
> > > >  [java] ... 2 more
> > > >  [java] Caused by: java.lang.RuntimeException : Schema for namespace
> > > 'http://wpm.accelior.com/v2/core/common/i18N/bo' already
> > > contains type 'string
> > > > (...)
> > > >
> > > > When I executed WSDL2Java (using ADB) to generate my sources I had the
> > > same exception. Following forum posts on that topic, I've seen that it 
> > > was a
> > > known problem that could be solved by using xmlbeans instead of ADB.
> > > > So did I but even if the codegen went fine, the exception is now 
> > > > appearing
> > > on the server side when trying to view the wsdl...
> > > >
> > > > An I missing something ?
> > > >
> > > > Thanks in advance,
> > > >
> > > > Axel
> > > >
> > > >
> > > > ---
> > > > Axel Bernard
> > > > Integration Services Group
> > > > Accelior Consulting
> > > >
> > > > Email:   [EMAIL PROTECTED]
> > > > Mobile:  +32-484-108-330
> > > > Website:   http://www.accelior.com
> > > > ---
> > > >
> > > > ** Disclaimer: **
> > > > This e-mail is intended for the exclusive use by the person(s) mentioned
> > > as recipient(s).
> > > > This e-mail and its attachments, if any, contain confidential 
> > > > information
> > > > and/or information protected by intellectual property rights or other
> > > rights.
> > > > This e-mail does not constitute any commitment for Accelior or its
> > > subsidiaries
> > > > except when expressly otherwise agreed in a written agreement between 
> > > > the
> > > > intended recipient and the originating subsidiaries of Accelior, sender 
> > > > of
> > > the mail.
> > > > If you receive this message by mistake, please, notify the sender with 
> > > > the
> > > > "reply" option and delete immediately this e-mail from your system, and
> > > > destroy all copies of it.
> > > > You may not, directly or indirectly, use, disclose, distribute, print or
> > > copy,
> > > > this e-mail or any part of it if you are not the intended recipient.
> > > > You have to take at any time all necessary measures against viruses.
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > Davanum Srinivas : http://wso2.com/blogs/
>
>
> ---
> Axel Bernard
> Integration Services Group
> Accelior Consulting
>
> Email:  [EMAIL PROTECTED]
> Mobile:  +32-484-108-330
> Website:   http://www.accelior.com
> ---
>
> ** Disclaimer: **
> This e-mail is intended for the exclusive use by the person(s) mentioned as 
> recipient(s).
> This e-mail and its attachments, if any, contain confidential information
> and/or information protected by intellectual property rights or other rights.
> This e-mail does not constitute any commitment for Accelior or 

Re: Generation of proxies on demand: is it possible?

[Seth Griffin]

Helcio,     I cannot answer whether or not a cell phone has the power to efficiently generate proxy classes on demand or not. It really depends on what the specs of the cell phone are.      I do, however, know that on demand generation of proxy classes is possible. I have never done it myself, but there is a tool floating around called Web Service Studio that can be used for testing web services. The tool was produced by a Microsoft engineer and was written in C# (so the language syntax should be familiar to you as a Java developer) If you are willing to download it, the code is also given and it may help you to see the process involved.     The binaries and source are available from:      http://www.gotdotnet.com/team/tools/web_svc/default.aspx     Best 
 of luck
 to you,     -SethHelcio Wagner da Silva <[EMAIL PROTECTED]> wrote:Gentlemen, good morning.I used successfully the Apache Axis in order to create a Web Service and aClient for it. Both applications were created and deployed in PCs usingJava. In order to generate the proxy to the Web Service, I used thewsdl2java tool. That was okay. Now, I have a little question to yourelated to utilization of a Web Service by a Client installed in a cellphone. Help me, please.Let's supose I want to use a Web Service installed in a PC located in aremote location from my cell phone. Let's supose I have the WSDL filerelated to that Web Service as well. How can I generate the proxy to theWeb Service from its WSDL file in deployment time? Is it possible toperform t
 hat
 on-demand procedure using Apache Axis or another product?I am investigating how to use Web Services from a cell phone (or a PDA, oranother low computational power device). I know some conceptualrequirements to make that utilization possible. One of them is thepresence of a piece of software capable to send and receive SOAP (orXML-RPC) messages. This piece of software is the proxy to the Web Service,right? If a have a set of proxies installed in the cell phone related topre-defined Web Services, there is no problems. But, if I want to use anew Web Services, I must follow two steps:1. Obtain its related WSDL file;2. convert that WSDL file in a proxy.The step 1 must be accomplished with aid of a UDDI registry (by the way,can I use a UDDI registry using the Apache Axis API?);The step 2 brings me some questions. First: is it possible to perform thaton-demand conversion ? More accurately, Is it possible to per
 form it
 IN ACELL PHONE ? Second: what is the burden imposed by that computationalpower consuming task ?My apologize for the long message, gentlemen. Any help will be welcome.Thanks in advance.H. Wagner
		Do you Yahoo!? 
With a free 1 GB, there's more in store with Yahoo! Mail.

Re: OutOfMemoryError when submitting large SOAP requests to Axis

[Jared Klett]

Of course, the moment I send off a message to a mailing list, after
having claimed I read the archives, I find a message that nearly
answers my question.

http://marc.theaimsgroup.com/?l=axis-user&m=113871304213627&w=2

This message mentions this JIRA issue:

http://issues.apache.org/jira/browse/AXIS-2221

which looks like it will solve my problem, however, I'm not sure how
to go about implementing it. Is there a configuration option to Axis
to use the streaming capability? What changes, if any, should I make
to my application code?

cheers,

- Jared

On 2/2/06, Jared Klett <[EMAIL PROTECTED]> wrote:
> greetings all,
>
> I've taken a contract job to improve the performance of a Java Web
> Service based on Axis. The service is required to handle multiple
> simultaneous SOAP requests that can be anywhere from  two to 100 MB in
> size. So far, the service fails with an OutOfMemoryError when I submit
> any more than one simultaneous request at a time.
>
> I participated in a previous thread entitled "Status w/r/t memory
> leaks..." started by Jesse Sightler. I've tried the Axis 1.3 final
> release, as well as a version built from the trunk of the latest (as
> of yesterday) SVN source tree.
>
> The SOAP requests have a number of attachments in the form of
> base64-encoded data, which look something like this:
>
> 
> spacer.gif
> R0lGODlhAQABAIAAACH5BAEALAABAAEAAAICRAEAOw==
> 
>
> The content inside the  tag can be extremely large - as I
> mentioned, these requests can be upwards of 100 MB in size.
>
> I've tweaked the JVM parameters, setting the max and initial heap
> sizes, the perm gen heap size, as well as trying several different
> options to change the behavior of the garbage collector - all to no
> avail.
>
> I've narrowed down the problem down to the point where I'm sure it's
> happening somewhere inside of Axis - the request is submitted to
> AxisServlet, then passed to SOAPMonitor via an invoke() call.
>
> Here is a snippet of the debug log output before the OOM happens:
>
> [] [2006-01-30 15:45:23,404] SAXOutputter - SAXOutputter.endElement
> ['' reporterCcc]
> [] [2006-01-30 15:45:23,404] ProjectResourceBundle -
> org.apache.axis.i18n.resource::handleGetObject(endElem00)
> [] [2006-01-30 15:45:23,404] SerializationContext - End element reporterCcc
> [] [2006-01-30 15:45:23,404] NSStack - NSPop (32)
> [] [2006-01-30 15:45:23,404] SAXOutputter - SAXOutputter.endElement
> ['http://.yyy.com' fileTestSubmission]
> [] [2006-01-30 15:45:23,404] ProjectResourceBundle -
> org.apache.axis.i18n.resource::handleGetObject(endElem00)
> [] [2006-01-30 15:45:23,404] SerializationContext - End element
> q1:fileTestSubmission
> [] [2006-01-30 15:45:23,404] NSStack - NSPop (32)
> [] [2006-01-30 15:45:23,404] SAXOutputter - SAXOutputter.endElement
> ['http://schemas.xmlsoap.org/soap/envelope/' Body]
> [] [2006-01-30 15:45:23,404] ProjectResourceBundle -
> org.apache.axis.i18n.resource::handleGetObject(endElem00)
> [] [2006-01-30 15:45:23,404] SerializationContext - End element soap:Body
> [] [2006-01-30 15:45:23,404] NSStack - NSPop (32)
> [] [2006-01-30 15:45:23,404] SAXOutputter - SAXOutputter.endElement
> ['http://schemas.xmlsoap.org/soap/envelope/' Envelope]
> [] [2006-01-30 15:45:23,404] ProjectResourceBundle -
> org.apache.axis.i18n.resource::handleGetObject(endElem00)
> [] [2006-01-30 15:45:23,404] SerializationContext - End element soap:Envelope
> [] [2006-01-30 15:45:23,404] ProjectResourceBundle -
> org.apache.axis.i18n.resource::handleGetObject(empty00)
> [] [2006-01-30 15:45:23,405] NSStack - NSPop (empty)
> [] [2006-01-30 15:45:23,405] SAXOutputter - SAXOutputter.endDocument
> [] [2006-01-30 15:45:38,782] ProjectResourceBundle -
> org.apache.axis.i18n.resource::handleGetObject(exception00)
> [] [2006-01-30 15:45:38,782] EXCEPTIONS - Exception:
> java.lang.OutOfMemoryError: Java heap space
>
> I have been looking at the source code to Axis, and I note that in
> SOAPPart, around line 444, data is loaded via an InputStream into a
> memory-resident byte array. So far that's the only place I can find
> that might actually be causing the problem.
>
> It seems logical that a large SOAP request that is separated into
> attachments should be written to disk, and then parsed inside of a
> buffer. Here is a link to an article with such a code example (under
> "Receive and process a SOAP message with SAAJ", a little more than
> halfway down the page):
>
> http://www.javaworld.com/javaworld/jw-09-2003/jw-0912-webservices-p2.html
>
> I've read the archives of this mailing list, so I know I'm not the
> first one to run into this issue. So far, I have not found any
> proposed solutions.
>
> I'm going to continue to investigate, but I would really appreciate
> some help or insights from the list. Thanks very much!
>
> cheers,
>
> - Jared
>

Re: OutOfMemoryError when submitting large SOAP requests to Axis

[Linus Kamb]

What "style" of web service are  you using?

I have successfully sent attachments of > 200MB using doc/lit wrapped, 
and I'm sure I could send larger ones. 
The trouble I run into is when I try to parse the attachments (they are 
XML,) but that is outside of Axis/SOAP.



Jared Klett wrote:


greetings all,

I've taken a contract job to improve the performance of a Java Web
Service based on Axis. The service is required to handle multiple
simultaneous SOAP requests that can be anywhere from  two to 100 MB in
size. So far, the service fails with an OutOfMemoryError when I submit
any more than one simultaneous request at a time.

I participated in a previous thread entitled "Status w/r/t memory
leaks..." started by Jesse Sightler. I've tried the Axis 1.3 final
release, as well as a version built from the trunk of the latest (as
of yesterday) SVN source tree.

The SOAP requests have a number of attachments in the form of
base64-encoded data, which look something like this:


spacer.gif
R0lGODlhAQABAIAAACH5BAEALAABAAEAAAICRAEAOw==


The content inside the  tag can be extremely large - as I
mentioned, these requests can be upwards of 100 MB in size.

I've tweaked the JVM parameters, setting the max and initial heap
sizes, the perm gen heap size, as well as trying several different
options to change the behavior of the garbage collector - all to no
avail.

I've narrowed down the problem down to the point where I'm sure it's
happening somewhere inside of Axis - the request is submitted to
AxisServlet, then passed to SOAPMonitor via an invoke() call.

Here is a snippet of the debug log output before the OOM happens:

[] [2006-01-30 15:45:23,404] SAXOutputter - SAXOutputter.endElement
['' reporterCcc]
[] [2006-01-30 15:45:23,404] ProjectResourceBundle -
org.apache.axis.i18n.resource::handleGetObject(endElem00)
[] [2006-01-30 15:45:23,404] SerializationContext - End element reporterCcc
[] [2006-01-30 15:45:23,404] NSStack - NSPop (32)
[] [2006-01-30 15:45:23,404] SAXOutputter - SAXOutputter.endElement
['http://.yyy.com' fileTestSubmission]
[] [2006-01-30 15:45:23,404] ProjectResourceBundle -
org.apache.axis.i18n.resource::handleGetObject(endElem00)
[] [2006-01-30 15:45:23,404] SerializationContext - End element
q1:fileTestSubmission
[] [2006-01-30 15:45:23,404] NSStack - NSPop (32)
[] [2006-01-30 15:45:23,404] SAXOutputter - SAXOutputter.endElement
['http://schemas.xmlsoap.org/soap/envelope/' Body]
[] [2006-01-30 15:45:23,404] ProjectResourceBundle -
org.apache.axis.i18n.resource::handleGetObject(endElem00)
[] [2006-01-30 15:45:23,404] SerializationContext - End element soap:Body
[] [2006-01-30 15:45:23,404] NSStack - NSPop (32)
[] [2006-01-30 15:45:23,404] SAXOutputter - SAXOutputter.endElement
['http://schemas.xmlsoap.org/soap/envelope/' Envelope]
[] [2006-01-30 15:45:23,404] ProjectResourceBundle -
org.apache.axis.i18n.resource::handleGetObject(endElem00)
[] [2006-01-30 15:45:23,404] SerializationContext - End element soap:Envelope
[] [2006-01-30 15:45:23,404] ProjectResourceBundle -
org.apache.axis.i18n.resource::handleGetObject(empty00)
[] [2006-01-30 15:45:23,405] NSStack - NSPop (empty)
[] [2006-01-30 15:45:23,405] SAXOutputter - SAXOutputter.endDocument
[] [2006-01-30 15:45:38,782] ProjectResourceBundle -
org.apache.axis.i18n.resource::handleGetObject(exception00)
[] [2006-01-30 15:45:38,782] EXCEPTIONS - Exception:
java.lang.OutOfMemoryError: Java heap space

I have been looking at the source code to Axis, and I note that in
SOAPPart, around line 444, data is loaded via an InputStream into a
memory-resident byte array. So far that's the only place I can find
that might actually be causing the problem.

It seems logical that a large SOAP request that is separated into
attachments should be written to disk, and then parsed inside of a
buffer. Here is a link to an article with such a code example (under
"Receive and process a SOAP message with SAAJ", a little more than
halfway down the page):

http://www.javaworld.com/javaworld/jw-09-2003/jw-0912-webservices-p2.html

I've read the archives of this mailing list, so I know I'm not the
first one to run into this issue. So far, I have not found any
proposed solutions.

I'm going to continue to investigate, but I would really appreciate
some help or insights from the list. Thanks very much!

cheers,

- Jared

 

OutOfMemoryError when submitting large SOAP requests to Axis

[Jared Klett]

greetings all,

I've taken a contract job to improve the performance of a Java Web
Service based on Axis. The service is required to handle multiple
simultaneous SOAP requests that can be anywhere from  two to 100 MB in
size. So far, the service fails with an OutOfMemoryError when I submit
any more than one simultaneous request at a time.

I participated in a previous thread entitled "Status w/r/t memory
leaks..." started by Jesse Sightler. I've tried the Axis 1.3 final
release, as well as a version built from the trunk of the latest (as
of yesterday) SVN source tree.

The SOAP requests have a number of attachments in the form of
base64-encoded data, which look something like this:


spacer.gif
R0lGODlhAQABAIAAACH5BAEALAABAAEAAAICRAEAOw==


The content inside the  tag can be extremely large - as I
mentioned, these requests can be upwards of 100 MB in size.

I've tweaked the JVM parameters, setting the max and initial heap
sizes, the perm gen heap size, as well as trying several different
options to change the behavior of the garbage collector - all to no
avail.

I've narrowed down the problem down to the point where I'm sure it's
happening somewhere inside of Axis - the request is submitted to
AxisServlet, then passed to SOAPMonitor via an invoke() call.

Here is a snippet of the debug log output before the OOM happens:

[] [2006-01-30 15:45:23,404] SAXOutputter - SAXOutputter.endElement
['' reporterCcc]
[] [2006-01-30 15:45:23,404] ProjectResourceBundle -
org.apache.axis.i18n.resource::handleGetObject(endElem00)
[] [2006-01-30 15:45:23,404] SerializationContext - End element reporterCcc
[] [2006-01-30 15:45:23,404] NSStack - NSPop (32)
[] [2006-01-30 15:45:23,404] SAXOutputter - SAXOutputter.endElement
['http://.yyy.com' fileTestSubmission]
[] [2006-01-30 15:45:23,404] ProjectResourceBundle -
org.apache.axis.i18n.resource::handleGetObject(endElem00)
[] [2006-01-30 15:45:23,404] SerializationContext - End element
q1:fileTestSubmission
[] [2006-01-30 15:45:23,404] NSStack - NSPop (32)
[] [2006-01-30 15:45:23,404] SAXOutputter - SAXOutputter.endElement
['http://schemas.xmlsoap.org/soap/envelope/' Body]
[] [2006-01-30 15:45:23,404] ProjectResourceBundle -
org.apache.axis.i18n.resource::handleGetObject(endElem00)
[] [2006-01-30 15:45:23,404] SerializationContext - End element soap:Body
[] [2006-01-30 15:45:23,404] NSStack - NSPop (32)
[] [2006-01-30 15:45:23,404] SAXOutputter - SAXOutputter.endElement
['http://schemas.xmlsoap.org/soap/envelope/' Envelope]
[] [2006-01-30 15:45:23,404] ProjectResourceBundle -
org.apache.axis.i18n.resource::handleGetObject(endElem00)
[] [2006-01-30 15:45:23,404] SerializationContext - End element soap:Envelope
[] [2006-01-30 15:45:23,404] ProjectResourceBundle -
org.apache.axis.i18n.resource::handleGetObject(empty00)
[] [2006-01-30 15:45:23,405] NSStack - NSPop (empty)
[] [2006-01-30 15:45:23,405] SAXOutputter - SAXOutputter.endDocument
[] [2006-01-30 15:45:38,782] ProjectResourceBundle -
org.apache.axis.i18n.resource::handleGetObject(exception00)
[] [2006-01-30 15:45:38,782] EXCEPTIONS - Exception:
java.lang.OutOfMemoryError: Java heap space

I have been looking at the source code to Axis, and I note that in
SOAPPart, around line 444, data is loaded via an InputStream into a
memory-resident byte array. So far that's the only place I can find
that might actually be causing the problem.

It seems logical that a large SOAP request that is separated into
attachments should be written to disk, and then parsed inside of a
buffer. Here is a link to an article with such a code example (under
"Receive and process a SOAP message with SAAJ", a little more than
halfway down the page):

http://www.javaworld.com/javaworld/jw-09-2003/jw-0912-webservices-p2.html

I've read the archives of this mailing list, so I know I'm not the
first one to run into this issue. So far, I have not found any
proposed solutions.

I'm going to continue to investigate, but I would really appreciate
some help or insights from the list. Thanks very much!

cheers,

- Jared

Re: Document Literal vs Document Wrapped vs RPC Encoding

[Cyrille Le Clerc]

WS-I Basic Profile, the reference for SOAP interoperability, says it
prefers "literal" rather than "encoded" :
  Extract : "As a result, the Profile prefers the use of literal,
non-encoded XML."
  Chapter : "4.1.7 SOAP encodingStyle Attribute"
  URL : 
http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16448072

Unfortunately, I did not find in this spec any clear statement saying
that "document" (in a wrapped style) is preferred to "rpc".
However, you will find many articles that say "document" is preferred to "rpc".

Cyrille

--
Cyrille Le Clerc
[EMAIL PROTECTED]
[EMAIL PROTECTED]

http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html

On 2/2/06, Jyotishman Pathak <[EMAIL PROTECTED]> wrote:
> Dov,
>
>  I found this article [1] from IBM to be quite useful. At the same time, I am 
> interested in knowing more about your investigation.
>
>  Thanks,
>  - Jyoti
>
>  [1] 
> http://www.ibm.com/developerworks/webservices/library/ws-whichwsdl/?ca=dgr-devx-WebServicesMVP03
>
>
>
>
>
> On 2/2/06, Balaji D L <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > Can you share your analyse with us ??
> > It will be very useful.
> > Regards
> > Balaji
> >
> > - Original Message 
> > From: Dov Rosenberg <[EMAIL PROTECTED]>
> > To:  axis-user@ws.apache.org
> > Sent: 02 February 2006 14:21:37
> > Subject: Document Literal vs Document Wrapped vs RPC Encoding
> >
> > I have done a bunch of investigating to determine the 
> > differences/benefits/limitations of the 3 styles of WSDL generation. In 
> > general it seems that the preferred version is Document Literal. Are there 
> > any other opinions as to the most popular version?
> >
> > Thanks in advance
> >
> >
> > --
> > Dov Rosenberg
> > Inquira Inc
> > 370 Centerpointe Circle, ste 1178
> > Altamonte Springs, FL 32701
> > (407) 339-1177 x 102
> > (407) 339-6704 (fax)
> >  [EMAIL PROTECTED]
> > AOL IM: dovrosenberg
> >
> >
>
>
>
> --
> Jyotishman Pathak
> WWW: http://www.cs.iastate.edu/~jpathak

Re: already contains type 'string;

[Axel Bernard]

On 2 of February of 2006, Davanum Srinivas wrote:

Dims,

I build Axis2 from the latest SVN trunk but I still experience the same error.
Do you need more details to figure-out what's happening ?

Thanks,

Axel


> It has been fixed in latest SVN 
> (http://issues.apache.org/jira/browse/AXIS2-382)
> 
> thanks,
> dims
> 
> On 2/1/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
> > It's a bug -- known problem, but I don't think it's been fixed yet.
> >
> >
> > On 2/1/06, Axel Bernard <[EMAIL PROTECTED] > wrote:
> > >
> > > Gentlemen,
> > >
> > > I have a RuntimeException while trying to view the WSDL of a deployed
> > service on axis2 - version 0.94
> > >  [java]
> > org.apache.axis2.wsdl.codegen.CodeGenerationException:
> > java.lang.RuntimeException: java.lang.RuntimeException: Schema for namespace
> > 'http://wpm.accelior.com/v2/core/common/i18N/bo' already
> > contains type 'string
> > >  [java]
> > org.apache.axis2.wsdl.codegen.CodeGenerationException:
> > java.lang.RuntimeException: java.lang.RuntimeException: Schema for namespace
> > 'http://wpm.accelior.com/v2/core/common/i18N/bo' already
> > contains type 'string
> > >  [java] at
> > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate
> > (CodeGenerationEngine.java:118)
> > >  [java] at
> > org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:31)
> > >  [java] at
> > org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
> > >  [java] Caused by: java.lang.RuntimeException:
> > java.lang.RuntimeException: Schema for namespace
> > 'http://wpm.accelior.com/v2/core/common/i18N/bo' already
> > contains type 'string
> > >  [java] at
> > org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage
> > (SimpleDBExtension.java:152)
> > >  [java] at
> > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:80)
> > >  [java] ... 2 more
> > >  [java] Caused by: java.lang.RuntimeException : Schema for namespace
> > 'http://wpm.accelior.com/v2/core/common/i18N/bo' already
> > contains type 'string
> > > (...)
> > >
> > > When I executed WSDL2Java (using ADB) to generate my sources I had the
> > same exception. Following forum posts on that topic, I've seen that it was a
> > known problem that could be solved by using xmlbeans instead of ADB.
> > > So did I but even if the codegen went fine, the exception is now appearing
> > on the server side when trying to view the wsdl...
> > >
> > > An I missing something ?
> > >
> > > Thanks in advance,
> > >
> > > Axel
> > >
> > >
> > > ---
> > > Axel Bernard
> > > Integration Services Group
> > > Accelior Consulting
> > >
> > > Email:   [EMAIL PROTECTED]
> > > Mobile:  +32-484-108-330
> > > Website:   http://www.accelior.com
> > > ---
> > >
> > > ** Disclaimer: **
> > > This e-mail is intended for the exclusive use by the person(s) mentioned
> > as recipient(s).
> > > This e-mail and its attachments, if any, contain confidential information
> > > and/or information protected by intellectual property rights or other
> > rights.
> > > This e-mail does not constitute any commitment for Accelior or its
> > subsidiaries
> > > except when expressly otherwise agreed in a written agreement between the
> > > intended recipient and the originating subsidiaries of Accelior, sender of
> > the mail.
> > > If you receive this message by mistake, please, notify the sender with the
> > > "reply" option and delete immediately this e-mail from your system, and
> > > destroy all copies of it.
> > > You may not, directly or indirectly, use, disclose, distribute, print or
> > copy,
> > > this e-mail or any part of it if you are not the intended recipient.
> > > You have to take at any time all necessary measures against viruses.
> > >
> > >
> >
> >
> 
> 
> --
> Davanum Srinivas : http://wso2.com/blogs/


---
Axel Bernard
Integration Services Group
Accelior Consulting

Email:  [EMAIL PROTECTED] 
Mobile:  +32-484-108-330
Website:   http://www.accelior.com 
---

** Disclaimer: **
This e-mail is intended for the exclusive use by the person(s) mentioned as 
recipient(s).
This e-mail and its attachments, if any, contain confidential information
and/or information protected by intellectual property rights or other rights.
This e-mail does not constitute any commitment for Accelior or its subsidiaries
except when expressly otherwise agreed in a written agreement between the
intended recipient and the originating subsidiaries of Accelior, sender of the 
mail.
If you receive this message by mistake, please, notify the sender with the
"reply" option and delete immediately this e-mail from your system, and
destroy all copies of it.
You may not, directly or indirectly, use, disclose, distribute

Re: wss4j and axis2

[Ruchith Fernando]

If you are using the axis2.xml file to configure security module
parameters in the server side, please note that those configurations
will be applicable to ALL the services in that axis2 repository.
Therefore if you want to configure security on a per service basis you
MUST use the services.xml file to configure the parameters.

Thanks,
Ruchith

On 2/2/06, Ruchith Fernando <[EMAIL PROTECTED]> wrote:
> Hi Brian,
>
> If you get "the request does not contain the required Security
> headers" then it seems like the security module is not deployed at the
> client side OR the configured axis2.xml file is not picked up by the
> client. You MUST provide this configured axis2.xml file along with a
> repository containing the security.mar in the 'modules' directory. [1]
>
> - Are you providing the repository location to the ServiceClient?
>
>- If NOT, please provide an axis2 repository with the 'modules'
> directory as as sub directory and make sure you have security
> configured [2] axis2.xml file in the repo directory (if you are using
> the SVN HEAD axis2.xml file should be in the 'conf' directory in the
> repo direcotry).
>
>   - If YES, the please check whether you have the security.mar file in
> the 'modules' directory of the repo.
>
> Thanks,
> Ruchith
>
> Notes:
> [1] Creating a ServiceClient with a custom repository:
>
> ConfigurationContext ctx =
> ConfigurationContextFactory.createConfigurationContextFromFileSystem("/path/to/axis2/repo",
> "path/to/configured/axis2.xml");
> ServiceClient serviceClient = new ServiceClient(ctx, null);
>
>
> [2] Security configured mean that you must have the  ref="security" /> entry in axis2.xml along with the required
> inflow/outflow parameters. But if you don't have the  ref="security" /> entry in the axis2.xml you can engage the security
> module using the ServiceClient object as shown beow:
>
> serviceClient.engageModule(new QName("security"));
>
> [3] Make sure you include the commons-codec.jar in the client's and
> server's classpath (in WEB-INF/lib directory in the case of Tomcat)
>
> On 2/2/06, Brian Shields <[EMAIL PROTECTED]> wrote:
> > Thanks for the reply Ruchith,
> > What do you mean by the axis2.xml file of the client? Is this the same
> > axis2.xml file as that of the server if one is calling a service from
> > localhost? I am using 2 deployments of axis2 on two different machines,
> > one of which i have the two parameters below included in the axis2. This
> > is my server. My client machine on the other hand has the same
> > configurations all down to the axis2.xml file where i have only the
> > OutflowSecurity parameter included.
> > When calling the service i get an error saying that the request does not
> > contain the required Security headers!! I have used tcpmon and the
> > message is being sent successfully, without the security header! Is it
> > possible that the client is ignoring the axis2.xml configurations when
> > calling the service? I presume the axis2.xml replaces the
> > client_deploy.wsdd file!
> > Thanks,
> > Brian.
> >
> > Ruchith Fernando wrote:
> >
> > >Hi Brian,
> > >
> > >Please see my comments below:
> > >
> > >On 2/2/06, Brian Shields <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > >>Hello,
> > >>I am deploying security handlers in axis2. My question may be very
> > >>simple, apologies if the answer is staring me in the face!!
> > >>Where is the best place to include security tokens in the client? I have
> > >>altered the axis2.xml file to include a parameters in the inflow and
> > >>outflow..
> > >>
> > >>
> > >>Timestamp
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>Timestamp
> > >>
> > >>
> > >> From what i can make out, the outflowsecurity parmeter refers to any
> > >>security tokens which will be added in the outflow of a service request
> > >>and the inflowsecurity parameters are parameters which are expected for
> > >>the service to be invoked?!?
> > >>
> > >>
> > >
> > >Correct !!!
> > >
> > >The above configuration will ensure that a Timestamp is added to the
> > >outgoing message and it will require all incoming messages to contain
> > >a Timestamp header.
> > >
> > >
> > >
> > >>Where then are they applied to the client? Using the Options parameters?
> > >>
> > >>
> > >
> > >With the Axis2-0.94 release we support setting the client parameters
> > >in the axis2.xml of the client. And from the next release you will be
> > >able to set the configuration via Options parameters (Using
> > >org.apache.axis2.security.handler.config.InflowConfiguration and
> > >org.apache.axis2.security.handler.config.OutflowConfiguration). This
> > >feature is already available in the SVN HEAD.
> > >
> > >Thanks,
> > >Ruchith
> > >
> > >
> > >
> > >>Thanks,
> > >>Brian.
> > >>
> > >>--
> > >>Brian Shields BSc. MSc.,
> > >>PhD Candidate,
> > >>Department of Information Technology,
> > >>National University of Ireland,
> > >>Galway,
> > >>Ireland.
> > >>
> > >>
> > >>
>

Re: wss4j and axis2

[Ruchith Fernando]

Hi Brian,

If you get "the request does not contain the required Security
headers" then it seems like the security module is not deployed at the
client side OR the configured axis2.xml file is not picked up by the
client. You MUST provide this configured axis2.xml file along with a
repository containing the security.mar in the 'modules' directory. [1]

- Are you providing the repository location to the ServiceClient?

   - If NOT, please provide an axis2 repository with the 'modules'
directory as as sub directory and make sure you have security
configured [2] axis2.xml file in the repo directory (if you are using
the SVN HEAD axis2.xml file should be in the 'conf' directory in the
repo direcotry).

  - If YES, the please check whether you have the security.mar file in
the 'modules' directory of the repo.

Thanks,
Ruchith

Notes:
[1] Creating a ServiceClient with a custom repository:

ConfigurationContext ctx =
ConfigurationContextFactory.createConfigurationContextFromFileSystem("/path/to/axis2/repo",
"path/to/configured/axis2.xml");
ServiceClient serviceClient = new ServiceClient(ctx, null);


[2] Security configured mean that you must have the  entry in axis2.xml along with the required
inflow/outflow parameters. But if you don't have the  entry in the axis2.xml you can engage the security
module using the ServiceClient object as shown beow:

serviceClient.engageModule(new QName("security"));

[3] Make sure you include the commons-codec.jar in the client's and
server's classpath (in WEB-INF/lib directory in the case of Tomcat)

On 2/2/06, Brian Shields <[EMAIL PROTECTED]> wrote:
> Thanks for the reply Ruchith,
> What do you mean by the axis2.xml file of the client? Is this the same
> axis2.xml file as that of the server if one is calling a service from
> localhost? I am using 2 deployments of axis2 on two different machines,
> one of which i have the two parameters below included in the axis2. This
> is my server. My client machine on the other hand has the same
> configurations all down to the axis2.xml file where i have only the
> OutflowSecurity parameter included.
> When calling the service i get an error saying that the request does not
> contain the required Security headers!! I have used tcpmon and the
> message is being sent successfully, without the security header! Is it
> possible that the client is ignoring the axis2.xml configurations when
> calling the service? I presume the axis2.xml replaces the
> client_deploy.wsdd file!
> Thanks,
> Brian.
>
> Ruchith Fernando wrote:
>
> >Hi Brian,
> >
> >Please see my comments below:
> >
> >On 2/2/06, Brian Shields <[EMAIL PROTECTED]> wrote:
> >
> >
> >>Hello,
> >>I am deploying security handlers in axis2. My question may be very
> >>simple, apologies if the answer is staring me in the face!!
> >>Where is the best place to include security tokens in the client? I have
> >>altered the axis2.xml file to include a parameters in the inflow and
> >>outflow..
> >>
> >>
> >>Timestamp
> >>
> >>
> >>
> >>
> >>
> >>Timestamp
> >>
> >>
> >> From what i can make out, the outflowsecurity parmeter refers to any
> >>security tokens which will be added in the outflow of a service request
> >>and the inflowsecurity parameters are parameters which are expected for
> >>the service to be invoked?!?
> >>
> >>
> >
> >Correct !!!
> >
> >The above configuration will ensure that a Timestamp is added to the
> >outgoing message and it will require all incoming messages to contain
> >a Timestamp header.
> >
> >
> >
> >>Where then are they applied to the client? Using the Options parameters?
> >>
> >>
> >
> >With the Axis2-0.94 release we support setting the client parameters
> >in the axis2.xml of the client. And from the next release you will be
> >able to set the configuration via Options parameters (Using
> >org.apache.axis2.security.handler.config.InflowConfiguration and
> >org.apache.axis2.security.handler.config.OutflowConfiguration). This
> >feature is already available in the SVN HEAD.
> >
> >Thanks,
> >Ruchith
> >
> >
> >
> >>Thanks,
> >>Brian.
> >>
> >>--
> >>Brian Shields BSc. MSc.,
> >>PhD Candidate,
> >>Department of Information Technology,
> >>National University of Ireland,
> >>Galway,
> >>Ireland.
> >>
> >>
> >>
> >
> >
> >
> >
>
> --
> Brian Shields BSc. MSc.,
> PhD Candidate,
> Department of Information Technology,
> National University of Ireland,
> Galway,
> Ireland.
>

Re: Document Literal vs Document Wrapped vs RPC Encoding

[Jyotishman Pathak]

Dov,

I found this article [1] from IBM to be quite useful. At the same time,
I am interested in knowing more about your investigation.

Thanks,
- Jyoti

[1] http://www.ibm.com/developerworks/webservices/library/ws-whichwsdl/?ca=dgr-devx-WebServicesMVP03

On 2/2/06, Balaji D L <[EMAIL PROTECTED]> wrote:

Can you share your analyse with us ??
It will be very useful.
Regards
Balaji- Original Message From: Dov Rosenberg <[EMAIL PROTECTED]>To: 
axis-user@ws.apache.orgSent: 02 February 2006 14:21:37Subject: Document Literal vs Document Wrapped vs RPC Encoding
I have done a bunch of investigating to determine the differences/benefits/limitations
of the 3 styles of WSDL generation. In general it seems that the
preferred version is Document Literal. Are there any other opinions as
to the most popular version?Thanks in advance-- Dov RosenbergInquira Inc370 Centerpointe Circle, ste 1178Altamonte Springs, FL 32701(407) 339-1177 x 102(407) 339-6704 (fax)
[EMAIL PROTECTED]AOL IM: dovrosenberg
-- Jyotishman PathakWWW: http://www.cs.iastate.edu/~jpathak

Re: Document Literal vs Document Wrapped vs RPC Encoding

[Balaji D L]

Can you share your analyse with us ??
It will be very useful.
Regards
Balaji- Original Message From: Dov Rosenberg <[EMAIL PROTECTED]>To: axis-user@ws.apache.orgSent: 02 February 2006 14:21:37Subject: Document Literal vs Document Wrapped vs RPC EncodingI have done a bunch of investigating to determine the differences/benefits/limitations of the 3 styles of WSDL generation. In general it seems that the preferred version is Document Literal. Are there any other opinions as to the most popular version?Thanks in advance-- Dov RosenbergInquira Inc370 Centerpointe Circle, ste 1178Altamonte Springs, FL 32701(407) 339-1177 x 102(407) 339-6704 (fax)[EMAIL PROTECTED]AOL IM: dovrosenberg

wrapped/literal array results -> cast exception in client

[Fernando.Matomira]

With a client using Axis 1.3, when one calls a method that
is declared to return String[]

(confirmed by wsdl2java), the call fails with a
ClassCastException because what the deserializer is actually returning to the
proxy is an ArrayList.

 

 

Re: wss4j and axis2

[Brian Shields]

Thanks for the reply Ruchith,
What do you mean by the axis2.xml file of the client? Is this the same 
axis2.xml file as that of the server if one is calling a service from 
localhost? I am using 2 deployments of axis2 on two different machines, 
one of which i have the two parameters below included in the axis2. This 
is my server. My client machine on the other hand has the same 
configurations all down to the axis2.xml file where i have only the 
OutflowSecurity parameter included.
When calling the service i get an error saying that the request does not 
contain the required Security headers!! I have used tcpmon and the 
message is being sent successfully, without the security header! Is it 
possible that the client is ignoring the axis2.xml configurations when 
calling the service? I presume the axis2.xml replaces the 
client_deploy.wsdd file!

Thanks,
Brian.

Ruchith Fernando wrote:


Hi Brian,

Please see my comments below:

On 2/2/06, Brian Shields <[EMAIL PROTECTED]> wrote:
 


Hello,
I am deploying security handlers in axis2. My question may be very
simple, apologies if the answer is staring me in the face!!
Where is the best place to include security tokens in the client? I have
altered the axis2.xml file to include a parameters in the inflow and
outflow..

   
   Timestamp
   
   

   
   
   Timestamp
   
   
From what i can make out, the outflowsecurity parmeter refers to any
security tokens which will be added in the outflow of a service request
and the inflowsecurity parameters are parameters which are expected for
the service to be invoked?!?
   



Correct !!!

The above configuration will ensure that a Timestamp is added to the
outgoing message and it will require all incoming messages to contain
a Timestamp header.

 


Where then are they applied to the client? Using the Options parameters?
   



With the Axis2-0.94 release we support setting the client parameters
in the axis2.xml of the client. And from the next release you will be
able to set the configuration via Options parameters (Using
org.apache.axis2.security.handler.config.InflowConfiguration and
org.apache.axis2.security.handler.config.OutflowConfiguration). This
feature is already available in the SVN HEAD.

Thanks,
Ruchith

 


Thanks,
Brian.

--
Brian Shields BSc. MSc.,
PhD Candidate,
Department of Information Technology,
National University of Ireland,
Galway,
Ireland.

   




 



--
Brian Shields BSc. MSc.,
PhD Candidate,
Department of Information Technology,
National University of Ireland,
Galway,
Ireland.

ServiceFactory in Axis2?

[Fernando.Matomira]

What is the equivalent of
org.apache.axis.client.ServiceFactory in Axis2 so that it can be plugged into a
Spring-based client?

 

Thanks

Re: wss4j and axis2

[Ruchith Fernando]

Hi Brian,

Please see my comments below:

On 2/2/06, Brian Shields <[EMAIL PROTECTED]> wrote:
> Hello,
> I am deploying security handlers in axis2. My question may be very
> simple, apologies if the answer is staring me in the face!!
> Where is the best place to include security tokens in the client? I have
> altered the axis2.xml file to include a parameters in the inflow and
> outflow..
> 
> 
> Timestamp
> 
> 
>
> 
> 
> Timestamp
> 
> 
>  From what i can make out, the outflowsecurity parmeter refers to any
> security tokens which will be added in the outflow of a service request
> and the inflowsecurity parameters are parameters which are expected for
> the service to be invoked?!?

Correct !!!

The above configuration will ensure that a Timestamp is added to the
outgoing message and it will require all incoming messages to contain
a Timestamp header.

> Where then are they applied to the client? Using the Options parameters?

With the Axis2-0.94 release we support setting the client parameters
in the axis2.xml of the client. And from the next release you will be
able to set the configuration via Options parameters (Using
org.apache.axis2.security.handler.config.InflowConfiguration and
org.apache.axis2.security.handler.config.OutflowConfiguration). This
feature is already available in the SVN HEAD.

Thanks,
Ruchith

> Thanks,
> Brian.
>
> --
> Brian Shields BSc. MSc.,
> PhD Candidate,
> Department of Information Technology,
> National University of Ireland,
> Galway,
> Ireland.
>

RE: java client to invoke webservices?

[mm jj]

yes i did add the SOAPAction but noting change. any other suggestion or solutions.     i really appreciate.Dinesh Shahane <[EMAIL PROTECTED]> wrote:  Looking at your WSDL, I think you need the following SOAPAction call.setSOAPActionURI("/Processes/SOAPServer ");From: mm jj [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 01, 2006 1:33 PMTo: axis-user@ws.apache.orgSubject: Re: could someone help me in java client to invoke webservices?i did add the following line but nothing change. if you see the error, what is this "faultString: No handler for body element" and some oth
 er
 errors.Dong Liu <[EMAIL PROTECTED]>wrote:Please try after adding this line into your clientcall.setSOAPActionURI("Operation");Cheers,DonOn 2/1/06, mm jj < [EMAIL PROTECTED]> wrote: thanks for reply. could you please look into the following code, error and WSDL.  here is the code, error, and wsdl(this wsdl is created in TIBCO). I used AXIS 1.3 to write and c ompile java code. import org.apache.axis.client.*;import javax.xml.rpc.ParameterMode ;import org.apache.axis.encoding.XMLType;import org.apache.axis.utils.Options; public class FibClient {  public static void main(String[] args) throws Exception {    String endpoint = " http://DUSU41009X1:80/Processes/SOAPServer";    //String endpoint = " http://DUSU41009X1:8080/Processes_sp_Definition";    String Sub = "SUBJECT";    String Data =
 "";    Service service = n ew Service();    Call call = (Call) service.createCall();    call.setTargetEndpointAddress(endpoint);    call.setOperationName("Operation");    call.setProperty(Call.OPERATION_STYLE_PROPERTY, "wrapped");     call.addParameter("op1", XMLType.XSD_STRING, ParameterMode.IN);    call.addParameter("op2", XMLType.XSD_STRING, ParameterMode.IN);    call.setReturnType(XMLType.XSD_STRING);    call.setReturnType (XMLType.XSD_STRING);    String ret = (String) call.invoke(new Object[]{Sub, Data});    System.out.println("Got result : " + ret);              }}-- init:deps-jar:compile-single:run-single:- Unable to find required cla
 sses
 (javax.activation.DataHandler an d javax.mail.internet.MimeMultipart). Attachment support is disabled.AxisFault faultCode: { http://schemas.xmlsoap.org/soap/envelope/}Client faultSubcode:  faultString: No handler for body element faultActor:  faultNode:  faultDetail:     {}detail: http://DUSU41009X1:80/Processes/SOAPServer""OperationNo handler for body element    at org.apache.axis.message.SOAPFaultBuilder.createFault (SOAPFaultBuilder.java:222)    at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)    at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)    at
 org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1712)    at org.apache.crimson.parser.Parser2.content (Parser2.java:1963)    at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691)    at org.apache.crimson.parser.Parser2.content(Parser2.java:1963)    at org.apache.crimson.parser.Parser2.maybeElement (Parser2.java:1691)    at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667)    at org.apache.crimson.parser.Parser2.parse(Parser2.java:337)    at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)    at
 javax.xml.parsers.SAXParser.parse(SAXParser.java:345)    at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java :227)    at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)    at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)    at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke (MustUnderstandChecker.java:62)    at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)    at org.apache.axis.client.Call.invokeEngine(Call.java:2784)    at org.apache.axis.client.Call.invoke(Call.java:2767)    at
 org.apache.axis.client.Call.invoke(Call.java:2443)    at org.apache.axis.client.Call.invoke(Call.java:2366)    at org.apache.axis.client.Call.invoke (Call.java:1812)    at FibClient.main(FibClient.java:24)Exception in thread "main" Java Result: 1BUILD SUCCESSFUL (total time: 1 second) --     
             Generic web service request           
                 insert the reply XML
 here                           
     Generic web service request                             insert the request XML here     

using different versiosn of Axis

[Frank]

I believe I know the answer to this through experimentation but others 
have told me that it should not be a problem but i think it is.  I'm 
using someone's code that compiled it with Axis 1.2.  I'm using their 
code along with some of mine but I'm compiling and running in axis 
1.2.1. When calls are made to their code I get errors.  If I use 1.2 
axis it works fine.


Over all question on Axis.  If you use some one else code that uses Axis 
and they compiled it with come version of it axis like 1.2.  Are you 
required to also use that same version if you use their code even if you 
use a newer version?  I have not been able to get it to work.



Thanks,

Frank

RE: Document Literal vs Document Wrapped vs RPC Encoding

[glenn bech]

The far best article I've read so far on the topic of deciding "what style"
to use is this one 

http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/

It goes through all different combinations of style and encoding, with
complete XML listings for the SOAP Messages etc. I advice you to read
through I carefully, it helped me lot.

Have fun.



From: Dov Rosenberg [mailto:[EMAIL PROTECTED] 
Sent: 2. februar 2006 14:22
To: axis-user@ws.apache.org
Subject: Document Literal vs Document Wrapped vs RPC Encoding

I have done a bunch of investigating to determine the
differences/benefits/limitations of the 3 styles of WSDL generation. In
general it seems that the preferred version is Document Literal. Are there
any other opinions as to the most popular version?

Thanks in advance


-- 
Dov Rosenberg
Inquira Inc
370 Centerpointe Circle, ste 1178
Altamonte Springs, FL 32701
(407) 339-1177 x 102
(407) 339-6704 (fax)
[EMAIL PROTECTED]
AOL IM: dovrosenberg
BEGIN:VCARD
VERSION:2.1
N:Bech;Glenn;Richard
FN:[EMAIL PROTECTED]
ORG:Webstep Consulting AS
TITLE:Seniorkonsulent
TEL;WORK;VOICE:99356459
TEL;CELL;VOICE:99356459
ADR;WORK:;;P.O. Box 66;;Lysaker;1324;Norway
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:P.O. Box 66=0D=0ALysaker 1324=0D=0ANorway
EMAIL;PREF;INTERNET:[EMAIL PROTECTED]
REV:20050923T071750Z
END:VCARD

Document Literal vs Document Wrapped vs RPC Encoding

[Dov Rosenberg]

Title: Document Literal vs Document Wrapped vs RPC Encoding



I have done a bunch of investigating to determine the differences/benefits/limitations of the 3 styles of WSDL generation. In general it seems that the preferred version is Document Literal. Are there any other opinions as to the most popular version?

Thanks in advance


-- 
Dov Rosenberg
Inquira Inc
370 Centerpointe Circle, ste 1178
Altamonte Springs, FL 32701
(407) 339-1177 x 102
(407) 339-6704 (fax)
[EMAIL PROTECTED]
AOL IM: dovrosenberg

Re: Wat Java2WSDL equivalent in Axis2?

[Ajith Ranabahu]

hi,
there were some code in 0.94 that did this WSDL generation but it was
not really tested and was not made into a tool. But recently we've
added the commandline tool support for this tool. You are welcome to
test out Java2WSDL in the latest codebase.
BTW we only generate doc/lit WSDL's :)On 2/2/06, anshuk pal chaudhuri <[EMAIL PROTECTED]> wrote:
Hi,In Axis2 to generate a wsdl from the interfaces anddifferent command line parameters (likewise in
previous axis versions using Java2WSDL) what is thetool that is being used?Anshuk__Do You Yahoo!?Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com-- Ajith Ranabahu

Wat Java2WSDL equivalent in Axis2?

[anshuk pal chaudhuri]

Hi,

In Axis2 to generate a wsdl from the interfaces and
different command line parameters (likewise in
previous axis versions using Java2WSDL) what is the
tool that is being used?

Anshuk

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

wss4j and axis2

[Brian Shields]

Hello,
I am deploying security handlers in axis2. My question may be very 
simple, apologies if the answer is staring me in the face!!
Where is the best place to include security tokens in the client? I have 
altered the axis2.xml file to include a parameters in the inflow and 
outflow..


   
   Timestamp   
   

   
  
   

   
   Timestamp   
   

   
From what i can make out, the outflowsecurity parmeter refers to any 
security tokens which will be added in the outflow of a service request 
and the inflowsecurity parameters are parameters which are expected for 
the service to be invoked?!?

Where then are they applied to the client? Using the Options parameters?
Thanks,
Brian.

--
Brian Shields BSc. MSc.,
PhD Candidate,
Department of Information Technology,
National University of Ireland,
Galway,
Ireland.

Re: trouble redeploying handlers

[Brian Shields]

thanks guys, figured it outsilly mistake on my behalf. I had an old 
classname referenced from the modules.xml file within the .mar file. 
Still unusual behaviour though, surely i should have gotten a 
ClassNotFoundException as the class being referred to was no longer on 
the system!!

Brian.

Deepal Jayasinghe wrote:

hmmm , that can  not be unless you have some files in commons lib , or 
the lib that CCL pick up , I have test that and I don't have any 
problem , any way pls try it again ,

1. do the changes
2. re-create mar file
3. re-deploy that
4. re-start the server

if you still have the problem pls create JIRA

Thanks,
Deepal

~Future is Open~

- Original Message - From: "Brian Shields" 
<[EMAIL PROTECTED]>

To: 
Sent: Tuesday, January 31, 2006 11:08 PM
Subject: trouble redeploying handlers



Hello,
I am having some trouble redeploying a handler .mar file in axis2. 
The engine seems to have an old reference to the classes inside my 
module and any changes i make are not being reflected when i 
repackage the module and redeploy it. I am restarting the web server 
and it is still referencing the older version of the classes!! Any 
ideas?


--
Brian Shields BSc. MSc.,
PhD Candidate,
Department of Information Technology,
National University of Ireland,
Galway,
Ireland.







--
Brian Shields BSc. MSc.,
PhD Candidate,
Department of Information Technology,
National University of Ireland,
Galway,
Ireland.

Re: newbie to Axis2

[anshuk pal chaudhuri]

ok.
But actualli I am trying any of the soap engines
present generate WSDL2.0 compliant.If any can you
please let me know.

Thanks,
Anshuk
--- Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:

> well WSDL 2.0 support is not fully completed , Axis2
> can read WSDL 2.0 but 
> the writing part is not complete , since we are
> using WSDL 1.1 writer you 
> only get WSDL 1.1 doc when you ask for wsdl from
> axis2 :)
> 
> Thanks,
>  Deepal
>

> ~Future is Open~
> 
> - Original Message - 
> From: "anshuk pal chaudhuri" <[EMAIL PROTECTED]>
> To: 
> Sent: Wednesday, February 01, 2006 8:30 PM
> Subject: Re: newbie to Axis2
> 
> 
> > Ajith,
> >
> > Sorry for the trouble.It must have been some other
> > release which I was using.I downloaded the 0.94
> > version and its working ok.I have tried the
> > MyService.aar services and its working fine.The
> wsdl
> > is also generated properly.But the wsdl that is
> > generated is compliant to 1.1.
> > Axis 2 supports WSDL 2.0.rite??How will one
> service
> > (say the sample web services)generate a WSDL 2.0
> > compliant wsdl?
> > Can you please let me know.
> >
> > Anshuk
> >
> > --- Ajith Ranabahu <[EMAIL PROTECTED]>
> wrote:
> >
> >> Hmm..
> >> We've checked and verified that all these
> features
> >> are available. Is this
> >> surely the 0.94 release ?
> >>
> >> On 2/1/06, anshuk pal chaudhuri
> <[EMAIL PROTECTED]>
> >> wrote:
> >> >
> >> > yah Ajith,
> >> >
> >> > I have got one temporary solution to it.The
> >> problem
> >> > what i thot was that the servlet getting
> created
> >> for
> >> > the HappyAxis.jsp was happaxis_jsp.java.Check
> the
> >> name
> >> > caps in both the cases.I changed the
> HappyAxis.jsp
> >> in
> >> > the axis2 to happaxis.jsp.Also changed the
> >> > corresponding urlin the index.jsp page for the
> >> > Validate Link.
> >> >
> >> > Now the axis is properly as its getting all the
> >> the
> >> > componenents.
> >> > Now The problem that I am still facing is that
> the
> >> > service which I have deployed (the one with
> echo
> >> and
> >> > ping operations, the userguide examples one),I
> am
> >> not
> >> > able to see the wsdl of the service.
> >> > Someone said that the web page where the list
> of
> >> > services is being displayed, the service name
> >> > (MYService in this case) is a hyperlink which
> will
> >> > lead to the wsdl page.But my Sevice Name is not
> >> any
> >> > link.So how do I view the wsdl of my service
> >> deployed
> >> > in axis2 ???
> >> >
> >> > Anshuk
> >> >
> >> >
> >> >
> >> > --- Ajith Ranabahu <[EMAIL PROTECTED]>
> >> wrote:
> >> >
> >> > > Hmmm... Is this in the 0.94 release ?  I'm
> >> thinking
> >> > > that it's something to
> >> > > do with the servlet container setup but need
> >> more
> >> > > info to confirm.
> >> > > You can try deleting the work directory if
> you
> >> are
> >> > > using tomcat.
> >> > > BTW can you post the details about your
> servlet
> >> > > container setup, OS and the
> >> > > rest of the environment ?
> >> > >
> >> > > On 2/1/06, anshuk pal chaudhuri
> >> <[EMAIL PROTECTED]>
> >> > > wrote:
> >> > > >
> >> > > > Hi,
> >> > > >
> >> > > > I have installed axis2 web application but
> >> when I
> >> > > am
> >> > > > trying to view the Axis Happiness Page
> using
> >> the
> >> > > > Validate Link in order to know that whether
> >> all
> >> > > the
> >> > > > componenets are properly installed or
> not,its
> >> > > throwing
> >> > > > an error.
> >> > > >
> >> > > > java.lang.NoClassDefFoundError:
> >> > > > org/apache/jsp/HappyAxis_jsp (wrong name:
> >> > > > org/apache/jsp/happyaxis_jsp)
> >> > > >
> >> java.lang.ClassLoader.defineClass0(Native
> >> > > Method)
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>
java.lang.ClassLoader.defineClass(ClassLoader.java:537)
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>
java.net.URLClassLoader.defineClass(URLClassLoader.java:251)
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>
java.net.URLClassLoader.access$100(URLClassLoader.java:55)
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>
java.net.URLClassLoader$1.run(URLClassLoader.java:194)
> >> > > >
> >> > >
> >>
> java.security.AccessController.doPrivileged(Native
> >> > > > Method)
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>
java.net.URLClassLoader.findClass(URLClassLoader.java:187)
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>
org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:156)
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>
org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:69)
> >> > > >
> >> > > >
> >> > >
> 
=== message truncated ===


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Generation of proxies on demand: is it possible?

[Helcio Wagner da Silva]

Gentlemen, good morning.

I used successfully the Apache Axis in order to create a Web Service and a
Client for it. Both applications were created and deployed in PCs using
Java. In order to generate the proxy to the Web Service, I used the
wsdl2java tool. That was okay. Now, I have a little question to you
related to utilization of a Web Service by a Client installed in a cell
phone. Help me, please.

Let's supose I want to use a Web Service installed in a PC located in a
remote location from my cell phone. Let's supose I have the WSDL file
related to that Web Service as well. How can I generate the proxy to the
Web Service from its WSDL file in deployment time? Is it possible to
perform that on-demand procedure using Apache Axis or another product?

I am investigating how to use Web Services from a cell phone (or a PDA, or
another low computational power device). I know some conceptual
requirements to make that utilization possible. One of them is the
presence of a piece of software capable to send and receive SOAP (or
XML-RPC) messages. This piece of software is the proxy to the Web Service,
right? If a have a set of proxies installed in the cell phone related to
pre-defined Web Services, there is no problems. But, if I want to use a
new Web Services, I must follow two steps:

1. Obtain its related WSDL file;
2. convert that WSDL file in a proxy.

The step 1 must be accomplished with aid of a UDDI registry (by the way,
can I use a UDDI registry using the Apache Axis API?);

The step 2 brings me some questions. First: is it possible to perform that
on-demand conversion ? More accurately, Is it possible to perform it IN A
CELL PHONE ? Second: what is the burden imposed by that computational
power consuming task ?

My apologize for the long message, gentlemen. Any help will be welcome.
Thanks in advance.

H. Wagner

RE: Digital signatures on AXIS?

[glenn bech]

In my opinion, this is a bit more complex than just setting up Axis the
right way. 

If you need to do such things as "This message was signed by john smith",
you will need some kind of PKI infrastructure. 

You have to think of how you store and distribute your keys. How will
'client A' be able to reach client 'B's public' certificate for message
validation? 

If you want to go down this path, I found some articles on how to build axis
that way here ;

" This is needed for Axis to support signed and encrypted messages (as
opposed to unsigned messages over HTTPS, which is different)"

http://ws.apache.org/axis/java/building-axis.html
http://xml.apache.org/security/

However,  if you don't want to set-up the key infrastracuture, a strategy
for unsigned XML messages over HTTPS could still meet your need. 

Ask me if anything of this is unclear.

Best regards,

Glenn





-Original Message-
From: Hernan Bay Area Guy [mailto:[EMAIL PROTECTED] 
Sent: 2. februar 2006 02:20
To: axis-user@ws.apache.org
Subject: Digital signatures on AXIS?


Hello,

We have a prototype SOAP server running on AXIS 1.3
and would like to add client authentication using
digital signature.

I didn't find much information on the web, some
articles from 2002 or so mostly. According to these
articles, we need to use XML signatures, and
intercepti the messages before they reach the SOAP
engine itself to verify that the signature matches.

I'm still doing some research on this, but it's not
obvious to me how to tell the SOAP engine something
like "this message was signed by John Smith". We need
this type of functionality to be able to manage user's
permissions adequately of course.

We would like to avoid re-inventing the (square)
wheel, so pointers to articles / books on the subject,
and also any comments on how do you all implement
digital signatures on AXIS are much appreciated.

Many thanks in advance!

-- Hernan


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: Axis2 0.94 and WSDL2Java

[Justin Schoeman]

I see that by simply adding the operation name inside the stub, 
everything works fine.  Do you perhaps have the JIRA ref for this bug?


Thanks,

Justin


Ajith Ranabahu wrote:

Hi Justin,
Attach the WSDL please. I've the feeling that this is the codegen bug 
that we came across some time earlier but have to make sure.


On 1/31/06, *Justin Schoeman* <[EMAIL PROTECTED] 
> wrote:


Hi all, when using Axis2 0.94 and WSDL2Java to generate both client and
server, I get the following exception (just the first lines quoted):

org.apache.axis2.AxisFault: org.apache.axis2.AxisFault: Operation Not
found EPR is http://127.0.0.1:8080/axis2/services/XMLVendService2.0 and
WSA Action =
 at

org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:46)

Any idea what is wrong?
http://127.0.0.1:8080/axis2/services/expertron_client/XMLVendService2.0?wsdl

Gives me the WSDL for the service, so it seems to be up at the right
place.

Any idea what may be wrong here?

Thanks,

Justin




--
Ajith Ranabahu

Problem with AXIS-based web service client on WAS5.

[cees.van.wijk]

All,
 
I'm running into an XML parsing problem while migrating a web service client 
based on AXIS and WSIF from WAS 4 to WAS 5.
 
The error-message I get is: (the stacktrace is below)
 
Provider null could not be instantiated: java.lang.NullPointerException: 
javax.xml.parsers.FactoryConfigurationError: Provider null could not be 
instantiated: java.lang.NullPointerException
 
Does this problem sound familiar to anyone? All suggestions on how to fix this 
or on how to get more debug information are more then welcome.
 
Thanks in advance,
Cees van Wijk
 
 
 
 at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)
 at com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(Unknown Source)
 at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
 at org.apache.wsif.util.WSIFUtils.readWSDL(WSIFUtils.java:401)
 at org.apache.wsif.base.WSIFServiceImpl.(WSIFServiceImpl.java:186)
 at 
org.apache.wsif.base.WSIFServiceFactoryImpl.getService(WSIFServiceFactoryImpl.java:136)
 at 
dispatcher.WSDPServiceFactory.getServiceInstance(WSDPServiceFactory.java:165)
 at dispatcher.WSDPServiceFactory.getService(WSDPServiceFactory.java:132)
 at 
getcurrencyconversion.GetCurrencyConversionProxy.getService(GetCurrencyConversionProxy.java:59)
 at org.apache.jsp._test._jspService(_test.java:243)
 at com.ibm.ws.webcontainer.jsp.runtime.HttpJspBase.service(HttpJspBase.java:89)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at 
com.ibm.ws.webcontainer.jsp.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:344)
 at 
com.ibm.ws.webcontainer.jsp.servlet.JspServlet.serviceJspFile(JspServlet.java:669)
 at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.service(JspServlet.java:767)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at 
com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
 at 
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
 at 
com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
 at 
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
 at 
com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
 at 
com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
 at 
com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
 at 
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:983)
 at 
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:564)
 at 
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:200)
 at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:119)
 at 
com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:276)
 at 
com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
 at 
com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)
 at 
com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
 at 
com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
 at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:618)
 at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:439)
 at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:672)

 


This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise private information.  If you have received it in 
error, please notify the sender immediately and delete the original.  Any other 
use of the email by you is prohibited.