Semantic

2008-10-02 Thread Demetris G


Hi all,

   is there an automated tool you know of that can semantically query
Axis engines for services?

Thanks


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



Re: axiom VS data-binding?

2008-10-02 Thread Steve Cohen

keith chapman wrote:

no anytypes anywhere in the WSDL.

WSDL is here, check it out yourself: 
https://duoshare.com/dsWS/services/PostML/wsdl
The main problem with it, as I see are the huge number of elements.  
There are probably better ways to arrange it.


I guess my question was meant to be more general: 
Do people use Axiom Instead of or In addition to WSDL2Java generated 
code for the client side?  Does it make sense to use Axiom on the 
request but generated classes on the response?  What works well, what 
doesn't?  That is what I want to know.

Oops I means OMElement (not IMElement ;)).


On Fri, Oct 3, 2008 at 6:53 AM, keith chapman <[EMAIL PROTECTED] 
> wrote:


Can you post a snippet of your types section. I wonder whether
they all use anyType, is so they are bound to IMElement which is
Axiom. To get best use
of DataBinding you need to have your schema bound to types rather
than anyType.

See how easy it is to use WSDL2java at times


[1] . But as I've said it depends on the schema.

Thanks,
Keith.

[1]

http://www.keith-chapman.org/2008/10/axis2-wsdl2java-generate-better-code.html




On Fri, Oct 3, 2008 at 3:06 AM, Steve Cohen
<[EMAIL PROTECTED] > wrote:

Well, I've a achieved a working connection to the vendor's WS.
 Thanks to all who provided useful input along the way and my
apologies if I posted overmuch or if some of these posts were
a tad ill-tempered.  Open-source can be a pain at times and I
certainly felt my share this past week.

Now looking back on what I did, I realize that after all the
pain of generating with WSDL2Java my client doesn't use any of
this ugly generated code at all!!  It's all built with AXIOM!!
 And while it isn't finished, in this application, I think
I'll want to continue down that path to completion.
This is a small project, part of a larger whole and the Axiom
model seems to fit with what I'm trying to do.  I can well
imagine bigger projects where that would not be the case,
where I'd want some sort of automated data binding, but ADB
didn't do it for me.  JIBX might be somewhat better, but I
think in this case AXIOM gives the most bang for the buck.

I would be interested in the opinions of others here.  I am
only interested here in client applications.  I am not
thinking about building services, just consuming them.  What
kinds are situations are best handled with AXIOM and which are
better handled with an automatic data binding technology?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]

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





-- 
Keith Chapman

Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org




--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org



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



Re: Error "HTTP :unsupported content-encoding of 'identity' found"

2008-10-02 Thread keith chapman
We run the Axis2 nightly build at WSO2  as well. So you
should be able to get it off the builder machine
here[1]

Thanks,
Keith.

[1] http://builder.wso2.org/browse/AXIS2-NIGHTLY/latest/artifact

On Fri, Oct 3, 2008 at 8:52 AM, <[EMAIL PROTECTED]> wrote:

>  what is the location of the nightly builds.  I am getting access
> forbidden when I try to access
> http://ws.zones.apache.org/dist/axis2/nightly/
>
>
> *Sangita Pandit*
> *728 1606*
>
>
>  --
> *From:* keith chapman [mailto:[EMAIL PROTECTED]
> *Sent:* Tuesday, September 30, 2008 8:04 PM
>
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Error "HTTP :unsupported content-encoding of 'identity'
> found"
>
>  We do not have a Axis2 release planned for any time soon. So you may have
> to get the nightly.
>
> Thanks,
> Keith.
>
> On Wed, Oct 1, 2008 at 1:33 AM, <[EMAIL PROTECTED]> wrote:
>
>>  How can I get the jar and when will this change be in the official
>> release.
>>
>>
>> *Sangita Pandit*
>> *728 1606*
>>
>>
>>  --
>>  *From:* keith chapman [mailto:[EMAIL PROTECTED]
>> *Sent:* Tuesday, September 30, 2008 12:31 PM
>>
>> *To:* axis-user@ws.apache.org
>> *Subject:* Re: Error "HTTP :unsupported content-encoding of 'identity'
>> found"
>>
>>   I have fixed this in the transports module.
>>
>> Thanks,
>> Keith.
>>
>> On Tue, Sep 30, 2008 at 7:57 PM, <[EMAIL PROTECTED]> wrote:
>>
>>>  Also to be backwards compatible, AXIS2 has to support it as the AXIS
>>> did not have issues like this.
>>>
>>>
>>> *Sangita Pandit*
>>> *728 1606*
>>>
>>>
>>>  --
>>> *From:* keith chapman [mailto:[EMAIL PROTECTED]
>>> *Sent:* Tuesday, September 30, 2008 4:20 AM
>>> *To:* axis-user@ws.apache.org
>>>  *Subject:* Re: Error "HTTP :unsupported content-encoding of 'identity'
>>> found"
>>>
>>>   On Tue, Sep 30, 2008 at 2:40 PM, Andreas Veithen <
>>> [EMAIL PROTECTED]> wrote:
>>>
 Googling for "Content-encoding: identity" reveals that this is actually
 quite common, so I guess that we should indeed support it.
>>>
>>>
>>> Exactly. And we wont have to do much jsut ignore the content-type if its
>>> identity.
>>>
>>> Thanks,
>>> Keith .
>>>


 Andreas

 keith chapman wrote:

> Interesting, It says SHOULD NOT but not MUST NOT. So it may be
> acceptable to have this header too. I guess one could argue that Axis2
> should ignore it if there is a header which says Content-encoding: 
> identity.
> WDYT?
>
> Thanks,
> Keith.
>
> On Tue, Sep 30, 2008 at 12:01 AM, Andreas Veithen <
> [EMAIL PROTECTED] > wrote:
>
>RFC2616, section 3.5 says the following about the identity content
>encoding: "This content-coding is used only in the Accept-Encoding
>header, and SHOULD NOT be used in the Content-Encoding header."
>Assuming that the error is triggered by the Content-Encoding
>header, the behavior of Axis2 in this particular case seems to be
>acceptable.
>
>Andreas
>
>
>On 29 sept. 08, at 19:23, keith chapman wrote:
>
>I just had a look at the code and it looks like we dont deal
>with identity content encoding (whereas we should). Could you
>use TCPMonitor to trace to request and response please. If you
>want to use the TCPMonitor plugin this how to [1] would help.
>
>Thanks,
>Keith.
>
>[1]
>
> http://www.keith-chapman.org/2008/07/using-tcp-monitor-to-debug-web-service.html
>
>On Mon, Sep 29, 2008 at 10:19 PM, <[EMAIL PROTECTED]
>> wrote:
>I generated the stubs using the WSDLToJava tool.
>
>Sangita Pandit
>728 1606
>
>
>
>From: keith chapman [mailto:[EMAIL PROTECTED]
>]
>Sent: Monday, September 29, 2008 11:47 AM
>To: axis-user@ws.apache.org 
>Subject: Re: Error "HTTP :unsupported content-encoding of
>'identity' found"
>
>Hi,
>
>How did you write the client for this service? Did you use
>ServiceClient API or did you use a generated stub?
>
>Thanks,
>Keith.
>
>On Mon, Sep 29, 2008 at 8:26 PM, <[EMAIL PROTECTED]
>> wrote:
>I am getting this error when webservice client is trying to
>make a call to the webservice method.  I am using the released
>version of Axis2 1.4.1. 
>
>
>See stack trace here
>org.apache.axis2.AxisFault: HTTP :unsupported content-encoding
>of 'identity' found
>   at
>
>>>

RE: Error "HTTP :unsupported content-encoding of 'identity' found"

2008-10-02 Thread Sangita_Pandit
what is the location of the nightly builds.  I am getting access
forbidden when I try to access
http://ws.zones.apache.org/dist/axis2/nightly/
 

Sangita Pandit 
728 1606 

 



From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 30, 2008 8:04 PM
To: axis-user@ws.apache.org
Subject: Re: Error "HTTP :unsupported content-encoding of 'identity'
found"


We do not have a Axis2 release planned for any time soon. So you may
have to get the nightly.

Thanks,
Keith.


On Wed, Oct 1, 2008 at 1:33 AM, <[EMAIL PROTECTED]> wrote:


How can I get the jar and when will this change be in the
official release.
 

Sangita Pandit 
728 1606 

 




From: keith chapman [mailto:[EMAIL PROTECTED] 

Sent: Tuesday, September 30, 2008 12:31 PM 

To: axis-user@ws.apache.org
Subject: Re: Error "HTTP :unsupported content-encoding of
'identity' found"


I have fixed this in the transports module. 

Thanks,
Keith.


On Tue, Sep 30, 2008 at 7:57 PM, <[EMAIL PROTECTED]>
wrote:


Also to be backwards compatible, AXIS2 has to support it
as the AXIS did not have issues like this.
 

Sangita Pandit 
728 1606 

 



From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 30, 2008 4:20 AM 

To: axis-user@ws.apache.org

Subject: Re: Error "HTTP :unsupported content-encoding
of 'identity' found"


On Tue, Sep 30, 2008 at 2:40 PM, Andreas Veithen
<[EMAIL PROTECTED]> wrote:


Googling for "Content-encoding: identity"
reveals that this is actually quite common, so I guess that we should
indeed support it.


Exactly. And we wont have to do much jsut ignore the
content-type if its identity.

Thanks,
Keith .




Andreas

keith chapman wrote:


Interesting, It says SHOULD NOT but not
MUST NOT. So it may be acceptable to have this header too. I guess one
could argue that Axis2 should ignore it if there is a header which says
Content-encoding: identity. WDYT?

Thanks,
Keith.


On Tue, Sep 30, 2008 at 12:01 AM,
Andreas Veithen <[EMAIL PROTECTED]
> wrote:

   RFC2616, section 3.5 says the
following about the identity content
   encoding: "This content-coding is
used only in the Accept-Encoding
   header, and SHOULD NOT be used in the
Content-Encoding header."
   Assuming that the error is triggered
by the Content-Encoding
   header, the behavior of Axis2 in this
particular case seems to be
   acceptable.

   Andreas


   On 29 sept. 08, at 19:23, keith
chapman wrote:

   I just had a look at the code and
it looks like we dont deal
   with identity content encoding
(whereas we should). Could you
   use TCPMonitor to trace to
request and response please. If you
   want to use the TCPMonitor plugin
this how to [1] would help.

   Thanks,
   Keith.

   [1]

http://www.keith-chapman.org/2008/07/using-tcp-monitor-to-debug-web-serv
ice.html

   On Mon, Sep 29, 2008 at 10:19 PM,
<[EMAIL PROTECTED]

   >
wrote:
   I generated the stubs using the
WSDLToJava tool.

   Sangita Pandit
   728 1606



  

Re: axiom VS data-binding?

2008-10-02 Thread keith chapman
Can you post a snippet of your types section. I wonder whether they all use
anyType, is so they are bound to IMElement which is Axiom. To get best use
of DataBinding you need to have your schema bound to types rather than
anyType.

See how easy it is to use WSDL2java at
times[1]
. But as I've said it depends on the schema.

Thanks,
Keith.

[1]
http://www.keith-chapman.org/2008/10/axis2-wsdl2java-generate-better-code.html


On Fri, Oct 3, 2008 at 3:06 AM, Steve Cohen <[EMAIL PROTECTED]> wrote:

> Well, I've a achieved a working connection to the vendor's WS.  Thanks to
> all who provided useful input along the way and my apologies if I posted
> overmuch or if some of these posts were a tad ill-tempered.  Open-source can
> be a pain at times and I certainly felt my share this past week.
>
> Now looking back on what I did, I realize that after all the pain of
> generating with WSDL2Java my client doesn't use any of this ugly generated
> code at all!!  It's all built with AXIOM!!  And while it isn't finished, in
> this application, I think I'll want to continue down that path to
> completion.
> This is a small project, part of a larger whole and the Axiom model seems
> to fit with what I'm trying to do.  I can well imagine bigger projects where
> that would not be the case, where I'd want some sort of automated data
> binding, but ADB didn't do it for me.  JIBX might be somewhat better, but I
> think in this case AXIOM gives the most bang for the buck.
>
> I would be interested in the opinions of others here.  I am only interested
> here in client applications.  I am not thinking about building services,
> just consuming them.  What kinds are situations are best handled with AXIOM
> and which are better handled with an automatic data binding technology?
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org


Re: axiom VS data-binding?

2008-10-02 Thread keith chapman
Oops I means OMElement (not IMElement ;)).


On Fri, Oct 3, 2008 at 6:53 AM, keith chapman <[EMAIL PROTECTED]>wrote:

> Can you post a snippet of your types section. I wonder whether they all use
> anyType, is so they are bound to IMElement which is Axiom. To get best use
> of DataBinding you need to have your schema bound to types rather than
> anyType.
>
> See how easy it is to use WSDL2java at 
> times[1]
>  . But as I've said it depends on the schema.
>
> Thanks,
> Keith.
>
> [1]
> http://www.keith-chapman.org/2008/10/axis2-wsdl2java-generate-better-code.html
>
>
>
> On Fri, Oct 3, 2008 at 3:06 AM, Steve Cohen <[EMAIL PROTECTED]>wrote:
>
>> Well, I've a achieved a working connection to the vendor's WS.  Thanks to
>> all who provided useful input along the way and my apologies if I posted
>> overmuch or if some of these posts were a tad ill-tempered.  Open-source can
>> be a pain at times and I certainly felt my share this past week.
>>
>> Now looking back on what I did, I realize that after all the pain of
>> generating with WSDL2Java my client doesn't use any of this ugly generated
>> code at all!!  It's all built with AXIOM!!  And while it isn't finished, in
>> this application, I think I'll want to continue down that path to
>> completion.
>> This is a small project, part of a larger whole and the Axiom model seems
>> to fit with what I'm trying to do.  I can well imagine bigger projects where
>> that would not be the case, where I'd want some sort of automated data
>> binding, but ADB didn't do it for me.  JIBX might be somewhat better, but I
>> think in this case AXIOM gives the most bang for the buck.
>>
>> I would be interested in the opinions of others here.  I am only
>> interested here in client applications.  I am not thinking about building
>> services, just consuming them.  What kinds are situations are best handled
>> with AXIOM and which are better handled with an automatic data binding
>> technology?
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>



-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org


Thomas Landgraf ist außer Haus / out of office reply

2008-10-02 Thread landgraf

Ich werde ab  03.10.2008 nicht im Büro sein. Ich kehre zurück am
19.10.2008.

Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.

I will answer your email when i am back in the office.


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



Re: FW: Integrating Axis2 with Tomcat and Eclipse

2008-10-02 Thread Bai Shen
I found out what the problem was.  Apparently when creating a web service,
you can choose between Axis and Axis2.  I didn't realize this and it was
defaulting to Axis.  So that got rid of the adminservice issue.

I ran into a couple other problems, but I haven't had a chance to figure
them out yet.

On Thu, Oct 2, 2008 at 1:45 PM, Bai Shen <[EMAIL PROTECTED]> wrote:

> The Axis2_Test path is from the name of my project.  Apparently, when using
> an integrated Tomcat it puts the name of the project in the url to
> differentiate from the various things you have running.
>
> I can still pull up the service list, etc, so Axis2 is working correctly.
> It just doesn't seem to have an Admin service.
>
> As for the war, I didn't install that.  I simply pointed Eclipse at the
> Axis2 binary files as mentioned in the beginning of the first link that
> Markus posted.
> Eclipse WTP Tutorials - Creating Top Down Web Service via Apache 
> Axis2
>
> I do have a log files directory.  However, as I mentioned, I didn't have
> any log files written to it.
>
> In my services dir under WEB-INF I only have a version service.
>
> I think I'm gonna try pointing Eclipse at the war version of Axis2 and see
> if that changes things.
>
>
> On Thu, Oct 2, 2008 at 1:01 PM, Barry Alexander <[EMAIL PROTECTED]>wrote:
>
>>  I tried to reply to the axis-user list but it kept bouncing…So I'll try
>> sending directly:
>>
>>
>>
>> I have installed Tomcat stand alone (outside of Eclipse) so that explains
>> my install path.  I would imagine even with embedded in Eclipse, there
>> should be logs files written somewhere on Tomcat statrtup.  Sorry I am not
>> familiar with embedded Tomcat.
>>
>>
>>
>> Shouldn't your endpoint address be something like
>> http://localhost:8080/axis2/services/listServices ?
>>
>>
>>
>> Yours has "Axis2_Test" in place of axis2.  How did you install your
>> axis2.war in Tomcat?
>>
>>
>>
>> What is your directory under Tomcat 6.0\webapps look like?
>>
>>
>>
>> This is what mine looks like: ..\Tomcat
>> 6.0\webapps\axis2\WEB-INF\services\services.list
>>
>>
>>  
>>  \
>> version-1.4.1.aar
>>
>>
>>
>>
>>
>> *From:* Bai Shen [mailto:[EMAIL PROTECTED]
>> *Sent:* Thursday, October 02, 2008 7:17 AM
>>
>> *To:* axis-user@ws.apache.org
>> *Subject:* Re: Integrating Axis2 with Tomcat and Eclipse
>>
>>
>>
>> I'm not sure where you got that install path.  I've never seen that in any
>> setup of Tomcat that I've done.
>>
>> Anyways, I'm running Tomcat integrated into Eclipse along with Axis2.  So
>> the log files aren't in the normal spot.  I looked in the temp dir that
>> Eclipse created, and there were no log files there either.  The console
>> doesn't contain any reference to the AdminService.
>>
>> So I'm not sure what the deal is.  The only thing I noticed out of place
>> in the console was this.
>>
>> [ERROR] Unable to find config file.  Creating new servlet engine config
>> file: /WEB-INF/server-config.wsdd
>>
>>  On Wed, Oct 1, 2008 at 5:47 PM, Barry Alexander <[EMAIL PROTECTED]>
>> wrote:
>>
>> Can you take a look in your Tomcat logs directory for recent logs for any
>> issues reported there.  Path should be [installDIr]\Apache Software
>> Foundation\Tomcat 6.0\logs
>>
>>
>>
>> You should see [INFO] entry for whether your AdminService was/was not
>> deployed
>>
>>
>>
>> *From:* Bai Shen [mailto:[EMAIL PROTECTED]
>> *Sent:* Wednesday, October 01, 2008 1:45 PM
>>
>>
>> *To:* axis-user@ws.apache.org
>> *Subject:* Re: Integrating Axis2 with Tomcat and Eclipse
>>
>>
>>
>> Okay, that worked.  Thanks.
>>
>> However, I didn't see any way to enable AdminService.  Any ideas on that?
>>
>> On Wed, Oct 1, 2008 at 3:47 PM, Barry Alexander <[EMAIL PROTECTED]>
>> wrote:
>>
>> >
>>
>>
>> * * *admin*
>>
>> * * *axis2*
>>
>>
>>
>> Ch
>>
>>
>>
>> *From:* Bai Shen [mailto:[EMAIL PROTECTED]
>> *Sent:* Wednesday, October 01, 2008 12:35 PM
>> *To:* axis-user@ws.apache.org
>> *Subject:* Re: Integrating Axis2 with Tomcat and Eclipse
>>
>>
>>
>> Okay, I started the tutorial in the first link.  I'm not sure what version
>> of Axis2/eclipse it's for, but several of the screenshots/settings are
>> different than mine.  Anyways, I managed to get to the equivalent of step
>> 13.  I was able to start my tomcat instance.  When I hit next, it attempted
>> to deploy my service to tomcat.  However, I got the following error.
>>
>> [ERROR] The service cannot be found for the endpoint reference (EPR)
>> http://localhost:8080/Axis2_Test/services/AdminService
>> org.apache.axis2.AxisFault: The service cannot be found for the endpoint
>> reference (EPR) http://localhost:8080/Axis2_Test/services/AdminService
>>
>> I'm not sure what I need to do the enable the AdminService.  It's not
>> listed in my running services.  However, when I looked on my tomcat in the
>> 

axiom VS data-binding?

2008-10-02 Thread Steve Cohen
Well, I've a achieved a working connection to the vendor's WS.  Thanks 
to all who provided useful input along the way and my apologies if I 
posted overmuch or if some of these posts were a tad ill-tempered.  
Open-source can be a pain at times and I certainly felt my share this 
past week.


Now looking back on what I did, I realize that after all the pain of 
generating with WSDL2Java my client doesn't use any of this ugly 
generated code at all!!  It's all built with AXIOM!!  And while it isn't 
finished, in this application, I think I'll want to continue down that 
path to completion. 

This is a small project, part of a larger whole and the Axiom model 
seems to fit with what I'm trying to do.  I can well imagine bigger 
projects where that would not be the case, where I'd want some sort of 
automated data binding, but ADB didn't do it for me.  JIBX might be 
somewhat better, but I think in this case AXIOM gives the most bang for 
the buck.


I would be interested in the opinions of others here.  I am only 
interested here in client applications.  I am not thinking about 
building services, just consuming them.  What kinds are situations are 
best handled with AXIOM and which are better handled with an automatic 
data binding technology?


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



Re: [axis2] Automatic schema validation

2008-10-02 Thread Dennis Sosnoski

Hi Jake,

I wrote a handler for schema validation some time ago, as an example for 
my training classes. Here's the information on it: 
http://www.sosnoski.com/jibx-wiki/space/axis2-jibx/validation


 - Dennis

--
Dennis M. Sosnoski
SOA and Web Services in Java
Axis2 Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117



Jake Goulding wrote:

Paul:

Thanks for the information. However, I think your example went over my 
head a bit.


I have a WSDL that has 4 or so XSD schemas. I point wsdl2java at that 
WSDL, then write an extremely simple driver program that calls the 
Axis2 stubs.


Is there a way to basically point Synapse at the same WSDL and then 
add a few lines of code to my driver program that will instruct Axis 
to use Synapse to validate the incoming message?


Thanks!

-Jake

Paul Fremantle wrote:

Jake

Synapse (http://synapse.apache.org) can be used to add Schema
Validation to Axis2 - either in the handler chain or as a standalone
gateway/security process.

See http://synapse.apache.org/Synapse_Samples.html#Sample7

Paul

On Thu, Oct 2, 2008 at 6:11 PM, Deepal Jayasinghe 
<[EMAIL PROTECTED]> wrote:

Deepal:

Thanks for the quick answer (most of my other email to list seems to
get ignored ;-)).

I am sorry for that , if I see any mail that I can answer I will do my
best,.

I'm sure that schema validation would slow down the system,
potentially a lot, but this would be invaluable for people operating
with systems outside of their control. There is also a great quote
that I cannot seem to find now, but it goes along the lines of "how
important is it to get the wrong answer quickly?"

Do you have any pointers to help me write the handler that you
suggest? For further reference, I am writing a client based on JAXB,
using Axis2 1.4.1.

http://www.developer.com/java/web/article.php/3529321
http://www.packtpub.com/article/handler-and-phase-in-apache-axis

Thank you!
Deepal

Thanks!

-Jake


Deepal jayasinghe wrote:

Answers is no , because it slow down the system. However you can
implement that your own. Just need to write a handler :)

-Deepal

Hey all:

Is there any way to have Axis automatically check the incoming (and
potentially the outgoing) XML against the schema(s) originally
provided in the WSDL? I did a search online, but didn't see anything
that seems too likely.

Thanks!

-Jake

- 


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





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



--
Thank you!


http://blogs.deepal.org


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








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



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



Re: Help with Axis Fault

2008-10-02 Thread Steve Cohen
The "E" is the first letter of an Error 500 page that the server is 
sending instead of a Soap Fault.  I am working with the vendor of the 
service to diagnose it.

Steve Cohen wrote:
I can't, unfortunately.  To do so would require me to expose my 
username and password on this WS's server.  I did try changing them to 
different values and then I got a normal "unknown user" type of 
message.  Perhaps this provides some clues?




keith chapman wrote:

Could you post your request and response please.

Thanks,
Keith.

On Thu, Oct 2, 2008 at 10:30 PM, Steve Cohen <[EMAIL PROTECTED] 
> wrote:


I have now hand-built my Axis client with all needed headers.  I
notice the following error code which makes no sense to me:

Exception in thread "main" org.apache.axis2.AxisFault:
com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character
'E' (code 69) in prolog; expected '<'
at [row,col {unknown-source}]: [1,1]
  at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
  at

org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:90) 


  at

org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:353) 


  at

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


  at

org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228) 


  at

org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) 


  at

org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:548) 


  at

