[Axis2] Simple svc client or http client crashing in linux...

2006-12-08 Thread Dinesh Premalal

Forward with correct prefix ...

-- Forwarded message --
From: Raju, Prabhakar (P.) [EMAIL PROTECTED]
Date: Dec 8, 2006 4:09 AM
Subject: Simple svc client or http client crashing in linux...
To: Apache AXIS C User List axis-c-user@ws.apache.org

Hi,

If I run the simple server and echo client ( axis2/c) , if the server dies
or hangs for a while (I think) , the client crashes with segmentation fault.
To test this, I ran the sample client echo.c

Something like this.

for(i=0;i10;++i){
   ret_node = AXIS2_SVC_CLIENT_SEND_RECEIVE(svc_client, env, payload);
   printf(%d times\n, i);
   }

The call ran about 1000 times and the client reported SIGSEGV. I face the
same problem, using http_client for our program. The call fails at random
(either 300 calls or 16000 calls or 5000 calls).

My linux version is Suse 8.1

FYI


--
W.Dinesh Premalal
[EMAIL PROTECTED]
WSO2, Inc.; http://www.wso2.com/
GPG Key ID : A255955C
GPG Key Finger Print : C481 E5D4 C27E DC34 9257  0229 4F44 266E A255 955C


[Axis2] Simple svc client or http client crashing in linux...

2006-12-08 Thread Raju, Prabhakar \(P.\)
Hi,
The problem is fixed now. We had to set the client TIMEOUT explicitly.
FYI



pls un subscribe

2006-12-08 Thread Giri



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



Re: MTOM Sample

2006-12-08 Thread Thilina Gunarathne

We are not using the generate all(-g) in the MTOM sample..

You can generate the client by running the ant run.client (or by
altering it to just generate source)...
IIRC it'll generate source code in to the build/client folder..

Thanx,
Thilina

On 12/7/06, Danny Lin [EMAIL PROTECTED] wrote:



I am trying to get MTOM Sample code to run. I use Eclipse 3.2. After I run
the generate.service target, I have the AAR created several source files
(e.g. MTOMSampleMessageReceiverInOut.java,
MTOMSampleSkeleton.java, etc.)

My problem is that in the Client.java class it has import statements:
import sample.mtom.service.MTOMSampleStub;
import
sample.mtom.service.MTOMSampleStub.AttachmentRequest;
import
sample.mtom.service.MTOMSampleStub.AttachmentResponse;
import
sample.mtom.service.MTOMSampleStub.AttachmentType;
import sample.mtom.service.MTOMSampleStub.Base64Binary;

I can't find any of these source files. I added -g argument to the target
and got the stub generated. How can I generate the other 4 classes? Any
comment and help is appreciated.

Danny






--
http://webservices.apache.org/~thilina/
http://thilinag.blogspot.com/

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



Re: Why it only read 28 bytes

2006-12-08 Thread jim ma

Hi all ,

I think this is a bug maybe introduced by jakarta-httpcore-4.0-alpha2.  When
enable the chunk mode for StringEntity , client will read 28 bytes each time
. Client will read many times when a large payload response returned . This
definitely affects Aixs2's performance.

Axis2 need to set chunk buffersize for HttpCore before invoking
StringEntity.setChunk(true) ?

Regards

Jim

On 12/5/06, jim ma [EMAIL PROTECTED] wrote:


Hi all ,

I downloaded the aixs2 1.1 std kit and tried a simple sample contains one
operation: echoString() . After I deployed the service in repository and
launch the server with axis2server.I wrote the following code to send the
payload to aixs2server and soap response :

httpCon.getOutputStream().write(payload);
httpCon.getOutputStream().flush();
byte[] buffer = new byte[1024];
count = httpCon.getInputStream().read(buffer);
while (count  0) {
   System.out.println (---readed + count);
   count = httpCon.getInputStream().read(buffer);
}

I found the thing confused me : each time it only can read 28 bytes from
inputStream . Large size respsone will be readed many times.  But I deployed
it into tomcat , It will read 1024 bytes each time.

Which line code in Artix2 1.1 cause this ?

Thanks

Jim







[Axis2 v1.1] How can I get full XML from SOAP Request ?

2006-12-08 Thread John DeeBee
Hi, 

I'm working on server-side from Axis2 v1.1 and I need to
get the whole XML request in my WS skeleton (and after) to make other
XML parsing and to log every message going in and out from my webapp.
In
Axis2 v1.0, I wrote a method called setOperationContext() in my
skeleton which retireved the full XML request by using
messageContext.getEnveloppe().toString().
But now I'm working with
v1.1 and it doesn't work anymore. So I delete my setOperationContext()
method and, in my WS operation, I write this code to replace :

MessageContext contexteMessage = 
MessageContext.getCurrentMessageContext();
setFluxXML(contexteMessage.getEnvelope().toString());

But
 contexteMessage.getEnvelope().toString() gives me only the beginning and the 
end of the request, not the full content.
I
tried to make a logging module as described in documentation but the
result is the quite the same. I have the full xml from WS response but
not for request.
Who have a solution before I getting mad ?

