[Axis2] Trouble running Security sample client on Windows XP

[Jorge Ortiz Hinojosa]

I’m trying to run Axis2 as a webapp on Tomcat5.5 on WinXP
SP2 with JDK1.5. Specifically, I’m trying to run the “security”
sample client and service that come with the Axis2 distribution (under samples/security/).

 

The service shows up just fine in my list of services on http://localhost:8080/axis2/services/listServices

 

But when I try to run the client, I get the following:

 

***

 

C:\axis2\samples\security>ant securitySample

Buildfile: build.xml

 

securitySample:

 [java] log4j:WARN No appenders
could be found for logger (org.apache.axiom.om.impl.builder.StAXOMBuilder).

 [java] log4j:WARN Please initialize
the log4j system properly.

 [java] Exception in thread
"main" java.lang.NoClassDefFoundError: org/apache/xml/utils/URI$MalformedURIException

 [java] at
org.apache.ws.security.message.WSSecSignature.prepare(WSSecSignature.java:336)

 [java] at
org.apache.ws.security.message.WSSecSignature.build(WSSecSignature.java:643)

 [java] at org.apache.ws.security.action.SignatureAction.execute(SignatureAction.java:54)

 [java] at
org.apache.ws.security.handler.WSHandler.doSenderAction(WSHandler.java:191)

 [java] at
org.apache.axis2.security.WSDoAllSender.processMessage(WSDoAllSender.java:181)

 [java] at
org.apache.axis2.security.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:82)

 [java] at
org.apache.axis2.engine.Phase.invoke(Phase.java:381)

 [java] at
org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:473)

 [java] at
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:572)

 [java] at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:328)

 [java] at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:279)

 [java] at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:457)

 [java] at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:399)

 [java] at
sample.security.Client.main(Client.java:58)

 [java] Java Result: 1

 

BUILD SUCCESSFUL

Total time: 2 seconds

C:\axis2\samples\security>

 

***

 

Any idea what’s wrong?

 

Thanks,

 

Jorge

Troubles executing axis client on windows mobile (related to AxisEngine?)

[Herve Chang]

Hi all,

I'm currently developping a web service client using Axis.
This client is to be executed on a windows mobile pocketpc over the
Mysaifu JVM, built upon GNU Classpath libraries
(http://www.gnu.org/software/classpath/classpath.html).

When executing my client, AxisEngine seems not to be configured properly:

Exception in thread "Thread-1" java.lang.ExceptionInInitializerError
   at org.apache.axis.configuration.FileProvider.configureEngine
(FileProvider.java:179)

(Detailed stacktrace pasted below),
and I don't really know what is happening.
Note that, my client use axis stubs generated from the Axis WSDL2Java
tool, and this same client correcly runs on a desktop PC.


As I'm not an expert of the core axis engine, If you have any idea,
please tell me.


Regards,
Hervé


StackTrace follows:

in main client: before web service call
Exception in thread "Thread-1" java.lang.ExceptionInInitializerError
   at org.apache.axis.configuration.FileProvider.configureEngine
(FileProvider.java:179)

   at org.apache.axis.AxisEngine.init (AxisEngine.java:172)
   at org.apache.axis.AxisEngine. (AxisEngine.java:156)
   at org.apache.axis.client.AxisClient. (AxisClient.java:52)
   at org.apache.axis.client.Service.getAxisClient (Service.java:104)
   at org.apache.axis.client.Service. (Service.java:113)
   at
_10._1._168._192.axis1.services.MyServerValidate.MyServerValidateServiceLocator. 


(Unknown source)
   at MyClientValidate.sayHello (Unknown source)
   at MyClientValidate.main (Unknown source)
   at java.lang.reflect.Method.invokeNative (Native Method)
   at java.lang.reflect.Method.invoke (Method.java:329)
   at java.lang.VMMainThread$1.run (VMMainThread.java)
   at java.lang.VMThread.run (VMThread.java:120)
Caused by: java.lang.ExceptionInInitializerError
   at java.lang.VMClassLoader.loadClass (Native Method)
   at java.lang.ClassLoader.loadClass (ClassLoader.java:329)
   at java.lang.ClassLoader$1.loadClass (ClassLoader.java:1110)
   at java.lang.ClassLoader.loadClass (ClassLoader.java:294)
   at org.w3c.dom.bootstrap.DOMImplementationRegistry.newInstance
(DOMImplementationRegistry.java:140)
   at gnu.xml.dom.DomDocumentBuilderFactory.
(DomDocumentBuilderFactory.java:69)
   at java.lang.reflect.Constructor.constructNative (Native Method)
   at java.lang.reflect.Constructor.newInstance (Constructor.java:242)
   at java.lang.Class.newInstance (Class.java:1136)
   at javax.xml.parsers.DocumentBuilderFactory.newInstance
(DocumentBuilderFactory.java:104)
   at org.apache.axis.utils.XMLUtils.getDOMFactory (XMLUtils.java:221)
   at org.apache.axis.utils.XMLUtils. (XMLUtils.java)
   at org.apache.axis.utils.XMLUtils. (XMLUtils.java)
   at org.apache.axis.configuration.FileProvider.configureEngine
(FileProvider.java:179)
   ...12 more
Caused by: java.lang.ExceptionInInitializerError
   at java.lang.VMClass.forName (Native Method)
   at java.lang.Class.forName (Class.java:161)
   at gnu.xml.dom.ImplementationSource. (ImplementationSource.java)
   at gnu.xml.dom.ImplementationSource. (ImplementationSource.java)
   at java.lang.VMClassLoader.loadClass (Native Method)
   ...25 more
Caused by: java.lang.UnsatisfiedLinkError: Native library `xmlj' not
found (as file `xmlj') in gnu.classpath.boot.library.path and
java.library.path
   at java.lang.Runtime.loadLibrary (Runtime.java:763)
   at java.lang.System.loadLibrary (System.java:529)
   at gnu.xml.libxmlj.util.XMLJ.init (XMLJ.java:92)
   at gnu.xml.libxmlj.dom.GnomeDocumentBuilder.
(GnomeDocumentBuilder.java)
   at gnu.xml.libxmlj.dom.GnomeDocumentBuilder.
(GnomeDocumentBuilder.java)
   at java.lang.VMClass.forName (Native Method)
   ...29 more
JVM exit.


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

Re: [Axis 1.4] Server side question !!!

[Martin Gainty]

Luis-

*If* you write your own connector you can configure it in as a Connector in 
$TOMCAT_HOME/conf/server.xml
here is an example of the default Port 8080 connector..




Anyone else?
M-
*
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.



- Original Message - 
From: "Luis Rivera" <[EMAIL PROTECTED]>
To: 
Sent: Friday, July 14, 2006 5:35 PM
Subject: Re: [Axis 1.4] Server side question !!!


> 
> 
>Hi again Axis-Users/Devs,
> 
> I have another couple of questions:
> 
> Fisrt of all, after installing Tomcat and figuring out how to deploy my 
> application, I have sucessfully made my first client call to the empty 
> implementation. However, the original server side implementation (c++ 
> RogueWave) uses 4 different ports, one for each bindings (4 of them). Now 
> with Tomcat I have only one and I am using a different path to each binding, 
> so
> 
> 1) Can I configure Tomcat to use a different port for each service using a 
> different Connector for each one?
> 
> Second, my application will be accessed by the axis implementation via JNI. 
> I have read on the web that they should not be placed in the 
> webapps/axis/classes directory to avoid classloading problems of the static 
> llibrary. But if placing them in the shared/lib directory is not where I can 
> to place them,
> 
> 2) How can I make tomcat look into the directory where I want to place them? 
> (both in Windows/Solaris)? .. .should I just include them into the path?
> 
> Thanks in advance,
> --Luis R.
> 
> 
>>From: "Anne Thomas Manes" <[EMAIL PROTECTED]>
>>Reply-To: axis-user@ws.apache.org
>>To: axis-user@ws.apache.org
>>Subject: Re: [Axis 1.4] Server side question !!!
>>Date: Fri, 7 Jul 2006 18:12:54 -0400
>>
>>Go with Tomcat 5.5.
>>
>>On 7/7/06, Luis Rivera <[EMAIL PROTECTED]> wrote:
>>>
>>>Hi Anne,
>>>
>>>Fair enough and thanks agan :) ... I also think J2EE is overkill. Now, 
>>>what
>>>versino of Tomcat should I use? 5.5 is the one I downloaded, but it seems
>>>from the axis documentation they recomend 4.1. In any way it seems that
>>>configuring and deploying in Solaris are the trickiest parts of all this.
>>>
>>>The systinet idea was already explored here, but I guess they want to go 
>>>on
>>>the cheap. I guess it is up to me to prove that this can be done in a 
>>>fairly
>>>reasonable amount of time and with the smallest impact to the current
>>>implementation.
>>>
>>>Thanks in advance,
>>>--Luis R.
>>>
>>>
>>> >From: "Anne Thomas Manes" <[EMAIL PROTECTED]>
>>> >Reply-To: axis-user@ws.apache.org
>>> >To: axis-user@ws.apache.org
>>> >Subject: Re: [Axis 1.4] Server side question !!!
>>> >Date: Fri, 7 Jul 2006 16:40:29 -0400
>>> >
>>> >If you don't plan to use all the crap -- I mean features -- that comes
>>> >bundled with J2EE, then I see no reason whatsoever to use J2EE. If
>>> >your goal is simply to provide a very thin JNI veneer over your
>>> >existing C++ apps, then Axis/Tomcat is a much better, more
>>> >stream-lined solution.
>>> >
>>> >The only other suggestion that I recommend you explore is Systinet
>>> >Server for C++ (see http://www.systinet.com/products/ssc/overview).
>>> >It's not open source, but it is less expensive than LEIF.
>>> >
>>> >Anne
>>> >
>>> >On 7/7/06, Luis Rivera <[EMAIL PROTECTED]> wrote:
>>> >>
>>> >>First of all, thanks for the reply Anne, I appreciate it :)
>>> >>
>>> >>We already looked into C/C++ axis, but it is clearly not mature and 
>>>full
>>> >>of
>>> >>bugs. That let us with two choices:
>>> >>
>>> >>1) As you said, rewrite the whole server side in Java ... let's just 
>>>say
>>> >>this was not even a real option.
>>> >>
>>> >>2) Write a thin server side in Java with JNI as the bridge to the 
>>>already
>>> >>existing code in C++. The current architecture of the application 
>>>allows a
>>> >>simple substiution of the SOAP layer with a Java version, using the
>>> >>proxies
>>> >>behind to bridge the rest of the application.
>>> >>
>>> >>So, the server side in this case should be fairly simple, but I wanted 
>>>to
>>> >>know what made more sense for deployment knowing that the server side 
>>>can
>>> >>either be Solaris/Windows and in the near future Linux. I looked first
>>> >>into
>>> >>axis because I had the clients alredy using axis and it seemed to me 
>>>that
>>> >>having axis in both sides could simplyfy the task, but I may be wrong.
>>> >>
>>> >>So, let me ask again, knowing that I will use Java/JNI, is axis/Tomcat
>>> >>better or at least comparable to J2EE?
>>> >>
>>> >> Again, thanks in advance,
>>> >> --Luis R.
>>> >>
>>> >> >From: "Anne Thomas Manes" <[EMAIL PROTECTED]>
>>> >> >Reply-To: axis-us

