Re: Axis 2 V 1.0 Another Problem

[Ali Sadik Kumlali]

Hi Christian,

Have you had a look at
http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200605.mbox/[EMAIL 
PROTECTED]

AFAIK, there is an JIRA issue regarding this.

Regards,

Ali Sadik Kumlali

--- Christian Strobel <[EMAIL PROTECTED]> wrote:

> log4j:WARN No appenders could be found for logger
> (org.apache.axiom.om.impl.builder.StAXOMBuilder).
> log4j:WARN Please initialize the log4j system properly.
> 
> I get every time this warning. I found different suggestions to solve
> that
> problem, but nothing realy works.
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

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

RE: Schema validation

[Ken Tam]

Hi 
Anne and Martin,
 
Thank 
you both for your responses. I already tried to obtain the latest WSDL but it 
wasn't available. I'll try the handler method.
 
Ken

  -Original Message-From: Anne Thomas Manes 
  [mailto:[EMAIL PROTECTED]Sent: Monday, May 22, 2006 5:26 
  AMTo: axis-user@ws.apache.orgSubject: Re: Schema 
  validationKen,I agree with Martin -- your service 
  provider should supply you with a new WSDL. Have you tried just doing a GET on 
  the service URL appended with "?wsdl"?. In the meantime, you can use a 
  handler to validate the message. Java provides native support for validation 
  in the javax.xml.validation package.Anne
  On 5/22/06, Martin 
  Gainty <[EMAIL PROTECTED]> wrote:
  Good 
Morning KenWho(m)ever is supplying the WSDL to you is responsible 
for specifying request and response for all methods along with 
specifyingparameters to those methods.Who(m)ever is changing the 
schema needs to re-gen and re-publish the WSDL A situation arose 
where my webservice is now returning a String parameter so I have 
re-published and regen'ed the WSDL to reflect the response 
string 
  Does this 
answer your question?Martin 
--* 
This email message and any files transmitted with it contain 
confidentialinformation intended only for the person(s) to whom this 
email message isaddressed.  If you have received this email 
message in error, please notify the sender immediately by telephone or 
email and destroy the originalmessage without making a 
copy.  Thank you.- Original Message 
-From: "Ken Tam" < 
[EMAIL PROTECTED]>To: Sent: 
Sunday, May 21, 2006 9:18 PMSubject: Schema validation> 
Hi all,>> I am consuming web services made available from my 
customer. I was given a > very elaborate WSDL with schemas and I was 
able to generate the stubs by> using Axis's WSDL2Java. Everything was 
working fine until the service was> changed on the customer's end. 
This causes the deserialization step to fail > as the SOAP response 
does not match the schema. The customer in this case is> a big 
company and they don't tend to respond in a timely manner. However,> 
the problem persists which I must fix. I am using Axis 1.3 and it 
doesn't> seem to validate the SOAP response with the WSDL's schema. 
How do I> configure Axis to do so? Currently, I had to spend quite a 
bit of time to> track down the mismatches. I figure if the schema is 
used to validate, it > should point out the mismatches right off to 
spare me the time to track them> down.>> 
Thanks,> Ken 
- 
> To unsubscribe, e-mail: [EMAIL PROTECTED]> 
For additional commands, e-mail: [EMAIL PROTECTED] 
>>

Newbie Question MessageElement

[O'Reilly, Barry]

Hi 
Axis,
 
I'm trying to write 
a call and need to add a message element part to my message but am unsure of how 
to achieve this. Can someone point me in the right 
direction.
 
I do not know how to 
get a handle on the SOAPEvenlope or even if I require to. I use WSDL2Java to 
generate everything. I have included the method signature and QUERY class. Any 
help or advice is great.
 
Thanks,
Barry
 
**
 
public static final String QUERY_STRING = 
Barry;
 
public SearchResult[] queryContent()throws 
Exception{  LORAXSoap soap = new 
LORAXLocator().getLORAXSoap();  QUERY query = new QUERY ( 
getBodyElement( QUERY_STRING ) );  return 
soap.queryContent(query , USERNAME, 
PASSWORD); } /**  
* @param inputStream  * @return  * @throws Exception  
*/ private MessageElement[] getBodyElement(String query)throws 
Exception{SOAPBodyElement bodyElement = new 
SOAPBodyElement( query  );  MessageElement 
messageElement[] = new MessageElement[1];  messageElement[0] = 
bodyElement;  return 
messageElement; } 
 
**
 
/** * Retrieves an array of 
SearchResult's given an (XML) Criteria * search 
term. */    public 
au.edu.thelearningfederation.lex.webservices._2004._07.LORAX.SearchResult[] 
queryContent(au.edu.thelearningfederation.lex.webservices._2004._07.Definitions.QuerySyntax.QUERY 
QUERY, java.lang.String username, java.lang.String password) throws 
java.rmi.RemoteException;
 
**
 
public class 
QUERY  implements java.io.Serializable, 
org.apache.axis.encoding.AnyContentType, 
org.apache.axis.encoding.MixedContentType {    private 
org.apache.axis.message.MessageElement [] _any;
 
    
public QUERY() {    }
 
    
public QUERY(   
org.apache.axis.message.MessageElement [] _any) 
{   this._any = 
_any;    }
.
}

Axis 2 V 1.0 Another Problem

[Christian Strobel]

log4j:WARN No appenders could be found for logger
(org.apache.axiom.om.impl.builder.StAXOMBuilder).
log4j:WARN Please initialize the log4j system properly.

I get every time this warning. I found different suggestions to solve that
problem, but nothing realy works.


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

Re: Possible to configure a module using services.xml for a client stub

[Ruchith Fernando]

Hi Kent,



Thanks for the reply. So, it means it's got to be a global thing? For
example, one can't encrypt the out message of an operation while just
sign the out message of another operation?



You can actually do this using the following :

org.apache.axis2.security.handler.config.InflowConfiguration
org.apache.axis2.security.handler.config.OutflowConfiguration

I have explained a bit about those at in at the end of my response in
this [1] mail.
You can use these configurations separately for each operation by
setting the parameter into options of the stub or service/operation
client just before invoking that operation.

Thanks,
Ruchith

[1] http://marc.theaimsgroup.com/?l=axis-dev&m=114732539613452&w=2

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

Re: Passing XML Best Practice

[Eran Chinthaka]

Anne Thomas Manes wrote:
> Attachments are problematic if you need cross-platform interoperability.

Isn't it that MTOM tries to address ?

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: envelope prefix issue

[Dies Koper]

Hello Razvan,

I have not looked at the user guides Robert pointed out to you, but I 
previously posted the following about registering handlers:


Refer to the JAX-RPC1.1 spec to see how to use a client handler in a 
portable way. I believe it goes something like this:


  sf = javax.xml.rpc.ServiceFactory.newInstance();
  SEIService si = (SEIService)sf.loadService(SEIService.class);

  // register client handler
  javax.xml.rpc.handler.HandlerRegistry hr = si.getHandlerRegistry();
  java.util.List hl = new java.util.ArrayList();
  hl.add(new 
javax.xml.rpc.handler.HandlerInfo(YourHandler.class,null,null));

  hr.setHandlerChain(new QName("http://localhost/xxx/","yourPort";),hl);

  SEI sei = si.getSEIPort();

((javax.xml.rpc.Stub)sei)._setProperty(Stub.ENDPOINT_ADDRESS_PROPERTY, url);

YourHandler should implement javax.xml.rpc.handler.Handler.

Good luck!
Dies


Razvan Dani wrote:

Hi Xinjun

Thank you very much for your useful intervention.

Could either you or otherwise another Axis guru maybe present me a brief 
example of how a Handler can be inserted in the request flow (which 
translates into: i don't know how that could be done).


Again i would like to remind that i am using WSDL2Java to generate 
classes for a given WSDL and then i am sending SOAP messages via the 
generated stub (so i am not constructing anything manually).


Regards,
   Razvan

Xinjun Chen wrote:

Hi Razvan,
 
What I can think of is to insert a Handler in the request flow. Inside 
the Handler, you can modify the message. If you are using Axis2, you 
can write a module or a handler to do that. I believe this will be 
much easier than customize Axis or Axis2.

Axis gurus, please correct me if I am not correct.
 
Regards,

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


Hi

thank you for your suggestion. if i reach desperation i will 
certainly

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

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

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

Regards,
   Razvan

Davanum Srinivas wrote:
> easier would be to edit axiom source
> (

http://svn.apache.org/repos/asf/webservices/commons/trunk/modules/axiom/src/org/apache/axiom/soap/SOAPConstants.java) 


>
>
> and build a jar for your own use.
>
> -- dims
>
> On 5/22/06, Razvan Dani < [EMAIL PROTECTED]
> wrote:
>>
>>  Hi Anne
>>
>>  Thank you for your suggestions. However as a person that only
found
>> Axis
>> few days ago, i am not sure how would i go about inserting and
>> intermediary
>> into my message path to transform the message (i.e. replace
>> occurences of
>> soapenv with soap-env).
>>
>>  I would appreciate a lot if could could just point me to a sample
>> code or
>> to some documentation where that is explained.
>>
>>  Regards,
>>  Razvan
>>
>>
>>
>>  Anne Thomas Manes wrote:
>> Axis does not provide this type of configuration option. Either
>> construct
>> the message programmatically using JAXP or insert an intermediary
>> into your
>> message path to transform the message.
>>
>>  Anne
>>
>>
>> On 5/22/06, Razvan Dani <[EMAIL PROTECTED]
> wrote:
>> > Hi
>> >
>> > I am not sure if this is the right place to address this, but 
i'd

>> > appreciate some feedback if possible, because i already made
lots of
>> > queries on the internet about this issue with no success.
>> >
>> > My problem is the following:
>> > - i am using WSDL to Java ant task to generate classes
against a WSDL.
>> > - when i make a method call on the generated Stub (so notice
that i am
>> > not constructing the envelope by hand neither i use the Call
class
>> > directly), Axis is constructing the envelope as this:
>> > > >
>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
>> >
>> > This works just fine for many Web Services, but in my
particular case,
>> > the Web Service implementation on the server side is
"hardcoded" to
>> only
>> > be able to accept
>> > > > xmlns:soap-env=" http://schemas.xmlsoap.org/soap/envelope/
>> "
>> >
>> > I know this is an issue that should be fixed on the server
part since
>> > the Web Service specs is flexibl

doc literal web service?

[Suavi Ali Demir]

hello,     i am newbie. I have some code that generates xml. i want to make this xml available as a web service in doc literal fashion. would using axis help me do this? what would i have to do with axis to get this done? do i implement a handler? or what else? does axis have a way such that i register my function to produce the content and axis handles the rest?     thanks,  suavi      

Re: Passing XML Best Practice

[Anne Thomas Manes]

Attachments are problematic if you need cross-platform interoperability. Encoding the document as a string can also be problematic if you have embedded "<" or ">" characters in the XML content or if you have encoded characters, 
e.g., ">" in the content or if you have CDATA in the document.Also if you send the XML within the envelope, you can protect it using WS-Security.Anne
On 5/22/06, Hoda Nadeem <[EMAIL PROTECTED]> wrote:





 
Anne, thanks for the suggestion. 
 
Both yourself and Muthana suggested sending XML in the SOAP 
body instead of SOAP with attachments. 
 
Is there a reason for this preference?
 
Thanks for the help.
 
Nadeem


From: Anne Thomas Manes 
[mailto:[EMAIL PROTECTED]] Sent: Monday, May 22, 2006 4:57 
PMTo: axis-user@ws.apache.org
Subject: Re: Passing XML Best 
Practice
Then I suggest using the Messaging API (Axis1) or the 
RawXMLMessageProvider (Axis2) and don't attempt to bind the schema to Java 
objects. But it's still better to send the XML within the SOAP envelope.
On 5/22/06, Hoda 
Nadeem <[EMAIL PROTECTED]> 
wrote:

  
  
   
  Good 
  suggestion, but unfortunately, the schema, and the schemas it depends on make 
  it impractical to include in the WSDL. 
   
  It took 
  XMLBeans 15+ mins and modification (to the schema) to generate the data 
  binding jars. So, for the sake of sanity, and handling the XML cleanly, we 
  decided it is better to pass the XML in raw form. 
   
  But we are 
  not sure what the best practice is in this specific case. Is attachments 
  better, or one string.
   
  Thanks. 
  
   
  Nadeem
  
  
  From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]] 
  Sent: Monday, May 22, 2006 4:45 PMTo: axis-user@ws.apache.orgSubject:
 Re: Passing XML 
  Best Practice
  
  Why don't you import the schema into the WSDL?It's always 
  better to pass the XML within the SOAP envelope than to send it as a string or 
  as an attachment.Anne
  
  On 5/22/06, Hoda 
  Nadeem <[EMAIL PROTECTED]> 
  wrote: 
  


 
When dealing with raw xml data that needs 
to be passed through web services (the XML schemas are complicated and big 
enough that we are not including the types in the WSDL explicitly), is it 
better to:
 
a. Pass the XML in a doc-literal web 
service through a string
 
or 
 
b. Use SOAP with attachments to pass the 
XML through.
 
Thanks. 
 
Nadeem
  

Re: javax.xml.rpc.service

[tom mccarthy]

nevermind. I hadn't realized I needed to add the axis jar files to my 
servlet lib directory.


tom mccarthy wrote:
I am writing an applet which accesses a web client to send information 
to a web service. However, I am getting the following exception:


java.lang.NoClassDefFoundError: javax/xml/rpc/Service

I believe I have all of the axis jars in my classpath and the 
application compiles correctly, so this problem troubles me. What could 
cause this problem? Are there any potential solutions you can think of?


Thanks.

-
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: Adding Digital Signatures to all outgoing SOAP envelopes

[Scudder, Jeffrey W]

Thank you very much

-Jeff 

-Original Message-
From: Ali Sadik Kumlali [mailto:[EMAIL PROTECTED] 
Sent: Monday, May 22, 2006 1:37 PM
To: axis-user@ws.apache.org
Subject: Re: Adding Digital Signatures to all outgoing SOAP envelopes

Hi Jeffrey,

Followings are the first steps that come to my mind:
1) Find yourself a tool that ease your work. portecle[1] is my favorite.
Other tools such as OpenSSL[2] and keytool[3] are very popular, though.
2) You need to create a keystore file for both client and the server.
Later you will store private key and public key certificates in it.
3) Format of keystore file can be either JKS or PKCS#12. Let's use JKS.
4) server.jks should contain private key of server and the public key of
the client. 
5) client.jks should contain private key of client and the public key of
the server. 
6) You need to create a keypair which implicitly has your private key.
7) By using portecle, you need to export public key certificate which
will later be imported in other jks.
8) Exported public key certificate should be a "cer" file.
9) Now, you need to import the public key certificate into the other jks
.
10) Consequently, the keystore file should be as follows:

client.jks
   client private
   server public

server.jks
   server private
   client public
 
11) Here are InflowSecurity and OutflowSecurity of each side. Please
note that we use only signing here. There is no encryption.

axis2.xml of client
---

  
Signature
client_user  
   