John







___ 
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! 
Profitez des connaissances, des opinions et des expériences des internautes sur 
Yahoo! Questions/Réponses 
http://fr.answers.yahoo.com

Re: [Axis2 v1.1] How can I get full XML from SOAP Request ?

2006-12-08 Thread robert lazarski

It may be a bug that it doesn't give the full envelope - someone else
may be able to comment and if not file a jira. However, the handler
approach can work as the SOAPMonitor uses
messageContext.getEnvelope().toString() . Look at the soapmonitor mar
and SOAPMonitorHandler.java - the soapmonitor displays both the
response and request correctly with 1.1 so that code should work for
you.

HTH,
Robert

On 12/8/06, John DeeBee [EMAIL PROTECTED] wrote:


Hi,

I'm working on server-side from Axis2 v1.1 and I need to get the whole XML
request in my WS skeleton (and after) to make other XML parsing and to log
every message going in and out from my webapp.
In Axis2 v1.0, I wrote a method called setOperationContext() in my skeleton
which retireved the full XML request by using
messageContext.getEnveloppe().toString().
But now I'm working with v1.1 and it doesn't work anymore. So I delete my
setOperationContext() method and, in my WS operation, I write this code to
replace :

MessageContext contexteMessage =
MessageContext.getCurrentMessageContext();
setFluxXML(contexteMessage.getEnvelope().toString());

But contexteMessage.getEnvelope().toString() gives me only the beginning
and the end of the request, not the full content.
I tried to make a logging module as described in documentation but the
result is the quite the same. I have the full xml from WS response but not
for request.
Who have a solution before I getting mad ?

John
 
 Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions
! Profitez des connaissances, des opinions et des expériences des
internautes sur Yahoo! Questions/Réponses.


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



Re: Null pointer exception when using the WSDL2Java tool

2006-12-08 Thread robert lazarski

Have you validated the WSDL ? If it validates using Eclipses WTP,
xmlspy or the like, post the wsdl and maybe we can help.

Robert

On 12/7/06, Coleman, Piers [EMAIL PROTECTED] wrote:




This is my first post, so here goes.

I'm new to the Java world for creating Web services and I'm trying to use
the WSDL2Java tool to generate my server-side skeleton code. The results are
below. The WSDL file imports the XSD files that it uses.

Could someone provide me with a few pointers on how to investigate this
further? I could post the WSDL as well.

Thanks in advance.

C:\WCA\PocWebService\TypesWSDL2Java.bat -uri PocService.wsdl -ss -sd -d
xmlbean
s -o ..\out -p services.pocservice
Using AXIS2_HOME:   C:\axis2-1.1
Using JAVA_HOME:C:\j2sdk1.4.2_13
Retrieving schema at 'EmployerInfoResponse.xsd', relative to
'file:/C:/WCA/PocWe
bService/Types/'.
Retrieving schema at 'ContactTypes.xsd', relative to
'file:/C:/WCA/PocWebService
/Types/EmployerInfoResponse.xsd'.
Retrieving schema at 'EmployerInfoException.xsd', relative to
'file:/C:/WCA/PocW
ebService/Types/'.
Retrieving schema at 'EmployerInfoRequest.xsd', relative to
'file:/C:/WCA/PocWeb
Service/Types/'.
Dec 7, 2006 5:01:50 PM
org.apache.axis2.description.WSDL11ToAxisServiceBuilder p
opulateService
SEVERE: java.lang.NullPointerException
Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException
: Error parsing WSDL
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerat
ionEngine.java:112)
at
org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
at
org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: org.apache.axis2.AxisFault: null; nested exception is:
java.lang.NullPointerException
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
ce(WSDL11ToAxisServiceBuilder.java:250)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerat
ionEngine.java:103)
... 2 more
Caused by: java.lang.NullPointerException
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
ce(WSDL11ToAxisServiceBuilder.java:235)
... 3 more
Find out about young workers' safety needs at www.demandsafety.ca



CONFIDENTIALITY DISCLAIMER

The information contained in this transmission may contain privileged and
confidential information of WorkSafeBC - the Workers' Compensation Board. It
is intended for review only by the person(s) named above. Dissemination,
distribution or duplication of this communication is strictly prohibited by
all recipients unless expressly authorized otherwise. If you are not the
intended recipient, please contact the sender by reply email and destroy all
copies of the original message. Thank you.



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



[Axis2][1_1] Security exception is swallowed

2006-12-08 Thread Ali Sadik Kumlali
Hi folks,

I need to catch the exception occured in securiy phase. But it seems Rampart 
just logs the exception and  not propagate to the transport receiver. Thus, I'm 
not able to catch it and notify the sender.

Here is my scenario:

- My WSDL has input only (one-way) operations.
- Client sends signed messages by invoking appropriate method of generated stub.
- Service's keystore doesn't have the public certificate of the client
- Rampart logs the exception[1] BUT doesn't throw it.

Since I wrote my own transport receiver, I'm able to catch any 
exception(including RuntimeException) thrown through the execution 
path(transport receiver - phases/modules - message receiver).

