date:20060317

In really, I did two changes before get my axis copy buiding:1) turn off Norton Worm Protection2) applied the recomendation for users of JDK 1.5 (http://ws.apache.org/axis2/faq.html
)What is your java version?LorenoOn 3/17/06, Sean Doyle (Gmail) <[EMAIL PROTECTED]
> wrote:Loreno Oliveira wrote:> I got also problems with some tests, just like Sean and Bruno.
> My problem was fixed when I turned off the Norton Worm Protection...No such luck here - I've turned off my Trend Micro, ran svn update, andstill see errors.After>[junit] [ERROR] TEST 
org.apache.axis2.rpc.RPCCallTest FAILED>[junit] Running org.apache.axis2.security.AddressingMTOMSecurityTestyou see> BUILD FAILED> File.. C:\Documents and> Settings\sean\.maven\cache\maven-
multiproject-plugin-1.3.1\plugin.jelly> Element... maven:reactor> Line.. 217> Column 9> Unable to obtain goal [multiproject:install-callback] -- C:\Documents> and Settings\sean\.maven\cache\maven-test-plugin-1
> .6.2\plugin.jelly:181:54:  There were test failures.> Total time: 20 minutes 39 seconds> Finished at: Fri Mar 17 15:25:25 EST 2006This was in response to a 'maven release'.
>> Now I'm building and testing axis2 fine...>> Loreno>> On 3/16/06, *Eran Chinthaka* <[EMAIL PROTECTED]> 
[EMAIL PROTECTED]>> wrote:>> Hi Sean and Bruno,>> We experience a build failure in Axis2 main branch now. Please give us> time till tomoro for us to fix it.
>> Thanks,> Chinthaka>> Sean Doyle (Gmail) wrote:> > bruno wanadoo wrote:> >> >> Hi Chinthaka & everybody else> >>
> >> I followed instructions in the FAQ ( with jdk1.5 I modify the> >> security file to add BC as provider)> >> But when I launch maven , a lot of targets are built but at the
> end I> >> got this> >>> > I'm getting the same> >Unable to obtain goal [multiproject:install-callback] --> > C:\Documents and
> >> Settings\bruno\.maven\cache\maven-test-plugin-1.6.2\plugin.jelly:181:54:>> > I've also put in the same attribute for BC. And svn is current> as of a> > few minutes ago.
> >> > Here's what works and doesn't work - I'm a bit confused by the> site's> > documentation since it has two different calls to maven> specified for> > building the project. One fails with the 
plugin.jelly message, the> > other works but doesn't make the war file.> >> > I'm running this in WindowsXP. My version of Maven is 1.0.2. My> > version of Java is java version " 
1.5.0_06".> >> >> > According to http://ws.apache.org/axis2/svn.html - you just type> > 'maven'. This fails -
> >> >> test:test:> >> [junit] Running org.apache.axis2.om.impl.dom.DocumentImplTest> >> [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed:
> 0.39 sec> >> [junit] Running> org.apache.axis2.om.impl.dom.DOMImplementationTest> >> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed:> 0.28
 sec> >> [junit] Running org.apache.axis2.om.impl.dom.ElementImplTest> >> [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed:> 0.381> >> sec
> >> [junit] Running org.apache.axis2.om.impl.dom.MessagesTest> >> [junit] Tests run: 4, Failures: 0, Errors: 4, Time elapsed:> 0.471> >> sec> >> *[junit] [ERROR] TEST 
org.apache.axis2.om.impl.dom.MessagesTest> >> FAILED*> >> [junit] Running org.apache.axis2.om.impl.dom.OMDOMFactoryTest> >> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed:
> 0.281> >> sec> >> [junit] Running org.apache.axis2.om.impl.dom.TextImplTest> >> [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed:> 
0.28 sec> >>> >> BUILD FAILED> >> File.. C:\Documents and> >>> Settings\sean\.maven\cache\maven-multiproject-plugin-1.3.1\plugin.jelly
>> >> Element... maven:reactor> >> Line.. 217> >> Column 9> >> Unable to obtain goal [multiproject:install-callback] --> C:\Documents
> >> and Settings\sean\.maven\cache\maven-test-plugin-1> >> .6.2\plugin.jelly:181:54:  There were test failures.> >> Total time: 4 minutes 9 seconds> >> Finished at: Thu Mar 16 10:22:34 EST 2006
> >> >> > According to http://ws.apache.org/axis2/siteHowTo.html - you type> > 'maven multiproject'. This worked yesterday - but it didn't make the
> > war file. And - although it worked there are several errors of> the sort:> >> >> Error retrieving artifact from> >>> [
http://www.ibiblio.org/maven/axis2/jars/axis2-codegen-0.95-SNAPSHOT.jar]:> >> java.net.Conne> >> ctException: Connection timed out: connect> >> 192K downloaded> >
> >> >> > Somewhere on the apache site there was a suggestion to use> 'maven.war'> > - this failed with (I believe) the same plugin.jelly error.> >
> > Also - I've been running 'maven clean' between runs

RE: Problems in accessing the sample service in Axis2

2006-03-17 Thread Kashif Saleem

Hi again,
 I installed an axis2.0.93 rather than 2.0.94.
Kind Regards
Kashif Saleem


-Original Message-
From: robert [mailto:[EMAIL PROTECTED]
Sent: Fri 17/03/2006 18:57
To: axis-user@ws.apache.org
Subject: Re: Problems in accessing the sample service in Axis2
 
Did you follow the instructions in yellow on the dowload page? 

http://ws.apache.org/axis2/download.cgi

HTH,
Robert
http://www.braziloutsource.com/

Em Sexta 17 Março 2006 15:25, o Kashif Saleem escreveu:
> Hi All,
>I deployed the service Axis2SampleDocLitPortType successfully as
> mentioned in the use-guide.But when I tried to access this service  through
> client I got the following exceptions.I would appreciate if someone could
> tell me the cause of this error.Below is the output that I got after
> running the client:
>
> [EMAIL PROTECTED]:~/Desktop/softwares/axis2-0.93-bin/samples/src$ java
> -classpath $CLASSPATH org/apache/axis2/userguide/TestClient - Module
> validation failed  org.apache.axis.handlers.addressing.AddressingInHandler;
> nested exception is: org.apache.axis2.AxisFault:
> org.apache.axis.handlers.addressing.AddressingInHandler
> org.apache.axis2.deployment.DeploymentException:
> org.apache.axis.handlers.addressing.AddressingInHandler; nested exception
> is: org.apache.axis2.AxisFault:
> org.apache.axis.handlers.addressing.AddressingInHandler; nested exception
> is: org.apache.axis2.deployment.DeploymentException:
> org.apache.axis.handlers.addressing.AddressingInHandler; nested exception
> is: org.apache.axis2.AxisFault:
> org.apache.axis.handlers.addressing.AddressingInHandler; nested exception
> is: org.apache.axis2.deployment.DeploymentException:
> org.apache.axis.handlers.addressing.AddressingInHandler; nested exception
> is: org.apache.axis2.AxisFault:
> org.apache.axis.handlers.addressing.AddressingInHandler; nested exception
> is: org.apache.axis2.deployment.DeploymentException:
> org.apache.axis.handlers.addressing.AddressingInHandler; nested exception
> is: org.apache.axis2.AxisFault:
> org.apache.axis.handlers.addressing.AddressingInHandler at
> org.apache.axis2.context.ConfigurationContextFactory.buildClientConfigurati
>onContext(ConfigurationContextFactory.java:68) at
> org.apache.axis2.userguide.Axis2SampleDocLitPortTypeStub.(Axis2Sample
>DocLitPortTypeStub.java:53) at
> org.apache.axis2.userguide.TestClient.foo(TestClient.java:35) at
> org.apache.axis2.userguide.TestClient.main(TestClient.java:21) Caused by:
> org.apache.axis2.deployment.DeploymentException:
> org.apache.axis.handlers.addressing.AddressingInHandler; nested exception
> is: org.apache.axis2.AxisFault:
> org.apache.axis.handlers.addressing.AddressingInHandler; nested exception
> is: org.apache.axis2.deployment.DeploymentException:
> org.apache.axis.handlers.addressing.AddressingInHandler; nested exception
> is: org.apache.axis2.AxisFault:
> org.apache.axis.handlers.addressing.AddressingInHandler at
> org.apache.axis2.deployment.DeploymentEngine.loadClient(DeploymentEngine.ja
>va:272) at
> org.apache.axis2.context.ConfigurationContextFactory.buildClientConfigurati
>onContext(ConfigurationContextFactory.java:60) ... 3 more
> Caused by: org.apache.axis2.deployment.DeploymentException:
> org.apache.axis.handlers.addressing.AddressingInHandler; nested exception
> is: org.apache.axis2.AxisFault:
> org.apache.axis.handlers.addressing.AddressingInHandler at
> org.apache.axis2.deployment.DeploymentEngine.buildModule(DeploymentEngine.j
>ava:743) at
> org.apache.axis2.engine.AxisConfiguration.engageModule(AxisConfiguration.ja
>va:433) at
> org.apache.axis2.deployment.DeploymentEngine.engageModules(DeploymentEngine
>.java:329) at
> org.apache.axis2.deployment.DeploymentEngine.loadClient(DeploymentEngine.ja
>va:269) ... 4 more
> Caused by: org.apache.axis2.AxisFault:
> org.apache.axis.handlers.addressing.AddressingInHandler at
> org.apache.axis2.deployment.util.Utils.getHandlerClass(Utils.java:136) at
> org.apache.axis2.deployment.util.Utils.addFlowHandlers(Utils.java:116) at
> org.apache.axis2.deployment.DeploymentEngine.buildModule(DeploymentEngine.j
>ava:727) ... 7 more
> [EMAIL PROTECTED]:~/Desktop/softwares/axis2-0.93-bin/samples/src$ javac
> -classpath
> $CLASSPATH:org/apache/axis2/userguide/databinding/org/apache/axis2/userguid
>e/.*:org/apache/axis2/userguide/databinding/org/apache/axis2/userguide/impl/
>.*:org/apache/axis2/userguide/databinding/org/w3/www/.*:org/apache/axis2/use
>rguide/databinding/org/w3/www/impl/.*:org/apache/axis2/userguide/databinding
>/org/xmlsoap/schemas/.* org/apache/axis2/userguide/TestClient.java
> [EMAIL PROTECTED]:~/Desktop/softwares/axis2-0.93-bin/samples/src$ java
> -classpath
> $CLASSPATH:org/apache/axis2/userguide/databinding/org/apache/axis2/userguid
>e/.*:org/apache/axis2/userguide/databinding/org/apache/axis2/userguide/impl/
>.*:org/apache/axis2/userguide/databinding/org/w3/www/.*:org/apache/axis2/use
>rguide/databinding/org/w3/www/impl/.*:org/apache/axis2/userguide/databinding
>/org/xmlsoap/

Re: Writing SOAP messages to disk

Robert,

I see now that new MyServiceServiceLocator() in fact extends Axis.Client. I was 
able to get it to work by using the Handler strategy that you suggested.

Thanks!

Jordan.

- Original Message -
From: Jordan Lee <[EMAIL PROTECTED]>
Date: Friday, March 17, 2006 12:55 pm
Subject: Re: Writing SOAP messages to disk

> Robert, to clarify, how I call the web service is nearly identical 
> to what they do in step 6 on 
> 
> http://www.onjava.com/pub/a/onjava/2002/06/05/axis.html?page=2
> 
> thanks again,
> Jordan.
> 
> - Original Message -
> From: Jordan Lee <[EMAIL PROTECTED]>
> Date: Friday, March 17, 2006 12:50 pm
> Subject: Re: Writing SOAP messages to disk
> 
> > Hi Robert,
> > 
> > Thanks for the response. You are correct on 1) and I have this 
> > working. You are correct on 2). But I think you may have an 
> > assumption as to the implementation of my client.
> > 
> > Or it may be that I'm not implementing the client in the correct 
> way.> 
> > The code snippet that I provided, is the sole link between my 
> > application code and where it calls another web service. The 
> > HTTPBindingStub is generated from the WSDL2Java, and it is 
> through 
> > this object that I bind to the target web service and call a 
> > method on it.
> > 
> > Jordan.
> > 
> > - Original Message -
> > From: robert <[EMAIL PROTECTED]>
> > Date: Friday, March 17, 2006 12:16 pm
> > Subject: Re: Writing SOAP messages to disk
> > 
> > > Perhaps I misunderstand what you are trying to do. 
> > > 
> > > 1) You have a handler on the service side that gets the 
> > > SOAPMessage as a 
> > > Document and writes it to disk on the service side. 
> > > 
> > > 2) You want to do the same thing on the client side, with the 
> > out 
> > > going 
> > > message. 
> > > 
> > > What I recommended was to put another separate though similar 
> > > Handler on the 
> > > client side. Or to add to my first post call MessageContext in 
> a 
> > > static way 
> > > from your client - the FAQ explains how. 
> > > 
> > > If that's wrong try to clarify and maybe I can help. 
> > > 
> > > Robert
> > > http://www.braziloutsource.com/
> > > 
> > > Em Sexta 17 Março 2006 17:02, o Jordan Lee escreveu:
> > > > Hi Robert,
> > > >
> > > > I'm not too sure what you mean by this. My 'client' does the 
> > > following:>
> > > > MyServiceSoapHTTPBindingStub binding = 
> > > (MyServiceSoapHTTPBindingStub) new
> > > > MyServiceServiceLocator() .getMyService("target web service 
> url");> > >
> > > > binding.someMethod(axisMessage);
> > > >
> > > > i'm trying to get the underlying XML representation of the 
> > > 'axisMessage'> object.
> > > >
> > > > - Original Message -
> > > > From: robert <[EMAIL PROTECTED]>
> > > > Date: Friday, March 17, 2006 11:47 am
> > > > Subject: Re: Writing SOAP messages to disk
> > > >
> > > > > Have you considered a client side handler ? Same concept, 
> > but you
> > > > > use:
> > > > >
> > > > > Service.getHandlerRegistry().getHandlerChain(portQN)
> > > > >
> > > > > instead of WSDD to configure it.
> > > > >
> > > > > This would allow you to write the file on the client side, 
> > if I
> > > > > understand you
> > > > > right.
> > > > >
> > > > > HTH,
> > > > > Robert
> > > > > http://www.braziloutsource.com/
> > > > >
> > > > > Em Sexta 17 Março 2006 16:35, o Jordan Lee escreveu:
> > > > > > Hi all,
> > > > > >
> > > > > > I've figured out how to get my web service to write incoming
> > > > >
> > > > > SOAP xml to
> > > > >
> > > > > > disk (using the response\request flows of the wsdd and 
> Handler> > > >
> > > > > classes).>
> > > > >
> > > > > > However - if I'm accessing an Axis web service as a 
> client 
> > -
> > > > >
> > > > > creating a
> > > > >
> > > > > > binding, calling the method with a n Axis defined class 
> as a
> > > > >
> > > > > parameter, etc
> > > > >
> > > > > > - how abouts would I write the outgoing XML to disk?
> > > > > >
> > > > > > thanks,
> > > > > > Jordan.
> > > > >
> > > > > --
> > > 
> > > -- 
> > > 
> > 
>

[Axis2 0.94] Reusing a Stub across multiple operations

2006-03-17 Thread Chuck Williams





Resending with proper subject header:

Hi All,

We have been creating a new Stub instance for every operation initiated
by our client, because if we don't, subsequent operations always get
confused and think they are instances of the first operation performed. 
I.e., if we do operation A and then operation B on the same Stub, then
the operation for B sends the correct message payload to the server, but
the server thinks it is another A operation; the implementation of A of
course then dies because the message is of the wrong type.

In looking at the code, it seems this must be a bug as the Stub is
designed to be reused across operations.  Is this a known problem?  We
are using the http client transport.  Or perhaps, the bug is on the
server side not accepting a message for a different operation on the
same connection?  We are using the built-in http client on the server
side.  There is this interesting comment at the top of Stub.java:

> /**
>  * If _maintainSession is set to true, all the calls can use the same
>  * ServiceContext. The user can share information through this
>  * ServiceContext across operations.
>  */


However, grep _maintainSession shows no other references in the axis2
code base.  I'm wonder if this is somehow related to our issue.  E.g.,
if the operation is somehow sticky in the ServiceContext.  I don't see
any other shared state than the ServiceContext (and Options) across
client operations on a single Stub instance.

I'm looking into this problem again because we are getting a large
number of hanging TimerThreads in our client on Windows.  The same
behavior does not happen running on linux.  Anyone seen this issue?

Thanks for any help,

Chuck



-- 

Chuck Williams
Manawiz
Principal
V: (808)885-8688
C: (415)846-9018
[EMAIL PROTECTED]
Skype: manawiz
AIM: hawimanawiz
Yahoo: jcwxx

Reusing a Stub across multiple operations

2006-03-17 Thread Chuck Williams

Hi All,

We have been creating a new Stub instance for every operation initiated
by our client, because if we don't, subsequent operations always get
confused and think they are instances of the first operation performed. 
I.e., if we do operation A and then operation B on the same Stub, then
the operation for B sends the correct message payload to the server, but
the server thinks it is another A operation; the implementation of A of
course then dies because the message is of the wrong type.

In looking at the code, it seems this must be a bug as the Stub is
designed to be reused across operations.  Is this a known problem?  We
are using the http client transport.  Or perhaps, the bug is on the
server side not accepting a message for a different operation on the
same connection?  We are using the built-in http client on the server
side.  There is this interesting comment at the top of Stub.java:

> /**
>  * If _maintainSession is set to true, all the calls can use the same
>  * ServiceContext. The user can share information through this
>  * ServiceContext across operations.
>  */


However, grep _maintainSession shows no other references in the axis2
code base.  I'm wonder if this is somehow related to our issue.  E.g.,
if the operation is somehow sticky in the ServiceContext.  I don't see
any other shared state than the ServiceContext (and Options) across
client operations on a single Stub instance.

I'm looking into this problem again because we are getting a large
number of hanging TimerThreads in our client on Windows.  The same
behavior does not happen running on linux.  Anyone seen this issue?

Thanks for any help,

Chuck

Missing DOCTYPE and validation

2006-03-17 Thread Michael Oltz


Hello,

I am using Axis 1.3 with Xerces 2.7.1. I am writing a client
for a web service which, I have discovered, does not put a
DOCTYPE header in the SOAP message that comes back. I get an
XML error when Axis starts to try to unmarshall the SOAP.
I am not in a position to fix the other end, nor to fudge
the response way down deep. How can I make the parsing
nonvalidating? Or is that forbidden because it would break
too many other things?

Regards,
Michael Oltz

Re: Writing SOAP messages to disk

Robert, to clarify, how I call the web service is nearly identical to what they 
do in step 6 on 

http://www.onjava.com/pub/a/onjava/2002/06/05/axis.html?page=2

thanks again,
Jordan.

- Original Message -
From: Jordan Lee <[EMAIL PROTECTED]>
Date: Friday, March 17, 2006 12:50 pm
Subject: Re: Writing SOAP messages to disk

> Hi Robert,
> 
> Thanks for the response. You are correct on 1) and I have this 
> working. You are correct on 2). But I think you may have an 
> assumption as to the implementation of my client.
> 
> Or it may be that I'm not implementing the client in the correct way.
> 
> The code snippet that I provided, is the sole link between my 
> application code and where it calls another web service. The 
> HTTPBindingStub is generated from the WSDL2Java, and it is through 
> this object that I bind to the target web service and call a 
> method on it.
> 
> Jordan.
> 
> - Original Message -
> From: robert <[EMAIL PROTECTED]>
> Date: Friday, March 17, 2006 12:16 pm
> Subject: Re: Writing SOAP messages to disk
> 
> > Perhaps I misunderstand what you are trying to do. 
> > 
> > 1) You have a handler on the service side that gets the 
> > SOAPMessage as a 
> > Document and writes it to disk on the service side. 
> > 
> > 2) You want to do the same thing on the client side, with the 
> out 
> > going 
> > message. 
> > 
> > What I recommended was to put another separate though similar 
> > Handler on the 
> > client side. Or to add to my first post call MessageContext in a 
> > static way 
> > from your client - the FAQ explains how. 
> > 
> > If that's wrong try to clarify and maybe I can help. 
> > 
> > Robert
> > http://www.braziloutsource.com/
> > 
> > Em Sexta 17 Março 2006 17:02, o Jordan Lee escreveu:
> > > Hi Robert,
> > >
> > > I'm not too sure what you mean by this. My 'client' does the 
> > following:>
> > > MyServiceSoapHTTPBindingStub binding = 
> > (MyServiceSoapHTTPBindingStub) new
> > > MyServiceServiceLocator() .getMyService("target web service url");
> > >
> > > binding.someMethod(axisMessage);
> > >
> > > i'm trying to get the underlying XML representation of the 
> > 'axisMessage'> object.
> > >
> > > - Original Message -
> > > From: robert <[EMAIL PROTECTED]>
> > > Date: Friday, March 17, 2006 11:47 am
> > > Subject: Re: Writing SOAP messages to disk
> > >
> > > > Have you considered a client side handler ? Same concept, 
> but you
> > > > use:
> > > >
> > > > Service.getHandlerRegistry().getHandlerChain(portQN)
> > > >
> > > > instead of WSDD to configure it.
> > > >
> > > > This would allow you to write the file on the client side, 
> if I
> > > > understand you
> > > > right.
> > > >
> > > > HTH,
> > > > Robert
> > > > http://www.braziloutsource.com/
> > > >
> > > > Em Sexta 17 Março 2006 16:35, o Jordan Lee escreveu:
> > > > > Hi all,
> > > > >
> > > > > I've figured out how to get my web service to write incoming
> > > >
> > > > SOAP xml to
> > > >
> > > > > disk (using the response\request flows of the wsdd and Handler
> > > >
> > > > classes).>
> > > >
> > > > > However - if I'm accessing an Axis web service as a client 
> -
> > > >
> > > > creating a
> > > >
> > > > > binding, calling the method with a n Axis defined class as a
> > > >
> > > > parameter, etc
> > > >
> > > > > - how abouts would I write the outgoing XML to disk?
> > > > >
> > > > > thanks,
> > > > > Jordan.
> > > >
> > > > --
> > 
> > -- 
> > 
>

