Is Axis 1.4 Supports Operations with custom java object as input

[Durga Srinivasu]

Hai All,

I have a question on Axis 1.4. 

Is axis supports web service operations with complex java object as input (Ex: 
addUser(String userName,NewUser details))?. 

I am able to deploy the service with custom java object "NewUser" input. But 
when i try to invoke the same service with soap client, i am getting the 
following soap fault message.

SOAP RESPONSE:

http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
   
  
 soapenv:Server.userException
 org.xml.sax.SAXException: operation description is 
missing parameter description!
 
http://xml.apache.org/axis/";>srinivasu
 
  
   


SOAP REQUEST:

http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:pwc="http://proactivenet.com/webservices/pwcommand/";>
   
  EX
   
   
  
 EX
 
EX
EX
EX
 
  
   


addUser schema definition in wsdl:

 
  
 
 
 
  
 

 
  
   
 
 
   
  
 


If anybody is facing the similar issue, please let me know.

thanks
Durga Srinivasu

Re: [Axis2] -New feature : Adding custom deployer

[Thilina Gunarathne]

I'm definitely +1 for this..  In fact I started doing the same couple
of days ago :)..

BTW it would be great if you can provide more details of the interface
which you are going to provide..

Thanks,
Thilina

On 2/9/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:

Hi All;

The BOF we had at the ApcheConUS 2006 I suggested the idea of supporting
custom deployers into Axis2. The main reason with that was in Axis2 we
can not easily deploy new file extension (as an example JavaScript ) ,
and In JAXWS side they are doing all the initialization at the
MessageReceiver level since they do not have a deployment plug point. So
with this approach we have much more flexibility ,among them

- If you do not like the directory name "services" and "modules" then
you can easily changed that to whatever you like
- If you do not like the .aar , .mar file extension you can easily
change that to whatever you like
- If you want make a javaScript into a AxisService (or Module) and you
want to deploy that into a new directory inside the repository (let's
say folder called "javaScript") you can easily do that.
- If you want to deploy test file as a service, module, Transport or
even Parameter you can do that
- Among the most useful thing we can easily write a new Deployer to make
Axis1 service into Axis2


I spent last night and completed the new approach (I am very sorry for
implementing the feature w.o letting know the community), which
introduces a new Interface called "Deployer" with fore method. If you
want to write a new Deployer then you need to implement that .

I changed the current Deployment mechanism to work the new approach.

With new approach if you want to add new Deployer, then the following
are the steps;
- First write a class implementing Deployer interface
- Second add the following entry to to axis2.xml



I think this is one of the very cool features I added to Axis2 and hope
no one will -1 on this , I will commmit the changes soon. If everything
goes well we can keep the code else we can revert.

here is my +1 for this feature as well as for commiting the code.

Thanks
Deepal


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





--
Thilina Gunarathne
WSO2, Inc.; http://www.wso2.com/
Home page: http://webservices.apache.org/~thilina/
Blog: http://thilinag.blogspot.com/

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

Re: WSDL2Java choice handling

[Amila Suriarachchi]

Adb currently does not support this type of schemas,


  
  
  
  
  
  
  
  
  
  
  

it does not process any element other than Element and Any under sequence
element. it supports only the xsd:choices directly under complex type.


--
Amila Suriarachchi,
WSO2 Inc.

[Axis2] -New feature : Adding custom deployer

[Deepal Jayasinghe]

Hi All;

The BOF we had at the ApcheConUS 2006 I suggested the idea of supporting
custom deployers into Axis2. The main reason with that was in Axis2 we
can not easily deploy new file extension (as an example JavaScript ) ,
and In JAXWS side they are doing all the initialization at the
MessageReceiver level since they do not have a deployment plug point. So
with this approach we have much more flexibility ,among them

- If you do not like the directory name “services” and “modules” then
you can easily changed that to whatever you like
- If you do not like the .aar , .mar file extension you can easily
change that to whatever you like
- If you want make a javaScript into a AxisService (or Module) and you
want to deploy that into a new directory inside the repository (let's
say folder called “javaScript”) you can easily do that.
- If you want to deploy test file as a service, module, Transport or
even Parameter you can do that
- Among the most useful thing we can easily write a new Deployer to make
Axis1 service into Axis2


I spent last night and completed the new approach (I am very sorry for
implementing the feature w.o letting know the community), which
introduces a new Interface called “Deployer” with fore method. If you
want to write a new Deployer then you need to implement that .

I changed the current Deployment mechanism to work the new approach.

With new approach if you want to add new Deployer, then the following
are the steps;
- First write a class implementing Deployer interface
- Second add the following entry to to axis2.xml



I think this is one of the very cool features I added to Axis2 and hope
no one will -1 on this , I will commmit the changes soon. If everything
goes well we can keep the code else we can revert.

here is my +1 for this feature as well as for commiting the code.

Thanks
Deepal


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

New Features to ADB

[Amila Suriarachchi]

Recently I fixed some bugs and added new features to support both simple
type and complex type restrictions and extensions.
So now axis2-adb supports all these features

1. Simple type restrictions & extensions
  Enumeration support
  Pattern and other restrictions support
2.  Simple type  Union
3.  Simple type  List
4. Complex type restrictions & extensions

Apart from this adb now fully support the xsd:QName for all types.

I saw in mailing list that some wsdls fail to generated code with adb data
binding due to not present of these features.
So please try out now.

Amila.

--
Amila Suriarachchi,
WSO2 Inc.

Ws-Policy HttpsToken SSL client cert

[Elena Neroslavskaya]

Hello,

I'm looking for a sample configuration policy to
add client ssl certificate to https transport.
If  Httpstoken defined in policy : 

   
 

 
   

How to set the certificate identifier and store for the transport ssl?

Thank you

Re: axis2 Version 1.1.1 documentation seems wrong on uploading services

[Ajith Ranabahu]

Hi Peter.
AFAIK the default behavior of tomcat is to
1. automatically deploy .war files it finds inside the webapp directory
2. expand the war files.

The documentation is based on this default behavior. in fact bulk of
our servlet testing takes place on tomcat and we have not seen this
behavior so far with a default installation of tomcat, so I'm guessing
this is something to do with one of your settings. Did you install
tomcat with the installer ?

Ajith

On 2/8/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:

Peter,

Which app server are you using? that documentation is geared towards tomcat.

thanks,
dims


On 2/8/07, Peter Rosner <[EMAIL PROTECTED]> wrote:
>
>
> Version 1.1.1 axis2 on-line documentation for deploying the sample services
> quickstart and quickstartadb (and maybe others) appears wrong. It looks to
> me that one can only deploy services via using the administrator's upload
> service, not via placing the aar file in the axis2\WEB_INF\services
> directory under webapps. I am using a Windows/XP machine.
>
> Firstly ( a relatively minor point) it talks about placing axis2.war in the
> webapps directory of the J2EE server (in my case
> Tomcat 5.5). Then it implies that this will be expanded out automatically.
> This doesn't happen for me at least. I needed to expand it out myself (in
> order to be able to follow subsequent instructions about depositing .aar
> files into the axis2\WEB_INF\services directory). I  extracted it into an
> axis2 top level folder which I had to explicitly create under webapps. The
> documentation does not make this clear
>
> More seriously, even when I do this and copy, for example, the
> StockQuoteService.aar across, the service is not being seen at all. I can
> only get successful deployment of the service if I use the upload
> administrator service. I had to scrabble around in the axis2.xml to find out
> the user name and password that I needed to enter before I could get to this
> service.
>
> Am I  missing something, or am I right about the documentation being
> inaccurate on several counts?


--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

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





--
Ajith Ranabahu

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

Re: axis2 Version 1.1.1 documentation seems wrong on uploading services

[Davanum Srinivas]

Peter,

Which app server are you using? that documentation is geared towards tomcat.

thanks,
dims


On 2/8/07, Peter Rosner <[EMAIL PROTECTED]> wrote:



Version 1.1.1 axis2 on-line documentation for deploying the sample services
quickstart and quickstartadb (and maybe others) appears wrong. It looks to
me that one can only deploy services via using the administrator's upload
service, not via placing the aar file in the axis2\WEB_INF\services
directory under webapps. I am using a Windows/XP machine.

Firstly ( a relatively minor point) it talks about placing axis2.war in the
webapps directory of the J2EE server (in my case
Tomcat 5.5). Then it implies that this will be expanded out automatically.
This doesn't happen for me at least. I needed to expand it out myself (in
order to be able to follow subsequent instructions about depositing .aar
files into the axis2\WEB_INF\services directory). I  extracted it into an
axis2 top level folder which I had to explicitly create under webapps. The
documentation does not make this clear

More seriously, even when I do this and copy, for example, the
StockQuoteService.aar across, the service is not being seen at all. I can
only get successful deployment of the service if I use the upload
administrator service. I had to scrabble around in the axis2.xml to find out
the user name and password that I needed to enter before I could get to this
service.

Am I  missing something, or am I right about the documentation being
inaccurate on several counts?



--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

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

Re: [Axis2] hmac-sha1 Signature

[Ruchith Fernando]

Hi Maxim,

Right now it is not possible to do this with an arbitrary key with Rampart.

But if you explain your requirement in detail (message samples will be
great) I can have a look at how to support this scenario.

Thanks,
Ruchith

On 2/8/07, Tonkikh Maxim <[EMAIL PROTECTED]> wrote:

Hi

So? Is it possible to configure rampart?

I'd like to read something about how to configure, pass my key,...

Thanx
Maxim

-Original Message-
From: Ruchith Fernando [mailto:[EMAIL PROTECTED]
Sent: Thursday, 08 February, 2007 15:14
To: axis-user@ws.apache.org
Subject: Re: [Axis2] hmac-sha1 Signature

Hi folks,

In cases where we have to use a symmetric key and ensure integrity of a
message we use hmac-sha1 and compute the MAC value over the
canonicalized SignedInfo element and use that MAC value (base64ed) as
the SignatureValue:


 
 ...
...

...
...


I support this is the scenario that Maxim mentioned.

Do you have a scenario where you should be able to do this with an
arbitrary key that you have? Can you also let us know how you are
planning to refer to the shared key used in the signature structure.
Specifically how the "KeyInfo" element of the Signature should be setup.

Right now rampart supports this approach only with the WS-SecConv
implementation where we have to use the derived key to generate
signature as above.

Thanks,
Ruchith

On 2/8/07, Jyrki Saarinen <[EMAIL PROTECTED]> wrote:
> On Thu, 2007-02-08 at 13:58 +0200, Tonkikh Maxim wrote:
> > Hi All
> >
> > I need to use hmac-sha1 Signature.
> >
> > How can I pass my SecretKey to rampart?
>
> You need to read some cryptography, HMAC-SHA1 isn't a digital
> signature algorithm, it is a MAC (Message Authentication Code).
>
> Jyrki
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
www.ruchith.org
www.wso2.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]





--
www.ruchith.org
www.wso2.org

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

Re: Market Share of the Axis in web service industry

[Genious Soul]

Anne,
 Thanks for your response.Is it possible to  get a general idea about 
the size of the web service market as a whole?Thanks for any help.

Regards
Kash  

- Original Message 
From: Anne Thomas Manes <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org
Sent: Tuesday, February 6, 2007 8:17:33 PM
Subject: Re: Market Share of the Axis in web service industry

I seriously doubt that you will find anyone that has don't this type
of market analysis. It's almost impossible to determine the total
market share of an open source project (at least with any kind of
statistical accuracy). Axis and Axis2 certainly hold a major share of
the open source SOAP implementation market. The biggest competitors
are XFire/CeltixFire and Sun's JWSDP/Glassfish projects. I expect that
the new JBoss SOAP engine (supplied with JBoss AS and JBoss ESB) will
become a major contenter also.

Of course all these open source projects compete with the native SOAP
engines supplied with application platforms (WebSphere, WebLogic,
Oracle 10g, NetWeaver, etc.), as well as with the native SOAP engines
supplied with ESBs (WebSphere ESB, AquaLogic, Oracle ESB, Sonic ESB,
IONA Artix, Cape Clear ESB, ServiceMix, Mule, etc.)

Anne