Any help would be great!


Regards,

Ali Sadik Kumlali




[1] [ERROR][2006-12-08 14:40:48,535] org.apache.axis2.transport.jms.AxisMdb - 
JMS Wo
rker [JMS Session Delivery Thread] Encountered an Axis Fault : WSDoAllReceiver:
security processing failed; nested exception is:
org.apache.ws.security.WSSecurityException: The signature verification f
ailed
org.apache.axis2.AxisFault: WSDoAllReceiver: security processing failed; nested
exception is:
org.apache.ws.security.WSSecurityException: The signature verification f
ailed
at org.apache.rampart.handler.WSDoAllReceiver.processBasic(WSDoAllReceiv
er.java:275)
at org.apache.rampart.handler.WSDoAllReceiver.processMessage(WSDoAllRece
iver.java:98)
at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:
74)
at org.apache.axis2.engine.Phase.invoke(Phase.java:381)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:521)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:485)
at org.apache.axis2.transport.jms.AxisMdb.onMessage(AxisMdb.java:245)




 

Want to start your own business?
Learn how on Yahoo! Small Business.
http://smallbusiness.yahoo.com/r-index

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



Re: [Axis2][1_1] Security exception is swallowed

2006-12-08 Thread Davanum Srinivas

Can you please log a JIRA?

thanks,
dims

On 12/8/06, Ali Sadik Kumlali [EMAIL PROTECTED] wrote:

Hi folks,

I need to catch the exception occured in securiy phase. But it seems Rampart 
just logs the exception and  not propagate to the transport receiver. Thus, I'm 
not able to catch it and notify the sender.

Here is my scenario:

- My WSDL has input only (one-way) operations.
- Client sends signed messages by invoking appropriate method of generated stub.
- Service's keystore doesn't have the public certificate of the client
- Rampart logs the exception[1] BUT doesn't throw it.

Since I wrote my own transport receiver, I'm able to catch any exception(including 
RuntimeException) thrown through the execution path(transport receiver - 
phases/modules - message receiver).

Any help would be great!


Regards,

Ali Sadik Kumlali




[1] [ERROR][2006-12-08 14:40:48,535] org.apache.axis2.transport.jms.AxisMdb - 
JMS Wo
rker [JMS Session Delivery Thread] Encountered an Axis Fault : WSDoAllReceiver:
security processing failed; nested exception is:
org.apache.ws.security.WSSecurityException: The signature verification f
ailed
org.apache.axis2.AxisFault: WSDoAllReceiver: security processing failed; nested
exception is:
org.apache.ws.security.WSSecurityException: The signature verification f
ailed
at org.apache.rampart.handler.WSDoAllReceiver.processBasic(WSDoAllReceiv
er.java:275)
at org.apache.rampart.handler.WSDoAllReceiver.processMessage(WSDoAllRece
iver.java:98)
at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:
74)
at org.apache.axis2.engine.Phase.invoke(Phase.java:381)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:521)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:485)
at org.apache.axis2.transport.jms.AxisMdb.onMessage(AxisMdb.java:245)






Want to start your own business?
Learn how on Yahoo! Small Business.
http://smallbusiness.yahoo.com/r-index

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





--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

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



Re: [Axis2][1_1] Security exception is swallowed

2006-12-08 Thread Ali Sadik Kumlali
Done: https://issues.apache.org/jira/browse/AXIS2-1849

I just wanted to be make sure that it wasn't a user fault :)

Regards,

Ali Sadik Kumlali

- Original Message 
From: Davanum Srinivas [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Friday, December 8, 2006 4:15:45 PM
Subject: Re: [Axis2][1_1] Security exception is swallowed

Can you please log a JIRA?

thanks,
dims

On 12/8/06, Ali Sadik Kumlali [EMAIL PROTECTED] wrote:
 Hi folks,

 I need to catch the exception occured in securiy phase. But it seems Rampart 
 just logs the exception and  not propagate to the transport receiver. Thus, 
 I'm not able to catch it and notify the sender.

 Here is my scenario:

 - My WSDL has input only (one-way) operations.
 - Client sends signed messages by invoking appropriate method of generated 
 stub.
 - Service's keystore doesn't have the public certificate of the client
 - Rampart logs the exception[1] BUT doesn't throw it.

 Since I wrote my own transport receiver, I'm able to catch any 
 exception(including RuntimeException) thrown through the execution 
 path(transport receiver - phases/modules - message receiver).

 Any help would be great!


 Regards,

 Ali Sadik Kumlali




 [1] [ERROR][2006-12-08 14:40:48,535] org.apache.axis2.transport.jms.AxisMdb - 
 JMS Wo
 rker [JMS Session Delivery Thread] Encountered an Axis Fault : 
 WSDoAllReceiver:
 security processing failed; nested exception is:
 org.apache.ws.security.WSSecurityException: The signature 
 verification f
 ailed
 org.apache.axis2.AxisFault: WSDoAllReceiver: security processing failed; 
 nested
 exception is:
 org.apache.ws.security.WSSecurityException: The signature 
 verification f
 ailed
 at 
 org.apache.rampart.handler.WSDoAllReceiver.processBasic(WSDoAllReceiv
 er.java:275)
 at 
 org.apache.rampart.handler.WSDoAllReceiver.processMessage(WSDoAllRece
 iver.java:98)
 at 
 org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:
 74)
 at org.apache.axis2.engine.Phase.invoke(Phase.java:381)
 at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:521)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:485)
 at org.apache.axis2.transport.jms.AxisMdb.onMessage(AxisMdb.java:245)





 
 Want to start your own business?
 Learn how on Yahoo! Small Business.
 http://smallbusiness.yahoo.com/r-index

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