Re: [axis2] failure when trying to build axis2

2006-03-17 Thread Sean Doyle (Gmail)


Loreno Oliveira wrote:


I got also problems with some tests, just like Sean and Bruno.
My problem was fixed when I turned off the Norton Worm Protection...


No such luck here - I've turned off my Trend Micro, ran svn update, and 
still see errors.


After


   [junit] [ERROR] TEST org.apache.axis2.rpc.RPCCallTest FAILED
   [junit] Running org.apache.axis2.security.AddressingMTOMSecurityTest



you see


BUILD FAILED
File.. C:\Documents and 
Settings\sean\.maven\cache\maven-multiproject-plugin-1.3.1\plugin.jelly

Element... maven:reactor
Line.. 217
Column 9
Unable to obtain goal [multiproject:install-callback] -- C:\Documents 
and Settings\sean\.maven\cache\maven-test-plugin-1

.6.2\plugin.jelly:181:54:  There were test failures.
Total time: 20 minutes 39 seconds
Finished at: Fri Mar 17 15:25:25 EST 2006


This was in response to a 'maven release'.




Now I'm building and testing axis2 fine...

Loreno

On 3/16/06, *Eran Chinthaka* <[EMAIL PROTECTED] 
> wrote:


Hi Sean and Bruno,

We experience a build failure in Axis2 main branch now. Please give us
time till tomoro for us to fix it.

Thanks,
Chinthaka

Sean Doyle (Gmail) wrote:
> bruno wanadoo wrote:
>
>> Hi Chinthaka & everybody else
>>
>> I followed instructions in the FAQ ( with jdk1.5 I modify the
>> security file to add BC as provider)
>> But when I launch maven , a lot of targets are built but at the
end I
>> got this
>>
> I'm getting the same
>Unable to obtain goal [multiproject:install-callback] --
> C:\Documents and
>
Settings\bruno\.maven\cache\maven-test-plugin-1.6.2\plugin.jelly:181:54:

> I've also put in the same attribute for BC. And svn is current
as of a
> few minutes ago.
>
> Here's what works and doesn't work - I'm a bit confused by the
site's
> documentation since it has two different calls to maven
specified for
> building the project. One fails with the plugin.jelly message, the
> other works but doesn't make the war file.
>
> I'm running this in WindowsXP. My version of Maven is 1.0.2. My
> version of Java is java version " 1.5.0_06".
>
>
> According to http://ws.apache.org/axis2/svn.html - you just type
> 'maven'. This fails -
>
>> test:test:
>> [junit] Running org.apache.axis2.om.impl.dom.DocumentImplTest
>> [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed:
0.39 sec
>> [junit] Running
org.apache.axis2.om.impl.dom.DOMImplementationTest
>> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed:
0.28 sec
>> [junit] Running org.apache.axis2.om.impl.dom.ElementImplTest
>> [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed:
0.381
>> sec
>> [junit] Running org.apache.axis2.om.impl.dom.MessagesTest
>> [junit] Tests run: 4, Failures: 0, Errors: 4, Time elapsed:
0.471
>> sec
>> *[junit] [ERROR] TEST org.apache.axis2.om.impl.dom.MessagesTest
>> FAILED*
>> [junit] Running org.apache.axis2.om.impl.dom.OMDOMFactoryTest
>> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed:
0.281
>> sec
>> [junit] Running org.apache.axis2.om.impl.dom.TextImplTest
>> [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed:
0.28 sec
>>
>> BUILD FAILED
>> File.. C:\Documents and
>>
Settings\sean\.maven\cache\maven-multiproject-plugin-1.3.1\plugin.jelly

>> Element... maven:reactor
>> Line.. 217
>> Column 9
>> Unable to obtain goal [multiproject:install-callback] --
C:\Documents
>> and Settings\sean\.maven\cache\maven-test-plugin-1
>> .6.2\plugin.jelly:181:54:  There were test failures.
>> Total time: 4 minutes 9 seconds
>> Finished at: Thu Mar 16 10:22:34 EST 2006
>
>
> According to http://ws.apache.org/axis2/siteHowTo.html - you type
> 'maven multiproject'. This worked yesterday - but it didn't make the
> war file. And - although it worked there are several errors of
the sort:
>
>> Error retrieving artifact from
>>
[http://www.ibiblio.org/maven/axis2/jars/axis2-codegen-0.95-SNAPSHOT.jar]:
>> java.net.Conne
>> ctException: Connection timed out: connect
>> 192K downloaded
>
>
>
> Somewhere on the apache site there was a suggestion to use
'maven.war'
> - this failed with (I believe) the same plugin.jelly error.
>
> Also - I've been running 'maven clean' between runs if that
makes any
> difference.
>
> I did invoke
>
> %MAVEN_HOME%\bin\install_repo.bat c:\.maven\repository
> when I installed Maven a few days ago.
>
> What should I try next if I want to build the war file?
>
>
> Thanks..
>
> Sean
>
>>
>>
>> /+
>> | Executing m

Re: Writing SOAP messages to disk

Hi Robert,

Thanks for the response. You are correct on 1) and I have this working. You are 
correct on 2). But I think you may have an assumption as to the implementation 
of my client.

Or it may be that I'm not implementing the client in the correct way.

The code snippet that I provided, is the sole link between my application code 
and where it calls another web service. The HTTPBindingStub is generated from 
the WSDL2Java, and it is through this object that I bind to the target web 
service and call a method on it.

Jordan.

- Original Message -
From: robert <[EMAIL PROTECTED]>
Date: Friday, March 17, 2006 12:16 pm
Subject: Re: Writing SOAP messages to disk

> Perhaps I misunderstand what you are trying to do. 
> 
> 1) You have a handler on the service side that gets the 
> SOAPMessage as a 
> Document and writes it to disk on the service side. 
> 
> 2) You want to do the same thing on the client side, with the out 
> going 
> message. 
> 
> What I recommended was to put another separate though similar 
> Handler on the 
> client side. Or to add to my first post call MessageContext in a 
> static way 
> from your client - the FAQ explains how. 
> 
> If that's wrong try to clarify and maybe I can help. 
> 
> Robert
> http://www.braziloutsource.com/
> 
> Em Sexta 17 Março 2006 17:02, o Jordan Lee escreveu:
> > Hi Robert,
> >
> > I'm not too sure what you mean by this. My 'client' does the 
> following:>
> > MyServiceSoapHTTPBindingStub binding = 
> (MyServiceSoapHTTPBindingStub) new
> > MyServiceServiceLocator() .getMyService("target web service url");
> >
> > binding.someMethod(axisMessage);
> >
> > i'm trying to get the underlying XML representation of the 
> 'axisMessage'> object.
> >
> > - Original Message -
> > From: robert <[EMAIL PROTECTED]>
> > Date: Friday, March 17, 2006 11:47 am
> > Subject: Re: Writing SOAP messages to disk
> >
> > > Have you considered a client side handler ? Same concept, but you
> > > use:
> > >
> > > Service.getHandlerRegistry().getHandlerChain(portQN)
> > >
> > > instead of WSDD to configure it.
> > >
> > > This would allow you to write the file on the client side, if I
> > > understand you
> > > right.
> > >
> > > HTH,
> > > Robert
> > > http://www.braziloutsource.com/
> > >
> > > Em Sexta 17 Março 2006 16:35, o Jordan Lee escreveu:
> > > > Hi all,
> > > >
> > > > I've figured out how to get my web service to write incoming
> > >
> > > SOAP xml to
> > >
> > > > disk (using the response\request flows of the wsdd and Handler
> > >
> > > classes).>
> > >
> > > > However - if I'm accessing an Axis web service as a client -
> > >
> > > creating a
> > >
> > > > binding, calling the method with a n Axis defined class as a
> > >
> > > parameter, etc
> > >
> > > > - how abouts would I write the outgoing XML to disk?
> > > >
> > > > thanks,
> > > > Jordan.
> > >
> > > --
> 
> -- 
>