On 2/5/07, Genious Soul <[EMAIL PROTECTED]> wrote:
>
> Hi All,
>   I would be extremely sorry if it is not the right forum to ask
> this question.I would appreciate if some one could point me to the link
> where I get the total market share of the Axis in web service industry.It
> would be extremely helpfull if someone could tell me what other stakeholders
> are in this web service industry? and how much share they have in this
> industry.Thanks for any help as it might help us in making important
> decision.
>
>
> Regards
> kash
>
>  
> Access over 1 million songs - Yahoo! Music Unlimited.

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








 

Sucker-punch spam with award-winning protection. 
Try the free Yahoo! Mail Beta.
http://advision.webevents.yahoo.com/mailbeta/features_spam.html

Re: [Axis2]

[Peter Rosner]

Hi

Since I sent the last message I have found out that the problem in my case 
was my configuration. CATALINA_HOME was pointing to another installation 
(5.0) of Tomcat. Correcting this means that all the issues I raised have now 
gone away. Apologies for leading all up the garden path! The documentation 
all seems ok now.


Pete
- Original Message - 
From: "Jones, Alan R" <[EMAIL PROTECTED]>

To: 
Sent: Thursday, February 08, 2007 11:24 PM
Subject: RE: [Axis2]



Correction...


...shows the correct version, 1.5.0._11,


..no mention of Sun.

alan



Alan R Jones
Boeing S&IS Mission Systems
Denver Engineering Center (BDEC)
303.307.3415

-Original Message-
From: Jones, Alan R
Sent: Thursday, February 08, 2007 4:22 PM
To: 'axis-user@ws.apache.org'; '[EMAIL PROTECTED]'
Subject: RE: [Axis2]

Dims,

Yes, you are right in that the issue appears to be the
jvm/jre...However, upon checking java -version in FC6, it shows the
correct version, sun 1.5.0._11, but it does not say whether it's gcj or
kaffee. It mentions Java Hotspot.  The jdk/jre was downloaded via yum
install.

I resolved the issue by setting the fork="true" attribute inside the
java task in my ant build file, thereby executing the java class file of
the client in a different JVM, external to the one that ant was
executing in.



Thanks,

alan



Alan R Jones
Boeing S&IS Mission Systems
Denver Engineering Center (BDEC)
303.307.3415

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 08, 2007 2:21 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2]

Alan,

You need to run with Sun's jvm. please run "java -version" to check
which version of jdk/jre you are using. I believe you are using the
built-in gcj or kaffee in FC6. Please get latest JDK1.5 from sun.

thanks,
dims

On 2/8/07, Jones, Alan R <[EMAIL PROTECTED]> wrote:



Hi,

I have a client written in Axis2.0 v1.0 that is launched from ant
build file. When I run it on Win XP machine, it runs fine and prints
the web service response as expected. However, when I run the same
client on Linux FC6, with same Axis2 on the same version of tomcat as
Win machine (5.5.17),

it fails with an exception containing the following (I'm showing the
first 3
lines):



java.lang.IllegalArgumentException: illegal NCName:
at gnu.xml.stream.XMLStreamWriterImpl.writeStartElement
(libgcj.so.7rh)
at
org.apache.axiom.om.impl.MTOMXMLStreamwriter.wrtieStartElement(MTOMXML
StreamWriter.java:91)
...


What seems strange is the gnu.xml line...is that FC6 related, in other



words, something that FC6 is "intercepting" and then initiating the
cascading exception? I see no reference to that package in any of the
jar files in the AXIS2 lib which is added to classpath in the ant file



at runtime.





aj




--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services
Developers

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


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




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

axis2 Version 1.1.1 documentation seems wrong on uploading services

[Peter Rosner]

Version 1.1.1 axis2 on-line documentation for deploying the sample services 
quickstart and quickstartadb (and maybe others) appears wrong. It looks to me 
that one can only deploy services via using the administrator's upload service, 
not via placing the aar file in the axis2\WEB_INF\services directory under 
webapps. I am using a Windows/XP machine.

Firstly ( a relatively minor point) it talks about placing axis2.war in the 
webapps directory of the J2EE server (in my case
Tomcat 5.5). Then it implies that this will be expanded out automatically. This 
doesn't happen for me at least. I needed to expand it out myself (in order to 
be able to follow subsequent instructions about depositing .aar files into the 
axis2\WEB_INF\services directory). I  extracted it into an  axis2 top level 
folder which I had to explicitly create under webapps. The documentation does 
not make this clear

More seriously, even when I do this and copy, for example, the 
StockQuoteService.aar across, the service is not being seen at all. I can only 
get successful deployment of the service if I use the upload administrator 
service. I had to scrabble around in the axis2.xml to find out the user name 
and password that I needed to enter before I could get to this service.

Am I  missing something, or am I right about the documentation being inaccurate 
on several counts? 

RE: [Axis2]

[Jones, Alan R]

 
Correction...

>>...shows the correct version, 1.5.0._11, 

..no mention of Sun.

alan



Alan R Jones
Boeing S&IS Mission Systems
Denver Engineering Center (BDEC)
303.307.3415

-Original Message-
From: Jones, Alan R 
Sent: Thursday, February 08, 2007 4:22 PM
To: 'axis-user@ws.apache.org'; '[EMAIL PROTECTED]'
Subject: RE: [Axis2]

Dims,

Yes, you are right in that the issue appears to be the
jvm/jre...However, upon checking java -version in FC6, it shows the
correct version, sun 1.5.0._11, but it does not say whether it's gcj or
kaffee. It mentions Java Hotspot.  The jdk/jre was downloaded via yum
install.

 I resolved the issue by setting the fork="true" attribute inside the
java task in my ant build file, thereby executing the java class file of
the client in a different JVM, external to the one that ant was
executing in.



Thanks,

alan



Alan R Jones
Boeing S&IS Mission Systems
Denver Engineering Center (BDEC)
303.307.3415

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 08, 2007 2:21 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2]

Alan,

You need to run with Sun's jvm. please run "java -version" to check
which version of jdk/jre you are using. I believe you are using the
built-in gcj or kaffee in FC6. Please get latest JDK1.5 from sun.

thanks,
dims

On 2/8/07, Jones, Alan R <[EMAIL PROTECTED]> wrote:
>
>
> Hi,
>
> I have a client written in Axis2.0 v1.0 that is launched from ant 
> build file. When I run it on Win XP machine, it runs fine and prints 
> the web service response as expected. However, when I run the same 
> client on Linux FC6, with same Axis2 on the same version of tomcat as 
> Win machine (5.5.17),
>
> it fails with an exception containing the following (I'm showing the 
> first 3
> lines):
>
>
>
> java.lang.IllegalArgumentException: illegal NCName:
> at gnu.xml.stream.XMLStreamWriterImpl.writeStartElement
> (libgcj.so.7rh)
> at
> org.apache.axiom.om.impl.MTOMXMLStreamwriter.wrtieStartElement(MTOMXML
> StreamWriter.java:91)
> ...
>
>
> What seems strange is the gnu.xml line...is that FC6 related, in other

> words, something that FC6 is "intercepting" and then initiating the 
> cascading exception? I see no reference to that package in any of the 
> jar files in the AXIS2 lib which is added to classpath in the ant file

> at runtime.
>
>
>
>
>
> aj
>


--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services
Developers

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


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

RE: [Axis2]

[Jones, Alan R]

Dims,

Yes, you are right in that the issue appears to be the
jvm/jre...However, upon checking java -version in FC6, it shows the
correct version, sun 1.5.0._11, but it does not say whether it's gcj or
kaffee. It mentions Java Hotspot.  The jdk/jre was downloaded via yum
install.

 I resolved the issue by setting the fork="true" attribute inside the
java task in my ant build file, thereby executing the java class file of
the client in a different JVM, external to the one that ant was
executing in.



Thanks,

alan



Alan R Jones
Boeing S&IS Mission Systems
Denver Engineering Center (BDEC)
303.307.3415

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 08, 2007 2:21 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2]

Alan,

You need to run with Sun's jvm. please run "java -version" to check
which version of jdk/jre you are using. I believe you are using the
built-in gcj or kaffee in FC6. Please get latest JDK1.5 from sun.

thanks,
dims

On 2/8/07, Jones, Alan R <[EMAIL PROTECTED]> wrote:
>
>
> Hi,
>
> I have a client written in Axis2.0 v1.0 that is launched from ant 
> build file. When I run it on Win XP machine, it runs fine and prints 
> the web service response as expected. However, when I run the same 
> client on Linux FC6, with same Axis2 on the same version of tomcat as 
> Win machine (5.5.17),
>
> it fails with an exception containing the following (I'm showing the 
> first 3
> lines):
>
>
>
> java.lang.IllegalArgumentException: illegal NCName:
> at gnu.xml.stream.XMLStreamWriterImpl.writeStartElement
> (libgcj.so.7rh)
> at
> org.apache.axiom.om.impl.MTOMXMLStreamwriter.wrtieStartElement(MTOMXML
> StreamWriter.java:91)
> ...
>
>
> What seems strange is the gnu.xml line...is that FC6 related, in other

> words, something that FC6 is "intercepting" and then initiating the 
> cascading exception? I see no reference to that package in any of the 
> jar files in the AXIS2 lib which is added to classpath in the ant file

> at runtime.
>
>
>
>
>
> aj
>


--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services
Developers

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


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

Re: [Axis2]

[Davanum Srinivas]

Alan,

You need to run with Sun's jvm. please run "java -version" to check
which version of jdk/jre you are using. I believe you are using the
built-in gcj or kaffee in FC6. Please get latest JDK1.5 from sun.

thanks,
dims

On 2/8/07, Jones, Alan R <[EMAIL PROTECTED]> wrote:



Hi,

I have a client written in Axis2.0 v1.0 that is launched from ant build
file. When I run it on Win XP machine, it runs fine and prints the web
service response as expected. However, when I run the same client on Linux
FC6, with same Axis2 on the same version of tomcat as Win machine (5.5.17),

it fails with an exception containing the following (I'm showing the first 3
lines):



java.lang.IllegalArgumentException: illegal NCName:
at gnu.xml.stream.XMLStreamWriterImpl.writeStartElement
(libgcj.so.7rh)
at
org.apache.axiom.om.impl.MTOMXMLStreamwriter.wrtieStartElement(MTOMXMLStreamWriter.java:91)
...


What seems strange is the gnu.xml line...is that FC6 related, in other
words, something that FC6 is "intercepting" and then initiating the
cascading exception? I see no reference to that package in any of the jar
files in the AXIS2 lib which is added to classpath in the ant file at
runtime.





aj




--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

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

RE: Axis 1.4 Attachements sample

[Bo Xu]

You need the following jar files. I believe they are in the source
distribution package, not in binary package.

 

activation.jar

mailapi_1_3_1.jar

 

 

  _  