Re: [Axis 1.4] Server side question !!!

[Luis Rivera]

   Hi again Axis-Users/Devs,

I have another couple of questions:

Fisrt of all, after installing Tomcat and figuring out how to deploy my 
application, I have sucessfully made my first client call to the empty 
implementation. However, the original server side implementation (c++ 
RogueWave) uses 4 different ports, one for each bindings (4 of them). Now 
with Tomcat I have only one and I am using a different path to each binding, 
so


1) Can I configure Tomcat to use a different port for each service using a 
different Connector for each one?


Second, my application will be accessed by the axis implementation via JNI. 
I have read on the web that they should not be placed in the 
webapps/axis/classes directory to avoid classloading problems of the static 
llibrary. But if placing them in the shared/lib directory is not where I can 
to place them,


2) How can I make tomcat look into the directory where I want to place them? 
(both in Windows/Solaris)? .. .should I just include them into the path?


Thanks in advance,
--Luis R.



From: "Anne Thomas Manes" <[EMAIL PROTECTED]>
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: Re: [Axis 1.4] Server side question !!!
Date: Fri, 7 Jul 2006 18:12:54 -0400

Go with Tomcat 5.5.

On 7/7/06, Luis Rivera <[EMAIL PROTECTED]> wrote:


   Hi Anne,

Fair enough and thanks agan :) ... I also think J2EE is overkill. Now, 
what

versino of Tomcat should I use? 5.5 is the one I downloaded, but it seems
from the axis documentation they recomend 4.1. In any way it seems that
configuring and deploying in Solaris are the trickiest parts of all this.

The systinet idea was already explored here, but I guess they want to go 
on
the cheap. I guess it is up to me to prove that this can be done in a 
fairly

reasonable amount of time and with the smallest impact to the current
implementation.

   Thanks in advance,
   --Luis R.


>From: "Anne Thomas Manes" <[EMAIL PROTECTED]>
>Reply-To: axis-user@ws.apache.org
>To: axis-user@ws.apache.org
>Subject: Re: [Axis 1.4] Server side question !!!
>Date: Fri, 7 Jul 2006 16:40:29 -0400
>
>If you don't plan to use all the crap -- I mean features -- that comes
>bundled with J2EE, then I see no reason whatsoever to use J2EE. If
>your goal is simply to provide a very thin JNI veneer over your
>existing C++ apps, then Axis/Tomcat is a much better, more
>stream-lined solution.
>
>The only other suggestion that I recommend you explore is Systinet
>Server for C++ (see http://www.systinet.com/products/ssc/overview).
>It's not open source, but it is less expensive than LEIF.
>
>Anne
>
>On 7/7/06, Luis Rivera <[EMAIL PROTECTED]> wrote:
>>
>>First of all, thanks for the reply Anne, I appreciate it :)
>>
>>We already looked into C/C++ axis, but it is clearly not mature and 
full

>>of
>>bugs. That let us with two choices:
>>
>>1) As you said, rewrite the whole server side in Java ... let's just 
say

>>this was not even a real option.
>>
>>2) Write a thin server side in Java with JNI as the bridge to the 
already
>>existing code in C++. The current architecture of the application 
allows a

>>simple substiution of the SOAP layer with a Java version, using the
>>proxies
>>behind to bridge the rest of the application.
>>
>>So, the server side in this case should be fairly simple, but I wanted 
to
>>know what made more sense for deployment knowing that the server side 
can

>>either be Solaris/Windows and in the near future Linux. I looked first
>>into
>>axis because I had the clients alredy using axis and it seemed to me 
that

>>having axis in both sides could simplyfy the task, but I may be wrong.
>>
>>So, let me ask again, knowing that I will use Java/JNI, is axis/Tomcat
>>better or at least comparable to J2EE?
>>
>> Again, thanks in advance,
>> --Luis R.
>>
>> >From: "Anne Thomas Manes" <[EMAIL PROTECTED]>
>> >Reply-To: axis-user@ws.apache.org
>> >To: axis-user@ws.apache.org
>> >Subject: Re: [Axis 1.4] Server side question !!!
>> >Date: Fri, 7 Jul 2006 08:53:44 -0400
>> >
>> >Axis supports C/C++. Given that you've been using LEIF, I assume that
>> >your services are written in C/C++. Do you intend to rewrite all your
>> >apps?
>> >
>> >Axis for Java can run in any servlet engine -- including any J2EE
>> >server. It's true that Sun's J2EE server includes a SOAP engine, but
>> >it doesn't support C/C++. Assuming that you really don't want to
>> >reimplement all your apps, Axis provides you with a common SOAP
>> >architecture that supports both Java and C++.
>> >
>> >Anne
>> >
>> >On 7/6/06, Luis Rivera <[EMAIL PROTECTED]> wrote:
>> >>
>> >>Hi axis users,
>> >>
>> >>I finally got the green light to port the server side or our web
>>services
>> >>from LEIF/Roguewave to axis. The main reason is economics, we want 
to

>> >>explore cheaper options.
>> >>
>> >>I was exploring the alternatives for serverlet containers in the 
server

>> >>side, which will be Windows/Solaris. I think the best for axis is
>>Tomcat,
>> >>but I 

Re: Undefined schema definition in request soap message

[Anne Thomas Manes]

My guess is that the fact that this message has been signed has
nothing to do with whether or not the message content is correct.

How was this message generated?
Can you post the WSDL?

The message doesn't conform to SOAP requirements, which states that
the child of the  must be a qualified element. Given that
there is no default namespace declared, and none of the elements are
explicitly qualified, the entire message is unqualified. (They do not
belong to "ns1".)

To answer your specific questions:


"AddressType" is declared to be belonging to the namespace
"http://www.mediclaim.org/2003/05"; however "AddressType" is not
defined in the soap message with the namespace
"http://www.mediclaim.org/2003/05";. Is this an error or my
understanding is wrong?


This indicates that the "AddressType" type is defined in a schema
whose targetNamespace is "http://www.mediclaim.org/2003/05";.


Also, since there is no namespace prefix for  element and its
child elements like ,   etc. does it mean all
these elements belong to default namespace instead of ns1 ? or do they
have to be explicitly prefixed with the namespace prefix ns1 ?. Is the
soap message generated using AXIS for the   element correct?


No default namespace has been defined; therefore, all of these
elements are in no namespace. They are not in the "ns1" namespace.
(Only the "AddressType" type is in the "ns1" namespace.) The message
is inappropriate, but Axis will generate a message that corresponds to
the WSDL. If the WSDL is wrong, the the resulting message will be
wrong.

Please post the WSDL.

Anne

On 7/14/06, akkachotu <[EMAIL PROTECTED]> wrote:

I have below soap message with WS Security Signature generated by Axis 1.2.1:


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

xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";

xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";>



...
...
http://www.mediclaim.org/2003/05";>
2200 W
VEGAS
34343
BLAH
USA








"AddressType" is declared to be belonging to the namespace
"http://www.mediclaim.org/2003/05"; however "AddressType" is not
defined in the soap message with the namespace
"http://www.mediclaim.org/2003/05";. Is this an error or my
understanding is wrong?

Also, since there is no namespace prefix for  element and its
child elements like ,   etc. does it mean all
these elements belong to default namespace instead of ns1 ? or do they
have to be explicitly prefixed with the namespace prefix ns1 ?. Is the
soap message generated using AXIS for the   element correct?


Can anyone please clarify?

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




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

Axis src build solved

[Martin Gainty]

To All-

The source download the source from the axis2 site is problematic ..unless you 
want to spend days reconfiguring maven and jelly properties files
Instead
from %AXIS2_HOME%
create a new source folder e.g. new_src
svn checkout http://svn.apache.org/repos/asf/webservices/axis2/trunk/java 
./new_src
cd /new_src
$MAVEN_HOME/bin/maven

Suggestion to all axis2 developers
replace the src.zip with the latest working jar'ed source from svn.apache.org

Happy programming to all/
Martin-
*
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.



- Original Message - 
From: <[EMAIL PROTECTED]>
To: 
Sent: Friday, July 14, 2006 8:49 AM
Subject: AW: [axis2] Setting realtesTo() leads to Exception while sending


Hi Eran,

your new version of the addressing module works fine. Yesterday I figured out 
the problem you solved now cuse walking through the code takes me to use the 
other constructor and the problem was fixed. Cause you was so quick in fixing 
the bug, I just couldn't help you anymore ;-)

So, there is an other 'problem' now and maybe you can give me an answer (wich 
will bring me a big time affort not walking through all the code and debugging 
it): the Fault wich is created now is, that the system is not able to correlate 
the message I send (wich is not a failure cause  the id i used for testing is a 
randomized one). My question about it is: is it possible to have an entry to a 
service operation with an in-only mep to provide it a id from a message wich 
was sent via an other endpoint of the system?

Thanks a lot!
Ted

- Ursprüngliche Mail 
Von: Eran Chinthaka <[EMAIL PROTECTED]>
An: axis-user@ws.apache.org
Gesendet: Freitag, den 14. Juli 2006, 10:34:06 Uhr
Betreff: Re: [axis2] Setting realtesTo() leads to Exception while sending


hi,

I just ran your code and found a bug in our addressing code. I fixed it
and now I got the code working.

Can you test it now?

-- Chinthaka