com.mycompany.service.security.client.PWCallback<
/passwordCallbackClass>
client_security.properties
SKIKeyIdentifier
  


  
Signature
client_security.properties
  


axis2.xml of server
---

  
Signature
server_user  
   
com.mycompany.service.security.server.PWCallback<
/passwordCallbackClass>
server_security.properties
SKIKeyIdentifier
  


  
Signature
server_security.properties
  


12) Additional resources I've come through
  http://jetty.mortbay.org/jetty/faq?s=400-Security&t=ssl#step3
  http://www.devx.com/Java/Article/28816/0/page/2
  http://www.rsasecurity.com/rsalabs/node.asp?id=2124

Hope this helps.

Regards,

Ali Sadik Kumlali

[1] http://portecle.sourceforge.net/
[2] http://www.openssl.org/
[3] http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/keytool.html

--- "Scudder, Jeffrey W" <[EMAIL PROTECTED]> wrote:

> I am trying to configure Axis2 v1.0 to add digital signatures to all 
> outgoing soap messages by configuring the rampart module. While 
> filling in the blanks in the OutflowSecurity parameter I realized I 
> have no idea how to obtain a signature key or have it signed by a CA.
> 
> The implementation will be used in a closed lab, so there is no need 
> to use an Internet CA (Verisign etc.)
> 
> How do I create a signature key and import is into the Axis2 
> framework?
> I'm new at this.
> 
> Thank you,
> 
> Jeff Scudder
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.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]

Define Axis Services in Runtime

[Duncan Krebs]

Hi,   As of now I have been declaring my axis webservices in a servlet container via server-config.wsdd in the WEB-INF folder. However ideally I want to be able to declare services in runtime during startup. Does anyone know what API I can use to do this? I'm hoping its not that hard. 
	
		Sneak preview the  all-new Yahoo.com. It's not radically different. Just radically better. 

javax.xml.rpc.service

[tom mccarthy]

I am writing an applet which accesses a web client to send information 
to a web service. However, I am getting the following exception:


java.lang.NoClassDefFoundError: javax/xml/rpc/Service

I believe I have all of the axis jars in my classpath and the 
application compiles correctly, so this problem troubles me. What could 
cause this problem? Are there any potential solutions you can think of?


Thanks.

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

web services client threads choking app server

[E Zaffar]

Hi,

We consume a web service using axis 1.1. Whenever the
webservice goes
down or is slow to respond, it appears like our
appservers keep
creating new threads for subsequent requests and the
web service client
thread is never released as the service is not
responding. This causes
the web container to run out of threads (there is a
max no of threads
specified). This not only blocks everything from the
appserver, but
even our webserver stops responding to static file
requests.

Any idea what I can do to make my client more robust,
so it does not
let the threads get locked for a long period of time.
Is there any way
to implement timeouts with axis/connection pooling, so
only a set no of
threads are ever used for the web service. 

Also, any good source of documentation on using Axis
(books etc.) that really goes into the nuts and bolts
of it and not just get away with superficial examples?

Any help is greatly appreciated.

Thanks.

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

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

Re: show a method return in xml response

[Gabriel Moura]

well,

I am beginning and I did not understand very well.
you can detail as you show the result? for example,
System.out.println().

I want to show in my java aplication for example, only:   
HELLO TESTING

thanks!
--
View this message in context: 
http://www.nabble.com/show+a+method+return+in+xml+response-t1664824.html#a4513290
Sent from the Axis - User forum at Nabble.com.


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

RE: Passing XML Best Practice

[Hoda Nadeem]

 
Anne, thanks for the suggestion. 
 
Both yourself and Muthana suggested sending XML in the SOAP 
body instead of SOAP with attachments. 
 
Is there a reason for this preference?
 
Thanks for the help.
 
Nadeem


From: Anne Thomas Manes 
[mailto:[EMAIL PROTECTED] Sent: Monday, May 22, 2006 4:57 
PMTo: axis-user@ws.apache.orgSubject: Re: Passing XML Best 
Practice
Then I suggest using the Messaging API (Axis1) or the 
RawXMLMessageProvider (Axis2) and don't attempt to bind the schema to Java 
objects. But it's still better to send the XML within the SOAP envelope.
On 5/22/06, Hoda 
Nadeem <[EMAIL PROTECTED]> 
wrote:

  
  
   
  Good 
  suggestion, but unfortunately, the schema, and the schemas it depends on make 
  it impractical to include in the WSDL. 
   
  It took 
  XMLBeans 15+ mins and modification (to the schema) to generate the data 
  binding jars. So, for the sake of sanity, and handling the XML cleanly, we 
  decided it is better to pass the XML in raw form. 
   
  But we are 
  not sure what the best practice is in this specific case. Is attachments 
  better, or one string.
   
  Thanks. 
  
   
  Nadeem
  
  
  From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]] 
  Sent: Monday, May 22, 2006 4:45 PMTo: axis-user@ws.apache.orgSubject: Re: Passing XML 
  Best Practice
  
  Why don't you import the schema into the WSDL?It's always 
  better to pass the XML within the SOAP envelope than to send it as a string or 
  as an attachment.Anne
  
  On 5/22/06, Hoda 
  Nadeem <[EMAIL PROTECTED]> 
  wrote: 
  


 
When dealing with raw xml data that needs 
to be passed through web services (the XML schemas are complicated and big 
enough that we are not including the types in the WSDL explicitly), is it 
better to:
 
a. Pass the XML in a doc-literal web 
service through a string
 
or 
 
b. Use SOAP with attachments to pass the 
XML through.
 
Thanks. 
 
Nadeem
  

Re: Passing XML Best Practice

[Anne Thomas Manes]

Then I suggest using the Messaging API (Axis1) or the RawXMLMessageProvider (Axis2) and don't attempt to bind the schema to Java objects. But it's still better to send the XML within the SOAP envelope.
On 5/22/06, Hoda Nadeem <[EMAIL PROTECTED]> wrote:





 
Good suggestion, but unfortunately, the schema, and the 
schemas it depends on make it impractical to include in the WSDL. 

 
It took XMLBeans 15+ mins and modification (to the schema) 
to generate the data binding jars. So, for the sake of sanity, and handling the 
XML cleanly, we decided it is better to pass the XML in raw form. 

 
But we are not sure what the best practice is in this 
specific case. Is attachments better, or one string.
 
Thanks. 
 
Nadeem


From: Anne Thomas Manes 
[mailto:[EMAIL PROTECTED]] Sent: Monday, May 22, 2006 4:45 
PMTo: axis-user@ws.apache.orgSubject: Re: Passing XML Best 
Practice
Why don't you import the schema into the WSDL?It's always better 
to pass the XML within the SOAP envelope than to send it as a string or as an 
attachment.Anne
On 5/22/06, Hoda 
Nadeem <[EMAIL PROTECTED]> 
wrote:

  
  
   
  When dealing with raw xml data that needs 
  to be passed through web services (the XML schemas are complicated and big 
  enough that we are not including the types in the WSDL explicitly), is it 
  better to:
   
  a. Pass the XML in a doc-literal web 
  service through a string
   
  or 
   
  b. Use SOAP with attachments to pass the 
  XML through.
   
  Thanks. 
   
  Nadeem

RE: Passing XML Best Practice

[Hoda Nadeem]

 
Good suggestion, but unfortunately, the schema, and the 
schemas it depends on make it impractical to include in the WSDL. 

 
It took XMLBeans 15+ mins and modification (to the schema) 
to generate the data binding jars. So, for the sake of sanity, and handling the 
XML cleanly, we decided it is better to pass the XML in raw form. 

 
But we are not sure what the best practice is in this 
specific case. Is attachments better, or one string.
 
Thanks. 
 
Nadeem


From: Anne Thomas Manes 
[mailto:[EMAIL PROTECTED] Sent: Monday, May 22, 2006 4:45 
PMTo: axis-user@ws.apache.orgSubject: Re: Passing XML Best 
Practice
Why don't you import the schema into the WSDL?It's always better 
to pass the XML within the SOAP envelope than to send it as a string or as an 
attachment.Anne
On 5/22/06, Hoda 
Nadeem <[EMAIL PROTECTED]> 
wrote:

  
  
   
  When dealing with raw xml data that needs 
  to be passed through web services (the XML schemas are complicated and big 
  enough that we are not including the types in the WSDL explicitly), is it 
  better to:
   
  a. Pass the XML in a doc-literal web 
  service through a string
   
  or 
   
  b. Use SOAP with attachments to pass the 
  XML through.
   
  Thanks. 
   
  Nadeem

Re: Passing XML Best Practice

[Muthana A.]

Hallo Hoda,


you can use both of them but the better is the first (a)

Regards
Muthana Al-Temimi
M.Sc.in Information and Communication Systems
Hamburg Germany

 Original-Nachricht 
Betreff: Passing XML Best Practice
Datum: Mon, 22 May 2006 16:35:35 -0400
Von: "Hoda Nadeem" <[EMAIL PROTECTED]>
An: 

>  When dealing with raw xml data that needs to be passed through web 
> services (the XML schemas are complicated and big enough that we are not 
> including the types in the WSDL explicitly), is it better to: a. Pass the
> XML in a doc-literal web service through a string or  b. Use SOAP with 
> attachments to pass the XML through. Thanks.  Nadeem

-- 


Bis zu 70% Ihrer Onlinekosten sparen: GMX SmartSurfer!
  Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer


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

Re: AXIS 1.2 and SOA

[Ravi Krishnamurthy]

Thanks Anne.


Anne Thomas Manes wrote:
See http://www.google.com/search?q=soa+design+practices
  
  
  On 5/22/06, Ravi Krishnamurthy <[EMAIL PROTECTED]> wrote:
  Anne:
Could you suggest any good articles on SOA.


Thanks,
Ravi

Anne Thomas Manes wrote:

> I don't think the term "SOA-compliant" applies to a development
tool.
> Both Axis1 and Axis2 are tools that you can use to implement
services,

> but that doesn't make them "SOA-compliant".
>
> SOA is a style of design in which the fundamental unit of design
is a
> service. An application system is "SOA-compliant" if you design it

> using SOA principles -- although all design is somewhat relative.
You
> can build service-oriented systems with Axis 1.2. You can also
build
> them with Axis 2. You can also build them using CORBA, or Jini, or
a

> proprietary MOM system. Or with "plain old XML" (POX) over HTTP.
>
> Axis2 is WS-* compliant. It has been designed from the bottom up to
> support the extensible, composable WS-* architecture. It also
supports

> development of RESTful services. I think it provides a better
> foundation for building service-oriented systems than Axis1, but
you
> can also use Axis2 to build tightly coupled, monolithic
applications.

>
> As I said, SOA is about design. It's not about technology.
>
> Anne




-
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: AXIS 1.2 and SOA

[Anne Thomas Manes]

See http://www.google.com/search?q=soa+design+practices On 5/22/06, Ravi Krishnamurthy
 <[EMAIL PROTECTED]> wrote:Anne:Could you suggest any good articles on SOA.
Thanks,RaviAnne Thomas Manes wrote:> I don't think the term "SOA-compliant" applies to a development tool.> Both Axis1 and Axis2 are tools that you can use to implement services,
> but that doesn't make them "SOA-compliant".>> SOA is a style of design in which the fundamental unit of design is a> service. An application system is "SOA-compliant" if you design it
> using SOA principles -- although all design is somewhat relative. You> can build service-oriented systems with Axis 1.2. You can also build> them with Axis 2. You can also build them using CORBA, or Jini, or a
> proprietary MOM system. Or with "plain old XML" (POX) over HTTP.>> Axis2 is WS-* compliant. It has been designed from the bottom up to> support the extensible, composable WS-* architecture. It also supports
> development of RESTful services. I think it provides a better> foundation for building service-oriented systems than Axis1, but you> can also use Axis2 to build tightly coupled, monolithic applications.
>> As I said, SOA is about design. It's not about technology.>> Anne-To unsubscribe, e-mail: 
[EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

Re: Axis2 and WS Security

[Ali Sadik Kumlali]

Hi Sagar,

You may start from the security sample that comes with axis2
distribution. Then, you may create the stub of the secure service by
using WSDL2Java. Using client_repo folder as found in security sample
along with your stub will let you do what you want.

Regards,

Ali Sadik Kumlali

--- sagar kar <[EMAIL PROTECTED]> wrote:

> 
> I am doing a proof of concept on WS-Security. We use websphere
> appserver v
> 6.0 to develop our webservices.
> RAD 6.0 supports the WS-Security 1.0.
> I was able to create a secured webservice on RAD 6.0.
> I can also use a RAD web client to send and receive messages from the
> secured webservice.
> Now my task is to create a Axis2 client and send and receive a
> secured
> message to the WAS 6.0 service.
> I am completely new to Axis2.
> 
> 1)Is it possible to create a standalone axis client to test the WAS
> 6.0
> secured web service? 
> 2)Where do I start from?
> 
> Any help is appreciated. Thanks in advance.
> 
> Sagar
> --
> View this message in context:
> http://www.nabble.com/Axis2+and+WS+Security-t1665049.html#a4512228
> Sent from the Axis - User forum at Nabble.com.
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

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

Re: Passing XML Best Practice

[Anne Thomas Manes]

Why don't you import the schema into the WSDL?It's always better to pass the XML within the SOAP envelope than to send it as a string or as an attachment.AnneOn 5/22/06, 
Hoda Nadeem <[EMAIL PROTECTED]> wrote:





 
When dealing with 
raw xml data that needs to be passed through web services (the XML schemas are 
complicated and big enough that we are not including the types in the WSDL 
explicitly), is it better to:
 
a. Pass the XML in a 
doc-literal web service through a string
 
or 

 
b. Use SOAP with 
attachments to pass the XML through.
 
Thanks. 

 
Nadeem

Re: show a method return in xml response

[robert lazarski]

Assuming you have a 'xxxReturn' as a node in your soap message - take a
look at tcpmon or the soap applet, etc, if you need to...

I think what you want is to get a node and show just that - I think
axis 1.x allows you to get the Document from Message Context directly,
but anyways:

   DocumentBuilderFactory factory =
    DocumentBuilderFactory.newInstance();
    factory.setNamespaceAware(true);
    factory.setIgnoringElementContentWhitespace(false);
    DocumentBuilder builder = factory.newDocumentBuilder();

   
InputSource isXml = new InputSource(new StringReader(XMLContents));
    Document doc = builder.parse(isXml);
    NodeList nodeList = doc.getElementsByTagName("xxxReturn");

    // What you do next depends a lot on what is in myNode - 
    //
you may have attributes, child elements, etc.
    
    Node myNode = nodeList.item(0);

If that isn't what you want, try and rephrase the question. 