From: asaf.lahav [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 08, 2007 11:38 AM
To: axis-user@ws.apache.org
Subject: Axis 1.4 Attachements sample

 

Hi all,

 

I'm trying to execute the Attachments sample which is coming with the Axis
1.4 samples and its not going well.

 

For some reason I'm getting the following line on my Eclipse console:

-Unable to find required classes (javax.activation.DataHandler and
javax.mail.internet.MimeMultipart). Attachment support is disabled.

 

And the following exception when executing the actual invoke statement:

java.lang.RuntimeException: No support for attachments

  at org.apache.axis.client.Call.setRequestMessage(Call.java:2176)

  at org.apache.axis.client.Call.invoke(Call.java:1790)

  at attachments.TestRef.testit(TestRef.java:173)

  at attachments.TestRef.main(TestRef.java:301)

 

 

Any help would be appreciated.

Thanks

Axis 1.4 Attachements sample

[asaf.lahav]

Hi all,

 

I'm trying to execute the Attachments sample which is coming with the Axis
1.4 samples and its not going well.

 

For some reason I'm getting the following line on my Eclipse console:

-Unable to find required classes (javax.activation.DataHandler and
javax.mail.internet.MimeMultipart). Attachment support is disabled.

 

And the following exception when executing the actual invoke statement:

java.lang.RuntimeException: No support for attachments

  at org.apache.axis.client.Call.setRequestMessage(Call.java:2176)

  at org.apache.axis.client.Call.invoke(Call.java:1790)

  at attachments.TestRef.testit(TestRef.java:173)

  at attachments.TestRef.main(TestRef.java:301)

 

 

Any help would be appreciated.

Thanks

[Axis2]

[Jones, Alan R]

Hi,
 
I have a client written in Axis2.0 v1.0 that is launched from ant build
file. When I run it on Win XP machine, it runs fine and prints the web
service response as expected. However, when I run the same client on
Linux FC6, with same Axis2 on the same version of tomcat as Win machine
(5.5.17),
 
it fails with an exception containing the following (I'm showing the
first 3 lines):
 
 
 
java.lang.IllegalArgumentException: illegal NCName:
at gnu.xml.stream.XMLStreamWriterImpl.writeStartElement
(libgcj.so.7rh)
at
org.apache.axiom.om.impl.MTOMXMLStreamwriter.wrtieStartElement(MTOMXMLSt
reamWriter.java:91)
...
 
What seems strange is the gnu.xml line...is that FC6 related, in other
words, something that FC6 is "intercepting" and then initiating the
cascading exception? I see no reference to that package in any of the
jar files in the AXIS2 lib which is added to classpath in the ant file
at runtime.
 



aj 

FW: [Axis2] hmac-sha1 Signature

[Tonkikh Maxim]

SHA1 is a MAC (Message Authentication Code).

HMAC-SHA1 is used for signature generation at MSP 3.0 protocol.
 
 -Original Message-
From: Jyrki Saarinen [mailto:[EMAIL PROTECTED]
 ]
Sent: Thursday, 08 February, 2007 14:10
To: axis-user@ws.apache.org
Subject: Re: [Axis2] hmac-sha1 Signature

On Thu, 2007-02-08 at 13:58 +0200, Tonkikh Maxim wrote:
> Hi All
>
> I need to use hmac-sha1 Signature.
>
> How can I pass my SecretKey to rampart?

You need to read some cryptography, HMAC-SHA1 isn't a digital signature
algorithm, it is a MAC (Message Authentication Code).

Jyrki



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

Re: Problem retrieving ENABLE_MTOM value

[donald yang]

Hi, Maria,

   I am trying to send attachment to a web service using AXIS2-1.1.1. But
the binary data is sent by value not by reference. My client also enabled
MTOM and set optimization of OMText to TRUE. The only difference is that you
use createSoapMimeDataSource()( I don't know how you implement it), I
directly pass a  FILE variable. Could you please give me one complete
example how to sent attachment in client side? Sorry for interrupt you.

best regards
donald

On 2/8/07, Maria McCafferty <[EMAIL PROTECTED]> wrote:


Hi,

I am using Axis2 version 1.1.1. I have a client sending either and MTOM or
SwA message. Here is part of the
client code for sending an MTOM message:

ServiceClient service = new ServiceClient();
Options options = new Options();
options.setTo(targetEPR);
options.setProperty(Constants.Configuration.ENABLE_MTOM,
Constants.VALUE_TRUE);

service.setOptions(options);

OMElement payload = createPayload();

OMFactory fac = OMAbstractFactory.getOMFactory();

DataHandler dataHandler = new
DataHandler(createSoapMimeDataSource());

OMText textData = fac.createOMText(dataHandler, true);

textData.setOptimize(true);

payload.addChild(textData);

OMElement res = service.sendReceive(payload);

The SwA/MTOM request messages are fine and I am able to retrieve the
attachments.
As you can see, I set the property ENABLE_MTOM to true. However I am
having problems retrieving
the value from my server code. I am trying to access it by calling:

MessageContext.getCurrentMessageContext().isDoingMTOM()

I thought this would return true given that the option was set in the
Client. I have also checked the
list of properties, and it is not included. I am getting the same problem
when sending an SwA request -
isDoingMTOM, isDoingSwA and isDoingREST are all set to false. I realise I
can check the for the xop header,
but felt that the above should work.

Thanks,
Maria


POST /mm7 HTTP/1.1

SOAPAction: "urn:anonOutInOp"
User-Agent: Axis2
Transfer-Encoding: chunked
Content-Type: multipart/related;
boundary=MIMEBoundaryurn_uuid_29526B260178FA14181170945919864;
type="application/xop+xml"; start="<
0.urn:uuid:[EMAIL PROTECTED]>";
start-info="text/xml"; charset=UTF-8

2495
--MIMEBoundaryurn_uuid_29526B260178FA14181170945919864
content-type: application/xop+xml; charset=UTF-8; type="text/xml";
content-transfer-encoding: binary
content-id: <0.urn:uuid:[EMAIL PROTECTED]>

http://schemas.xmlsoap.org/soap/envelope/";>http://www.w3.org/2004/08/xop/include";>

.
.
.


--MIMEBoundaryurn_uuid_29526B260178FA14181170945919864
content-type: multipart/related;
.boundary="=_Part_0_23276589.1170945917770"
content-transfer-encoding: binary
content-id: <1.urn:uuid:[EMAIL PROTECTED]>

--=_Part_0_23276589.1170945917770
Content-Type: text/plain

first attachment

--=_Part_0_23276589.1170945917770
Content-Type: image/jpeg
Content-Transfer-Encoding: base64
Content-Location: attach2.jpg
Content-Id: attach2.jpg


--=_Part_0_23276589.1170945917770--



--MIMEBoundaryurn_uuid_29526B260178FA14181170945919864--



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

Re: Axis2: skeleton differences w/Axis 1.4

[Sarwar_Raza]

Hi Amila,
Your suggestion to specify the body part in the wsdl:input did not work. 
Using WSDL2JAVA, all we get is a method signature for opControlRequest 
that specifies the Security element as a param. Were you using any other 
flags to the codegen tool?

Thanks
\Sarwar



"Amila Suriarachchi" <[EMAIL PROTECTED]> 
02/08/2007 12:22 AM
Please respond to
axis-user@ws.apache.org


To
axis-user@ws.apache.org
cc

Subject
Re: Axis2: skeleton differences w/Axis 1.4






here is the problem.

you have  a soap binding input element like this


http://ws.test.sample.com/WSSecurity/"/>


and your refering message like this





In this case since there are two parts for the message you have to sepcify
which part to using in wsdl:input as follows


but having done that may results the same since there is an axis2 problem.
So the correct skelton is would be to generate only the body part.

Axis2 does not produce any bining specific details  (header part is a
binding specific)in the Skelton class. In Axis 2 if you want to handle
custom headers you have to write a handler for it.


On 2/7/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
> Hi Davanum...
> I didn't think a determination had been made that this was indeed a bug 
in
> Axis 2 which is why I have not gone the JIRA route. Was hoping someone 
could
> just tell me I was doing something wrong with regards to my WSDL (that 
would
> be an easy fix!) . I'll put something in JIRA if thats how you want me 
to
> proceed.
>
> Thanks
> \Sarwar
>
>
>  *"Davanum Srinivas" <[EMAIL PROTECTED]>*
>
> 02/07/2007 10:24 AM
>  Please respond to
> axis-user@ws.apache.org
>
>   To
> axis-user@ws.apache.org  cc
>
>  Subject
> Re: Axis2: skeleton differences w/Axis 1.4
>
>
>
>
>
>
> Sarwar,
>
> JIRA bug please :) After you create the bug, you can upload the files as
> well.
>
> thanks,
> dims
>
> On 2/6/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > Addendum to last post:
> > Neither the unwrapping nor backwards compatilbity options in the 
codegen
> tool helped - which leads me to believe that something in the WSDL I
> attached in the last message may be amiss. Our goal is to pack portions 
of a
> SOAP header and SOAP body using the WSDL definitions - any help 
appreciated.
> >
> > \Sarwar
> >
> >
> >
> >  Sarwar Raza/US/[EMAIL PROTECTED]
> >
> > 02/06/2007 10:49 PM
> >
> >
> > Please respond to
> >  axis-user@ws.apache.org
> >
> >
> > To axis-user@ws.apache.org
> >
> > cc
> >
> >
> > Subject Re: Axis2: skeleton differences w/Axis 1.4
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi Anne,
> >  Thanks for the response.
> >
> > Here is what we were able to get working with Axis 1.4, and have been
> >  struggling with Axis 2...
> >  Our input message contained TWO parts, one destined for the body, and
> the
> >  other destined for the header (we set this up in the binding).
> >  The header contains security info that gets used by WSSJ - pretty
> typical
> >  usage best we can tell.
> >
> > When we ran WSDL2Java using Axis 1.4, the resulting stubs resulted in 
a
> >  method signature for each of the methods that looked something like:
> >
> > message (header, body).
> >
> > Using Axis2, the WSDL does get parsed correctly (even though we have
> >  defined two parts for the input message), but the resulting method
> >  signature in the skeleton code always turns out like:
> >
> > message(header)
> >
> > Note the body is absent, even though it was set up to be one of the 
two
> >  parts for the message.
> >
> > Other than the fact that we need to pack our security tokens into the
> >  header, the WSDL is pretty basic. I can't rule out that 
transmogrifying
> >  the WSDL to work with Axis 2 has led to some errors creeping in - at
> this
> >  point, we've been staring at it for quite a while and can't see what 
we
> >  may be doing wrong. I'm attaching the WSDL here - perhaps someone can
> >  eyeball a problem we've missed. Note the header/body setup in the
> binding
> >  - we construct the binding by hand - is there any way to annotate a
> >  message part as being destined for the header so that we could use
> Eclipse
> >  WTP to generate the binding automagically?
> >
> > Thanks.
> >  \Sarwar
> >
> >
> >
> >
> >
> >
> >
> > "Anne Thomas Manes" <[EMAIL PROTECTED]>
> >  02/06/2007 03:08 PM
> >  Please respond to
> >  axis-user@ws.apache.org
> >
> >
> > To
> >  axis-user@ws.apache.org
> >  cc
> >
> > Subject
> >  Re: Axis2: skeleton differences w/Axis 1.4
> >
> >
> >
> >
> >
> >
> > "changing a few 'types' to 'elements'" tells me that the original WSDL
> >  was defined as style="rpc", and my guess is that it used RPC/encoded.
> >  Unfortunately, you have to do a little more than just tweak the
> >  "types" to "elements". For one thing, when using document style, your
> >  message may contain at monst one body element. That element must
> >  reference an element definition in your types section that contains
> >  all your input parameters. See my blog on wrapped document/literal 
for
> >  

Re: WSDL2Java choice handling

[danop]

After running the WSDL2Java utility, I did a text search for any references
to "clear" in the generated files but was unable to find any.   

I have included a test version of the scenario that I am running into with
the hopes of identifying where my files are in error.  Can you identify in
the below file contents where my error is?  TIA

TestSchema1.xsd 

http://mynamespace.com/TestSchema1";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:test1="http://mynamespace.com/TestSchema1";
elementFormDefault="qualified" attributeFormDefault="unqualified"
version="1.0">

































TestService.wsdl

http://myservice/Test";
xmlns="http://schemas.xmlsoap.org/wsdl/";
 xmlns:test1="http://mynamespace.com/TestSchema1";
 xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; 
 targetNamespace="http://myservice/Test"; 
 name="TestService">


http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
targetNamespace="http://myservice/Test"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
 http://mynamespace.com/TestSchema1";
schemaLocation="TestSchema1.xsd" id="test1"/>















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



http://myservice/Test"; use="literal"/>


http://myservice/Test"; use="literal"/>





http://myservice/Test"/>







Wsdl2Java command
org.apache.axis2.wsdl.WSDL2Java -uri TestService.wsdl -p com.mynamespace -o
/workingdir/axis2test -d adb -s -wv 1.1 -ss -sd 



Amila Suriarachchi wrote:
> 
> On 2/8/07, danop <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>> I have been running the Axis2 WSDL2Java utility on a wsdl that uses
>> multiple
>> xsd's that contain xsd:choices.  Everything appears to be run smoothly
>> with
>> no errors.  However, after looking at the generated files, there are no
>> references to any of the xsd:choice elements in the files.
> 
> 
> It fully supported. Lets take this simple Element
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> The generated code for this has this method
> 
>  private void clearAllSettingTrackers() {
> 
> localChoice1Tracker = false;
> 
> localChoice2Tracker = false;
> 
> }
> 
> and setter method like this
> 
>  public void setChoice1(java.lang.String param){
> 
> clearAllSettingTrackers();
> 
>if (param != null){
>   //update the setting tracker
>   localChoice1Tracker = true;
>} else {
>   localChoice1Tracker = false;
> 
>}
> 
> this.localChoice1=param;
> 
> 
>}
> 
> When ever you set one variable others tracker is set to false
> 
> then when serializing it checks whether the tracker is on
> 
> if (localChoice1Tracker){
> // some code to serialize
> }
> 
> In this way it serialize only one variable. (the variable to set finally)
> 
> As you can see ADB has implemented it in a bit smoother way using trackers
> with out using any choice elements.
> 
> 
> 
> 
> Can anyone
>> confirm whether or not Axis2 fully supports xsd:choice as part of adb
>> binding?
>>
>> TIA,
>> danop
>> --
>> View this message in context:
>> http://www.nabble.com/WSDL2Java-choice-handling-tf3189985.html#a8855376
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 
> -- 
> Amila Suriarachchi,
> WSO2 Inc.
> 
> 

-- 
View this message in context: 
http://www.nabble.com/WSDL2Java-choice-handling-tf318998

RE: MTOM and SWA related problem

[Yadav, Yogendra \(IT\)]

Hi,
Regarding requirement: One of the project here is using an external web
service. When they tested with Sun SAAJ implementation everything worked
fine and the body part header looks like:
Content-Type: text/xml; charset=utf-8

Content-Id: <[EMAIL PROTECTED]>

Since Sun SAAJ is not yet supported here, I am trying to make it work
with AXIS2's OperationClient API and the service returns an error. The
body part header looks like:
content-type: text/xml; charset=UTF-8

content-transfer-encoding: 8bit

content-id: <0.urn:uuid:[EMAIL PROTECTED]>

So, I was wondering if I could make content-transfer-encoding "binary"
or remove it altogether from header.

Out of curiosity: Does AXIS2 SwA work with SAAJ ?

Thanx
-yogen



-Original Message-
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 08, 2007 7:48 AM
To: axis-user@ws.apache.org
Cc: [EMAIL PROTECTED]
Subject: Re: MTOM and SWA related problem

Currently there is no way to set it. "8-bit" is the encoding we use for
the body part of all the SwA messages..

Can you please elaborate your requirement...

Thanks,
Thilina

On 2/7/07, Yadav, Yogendra (IT) <[EMAIL PROTECTED]>
wrote:
> Hi,
> Thanx, I reached the same conclusion.
> Setting "content-transfer-encoding: binary" in Options changes 
> transfer encoding for multipart/related and not for the part in which 
> SOAP Body goes.
>
> Any idea how to make it work? What class of Commons Http Client adds 
> the SOAP Body part to the message on the wire ?
>
> Appreciate your feedback.
> Thanx
> -yogen
>
>
> -Original Message-
> From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, February 07, 2007 8:34 AM
> To: axis-user@ws.apache.org
> Cc: [EMAIL PROTECTED]
> Subject: Re: MTOM and SWA related problem
>
> It's not possible to change the encoding of the first part..
> You can change the content-type of the attachment part by creating 
> your DataHandler using
org.apache.axiom.attachments.ConfigurableDataHandler.
> ConfigurableDataHandler is behaves same as the DataHandler and it has 
> a setContentType method..
>
> ~Thilina
>
> On 2/7/07, Yadav, Yogendra (IT) <[EMAIL PROTECTED]>
> wrote:
> > Thank you Dims.
> > One more question, when I used OperationClient API, the content-type

> > and content-transfer-encoding for first part look like this:
> > content-type: text/xml; charset=UTF-8
> > content-transfer-encoding: 8bit
> >
> > And for attachment part look like this:
> > content-type: application/octet-stream
> > content-transfer-encoding: binary
> >
> > Is it possible to make "content-transfer-encoding: binary" for the 
> > first part and "Content-Type: text/xml" for the attachment part ?
> >
> > Thanx, appreciate it.
> > -yogen
> >
> >
> >
> > -Original Message-
> > From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, February 06, 2007 4:22 PM
> > To: axis-user@ws.apache.org
> > Subject: Re: MTOM and SWA related problem
> >
> > Yogen,
> >
> > Those are from Commons HTTP Client basically means that the client 
> > is using http chunking.
> >
> > thanks,
> > dims
> >
> > On 2/6/07, Yadav, Yogendra (IT) <[EMAIL PROTECTED]>
> > wrote:
> > >
> > >
> > >
> > > Hi,
> > > Anyone who has used attachments with AXIS2 ?
> > > -yogen
> > >
> > >
> > >  
> > >  From: Yadav, Yogendra (IT)
> > > Sent: Tuesday, February 06, 2007 3:26 PM
> > > To: axis-user@ws.apache.org
> > > Subject: FW: MTOM and SWA related problem
> > >
> > >
> > >
> > >
> > > Sorry if this email is repeated multiple times. I had corporate 
> > > security issues sending attachments.
> > >
> > >  Hi,
> > > This problem is related to using MTOM and SAAJ APIs in AXIS2. I am

> > > sending attachment to a service which is implemented using Sun's 
> > > SAAJ implementation. When I use Sun's SAAJ as client to access 
> > > this service
> >
> > > everything works well. But when use AXIS2's MTOM or SAAJ 
> > > implementation, the service returns invalid response. I have 
> > > noticed
>
> > > differences in the request message being sent in eiather case in 
> > > TCPMon and noticed unusual characters in the request generated by
> > AXIS2.
> > >
> > > Can someone explain if these unusual characters are the cause of 
> > > failure or its something else.
> > >
> > > Note: If you notice AXIS2's implementations insert unusual 
> > > characters in the
> > > request:
> > > 1a97<---
> > > --MIMEBoundaryurn_uuid_1E6396FC3B5AC6B6D31170792603911
> > > 3a<---
> > > --MIMEBoundaryurn_uuid_1E6396FC3B5AC6B6D31170792603911--
> > > 0<---
> > >
> > > 1ba2<---
> > > --MIMEBoundaryurn_uuid_6F2725CFB5F14717A21170792657850
> > > 3a<---
> > > --MIMEBoundaryurn_uuid_6F2725CFB5F14717A21170792657850--
> > > 0<---
> > >
> > >
> > > I have attached  below the relevant information from TCPMon . Any 
> > > help
> >
> > > is appreciated.
> > >
> > > thanx
> > > -yogen
> > >
> > > axis2's SAAJ:
> > > 

Problem retrieving ENABLE_MTOM value

[Maria McCafferty]

Hi,

I am using Axis2 version 1.1.1. I have a client sending either and MTOM or SwA 
message. Here is part of the
client code for sending an MTOM message:

ServiceClient service = new ServiceClient();
Options options = new Options();
   options.setTo(targetEPR);
options.setProperty(Constants.Configuration.ENABLE_MTOM, 
Constants.VALUE_TRUE);

service.setOptions(options);

   OMElement payload = createPayload();

   	OMFactory fac = OMAbstractFactory.getOMFactory();  


DataHandler dataHandler = new DataHandler(createSoapMimeDataSource());

OMText textData = fac.createOMText(dataHandler, true);

textData.setOptimize(true);

payload.addChild(textData);

OMElement res = service.sendReceive(payload);

The SwA/MTOM request messages are fine and I am able to retrieve the 
attachments.
As you can see, I set the property ENABLE_MTOM to true. However I am having problems retrieving 
the value from my server code. I am trying to access it by calling:


MessageContext.getCurrentMessageContext().isDoingMTOM()

I thought this would return true given that the option was set in the Client. I 
have also checked the
list of properties, and it is not included. I am getting the same problem when sending an SwA request - 
isDoingMTOM, isDoingSwA and isDoingREST are all set to false. I realise I can check the for the xop header,

but felt that the above should work.

Thanks,
Maria


POST /mm7 HTTP/1.1

SOAPAction: "urn:anonOutInOp"
User-Agent: Axis2
Transfer-Encoding: chunked
Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_29526B260178FA14181170945919864; 
type="application/xop+xml"; start="<0.urn:uuid:[EMAIL PROTECTED]>"; 
start-info="text/xml"; charset=UTF-8

2495
--MIMEBoundaryurn_uuid_29526B260178FA14181170945919864
content-type: application/xop+xml; charset=UTF-8; type="text/xml";
content-transfer-encoding: binary
content-id: <0.urn:uuid:[EMAIL PROTECTED]>

http://schemas.xmlsoap.org/soap/envelope/";>http://www.w3.org/2004/08/xop/include";>

.
.
.


--MIMEBoundaryurn_uuid_29526B260178FA14181170945919864
content-type: multipart/related; 
.boundary="=_Part_0_23276589.1170945917770"

content-transfer-encoding: binary
content-id: <1.urn:uuid:[EMAIL PROTECTED]>

--=_Part_0_23276589.1170945917770
Content-Type: text/plain

first attachment

--=_Part_0_23276589.1170945917770
Content-Type: image/jpeg
Content-Transfer-Encoding: base64
Content-Location: attach2.jpg
Content-Id: attach2.jpg


--=_Part_0_23276589.1170945917770--



--MIMEBoundaryurn_uuid_29526B260178FA14181170945919864--



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

RE: soap over jms

[Fabio.Ferri]

Hi Paul,
of course, I have never done it. Is it simple? Can you help me?

Thanks a lot.

Regards,
Fabio

-Original Message-
From: Paul Fremantle [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 08, 2007 3:38 PM
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: Re: soap over jms

Fabio

Please can you raise a JIRA about allowing the addition of custom JMS
headers.

Thanks

Paul

On 2/8/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi all,
> I am new to Axis2 and to axis in general.
>
> I need to create an Axis2 client starting from the WSDL provided by 
> the server.
> I have gone through changing the axis2.xml file with the filowing
> information:
>
>  class="org.apache.axis2.transport.jms.JMSListener">
>  locked="false">
>  locked="false">com.tibco.tibjms.naming.TibjmsInitialContextFactory rameter>
>
>  locked="false">tibjmsnaming://localhost:7222
>  name="transport.jms.ConnectionFactoryJNDIName"
> locked="false">QueueConnectionFactory
> 
> 
>
>  class="org.apache.axis2.transport.jms.JMSSender"/>
>
> and after that I have used the wsdl2java tool to generate the java 
> stub. I have then created a simple client that was using this stub:
>
> public class testAxis2JMS {
> /**
>  * @param args
>  */
> public static void main(String[] args) {
> // TODO Auto-generated method stub
> try{
> String endpointURL = "jms:/TCM.INTEGRAT.REQ.ADDRESS?"
> +
> "transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory"
> + "&java.naming.factory.initial="
>   +
> "com.tibco.tibjms.naming.TibjmsInitialContextFactory"
> +
> "&java.naming.provider.url=tibjmsnaming://localhost:7222"
> + "&java.naming.security.principal=user"
> +
> "&java.naming.security.credentials=password";
>
> IntfTestWSfromXSDProcessServiceStub stub =
> new
> IntfTestWSfromXSDProcessServiceStub(endpointURL);
> Indirizzo ind = new Indirizzo();
> ind.setCitta("Rome");
> ind.setNumero(2);
> ind.setVia("blabla");
>
> Output out = stub.TestWSfromXSDProcessOp(ind);
> System.out.println("Code : " + out.getCode());
> System.out.println("Me : " + out.getMsg());
> } catch(Exception e){
> e.printStackTrace();
> System.out.println("\n\n\n");
> }
>
> }
> }
>
> Now when I send the request to the jms server the message is 
> successfully sent. The problem is that the web service that I am 
> calling needs to have some more information on the JMS header sent 
> from my client to the jms server.
>
>  The jms message sent look like this:
>  $Header:
> JMSMessageID=ID:EMS-SERVER.8A445C9FBB14:3
> JMSTimestamp=Wed Feb 07 17:18:09 CET 2007 
> JMSDestination=Queue[TCM.INTEGRAT.REQ.ADDRESS]
> JMSDeliveryMode=PERSISTENT
> JMSCorrelationID=null
> JMSType=null
> JMSReplyTo=Queue[$TMP$.EMS-SERVER.8A445C9FBB14.3]
> JMSPriority=4
> $Properties:
> SOAPAction="test/Axis2"
> $Body:
>  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> der
> /> xmlns:ns1="http://www.tibco.com/schemas/eChannel/Schema.xsd";> a>Romeblabla2<
> /ns1:Indirizzo>
>
> The problem is that it should look like this:
>
> $Header:
> JMSMessageID=ID:EMS-SERVER.8A445C9FBB184:8
> JMSTimestamp=Thu Feb 08 10:09:16 CET 2007 
> JMSDestination=Queue[TCM.INTEGRAT.REQ.ADDRESS]
> JMSDeliveryMode=PERSISTENT
> JMSCorrelationID=null
> JMSType=null
> JMSReplyTo=Queue[$TMP$.EMS-SERVER.8A445C9FBB185.7]
> JMSPriority=4
> $Properties:
> Content_Type=application/xml; charset="utf-8"
> Mime_Version=1.0
> SoapAction="test/Axis2"
> $Body:
>  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> der
> /> xmlns:ns1="http://www.tibco.com/schemas/eChannel/Schema.xsd";> a>Romeblabla2<
> /ns1:Indirizzo>
>
> There are this two properties in the jms message header (Content_Type 
> and
> Mime_Version) that I need to add in order to make the Web Servixce 
> server work.
>
> Is it possible to do anything like this form the client side?
> I have tried to check withtin the Axis2 Api but i did not successfully

> find a way to add this information.
>
> Is there anyone that can help me?
>
> Thanks a lot in advance.
>
> Cheers,
>  Fabio


--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair

http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]

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

-
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: (Interop) - Serialization /Deseralization in .net Client c# accesssing Axis 1.4

[Kinichiro Inoguchi]

Hi Jose,

When I tested Axis2 WebService and .NET client,
elementFormDefault="qualified" in schema was needed.

If I set elementFormDefault="unqualified",
.NET client got empty (nothing) response.

How about checking your WSDL types secion ?

Regards,
kinichiro

--- José Ferreiro <[EMAIL PROTECTED]> wrote:

> Hello,
> 
> I am trying to achieve interoperability between a .net client written
> in C#
> (.net 2.0)  to access a axis 1.4 web service.
> 
> Java client access without any problem the web service and is able to
> deserialize the class in the response.
> 
> I'm using document/litteral.
> 
> When I use a c# client after generating the proxy using wsdl.exe tool
> from
> the WSDL file written by hand for axis.
> the call is successfull but I am not able to get the answer (web
> service
> response).
> All the field are null.
> 
> Does anybody knows a solution for this?
> I am thinking to use arrays as it seems there is problems when using
> classes
> (to serialize and deserialize, mainly deserialize in the .net
> client).
> 
> Any suggestion, comments, doc are welcome.
> I wish all of you a nice day.
> 
> Happy Axis
> 
> José Ferreiro
> 
> -- 
> José Ferreiro
> EPFL Communication Systems engineer
> ing.sys.com.dipl.EPFL
> 



 

Bored stiff? Loosen up... 
Download and play hundreds of games for free on Yahoo! Games.
http://games.yahoo.com/games/front

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

Re: soap over jms

[Paul Fremantle]

Fabio

Please can you raise a JIRA about allowing the addition of custom JMS headers.

Thanks

Paul

On 2/8/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:




Hi all,
I am new to Axis2 and to axis in general.

I need to create an Axis2 client starting from the WSDL provided by the
server.
I have gone through changing the axis2.xml file with the filowing
information:



com.tibco.tibjms.naming.TibjmsInitialContextFactory

tibjmsnaming://localhost:7222
QueueConnectionFactory





and after that I have used the wsdl2java tool to generate the java stub. I
have then created a simple client that was using this stub:

public class testAxis2JMS {
/**
 * @param args
 */
public static void main(String[] args) {
// TODO Auto-generated method stub
try{
String endpointURL = "jms:/TCM.INTEGRAT.REQ.ADDRESS?"
+
"transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory"
+ "&java.naming.factory.initial="
  +
"com.tibco.tibjms.naming.TibjmsInitialContextFactory"
+
"&java.naming.provider.url=tibjmsnaming://localhost:7222"
+ "&java.naming.security.principal=user"
+
"&java.naming.security.credentials=password";

IntfTestWSfromXSDProcessServiceStub stub =
new
IntfTestWSfromXSDProcessServiceStub(endpointURL);
Indirizzo ind = new Indirizzo();
ind.setCitta("Rome");
ind.setNumero(2);
ind.setVia("blabla");

Output out = stub.TestWSfromXSDProcessOp(ind);
System.out.println("Code : " + out.getCode());
System.out.println("Me : " + out.getMsg());
} catch(Exception e){
e.printStackTrace();
System.out.println("\n\n\n");
}

}
}

Now when I send the request to the jms server the message is successfully
sent. The problem is that the web service that I am calling needs to have
some more information on the JMS header sent from my client to the jms
server.

 The jms message sent look like this:
 $Header:
JMSMessageID=ID:EMS-SERVER.8A445C9FBB14:3
JMSTimestamp=Wed Feb 07 17:18:09 CET 2007
JMSDestination=Queue[TCM.INTEGRAT.REQ.ADDRESS]
JMSDeliveryMode=PERSISTENT
JMSCorrelationID=null
JMSType=null
JMSReplyTo=Queue[$TMP$.EMS-SERVER.8A445C9FBB14.3]
JMSPriority=4
$Properties:
SOAPAction="test/Axis2"
$Body:
http://schemas.xmlsoap.org/soap/envelope/";>http://www.tibco.com/schemas/eChannel/Schema.xsd";>Romeblabla2

The problem is that it should look like this:

$Header:
JMSMessageID=ID:EMS-SERVER.8A445C9FBB184:8
JMSTimestamp=Thu Feb 08 10:09:16 CET 2007
JMSDestination=Queue[TCM.INTEGRAT.REQ.ADDRESS]
JMSDeliveryMode=PERSISTENT
JMSCorrelationID=null
JMSType=null
JMSReplyTo=Queue[$TMP$.EMS-SERVER.8A445C9FBB185.7]
JMSPriority=4
$Properties:
Content_Type=application/xml; charset="utf-8"
Mime_Version=1.0
SoapAction="test/Axis2"
$Body:
http://schemas.xmlsoap.org/soap/envelope/";>http://www.tibco.com/schemas/eChannel/Schema.xsd";>Romeblabla2

There are this two properties in the jms message header (Content_Type and
Mime_Version) that I need to add in order to make the Web Servixce server
work.

Is it possible to do anything like this form the client side?
I have tried to check withtin the Axis2 Api but i did not successfully find
a way to add this information.

Is there anyone that can help me?

Thanks a lot in advance.

Cheers,
 Fabio



--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair

http://bloglines.com/blog/paulfremantle
[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] soap over jms

[Ali Sadik Kumlali]

Hi Fabio,

Yes, you can use your stubs without any modification. Just compile the custom 
sender and put it in your classpath where you run your client.

Regards,

Ali Sadik Kumlali

- Original Message 
From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org
Sent: Thursday, February 8, 2007 4:06:37 PM
Subject: RE: [Axis2] soap over jms

Hi Ali,
thanks a lot for your help.

Just one question, is the solution that you are suggesting going to be
possible after the wsdl2java tool use?

If you look at my client which one will be the right place to put this
information? I mean where should i put the code that you suggest me?
Am i still able to use the stub?

Thanks a lot i advance.

Best Regards,
Fabio

-Original Message-
From: Ali Sadik Kumlali [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 08, 2007 1:35 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] soap over jms

Hi Fabio,



AFAIK, API doesn't support custom JMS properties and you don't have an
easy solution for now.



I would suggest you follow the steps below:

- Create your custom sender (e.g. CustomJmsSender) by copying JMSSender
coming with Axis2.
Note that you should use "org.apache.axis2.transport.jms" as package
name. Since createJMSMessage() is private, we cannot just extend
JMSSender and override the method.
- Add following lines just before "return message;" statement of
createJMSMessage ().


   message.setStringProperty("Content_Type", "application/xml;
charset=\"utf-8\"  ");

   message.setStringProperty("Mime_Version", "1.0");

-   In axis2.xml, replace transport sender definition
"org.apache.axis2.transport.jms.JMSSender" with
"org.apache.axis2.transport.jms.CustomJmsSender"

Don't forget that it is in your responsibility to keep this class
compatible with the new Axis2 releases ;)