Re: Writing SOAP messages to disk

Perhaps I misunderstand what you are trying to do. 

1) You have a handler on the service side that gets the SOAPMessage as a 
Document and writes it to disk on the service side. 

2) You want to do the same thing on the client side, with the out going 
message. 

What I recommended was to put another separate though similar Handler on the 
client side. Or to add to my first post call MessageContext in a static way 
from your client - the FAQ explains how. 

If that's wrong try to clarify and maybe I can help. 

Robert
http://www.braziloutsource.com/

Em Sexta 17 Março 2006 17:02, o Jordan Lee escreveu:
> Hi Robert,
>
> I'm not too sure what you mean by this. My 'client' does the following:
>
> MyServiceSoapHTTPBindingStub binding = (MyServiceSoapHTTPBindingStub) new
> MyServiceServiceLocator() .getMyService("target web service url");
>
> binding.someMethod(axisMessage);
>
> i'm trying to get the underlying XML representation of the 'axisMessage'
> object.
>
> - Original Message -
> From: robert <[EMAIL PROTECTED]>
> Date: Friday, March 17, 2006 11:47 am
> Subject: Re: Writing SOAP messages to disk
>
> > Have you considered a client side handler ? Same concept, but you
> > use:
> >
> > Service.getHandlerRegistry().getHandlerChain(portQN)
> >
> > instead of WSDD to configure it.
> >
> > This would allow you to write the file on the client side, if I
> > understand you
> > right.
> >
> > HTH,
> > Robert
> > http://www.braziloutsource.com/
> >
> > Em Sexta 17 Março 2006 16:35, o Jordan Lee escreveu:
> > > Hi all,
> > >
> > > I've figured out how to get my web service to write incoming
> >
> > SOAP xml to
> >
> > > disk (using the response\request flows of the wsdd and Handler
> >
> > classes).>
> >
> > > However - if I'm accessing an Axis web service as a client -
> >
> > creating a
> >
> > > binding, calling the method with a n Axis defined class as a
> >
> > parameter, etc
> >
> > > - how abouts would I write the outgoing XML to disk?
> > >
> > > thanks,
> > > Jordan.
> >
> > --

--

Re: Writing SOAP messages to disk

Hi Robert,

I'm not too sure what you mean by this. My 'client' does the following:

MyServiceSoapHTTPBindingStub binding = (MyServiceSoapHTTPBindingStub) new 
MyServiceServiceLocator()
.getMyService("target web service url");

binding.someMethod(axisMessage);

i'm trying to get the underlying XML representation of the 'axisMessage' object.

- Original Message -
From: robert <[EMAIL PROTECTED]>
Date: Friday, March 17, 2006 11:47 am
Subject: Re: Writing SOAP messages to disk

> Have you considered a client side handler ? Same concept, but you 
> use: 
> 
> Service.getHandlerRegistry().getHandlerChain(portQN)
> 
> instead of WSDD to configure it.
> 
> This would allow you to write the file on the client side, if I 
> understand you 
> right. 
> 
> HTH,
> Robert
> http://www.braziloutsource.com/
> 
> Em Sexta 17 Março 2006 16:35, o Jordan Lee escreveu:
> > Hi all,
> >
> > I've figured out how to get my web service to write incoming 
> SOAP xml to
> > disk (using the response\request flows of the wsdd and Handler 
> classes).>
> > However - if I'm accessing an Axis web service as a client - 
> creating a
> > binding, calling the method with a n Axis defined class as a 
> parameter, etc
> > - how abouts would I write the outgoing XML to disk?
> >
> > thanks,
> > Jordan.
> 
> -- 
>

Re: Writing SOAP messages to disk

Have you considered a client side handler ? Same concept, but you use: 

Service.getHandlerRegistry().getHandlerChain(portQN)

instead of WSDD to configure it.

This would allow you to write the file on the client side, if I understand you 
right. 

HTH,
Robert
http://www.braziloutsource.com/

Em Sexta 17 Março 2006 16:35, o Jordan Lee escreveu:
> Hi all,
>
> I've figured out how to get my web service to write incoming SOAP xml to
> disk (using the response\request flows of the wsdd and Handler classes).
>
> However - if I'm accessing an Axis web service as a client - creating a
> binding, calling the method with a n Axis defined class as a parameter, etc
> - how abouts would I write the outgoing XML to disk?
>
> thanks,
> Jordan.

--

Writing SOAP messages to disk

Hi all,

I've figured out how to get my web service to write incoming SOAP xml to disk 
(using the response\request flows of the wsdd and Handler classes).

However - if I'm accessing an Axis web service as a client - creating a 
binding, calling the method with a n Axis defined class as a parameter, etc - 
how abouts would I write the outgoing XML to disk?

thanks,
Jordan.

Re: [Axis2] Handling request-responseS type messaging

Add a decrementing count element to the message. In any case, the client should know the cardinality of its initial request message. Therefore it should know how many "response" messages it expects to receive. (Note that these response messages are, technically, request messages.)
AnneOn 3/17/06, Ali Sadik Kumlali <[EMAIL PROTECTED]> wrote:
Thank you Anne. But, AFAIK, WSDL does not support IN-Multiple OUT as operation type. If WSDL does not has signature for multiple results, how can client assume that it must wait for more than one results?
Thanks a lot,Ali Sadik KumlaliAnne Thomas Manes <
[EMAIL PROTECTED]> wrote:
 Ali,   Do you mean;  1) Client sends request without waiting a response to it. Request has a CSV tag which has many lines to process.  2) Server processes the message and sends a result for each line in  CS  V. It  sends results to the client without waiting a response.
Yes. (Or alternatively, each message exchange could return an "ack", which would be easier to implement if you're using Axis 1.)Anne 
On 3/16/06, Al
 i Sadik
 Kumlali <[EMAIL PROTECTED]> wrote:
 Hi Eran, Hi Anne!What a quick response! What a good community! Thank you very very much.  I love this community and  hope companies discover the power of  open-source products. I post your responses to my colleagues in the  company to let them recognize that support does not always mean money,  and vice versa :) 
Eran,Our current implementation uses DocSoap XDK based custom codes. Since  we are required to handle all the soap related stuff manually, we are  able to support  "IN-multiple OUT" type messaging. Actually,  manual operations are one of the reasons we want to give DocSoap XDK  up. Therefore, it would be great if I could find a robust way in Axis2  to support "IN-multiple
  OUT"
 type messaging. Anne,Do you mean;  1) Client sends request without waiting a response to it. Request has a CSV tag which has many lines to process.  2) Server processes the message and sends a result for each line in  CS  V. It  sends results to the client without waiting a response.
Many thanks to you both!Ali Sadik Kumlali  Anne Thomas Manes <
 [EMAIL PROTECTED]> wrote:
   You can also  implement the pattern using one-way messages.Anne
 On 3/16/06, Eran Chinthaka <
[EMAIL PROTECTED]  > wrote: 
 Hi Ali,Interesting scenario.First of all, Axis2 supports IN only and IN-OUT invocations by  *default.* But thats doesn't mean we can not do IN-multiple OUT meps.
Yes, we haven't come across them so far, but our pipe model enables custom MEPs. If you really ne  ed this  we can give a  try to implement the
  first custom MEP using Axi
 s2. (or
 you can convince your boss otherwise ;-) )-- Chinthaka Ali Sadik Kumlali wrote:> Dear all,>> There is an interesting messaging pattern between my company  
> and its partner. Partner sends a message containing a tag named> CSV that has multiple lines in it. Although we process all of them > separately, we assume it as one message. After processing has
  > been completed, we send a result message for every line in CSV.> Thus, request-responseS type messaging occurs.>> This seems very strange when I look at the async messaging > samples that come with Axis2. If I understand correctly, when  
> client sends a request in an async-non blocker way, it also> starts an http server to listen response. When the server finishes> processing, it sends the result back to the client's http server. 
  >  Consequently, each request has one response.>> AFAIK, we a
 re
 allowed to have one-way and request-response> type operations, but not request-responseS.>> Is there a way to handle request-responseS type messaging   
> with Axis2? Or do I ne ed to convince my boss to give these kind> of messaging up? :)>> Thanks a lot,>> Ali Sadik Kumlali>>    
> Yahoo! Mail> Bring photos to life! New PhotoMail> <
 http://pa.yahoo.com/*http://us.rd.yahoo.com/evt=39174/*http://photomail.mail.yahoo.com  >> makes sharing a breeze.
   Yahoo! Mail
  Use Photomail to share photos without annoying attachments. 
 

		Yahoo! Mail
Bring photos to life! New PhotoMail  makes sharing a breeze.

Re: Document style parameters

Chris,Perhaps someone else can help you the proper coding of your client, but I want to point out that you have some errors in the WSDL:In the  defintion in the portType, you should remove the parameterOrder attribute. At the very least you must remove " resp" from the value of the attribute:
Also, in the  definition in the binding, you must remove the namespace attribute. The attribute is used only with RPC style bindings.
AnneOn 3/17/06, Chris Mannion <[EMAIL PROTECTED]> wrote:







Hi all
 
I'm having a problem properly putting a parameter 
into a call to a document style webservice.  I have a generic client build 
in axis, the basics of while are demonstrated with the following code 
extracts:
 
ServiceFactory serviceFactory = 
ServiceFactory.newInstance();Service webService = 
serviceFactory.createService(wsdlUrl, serviceQName);
Call opCall = webService.createCall(portQName, 
operationName);
Object response = 
opCall.invoke(params);
 
The webservice I'm trying to call is a document 
style, here are the parts of the wsdl relevant to the input 
messages
 
 
 xmlns="urn:TransactionTypesWs" xmlns:apachesoap="
http://xml.apache.org/xml-soap" xmlns:impl="urn:TransactionTypesWs" xmlns:intf="urn:TransactionTypesWs" xmlns:soapenc="
http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/
" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="
http://www.w3.org/2001/XMLSchema">  
      
      
  
    
    
    
    
    
    
  
    
  
  
    ...    
      
    
  

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

 
So the service is expection an input message with a 
soap body that looks like this

  
    
...
    
...
    
...
    
...
    
...
    
...
  

 
I've worked out that to have axis format my input 
as a proper document style soap message rather than escape the xml and make it a 
string parameter, I should invoke the call with an org.w3c.dom.Document object 
as the parameter.  However, if I build a document object from xml with the 
 tag as it's root element, when incorparates it into the soap 
message, there is an extra set of  tags, presumably 
auto-generated by axis based on what's in the wsdl file, so the end message 
looks like

  
    
  
...
  ...
    
  

 
The fact that axis has automatically inserted one 
set of  tags made me think that I should only enter the child 
elements of .  However, because the method is specified as 
only requiring one parameter, passing in the six child elements as separate 
org.w3c.dom.Element objects causes an axis fault for providing the 
wrong number of parameters.  And the only way I know of to combine them 
into one object is to make a Document object but that can't be done unless there 
is one root element surrounding the six, which puts me back to where I 
started.
 
Can anyone help?  How can I get the correct 
input into axis to generate the correctly formatted soap message?  As I 
said, this is a generic web service client and I have several other document 
style services to integrate with which are going to cause the same 
problem so generating bespoke code for each new web service isn't a 
viable option.  I'll be eternally grateful if there's an easy answer 
to this, thanks.
Chris MannionIT Junction020 8452 
4274