[EMAIL PROTECTED] wrote:
> Hi,
> 
> I already posted this problem a week ago, but cause it still exists I try it 
> with some more detail I figured out up till now.
> 
> The problem is, using fireAndForget to send some Data from one Service to an 
> other and setting WSA relatesTo at the ServiceClients options, no xml content 
> is send. The Exception wich is throws from out of the system is ... not very 
> helpfull but here it is:
> 
> - Servlet.service() for servlet AxisServlet threw exception
> org.apache.axiom.om.OMException: SOAPEnvelope must contain a body element 
> which is either first or second child element of the SOAPEnvelope.
> at 
> org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getBody(SOAPEnvelope 
> Impl.java:142)
> at 
> org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.addChild(SOAPEnvelopeImpl.java:103)
> at 
> org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeImpl.java:82)
> at 
> org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngine.java:183)
> at 
> org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:168)
> at 
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:153)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
> 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.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
> at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
> 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:869)
> at 
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
> at 
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
> at 
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
> at 
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
> 

Undefined schema definition in request soap message

[akkachotu]

I have below soap message with WS Security Signature generated by Axis 1.2.1:


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

xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";

xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";>



...
...
http://www.mediclaim.org/2003/05";>
2200 W
VEGAS
34343
BLAH
USA








"AddressType" is declared to be belonging to the namespace
"http://www.mediclaim.org/2003/05"; however "AddressType" is not
defined in the soap message with the namespace
"http://www.mediclaim.org/2003/05";. Is this an error or my
understanding is wrong?

Also, since there is no namespace prefix for  element and its
child elements like ,   etc. does it mean all
these elements belong to default namespace instead of ns1 ? or do they
have to be explicitly prefixed with the namespace prefix ns1 ?. Is the
soap message generated using AXIS for the   element correct?


Can anyone please clarify?

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

Re: Repost: WSSecurityException - Check Signature confirmation (Axis 1.4 + wss4j)

[Ravi Krishnamurthy]

Hello:
Could anybody give some pointers please. I'm running the Scenario3
application. I also posted this question to wss4j but no replies.

Regards,
Ravi

Ravi Krishnamurthy wrote:

  
Hello:
Would appreciate if someone could give me some pointers.
  
Thanks,
Ravi
  
Ravi Krishnamurthy wrote:
  


Hello:
I'm trying to use wss4j with Axis1.4 and trying out the samples that
comes with wss4j/interop.

On executing the org.apache.ws.axis.oasis.Scenario3  I get the
following exception:

WSHandler: Check Signature confirmation: stored SV vector not empty;
nested exception is: 
    org.apache.ws.security.WSSecurityException: WSHandler: Check
Signature confirmation: stored SV vector not empty
    at
org.apache.ws.axis.security.WSDoAllReceiver.invoke(WSDoAllReceiver.java:351)

I monitor the soap messages through the tcpmon and they are below:

request soap message:
--

   "http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  
 "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
soapenv:mustUnderstand="1">
    "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
wsu:Id="Timestamp-6559246">
  
2006-07-10T20:19:53.011Z
  
2006-07-10T20:24:53.011Z
    
    
   "http://www.w3.org/2001/04/xmlenc#rsa-1_5">
   "http://www.w3.org/2000/09/xmldsig#">
  
 "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"
ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier">Xeg55vRyK3ZhAEhEf+YT0z986L0=
  
   
   
 
HEhP2Wm923TOcrC6vcfyf3I7BQPFW6pzZb4oRsV6GHL1THJvLbmjeIGTX9p3/6bLL4lQEy/7M3Sk2znE7QBjTtQuip+WAiJuiKONzQRC175FZTkhNgF6iD62/ikuGMihR3yn/1KZtjMiH8k/gh1Q+sRW0pD8JmEKnBWw2hhX/n8=
   
   
  
   
    
    "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"
ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"
wsu:Id="CertId-1776694">MIIDDDCCAfSgAwIBAgIQM6YEf7FVYx/tZyEXgVComTANBgkqhkiG9w0BAQUFADAwMQ4wDAYDVQQKDAVPQVNJUzEeMBwGA1UEAwwVT0FTSVMgSW50ZXJvcCBUZXN0IENBMB4XDTA1MDMxOTAwMDAwMFoXDTE4MDMxOTIzNTk1OVowQjEOMAwGA1UECgwFT0FTSVMxIDAeBgNVBAsMF09BU0lTIEludGVyb3AgVGVzdCBDZXJ0MQ4wDAYDVQQDDAVBbGljZTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAoqi99By1VYo0aHrkKCNT4DkIgPL/SgahbeKdGhrbu3K2XG7arfD9tqIBIKMfrX4Gp90NJa85AV1yiNsEyvq+mUnMpNcKnLXLOjkTmMCqDYbbkehJlXPnaWLzve+mW0pJdPxtf3rbD4PS/cBQIvtpjmrDAU8VsZKT8DN5Kyz+EZsCAwEAAaOBkzCBkDAJBgNVHRMEAjAAMDMGA1UdHwQsMCowKKImhiRodHRwOi8vaW50ZXJvcC5iYnRlc3QubmV0L2NybC9jYS5jcmwwDgYDVR0PAQH/BAQDAgSwMB0GA1UdDgQWBBQK4l0TUHZ1QV3V2QtlLNDm+PoxiDAfBgNVHSMEGDAWgBTAnSj8wes1oR3WqqqgHBpNwkkPDzANBgkqhkiG9w0BAQUFAAOCAQEABTqpOpvW+6yrLXyUlP2xJbEkohXHI5OWwKWleOb9hlkhWntUalfcFOJAgUyH30TTpHldzx1+vK2LPzhoUFKYHE1IyQvokBN2JjFO64BQukCKnZhldLRPxGhfkTdxQgdf5rCK/wh3xVsZCNTfuMNmlAM6lOAg8QduDah3WFZpEA0s2nwQaCNQTNMjJC8tav1CBr6+E5FAmwPXP7pJxn9Fw9OXRyqbRA4v2y7YpbGkG2GI9UvOHw6SGvf4FRSthMMO35

YbpikGsLix3vAsXWWi4rwfVOYzQK0OFPNi9RMCUdSH06m9uLWckiCxjos0FQODZE9l4ATGy9s9hNVwryOJTw==
    "http://www.w3.org/2000/09/xmldsig#"
Id="Signature-2950265">
   
  "http://www.w3.org/2001/10/xml-exc-c14n#">
  "http://www.w3.org/2000/09/xmldsig#rsa-sha1">
  
 
    "http://www.w3.org/2001/10/xml-exc-c14n#">
 
 "http://www.w3.org/2000/09/xmldsig#sha1">

zzx3ig1a7LmzkrkBpLOTIJbLd3s=
  
   
  
IuRirKy+x18gU00p0uhMEDzEAFvpoHMGKcq45ROmpzQ6ZpD/VEghpYjru6Kff0y3tyWzSvW6nA1mH1pudDP1yLxP5geYvXNPQlFV5X+7T60QPlM6ho3sBj2D3IDAZZXZQdJV+fqC7JycqdzLfXU15fHw+ReZm2r7hIPoys9eHgg=
   
  "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
wsu:Id="STRId-29769356">
 "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3">
  
   
    
 
  
  "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
wsu:Id="id-30568553">
 "http://www.w3.org/2001/04/xmlenc#Content">
    "http://www.w3.org/2001/04/xmlenc#aes128-cbc">
    
  
oXcNsV8AMx98dJom1wFX1i6y0Q90oPf7SpLM88MqCsc9dbVFkJNwN5prhs3WXUtjQ40IKuBRxX+MRNg+J79tT3sm+ivzH7+qol3JaudVz5ahPyLO7BPHmjOLNFV0YrtVs+dUbjhtJHk152uU6Lty/3l9RKuPbC6FDy6NGNpF

RE: AW: How to access the SOAPHeader

[Derek]

+1 from me. Interfaces defined only by implicit signatures and invoked via
reflection scare me, since if I misremember the arguments or names, things
fail to work with no compiler warnings. I much prefer interfaces defined by
actual 'implements' declarations, which my IDE (IntelliJ IDEA) can check at
edit time to warn me if I am doing something wrong.

Derek

> -Original Message-
> From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
> Sent: Friday, July 14, 2006 5:21 AM
> To: axis-user@ws.apache.org
> Subject: Re: AW: How to access the SOAPHeader
> 
> 
> +1 from me.
> 
> On 7/14/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
> > so lets go for that , AFAIK we only need to change 
> DependencyManager 
> > to support that.
> >
> > Eran Chinthaka wrote:
> >
> > >Rodrigo Ruiz wrote:
> > >
> > >
> > >>Mmm, yes of course. But I guess you are talking about a mandatory 
> > >>interface, like Remote. I am talking about an optional one, like 
> > >>LifeCycle. For example:
> > >>
> > >>public interface ContextAware {
> > >>  void setOperationContext(OperationContext ctx);
> > >>}
> > >>
> > >>In this case, only those services interested in having this data 
> > >>will need to implement it. The rest can work just like now.
> > >>
> > >>Such an interface would make reflection/introspection 
> unnecessary, 
> > >>and the relationship with Axis2 more explicit.
> > >>
> > >>
> > >
> > >Hmm, now it makes sense to me :). I can remember there was a 
> > >discussion on the same topic some time back, on this list, but can 
> > >not remember what happened to it.
> > >
> > >What do the others think about this? Can I implement this?
> > >
> > >For the time being, lets leave the dependency injection for the 
> > >existing code to work and implement this as well.
> > >
> > >Comments ?
> > >
> > >-- Chinthaka
> > >
> > >
> > >
> >
> > --
> > Thanks,
> > Deepal 
> > 
> > ~Future is Open~
> >
> >
> >
> > 
> -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> 
> 
> -- 
> Davanum Srinivas : http://www.wso2.net (Oxygen for Web 
> Service Developers)
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 



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

Re: AW: How to access the SOAPHeader

[Eran Chinthaka]

Ok guys. its implemented and committed to the code base. You may try it now.

You need to implement org.apache.axis2.Service interface.

-- Chinthaka

Davanum Srinivas wrote:
> +1 from me.
> 
> On 7/14/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
>> so lets go for that , AFAIK we only need to change DependencyManager to
>> support that.
>>
>> Eran Chinthaka wrote:
>>
>> >Rodrigo Ruiz wrote:
>> >
>> >
>> >>Mmm, yes of course. But I guess you are talking about a mandatory
>> >>interface, like Remote. I am talking about an optional one, like
>> >>LifeCycle. For example:
>> >>
>> >>public interface ContextAware {
>> >>  void setOperationContext(OperationContext ctx);
>> >>}
>> >>
>> >>In this case, only those services interested in having this data will
>> >>need to implement it. The rest can work just like now.
>> >>
>> >>Such an interface would make reflection/introspection unnecessary, and
>> >>the relationship with Axis2 more explicit.
>> >>
>> >>
>> >
>> >Hmm, now it makes sense to me :). I can remember there was a discussion
>> >on the same topic some time back, on this list, but can not remember
>> >what happened to it.
>> >
>> >What do the others think about this? Can I implement this?
>> >
>> >For the time being, lets leave the dependency injection for the existing
>> >code to work and implement this as well.
>> >
>> >Comments ?
>> >
>> >-- Chinthaka
>> >
>> >
>> >
>>
>> -- 
>> Thanks,
>> Deepal
>> 
>> ~Future is Open~
>>
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 