HTH,
Robert
http://www.braziloutsource.com/On 5/22/06, Gabriel Moura <[EMAIL PROTECTED]
> wrote:hi, i am brazilian student and speak english very well. :Dmy doubt is:
i want show only "xxxReturn" in the aplication..my client is generated by wsdl2..i obtain xml response using:---java.io.ByteArrayOutputStream baos = new 
java.io.ByteArrayOutputStream();_call.getMessageContext().getMessage().writeTo(baos);String XMLContents = new java.lang.String(baos.toByteArray(), "UTF-8");System.out.println(XMLContents);---
How i show only "xxxReturn" for example?anyone can help-me?--View this message in context: http://www.nabble.com/show+a+method+return+in+xml+response-t1664824.html#a4511532
Sent from the Axis - User forum at Nabble.com.-To unsubscribe, e-mail: 
[EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

Re: Axis2 and WS Security

[Anne Thomas Manes]

Use WSDL2Java to generate the client stub and use the Rampart module to secure it.AnneOn 5/22/06, sagar kar <
[EMAIL PROTECTED]> wrote:I am doing a proof of concept on WS-Security. We use websphere appserver v
6.0 to develop our webservices.RAD 6.0 supports the WS-Security 1.0.I was able to create a secured webservice on RAD 6.0.I can also use a RAD web client to send and receive messages from thesecured webservice.
Now my task is to create a Axis2 client and send and receive a securedmessage to the WAS 6.0 service.I am completely new to Axis2.1)Is it possible to create a standalone axis client to test the WAS 6.0
secured web service?2)Where do I start from?Any help is appreciated. Thanks in advance.Sagar--View this message in context: 
http://www.nabble.com/Axis2+and+WS+Security-t1665049.html#a4512228Sent from the Axis - User forum at Nabble.com.-
To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

Axis2 and WS Security

[sagar kar]

I am doing a proof of concept on WS-Security. We use websphere appserver v
6.0 to develop our webservices.
RAD 6.0 supports the WS-Security 1.0.
I was able to create a secured webservice on RAD 6.0.
I can also use a RAD web client to send and receive messages from the
secured webservice.
Now my task is to create a Axis2 client and send and receive a secured
message to the WAS 6.0 service.
I am completely new to Axis2.

1)Is it possible to create a standalone axis client to test the WAS 6.0
secured web service? 
2)Where do I start from?

Any help is appreciated. Thanks in advance.

Sagar
--
View this message in context: 
http://www.nabble.com/Axis2+and+WS+Security-t1665049.html#a4512228
Sent from the Axis - User forum at Nabble.com.


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

Re: Adding Digital Signatures to all outgoing SOAP envelopes

[Ali Sadik Kumlali]

Hi Jeffrey,

Followings are the first steps that come to my mind:
1) Find yourself a tool that ease your work. portecle[1] is my
favorite. Other tools such as OpenSSL[2] and keytool[3] are very
popular, though.
2) You need to create a keystore file for both client and the server.
Later you will store private key and public key certificates in it.
3) Format of keystore file can be either JKS or PKCS#12. Let's use JKS.
4) server.jks should contain private key of server and the public key
of the client. 
5) client.jks should contain private key of client and the public key
of the server. 
6) You need to create a keypair which implicitly has your private key.
7) By using portecle, you need to export public key certificate which
will later be imported in other jks.
8) Exported public key certificate should be a "cer" file.
9) Now, you need to import the public key certificate into the other
jks .
10) Consequently, the keystore file should be as follows:

client.jks
   client private
   server public

server.jks
   server private
   client public
 
11) Here are InflowSecurity and OutflowSecurity of each side. Please
note that we use only signing here. There is no encryption.

axis2.xml of client
---

  
Signature
client_user  
   
com.mycompany.service.security.client.PWCallback
client_security.properties
SKIKeyIdentifier
  


  
Signature
client_security.properties
  


axis2.xml of server
---

  
Signature
server_user  
   
com.mycompany.service.security.server.PWCallback
server_security.properties
SKIKeyIdentifier
  


  
Signature
server_security.properties
  


12) Additional resources I've come through
  http://jetty.mortbay.org/jetty/faq?s=400-Security&t=ssl#step3
  http://www.devx.com/Java/Article/28816/0/page/2
  http://www.rsasecurity.com/rsalabs/node.asp?id=2124

Hope this helps.

Regards,

Ali Sadik Kumlali

[1] http://portecle.sourceforge.net/ 
[2] http://www.openssl.org/
[3] http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/keytool.html

--- "Scudder, Jeffrey W" <[EMAIL PROTECTED]> wrote:

> I am trying to configure Axis2 v1.0 to add digital signatures to all
> outgoing soap messages by configuring the rampart module. While
> filling
> in the blanks in the OutflowSecurity parameter I realized I have no
> idea
> how to obtain a signature key or have it signed by a CA.
> 
> The implementation will be used in a closed lab, so there is no need
> to
> use an Internet CA (Verisign etc.)
> 
> How do I create a signature key and import is into the Axis2
> framework?
> I'm new at this.
> 
> Thank you,
> 
> Jeff Scudder
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

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

Fw: Location of SAAJUtil?

[Daniel Jemiolo]

Just a follow up - I copied SAAJUtil
into my project as a package-private class and the code works just fine.
My hope is that once I find the actual jar with SAAJUtil in it, I can replace
this hack with a simple import statement. The source code says that this
was originally written to support WSS4J, but the 1.0 version of the WSS4J
MAR does not have this package/class - any tips?

Thanks,
Dan


- Forwarded by Daniel
Jemiolo/Durham/IBM on 05/22/2006 04:28 PM -

Daniel Jemiolo/Durham/IBM wrote on 05/22/2006 11:37:11
AM:

> Hi,
> 
> Which jar file is the org.apache.axis2.saaj.util package in? I'm trying
to 
> compile a project that uses SAAJUtil and can't find the class in any
of the 
> $AXIS2_WAR/WEB-INF/lib or $STANDARD_DISTRIBUTION/lib archives. I see
the code 
> in SVN, I'm just not sure where it's packaged.
> 
> Thanks,
> Dan
> 
> 
> Dan Jemiolo
> IBM Corporation
> Research Triangle Park, NC
> 
> 
> +++ I'm an engineer. I make slides that people can't read. Sometimes
I eat donuts. +++
> 

Passing XML Best Practice

[Hoda Nadeem]

 
When dealing with 
raw xml data that needs to be passed through web services (the XML schemas are 
complicated and big enough that we are not including the types in the WSDL 
explicitly), is it better to:
 
a. Pass the XML in a 
doc-literal web service through a string
 
or 

 
b. Use SOAP with 
attachments to pass the XML through.
 
Thanks. 

 
Nadeem

Re: AXIS 1.2 and SOA

[Ravi Krishnamurthy]

Anne:
Could you suggest any good articles on SOA.

Thanks,
Ravi

Anne Thomas Manes wrote:

I don't think the term "SOA-compliant" applies to a development tool. 
Both Axis1 and Axis2 are tools that you can use to implement services, 
but that doesn't make them "SOA-compliant".


SOA is a style of design in which the fundamental unit of design is a 
service. An application system is "SOA-compliant" if you design it 
using SOA principles -- although all design is somewhat relative. You 
can build service-oriented systems with Axis 1.2. You can also build 
them with Axis 2. You can also build them using CORBA, or Jini, or a 
proprietary MOM system. Or with "plain old XML" (POX) over HTTP.


Axis2 is WS-* compliant. It has been designed from the bottom up to 
support the extensible, composable WS-* architecture. It also supports 
development of RESTful services. I think it provides a better 
foundation for building service-oriented systems than Axis1, but you 
can also use Axis2 to build tightly coupled, monolithic applications.


As I said, SOA is about design. It's not about technology.

Anne 





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

Re: AXIS 1.2 and SOA

[Anne Thomas Manes]

I don't think the term "SOA-compliant" applies to a development tool. Both Axis1 and Axis2 are tools that you can use to implement services, but that doesn't make them "SOA-compliant".SOA is a style of design in which the fundamental unit of design is a service. An application system is "SOA-compliant" if you design it using SOA principles -- although all design is somewhat relative. You can build service-oriented systems with Axis 
1.2. You can also build them with Axis 2. You can also build them using CORBA, or Jini, or a proprietary MOM system. Or with "plain old XML" (POX) over HTTP.Axis2 is WS-* compliant. It has been designed from the bottom up to support the extensible, composable WS-* architecture. It also supports development of RESTful services. I think it provides a better foundation for building service-oriented systems than Axis1, but you can also use Axis2 to build tightly coupled, monolithic applications. 
As I said, SOA is about design. It's not about technology.Anne On 5/22/06, Jayaraman, Venkatesh <
[EMAIL PROTECTED]> wrote:












Is axis 1.2 considered as SOA?

 

Move AXIS2 to make remove JAX-RPC and become SOA compliant?

 

-Venky

show a method return in xml response

[Gabriel Moura]

hi, i am brazilian student and speak english very well. :D
my doubt is:

i want show only "xxxReturn" in the aplication..
my client is generated by wsdl2..  
i obtain xml response using:
---
java.io.ByteArrayOutputStream baos = new java.io.ByteArrayOutputStream();
_call.getMessageContext().getMessage().writeTo(baos);
String XMLContents = new java.lang.String(baos.toByteArray(), "UTF-8");
System.out.println(XMLContents);
---

How i show only "xxxReturn" for example?
anyone can help-me?

--
View this message in context: 
http://www.nabble.com/show+a+method+return+in+xml+response-t1664824.html#a4511532
Sent from the Axis - User forum at Nabble.com.


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

Re: Axis 2 V 1.0

[robert lazarski]

The issue is that you can only get the wsdl to display under two scenarios:

1)  You are using RPC, such as RPCInOutMessageReceiver, as your message receiver in your services.xml . 
2) You have your own WSDL that you use for databinding, and you put it under the META-INF directory in your war. 

As I understand it, nothing else is currently valid. Deepal has
explained this a few times - you might search the list for more info if
need be. 

Hope that helps,
Robert
http://www.braziloutsource.com/On 5/22/06, Christian Strobel <
[EMAIL PROTECTED]> wrote:Hi,-   Unable to generate WSDL for this service
  Either user has not dropped the wsdl into META-INF or operationsuse message receivers other than RPC.  Get every time this error message! Doesn't matter if I use the give examples
or my own code. Anyone who can help?Greetz and thanks-To unsubscribe, e-mail: 
[EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

Re: Release 1.0 How to disable MTOM

[Thilina Gunarathne]

See my comments below...
 >On 5/22/06, Laurent CELLA <[EMAIL PROTECTED]> wrote:
This sample is supposed to return us an instance of class Attachmentslinking to attachments retrieved on mime.
The result is null.When i log the OMElement received by the method, it looks like it is theMTOM way( my attachment is contained in a XML node ).
 
MTOM is backward compatible with SwA. So we use MTOM to send SwA messages.
It looks like exactly as my service was configured to be implementedwith MTOM pattern.Where to configure my service in order it to function the SWA way ?

 
Receiving of attachments will not be affected by any configurations. MTOM/SwA/non-optimised will be auto detected by Axis2 based on the content-type, and will be decoded accordingly.
I had no axis2.xml present. Is it a default behaviour that would makeMTOM by default in AXIS 2 rel 1.0
 ?My Server code modification consisted in what is following ( only tomake my method match the mtomSample element )public void setOperationContext(OperationContext oc) throws AxisFault {   msgcts =
oc.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);   }
 
Change this to MESSAGE_LABEL_IN_VALUE
 
HTH,
~Thilina
   public OMElement mtomSample(OMElement omEle) throws Exception {   System.out.println("here we are! " + 
omEle.toString()); //MTOM like xml ( attachments by value )   Attachments attachment = (Attachments)msgcts.getProperty(MTOMConstants.ATTACHMENTS);   System.out.println("attachment=" + attachment ); // null returned.
   omEle.detach(); omEle.build(); return omEle;   }Thanks alot for the time you have taken to read this mail.Laurent CELLAInexbee Software
-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: 
[EMAIL PROTECTED]-- "May the SourcE be with u"
http://webservices.apache.org/~thilina/http://thilinag.blogspot.com/ http://www.bloglines.com/blog/Thilina
   

Re: envelope prefix issue

[robert lazarski]

Not sure which axis version you are using, but both axis 1.x and axis2
show a simple LogHandler in their respective user guides. That would be
a good place to start. Also, the axis2 migration guide shows an Axis
1.x handler and how to migrate that to Axis2. 

HTH,
Robert
http://www.braziloutsource.com/On 5/22/06, Razvan Dani <[EMAIL PROTECTED]
> wrote:


  


Hi Xinjun

Thank you very much for your useful intervention. 