Re: Problems in accessing the sample service in Axis2

Did you follow the instructions in yellow on the dowload page? 

http://ws.apache.org/axis2/download.cgi

HTH,
Robert
http://www.braziloutsource.com/

Em Sexta 17 Março 2006 15:25, o Kashif Saleem escreveu:
> Hi All,
>I deployed the service Axis2SampleDocLitPortType successfully as
> mentioned in the use-guide.But when I tried to access this service  through
> client I got the following exceptions.I would appreciate if someone could
> tell me the cause of this error.Below is the output that I got after
> running the client:
>
> [EMAIL PROTECTED]:~/Desktop/softwares/axis2-0.93-bin/samples/src$ java
> -classpath $CLASSPATH org/apache/axis2/userguide/TestClient - Module
> validation failed  org.apache.axis.handlers.addressing.AddressingInHandler;
> nested exception is: org.apache.axis2.AxisFault:
> org.apache.axis.handlers.addressing.AddressingInHandler
> org.apache.axis2.deployment.DeploymentException:
> org.apache.axis.handlers.addressing.AddressingInHandler; nested exception
> is: org.apache.axis2.AxisFault:
> org.apache.axis.handlers.addressing.AddressingInHandler; nested exception
> is: org.apache.axis2.deployment.DeploymentException:
> org.apache.axis.handlers.addressing.AddressingInHandler; nested exception
> is: org.apache.axis2.AxisFault:
> org.apache.axis.handlers.addressing.AddressingInHandler; nested exception
> is: org.apache.axis2.deployment.DeploymentException:
> org.apache.axis.handlers.addressing.AddressingInHandler; nested exception
> is: org.apache.axis2.AxisFault:
> org.apache.axis.handlers.addressing.AddressingInHandler; nested exception
> is: org.apache.axis2.deployment.DeploymentException:
> org.apache.axis.handlers.addressing.AddressingInHandler; nested exception
> is: org.apache.axis2.AxisFault:
> org.apache.axis.handlers.addressing.AddressingInHandler at
> org.apache.axis2.context.ConfigurationContextFactory.buildClientConfigurati
>onContext(ConfigurationContextFactory.java:68) at
> org.apache.axis2.userguide.Axis2SampleDocLitPortTypeStub.(Axis2Sample
>DocLitPortTypeStub.java:53) at
> org.apache.axis2.userguide.TestClient.foo(TestClient.java:35) at
> org.apache.axis2.userguide.TestClient.main(TestClient.java:21) Caused by:
> org.apache.axis2.deployment.DeploymentException:
> org.apache.axis.handlers.addressing.AddressingInHandler; nested exception
> is: org.apache.axis2.AxisFault:
> org.apache.axis.handlers.addressing.AddressingInHandler; nested exception
> is: org.apache.axis2.deployment.DeploymentException:
> org.apache.axis.handlers.addressing.AddressingInHandler; nested exception
> is: org.apache.axis2.AxisFault:
> org.apache.axis.handlers.addressing.AddressingInHandler at
> org.apache.axis2.deployment.DeploymentEngine.loadClient(DeploymentEngine.ja
>va:272) at
> org.apache.axis2.context.ConfigurationContextFactory.buildClientConfigurati
>onContext(ConfigurationContextFactory.java:60) ... 3 more
> Caused by: org.apache.axis2.deployment.DeploymentException:
> org.apache.axis.handlers.addressing.AddressingInHandler; nested exception
> is: org.apache.axis2.AxisFault:
> org.apache.axis.handlers.addressing.AddressingInHandler at
> org.apache.axis2.deployment.DeploymentEngine.buildModule(DeploymentEngine.j
>ava:743) at
> org.apache.axis2.engine.AxisConfiguration.engageModule(AxisConfiguration.ja
>va:433) at
> org.apache.axis2.deployment.DeploymentEngine.engageModules(DeploymentEngine
>.java:329) at
> org.apache.axis2.deployment.DeploymentEngine.loadClient(DeploymentEngine.ja
>va:269) ... 4 more
> Caused by: org.apache.axis2.AxisFault:
> org.apache.axis.handlers.addressing.AddressingInHandler at
> org.apache.axis2.deployment.util.Utils.getHandlerClass(Utils.java:136) at
> org.apache.axis2.deployment.util.Utils.addFlowHandlers(Utils.java:116) at
> org.apache.axis2.deployment.DeploymentEngine.buildModule(DeploymentEngine.j
>ava:727) ... 7 more
> [EMAIL PROTECTED]:~/Desktop/softwares/axis2-0.93-bin/samples/src$ javac
> -classpath
> $CLASSPATH:org/apache/axis2/userguide/databinding/org/apache/axis2/userguid
>e/.*:org/apache/axis2/userguide/databinding/org/apache/axis2/userguide/impl/
>.*:org/apache/axis2/userguide/databinding/org/w3/www/.*:org/apache/axis2/use
>rguide/databinding/org/w3/www/impl/.*:org/apache/axis2/userguide/databinding
>/org/xmlsoap/schemas/.* org/apache/axis2/userguide/TestClient.java
> [EMAIL PROTECTED]:~/Desktop/softwares/axis2-0.93-bin/samples/src$ java
> -classpath
> $CLASSPATH:org/apache/axis2/userguide/databinding/org/apache/axis2/userguid
>e/.*:org/apache/axis2/userguide/databinding/org/apache/axis2/userguide/impl/
>.*:org/apache/axis2/userguide/databinding/org/w3/www/.*:org/apache/axis2/use
>rguide/databinding/org/w3/www/impl/.*:org/apache/axis2/userguide/databinding
>/org/xmlsoap/schemas/.* org/apache/axis2/userguide/TestClient - Module
> validation failed  org.apache.axis.handlers.addressing.AddressingInHandler;
> nested exception is: org.apache.axis2.AxisFault:
> org.apache.axis.handlers.addressing.AddressingInHandler
> org.apache.axis2.deployment.Deplo

boring messagens buiding axis2

Hi all, me again... :-)Every time I build axis2 I'm getting lots of boring messages such as:Error retrieving artifact from [
http://mirrors.sunsite.dk/maven/ws-commons/jars/XmlSchema-1.0-SNAPSHOT.jar]: java.io.IOException: Forbidden.Artifact /ws-commons/jars/XmlSchema-1.0-SNAPSHOT.jar doesn't exists in remote repository, but it exists locally
Possibly I'm wrong, but it smells as a maven debility. That is, it shoud first check if the artifact is present locally. If not, it should try to download it from some place. However, seems like it is doing the inverse algorithm...
Is there anyway of hiding these messages??Thanks!PS: I think it's time to lighten the list and invest some hours studing maven :-)Loreno

Re: No scheme found in URI.

2006-03-17 Thread Jeff Greif

It appears that UNC names are not legal URIs according to Internet RFC
2396.  In particular, the scheme is missing (such as http: or file:)
and the \ is not a path separator (but it is not a forbidden
character), nor is \\ valid to separate the scheme from the rest. 
This is probably not a bug in Axis -- the web service should produce a
valid URI string.

Jeff