signature.asc
Description: OpenPGP digital signature

Re: [Axis2] re: WSDL2Java does not handle xsd:include correctly

[Martin Gainty]

Good Morning Everyone

Whomever is in charge of the repository 
Can we get the maven-itest-plugin-1.0.jar into the repository?
go to %AXIS2_HOME%/src
%MAVEN_HOME%/bin/maven

Attempting to download maven-itest-plugin-1.0.jar.
Error retrieving artifact from [http://cvs.apache.org/repository/maven-itest-plu
gin/plugins/maven-itest-plugin-1.0.jar]: java.io.IOException: Unknown error down
loading; status code was: 302
Error retrieving artifact from [http://www.openejb.org/maven/maven-itest-plugin/
plugins/maven-itest-plugin-1.0.jar]: java.io.IOException: Unknown error download
ing; status code was: 302
WARNING: Failed to download maven-itest-plugin-1.0.jar.

Advice or suggestions?
Martin--
*
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.



- Original Message - 
From: "Marc Gagnon" <[EMAIL PROTECTED]>
To: "axis2 " 
Sent: Thursday, July 13, 2006 10:13 PM
Subject: [Axis2] re: WSDL2Java does not handle xsd:include correctly


> Thank you for the suggestions, Anne... But my most recent tests failed again:
> 
> I modified the WSDL like you suggested (see xml comments):
> 
> 
> http://schemas.xmlsoap.org/wsdl/";
> xmlns:ota="http://www.opentravel.org/OTA/2003/05";
> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
> xmlns:http="http://schemas.xmlsoap.org/wsdl/http/";
> xmlns:xs="http://www.w3.org/2001/XMLSchema";
> targetNamespace="http://www.opentravel.org/OTA/2003/05";>
> 
> http://www.opentravel.org/OTA/2003/05"; 
> location="OTA_VehResInterface.wsdl"/>
> 
>  type="ota:VehicleReservationPortType">
> 
>  transport="http://schemas.xmlsoap.org/soap/http"/>
> 
> 
> 
> 
>
> 
> 
>
> 
> 
> 
> 
> 
> 
> 
> http://mydomain/myservicename"/>
> 
> 
> 
> 
> And the other WSDL (types):
> 
> 
> http://schemas.xmlsoap.org/wsdl/"; 
> xmlns:ota="http://www.opentravel.org/OTA/2003/05"; 
> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; 
> xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; 
> xmlns:xs="http://www.w3.org/2001/XMLSchema"; 
> targetNamespace="http://www.opentravel.org/OTA/2003/05"; 
> name="VehReservationService">
> 
> 
> 
> 
> 
> 
> http://www.opentravel.org/OTA/2003/05";>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Same result:
> 
> Axis2 1.0: wsdl2java -uri vehicule.wsdl
> 
> Using AXIS2_HOME:   c:\JavaLib\axis2-std-1.0_bin
> Using JAVA_HOME:c:\Program Files\Java\jdk1.5.0_06
> Retrieving document at 'OTA_VehResInterface.wsdl', relative to 
> 'file:/C:/workspace/TestOTA/wsdl/'.
> Retrieving schema at 'OTA_VehResRQ.xsd', relative to 
> 'file:/C:/workspace/TestOTA/wsdl/OTA_VehResInterface.wsdl'.
> Retrieving schema at 'OTA_VehicleCommonTypes.xsd', relative to 
> 'file:/C:/workspace/TestOTA/wsdl/OTA_VehResRQ.xsd'.
> Retrieving schema at 'OTA_SimpleTypes.xsd', relative to 
> 'file:/C:/workspace/TestOTA/wsdl/OTA_VehicleCommonTypes.xsd'.
> Retrieving schema at 'OTA_CommonTypes.xsd', relative to 
> 'file:/C:/workspace/TestOTA/wsdl/OTA_VehicleCommonTypes.xsd'.
> Retrieving schema at 'OTA_SimpleTypes.xsd', relative to 
> 'file:/C:/workspace/TestOTA/wsdl/OTA_CommonTypes.xsd'.
> Retrieving schema at 'OTA_AirCommonTypes.xsd', relative to 
> 'file:/C:/workspace/TestOTA/wsdl/OTA_VehicleCommonTypes.xsd'.
> Retrieving schema at 'OTA_SimpleTypes.xsd', relative to 
> 'file:/C:/workspace/TestOTA/wsdl/OTA_AirCommonTypes.xsd'.
> Retrieving schema at 'OTA_CommonTypes.xsd', relative to 
> 'file:/C:/workspace/TestOTA/wsdl/OTA_AirCommonTypes.xsd'.
> Retrieving schema at 'OTA_CommonPrefs.xsd', relative to 
> 'file:/C:/workspace/TestOTA/wsdl/OTA_VehicleCommonTypes.xsd'.
> Retrieving schema at 'OTA_SimpleTypes.xsd', relative to 
> 'file:/C:/workspace/TestOTA/wsdl/OTA_CommonPrefs.xsd'.
> Retrieving schema at 'OTA_CommonTypes.xsd', relative to 
> 'file:/C:/workspace/TestOTA/wsdl/OTA_CommonPrefs.xsd'.
> Retrieving schema at 'OTA_SimpleTypes.xsd', relative to 
> 'file:/C:/workspace/TestOTA/wsdl/OTA_VehResRQ.xsd'.
> Retrieving schema at 'OTA_CommonTypes.xsd', relative to 
> 'file:/C:/workspace/TestOTA/wsdl/OTA_VehResRQ.xsd'.
> Retrieving schema at 'OTA_AirCommonTypes.xsd', relative to 
> 'file:/C:/workspace/TestOTA/wsdl/OTA_VehResRQ.xsd'.
> Retrieving schema at 'OTA_CommonPrefs.xsd', relative to 
> 'file:/C:/workspace/TestOTA/wsdl/OTA_VehResRQ.xsd'.
> Retrieving schema at 'OTA_VehResRS.xsd', relative to 
> 'file:/C:/workspace/TestOTA/wsdl/OTA_VehResInterface.wsdl'.
> Retrieving schema at 'OTA_VehicleCommonTypes.xsd', relative to 
> 'file:/C:/workspace/TestOTA/wsdl/OTA_VehResRS.xsd'.
> Retrieving schema at 'OTA_SimpleTypes.xsd', relative to 
> 'file:/C:/workspace/TestOTA/wsdl/OTA_VehResRS.xsd'.
> Retrieving schema at 'OTA_CommonTypes.xsd', relative t

RE: AW: How to access the SOAPHeader

[Tony Dean]

This makes perfect sense to me.  This is how I thought it should have been from 
the start.

I started working with service lifecycle from the start and initially all that 
was available was init() and destroy().  If there had been a lifecycle 
interface that I was required to implement, when things changed to 
init(ServiceContext), destroy(ServiceContext), and 
setOperationContext(OperationContext), I would have been warned about it at 
compile time and not wondering why my old init() code wasn't being called at 
runtime.

-Tony

-Original Message-
From: Eran Chinthaka [mailto:[EMAIL PROTECTED] 
Sent: Friday, July 14, 2006 8:06 AM
To: axis-user@ws.apache.org
Subject: Re: AW: How to access the SOAPHeader

Rodrigo Ruiz wrote:
> Mmm, yes of course. But I guess you are talking about a mandatory 
> interface, like Remote. I am talking about an optional one, like 
> LifeCycle. For example:
> 
> public interface ContextAware {
>   void setOperationContext(OperationContext ctx); }
> 
> In this case, only those services interested in having this data will 
> need to implement it. The rest can work just like now.
> 
> Such an interface would make reflection/introspection unnecessary, and 
> the relationship with Axis2 more explicit.

Hmm, now it makes sense to me :). I can remember there was a discussion on the 
same topic some time back, on this list, but can not remember what happened to 
it.

What do the others think about this? Can I implement this?

For the time being, lets leave the dependency injection for the existing code 
to work and implement this as well.

Comments ?

-- Chinthaka


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

WSDoAllReceiver: Request does not contain required Security header

[Kirby Ian]

-Original Message-
Sent: Friday, July 14, 2006 9:37 AM
To: wss4j-dev@ws.apache.org

Please help if you can.
 
I'm trying to set up a web service and I'm having problems with the
security validation for our client.
The web service works fine for our test web client, which is written in
Java and run using the axis toolkit.
Our client uses .NET as their web client and reciprical web service.
 
When our client tries the web service they receive an error Error logged
by the Supplier Outbound Interface in
xmlSupplierOutboundService_MessageArrived. Error was WSDoAllReceiver:
Request does not contain required Security header
 
When we run the web service using the web client we have, everything is
fine.
 
The only thing I've been able to find different are WSRP: tags and that
the WSSE: and WSU: namespaces are different. I think that it's the
different namepsaces that are causing the problem.
I've been searching the web, but been unable to find anything that helps
me alter the Axis namespaces. I'm sure it can be done, the WSS4J
examples all seem to use the alternative, but I just don't know how this
can be done. 
Could someone please let me know how to configure Axis to use the
alternative namespaces.
 
Our Environment is
Linux (Red Hat Linux Advanced Server release 2.1AS (Pensacola); kernel
version 2.4.9-e.27smp) Apache HTTP 1.3 Apache Tomcat 4.1.31 Apache Axis
1.3 WSS4j 1.1.0 (tried 1.5 first, but this didn't have the alternatives
in
WSConstants)
 
The client environment is
.NET / WSE 1.0
 
The Server WSDD is
http://xml.apache.org/axis/wsdd/";
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
 
  
   





   
  
  
  


 
The Client .NET SOAP Message is
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
 
  http://schemas.xmlsoap.org/soap/actor/next";
soap:mustUnderstand="1" xmlns:wsrp="http://schemas.xmlsoap.org/rp";>
   
http://www.client.com/CLIENT/PassXMLDocument   
   