-- 
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

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





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

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



Re: [Axis2] Rampart not available on Axis modules page

2006-12-08 Thread Sathija Pavuluri
Thanks.
Until that happens, where can I obtain the rampart nightly?
Couldnt find it on the axis nightly page or WS4J site.

Sathija.


 Hi Sathija,

 We are yet to release Rampart-1.1 for Axis2-1.1.

 The page will be updated when the release is done - most probably over
 the weekend.

 Thanks,
 Ruchith

 On 11/29/06, Sathija Pavuluri [EMAIL PROTECTED] wrote:
 Hello,

 Why is Rampart 1.1 (or whatever is the compatible version for Axis2 1.1) not 
 listed/available for download on Axis
 Modules page?
 http://ws.apache.org/axis2/modules/index.html

 There are other pages on Axis2 website that point to this link for Rampart.


 Thanks,
 Sathija


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




 --
 www.ruchith.org

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





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



[Axis2][1_1] Security validation is made only if security header is found...

2006-12-08 Thread Ali Sadik Kumlali
Hi folks,

Is it normal that I don't get any exception if no WS-Security header  added to 
the message while service expecting a signed message?

If not, please let me know so that I can file a JIRA.

Here are the use cases and how Rampart behaves:

Common:
  - Service requires a signed message[1] 
  
Case1: Client adds module ref=rampart/ but doesn't add parameter 
name=OutflowSecurity to the axis2.xml
  - Client sends message 
  - Message doesn't have necessary WS-Security headers but only a single one[2]

  Result
  - Rampart doesn't log or throw any exception and the message passes to the 
message receiver (Unexpected(?) behaviour)
  
Case2: Client doesn't add either module ref=rampart/ or parameter 
name=OutflowSecurity...
  - Client sends message 
  - Message doesn't have any WS-Security header.

  Result
  - Rampart doesn't log or throw any exception and the message passes to the 
message receiver (Unexpected(?) behaviour)
  

Regards,

Ali Sadik Kumlali
  

[1]
module ref=rampart/

parameter name=InflowSecurity
action
itemsSignature/items
signaturePropFileserver_security.properties/signaturePropFile
/action
/parameter
  
[2] 
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd/





 

Want to start your own business?
Learn how on Yahoo! Small Business.
http://smallbusiness.yahoo.com/r-index

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



Re: [Axis2][1_1] Security validation is made only if security header is found...

2006-12-08 Thread Ali Sadik Kumlali
Sorry, [2] should have been as follows:

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