On 3/17/06, Luca Albertazzi <[EMAIL PROTECTED]> wrote:
>  I found where the problem occurs:
>
>  The response object  (_resp) contains an object of type
> 'org.apache.axis.types.URI'. The web service I invoke (wich is written in
> C#) valorizes the field corresponding to that object with an 'UNC' value
> like this:
> '\\192.168.1.103\c$\temp\6a165c0f869d4741b991973d202cf0ca',
> wich causes the MalformedURIException during the deserialization.
>
>  Can we say that is a bug of the class org.apache.axis.types.URI? Is that
> problem resolved in Axis 2.0?
>
>  Thank you,
>
>  Luca
>
>
>
>
>
>
>  Luca Albertazzi ha scritto:
>  Hello,
>  I have made a client starting from a given Wsdl using WSDL2Java tool
> but invoking the web service.
>  The exception occurs in the stub created by the tool during the
> _call.invoke(..) operation:
>
> _call.setOperationName(new
> javax.xml.namespace.QName("http://www.mps.it/MultiChannel/";,
> "RegisterDocument"));
>
>  setRequestHeaders(_call);
>  setAttachments(_call);
>   try {java.lang.Object _resp = _call.invoke(new java.lang.Object[]
> {documentId, flowName, documentSize, documentHash, properties,
> supportedChannels, callbackUrl});
>
>  if (_resp instanceof java.rmi.RemoteException) {
>  throw (java.rmi.RemoteException)_resp;
>  }
>  else {
>  extractAttachments(_call);
>  try {
>  return
> (it.mps.www.MultiChannel.ChannelDefinition) _resp;
>  } catch (java.lang.Exception _exception) {
>  return
> (it.mps.www.MultiChannel.ChannelDefinition)
> org.apache.axis.utils.JavaUtils.convert(_resp,
> it.mps.www.MultiChannel.ChannelDefinition.class);
>  }
>  }
>} catch (org.apache.axis.AxisFault axisFaultException) {
>throw axisFaultException;
>
>  Each time I execute the service I get the error wich follows:
>
>  - Exception:
>  org.apache.axis.types.URI$MalformedURIException: No scheme
> found in URI.
>  at
> org.apache.axis.encoding.ser.SimpleDeserializer.onEndElement(SimpleDeserializer.java:180)
>  at
> org.apache.axis.encoding.DeserializerImpl.endElement(DeserializerImpl.java:502)
>  at
> org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
>  at
> org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:171)
>  at
> org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
>  at
> org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
>  at
> org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
>  at org.apache.axis.client.Call.invoke(Call.java:2467)
>  at org.apache.axis.client.Call.invoke(Call.java:2366)
>  at org.apache.axis.client.Call.invoke(Call.java:1812)
>  at
> it.mps.www.MultiChannel.MultiChannelWSSoapStub.registerDocument(MultiChannelWSSoapStub.java:283)
>  at
> com.cedac.webservices.test.TestMultiChannelWS.main(TestMultiChannelWS.java:42)
>  AxisFault
>   faultCode:
> {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
>   faultSubcode:
>   faultString:
> org.apache.axis.types.URI$MalformedURIException: No scheme
> found in URI.
>   faultActor:
>   faultNode:
>   faultDetail:
>
> {http://xml.apache.org/axis/}stackTrace:org.apache.axis.types.URI$MalformedURIException:
> No scheme found in URI.
>  at
> org.apache.axis.encoding.ser.SimpleDeserializer.onEndElement(SimpleDeserializer.java:180)
>  at
> org.apache.axis.encoding.DeserializerImpl.endElement(DeserializerImpl.java:502)
>  at
> org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
>  at
> org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:171)
>  at
> org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
>  at
> org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
>  at
> org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
>  at org.apache.axis.client.Call.invoke(Call.java:2467)
>  at org.apache.axis.client.Call.invoke(Call.java:2366)
>  at org.apache.axis.client.Call.invoke(Call.java:1812)
>  at
> it.mps.www.MultiChannel.MultiChannelWSSoapStub.registerDocument(MultiChannelWSSoapStub.java:283)
>  at
> com.cedac.webservices.test.TestMultiChannelWS.main(TestMultiChannelWS.java:42)
>
>  {http://xml.apache.org/axis/}hostname:WALLACE
>
>  org.apache.axis.types.URI$MalformedURIException: No scheme
> found in URI.
>  at
> org.apache.axis.AxisFault.makeFault(AxisFau

Problems in accessing the sample service in Axis2

2006-03-17 Thread Kashif Saleem

Hi All,
   I deployed the service Axis2SampleDocLitPortType successfully as 
mentioned in the use-guide.But when I tried to access this service  through 
client I got the following exceptions.I would appreciate if someone could tell 
me the cause of this error.Below is the output that I got after running the 
client:

[EMAIL PROTECTED]:~/Desktop/softwares/axis2-0.93-bin/samples/src$ java 
-classpath $CLASSPATH org/apache/axis2/userguide/TestClient
- Module validation failed  
org.apache.axis.handlers.addressing.AddressingInHandler; nested exception is:
org.apache.axis2.AxisFault: 
org.apache.axis.handlers.addressing.AddressingInHandler
org.apache.axis2.deployment.DeploymentException: 
org.apache.axis.handlers.addressing.AddressingInHandler; nested exception is:
org.apache.axis2.AxisFault: 
org.apache.axis.handlers.addressing.AddressingInHandler; nested exception is:
org.apache.axis2.deployment.DeploymentException: 
org.apache.axis.handlers.addressing.AddressingInHandler; nested exception is:
org.apache.axis2.AxisFault: 
org.apache.axis.handlers.addressing.AddressingInHandler; nested exception is:
org.apache.axis2.deployment.DeploymentException: 
org.apache.axis.handlers.addressing.AddressingInHandler; nested exception is:
org.apache.axis2.AxisFault: 
org.apache.axis.handlers.addressing.AddressingInHandler; nested exception is:
org.apache.axis2.deployment.DeploymentException: 
org.apache.axis.handlers.addressing.AddressingInHandler; nested exception is:
org.apache.axis2.AxisFault: 
org.apache.axis.handlers.addressing.AddressingInHandler
at 
org.apache.axis2.context.ConfigurationContextFactory.buildClientConfigurationContext(ConfigurationContextFactory.java:68)
at 
org.apache.axis2.userguide.Axis2SampleDocLitPortTypeStub.(Axis2SampleDocLitPortTypeStub.java:53)
at org.apache.axis2.userguide.TestClient.foo(TestClient.java:35)
at org.apache.axis2.userguide.TestClient.main(TestClient.java:21)
Caused by: org.apache.axis2.deployment.DeploymentException: 
org.apache.axis.handlers.addressing.AddressingInHandler; nested exception is:
org.apache.axis2.AxisFault: 
org.apache.axis.handlers.addressing.AddressingInHandler; nested exception is:
org.apache.axis2.deployment.DeploymentException: 
org.apache.axis.handlers.addressing.AddressingInHandler; nested exception is:
org.apache.axis2.AxisFault: 
org.apache.axis.handlers.addressing.AddressingInHandler
at 
org.apache.axis2.deployment.DeploymentEngine.loadClient(DeploymentEngine.java:272)
at 
org.apache.axis2.context.ConfigurationContextFactory.buildClientConfigurationContext(ConfigurationContextFactory.java:60)
... 3 more
Caused by: org.apache.axis2.deployment.DeploymentException: 
org.apache.axis.handlers.addressing.AddressingInHandler; nested exception is:
org.apache.axis2.AxisFault: 
org.apache.axis.handlers.addressing.AddressingInHandler
at 
org.apache.axis2.deployment.DeploymentEngine.buildModule(DeploymentEngine.java:743)
at 
org.apache.axis2.engine.AxisConfiguration.engageModule(AxisConfiguration.java:433)
at 
org.apache.axis2.deployment.DeploymentEngine.engageModules(DeploymentEngine.java:329)
at 
org.apache.axis2.deployment.DeploymentEngine.loadClient(DeploymentEngine.java:269)
... 4 more
Caused by: org.apache.axis2.AxisFault: 
org.apache.axis.handlers.addressing.AddressingInHandler
at 
org.apache.axis2.deployment.util.Utils.getHandlerClass(Utils.java:136)
at 
org.apache.axis2.deployment.util.Utils.addFlowHandlers(Utils.java:116)
at 
org.apache.axis2.deployment.DeploymentEngine.buildModule(DeploymentEngine.java:727)
... 7 more
[EMAIL PROTECTED]:~/Desktop/softwares/axis2-0.93-bin/samples/src$ javac 
-classpath 
$CLASSPATH:org/apache/axis2/userguide/databinding/org/apache/axis2/userguide/.*:org/apache/axis2/userguide/databinding/org/apache/axis2/userguide/impl/.*:org/apache/axis2/userguide/databinding/org/w3/www/.*:org/apache/axis2/userguide/databinding/org/w3/www/impl/.*:org/apache/axis2/userguide/databinding/org/xmlsoap/schemas/.*
 org/apache/axis2/userguide/TestClient.java
[EMAIL PROTECTED]:~/Desktop/softwares/axis2-0.93-bin/samples/src$ java 
-classpath 
$CLASSPATH:org/apache/axis2/userguide/databinding/org/apache/axis2/userguide/.*:org/apache/axis2/userguide/databinding/org/apache/axis2/userguide/impl/.*:org/apache/axis2/userguide/databinding/org/w3/www/.*:org/apache/axis2/userguide/databinding/org/w3/www/impl/.*:org/apache/axis2/userguide/databinding/org/xmlsoap/schemas/.*
 org/apache/axis2/userguide/TestClient
- Module validation failed  
org.apache.axis.handlers.addressing.AddressingInHandler; nested exception is:
org.apache.axis2.AxisFault: 
org.apache.axis.handlers.addressing.AddressingInHandler
org.apache.axis2.deployment.DeploymentException: 
org.apache.axis.handlers.addressing.AddressingInHandler; nested exception is:

Re: [axis2] failure when trying to build axis2

I got also problems with some tests, just like Sean and Bruno.My problem was fixed when I turned off the Norton Worm Protection...Now I'm building and testing axis2 fine...Loreno
On 3/16/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
Hi Sean and Bruno,We experience a build failure in Axis2 main branch now. Please give ustime till tomoro for us to fix it.Thanks,ChinthakaSean Doyle (Gmail) wrote:> bruno wanadoo wrote:
>>> Hi Chinthaka & everybody else I followed instructions in the FAQ ( with jdk1.5 I modify the>> security file to add BC as provider)>> But when I launch maven , a lot of targets are built but at the end I
>> got this>>> I'm getting the same>Unable to obtain goal [multiproject:install-callback] --> C:\Documents and> Settings\bruno\.maven\cache\maven-test-plugin-1.6.2\plugin.jelly:181:54:
> I've also put in the same attribute for BC. And svn is current as of a> few minutes ago.>> Here's what works and doesn't work - I'm a bit confused by the site's> documentation since it has two different calls to maven specified for
> building the project. One fails with the plugin.jelly message, the> other works but doesn't make the war file.>> I'm running this in WindowsXP. My version of Maven is 1.0.2. My> version of Java is java version "
1.5.0_06".>>> According to http://ws.apache.org/axis2/svn.html - you just type> 'maven'. This fails ->>> test:test:>> [junit] Running 
org.apache.axis2.om.impl.dom.DocumentImplTest>> [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.39 sec>> [junit] Running org.apache.axis2.om.impl.dom.DOMImplementationTest>> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 
0.28 sec>> [junit] Running org.apache.axis2.om.impl.dom.ElementImplTest>> [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 0.381>> sec>> [junit] Running org.apache.axis2.om.impl.dom.MessagesTest
>> [junit] Tests run: 4, Failures: 0, Errors: 4, Time elapsed: 0.471>> sec>> *[junit] [ERROR] TEST org.apache.axis2.om.impl.dom.MessagesTest>> FAILED*>> [junit] Running 
org.apache.axis2.om.impl.dom.OMDOMFactoryTest>> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.281>> sec>> [junit] Running org.apache.axis2.om.impl.dom.TextImplTest
>> [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.28 sec BUILD FAILED>> File.. C:\Documents and>> Settings\sean\.maven\cache\maven-multiproject-plugin-1.3.1\plugin.jelly
>> Element... maven:reactor>> Line.. 217>> Column 9>> Unable to obtain goal [multiproject:install-callback] -- C:\Documents>> and Settings\sean\.maven\cache\maven-test-plugin-1
>> .6.2\plugin.jelly:181:54:  There were test failures.>> Total time: 4 minutes 9 seconds>> Finished at: Thu Mar 16 10:22:34 EST 2006>>> According to 
http://ws.apache.org/axis2/siteHowTo.html - you type> 'maven multiproject'. This worked yesterday - but it didn't make the> war file. And - although it worked there are several errors of the sort:>
>> Error retrieving artifact from>> [http://www.ibiblio.org/maven/axis2/jars/axis2-codegen-0.95-SNAPSHOT.jar]:>> 
java.net.Conne>> ctException: Connection timed out: connect>> 192K downloaded Somewhere on the apache site there was a suggestion to use 'maven.war'> - this failed with (I believe) the same 
plugin.jelly error.>> Also - I've been running 'maven clean' between runs if that makes any> difference.>> I did invoke>> %MAVEN_HOME%\bin\install_repo.bat c:\.maven\repository
> when I installed Maven a few days ago.>> What should I try next if I want to build the war file?>>> Thanks..>> Sean>>> /+
>> | Executing multiproject:install-callback Apache Axis 2.0 - DOM over OM>> | Memory: 8M/12M>> +>> Tentative de tÚlÚchargement de axiom-1.0-SNAPSHOT.jar
.>> Tentative de tÚlÚchargement de axis2-common-0.95-SNAPSHOT.jar.>> Tentative de tÚlÚchargement de axis2-core-0.95-SNAPSHOT.jar. jar:jar: jar:install:
>> build:end: build:start: multiproject:install-callback:>> [echo] Running jar:install for Apache Axis 2.0 - DOM over OM>> java:prepare-filesystem:
 java:compile:>> [echo] Compiling to D:\work\axis2-dev\modules\doom/target/classes java:jar-resources: test:prepare-filesystem:>>
>> test:test-resources: test:compile: test:test:>> [junit] Running org.apache.axis2.om.impl.dom.DocumentImplTest>> [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0,5 sec
>> [junit] Running org.apache.axis2.om.impl.dom.DOMImplementationTest>> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,39 sec>> [junit] Running org.apache.axis2.om.impl.dom.ElementImplTest
>> [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 0,406>> sec>> [junit] Running org.apache.axis2.om.impl.dom.MessagesTest>> [junit] Tests run: 4, Failures: 0, Errors: 4, Time elapsed: 0,672
>> sec>> [junit] [ERROR] TEST org.apache.axis2.om.impl.dom.Me

Document style parameters

2006-03-17 Thread Chris Mannion




Hi all
 
I'm having a problem properly putting a parameter 
into a call to a document style webservice.  I have a generic client build 
in axis, the basics of while are demonstrated with the following code 
extracts:
 
ServiceFactory serviceFactory = 
ServiceFactory.newInstance();Service webService = 
serviceFactory.createService(wsdlUrl, serviceQName);
Call opCall = webService.createCall(portQName, 
operationName);
Object response = 
opCall.invoke(params);
 
The webservice I'm trying to call is a document 
style, here are the parts of the wsdl relevant to the input 
messages
 
 
 xmlns="urn:TransactionTypesWs" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="urn:TransactionTypesWs" xmlns:intf="urn:TransactionTypesWs" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">  
      
      
  
    
    
    
    
    
    
  
    
  
  
    ...    
      
    
  

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

 
So the service is expection an input message with a 
soap body that looks like this

  
    
...
    
...
    
...
    
...
    
...
    
...
  

 
I've worked out that to have axis format my input 
as a proper document style soap message rather than escape the xml and make it a 
string parameter, I should invoke the call with an org.w3c.dom.Document object 
as the parameter.  However, if I build a document object from xml with the 
 tag as it's root element, when incorparates it into the soap 
message, there is an extra set of  tags, presumably 
auto-generated by axis based on what's in the wsdl file, so the end message 
looks like

  
    
  
...
  ...
    
  

 
The fact that axis has automatically inserted one 
set of  tags made me think that I should only enter the child 
elements of .  However, because the method is specified as 
only requiring one parameter, passing in the six child elements as separate 
org.w3c.dom.Element objects causes an axis fault for providing the 
wrong number of parameters.  And the only way I know of to combine them 
into one object is to make a Document object but that can't be done unless there 
is one root element surrounding the six, which puts me back to where I 
started.
 
Can anyone help?  How can I get the correct 
input into axis to generate the correctly formatted soap message?  As I 
said, this is a generic web service client and I have several other document 
style services to integrate with which are going to cause the same 
problem so generating bespoke code for each new web service isn't a 
viable option.  I'll be eternally grateful if there's an easy answer 
to this, thanks.
Chris MannionIT Junction020 8452 
4274

[Axis2] In which version do you plan to support exception generation for faults?

Dear Axis2 developers,As far as I know, code generator of 0.94 does not generate exceptions for faults defined in WSDL. Instead, we are required to throw AxisFault.Do you have a plan to add this support to 0.95? Or, in which version do you plan to support?Regards,Ali Sadik Kumlali
		 Yahoo! Mail 
Use Photomail to share photos without annoying attachments.

Re: [Axis2] Handling request-responseS type messaging

Thank you Anne. But, AFAIK, WSDL does not support IN-Multiple OUT as operation type. If WSDL does not has signature for multiple results, how can client assume that it must wait for more than one results?Thanks a lot,Ali Sadik KumlaliAnne Thomas Manes <[EMAIL PROTECTED]> wrote: Ali,   Do you mean;  1) Client sends request without waiting a response to it. Request has a CSV tag which has many lines to process.  2) Server processes the message and sends a result for each line in  CS  V. It  sends results to the client without waiting a response.Yes. (Or alternatively, each message exchange could return an "ack", which would be easier to implement if you're using Axis 1.)Anne On 3/16/06, Al
 i Sadik
 Kumlali <[EMAIL PROTECTED]> wrote: Hi Eran, Hi Anne!What a quick response! What a good community! Thank you very very much.  I love this community and  hope companies discover the power of  open-source products. I post your responses to my colleagues in the  company to let them recognize that support does not always mean money,  and vice versa :) Eran,Our current implementation uses DocSoap XDK based custom codes. Since  we are required to handle all the soap related stuff manually, we are  able to support  "IN-multiple OUT" type messaging. Actually,  manual operations are one of the reasons we want to give DocSoap XDK  up. Therefore, it would be great if I could find a robust way in Axis2  to support "IN-multiple
  OUT"
 type messaging. Anne,Do you mean;  1) Client sends request without waiting a response to it. Request has a CSV tag which has many lines to process.  2) Server processes the message and sends a result for each line in  CS  V. It  sends results to the client without waiting a response.Many thanks to you both!Ali Sadik Kumlali  Anne Thomas Manes < [EMAIL PROTECTED]> wrote:   You can also  implement the pattern using one-way messages.Anne On 3/16/06, Eran Chinthaka <[EMAIL PROTECTED]  > wrote:  Hi Ali,Interesting scenario.First of all, Axis2 supports IN only and IN-OUT invocations by  *default.* But thats doesn't mean we can not do IN-multiple OUT meps.Yes, we haven't come across them so far, but our pipe model enables custom MEPs. If you really ne  ed this  we can give a  try to implement the  first custom MEP using Axi
 s2. (or
 you can convince your boss otherwise ;-) )-- Chinthaka Ali Sadik Kumlali wrote:> Dear all,>> There is an interesting messaging pattern between my company  > and its partner. Partner sends a message containing a tag named> CSV that has multiple lines in it. Although we process all of them > separately, we assume it as one message. After processing has  > been completed, we send a result message for every line in CSV.> Thus, request-responseS type messaging occurs.>> This seems very strange when I look at the async messaging > samples that come with Axis2. If I understand correctly, when  > client sends a request in an async-non blocker way, it also> starts an http server to listen response. When the server finishes> processing, it sends the result back to the client's http server.   >  Consequently, each request has one response.>> AFAIK, we a
 re
 allowed to have one-way and request-response> type operations, but not request-responseS.>> Is there a way to handle request-responseS type messaging   > with Axis2? Or do I ne ed to convince my boss to give these kind> of messaging up? :)>> Thanks a lot,>> Ali Sadik Kumlali>>    > Yahoo! Mail> Bring photos to life! New PhotoMail> < http://pa.yahoo.com/*http://us.rd.yahoo.com/evt=39174/*http://photomail.mail.yahoo.com  >> makes sharing a breeze.   Yahoo! Mail  Use Photomail to share photos without annoying attachments.  
		Yahoo! Mail
Bring photos to life! New PhotoMail  makes sharing a breeze.

Re: [Axis2] Handling request-responseS type messaging

Ali,   Do you mean;  1) Client sends request without waiting a response to it. Request has a CSV tag which has many lines to process.  2) Server processes the message and sends a result for each line in  CS
 V. It
 sends results to the client without waiting a response.Yes. (Or alternatively, each message exchange could return an "ack", which would be easier to implement if you're using Axis 1.)Anne
On 3/16/06, Ali Sadik Kumlali <[EMAIL PROTECTED]> wrote:
Hi Eran, Hi Anne!What a quick response! What a good community! Thank you very very much.  I love this community and  hope companies discover the power of  open-source products. I post your responses to my colleagues in the  company to let them recognize that support does not always mean money,  and vice versa :)
Eran,Our current implementation uses DocSoap XDK based custom codes. Since  we are required to handle all the soap related stuff manually, we are  able to support  "IN-multiple OUT" type messaging. Actually,  manual operations are one of the reasons we want to give DocSoap XDK  up. Therefore, it would be great if I could find a robust way in Axis2  to support "IN-multiple OUT" type messaging.
Anne,Do you mean;  1) Client sends request without waiting a response to it. Request has a CSV tag which has many lines to process.  2) Server processes the message and sends a result for each line in  CS
 V. It
 sends results to the client without waiting a response.Many thanks to you both!Ali Sadik Kumlali  Anne Thomas Manes <