Regards,

Ali Sadik Kumlali


- Original Message 

From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>

To: axis-user@ws.apache.org

Sent: Thursday, February 8, 2007 11:14:08 AM

Subject: soap over jms



soap over jms   Hi all,  

I am new to Axis2 and to axis in general. 

  I need to create an Axis2 client starting from the WSDL provided by
the server.  

I have gone through changing the axis2.xml file with the filowing
information: 



  

com.tibco.tibjms.naming.TibjmsInitialContextFactory

  tibjmsnaming://localhost:7222  

QueueConnectionFactory  

  

 

   

  and after that I have used the wsdl2java tool to generate the java
stub. I have then created a simple client that was using this stub:

   

public class testAxis2JMS {  

/**  

 * @param args  

 */  

public static void main(String[] args) {  

// TODO Auto-generated method stub  

try{  

String endpointURL = "jms:/TCM.INTEGRAT.REQ.ADDRESS?"  

+
"transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory"  

+ "&java.naming.factory.initial="   

  +
"com.tibco.tibjms.naming.TibjmsInitialContextFactory"  

+
"&java.naming.provider.url=tibjmsnaming://localhost:7222"  

+ "&java.naming.security.principal=user"  

+ "&java.naming.security.credentials=password";


  

IntfTestWSfromXSDProcessServiceStub stub =   

new
IntfTestWSfromXSDProcessServiceStub(endpointURL);  

Indirizzo ind = new Indirizzo();  

ind.setCitta("Rome");  

ind.setNumero(2);  

ind.setVia("blabla");  

  

Output out = stub.TestWSfromXSDProcessOp(ind);  

System.out.println("Code : " + out.getCode());  

System.out.println("Me : " + out.getMsg());  

} catch(Exception e){  

e.printStackTrace();  

System.out.println("\n\n\n");  

} 

  }  

} 

  Now when I send the request to the jms server the message is
