Re: |AXIS2] [AXIS2C] c-stubs: memset in axis2_TYPE_create missing

2007-06-25 Thread Dr. Florian Steinborn

Hi,

I checked out the source and looked into it and think the problem could be  
solved by feeding the source


modules/codegen/src/org/apache/axis2/wsdl/template/c/ServiceSkeleton.xsl

with the desired line. Unfortunately I do not understand the make  
hierarchy of Axis2 - not yet :-) Therefore I could not test my suggestion.


Greetings,
Flori

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



Re: [AXIS2C] throwing an exception from the server to the Java-client

2007-06-25 Thread Dr. Florian Steinborn

Hello experts,

unfortunately Marc replied to my mail with a different contect (at least  
my mailer shows that) - people could tend to thinking my subject is  
answered. Just wanted to say, that it is not. Still do not know how to  
generate the fault from inside the server stubs...


Thanks,
Flori

On Sat, 23 Jun 2007 01:00:12 +0200, Dr. Florian Steinborn [EMAIL PROTECTED]  
wrote:



Hi folks,

someone has a code piece that shows how to generate an exception in the  
AXIS2C server?


I can see that code was generated , the files are named  
axis2_functionFault.[ch.] but I don't know how to use the functions in  
the modules from inside axis2_svc_skel_service_invoke() function,  
where the operation is called that has to issue the exception...


Thanks,
Flori

-
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: [AXIS2C] throwing an exception from the server to the Java-client

2007-06-25 Thread mark . nuessler
hello flori,

sry, when i start to write the mail, i took yours to reply but
started a new thread - because i was just to lazy to search
for the mailinglist-email in my contactlist - sorry about this.

to your prob, i don't know if i understand it correctly.

do you have the wsdl file for me where you have defined the fault and
from which you have generated the file axis2_functionFault.[ch.] ?
because in my own examples i havend used a fault till now and
i don't know what was generated in this file.

i tried to generate code from /test/resources/wsdl/FaultMapping.wsdl,
but here 2 other problem came up
[1. encoding not supportet]
[2. more than one part for message divRequest]

if you want to raise an Exception like in java, when you write :

throw new java.lang.UnsupportedOperationException(Please implement  +
this.getClass().getName() + #myOperation);

i think you can do it this way in c :

axiom_node_t *ret_node = NULL;
axiom_soap_envelope_t *soap_envelope = NULL;
axiom_soap_body_t *soap_body = NULL;
axiom_soap_fault_t *soap_fault = NULL;

soap_envelope = axiom_soap_envelope_create_default_soap_envelope(
env, AXIOM_SOAP11);
soap_body = axiom_soap_body_create_with_parent(env, soap_envelope);
soap_fault = axiom_soap_fault_create_default_fault(
env, soap_body, fault-code, fault-reason,
AXIOM_SOAP11);
ret_node = axiom_soap_fault_get_base_node(soap_fault, env);
return ret_node;

but i think i misunderstood your prob.

mfg derMark

P.S. sry this time i have to use a webmailer ;-)


Dr. Florian Steinborn schrieb:
 Hello experts,

 unfortunately Marc replied to my mail with a different contect (at least
 my mailer shows that) - people could tend to thinking my subject is
 answered. Just wanted to say, that it is not. Still do not know how to
 generate the fault from inside the server stubs...

 Thanks,
 Flori

 On Sat, 23 Jun 2007 01:00:12 +0200, Dr. Florian Steinborn
 [EMAIL PROTECTED] wrote:

 Hi folks,

 someone has a code piece that shows how to generate an exception in
 the AXIS2C server?

 I can see that code was generated , the files are named
 axis2_functionFault.[ch.] but I don't know how to use the functions
 in the modules from inside axis2_svc_skel_service_invoke() function,
 where the operation is called that has to issue the exception...

 Thanks,
 Flori

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



 --No virus found in this incoming message.
 Checked by AVG Free Edition.Version: 7.5.472 / Virus Database:
 269.9.6/865 - Release Date: 24.06.2007 08:33




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



Re: [AXIS2C] throwing an exception from the server to the Java-client

2007-06-25 Thread Dr. Florian Steinborn

Hi Mark,

no problem at all.

Attached you find a Fehler.java, that I used to generate the  
Fehler.wsdl that is attached as well. When you generate c-server stubs  
you will find the axis2_raiseErrorFault.[ch] files. In my understanding  
the error should be raised in axis2_skel_Fehler_raiseError() function -  
that is the place where the business logic registers the error and wants  
to raise it. This function usually returns an int (as it is defined),  
but how has it have to look like, when we do not return the int but the  
fault? The return type of the function is axis2_raiseErrorResponse_t* -  
sure, you can return a NULL, but what about the raiseErrorFault?


Thanks for your patience,
Flori


Fehler.java
Description: Binary data


Fehler.wsdl
Description: Binary data
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Recompile Axis2/C on cygwin

2007-06-25 Thread Wang, Hailong (NIH/CIT) [C]
Hi ,

 

Is there anyone who is able to compile Axis2/C on cygwin? I tried, but I
can not. Can someone help me on this? Thanks in advance.

 

 

Hailong Wang

National Database for Autism Research(NDAR)

NIH/CIT/DECA (MOM CONTRACTOR)

9000 Rockville Pike, Bld 12A/Room 2027

Bethesda, MD 20892

Phone:  301-402-3045

Fax:   301-480-0028

Email:   [EMAIL PROTECTED]

URL:   http://ndar.nih.gov

 



RE: Recompile Axis2/C on cygwin

2007-06-25 Thread Wang, Hailong (NIH/CIT) [C]
Dear Dinesh,

Thanks very much for you quick reply. I created a issue(AXIS2C-627) for
this new feature. I appreciate your help to solve this problem. But
could you shorten the time, because I run out of time. Can make it work
within 3 days? Thanks again.


Hailong

-Original Message-
From: Dinesh Premalal [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 25, 2007 10:35 AM
To: axis-c-user@ws.apache.org
Subject: Re: Recompile Axis2/C on cygwin

Hi Hailong,
Wang, Hailong (NIH/CIT) [C] [EMAIL PROTECTED] writes:

 Hi ,

  

 Is there anyone who is able to compile Axis2/C on cygwin? I tried, but
I can
 not. Can someone help me on this? Thanks in advance.
AFAIK, we didn't try to install in Cygwin. There maybe users who tried
to install on Cygwin. BTW I think its worth to shape our build system
install on Cygwin. Give us sometime (3-4 days :))we will get back to
you.

If you could raise a jira issue with whatever information (errors,
logs) you have that will be helpful.

thanks,
Dinesh
-- 
Dinesh Premalal
http://feeds.feedburner.com/Dinesh
GPG ID : A255955C
GPG Key Finger Print : C481 E5D4 C27E DC34 9257  0229 4F44 266E A255
955C

-
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: Does Axis2/C client has the ability to set the session management?

2007-06-25 Thread Dumindu Pallewela

Hi Wang,

My understanding is that it does not, but facilitates such 
implementation. Please refer to the following thread [1].


Regards,
Dumindu.

[1] http://marc.info/?l=axis-c-userm=118224624421829w=2

Wang, Hailong (NIH/CIT) [C] wrote:

Hi,


I have a web service written in Java and use the soapsession management. 
Right now I want to create a client using Axis2/C. Is Axis2/C client 
able to mange session? Thanks in advance.


 

 


**Hailong Wang**

National Database for Autism Research(NDAR)

NIH/CIT/DECA (MOM CONTRACTOR)

9000 Rockville Pike, Bld 12A/Room 2027

Bethesda, MD 20892

Phone:  301-402-3045

Fax:   301-480-0028

Email:   [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]

URL:   http://ndar.nih.gov

 




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



Re: Does Axis2/C client has the ability to set the session management?

2007-06-25 Thread Samisa Abeysinghe


I have a web service written in Java and use the soapsession 
management. Right now I want to create a client using Axis2/C. Is 
Axis2/C client able to mange session? 