https://OurServer/axis/services/OurSOAPService   
   
uuid:131f35ce-433f-47a9-aa16-237921ed50d4   
  
  http://schemas.xmlsoap.org/ws/2002/07/utility";>
   
2006-07-07T15:06:12Z   
   
2006-07-07T15:11:12Z   
  
  http://schemas.xmlsoap.org/ws/2002/07/secext";>
   http://schemas.xmlsoap.org/ws/2002/07/utility";>

UserName

Password

VDQmAV8uqT6z8zcxC1V75w==

2006-07-07T15:06:12Z
   
  
 
 
  http://www.client.com/CLIENT/";>
   
< (rest of XML data document
... ) 
  
 

 
The SOAP Message generated by our client is  http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
  
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wsse
curity-secext-1.0.xsd" soapenv:mustUnderstand="1">
  http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec
urity-utility-1.0.xsd" wsu:Id="UsernameToken-1725467642">
 UserName
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-t
oken-profile-1.0#PasswordText">
Password
TvzcnguhUyPrGmKUd/4uxg==
2006-07-10T11:18:29.272Z
  
  http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec
urity-utility-1.0.xsd" wsu:Id="Timestamp-134106106">
2006-07-10T11:18:29.009Z
2006-07-10T11:23:29.009Z
  

  
  
http://ws.rsa.b2b.signet";>< (rest of XML data document ... ) 
  

 

Any help greatly appreciated.
Regards,
Ian Kirby


*

This E-mail and any files transmitted with it is intended for the use of the
addressee only and may contain confidential information. If you are not the
intended recipient you are hereby notified that any use or dissemination of
this communication is strictly prohibited. If you receive this transmission
in error, please notify us immediately and delete this e-mail.
The views and opinions expressed in this e-mail message are the author's own
and may not reflect the views and opinions of Signet Group plc
or any of its subsidiaries.
***

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

AW: [axis2] Setting realtesTo() leads to Exception while sending

[donnerdrummel2000-mailing]

Hi Eran,

your new version of the addressing module works fine. Yesterday I figured out 
the problem you solved now cuse walking through the code takes me to use the 
other constructor and the problem was fixed. Cause you was so quick in fixing 
the bug, I just couldn't help you anymore ;-)

So, there is an other 'problem' now and maybe you can give me an answer (wich 
will bring me a big time affort not walking through all the code and debugging 
it): the Fault wich is created now is, that the system is not able to correlate 
the message I send (wich is not a failure cause  the id i used for testing is a 
randomized one). My question about it is: is it possible to have an entry to a 
service operation with an in-only mep to provide it a id from a message wich 
was sent via an other endpoint of the system?

Thanks a lot!
Ted

- Ursprüngliche Mail 
Von: Eran Chinthaka <[EMAIL PROTECTED]>
An: axis-user@ws.apache.org
Gesendet: Freitag, den 14. Juli 2006, 10:34:06 Uhr
Betreff: Re: [axis2] Setting realtesTo() leads to Exception while sending


hi,

I just ran your code and found a bug in our addressing code. I fixed it
and now I got the code working.

Can you test it now?

-- Chinthaka

[EMAIL PROTECTED] wrote:
> Hi,
> 
> I already posted this problem a week ago, but cause it still exists I try it 
> with some more detail I figured out up till now.
> 
> The problem is, using fireAndForget to send some Data from one Service to an 
> other and setting WSA relatesTo at the ServiceClients options, no xml content 
> is send. The Exception wich is throws from out of the system is ... not very 
> helpfull but here it is:
> 
> - Servlet.service() for servlet AxisServlet threw exception
> org.apache.axiom.om.OMException: SOAPEnvelope must contain a body element 
> which is either first or second child element of the SOAPEnvelope.
> at 
> org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getBody(SOAPEnvelope 
> Impl.java:142)
> at 
> org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.addChild(SOAPEnvelopeImpl.java:103)
> at 
> org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeImpl.java:82)
> at 
> org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngine.java:183)
> at 
> org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:168)
> at 
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:153)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
> 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.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
> at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
> 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:869)
> at 
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
> at 
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
> at 
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
> at 
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
> at java.lang.Thread.run(Thread.java:595)
> - Servlet.service() for servlet jsp threw exception
> java.lang.IllegalStateException: getOutputStream() has already been called 
> for this response
> at org.apache.catalina.connector.Response.getWriter(Response.java:599)
> at 
> org.apache.catalina.connector.ResponseFacade.getWriter(ResponseFacade.java:195)
> at 
> org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:124)
> at 
> org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:117)
> at 
> org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java:191)
> at 
> org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspFactoryImpl.java:115)
> at 
> org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(JspFactoryImpl.java:75)
> at 
> org.apache.jsp.axis2_002dweb.Error.error500_jsp._jspService(error500_jsp.java:97)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
> at javax.servlet.http.HttpSer

Re: AW: How to access the SOAPHeader

[Davanum Srinivas]

+1 from me.

On 7/14/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:

so lets go for that , AFAIK we only need to change DependencyManager to
support that.

Eran Chinthaka wrote:

>Rodrigo Ruiz wrote:
>
>
>>Mmm, yes of course. But I guess you are talking about a mandatory
>>interface, like Remote. I am talking about an optional one, like
>>LifeCycle. For example:
>>
>>public interface ContextAware {
>>  void setOperationContext(OperationContext ctx);
>>}
>>
>>In this case, only those services interested in having this data will
>>need to implement it. The rest can work just like now.
>>
>>Such an interface would make reflection/introspection unnecessary, and
>>the relationship with Axis2 more explicit.
>>
>>
>
>Hmm, now it makes sense to me :). I can remember there was a discussion
>on the same topic some time back, on this list, but can not remember
>what happened to it.
>
>What do the others think about this? Can I implement this?
>
>For the time being, lets leave the dependency injection for the existing
>code to work and implement this as well.
>
>Comments ?
>
>-- Chinthaka
>
>
>

--
Thanks,
Deepal

~Future is Open~



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





--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

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

Re: AW: How to access the SOAPHeader

[Deepal Jayasinghe]

so lets go for that , AFAIK we only need to change DependencyManager to
support that.

Eran Chinthaka wrote:

>Rodrigo Ruiz wrote:
>  
>
>>Mmm, yes of course. But I guess you are talking about a mandatory
>>interface, like Remote. I am talking about an optional one, like
>>LifeCycle. For example:
>>
>>public interface ContextAware {
>>  void setOperationContext(OperationContext ctx);
>>}
>>
>>In this case, only those services interested in having this data will
>>need to implement it. The rest can work just like now.
>>
>>Such an interface would make reflection/introspection unnecessary, and
>>the relationship with Axis2 more explicit.
>>
>>
>
>Hmm, now it makes sense to me :). I can remember there was a discussion
>on the same topic some time back, on this list, but can not remember
>what happened to it.
>
>What do the others think about this? Can I implement this?
>
>For the time being, lets leave the dependency injection for the existing
>code to work and implement this as well.
>
>Comments ?
>
>-- Chinthaka
>
>  
>

-- 
Thanks,
Deepal

~Future is Open~ 



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

Re: AW: How to access the SOAPHeader

[Eran Chinthaka]

Rodrigo Ruiz wrote:
> Mmm, yes of course. But I guess you are talking about a mandatory
> interface, like Remote. I am talking about an optional one, like
> LifeCycle. For example:
> 
> public interface ContextAware {
>   void setOperationContext(OperationContext ctx);
> }
> 
> In this case, only those services interested in having this data will
> need to implement it. The rest can work just like now.
> 
> Such an interface would make reflection/introspection unnecessary, and
> the relationship with Axis2 more explicit.

Hmm, now it makes sense to me :). I can remember there was a discussion
on the same topic some time back, on this list, but can not remember
what happened to it.

What do the others think about this? Can I implement this?

For the time being, lets leave the dependency injection for the existing
code to work and implement this as well.

Comments ?

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

AW: [Axis2] Exception after correct sending message with fireAndForget()

[donnerdrummel2000-mailing]

Hi Deepal,

the scenario is as followes:
- Two services 'Service A' running on 
http://localhost:8080/axis2/services/ServiceA and ServiceB running on   
  http://localhost:8585/axis2/services/ServiceB. Both services provide a 
'InOnly' operation.
- A Serviceconsumer now sends a message to ServiceA and as a listener for 
Service A's response Service B has to be 
  is used.

The code I wrote for that scenario is a ServiceA wich has a (private) method to 
send a response to ServiceB using an OutOnlyAxisOperation. The thing is, that 
the message receives correctly at ServiceB's provided 'InOnly'-operation but 
the exception with that transport error occours afterwards.

Hope that helps. Let me know if you need more detail (for example some concrete 
parts of code),

Greetings
Ted



- Ursprüngliche Mail 
Von: Deepal Jayasinghe <[EMAIL PROTECTED]>
An: axis-user@ws.apache.org
Gesendet: Freitag, den 14. Juli 2006, 11:50:36 Uhr
Betreff: Re: [Axis2] Exception after correct sending message with 
fireAndForget()

Hi ;


[EMAIL PROTECTED] wrote:

>Hi,
>
>senden a message using fireAndForget(), the message was delivered properly but 
>there is allways this exception wich occours:
>
>  
>
I doubt , how can it deliver the message with following exception, btw
can you please help me to regenerate the problem.

>INFO: Axis2 transport error : No Host matches server name 127.0.0.1; nested 
>exception is:
>org.apache.axis2.AxisFault: Axis2 transport error : No Host matches 
> server name 127.0.0.1; nested exception is:
>org.apache.axis2.AxisFault: Axis2 transport error : No Host matches 
> server name 127.0.0.1; nested exception is:
>org.apache.axis2.AxisFault: Axis2 transport error : No Host matches 
> server name 127.0.0.1
>
>
>Is this a normal behavior (cause it is published using a log.info level)?
>
>
>Thanks Ted
>
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>  
>

-- 
Thanks,
Deepal

~Future is Open~ 



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





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

Re: AW: How to access the SOAPHeader

[Rodrigo Ruiz]

Mmm, yes of course. But I guess you are talking about a mandatory
interface, like Remote. I am talking about an optional one, like
LifeCycle. For example:

public interface ContextAware {
  void setOperationContext(OperationContext ctx);
}

In this case, only those services interested in having this data will
need to implement it. The rest can work just like now.

Such an interface would make reflection/introspection unnecessary, and
the relationship with Axis2 more explicit.

Rodrigo