Could either you or otherwise another Axis guru maybe present me a
brief example of how a Handler can be inserted in the request flow
(which translates into: i don't know how that could be done).

Again i would like to remind that i am using WSDL2Java to generate
classes for a given WSDL and then i am sending SOAP messages via the
generated stub (so i am not constructing anything manually).

Regards,
    Razvan

Xinjun Chen wrote:

  Hi Razvan, 
   
  What I can think of is to insert a Handler in the request flow.
Inside the Handler, you can modify the message. If you are using Axis2,
you can write a module or a handler to do that. I believe this will be
much easier than customize Axis or Axis2. 
  Axis gurus, please correct me if I am not correct. 
 
  Regards, 
  Xinjun
 
  On 5/22/06, Razvan Dani <[EMAIL PROTECTED]
>
wrote:
  Hi

thank you for your suggestion. if i reach desperation i will certainly
customize axis for my own use, but i'd certainly like to stick to the

"standard axis" if at all possible. otherwise when i want to switch to a
new version of axis latter on, i would be loosing by custom changes.

what i am ideally looking for is a way to "plug" (or whatever other
term

you prefer) an extra thing that would change axis behaviour without
modifying Axis source and making my personal axis.jar. I would be
perfectly able to do that if it's the only solution...

I think this is an interesting challenge to people with Axis
experience,

so i'd be more than happy to hear more opinions :) .

Regards,
   Razvan

Davanum Srinivas wrote:
> easier would be to edit axiom source
> (
http://svn.apache.org/repos/asf/webservices/commons/trunk/modules/axiom/src/org/apache/axiom/soap/SOAPConstants.java)
>
>
> and build a jar for your own use.
>
> -- dims
>
> On 5/22/06, Razvan Dani <
[EMAIL PROTECTED]>
wrote:
>>
>>  Hi Anne
>>
>>  Thank you for your suggestions. However as a person that only
found
>> Axis
>> few days ago, i am not sure how would i go about inserting and
>> intermediary
>> into my message path to transform the message (i.e. replace
>> occurences of
>> soapenv with soap-env).

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

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

>> into your
>> message path to transform the message.
>>
>>  Anne
>>
>>
>> On 5/22/06, Razvan Dani <[EMAIL PROTECTED]
> wrote:
>> > Hi
>> >
>> > I am not sure if this is the right place to address this,
but i'd
>> > appreciate some feedback if possible, because i already
made lots of

>> > queries on the internet about this issue with no success.
>> >
>> > My problem is the following:
>> > - i am using WSDL to Java ant task to generate classes
against a WSDL.

>> > - when i make a method call on the generated Stub (so
notice that i am
>> > not constructing the envelope by hand neither i use the
Call class
>> > directly), Axis is constructing the envelope as this:

>> > 
>> >
>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
>> >
>> > This works just fine for many Web Services, but in my
particular case,

>> > the Web Service implementation on the server side is
"hardcoded" to
>> only
>> > be able to accept
>> > 
>> > xmlns:soap-env="
http://schemas.xmlsoap.org/soap/envelope/
>> "
>> >
>> > I know this is an issue that should be fixed on the
server part since
>> > the Web Service specs is flexible to allow any prefix for
the envelope
>> > as long as the name space URL is correct. But i don't
have control on
>> > the server part and thus i would like to know if this
issue can be

>> > tackled from Axis.
>> >
>> > So the question is whether it is possible to make some
>> configuration in
>> > Axis so that i can specify at runtime what prefix should
be used

>> for the
>> > envelope (e.g. soap-env instead of soapenv)?
>> >
>> > Many thanks in advance if i receive any answer to this
issue.
>> >
>> > Regards,

>> >Razvan
>> >
>> > --
>> > Razvan Dani
>> >
>> > Senior Java Developer
>> >
>> > ARoBS Transilvania Software
>> >

>> > 11 Donath Str , M4 - 28
>> > 400301 Cluj-Napoca, Romania
>> >
>> > Main:   +40 264 598 204
>> > Fax:+40 264 598 426
>> > email:  
[EMAIL PROTECTED]
>> > www.ARoBS.com
>> >
>> >
>> >
>> >
>>
-

Adding Digital Signatures to all outgoing SOAP envelopes

[Scudder, Jeffrey W]

I am trying to configure Axis2 v1.0 to add digital signatures to all
outgoing soap messages by configuring the rampart module. While filling
in the blanks in the OutflowSecurity parameter I realized I have no idea
how to obtain a signature key or have it signed by a CA.

The implementation will be used in a closed lab, so there is no need to
use an Internet CA (Verisign etc.)

How do I create a signature key and import is into the Axis2 framework?
I'm new at this.

Thank you,

Jeff Scudder

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

Release 1.0 How to disable MTOM

[Laurent CELLA]

Hi Dear Axis Users.

I Have tested the sample given in AXIS 2 rel 1.0 :  MTOMService / 
imagetransfer

-> the client let us select a file, name it and post to the server.
-> the server is a MTOM implementation.

It works perfectly.

So, I modified a bit the Server Sample to handles in SOAP with 
attachments. found in the user guide in this url

http://ws.apache.org/axis2/1_0/mtom-guide.html
Then I Used the client again, but targeting my modified service instead.

This sample is supposed to return us an instance of class Attachments 
linking to attachments retrieved on mime.

The result is null.

When i log the OMElement received by the method, it looks like it is the 
MTOM way

( my attachment is contained in a XML node ).

It looks like exactly as my service was configured to be implemented 
with MTOM pattern.

Where to configure my service in order it to function the SWA way ?

I had no axis2.xml present. Is it a default behaviour that would make 
MTOM by default in AXIS 2 rel 1.0 ?


My Server code modification consisted in what is following ( only to 
make my method match the mtomSample element )


 public void setOperationContext(OperationContext oc) throws AxisFault {
   msgcts = 
oc.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);

   }
 
   public OMElement mtomSample(OMElement omEle) throws Exception {
   
   System.out.println("here we are! " + omEle.toString()); // 
MTOM like xml ( attachments by value )
   Attachments attachment = (Attachments) 
msgcts.getProperty(MTOMConstants.ATTACHMENTS);


   System.out.println("attachment=" + attachment ); // null returned.

  
 
 omEle.detach();

 omEle.build();
 return omEle;
   }

Thanks alot for the time you have taken to read this mail.

Laurent CELLA
Inexbee Software




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

Axis 2 V 1.0

[Christian Strobel]

Hi,

- 
  Unable to generate WSDL for this service
  Either user has not dropped the wsdl into META-INF or operations
use message receivers other than RPC.
  

Get every time this error message! Doesn't matter if I use the give examples
or my own code. Anyone who can help?

Greetz and thanks


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

Re: envelope prefix issue

[Razvan Dani]

Hi Xinjun

Thank you very much for your useful intervention. 

Could either you or otherwise another Axis guru maybe present me a
brief example of how a Handler can be inserted in the request flow
(which translates into: i don't know how that could be done).

Again i would like to remind that i am using WSDL2Java to generate
classes for a given WSDL and then i am sending SOAP messages via the
generated stub (so i am not constructing anything manually).

Regards,
    Razvan

Xinjun Chen wrote:

  Hi Razvan, 
   
  What I can think of is to insert a Handler in the request flow.
Inside the Handler, you can modify the message. If you are using Axis2,
you can write a module or a handler to do that. I believe this will be
much easier than customize Axis or Axis2. 
  Axis gurus, please correct me if I am not correct. 
 
  Regards, 
  Xinjun
 
  On 5/22/06, Razvan Dani <[EMAIL PROTECTED]>
wrote:
  Hi

thank you for your suggestion. if i reach desperation i will certainly
customize axis for my own use, but i'd certainly like to stick to the

"standard axis" if at all possible. otherwise when i want to switch to a
new version of axis latter on, i would be loosing by custom changes.

what i am ideally looking for is a way to "plug" (or whatever other
term

you prefer) an extra thing that would change axis behaviour without
modifying Axis source and making my personal axis.jar. I would be
perfectly able to do that if it's the only solution...

I think this is an interesting challenge to people with Axis
experience,

so i'd be more than happy to hear more opinions :) .

Regards,
   Razvan

Davanum Srinivas wrote:
> easier would be to edit axiom source
> (
http://svn.apache.org/repos/asf/webservices/commons/trunk/modules/axiom/src/org/apache/axiom/soap/SOAPConstants.java)
>
>
> and build a jar for your own use.
>
> -- dims
>
> On 5/22/06, Razvan Dani <
[EMAIL PROTECTED]>
wrote:
>>
>>  Hi Anne
>>
>>  Thank you for your suggestions. However as a person that only
found
>> Axis
>> few days ago, i am not sure how would i go about inserting and
>> intermediary
>> into my message path to transform the message (i.e. replace
>> occurences of
>> soapenv with soap-env).

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

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

>> into your
>> message path to transform the message.
>>
>>  Anne
>>
>>
>> On 5/22/06, Razvan Dani <[EMAIL PROTECTED]
> wrote:
>> > Hi
>> >
>> > I am not sure if this is the right place to address this,
but i'd
>> > appreciate some feedback if possible, because i already
made lots of

>> > queries on the internet about this issue with no success.
>> >
>> > My problem is the following:
>> > - i am using WSDL to Java ant task to generate classes
against a WSDL.

>> > - when i make a method call on the generated Stub (so
notice that i am
>> > not constructing the envelope by hand neither i use the
Call class
>> > directly), Axis is constructing the envelope as this:

>> > 
>> >
>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
>> >
>> > This works just fine for many Web Services, but in my
particular case,

>> > the Web Service implementation on the server side is
"hardcoded" to
>> only
>> > be able to accept
>> > 
>> > xmlns:soap-env="
http://schemas.xmlsoap.org/soap/envelope/
>> "
>> >
>> > I know this is an issue that should be fixed on the
server part since
>> > the Web Service specs is flexible to allow any prefix for
the envelope
>> > as long as the name space URL is correct. But i don't
have control on
>> > the server part and thus i would like to know if this
issue can be

>> > tackled from Axis.
>> >
>> > So the question is whether it is possible to make some
>> configuration in
>> > Axis so that i can specify at runtime what prefix should
be used

>> for the
>> > envelope (e.g. soap-env instead of soapenv)?
>> >
>> > Many thanks in advance if i receive any answer to this
issue.
>> >
>> > Regards,

>> >Razvan
>> >
>> > --
>> > Razvan Dani
>> >
>> > Senior Java Developer
>> >
>> > ARoBS Transilvania Software
>> >

>> > 11 Donath Str , M4 - 28
>> > 400301 Cluj-Napoca, Romania
>> >
>> > Main:   +40 264 598 204
>> > Fax:+40 264 598 426
>> > email:  
[EMAIL PROTECTED]
>> > www.ARoBS.com
>> >
>> >
>> >
>> >
>>
-

>> > To unsubscribe, e-mail:
>> [EMAIL PROTECTED]
>> > For additional commands, e-mail: 
[EMAIL PROTECTED]
>> >
>> >
>>
>>
>>
>>
>> --
>> Razvan Dani
>>
>> Senior Java Developer
>>
>> ARoBS Transilvania Software

>>
>> 11 Donath Str , M4 - 28
>> 400301 Cluj-Napoca, Romania
>>
>> Main: +40 264 598 204
>> Fax: +40 264 598

AXIS 1.2 and SOA

[Jayaraman, Venkatesh]

Is axis 1.2 considered as SOA?

 

Move AXIS2 to make remove JAX-RPC and become SOA compliant?

 

-Venky

Re: envelope prefix issue

[Xinjun Chen]

Hi Razvan, 
 
What I can think of is to insert a Handler in the request flow. Inside the Handler, you can modify the message. If you are using Axis2, you can write a module or a handler to do that. I believe this will be much easier than customize Axis or Axis2. 

Axis gurus, please correct me if I am not correct.  
Regards, 
Xinjun 
On 5/22/06, Razvan Dani <[EMAIL PROTECTED]> wrote:
Hithank you for your suggestion. if i reach desperation i will certainlycustomize axis for my own use, but i'd certainly like to stick to the
"standard axis" if at all possible. otherwise when i want to switch to anew version of axis latter on, i would be loosing by custom changes.what i am ideally looking for is a way to "plug" (or whatever other term
you prefer) an extra thing that would change axis behaviour withoutmodifying Axis source and making my personal axis.jar. I would beperfectly able to do that if it's the only solution...I think this is an interesting challenge to people with Axis experience,
so i'd be more than happy to hear more opinions :) .Regards,   RazvanDavanum Srinivas wrote:> easier would be to edit axiom source> (
http://svn.apache.org/repos/asf/webservices/commons/trunk/modules/axiom/src/org/apache/axiom/soap/SOAPConstants.java)>>> and build a jar for your own use.>> -- dims>> On 5/22/06, Razvan Dani <
[EMAIL PROTECTED]> wrote:  Hi Anne  Thank you for your suggestions. However as a person that only found>> Axis
>> few days ago, i am not sure how would i go about inserting and>> intermediary>> into my message path to transform the message (i.e. replace>> occurences of>> soapenv with soap-env).
  I would appreciate a lot if could could just point me to a sample>> code or>> to some documentation where that is explained.  Regards,>>  Razvan
  Anne Thomas Manes wrote:>> Axis does not provide this type of configuration option. Either>> construct>> the message programmatically using JAXP or insert an intermediary
>> into your>> message path to transform the message.  Anne>> On 5/22/06, Razvan Dani <[EMAIL PROTECTED]
> wrote:>> > Hi>> >>> > I am not sure if this is the right place to address this, but i'd>> > appreciate some feedback if possible, because i already made lots of
>> > queries on the internet about this issue with no success.>> >>> > My problem is the following:>> > - i am using WSDL to Java ant task to generate classes against a WSDL.
>> > - when i make a method call on the generated Stub (so notice that i am>> > not constructing the envelope by hand neither i use the Call class>> > directly), Axis is constructing the envelope as this:
>> > >> >>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">> >>> > This works just fine for many Web Services, but in my particular case,
>> > the Web Service implementation on the server side is "hardcoded" to>> only>> > be able to accept>> > >> > xmlns:soap-env="
http://schemas.xmlsoap.org/soap/envelope/>> ">> >>> > I know this is an issue that should be fixed on the server part since
>> > the Web Service specs is flexible to allow any prefix for the envelope>> > as long as the name space URL is correct. But i don't have control on>> > the server part and thus i would like to know if this issue can be
>> > tackled from Axis.>> >>> > So the question is whether it is possible to make some>> configuration in>> > Axis so that i can specify at runtime what prefix should be used
>> for the>> > envelope (e.g. soap-env instead of soapenv)?>> >>> > Many thanks in advance if i receive any answer to this issue.>> >>> > Regards,
>> >Razvan>> >>> > -->> > Razvan Dani>> >>> > Senior Java Developer>> >>> > ARoBS Transilvania Software>> >
>> > 11 Donath Str , M4 - 28>> > 400301 Cluj-Napoca, Romania>> >>> > Main:   +40 264 598 204>> > Fax:+40 264 598 426>> > email:  
[EMAIL PROTECTED]>> > www.ARoBS.com>> >>> >>> >>> >>> -
>> > To unsubscribe, e-mail:>> [EMAIL PROTECTED]>> > For additional commands, e-mail: 
[EMAIL PROTECTED]>> >>> >>> -->> Razvan Dani Senior Java Developer ARoBS Transilvania Software
 11 Donath Str , M4 - 28>> 400301 Cluj-Napoca, Romania Main: +40 264 598 204>> Fax: +40 264 598 426>> email: [EMAIL PROTECTED]
>> www.ARoBS.com--Razvan DaniSenior Java DeveloperARoBS Transilvania Software11 Donath Str , M4 - 28
400301 Cluj-Napoca, RomaniaMain:   +40 264 598 204Fax:+40 264 598 426email:  [EMAIL PROTECTED]www.ARoBS.com-
To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

Re: Inconsistent Array Elements

[Stephan Fischli]

Dear Anne

Thank you for the quick answer. I migrated my server installation to Axis 1.4 but unfortunately the problem remains.

Regards, Stephan



View this message in context: Re: Inconsistent Array Elements
Sent from the Axis - User forum at Nabble.com.

Location of SAAJUtil?

[Daniel Jemiolo]

Hi,

Which jar file is the org.apache.axis2.saaj.util
package in? I'm trying to compile a project that uses SAAJUtil and can't
find the class in any of the $AXIS2_WAR/WEB-INF/lib or $STANDARD_DISTRIBUTION/lib
archives. I see the code in SVN, I'm just not sure where it's packaged.

Thanks,
Dan


Dan Jemiolo
IBM Corporation
Research Triangle Park, NC


+++ I'm an engineer. I make slides that people can't read. Sometimes I
eat donuts. +++

XML Non-English Character Support

[Recep Ayaz]

Hello,Does anyone know how I can add Non-English character support to my Axis web services? Should I add the encoding information to my wsdd file or somethig else?Appreciate on help.Thanks.

Re: envelope prefix issue

[Razvan Dani]

Hi

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


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


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


Regards,
   Razvan

Davanum Srinivas wrote:

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



and build a jar for your own use.

-- dims

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


 Hi Anne

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

soapenv with soap-env).

 I would appreciate a lot if could could just point me to a sample 
code or

to some documentation where that is explained.

 Regards,
 Razvan



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

message path to transform the message.

 Anne


On 5/22/06, Razvan Dani <[EMAIL PROTECTED]> wrote:
> Hi
>
> I am not sure if this is the right place to address this, but i'd
> appreciate some feedback if possible, because i already made lots of
> queries on the internet about this issue with no success.
>
> My problem is the following:
> - i am using WSDL to Java ant task to generate classes against a WSDL.
> - when i make a method call on the generated Stub (so notice that i am
> not constructing the envelope by hand neither i use the Call class
> directly), Axis is constructing the envelope as this:
> 
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
>
> This works just fine for many Web Services, but in my particular case,
> the Web Service implementation on the server side is "hardcoded" to 
only

> be able to accept
>  xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/
"
>
> I know this is an issue that should be fixed on the server part since
> the Web Service specs is flexible to allow any prefix for the envelope
> as long as the name space URL is correct. But i don't have control on
> the server part and thus i would like to know if this issue can be
> tackled from Axis.
>
> So the question is whether it is possible to make some 
configuration in
> Axis so that i can specify at runtime what prefix should be used 
for the

> envelope (e.g. soap-env instead of soapenv)?
>
> Many thanks in advance if i receive any answer to this issue.
>
> Regards,
>Razvan
>
> --
> Razvan Dani
>
> Senior Java Developer
>
> ARoBS Transilvania Software
>
> 11 Donath Str , M4 - 28
> 400301 Cluj-Napoca, Romania
>
> Main:   +40 264 598 204
> Fax:+40 264 598 426
> email:  [EMAIL PROTECTED]
> www.ARoBS.com
>
>
>
>
-
> To unsubscribe, e-mail:
[EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>




--
Razvan Dani

Senior Java Developer

ARoBS Transilvania Software

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

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







--
Razvan Dani

Senior Java Developer

ARoBS Transilvania Software

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

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




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

Re: [Axis2] WSDL Generation

[Ingo Siebert]

Thank you,
i deleted the dir and the wizard starts now.

I've get at the end of the wizard an TargetInvocationException, but my 
app build process isn't complete so it's possible that's why it isn't 
working. But the classpath-check was successful...

Cheers,

Ingo

Ajith Ranabahu schrieb:

hmmm..
I guess this is probably related to the fact that you had the previous
version of the plugin installed. Try doing this
goto the .metadata -> .plugins folder and find the folder relevant to
the plugin (Axis2_Codegen_Wizard) and delete it. this erases the
settings related to the earlier plugin

Ajith



On 5/22/06, Ingo Siebert <[EMAIL PROTECTED]> wrote:

Hi,

i've installed 1.2 (1.1 before) and it's not grey anymore. But if i
select it and press "next", nothing happens (Eclipse 3.1.2).

Ingo


Ajith Ranabahu schrieb:
> hi.
> You are probably having an old version of the plugin. Download the
> latest from
> http://ws.apache.org/axis2/tools/index.html
>
> Ajith
>
> On 5/22/06, Ingo Siebert <[EMAIL PROTECTED]> wrote:
>> Hi,
>>
>> the option "Generate WSDL form Java source file" isn't 
selectable(grey).

>> Cheers,
>>
>> Ingo
>>
>> Kinichiro Inoguchi schrieb:
>> > Ingo,
>> >
>> > With Axis2, how about using "Code Generator Wizard - eclipse 
Plug-in".

>> > http://ws.apache.org/axis2/tools/1_0/eclipse/wsdl2java-plugin.html
>> > You can generate WSDL from java code.
>> >
>> > Or, deploying service using RPCMessageReceiver, Axis2 will generates
>> > WSDL automatically.
>> > You can see WSDL via url, like
>> > http://server:port/axis2/services/version?wsdl.
>> > Please check sample service, "version".
>> >
>> > Regards,
>> > kinichiro
>> >
>> > --- A A <[EMAIL PROTECTED]> wrote:
>> >
>> >> Easily possible; deploy your java file into axis2 (version< 1)
>> >> repository
>> >> with jws extension.
>> >> call http://hostname/axis/yourjava.jws from your browser and 
here is

>> >> the
>> >> WSDL !
>> >>
>> >> On 5/22/06, Ingo Siebert <[EMAIL PROTECTED]> wrote:
>> >>> Hi,
>> >>>
>> >>> is it possible to generate the WSDL file from Java code?
>> >>> I found only a tool which creates server/client stubs from a WSDL
>> >> file.
>> >>> Cheers,
>> >>>
>> >>> Ingo



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

Re: envelope prefix issue

[Davanum Srinivas]

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

and build a jar for your own use.

-- dims

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


 Hi Anne

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

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

 Regards,
 Razvan



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

 Anne


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




--
Razvan Dani

Senior Java Developer

ARoBS Transilvania Software

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

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




--
Davanum Srinivas : http://wso2.com/blogs/

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

some question

[eL. Bi.]

Hi,

i create a system of authentication with client/side
structure, i want to deploy it as Web Service, so i
choose Axix + Tomcat to do it. I have some questions:

A) i  have my own class that construct SOAP messages,
so it is possible to disable in the wsdll file the
serialization and deserialization automatic of Axis?
How i can do it?

B) If it isn't possbile to disable totally the
automatic construction of SOAP, it's possibile to pass
my soap messages as strings?

C) in my system i use methods in my class with static,
this is correct or it's better to don't use it?