successfully sent. The problem is that the web service that I am calling
needs to have some more information on the JMS header sent from my
client to the jms server.

 

 The jms message sent look like this:

 $Header:  

JMSMessageID=ID:EMS-SERVER.8A445C9FBB14:3  

JMSTimestamp=Wed Feb 07 17:18:09 CET 2007  

JMSDestination=Queue[TCM.INTEGRAT.REQ.ADDRESS]  

JMSDeliveryMode=PERSISTENT  

JMSCorrelationID=null  

JMSType=null  

JMSReplyTo=Queue[$TMP$.EMS-SERVER.8A445C9FBB14.3]  

JMSPriority=4  

$Properties:  

SOAPAction="test/Axis2"  

$Body:  

http://schemas.xmlsoap.org/soap/envelope/";>http://www.tibco.com/schemas/eChannel/Schema.xsd";>
Romeblabla2

  The problem is that it should look like this: 

  $Header:  

JMSMessageID=ID:EMS-SERVER.8A445C9FBB184:8  

JMSTimestamp=Thu Feb 08 10:09:16 CET 2007  

JMSDestination=Queue[TCM.INTEGRAT.REQ.ADDRESS]  

JMSDeliveryMode=PERSISTENT  

JMSCorrelationID=null  

JMSType=null  

RE: [Axis2] soap over jms

[Fabio.Ferri]

Hi Ali,
thanks a lot for your help.

Just one question, is the solution that you are suggesting going to be
possible after the wsdl2java tool use?

If you look at my client which one will be the right place to put this
information? I mean where should i put the code that you suggest me?
Am i still able to use the stub?

Thanks a lot i advance.

Best Regards,
Fabio

-Original Message-
From: Ali Sadik Kumlali [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 08, 2007 1:35 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] soap over jms

Hi Fabio,



AFAIK, API doesn't support custom JMS properties and you don't have an
easy solution for now.



I would suggest you follow the steps below:

- Create your custom sender (e.g. CustomJmsSender) by copying JMSSender
coming with Axis2.
Note that you should use "org.apache.axis2.transport.jms" as package
name. Since createJMSMessage() is private, we cannot just extend
JMSSender and override the method.
- Add following lines just before "return message;" statement of
createJMSMessage ().


   message.setStringProperty("Content_Type", "application/xml;
charset=\"utf-8\"  ");

   message.setStringProperty("Mime_Version", "1.0");

-   In axis2.xml, replace transport sender definition
"org.apache.axis2.transport.jms.JMSSender" with
"org.apache.axis2.transport.jms.CustomJmsSender"

Don't forget that it is in your responsibility to keep this class
compatible with the new Axis2 releases ;)

Regards,

Ali Sadik Kumlali


- Original Message 