Eran Chinthaka wrote:
> Hi Rodrigu,
> 
> Rodrigo Ruiz wrote:
>> Eran Chinthaka wrote:
>>> We didn't want to put any restriction on a user who wanna write a simple
>>> java class and expose that as a web service. Thats been the case so far.
>>> I hope you can understand that it will make the most common and simple
>>> case simple.
>>> And I don't see a single reason behind the service impl being dependent
>>> on the web services engine being used. So thats why we didn't wanna
>>> define a contract for the service implementor to implement.
>> Sorry Chintaka, but I think I miss something here. Why does implementing
>> an Axis2 interface makes your service more implementation dependent than
>> adding a method that receives an Axis2 parameter?
>>
>> Once you need to pass an OperationContext instance you are
>> implementation dependent, aren't you?.
> 
> Yes, that will happen iff you, as the service author, wanna get some
> information from the Axis2 environment.
> But, if you wanna deploy a simple service which does an xslt
> transformation on the recd xml, you don't wanna know what is happening
> in Axis2. Isn't it?
> 
> -- Chinthaka
> 
> 

-- 
---
GRIDSYSTEMSRodrigo Ruiz Aguayo
Parc Bit - Son Espanyol
07120 Palma de Mallorcamailto:[EMAIL PROTECTED]
Baleares - España  Tel:+34-971435085 Fax:+34-971435082
http://www.gridsystems.com
---


-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.10.0/388 - Release Date: 13/07/2006


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

AW: AW: How to access the SOAPHeader

[Haug, Thomas]

Hi Chinthaka, hi Rodrigo,

1)
As Rodrigo has pointed out there is already an dependency of the service class 
to Axis2 because of the OperationContext class in the setOperationContext() 
method, if you need to access the framework. So having therefore an explicit 
interface does not hurt anyfurther.

2) 
Inversion of control is one of the pillars of framework design and using 
abstract classes and/or interfaces to define the (static) contract for the 
framework adaptation (how to plugin into the framework) is commonly used (see 
Building Applications Frameworks by Fayad et al). Maybe there are now 
tendencies to have more 'implicit contracts'. But I am not sure if I like that 
because in my opinon it is more complex to understand and to remember if you 
have to alter the service class months later and don't remember the 'magic' 
anymore.

So my suggestion whould be to use an approach as it has been realized in the 
Apache Avalon component model: there is an set of optional interfaces which can 
be used if a component wants to get some dedicated data from the framework or 
participate in a special 'interaction'. So for the Axis2 toolkit this would 
mean: the vast majority of the sercie classes would have no dependency on the 
framework. If a service class has the requirement to access some specific data 
(like the SOAPHeader), then it can implement the corresponding interface, thus 
making the contract explicit. If the axis2 detects that the service class 
realizes some of these optional interfaces than it calls the approriate methods 
at the required time. This is in my opinon more simple to understand asnd 
therefore easier to maintain.

As usual, only my(!!) thoughts on this ;-)

Regards,
Thomas 