[EMAIL PROTECTED]> wrote:
  You can also  implement the pattern using one-way messages.Anne
On 3/16/06, Eran Chinthaka <[EMAIL PROTECTED]  > wrote:

Hi Ali,Interesting scenario.First of all, Axis2 supports IN only and IN-OUT invocations by  *default.* But thats doesn't mean we can not do IN-multiple OUT meps.Yes, we haven't come across them so far, but our pipe model enables
custom MEPs. If you really ne
 ed this
 we can give a  try to implement the  first custom MEP using Axis2. (or you can convince your boss otherwise ;-) )-- Chinthaka
Ali Sadik Kumlali wrote:> Dear all,>> There is an interesting messaging pattern between my company  > and its partner. Partner sends a message containing a tag named> CSV that has multiple lines in it. Although we process all of them
> separately, we assume it as one message. After processing has  > been completed, we send a result message for every line in CSV.> Thus, request-responseS type messaging occurs.>> This seems very strange when I look at the async messaging
> samples that come with Axis2. If I understand correctly, when  > client sends a request in an async-non blocker way, it also> starts an http server to listen response. When the server finishes> processing, it sends the result back to the client's http server.
  >
 Consequently, each request has one response.>> AFAIK, we are allowed to have one-way and request-response> type operations, but not request-responseS.>> Is there a way to handle request-responseS type messaging  
> with Axis2? Or do I ne ed to convince my boss to give these kind> of messaging up? :)>> Thanks a lot,>> Ali Sadik Kumlali>>   
> Yahoo! Mail> Bring photos to life! New PhotoMail> <
http://pa.yahoo.com/*http://us.rd.yahoo.com/evt=39174/*http://photomail.mail.yahoo.com  >> makes sharing a breeze.

		 Yahoo! Mail 
Use Photomail to share photos without annoying attachments.

Re: Axis 1.3 document literal and no parts in the message

The WSDL 1.1 spec has a bunch of errors in it. (It's not a formal standard, after all.) The WS-I Basic Profile clarifies these errors. See section 4.4 [1] for clarifications related to messages and parts. To whit:

R2201

A document-literal binding in a DESCRIPTION MUST, in each of its soapbind:body element(s), have
at most one part listed in the parts attribute, if the parts attribute is specified. Zero parts is permitted. Assuming that your getAllSectors operation is defined as document/literal, Axis should not insert the remote.ws.mycompany.org"/> element into the SOAP Body. The Body should be empty. Axis should insert the method name element only if the operation is defined as rpc style.
[1] http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html#WSDLMSGS AnneOn 3/16/06,
Lars Torunski <[EMAIL PROTECTED]> wrote:
I got stuck in a discussion between two consultants if Axis 1.3 fulfills the WSDL 1.1 specification for document/literal correctly.Consultant 1:Taken from http://www.w3.org/TR/wsdl#_messages
(2.3 Messages) the message is defined by "Messages consist of one or more logical parts.".Consultant 2:On the other hand the WSDL schema definition in http://www.w3.org/TR/wsdl#A4.1
defines "wsdl:part" with Consultant 1:This maybe contradictory, but this is because WSDL may use either by "rpc" or "document" styles. Per RPC, of course, may be without any . Unfortunately, this is not the case with "document" style. For "document" style only the are sent. No other leading information is used. Thus, the inner message-parts in this case are must. One MUST NOT discard message-parts when "document" style is used.
Me:We have a message "getAllSectors" defined as Thus, no is defined. Axis 1.3 create the following http request:
http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="
http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">remote.ws.mycompany.org"/>What do you think? Is there a problem in our wsdl file or is this a bug in Axis 1.3 by using document/literal?

Re: frenzy trying to build axis2

This is bad...Anyway, I've downloaded the code from svn and tried to build it. One more time I got the same problem, now for the WSDL module (see erro below).multiproject:install-callback:    [echo] Running jar:install for Apache Axis 
2.0 - WSDLjava:prepare-filesystem:    [mkdir] Created dir: C:\Documents and Settings\Loreno Oliveira\My Documents\Projetos\axis2\axis2\modules\wsdl\target\classesjava:compile:    [echo] Compiling to C:\Documents and Settings\Loreno Oliveira\My Documents\Projetos\axis2\axis2\modules\wsdl/target/classe
s    [javac] Compiling 89 source files to C:\Documents and Settings\Loreno Oliveira\My Documents\Projetos\axis2\axis2\modules\wsdl\target\classes    [javac] javac: invalid flag: C:\Documents    [javac] Usage: javac  
    [javac] where possible options include:    [javac]   -g Generate all debugging info    [javac]   -g:none    Generate no debugging info    [javac]   -g:{lines,vars,source} Generate only some debugging info
    [javac]   -nowarn    Generate no warnings    [javac]   -verbose   Output messages about what the compiler is doing    [javac]   -deprecation   Output source locations where deprecated APIs are used
    [javac]   -classpath   Specify where to find user class files    [javac]   -cp  Specify where to find user class files    [javac]   -sourcepath  Specify where to find input source files
    [javac]   -bootclasspath   Override location of bootstrap class files    [javac]   -extdirs     Override location of installed extensions    [javac]   -endorseddirs    Override location of endorsed standards path
    [javac]   -d  Specify where to place generated class files    [javac]   -encoding    Specify character encoding used by source files    [javac]   -source   Provide source compatibility with specified release
    [javac]   -target   Generate class files for specific VM version    [javac]   -version   Version information    [javac]   -help  Print a synopsis of standard options
    [javac]   -X Print a synopsis of nonstandard options    [javac]   -J   Pass  directly to the runtime system    [javac]BUILD FAILED
File.. C:\Documents and Settings\Loreno Oliveira\.maven\cache\maven-multiproject-plugin-1.3.1\plugin.jellyElement... maven:reactorLine.. 217Column 9Unable to obtain goal [multiproject:install-callback] -- C:\Documents and Settings\Loreno Oliveira\.maven\cache\maven-java-plu
gin-1.5\plugin.jelly:63:48:  Compile failed; see the compiler error output for details.Total time: 11 secondsFinished at: Fri Mar 17 10:34:35 BRT 2006Of course, this is easy to fix. I've only moved the project folder to the root (c:\axis2). However, I'm still curious to know what is the problem. That is, why does some modules are built normaly and others doesn't??
In time, one more question. Is it safe to use and change do code downloaded from svn?? That is, I understand it's a code under constant changes. Thus, it may be possible to have some inconsistency on it??[]'s
LorenoOn 3/17/06, robert <[EMAIL PROTECTED]> wrote:
The .94 sources don't build :-(http://marc.theaimsgroup.com/?l=axis-dev&m=113936664324887&w=2HTH,Robert
http://www.braziloutsource.com/Em Sexta 17 Março 2006 09:48, o Loreno Oliveira escreveu:> The version I'm trying to build is the standard 0.94, downloaded as a zip> from 
http://ws.apache.org/axis2/download.cgi>> Loreno>> On 3/17/06, Ajith Ranabahu <[EMAIL PROTECTED]> wrote:> > Hmm...> > We no longer have the XML Module and it seems that you are using a
> > pretty old codebase. Have a go with the latest codebase!> >> > Ajith> >> > On 3/17/06, Loreno Oliveira <[EMAIL PROTECTED]
> wrote:> > > I'm still trying to buid axis2 (I know sometime I'll attain it :-) ).> > > Now the problem is the way maven builds diferent modules. That is, axis> >> > is
> >> > > in the folder "C:\Documents and Settings\Loreno Oliveira\My> > > Documents\Projetos\axis2". When I start a complete build (for all the> > > modules), the first module (Common) is built without any issue.
> > > But in the following module (XML) I got the error below:> > >> > > [javac] Compiling 134 source files to C:\Documents and> >> > Settings\Loreno> >
> > > Oliveira\My Documents\Projetos\axis2\modules\xml\ta> > > rget\classes> > > [javac] javac: invalid flag: C:\Documents> > > [javac] Usage: javac  
> > > [javac] where possible options include:> > > [javac]   -g Generate all debugging info> > > [javac]   -g:noneGenerate no debugging info
> > > [javac]   -g:{lines,vars,source} Generate only some debugging> >> > info> >> > > [javac]   -nowarnGenerate no warnings> > > [javac]   -verbose   Output messages about what the
> > > compiler is doing> > > [

Re: WSDL related

Retrieve the WSDL via the browser.Copy and paste it into an editor.Make appropriate changes.Save it.Redploy the service using the modified WSDL.On 3/17/06, 
Sandip Wadkar <[EMAIL PROTECTED]> wrote:

















Hi Anne,

 

Thanks for reply.

 

I know how to retrieve WSDL content on
browser.  Could you please explain the steps for wsdl updating because I am
not able to get the physical location of wsdl file.

 

 

Sandip



---


CCWLL Services Dev Group | Zensar-Cisco ODC 
| (D) +91 (020) 5609 8245 

 

Don't worry about the
world coming to an end today. It's already tomorrow in Australia
 

  

 











From: Anne Thomas
Manes [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, March 16, 2006
6:36 PM
To: axis-user@ws.apache.org
Subject: Re: WSDL related



 

You can retrieve your
WSDL by appending "?wsdl" to the end of the endpoint URL. Then you
can modify the endpoint URL, save it, and redeploy the service with the new URL
by specifying [wsdl-url]

Anne



On 3/16/06, Sandip
Wadkar <[EMAIL PROTECTED]>
wrote:





Hi
Team,

 

I
am supporting one Axis Webservice based application, for some enhancement I
need to change WebService related URL in WSDL file.

And
for reason I don't have script/options to know how the earlier WSDL file has
been created.

Could
you please let me know that is there any way to edit the same WSDL file to
resolve my purpose?

 

Thanks
in advance.

Sandip

---



CCWLL Services Dev Group
 | Zensar-Cisco
ODC | (D) +91 (020) 5609 8245 

 

Don't worry about the world coming to an end
today. It's already tomorrow in Australia

Re: frenzy trying to build axis2

The .94 sources don't build :-( 

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

HTH,
Robert
http://www.braziloutsource.com/

Em Sexta 17 Março 2006 09:48, o Loreno Oliveira escreveu:
> The version I'm trying to build is the standard 0.94, downloaded as a zip
> from http://ws.apache.org/axis2/download.cgi
>
> Loreno
>
> On 3/17/06, Ajith Ranabahu <[EMAIL PROTECTED]> wrote:
> > Hmm...
> > We no longer have the XML Module and it seems that you are using a
> > pretty old codebase. Have a go with the latest codebase!
> >
> > Ajith
> >
> > On 3/17/06, Loreno Oliveira <[EMAIL PROTECTED]> wrote:
> > > I'm still trying to buid axis2 (I know sometime I'll attain it :-) ).
> > > Now the problem is the way maven builds diferent modules. That is, axis
> >
> > is
> >
> > > in the folder "C:\Documents and Settings\Loreno Oliveira\My
> > > Documents\Projetos\axis2". When I start a complete build (for all the
> > > modules), the first module (Common) is built without any issue.
> > > But in the following module (XML) I got the error below:
> > >
> > > [javac] Compiling 134 source files to C:\Documents and
> >
> > Settings\Loreno
> >
> > > Oliveira\My Documents\Projetos\axis2\modules\xml\ta
> > > rget\classes
> > > [javac] javac: invalid flag: C:\Documents
> > > [javac] Usage: javac  
> > > [javac] where possible options include:
> > > [javac]   -g Generate all debugging info
> > > [javac]   -g:noneGenerate no debugging info
> > > [javac]   -g:{lines,vars,source} Generate only some debugging
> >
> > info
> >
> > > [javac]   -nowarnGenerate no warnings
> > > [javac]   -verbose   Output messages about what the
> > > compiler is doing
> > > [javac]   -deprecation   Output source locations where
> > > deprecated APIs are used
> > > [javac]   -classpath   Specify where to find user
> >
> > class
> >
> > > files
> > > [javac]   -cp  Specify where to find user
> >
> > class
> >
> > > files
> > > [javac]   -sourcepath  Specify where to find input
> >
> > source
> >
> > > files
> > > [javac]   -bootclasspath   Override location of bootstrap
> > > class files
> > > [javac]   -extdirs Override location of installed
> > > extensions
> > > [javac]   -endorseddirsOverride location of endorsed
> > > standards path
> > > [javac]   -d  Specify where to place
> >
> > generated
> >
> > > class files
> > > [javac]   -encodingSpecify character encoding
> > > used
> >
> > by
> >
> > > source files
> > > [javac]   -source   Provide source compatibility
> >
> > with
> >
> > > specified release
> > > [javac]   -target   Generate class files for
> >
> > specific
> >
> > > VM version
> > > [javac]   -version   Version information
> > > [javac]   -help  Print a synopsis of standard
> > > options
> > > [javac]   -X Print a synopsis of
> > > nonstandard options
> > > [javac]   -J   Pass  directly to the
> >
> > runtime
> >
> > > system
> > > [javac]
> > >
> > > BUILD FAILED
> > > File.. C:\Documents and Settings\Loreno
> > > Oliveira\.maven\cache\maven-multiproject-plugin-1.3.1\plugin.jelly
> > > Element... maven:reactor
> > > Line.. 217
> > > Column 9
> > > Unable to obtain goal [multiproject:install-callback] -- C:\Documents
> >
> > and
> >
> > > Settings\Loreno Oliveira\.maven\cache\maven-java-plu
> > > gin-1.5\plugin.jelly:63:48:  Compile failed; see the
> > > compiler error output for details.
> > > Total time: 9 seconds
> > > Finished at: Thu Mar 16 17:16:30 BRT 2006
> > >
> > > The line "[javac] javac: invalid flag: C:\Documents" makes me
> >
> > believe
> >
> > > the path is being splited into tokens. My questions are:
> > > 1- am I doing something wrong??
> > > 2- why does the build works fine for the Common module and doesn't for
> >
> > the
> >
> > > XML module??
> > >
> > > Thanks for any help!
> > >
> > > []'s
> > >
> > > Loreno
> >
> > --
> > Ajith Ranabahu