Axis2/C client cannot manage sessions with a Java service :(

Samisa...

--
Samisa Abeysinghe : http://www.wso2.org/ (WSO2 Oxygen Tank - Web Services 
Developers' Portal)


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



RE: [Axis2] Axis2 client message different to Axis1 client messag e

2007-06-25 Thread Alick Buckley
Hi,
 
If the elementFormDefault is set to unqualified then the SOAP message does
not have the namespace prefixes.
 
But the getNumber element has a namespace prefix, but there is no default
namespace ?
 
schema elementFormDefault=unqualified targetNamespace=
http://soap.service.acme.com http://soap.service.acme.com  xmlns=
http://www.w3.org/2001/XMLSchema http://www.w3.org/2001/XMLSchema 
 
===
 
?xml version=1.0 encoding=utf-8?
soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/
http://schemas.xmlsoap.org/soap/envelope/ 
soapenv:Body
ns1:getNumber xmlns:ns1=  http://soap.service.acme.com
http://soap.service.acme.com;
param1
a_int
item2/item
item3/item
item4/item
/a_int
n_double22.5/n_double
n_float23.4/n_float
n_int123/n_int
n_long3456/n_long
o_bigdecimal567.67/o_bigdecimal
o_biginteger98765/o_biginteger
o_double345.67/o_double
o_int7585/o_int
/param1
/ns1:getNumber
/soapenv:Body
/soapenv:Envelope

===

-Original Message-
From: Alick Buckley [mailto:[EMAIL PROTECTED]
Sent: Monday, 25 June 2007 3:50 PM
To: axis-user@ws.apache.org
Subject: [Axis2] Axis2 client message different to Axis1 client message




Hi, 

I am using the same test WSDL for an Axis 1.4 generated client and an Axis2
1.2 generated client. 

The Axis2 1.2 is qualifying the elements with a namespace prefix ? 


= 

Axis2 1.2 

?xml version=1.0 encoding=utf-8? 
soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/
http://schemas.xmlsoap.org/soap/envelope/  
soapenv:Body 
ns1:getNumber xmlns:ns1= http://soap.service.acme.com
http://soap.service.acme.com  
ns1:param1 
ns1:a_int 
ns1:item2/ns1:item 
ns1:item3/ns1:item 
ns1:item4/ns1:item 
/ns1:a_int 
ns1:n_double22.5/ns1:n_double 
ns1:n_float23.4/ns1:n_float 
ns1:n_int123/ns1:n_int 
ns1:n_long3456/ns1:n_long 
ns1:o_bigdecimal567.67/ns1:o_bigdecimal 
ns1:o_biginteger98765/ns1:o_biginteger 
ns1:o_double345.67/ns1:o_double 
ns1:o_int7585/ns1:o_int 
/ns1:param1 
/ns1:getNumber 
/soapenv:Body 
/soapenv:Envelope 


= 

Axis 1.4 

?xml version=1.0 encoding=utf-8? 
soapenv:Envelope 
xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/
http://schemas.xmlsoap.org/soap/envelope/  
xmlns:xsd= http://www.w3.org/2001/XMLSchema
http://www.w3.org/2001/XMLSchema  xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance
http://www.w3.org/2001/XMLSchema-instance  
soapenv:Body 
getNumber xmlns= http://soap.service.acme.com
http://soap.service.acme.com  
param1 
a_int 
item123/item 
item456/item 
/a_int 
n_double20.1/n_double 
n_float21.11/n_float 
n_int22/n_int 
n_long22345678/n_long 
o_bigdecimal223.546/o_bigdecimal 
o_biginteger22385943/o_biginteger 
o_double2435.456/o_double 
o_int23245/o_int 
/param1 
/getNumber 
/soapenv:Body 
/soapenv:Envelope 


= 

EveryNumberServiceServiceStub stub = new
EveryNumberServiceServiceStub () ; 

EveryNumberServiceServiceStub.EveryNumber param1 = new
EveryNumberServiceServiceStub.EveryNumber () 

int[] intArray = new int[]{ 2, 3, 4 } ; 

EveryNumberServiceServiceStub.ArrayOf_xsd_int valueArray = new
EveryNumberServiceServiceStub.ArrayOf_xsd_int () ;

valueArray.setItem ( intArray ) ; 

param1.setA_int ( valueArray ) ; 

param1.setN_double ( 22.5 ) ; 

param1.setN_float ( 23.4f ) ; 

param1.setN_int ( 123 ) ; 

param1.setN_long ( 3456 ) ; 

param1.setO_bigdecimal ( new BigDecimal ( 567.67 ) ) ; 

param1.setO_biginteger ( new BigInteger ( 98765 ) ) ; 

param1.setO_double ( 345.67 ) ; 

param1.setO_int ( 7585 ) ; 

EveryNumberServiceServiceStub.GetNumber request = new
EveryNumberServiceServiceStub.GetNumber () ; 

request.setParam1 ( param1 ) ; 

EveryNumberServiceServiceStub.GetNumberResponse response =
stub.getNumber ( request ) ; 


RE: [Axis2] Axis2 client message different to Axis1 client messag e

2007-06-25 Thread Alick Buckley
Hi,
 
If I use the original test WSDL with the .NET WebService Studio Tool, the
SOAP message is the same as Axis 1.4 ?
 
Microsoft .NET WebService Studio Tool
 
?xml version=1.0 encoding=utf-8?
soap:Envelope xmlns:soap= http://schemas.xmlsoap.org/soap/envelope/
http://schemas.xmlsoap.org/soap/envelope/ 
xmlns:xsd= http://www.w3.org/2001/XMLSchema
http://www.w3.org/2001/XMLSchema  xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance
http://www.w3.org/2001/XMLSchema-instance 
soap:Body
getNumber xmlns= http://soap.service.acme.com
http://soap.service.acme.com 
param1
a_int
item23/item
/a_int
n_double23.45/n_double
n_float56.78/n_float
n_int876/n_int
n_long284849/n_long
o_biginteger48484/o_biginteger
/param1
/getNumber
/soap:Body
/soap:Envelope

Axis 1.4 

?xml version=1.0 encoding=utf-8? 
soapenv:Envelope 
xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/
http://schemas.xmlsoap.org/soap/envelope/  
xmlns:xsd= http://www.w3.org/2001/XMLSchema
http://www.w3.org/2001/XMLSchema  xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance
http://www.w3.org/2001/XMLSchema-instance  
soapenv:Body 
getNumber xmlns= http://soap.service.acme.com
http://soap.service.acme.com/  
param1 
a_int 
item123/item 
item456/item 
/a_int 
n_double20.1/n_double 
n_float21.11/n_float 
n_int22/n_int 
n_long22345678/n_long 
o_bigdecimal223.546/o_bigdecimal 
o_biginteger22385943/o_biginteger 
o_double2435.456/o_double 
o_int23245/o_int 
/param1 
/getNumber 
/soapenv:Body 
/soapenv:Envelope 

=

-Original Message-
From: Alick Buckley [mailto:[EMAIL PROTECTED]
Sent: Monday, 25 June 2007 4:15 PM
To: axis-user@ws.apache.org
Subject: RE: [Axis2] Axis2 client message different to Axis1 client messag e


Hi,
 
If the elementFormDefault is set to unqualified then the SOAP message does
not have the namespace prefixes.
 
But the getNumber element has a namespace prefix, but there is no default
namespace ?
 
schema elementFormDefault=unqualified targetNamespace=
http://soap.service.acme.com http://soap.service.acme.com  xmlns=
http://www.w3.org/2001/XMLSchema http://www.w3.org/2001/XMLSchema 
 
===
 
?xml version=1.0 encoding=utf-8?
soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/
http://schemas.xmlsoap.org/soap/envelope/ 
soapenv:Body
ns1:getNumber xmlns:ns1=  http://soap.service.acme.com
http://soap.service.acme.com;
param1
a_int
item2/item
item3/item
item4/item
/a_int
n_double22.5/n_double
n_float23.4/n_float
n_int123/n_int
n_long3456/n_long
o_bigdecimal567.67/o_bigdecimal
o_biginteger98765/o_biginteger
o_double345.67/o_double
o_int7585/o_int
/param1
/ns1:getNumber
/soapenv:Body
/soapenv:Envelope

===

-Original Message-
From: Alick Buckley [mailto:[EMAIL PROTECTED]
Sent: Monday, 25 June 2007 3:50 PM
To: axis-user@ws.apache.org
Subject: [Axis2] Axis2 client message different to Axis1 client message




Hi, 

I am using the same test WSDL for an Axis 1.4 generated client and an Axis2
1.2 generated client. 

The Axis2 1.2 is qualifying the elements with a namespace prefix ? 


= 

Axis2 1.2 

?xml version=1.0 encoding=utf-8? 
soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/
http://schemas.xmlsoap.org/soap/envelope/  
soapenv:Body 
ns1:getNumber xmlns:ns1= http://soap.service.acme.com
http://soap.service.acme.com  
ns1:param1 
ns1:a_int 
ns1:item2/ns1:item 
ns1:item3/ns1:item 
ns1:item4/ns1:item 
/ns1:a_int 
ns1:n_double22.5/ns1:n_double 
ns1:n_float23.4/ns1:n_float 
ns1:n_int123/ns1:n_int 
ns1:n_long3456/ns1:n_long 
ns1:o_bigdecimal567.67/ns1:o_bigdecimal 
ns1:o_biginteger98765/ns1:o_biginteger 
ns1:o_double345.67/ns1:o_double 
ns1:o_int7585/ns1:o_int 
/ns1:param1 
/ns1:getNumber 
/soapenv:Body 
/soapenv:Envelope 


Re: [Axis2] Service Settings, DB connection

2007-06-25 Thread Ognjen Blagojevic

Hi Oliver,


1. Where should I store the db-connection parameters. Now I have
integrated it to service.xml! It works fine, but if I make the
deployment of the services I generate an .aar file which includes
also the service.xml. This implicates, that by updating the service on
a server, the service.xml is also overwritten, it means the
customer-settings (like db connection parameters, etc.) are lost and
have to set again.
Is there a better place to store such settings?


Do you really want to allow your customers to change DB connection 
parameters? This doesn't look like a very good decision.


Anyway, if they can change them, then you must put them somewhere 
outside the database, i.e. in file system. Since you overwrite .aar file 
each time you deploy your service you could use some other place in the 
file system.




2. I connect to db in the startUp method of an additional service-class
implementing the ServiceLifeCycle interface and stores it to a
service-parameter (the disconnecting is made in the shutDown method).
So from the serveral service-methods I can acces the db-connection
object over the servicecontext. It runs well.
Now, my question is, was happens, if there comes several requests to
services wich used the db-connection from different clients at the same
time? I think there is only one db-connection object instance, so there
can occur access violations, isn't it?


Yes. You could use locking to prevent this. Even better, you could add 
conncetion pooling to your application, plus, open the connection before 
writing to database, and close it afterwards. Connection is a valuable 
resource, and you shouldn't keep it open all the time.


Regards,
Ognjen

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



RE: Axis2 1.1.1 WSDL2JAVA - Not generating java classes for wsdl:portType

2007-06-25 Thread Desmond Whewell (CV/ETL)
The multiple-run and merge option is exactly what I did. If you study
the generated code, you will see that is it fairly regular and it is
straightforward to merge the results of multiple runs into one
implementation. 

Despite this, it *is* error-prone and extremely tedious. Thankfully, my
wsdl is pretty stable, but if you were going around this loop several
times, it could send you mad! On the other hand, you may find, as I did,
that the generated code is only sufficient to get you started; I had to
add several bits of code to manage header faults. Therefore, you will
probably end up with your own receiver code that is always used in place
of the boiler-plate.

YMMV

Cheers, Des

-Original Message-
From: Ajith Ranabahu [mailto:[EMAIL PROTECTED] 
Sent: 24 June 2007 20:10
To: axis-user@ws.apache.org
Subject: Re: Axis2 1.1.1 WSDL2JAVA - Not generating java classes for
wsdl:portType

Hi,
From a glance at the WSDL I feel that you can use the code generator to
generate multiple stubs for the different porttypes and still use it. I
believe even if the codegen had the ability to handle multiple ports, it
would have done the same thing, the difference in this case is that you
have to invoke the codegen multiple times to generate the code for all
ports.

Ajith

On 6/23/07, Alexey Zavizionov [EMAIL PROTECTED]
wrote:
 Hi,
 I really haven't time in my wsrp implementation and this impossibility

 for multiple porttypes blocked my project. This leads me to seek other

 soap implementations... :(

 Will be fix it soon?
 When will be the next release?

 Regards,
 Alexey

 On 6/22/07, Ajith Ranabahu [EMAIL PROTECTED] wrote:
  Hi,
  You can use -pn, -sn options to specify the different port/service 
  combinations. As for the point raised by Kim, yes it is a problem 
  since now each port will yield a different service. Really this 
  becomes a issue when you have multiple bindings and multiple 
  porttypes.
 
  Ajith
 
  On 6/22/07, Alexey Zavizionov [EMAIL PROTECTED]
wrote:
   How can I do generate code for each port with separate WSDL2Java 
   calls if I can't modify wsdl file, because it was given by wsrp 
   specification 
   http://www.oasis-open.org/committees/wsrp/specifications/version1/
   wsrp_service.wsdl
?
  
   Regards,
   Alexey
  
  
   On 6/22/07, Sagnwoo Kim [EMAIL PROTECTED] wrote:
Ajith suggested multiple wsdl files for the solution of multiple

ports. I have a question for that. When you want to create 
client from the wsdl files. with WSDL2Java and if you have
multiple wsdl files for one service.
Then you have to create multiple clients as well for every 
ports? Even though they are all under the same service?
   
Thanks
Sangwoo Kim
   
   
On 6/22/07, Bo Xie [EMAIL PROTECTED] wrote:
 Hi Ajith,

   Thanks for the comments. Look forward to your explanation. 
 Like to know
the difference between the workaround and the expected.

 Thanks,
 -Bo


 On 6/13/07, Ajith Ranabahu [EMAIL PROTECTED] wrote:
  Hi,
  We will definitely look at the possibility of supporting 
  this during the hackathon. I will perhaps explain in a 
  separate mail what is the thinking behind starting from the 
  port but it seems that we need to rethink this when it comes
to skeletons.
 
  What I can suggest as a workaround is to generate code for 
  each port with separate WSDL2Java calls (which will yield
multiple skeletons).
  You can make this easy if you use the ant task
 
  Ajith
 
  On 6/13/07, Bo Xie [EMAIL PROTECTED] wrote:
   Hi Amila and all,
  
 In case this is not working yet, can you suggest any 
   alternative? I
have a
   few services that shared a lot of common data among them. 
   I have to
move all
   the methods in all services into one mega service and 
   change method
name if
   necessary to avoid conflicts. Mixing methods of different 
   purpose into
one
   service looks messy.
  
  Appreciate any advice.
  
   -Bo
  
  
   On 5/24/07, Jess Fisher  [EMAIL PROTECTED] wrote:
I still cannot get all the portTypes generated even with
Axis 1.2.
Any
   plans on fixing this ?
   
   
Bo Xie  [EMAIL PROTECTED] wrote:
Sorry to bother you again. Just want to know if this is 
a bug or I
did not
   set the parameter correctly. Any advice on how to make
this work.
   
Thanks,
-Bo
   
   
On 5/20/07, Bo Xie  [EMAIL PROTECTED] wrote:
 I attached the wsdls from the original email.

 Thanks,
 -Bo



 On 5/20/07, Amila Suriarachchi  
 [EMAIL PROTECTED] 
wrote:
  Can you send your wsdl? do you have ports for each
bining?
  Actually code is generated per port.
 
 
 
  On 5/20/07, Bo 

Re: text/xml to application/xml trouble

2007-06-25 Thread Thilina Gunarathne

Hi,
Earlier Axis2 was treating messages with text/xml as the content-type
without a SOAPAction http-header as POX messages. Reason was SOAP 1.1,
which defines content-type of the messages as text/xml and it
mandates SOAPAction header.

Later with the introduction of WSDL 2.0 support (specifically the
WSDL2 HTTPBinding support) Axis2 is using the application/xml to treat
POX messages.. But we kept the text/xml without SOAPAction identified
as POX mechanism for the sake of backward compatibility.

Please check whether you have the SOAPAction header in your messages...


AxisConfigutator is overriding some of the content-type to builder mappings
to specific builders (application/xml being one of them), so I'm right back
to a Builder that doesn't work.

It was not supposed to override the user configured builders... Are
you using Axis2 1.2..

Thanks,
Thilina



Any suggestions?
--
View this message in context: 
http://www.nabble.com/text-xml-to-application-xml-trouble-tf3974013.html#a11280629
Sent from the Axis - User mailing list archive at Nabble.com.


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





--
Thilina Gunarathne  -  http://www.wso2.com - http://thilinag.blogspot.com

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



Beginner ask a simple question?

2007-06-25 Thread GAMBELLI Raffaele
Hi all, this is my first post.

I'm trying Axis2 inside a Tomcat Embedded application.
I've used also both plugins client side and server side.

My very simple question is:
On CLIENT SIDE, to make running a simple client which launchs some web 
services, which libraries (jar) should I need?
I see there are 51 jar inside axis2-1.2/lib folderand it seems a lot of 
jars, don't you think?

Thanks in advance and best regards.
Raffaele - axis2 + embedded tomcat beginner


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



Re: Beginner ask a simple question?

2007-06-25 Thread Ognjen Blagojevic

Hello Raffaele,


My very simple question is:
On CLIENT SIDE, to make running a simple client which launchs some web 
services, which libraries (jar) should I need?
I see there are 51 jar inside axis2-1.2/lib folderand it seems a lot of 
jars, don't you think?


It depends. Read this thread:

http://mail-archives.apache.org/mod_mbox/ws-axis-user/200702.mbox/[EMAIL 
PROTECTED]

Regards,
Ognjen

PS. Someone should put this question in FAQ.

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



Re: axis2 command ns2p

2007-06-25 Thread Alexey Zavizionov

Thanks!
I think if option, like in the first axis --fileNStoPkg, was in Axis2
would be more convenient.

Thanks,
Alexey

On 6/24/07, Eran Chinthaka [EMAIL PROTECTED] wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I just had a quick glance over the supported constants inside WSDL2Code
and I couldn't find an option like that. The only way you can do that is
to pass that in the command like using -ns2p option.

Alexey Zavizionov wrote:
 In axis1 it was:
-N, --NStoPkg argument=value
mapping of namespace to package
(now: -ns2p in axis2)
-f, --fileNStoPkg argument
file of NStoPkg mappings (default NStoPkg.properties)
  (now: none in axis2)
 Does axis2 have set the mapping file?

 Regards,
 Alexey

 On 6/21/07, Alexey Zavizionov [EMAIL PROTECTED] wrote:
 Hello

 Does axis2 have option like -ns2p with arg file, file which contains
 ns1=pkg1,ns2=pkg2?
 In axis1 it was NStoPkg.properties

 Thanks,
 Alexey


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



-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGffUrjON2uBzUhh8RAthUAKCVHmmlH0DPRdve8jEL63yPbCX3/gCgjHZ6
Q86ALh6d4U/FnTjSo/9nPRA=
=x/KO
-END PGP SIGNATURE-

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




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



axis2 command -em

2007-06-25 Thread Alexey Zavizionov

Hello,
I'm looking for option em all over axis2 site and have no results.
Does anybody know something about external mapping file or where I can find out?
Is it xml file or not?

-em : Specify an external mapping file

Thanks,
Alexey

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



Re: axis2 and axiom DocumentBuilderFactory

2007-06-25 Thread Alexey Zavizionov

Hi,
I use axis2 1.2 with axiom 1.2.4
http://ws.apache.org/axis2/1_0/OMTutorial.html

HTH,
Alexey

On 6/25/07, Johan Roch [EMAIL PROTECTED] wrote:


We use axiom 1.2 and axis2 1.1. Any idea ?


From: Davanum Srinivas [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Subject: Re: axis2 and axiom DocumentBuilderFactory
Date: Fri, 22 Jun 2007 14:39:16 -0400

Johan,

Which version of Axis2? Axiom?

thanks,
dims

On 6/22/07, Johan Roch [EMAIL PROTECTED] wrote:

Hi all,

We have a webapp with some Axis2 clients. Axis2 uses Axiom to handle xml.
The problem is that other parts of the application must parse some XML
documents. As long as the Xerces DocumentBuilderFactory is used, we have
no
problem. But from a given time, our webapp starts to use the Axiom
DocumentBuilderFactory everywhere and we get some NullPointerException
each
time:

Example with JasperReport:

 StackTrace on java.lang.NullPointerException

org.apache.axiom.om.impl.dom.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(DocumentBuilderFactoryImpl.java:73)

net.sf.jasperreports.engine.util.JRStyledTextParser.init(JRStyledTextParser.java:115)

net.sf.jasperreports.engine.fill.JRBaseFiller.init(JRBaseFiller.java:157)

net.sf.jasperreports.engine.fill.JRVerticalFiller.init(JRVerticalFiller.java:92)

net.sf.jasperreports.engine.fill.JRVerticalFiller.init(JRVerticalFiller.java:74)

... another one:

 Caused by: java.lang.NullPointerException
 at
org.apache.axiom.om.impl.dom.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(DocumentBuilderFactoryImpl.java:73)
 at
com.notary.util.signature.impl.AbstractVerifierImpl.getDocBuilder(AbstractVerifierImpl.java:116)
 at
com.notary.util.signature.impl.iaik.XadesVerifierImpl.verifySignature(XadesVerifierImpl.java:119)
 ... 55 more



I had a look at the Javadoc about DocumentBuilderFactory
http://java.sun.com/j2se/1.4.2/docs/api/javax/xml/parsers/DocumentBuilderFactory.html#newInstance().

and Xerces has a
META-INF/services/javax.xml.parsers.DocumentBuilderFactory
file in the jar while Axiom not.

= the question is: How does Axis2 get the Axiom's DocumentBuilderFactory
?
Does it set the System property ?

About the NullPointerException itself, I guess I should post it in axiom's
mailing list...

Thx,
Johan.

_
Grand passioné ?  Rassemblez tout ce qui vous intéresse   en un seul
endroit
! http://get.live.com/live/features


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




--
Davanum Srinivas :: http://davanum.wordpress.com

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


_
A la recherche d'un ami d'enfance ? Peut-être est-il dans la liste d'amis de
vos amis ! http://spaces.live.com/default.aspx?page=Ed01ss=True


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




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



Re: [Axis2] Axis2 client message different to Axis1 client messag e

2007-06-25 Thread Anne Thomas Manes

Alick,

What exactly is your question?

The messages are semantically equivalent.

Anne

On 6/25/07, Alick Buckley [EMAIL PROTECTED] wrote:


 Hi,

If I use the original test WSDL with the .NET WebService Studio Tool, the
SOAP message is the same as Axis 1.4 ?

Microsoft .NET WebService Studio Tool

?xml version=1.0 encoding=utf-8?
soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance;
soap:Body
getNumber xmlns=http://soap.service.acme.com;
param1
a_int
item23/item
/a_int
n_double23.45/n_double
n_float56.78/n_float
n_int876/n_int
n_long284849/n_long
o_biginteger48484/o_biginteger
/param1
/getNumber
/soap:Body
/soap:Envelope

Axis 1.4

?xml version=1.0 encoding=utf-8?
soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance;
soapenv:Body
*getNumber xmlns=http://soap.service.acme.com;*
param1
a_int
item123/item
item456/item
/a_int
n_double20.1/n_double
n_float21.11/n_float
n_int22/n_int
n_long22345678/n_long
o_bigdecimal223.546/o_bigdecimal
o_biginteger22385943/o_biginteger
o_double2435.456/o_double
o_int23245/o_int
/param1
/getNumber
/soapenv:Body
/soapenv:Envelope

=

-Original Message-
*From:* Alick Buckley [mailto:[EMAIL PROTECTED]
*Sent:* Monday, 25 June 2007 4:15 PM
*To:* axis-user@ws.apache.org
*Subject:* RE: [Axis2] Axis2 client message different to Axis1 client
messag e

Hi,

If the elementFormDefault is set to unqualified then the SOAP message does
not have the namespace prefixes.

But the getNumber element has a namespace prefix, but there is no default
namespace ?

schema elementFormDefault=unqualified targetNamespace=
http://soap.service.acme.com; xmlns=http://www.w3.org/2001/XMLSchema;

===

?xml version=1.0 encoding=utf-8?
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/

soapenv:Body
*ns1:getNumber 
xmlns:ns1=**http://soap.service.acme.com*http://soap.service.acme.com
**
param1
a_int
item2/item
item3/item
item4/item
/a_int
n_double22.5/n_double
n_float23.4/n_float
n_int123/n_int
n_long3456/n_long
o_bigdecimal567.67/o_bigdecimal
o_biginteger98765/o_biginteger
o_double345.67/o_double
o_int7585/o_int
/param1
*/ns1:getNumber
*/soapenv:Body
/soapenv:Envelope
===

-Original Message-
*From:* Alick Buckley [mailto:[EMAIL PROTECTED]
*Sent:* Monday, 25 June 2007 3:50 PM
*To:* axis-user@ws.apache.org
*Subject:* [Axis2] Axis2 client message different to Axis1 client message


Hi,

I am using the same test WSDL for an Axis 1.4 generated client and an
Axis2 1.2 generated client.

The Axis2 1.2 is qualifying the elements with a namespace prefix ?


=

Axis2 1.2

?xml version=1.0 encoding=utf-8?
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/

soapenv:Body
*ns1:getNumber xmlns:ns1=http://soap.service.acme.com;*
ns1:param1
ns1:a_int
ns1:item2/ns1:item
ns1:item3/ns1:item
ns1:item4/ns1:item
/ns1:a_int
ns1:n_double22.5/ns1:n_double
ns1:n_float23.4/ns1:n_float
ns1:n_int123/ns1:n_int
ns1:n_long3456/ns1:n_long
ns1:o_bigdecimal567.67/ns1:o_bigdecimal
ns1:o_biginteger98765/ns1:o_biginteger
ns1:o_double345.67/ns1:o_double
ns1:o_int7585/ns1:o_int
/ns1:param1
/ns1:getNumber
/soapenv:Body
/soapenv:Envelope


=

Axis 1.4

?xml version=1.0 encoding=utf-8?
soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance;
soapenv:Body
*getNumber xmlns=http://soap.service.acme.com;*
param1
 

Re: axis2 and axiom DocumentBuilderFactory

2007-06-25 Thread Johan Roch


We use axiom 1.2 and axis2 1.1. Any idea ?



From: Davanum Srinivas [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Subject: Re: axis2 and axiom DocumentBuilderFactory
Date: Fri, 22 Jun 2007 14:39:16 -0400

Johan,

Which version of Axis2? Axiom?

thanks,
dims

On 6/22/07, Johan Roch [EMAIL PROTECTED] wrote:


Hi all,

We have a webapp with some Axis2 clients. Axis2 uses Axiom to handle xml.
The problem is that other parts of the application must parse some XML
documents. As long as the Xerces DocumentBuilderFactory is used, we have 
no

problem. But from a given time, our webapp starts to use the Axiom
DocumentBuilderFactory everywhere and we get some NullPointerException 
each

time:

Example with JasperReport:

StackTrace on java.lang.NullPointerException

org.apache.axiom.om.impl.dom.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(DocumentBuilderFactoryImpl.java:73)

net.sf.jasperreports.engine.util.JRStyledTextParser.init(JRStyledTextParser.java:115)

net.sf.jasperreports.engine.fill.JRBaseFiller.init(JRBaseFiller.java:157)

net.sf.jasperreports.engine.fill.JRVerticalFiller.init(JRVerticalFiller.java:92)

net.sf.jasperreports.engine.fill.JRVerticalFiller.init(JRVerticalFiller.java:74)


... another one:

Caused by: java.lang.NullPointerException
at
org.apache.axiom.om.impl.dom.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(DocumentBuilderFactoryImpl.java:73)
at
com.notary.util.signature.impl.AbstractVerifierImpl.getDocBuilder(AbstractVerifierImpl.java:116)
at
com.notary.util.signature.impl.iaik.XadesVerifierImpl.verifySignature(XadesVerifierImpl.java:119)
... 55 more



I had a look at the Javadoc about DocumentBuilderFactory
http://java.sun.com/j2se/1.4.2/docs/api/javax/xml/parsers/DocumentBuilderFactory.html#newInstance().

and Xerces has a 
META-INF/services/javax.xml.parsers.DocumentBuilderFactory

file in the jar while Axiom not.

= the question is: How does Axis2 get the Axiom's DocumentBuilderFactory 
?

Does it set the System property ?

About the NullPointerException itself, I guess I should post it in axiom's
mailing list...

Thx,
Johan.

_
Grand passioné ?  Rassemblez tout ce qui vous intéresse   en un seul 
endroit

! http://get.live.com/live/features


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





--
Davanum Srinivas :: http://davanum.wordpress.com

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



_
A la recherche d'un ami d'enfance ? Peut-être est-il dans la liste d'amis de 
vos amis ! http://spaces.live.com/default.aspx?page=Ed01ss=True



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



Vien N Tran/Austin/IBM is out of the office.

2007-06-25 Thread Vien N Tran

I will be out of the office starting  06/25/2007 and will not return until
07/09/2007.

I will respond to your message when I return on July 9, 2007

[Axis2] Undeployment doesn't work

2007-06-25 Thread Angel Todorov

Hi Deepal,

Is there any recent fix in the snapshot that makes undeployment to
successfully un-register the undeployed service ? No matter which service i
try to undeploy, the service remains registered in the Axis2 runtime.

Regards,
Angel


Re: axis2 and axiom DocumentBuilderFactory

2007-06-25 Thread Davanum Srinivas

Johan,

Is there some stripped down sample you can show us? Please create a
JIRA so that we can track this issue. You can upload the zip to JIRA.

thanks,
dims

On 6/25/07, Johan Roch [EMAIL PROTECTED] wrote:


We use axiom 1.2 and axis2 1.1. Any idea ?


From: Davanum Srinivas [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Subject: Re: axis2 and axiom DocumentBuilderFactory
Date: Fri, 22 Jun 2007 14:39:16 -0400

Johan,

Which version of Axis2? Axiom?

thanks,
dims

On 6/22/07, Johan Roch [EMAIL PROTECTED] wrote:

Hi all,

We have a webapp with some Axis2 clients. Axis2 uses Axiom to handle xml.
The problem is that other parts of the application must parse some XML
documents. As long as the Xerces DocumentBuilderFactory is used, we have
no
problem. But from a given time, our webapp starts to use the Axiom
DocumentBuilderFactory everywhere and we get some NullPointerException
each
time:

Example with JasperReport:

 StackTrace on java.lang.NullPointerException

org.apache.axiom.om.impl.dom.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(DocumentBuilderFactoryImpl.java:73)

net.sf.jasperreports.engine.util.JRStyledTextParser.init(JRStyledTextParser.java:115)

net.sf.jasperreports.engine.fill.JRBaseFiller.init(JRBaseFiller.java:157)

net.sf.jasperreports.engine.fill.JRVerticalFiller.init(JRVerticalFiller.java:92)

net.sf.jasperreports.engine.fill.JRVerticalFiller.init(JRVerticalFiller.java:74)

... another one:

 Caused by: java.lang.NullPointerException
 at
org.apache.axiom.om.impl.dom.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(DocumentBuilderFactoryImpl.java:73)
 at
com.notary.util.signature.impl.AbstractVerifierImpl.getDocBuilder(AbstractVerifierImpl.java:116)
 at
com.notary.util.signature.impl.iaik.XadesVerifierImpl.verifySignature(XadesVerifierImpl.java:119)
 ... 55 more



I had a look at the Javadoc about DocumentBuilderFactory
http://java.sun.com/j2se/1.4.2/docs/api/javax/xml/parsers/DocumentBuilderFactory.html#newInstance().

and Xerces has a
META-INF/services/javax.xml.parsers.DocumentBuilderFactory
file in the jar while Axiom not.

= the question is: How does Axis2 get the Axiom's DocumentBuilderFactory
?
Does it set the System property ?

About the NullPointerException itself, I guess I should post it in axiom's
mailing list...

Thx,
Johan.

_
Grand passioné ?  Rassemblez tout ce qui vous intéresse   en un seul
endroit
! http://get.live.com/live/features


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




--
Davanum Srinivas :: http://davanum.wordpress.com

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


_
A la recherche d'un ami d'enfance ? Peut-être est-il dans la liste d'amis de
vos amis ! http://spaces.live.com/default.aspx?page=Ed01ss=True


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





--
Davanum Srinivas :: http://davanum.wordpress.com

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



Re: WSDL2Java for HTTPS

2007-06-25 Thread Davanum Srinivas

Excellent write up. thanks!

-- dims

On 6/25/07, r1c4r60 [EMAIL PROTECTED] wrote:


Hi,

This is a way to solve the WSDL over HTTPS issue reported by so many
resulting in No Trusted Certificate.

1 - Export Certificate from Internet Explorer

1.1 - Access the service WSDL location (Ex. https://foo.com/bar?wsdl)
1.2 - Internet explorer will prompt a security alert
1.3 - Select the View Certificate button
1.4 - Navigate to the tab Details
1.5 - Select the Copy to File.. button
1.6 - Certificate Export Wizard will be displayed. Select NEXT button.
1.7 - The option DER encoded binary X.509 (.CER) will by default be
selected. Select Next
1.8 - Place the file where it suits you better. (Ex. foobar) PS. Don't add
an extension. It will be store as: [given name].cer
1.9 - Select Next
1.10 - The Completing Certificate Export Wizard will be displayed.
1.11 - Select Finish
1.12 - The will be a pop-up saying The export was successful

2 - Importing the certificate signature into the keystore

2.1 - Find out which keystore is being used by ANT by using the command:
ant -diagnostics
2.2 - Lots of information will be displayed. Find the key java.home (Ex.
java.home : C:\j2sdk1.4.2_14\jre)
2.3 - Thereby the truststore being used by ANT is in:
C:\j2sdk1.4.2_14\jre\lib\security\cacerts
2.4 - Now you have to import the certificate into the keystore: keytool
-import -trustcacerts -keystore C:\j2sdk1.4.2_14\jre\lib\security\cacerts
-storepass changeit -alias [foo bar] -file [the name you gave in step
1.8].cer
2.5 - Verify if the entry was created correctly.
C:\j2sdk1.4.2_14\jre\lib\securitykeytool -keystore cacerts -storepass
changeit -list -alias [foo bar]

3 - Run the Ant task

target name=wsdl2java
mkdir dir=src/main/java-generated/
axis-wsdl2java
output=src/main/java-generated
testcase=false
verbose=true
serverside=false
url=https://foo.com/bar?wsdl/
/target

Best Regards,
Ricardo


Mark Babcock-3 wrote:

 I am trying to generate stubs with the WSDL2Java tool

 I imported my certificate into my keystore (cacerts) using

 The keytool.



 When I run my build file I get the following exception:



  [java] javax.net.ssl.SSLHandshakeException:
 sun.security.validator.Validato

 rException: PKIX path building failed:
 sun.security.provider.certpath.SunCertPat

 hBuilderException: unable to find valid certification path to requested
 target



 ?xml version=1.0 encoding=UTF-8?



 !-- = --

 !-- xxx wsdl2java --

 !-- = --



 project name=xxxWSDL2Java default=main basedir=.





 !--
  --

 !-- creates axis stubs for webservices
 --

 !--
  --

   target  name=generateWebServiceStubs depends=

 java  classname=org.apache.axis.wsdl.WSDL2Java
 fork=true

   classpath

 pathelement location=axis.jar/

 pathelement location=axis-ant.jar /

 pathelement location=jaxrpc.jar /

 pathelement
 location=commons-logging-1.0.4.jar /

 pathelement
 location=commons-discovery-0.2.jar /

 pathelement location=wsdl4j-1.5.1.jar /

   /classpath

   arg value=https://URL//

   arg value=-o /

   arg value=-Djavax.net.ssl.trustStore=c:/program
 files/javajre1.6.0_01/lib/security/cacerts /

 /java

   /target



   target name=main depends=generateWebServiceStubs

 echo

   Building xxx WSDL 2 Java\par

 /echo

   /target

 /project








--
View this message in context: 
http://www.nabble.com/WSDL2Java-for-HTTPS-tf3965233.html#a11286558
Sent from the Axis - User mailing list archive at Nabble.com.


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





--
Davanum Srinivas :: http://davanum.wordpress.com

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



Re: WSDL2Java for HTTPS

2007-06-25 Thread r1c4r60

Hi,

This is a way to solve the WSDL over HTTPS issue reported by so many
resulting in No Trusted Certificate.

1 - Export Certificate from Internet Explorer

1.1 - Access the service WSDL location (Ex. https://foo.com/bar?wsdl)
1.2 - Internet explorer will prompt a security alert
1.3 - Select the View Certificate button
1.4 - Navigate to the tab Details 
1.5 - Select the Copy to File.. button
1.6 - Certificate Export Wizard will be displayed. Select NEXT button.
1.7 - The option DER encoded binary X.509 (.CER) will by default be
selected. Select Next
1.8 - Place the file where it suits you better. (Ex. foobar) PS. Don't add
an extension. It will be store as: [given name].cer
1.9 - Select Next 
1.10 - The Completing Certificate Export Wizard will be displayed. 
1.11 - Select Finish
1.12 - The will be a pop-up saying The export was successful

2 - Importing the certificate signature into the keystore

2.1 - Find out which keystore is being used by ANT by using the command:
ant -diagnostics
2.2 - Lots of information will be displayed. Find the key java.home (Ex.
java.home : C:\j2sdk1.4.2_14\jre) 
2.3 - Thereby the truststore being used by ANT is in:
C:\j2sdk1.4.2_14\jre\lib\security\cacerts 
2.4 - Now you have to import the certificate into the keystore: keytool
-import -trustcacerts -keystore C:\j2sdk1.4.2_14\jre\lib\security\cacerts
-storepass changeit -alias [foo bar] -file [the name you gave in step
1.8].cer
2.5 - Verify if the entry was created correctly.
C:\j2sdk1.4.2_14\jre\lib\securitykeytool -keystore cacerts -storepass
changeit -list -alias [foo bar]

3 - Run the Ant task

target name=wsdl2java
mkdir dir=src/main/java-generated/
axis-wsdl2java 
output=src/main/java-generated
testcase=false
verbose=true
serverside=false
url=https://foo.com/bar?wsdl/
/target

Best Regards,
Ricardo


Mark Babcock-3 wrote:
 
 I am trying to generate stubs with the WSDL2Java tool
 
 I imported my certificate into my keystore (cacerts) using 
 
 The keytool.  
 
  
 
 When I run my build file I get the following exception:
 
  
 
  [java] javax.net.ssl.SSLHandshakeException:
 sun.security.validator.Validato
 
 rException: PKIX path building failed:
 sun.security.provider.certpath.SunCertPat
 
 hBuilderException: unable to find valid certification path to requested
 target
 
  
 
 ?xml version=1.0 encoding=UTF-8?
 
  
 
 !-- = --
 
 !-- xxx wsdl2java --
 
 !-- = --
 
  
 
 project name=xxxWSDL2Java default=main basedir=.
 
  
 
  
 
 !--
  --
 
 !-- creates axis stubs for webservices
 --
 
 !--
  --
 
   target  name=generateWebServiceStubs depends=   
 
 java  classname=org.apache.axis.wsdl.WSDL2Java
 fork=true
 
   classpath
 
 pathelement location=axis.jar/
 
 pathelement location=axis-ant.jar /
 
 pathelement location=jaxrpc.jar /
 
 pathelement
 location=commons-logging-1.0.4.jar /
 
 pathelement
 location=commons-discovery-0.2.jar /
 
 pathelement location=wsdl4j-1.5.1.jar /
 
   /classpath
 
   arg value=https://URL//
 
   arg value=-o /
 
   arg value=-Djavax.net.ssl.trustStore=c:/program
 files/javajre1.6.0_01/lib/security/cacerts /
 
 /java
 
   /target
 
  
 
   target name=main depends=generateWebServiceStubs
 
 echo
 
   Building xxx WSDL 2 Java\par
 
 /echo
 
   /target
 
 /project
 
  
 
  
 
 
 

-- 
View this message in context: 
http://www.nabble.com/WSDL2Java-for-HTTPS-tf3965233.html#a11286558
Sent from the Axis - User mailing list archive at Nabble.com.


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



RE: WSDL2Java for HTTPS

2007-06-25 Thread Mark Babcock
Ricardo,

Thank you for that amazing help.  However, I'm having problems with the
ant tag axis-wsdl2java.  Getting the name is undefined.

-Original Message-
From: r1c4r60 [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 25, 2007 9:22 AM
To: axis-user@ws.apache.org
Subject: Re: WSDL2Java for HTTPS


Hi,

This is a way to solve the WSDL over HTTPS issue reported by so many
resulting in No Trusted Certificate.

1 - Export Certificate from Internet Explorer

1.1 - Access the service WSDL location (Ex. https://foo.com/bar?wsdl)
1.2 - Internet explorer will prompt a security alert
1.3 - Select the View Certificate button
1.4 - Navigate to the tab Details 
1.5 - Select the Copy to File.. button
1.6 - Certificate Export Wizard will be displayed. Select NEXT
button.
1.7 - The option DER encoded binary X.509 (.CER) will by default be
selected. Select Next
1.8 - Place the file where it suits you better. (Ex. foobar) PS. Don't
add
an extension. It will be store as: [given name].cer
1.9 - Select Next 
1.10 - The Completing Certificate Export Wizard will be displayed. 
1.11 - Select Finish
1.12 - The will be a pop-up saying The export was successful

2 - Importing the certificate signature into the keystore

2.1 - Find out which keystore is being used by ANT by using the
command:
ant -diagnostics
2.2 - Lots of information will be displayed. Find the key java.home
(Ex.
java.home : C:\j2sdk1.4.2_14\jre) 
2.3 - Thereby the truststore being used by ANT is in:
C:\j2sdk1.4.2_14\jre\lib\security\cacerts 
2.4 - Now you have to import the certificate into the keystore:
keytool
-import -trustcacerts -keystore
C:\j2sdk1.4.2_14\jre\lib\security\cacerts
-storepass changeit -alias [foo bar] -file [the name you gave in step
1.8].cer
2.5 - Verify if the entry was created correctly.
C:\j2sdk1.4.2_14\jre\lib\securitykeytool -keystore cacerts -storepass
changeit -list -alias [foo bar]

3 - Run the Ant task

target name=wsdl2java
mkdir dir=src/main/java-generated/
axis-wsdl2java 
output=src/main/java-generated
testcase=false
verbose=true
serverside=false
url=https://foo.com/bar?wsdl/
/target

Best Regards,
Ricardo


Mark Babcock-3 wrote:
 
 I am trying to generate stubs with the WSDL2Java tool
 
 I imported my certificate into my keystore (cacerts) using 
 
 The keytool.  
 
  
 
 When I run my build file I get the following exception:
 
  
 
  [java] javax.net.ssl.SSLHandshakeException:
 sun.security.validator.Validato
 
 rException: PKIX path building failed:
 sun.security.provider.certpath.SunCertPat
 
 hBuilderException: unable to find valid certification path to
requested
 target
 
  
 
 ?xml version=1.0 encoding=UTF-8?
 
  
 
 !-- = --
 
 !-- xxx wsdl2java --
 
 !-- = --
 
  
 
 project name=xxxWSDL2Java default=main basedir=.
 
  
 
  
 
 !--
 
--
 
 !-- creates axis stubs for webservices
 --
 
 !--
 
--
 
   target  name=generateWebServiceStubs depends=

 
 java  classname=org.apache.axis.wsdl.WSDL2Java
 fork=true
 
   classpath
 
 pathelement location=axis.jar/
 
 pathelement location=axis-ant.jar /
 
 pathelement location=jaxrpc.jar /
 
 pathelement
 location=commons-logging-1.0.4.jar /
 
 pathelement
 location=commons-discovery-0.2.jar /
 
 pathelement location=wsdl4j-1.5.1.jar /
 
   /classpath
 
   arg value=https://URL//
 
   arg value=-o /
 
   arg value=-Djavax.net.ssl.trustStore=c:/program
 files/javajre1.6.0_01/lib/security/cacerts /
 
 /java
 
   /target
 
  
 
   target name=main depends=generateWebServiceStubs
 
 echo
 
   Building xxx WSDL 2 Java\par
 
 /echo
 
   /target
 
 /project
 
  
 
  
 
 
 

-- 
View this message in context:
http://www.nabble.com/WSDL2Java-for-HTTPS-tf3965233.html#a11286558
Sent from the Axis - User mailing list archive at Nabble.com.


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


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



RE: JMS/SOAP axis2

2007-06-25 Thread Kang, Kamaljeet K.
I ran the same test with XMLBeans few months back, I didn't have any
issues.

kamal

-Original Message-
From: Chathura Herath [mailto:[EMAIL PROTECTED] 
Sent: Saturday, June 23, 2007 1:01 PM
To: axis-user@ws.apache.org
Subject: Re: JMS/SOAP axis2

This looks familiar to some of the problems i have seen in JSON. I
assume you are using ADB for data binding,  are u?
If so could you try  -d xmlbeans and see whether it works. This may
not solve your problem completely, but it would give us an idea.
Thanks
Chathura

On 6/21/07, Kang, Kamaljeet K. [EMAIL PROTECTED] wrote:



 Hi,

 I am trying to test a webservice with JMS transport. The service works
 perfectly fine with HTTP but with JMS it gives the following exception
 during unmarshling. Looks like localName is incorrect. Is it a bug?


 OMElelment BodyBy the StaxSOAPModelBuilder
 1-Jun 15:44:40,552 DEBUG builder.StAXOMBuilder [JMSWorker-1] -
 START_ELEMENT: {
 mf854.v1}notify:notify
 1-Jun 15:44:40,552 DEBUG builder.StAXSOAPModelBuilder [JMSWorker-1] -
Build
 the
 OMElelment notifyBy the StaxSOAPModelBuilder
 1-Jun 15:44:40,552 DEBUG engine.AxisEngine [JMSWorker-1] -
[MessageContext:
 log
 D=urn:uuid:4153845C2D42C4D72B1182455081080] receive:null
 1-Jun 15:44:40,552 DEBUG
 addressing.AddressingValidationHandler [JMSWorker-1] -
 invoke: IS_ADDR_INFO_ALREADY_PROCESSED=null
 1-Jun 15:44:40,552 DEBUG
 addressing.AddressingValidationHandler [JMSWorker-1] -
 checkUsingAddressing: WSAddressingFlag=unspecified
 1-Jun 15:51:30,779 DEBUG builder.StAXOMBuilder [JMSWorker-1] -
 START_ELEMENT: {
 mf854.v1}TopicExpression_T:TopicExpression_T (it should be
 topic)
 1-Jun 15:51:30,779 DEBUG builder.StAXSOAPModelBuilder [JMSWorker-1] -
Build
 the
 OMElelment TopicExpression_TBy the StaxSOAPModelBuilder
 1-Jun 15:52:48,088 ERROR jms.JMSMessageReceiver [JMSWorker-1] - JMS
Worker
 [JMS
 orker-1] Encountered an Axis Fault : java.lang.RuntimeException:
Unexpected
 sub
 lement TopicExpression_T; nested exception is:
java.lang.RuntimeException: java.lang.RuntimeException:
Unexpected
 subel
 ment TopicExpression_T
 rg.apache.axis2.AxisFault: java.lang.RuntimeException: Unexpected
subelement
 To
 icExpression_T; nested exception is:
java.lang.RuntimeException: java.lang.RuntimeException:
Unexpected
 subel
 ment TopicExpression_T
at
 org.apache.axis2.AxisFault.makeFault(AxisFault.java:367)
at
 org.tmforum.tmf854.v1.ws.notif.NotificationConsumerMessageReceiverInO

ly.invokeBusinessLogic(NotificationConsumerMessageReceiverInOnly.java:55
)
at
 org.apache.axis2.receivers.AbstractInMessageReceiver.receive(Abstract
 nMessageReceiver.java:35)
at
 org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:186)
 Kamal




 
 The information contained in this message may be privileged
 and confidential and protected from disclosure. If the reader
 of this message is not the intended recipient, or an employee
 or agent responsible for delivering this message to the
 intended recipient, you are hereby notified that any reproduction,
 dissemination or distribution of this communication is strictly
 prohibited. If you have received this communication in error,
 please notify us immediately by replying to the message and
 deleting it from your computer. Thank you. Tellabs
 




-- 
Chathura Herath
http://people.apache.org/~chathura/
http://chathurah.blogspot.com/

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

The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs


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



RE: SOAP response

2007-06-25 Thread Walker, Jeff
Demetris G,
Time for me to ask a stupid question.
Does the value of the Content-Length:  http header of your response
match the length of all of the actual sent characters?
-jeff


-Original Message-
From: Demetris G [mailto:[EMAIL PROTECTED] 
Sent: Saturday, June 23, 2007 10:33 PM
To: axis-user@ws.apache.org
Subject: Re: SOAP response


Hi all,
   
is it possible that no one working with Axis for a while now knows 
what terminates
the SOAP message coming from the server engine ?? Anyone ? I will 
appreciate it.
Nothing shows up in the tcpmon or any other tool I used however the SAX 
parser
see the complete SOAP envelope as shown below but yet it block waiting 
for something
else. What is this extra data that it is expecting ? I am sifting 
through the Axis/SAX
classes but it takes a long time to chase this.

Thanks much

Demetris G wrote:

 Jeff -- I traced the SAX and Xerces routines to find out what they are

 doing but it
 gets a bit hectic to figure them out. I know the client reads back the

 headers I send
 it and all of the SOAP message below (if for example I mispell the 
 last tag of the SOAP
 message then SAX is complaining which means it does parse it till 
 them). But the parser
 is stuck on SocketInputStream.read() as if it is expecting more after 
 the last tag of the
 SOAP message - I tried CR / LF but that does not do it.

 Any suggestions ??

   ?xml version=\1.0\ encoding=\UTF-8\?
  soapenv:Envelope 
 xmlns:soapenv=\http://schemas.xmlsoap.org/soap/envelope/\; 
  
 xmlns:xsd=\http://www.w3.org/2001/XMLSchema\; 
  
 xmlns:xsi=\http://www.w3.org/2001/XMLSchema-instance\;
  soapenv:Body
  ns1:getBundlesResponse 
 soapenv:encodingStyle=\
  
 http://schemas.xmlsoap.org/soap/encoding/\; 
  
 xmlns:ns1=\http://soapobject.bundle.org\;
  getBundlesReturn 
 soapenc:arrayType=\xsd:long[24]\ xsi:type=\soapenc:Array\ 
  
 xmlns:soapenc=\http://schemas.xmlsoap.org/soap/encoding/\;
  getBundlesReturn 
 href=\#id23\/
  /getBundlesReturn
  /ns1:getBundlesResponse
  multiRef id=\id23\ 
 soapenc:root=\0\ 
  
 soapenv:encodingStyle=\http://schemas.xmlsoap.org/soap/encoding/\; 
  xsi:type=\xsd:long\ 
 xmlns:soapenc=\http://schemas.xmlsoap.org/soap/encoding/\;
  3
  /multiRef
  /soapenv:Body
  /soapenv:Envelope;


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



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




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



RE: WSDL2Java for HTTPS

2007-06-25 Thread r1c4r60

Hi Mark,

Most likely you haven't set the Axis Classpath. It could be done in several
different ways as for example the one described at the Axis Installation
page: 

http://ws.apache.org/axis/java/install.html#ClasspathSetup

 
Or just follow the instruction below:

Add these lines to your build.xml and it should start working.

property name=axis.home value=C:\axis-1_4 / !--The value should be
your AXIS home directory--
  
path id=axis.classpath
fileset dir=${axis.home}/lib
include name=**/*.jar /
/fileset
/path

taskdef resource=axis-tasks.properties classpathref=axis.classpath /  

PS. This is a refence to http://ws.apache.org/axis/java/ant/ant.html

Best Regards,
Ricardo
 


Mark Babcock-3 wrote:
 
 Ricardo,
 
 Thank you for that amazing help.  However, I'm having problems with the
 ant tag axis-wsdl2java.  Getting the name is undefined.
 
 -Original Message-
 From: r1c4r60 [mailto:[EMAIL PROTECTED] 
 Sent: Monday, June 25, 2007 9:22 AM
 To: axis-user@ws.apache.org
 Subject: Re: WSDL2Java for HTTPS
 
 
 Hi,
 
 This is a way to solve the WSDL over HTTPS issue reported by so many
 resulting in No Trusted Certificate.
 
 1 - Export Certificate from Internet Explorer
 
 1.1 - Access the service WSDL location (Ex. https://foo.com/bar?wsdl)
 1.2 - Internet explorer will prompt a security alert
 1.3 - Select the View Certificate button
 1.4 - Navigate to the tab Details 
 1.5 - Select the Copy to File.. button
 1.6 - Certificate Export Wizard will be displayed. Select NEXT
 button.
 1.7 - The option DER encoded binary X.509 (.CER) will by default be
 selected. Select Next
 1.8 - Place the file where it suits you better. (Ex. foobar) PS. Don't
 add
 an extension. It will be store as: [given name].cer
 1.9 - Select Next 
 1.10 - The Completing Certificate Export Wizard will be displayed. 
 1.11 - Select Finish
 1.12 - The will be a pop-up saying The export was successful
 
 2 - Importing the certificate signature into the keystore
 
 2.1 - Find out which keystore is being used by ANT by using the
 command:
 ant -diagnostics
 2.2 - Lots of information will be displayed. Find the key java.home
 (Ex.
 java.home : C:\j2sdk1.4.2_14\jre) 
 2.3 - Thereby the truststore being used by ANT is in:
 C:\j2sdk1.4.2_14\jre\lib\security\cacerts 
 2.4 - Now you have to import the certificate into the keystore:
 keytool
 -import -trustcacerts -keystore
 C:\j2sdk1.4.2_14\jre\lib\security\cacerts
 -storepass changeit -alias [foo bar] -file [the name you gave in step
 1.8].cer
 2.5 - Verify if the entry was created correctly.
 C:\j2sdk1.4.2_14\jre\lib\securitykeytool -keystore cacerts -storepass
 changeit -list -alias [foo bar]
 
 3 - Run the Ant task
 
 target name=wsdl2java
 mkdir dir=src/main/java-generated/
 axis-wsdl2java 
 output=src/main/java-generated
 testcase=false
 verbose=true
 serverside=false
 url=https://foo.com/bar?wsdl/
 /target
 
 Best Regards,
 Ricardo
 
 
 Mark Babcock-3 wrote:
 
 I am trying to generate stubs with the WSDL2Java tool
 
 I imported my certificate into my keystore (cacerts) using 
 
 The keytool.  
 
  
 
 When I run my build file I get the following exception:
 
  
 
  [java] javax.net.ssl.SSLHandshakeException:
 sun.security.validator.Validato
 
 rException: PKIX path building failed:
 sun.security.provider.certpath.SunCertPat
 
 hBuilderException: unable to find valid certification path to
 requested
 target
 
  
 
 ?xml version=1.0 encoding=UTF-8?
 
  
 
 !-- = --
 
 !-- xxx wsdl2java --
 
 !-- = --
 
  
 
 project name=xxxWSDL2Java default=main basedir=.
 
  
 
  
 
 !--
 
 --
 
 !-- creates axis stubs for webservices
 --
 
 !--
 
 --
 
   target  name=generateWebServiceStubs depends=
 
 
 java  classname=org.apache.axis.wsdl.WSDL2Java
 fork=true
 
   classpath
 
 pathelement location=axis.jar/
 
 pathelement location=axis-ant.jar /
 
 pathelement location=jaxrpc.jar /
 
 pathelement
 location=commons-logging-1.0.4.jar /
 
 pathelement
 location=commons-discovery-0.2.jar /
 
 pathelement location=wsdl4j-1.5.1.jar /
 
   /classpath
 
   arg value=https://URL//
 
   arg value=-o /
 
   arg value=-Djavax.net.ssl.trustStore=c:/program
 files/javajre1.6.0_01/lib/security/cacerts /
 
 /java
 
   /target
 
  
 
   target name=main depends=generateWebServiceStubs
 
 echo
 
   Building xxx WSDL 2 Java\par
 
 /echo
 
   /target
 
 /project
 
  
 
  
 
 
 
 
 -- 
 View this message in context:
 

Need Experts advice

2007-06-25 Thread renjith kalappurackal
Hi All,
   
  I am inviting everyones attention to two problems I am facing in my current 
project.
   
  Let me expain my first problem.
  I am in a confusion to decide upon the best approach to follow in developing 
a web service.
  My confusion is to get best of webservices. Which one will be best practice ?
  a) Embedded Webserivce
  b)Standalone webservice
   
  The scenario I am having is I have different .WAR(WEb archive) instances in 
my server that is using single EAR. If I am going for Embedded service I need 
to have services embedded in each WAR files. If I am going for Standalone 
approach, I don't know whether it can impact performance to the entire system.
   
 My second probelm isto choose the Session management option in 
Axis2.
  I have different types of client that are accessible to my webservice ( 
Actually I generated my service in order to communicate with the client 
programs using the WSDL provided by them) And these client programs are 
generated in Microsoft platform. I have no idea how client programs are manging 
their session. Only thing I know is that this client will try to communicate 
with my webservice using a token(generated by my webservice program) that is 
send to client programs when they communicate for the first time. And for every 
consecutive communication Client programs will send this token as an argument. 
I think I can manage the session by keeping a HashMap/ ArrayList to hold custom 
made session objects against each token to hold the details inorder to identify 
each client instance. 
  Is there any way Axis2 allows to hold these clent details inside the 
session. I am not sure whetehr I can use Soap Session or something like that to 
keep track of client instances, since I have no control over the client 
programs( And I have no idea how they are created and what approach they are 
using for managing their session).
   
   Could you please provide me with your suggestions ?
  If I am wrong please correct me.
   
  Thanks in advance,
  Renjit
   

   
-
Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's on, 
when. 

RE: Axis2 and SAML

2007-06-25 Thread Michael.Davis
Thanks George,

For some reason it took me a whole week to come across this post.

Anyway, you say you'd recommend SAML, but you also say you prefer WS-Trust. I'm 
a bit confused - I thought SAML was a language for representing users and their 
permissions, whereas WS-Trust was for exchanging security tokens. In other 
words, I thought these addressed two different classes of use cases.

I'm still very new to this stuff... 

cheers,
md
 

 -Original Message-
 From: George Stanchev [mailto:[EMAIL PROTECTED]
 Sent: Monday, June 18, 2007 12:15 PM
 To: axis-user@ws.apache.org
 Subject: RE: Axis2 and SAML
 
 
 Hi Michael,
 
 The support for SAML in Rampart is rather weak and if you go 
 with SAML,
 do not expect much
 help from it. It uses is internally for the more of a special case of
 WS-SecureConversation SC token.
 In addition, in Rampart 1.1 there was a way to create a signed and
 unsigned SAML tokens but you get the
 token only in the outbound SOAP and you don't have much control over
 what goes inside (for example SAML attributes).
 
 I'd definetely recommend SAML as the way to go for tokens in an SSO
 implementation - it is standard, 
 its been around for a while, its proven, it is signed and it is
 extensible. In addtion, the SAML 2.0 by
 it self defines a security language rivaling WS-Trust so 
 you can just
 stay with it, though I
 prefer WS-Trust based exchanges as more standard and supported way to
 go.
 
 Internet2's OpenSAML libraries are the only mature open source SAML
 libraries that I know of. 
 Version 1.1 supports SAML 1.0 and 1.1 and version 2 supports all SAML
 standards. OpenSAML2 is 
 still being developed and even though it is stable for most parts it
 will change somewhat around 
 some of the more peripherical cases (Encryption is one that comes to
 mind). Though it does
 have a steeper learning curve, I'd start with OpenSAML2.
 
 Good luck with the SSO implementation.
 
 Best Regards,
 George
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] 
 Sent: Friday, June 15, 2007 2:36 PM
 To: axis-user@ws.apache.org
 Subject: Axis2 and SAML
 
 Hi,
 
 I'm working on a single-sign-on service for our 
 organization's intranet.
 The idea an application can send a username, and password and
 application identifier to the service, and the service responds with a
 list of permissions that the user has for the particular application.
 
 Just to get started, I created a service that returns a string from
 which I can parse out what I need. But I'm wondering if I could gain
 anything (such as greater interoperability) by using a 
 standard such as
 SAML to represent a user and his/her permissions.
 
 I see that there is a framework for working with SAML:
 http://www.opensaml.org/ 
 
 Does this sound reasonable or am I heading in the wrong 
 direction? Will
 I end up with a schema nightmare if I return a SAML xml document as a
 service payload? BTW, I plan on writing the client and server by hand,
 because later I will probably want to add rampart and have 
 more control
 over headers and stuff.
 
 Thanks
 Michael Davis
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 **
 This email and any files transmitted with it are confidential and
 intended solely for the use of the individual or entity to whom they
 are addressed. Any unauthorized review, use, disclosure or 
 distribution is prohibited. If you are not the intended 
 recipient, please contact the sender by reply e-mail and 
 destroy all copies of the original message.
 
 
 -
 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]



WSDoAllReceiver: security processing failed

2007-06-25 Thread masi


Hi all,

I am following the IBM guide
https://www6.software.ibm.com/developerworks/education/ws-understand-web-services4/section5.html

I first enabled the Signature in the client. itemsSignature/item
for the body for the outflowsecurity.

I got this:

  [java] org.apache.axis2.AxisFault: WSDoAllReceiver: security
processing failed

The username is good, the password  is good (from the callback handler).
[EMAIL PROTECTED]
~/Documents/workspace/TianiIdP/build/classes $ keytool -list -alias
umberto -keystore mykeys.j
Immettere la password del keystore:  mypass
umberto, 20-giu-2007, keyEntry,
Impronta digitale certificato (MD5):
DA:7A:E0:B1:9B:79:93:70:5F:10:7C:30:57:26:C4:C4


Can you help me?

Cheers,




This message was sent using IMP, the Internet Messaging Program.



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



RE: Axis2 and SAML

2007-06-25 Thread masi

Hi,

Quoting [EMAIL PROTECTED]:

Anyway, you say you'd recommend SAML, but you also say you prefer   
WS-Trust. I'm a bit confused - I thought SAML was a language for   
representing users and their permissions, whereas WS-Trust was for   
exchanging security tokens. In other words, I thought these   
addressed two different classes of use cases.


You can use WS-Trust to exchange SAML2.0 tokens, via the RequestTokenType
element.

If you're able to have a WS-Trust response using axis2, let me know.

I'm trying to implement this: I created the necessary header but I'm not
able to set it in the SOAP response (not using opensaml, since the examples
are not so good, and I don't know where to start).

I use rampart for signing and setting timestamps, but it does not work now
for me (see the previous post).

Cheers,




This message was sent using IMP, the Internet Messaging Program.



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



RE: Axis2 and SAML

2007-06-25 Thread Michael.Davis
Thanks, I'll let you know how it goes.

cheers,
md
 

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 Sent: Monday, June 25, 2007 11:15 AM
 To: axis-user@ws.apache.org
 Subject: RE: Axis2 and SAML
 
 
 Hi,
 
 Quoting [EMAIL PROTECTED]:
 
  Anyway, you say you'd recommend SAML, but you also say you prefer   
  WS-Trust. I'm a bit confused - I thought SAML was a language for   
  representing users and their permissions, whereas WS-Trust 
 was for   
  exchanging security tokens. In other words, I thought these   
  addressed two different classes of use cases.
 
 You can use WS-Trust to exchange SAML2.0 tokens, via the 
 RequestTokenType
 element.
 
 If you're able to have a WS-Trust response using axis2, let me know.
 
 I'm trying to implement this: I created the necessary header 
 but I'm not
 able to set it in the SOAP response (not using opensaml, 
 since the examples
 are not so good, and I don't know where to start).
 
 I use rampart for signing and setting timestamps, but it does 
 not work now
 for me (see the previous post).
 
 Cheers,
 
 
 
 
 This message was sent using IMP, the Internet Messaging Program.
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 

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



Re: Axis2 and SAML

2007-06-25 Thread Paul Fremantle

There is an open source identity server based on WS-Trust/SAML and Axis2 here:
http://wso2.org/projects/solutions/identity

Paul



On 6/25/07, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:

Thanks, I'll let you know how it goes.

cheers,
md


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 Sent: Monday, June 25, 2007 11:15 AM
 To: axis-user@ws.apache.org
 Subject: RE: Axis2 and SAML


 Hi,

 Quoting [EMAIL PROTECTED]:

  Anyway, you say you'd recommend SAML, but you also say you prefer
  WS-Trust. I'm a bit confused - I thought SAML was a language for
  representing users and their permissions, whereas WS-Trust
 was for
  exchanging security tokens. In other words, I thought these
  addressed two different classes of use cases.

 You can use WS-Trust to exchange SAML2.0 tokens, via the
 RequestTokenType
 element.

 If you're able to have a WS-Trust response using axis2, let me know.

 I'm trying to implement this: I created the necessary header
 but I'm not
 able to set it in the SOAP response (not using opensaml,
 since the examples
 are not so good, and I don't know where to start).

 I use rampart for signing and setting timestamps, but it does
 not work now
 for me (see the previous post).

 Cheers,



 
 This message was sent using IMP, the Internet Messaging Program.



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





--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

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

Oxygenating the Web Service Platform, www.wso2.com

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



[Axis2 ] Making the HttpServletRequest available for the Service methods ?

2007-06-25 Thread sol myr
Hi,
   
  We have an Axis2 service, with standard aar deployment under Tomcat.
   
  When receiving a soap request, we'd like the Service class (business logic) 
to also have direct access to the HttpServletRequest, which carried the soap 
request ( that's in *addition* to getting the usual parameters, parsed from 
soap into java objects).
   
  Could anyone please tell how to achieve this ? 
   
  We're aware it's bad design, mixing layers, etc.
  Unfortunately, the requirement is forced by an old application, with an 
unusual security design.
   
  Thanks :)

   
-
Get the free Yahoo! toolbar and rest assured with the added security of spyware 
protection. 

RE: Axis2 and SAML

2007-06-25 Thread Michael.Davis
Thanks. Looks interesting but it requires an apache httpd module, and I'm sure 
that the organization that maintains our servers will refuse to install it. 
It's a government thing... 

cheers,
md
 

 -Original Message-
 From: Paul Fremantle [mailto:[EMAIL PROTECTED]
 Sent: Monday, June 25, 2007 11:30 AM
 To: axis-user@ws.apache.org
 Subject: Re: Axis2 and SAML
 
 
 There is an open source identity server based on 
 WS-Trust/SAML and Axis2 here:
 http://wso2.org/projects/solutions/identity
 
 Paul
 
 
 
 On 6/25/07, [EMAIL PROTECTED]
 [EMAIL PROTECTED] wrote:
  Thanks, I'll let you know how it goes.
 
  cheers,
  md
 
 
   -Original Message-
   From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED]
   Sent: Monday, June 25, 2007 11:15 AM
   To: axis-user@ws.apache.org
   Subject: RE: Axis2 and SAML
  
  
   Hi,
  
   Quoting [EMAIL PROTECTED]:
  
Anyway, you say you'd recommend SAML, but you also say 
 you prefer
WS-Trust. I'm a bit confused - I thought SAML was a language for
representing users and their permissions, whereas WS-Trust
   was for
exchanging security tokens. In other words, I thought these
addressed two different classes of use cases.
  
   You can use WS-Trust to exchange SAML2.0 tokens, via the
   RequestTokenType
   element.
  
   If you're able to have a WS-Trust response using axis2, 
 let me know.
  
   I'm trying to implement this: I created the necessary header
   but I'm not
   able to set it in the SOAP response (not using opensaml,
   since the examples
   are not so good, and I don't know where to start).
  
   I use rampart for signing and setting timestamps, but it does
   not work now
   for me (see the previous post).
  
   Cheers,
  
  
  
   
   This message was sent using IMP, the Internet Messaging Program.
  
  
  
   
 -
   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]
 
 
 
 
 -- 
 Paul Fremantle
 Co-Founder and VP of Technical Sales, WSO2
 OASIS WS-RX TC Co-chair
 
 blog: http://pzf.fremantle.org
 [EMAIL PROTECTED]
 
 Oxygenating the Web Service Platform, www.wso2.com
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 

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



Re: Axis2 and SAML

2007-06-25 Thread masi

Hi,

Quoting Paul Fremantle [EMAIL PROTECTED]:

There is an open source identity server based on WS-Trust/SAML and   
Axis2 here:

http://wso2.org/projects/solutions/identity


It is based on SAML1.0 assertion,

PARAM  Name=tokenType
Value=urn:oasis:names:tc:SAML:1.0:assertion

but can be a good example of using Rahas for WS-Trust.

Cheers,

   Massimiliano Masi


This message was sent using IMP, the Internet Messaging Program.



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



Re: text/xml to application/xml trouble

2007-06-25 Thread shale



Thilina Gunarathne wrote:
 
 Hi,
 Earlier Axis2 was treating messages with text/xml as the content-type
 without a SOAPAction http-header as POX messages. Reason was SOAP 1.1,
 which defines content-type of the messages as text/xml and it
 mandates SOAPAction header.
 
 Later with the introduction of WSDL 2.0 support (specifically the
 WSDL2 HTTPBinding support) Axis2 is using the application/xml to treat
 POX messages.. But we kept the text/xml without SOAPAction identified
 as POX mechanism for the sake of backward compatibility.
 
 Please check whether you have the SOAPAction header in your messages...
 
 AxisConfigutator is overriding some of the content-type to builder
 mappings
 to specific builders (application/xml being one of them), so I'm right
 back
 to a Builder that doesn't work.
 It was not supposed to override the user configured builders... Are
 you using Axis2 1.2..
 
Yes I'm using Axis2 1.2.  The axis2.xml settings are being overridden in the
class:
org.apache.axis2.deployment.AxisConfigBuilder.populateConfig as follows

axisConfig.addMessageBuilder(multipart/related, new
MIMEBuilder());
axisConfig.addMessageBuilder(application/soap+xml, new
SOAPBuilder());
axisConfig.addMessageBuilder(text/xml, new SOAPBuilder());
axisConfig.addMessageBuilder(application/xop+xml, new
MTOMBuilder());
// process MessageBuilders
OMElement messageBuildersElement =
config_element.getFirstChildWithName(new
QName(TAG_MESSAGE_BUILDERS));
if (messageBuildersElement != null) {
HashMap builderSelector =
processMessageBuilders(messageBuildersElement);
Iterator keys = builderSelector.keySet().iterator();
while (keys.hasNext()) {
String key = (String) keys.next();
axisConfig.addMessageBuilder(key, (Builder)
builderSelector.get(key));
}
}
// OVERRIDE USER SPECIFED SETTINGS FOR 2 Content-types
axisConfig.addMessageBuilder(application/xml, new
ApplicationXMLBuilder());
   
axisConfig.addMessageBuilder(application/x-www-form-urlencoded,
 new XFormURLEncodedBuilder());


I'm not sure I follow you comments about SOAPAction Header.  Here's what a
typical SOAP request would look like:
SoapEnvelope:Envelope
xmlns:SoapEnvelope=http://schemas.xmlsoap.org/soap/envelope/;
SoapEnvelope:Body
getCustomer
cust-id2276772/cust-id
/getCustomer
/SoapEnvelope:Body
/SoapEnvelope:Envelope
-- 
View this message in context: 
http://www.nabble.com/text-xml-to-application-xml-trouble-tf3974013.html#a11289868
Sent from the Axis - User mailing list archive at Nabble.com.


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



RE: Axis2- question on creating ConfigurationContext

2007-06-25 Thread Chen, John (N-Avatar Inc.)
 

On my Axis2 client, I am using the following code to create
ConfigurationContext so that I can engage the rampart. I understand we
have to use absolute path for the module and axis2.xml. Is there anyway
I can load those from my classpath ? I have an tomcat server running and
I am wondering if I can put those file in a jar file and be part of my
classpath.

 

ConfigurationContext ctx =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(c:
/client_repo, c:/client_repo/conf/axis2.xml);

 

Thanks

 

John



[Axis2] SOAP 1.1 only

2007-06-25 Thread leanne stuive

I have just started using Axis2 to develop web services from Java code.  I
have been creating web services similar to the pojo example.  The WSDL that
is generated contains both SOAP 1.1 and 1.2 bindings.  However, I would like
to create a WSDL that follows only the SOAP 1.1 standards.  Is this
possible?
Thank you in advance,
Leanne


[U] Prebuilt schema objects

2007-06-25 Thread Ridgway, Jamie Mr CONT USAAC
UNCLASSIFIED


First, I have a project using Axis2 to expose some web services. I am
using the WSDL first approach.

Since I have already determined my schemas, I have a separate project in
which I compile my schemas using both XMLBeans and JAXB2. I would like
to use the compliled XMLBeans objects I within my webservice. Is is
possible to use WSDL2Java and specify these pre-built objects instead
of generating new ones?

TIA,

Jamie
UNCLASSIFIED

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



Re: [U] Prebuilt schema objects

2007-06-25 Thread Davanum Srinivas

Jamie,

No, we don't support that yet. Guess, it's not hard to do. We just
have to suppress code generation for specific schemas/package names.
Please log an enhancement request. Easiest work around is that, after
you run wsdl2java, just delete the generated code that you pick up
from the other project.

thanks,
dims

On 6/25/07, Ridgway, Jamie Mr CONT USAAC [EMAIL PROTECTED] wrote:

UNCLASSIFIED


First, I have a project using Axis2 to expose some web services. I am
using the WSDL first approach.

Since I have already determined my schemas, I have a separate project in
which I compile my schemas using both XMLBeans and JAXB2. I would like
to use the compliled XMLBeans objects I within my webservice. Is is
possible to use WSDL2Java and specify these pre-built objects instead
of generating new ones?

TIA,

Jamie
UNCLASSIFIED

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





--
Davanum Srinivas :: http://davanum.wordpress.com

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



RE: [Axis2] org.apache.axis2.AxisFault: First Element must contain the local name, Envelope

2007-06-25 Thread Raghu Upadhyayula
Hi Dims,

I've attached a zip file to the JIRA (AXIS2-2352) which has my
client code  the wsdl file.  Please let me know if I should upload
anything else.

Thanks
Raghu

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Friday, June 22, 2007 6:51 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] org.apache.axis2.AxisFault: First Element must
contain the local name, Envelope

Looks similar to this one -
http://issues.apache.org/jira/browse/AXIS2-2352

Can you please zip up your sample and upload it too?

thanks,
dims

On 6/22/07, Raghu Upadhyayula [EMAIL PROTECTED] wrote:




 Hi,



 When I deploy my webservices on my localhost (desktop) and
test
 it using a java client, it is working fine.



 But when the same webservices project is built  deployed
on our
 development server and tested using java client, I'm getting the below
 exception.



 org.apache.axis2.AxisFault: First Element must contain the local name,
 Envelope

 First Element must contain the local name, Envelope

 org.apache.axis2.AxisFault: First Element must contain the local name,
 Envelope

 at

org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUti
ls.java:81)

 at

org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper
ation.java:356)

 at

org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO
peration.java:294)

 at

com.rsys.ws.client.ResponsysWSServiceStub.login(ResponsysWSServiceStub.j
ava:276)

 at
 com.rsys.ws.samples.TestRILoginCmd.execute(TestRILoginCmd.java:29)

 at
 com.rsys.ws.samples.TestRILoginCmd.execute(TestRILoginCmd.java:16)

 at

com.rsys.ws.samples.TestResponsysWSClient.main(TestResponsysWSClient.jav
a:40)

 Caused by: org.apache.axiom.soap.SOAPProcessingException:
 First Element must contain the local name, Envelope

 at

org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode(St
AXSOAPModelBuilder.java:221)

 at

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

 at

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

 at

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

 at

org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.init(StAXSOAPM
odelBuilder.java:111)

 at

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

 at

org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUti
ls.java:142)

 at

org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUti
ls.java:77)

 ... 6 more



 Does anyone tell me why this is happening?



 I'm using Axis2 deployed in Jboss.



 Thanks

 Raghu




-- 
Davanum Srinivas :: http://davanum.wordpress.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]



Simple Axis2 service in transport session scope, which method is called with each request?

2007-06-25 Thread fat suze

I sent this on Saturday but I'm pretty sure it didn't make it through to the
list.  I'm sorry if this is a repeat post.

-- Forwarded message --
From: fat suze [EMAIL PROTECTED]
Date: Jun 23, 2007 9:28 PM
Subject: Simple Axis2 service in transport session scope, which method is
called with each request?
To: axis-user@ws.apache.org

I'm trying to find a method that is called every time my service is
accessed.  There is init(ServiceContext) and destroy(ServiceContext) that is
called at the start of each session, but that doesn't help (at least in
transport scope - because that is called at the start/end of each session I
believe).

After hours of googling, I've found mention of two things that don't seem to
actually exist anymore (I assume they did at some point in time) -

1) init(MessageContext), which was mentioned on
http://www.developer.com/open/print.php/10930_3589126_3

and

2) public void setOperationContext(OperationContext operationContext) which
is mentioned at http://www.developer.com/java/web/article.php/3620661

Neither of these seem to work, but obviously there is some simple way to do
something before each operation I just can't find the documentation on
it!

Please help, thanks

Susie


Sessions

2007-06-25 Thread Jorge Fernandez
Hi,

Has axis2 any timeout managing similar as the client, when is used at the 
server side? I tried with SessionContext but I couldn't get it working.

Thanks and regards,

Jorge Fernández


  

   
-

¡Descubre una nueva forma de obtener respuestas a tus preguntas!
Entra en Yahoo! Respuestas.


RE: Simple Axis2 service in transport session scope, which method is called with each request?

2007-06-25 Thread Ebert, Chris
You should be able to get what you want by implementing a Handler and
adding it to the chain. I use Axis 1.2, so maybe it's a little out of
date, but in the ~.wsdd file you can configure handler objects that are
executed in sequence whenever a request comes in. There are a couple of
places, the 'requestFlow' and 'responseFlow' sections seem likely.

Chris 

-Original Message-
From: fat suze [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 25, 2007 10:59
To: axis-user@ws.apache.org
Subject: Simple Axis2 service in transport session scope, which method
is called with each request?

I sent this on Saturday but I'm pretty sure it didn't make it through to
the list.  I'm sorry if this is a repeat post.

-- Forwarded message --
From: fat suze [EMAIL PROTECTED]
Date: Jun 23, 2007 9:28 PM
Subject: Simple Axis2 service in transport session scope, which method
is called with each request?
To: axis-user@ws.apache.org mailto:axis-user@ws.apache.org 


I'm trying to find a method that is called every time my service is
accessed.  There is init(ServiceContext) and destroy(ServiceContext)
that is called at the start of each session, but that doesn't help (at
least in transport scope - because that is called at the start/end of
each session I believe). 
 
After hours of googling, I've found mention of two things that don't
seem to actually exist anymore (I assume they did at some point in time)
- 
 
1) init(MessageContext), which was mentioned on
http://www.developer.com/open/print.php/10930_3589126_3 
 
and
 
2) public void setOperationContext(OperationContext operationContext)
which is mentioned at
http://www.developer.com/java/web/article.php/3620661
http://www.developer.com/java/web/article.php/3620661 
 
Neither of these seem to work, but obviously there is some simple way to
do something before each operation I just can't find the
documentation on it!
 
Please help, thanks
 
Susie

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



Re: SOAP response

2007-06-25 Thread Demetris G


Hi Jeff,

   in fact it didn't - for some strange reason the Content-Length comes 
in as -1 althought the
SOAP response is 2000 characters. So I simply re-send it myself after I 
read the response.
And now to the good part - I managed to figure out the issue of the 
Client stalling - as
silly as it sounds, I need to simply close the socket once I am done 
writing to it and voila
the Client accepts the complete message and it is happy. The parsing 
issue that I had
originally is a mystery cause it has not appeared again. So I guess I 
will need to open the
socket to write and then close it once I am done for all the RPC calls 
to and from the

Client. Sounds strange ? Well it works :)

   Jeff - thanks for all the help and insights so far - I appreciate it 
and I will continue to

keep you and the list updated on these adventures as we are all learning.

Walker, Jeff wrote:

Demetris G,
Time for me to ask a stupid question.
Does the value of the Content-Length:  http header of your response
match the length of all of the actual sent characters?
-jeff


-Original Message-
From: Demetris G [mailto:[EMAIL PROTECTED] 
Sent: Saturday, June 23, 2007 10:33 PM

To: axis-user@ws.apache.org
Subject: Re: SOAP response


Hi all,
   
is it possible that no one working with Axis for a while now knows 
what terminates
the SOAP message coming from the server engine ?? Anyone ? I will 
appreciate it.
Nothing shows up in the tcpmon or any other tool I used however the SAX 
parser
see the complete SOAP envelope as shown below but yet it block waiting 
for something
else. What is this extra data that it is expecting ? I am sifting 
through the Axis/SAX

classes but it takes a long time to chase this.

Thanks much

Demetris G wrote:
  

Jeff -- I traced the SAX and Xerces routines to find out what they are



  

doing but it
gets a bit hectic to figure them out. I know the client reads back the



  

headers I send
it and all of the SOAP message below (if for example I mispell the 
last tag of the SOAP
message then SAX is complaining which means it does parse it till 
them). But the parser
is stuck on SocketInputStream.read() as if it is expecting more after 
the last tag of the

SOAP message - I tried CR / LF but that does not do it.

Any suggestions ??

  ?xml version=\1.0\ encoding=\UTF-8\?
 soapenv:Envelope 
xmlns:soapenv=\http://schemas.xmlsoap.org/soap/envelope/\; 
 
xmlns:xsd=\http://www.w3.org/2001/XMLSchema\; 
 
xmlns:xsi=\http://www.w3.org/2001/XMLSchema-instance\;

 soapenv:Body
 ns1:getBundlesResponse 
soapenv:encodingStyle=\
 
http://schemas.xmlsoap.org/soap/encoding/\; 
 
xmlns:ns1=\http://soapobject.bundle.org\;
 getBundlesReturn 
soapenc:arrayType=\xsd:long[24]\ xsi:type=\soapenc:Array\ 
 
xmlns:soapenc=\http://schemas.xmlsoap.org/soap/encoding/\;
 getBundlesReturn 
href=\#id23\/

 /getBundlesReturn
 /ns1:getBundlesResponse
 multiRef id=\id23\ 
soapenc:root=\0\ 
 
soapenv:encodingStyle=\http://schemas.xmlsoap.org/soap/encoding/\; 
 xsi:type=\xsd:long\ 
xmlns:soapenc=\http://schemas.xmlsoap.org/soap/encoding/\;

 3
 /multiRef
 /soapenv:Body
 /soapenv:Envelope;


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





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




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



  


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



Re: [Axis2] Axis2 client message different to Axis1 client messag e

2007-06-25 Thread Davanum Srinivas

Alick,

Did you try the suppress-prefixes option in WSDL2Java?

http://svn.apache.org/viewvc?view=revrevision=480336
https://issues.apache.org/jira/browse/AXIS2-1784

thanks,
dims

On 6/25/07, Anne Thomas Manes [EMAIL PROTECTED] wrote:

Alick,

What exactly is your question?

The messages are semantically equivalent.

Anne


On 6/25/07, Alick Buckley  [EMAIL PROTECTED] wrote:


 Hi,

 If I use the original test WSDL with the .NET WebService Studio Tool, the
SOAP message is the same as Axis 1.4 ?

 Microsoft .NET WebService Studio Tool

 ?xml version=1.0 encoding=utf-8?
 soap:Envelope
xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;
 xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
 soap:Body
 getNumber xmlns=http://soap.service.acme.com;
 param1
 a_int
 item23/item
 /a_int
 n_double23.45/n_double
 n_float56.78/n_float
 n_int876/n_int
 n_long284849/n_long
 o_biginteger48484/o_biginteger
 /param1
 /getNumber
 /soap:Body
 /soap:Envelope

 Axis 1.4


 ?xml version=1.0 encoding=utf-8?
 soapenv:Envelope
 xmlns:soapenv=
http://schemas.xmlsoap.org/soap/envelope/;
 xmlns:xsd= http://www.w3.org/2001/XMLSchema;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance 
 soapenv:Body
 getNumber xmlns=http://soap.service.acme.com;
 param1
 a_int
 item123/item
 item456/item
 /a_int
 n_double20.1/n_double
 n_float21.11/n_float
 n_int22/n_int
 n_long22345678/n_long
 o_bigdecimal223.546/o_bigdecimal
 o_biginteger22385943/o_biginteger
 o_double2435.456/o_double
 o_int23245/o_int
 /param1
 /getNumber
 /soapenv:Body
 /soapenv:Envelope


=

 -Original Message-
 From: Alick Buckley [mailto:[EMAIL PROTECTED]
 Sent: Monday, 25 June 2007 4:15 PM
 To: axis-user@ws.apache.org

 Subject: RE: [Axis2] Axis2 client message different to Axis1 client messag
e



 Hi,

 If the elementFormDefault is set to unqualified then the SOAP message does
not have the namespace prefixes.

 But the getNumber element has a namespace prefix, but there is no default
namespace ?

 schema elementFormDefault=unqualified
targetNamespace= http://soap.service.acme.com;
xmlns=http://www.w3.org/2001/XMLSchema;


===

 ?xml version=1.0 encoding=utf-8?
 soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ 
 soapenv:Body
 ns1:getNumber xmlns:ns1=http://soap.service.acme.com 
 param1
 a_int
 item2/item
 item3/item
 item4/item
 /a_int
 n_double22.5/n_double
 n_float23.4/n_float
 n_int123/n_int
 n_long3456/n_long
 o_bigdecimal567.67/o_bigdecimal
 o_biginteger98765/o_biginteger
 o_double345.67/o_double
 o_int7585/o_int
 /param1
 /ns1:getNumber
 /soapenv:Body
 /soapenv:Envelope


===

 -Original Message-
 From: Alick Buckley [mailto:[EMAIL PROTECTED]
 Sent: Monday, 25 June 2007 3:50 PM
 To: axis-user@ws.apache.org
 Subject: [Axis2] Axis2 client message different to Axis1 client message




 Hi,

 I am using the same test WSDL for an Axis 1.4 generated client and an
Axis2 1.2 generated client.

 The Axis2 1.2 is qualifying the elements with a namespace prefix ?


=

 Axis2 1.2

 ?xml version=1.0 encoding=utf-8?
 soapenv:Envelope xmlns:soapenv=
http://schemas.xmlsoap.org/soap/envelope/;
 soapenv:Body
 ns1:getNumber xmlns:ns1=http://soap.service.acme.com;
 ns1:param1
 ns1:a_int
 ns1:item2/ns1:item
 ns1:item3/ns1:item
 ns1:item4/ns1:item
 /ns1:a_int
 ns1:n_double22.5/ns1:n_double
 ns1:n_float23.4/ns1:n_float
 ns1:n_int123/ns1:n_int
 ns1:n_long3456/ns1:n_long
 ns1:o_bigdecimal567.67/ns1:o_bigdecimal

ns1:o_biginteger98765/ns1:o_biginteger
 ns1:o_double345.67/ns1:o_double
 ns1:o_int7585/ns1:o_int
 /ns1:param1
 /ns1:getNumber
 /soapenv:Body
 /soapenv:Envelope


=

 Axis 1.4

 ?xml version=1.0 

RE: [Axis2] org.apache.axis2.AxisFault: First Element must contain the local name, Envelope

2007-06-25 Thread Raghu Upadhyayula
Hi Dims,

 

  I've tried to get the request  response SOAP messages for this
request.  Here is the request  response for this.

  

  Any idea why I'm getting a NPE in AxisServlet.

 

 

Dev-Orion Login SOAP Request

POST /webservices/services/ResponsysWSService HTTP/1.1

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

SOAPAction: 

User-Agent: Axis2

Host: dev-orion.corp.responsys.com:1234

Transfer-Encoding: chunked

 

119

?xml version='1.0' encoding='UTF-8'?

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

soapenv:Body

ns1:login xmlns:ns1=urn:ws.rsys.com

ns1:usernameraghu/ns1:username

ns1:passwordraghu/ns1:password

/ns1:login

/soapenv:Body

/soapenv:Envelope

0

 

Dev-Orion Login SOAP Response

HTTP/1.1 500 Internal Server Error

Server: Apache-Coyote/1.1

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

Content-Length: 1453

Date: Mon, 25 Jun 2007 18:06:51 GMT

Connection: close

 

html

head

titleJBossWeb/2.0.0.GA - Error report/title

style

!--

H1
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D7
6;font-size:22px;} 

H2
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D7
6;font-size:16px;} 

H3
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D7
6;font-size:14px;} 

BODY
{font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;
} 

B
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D7
6;} 

P
{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-s
ize:12px;}

A {color : black;}A.name {color : black;}HR {color :
#525D76;}

--

/style

/head

body

h1HTTP Status 500 - /h1

HR size=1 noshade=noshade

pbtype/b Exception report/p

pbmessage/b u/u/p

p

bdescription/b 

uThe server encountered an internal error () that
prevented it from fulfilling this request./u

/p

p

bexception/b

pre

java.lang.NullPointerException

 
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:170)

 
javax.servlet.http.HttpServlet.service(HttpServlet.java:710)

 
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

 
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilte
r.java:96)

/pre

/p

p

bnote/b 

uThe full stack trace of the root cause is available in the
JBossWeb/2.0.0.GA logs./u

/p

HR size=1 noshade=noshade

h3JBossWeb/2.0.0.GA/h3

/body

/html

 

Thanks

Raghu

 

-Original Message-
From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 25, 2007 10:26 AM
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: RE: [Axis2] org.apache.axis2.AxisFault: First Element must
contain the local name, Envelope

 

Hi Dims,

 

  I've attached a zip file to the JIRA (AXIS2-2352) which has my

client code  the wsdl file.  Please let me know if I should upload

anything else.

 

Thanks

Raghu

 

-Original Message-

From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 

Sent: Friday, June 22, 2007 6:51 PM

To: axis-user@ws.apache.org

Subject: Re: [Axis2] org.apache.axis2.AxisFault: First Element must

contain the local name, Envelope

 

Looks similar to this one -

http://issues.apache.org/jira/browse/AXIS2-2352

 

Can you please zip up your sample and upload it too?

 

thanks,

dims

 

On 6/22/07, Raghu Upadhyayula [EMAIL PROTECTED] wrote:

 

 

 

 

 Hi,

 

 

 

 When I deploy my webservices on my localhost (desktop) and

test

 it using a java client, it is working fine.

 

 

 

 But when the same webservices project is built  deployed

on our

 development server and tested using java client, I'm getting the below

 exception.

 

 

 

 org.apache.axis2.AxisFault: First Element must contain the local name,

 Envelope

 

 First Element must contain the local name, Envelope

 

 org.apache.axis2.AxisFault: First Element must contain the local name,

 Envelope

 

 at

 

org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUti

ls.java:81)

 

 at

 

org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper

ation.java:356)

 

 at

 

org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO

peration.java:294)

 

 at

 

com.rsys.ws.client.ResponsysWSServiceStub.login(ResponsysWSServiceStub.j

ava:276)

 

 at

 com.rsys.ws.samples.TestRILoginCmd.execute(TestRILoginCmd.java:29)

 

 at

 com.rsys.ws.samples.TestRILoginCmd.execute(TestRILoginCmd.java:16)

 

 at

 

com.rsys.ws.samples.TestResponsysWSClient.main(TestResponsysWSClient.jav

a:40)

 

 Caused by: 

Classpath Problem

2007-06-25 Thread Swavek Skret
When deploying the axis2.war I get the following error in the Tomcat log:

2007-06-25 12:19:36,018 ERROR org.apache.axis2.transport.http.AxisServlet -
java.lang.LinkageError: loader constraint violation: loader (instance of
org/apache/axis2/deployment/DeploymentClassLoader) previously initiated
loading for a different type with name javax/jms/QueueConnection

It is possibly related to the classpath changes I did in my Tomcat settings.
When creating the aar file, I added the lib directory that included my 3rd
party jar. However, I got a class not found exceptions so I changed Tomcat
shared.loader classpath and added my 3rd party jars to it but now  I am
getting the above error.

Does anyone have any idea of how to fix it?

Thanks,

Swavek




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



axis + tomcat tuning issue

2007-06-25 Thread Gabriela Gheorghe

Hi everybody,

I am facing a stress-testing problem using Tomcat 5.5 and Axis 1.4, and I
really need some ideas about what is happening behind the scenes.

This is the configuration: a few web services hosted on Axis 1.4 are
deployed on Tomcat. Everything runs on 2 Linux Pentium 4 machines (with
hyperthreading), one as client using Jmeter, the other one as server.

The problem is that I cannot run as many / time-consuming requests so that
the processor on the server reaches 100% CPU load. It only reaches 90%, so
the measurements for throughput that I  need to obtain by this testing,
cannot be too relevant; I want 100% of the CPU working.

So my question would be  - why is 10% of the CPU idle ? I should mention
that I already did a few performance tweaks, for the JVM memory, and
decreased the connection timeout for Tomcat to a few dozen milliseconds.
Still, it doesn;t reach 100% load, although I varied request message length,
and thread numbers.

If you have any ideas, please help.

Gabriela

--
Kind regards / Freundliche Gruesse,
Gabriela Gheorghe

Email: [EMAIL PROTECTED] / [EMAIL PROTECTED]


RE: SOAP response

2007-06-25 Thread Walker, Jeff
Excellent!
Congrats on working it out.
-jeff


-Original Message-
From: Demetris G [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 25, 2007 2:20 PM
To: axis-user@ws.apache.org
Subject: Re: SOAP response


Hi Jeff,

in fact it didn't - for some strange reason the Content-Length comes

in as -1 althought the
SOAP response is 2000 characters. So I simply re-send it myself after I 
read the response.
And now to the good part - I managed to figure out the issue of the 
Client stalling - as
silly as it sounds, I need to simply close the socket once I am done 
writing to it and voila
the Client accepts the complete message and it is happy. The parsing 
issue that I had
originally is a mystery cause it has not appeared again. So I guess I 
will need to open the
socket to write and then close it once I am done for all the RPC calls 
to and from the
Client. Sounds strange ? Well it works :)

Jeff - thanks for all the help and insights so far - I appreciate it

and I will continue to
keep you and the list updated on these adventures as we are all
learning.

Walker, Jeff wrote:
 Demetris G,
 Time for me to ask a stupid question.
 Does the value of the Content-Length:  http header of your response
 match the length of all of the actual sent characters?
 -jeff


 -Original Message-
 From: Demetris G [mailto:[EMAIL PROTECTED] 
 Sent: Saturday, June 23, 2007 10:33 PM
 To: axis-user@ws.apache.org
 Subject: Re: SOAP response


 Hi all,

 is it possible that no one working with Axis for a while now knows

 what terminates
 the SOAP message coming from the server engine ?? Anyone ? I will 
 appreciate it.
 Nothing shows up in the tcpmon or any other tool I used however the
SAX 
 parser
 see the complete SOAP envelope as shown below but yet it block waiting

 for something
 else. What is this extra data that it is expecting ? I am sifting 
 through the Axis/SAX
 classes but it takes a long time to chase this.

 Thanks much

 Demetris G wrote:
   
 Jeff -- I traced the SAX and Xerces routines to find out what they
are
 

   
 doing but it
 gets a bit hectic to figure them out. I know the client reads back
the
 

   
 headers I send
 it and all of the SOAP message below (if for example I mispell the 
 last tag of the SOAP
 message then SAX is complaining which means it does parse it till 
 them). But the parser
 is stuck on SocketInputStream.read() as if it is expecting more after

 the last tag of the
 SOAP message - I tried CR / LF but that does not do it.

 Any suggestions ??

   ?xml version=\1.0\ encoding=\UTF-8\?
  soapenv:Envelope 
 xmlns:soapenv=\http://schemas.xmlsoap.org/soap/envelope/\; 
  
 xmlns:xsd=\http://www.w3.org/2001/XMLSchema\; 
  
 xmlns:xsi=\http://www.w3.org/2001/XMLSchema-instance\;
  soapenv:Body
  ns1:getBundlesResponse 
 soapenv:encodingStyle=\
  
 http://schemas.xmlsoap.org/soap/encoding/\; 
  
 xmlns:ns1=\http://soapobject.bundle.org\;
  getBundlesReturn 
 soapenc:arrayType=\xsd:long[24]\ xsi:type=\soapenc:Array\ 
  
 xmlns:soapenc=\http://schemas.xmlsoap.org/soap/encoding/\;
  getBundlesReturn 
 href=\#id23\/
  /getBundlesReturn
  /ns1:getBundlesResponse
  multiRef id=\id23\ 
 soapenc:root=\0\ 
  
 soapenv:encodingStyle=\http://schemas.xmlsoap.org/soap/encoding/\;

  xsi:type=\xsd:long\ 
 xmlns:soapenc=\http://schemas.xmlsoap.org/soap/encoding/\;
  3
  /multiRef
  /soapenv:Body
  /soapenv:Envelope;


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


 

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




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



   

-
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 + tomcat tuning issue

2007-06-25 Thread Michele Mazzucco


On 25 Jun 2007, at 19:33, Gabriela Gheorghe wrote:

The problem is that I cannot run as many / time-consuming requests  
so that
the processor on the server reaches 100% CPU load. It only reaches  
90%, so

the measurements for throughput that I need to obtain by this testing,
cannot be too relevant; I want 100% of the CPU working.


Are you sure that the bottleneck is not the client?


So my question would be - why is 10% of the CPU idle ?


Couldn't it be because of I/O?



Michele



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



RE: WSDL2Java for HTTPS

2007-06-25 Thread Mark Babcock
I did everything you listed step by step and this is the stack trace I
get:

[axis-wsdl2java] javax.net.ssl.SSLHandshakeException:
sun.security.validator.Val
idatorException: PKIX path building failed:
sun.security.provider.certpath.SunCe
rtPathBuilderException: unable to find valid certification path to
requested tar
get
[axis-wsdl2java]at
com.sun.net.ssl.internal.ssl.Alerts.getSSLException(A
lerts.java:174)
[axis-wsdl2java]at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLS
ocketImpl.java:1520)
[axis-wsdl2java]at
com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Hands
haker.java:182)
[axis-wsdl2java]at
com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Hands
haker.java:176)
[axis-wsdl2java]at
com.sun.net.ssl.internal.ssl.ClientHandshaker.serverC
ertificate(ClientHandshaker.java:975)
[axis-wsdl2java]at
com.sun.net.ssl.internal.ssl.ClientHandshaker.process
Message(ClientHandshaker.java:123)
[axis-wsdl2java]at
com.sun.net.ssl.internal.ssl.Handshaker.processLoop(H
andshaker.java:511)
[axis-wsdl2java]at
com.sun.net.ssl.internal.ssl.Handshaker.process_recor
d(Handshaker.java:449)
[axis-wsdl2java]at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord
(SSLSocketImpl.java:817)
[axis-wsdl2java]at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.performIni
tialHandshake(SSLSocketImpl.java:1029)
[axis-wsdl2java]at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHands
hake(SSLSocketImpl.java:1056)
[axis-wsdl2java]at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHands
hake(SSLSocketImpl.java:1040)
[axis-wsdl2java]at
sun.net.www.protocol.https.HttpsClient.afterConnect(H
ttpsClient.java:405)
[axis-wsdl2java]at
sun.net.www.protocol.https.AbstractDelegateHttpsURLCo
nnection.connect(AbstractDelegateHttpsURLConnection.java:170)
[axis-wsdl2java]at
sun.net.www.protocol.http.HttpURLConnection.getInputS
tream(HttpURLConnection.java:981)
[axis-wsdl2java]at
sun.net.www.protocol.https.HttpsURLConnectionImpl.get
InputStream(HttpsURLConnectionImpl.java:234)
[axis-wsdl2java]at
org.apache.xerces.impl.XMLEntityManager.setupCurrentE
ntity(Unknown Source)
[axis-wsdl2java]at
org.apache.xerces.impl.XMLVersionDetector.determineDo
cVersion(Unknown Source)
[axis-wsdl2java]at
org.apache.xerces.parsers.XML11Configuration.parse(Un
known Source)
[axis-wsdl2java]at
org.apache.xerces.parsers.XML11Configuration.parse(Un
known Source)
[axis-wsdl2java]at
org.apache.xerces.parsers.XMLParser.parse(Unknown Sou
rce)
[axis-wsdl2java]at
org.apache.xerces.parsers.DOMParser.parse(Unknown Sou
rce)
[axis-wsdl2java]at
org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unkn
own Source)
[axis-wsdl2java]at
org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.j
ava:369)
[axis-wsdl2java]at
org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.j
ava:420)
[axis-wsdl2java]at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate
(SymbolTable.java:482)
[axis-wsdl2java]at
org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Pars
er.java:361)
[axis-wsdl2java]at java.lang.Thread.run(Thread.java:619)
[axis-wsdl2java] Caused by: sun.security.validator.ValidatorException:
PKIX path
 building failed:
sun.security.provider.certpath.SunCertPathBuilderException: un
able to find valid certification path to requested target
[axis-wsdl2java]at
sun.security.validator.PKIXValidator.doBuild(PKIXVali
dator.java:285)
[axis-wsdl2java]at
sun.security.validator.PKIXValidator.engineValidate(P
KIXValidator.java:191)
[axis-wsdl2java]at
sun.security.validator.Validator.validate(Validator.j
ava:218)
[axis-wsdl2java]at
com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.val
idate(X509TrustManagerImpl.java:126)
[axis-wsdl2java]at
com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.che
ckServerTrusted(X509TrustManagerImpl.java:209)
[axis-wsdl2java]at
com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.che
ckServerTrusted(X509TrustManagerImpl.java:249)
[axis-wsdl2java]at
com.sun.net.ssl.internal.ssl.ClientHandshaker.serverC
ertificate(ClientHandshaker.java:954)
[axis-wsdl2java]... 23 more
[axis-wsdl2java] Caused by:
sun.security.provider.certpath.SunCertPathBuilderExc
eption: unable to find valid certification path to requested target
[axis-wsdl2java]at
sun.security.provider.certpath.SunCertPathBuilder.eng
ineBuild(SunCertPathBuilder.java:174)
[axis-wsdl2java]at
java.security.cert.CertPathBuilder.build(CertPathBuil
der.java:238)
[axis-wsdl2java]at
sun.security.validator.PKIXValidator.doBuild(PKIXVali
dator.java:280)
[axis-wsdl2java]... 29 more
-Original Message-
From: r1c4r60 [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 25, 2007 10:57 AM
To: axis-user@ws.apache.org
Subject: RE: WSDL2Java for HTTPS


Hi Mark,

Most likely you haven't set the Axis Classpath. It could be done in
several
different 

[Axis2] Ending a transport session

2007-06-25 Thread Scott Pelton

I am using transportsession scopre in my web service. I want to
end the session when the user calls a logout service. I am having a
difficult time finding out how to accomplish this seemingly simple task.



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



RE: WSDL2Java for HTTPS

2007-06-25 Thread r1c4r60

Hi,

Certificates for IP addresses will not work

Quite simply, issuing and using certificates that authenticate IP addresses
rather than host names will not work. Don't do it. For anything larger than
a trivial installation, your CAS server and its clients need real hostnames
and certificates that authenticate those hostnames (for proxy ticket
functionality). In particular, if you get an error like (unable to find
valid certification path to requested target) in the CAS server log, it
means that the SSL callback was specified in terms of an IP address rather
than a hostname.

Quoted from: http://www.ja-sig.org/products/cas/server/ssl/index.html

Does this seem to be your case?

Regards,
Ricardo


Mark Babcock-3 wrote:
 
 I did everything you listed step by step and this is the stack trace I
 get:
 
 [axis-wsdl2java] javax.net.ssl.SSLHandshakeException:
 sun.security.validator.Val
 idatorException: PKIX path building failed:
 sun.security.provider.certpath.SunCe
 rtPathBuilderException: unable to find valid certification path to
 requested tar
 get
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.Alerts.getSSLException(A
 lerts.java:174)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLS
 ocketImpl.java:1520)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Hands
 haker.java:182)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Hands
 haker.java:176)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.ClientHandshaker.serverC
 ertificate(ClientHandshaker.java:975)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.ClientHandshaker.process
 Message(ClientHandshaker.java:123)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.Handshaker.processLoop(H
 andshaker.java:511)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.Handshaker.process_recor
 d(Handshaker.java:449)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord
 (SSLSocketImpl.java:817)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.SSLSocketImpl.performIni
 tialHandshake(SSLSocketImpl.java:1029)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHands
 hake(SSLSocketImpl.java:1056)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHands
 hake(SSLSocketImpl.java:1040)
 [axis-wsdl2java]at
 sun.net.www.protocol.https.HttpsClient.afterConnect(H
 ttpsClient.java:405)
 [axis-wsdl2java]at
 sun.net.www.protocol.https.AbstractDelegateHttpsURLCo
 nnection.connect(AbstractDelegateHttpsURLConnection.java:170)
 [axis-wsdl2java]at
 sun.net.www.protocol.http.HttpURLConnection.getInputS
 tream(HttpURLConnection.java:981)
 [axis-wsdl2java]at
 sun.net.www.protocol.https.HttpsURLConnectionImpl.get
 InputStream(HttpsURLConnectionImpl.java:234)
 [axis-wsdl2java]at
 org.apache.xerces.impl.XMLEntityManager.setupCurrentE
 ntity(Unknown Source)
 [axis-wsdl2java]at
 org.apache.xerces.impl.XMLVersionDetector.determineDo
 cVersion(Unknown Source)
 [axis-wsdl2java]at
 org.apache.xerces.parsers.XML11Configuration.parse(Un
 known Source)
 [axis-wsdl2java]at
 org.apache.xerces.parsers.XML11Configuration.parse(Un
 known Source)
 [axis-wsdl2java]at
 org.apache.xerces.parsers.XMLParser.parse(Unknown Sou
 rce)
 [axis-wsdl2java]at
 org.apache.xerces.parsers.DOMParser.parse(Unknown Sou
 rce)
 [axis-wsdl2java]at
 org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unkn
 own Source)
 [axis-wsdl2java]at
 org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.j
 ava:369)
 [axis-wsdl2java]at
 org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.j
 ava:420)
 [axis-wsdl2java]at
 org.apache.axis.wsdl.symbolTable.SymbolTable.populate
 (SymbolTable.java:482)
 [axis-wsdl2java]at
 org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Pars
 er.java:361)
 [axis-wsdl2java]at java.lang.Thread.run(Thread.java:619)
 [axis-wsdl2java] Caused by: sun.security.validator.ValidatorException:
 PKIX path
  building failed:
 sun.security.provider.certpath.SunCertPathBuilderException: un
 able to find valid certification path to requested target
 [axis-wsdl2java]at
 sun.security.validator.PKIXValidator.doBuild(PKIXVali
 dator.java:285)
 [axis-wsdl2java]at
 sun.security.validator.PKIXValidator.engineValidate(P
 KIXValidator.java:191)
 [axis-wsdl2java]at
 sun.security.validator.Validator.validate(Validator.j
 ava:218)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.val
 idate(X509TrustManagerImpl.java:126)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.che
 ckServerTrusted(X509TrustManagerImpl.java:209)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.che
 ckServerTrusted(X509TrustManagerImpl.java:249)
 [axis-wsdl2java]at
 

Client configuration for web apps?

2007-06-25 Thread Michael.Davis
Hi,

I've got an axis client that I want to distribute as a jar file that can then 
be used by various web applications. So far it works.

But now I want to add the rampart module. In order to use rampart, I have to 
add a line to axis2.xml. I'm having trouble getting the client-side axis 
library to see my axis2.xml file rather than the one that's packed in 
axis2-kernel.jar.

I know I could force the issue by unpacking axis2-kernel.jar, removing 
axis2.xml, then repacking it, but I know that there must be an easier way.

The samples that came with rampart all load the file using 
ConfigurationContextFactory.createConfigurationContextFromFileSystem(), but 
obviously I can't use that.

I'm sure that the next stumbling block will be figuring out how to tell axis 
where the repository is that contains the rampart module, in the context of a 
web app.

Many thanks,
Michael Davis
 

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



duplicate fault elements in generated wsdl

2007-06-25 Thread Hans Benedict

Hi,

I am building a simple POJO based web service offering two methods which 
both throw the same custom exception:


public String getA(String x) throws WsException {...}

public String getB(String y) throws WsException {...}

WsException is extending AxisFault.

The generated wsdl file (.../axis2/services/ab?wsdl - see attachment) 
then contains *two* elements named WsExceptionFault. On validation of 
the file this leads to an error:
Duplicate key value [WsExceptionFault] declared for identity constraint 
element of element schema.


Is this a bug or am I missing something?

My environment:
axis2 1.2
tomcat 5.5.23
jdk-1_5_0_11
debian sarge

Kind regards,
Hans Benedict

--
Hans Benedict   | Freie Universität Berlin
   | Zentraleinrichtung für Datenverarbeitung
Tel.  : +49 30 838 56531| FU Directory and Identity Service (FUDIS)
Fax.  : +49 30 838 56721| Fabeckstr. 32, 14195 Berlin, Germany

wsdl:definitions xmlns:axis2=http://test.ws.cms.zedat.de;
	xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/;
	xmlns:ns0=http://test.ws.cms.zedat.de/xsd;
	xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/;
	xmlns:http=http://schemas.xmlsoap.org/wsdl/http/;
	xmlns:ns1=http://org.apache.axis2/xsd;
	xmlns:xs=http://www.w3.org/2001/XMLSchema;
	xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
	xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
	targetNamespace=http://test.ws.cms.zedat.de;
	wsdl:documentationab/wsdl:documentation
	wsdl:types
		xs:schema xmlns:ns=http://test.ws.cms.zedat.de/xsd;
			attributeFormDefault=qualified elementFormDefault=qualified
			targetNamespace=http://test.ws.cms.zedat.de/xsd;
			xs:element name=WsExceptionFault
xs:complexType
	xs:sequence
		xs:element name=WsException nillable=true
			type=ns:WsException /
	/xs:sequence
/xs:complexType
			/xs:element
			xs:element name=WsException type=ns:WsException /
			xs:complexType name=WsException
xs:sequence /
			/xs:complexType
			xs:element name=getA
xs:complexType
	xs:sequence
		xs:element name=x nillable=true
			type=xs:string /
	/xs:sequence
/xs:complexType
			/xs:element
			xs:element name=getAResponse
xs:complexType
	xs:sequence
		xs:element name=return nillable=true
			type=xs:string /
	/xs:sequence
/xs:complexType
			/xs:element
			xs:element name=WsExceptionFault
xs:complexType
	xs:sequence
		xs:element name=WsException nillable=true
			type=ns:WsException /
	/xs:sequence
/xs:complexType
			/xs:element
			xs:element name=getB
xs:complexType
	xs:sequence
		xs:element name=y nillable=true
			type=xs:string /
	/xs:sequence
/xs:complexType
			/xs:element
			xs:element name=getBResponse
xs:complexType
	xs:sequence
		xs:element name=return nillable=true
			type=xs:string /
	/xs:sequence
/xs:complexType
			/xs:element
		/xs:schema
	/wsdl:types
	wsdl:message name=getBMessage
		wsdl:part name=part1 element=ns0:getB /
	/wsdl:message
	wsdl:message name=getBResponse
		wsdl:part name=part1 element=ns0:getBResponse /
	/wsdl:message
	wsdl:message name=getBFault
		wsdl:part name=part1 element=ns0:WsExceptionFault /
	/wsdl:message
	wsdl:message name=getAMessage
		wsdl:part name=part1 element=ns0:getA /
	/wsdl:message
	wsdl:message name=getAResponse
		wsdl:part name=part1 element=ns0:getAResponse /
	/wsdl:message
	wsdl:message name=getAFault
		wsdl:part name=part1 element=ns0:WsExceptionFault /
	/wsdl:message
	wsdl:portType name=abPortType
		wsdl:operation name=getB
			wsdl:input
xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl;
message=axis2:getBMessage wsaw:Action=urn:getB /
			wsdl:output message=axis2:getBResponse /
			wsdl:fault message=axis2:getBFault name=getBFault /
		/wsdl:operation
		wsdl:operation name=getA
			wsdl:input
xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl;
message=axis2:getAMessage wsaw:Action=urn:getA /
			wsdl:output message=axis2:getAResponse /
			wsdl:fault message=axis2:getAFault name=getAFault /
		/wsdl:operation
	/wsdl:portType
	wsdl:binding name=abSOAP11Binding type=axis2:abPortType
		soap:binding transport=http://schemas.xmlsoap.org/soap/http;
			style=document /
		wsdl:operation name=getB
			soap:operation soapAction=urn:getB style=document /
			wsdl:input
soap:body use=literal /
			/wsdl:input
			wsdl:output
soap:body use=literal /
			/wsdl:output
			wsdl:fault name=getBFault
soap12:fault use=literal name=getBFault /
			/wsdl:fault
		/wsdl:operation
		wsdl:operation name=getA
			soap:operation soapAction=urn:getA style=document /
			wsdl:input
soap:body use=literal /
			/wsdl:input
			wsdl:output
soap:body use=literal /
			/wsdl:output
			wsdl:fault name=getAFault
soap12:fault use=literal name=getAFault /
			/wsdl:fault
		/wsdl:operation
	/wsdl:binding
	wsdl:binding name=abSOAP12Binding type=axis2:abPortType
		soap12:binding transport=http://schemas.xmlsoap.org/soap/http;
			style=document /

Re: duplicate fault elements in generated wsdl

2007-06-25 Thread fat suze

Hans,

This is a bug.  I reported this a few weeks ago, and it seems to have
been fixed for a future release:
https://issues.apache.org/jira/browse/AXIS2-2759

Have a great day,

Susie


On 6/25/07, Hans Benedict [EMAIL PROTECTED] wrote:


Hi,

I am building a simple POJO based web service offering two methods which
both throw the same custom exception:

public String getA(String x) throws WsException {...}

public String getB(String y) throws WsException {...}

WsException is extending AxisFault.

The generated wsdl file (.../axis2/services/ab?wsdl - see attachment)
then contains *two* elements named WsExceptionFault. On validation of
the file this leads to an error:
Duplicate key value [WsExceptionFault] declared for identity constraint
element of element schema.

Is this a bug or am I missing something?

My environment:
axis2 1.2
tomcat 5.5.23
jdk-1_5_0_11
debian sarge

Kind regards,
Hans Benedict

--
Hans Benedict   | Freie Universität Berlin
   | Zentraleinrichtung für Datenverarbeitung
Tel.  : +49 30 838 56531| FU Directory and Identity Service (FUDIS)
Fax.  : +49 30 838 56721| Fabeckstr. 32, 14195 Berlin, Germany


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




RE: Axis2 and SAML

2007-06-25 Thread George Stanchev
Hi Michael,

In addition to be a structure for carrying identity information, SAML
defines different profiles, bindings, etc protocol related
specifications for requesting, canceling, verification, etc
manipulations of security tokens. In a sense it does the same thing
as WS-Trust but for SAML-tokens while WS-Trust allows other tokens as
well. The internet2 Shibboleth project uses fully SAML-based
identity solution - you might want to check it out (google it, it will
come up).

Its not only the token, but how you request it, cancel it in secure
manner etc.

In addition, if you are building a web based single sign on solution,
you migh want to check the WS-Federation Passive Requestor
profile, which defines a standardized way of building web-based SSO
solutions which can be federated.

Best Regards,
George

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Monday, June 25, 2007 9:10 AM
To: axis-user@ws.apache.org
Subject: RE: Axis2 and SAML

Thanks George,

For some reason it took me a whole week to come across this post.

Anyway, you say you'd recommend SAML, but you also say you prefer
WS-Trust. I'm a bit confused - I thought SAML was a language for
representing users and their permissions, whereas WS-Trust was for
exchanging security tokens. In other words, I thought these addressed
two different classes of use cases.

I'm still very new to this stuff... 

cheers,
md
 

 -Original Message-
 From: George Stanchev [mailto:[EMAIL PROTECTED]
 Sent: Monday, June 18, 2007 12:15 PM
 To: axis-user@ws.apache.org
 Subject: RE: Axis2 and SAML
 
 
 Hi Michael,
 
 The support for SAML in Rampart is rather weak and if you go with 
 SAML, do not expect much help from it. It uses is internally for the 
 more of a special case of WS-SecureConversation SC token.
 In addition, in Rampart 1.1 there was a way to create a signed and 
 unsigned SAML tokens but you get the token only in the outbound SOAP 
 and you don't have much control over what goes inside (for example 
 SAML attributes).
 
 I'd definetely recommend SAML as the way to go for tokens in an SSO 
 implementation - it is standard, its been around for a while, its 
 proven, it is signed and it is extensible. In addtion, the SAML 2.0 by

 it self defines a security language rivaling WS-Trust so you can 
 just stay with it, though I prefer WS-Trust based exchanges as more 
 standard and supported way to go.
 
 Internet2's OpenSAML libraries are the only mature open source SAML 
 libraries that I know of.
 Version 1.1 supports SAML 1.0 and 1.1 and version 2 supports all SAML 
 standards. OpenSAML2 is still being developed and even though it is 
 stable for most parts it will change somewhat around some of the more 
 peripherical cases (Encryption is one that comes to mind). Though it 
 does have a steeper learning curve, I'd start with OpenSAML2.
 
 Good luck with the SSO implementation.
 
 Best Regards,
 George
 
 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED]
 Sent: Friday, June 15, 2007 2:36 PM
 To: axis-user@ws.apache.org
 Subject: Axis2 and SAML
 
 Hi,
 
 I'm working on a single-sign-on service for our organization's 
 intranet.
 The idea an application can send a username, and password and 
 application identifier to the service, and the service responds with a

 list of permissions that the user has for the particular application.
 
 Just to get started, I created a service that returns a string from 
 which I can parse out what I need. But I'm wondering if I could gain 
 anything (such as greater interoperability) by using a standard such 
 as SAML to represent a user and his/her permissions.
 
 I see that there is a framework for working with SAML:
 http://www.opensaml.org/
 
 Does this sound reasonable or am I heading in the wrong direction? 
 Will I end up with a schema nightmare if I return a SAML xml document 
 as a service payload? BTW, I plan on writing the client and server by 
 hand, because later I will probably want to add rampart and have more 
 control over headers and stuff.
 
 Thanks
 Michael Davis
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 **
 This email and any files transmitted with it are confidential and 
 intended solely for the use of the individual or entity to whom they 
 are addressed. Any unauthorized review, use, disclosure or 
 distribution is prohibited. If you are not the intended recipient, 
 please contact the sender by reply e-mail and destroy all copies of 
 the original message.
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 

-
To unsubscribe, e-mail: [EMAIL 

RE: WSDL2Java for HTTPS

2007-06-25 Thread Ford, Jennifer M.
Have you tried adding the following to the constructor in your generated
code stub? If the path and password matches that of the keystore you
imported the key in, that would help.

System.setProperty(
java.protocol.handler.pkgs, com.sun.net.ssl.internal.www.protocol);
Security.addProvider( new
com.sun.net.ssl.internal.ssl.Provider() );

System.setProperty(javax.net.ssl.trustStore,
path);
 
System.setProperty(javax.net.ssl.trustStorePassword,  changeit);
 

-Original Message-
From: r1c4r60 [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 25, 2007 2:48 PM
To: axis-user@ws.apache.org
Subject: RE: WSDL2Java for HTTPS


Hi,

Certificates for IP addresses will not work

Quite simply, issuing and using certificates that authenticate IP
addresses rather than host names will not work. Don't do it. For
anything larger than a trivial installation, your CAS server and its
clients need real hostnames and certificates that authenticate those
hostnames (for proxy ticket functionality). In particular, if you get an
error like (unable to find valid certification path to requested
target) in the CAS server log, it means that the SSL callback was
specified in terms of an IP address rather than a hostname.

Quoted from: http://www.ja-sig.org/products/cas/server/ssl/index.html

Does this seem to be your case?

Regards,
Ricardo


Mark Babcock-3 wrote:
 
 I did everything you listed step by step and this is the stack trace I
 get:
 
 [axis-wsdl2java] javax.net.ssl.SSLHandshakeException:
 sun.security.validator.Val
 idatorException: PKIX path building failed:
 sun.security.provider.certpath.SunCe
 rtPathBuilderException: unable to find valid certification path to 
 requested tar get
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.Alerts.getSSLException(A
 lerts.java:174)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLS
 ocketImpl.java:1520)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Hands
 haker.java:182)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Hands
 haker.java:176)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.ClientHandshaker.serverC
 ertificate(ClientHandshaker.java:975)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.ClientHandshaker.process
 Message(ClientHandshaker.java:123)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.Handshaker.processLoop(H
 andshaker.java:511)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.Handshaker.process_recor
 d(Handshaker.java:449)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord
 (SSLSocketImpl.java:817)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.SSLSocketImpl.performIni
 tialHandshake(SSLSocketImpl.java:1029)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHands
 hake(SSLSocketImpl.java:1056)
 [axis-wsdl2java]at
 com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHands
 hake(SSLSocketImpl.java:1040)
 [axis-wsdl2java]at
 sun.net.www.protocol.https.HttpsClient.afterConnect(H
 ttpsClient.java:405)
 [axis-wsdl2java]at
 sun.net.www.protocol.https.AbstractDelegateHttpsURLCo
 nnection.connect(AbstractDelegateHttpsURLConnection.java:170)
 [axis-wsdl2java]at
 sun.net.www.protocol.http.HttpURLConnection.getInputS
 tream(HttpURLConnection.java:981)
 [axis-wsdl2java]at
 sun.net.www.protocol.https.HttpsURLConnectionImpl.get
 InputStream(HttpsURLConnectionImpl.java:234)
 [axis-wsdl2java]at
 org.apache.xerces.impl.XMLEntityManager.setupCurrentE
 ntity(Unknown Source)
 [axis-wsdl2java]at
 org.apache.xerces.impl.XMLVersionDetector.determineDo
 cVersion(Unknown Source)
 [axis-wsdl2java]at
 org.apache.xerces.parsers.XML11Configuration.parse(Un
 known Source)
 [axis-wsdl2java]at
 org.apache.xerces.parsers.XML11Configuration.parse(Un
 known Source)
 [axis-wsdl2java]at
 org.apache.xerces.parsers.XMLParser.parse(Unknown Sou
 rce)
 [axis-wsdl2java]at
 org.apache.xerces.parsers.DOMParser.parse(Unknown Sou
 rce)
 [axis-wsdl2java]at
 org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unkn
 own Source)
 [axis-wsdl2java]at
 org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.j
 ava:369)
 [axis-wsdl2java]at
 org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.j
 ava:420)
 [axis-wsdl2java]at
 org.apache.axis.wsdl.symbolTable.SymbolTable.populate
 (SymbolTable.java:482)
 [axis-wsdl2java]at
 org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Pars
 er.java:361)
 [axis-wsdl2java]at java.lang.Thread.run(Thread.java:619)
 [axis-wsdl2java] Caused by: sun.security.validator.ValidatorException:
 PKIX path
  building failed:
 sun.security.provider.certpath.SunCertPathBuilderException: un able to

 find valid certification path to requested target
 [axis-wsdl2java]at
 

Re: class loading problem

2007-06-25 Thread Joe Nathan

It does make difference, especially forward compatibility is not assured!


Michele Mazzucco-2 wrote:
 
 Joe,
 
 it should not make any difference because the linking is made at  
 runtime, and I wasn't using any of the new features.
 Indeed, I think the problem is related to the Axis2 class loader.
 
 
 Michele
 

-- 
View this message in context: 
http://www.nabble.com/class-loading-problem-tf3965801.html#a11297073
Sent from the Axis - User mailing list archive at Nabble.com.


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



RE: [Axis2] Axis2 client message different to Axis1 client messag e

2007-06-25 Thread Alick Buckley

Hi Dims, Fantastic, the -sp option did the trick.

   java org.apache.axis2.wsdl.WSDL2Java -uri EveryNumberService.wsdl -s -sp
-d adb

Hi Anne, I realize that the SOAP request with namespace prefixes are
equivalent.

ns1:getNumber xmlns:ns1=http://soap.service.acme.com; ...
/ns1:getNumber

But, I have had comments/problems/pushback from other 3rd party servers,
that they are not expecting elements with prefixes or they are expecting or
not expecting this or that in the SOAP message or this message looks
different to our message etc ...

I have found people generate and consume SOAP messages using a wide varity
of tools/methods:

Axis
.NET
NuSOAP
XML parsing
Simple string scan and substring out value
  ...

If Axis and .NET can produce similar SOAP messages, then I have two of the
most common SOAP stacks covered.



SOAP request using the -sp option

?xml version=1.0 encoding=utf-8?
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Body
getNumber xmlns=http://soap.service.acme.com;
param1
a_int
item2/item
item3/item
item4/item
/a_int
n_double22.5/n_double
n_float23.4/n_float
n_int123/n_int
n_long3456/n_long
o_bigdecimal567.67/o_bigdecimal
o_biginteger98765/o_biginteger
o_double345.67/o_double
o_int7585/o_int
/param1
/getNumber
/soapenv:Body
/soapenv:Envelope



-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 26 June 2007 4:25 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] Axis2 client message different to Axis1 client
messag e


Alick,

Did you try the suppress-prefixes option in WSDL2Java?

http://svn.apache.org/viewvc?view=revrevision=480336
https://issues.apache.org/jira/browse/AXIS2-1784

thanks,
dims

On 6/25/07, Anne Thomas Manes [EMAIL PROTECTED] wrote:
 Alick,

 What exactly is your question?

 The messages are semantically equivalent.

 Anne


 On 6/25/07, Alick Buckley  [EMAIL PROTECTED] wrote:
 
 
  Hi,
 
  If I use the original test WSDL with the .NET WebService Studio Tool,
the
 SOAP message is the same as Axis 1.4 ?
 
  Microsoft .NET WebService Studio Tool
 
  ?xml version=1.0 encoding=utf-8?
  soap:Envelope
 xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;
  xmlns:xsd=http://www.w3.org/2001/XMLSchema;
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
  soap:Body
  getNumber xmlns=http://soap.service.acme.com;
  param1
  a_int
  item23/item
  /a_int
  n_double23.45/n_double
  n_float56.78/n_float
  n_int876/n_int
  n_long284849/n_long
  o_biginteger48484/o_biginteger
  /param1
  /getNumber
  /soap:Body
  /soap:Envelope
 
  Axis 1.4
 
 
  ?xml version=1.0 encoding=utf-8?
  soapenv:Envelope
  xmlns:soapenv=
 http://schemas.xmlsoap.org/soap/envelope/;
  xmlns:xsd= http://www.w3.org/2001/XMLSchema;
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance 
  soapenv:Body
  getNumber xmlns=http://soap.service.acme.com;
  param1
  a_int
  item123/item
  item456/item
  /a_int
  n_double20.1/n_double
  n_float21.11/n_float
  n_int22/n_int
  n_long22345678/n_long
  o_bigdecimal223.546/o_bigdecimal
  o_biginteger22385943/o_biginteger
  o_double2435.456/o_double
  o_int23245/o_int
  /param1
  /getNumber
  /soapenv:Body
  /soapenv:Envelope
 
 
 =
 
  -Original Message-
  From: Alick Buckley [mailto:[EMAIL PROTECTED]
  Sent: Monday, 25 June 2007 4:15 PM
  To: axis-user@ws.apache.org
 
  Subject: RE: [Axis2] Axis2 client message different to Axis1 client
messag
 e
 
 
 
  Hi,
 
  If the elementFormDefault is set to unqualified then the SOAP message
does
 not have the namespace prefixes.
 
  But the getNumber element has a namespace prefix, but there is no
default
 namespace ?
 
  schema elementFormDefault=unqualified
 targetNamespace= http://soap.service.acme.com;
 xmlns=http://www.w3.org/2001/XMLSchema;
 
 
 ===
 
  ?xml version=1.0 encoding=utf-8?
  soapenv:Envelope
 xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ 
  soapenv:Body
  ns1:getNumber xmlns:ns1=http://soap.service.acme.com 
  

Axis and resource management

2007-06-25 Thread Joe Nathan

I think most will host both SOAP and Servlets together using Tomcat+Axis. In
addition, most will have running environmental resources such as database
connections, files, etc. Currently, we ended up with two separate rources
managers. This is a highly undesirable situation! It should be better if we
can serve Servlets and SOAPs together using a single resources manager.

In addition, Axis returns URL which is not actual location for the following
call;

  URL url = xx.getClassLoader().getResource(??);

This should return actual .jar or .aar path names!

Regards.

-- 
View this message in context: 
http://www.nabble.com/Axis-and-resource-management-tf3979466.html#a11297223
Sent from the Axis - User mailing list archive at Nabble.com.


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



datetime handling in Axis!

2007-06-25 Thread Suresh Koya
Hi,

  I am using axis 2.0. I have facing some issues with the datetime handling of 
axis. It looks like in axis, the xsd:dateTime map to java.util.Calendar.
 I am generating stubs with wsdl2java. A class called DateTimeType is generated 
by axis based on my wsdl. Here is my schema definition for the DateTimeType. 

xs:complexType name=DateTimeType
xs:simpleContent
xs:extension base=xs:dateTime
xs:attribute fixed=DateTime name=type type=xs:string 
use=required/
xs:attribute name=mandatory type=xs:boolean use=optional/
xs:attribute name=readonly type=xs:boolean use=optional/
/xs:extension
/xs:simpleContent
/xs:complexType

It looks like axis generated the following code to deseralize the DateTime. 
java.util.Calendar cal =
(java.util.Calendar) new 
org.apache.axis.encoding.ser.CalendarDeserializer(
java.lang.String.class, 
org.apache.axis.Constants.XSD_STRING).makeValue(_value);

Everytime when the server sends the date, it has the format 
2007-06-24T00:14:14+00:00 but when the date passes through axis the datetime 
field value changes to 2007-06-24T00:14:14.000Z with a Z in the tail. My server 
does not understand this format and reports a SOAP fault. 

Is there any way to change this?

Regards,
Suresh Koya

RE: datetime handling in Axis!

2007-06-25 Thread Ford, Jennifer M.
DateTime is not a safe type to use in web services.  I would recommend
using a string or long and parsing it back out to a date object on both
sides of the interface. 



From: Suresh Koya [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 25, 2007 6:23 PM
To: Axis User
Subject: datetime handling in Axis!


Hi,

  I am using axis 2.0. I have facing some issues with the datetime
handling of axis. It looks like in axis, the xsd:dateTime map to
java.util.Calendar.
 I am generating stubs with wsdl2java. A class called DateTimeType is
generated by axis based on my wsdl. Here is my schema definition for the
DateTimeType. 

xs:complexType name=DateTimeType
xs:simpleContent
xs:extension base=xs:dateTime
xs:attribute fixed=DateTime name=type type=xs:string
use=required/
xs:attribute name=mandatory type=xs:boolean
use=optional/
xs:attribute name=readonly type=xs:boolean use=optional/
/xs:extension
/xs:simpleContent
/xs:complexType

It looks like axis generated the following code to deseralize the
DateTime. 
java.util.Calendar cal =
(java.util.Calendar) new
org.apache.axis.encoding.ser.CalendarDeserializer(
java.lang.String.class,
org.apache.axis.Constants.XSD_STRING).makeValue(_value);

Everytime when the server sends the date, it has the format
2007-06-24T00:14:14+00:00 but when the date passes through axis the
datetime field value changes to 2007-06-24T00:14:14.000Z with a Z in the
tail. My server does not understand this format and reports a SOAP
fault. 

Is there any way to change this?

Regards,
Suresh Koya


RE: [Axis2] Streaming dynamically generated large sized content

2007-06-25 Thread Shalab Goel
 

Resending my query on sending dynamically generated content as a stream
in SOAP attachment, hoping it will catch an eye that can comment on
whether this is expected to work in Axis, and if not, if there are there
suggestions on trying something alternate.

 

Thanks

Shalab



From: Shalab Goel 
Sent: Thursday, June 21, 2007 11:54 AM
To: axis-user@ws.apache.org
Subject: [Axis2] Streaming dynamically generated large sized content

 

Hello Everyone,

 

I am looking for some assistance with streaming large sized dynamically
generated content.

 

I have defined an 'echoString' operation, which takes two request
arguments a string to repeat, and count of number of times to repeat.
This is a service which replicates somewhat the requirement I am working
on - to be able to stream dynamically generated content (size in order
of 50 to 200 MBs). 

 

public OMElement echoString (String echo, String count)
throws Exception

{

PipedInputStream inStream = new
PipedInputStream();

PipedOutputStream outStream = new
PipedOutputStream(inStream);

 

DataHandler dh = new DataHandler(inStream,
text/plain);

 

MessageContext inCtx =
MessageContext.getCurrentMessageContext();

   OperationContext operationContext =
inCtx.getOperationContext();

   MessageContext outCtx = operationContext

 
.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);



String attachmentID = outCtx.addAttachment(dh);

 

OMFactory fac =
OMAbstractFactory.getOMFactory();

OMNamespace omNs = fac.createOMNamespace(

 
http://service.soapwithattachments.sample/xsd;, swa);

OMElement echoStringOp =
fac.createOMElement(echoStringResponse, omNs);

OMElement idEle =
fac.createOMElement(attchmentID, omNs);

idEle.addAttribute(href,
cid:+attachmentID,null);

echoStringOp.addChild(idEle);

 

byte bytes[] = strArg.getBytes();

try

{

  for (int i=0; i  cntArg; i++)

  outStream.write(bytes);

  outStream.flush();

  outStream.close();

}

catch (Exception e) {};

 

return echoStringOp;

}

 

In the services.xml, I have added parameter for enabling SWA

 

 parameter name=enableSwAtrue/parameter

 

 

When I run my client code, I get the following exception trace:

 

contentID 0.urn:uuid:[EMAIL PROTECTED]

Exception in thread main java.io.IOException: eosBeforeMarker

  at
org.apache.axiom.attachments.BoundaryDelimitedStream.read(BoundaryDelimi
tedStream.java:300)

  at
org.apache.axiom.attachments.IncomingAttachmentInputStream.read(Incoming
AttachmentInputStream.java:121)

  at
sample.soapwithattachments.client.SWAClient.callEchoManyTimes(SWAClient.
java:212)

  at
sample.soapwithattachments.client.SWAClient.main(SWAClient.java:59)

 

 

Following is how the attachment is being accessed in client code:

 

MessageContext response = mepClient

 
.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);

Attachments attachments =
response.getAttachmentMap();

IncomingAttachmentStreams streams =
attachments.getIncomingAttachmentStreams();

IncomingAttachmentInputStream inStream = null;

if (streams != null)

{

inStream = streams.getNextStream();

System.out.println(contentID  +
inStream.getContentId());

}

 

Following is the SOAP request (in TCPMonitor):

-  

 

POST /axis2/services/SWASampleService HTTP/1.1

Content-Type: multipart/related;
boundary=MIMEBoundaryurn_uuid_C2F2DEF18072BF88741182450074533;
type=text/xml;
start=0.urn:uuid:[EMAIL PROTECTED];
charset=UTF-8

SOAPAction: urn:echoString

User-Agent: Axis2

Host: 127.0.0.1:8081

Transfer-Encoding: chunked

 

231

--MIMEBoundaryurn_uuid_C2F2DEF18072BF88741182450074533

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

Content-Transfer-Encoding: 8bit

Content-ID: 0.urn:uuid:[EMAIL PROTECTED]

   ?xml version='1.0' encoding='UTF-8'?

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

 soapenv:Body

swa:echoString
xmlns:swa=http://service.soapwithattachments.sample/xsd;

   swa:echohowdy/swa:echo

   swa:count45/swa:count

/swa:echoString

 

[Axis2] Axis2 1.2 client cannot process SOAP response from Axis 1 .4 server

2007-06-25 Thread Alick Buckley

Hi,

When a Axis2 1.2 client test program calls an Axis 1.4 server, the SOAP
message request message is ok, and the server consumes the request and sends
back a response.

When the Axis2 1.2 client program recieves the SOAP message response the
following AxisFault message is thrown.

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




Looking at the following link, the problem looks like it occurs when a Axis2
server is receiving a SOAP message, but my problem is that this message is
thrown by the Axis2 client when it receives a SOAP response.

http://wso2.org/library/559




org.apache.axis2.AxisFault: Transport level information does not match with
SOAP Message namespace URI
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.j
ava:81)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperatio
n.java:356)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOpera
tion.java:294)
at
com.acme.service.soap.EveryNumberServiceServiceStub.getNumber(EveryNumberSer
viceServiceStub.java:162)
at Test.main(Test.java:82)
Caused by: org.apache.axiom.soap.SOAPProcessingException: Transport level
information does not match with SOAP Message namespace URI
at
org.apache.axis2.builder.BuilderUtil.validateSOAPVersion(BuilderUtil.java:51
5)
at
org.apache.axis2.builder.SOAPBuilder.processDocument(SOAPBuilder.java:45)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.j
ava:130)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.j
ava:77)
... 4 more




I generated the Axis2 1.2 client program using the following command.

java org.apache.axis2.wsdl.WSDL2Java -uri EveryNumberService.wsdl -s
-sp -d adb 


This is the SOAP Request sent to the server

?xml version=1.0 encoding=utf-8?
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Body
getNumber xmlns=http://soap.service.acme.com;
param1
a_int
item2/item
item3/item
item4/item
/a_int
n_double22.5/n_double
n_float23.4/n_float
n_int123/n_int
n_long3456/n_long
o_bigdecimal567.67/o_bigdecimal
o_biginteger98765/o_biginteger
o_double345.67/o_double
o_int7585/o_int
/param1
/getNumber
/soapenv:Body
/soapenv:Envelope




This is the SOAP Response sent from the server to the client

?xml version=1.0 encoding=utf-8?
soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
soapenv:Body
getNumberResponse xmlns=http://soap.service.acme.com;
getNumberReturn
 
a_bytePD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4NCg0KPCFET0NUWVBF
IE9yZGVycyBTWVNURU0gIm9yZGVyLmR0ZCIgID4NCg0KPE9yZGVycz4NCg0KICAgICAgPFNhbGVz
T3JkZXIgU09OdW1iZXI9IjEyMzQ1Ij4NCg0KICAgICAgICAgPEN1c3RvbWVyIEN1c3ROdW1iZXI9
IjU0MyI+DQogICAgICAgICAgICA8Q3VzdE5hbWU+IEFCQyBJbmR1c3RyaWVzPC9DdXN0TmFtZT4N
CiAgICAgICAgICAgIDxTdHJlZXQ+MTIzIE1haW4gU3QuPC9TdHJlZXQ+DQogICAgICAgICAgICA8
Q2l0eT5DaGljYWdvPC9DaXR5Pg0KICAgICAgICAgICAgPFN0YXRlPklMPC9TdGF0ZT4NCiAgICAg
ICAgICAgIDxQb3N0Q29kZT42MDYwOTwvUG9zdENvZGU+DQogICAgICAgICA8L0N1c3RvbWVyPg0K
DQogICAgICAgICA8T3JkZXJEYXRlPjk4MTIxNTwvT3JkZXJEYXRlPg0KDQogICAgICAgICA8TGlu
ZSBMaW5lTnVtYmVyPSIxIj4NCiAgICAgICAgICAgIDxQYXJ0IFBhcnROdW1iZXI9IjEyMyI+DQog
ICAgICAgICAgICAgICA8RGVzY3JpcHRpb24+R2Fza2V0IFBhcGVyPC9EZXNjcmlwdGlvbj4NCiAg
ICAgICAgICAgICAgIDxQcmljZT45Ljk1PC9QcmljZT4NCiAgICAgICAgICAgIDwvUGFydD4NCiAg
ICAgICAgICAgIDxRdWFudGl0eT4xMDwvUXVhbnRpdHk+DQogICAgICAgICA8L0xpbmU+DQoNCiAg
ICAgICAgIDxMaW5lIExpbmVOdW1iZXI9IjIiPg0KICAgICAgICAgICAgPFBhcnQgUGFydE51bWJl
cj0iNDU2Ij4NCiAgICAgICAgICAgICAgIDxEZXNjcmlwdGlvbj48IVtDREFUQVtHYXNrZXQgPFBv
bHltZXI+IEdsdWVdXT48L0Rlc2NyaXB0aW9uPg0KICAgICAgICAgICAgICAgPFByaWNlPjEzLjI3
PC9QcmljZT4NCiAgICAgICAgICAgIDwvUGFydD4NCiAgICAgICAgICAgIDxRdWFudGl0eT41PC9R
dWFudGl0eT4NCiAgICAgICAgIDwvTGluZT4NCg0KICAgICAgPC9TYWxlc09yZGVyPg0KDQo8L09y
ZGVycz4NCg==/a_byte
a_int xsi:nil=true/
n_double10.1/n_double
n_float11.11/n_float
n_int12/n_int
n_long12345678/n_long
o_bigdecimal123.546/o_bigdecimal

InvocationTargetException

2007-06-25 Thread Yifan (Eric) Jiang
Hi all,

 

I can successfully load a dll library in a standalone java application,
but I can't do it on the Axis web service, and it throws me a
java.lang.reflect.InvocationTargetException error. Can someone please
help me?

 

My source code:

String jlp = System.getProperty(java.library.path);

String newpath = jlp + : +
C:\\R\\R-2.4.1\\library\\rJava\\jri\\jri.dll; 

System.setProperty(java.library.path, newpath);

 

try {

 System.loadLibrary(jri);

} catch (UnsatisfiedLinkError e) {

  throw e;

}

 

 

Return:

 

run_client:

 [java] AxisFault

 [java]  faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException

 [java]  faultSubcode:

 [java]  faultString: java.lang.reflect.InvocationTargetException

 [java]  faultActor:

 [java]  faultNode:

 [java]  faultDetail:

 [java] {http://xml.apache.org/axis/}hostname:eric

 [java]

 [java] java.lang.reflect.InvocationTargetException

 [java] at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.ja
va:222

)

 [java] at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.jav
a:129)

 

 [java] at
org.apache.axis.encoding.DeserializationContext.endElement(Deserializati
onCont

ext.java:1087)

 [java] at
org.apache.xerces.parsers.SAXParser.endElement(SAXParser.java:1403)

 [java] at
org.apache.xerces.validators.common.XMLValidator.callEndElement(XMLValid
ator.j

ava:1550)

 [java] at
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatc
h(XMLD

ocumentScanner.java:1149)

 [java] at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScan
ner.ja

va:381)

 [java] at
org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1098)

 [java] at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)

 [java] at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationCon
text.j

ava:227)

 [java] at
org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)

 [java] at
org.apache.axis.Message.getSOAPEnvelope(Message.java:435)

 [java] at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstan
dCheck

er.java:62)

 [java] at
org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)

 [java] at
org.apache.axis.client.Call.invokeEngine(Call.java:2784)

 [java] at org.apache.axis.client.Call.invoke(Call.java:2767)

 [java] at org.apache.axis.client.Call.invoke(Call.java:2443)

 [java] at org.apache.axis.client.Call.invoke(Call.java:2366)

 [java] at org.apache.axis.client.Call.invoke(Call.java:1812)

 [java] at client.testClient.main(testClient.java:41)

 

 

Thanks

 

Eric



RE: [Axis2] Axis2 1.2 client cannot process SOAP response from Ax is 1 .4 server

2007-06-25 Thread Alick Buckley
Hi,
 
Using a HTTP server that allows me to capture the inbound SOAP message and
to return a SOAP message from a file.
 
I have reduced the SOAP message response down to this and the exception
still occurs.
 
?xml version=1.0 encoding=utf-8?
soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/
http://schemas.xmlsoap.org/soap/envelope/ 
soapenv:Body
getNumberResponse xmlns= http://soap.service.acme.com
http://soap.service.acme.com 
getNumberReturn
n_double10.1/n_double
n_float11.11/n_float
n_int12/n_int
n_long12345678/n_long
o_bigdecimal123.546/o_bigdecimal
o_biginteger12385943/o_biginteger
o_double135.456/o_double
o_int13245/o_int
/getNumberReturn
/getNumberResponse
/soapenv:Body
/soapenv:Envelope
 
The return HTTP content type is
 
Content-Type: application/soap+xml; charset=utf-8

===

-Original Message-
From: Alick Buckley [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 26 June 2007 10:20 AM
To: axis-user@ws.apache.org
Subject: [Axis2] Axis2 1.2 client cannot process SOAP response from Axis 1
.4 server




Hi, 

When a Axis2 1.2 client test program calls an Axis 1.4 server, the SOAP
message request message is ok, and the server consumes the request and sends
back a response.

When the Axis2 1.2 client program recieves the SOAP message response the
following AxisFault message is thrown. 

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


 

Looking at the following link, the problem looks like it occurs when a Axis2
server is receiving a SOAP message, but my problem is that this message is
thrown by the Axis2 client when it receives a SOAP response.

http://wso2.org/library/559 http://wso2.org/library/559  


 

org.apache.axis2.AxisFault: Transport level information does not match with
SOAP Message namespace URI 
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.j
ava:81) 
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperatio
n.java:356) 
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOpera
tion.java:294) 
at
com.acme.service.soap.EveryNumberServiceServiceStub.getNumber(EveryNumberSer
viceServiceStub.java:162) 
at Test.main(Test.java:82) 
Caused by: org.apache.axiom.soap.SOAPProcessingException: Transport level
information does not match with SOAP Message namespace URI

at
org.apache.axis2.builder.BuilderUtil.validateSOAPVersion(BuilderUtil.java:51
5) 
at
org.apache.axis2.builder.SOAPBuilder.processDocument(SOAPBuilder.java:45) 
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.j
ava:130) 
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.j
ava:77) 
... 4 more 


 

I generated the Axis2 1.2 client program using the following command. 

java org.apache.axis2.wsdl.WSDL2Java -uri EveryNumberService.wsdl -s
-sp -d adb 


This is the SOAP Request sent to the server 

?xml version=1.0 encoding=utf-8? 
soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/
http://schemas.xmlsoap.org/soap/envelope/  
soapenv:Body 
getNumber xmlns= http://soap.service.acme.com
http://soap.service.acme.com  
param1 
a_int 
item2/item 
item3/item 
item4/item 
/a_int 
n_double22.5/n_double 
n_float23.4/n_float 
n_int123/n_int 
n_long3456/n_long 
o_bigdecimal567.67/o_bigdecimal 
o_biginteger98765/o_biginteger 
o_double345.67/o_double 
o_int7585/o_int 
/param1 
/getNumber 
/soapenv:Body 
/soapenv:Envelope 


 

This is the SOAP Response sent from the server to the client 

?xml version=1.0 encoding=utf-8? 
soapenv:Envelope 
xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/
http://schemas.xmlsoap.org/soap/envelope/  
xmlns:xsd= http://www.w3.org/2001/XMLSchema
http://www.w3.org/2001/XMLSchema  xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance
http://www.w3.org/2001/XMLSchema-instance  
soapenv:Body 
getNumberResponse xmlns= http://soap.service.acme.com
http://soap.service.acme.com  
getNumberReturn 
 

RE: datetime handling in Axis!

2007-06-25 Thread Suresh Koya
I tried that but the date arithmetic gets confused with the String datatype. I 
can only change the code on client side. 

regards,
Suresh Koya

Ford, Jennifer M. [EMAIL PROTECTED] wrote: DateTime is not a safe type 
to use in web  services.  I would recommend using a string or long and parsing 
it back out  to a date object on both sides of the interface. 

  
-
 From: Suresh Koya [mailto:[EMAIL PROTECTED]  
Sent: Monday, June 25, 2007 6:23 PM
To: Axis  User
Subject: datetime handling in Axis!


 
Hi,

  I am using axis 2.0. I have facing some issues with  the datetime handling of 
axis. It looks like in axis, the xsd:dateTime map to  java.util.Calendar.
 I am generating stubs with wsdl2java. A class  called DateTimeType is 
generated by axis based on my wsdl. Here is my schema  definition for the 
DateTimeType. 

xs:complexType  name=DateTimeType
 xs:simpleContent
 xs:extension base=xs:dateTime
 xs:attribute fixed=DateTime name=type type=xs:string  
use=required/
xs:attribute  name=mandatory type=xs:boolean use=optional/
 xs:attribute name=readonly type=xs:boolean  use=optional/
 /xs:extension
 /xs:simpleContent
/xs:complexType

It looks like  axis generated the following code to deseralize the DateTime.  
java.util.Calendar cal  =
 (java.util.Calendar) new  
org.apache.axis.encoding.ser.CalendarDeserializer(
 java.lang.String.class,  
org.apache.axis.Constants.XSD_STRING).makeValue(_value);

Everytime when  the server sends the date, it has the format 
2007-06-24T00:14:14+00:00 but when  the date passes through axis the datetime 
field value changes to  2007-06-24T00:14:14.000Z with a Z in the tail. My 
server does not understand  this format and reports a SOAP fault. 

Is there any way to change  this?

Regards,
Suresh Koya


Re: [Axis2] Streaming dynamically generated large sized content

2007-06-25 Thread Davanum Srinivas

Shalab,

Firstly, check the API usage for the attachment streams here:
http://svn.apache.org/viewvc/webservices/commons/trunk/modules/axiom/modules/axiom-tests/src/test/java/org/apache/axiom/attachments/IncomingAttachmentInputTest.java

You actually have to read the bytes before getting the next stream.

Second, i don't recommend using the PipedOutputStream/PipedInputStream
the way you have set it up. You will end up consuming huge memory and
will not be able to handle many connections. Please come up with a
concrete implementation of javax.activation.DataSource and use that to
create your DataHandler. The DataSource implkementation can have a
dynamically generated input stream. A quick google search brought up
this sample.

http://xqzone.marklogic.com/pubs/3.2/javadoc/com/marklogic/xcc/examples/doc-files/DynamicContentStream.java.txt

Thanks,
dims

On 6/25/07, Shalab Goel [EMAIL PROTECTED] wrote:







Resending my query on sending dynamically generated content as a stream in
SOAP attachment, hoping it will catch an eye that can comment on whether
this is expected to work in Axis, and if not, if there are there suggestions
on trying something alternate.



Thanks

Shalab

 


From: Shalab Goel
 Sent: Thursday, June 21, 2007 11:54 AM
 To: axis-user@ws.apache.org
 Subject: [Axis2] Streaming dynamically generated large sized content



Hello Everyone,



I am looking for some assistance with streaming large sized dynamically
generated content.



I have defined an 'echoString' operation, which takes two request arguments
a string to repeat, and count of number of times to repeat. This is a
service which replicates somewhat the requirement I am working on – to be
able to stream dynamically generated content (size in order of 50 to 200
MBs).



public OMElement echoString (String echo, String count) throws
Exception

{

PipedInputStream inStream = new PipedInputStream();

PipedOutputStream outStream = new
PipedOutputStream(inStream);



DataHandler dh = new DataHandler(inStream,
text/plain);



MessageContext inCtx =
MessageContext.getCurrentMessageContext();

   OperationContext operationContext =
inCtx.getOperationContext();

   MessageContext outCtx = operationContext


.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);



String attachmentID = outCtx.addAttachment(dh);



OMFactory fac = OMAbstractFactory.getOMFactory();

OMNamespace omNs = fac.createOMNamespace(


http://service.soapwithattachments.sample/xsd;, swa);

OMElement echoStringOp =
fac.createOMElement(echoStringResponse, omNs);

OMElement idEle = fac.createOMElement(attchmentID,
omNs);

idEle.addAttribute(href,
cid:+attachmentID,null);

echoStringOp.addChild(idEle);



byte bytes[] = strArg.getBytes();

try

{

  for (int i=0; i  cntArg; i++)


outStream.write(bytes);

  outStream.flush();

  outStream.close();

}

catch (Exception e) {};



return echoStringOp;

}



In the services.xml, I have added parameter for enabling SWA



 parameter name=enableSwAtrue/parameter





When I run my client code, I get the following exception trace:



contentID
0.urn:uuid:[EMAIL PROTECTED]

Exception in thread main java.io.IOException: eosBeforeMarker

  at
org.apache.axiom.attachments.BoundaryDelimitedStream.read(BoundaryDelimitedStream.java:300)

  at
org.apache.axiom.attachments.IncomingAttachmentInputStream.read(IncomingAttachmentInputStream.java:121)

  at
sample.soapwithattachments.client.SWAClient.callEchoManyTimes(SWAClient.java:212)

  at
sample.soapwithattachments.client.SWAClient.main(SWAClient.java:59)





Following is how the attachment is being accessed in client code:



MessageContext response = mepClient


.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);

Attachments attachments =
response.getAttachmentMap();

IncomingAttachmentStreams streams =
attachments.getIncomingAttachmentStreams();

IncomingAttachmentInputStream inStream = null;

if (streams != null)

{

inStream = streams.getNextStream();

System.out.println(contentID  +
inStream.getContentId());

}



Following is the SOAP request (in TCPMonitor):


Re: Classpath Problem

2007-06-25 Thread Chad DeBauch

You should keep the third party jars with the aar file and tackle the
problem from that angle.  The jars in the WEB-INF/lib directory will be
loaded first so you may have conflicts with the jars that you have in your
aar or in the jars that Tomcat loads.  That is why you may be getting the
class not found exception.

Chad

On 6/25/07, Swavek Skret [EMAIL PROTECTED] wrote:


When deploying the axis2.war I get the following error in the Tomcat log:

2007-06-25 12:19:36,018 ERROR org.apache.axis2.transport.http.AxisServlet-
java.lang.LinkageError: loader constraint violation: loader (instance of
org/apache/axis2/deployment/DeploymentClassLoader) previously initiated
loading for a different type with name javax/jms/QueueConnection

It is possibly related to the classpath changes I did in my Tomcat
settings.
When creating the aar file, I added the lib directory that included my 3rd
party jar. However, I got a class not found exceptions so I changed Tomcat
shared.loader classpath and added my 3rd party jars to it but now  I am
getting the above error.

Does anyone have any idea of how to fix it?

Thanks,

Swavek




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




Re: [Axis2] Undeployment doesn't work

2007-06-25 Thread Deepal Jayasinghe
Hi  Angel ,

Few days ago at the hackathon I fixed the undeployment issues , if you
take today's nightly build you have the fix.

Thanks
Deepal
 Hi Deepal,

 Is there any recent fix in the snapshot that makes undeployment to
 successfully un-register the undeployed service ? No matter which
 service i try to undeploy, the service remains registered in the Axis2
 runtime.

 Regards,
 Angel



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



RE: Classpath Problem

2007-06-25 Thread Swavek Skret
Hello Chad,

 

It appears that an attempt to establish a JMS connection with Weblogic 8.1
is the source of the problem. The interfaces returned by the
javax.naming.InitialContext do not seem to match javax.jms.* interfaces
(QueueConnectionFactory, QueueConnection, etc.) in the Weblogic 8.1
implementation. There are two files in axis2 libs,
geronimo-spec-jms-1.1-rc4.jar and axis2-kernel-1.2.jar, that deal with JMS
and I presume that the version of the JMS that they are using differs from
Weblogic 8.1. Could you suggest an approach to ensure that during the run
time all of the JMS will be resolved correctly (putting Weblogic jars into
the aar file won't fix it since geronimo-spec-jms-1.1-rc4.jar and
axis2-kernel-1.2.jar will be loaded first and loading Weblogic jars before
these two will cause the problem I mentioned already). Please advice.

 

Thanks,

 

Swavek

 

 

From: Chad DeBauch [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 25, 2007 7:42 PM
To: axis-user@ws.apache.org
Subject: Re: Classpath Problem

 

You should keep the third party jars with the aar file and tackle the
problem from that angle.  The jars in the WEB-INF/lib directory will be
loaded first so you may have conflicts with the jars that you have in your
aar or in the jars that Tomcat loads.  That is why you may be getting the
class not found exception. 

Chad

On 6/25/07, Swavek Skret [EMAIL PROTECTED] wrote:

When deploying the axis2.war I get the following error in the Tomcat log:

2007-06-25 12:19:36,018 ERROR org.apache.axis2.transport.http.AxisServlet -
java.lang.LinkageError: loader constraint violation: loader (instance of 
org/apache/axis2/deployment/DeploymentClassLoader) previously initiated
loading for a different type with name javax/jms/QueueConnection

It is possibly related to the classpath changes I did in my Tomcat settings.

When creating the aar file, I added the lib directory that included my 3rd
party jar. However, I got a class not found exceptions so I changed Tomcat
shared.loader classpath and added my 3rd party jars to it but now  I am 
getting the above error.

Does anyone have any idea of how to fix it?

Thanks,

Swavek




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

 



axis error - no SOAP service at this location - Calculator.jws - steps to create websevice.

2007-06-25 Thread Leonard Gestrin
Hello, 

I am newbie to the product so I would appreciate any help pointers. 

 

I have few problems/questions that I could not find answer in the
user-guide/archive.

 

1.  I can successfully run axis web application and copying
Calculator.jws as described in the doc,  exposes the link and wsdl can
be generated. However, once I merged axis's web.xml and our own
application, same test produces the error when I click on  on 'Click to
see the WSDL'. I have also merged happyaxis.jsp and it does not report
any errors and soap engine is packaged with our app.  


AXIS error


Could not generate WSDL!

There is no SOAP service at this location

If anybody has any clues/ideas what this message really means and how it
should be debugged, I would appreciate it. I compared lib directories
and verified that nothing is missing between custom app and 'axis'
webapp.

 

2.  What is the conventional way of creating webservice? Based on
user's doc, it appears that these are the steps

a.  Manually create server-config.wsdd and put it under
webapp.
b.  Have axis generate wsdl

   i.
Using wsdl2java generate skeletons and add them to src so it gets
packaged with application providing a server.

 ii.
Using wsdl2java generate stubs and add them to the client using the
service.

  Does this sound correct?  Can wsdd be also generated? 



 

3.  it appears that URL used in .wsdd is inaccessible
'http://xml.apache.org/axis/wsdd/'. Is this  a concern? Where can I find
these references?

 

Thank you so much. If, these issues/questions have already been
discussed, reference to a thread would be appreciate it.

Leonard Gestrin

 

MarketTools, Inc.

150 Spear Street, Suite 600

San Francisco, CA 94105

 

Tel: 415-957-2085 | Mobile: 415-407-6461

[EMAIL PROTECTED]

 

MarketTools(tm) http://www.markettools.com http://www.markettools.com/


 

This e-mail and any attachments may contain privileged, confidential or
proprietary information. If you are not the intended recipient, be aware
that any review, copying, or distribution of this e-mail or any
attachment is strictly prohibited. If you have received this e-mail in
error, please return it to the sender immediately, and permanently
delete the original and any copies from your system. Thank you for your
cooperation.