From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>

To: axis-user@ws.apache.org

Sent: Thursday, February 8, 2007 11:14:08 AM

Subject: soap over jms



soap over jms   Hi all,  

I am new to Axis2 and to axis in general. 

  I need to create an Axis2 client starting from the WSDL provided by
the server.  

I have gone through changing the axis2.xml file with the filowing
information: 



  

com.tibco.tibjms.naming.TibjmsInitialContextFactory

  tibjmsnaming://localhost:7222  

QueueConnectionFactory  

  

 

   

  and after that I have used the wsdl2java tool to generate the java
stub. I have then created a simple client that was using this stub:

   

public class testAxis2JMS {  

/**  

 * @param args  

 */  

public static void main(String[] args) {  

// TODO Auto-generated method stub  

try{  

String endpointURL = "jms:/TCM.INTEGRAT.REQ.ADDRESS?"  

+
"transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory"  

+ "&java.naming.factory.initial="   

  +
"com.tibco.tibjms.naming.TibjmsInitialContextFactory"  

+
"&java.naming.provider.url=tibjmsnaming://localhost:7222"  

+ "&java.naming.security.principal=user"  

+ "&java.naming.security.credentials=password";


  

IntfTestWSfromXSDProcessServiceStub stub =   

new
IntfTestWSfromXSDProcessServiceStub(endpointURL);  

Indirizzo ind = new Indirizzo();  

ind.setCitta("Rome");  

ind.setNumero(2);  

ind.setVia("blabla");  

  

Output out = stub.TestWSfromXSDProcessOp(ind);  

System.out.println("Code : " + out.getCode());  

System.out.println("Me : " + out.getMsg());  

} catch(Exception e){  

e.printStackTrace();  

System.out.println("\n\n\n");  

} 

  }  

} 

  Now when I send the request to the jms server the message is
successfully sent. The problem is that the web service that I am calling
needs to have some more information on the JMS header sent from my
client to the jms server.

 

 The jms message sent look like this:

 $Header:  

JMSMessageID=ID:EMS-SERVER.8A445C9FBB14:3  

JMSTimestamp=Wed Feb 07 17:18:09 CET 2007  

JMSDestination=Queue[TCM.INTEGRAT.REQ.ADDRESS]  

JMSDeliveryMode=PERSISTENT  

JMSCorrelationID=null  

JMSType=null  

JMSReplyTo=Queue[$TMP$.EMS-SERVER.8A445C9FBB14.3]  

JMSPriority=4  

$Properties:  

SOAPAction="test/Axis2"  

$Body:  

http://schemas.xmlsoap.org/soap/envelope/";>http://www.tibco.com/schemas/eChannel/Schema.xsd";>
Romeblabla2

  The problem is that it should look like this: 

  $Header:  

JMSMessageID=ID:EMS-SERVER.8A445C9FBB184:8  

JMSTimestamp=Thu Feb 08 10:09:16 CET 2007  

JMSDestination=Queue[TCM.INTEGRAT.REQ.ADDRESS]  

JMSDeliveryMode=PERSISTENT  

JMSCorrelationID=null  

JMSType=null  

JMSReplyTo=Queue[$TMP$.EMS-SERVER.8A445C9FBB185.7]  

JMSPriority=4  

$Properties:  

Content_Type=application/xml; charset="utf-8"  

Mime_Version=1.0  

SoapAction="test/Axis2"  

$Body:  

http://schemas.xmlsoap.org/soap/envelope/";>http://www.tibco.com/schemas/eChannel/Schema.xsd";>
Romeblabla2

  There are this two properties in the jms message header (Con

RE: [Axis2] hmac-sha1 Signature

[Tonkikh Maxim]

Hi

So? Is it possible to configure rampart?

I'd like to read something about how to configure, pass my key,...

Thanx
Maxim 

-Original Message-
From: Ruchith Fernando [mailto:[EMAIL PROTECTED] 
Sent: Thursday, 08 February, 2007 15:14
To: axis-user@ws.apache.org
Subject: Re: [Axis2] hmac-sha1 Signature

Hi folks,

In cases where we have to use a symmetric key and ensure integrity of a
message we use hmac-sha1 and compute the MAC value over the
canonicalized SignedInfo element and use that MAC value (base64ed) as
the SignatureValue:


 
 ...
...

...
...


I support this is the scenario that Maxim mentioned.

Do you have a scenario where you should be able to do this with an
arbitrary key that you have? Can you also let us know how you are
planning to refer to the shared key used in the signature structure.
Specifically how the "KeyInfo" element of the Signature should be setup.

Right now rampart supports this approach only with the WS-SecConv
implementation where we have to use the derived key to generate
signature as above.

Thanks,
Ruchith

On 2/8/07, Jyrki Saarinen <[EMAIL PROTECTED]> wrote:
> On Thu, 2007-02-08 at 13:58 +0200, Tonkikh Maxim wrote:
> > Hi All
> >
> > I need to use hmac-sha1 Signature.
> >
> > How can I pass my SecretKey to rampart?
>
> You need to read some cryptography, HMAC-SHA1 isn't a digital 
> signature algorithm, it is a MAC (Message Authentication Code).
>
> Jyrki
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
www.ruchith.org
www.wso2.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] hmac-sha1 Signature

[Ruchith Fernando]

Hi folks,

In cases where we have to use a symmetric key and ensure integrity of
a message we use hmac-sha1 and compute the MAC value over the
canonicalized SignedInfo element and use that MAC value (base64ed) as
the SignatureValue:





...
...

...
...


I support this is the scenario that Maxim mentioned.

Do you have a scenario where you should be able to do this with an
arbitrary key that you have? Can you also let us know how you are
planning to refer to the shared key used in the signature structure.
Specifically how the "KeyInfo" element of the Signature should be
setup.

Right now rampart supports this approach only with the WS-SecConv
implementation where we have to use the derived key to generate
signature as above.

Thanks,
Ruchith

On 2/8/07, Jyrki Saarinen <[EMAIL PROTECTED]> wrote:

On Thu, 2007-02-08 at 13:58 +0200, Tonkikh Maxim wrote:
> Hi All
>
> I need to use hmac-sha1 Signature.
>
> How can I pass my SecretKey to rampart?

You need to read some cryptography, HMAC-SHA1 isn't a digital signature
algorithm, it is a MAC (Message Authentication Code).

Jyrki



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





--
www.ruchith.org
www.wso2.org

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

Re: MTOM and SWA related problem

[Thilina Gunarathne]

Currently there is no way to set it. "8-bit" is the encoding we use
for the body part of all the SwA messages..

Can you please elaborate your requirement...

Thanks,
Thilina

On 2/7/07, Yadav, Yogendra (IT) <[EMAIL PROTECTED]> wrote:

Hi,
Thanx, I reached the same conclusion.
Setting "content-transfer-encoding: binary" in Options changes transfer
encoding for multipart/related and not for the part in which SOAP Body
goes.

Any idea how to make it work? What class of Commons Http Client adds the
SOAP Body part to the message on the wire ?

Appreciate your feedback.
Thanx
-yogen


-Original Message-
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 07, 2007 8:34 AM
To: axis-user@ws.apache.org
Cc: [EMAIL PROTECTED]
Subject: Re: MTOM and SWA related problem

It's not possible to change the encoding of the first part..
You can change the content-type of the attachment part by creating your
DataHandler using org.apache.axiom.attachments.ConfigurableDataHandler.
ConfigurableDataHandler is behaves same as the DataHandler and it has a
setContentType method..

~Thilina

On 2/7/07, Yadav, Yogendra (IT) <[EMAIL PROTECTED]>
wrote:
> Thank you Dims.
> One more question, when I used OperationClient API, the content-type
> and content-transfer-encoding for first part look like this:
> content-type: text/xml; charset=UTF-8
> content-transfer-encoding: 8bit
>
> And for attachment part look like this:
> content-type: application/octet-stream
> content-transfer-encoding: binary
>
> Is it possible to make "content-transfer-encoding: binary" for the
> first part and "Content-Type: text/xml" for the attachment part ?
>
> Thanx, appreciate it.
> -yogen
>
>
>
> -Original Message-
> From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, February 06, 2007 4:22 PM
> To: axis-user@ws.apache.org
> Subject: Re: MTOM and SWA related problem
>
> Yogen,
>
> Those are from Commons HTTP Client basically means that the client is
> using http chunking.
>
> thanks,
> dims
>
> On 2/6/07, Yadav, Yogendra (IT) <[EMAIL PROTECTED]>
> wrote:
> >
> >
> >
> > Hi,
> > Anyone who has used attachments with AXIS2 ?
> > -yogen
> >
> >
> >  
> >  From: Yadav, Yogendra (IT)
> > Sent: Tuesday, February 06, 2007 3:26 PM
> > To: axis-user@ws.apache.org
> > Subject: FW: MTOM and SWA related problem
> >
> >
> >
> >
> > Sorry if this email is repeated multiple times. I had corporate
> > security issues sending attachments.
> >
> >  Hi,
> > This problem is related to using MTOM and SAAJ APIs in AXIS2. I am
> > sending attachment to a service which is implemented using Sun's
> > SAAJ implementation. When I use Sun's SAAJ as client to access this
> > service
>
> > everything works well. But when use AXIS2's MTOM or SAAJ
> > implementation, the service returns invalid response. I have noticed

> > differences in the request message being sent in eiather case in
> > TCPMon and noticed unusual characters in the request generated by
> AXIS2.
> >
> > Can someone explain if these unusual characters are the cause of
> > failure or its something else.
> >
> > Note: If you notice AXIS2's implementations insert unusual
> > characters in the
> > request:
> > 1a97<---
> > --MIMEBoundaryurn_uuid_1E6396FC3B5AC6B6D31170792603911
> > 3a<---
> > --MIMEBoundaryurn_uuid_1E6396FC3B5AC6B6D31170792603911--
> > 0<---
> >
> > 1ba2<---
> > --MIMEBoundaryurn_uuid_6F2725CFB5F14717A21170792657850
> > 3a<---
> > --MIMEBoundaryurn_uuid_6F2725CFB5F14717A21170792657850--
> > 0<---
> >
> >
> > I have attached  below the relevant information from TCPMon . Any
> > help
>
> > is appreciated.
> >
> > thanx
> > -yogen
> >
> > axis2's SAAJ:
> > 
> > 1a97
> >
> > --MIMEBoundaryurn_uuid_1E6396FC3B5AC6B6D31170792603911
> >
> > content-type: application/xop+xml; charset=UTF-8; type="text/xml";
> >
> > content-transfer-encoding: binary
> >
> > content-id:
> > <0.urn:uuid:[EMAIL PROTECTED]>
> >
> > sun's SAAJ
> > --
> > --=_Part_0_20918341.1170792531816
> >
> > Content-Type: text/xml; charset=utf-8
> >
> > Content-Id: <[EMAIL PROTECTED]>
> >
> >  
> >
> >
> > NOTICE: If received in error, please destroy and notify sender.
> > Sender
>
> > does not intend to waive confidentiality or privilege. Use of this
> > email is prohibited when received in error.
> >
> >  
> >
> >
> > NOTICE: If received in error, please destroy and notify sender.
> > Sender
>
> > does not intend to waive confidentiality or privilege. Use of this
> > email is prohibited when received in error.
> >
>
>
> --
> Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services
> Developers
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

Re: [Axis2] soap over jms

[Ali Sadik Kumlali]

Hi Fabio,



AFAIK, API doesn't support custom JMS properties and you don't have an easy 
solution for now.



I would suggest you follow the steps below:

- Create your custom sender (e.g. CustomJmsSender) by copying JMSSender coming 
with Axis2.
Note that you should use "org.apache.axis2.transport.jms" as package name. 
Since createJMSMessage() is private, we cannot just extend JMSSender and 
override the method.
- Add following lines just before "return message;" statement of 
createJMSMessage ().


   message.setStringProperty("Content_Type", "application/xml; 
charset=\"utf-8\"  ");

   message.setStringProperty("Mime_Version", "1.0");

-   In axis2.xml, replace transport sender definition 
"org.apache.axis2.transport.jms.JMSSender" with 
"org.apache.axis2.transport.jms.CustomJmsSender"

Don't forget that it is in your responsibility to keep this class compatible 
with the new Axis2 releases ;)

Regards,

Ali Sadik Kumlali


- Original Message 