org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:528) 


  at MyClient.main(MyClient.java:53)
Caused by: org.apache.axiom.om.OMException:
com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character
'E' (code 69) in prolog; expected '<'
at [row,col {unknown-source}]: [1,1]
  at

org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:249) 


  at

org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:156) 


  at

org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.(StAXSOAPModelBuilder.java:105) 


  at

org.apache.axis2.builder.BuilderUtil.getSOAPBuilder(BuilderUtil.java:677) 


  at

org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:182) 


  at

org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:112) 


  at

org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:88) 


  ... 7 more
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException:
Unexpected character 'E' (code 69) in prolog; expected '<'
at [row,col {unknown-source}]: [1,1]
  at

com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:623) 


  at

com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2047) 


  at
com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069)
  at

org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:506) 


  at

org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:161) 


  ... 13 more


There are only 4 UpperCase E characters in the packet:  in the
opening and closing  tags and two more in
various text elements.

What is Axis trying to tell me here?  I can't make head or tail 
of it.



-

To unsubscribe, e-mail: [EMAIL PROTECTED]

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





--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org



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






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



Re: Async processing, client stubs thread safety and port conflicts

2008-10-02 Thread Dmitriy Frolov
How should I go about extracting wsa:MessageID from the client's
asynchronous (call and transport with a separate listener) request and
response?  Am I responsible for correlating messages together or does axis2
offer such functionality as well?

Thanks,
Dmitriy

On Wed, Sep 24, 2008 at 9:59 PM, Dmitriy Frolov <[EMAIL PROTECTED]>wrote:

> Thanks again for the information.  I will post my findings based on POC.
>
> -Dmitriy
>
>
> On Wed, Sep 24, 2008 at 4:48 PM, Deepal Jayasinghe <[EMAIL PROTECTED]>wrote:
>
>>
>> > Deepal,
>> > Thanks for your quick response.  It worked perfectly.  I didn't
>> > realize that configuration was initialized multiple times.
>> Yes , whenever you create a new service client it create a new
>> configuration context.
>> >
>> > I have another question.  Is client listener implemented as a server
>> > model?  Meaning that once it receives a response it hands it over to
>> > another thread for processing?
>> Which listener you mean ?
>> If you are talking about the client side HTTP listener , then the answer
>> is yes. It is exactly a server.
>> >
>> > We are considering to use asynchronous client/server to reduce the
>> > load on the client and improve its throughput.
>> Yes that would be a good option , in fact Axis2 has support for NIO , so
>> you might be able to use that too.
>> >
>> > In our case we have a client application that acts more or less as a
>> > proxy and does very little processing itself.  It delegate all of the
>> > work synchronously to backend web services.  Responses average from
>> > several hundred milliseconds to several seconds with about 400 tps.
>> >
>> > Would you recommend asynchronous approach or could it potentially have
>> > other side affects?  All of the feedback will be much appreciated.
>> I think asynchronous approach would be a good option for your
>> application. However you can try both and let us know which one is
>> better. Then we can learn from you .
>>
>> -Deepal
>> >
>> > Thanks,
>> > Dmitriy
>> >
>> > On Tue, Sep 23, 2008 at 7:03 PM, Deepal Jayasinghe
>> > <[EMAIL PROTECTED] > wrote:
>> >
>> > Did you make two calls?
>> > If so please try to share the same configuration context.
>> >
>> > -Deepal
>> >
>> > Dmitriy Frolov wrote:
>> > > Hi all,
>> > > I am trying to utilize axis2 asynchronous processing via callback
>> > > mechanism and 2-way HTTP transport channels.  The question I have
>> is
>> > > if client stub implementation is thread safe.  Even though
>> > Inderi have
>> > > seen some reports that it is not, I was wong if anything changed
>> in
>> > > version 1.4.1.    Assuming it is
>> > not thread safe and I
>> > > cannot share client stubs between multiple threads, is there way
>> to
>> > > reuse same separate response listener for all of the transactions?
>> > >
>> > > I have tried creating client stubs for each thread separately,
>> > but ran
>> > > into following exception:
>> > > Sep 23, 2008 6:27:14 PM
>> > >
>> >
>> org.apache.axis2.transport.http.server.DefaultConnectionListenerFailureHandler
>> > > failed
>> > > WARNING: Attempt number 1 of 10 to reestalish connection listener
>> > >
>> >
>> [EMAIL PROTECTED]
>> > > due to failure
>> > > java.net.BindException: Address already in use: NET_Bind
>> > > at java.net.PlainSocketImpl.socketBind(Native Method)
>> > > at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:398)
>> > > at java.net.ServerSocket.bind(ServerSocket.java:331)
>> > > at java.net.ServerSocket.(ServerSocket.java:197)
>> > > at java.net.ServerSocket.(ServerSocket.java:109)
>> > > at
>> > >
>> >
>> org.apache.axis2.transport.http.server.DefaultConnectionListener.run(DefaultConnectionListener.java:72)
>> > > at
>> > >
>> >
>> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
>> > > at
>> > >
>> >
>> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
>> > >
>> > >
>> > > Also if there is no way to use one listener for all of the
>> > responses,
>> > > are there any optimization techniques that can be utilized like
>> > a pool
>> > > of listeners for high volume system (~400tps)?  Creating a
>> listener
>> > > every time could be rather expensive.
>> > >
>> > > Thanks,
>> > > Dmitriy
>> >
>> > --
>> > Thank you!
>> >
>> >
>> > http://blogs.deepal.org
>> >
>> >
>> >
>> -
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > 
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> > 
>> >
>> >
>>
>> --
>> Thank you!
>>
>>
>> http://blogs.deepal.org
>>
>>
>> 

RE: [axis2] Automatic schema validation

2008-10-02 Thread Li, Zhenge
The Axis2 soap monitor module is a perfect example on how to write a
handler. Just download the code from 

http://ws.apache.org/axis2/modules/index.html

and you'll be able make the monitor work within half an hour. Then the
monitor module can be easily customized for schema validation, I
believe. 

http://ws.apache.org/axis2/1_4/soapmonitor-module.html

-richard 


-Original Message-
From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED] 
Sent: October 2, 2008 2:12 PM
To: axis-user@ws.apache.org
Subject: Re: [axis2] Automatic schema validation


> Deepal:
>
> Thanks for the quick answer (most of my other email to list seems to
> get ignored ;-)).
I am sorry for that , if I see any mail that I can answer I will do my
best,.
>
> I'm sure that schema validation would slow down the system,
> potentially a lot, but this would be invaluable for people operating
> with systems outside of their control. There is also a great quote
> that I cannot seem to find now, but it goes along the lines of "how
> important is it to get the wrong answer quickly?"
>
> Do you have any pointers to help me write the handler that you
> suggest? For further reference, I am writing a client based on JAXB,
> using Axis2 1.4.1.

http://www.developer.com/java/web/article.php/3529321
http://www.packtpub.com/article/handler-and-phase-in-apache-axis

Thank you!
Deepal
>
> Thanks!
>
> -Jake
>
>
> Deepal jayasinghe wrote:
>> Answers is no , because it slow down the system. However you can
>> implement that your own. Just need to write a handler :)
>>
>> -Deepal
>>> Hey all:
>>>
>>> Is there any way to have Axis automatically check the incoming (and
>>> potentially the outgoing) XML against the schema(s) originally
>>> provided in the WSDL? I did a search online, but didn't see anything
>>> that seems too likely.
>>>
>>> Thanks!
>>>
>>> -Jake
>>>
>>>
-
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-- 
Thank you!


http://blogs.deepal.org


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


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



Re: [axis2] Automatic schema validation

2008-10-02 Thread Jake Goulding

Paul:

Thanks for the information. However, I think your example went over my 
head a bit.


I have a WSDL that has 4 or so XSD schemas. I point wsdl2java at that 
WSDL, then write an extremely simple driver program that calls the Axis2 
stubs.


Is there a way to basically point Synapse at the same WSDL and then add 
a few lines of code to my driver program that will instruct Axis to use 
Synapse to validate the incoming message?


Thanks!

-Jake

Paul Fremantle wrote:

Jake

Synapse (http://synapse.apache.org) can be used to add Schema
Validation to Axis2 - either in the handler chain or as a standalone
gateway/security process.

See http://synapse.apache.org/Synapse_Samples.html#Sample7

Paul

On Thu, Oct 2, 2008 at 6:11 PM, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:

Deepal:

Thanks for the quick answer (most of my other email to list seems to
get ignored ;-)).

I am sorry for that , if I see any mail that I can answer I will do my
best,.

I'm sure that schema validation would slow down the system,
potentially a lot, but this would be invaluable for people operating
with systems outside of their control. There is also a great quote
that I cannot seem to find now, but it goes along the lines of "how
important is it to get the wrong answer quickly?"

Do you have any pointers to help me write the handler that you
suggest? For further reference, I am writing a client based on JAXB,
using Axis2 1.4.1.

http://www.developer.com/java/web/article.php/3529321
http://www.packtpub.com/article/handler-and-phase-in-apache-axis

Thank you!
Deepal

Thanks!

-Jake


Deepal jayasinghe wrote:

Answers is no , because it slow down the system. However you can
implement that your own. Just need to write a handler :)

-Deepal

Hey all:

Is there any way to have Axis automatically check the incoming (and
potentially the outgoing) XML against the schema(s) originally
provided in the WSDL? I did a search online, but didn't see anything
that seems too likely.

Thanks!

-Jake

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





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



--
Thank you!


http://blogs.deepal.org


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








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



Re: Help with Axis Fault

2008-10-02 Thread Steve Cohen
I can't, unfortunately.  To do so would require me to expose my username 
and password on this WS's server.  I did try changing them to different 
values and then I got a normal "unknown user" type of message.  Perhaps 
this provides some clues?




keith chapman wrote:

Could you post your request and response please.

Thanks,
Keith.

On Thu, Oct 2, 2008 at 10:30 PM, Steve Cohen <[EMAIL PROTECTED] 
> wrote:


I have now hand-built my Axis client with all needed headers.  I
notice the following error code which makes no sense to me:

Exception in thread "main" org.apache.axis2.AxisFault:
com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character
'E' (code 69) in prolog; expected '<'
at [row,col {unknown-source}]: [1,1]
  at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
  at

org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:90)
  at

org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:353)
  at

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

org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
  at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
  at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:548)
  at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:528)
  at MyClient.main(MyClient.java:53)
Caused by: org.apache.axiom.om.OMException:
com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character
'E' (code 69) in prolog; expected '<'
at [row,col {unknown-source}]: [1,1]
  at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:249)
  at

org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:156)
  at

org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.(StAXSOAPModelBuilder.java:105)
  at
org.apache.axis2.builder.BuilderUtil.getSOAPBuilder(BuilderUtil.java:677)
  at

org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:182)
  at

org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:112)
  at

org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:88)
  ... 7 more
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException:
Unexpected character 'E' (code 69) in prolog; expected '<'
at [row,col {unknown-source}]: [1,1]
  at
com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:623)
  at

com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2047)
  at
com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069)
  at

org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:506)
  at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:161)
  ... 13 more


There are only 4 UpperCase E characters in the packet:  in the
opening and closing  tags and two more in
various text elements.