Tanks for help, Luca.







___ 
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB 
http://mail.yahoo.it

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

Re: envelope prefix issue

[Razvan Dani]

Hi Anne

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

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

Regards,
    Razvan


Anne Thomas Manes wrote:
Axis does not provide this type of configuration option.
Either construct the message programmatically using JAXP or insert an
intermediary into your message path to transform the message. 
  
Anne
  
  On 5/22/06, Razvan Dani <[EMAIL PROTECTED]>
wrote:
  Hi

I am not sure if this is the right place to address this, but i'd
appreciate some feedback if possible, because i already made lots of
queries on the internet about this issue with no success.

My problem is the following:

- i am using WSDL to Java ant task to generate classes against a WSDL.
- when i make a method call on the generated Stub (so notice that i am
not constructing the envelope by hand neither i use the Call class
directly), Axis is constructing the envelope as this:

xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"

This works just fine for many Web Services, but in my particular case,

the Web Service implementation on the server side is "hardcoded" to only
be able to accept

xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/
"

I know this is an issue that should be fixed on the server part since
the Web Service specs is flexible to allow any prefix for the envelope
as long as the name space URL is correct. But i don't have control on

the server part and thus i would like to know if this issue can be
tackled from Axis.

So the question is whether it is possible to make some configuration in
Axis so that i can specify at runtime what prefix should be used for
the

envelope (e.g. soap-env instead of soapenv)?

Many thanks in advance if i receive any answer to this issue.

Regards,
   Razvan

--
Razvan Dani

Senior Java Developer

ARoBS Transilvania Software


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

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




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

  
  
  



-- 
Razvan Dani

Senior Java Developer

ARoBS Transilvania Software

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

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

[Axis2] WSDL Generation from Java (Java2WSDL

[Hansen, Geir]

In Axis 1.x there was a tool Java2Wsdl.

I downloaded the Axis2 1.0 release and the IntelliJ IDEA plugin, but
cannot find the same tool in there, only WSDL2Java.

Is this tool available in some way?

Geir Hansen

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

Re: [Axis2] WSDL Generation

[Ajith Ranabahu]

hmmm..
I guess this is probably related to the fact that you had the previous
version of the plugin installed. Try doing this
goto the .metadata -> .plugins folder and find the folder relevant to
the plugin (Axis2_Codegen_Wizard) and delete it. this erases the
settings related to the earlier plugin

Ajith



On 5/22/06, Ingo Siebert <[EMAIL PROTECTED]> wrote:

Hi,

i've installed 1.2 (1.1 before) and it's not grey anymore. But if i
select it and press "next", nothing happens (Eclipse 3.1.2).

Ingo


Ajith Ranabahu schrieb:
> hi.
> You are probably having an old version of the plugin. Download the
> latest from
> http://ws.apache.org/axis2/tools/index.html
>
> Ajith
>
> On 5/22/06, Ingo Siebert <[EMAIL PROTECTED]> wrote:
>> Hi,
>>
>> the option "Generate WSDL form Java source file" isn't selectable(grey).
>> Cheers,
>>
>> Ingo
>>
>> Kinichiro Inoguchi schrieb:
>> > Ingo,
>> >
>> > With Axis2, how about using "Code Generator Wizard - eclipse Plug-in".
>> > http://ws.apache.org/axis2/tools/1_0/eclipse/wsdl2java-plugin.html
>> > You can generate WSDL from java code.
>> >
>> > Or, deploying service using RPCMessageReceiver, Axis2 will generates
>> > WSDL automatically.
>> > You can see WSDL via url, like
>> > http://server:port/axis2/services/version?wsdl.
>> > Please check sample service, "version".
>> >
>> > Regards,
>> > kinichiro
>> >
>> > --- A A <[EMAIL PROTECTED]> wrote:
>> >
>> >> Easily possible; deploy your java file into axis2 (version< 1)
>> >> repository
>> >> with jws extension.
>> >> call http://hostname/axis/yourjava.jws from your browser and here is
>> >> the
>> >> WSDL !
>> >>
>> >> On 5/22/06, Ingo Siebert <[EMAIL PROTECTED]> wrote:
>> >>> Hi,
>> >>>
>> >>> is it possible to generate the WSDL file from Java code?
>> >>> I found only a tool which creates server/client stubs from a WSDL
>> >> file.
>> >>> Cheers,
>> >>>
>> >>> Ingo


-
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][1.0] fireAndDontForget ??

[Ali Sadik Kumlali]

Hi Deepal,

Thank you for spending your time with my problem. Should I open a JIRA
for this?

Regards,

Ali Sadik Kumlali

--- Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:

> Hi Ali
> 
> Ali Sadik Kumlali wrote:
> 
> >Hi all,
> >
> >What I want is:
> >- Make a request to a service which uses
> RawXMLINOnlyMessageReceiver.
> >- If server sends HTTP 200 or 202, don't expect the input stream
> being
> >not null and don't do anything.
> >- If server sends HTTP 500, retrieve the stream (which is a
> SOAPFault)
> >and throw the AxisFault.
> >
> >I tried many things:
> >- fireAndForget(): Doesn't handle HTTP 500
> >  
> >
> hmmm , I am not sure that fireAndForget handle HTTP500 or not.
> 
> >- sendRobust(): Can handle HTTP 500. But it expects a not-null input
> >stream from the server.
> >  
> >
> sendRobuts problem need to be fixed.
> 
> >Is there a way doing this?
> >
> >Any help would be appreciated.
> >
> >Ali Sadik Kumlali
> >
> >__
> >Do You Yahoo!?
> >Tired of spam?  Yahoo! Mail has the best spam protection around 
> >http://mail.yahoo.com 
> >
> >
> >  
> >
> 
> -- 
> Thanks,
> Deepal
> 
> ~Future is Open~ 
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

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

Re: Client Repository

[Eran Chinthaka]

Lakshmi Chaparala wrote:
> Hi,
> 
> We are using axis2.1.0. Does this version still need client repository
> specified ?
> 
> ServiceClient client = new ServiceClient(configcontext, null);

Nope, you can call,

ServiceClient client = new ServiceClient();

-- EC

> 
>  
> 
> Lakshmi
> 
>  
> 




signature.asc
Description: OpenPGP digital signature

Re: [Axis2][1.0] "Transport error 500" for EchoBlockingDualClient & echoF

[Ali Sadik Kumlali]

Hi Deepal,

Thanks for the reply. I had already created a JIRA issue:
http://issues.apache.org/jira/browse/AXIS2-741

Regards,

Ali Sadik Kumlali


--- Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:

> create  a JIRA
> 
> Ali Sadik Kumlali wrote:
> 
> >Hi all,
> >
> >When I use EchoBlockingDualClient to invoke echoF service which
> throws
> >AxisFault, I run into a strange(?) situation.
> >
> >Server returnes back an error through the *first* channel. Error
> says
> >"Transport error 500 . Error Message is Apache
> >Tomcat/5.5.14 - Error report...".
> >
> >Then the server sends the actual error over the *second* channel. 
> >
> >When I look at the server logs, AxisFault thrown by echoF is shown.
> >There seems no transport related errors.
> >
> >However, client *only* catches the first error and writes it down to
> >the console. Then, it throws another exception that says
> >"org.apache.axis2.AxisFault: Time out while waiting for the server
> to
> >send the response"
> >
> >I've listed echoF and the client side stack trace below.
> >
> >Is this the expected behaviour or should I create a JIRA log?
> >
> >Thanks in advance,
> >
> >Ali Sadik Kumlali
> >
> >
> >
> >public OMElement echoF(OMElement element) throws AxisFault {
> >  throw new AxisFault("MyFault message", "MyFaultCode");
> >}
> >
> >
> >- Transport error 500 . Error Message is Apache
> >Tomcat/5.5.14 - Error report
> >HTTP Status 500 -  >noshade="noshade">type Status reportmessage
> >description The server encountered an
> internal
> >error () that prevented it from fulfilling this request. >size="1" noshade="noshade">Apache
> Tomcat/5.5.14;
> >nested exception is: 
> >...
> >
> >
> >org.apache.axis2.AxisFault: Time out while waiting for the server to
> >send the response[SimpleHTTPServer] Stop called
> > at
>
>org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:448)
> > at
>
>org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:399)
> > at
>
>userguide.clients.EchoBlockingDualClient.main(EchoBlockingDualClient.java:54)
> >
> >
> >__
> >Do You Yahoo!?
> >Tired of spam?  Yahoo! Mail has the best spam protection around 
> >http://mail.yahoo.com 
> >
> >
> >  
> >
> 
> -- 
> Thanks,
> Deepal
> 
> ~Future is Open~ 
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

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

[Axis2] directories and the files generated ???

[Mérième N]

Hi,Do you have any guidelines or documents, which explain what are the directories and the files generated by WSDL2Java tool provided by Axis2 and their use?Thanking you in advance.Regards,Merieme

Re: Sax exception:Invalid element in...

[Roy]

Thank you for your fast response.I compared the wsdl to the returned message and it seems ok(I checked the response objects and have the same names and structures to the ones i get in the response).  Is there any other way to check the response i should get ? Can i use a custom deserialiser for the response?Anne Thomas Manes <[EMAIL PROTECTED]> έγραψε: Compare the return message to the expected schema as defined by the WSDL. It's likely that the service is returning a message that doesn't conform to the schema. If so, you should report the error to the service provider. If they won't fix the error, then you may need to modify the WSDL so that it specifies a schema that matches the actual return message. AnneOn 5/22/06, Roy <[EMAIL PROTECTED]> wrote: Hello,I use axis 1.3 to call a service that is implemented in an uknown language (probably .NET but not Java). I have generated the classes with the wsdl2Java tool from the service's  WSDL and i called normally the service with a static stub. In the SOAP monitor i can see the respone with the expected data but i get this SAX exception: org.xml.sax.SAXException:Invalid element in com.advertsoft.APP_Response.USERS - DataValuesat org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258)I have read previous threads and i noticed that probably is a problem in the first character of DataValues(it is capital?) tag in the response. Can anyone please give a way of how to solve this and deserialize the respnse
 normally?Thanks in advance,Roy Χρησιμοποιείτε Yahoo!  Βαρεθήκατε τα ενοχλητικά μηνύ ματα (spam); Το Yahoo! Mail διαθέτει την καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων   http://login.yahoo.com/config/mail?.intl=gr   
		 
Χρησιμοποιείτε Yahoo! 
Βαρεθήκατε τα ενοχλητικά μηνύ ματα (spam); Το Yahoo! Mail διαθέτει την καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων  
http://login.yahoo.com/config/mail?.intl=gr 

Re: [Axis2] specifying username and password

[Kees de Kooter]

