Hi

thank you for your suggestion. if i reach desperation i will certainly customize axis for my own use, but i'd certainly like to stick to the "standard axis" if at all possible. otherwise when i want to switch to a new version of axis latter on, i would be loosing by custom changes.

what i am ideally looking for is a way to "plug" (or whatever other term you prefer) an extra thing that would change axis behaviour without modifying Axis source and making my personal axis.jar. I would be perfectly able to do that if it's the only solution...

I think this is an interesting challenge to people with Axis experience, so i'd be more than happy to hear more opinions :) .

Regards,
   Razvan

Davanum Srinivas wrote:
easier would be to edit axiom source
(http://svn.apache.org/repos/asf/webservices/commons/trunk/modules/axiom/src/org/apache/axiom/soap/SOAPConstants.java)

and build a jar for your own use.

-- dims

On 5/22/06, Razvan Dani <[EMAIL PROTECTED]> wrote:

 Hi Anne

Thank you for your suggestions. However as a person that only found Axis few days ago, i am not sure how would i go about inserting and intermediary into my message path to transform the message (i.e. replace occurences of
soapenv with soap-env).

I would appreciate a lot if could could just point me to a sample code or
to some documentation where that is explained.

 Regards,
     Razvan



 Anne Thomas Manes wrote:
Axis does not provide this type of configuration option. Either construct the message programmatically using JAXP or insert an intermediary into your
message path to transform the message.

 Anne


On 5/22/06, Razvan Dani <[EMAIL PROTECTED]> wrote:
> Hi
>
> I am not sure if this is the right place to address this, but i'd
> appreciate some feedback if possible, because i already made lots of
> queries on the internet about this issue with no success.
>
> My problem is the following:
> - i am using WSDL to Java ant task to generate classes against a WSDL.
> - when i make a method call on the generated Stub (so notice that i am
> not constructing the envelope by hand neither i use the Call class
> directly), Axis is constructing the envelope as this:
> <soapenv:Envelope
>
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";....
>
> This works just fine for many Web Services, but in my particular case,
> the Web Service implementation on the server side is "hardcoded" to only
> be able to accept
> <soap-env:Envelope
> xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/
"
>
> I know this is an issue that should be fixed on the server part since
> the Web Service specs is flexible to allow any prefix for the envelope
> as long as the name space URL is correct. But i don't have control on
> the server part and thus i would like to know if this issue can be
> tackled from Axis.
>
> So the question is whether it is possible to make some configuration in > Axis so that i can specify at runtime what prefix should be used for the
> envelope (e.g. soap-env instead of soapenv)?
>
> Many thanks in advance if i receive any answer to this issue.
>
> Regards,
>    Razvan
>
> --
> Razvan Dani
>
> Senior Java Developer
>
> ARoBS Transilvania Software
>
> 11 Donath Str , M4 - 28
> 400301 Cluj-Napoca, Romania
>
> Main:   +40 264 598 204
> Fax:    +40 264 598 426
> email:  [EMAIL PROTECTED]
> www.ARoBS.com
>
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
[EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>




--
Razvan Dani

Senior Java Developer

ARoBS Transilvania Software

11 Donath Str , M4 - 28
400301 Cluj-Napoca, Romania

Main: +40 264 598 204
Fax: +40 264 598 426
email: [EMAIL PROTECTED]
www.ARoBS.com





--
Razvan Dani

Senior Java Developer

ARoBS Transilvania Software

11 Donath Str , M4 - 28
400301 Cluj-Napoca, Romania

Main:   +40 264 598 204
Fax:    +40 264 598 426
email:  [EMAIL PROTECTED]
www.ARoBS.com


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

Reply via email to