- Original Message 
From: Ali Sadik Kumlali [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Friday, December 8, 2006 5:14:11 PM
Subject: [Axis2][1_1] Security validation is made only if security header is 
found...

Hi folks,

Is it normal that I don't get any exception if no WS-Security header  added to 
the message while service expecting a signed message?

If not, please let me know so that I can file a JIRA.

Here are the use cases and how Rampart behaves:

Common:
  - Service requires a signed message[1] 
  
Case1: Client adds module ref=rampart/ but doesn't add parameter 
name=OutflowSecurity to the axis2.xml
  - Client sends message 
  - Message doesn't have necessary WS-Security headers but only a single one[2]

  Result
  - Rampart doesn't log or throw any exception and the message passes to the 
message receiver (Unexpected(?) behaviour)
  
Case2: Client doesn't add either module ref=rampart/ or parameter 
name=OutflowSecurity...
  - Client sends message 
  - Message doesn't have any WS-Security header.

  Result
  - Rampart doesn't log or throw any exception and the message passes to the 
message receiver (Unexpected(?) behaviour)
  

Regards,

Ali Sadik Kumlali
  

[1]
module ref=rampart/

parameter name=InflowSecurity
action
itemsSignature/items
signaturePropFileserver_security.properties/signaturePropFile
/action
/parameter
  
[2] 
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd/




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

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



Re: [Axis2][1_1] Security validation is made only if security header is found...

2006-12-08 Thread Ali Sadik Kumlali
Beginning part of the line is *somehow* clipped.

Really sorry for disturbing :(

- Original Message 
From: Ali Sadik Kumlali [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Friday, December 8, 2006 5:22:41 PM
Subject: Re: [Axis2][1_1] Security validation is made only if security header 
is found...

Sorry, [2] should have been as follows:

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


- Original Message 
From: Ali Sadik Kumlali [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Friday, December 8, 2006 5:14:11 PM
Subject: [Axis2][1_1] Security validation is made only if security header is 
found...

Hi folks,

Is it normal that I don't get any exception if no WS-Security header  added to 
the message while service expecting a signed message?

If not, please let me know so that I can file a JIRA.

Here are the use cases and how Rampart behaves:

Common:
  - Service requires a signed message[1] 
  
Case1: Client adds module ref=rampart/ but doesn't add parameter 
name=OutflowSecurity to the axis2.xml
  - Client sends message 
  - Message doesn't have necessary WS-Security headers but only a single one[2]

  Result
  - Rampart doesn't log or throw any exception and the message passes to the 
message receiver (Unexpected(?) behaviour)
  
Case2: Client doesn't add either module ref=rampart/ or parameter 
name=OutflowSecurity...
  - Client sends message 
  - Message doesn't have any WS-Security header.

  Result
  - Rampart doesn't log or throw any exception and the message passes to the 
message receiver (Unexpected(?) behaviour)
  

Regards,

Ali Sadik Kumlali
  

[1]
module ref=rampart/

parameter name=InflowSecurity
action
itemsSignature/items
signaturePropFileserver_security.properties/signaturePropFile
/action
/parameter
  
[2] 
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd/




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

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






 

Cheap talk?
Check out Yahoo! Messenger's low PC-to-Phone call rates.
http://voice.yahoo.com

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



RE: Null pointer exception when using the WSDL2Java tool

2006-12-08 Thread Coleman, Piers
I validated it using the interoperability tool from WS-I:
http://www.ws-i.org/deliverables/workinggroup.aspx?wg=testingtools. I
plugged this tool into SoapUI and everything passed ok.

I'm trying to use the Eclipse WTP that you suggested. It looks
promising, but I'm getting the following error when I try and validate
the WSDL. I'm currently googling to see if I can find anything.

WS-I: A problem occured while running the WS-I WSDL conformance check:
org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException: The WS-I
Test Assertion Document (TAD)document was either not found or could not
be processed.The WSDLAnalyzer was unable to validate the given WSDL
File.   Poc/Types   PocService.wsdl line 1  1165599589677   1

-Original Message-
From: robert lazarski [mailto:[EMAIL PROTECTED] 
Sent: Friday, December 08, 2006 4:23 AM
To: axis-user@ws.apache.org
Subject: Re: Null pointer exception when using the WSDL2Java tool

Have you validated the WSDL ? If it validates using Eclipses WTP,
xmlspy or the like, post the wsdl and maybe we can help.

Robert

On 12/7/06, Coleman, Piers [EMAIL PROTECTED] wrote:



 This is my first post, so here goes.

 I'm new to the Java world for creating Web services and I'm trying to
use
 the WSDL2Java tool to generate my server-side skeleton code. The
results are
 below. The WSDL file imports the XSD files that it uses.

 Could someone provide me with a few pointers on how to investigate
this
 further? I could post the WSDL as well.

 Thanks in advance.

 C:\WCA\PocWebService\TypesWSDL2Java.bat -uri PocService.wsdl -ss -sd
-d
 xmlbean
 s -o ..\out -p services.pocservice
 Using AXIS2_HOME:   C:\axis2-1.1
 Using JAVA_HOME:C:\j2sdk1.4.2_13
 Retrieving schema at 'EmployerInfoResponse.xsd', relative to
 'file:/C:/WCA/PocWe
 bService/Types/'.
 Retrieving schema at 'ContactTypes.xsd', relative to
 'file:/C:/WCA/PocWebService
 /Types/EmployerInfoResponse.xsd'.
 Retrieving schema at 'EmployerInfoException.xsd', relative to
 'file:/C:/WCA/PocW
 ebService/Types/'.
 Retrieving schema at 'EmployerInfoRequest.xsd', relative to
 'file:/C:/WCA/PocWeb
 Service/Types/'.
 Dec 7, 2006 5:01:50 PM
 org.apache.axis2.description.WSDL11ToAxisServiceBuilder p
 opulateService
 SEVERE: java.lang.NullPointerException
 Exception in thread main
 org.apache.axis2.wsdl.codegen.CodeGenerationException
 : Error parsing WSDL
 at
 org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerat
 ionEngine.java:112)
 at
 org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
 at
 org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
 Caused by: org.apache.axis2.AxisFault: null; nested exception is:
 java.lang.NullPointerException
 at
 org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
 ce(WSDL11ToAxisServiceBuilder.java:250)
 at
 org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerat
 ionEngine.java:103)
 ... 2 more
 Caused by: java.lang.NullPointerException
 at
 org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
 ce(WSDL11ToAxisServiceBuilder.java:235)
 ... 3 more
 Find out about young workers' safety needs at www.demandsafety.ca



 CONFIDENTIALITY DISCLAIMER

 The information contained in this transmission may contain privileged
and
 confidential information of WorkSafeBC - the Workers' Compensation
Board. It
 is intended for review only by the person(s) named above.
Dissemination,
 distribution or duplication of this communication is strictly
prohibited by
 all recipients unless expressly authorized otherwise. If you are not
the
 intended recipient, please contact the sender by reply email and
destroy all
 copies of the original message. Thank you.


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




Find out about young workers' safety needs at www.demandsafety.ca



CONFIDENTIALITY DISCLAIMER 

The information contained in this transmission may contain privileged and 
confidential information of WorkSafeBC - the Workers' Compensation Board. It is 
intended for review only by the person(s) named above. Dissemination, 
distribution or duplication of this communication is strictly prohibited by all 
recipients unless expressly authorized otherwise. If you are not the intended 
recipient, please contact the sender by reply email and destroy all copies of 
the original message. Thank you.



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



Re: [Axis2 v1.1] How can I get full XML from SOAP Request ?

2006-12-08 Thread Davanum Srinivas

See if it helps if you call contexteMessage.getEnvelope().build()
before you print it.

-- dims

On 12/8/06, John DeeBee [EMAIL PROTECTED] wrote:


Hi,

I'm working on server-side from Axis2 v1.1 and I need to get the whole XML
request in my WS skeleton (and after) to make other XML parsing and to log
every message going in and out from my webapp.
In Axis2 v1.0, I wrote a method called setOperationContext() in my skeleton
which retireved the full XML request by using
messageContext.getEnveloppe().toString().
But now I'm working with v1.1 and it doesn't work anymore. So I delete my
setOperationContext() method and, in my WS operation, I write this code to
replace :

MessageContext contexteMessage =
MessageContext.getCurrentMessageContext();
setFluxXML(contexteMessage.getEnvelope().toString());

But contexteMessage.getEnvelope().toString() gives me only the beginning
and the end of the request, not the full content.
I tried to make a logging module as described in documentation but the
result is the quite the same. I have the full xml from WS response but not
for request.
Who have a solution before I getting mad ?

John
 
 Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions
! Profitez des connaissances, des opinions et des expériences des
internautes sur Yahoo! Questions/Réponses.



--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

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



RE: Null pointer exception when using the WSDL2Java tool

2006-12-08 Thread Coleman, Piers

The WSDL successfully validated with the latest of XML Spy. Here is the
WSDL. Nothing too complex here I don't think:

definitions xmlns:tns=urn:wsbc.com:webportal:services:pocservice
xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:import1=urn:wsbc.com:webportal:messages
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns=http://schemas.xmlsoap.org/wsdl/; name=PocService
targetNamespace=urn:wsbc.com:webportal:services:pocservice
wsdl:documentation
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl//
types
xsd:schema
xsd:import
schemaLocation=EmployerInfoResponse.xsd
namespace=urn:wsbc.com:webportal:messages/
xsd:import
schemaLocation=EmployerInfoException.xsd
namespace=urn:wsbc.com:webportal:messages/
xsd:import
schemaLocation=EmployerInfoRequest.xsd
namespace=urn:wsbc.com:webportal:messages/
/xsd:schema
/types
message name=getEmployerInfoIn
wsdl:documentation
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl//
part name=messagePart
element=import1:GetEmployerInfo/
/message
message name=getEmployerInfoOut
wsdl:documentation
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl//
part name=messagePart
element=import1:GetEmployerInfoResponse/
/message
message name=employerInfoProcessingFaultIn
wsdl:documentation
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl//
part name=messagePart
element=import1:EmployerInfoProcessingFault/
/message
portType name=PocServiceInterface
wsdl:documentation
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl//
operation name=GetEmployerInfo
wsdl:documentation
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl//
input message=tns:getEmployerInfoIn/
output message=tns:getEmployerInfoOut/
fault name=EmployerInfoProcessingException
message=tns:employerInfoProcessingFaultIn/
/operation
/portType
binding name=PocService type=tns:PocServiceInterface
soap:binding
transport=http://schemas.xmlsoap.org/soap/http/
operation name=GetEmployerInfo
soap:operation
soapAction=urn:wsbc.com:webportal:services:pocservice:getEmployerInfoIn
 style=document/
input
soap:body use=literal/
/input
output
soap:body use=literal/
/output
fault name=EmployerInfoProcessingException
soap:fault
name=EmployerInfoProcessingException use=literal/
/fault
/operation
/binding
service name=PocServicePort
port name=PocServicePort binding=tns:PocService
soap:address
location=http://localhost:9080/axis2/pocwebservice/
/port
/service
/definitions 

-Original Message-
From: Coleman, Piers [mailto:[EMAIL PROTECTED] 
Sent: Friday, December 08, 2006 9:53 AM
To: axis-user@ws.apache.org
Subject: RE: Null pointer exception when using the WSDL2Java tool

I validated it using the interoperability tool from WS-I:
http://www.ws-i.org/deliverables/workinggroup.aspx?wg=testingtools. I
plugged this tool into SoapUI and everything passed ok.

I'm trying to use the Eclipse WTP that you suggested. It looks
promising, but I'm getting the following error when I try and validate
the WSDL. I'm currently googling to see if I can find anything.

WS-I: A problem occured while running the WS-I WSDL conformance check:
org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException: The WS-I
Test Assertion Document (TAD)document was either not found or could not
be processed.The WSDLAnalyzer was unable to validate the given WSDL
File.   Poc/Types   PocService.wsdl line 1  1165599589677   1

-Original Message-
From: robert lazarski [mailto:[EMAIL PROTECTED] 
Sent: Friday, December 08, 2006 4:23 AM
To: axis-user@ws.apache.org
Subject: Re: Null pointer exception when using the WSDL2Java tool

Have you validated the WSDL ? If it validates using Eclipses WTP,
xmlspy or the like, post the wsdl and maybe we can help.

Robert

On 12/7/06, Coleman, Piers [EMAIL PROTECTED] wrote:



 This is my first post, so here goes.

 I'm new to the Java world for creating Web services and I'm trying to
use
 the WSDL2Java tool to generate my server-side skeleton code. The
results are
 below. The WSDL file imports the XSD files that it uses.

 Could someone provide me with a few pointers on how to investigate
this
 further? I could post the WSDL as well.

 Thanks in advance.

 C:\WCA\PocWebService\TypesWSDL2Java.bat -uri 

Re: Null pointer exception when using the WSDL2Java tool

2006-12-08 Thread Davanum Srinivas

Piers,

Please log a bug in JIRA and upload the wsdl so that we can track this
bug and fix it.

thanks,
dims

On 12/8/06, Coleman, Piers [EMAIL PROTECTED] wrote:


The WSDL successfully validated with the latest of XML Spy. Here is the
WSDL. Nothing too complex here I don't think:

definitions xmlns:tns=urn:wsbc.com:webportal:services:pocservice
xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:import1=urn:wsbc.com:webportal:messages
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns=http://schemas.xmlsoap.org/wsdl/; name=PocService
targetNamespace=urn:wsbc.com:webportal:services:pocservice
wsdl:documentation
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl//
types
xsd:schema
xsd:import
schemaLocation=EmployerInfoResponse.xsd
namespace=urn:wsbc.com:webportal:messages/
xsd:import
schemaLocation=EmployerInfoException.xsd
namespace=urn:wsbc.com:webportal:messages/
xsd:import
schemaLocation=EmployerInfoRequest.xsd
namespace=urn:wsbc.com:webportal:messages/
/xsd:schema
/types
message name=getEmployerInfoIn
wsdl:documentation
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl//
part name=messagePart
element=import1:GetEmployerInfo/
/message
message name=getEmployerInfoOut
wsdl:documentation
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl//
part name=messagePart
element=import1:GetEmployerInfoResponse/
/message
message name=employerInfoProcessingFaultIn
wsdl:documentation
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl//
part name=messagePart
element=import1:EmployerInfoProcessingFault/
/message
portType name=PocServiceInterface
wsdl:documentation
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl//
operation name=GetEmployerInfo
wsdl:documentation
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl//
input message=tns:getEmployerInfoIn/
output message=tns:getEmployerInfoOut/
fault name=EmployerInfoProcessingException
message=tns:employerInfoProcessingFaultIn/
/operation
/portType
binding name=PocService type=tns:PocServiceInterface
soap:binding
transport=http://schemas.xmlsoap.org/soap/http/
operation name=GetEmployerInfo
soap:operation
soapAction=urn:wsbc.com:webportal:services:pocservice:getEmployerInfoIn
 style=document/
input
soap:body use=literal/
/input
output
soap:body use=literal/
/output
fault name=EmployerInfoProcessingException
soap:fault
name=EmployerInfoProcessingException use=literal/
/fault
/operation
/binding
service name=PocServicePort
port name=PocServicePort binding=tns:PocService
soap:address
location=http://localhost:9080/axis2/pocwebservice/
/port
/service
/definitions

-Original Message-
From: Coleman, Piers [mailto:[EMAIL PROTECTED]
Sent: Friday, December 08, 2006 9:53 AM
To: axis-user@ws.apache.org
Subject: RE: Null pointer exception when using the WSDL2Java tool

I validated it using the interoperability tool from WS-I:
http://www.ws-i.org/deliverables/workinggroup.aspx?wg=testingtools. I
plugged this tool into SoapUI and everything passed ok.

I'm trying to use the Eclipse WTP that you suggested. It looks
promising, but I'm getting the following error when I try and validate
the WSDL. I'm currently googling to see if I can find anything.

WS-I: A problem occured while running the WS-I WSDL conformance check:
org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException: The WS-I
Test Assertion Document (TAD)document was either not found or could not
be processed.The WSDLAnalyzer was unable to validate the given WSDL
File.   Poc/Types   PocService.wsdl line 1  1165599589677   1

-Original Message-
From: robert lazarski [mailto:[EMAIL PROTECTED]
Sent: Friday, December 08, 2006 4:23 AM
To: axis-user@ws.apache.org
Subject: Re: Null pointer exception when using the WSDL2Java tool

Have you validated the WSDL ? If it validates using Eclipses WTP,
xmlspy or the like, post the wsdl and maybe we can help.

Robert

On 12/7/06, Coleman, Piers [EMAIL PROTECTED] wrote:



 This is my first post, so here goes.

 I'm new to the Java world for creating Web services and I'm trying to
use
 the WSDL2Java tool to generate my server-side skeleton code. The
results are
 below. The WSDL file imports the XSD files that it uses.

 Could someone provide me 

RE: Null pointer exception when using the WSDL2Java tool

2006-12-08 Thread Coleman, Piers
Done:
https://issues.apache.org/jira/browse/AXIS2-1851
 

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Friday, December 08, 2006 1:32 PM
To: axis-user@ws.apache.org
Subject: Re: Null pointer exception when using the WSDL2Java tool

Piers,

Please log a bug in JIRA and upload the wsdl so that we can track this
bug and fix it.

thanks,
dims

On 12/8/06, Coleman, Piers [EMAIL PROTECTED] wrote:

 The WSDL successfully validated with the latest of XML Spy. Here is
the
 WSDL. Nothing too complex here I don't think:

 definitions xmlns:tns=urn:wsbc.com:webportal:services:pocservice
 xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/;
 xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
 xmlns:import1=urn:wsbc.com:webportal:messages
 xmlns:xsd=http://www.w3.org/2001/XMLSchema;
 xmlns=http://schemas.xmlsoap.org/wsdl/; name=PocService
 targetNamespace=urn:wsbc.com:webportal:services:pocservice
 wsdl:documentation
 xmlns:wsdl=http://schemas.xmlsoap.org/wsdl//
 types
 xsd:schema
 xsd:import
 schemaLocation=EmployerInfoResponse.xsd
 namespace=urn:wsbc.com:webportal:messages/
 xsd:import
 schemaLocation=EmployerInfoException.xsd
 namespace=urn:wsbc.com:webportal:messages/
 xsd:import
 schemaLocation=EmployerInfoRequest.xsd
 namespace=urn:wsbc.com:webportal:messages/
 /xsd:schema
 /types
 message name=getEmployerInfoIn
 wsdl:documentation
 xmlns:wsdl=http://schemas.xmlsoap.org/wsdl//
 part name=messagePart
 element=import1:GetEmployerInfo/
 /message
 message name=getEmployerInfoOut
 wsdl:documentation
 xmlns:wsdl=http://schemas.xmlsoap.org/wsdl//
 part name=messagePart
 element=import1:GetEmployerInfoResponse/
 /message
 message name=employerInfoProcessingFaultIn
 wsdl:documentation
 xmlns:wsdl=http://schemas.xmlsoap.org/wsdl//
 part name=messagePart
 element=import1:EmployerInfoProcessingFault/
 /message
 portType name=PocServiceInterface
 wsdl:documentation
 xmlns:wsdl=http://schemas.xmlsoap.org/wsdl//
 operation name=GetEmployerInfo
 wsdl:documentation
 xmlns:wsdl=http://schemas.xmlsoap.org/wsdl//
 input message=tns:getEmployerInfoIn/
 output message=tns:getEmployerInfoOut/
 fault name=EmployerInfoProcessingException
 message=tns:employerInfoProcessingFaultIn/
 /operation
 /portType
 binding name=PocService type=tns:PocServiceInterface
 soap:binding
 transport=http://schemas.xmlsoap.org/soap/http/
 operation name=GetEmployerInfo
 soap:operation

soapAction=urn:wsbc.com:webportal:services:pocservice:getEmployerInfoIn
  style=document/
 input
 soap:body use=literal/
 /input
 output
 soap:body use=literal/
 /output
 fault name=EmployerInfoProcessingException
 soap:fault
 name=EmployerInfoProcessingException use=literal/
 /fault
 /operation
 /binding
 service name=PocServicePort
 port name=PocServicePort binding=tns:PocService
 soap:address
 location=http://localhost:9080/axis2/pocwebservice/
 /port
 /service
 /definitions

 -Original Message-
 From: Coleman, Piers [mailto:[EMAIL PROTECTED]
 Sent: Friday, December 08, 2006 9:53 AM
 To: axis-user@ws.apache.org
 Subject: RE: Null pointer exception when using the WSDL2Java tool

 I validated it using the interoperability tool from WS-I:
 http://www.ws-i.org/deliverables/workinggroup.aspx?wg=testingtools. I
 plugged this tool into SoapUI and everything passed ok.

 I'm trying to use the Eclipse WTP that you suggested. It looks
 promising, but I'm getting the following error when I try and validate
 the WSDL. I'm currently googling to see if I can find anything.

 WS-I: A problem occured while running the WS-I WSDL conformance check:
 org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException: The WS-I
 Test Assertion Document (TAD)document was either not found or could
not
 be processed.The WSDLAnalyzer was unable to validate the given WSDL
 File.   Poc/Types   PocService.wsdl line 1  1165599589677   1

 -Original Message-
 From: robert lazarski [mailto:[EMAIL PROTECTED]
 Sent: Friday, December 08, 2006 4:23 AM
 To: axis-user@ws.apache.org
 Subject: Re: Null pointer exception when using the WSDL2Java tool

 Have you validated the WSDL ? If it validates using Eclipses WTP,
 xmlspy or the like, post the