-Ursprüngliche Nachricht-
Von: Eran Chinthaka [mailto:[EMAIL PROTECTED] 
Gesendet: Freitag, 14. Juli 2006 13:47
An: axis-user@ws.apache.org
Betreff: Re: AW: How to access the SOAPHeader

Hi Rodrigu,

Rodrigo Ruiz wrote:
> 
> Eran Chinthaka wrote:
>> We didn't want to put any restriction on a user who wanna write a simple
>> java class and expose that as a web service. Thats been the case so far.
>> I hope you can understand that it will make the most common and simple
>> case simple.
>> And I don't see a single reason behind the service impl being dependent
>> on the web services engine being used. So thats why we didn't wanna
>> define a contract for the service implementor to implement.
> 
> Sorry Chintaka, but I think I miss something here. Why does implementing
> an Axis2 interface makes your service more implementation dependent than
> adding a method that receives an Axis2 parameter?
> 
> Once you need to pass an OperationContext instance you are
> implementation dependent, aren't you?.

Yes, that will happen iff you, as the service author, wanna get some
information from the Axis2 environment.
But, if you wanna deploy a simple service which does an xslt
transformation on the recd xml, you don't wanna know what is happening
in Axis2. Isn't it?

-- Chinthaka



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

Re: [Axis2] Reliable Notification

[Chamikara Jayalath]

Hi Eric,

Please see my comments below.On 7/12/06, Eric Winter <[EMAIL PROTECTED]> wrote:
Reliable NotificationI have a pretty simple problem I'd like to solve, but the tool I thinkI should use is not being cooperative.I have a client that has to deliver a message to at least one server
within a reasonable time.Based on that requirement I though I should use MEP InOnly andSandesha2 (Reliable Messaging).  The problem is that I need to knowthat the message arrived and I can't seem to get that using Sandesha
and the InOnly pattern. All I really want from the service is an ACKthat I can pick up somehow at the client.  Clearly this is part andparcel of what Sandesha does... I just want to know about it.


Acknowledgements are handled  inside Sandesha2 and they are not
delivered to the client.  Sandesha2 will retransmit messages
until  a ack is received or till the message sequence times out.
A couple of thoughts came up:1. Manually check via the SequenceReport. (never see anything in the
Outgoing Sequence Report)
After you your messages get successfully delivered the the server and
after the Sandesha2 client receive acknowledgements you should hv those
message numbers in the outgoing sequence report. Dont you see these
values? What are the velues of the other properties of the Sequence
Report (for e.g. Sequece Status).
 2. Use a SandeshaListener (callbacks for onError and onTimeout).  Itried running client w/ server down. No luck.


This will not help ur scenario. You can only use this to know when your sequence times out.
 3. SandeshaClient.waitUntilSequenceCompleted works but who wants toblock?  And if it does time out I still want to be notified.


yes. This will only help if blocking is ok.

None of these fullfill the basic requirement: within a reasonableabout of time, I want to know, at the client, that the message has
been received at the service.FYI I am using the Sandesha2 UserguideEchoClient client - the code w/ myadditions are here.clientOptions.setTo(new EndpointReference (toEPR));ServiceClient serviceClient = new ServiceClient
(configContext,null);clientOptions.setAction("urn:wsrm:Ping");serviceClient.setOptions(clientOptions); clientOptions.setProperty(SandeshaClientConstants.SANDESHA_LISTENER,
new SandeshaListener_Impl());//newclientOptions.setTimeOutInMilliSeconds(1);//trying to cause itto timeout, but it doesn't.serviceClient.fireAndForget(getPingOMBlock("ping1"));
serviceClient.fireAndForget(getPingOMBlock("ping2"));clientOptions.setProperty(SandeshaClientConstants.LAST_MESSAGE,"true");serviceClient.fireAndForget(getPingOMBlock("ping3"));
 SandeshaClient.waitUntilSequenceCompleted(serviceClient,1000*50);//newserviceClient.finalizeInvoke();


My sugestion for you for now is to use the sequence report. May be from
a seperate thread. But a better way will be to have a method in the
SandeshaClient to notify the client when a specific message get
successfully delivered. I'll mark this as a improvement :-)

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

Re: AW: How to access the SOAPHeader

[Eran Chinthaka]

Hi Rodrigu,

Rodrigo Ruiz wrote:
> 
> Eran Chinthaka wrote:
>> We didn't want to put any restriction on a user who wanna write a simple
>> java class and expose that as a web service. Thats been the case so far.
>> I hope you can understand that it will make the most common and simple
>> case simple.
>> And I don't see a single reason behind the service impl being dependent
>> on the web services engine being used. So thats why we didn't wanna
>> define a contract for the service implementor to implement.
> 
> Sorry Chintaka, but I think I miss something here. Why does implementing
> an Axis2 interface makes your service more implementation dependent than
> adding a method that receives an Axis2 parameter?
> 
> Once you need to pass an OperationContext instance you are
> implementation dependent, aren't you?.

Yes, that will happen iff you, as the service author, wanna get some
information from the Axis2 environment.
But, if you wanna deploy a simple service which does an xslt
transformation on the recd xml, you don't wanna know what is happening
in Axis2. Isn't it?

-- Chinthaka




signature.asc
Description: OpenPGP digital signature

RE: problem in invoke the webservice using REST Style by client program

[Kinichiro Inoguchi]

Hi, Vimal.

Could you try latest nightly build axis2.war in server side, please ?


--- "Bansal, Vimal" <[EMAIL PROTECTED]> wrote:

> Hi kinichiro,
>   as per my earlier mail I am getting the access for my service using
> following url by browser
>   http://localhost:8080/Axis2/rest/servicename/methodname?param0=23
>   output is:-
>  - http://org.apache.axis2/xsd";>
>   hfdj 
>   dfds 
>   Andrews 
>   pvcv 
>   21 
>   
> this is nice .
> now I am writing the client program for same my code snippets is
> following:
> 
>   public class  RestClient
> {
> private static EndpointReference targetEPR = new
>
EndpointReference("http://localhost:8080/Axis2/rest/servicename/methodname?param0=34";);
> 
> public static void main(String[] args) {
> try {
> 
> 
> //ServiceClient sender = null;
> RESTCall call = new RESTCall();
> Options options = new Options();
> options.setTo(targetEPR);
> options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
> options.setProperty(Constants.Configuration.ENABLE_REST,
> Constants.VALUE_TRUE);
>
>
options.setProperty(Constants.Configuration.HTTP_METHOD,Constants.Configuration.HTTP_METHOD_GET);
> call.setOptions(options);
> System.out.println("$$$ B4 sendReceive ... $$$ ");
> OMElement result= call.sendReceive();
> System.out.println("$$$ After sendReceive ... ");
> System.out.println(result.getFirstElement().getText());
>   }
> catch (AxisFault axisFault) {
> 
> System.out.println(axisFault+":"+axisFault.getMessage());
>  }
> catch (Exception axisFault) {
> 
> System.out.println(axisFault+":"+axisFault.getMessage());
> }
> }
>but i am not getting output I am getting following error message
> at dos prompt.
>org.apache.axis2.AxisFault: Incoming message input stream is
> null:Incoming message input stream is null
>what I am missing.url is same for both cases.
>   Thanks 
> Vimal Bansal
> 
> -Original Message-
> From: Bansal, Vimal [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 14, 2006 9:32 AM
> To: axis-user@ws.apache.org
> Subject: RE: problem to invoke the webservice using REST Style
> 
> 
> Hi kinichiro,
>  Thanks for your response, now problem is fix and i am getting the
> expected output.one can use RPCMessageReceiver for any 
>  cases,the men thing is that i realize one shoud have only one method
> define in your service class,in case of more than one   
>  method you would'nt get the excees of all the method.
>  you can access your method via following url:-
>  http://localhost:8080/Axis2/rest/servicename/methodname?paramo=23
>  remember parameter other than param0 in url is not allowed.
>  thanks
>  Vimal Bansal.
> 
> 
> -Original Message-
> From: Kinichiro Inoguchi [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 13, 2006 10:26 AM
> To: axis-user@ws.apache.org
> Subject: RE: problem to invoke the webservice using REST Style
> 
> 
> Hi Bansal,
> 
> Test class is like this.
> 
> package test;
> public class MyService1 {
> public void ping(int element) {
>   System.out.println("value of input value = "+ element);
> }
> 
> public int echo(int element) {
> return element * element;
> }
> }
> 
> services.xml is like this.
> 
> test service.
>  locked="false">test.MyService1
> 
>  class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver"/>
> 
> 
>  class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
> 
> 
> 
> You can call this by REST.
> http://localhost:8080/axis2/rest/MyService1/ping?element=15
> 
> I could see this log message in tomcat stdout.log
> value of input value = 15
> 
> It worked fine.
> 
> Regards,
> kinichiro
> 
> --- "Bansal, Vimal" <[EMAIL PROTECTED]> wrote:
> 
> > Hi kinichiro,
> >  I have tried for this also but problem is same. can you check the
> > link below,
> > 
> >
>
http://ws.apache.org/axis2/0_95/api/org/apache/axis2/rpc/receivers/class-use/RPCInOnlyMessageReceiver.html
> > 
> > in this it is clearly mention that there is no use of
> > RpcInOnlyMessageReceiver.finding the method in service may be the
> > problem.
> > http://localhost:8080/axis2/rest/ServiceName/setData?num=10
> > can you send me the running sample code including
> service.xml,client
> > and service if you have.
> > Thanks
> > Vimal Bansal. 
> > 
> > -Original Message-
> > From: Kinichiro Inoguchi [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, July 12, 2006 7:32 PM
> > To: axis-user@ws.apache.org
> > Subject: RE: problem to invoke the webservice using RESTt Style
> > 
> > 
> > Hi Bansal,
> > 
> > You must use RPCInOnlyMessageReceiver instead of
> RPCMessageReceiver,
> > because your method is void.
> > 
> > Regards,
> > kinichiro
> > 
> > --- "Bansal, Vimal" <[EMAIL PROTECTED]> wrote:
> > 
> > > Hi kinichiro,
> > > Thanks again, tried my all st

RE: problem in invoke the webservice using REST Style by client program

[Bansal, Vimal]

Hi kinichiro,
  as per my earlier mail I am getting the access for my service using following 
url by browser
  http://localhost:8080/Axis2/rest/servicename/methodname?param0=23
  output is:-
 - http://org.apache.axis2/xsd";>
  hfdj 
  dfds 
  Andrews 
  pvcv 
  21 
  
this is nice .
now I am writing the client program for same my code snippets is following:

  public class  RestClient
{
private static EndpointReference targetEPR = new 
EndpointReference("http://localhost:8080/Axis2/rest/servicename/methodname?param0=34";);

public static void main(String[] args) {
try {


//ServiceClient sender = null;
RESTCall call = new RESTCall();
Options options = new Options();
options.setTo(targetEPR);
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
options.setProperty(Constants.Configuration.ENABLE_REST, 
Constants.VALUE_TRUE);

options.setProperty(Constants.Configuration.HTTP_METHOD,Constants.Configuration.HTTP_METHOD_GET);
call.setOptions(options);
System.out.println("$$$ B4 sendReceive ... $$$ ");
OMElement result= call.sendReceive();
System.out.println("$$$ After sendReceive ... ");
System.out.println(result.getFirstElement().getText());
  }
catch (AxisFault axisFault) {
 System.out.println(axisFault+":"+axisFault.getMessage());
 }
  catch (Exception axisFault) {
 System.out.println(axisFault+":"+axisFault.getMessage());
}
}
   but i am not getting output I am getting following error message at dos 
prompt.
   org.apache.axis2.AxisFault: Incoming message input stream is null:Incoming 
message input stream is null
   what I am missing.url is same for both cases.
  Thanks 
Vimal Bansal

-Original Message-
From: Bansal, Vimal [mailto:[EMAIL PROTECTED]
Sent: Friday, July 14, 2006 9:32 AM
To: axis-user@ws.apache.org
Subject: RE: problem to invoke the webservice using REST Style


Hi kinichiro,
 Thanks for your response, now problem is fix and i am getting the expected 
output.one can use RPCMessageReceiver for any 
 cases,the men thing is that i realize one shoud have only one method define in 
your service class,in case of more than one   
 method you would'nt get the excees of all the method.
 you can access your method via following url:-
 http://localhost:8080/Axis2/rest/servicename/methodname?paramo=23
 remember parameter other than param0 in url is not allowed.
 thanks
 Vimal Bansal.


-Original Message-
From: Kinichiro Inoguchi [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 13, 2006 10:26 AM
To: axis-user@ws.apache.org
Subject: RE: problem to invoke the webservice using REST Style


Hi Bansal,

Test class is like this.

package test;
public class MyService1 {
public void ping(int element) {
System.out.println("value of input value = "+ element);
}

public int echo(int element) {
return element * element;
}
}

services.xml is like this.

test service.
test.MyService1








You can call this by REST.
http://localhost:8080/axis2/rest/MyService1/ping?element=15

I could see this log message in tomcat stdout.log
value of input value = 15

It worked fine.

Regards,
kinichiro

--- "Bansal, Vimal" <[EMAIL PROTECTED]> wrote:

> Hi kinichiro,
>  I have tried for this also but problem is same. can you check the
> link below,
> 
>
http://ws.apache.org/axis2/0_95/api/org/apache/axis2/rpc/receivers/class-use/RPCInOnlyMessageReceiver.html
> 
> in this it is clearly mention that there is no use of
> RpcInOnlyMessageReceiver.finding the method in service may be the
> problem.
> http://localhost:8080/axis2/rest/ServiceName/setData?num=10
> can you send me the running sample code including service.xml,client
> and service if you have.
> Thanks
> Vimal Bansal. 
> 
> -Original Message-
> From: Kinichiro Inoguchi [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 12, 2006 7:32 PM
> To: axis-user@ws.apache.org
> Subject: RE: problem to invoke the webservice using RESTt Style
> 
> 
> Hi Bansal,
> 
> You must use RPCInOnlyMessageReceiver instead of RPCMessageReceiver,
> because your method is void.
> 
> Regards,
> kinichiro
> 
> --- "Bansal, Vimal" <[EMAIL PROTECTED]> wrote:
> 
> > Hi kinichiro,
> > Thanks again, tried my all stuff now I have just created one method
> > in my service Say setdata(in num) my code snippets is below just
> for
> > testing purpose
> >   
> >public void setData(int num)  {
> > System.out.println("Entry in setData");
> > System.out.println("value of num ="+ num);
> > System.out.println("Exit from setData");
> > }
> >  and i am passing parameter via REST like this,
> > http://localhost:8080/axis2/rest/ServiceName/setData?num=10
> > but i have the same problem i am not getting access of setdata()
> > method.
> > i have also c

Re: AW: How to access the SOAPHeader

[Rodrigo Ruiz]

Eran Chinthaka wrote:
> We didn't want to put any restriction on a user who wanna write a simple
> java class and expose that as a web service. Thats been the case so far.
> I hope you can understand that it will make the most common and simple
> case simple.
> And I don't see a single reason behind the service impl being dependent
> on the web services engine being used. So thats why we didn't wanna
> define a contract for the service implementor to implement.

Sorry Chintaka, but I think I miss something here. Why does implementing
an Axis2 interface makes your service more implementation dependent than
adding a method that receives an Axis2 parameter?

Once you need to pass an OperationContext instance you are
implementation dependent, aren't you?.

Regards,
Rodrigo Ruiz

-- 
---
GRIDSYSTEMSRodrigo Ruiz Aguayo
Parc Bit - Son Espanyol
07120 Palma de Mallorcamailto:[EMAIL PROTECTED]
Baleares - España  Tel:+34-971435085 Fax:+34-971435082
http://www.gridsystems.com
---



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

Re: AW: How to access the SOAPHeader

[Eran Chinthaka]

Hi Thomas,

Haug, Thomas wrote:
> Hi Chinthaka,
> 
> Thank you for the quick answer.
> So if I got it right: the Axis2 framework inspects the service class (via 
> reflection?), if the service class provides a  
> setOperationContext(OperationContext opContext) method. Are there any other 
> operation which can be 'magically' called ?
> 
>>From a design perspective this looks a bit awkward, because there is no 
>>interface which mandates that my service class has to implement the 
>>corresponding method(s). Instead the contract between my class and Axis2 is 
>>done implicitly and I have to mention it at least at 'JavaDoc level' 
>>otherwise nobody of my developers whould know. I would rather like to see an 
>>approach similar as in Axis 1 (which is similar to the CORBA Current object 
>>approach).But this is only my opinion ... ;-)

Good point. Let me ask explain a bit on this and ask a question from
you. I'd like to see your approach to this problem.

We didn't want to put any restriction on a user who wanna write a simple
java class and expose that as a web service. Thats been the case so far.
I hope you can understand that it will make the most common and simple
case simple.
And I don't see a single reason behind the service impl being dependent
on the web services engine being used. So thats why we didn't wanna
define a contract for the service implementor to implement.

But at the same time, there are situations where the service author
needs to get some information from the framework. That needs the
framework requires a method in the service to invoke.
Our approach to this was to use IOC concepts as used heavily in
Geronimo. So thats why through a dependency manager, we have a mechanism
to inject operation context to the service implementation class.

IMO, this is the ideal compromise we can get to make the simple case
simple and get to other cases also work.

If you have any other approach for this problem, we are happy to hear that.

Note : this dependency injection will happen iff, you use an in-built
message receiver that comes with Axis2. That won't work with the
generated or custom message receivers.



> 
> Nevertheless, thanks for the hint. At least I am now able to get the 
> SOAPHeader.

np.

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Exception after correct sending message with fireAndForget()

[Deepal Jayasinghe]

Hi ;


[EMAIL PROTECTED] wrote:

>Hi,
>
>senden a message using fireAndForget(), the message was delivered properly but 
>there is allways this exception wich occours:
>
>  
>
I doubt , how can it deliver the message with following exception, btw
can you please help me to regenerate the problem.

>INFO: Axis2 transport error : No Host matches server name 127.0.0.1; nested 
>exception is:
>org.apache.axis2.AxisFault: Axis2 transport error : No Host matches 
> server name 127.0.0.1; nested exception is:
>org.apache.axis2.AxisFault: Axis2 transport error : No Host matches 
> server name 127.0.0.1; nested exception is:
>org.apache.axis2.AxisFault: Axis2 transport error : No Host matches 
> server name 127.0.0.1
>
>
>Is this a normal behavior (cause it is published using a log.info level)?
>
>
>Thanks Ted
>
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>  
>

-- 
Thanks,
Deepal

~Future is Open~ 



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

AW: How to access the SOAPHeader

[Haug, Thomas]

Hi Chinthaka,

Thank you for the quick answer.
So if I got it right: the Axis2 framework inspects the service class (via 
reflection?), if the service class provides a  
setOperationContext(OperationContext opContext) method. Are there any other 
operation which can be 'magically' called ?

>From a design perspective this looks a bit awkward, because there is no 
>interface which mandates that my service class has to implement the 
>corresponding method(s). Instead the contract between my class and Axis2 is 
>done implicitly and I have to mention it at least at 'JavaDoc level' otherwise 
>nobody of my developers whould know. I would rather like to see an approach 
>similar as in Axis 1 (which is similar to the CORBA Current object 
>approach).But this is only my opinion ... ;-)

Nevertheless, thanks for the hint. At least I am now able to get the SOAPHeader.

Cheers,
Thomas


-Ursprüngliche Nachricht-
Von: Eran Chinthaka [mailto:[EMAIL PROTECTED] 
Gesendet: Freitag, 14. Juli 2006 11:53
An: axis-user@ws.apache.org
Betreff: Re: How to access the SOAPHeader

First get access to the message context within the service
implementation class following this (http://www.wso2.net/kb/106).

Then from the message context you can get access to the soap envelope
using msgCtxt.getEnvelope()

-- Chinthaka

Haug, Thomas wrote:
> 
> 
> Hi,
> 
> I want to access the SOAPHeader in my service implementation class.
> In Axis 1 I have done soemthing like
>SOAPHeader header = null;
> 
>//extract the Header from the current SOAP Request
>try {
>  header = (SOAPHeader)
> MessageContext.getCurrentContext().getRequestMessage().getSOAPEnvelope().getHeader();
> 
>}
>catch (SOAPException e) {
>  //do what ever
>}
> Is there a similar mechanism in Axis2. I have not found a glue so far.
> Thanks,
> Thomas
> 



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

Re: How to access the SOAPHeader

[Eran Chinthaka]

First get access to the message context within the service
implementation class following this (http://www.wso2.net/kb/106).

Then from the message context you can get access to the soap envelope
using msgCtxt.getEnvelope()

-- Chinthaka

Haug, Thomas wrote:
> 
> 
> Hi,
> 
> I want to access the SOAPHeader in my service implementation class.
> In Axis 1 I have done soemthing like
>SOAPHeader header = null;
> 
>//extract the Header from the current SOAP Request
>try {
>  header = (SOAPHeader)
> MessageContext.getCurrentContext().getRequestMessage().getSOAPEnvelope().getHeader();
> 
>}
>catch (SOAPException e) {
>  //do what ever
>}
> Is there a similar mechanism in Axis2. I have not found a glue so far.
> Thanks,
> Thomas
> 




signature.asc
Description: OpenPGP digital signature

How to access the SOAPHeader

[Haug, Thomas]

Title: How to access the SOAPHeader






Hi,


I want to access the SOAPHeader in my service implementation class.

In Axis 1 I have done soemthing like 

   SOAPHeader header = null;

   //extract the Header from the current SOAP Request
   try {
 header = (SOAPHeader) MessageContext.getCurrentContext().getRequestMessage().getSOAPEnvelope().getHeader(); 

   }
   catch (SOAPException e) {
 //do what ever
   } 

Is there a similar mechanism in Axis2. I have not found a glue so far.

Thanks,

Thomas

RE: [Axis2] MessageContext w/o any properties

[Rishikesh . Mallesh]

Hi 

Could anybody tell me how do I get the HTTPServletRequest object in Axis
1.3?

Thanks!

-Original Message-
From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED] 
Sent: 13 July 2006 17:25
To: axis-user@ws.apache.org
Subject: Re: [Axis2] MessageContext w/o any properties

Hi Heikki;

I am sorry for my mistake , I thought that you are invoking service
using http post ,
there was a problem in http get and I fixed that in current code base ,
so you will be able to get the HttpServlet Request  using

httpServletRequest = (HttpServletRequest)
msgContext.getProperty(Constants.HTTP_SERVLET_REQUEST );

if you use either nightly builds or current svn code .

heikki wrote:

> thanks for the tips, alas I'm still not getting the HttpServlet Request ..
>
> I tried, in the handler :
>
> 1. Deepal's tip :
>
> httpServletRequest = (HttpServletRequest)
> msgContext.getProperty(Constants.HTTP_SERVLET_REQUEST );
>
> 2. Robert's tip :
>
> httpServletRequest = (HttpServletRequest)
>
msgContext.getOperationContext().getProperty(HTTPConstants.MC_HTTP_SERVLETRE
QUEST);
>
> 3. those two combined :
>
> httpServletRequest = (HttpServletRequest)
>
msgContext.getOperationContext().getProperty(Constants.HTTP_SERVLET_REQUEST)
;
>
> In each case, I don't find the HttpServletContext, instead ending up
> with null.
>
> This being so, I do not fully understand this remark from Robert's post :
>
>
> "Its by design- you have to get the operation context from the outgoing
> MC and then get the incoming MC from that and look there for the servlet
> context and any other "incoming" info. "
>
> My handler is used to process incoming messages; how could I get
> things from outgoing MC at this stage ? Could you explain what is
> meant here?
>
> Does anyone have more advice on how I could obtain the
> HttpServletContext in a handler that operates on incoming messages?
> Surely this should be a quite easy task ..
>
> thank you and regards,
> Heikki Doeleman
>
>
>
>
>
>
>
> On 7/13/06, *Carsten Ziegeler* <[EMAIL PROTECTED]
> > wrote:
>
> This is a bug in the MessageContext which has been discussed
> recently on
> the dev list. The getProperties() method of the MessageContext always
> returns an empty map. So you can only get those properties you
> know the
> key of by calling getProperty(key).
>
> Carsten
>
> Deepal Jayasinghe wrote:
> > You need to call
> > msgCtx.getProperty(Constants.HTTP_SERVLET_REQUEST);
> >
> > heikki wrote:
> >
> >> Hi there,
> >>
> >> I'm trying to retrieve the HttpServletRequest in a handler,
> through
> >> its MessageContext, like so
> >>
> >> HttpServletRequest httpServletRequest = (HttpServletRequest)
> >> msgContext.getProperty(HTTPConstants.MC_HTTP_SERVLETREQUEST );
> >>
> >> However, running this,  httpServletRequest was null. On further
> >> examination I looked at all the properties I could get from
> >> MessageContext, using this code
> >>
> >> Map propsMap = msgContext.getProperties();
> >> if(propsMap.size () == 0) {
> >> System.out.println("msgContext props map is empty
> !!!  ");
> >> }
> >> Set propsSet = props.entrySet();
> >> if(propsSet.size() == 0) {
> >> System.out.println("msgContext props set is empty
> !!!  ");
> >> }
> >>
> >> which put out this
> >>
> >> msgContext props map is empty !!!
> >> msgContext props set is empty !!!
> >>
> >> Apparently, I don't have any property in the MessageContext in the
> >> handler. Is this usual? Should I take some extra step somewhere
> along
> >> the line?
> >>
> >> My purpose of getting HttpServletRequest is to retrieve URL params
> >> from the HTTP GET request. Is there another way to do achieve this?
> >>
> >>
> >> thanks and regards,
> >> Heikki Doeleman
> >
> >
>
>
> --
> Carsten Ziegeler - Open Source Group, S&N AG
> http://www.s-und-n.de
> http://www.osoco.org/weblogs/rael/
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> 
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>
>

-- 
Thanks,
Deepal

~Future is Open~ 




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



This message is intended for the addressee or its representative only. 
Any form of unauthorized use, publication, reproduction, copying or 
disclosure of the content of this e-mail is not permitted. If you are 
not the intended recip

Re: [axis2] Setting realtesTo() leads to Exception while sending

[Eran Chinthaka]

hi,

I just ran your code and found a bug in our addressing code. I fixed it
and now I got the code working.

Can you test it now?

-- Chinthaka

[EMAIL PROTECTED] wrote:
> Hi,
> 
> I already posted this problem a week ago, but cause it still exists I try it 
> with some more detail I figured out up till now.
> 
> The problem is, using fireAndForget to send some Data from one Service to an 
> other and setting WSA relatesTo at the ServiceClients options, no xml content 
> is send. The Exception wich is throws from out of the system is ... not very 
> helpfull but here it is:
> 
> - Servlet.service() for servlet AxisServlet threw exception
> org.apache.axiom.om.OMException: SOAPEnvelope must contain a body element 
> which is either first or second child element of the SOAPEnvelope.
> at 
> org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getBody(SOAPEnvelope 
> Impl.java:142)
> at 
> org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.addChild(SOAPEnvelopeImpl.java:103)
> at 
> org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeImpl.java:82)
> at 
> org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngine.java:183)
> at 
> org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:168)
> at 
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:153)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
> 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.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
> at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
> 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:869)
> at 
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
> at 
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
> at 
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
> at 
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
> at java.lang.Thread.run(Thread.java:595)
> - Servlet.service() for servlet jsp threw exception
> java.lang.IllegalStateException: getOutputStream() has already been called 
> for this response
> at org.apache.catalina.connector.Response.getWriter(Response.java:599)
> at 
> org.apache.catalina.connector.ResponseFacade.getWriter(ResponseFacade.java:195)
> at 
> org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:124)
> at 
> org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:117)
> at 
> org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java:191)
> at 
> org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspFactoryImpl.java:115)
> at 
> org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(JspFactoryImpl.java:75)
> at 
> org.apache.jsp.axis2_002dweb.Error.error500_jsp._jspService(error500_jsp.java:97)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at 
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332)
> at 
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> at 
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
> at 
> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:465)
> at 
> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398)
> at 
> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
> at 
> org.apache.catalina.core.Standard