From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>

To: axis-user@ws.apache.org

Sent: Thursday, February 8, 2007 11:14:08 AM

Subject: soap over jms



soap over jms   Hi all,  

I am new to Axis2 and to axis in general. 

  I need to create an Axis2 client starting from the WSDL provided by the 
server.  

I have gone through changing the axis2.xml file with the filowing information: 



  

com.tibco.tibjms.naming.TibjmsInitialContextFactory

  tibjmsnaming://localhost:7222  

QueueConnectionFactory  

  

 

   

  and after that I have used the wsdl2java tool to generate the java stub. I 
have then created a simple client that was using this stub:

   

public class testAxis2JMS {  

/**  

 * @param args  

 */  

public static void main(String[] args) {  

// TODO Auto-generated method stub  

try{  

String endpointURL = "jms:/TCM.INTEGRAT.REQ.ADDRESS?"  

+ 
"transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory"  

+ "&java.naming.factory.initial="   

  + "com.tibco.tibjms.naming.TibjmsInitialContextFactory"  

+ "&java.naming.provider.url=tibjmsnaming://localhost:7222"  

+ "&java.naming.security.principal=user"  

+ "&java.naming.security.credentials=password";   

  

IntfTestWSfromXSDProcessServiceStub stub =   

new IntfTestWSfromXSDProcessServiceStub(endpointURL);  

Indirizzo ind = new Indirizzo();  

ind.setCitta("Rome");  

ind.setNumero(2);  

ind.setVia("blabla");  

  

Output out = stub.TestWSfromXSDProcessOp(ind);  

System.out.println("Code : " + out.getCode());  

System.out.println("Me : " + out.getMsg());  

} catch(Exception e){  

e.printStackTrace();  

System.out.println("\n\n\n");  

} 

  }  

} 

  Now when I send the request to the jms server the message is successfully 
sent. The problem is that the web service that I am calling needs to have some 
more information on the JMS header sent from my client to the jms server.

 

 The jms message sent look like this:

 $Header:  

JMSMessageID=ID:EMS-SERVER.8A445C9FBB14:3  

JMSTimestamp=Wed Feb 07 17:18:09 CET 2007  

JMSDestination=Queue[TCM.INTEGRAT.REQ.ADDRESS]  

JMSDeliveryMode=PERSISTENT  

JMSCorrelationID=null  

JMSType=null  

JMSReplyTo=Queue[$TMP$.EMS-SERVER.8A445C9FBB14.3]  

JMSPriority=4  

$Properties:  

SOAPAction="test/Axis2"  

$Body:  

http://schemas.xmlsoap.org/soap/envelope/";>http://www.tibco.com/schemas/eChannel/Schema.xsd";>Romeblabla2

  The problem is that it should look like this: 

  $Header:  

JMSMessageID=ID:EMS-SERVER.8A445C9FBB184:8  

JMSTimestamp=Thu Feb 08 10:09:16 CET 2007  

JMSDestination=Queue[TCM.INTEGRAT.REQ.ADDRESS]  

JMSDeliveryMode=PERSISTENT  

JMSCorrelationID=null  

JMSType=null  

JMSReplyTo=Queue[$TMP$.EMS-SERVER.8A445C9FBB185.7]  

JMSPriority=4  

$Properties:  

Content_Type=application/xml; charset="utf-8"  

Mime_Version=1.0  

SoapAction="test/Axis2"  

$Body:  

http://schemas.xmlsoap.org/soap/envelope/";>http://www.tibco.com/schemas/eChannel/Schema.xsd";>Romeblabla2

  There are this two properties in the jms message header (Content_Type and 
Mime_Version) that I need to add in order to make the Web Servixce server work.

  Is it possible to do anything like this form the client side?   

I have tried to check withtin the Axis2 Api but i did not successfully find a 
way to add this information.  

  Is there anyone that can help me? 

  Thanks a lot in advance. 

  Cheers,

 Fabio 

  









 

Be a PS3 game guru.
Get your game face on with the latest PS3 news an

Re: Axis2: Security phase (Rampart) alters response

[riis]

Sorry,

I forgot to attach the wsdl.

(See attached file: URIService.wsdl)(See attached file: maTypes.xsd)(See
attached file: services.xml)


Regards
Multi-Support A/S

Torben Riis

Phone +45 96 600 600, Fax +45 96 600 601
E-mail: [EMAIL PROTECTED]
http://www.multi-support.com


   
 "Ruchith  
 Fernando" 
axis-user@ws.apache.org 
cc 
 08-02-2007 09:47  
   Subject 
   Re: Axis2: Security phase (Rampart) 
 Please respond to alters response 
 [EMAIL PROTECTED] 
  he.org   
   
   
   
   




Hi,

Can you please create a JIRA issue and add the WSDL. I'll try to
reproduce the issue.

Axis2: Security phase (Rampart) alters response

Thanks,
Ruchith

On 2/8/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I have registered a strange behaviour with Axis2 1.1.1 and rampart 1.1.
It
> seams like rampart alters the soap body response.
>
> Below are two soap response messages, taken with soapUI. One with Rampart
> enabled and one without. As you can see the elements in
> RetrieveFolderURIResponse isn't the same.
>
> Response without Rampart
> http://schemas.xmlsoap.org/soap/envelope/
> ">
>
>
>   http://www.multi-support.com/URIService/types";>
>  www.mrtg.org
>  www.google.com
>  mytest
>   
>
> 
>
> Response with rampart enabled
> http://schemas.xmlsoap.org/soap/envelope/
> ">
>
>
>   http://www.multi-support.com/URIService/types";>
>  www.mrtg.org
>  http://www.multi-support.com/xsd/matypes
> ">www.google.com
>  mytest
>   
>
> 
>
>
> If we look at the definition in the wsdl, it looks like element types
from
> RetrieveFolderURIResponse is used as element name
> in the response when rampart is enabled. But only for types referring to
> simple and complex types.
>
> Rampart enabled
> ..
>   http://www.multi-support.com/URIService/types";>
>  www.mrtg.org
>  http://www.multi-support.com/xsd/matypes
> ">www.google.com
>  mytest
>   
>
>   
> 
> 
> 
>   
> ..
>
>
> Snippet from URIService.wsdl
>xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
>   xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>   targetNamespace="http://www.multi-support.com/URIService/";
>   xmlns:ma="http://www.multi-support.com/URIService/types";
>   xmlns:mau="http://www.multi-support.com/URIService/";
>   xmlns:mat="http://www.multi-support.com/xsd/matypes";
>   xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>
>namespace="http://www.multi-support.com/xsd/matypes";
>   schemaLocation="maTypes.xsd" />
>
> 
>   
> 
>
> 
>   
> 
>   
>   
>   
> 
>   
> 
>
> Snippet from maTypes.xsd
> 
>   
> 
>
>
> Rampart is only enabled for inflow security.
>
> Snippet from Services.xml
> 
> 
>   
> UsernameToken
>
com.multisupport.maservices.PWCBHandler
> 
>   
> 
>
>
> I have enabled the SOAPMonitor and if the soapmonitorPhase is placed
before
> the Security phase, then the response looks right
> whether or not Rampart is enabled. But if I place the soapmonitorPhase
> after the Security phase, then the monitor reflects the result
> actually returned.
>
> Axis2.xml
> 
>   
>   
> 
> 
> 
> 
> 
> 
>
>
> Regards
> Multi-Support A/S
>
> Torben Riis
> 
> Phone +45 96 600 600, Fax +45 96 600 601
> E-mail: [EMAIL PROTECTED]
> http://www.multi-support.com
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
www.ruchith.org
www.wso2.org

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



URIService.wsdl
Description: Bina

Re: [Axis2] hmac-sha1 Signature

[Jyrki Saarinen]

On Thu, 2007-02-08 at 13:58 +0200, Tonkikh Maxim wrote:
> Hi All
> 
> I need to use hmac-sha1 Signature.
> 
> How can I pass my SecretKey to rampart?

You need to read some cryptography, HMAC-SHA1 isn't a digital signature
algorithm, it is a MAC (Message Authentication Code).

Jyrki



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

[Axis2] hmac-sha1 Signature

[Tonkikh Maxim]

Hi All

I need to use hmac-sha1 Signature.

How can I pass my SecretKey to rampart?

Thanx
Maxim

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

Re: Axis2: skeleton differences w/Axis 1.4

[Sarwar_Raza]

Thanks Amila,
Are there any examples for writing a handler to deal with custom headers?

Thanks
\Sarwar



"Amila Suriarachchi" <[EMAIL PROTECTED]> 
02/08/2007 12:22 AM
Please respond to
axis-user@ws.apache.org


To
axis-user@ws.apache.org
cc

Subject
Re: Axis2: skeleton differences w/Axis 1.4






here is the problem.

you have  a soap binding input element like this


http://ws.test.sample.com/WSSecurity/"/>


and your refering message like this





In this case since there are two parts for the message you have to sepcify
which part to using in wsdl:input as follows


but having done that may results the same since there is an axis2 problem.
So the correct skelton is would be to generate only the body part.

Axis2 does not produce any bining specific details  (header part is a
binding specific)in the Skelton class. In Axis 2 if you want to handle
custom headers you have to write a handler for it.


On 2/7/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
> Hi Davanum...
> I didn't think a determination had been made that this was indeed a bug 
in
> Axis 2 which is why I have not gone the JIRA route. Was hoping someone 
could
> just tell me I was doing something wrong with regards to my WSDL (that 
would
> be an easy fix!) . I'll put something in JIRA if thats how you want me 
to
> proceed.
>
> Thanks
> \Sarwar
>
>
>  *"Davanum Srinivas" <[EMAIL PROTECTED]>*
>
> 02/07/2007 10:24 AM
>  Please respond to
> axis-user@ws.apache.org
>
>   To
> axis-user@ws.apache.org  cc
>
>  Subject
> Re: Axis2: skeleton differences w/Axis 1.4
>
>
>
>
>
>
> Sarwar,
>
> JIRA bug please :) After you create the bug, you can upload the files as
> well.
>
> thanks,
> dims
>
> On 2/6/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > Addendum to last post:
> > Neither the unwrapping nor backwards compatilbity options in the 
codegen
> tool helped - which leads me to believe that something in the WSDL I
> attached in the last message may be amiss. Our goal is to pack portions 
of a
> SOAP header and SOAP body using the WSDL definitions - any help 
appreciated.
> >
> > \Sarwar
> >
> >
> >
> >  Sarwar Raza/US/[EMAIL PROTECTED]
> >
> > 02/06/2007 10:49 PM
> >
> >
> > Please respond to
> >  axis-user@ws.apache.org
> >
> >
> > To axis-user@ws.apache.org
> >
> > cc
> >
> >
> > Subject Re: Axis2: skeleton differences w/Axis 1.4
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi Anne,
> >  Thanks for the response.
> >
> > Here is what we were able to get working with Axis 1.4, and have been
> >  struggling with Axis 2...
> >  Our input message contained TWO parts, one destined for the body, and
> the
> >  other destined for the header (we set this up in the binding).
> >  The header contains security info that gets used by WSSJ - pretty
> typical
> >  usage best we can tell.
> >
> > When we ran WSDL2Java using Axis 1.4, the resulting stubs resulted in 
a
> >  method signature for each of the methods that looked something like:
> >
> > message (header, body).
> >
> > Using Axis2, the WSDL does get parsed correctly (even though we have
> >  defined two parts for the input message), but the resulting method
> >  signature in the skeleton code always turns out like:
> >
> > message(header)
> >
> > Note the body is absent, even though it was set up to be one of the 
two
> >  parts for the message.
> >
> > Other than the fact that we need to pack our security tokens into the
> >  header, the WSDL is pretty basic. I can't rule out that 
transmogrifying
> >  the WSDL to work with Axis 2 has led to some errors creeping in - at
> this
> >  point, we've been staring at it for quite a while and can't see what 
we
> >  may be doing wrong. I'm attaching the WSDL here - perhaps someone can
> >  eyeball a problem we've missed. Note the header/body setup in the
> binding
> >  - we construct the binding by hand - is there any way to annotate a
> >  message part as being destined for the header so that we could use
> Eclipse
> >  WTP to generate the binding automagically?
> >
> > Thanks.
> >  \Sarwar
> >
> >
> >
> >
> >
> >
> >
> > "Anne Thomas Manes" <[EMAIL PROTECTED]>
> >  02/06/2007 03:08 PM
> >  Please respond to
> >  axis-user@ws.apache.org
> >
> >
> > To
> >  axis-user@ws.apache.org
> >  cc
> >
> > Subject
> >  Re: Axis2: skeleton differences w/Axis 1.4
> >
> >
> >
> >
> >
> >
> > "changing a few 'types' to 'elements'" tells me that the original WSDL
> >  was defined as style="rpc", and my guess is that it used RPC/encoded.
> >  Unfortunately, you have to do a little more than just tweak the
> >  "types" to "elements". For one thing, when using document style, your
> >  message may contain at monst one body element. That element must
> >  reference an element definition in your types section that contains
> >  all your input parameters. See my blog on wrapped document/literal 
for
> >  some guidance:
> >
> >
> 
http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.html