What is Axis trying to tell me here?  I can't make head or tail of it.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]

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





--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org



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



Re: FW: Integrating Axis2 with Tomcat and Eclipse

2008-10-02 Thread Bai Shen
The Axis2_Test path is from the name of my project.  Apparently, when using
an integrated Tomcat it puts the name of the project in the url to
differentiate from the various things you have running.

I can still pull up the service list, etc, so Axis2 is working correctly.
It just doesn't seem to have an Admin service.

As for the war, I didn't install that.  I simply pointed Eclipse at the
Axis2 binary files as mentioned in the beginning of the first link that
Markus posted.
Eclipse WTP Tutorials - Creating Top Down Web Service via Apache
Axis2

I do have a log files directory.  However, as I mentioned, I didn't have any
log files written to it.

In my services dir under WEB-INF I only have a version service.

I think I'm gonna try pointing Eclipse at the war version of Axis2 and see
if that changes things.

On Thu, Oct 2, 2008 at 1:01 PM, Barry Alexander <[EMAIL PROTECTED]>wrote:

>  I tried to reply to the axis-user list but it kept bouncing…So I'll try
> sending directly:
>
>
>
> I have installed Tomcat stand alone (outside of Eclipse) so that explains
> my install path.  I would imagine even with embedded in Eclipse, there
> should be logs files written somewhere on Tomcat statrtup.  Sorry I am not
> familiar with embedded Tomcat.
>
>
>
> Shouldn't your endpoint address be something like
> http://localhost:8080/axis2/services/listServices ?
>
>
>
> Yours has "Axis2_Test" in place of axis2.  How did you install your
> axis2.war in Tomcat?
>
>
>
> What is your directory under Tomcat 6.0\webapps look like?
>
>
>
> This is what mine looks like: ..\Tomcat
> 6.0\webapps\axis2\WEB-INF\services\services.list
>
>
>   
> \
> version-1.4.1.aar
>
>
>
>
>
> *From:* Bai Shen [mailto:[EMAIL PROTECTED]
> *Sent:* Thursday, October 02, 2008 7:17 AM
>
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Integrating Axis2 with Tomcat and Eclipse
>
>
>
> I'm not sure where you got that install path.  I've never seen that in any
> setup of Tomcat that I've done.
>
> Anyways, I'm running Tomcat integrated into Eclipse along with Axis2.  So
> the log files aren't in the normal spot.  I looked in the temp dir that
> Eclipse created, and there were no log files there either.  The console
> doesn't contain any reference to the AdminService.
>
> So I'm not sure what the deal is.  The only thing I noticed out of place in
> the console was this.
>
> [ERROR] Unable to find config file.  Creating new servlet engine config
> file: /WEB-INF/server-config.wsdd
>
>  On Wed, Oct 1, 2008 at 5:47 PM, Barry Alexander <[EMAIL PROTECTED]>
> wrote:
>
> Can you take a look in your Tomcat logs directory for recent logs for any
> issues reported there.  Path should be [installDIr]\Apache Software
> Foundation\Tomcat 6.0\logs
>
>
>
> You should see [INFO] entry for whether your AdminService was/was not
> deployed
>
>
>
> *From:* Bai Shen [mailto:[EMAIL PROTECTED]
> *Sent:* Wednesday, October 01, 2008 1:45 PM
>
>
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Integrating Axis2 with Tomcat and Eclipse
>
>
>
> Okay, that worked.  Thanks.
>
> However, I didn't see any way to enable AdminService.  Any ideas on that?
>
> On Wed, Oct 1, 2008 at 3:47 PM, Barry Alexander <[EMAIL PROTECTED]>
> wrote:
>
> 
>
>
> * * *admin*
>
> * * *axis2*
>
>
>
> Ch
>
>
>
> *From:* Bai Shen [mailto:[EMAIL PROTECTED]
> *Sent:* Wednesday, October 01, 2008 12:35 PM
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Integrating Axis2 with Tomcat and Eclipse
>
>
>
> Okay, I started the tutorial in the first link.  I'm not sure what version
> of Axis2/eclipse it's for, but several of the screenshots/settings are
> different than mine.  Anyways, I managed to get to the equivalent of step
> 13.  I was able to start my tomcat instance.  When I hit next, it attempted
> to deploy my service to tomcat.  However, I got the following error.
>
> [ERROR] The service cannot be found for the endpoint reference (EPR)
> http://localhost:8080/Axis2_Test/services/AdminService
> org.apache.axis2.AxisFault: The service cannot be found for the endpoint
> reference (EPR) http://localhost:8080/Axis2_Test/services/AdminService
>
> I'm not sure what I need to do the enable the AdminService.  It's not
> listed in my running services.  However, when I looked on my tomcat in the
> Axis2_Test dir, there was an axis2-web folder.  I went into that and was
> able to list my services.  There's also an Administration link, but when I
> click on that, it wants a login/pass.  I'm not sure what to use as I don't
> recall setting any usr/pass for Axis2.
>
> TIA.
>
> On Mon, Sep 29, 2008 at 1:34 AM, Grimm, Markus <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Axis2-setup is integrated in Eclispe WTP.
> Look at
>
> http://www.eclipse.org/webtools/community/tutorials/BottomUpAxis2WebServ
> ice/bu_tutorial.html

Re: [LIKELY JUNK]Re: [axis2] Automatic schema validation

2008-10-02 Thread Paul Fremantle
Jennifer

Actually in the doc/lit case it would be pretty easy to validate
against the WSDL, but in general its a bit harder. Synapse already
does validation if you are willing to specify the XSD. It would be
fairly simple to extend that to validate using the WSDL - as long as
its doc/lit.

Paul

On Thu, Oct 2, 2008 at 6:09 PM, Chen, Jennifer <[EMAIL PROTECTED]> wrote:
> I did some testing, for ADB beans, most of the validations are there, but
> it's not complete.  At least decimal precision is NOT validated.  Do you
> have an example of writing a handler to validate the xml message against a
> WSDL file?
>
> Thanks,
>
> Jennifer
> 
> From: keith chapman [mailto:[EMAIL PROTECTED]
> Sent: Thursday, October 02, 2008 12:35 PM
> To: axis-user@ws.apache.org
> Subject: [LIKELY JUNK]Re: [axis2] Automatic schema validation
>
> I think you would get some form of validation if you use generated code on
> the server. i.e If a message is sent with a missing element the
> MessageReceiver will detect this and throw a fault. Also this comes without
> any additional cost. It will also check minoccurs and nillable attributes.
>
> Thanks,
> Keith.
>
> On Thu, Oct 2, 2008 at 8:45 PM, Jake Goulding <[EMAIL PROTECTED]> wrote:
>>
>> Hey all:
>>
>> Is there any way to have Axis automatically check the incoming (and
>> potentially the outgoing) XML against the schema(s) originally provided in
>> the WSDL? I did a search online, but didn't see anything that seems too
>> likely.
>>
>> Thanks!
>>
>> -Jake
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>



-- 
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

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



RE: [LIKELY JUNK]Re: [axis2] Automatic schema validation

2008-10-02 Thread Chen, Jennifer
I did some testing, for ADB beans, most of the validations are there,
but it's not complete.  At least decimal precision is NOT validated.  Do
you have an example of writing a handler to validate the xml message
against a WSDL file?
 
Thanks,
 
Jennifer



From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Thursday, October 02, 2008 12:35 PM
To: axis-user@ws.apache.org
Subject: [LIKELY JUNK]Re: [axis2] Automatic schema validation


I think you would get some form of validation if you use generated code
on the server. i.e If a message is sent with a missing element the
MessageReceiver will detect this and throw a fault. Also this comes
without any additional cost. It will also check minoccurs and nillable
attributes.

Thanks,
Keith.


On Thu, Oct 2, 2008 at 8:45 PM, Jake Goulding <[EMAIL PROTECTED]>
wrote:


Hey all:

Is there any way to have Axis automatically check the incoming
(and potentially the outgoing) XML against the schema(s) originally
provided in the WSDL? I did a search online, but didn't see anything
that seems too likely.

Thanks!

-Jake


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






-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org



Re: [axis2] Automatic schema validation

2008-10-02 Thread Paul Fremantle
Jake

Synapse (http://synapse.apache.org) can be used to add Schema
Validation to Axis2 - either in the handler chain or as a standalone
gateway/security process.

See http://synapse.apache.org/Synapse_Samples.html#Sample7

Paul

On Thu, Oct 2, 2008 at 6:11 PM, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
>
>> Deepal:
>>
>> Thanks for the quick answer (most of my other email to list seems to
>> get ignored ;-)).
> I am sorry for that , if I see any mail that I can answer I will do my
> best,.
>>
>> I'm sure that schema validation would slow down the system,
>> potentially a lot, but this would be invaluable for people operating
>> with systems outside of their control. There is also a great quote
>> that I cannot seem to find now, but it goes along the lines of "how
>> important is it to get the wrong answer quickly?"
>>
>> Do you have any pointers to help me write the handler that you
>> suggest? For further reference, I am writing a client based on JAXB,
>> using Axis2 1.4.1.
>
> http://www.developer.com/java/web/article.php/3529321
> http://www.packtpub.com/article/handler-and-phase-in-apache-axis
>
> Thank you!
> Deepal
>>
>> Thanks!
>>
>> -Jake
>>
>>
>> Deepal jayasinghe wrote:
>>> Answers is no , because it slow down the system. However you can
>>> implement that your own. Just need to write a handler :)
>>>
>>> -Deepal
 Hey all:

 Is there any way to have Axis automatically check the incoming (and
 potentially the outgoing) XML against the schema(s) originally
 provided in the WSDL? I did a search online, but didn't see anything
 that seems too likely.

 Thanks!

 -Jake

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


>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> --
> Thank you!
>
>
> http://blogs.deepal.org
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-- 
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

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



Re: [axis2] Automatic schema validation

2008-10-02 Thread Deepal Jayasinghe

> Deepal:
>
> Thanks for the quick answer (most of my other email to list seems to
> get ignored ;-)).
I am sorry for that , if I see any mail that I can answer I will do my
best,.
>
> I'm sure that schema validation would slow down the system,
> potentially a lot, but this would be invaluable for people operating
> with systems outside of their control. There is also a great quote
> that I cannot seem to find now, but it goes along the lines of "how
> important is it to get the wrong answer quickly?"
>
> Do you have any pointers to help me write the handler that you
> suggest? For further reference, I am writing a client based on JAXB,
> using Axis2 1.4.1.

http://www.developer.com/java/web/article.php/3529321
http://www.packtpub.com/article/handler-and-phase-in-apache-axis

Thank you!
Deepal
>
> Thanks!
>
> -Jake
>
>
> Deepal jayasinghe wrote:
>> Answers is no , because it slow down the system. However you can
>> implement that your own. Just need to write a handler :)
>>
>> -Deepal
>>> Hey all:
>>>
>>> Is there any way to have Axis automatically check the incoming (and
>>> potentially the outgoing) XML against the schema(s) originally
>>> provided in the WSDL? I did a search online, but didn't see anything
>>> that seems too likely.
>>>
>>> Thanks!
>>>
>>> -Jake
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-- 
Thank you!


http://blogs.deepal.org


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



Re: Character problem with axis2 - rampart 1.3

2008-10-02 Thread Nandana Mihindukulasooriya
Hi Laszlo,
  Rampart 1.3 was zipped with Apache XML Security 1.4.0 and it has a bug
[1] when it comes to creating signatures containing non ascii characters.
This is fixed in XML Security 1.4.1 and can you try replacing the XML
Security 1.4.0  library with XML Security 1.4.1 [2] .

thanks,
nandana

[1] - https://issues.apache.org/bugzilla/show_bug.cgi?id=41462
[2] - http://xml.apache.org/security/dist/java-library/

On Thu, Oct 2, 2008 at 9:34 PM, Laszlo Benke <[EMAIL PROTECTED]> wrote:

>
> Hello!
>
> I've made a ws-security client which is communicating to a Websphere
> webservice with signed body, using x503Token. It works fine if the body
> doesn't contain any non iso-8859-1 characters. But if it contains I've got
> org.apache.ws.security.WSSecurityException: The signature verification
> failed exception. The server sends the answer in utf-8 and it sets
> context-type to text/xml; charset=utf-8. The received message is also good,
> when I take a look at this line in the log:
> org.apache.rampart.MESSAGE.invoke:78 - ***
> RampartReceiver received. But later in the log it becomes wrong
> here:org.apache.ws.security.message.EnvelopeIdResolver.engineResolve:145 -
> exit engineResolve, result: XMLSignatureInput/Element/
>
> Difference in the lines are the following:
> A Casco szerződés nem élő.
> A Casco szerzĹ'dĂ(c)s nem Ă(c)lĹ'.
>
> Anybody has idea what can I do with this problem.
>
> Thanks for the answers
> Laszlo
>
>
>
> --
> View this message in context:
> http://www.nabble.com/Character-problem-with-axis2---rampart-1.3-tp19781765p19781765.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Nandana Mihindukulasooriya
WSO2 inc.

http://nandana83.blogspot.com/
http://www.wso2.org


Re: Help with Axis Fault

2008-10-02 Thread keith chapman
Could you post your request and response please.

Thanks,
Keith.

On Thu, Oct 2, 2008 at 10:30 PM, Steve Cohen <[EMAIL PROTECTED]> wrote:

> I have now hand-built my Axis client with all needed headers.  I notice the
> following error code which makes no sense to me:
>
> Exception in thread "main" org.apache.axis2.AxisFault:
> com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character 'E' (code
> 69) in prolog; expected '<'
> at [row,col {unknown-source}]: [1,1]
>   at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
>   at
> org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:90)
>   at
> org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:353)
>   at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
>   at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
>   at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
>   at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:548)
>   at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:528)
>   at MyClient.main(MyClient.java:53)
> Caused by: org.apache.axiom.om.OMException:
> com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character 'E' (code
> 69) in prolog; expected '<'
> at [row,col {unknown-source}]: [1,1]
>   at
> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:249)
>   at
> org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:156)
>   at
> org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.(StAXSOAPModelBuilder.java:105)
>   at
> org.apache.axis2.builder.BuilderUtil.getSOAPBuilder(BuilderUtil.java:677)
>   at
> org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:182)
>   at
> org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:112)
>   at
> org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:88)
>   ... 7 more
> Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected
> character 'E' (code 69) in prolog; expected '<'
> at [row,col {unknown-source}]: [1,1]
>   at
> com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:623)
>   at
> com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2047)
>   at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069)
>   at
> org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:506)
>   at
> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:161)
>   ... 13 more
>
>
> There are only 4 UpperCase E characters in the packet:  in the opening and
> closing  tags and two more in various text elements.
>
> What is Axis trying to tell me here?  I can't make head or tail of it.
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org