--

Re: No scheme found in URI.

2006-03-17 Thread Luca Albertazzi





I found where the problem occurs:

The response object  (_resp)
contains an object of type 'org.apache.axis.types.URI'. The web service
I invoke (wich is written in C#) valorizes the field corresponding to
that object with an 'UNC' value like this:
'\\192.168.1.103\c$\temp\6a165c0f869d4741b991973d202cf0ca', wich causes
the MalformedURIException during the deserialization.

Can we say that is a bug of the class org.apache.axis.types.URI? Is
that problem resolved in Axis 2.0?

Thank you,

Luca






Luca Albertazzi ha scritto:

  
  
Hello,
    I have made a client starting from a given Wsdl using WSDL2Java
tool but invoking the web service.
The exception occurs in the stub created by the tool during the
_call.invoke(..) operation:
  
    
_call.setOperationName(new
javax.xml.namespace.QName("http://www.mps.it/MultiChannel/",
"RegisterDocument"));
  
    setRequestHeaders(_call);
    setAttachments(_call);
 try {    java.lang.Object _resp = _call.invoke(new
java.lang.Object[] {documentId, flowName, documentSize, documentHash,
properties, supportedChannels, callbackUrl});
  
    if (_resp instanceof java.rmi.RemoteException) {
    throw (java.rmi.RemoteException)_resp;
    }
    else {
    extractAttachments(_call);
    try {
    return (it.mps.www.MultiChannel.ChannelDefinition)
_resp;
    } catch (java.lang.Exception _exception) {
    return (it.mps.www.MultiChannel.ChannelDefinition)
org.apache.axis.utils.JavaUtils.convert(_resp,
it.mps.www.MultiChannel.ChannelDefinition.class);
    }
    }
  } catch (org.apache.axis.AxisFault axisFaultException) {
  throw axisFaultException;
  
Each time I execute the service I get the error wich follows:
  
- Exception:
org.apache.axis.types.URI$MalformedURIException: No scheme found in URI.
    at
org.apache.axis.encoding.ser.SimpleDeserializer.onEndElement(SimpleDeserializer.java:180)
    at
org.apache.axis.encoding.DeserializerImpl.endElement(DeserializerImpl.java:502)
    at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
    at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:171)
    at
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
    at
org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
    at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
    at org.apache.axis.client.Call.invoke(Call.java:2467)
    at org.apache.axis.client.Call.invoke(Call.java:2366)
    at org.apache.axis.client.Call.invoke(Call.java:1812)
    at
it.mps.www.MultiChannel.MultiChannelWSSoapStub.registerDocument(MultiChannelWSSoapStub.java:283)
    at
com.cedac.webservices.test.TestMultiChannelWS.main(TestMultiChannelWS.java:42)
AxisFault
 faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode: 
 faultString: org.apache.axis.types.URI$MalformedURIException: No
scheme found in URI.
 faultActor: 
 faultNode: 
 faultDetail: 
   
{http://xml.apache.org/axis/}stackTrace:org.apache.axis.types.URI$MalformedURIException:
No scheme found in URI.
    at
org.apache.axis.encoding.ser.SimpleDeserializer.onEndElement(SimpleDeserializer.java:180)
    at
org.apache.axis.encoding.DeserializerImpl.endElement(DeserializerImpl.java:502)
    at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
    at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:171)
    at
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
    at
org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
    at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
    at org.apache.axis.client.Call.invoke(Call.java:2467)
    at org.apache.axis.client.Call.invoke(Call.java:2366)
    at org.apache.axis.client.Call.invoke(Call.java:1812)
    at
it.mps.www.MultiChannel.MultiChannelWSSoapStub.registerDocument(MultiChannelWSSoapStub.java:283)
    at
com.cedac.webservices.test.TestMultiChannelWS.main(TestMultiChannelWS.java:42)
  
    {http://xml.apache.org/axis/}hostname:WALLACE
  
org.apache.axis.types.URI$MalformedURIException: No scheme found in URI.
    at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
    at org.apache.axis.client.Call.invoke(Call.java:2470)
    at org.apache.axis.client.Call.invoke(Call.java:2366)
    at org.apache.axis.client.Call.invoke(Call.java:1812)
    at
it.mps.www.MultiChannel.MultiChannelWSSoapStub.registerDocument(MultiChannelWSSoapStub.java:283)
    at
com.cedac.webservices.test.TestMultiChannelWS.main(TestMultiChannelWS.java:42)
Caused by: org.apache.axis.types.URI$MalformedURIException: No scheme
found in URI.
    at
org.apache.axis.encoding.ser.SimpleDeserializer.onEndElement(SimpleDeserializer.java:180)
    at
org.apache.axis.encoding.DeserializerImpl.endElement(DeserializerImpl.java:502)
    at
org.apache.axis.encoding.

Re: [0.94] How can i shutdown connection after call

Your makeCall() method has a reference to serviceClient. 

HTH,
Robert
http://www.braziloutsource.com/

Em Sexta 17 Março 2006 06:55, o Filipp Akinfiev escreveu:
> the method finalizeInvoke(MessageContent) or finalize() is not visible from
> my class...
>
> Am Freitag 17 März 2006 05:10 schrieb Deepal Jayasinghe:
> > you can call;
> >
> > serviceClient.finalizeInvoke();
> >
> > Filipp Akinfiev wrote:
> > >Hi all,
> > >in my client class  i have function like :
> > >  public TFileSendResponse storeFile(int type, String fileName, String
> > >pathToFile) {
> > >   TFileSendResponse response = null;
> > >   try {
> > >   response = 
> > > FileSend.response(makeCall(FileSend.request(new
> > > TFileSend("", "", type, fileName, pathToFile)), "storeFile"));
> > >   } catch (Exception e) {
> > >   e.printStackTrace();
> > >   }
> > >   return response;
> > >   }
> > >
> > >it's call function makeCall:
> > >
> > >private MessageContext makeCall(MessageContext requestContext,
> > > String action) {
> > >   ServiceClient client;
> > >   MessageContext result = null;
> > >   try {
> > >   // creating the Service
> > >   AxisService service = new AxisService("IXMLWS2");
> > >
> > >   // creating the operations
> > >   AxisOperation operation = new OutInAxisOperation();
> > >   operation.setName(new
> > >javax.xml.namespace.QName("urn:XMLWSIntf-IXMLWS", action));
> > >   service.addOperation(operation);
> > >   client = new ServiceClient(new
> > >ConfigurationContextFactory().createConfigurationContextFromFileSystem(A
> > >XI S2_HOME), service);
> > >   client.getOptions().setTo(targetEPR);
> > >   
> > > client.getOptions().setSoapAction("urn:XMLWSIntf2-IXMLWS2#" +
> > > action); client.getOptions().setExceptionToBeThrownOnSOAPFault(true);
> > > client.getOptions().setTransportInProtocol(Constants.TRANSPORT_TCP);
> > >
> > >client.getOptions().setProperty(org.apache.axis2.context.MessageContextC
> > >on stants.CHUNKED,org.apache.axis2.Constants.VALUE_FALSE);
> > > client.getOptions().setProperty(Constants.Configuration.ENABLE_MTOM,
> > > Constants.VALUE_TRUE);
> > >
> > >   OperationClient opClient = client.createClient(new
> > >javax.xml.namespace.QName("urn:XMLWSIntf-IXMLWS", action));
> > >
> > >   opClient.addMessageContext(requestContext);
> > >   opClient.execute(true);
> > >
> > >   return
> > > opClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE); }
> > > catch (AxisFault e) {
> > >   e.printStackTrace();
> > >   }
> > >   return result;
> > >}
> > >
> > >after execute, i have open connection to axis server, how can i
> > > terminate it ?
> > >
> > >thanks in advance!

--

Re: frenzy trying to build axis2

The version I'm trying to build is the standard 0.94, downloaded as a zip from http://ws.apache.org/axis2/download.cgiLoreno
On 3/17/06, Ajith Ranabahu <[EMAIL PROTECTED]> wrote:
Hmm...We no longer have the XML Module and it seems that you are using apretty old codebase. Have a go with the latest codebase!AjithOn 3/17/06, Loreno Oliveira <
[EMAIL PROTECTED]> wrote:> I'm still trying to buid axis2 (I know sometime I'll attain it :-) ).> Now the problem is the way maven builds diferent modules. That is, axis is> in the folder "C:\Documents and Settings\Loreno Oliveira\My
> Documents\Projetos\axis2". When I start a complete build (for all the> modules), the first module (Common) is built without any issue.> But in the following module (XML) I got the error below:
>> [javac] Compiling 134 source files to C:\Documents and Settings\Loreno> Oliveira\My Documents\Projetos\axis2\modules\xml\ta> rget\classes> [javac] javac: invalid flag: C:\Documents
> [javac] Usage: javac  > [javac] where possible options include:> [javac]   -g Generate all debugging info> [javac]   -g:noneGenerate no debugging info
> [javac]   -g:{lines,vars,source} Generate only some debugging info> [javac]   -nowarnGenerate no warnings> [javac]   -verbose   Output messages about what the
> compiler is doing> [javac]   -deprecation   Output source locations where> deprecated APIs are used> [javac]   -classpath   Specify where to find user class
> files> [javac]   -cp  Specify where to find user class> files> [javac]   -sourcepath  Specify where to find input source> files
> [javac]   -bootclasspath   Override location of bootstrap> class files> [javac]   -extdirs Override location of installed> extensions> [javac]   -endorseddirs    Override location of endorsed
> standards path> [javac]   -d  Specify where to place generated> class files> [javac]   -encoding    Specify character encoding used by
> source files> [javac]   -source   Provide source compatibility with> specified release> [javac]   -target   Generate class files for specific
> VM version> [javac]   -version   Version information> [javac]   -help  Print a synopsis of standard> options> [javac]   -X Print a synopsis of nonstandard
> options> [javac]   -J   Pass  directly to the runtime> system> [javac]>> BUILD FAILED> File.. C:\Documents and Settings\Loreno
> Oliveira\.maven\cache\maven-multiproject-plugin-1.3.1\plugin.jelly> Element... maven:reactor> Line.. 217> Column 9> Unable to obtain goal [multiproject:install-callback] -- C:\Documents and
> Settings\Loreno Oliveira\.maven\cache\maven-java-plu> gin-1.5\plugin.jelly:63:48:  Compile failed; see the compiler> error output for details.> Total time: 9 seconds> Finished at: Thu Mar 16 17:16:30 BRT 2006
>> The line "[javac] javac: invalid flag: C:\Documents" makes me believe> the path is being splited into tokens. My questions are:> 1- am I doing something wrong??> 2- why does the build works fine for the Common module and doesn't for the
> XML module??>> Thanks for any help!>> []'s>> Loreno>--Ajith Ranabahu

Re: Axis0.94: Modifying envelope right before sending?

Instead of placing info into the MessageContext at the stub level, what you 
could do is write a Module and a Handler that would be placed at the end of 
the phaseOrder on the client side. Then you could add headers there. That way 
you should be ok with whatever Axis2 puts into the header - now and in the 
future. 

BTW, I believe WSS4J already handles that case (I've only done WS-Securtity 
with Axis 1.x) . 

Another point is that you can turn off ws-addressing if you don't need it - 
but then you would have to be careful on what else may be placed into the 
header. 

HTH,
Robert
http://www.braziloutsource.com/ 