Found it:

   HttpTransportProperties.BasicAuthentication
   basicAuthentication = new HttpTransportProperties().
   new BasicAuthentication();
   basicAuthentication.setUsername(userName);
   basicAuthentication.setPassword(password);

   options.setProperty(HTTPConstants.BASIC_AUTHENTICATION,
   basicAuthentication);

It is available in the snapshots.

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

Re: Migrating to Axis 2

[Anne Thomas Manes]

No -- you just have to use a bean to wrap your parameters. AnneOn 5/20/06, Scott McCoy <[EMAIL PROTECTED]> wrote:
I see, so I'm basically married to axis 1.3 for the time being.
- ScottOn 5/20/06, Anne Thomas Manes <
[EMAIL PROTECTED]
> wrote:Axis 2 does not yet support automatic unwrapping of wrapped doc/literal ...
On 5/20/06, Scott McCoy <
[EMAIL PROTECTED]> wrote:

Okay, attached is a WSDL that worked fine for generating very simple to use wrapped document/literal services with WSDL2Java.
Now, the code WSDL2Java generates is as though the wrapped document/literal convention is broken.
It accepts a "Request" bean for each argument, and expects a "Response" bean in return.What the heck?    Thanks,    Scott S. McCoy

-To unsubscribe, e-mail: 

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

Re: [Axis2] Server did not recognize the value of HTTP Header SOAPAction

[Kees de Kooter]

Thanks Anne!

On 5/22/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:

The SOAPAction value is a URI. The WSDL should specify the required
SOAPAction value.

Anne




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

Re: [Axis2] [1.0] RPC primitive types

[Anne Thomas Manes]

Axis2 does not yet support automatic unwrapping of parameters (e.g., wrapped doc/literal).Wait for the next release. In the meantime, you must wrap your parameters into a bean.Anne
On 5/21/06, Ahmed Ashour <[EMAIL PROTECTED]> wrote:
Dear Martin,     Thanks for your feedback.     However, I am asking for Axis2, not older Axis.     .wssd does not apply there.   
  Kind regards,  Ahmed AshourMartin Gainty <
[EMAIL PROTECTED]> wrote:  
The axis deploy implementation   java org.apache.axis.utils.Admin server (where server-config.wsdd is the master list of web services)
  For the service you are deploying the provider attribute for the service in your server should specify transport e.g.  
     Does this answer your question?Martin --     This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message isaddressed.  If you have received this email message in error, please notifythe sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.
- Original Message -   
From: Ahmed Ashour   
To: axis-user@ws.apache.org   
Sent: Sunday, May 21, 2006 8:02 AM  
Subject: [Axis2] [1.0] RPC primitive typesDear All,     I couldn't figure out a away for RPC handler to generate primitive types instead of unnecessary wrapping.
     For instance, to use .NET client for "Version" sample:     Version.version
 version = new Version.version();  Version.getVersion
 versionParam = new Version.getVersion();  
String value = version.getVersion( versionParam )[EMAIL PROTECTED];     Axis 1.3 does it much more nicely.
     Any ideas? Many thanks.     Ahmed Ashour  Ring'em or ping'em. Make 
PC-to-phone calls as low as 1¢/min
 with Yahoo! Messenger with Voice.
		How low will we go? Check out Yahoo! Messenger's low 
 PC-to-Phone call rates.

Re: [AXIS 2] [vers 1] : does php nuSOAP understand AXIS 2 ver 1 ?

[Anne Thomas Manes]

Try capturing the input message and comparing it to input messages submitted by your jsp client. See what's different.AnneOn 5/22/06, A A <
[EMAIL PROTECTED]> wrote:I have developped a web service using AXIS 2 version1, everythings work fine with a "jsp client" and "SOAPUI 
1.5" but when i call the service with php nuSOAP i have this SOAP response:Array([faultcode] => soapenv:Client[faultstring] => null; nested exception is: 	java.lang.NullPointerException
[detail] => Array([Exception] => org.apache.axis2.AxisFault: null; nested exception is: 	java.lang.NullPointerException	at org.apache.axis2.AxisFault.makeFault(AxisFault.java
:318)	at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:136)	at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java
:37)	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)	at org.apache.axis2.transport.http.AxisServlet.doPost
(AxisServlet.java:136)	at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)	at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:237)	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
	at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)	at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)	at org.apache.catalina.core.StandardContextValve.invokeInternal
(StandardContextValve.java:198)	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
	at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)	at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)	at org.apache.catalina.core.StandardHostValve.invoke
(StandardHostValve.java:137)	at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)	at org.apache.catalina.core.StandardValveContext.invokeNext
(StandardValveContext.java:102)	at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)	at org.apache.catalina.core.StandardValveContext.invokeNext
(StandardValveContext.java:104)	at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)	at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)	at org.apache.coyote.tomcat5.CoyoteAdapter.service
(CoyoteAdapter.java:160)	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)

	at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)	at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)	at java.lang.Thread.run(Thread.java:534)Caused by: 
java.lang.NullPointerException	at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:87)	... 30 more))

Re: Inconsistent Array Elements

[Anne Thomas Manes]

It's a bug. Upgrade to Axis 1.4.On 5/22/06, Stephan Fischli <[EMAIL PROTECTED]> wrote:

Hi

I have deployed a Stock Quoter Service with Axis 1.3 whose operation "getSymbols" returns an array of strings. According to the generated
WSDL
the array elements should be named "item". But in the SOAP response the array elements have the name "getSymbolsReturn".
Does anybody have an explanation of this obvious contradiction?

Thanks, Stephan

View this message in context: Inconsistent Array Elements
Sent from the Axis - User forum at 
Nabble.com.

Re: [Axis2] Server did not recognize the value of HTTP Header SOAPAction

[Anne Thomas Manes]

The SOAPAction value is a URI. The WSDL should specify the required SOAPAction value. AnneOn 5/22/06, Kees de Kooter <
[EMAIL PROTECTED]> wrote:Thanks Deepal,That works. What kind of value is expected anyway?
On 5/22/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:>>> Kees de Kooter wrote:>> > How can I set the SOAPAction??
>> option.setAction("soapaction");>> >> > This is the stacktrace:> >> > org.apache.axis2.AxisFault: Server did not recognize the value of HTTP> > Header SOAPAction: .
> > at> > org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:287)> >> > at> > org.apache.axis2.client.ServiceClient.sendReceive(
ServiceClient.java:432)> > at> > org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:374)> > at> > com.trafficits.soap.WebServiceConsumer.invoke(WebServiceConsumer.java
:81)> >> >> > And this is my code:> >> > EndpointReference endpointReference = new EndpointReference(> > endPointAddress);> >> > Options options = new Options();
> > options.setTo(endpointReference);> > options.setTransportInProtocol(Constants.TRANSPORT_HTTP);> >> > OMFactory factory = OMAbstractFactory.getOMFactory();> >> > OMNamespace namespace = 
factory.createOMNamespace(> > nameSpaceUri, "webService");> >> > OMElement method = factory.createOMElement(methodName, namespace);> >> > ServiceClient serviceClient = new ServiceClient();
> > serviceClient.setOptions(options);> >> > OMElement result = serviceClient.sendReceive(method);> >> >>> --> Thanks,> Deepal> 
> ~Future is Open~ -> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]>>--Cheers,Kees de Kooter
http://www.boplicity.net-To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Sax exception:Invalid element in...

[Anne Thomas Manes]

Compare the return message to the expected schema as defined by the WSDL. It's likely that the service is returning a message that doesn't conform to the schema. If so, you should report the error to the service provider. If they won't fix the error, then you may need to modify the WSDL so that it specifies a schema that matches the actual return message.
AnneOn 5/22/06, Roy <[EMAIL PROTECTED]> wrote:
Hello,I use axis 1.3 to call a service that is implemented in an uknown language (probably .NET but not Java). I have generated the classes with the wsdl2Java tool from the service's  WSDL and i called normally the service with a static stub. In the SOAP monitor i can see the respone with the expected data but i get this SAX exception:
org.xml.sax.SAXException:Invalid element in com.advertsoft.APP_Response.USERS - DataValuesat org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258)I have read previous threads and i noticed that probably is a problem in the first character of DataValues(it is capital?) tag in the response.
Can anyone please give a way of how to solve this and deserialize the respnse normally?Thanks in advance,Roy
		 
Χρησιμοποιείτε Yahoo! 
Βαρεθήκατε τα ενοχλητικά μηνύ ματα (spam); Το Yahoo! Mail διαθέτει την καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων  
http://login.yahoo.com/config/mail?.intl=gr 

Re: [Axis2] Server did not recognize the value of HTTP Header SOAPAction

[Kees de Kooter]

Thanks Deepal,

That works. What kind of value is expected anyway?


On 5/22/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:



Kees de Kooter wrote:

> How can I set the SOAPAction??

option.setAction("soapaction");

>
> This is the stacktrace:
>
> org.apache.axis2.AxisFault: Server did not recognize the value of HTTP
> Header SOAPAction: .
> at
> 
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:287)
>
> at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:432)
> at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:374)
> at
> com.trafficits.soap.WebServiceConsumer.invoke(WebServiceConsumer.java:81)
>
>
> And this is my code:
>
> EndpointReference endpointReference = new EndpointReference(
> endPointAddress);
>
> Options options = new Options();
> options.setTo(endpointReference);
> options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
>
> OMFactory factory = OMAbstractFactory.getOMFactory();
>
> OMNamespace namespace = factory.createOMNamespace(
> nameSpaceUri, "webService");
>
> OMElement method = factory.createOMElement(methodName, namespace);
>
> ServiceClient serviceClient = new ServiceClient();
> serviceClient.setOptions(options);
>
> OMElement result = serviceClient.sendReceive(method);
>
>

--
Thanks,
Deepal

~Future is Open~



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





--
Cheers,
Kees de Kooter
http://www.boplicity.net

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

Re: [Axis2] Server did not recognize the value of HTTP Header SOAPAction

[Anne Thomas Manes]

options.setActionOn 5/22/06, Kees de Kooter <[EMAIL PROTECTED]> wrote:
How can I set the SOAPAction??This is the stacktrace:org.apache.axis2.AxisFault: Server did not recognize the value of HTTPHeader SOAPAction: .at org.apache.axis2.description.OutInAxisOperationClient.execute
(OutInAxisOperation.java:287)at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:432)at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:374)at com.trafficits.soap.WebServiceConsumer.invoke
(WebServiceConsumer.java:81)And this is my code:EndpointReference endpointReference = new EndpointReference(endPointAddress);Options options = new Options();options.setTo(endpointReference);
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);OMFactory factory = OMAbstractFactory.getOMFactory();OMNamespace namespace = factory.createOMNamespace(nameSpaceUri, "webService");
OMElement method = factory.createOMElement(methodName, namespace);ServiceClient serviceClient = new ServiceClient();serviceClient.setOptions(options);OMElement result = serviceClient.sendReceive
(method);--Cheers,Kees de Kooterhttp://www.boplicity.net-To unsubscribe, e-mail: 
[EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] WSDL Generation

[Ingo Siebert]

Hi,

i've installed 1.2 (1.1 before) and it's not grey anymore. But if i 
select it and press "next", nothing happens (Eclipse 3.1.2).


Ingo


Ajith Ranabahu schrieb:

hi.
You are probably having an old version of the plugin. Download the 
latest from

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

Ajith

On 5/22/06, Ingo Siebert <[EMAIL PROTECTED]> wrote:

Hi,

the option "Generate WSDL form Java source file" isn't selectable(grey).
Cheers,

Ingo

Kinichiro Inoguchi schrieb:
> Ingo,
>
> With Axis2, how about using "Code Generator Wizard - eclipse Plug-in".
> http://ws.apache.org/axis2/tools/1_0/eclipse/wsdl2java-plugin.html
> You can generate WSDL from java code.
>
> Or, deploying service using RPCMessageReceiver, Axis2 will generates
> WSDL automatically.
> You can see WSDL via url, like
> http://server:port/axis2/services/version?wsdl.
> Please check sample service, "version".
>
> Regards,
> kinichiro
>
> --- A A <[EMAIL PROTECTED]> wrote:
>
>> Easily possible; deploy your java file into axis2 (version< 1)
>> repository
>> with jws extension.
>> call http://hostname/axis/yourjava.jws from your browser and here is
>> the
>> WSDL !
>>
>> On 5/22/06, Ingo Siebert <[EMAIL PROTECTED]> wrote:
>>> Hi,
>>>
>>> is it possible to generate the WSDL file from Java code?
>>> I found only a tool which creates server/client stubs from a WSDL
>> file.
>>> Cheers,
>>>
>>> Ingo



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

Re: [Axis2] Server did not recognize the value of HTTP Header SOAPAction

[Deepal Jayasinghe]

Kees de Kooter wrote:

> How can I set the SOAPAction??

option.setAction("soapaction");

>
> This is the stacktrace:
>
> org.apache.axis2.AxisFault: Server did not recognize the value of HTTP
> Header SOAPAction: .
> at
> org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:287)
>
> at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:432)
> at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:374)
> at
> com.trafficits.soap.WebServiceConsumer.invoke(WebServiceConsumer.java:81)
>
>
> And this is my code:
>
> EndpointReference endpointReference = new EndpointReference(
> endPointAddress);
>
> Options options = new Options();
> options.setTo(endpointReference);
> options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
>
> OMFactory factory = OMAbstractFactory.getOMFactory();
>
> OMNamespace namespace = factory.createOMNamespace(
> nameSpaceUri, "webService");
>
> OMElement method = factory.createOMElement(methodName, namespace);
>
> ServiceClient serviceClient = new ServiceClient();
> serviceClient.setOptions(options);
>
> OMElement result = serviceClient.sendReceive(method);
>
>

-- 
Thanks,
Deepal

~Future is Open~ 



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

Re: Schema validation

[Anne Thomas Manes]

Ken,I agree with Martin -- your service provider should supply you with a new WSDL. Have you tried just doing a GET on the service URL appended with "?wsdl"?. In the meantime, you can use a handler to validate the message. Java provides native support for validation in the 
javax.xml.validation package.AnneOn 5/22/06, Martin Gainty <[EMAIL PROTECTED]> wrote:
Good Morning KenWho(m)ever is supplying the WSDL to you is responsible for specifying request and response for all methods along with specifyingparameters to those methods.Who(m)ever is changing the schema needs to re-gen and re-publish the WSDL
A situation arose where my webservice is now returning a String parameter so I have re-published and regen'ed the WSDL to reflect the response string
  Does this answer your question?Martin --*
This email message and any files transmitted with it contain confidentialinformation intended only for the person(s) to whom this email message isaddressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the originalmessage without making a copy.  Thank you.- Original Message -From: "Ken Tam" <
[EMAIL PROTECTED]>To: Sent: Sunday, May 21, 2006 9:18 PMSubject: Schema validation> Hi all,>> I am consuming web services made available from my customer. I was given a
> very elaborate WSDL with schemas and I was able to generate the stubs by> using Axis's WSDL2Java. Everything was working fine until the service was> changed on the customer's end. This causes the deserialization step to fail
> as the SOAP response does not match the schema. The customer in this case is> a big company and they don't tend to respond in a timely manner. However,> the problem persists which I must fix. I am using Axis 
1.3 and it doesn't> seem to validate the SOAP response with the WSDL's schema. How do I> configure Axis to do so? Currently, I had to spend quite a bit of time to> track down the mismatches. I figure if the schema is used to validate, it
> should point out the mismatches right off to spare me the time to track them> down.>> Thanks,> Ken -
> To unsubscribe, e-mail: [EMAIL PROTECTED]> For additional commands, e-mail: [EMAIL PROTECTED]
>>