RE: Help-Error : org.apache.axis2.AxisFault: Transport level information does not match with SOAP Message namespace URI

2008-10-02 Thread Soyer, Muhammed A.
Thanks for your reply, I already tried what you suggested and that is working.

-ms

From: keith chapman [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 02, 2008 11:00 AM
To: axis-user@ws.apache.org
Subject: Re: Help-Error : org.apache.axis2.AxisFault: Transport level 
information does not match with SOAP Message namespace URI


On Thu, Oct 2, 2008 at 7:36 PM, Soyer, Muhammed A. <[EMAIL 
PROTECTED]> wrote:

Hi,

  I am getting an error[1] when I do a call to a .Net service by using and 
axis2 1.4.1 client.  I did some research and I found that axis throws this 
error when it can't be sure about the soap version of the message.[2]

I want to be sure that I am understanding correctly. According to the link 
below my message must have the Content type of http header as 
"application/soap+xml" not as text/xml.

Is this a correct statement?
Yes. Your soap envelop is SOAP 1.2 ( cause its namespace is 
http://www.w3.org/2003/05/soap-envelope) hence its content-type should be 
application/soap+xml. The content-type of SOAP 1.1 is text/xml. So there is a 
problem in your response.

I presume that Axis2 sent a SOAP 1.2 request (cause this is the default in 
Axis2). As a workaround try sending a SOAP 1.1 request. You could do this by 
setting the following on the options object,

options.setSoapVersionURI(org.apache.axiom.soap.SOAP11Constants.SOAP_ENVELOPE_NAMESPACE_URI);

But the Server is definitely in fault here and not Axis2. You may wanna raise 
an issue against it.

Thanks,
Keith.

Is there any quick workaround?



Thanks





1-org.apache.axis2.AxisFault: Transport level information does not match with 
SOAP Message namespace URI
2-http://wso2.org/library/559









HTTP/1.1 200 OK

Server: NGX.Transport.Protocol.Soap.Http/2.0.3167.26428

Date: Thu, 02 Oct 2008 13:31:47 GMT

Content-Type: text/xml; charset=utf-8

Content-Length: 1256



http://schemas.xmlsoap.org/ws/2004/08/addressing"; 
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
 xmlns:xs="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:env="http://www.w3.org/2003/05/soap-envelope";>

   

  uuid:6c84daa4-36ed-4ec0-8771-bd91a5f1af05

  
urn:uuid:66f38c0f-74cb-427d-91c4-f4cabdeb921d

  soap.tcp://abcd:3456/

  
http://www.zzz.com/BPEL/OpenActivity/CentralReservation/CentralReservationPortType/BeginCreateResponse

  

 2008-10-02T13:31:47Z

 2008-10-02T13:41:47Z

  

  http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"/>

   

   

  http://www.zzz.com/BPEL/OpenActivity/CentralReservation/"; 
xmlns="http://www.zzz.com/BPEL/OpenActivity/CentralReservation/";>

 f12fce7e-155e-4c02-871c-16254637fac7

  

   







--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org


Help with Axis Fault

2008-10-02 Thread Steve Cohen
I have now hand-built my Axis client with all needed headers.  I notice 
the following error code which makes no sense to me:


Exception in thread "main" org.apache.axis2.AxisFault: 
com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character 'E' 
(code 69) in prolog; expected '<'

at [row,col {unknown-source}]: [1,1]
   at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
   at 
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:90)
   at 
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:353)
   at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
   at 
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
   at 
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
   at 
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:548)
   at 
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:528)

   at MyClient.main(MyClient.java:53)
Caused by: org.apache.axiom.om.OMException: 
com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character 'E' 
(code 69) in prolog; expected '<'

at [row,col {unknown-source}]: [1,1]
   at 
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:249)
   at 
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:156)
   at 
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.(StAXSOAPModelBuilder.java:105)
   at 
org.apache.axis2.builder.BuilderUtil.getSOAPBuilder(BuilderUtil.java:677)
   at 
org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:182)
   at 
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:112)
   at 
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:88)

   ... 7 more
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected 
character 'E' (code 69) in prolog; expected '<'

at [row,col {unknown-source}]: [1,1]
   at 
com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:623)
   at 
com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2047)

   at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069)
   at 
org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:506)
   at 
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:161)

   ... 13 more


There are only 4 UpperCase E characters in the packet:  in the opening 
and closing  tags and two more in various text elements.


What is Axis trying to tell me here?  I can't make head or tail of it.

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



Re: Rampart - is it usable on client-side when you don't control server side

2008-10-02 Thread Steve Cohen

Never mind, I found HttpTransportProperties.Authenticator.

Steve Cohen wrote:

Nandana:
Thank you very much.  This clears up a lot.
However, still a problem.  The Basic HTTP Auth on the referenced page 
gives this code sample:


HttpTransportProperties.BasicAuthentication basicAuthentication =
   new HttpTransportProperties().new 
BasicAuthentication();

basicAuthentication.setUsername("axis2");
basicAuthentication.setPassword("axis2");
options.setProperty(
org.apache.axis2.transport.http.HTTPConstants.BASIC_AUTHENTICATION,
   basicAuthentication);

However the class HttpTransportProperties.BasicAuthentication appears 
to be missing from Axis2 1.4.1 and the sample code will not reply.  
What was this class replaced with?







Nandana Mihindukulasooriya wrote:

Hi Steve,

It looks like this one is a showstopper.  According to the Rampart
1.4 QuickStart guide http://ws.apache.org/rampart/quick-start.html

When securing a SOAP message, the sender must know the
security actions to be performed on the message and the
receiver must know enough details to process and validate the
security of the message. Therefore when using Rampart with
Axis2, it must be engaged at both ends.


First part of this is only true if the vendor provided WSDL doesn't 
contain policies expressing the security requirements of that web 
service. And Rampart must be engaged at both side only if both sides 
are Axis2. For example, we successfully interoperate with .NET where 
they secure their services using WCF. The information the quick start 
guide seems bit misleading and will update them.


So it sounds like Rampart is useless for my use case:
 generating a client side interface for a Web Service from its
vendor-provided WSDL, when this vendor is not using Rampart.
 This vendor requires basic HTTP authentication but his web
service is not built with Axis and doesn't use Rampart.

Is this right?  And short of hand-generating the SOAP envelope
with authentication information is there any way of interfacing to
such a WS with Axis?


Anyway, to do basic HTTP authentication with Axis2 you don't need 
Rampart. You need Rampart only if you are doing WS Security stuff. 
Please look at the tutorial [1] to see how to do http basic 
authentication with Axis2.


[1] - http://wso2.org/library/161

thanks,
nandana

 


Steve Cohen wrote:

Thanks, but still a little gnashing of teeth going on.

Rampart 1.4.  Who knew that such a thing existed?  Ah yes,
there it is, if I go to http://ws.apache.org/rampart/.
 Unfortunately, this is not the link shown at
http://ws.apache.org/axis2/modules/index.html (accessible from
the axis main page).  Oh well, it's only wasted time.

In general, is the correct thing to assume that an axis module
should have the same version number as axis does and that if
you need that module, you are restricted to using an axis
version no higher than the version number of that module?

And thanks for the pointer on JMS.




keith chapman wrote:

You should use rampart 1.3 with axis2-1.3 and rampart 1.4
with axis2-1.4 or axis2-1.4.1. I answered your JMS
question on the other thread. And no rampart does NOT
depend on JMS.

Thanks,
Keith.

On Thu, Oct 2, 2008 at 5:25 AM, Steve Cohen
<[EMAIL PROTECTED] 
>> wrote:

   After all day futilely trying to use Rampart I have
some simple
   questions that maybe the developers can answer:

   What versions of Axis2 is Rampart compatible or
incompatible with?
In particular is it compatible with Axis2-1.4?  If not
what must
   be done to make it so?

   What undocumented dependencies does Rampart have?  Why
does client
   code blow up because of

   java.lang.NoClassDefFoundError: javax/jms/BytesMessage

   Does Rampart use JMS?

   (Note: this happens with the out of the box sample
client code in
   sample03).

   What I am looking for is a simple solution that allows
me to take
   a vendor-provided WSDL for a Web Service that uses
basic HTTP
   authentication, and quickly generate a usable client
for it.  All
   documentation I have seen for Axis/Rampart seems to
contain an
   unhealthy intermingling of client-side and server-side
code with
   the client-side code always something of an
afterthought.  This
   negates the whole idea

Re: [axis2] Automatic schema validation

2008-10-02 Thread keith chapman
I think you would get some form of validation if you use generated code on
the server. i.e If a message is sent with a missing element the
MessageReceiver will detect this and throw a fault. Also this comes without
any additional cost. It will also check minoccurs and nillable attributes.

Thanks,
Keith.

On Thu, Oct 2, 2008 at 8:45 PM, Jake Goulding <[EMAIL PROTECTED]> wrote:

> Hey all:
>
> Is there any way to have Axis automatically check the incoming (and
> potentially the outgoing) XML against the schema(s) originally provided in
> the WSDL? I did a search online, but didn't see anything that seems too
> likely.
>
> Thanks!
>
> -Jake
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org


RE: [axis2] Automatic schema validation