> >
> >
> > Anne
> >
> > On 2/5/07, [EMAIL PROTECTED] <[EMAIL PROT

Re: Axis2: Security phase (Rampart) alters response

[riis]

Hi Ruchith,

Thanks for the fast answer. I have created jira AXIS2-2139.

Regards
Multi-Support A/S

Torben Riis

Phone +45 96 600 600, Fax +45 96 600 601
E-mail: [EMAIL PROTECTED]
http://www.multi-support.com


   
 "Ruchith  
 Fernando" 
axis-user@ws.apache.org 
cc 
 08-02-2007 09:47  
   Subject 
   Re: Axis2: Security phase (Rampart) 
 Please respond to alters response 
 [EMAIL PROTECTED] 
  he.org   
   
   
   
   




Hi,

Can you please create a JIRA issue and add the WSDL. I'll try to
reproduce the issue.

Axis2: Security phase (Rampart) alters response

Thanks,
Ruchith

On 2/8/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I have registered a strange behaviour with Axis2 1.1.1 and rampart 1.1.
It
> seams like rampart alters the soap body response.
>
> Below are two soap response messages, taken with soapUI. One with Rampart
> enabled and one without. As you can see the elements in
> RetrieveFolderURIResponse isn't the same.
>
> Response without Rampart
> http://schemas.xmlsoap.org/soap/envelope/
> ">
>
>
>   http://www.multi-support.com/URIService/types";>
>  www.mrtg.org
>  www.google.com
>  mytest
>   
>
> 
>
> Response with rampart enabled
> http://schemas.xmlsoap.org/soap/envelope/
> ">
>
>
>   http://www.multi-support.com/URIService/types";>
>  www.mrtg.org
>  http://www.multi-support.com/xsd/matypes
> ">www.google.com
>  mytest
>   
>
> 
>
>
> If we look at the definition in the wsdl, it looks like element types
from
> RetrieveFolderURIResponse is used as element name
> in the response when rampart is enabled. But only for types referring to
> simple and complex types.
>
> Rampart enabled
> ..
>   http://www.multi-support.com/URIService/types";>
>  www.mrtg.org
>  http://www.multi-support.com/xsd/matypes
> ">www.google.com
>  mytest
>   
>
>   
> 
> 
> 
>   
> ..
>
>
> Snippet from URIService.wsdl
>xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
>   xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>   targetNamespace="http://www.multi-support.com/URIService/";
>   xmlns:ma="http://www.multi-support.com/URIService/types";
>   xmlns:mau="http://www.multi-support.com/URIService/";
>   xmlns:mat="http://www.multi-support.com/xsd/matypes";
>   xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>
>namespace="http://www.multi-support.com/xsd/matypes";
>   schemaLocation="maTypes.xsd" />
>
> 
>   
> 
>
> 
>   
> 
>   
>   
>   
> 
>   
> 
>
> Snippet from maTypes.xsd
> 
>   
> 
>
>
> Rampart is only enabled for inflow security.
>
> Snippet from Services.xml
> 
> 
>   
> UsernameToken
>
com.multisupport.maservices.PWCBHandler
> 
>   
> 
>
>
> I have enabled the SOAPMonitor and if the soapmonitorPhase is placed
before
> the Security phase, then the response looks right
> whether or not Rampart is enabled. But if I place the soapmonitorPhase
> after the Security phase, then the monitor reflects the result
> actually returned.
>
> Axis2.xml
> 
>   
>   
> 
> 
> 
> 
> 
> 
>
>
> Regards
> Multi-Support A/S
>
> Torben Riis
> 
> Phone +45 96 600 600, Fax +45 96 600 601
> E-mail: [EMAIL PROTECTED]
> http://www.multi-support.com
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
www.ruchith.org
www.wso2.org

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




-
To unsubscribe, e-mail: [EMAIL

(Interop) - Serialization /Deseralization in .net Client c# accesssing Axis 1.4

[José Ferreiro]

Hello,

I am trying to achieve interoperability between a .net client written in C#
(.net 2.0)  to access a axis 1.4 web service.

Java client access without any problem the web service and is able to
deserialize the class in the response.

I'm using document/litteral.

When I use a c# client after generating the proxy using wsdl.exe tool from
the WSDL file written by hand for axis.
the call is successfull but I am not able to get the answer (web service
response).
All the field are null.

Does anybody knows a solution for this?
I am thinking to use arrays as it seems there is problems when using classes
(to serialize and deserialize, mainly deserialize in the .net client).

Any suggestion, comments, doc are welcome.
I wish all of you a nice day.

Happy Axis

José Ferreiro

--
José Ferreiro
EPFL Communication Systems engineer
ing.sys.com.dipl.EPFL

axis-wsdl2java and -w option

[Janusz Martyniak]

Hi all.

Is it any way to pass an wsdl2java -w (-wrapArrays) option the the above 
mentioned ant task ? (axis 1.4).


 any help will be appreciated,


 cheers  JM
begin:vcard
fn:Janusz Martyniak
n:Martyniak;Janusz
org:Imperial College London;HEP Group, Physics Dept.
adr:;;Prince Consort Rd, LONDON SW7 2BW;London;;SW7 2BW;United Kongdom
email;internet:[EMAIL PROTECTED]
tel;work:+44  (0)207 594 7810
tel;fax:+44  (0)207 823 8830
x-mozilla-html:FALSE
url:http://www.imperial.ac.uk
version:2.1
end:vcard


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

soap over jms

[Fabio.Ferri]

Hi all,
I am new to Axis2 and to axis in general.

I need to create an Axis2 client starting from the WSDL provided by the
server.
I have gone through changing the axis2.xml file with the filowing
information:



com.tibco.tibjms.naming.TibjmsInitialContextFactory
tibjmsnaming://localhost:7222
QueueConnectionFactory





and after that I have used the wsdl2java tool to generate the java stub.
I have then created a simple client that was using this stub:

public class testAxis2JMS {
/**
 * @param args
 */
public static void main(String[] args) {
// TODO Auto-generated method stub
try{
String endpointURL = "jms:/TCM.INTEGRAT.REQ.ADDRESS?"
+
"transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory"
+ "&java.naming.factory.initial=" 
  +
"com.tibco.tibjms.naming.TibjmsInitialContextFactory"
+
"&java.naming.provider.url=tibjmsnaming://localhost:7222"
+ "&java.naming.security.principal=user"
+ "&java.naming.security.credentials=password"; 

IntfTestWSfromXSDProcessServiceStub stub = 
new
IntfTestWSfromXSDProcessServiceStub(endpointURL);
Indirizzo ind = new Indirizzo();
ind.setCitta("Rome");
ind.setNumero(2);
ind.setVia("blabla");

Output out = stub.TestWSfromXSDProcessOp(ind);
System.out.println("Code : " + out.getCode());
System.out.println("Me : " + out.getMsg());
} catch(Exception e){
e.printStackTrace();
System.out.println("\n\n\n");
}

}
}

Now when I send the request to the jms server the message is
successfully sent. The problem is that the web service that I am calling
needs to have some more information on the JMS header sent from my
client to the jms server.

The jms message sent look like this:
$Header:
JMSMessageID=ID:EMS-SERVER.8A445C9FBB14:3
JMSTimestamp=Wed Feb 07 17:18:09 CET 2007
JMSDestination=Queue[TCM.INTEGRAT.REQ.ADDRESS]
JMSDeliveryMode=PERSISTENT
JMSCorrelationID=null
JMSType=null
JMSReplyTo=Queue[$TMP$.EMS-SERVER.8A445C9FBB14.3]
JMSPriority=4
$Properties:
SOAPAction="test/Axis2"
$Body:
http://schemas.xmlsoap.org/soap/envelope/";>http://www.tibco.com/schemas/eChannel/Schema.xsd";>
Romeblabla2

The problem is that it should look like this:

$Header:
JMSMessageID=ID:EMS-SERVER.8A445C9FBB184:8
JMSTimestamp=Thu Feb 08 10:09:16 CET 2007
JMSDestination=Queue[TCM.INTEGRAT.REQ.ADDRESS]
JMSDeliveryMode=PERSISTENT
JMSCorrelationID=null
JMSType=null
JMSReplyTo=Queue[$TMP$.EMS-SERVER.8A445C9FBB185.7]
JMSPriority=4
$Properties:
Content_Type=application/xml; charset="utf-8"
Mime_Version=1.0
SoapAction="test/Axis2"
$Body:
http://schemas.xmlsoap.org/soap/envelope/";>http://www.tibco.com/schemas/eChannel/Schema.xsd";>
Romeblabla2

There are this two properties in the jms message header (Content_Type
and Mime_Version) that I need to add in order to make the Web Servixce
server work.

Is it possible to do anything like this form the client side? 
I have tried to check withtin the Axis2 Api but i did not successfully
find a way to add this information. 

Is there anyone that can help me?

Thanks a lot in advance.

Cheers,
Fabio

Re: Axis2: Security phase (Rampart) alters response

[Ruchith Fernando]

Hi,

Can you please create a JIRA issue and add the WSDL. I'll try to
reproduce the issue.

Axis2: Security phase (Rampart) alters response

Thanks,
Ruchith

On 2/8/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:


Hi,

I have registered a strange behaviour with Axis2 1.1.1 and rampart 1.1. It
seams like rampart alters the soap body response.

Below are two soap response messages, taken with soapUI. One with Rampart
enabled and one without. As you can see the elements in
RetrieveFolderURIResponse isn't the same.

Response without Rampart
http://schemas.xmlsoap.org/soap/envelope/
">
   
   
  http://www.multi-support.com/URIService/types";>
 www.mrtg.org
 www.google.com
 mytest
  
   


Response with rampart enabled
http://schemas.xmlsoap.org/soap/envelope/
">
   
   
  http://www.multi-support.com/URIService/types";>
 www.mrtg.org
 http://www.multi-support.com/xsd/matypes
">www.google.com
 mytest
  
   



If we look at the definition in the wsdl, it looks like element types from
RetrieveFolderURIResponse is used as element name
in the response when rampart is enabled. But only for types referring to
simple and complex types.

Rampart enabled
..
  http://www.multi-support.com/URIService/types";>
 www.mrtg.org
 http://www.multi-support.com/xsd/matypes
">www.google.com
 mytest
  

  



  
..


Snippet from URIService.wsdl
http://schemas.xmlsoap.org/wsdl/soap/";
  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
  targetNamespace="http://www.multi-support.com/URIService/";
  xmlns:ma="http://www.multi-support.com/URIService/types";
  xmlns:mau="http://www.multi-support.com/URIService/";
  xmlns:mat="http://www.multi-support.com/xsd/matypes";
  xmlns:xsd="http://www.w3.org/2001/XMLSchema";>

http://www.multi-support.com/xsd/matypes";
  schemaLocation="maTypes.xsd" />


  



  

  
  
  

  


Snippet from maTypes.xsd

  



Rampart is only enabled for inflow security.

Snippet from Services.xml


  
UsernameToken
com.multisupport.maservices.PWCBHandler

  



I have enabled the SOAPMonitor and if the soapmonitorPhase is placed before
the Security phase, then the response looks right
whether or not Rampart is enabled. But if I place the soapmonitorPhase
after the Security phase, then the monitor reflects the result
actually returned.

Axis2.xml

  
  








Regards
Multi-Support A/S

Torben Riis

Phone +45 96 600 600, Fax +45 96 600 601
E-mail: [EMAIL PROTECTED]
http://www.multi-support.com


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





--
www.ruchith.org
www.wso2.org

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