[Axis2] Server did not recognize the value of HTTP Header SOAPAction

[Kees de Kooter]

How can I set the SOAPAction??

This is the stacktrace:

org.apache.axis2.AxisFault: Server did not recognize the value of HTTP
Header SOAPAction: .
at 
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:287)
at 
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:432)
at 
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:374)
at 
com.trafficits.soap.WebServiceConsumer.invoke(WebServiceConsumer.java:81)


And this is my code:

EndpointReference endpointReference = new EndpointReference(
endPointAddress);

Options options = new Options();
options.setTo(endpointReference);
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);

OMFactory factory = OMAbstractFactory.getOMFactory();

OMNamespace namespace = factory.createOMNamespace(
nameSpaceUri, "webService");

OMElement method = factory.createOMElement(methodName, namespace);

ServiceClient serviceClient = new ServiceClient();
serviceClient.setOptions(options);

OMElement result = serviceClient.sendReceive(method);


--
Cheers,
Kees de Kooter
http://www.boplicity.net

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

Re: envelope prefix issue

[Anne Thomas Manes]

Or -- customize Axis. On 5/22/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
Axis does not provide this type of configuration option. Either construct the message programmatically using JAXP or insert an intermediary into your message path to transform the message. 
Anne
On 5/22/06, Razvan Dani <[EMAIL PROTECTED]> wrote:

HiI am not sure if this is the right place to address this, but i'dappreciate some feedback if possible, because i already made lots ofqueries on the internet about this issue with no success.My problem is the following:
- i am using WSDL to Java ant task to generate classes against a WSDL.- when i make a method call on the generated Stub (so notice that i amnot constructing the envelope by hand neither i use the Call class

directly), Axis is constructing the envelope as this:xmlns:soapenv="
http://schemas.xmlsoap.org/soap/envelope/"This works just fine for many Web Services, but in my particular case,
the Web Service implementation on the server side is "hardcoded" to onlybe able to acceptxmlns:soap-env="
http://schemas.xmlsoap.org/soap/envelope/
"I know this is an issue that should be fixed on the server part sincethe Web Service specs is flexible to allow any prefix for the envelopeas long as the name space URL is correct. But i don't have control on
the server part and thus i would like to know if this issue can betackled from Axis.So the question is whether it is possible to make some configuration inAxis so that i can specify at runtime what prefix should be used for the
envelope (e.g. soap-env instead of soapenv)?Many thanks in advance if i receive any answer to this issue.Regards,   Razvan--Razvan DaniSenior Java DeveloperARoBS Transilvania Software
11 Donath Str , M4 - 28400301 Cluj-Napoca, RomaniaMain:   +40 264 598 204Fax:+40 264 598 426email:  
[EMAIL PROTECTED]www.ARoBS.com
-To unsubscribe, e-mail: 
[EMAIL PROTECTED]For additional commands, e-mail: 
[EMAIL PROTECTED]

Re: envelope prefix issue

[Anne Thomas Manes]

Axis does not provide this type of configuration option. Either construct the message programmatically using JAXP or insert an intermediary into your message path to transform the message. Anne
On 5/22/06, Razvan Dani <[EMAIL PROTECTED]> wrote:
HiI am not sure if this is the right place to address this, but i'dappreciate some feedback if possible, because i already made lots ofqueries on the internet about this issue with no success.My problem is the following:
- i am using WSDL to Java ant task to generate classes against a WSDL.- when i make a method call on the generated Stub (so notice that i amnot constructing the envelope by hand neither i use the Call class
directly), Axis is constructing the envelope as this:xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"This works just fine for many Web Services, but in my particular case,
the Web Service implementation on the server side is "hardcoded" to onlybe able to acceptxmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/
"I know this is an issue that should be fixed on the server part sincethe Web Service specs is flexible to allow any prefix for the envelopeas long as the name space URL is correct. But i don't have control on
the server part and thus i would like to know if this issue can betackled from Axis.So the question is whether it is possible to make some configuration inAxis so that i can specify at runtime what prefix should be used for the
envelope (e.g. soap-env instead of soapenv)?Many thanks in advance if i receive any answer to this issue.Regards,   Razvan--Razvan DaniSenior Java DeveloperARoBS Transilvania Software
11 Donath Str , M4 - 28400301 Cluj-Napoca, RomaniaMain:   +40 264 598 204Fax:+40 264 598 426email:  [EMAIL PROTECTED]www.ARoBS.com
-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: 
[EMAIL PROTECTED]

Re: Schema validation

[Martin Gainty]

Good Morning Ken

Who(m)ever is supplying the WSDL to you is responsible for specifying request 
and response for all methods along with specifying 
parameters to those methods.
Who(m)ever is changing the schema needs to re-gen and re-publish the WSDL 

A situation arose where my webservice is now returning a String parameter so I 
have re-published and regen'ed the WSDL to reflect the response string


   


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



- Original Message - 
From: "Ken Tam" <[EMAIL PROTECTED]>
To: 
Sent: Sunday, May 21, 2006 9:18 PM
Subject: Schema validation


> Hi all,
> 
> I am consuming web services made available from my customer. I was given a
> very elaborate WSDL with schemas and I was able to generate the stubs by
> using Axis's WSDL2Java. Everything was working fine until the service was
> changed on the customer's end. This causes the deserialization step to fail
> as the SOAP response does not match the schema. The customer in this case is
> a big company and they don't tend to respond in a timely manner. However,
> the problem persists which I must fix. I am using Axis 1.3 and it doesn't
> seem to validate the SOAP response with the WSDL's schema. How do I
> configure Axis to do so? Currently, I had to spend quite a bit of time to
> track down the mismatches. I figure if the schema is used to validate, it
> should point out the mismatches right off to spare me the time to track them
> down.
> 
> Thanks,
> Ken
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>

Re: Decryption of a complex Axis2 SOAP message fails in WSS4J/XmlSec

[Ruchith Fernando]

Hi Roy,

Thanks a lot for the feedback ... seems like a bug in MTOM with
_large_ base64 text.

I'm trying to reproduce your scenario ... I just checked the security
sample with the similar configuration (added wsa headers as parts to
be signed) and it worked with out a problem _with_ MTOM optimization
(both ways).

I will try with more complex/larger encrypted response.

Thanks,
Ruchith

On 5/22/06, Reshef Roy <[EMAIL PROTECTED]> wrote:


Ruchith, Werner.

Werner was right! I have switched off MTOM
optimization in the services.xml (service->client
message), and it works without problems. I did leave
MTOM optimization on the client Axis2 repository
configuration (client->service), this is also not a
problem (the client->service messages - I have two
operations - are small and have a rather "flat" XML
structure).

If you need any more information, please let me know.

Thanks again,

/ Roy


the --- Reshef Roy <[EMAIL PROTECTED]> wrote:

>
> Ruchith, Werner.
>
> Thanks for your (again, fast :) replies.
> Unfortunately I was already celebrating the weekend
> when I read them :) Monday morning (CET, I'm in
> Holland), I'll turn off the MTOM optimization and
> see
> where it leads. I'll post the results of course.
>
> As for thoughts: what Werner says does make some
> sense
> to me. I do not know the MTOM optimization mechanism
> but the client->service SOAP message (see my
> original
> post, here it's truncated already) is rather small.
> It
> includes actually the identification of the action
> and
> one or two parameters only.
> The service->client message is much larger and
> depends
> on the exact data one is querying for (the entities
> we
> ask for have children entities and the message can
> include these ones as well).
> Again, I am not familiar with the MTOM optimization
> algorithm but if it resembles other encoding and
> compression algorithms I do know, maybe it is more
> "forgiving" for small amounts of data; or for a a
> less
> complex XML strructure?
>
> When Brian complained about it in March he also
> complained about sending a complex XML document.
> Like
> him, my original message also included in the first
> place as a CDATA an embedded XML document (generated
> by a POJO object) but I have removed that and now I
> only work with AXIOM to generate the SOAP message.
>
> Friday at midnight I don't have any brighter ideas,
> more will follow Monday :)
>
> Nice weekend,
>
> / Roy
>
> --- Ruchith Fernando <[EMAIL PROTECTED]>
> wrote:
>
> > Werner, Roy,
> >
> > Yes ... I think can give it a try by turning off
> > MTOM optimization ...
> > however the thing that troubles me is that the
> > client -> service
> > configuration seems to be the same as service
> > ->client config and it
> > (client -> service) worked with MTOM optimization,
> > where is seems to
> > be replacing the binary content properly to be
> > decrypted at the
> > service.
> >
> > Thoughts??
> >
> > Thanks,
> > Ruchith
> >
> > On 5/19/06, Dittmann, Werner
> > <[EMAIL PROTECTED]> wrote:
> > > Roy,
> > >
> > > Axis2 has a feature that optimizes transmission
> of
> > binary
> > > data, AFAIK it convert base64 into real binary
> and
> > send it
> > > over the wire. That save some bandwith. The
> > problem is that
> > > the receiver cannot restore the base64 from the
> > binary in
> > > exactly the same way as it was. Thus decryption
> > and also
> > > signatuire processing have problems.
> > >
> > > You may switch off this optimization an try
> again,
> > > no "optimizeParts" parameter.
> > >
> > > Regards,
> > > Werner
> > >
> > > > -Urspr�ngliche Nachricht-
> > > > Von: Reshef Roy [mailto:[EMAIL PROTECTED]
> > > > Gesendet: Freitag, 19. Mai 2006 17:12
> > > > An: wss4j-dev@ws.apache.org;
> > axis-user@ws.apache.org
> > > > Betreff: Decryption of a complex Axis2 SOAP
> > message fails in
> > > > WSS4J/XmlSec
> > > >
> > > > Hello WSS4J and Axis2 folks,
> > > >
> > > > I come back here on this issue which was
> > discussed by
> > > > Brian and Werner on the WSS4J mailing list in
> > March,
> > > > and has not been resolved. I am facing exactly
> > the
> > > > same problem. I believe it is a WSS4J/XMLSec
> > issue,
> > > > but I send it to both Axis2 and WSSS4J mailing
> > lists.
> > > > The original thread I copied from the mail
> > archive and
> > > > added at the bottom.
> > > >
> > > > My configuration is as follows:
> > > > - My webservice is running on Axis2 1.0
> deployed
> > on
> > > > Tomcat 5.5.16
> > > > - My client application is a standalone Java
> > > > application using an Axis2 1.0 client
> repository
> > > > - jre1.5.0_06
> > > > - relevant jar files in the Axis2 lib
> directory
> > (both
> > > > the server and the client): wss4j-1.5.0,
> > xmlsec-1.3.0,
> > > > xalan-2.7.0 (probably not relevant), various
> > > > javamail-1.4 jars (in case it has to do with
> the
> > MTOM
> > > > attachment??).
> > > > - the security configuration of both the
> > webservice
> > > > and the Axis2 client repository is similar 

Re: [Axis2] specifying username and password

[Kees de Kooter]

This is an Axis 1 solution. There is no such object as Call in Axis2.

So I repeat my question: how can you specify username and password with Axis2??


On 5/3/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

On 5/3/06, Kees de Kooter <[EMAIL PROTECTED]> wrote:
> In Axis 1 I specified username/password like this:
>
> call.setUserName();
> call.setPassword();
>
> What is the equivalent in Axis 2?
>
>
> --
> Cheers,
> Kees de Kooter
> http://www.boplicity.net
>

I have used the following successfully:

call.setProperty(Call.USERNAME_PROPERTY, "user");
call.setProperty(Call.PASSWORD_PROPERTY , "pass");

--
//--
//  Computer Science is no more about computers than astronomy
//  is about telescopes.
//
//  - E. Dijkstra
//--



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

Re: [Axis2] WSDL Generation

[Ajith Ranabahu]

hi.
You are probably having an old version of the plugin. Download the latest from
http://ws.apache.org/axis2/tools/index.html

Ajith

On 5/22/06, Ingo Siebert <[EMAIL PROTECTED]> wrote:

Hi,

the option "Generate WSDL form Java source file" isn't selectable(grey).
Cheers,

Ingo

Kinichiro Inoguchi schrieb:
> Ingo,
>
> With Axis2, how about using "Code Generator Wizard - eclipse Plug-in".
> http://ws.apache.org/axis2/tools/1_0/eclipse/wsdl2java-plugin.html
> You can generate WSDL from java code.
>
> Or, deploying service using RPCMessageReceiver, Axis2 will generates
> WSDL automatically.
> You can see WSDL via url, like
> http://server:port/axis2/services/version?wsdl.
> Please check sample service, "version".
>
> Regards,
> kinichiro
>
> --- A A <[EMAIL PROTECTED]> wrote:
>
>> Easily possible; deploy your java file into axis2 (version< 1)
>> repository
>> with jws extension.
>> call http://hostname/axis/yourjava.jws from your browser and here is
>> the
>> WSDL !
>>
>> On 5/22/06, Ingo Siebert <[EMAIL PROTECTED]> wrote:
>>> Hi,
>>>
>>> is it possible to generate the WSDL file from Java code?
>>> I found only a tool which creates server/client stubs from a WSDL
>> file.
>>> Cheers,
>>>
>>> Ingo

-
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] WSDL Generation

[Ingo Siebert]

Hi,

the option "Generate WSDL form Java source file" isn't selectable(grey).
Cheers,

Ingo

Kinichiro Inoguchi schrieb:

Ingo,

With Axis2, how about using "Code Generator Wizard - eclipse Plug-in".
http://ws.apache.org/axis2/tools/1_0/eclipse/wsdl2java-plugin.html
You can generate WSDL from java code.

Or, deploying service using RPCMessageReceiver, Axis2 will generates
WSDL automatically.
You can see WSDL via url, like
http://server:port/axis2/services/version?wsdl.
Please check sample service, "version".

Regards,
kinichiro

--- A A <[EMAIL PROTECTED]> wrote:


Easily possible; deploy your java file into axis2 (version< 1)
repository
with jws extension.
call http://hostname/axis/yourjava.jws from your browser and here is
the
WSDL !

On 5/22/06, Ingo Siebert <[EMAIL PROTECTED]> wrote:

Hi,

is it possible to generate the WSDL file from Java code?
I found only a tool which creates server/client stubs from a WSDL

file.

Cheers,

Ingo


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

envelope prefix issue

[Razvan Dani]

Hi

I am not sure if this is the right place to address this, but i'd 
appreciate some feedback if possible, because i already made lots of 
queries on the internet about this issue with no success.


My problem is the following:
- i am using WSDL to Java ant task to generate classes against a WSDL.
- when i make a method call on the generated Stub (so notice that i am 
not constructing the envelope by hand neither i use the Call class 
directly), Axis is constructing the envelope as this:
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";