2008-10-02 Thread Chen, Jennifer
Hi Deepal,

I have the same question for both provisioning and consuming services,
and we are using ADB.

Thanks,

Jennifer 

-Original Message-
From: Jake Goulding [mailto:[EMAIL PROTECTED] 
Sent: Thursday, Oct 02, 2008 11:37 AM
To: axis-user@ws.apache.org
Subject: Re: [axis2] Automatic schema validation

Deepal:

Thanks for the quick answer (most of my other email to list seems to get

ignored ;-)).

I'm sure that schema validation would slow down the system, potentially 
a lot, but this would be invaluable for people operating with systems 
outside of their control. There is also a great quote that I cannot seem

to find now, but it goes along the lines of "how important is it to get 
the wrong answer quickly?"

Do you have any pointers to help me write the handler that you suggest? 
For further reference, I am writing a client based on JAXB, using Axis2 
1.4.1.

Thanks!

-Jake


Deepal jayasinghe wrote:
> Answers is no , because it slow down the system. However you can
> implement that your own. Just need to write a handler :)
> 
> -Deepal
>> Hey all:
>>
>> Is there any way to have Axis automatically check the incoming (and
>> potentially the outgoing) XML against the schema(s) originally
>> provided in the WSDL? I did a search online, but didn't see anything
>> that seems too likely.
>>
>> Thanks!
>>
>> -Jake
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 

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


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



Re: [axis2] Automatic schema validation

2008-10-02 Thread Jake Goulding

Deepal:

Thanks for the quick answer (most of my other email to list seems to get 
ignored ;-)).


I'm sure that schema validation would slow down the system, potentially 
a lot, but this would be invaluable for people operating with systems 
outside of their control. There is also a great quote that I cannot seem 
to find now, but it goes along the lines of "how important is it to get 
the wrong answer quickly?"


Do you have any pointers to help me write the handler that you suggest? 
For further reference, I am writing a client based on JAXB, using Axis2 
1.4.1.


Thanks!

-Jake


Deepal jayasinghe wrote:

Answers is no , because it slow down the system. However you can
implement that your own. Just need to write a handler :)

-Deepal

Hey all:

Is there any way to have Axis automatically check the incoming (and
potentially the outgoing) XML against the schema(s) originally
provided in the WSDL? I did a search online, but didn't see anything
that seems too likely.

Thanks!

-Jake

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







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



Character problem with axis2 - rampart 1.3

2008-10-02 Thread Laszlo Benke

Hello!

I've made a ws-security client which is communicating to a Websphere
webservice with signed body, using x503Token. It works fine if the body
doesn't contain any non iso-8859-1 characters. But if it contains I've got
org.apache.ws.security.WSSecurityException: The signature verification
failed exception. The server sends the answer in utf-8 and it sets
context-type to text/xml; charset=utf-8. The received message is also good,
when I take a look at this line in the log:
org.apache.rampart.MESSAGE.invoke:78 - ***
RampartReceiver received. But later in the log it becomes wrong
here:org.apache.ws.security.message.EnvelopeIdResolver.engineResolve:145 -
exit engineResolve, result: XMLSignatureInput/Element/

Difference in the lines are the following:
A Casco szerződés nem élő.
A Casco szerződés nem élő.

Anybody has idea what can I do with this problem.

Thanks for the answers
Laszlo



-- 
View this message in context: 
http://www.nabble.com/Character-problem-with-axis2---rampart-1.3-tp19781765p19781765.html
Sent from the Axis - User mailing list archive at Nabble.com.


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



Re: [axis2] Automatic schema validation

2008-10-02 Thread Deepal jayasinghe
Answers is no , because it slow down the system. However you can
implement that your own. Just need to write a handler :)

-Deepal
> Hey all:
>
> Is there any way to have Axis automatically check the incoming (and
> potentially the outgoing) XML against the schema(s) originally
> provided in the WSDL? I did a search online, but didn't see anything
> that seems too likely.
>
> Thanks!
>
> -Jake
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Thank you!


http://blogs.deepal.org


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



[axis2] Automatic schema validation

2008-10-02 Thread Jake Goulding

Hey all:

Is there any way to have Axis automatically check the incoming (and 
potentially the outgoing) XML against the schema(s) originally provided 
in the WSDL? I did a search online, but didn't see anything that seems 
too likely.


Thanks!

-Jake

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



Re: Rampart - is it usable on client-side when you don't control server side

2008-10-02 Thread keith chapman
Hi Steve,

Try this. This should work for you (cause I copied it off some of my working
code)

HttpTransportProperties.Authenticator authenticator = new
HttpTransportProperties.Authenticator();
authenticator.setUsername(basicAuthUsername);
authenticator.setPassword(basicAuthPassword);
authenticator.setPreemptiveAuthentication(true);
options.setProperty(HTTPConstants.AUTHENTICATE, authenticator);

Thanks,
Keith,

On Thu, Oct 2, 2008 at 6:57 PM, Steve Cohen <[EMAIL PROTECTED]> wrote:

> Nandana:
> Thank you very much.  This clears up a lot.
> However, still a problem.  The Basic HTTP Auth on the referenced page gives
> this code sample:
>
> HttpTransportProperties.BasicAuthentication basicAuthentication =
>   new HttpTransportProperties().new BasicAuthentication();
> basicAuthentication.setUsername("axis2");
> basicAuthentication.setPassword("axis2");
> options.setProperty(
>org.apache.axis2.transport.http.HTTPConstants.BASIC_AUTHENTICATION,
>   basicAuthentication);
>
> However the class HttpTransportProperties.BasicAuthentication appears to be
> missing from Axis2 1.4.1 and the sample code will not reply.  What was this
> class replaced with?
>
>
>
>
>
>
> Nandana Mihindukulasooriya wrote:
>
>> Hi Steve,
>>
>>It looks like this one is a showstopper.  According to the Rampart
>>1.4 QuickStart guide http://ws.apache.org/rampart/quick-start.html
>>
>>When securing a SOAP message, the sender must know the
>>security actions to be performed on the message and the
>>receiver must know enough details to process and validate the
>>security of the message. Therefore when using Rampart with
>>Axis2, it must be engaged at both ends.
>>
>>
>> First part of this is only true if the vendor provided WSDL doesn't
>> contain policies expressing the security requirements of that web service.
>> And Rampart must be engaged at both side only if both sides are Axis2. For
>> example, we successfully interoperate with .NET where they secure their
>> services using WCF. The information the quick start guide seems bit
>> misleading and will update them.
>>
>>So it sounds like Rampart is useless for my use case:
>> generating a client side interface for a Web Service from its
>>vendor-provided WSDL, when this vendor is not using Rampart.
>> This vendor requires basic HTTP authentication but his web
>>service is not built with Axis and doesn't use Rampart.
>>
>>Is this right?  And short of hand-generating the SOAP envelope
>>with authentication information is there any way of interfacing to
>>such a WS with Axis?
>>
>>
>> Anyway, to do basic HTTP authentication with Axis2 you don't need Rampart.
>> You need Rampart only if you are doing WS Security stuff. Please look at the
>> tutorial [1] to see how to do http basic authentication with Axis2.
>>
>> [1] - http://wso2.org/library/161
>>
>> thanks,
>> nandana
>>
>>
>>Steve Cohen wrote:
>>
>>Thanks, but still a little gnashing of teeth going on.
>>
>>Rampart 1.4.  Who knew that such a thing existed?  Ah yes,
>>there it is, if I go to http://ws.apache.org/rampart/.
>> Unfortunately, this is not the link shown at
>>http://ws.apache.org/axis2/modules/index.html (accessible from
>>the axis main page).  Oh well, it's only wasted time.
>>
>>In general, is the correct thing to assume that an axis module
>>should have the same version number as axis does and that if
>>you need that module, you are restricted to using an axis
>>version no higher than the version number of that module?
>>
>>And thanks for the pointer on JMS.
>>
>>
>>
>>
>>keith chapman wrote:
>>
>>You should use rampart 1.3 with axis2-1.3 and rampart 1.4
>>with axis2-1.4 or axis2-1.4.1. I answered your JMS
>>question on the other thread. And no rampart does NOT
>>depend on JMS.
>>
>>Thanks,
>>Keith.
>>
>>On Thu, Oct 2, 2008 at 5:25 AM, Steve Cohen
>><[EMAIL PROTECTED] 
>>>
>>>> wrote:
>>
>>   After all day futilely trying to use Rampart I have
>>some simple
>>   questions that maybe the developers can answer:
>>
>>   What versions of Axis2 is Rampart compatible or
>>incompatible with?
>>In particular is it compatible with Axis2-1.4?  If not
>>what must
>>   be done to make it so?
>>
>>   What undocumented dependencies does Rampart have?  Why
>>does client
>>   code blow up because of
>>
>>   java.lang.NoClassDefFoundError: javax/jms/BytesMessage
>>
>>   Does Rampart use JMS?
>>
>>  

Re: Help-Error : org.apache.axis2.AxisFault: Transport level information does not match with SOAP Message namespace URI

2008-10-02 Thread keith chapman
On Thu, Oct 2, 2008 at 7:36 PM, Soyer, Muhammed A. <[EMAIL PROTECTED]>wrote:

>  Hi,
>
>   I am getting an error[1] when I do a call to a .Net service by using and
> axis2 1.4.1 client.  I did some research and I found that axis throws this
> error when it can't be sure about the soap version of the message.[2]
>
> I want to be sure that I am understanding correctly. According to the link
> below my message must have the Content type of http header as
> "application/soap+xml" not as text/xml.
>
> Is this a correct statement?
>
Yes. Your soap envelop is SOAP 1.2 ( cause its namespace is *
http://www.w3.org/2003/05/soap-envelope) *hence its content-type should be
application/soap+xml. The content-type of SOAP 1.1 is text/xml. So there is
a problem in your response.

I presume that Axis2 sent a SOAP 1.2 request (cause this is the default in
Axis2). As a workaround try sending a SOAP 1.1 request. You could do this by
setting the following on the options object,

options.setSoapVersionURI(org.apache.axiom.soap.SOAP11Constants.SOAP_ENVELOPE_NAMESPACE_URI);

But the Server is definitely in fault here and not Axis2. You may wanna
raise an issue against it.

Thanks,
Keith.

> Is there any quick workaround?
>
>
>
> Thanks
>
>
>
>
>
> 1-org.apache.axis2.AxisFault: Transport level information does not match
> with SOAP Message namespace URI
> 2-http://wso2.org/library/559
>
>
>
>
>
> 
>
>
>
> HTTP/1.1 200 OK
>
> Server: NGX.Transport.Protocol.Soap.Http/2.0.3167.26428
>
> Date: Thu, 02 Oct 2008 13:31:47 GMT
>
> *Content-Type: text/xml; charset=utf-8*
>
> Content-Length: 1256
>
>
>
> http://schemas.xmlsoap.org/ws/2004/08/addressing";
> xmlns:wsu="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
> xmlns:xs="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance"; *xmlns:env="
> http://www.w3.org/2003/05/soap-envelope*";>
>
>
>
>
> uuid:6c84daa4-36ed-4ec0-8771-bd91a5f1af05
>
>
> urn:uuid:66f38c0f-74cb-427d-91c4-f4cabdeb921d
>
>   soap.tcp://abcd:3456/
>
>   
> http://www.zzz.com/BPEL/OpenActivity/CentralReservation/CentralReservationPortType/BeginCreateResponse
> 
>
>wsu:Id="Timestamp-ea6490c2-d8a6-49ce-a09b-d02cd8f6b03f">
>
>  2008-10-02T13:31:47Z
>
>  2008-10-02T13:41:47Z
>
>   
>
>   http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> "/>
>
>
>
>
>
>   http://www.zzz.com/BPEL/OpenActivity/CentralReservation/"; xmlns="
> http://www.zzz.com/BPEL/OpenActivity/CentralReservation/";>
>
>
> f12fce7e-155e-4c02-871c-16254637fac7
>
>   
>
>
>
> 
>
>
>



-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org


Re: Integrating Axis2 with Tomcat and Eclipse

2008-10-02 Thread Bai Shen
I'm not sure where you got that install path.  I've never seen that in any
setup of Tomcat that I've done.

Anyways, I'm running Tomcat integrated into Eclipse along with Axis2.  So
the log files aren't in the normal spot.  I looked in the temp dir that
Eclipse created, and there were no log files there either.  The console
doesn't contain any reference to the AdminService.

So I'm not sure what the deal is.  The only thing I noticed out of place in
the console was this.

[ERROR] Unable to find config file.  Creating new servlet engine config
file: /WEB-INF/server-config.wsdd


On Wed, Oct 1, 2008 at 5:47 PM, Barry Alexander <[EMAIL PROTECTED]>wrote:

>  Can you take a look in your Tomcat logs directory for recent logs for any
> issues reported there.  Path should be [installDIr]\Apache Software
> Foundation\Tomcat 6.0\logs
>
>
>
> You should see [INFO] entry for whether your AdminService was/was not
> deployed
>
>
>
> *From:* Bai Shen [mailto:[EMAIL PROTECTED]
> *Sent:* Wednesday, October 01, 2008 1:45 PM
>
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Integrating Axis2 with Tomcat and Eclipse
>
>
>
> Okay, that worked.  Thanks.
>
> However, I didn't see any way to enable AdminService.  Any ideas on that?
>
> On Wed, Oct 1, 2008 at 3:47 PM, Barry Alexander <[EMAIL PROTECTED]>
> wrote:
>
> 
>
>
> * * *admin*
>
> * * *axis2*
>
>
>
> Ch
>
>
>
> *From:* Bai Shen [mailto:[EMAIL PROTECTED]
> *Sent:* Wednesday, October 01, 2008 12:35 PM
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Integrating Axis2 with Tomcat and Eclipse
>
>
>
> Okay, I started the tutorial in the first link.  I'm not sure what version
> of Axis2/eclipse it's for, but several of the screenshots/settings are
> different than mine.  Anyways, I managed to get to the equivalent of step
> 13.  I was able to start my tomcat instance.  When I hit next, it attempted
> to deploy my service to tomcat.  However, I got the following error.
>
> [ERROR] The service cannot be found for the endpoint reference (EPR)
> http://localhost:8080/Axis2_Test/services/AdminService
> org.apache.axis2.AxisFault: The service cannot be found for the endpoint
> reference (EPR) http://localhost:8080/Axis2_Test/services/AdminService
>
> I'm not sure what I need to do the enable the AdminService.  It's not
> listed in my running services.  However, when I looked on my tomcat in the
> Axis2_Test dir, there was an axis2-web folder.  I went into that and was
> able to list my services.  There's also an Administration link, but when I
> click on that, it wants a login/pass.  I'm not sure what to use as I don't
> recall setting any usr/pass for Axis2.
>
> TIA.
>
> On Mon, Sep 29, 2008 at 1:34 AM, Grimm, Markus <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Axis2-setup is integrated in Eclispe WTP.
> Look at
>
> http://www.eclipse.org/webtools/community/tutorials/BottomUpAxis2WebServ
> ice/bu_tutorial.html
>  or
> http://www.eclipse.org/webtools/community/tutorials/TopDownAxis2WebServi
> ce/td_tutorial.html
>
> Thanks,
> Markus
>
>
>
> 
>
> Von: Bai Shen [mailto:[EMAIL PROTECTED]
> Gesendet: Sonntag, 28. September 2008 21:30
> An: axis-user@ws.apache.org
> Betreff: Integrating Axis2 with Tomcat and Eclipse
>
>
>
> I've been using Eclipse, Tomcat, and Axis for a while.  However, I'm
> working on automating my setup. Thanks to the helpful members of the
> Tomcat list, I have Tomcat integrated with Eclipse, so I can code and
> deploy easily.
>
> What I'm curious about is if there is a way to add Axis2 to the setup?
> I'm running Eclipse 3.4, Tomcat 6.0.18, and Axis2 1.4.1.
>
> TIA.
>
> Bai Shen
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>


Help-Error : org.apache.axis2.AxisFault: Transport level information does not match with SOAP Message namespace URI

2008-10-02 Thread Soyer, Muhammed A.
Hi,
  I am getting an error[1] when I do a call to a .Net service by using and 
axis2 1.4.1 client.  I did some research and I found that axis throws this 
error when it can't be sure about the soap version of the message.[2]
I want to be sure that I am understanding correctly. According to the link 
below my message must have the Content type of http header as 
"application/soap+xml" not as text/xml.
Is this a correct statement?
Is there any quick workaround?

Thanks


1-org.apache.axis2.AxisFault: Transport level information does not match with 
SOAP Message namespace URI
2-http://wso2.org/library/559




HTTP/1.1 200 OK
Server: NGX.Transport.Protocol.Soap.Http/2.0.3167.26428
Date: Thu, 02 Oct 2008 13:31:47 GMT
Content-Type: text/xml; charset=utf-8
Content-Length: 1256

http://schemas.xmlsoap.org/ws/2004/08/addressing"; 
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
 xmlns:xs="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:env="http://www.w3.org/2003/05/soap-envelope";>
   
  uuid:6c84daa4-36ed-4ec0-8771-bd91a5f1af05
  
urn:uuid:66f38c0f-74cb-427d-91c4-f4cabdeb921d
  soap.tcp://abcd:3456/
  
http://www.zzz.com/BPEL/OpenActivity/CentralReservation/CentralReservationPortType/BeginCreateResponse
  
 2008-10-02T13:31:47Z
 2008-10-02T13:41:47Z
  
  http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"/>
   
   
  http://www.zzz.com/BPEL/OpenActivity/CentralReservation/"; 
xmlns="http://www.zzz.com/BPEL/OpenActivity/CentralReservation/";>
 f12fce7e-155e-4c02-871c-16254637fac7
  
   




Configure Axis2 Client Timeout Descriptively

2008-10-02 Thread Jonathan Cornes

Hi,
 
I am trying to find a way to configure axis2 web server clients descriptively 
rather than programmatically using the Client API.
 
In particular I am trying to configure the length of time elapsed before the a 
timeout will occur during a call to the web service (resulting in a 
SocketTimeOut exception).
 
Can the following be done descriptively on the web server client in a wsdd or 
other configuration file?
stub._getServiceClient().getOptions().setTimeOutInMilliSeconds(soTimeout);
All help gratefully appreciated.
 
Kind regards
 
Jon
 
_
Make a mini you and download it into Windows Live Messenger
http://clk.atdmt.com/UKM/go/111354029/direct/01/

Re: Rampart - is it usable on client-side when you don't control server side

2008-10-02 Thread Steve Cohen

Nandana:
Thank you very much.  This clears up a lot.
However, still a problem.  The Basic HTTP Auth on the referenced page 
gives this code sample:


HttpTransportProperties.BasicAuthentication basicAuthentication =
   new HttpTransportProperties().new BasicAuthentication();
basicAuthentication.setUsername("axis2");
basicAuthentication.setPassword("axis2");
options.setProperty(
org.apache.axis2.transport.http.HTTPConstants.BASIC_AUTHENTICATION,
   basicAuthentication);

However the class HttpTransportProperties.BasicAuthentication appears to be 
missing from Axis2 1.4.1 and the sample code will not reply.  What was this 
class replaced with?






Nandana Mihindukulasooriya wrote:

Hi Steve,

It looks like this one is a showstopper.  According to the Rampart
1.4 QuickStart guide http://ws.apache.org/rampart/quick-start.html

When securing a SOAP message, the sender must know the
security actions to be performed on the message and the
receiver must know enough details to process and validate the
security of the message. Therefore when using Rampart with
Axis2, it must be engaged at both ends.


First part of this is only true if the vendor provided WSDL doesn't 
contain policies expressing the security requirements of that web 
service. And Rampart must be engaged at both side only if both sides 
are Axis2. For example, we successfully interoperate with .NET where 
they secure their services using WCF. The information the quick start 
guide seems bit misleading and will update them.


So it sounds like Rampart is useless for my use case:
 generating a client side interface for a Web Service from its
vendor-provided WSDL, when this vendor is not using Rampart.
 This vendor requires basic HTTP authentication but his web
service is not built with Axis and doesn't use Rampart.

Is this right?  And short of hand-generating the SOAP envelope
with authentication information is there any way of interfacing to
such a WS with Axis?


Anyway, to do basic HTTP authentication with Axis2 you don't need 
Rampart. You need Rampart only if you are doing WS Security stuff. 
Please look at the tutorial [1] to see how to do http basic 
authentication with Axis2.


[1] - http://wso2.org/library/161

thanks,
nandana

 


Steve Cohen wrote:

Thanks, but still a little gnashing of teeth going on.

Rampart 1.4.  Who knew that such a thing existed?  Ah yes,
there it is, if I go to http://ws.apache.org/rampart/.
 Unfortunately, this is not the link shown at
http://ws.apache.org/axis2/modules/index.html (accessible from
the axis main page).  Oh well, it's only wasted time.

In general, is the correct thing to assume that an axis module
should have the same version number as axis does and that if
you need that module, you are restricted to using an axis
version no higher than the version number of that module?

And thanks for the pointer on JMS.




keith chapman wrote:

You should use rampart 1.3 with axis2-1.3 and rampart 1.4
with axis2-1.4 or axis2-1.4.1. I answered your JMS
question on the other thread. And no rampart does NOT
depend on JMS.

Thanks,
Keith.

On Thu, Oct 2, 2008 at 5:25 AM, Steve Cohen
<[EMAIL PROTECTED] 
>> wrote:

   After all day futilely trying to use Rampart I have
some simple
   questions that maybe the developers can answer:

   What versions of Axis2 is Rampart compatible or
incompatible with?
In particular is it compatible with Axis2-1.4?  If not
what must
   be done to make it so?

   What undocumented dependencies does Rampart have?  Why
does client
   code blow up because of

   java.lang.NoClassDefFoundError: javax/jms/BytesMessage

   Does Rampart use JMS?

   (Note: this happens with the out of the box sample
client code in
   sample03).

   What I am looking for is a simple solution that allows
me to take
   a vendor-provided WSDL for a Web Service that uses
basic HTTP
   authentication, and quickly generate a usable client
for it.  All
   documentation I have seen for Axis/Rampart seems to
contain an
   unhealthy intermingling of client-side and server-side
code with
   the client-side code always something of an
afterthought.  This
   negates the whole idea of Web Services.

   Is there a sample out there or an article tha

AutoReply - Out Of Office - Re : Re: New to axis2, need some help

2008-10-02 Thread saurav . chatterjee




This is an automated response, please do not reply.
Your e-mail message - Re: Re: New to axis2, need some help has been
successfully delivered.

I will be out of the office starting Thu 10/02/2008 and will not return
until Sun 10/12/2008.

I will respond to your message when I return.

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


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



Re: New to axis2, need some help

2008-10-02 Thread Yefeng Liu
Thank u Keith!

2008/10/2 keith chapman <[EMAIL PROTECTED]>

> This is the thread [1] Saminda is referring to
>
> Thanks,
> Keith,
>
> [1]
> http://www.nabble.com/HELP!!!---Axis-2-1.4-CodeGenerator-Eclipse-Plugin-fails-td19742674.html
>
> 2008/10/2 Yefeng Liu <[EMAIL PROTECTED]>
>
>> Hi
>>
>> I'm new to this mailing list also, I dont have that mail in my mailbox..
>> Can u please make a copy&paste ?
>> Thx!
>>
>> 2008/10/2 Saminda Wijeratne <[EMAIL PROTECTED]>
>>
>>> Hi,
>>> sorry for the late reply. Since you are subscribed to the mailing list
>>> check for the mail with subject "Re: HELP!!! - Axis 2 1.4 CodeGenerator
>>> Eclipse Plugin fails".
>>> I've mentioned a couple of solutions there.
>>> regards
>>> Saminda
>>>
>>> Yefeng Liu wrote:
>>> > ��..
>>> > Thx a lot!
>>> > Btw what I should do? Should I replace them with older version plugins?
>>> >
>>> >
>>> > 2008/10/1 Saminda Wijeratne <[EMAIL PROTECTED] >> [EMAIL PROTECTED]>>
>>> >
>>> > The latest available plugin gives that error because it is giving
>>> > ClassDefNotFound exception for class
>>> > javax.xml.stream.XMLStreamException. This class resides in
>>> > geranimo-stax.
>>> >
>>> > Yefeng Liu wrote:
>>> > > Axis2 1.4.1
>>> > > Axis2 Codegen Wizard 1.3.0
>>> > > Axis2 Service Archiver 1.3.0
>>> > >
>>> > > All are the latest version I think.
>>> > >
>>> > > 2008/10/1 keith chapman <[EMAIL PROTECTED]
>>> > 
>>> > > >> >>>
>>> > >
>>> > > Which version of Axis2/ The eclipse plugin are you using?
>>> > >
>>> > > Thanks,
>>> > > Keith.
>>> > >
>>> > > 2008/9/30 Danny LIU <[EMAIL PROTECTED]
>>> >  >> > >>
>>> > >
>>> > > Hi everyone!
>>> > >
>>> > > Im a new learner of axis2, and basically Im following a
>>> > > tutorial to study it
>>> > > right now.
>>> > >
>>> > > My problem is I got a strange exception when I try to generate
>>> > > Java code from WSDL file
>>> > > using eclipse's plugin -Axis2 Code Generator .
>>> > > The exception is " java.lang.reflect.InvocationTargetException"
>>> > > does anyone know how to fix this?
>>> > >
>>> > > Thx in advance.
>>> > >
>>> > > Here is my wsdl code:
>>> > >
>>> > > 
>>> > > >> > > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
>>> > > xmlns:tns="http://www.example.org/helloAxis2/";
>>> > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>>> > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; name="helloAxis2"
>>> > > targetNamespace="http://www.example.org/helloAxis2/";>
>>> > > 
>>> > > >> > > targetNamespace="http://www.example.org/helloAxis2/";>
>>> > > 
>>> > > 
>>> > > 
>>> > > 
>>> > > 
>>> > > >> > > name="Response" />
>>> > > 
>>> > > 
>>> > > >> > > name="Request" />
>>> > > 
>>> > > 
>>> > > 
>>> > > 
>>> > > 
>>> > > 
>>> > > 
>>> > > 
>>> > > >> > > transport="http://schemas.xmlsoap.org/soap/http"; />
>>> > > 
>>> > > >> > > soapAction="http://localhost:8080/axis2/services/helloAxis2"; />
>>> > > 
>>> > > 
>>> > > 
>>> > > 
>>> > > 
>>> > > 
>>> > > 
>>> > > 
>>> > > 
>>> > > 
>>> > > >> > > location="http://localhost:8080/axis2/services/helloAxis2"; />
>>> > > 
>>> > > 
>>> > > 
>>> > >
>>> > > --
>>> > >
>>> > > 天生万物以养人
>>> > >
>>> > > 人无一德以报天
>>> > >
>>> > >
>>> > >
>>> > >
>>> > > --
>>> > > Keith Chapman
>>> > > Senior Software Engineer
>>> > > WSO2 Inc.
>>> > > Oxygenating the Web Service Platform.
>>> > > http://wso2.org/
>>> > >
>>> > > blog: http://www.keith-chapman.org
>>> > >
>>> > >
>>> > >
>>> > >
>>> > > --
>>> > >
>>> > > 天生万物以养人
>>> > >
>>> > > 人无一德以报天
>>> >
>>> >
>>> >
>>> -
>>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> > 
>>> > For additional commands, e-mail: [EMAIL PROTECTED]
>>> > 
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> >
>>> > 天生万物以养人
>>> >
>>> > 人无一德以报天
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>>
>> --
>>
>>   天生万物以养人
>>
>> 人无一德以报天
>>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>



-- 

  天生万物以养人

人无一德以报天


Re: New to axis2, need some help

2008-10-02 Thread keith chapman
This is the thread [1] Saminda is referring to

Thanks,
Keith,

[1]
http://www.nabble.com/HELP!!!---Axis-2-1.4-CodeGenerator-Eclipse-Plugin-fails-td19742674.html

2008/10/2 Yefeng Liu <[EMAIL PROTECTED]>

> Hi
>
> I'm new to this mailing list also, I dont have that mail in my mailbox..
> Can u please make a copy&paste ?
> Thx!
>
> 2008/10/2 Saminda Wijeratne <[EMAIL PROTECTED]>
>
> Hi,
>> sorry for the late reply. Since you are subscribed to the mailing list
>> check for the mail with subject "Re: HELP!!! - Axis 2 1.4 CodeGenerator
>> Eclipse Plugin fails".
>> I've mentioned a couple of solutions there.
>> regards
>> Saminda
>>
>> Yefeng Liu wrote:
>> > ��..
>> > Thx a lot!
>> > Btw what I should do? Should I replace them with older version plugins?
>> >
>> >
>> > 2008/10/1 Saminda Wijeratne <[EMAIL PROTECTED] > [EMAIL PROTECTED]>>
>> >
>> > The latest available plugin gives that error because it is giving
>> > ClassDefNotFound exception for class
>> > javax.xml.stream.XMLStreamException. This class resides in
>> > geranimo-stax.
>> >
>> > Yefeng Liu wrote:
>> > > Axis2 1.4.1
>> > > Axis2 Codegen Wizard 1.3.0
>> > > Axis2 Service Archiver 1.3.0
>> > >
>> > > All are the latest version I think.
>> > >
>> > > 2008/10/1 keith chapman <[EMAIL PROTECTED]
>> > 
>> > > > >>>
>> > >
>> > > Which version of Axis2/ The eclipse plugin are you using?
>> > >
>> > > Thanks,
>> > > Keith.
>> > >
>> > > 2008/9/30 Danny LIU <[EMAIL PROTECTED]
>> >  > > >>
>> > >
>> > > Hi everyone!
>> > >
>> > > Im a new learner of axis2, and basically Im following a
>> > > tutorial to study it
>> > > right now.
>> > >
>> > > My problem is I got a strange exception when I try to generate
>> > > Java code from WSDL file
>> > > using eclipse's plugin -Axis2 Code Generator .
>> > > The exception is " java.lang.reflect.InvocationTargetException"
>> > > does anyone know how to fix this?
>> > >
>> > > Thx in advance.
>> > >
>> > > Here is my wsdl code:
>> > >
>> > > 
>> > > > > > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
>> > > xmlns:tns="http://www.example.org/helloAxis2/";
>> > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>> > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; name="helloAxis2"
>> > > targetNamespace="http://www.example.org/helloAxis2/";>
>> > > 
>> > > > > > targetNamespace="http://www.example.org/helloAxis2/";>
>> > > 
>> > > 
>> > > 
>> > > 
>> > > 
>> > > > > > name="Response" />
>> > > 
>> > > 
>> > > > > > name="Request" />
>> > > 
>> > > 
>> > > 
>> > > 
>> > > 
>> > > 
>> > > 
>> > > 
>> > > > > > transport="http://schemas.xmlsoap.org/soap/http"; />
>> > > 
>> > > > > > soapAction="http://localhost:8080/axis2/services/helloAxis2"; />
>> > > 
>> > > 
>> > > 
>> > > 
>> > > 
>> > > 
>> > > 
>> > > 
>> > > 
>> > > 
>> > > > > > location="http://localhost:8080/axis2/services/helloAxis2"; />
>> > > 
>> > > 
>> > > 
>> > >
>> > > --
>> > >
>> > > 天生万物以养人
>> > >
>> > > 人无一德以报天
>> > >
>> > >
>> > >
>> > >
>> > > --
>> > > Keith Chapman
>> > > Senior Software Engineer
>> > > WSO2 Inc.
>> > > Oxygenating the Web Service Platform.
>> > > http://wso2.org/
>> > >
>> > > blog: http://www.keith-chapman.org
>> > >
>> > >
>> > >
>> > >
>> > > --
>> > >
>> > > 天生万物以养人
>> > >
>> > > 人无一德以报天
>> >
>> >
>> >
>> -
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > 
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> > 
>> >
>> >
>> >
>> >
>> > --
>> >
>> > 天生万物以养人
>> >
>> > 人无一德以报天
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
>
>   天生万物以养人
>
> 人无一德以报天
>



-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org


Re: New to axis2, need some help

2008-10-02 Thread Yefeng Liu
Hi

I'm new to this mailing list also, I dont have that mail in my mailbox..
Can u please make a copy&paste ?
Thx!

2008/10/2 Saminda Wijeratne <[EMAIL PROTECTED]>

> Hi,
> sorry for the late reply. Since you are subscribed to the mailing list
> check for the mail with subject "Re: HELP!!! - Axis 2 1.4 CodeGenerator
> Eclipse Plugin fails".
> I've mentioned a couple of solutions there.
> regards
> Saminda
>
> Yefeng Liu wrote:
> > ��..
> > Thx a lot!
> > Btw what I should do? Should I replace them with older version plugins?
> >
> >
> > 2008/10/1 Saminda Wijeratne <[EMAIL PROTECTED]  >>
> >
> > The latest available plugin gives that error because it is giving
> > ClassDefNotFound exception for class
> > javax.xml.stream.XMLStreamException. This class resides in
> > geranimo-stax.
> >
> > Yefeng Liu wrote:
> > > Axis2 1.4.1
> > > Axis2 Codegen Wizard 1.3.0
> > > Axis2 Service Archiver 1.3.0
> > >
> > > All are the latest version I think.
> > >
> > > 2008/10/1 keith chapman <[EMAIL PROTECTED]
> > 
> > > >>
> > >
> > > Which version of Axis2/ The eclipse plugin are you using?
> > >
> > > Thanks,
> > > Keith.
> > >
> > > 2008/9/30 Danny LIU <[EMAIL PROTECTED]
> >   > >>
> > >
> > > Hi everyone!
> > >
> > > Im a new learner of axis2, and basically Im following a
> > > tutorial to study it
> > > right now.
> > >
> > > My problem is I got a strange exception when I try to generate
> > > Java code from WSDL file
> > > using eclipse's plugin -Axis2 Code Generator .
> > > The exception is " java.lang.reflect.InvocationTargetException"
> > > does anyone know how to fix this?
> > >
> > > Thx in advance.
> > >
> > > Here is my wsdl code:
> > >
> > > 
> > >  > > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
> > > xmlns:tns="http://www.example.org/helloAxis2/";
> > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; name="helloAxis2"
> > > targetNamespace="http://www.example.org/helloAxis2/";>
> > > 
> > >  > > targetNamespace="http://www.example.org/helloAxis2/";>
> > > 
> > > 
> > > 
> > > 
> > > 
> > >  > > name="Response" />
> > > 
> > > 
> > >  > > name="Request" />
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >  > > transport="http://schemas.xmlsoap.org/soap/http"; />
> > > 
> > >  > > soapAction="http://localhost:8080/axis2/services/helloAxis2"; />
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >  > > location="http://localhost:8080/axis2/services/helloAxis2"; />
> > > 
> > > 
> > > 
> > >
> > > --
> > >
> > > 天生万物以养人
> > >
> > > 人无一德以报天
> > >
> > >
> > >
> > >
> > > --
> > > Keith Chapman
> > > Senior Software Engineer
> > > WSO2 Inc.
> > > Oxygenating the Web Service Platform.
> > > http://wso2.org/
> > >
> > > blog: http://www.keith-chapman.org
> > >
> > >
> > >
> > >
> > > --
> > >
> > > 天生万物以养人
> > >
> > > 人无一德以报天
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > 
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> >
> >
> >
> >
> > --
> >
> > 天生万物以养人
> >
> > 人无一德以报天
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 

  天生万物以养人

人无一德以报天