Em Sexta 17 Março 2006 07:12, o Gaël Pouzerate escreveu:
> Hi,
>
> I'm using Axis 0.94. I want to be able to modify the soap envelope right
> before it's sent by OperationClient.execute();
> How can I get access to the envelope from the OperationClient object? I
> thought the getMessageContext() would enable this but what parameter should
> I use?
>
> My exact need is to sign the envelope (add some signature in the header)
> right before it's sent: The signature is based on the content of the
> envelope, so that once the envelope is signed, it mustnt' be changed
> anymore.
>
> I've been trying to do it the following way, but it seems that axis adds
> extra stuff (wsa: tags) in the header before sending the envelope, so that
> my signature won't be valid anymore. So I'd like to be able to put my
> signature when the envelope is complete (with wsa tags) right before it's
> sent.
>
> Here is an extract of the code:
>
> public class MySearchEndpointStub extends Stub {
> public MyResultsDocument search(
>
> OperationClient _operationClient =
> _serviceClient.createClient(_operations[0].getName());
>
> // The envelope created here only contains a body, but an empty header
> SOAPEnvelope env = toEnvelope(getFactory(_options.getSoapVersionURI()),
> requestDoc);
>
> // Here we add a signature in the envelope's header based on it's current
> content
> env = sign(env);
> MessageContext _messageContext = new MessageContext();
> _messageContext.setEnvelope(env);
> _operationClient.addMessageContext(_messageContext);
>
> // The request is sent: I can see in the soap request (by tracing traffic)
> that some extra stuff have been added
> // in the header: a couple of wsa: tags. So my signature is not valid
> anymore
> _operationClient.execute(true);
> }
>
> Any idea on how I could achieve this?
>
> Thanx!
> Gaël

--

Re: [0.94] - NoSuchMethodError

There was a client refactoring for the .94 version - and looking at the .93 
and .94 sources show that a lot of what was once in 
getMessageInformationHeaders() is now placed into the Options class - now a 
big part of the client side of axis2. 

You're going to need to re-compile against .94 and then refactor to use 
Options. 

BTW, there is expected to be a .95 release hopefully by the end of the month. 
An option you may consider is running the nightly builds until then. 

HTH,
Robert 
http://www.braziloutsource.com/

Em Sexta 17 Março 2006 07:25, o Jens Wolinder escreveu:
> Hey all.
>
> Desperate for help.. Developing an applet which is suppose to send a file
> to a server using mtom.
>
> The problem is this, when calling ServiceClient. sendReceive (OMElement), I
> get a java.lang.NoSuchMethodError from
> org.apache.axis2.context.MessageContext, and the missing method is
> getMessageInformationHeaders().
>
> Checked the javadoc and true enough there is no such method in 0.94, but in
> 0.93 there is. and now I don't know what to do. is there a mismatch in the
> 0.94 release or did I miss something essential??
>
>
>
> Stacktrace:
>
> Exception in thread "Thread-3" java.lang.NoSuchMethodError:
> org.apache.axis2.context.MessageContext.getMessageInformationHeaders()Lorg/
>a pache/axis2/addressing/MessageInformationHeaders;
>
>   at
> org.apache.axis2.handlers.addressing.AddressingOutHandler.invoke(Addressing
>O utHandler.java:56)
>
>   at
> org.apache.axis2.engine.Phase.invoke(Phase.java:376)
>
>   at
> org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:351)
>
>   at
> org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:441)
>
>   at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperati
>o n.java:317)
>
>   at
> org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOper
>a tion.java:267)
>
>   at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:393)
>
>   at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:326)
>
>   at
> se.teknomedia.util.FileTransferHandler.transferFileMtom(FileTransferHandler
>. java:135)
>
>   at
> se.teknomedia.applet.DropZone.startTransfer(DropZone.java:760)
>
>   at
> se.teknomedia.applet.DropZone.run(DropZone.java:658)
>
>   at java.lang.Thread.run(Unknown Source)
>
>
>
> phanx
>
> /jens

--

Re: Axis2 DynamicInvoker

2006-03-17 Thread Srinath Perera

Hi Arnaud;

ServiceClient have a constructor
ServiceClient(ConfigurationContext,wsdlurl); which create a configured
service client. Then you can use that for OM level invocations. But
data binding is not supported.

Srinath

On 3/16/06, Arnaud MERGEY <[EMAIL PROTECTED]> wrote:
> hi,
>
> Is there any plan to include an Axiom DynamicInvoker sample in axis2
> dist like samples.client.DynamicInvoker in Axis ?
>
> thanks,
> Arnaud
>

--

Srinath Perera:
   http://www.cs.indiana.edu/~hperera/
   http://www.bloglines.com/blog/hemapani

Re: Questions about "java:MSG"

Hi Dink,I'm designing the same structure with Axis2 for my project. Although I'm not sure it's the best, I will implement 1th and 2nd as sync and 3th one as async. In this scenario, client must have a listener for the 3th.But I don't know what the "java:MSG" is and how to implement async service with it.Regards,Ali Sadik KumlaliDink <[EMAIL PROTECTED]> wrote: Thanks for your reply. What you draw is really my  case.   Message 
 1.  request    Client > ServerMessage  2.  ack response   Client  <--- Server... (time passes)         actual  resultMessage 3. Client <---  Server   I have thought of two kinds of  situation for the above case. The first situation, I regard the  message 1 and 2 as the synchronous message pattern  and the message 3 is the  asynchronous one.  The second situation, I regard the three messages
 as the asynchronous messages.  I don't know which kind of situation is suitable for my  case.    Besides, I don't know if the "java:MSG" provider  programming mode I used can fulfill the asynchronous case. If it  can not achieve the asynchronous transmission, how can I do  that?   Regards,   Dink  Lo- Original Message -From:Ali SadikKumlaliTo: axis-user@ws.apache.orgSent: Friday, March 17, 2006 5:59 PM   Subject: Re: Questions about"java:MSG"   Hi Dink,Just to make it clear, do youmean;  requestClient > Serverack responseClient <--- Server...(time passes)actual resultClient <---ServerIf this the your case, it has some asynchronousprocess logic. So, that might be your startingpoint.Regards,Ali Sadik KumlaliDink<[EMAIL PROTECTED]> wrote:   Hello, I need to develop a client and a web service to accomplish  some message exchange. Th
 e
 message exchange pattern is as follows: 1. The client sends an XML document to the web service to  do some request. 2. The web service returns an XML document to notify the  client that the request sent by the client is received and being  processed. 3. The web service has finished the request and return the  result to the client.   I have used the "provider=java:MSG" style to develop the  web service to handle the incoming message. But when I think of how to reach the step 3, I  can't find any method signature provided by axis to do  it.   The method signatures provided by axis are:   public Element [] method(Element []  bodies);public  SOAPBodyElement [] method (SOAPBodyElement []  bodies);public  Document method(Document body);public void method(SOAPEnvelope req,  SOAPEnvelope resp);    Every method looks like a simultaneous method except the  fourth one. The simultaneous method I mean is that the client sends a  request to the web service and receives a response from the  service. I think the methods provided by java:MSG can't fulfill  my full requirements.  Can somebody point me some directions to solve the  problem? Thanks,   Dink Lo Yahoo! MailBring photos to life! NewPhotoMail makes sharing a breeze. 
		 Yahoo! Mail 
Use Photomail to share photos without annoying attachments.

RE: WSDL related

2006-03-17 Thread Sandip Wadkar









Hi Anne,

 

Thanks for reply.

 

I know how to retrieve WSDL content on
browser.  Could you please explain the steps for wsdl updating because I am
not able to get the physical location of wsdl file.

 

 

Sandip



---

CCWLL Services Dev Group | Zensar-Cisco ODC | (D) +91 (020) 5609 8245 

 

Don't worry about the
world coming to an end today. It's already tomorrow in Australia 

  

 











From: Anne Thomas
Manes [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 16, 2006
6:36 PM
To: axis-user@ws.apache.org
Subject: Re: WSDL related



 

You can retrieve your
WSDL by appending "?wsdl" to the end of the endpoint URL. Then you
can modify the endpoint URL, save it, and redeploy the service with the new URL
by specifying [wsdl-url]

Anne



On 3/16/06, Sandip
Wadkar <[EMAIL PROTECTED]>
wrote:





Hi
Team,

 

I
am supporting one Axis Webservice based application, for some enhancement I
need to change WebService related URL in WSDL file.

And
for reason I don't have script/options to know how the earlier WSDL file has
been created.

Could
you please let me know that is there any way to edit the same WSDL file to
resolve my purpose?

 

Thanks
in advance.

Sandip

---


CCWLL Services Dev Group | Zensar-Cisco
ODC | (D) +91 (020) 5609 8245 

 

Don't worry about the world coming to an end
today. It's already tomorrow in Australia

Re: Questions about "java:MSG"

2006-03-17 Thread Dink




Thanks for your reply. What you draw is really my 
case.
 
Message 
1.  request   
Client > ServerMessage 
2.  ack response   Client 
<--- Server... (time passes)  
      actual 
resultMessage 3. Client <--- 
Server
 
I have thought of two kinds of 
situation for the above case.
The first situation, I regard the 
message 1 and 2 as the synchronous message pattern 
and the message 3 is the 
asynchronous one. 
The second situation, I regard the three messages
as the asynchronous messages. 
I don't know which kind of situation is suitable for my 
case.
  
Besides, I don't know if the "java:MSG" provider 
programming mode I used can fulfill the asynchronous case. If it 
can not achieve the asynchronous transmission, how can I do 
that?
 
Regards,
 
Dink 
Lo

  - Original Message - 
  From: 
  Ali Sadik 
  Kumlali 
  To: axis-user@ws.apache.org 
  Sent: Friday, March 17, 2006 5:59 PM
  Subject: Re: Questions about 
  "java:MSG"
  Hi Dink,Just to make it clear, do you 
  mean;   
  requestClient > Server 
  ack responseClient <--- Server... 
  (time passes) 
  actual resultClient <--- 
  ServerIf this the your case, it has some asynchronous 
  process logic. So, that might be your starting 
  point.Regards,Ali Sadik KumlaliDink 
  <[EMAIL PROTECTED]> wrote:
  



Hello,
I need to develop a client and a web service to accomplish 
some message exchange.
The message exchange pattern is as follows:
1. The client sends an XML document to the web service to 
do some request.
2. The web service returns an XML document to notify the 
client that the request sent by the client is received and being 
processed.
3. The web service has finished the request and return the 
result to the client.
 
I have used the "provider=java:MSG" style to develop the 
web service to handle the incoming message.
But when I think of how to reach the step 3, I 
can't find any method signature provided by axis to do 
it.
 
The method signatures provided by axis are:
 
public Element [] method(Element [] 
bodies);public 
SOAPBodyElement [] method (SOAPBodyElement [] 
bodies);public 
Document method(Document body);public void method(SOAPEnvelope req, 
SOAPEnvelope resp); 
 
Every method looks like a simultaneous method except the 
fourth one. The simultaneous method I mean is that the client sends a 
request to the web service and receives a response from the 
service.
I think the methods provided by java:MSG can't fulfill 
my full requirements. 
Can somebody point me some directions to solve the 
problem?
Thanks,
 
Dink Lo
  
  
  Yahoo! MailBring photos to life! New 
  PhotoMail makes sharing a breeze.

[0.94] - NoSuchMethodError

2006-03-17 Thread Jens Wolinder









Hey all…

Desperate
for help.. Developing an applet which is suppose to send a file to a server
using mtom…

The
problem is this, when calling ServiceClient. sendReceive (OMElement), I get a java.lang.NoSuchMethodError from org.apache.axis2.context.MessageContext,
and the missing method is getMessageInformationHeaders()…

Checked
the javadoc and true enough there is no such method in 0.94, but in 0.93 there
is… and now I don’t know what to do… is there a mismatch in
the 0.94 release or did I miss something essential??

 

Stacktrace:

Exception
in thread "Thread-3" java.lang.NoSuchMethodError:
org.apache.axis2.context.MessageContext.getMessageInformationHeaders()Lorg/apache/axis2/addressing/MessageInformationHeaders;

  at
org.apache.axis2.handlers.addressing.AddressingOutHandler.invoke(AddressingOutHandler.java:56)

  at
org.apache.axis2.engine.Phase.invoke(Phase.java:376)

  at
org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:351)

  at
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:441)

  at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:317)

  at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:267)

  at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:393)

  at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:326)

  at
se.teknomedia.util.FileTransferHandler.transferFileMtom(FileTransferHandler.java:135)

  at
se.teknomedia.applet.DropZone.startTransfer(DropZone.java:760)

  at
se.teknomedia.applet.DropZone.run(DropZone.java:658)

  at
java.lang.Thread.run(Unknown Source)

 

phanx

/jens

Axis0.94: Modifying envelope right before sending?

2006-03-17 Thread Gaël Pouzerate

Hi,I'm using Axis 0.94. I want to be able to modify the soap envelope right before it's sent by OperationClient.execute();How can I get access to the envelope from the OperationClient object? I thought the getMessageContext() would enable this but what parameter should I use?
My exact need is to sign the envelope (add some signature in the header) right before it's sent: The signature is based on the content of the envelope, so that once the envelope is signed, it mustnt' be changed anymore.
I've been trying to do it the following way, but it seems that axis adds extra stuff (wsa: tags) in the header before sending the envelope, so that my signature won't be valid anymore. So I'd like to be able to put my signature when the envelope is complete (with wsa tags) right before it's sent.
Here is an extract of the code:public class MySearchEndpointStub extends Stub {    public MyResultsDocument search(OperationClient _operationClient = _serviceClient.createClient(_operations[0].getName());
// The envelope created here only contains a body, but an empty headerSOAPEnvelope env = toEnvelope(getFactory(_options.getSoapVersionURI()), requestDoc);// Here we add a signature in the envelope's header based on it's current content
env = sign(env);MessageContext _messageContext = new MessageContext();_messageContext.setEnvelope(env);_operationClient.addMessageContext(_messageContext);// The request is sent: I can see in the soap request (by tracing traffic) that some extra stuff have been added
// in the header: a couple of wsa: tags. So my signature is not valid anymore_operationClient.execute(true);}Any idea on how I could achieve this?Thanx!Gaël

Re: Questions about "java:MSG"