This works just fine for many Web Services, but in my particular case, 
the Web Service implementation on the server side is "hardcoded" to only 
be able to accept
xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/";


I know this is an issue that should be fixed on the server part since 
the Web Service specs is flexible to allow any prefix for the envelope 
as long as the name space URL is correct. But i don't have control on 
the server part and thus i would like to know if this issue can be 
tackled from Axis.


So the question is whether it is possible to make some configuration in 
Axis so that i can specify at runtime what prefix should be used for the 
envelope (e.g. soap-env instead of soapenv)?


Many thanks in advance if i receive any answer to this issue.

Regards,
  Razvan

--
Razvan Dani

Senior Java Developer

ARoBS Transilvania Software

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

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




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

Re: Decryption of a complex Axis2 SOAP message fails in WSS4J/XmlSec

[Reshef Roy]

Ruchith, Werner.

Werner was right! I have switched off MTOM
optimization in the services.xml (service->client
message), and it works without problems. I did leave
MTOM optimization on the client Axis2 repository
configuration (client->service), this is also not a
problem (the client->service messages - I have two
operations - are small and have a rather "flat" XML
structure).

If you need any more information, please let me know.

Thanks again,

/ Roy


the --- Reshef Roy <[EMAIL PROTECTED]> wrote:

> 
> Ruchith, Werner.
> 
> Thanks for your (again, fast :) replies.
> Unfortunately I was already celebrating the weekend
> when I read them :) Monday morning (CET, I'm in
> Holland), I'll turn off the MTOM optimization and
> see
> where it leads. I'll post the results of course.
> 
> As for thoughts: what Werner says does make some
> sense
> to me. I do not know the MTOM optimization mechanism
> but the client->service SOAP message (see my
> original
> post, here it's truncated already) is rather small.
> It
> includes actually the identification of the action
> and
> one or two parameters only.
> The service->client message is much larger and
> depends
> on the exact data one is querying for (the entities
> we
> ask for have children entities and the message can
> include these ones as well).
> Again, I am not familiar with the MTOM optimization
> algorithm but if it resembles other encoding and
> compression algorithms I do know, maybe it is more
> "forgiving" for small amounts of data; or for a a
> less
> complex XML strructure?
> 
> When Brian complained about it in March he also
> complained about sending a complex XML document.
> Like
> him, my original message also included in the first
> place as a CDATA an embedded XML document (generated
> by a POJO object) but I have removed that and now I
> only work with AXIOM to generate the SOAP message.
> 
> Friday at midnight I don't have any brighter ideas,
> more will follow Monday :)
> 
> Nice weekend,
> 
> / Roy
> 
> --- Ruchith Fernando <[EMAIL PROTECTED]>
> wrote:
> 
> > Werner, Roy,
> > 
> > Yes ... I think can give it a try by turning off
> > MTOM optimization ...
> > however the thing that troubles me is that the
> > client -> service
> > configuration seems to be the same as service
> > ->client config and it
> > (client -> service) worked with MTOM optimization,
> > where is seems to
> > be replacing the binary content properly to be
> > decrypted at the
> > service.
> > 
> > Thoughts??
> > 
> > Thanks,
> > Ruchith
> > 
> > On 5/19/06, Dittmann, Werner
> > <[EMAIL PROTECTED]> wrote:
> > > Roy,
> > >
> > > Axis2 has a feature that optimizes transmission
> of
> > binary
> > > data, AFAIK it convert base64 into real binary
> and
> > send it
> > > over the wire. That save some bandwith. The
> > problem is that
> > > the receiver cannot restore the base64 from the
> > binary in
> > > exactly the same way as it was. Thus decryption
> > and also
> > > signatuire processing have problems.
> > >
> > > You may switch off this optimization an try
> again,
> > > no "optimizeParts" parameter.
> > >
> > > Regards,
> > > Werner
> > >
> > > > -Urspr�ngliche Nachricht-
> > > > Von: Reshef Roy [mailto:[EMAIL PROTECTED]
> > > > Gesendet: Freitag, 19. Mai 2006 17:12
> > > > An: wss4j-dev@ws.apache.org;
> > axis-user@ws.apache.org
> > > > Betreff: Decryption of a complex Axis2 SOAP
> > message fails in
> > > > WSS4J/XmlSec
> > > >
> > > > Hello WSS4J and Axis2 folks,
> > > >
> > > > I come back here on this issue which was
> > discussed by
> > > > Brian and Werner on the WSS4J mailing list in
> > March,
> > > > and has not been resolved. I am facing exactly
> > the
> > > > same problem. I believe it is a WSS4J/XMLSec
> > issue,
> > > > but I send it to both Axis2 and WSSS4J mailing
> > lists.
> > > > The original thread I copied from the mail
> > archive and
> > > > added at the bottom.
> > > >
> > > > My configuration is as follows:
> > > > - My webservice is running on Axis2 1.0
> deployed
> > on
> > > > Tomcat 5.5.16
> > > > - My client application is a standalone Java
> > > > application using an Axis2 1.0 client
> repository
> > > > - jre1.5.0_06
> > > > - relevant jar files in the Axis2 lib
> directory
> > (both
> > > > the server and the client): wss4j-1.5.0,
> > xmlsec-1.3.0,
> > > > xalan-2.7.0 (probably not relevant), various
> > > > javamail-1.4 jars (in case it has to do with
> the
> > MTOM
> > > > attachment??).
> > > > - the security configuration of both the
> > webservice
> > > > and the Axis2 client repository is similar to
> > the one
> > > > in the security sample of Axis2 1.0.
> > > >
> > > > I send a simple SOAP message from the client
> to
> > the
> > > > service, and get a complex, eventually a very
> > complex,
> > > > SOAP message containing the data back.
> > > >
> > > > The client->server message works fine, both
> when
> > I
> > > > configure it to be signed and encrypted and
> when
> > I
> > > > don't.
> > > > The server->client 

Sax exception:Invalid element in...

[Roy]

Hello,I use axis 1.3 to call a service that is implemented in an uknown language (probably .NET but not Java). I have generated the classes with the wsdl2Java tool from the service's  WSDL and i called normally the service with a static stub. In the SOAP monitor i can see the respone with the expected data but i get this SAX exception:org.xml.sax.SAXException:Invalid element in com.advertsoft.APP_Response.USERS - DataValuesat org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258)I have read previous threads and i noticed that probably is a problem in the first character of DataValues(it is capital?) tag in the response.Can anyone please give a way of how to solve this and deserialize the respnse normally?Thanks in advance,Roy
		 
Χρησιμοποιείτε Yahoo! 
Βαρεθήκατε τα ενοχλητικά μηνύ ματα (spam); Το Yahoo! Mail διαθέτει την καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων  
http://login.yahoo.com/config/mail?.intl=gr 

RE: [Axis2] Vanishing MTOM attachments

[Timo Ahokas]

Hi Thilina,

The fix you did to OMTextImpl seemed to fix the problem I'm seeing, so
thanks
very much for that. :) The only problem is that the fix was committed to
AXIS2-753 (Setting SOAP Version URI to type 1.2 creates invalid Content-Type
that fails during parsing) which seems to be a different client side
problem,
instead of the other JIRA I raised (AXIS2-752, Problem handling multiple
binary
MTOM attachments). So I think 752 has been fixed, but 753 is still an issue.

Kind regards,
Timo

-Original Message-
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
Sent: 20 May 2006 03:57
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: Re: [Axis2] Vanishing MTOM attachments


Can you post your client code for the creation of the OMElements...  And the
XML payload of the root MIME part... Your earlier posted code and the
message snaphots does not contain any valuable thing...

I think you are talking about the XOP:Include element as the extra added
element...

~Thilina


On 5/19/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
Timo,

Please create a JIRA issue with some code/wsdl whatever is needed to
recreate the problem.

thanks,
dims

On 5/19/06, Timo Ahokas <[EMAIL PROTECTED]> wrote:
> Ok, I think I know what's happening...
>
> --[Example 1]
> Client sends:
> 
>   XML
>   attachment 1
>   attachment 2
>   attachment 3
> 
>
> Service receives:
> 
>   XML
>   attachment 1
> 
>
> --[Example 2]
> Client sends:
> 
>   XML
>   
> attachment 1
> attachment 2
> attachment 3
>   
> 
>
> Service receives:
> 
>   XML
>   
> attachment 1
>   
>   attachment 2
> 
>
> --[Example 3]
> Client sends:
> 
>   XML
>   
> 
> attachment 1
> attachment 2
> attachment 3
> 
>   
> 
>
> Service receives:
> 
>   XML
>   
> 
> attachment 1
> 
> attachment 2
>   
>   attachment 3
> 
>
> So it seems that the code that is constructing the OMElement for the
> service has a bug and it adding the attachments back incorrectly -
> it seems to be adding any extra ones (2,3,...) to the parent
> element, instead of the current one.
>
> Anyone familiar with the code - where would this be handled?
>
> Kind regards,
> Timo
>
> -Original Message-
> From: Timo Ahokas [mailto: [EMAIL PROTECTED]
> Sent: 19 May 2006 13:39
> To: axis-user@ws.apache.org
> Subject: RE: [Axis2] Vanishing MTOM attachments
>
>
> Hi Thilina,
>
> I tried what you suggested by doing this on the server side:
>
> public OMElement service(OMElement element) {
>   element.build();
>   element.buildNext ();
>   element.detach();
>
>   OMNode firstOMChild = element.getFirstOMChild();
>   OMNode nextOMSibling = firstOMChild.getNextOMSibling();
>   if(nextOMSibling != null) {
> OMNode nextOMSibling2 = nextOMSibling.getNextOMSibling();
> if(nextOMSibling2 != null) {
>   OMNode nextOMSibling3 = nextOMSibling2.getNextOMSibling();
> }
>   }
> ...
>
> firstOMChild is the XML payload
> nextOMSibling is the first binary attachment
> nextOMSibling2 should be the second binary attachment (but is null)
> nextOMSibling3 should be the third binary attachment (-||-)
>
> I'm guessing that something is going wrong when the over-the-wire
> data is being demarshalled and before the OMElement is even handed
> down to my service (which would explain why I see the data
> coming in into Axis, but not when it reaches my service). But I
> could obviously misinterpret what the debugger is displaying.
>
> >>And if the mime processing is deferred, why would the element contain
> >>the first attachment (and not just the soap/xml part),
> >
> >Can't get your point clearly...
>
> I think my point was that if all binary mime processing is deferred, then
> why does one out of the three attachments come through fine? Unless
> the first one is pre-loaded and any latter ones are deferred...
>
> Has anyone successfully received multiple binary attachments with
> Axis 1.0? :)
>
> And Thilina - good luck with the exams... :)
>
> Cheers
> Timo
>
> -Original Message-
> From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
> Sent: 19 May 2006 12:50
> To: axis-user@ws.apache.org
> Subject: Re: [Axis2] Vanishing MTOM attachments
>
>
> Hi,
> See my comments below
>
>
> Thanks a lot for the response.
>
> :) WC..
>
>
>
>public OMElement mediaTransformation(OMElement element) {
>try {
>element.build ();
>element.detach();
>Iterator serviceIterator = element.getChildElements();
>OMElement servicePayload = (OMElement)
> serviceIterator.next();
>OMElement xmlDoc = (OMElement)
> servicePayload.getChildElements().next();
>
>// Handle attachments, if there are any.
>DataHandler attachmentDH;
>
>while(serviceIterator.hasNext()) {
>OMElement attachmentElement = (OMElement)
> serviceIterator.next

[AXIS 2] [vers 1] : does php nuSOAP understand AXIS 2 ver 1 ?

[A A]

I have developped a web service using AXIS 2 version1, everythings work fine with a "jsp client" and "SOAPUI 1.5" but when i call the service with php nuSOAP i have this SOAP response:Array
([faultcode] => soapenv:Client[faultstring] => null; nested exception is: 	java.lang.NullPointerException[detail] => Array([Exception] => org.apache.axis2.AxisFault
: null; nested exception is: 	java.lang.NullPointerException	at org.apache.axis2.AxisFault.makeFault(AxisFault.java:318)	at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java
:136)	at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37)	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest
(HTTPTransportUtils.java:284)	at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:136)	at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)	at javax.servlet.http.HttpServlet.service
(HttpServlet.java:802)	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)	at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)	at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:520)	at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
	at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)	at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)	at org.apache.catalina.core.StandardHostValve.invoke
(StandardHostValve.java:137)	at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)	at org.apache.catalina.core.StandardValveContext.invokeNext
(StandardValveContext.java:102)	at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)	at org.apache.catalina.core.StandardValveContext.invokeNext
(StandardValveContext.java:104)	at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)	at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)	at org.apache.coyote.tomcat5.CoyoteAdapter.service
(CoyoteAdapter.java:160)	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
	at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)	at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)	at java.lang.Thread.run(Thread.java:534)Caused by: 
java.lang.NullPointerException	at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:87)	... 30 more))

Re: [Axis2] WSDL Generation

[Kinichiro Inoguchi]

Ingo,

With Axis2, how about using "Code Generator Wizard - eclipse Plug-in".
http://ws.apache.org/axis2/tools/1_0/eclipse/wsdl2java-plugin.html
You can generate WSDL from java code.

Or, deploying service using RPCMessageReceiver, Axis2 will generates
WSDL automatically.
You can see WSDL via url, like
http://server:port/axis2/services/version?wsdl.
Please check sample service, "version".

Regards,
kinichiro

--- A A <[EMAIL PROTECTED]> wrote:

> Easily possible; deploy your java file into axis2 (version< 1)
> repository
> with jws extension.
> call http://hostname/axis/yourjava.jws from your browser and here is
> the
> WSDL !
> 
> On 5/22/06, Ingo Siebert <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > is it possible to generate the WSDL file from Java code?
> > I found only a tool which creates server/client stubs from a WSDL
> file.
> > Cheers,
> >
> > Ingo
> >
> >
> >
> -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

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

Inconsistent Array Elements

[Stephan Fischli]

Hi

I have deployed a Stock Quoter Service with Axis 1.3 whose operation "getSymbols" returns an array of strings. According to the generated
WSDL
the array elements should be named "item". But in the SOAP response the array elements have the name "getSymbolsReturn".
Does anybody have an explanation of this obvious contradiction?

Thanks, Stephan

View this message in context: Inconsistent Array Elements
Sent from the Axis - User forum at Nabble.com.

Re: [Axis2] WSDL Generation

[A A]

Easily possible; deploy your java file into axis2 (version< 1) repositorywith jws extension.call http://hostname/axis/yourjava.jws from your browser and here is the WSDL !
On 5/22/06, Ingo Siebert <[EMAIL PROTECTED]> wrote:
Hi,is it possible to generate the WSDL file from Java code?I found only a tool which creates server/client stubs from a WSDL file.Cheers,Ingo-
To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

[Axis2] WSDL Generation

[Ingo Siebert]

Hi,

is it possible to generate the WSDL file from Java code?
I found only a tool which creates server/client stubs from a WSDL file.
Cheers,

Ingo


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