date:20090204

Error establishing end to end conectivity in axis and jboss

2009-02-04 Thread Salman A. Kagzi

Hi All,

I have an axis web service which can acts as a client as well as server.

I am trying to deploy two instances of this web service on separate servers
and try and setup a communication link between them.

On M/C-1 I have installed axis2 1.3 under jboss 4.0.5 and have deployed my
web service.
On M/C-2 I have installed a standalone axis2 1.3 server and have my service
deployed there.
Both deployments are successful and no error/exception is seen.

I have a client running on M/C-3, this is a simple java program to call my
web service deployed on M/C-1 which will in turn call the web service on
M/C-2.
Web service on M/C-2 returns some data through callback to M/C-1 which will
in turn pass it over to M/C-3.

When I call this service I am getting following exception on axis2 server
running on M/C-2
org.apache.axis2.AxisFault: The endpoint reference (EPR) for the 
Operation not found is 
http://192.168.1.28:9000/axis2/services/ and the WSA 
Action = null
at 
org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java
:86)
at org.apache.axis2.engine.Phase.invoke(Phase.java:308)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:132)
at 
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HT
TPTransportUtils.java:275)
at 
org.apache.axis2.transport.nhttp.ServerWorker.processPost(ServerWorker.java:
207)
at 
org.apache.axis2.transport.nhttp.ServerWorker.run(ServerWorker.java:171)
at 
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run
Task(ThreadPoolExecutor.java:665)
at 
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)

I am trying to use HttpCoreNIOListener on both ends. As on later stage I
need to enable ssl as well for these web service


  8080 
  true 


PS: I have tested many different configurations and only this one works for
me.
On Jboss axis2.xml when I use SimpleHTTPServer for transportReceiver and
CommonsHTTPTransportSender for transportSender and disable global addressing
module, end to end communication is achieved. But this is not acceptable as
on later stage I need to enable ssl also and am forced to use non-blocking
methods.

I have been working out for 5-6 days to figure this out and am still no
where. Any help would be appreciated.

-Salman

Re: HTTP status

2009-02-04 Thread Guo Tianchong

hi, Sriram:

I think I met the same problem as yours.

My application asks the webservice to return the http 204 status.

My solution is to put the following code snippet in my ServiceClass's method.

HttpServletResponse resp = 
(HttpServletResponse)MessageContext.getCurrentMessageContext().getProperty(HTTPConstants.MC_HTTP_SERVLETRESPONSE);
resp.setStatus(204);


Using a kind of Http Monitor (ex: Live HTTP headers in Firefox), I could find 
the Http Response header's status is 204.


>All

But I put the following code snippet in my outflow's handler,

public InvocationResponse invoke(MessageContext msgContext) throws AxisFault {
..
HttpServletResponse response = 
(HttpServletResponse)msgContext.getProperty(HTTPConstants.MC_HTTP_SERVLETRESPONSE);
response.setStatus(204);
..
}

It always throw the NullPointerException for "response.setStatus(204);" 
statement.

Does the handler can not get HttpServletResponse?
Any ideas?

Thanks
Guo.



  - Original Message - 
  From: sri ram
  To: axis-user@ws.apache.org
  Sent: Monday, February 02, 2009 6:32 PM
  Subject: Re: HTTP status


Can someone give some insight on this

--- On Mon, 2/2/09, sri ram  wrote:

  From: sri ram 
  Subject: HTTP status
  To: axis-user@ws.apache.org
  Date: Monday, 2 February, 2009, 1:55 PM


Hi all,
I am using Axis 2.1.4 and XMLBeans as my databinding.
I have extended AxisServlet .If I get the proper response
with no exceptions I am getting HTTP status as 200, which is 
completely
fine but when I get any fault message its sets the status to 
500 automatically.
So I have added  the code to set the staus to 200 everytime 
even if there is an exception
but its not working .Does the Axis 2 apis prevent it from 
setting .

response.setContentType("text/xml; charset=UTF-8");
response.setStatus(200);

Do help me on this its urgent

Thanks ,
Sriram





--
  Add more friends to your messenger and enjoy! Invite them now.


--
  Unlimited freedom, unlimited storage. Get it now

Re: unsubscribe

2009-02-04 Thread m4rkuz

Sorry, my wrong, I was trying to unsubscribe from another list, and got
mixed up..




Marcus V. Sánchez D.
__
Enterprise Developer.
Sun Certified Java Programmer (SCJP)


On Wed, Feb 4, 2009 at 2:59 PM, Andreas Veithen
wrote:

> Christopher,
>
> If you want to unsubscribe, you need to send a mail to
> axis-user-unsubscr...@ws.apache.org.
>
> Andreas
>
> On Wed, Feb 4, 2009 at 20:56, Meeusen, Christopher W.
>  wrote:
> > unsubscribe
> > 
> > From: axis-user-return-77544-meeusen.christopher=mayo@ws.apache.org
> > [mailto:axis-user-return-77544-Meeusen.Christopher=mayo.edu@
> ws.apache.org]
> > On Behalf Of Nandana Mihindukulasooriya
> > Sent: Wednesday, February 04, 2009 12:30 PM
> > To: axis-user@ws.apache.org
> > Subject: Re: Problem building proper Policy file ...
> >
> > Hi Marcus,
> >  try changing
> >
> >  > sp:IncludeToken="
> http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/Never";>
> >
> > to
> >
> >  > sp:IncludeToken="
> http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient
> ">
> >
> > in the  assertion.
> >
> > thanks,
> > nandana
> >
> > On Wed, Feb 4, 2009 at 11:26 PM, m4rkuz  wrote:
> >>
> >> HI Nandana,
> >>
> >> Attached to this message is the soap message generated by rampart(the
> one
> >> that fails), is quite different and the first big difference I see is
> that
> >> oracle made soap has two (2) BinarySecurityToken and the rampart made
> just
> >> have one.
> >>
> >> the error I get in the client side wrap around the soap response message
> >> is:
> >>
> >> InvalidSecurity FAULT MESSAGE: An invalid token was provided
> >>
> >>
> >>
> >> Any Ideas?
> >>
> >> I would ask for the Oracle Log, to post it.
> >>
> >>
> >> Marcus V. Sánchez D.
> >> __
> >> Enterprise Developer.
> >> Sun Certified Java Programmer (SCJP)
> >>
> >>
> >> On Wed, Feb 4, 2009 at 12:21 PM, Nandana Mihindukulasooriya
> >>  wrote:
> >>>
> >>> Hi Marcus,
> >>>From the first look, it seems the policy you have matches the
> >>> success SOAP message. Do you get an error from the OWM side when you
> use
> >>> this policy at the client ? If so what is the error message ? The
> returning
> >>> message may not say what the error is, but if you have access to the
> OWM
> >>> logs, you will be able to find out what the error is. And can you
> attach the
> >>> message generated with this policy in Axis2/Rampart client so we can
> compare
> >>> it.
> >>>
> >>> thanks,
> >>> nandana
> >>>
> >>> On Wed, Feb 4, 2009 at 10:37 PM, m4rkuz  wrote:
> 
>  Hi Eeveryone,
> 
>  I've trying for a while now to make a proper client for a web service
>  made in oracle (OWM ) with Axis2 and Rampart, I had been able to
> overcome
>  some issues about x509v3 and the hole signing process but now in the
> last
>  part the Encription I just don't know how to declare it properly for
> the
>  client to sussesfuly call the WS.
> 
>  I had an example of a suscessfull soap message (oracle client
> generated)
>  and a copy of my policy for someone to take a quick look and help me
> out.
> 
> 
>  The files are attached.
> 
>  that same policy file and without the encription configuration works
>  fine if the WS require only signing, so is not totally wrong.
> 
> 
> 
>  If someone had an idea how to mimic that message from axis2, would
> help
>  me a lot,
> 
> 
>  Marcus V. Sánchez D.
>  __
>  Enterprise Developer.
>  Sun Certified Java Programmer (SCJP)
> >>>
> >>>
> >>>
> >>> --
> >>> Nandana Mihindukulasooriya
> >>> WSO2 inc.
> >>>
> >>> http://nandana83.blogspot.com/
> >>> http://www.wso2.org
> >>
> >
> >
> >
> > --
> > Nandana Mihindukulasooriya
> > WSO2 inc.
> >
> > http://nandana83.blogspot.com/
> > http://www.wso2.org
> >
>

RE: InOnlyAxisOperation

2009-02-04 Thread Sanjay Gupta

Hi,

I read some messages which pointed out at server.xml.  My server.xml looks good 
as far as I can see. But I still have issue. I even tried removing in-only 
receiver without any luck.

 

http://customer.ws.ccb.primalsw.com/";>



Customer Service





http://www.w3.org/2004/08/wsdl/in-only";

 
class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver"/>

http://www.w3.org/2004/08/wsdl/in-out";

 
class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>



http://customer.ws.ccb.primalsw.com/xsd"/>

com.primalsw.ccb.ws.CustomerHandler



 

From: Sanjay Gupta [mailto:sanjay.gu...@primal.com] 
Sent: Wednesday, February 04, 2009 11:12 AM
To: axis-user@ws.apache.org
Subject: InOnlyAxisOperation

 

Hi,

I just have upgraded my axis 1.2 web services to 1.4.1 and getting error while 
calling a service which returns nothing(void). See the stack trace below. The 
doc mentions these four types of operations but I don't know which one to pick 
and how to set it during client generation. 

DoInOnly, NoParameters, TwoWayOneParameterEcho, and MultipleParametersAddItem

 

I have both types of operations with return and without return. All my 
operations takes some kind of argument simple as well as some that takes 
customer objects.  Any help will be greatly appreciated.

 

Sanjay

 

[ERROR] An access occurred that is not valid.

java.lang.UnsupportedOperationException: An access occurred that is not valid.

at 
org.apache.axis2.description.InOnlyAxisOperation.getMessage(InOnlyAxisOperation.java:109)

at 
org.apache.axis2.util.MessageContextBuilder.createOutMessageContext(MessageContextBuilder.java:190)

at 
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.jav

:37)

at 
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100)

at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)

at 
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)

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

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

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

at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)

at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)

at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)

at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)

at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)

at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)

at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)

at 
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)

at java.lang.Thread.run(Thread.java:619)

Re: unsubscribe

2009-02-04 Thread Andreas Veithen

Christopher,

If you want to unsubscribe, you need to send a mail to
axis-user-unsubscr...@ws.apache.org.

Andreas

On Wed, Feb 4, 2009 at 20:56, Meeusen, Christopher W.
 wrote:
> unsubscribe
> 
> From: axis-user-return-77544-meeusen.christopher=mayo@ws.apache.org
> [mailto:axis-user-return-77544-meeusen.christopher=mayo@ws.apache.org]
> On Behalf Of Nandana Mihindukulasooriya
> Sent: Wednesday, February 04, 2009 12:30 PM
> To: axis-user@ws.apache.org
> Subject: Re: Problem building proper Policy file ...
>
> Hi Marcus,
>  try changing
>
>  sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/Never";>
>
> to
>
>  sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient";>
>
> in the  assertion.
>
> thanks,
> nandana
>
> On Wed, Feb 4, 2009 at 11:26 PM, m4rkuz  wrote:
>>
>> HI Nandana,
>>
>> Attached to this message is the soap message generated by rampart(the one
>> that fails), is quite different and the first big difference I see is that
>> oracle made soap has two (2) BinarySecurityToken and the rampart made just
>> have one.
>>
>> the error I get in the client side wrap around the soap response message
>> is:
>>
>> InvalidSecurity FAULT MESSAGE: An invalid token was provided
>>
>>
>>
>> Any Ideas?
>>
>> I would ask for the Oracle Log, to post it.
>>
>>
>> Marcus V. Sánchez D.
>> __
>> Enterprise Developer.
>> Sun Certified Java Programmer (SCJP)
>>
>>
>> On Wed, Feb 4, 2009 at 12:21 PM, Nandana Mihindukulasooriya
>>  wrote:
>>>
>>> Hi Marcus,
>>>From the first look, it seems the policy you have matches the
>>> success SOAP message. Do you get an error from the OWM side when you use
>>> this policy at the client ? If so what is the error message ? The returning
>>> message may not say what the error is, but if you have access to the OWM
>>> logs, you will be able to find out what the error is. And can you attach the
>>> message generated with this policy in Axis2/Rampart client so we can compare
>>> it.
>>>
>>> thanks,
>>> nandana
>>>
>>> On Wed, Feb 4, 2009 at 10:37 PM, m4rkuz  wrote:

 Hi Eeveryone,

 I've trying for a while now to make a proper client for a web service
 made in oracle (OWM ) with Axis2 and Rampart, I had been able to overcome
 some issues about x509v3 and the hole signing process but now in the last
 part the Encription I just don't know how to declare it properly for the
 client to sussesfuly call the WS.

 I had an example of a suscessfull soap message (oracle client generated)
 and a copy of my policy for someone to take a quick look and help me out.


 The files are attached.

 that same policy file and without the encription configuration works
 fine if the WS require only signing, so is not totally wrong.



 If someone had an idea how to mimic that message from axis2, would help
 me a lot,


 Marcus V. Sánchez D.
 __
 Enterprise Developer.
 Sun Certified Java Programmer (SCJP)
>>>
>>>
>>>
>>> --
>>> Nandana Mihindukulasooriya
>>> WSO2 inc.
>>>
>>> http://nandana83.blogspot.com/
>>> http://www.wso2.org
>>
>
>
>
> --
> Nandana Mihindukulasooriya
> WSO2 inc.
>
> http://nandana83.blogspot.com/
> http://www.wso2.org
>

unsubscribe

2009-02-04 Thread Meeusen, Christopher W.

unsubscribe

From: axis-user-return-77544-meeusen.christopher=mayo@ws.apache.org 
[mailto:axis-user-return-77544-meeusen.christopher=mayo@ws.apache.org] On 
Behalf Of Nandana Mihindukulasooriya
Sent: Wednesday, February 04, 2009 12:30 PM
To: axis-user@ws.apache.org
Subject: Re: Problem building proper Policy file ...

Hi Marcus, 
 try changing 

http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/Never";>

to 

http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient";>

in the  assertion. 

thanks,
nandana

On Wed, Feb 4, 2009 at 11:26 PM, m4rkuz  wrote:

HI Nandana,

Attached to this message is the soap message generated by rampart(the 
one that fails), is quite different and the first big difference I see is that 
oracle made soap has two (2) BinarySecurityToken and the rampart made just have 
one.

the error I get in the client side wrap around the soap response 
message is:

InvalidSecurity FAULT MESSAGE: An invalid token was provided

Any Ideas? 

I would ask for the Oracle Log, to post it. 

Marcus V. Sánchez D.
__
Enterprise Developer.
Sun Certified Java Programmer (SCJP)

On Wed, Feb 4, 2009 at 12:21 PM, Nandana Mihindukulasooriya 
 wrote:

Hi Marcus,
   From the first look, it seems the policy you have 
matches the success SOAP message. Do you get an error from the OWM side when 
you use this policy at the client ? If so what is the error message ? The 
returning message may not say what the error is, but if you have access to the 
OWM logs, you will be able to find out what the error is. And can you attach 
the message generated with this policy in Axis2/Rampart client so we can 
compare it. 

thanks,
nandana 

On Wed, Feb 4, 2009 at 10:37 PM, m4rkuz  
wrote:

Hi Eeveryone,

I've trying for a while now to make a proper client for 
a web service made in oracle (OWM ) with Axis2 and Rampart, I had been able to 
overcome some issues about x509v3 and the hole signing process but now in the 
last part the Encription I just don't know how to declare it properly for the 
client to sussesfuly call the WS.

I had an example of a suscessfull soap message (oracle 
client generated) and a copy of my policy for someone to take a quick look and 
help me out.

The files are attached.

that same policy file and without the encription 
configuration works fine if the WS require only signing, so is not totally 
wrong.

If someone had an idea how to mimic that message from 
axis2, would help me a lot,

Marcus V. Sánchez D.
__
Enterprise Developer.
Sun Certified Java Programmer (SCJP)

-- 
Nandana Mihindukulasooriya  
WSO2 inc.

http://nandana83.blogspot.com/
http://www.wso2.org

-- 
Nandana Mihindukulasooriya  
WSO2 inc.

http://nandana83.blogspot.com/
http://www.wso2.org

InOnlyAxisOperation

2009-02-04 Thread Sanjay Gupta

Hi,

I just have upgraded my axis 1.2 web services to 1.4.1 and getting error while 
calling a service which returns nothing(void). See the stack trace below. The 
doc mentions these four types of operations but I don't know which one to pick 
and how to set it during client generation. 

DoInOnly, NoParameters, TwoWayOneParameterEcho, and MultipleParametersAddItem

 

I have both types of operations with return and without return. All my 
operations takes some kind of argument simple as well as some that takes 
customer objects.  Any help will be greatly appreciated.

 

Sanjay

 

[ERROR] An access occurred that is not valid.

java.lang.UnsupportedOperationException: An access occurred that is not valid.

at 
org.apache.axis2.description.InOnlyAxisOperation.getMessage(InOnlyAxisOperation.java:109)

at 
org.apache.axis2.util.MessageContextBuilder.createOutMessageContext(MessageContextBuilder.java:190)

at 
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.jav

:37)

at 
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100)

at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)

at 
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)

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

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

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

at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)

at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)

at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)

at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)

at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)

at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)

at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)

at 
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)

at java.lang.Thread.run(Thread.java:619)

[Axis2] Need help embedding axis2 in desktop application

2009-02-04 Thread Khristian

Hi!
I'm trying to create a java application (which will later run as a
daemon) that uses axis to offer some web services.
Following some tutorials, I got the web service to run in axis2's own
server (deployed as a .aar file) with an automatically-generated
client (with the eclipse codegen plugin).
Next thing I did was to try and insert the axis server into my
application (following the tutorial at http://wso2.org/library/83).
The thing is, I have Axis2 1.4.1 and I couldn't adapt that code (the
one in the comments) to work here.

The server code:
[code]
package ws.example;

import java.util.HashMap;
import java.util.Map;

import org.apache.axis2.context.ConfigurationContext;
import org.apache.axis2.context.ConfigurationContextFactory;
import org.apache.axis2.description.AxisService;
import org.apache.axis2.rpc.receivers.*;
import org.apache.axis2.transport.http.SimpleHTTPServer;

public class EmbeddedAxis2Server {
public static void main(String[] args) throws Exception {

ConfigurationContext context = ConfigurationContextFactory
.createConfigurationContextFromFileSystem(null, 
null);

Map mrMap = new HashMap();

mrMap.put(" http://www.w3.org/ns/wsdl/in-out";, 
RPCMessageReceiver.class
.newInstance());

AxisService service = AxisService
.createService(

TemperatureConverter.class.getName(),
context.getAxisConfiguration(),
mrMap,
"http://example.ws";,

"http://localhost:8080/axis2/services/TemperatureConverter?xsd";,

EmbeddedAxis2Server.class.getClassLoader());

context.getAxisConfiguration().addService(service);

SimpleHTTPServer server = new SimpleHTTPServer(context, 8080);

server.start();
}
}
[/code]

And here the POJO (some silly example :P ):
[code]
package ws.example;

/**
 * Temperature Converter Implementation Class
 */
public class TemperatureConverter {
/**
 * util method to convert celsius to fahrenheit
 * @param cValue : double value of celsius
 * @return calculated value of fahrenheit
 */
public double c2fConvertion(double cValue) {
   return ((cValue * 9.0)/5.0 )+ 32.0;
}

 /**
 * util method to convert fahrenheit to celsius
 * @param fValue : double value of fahrenheit
 * @return calculated value of celsius
 */
public double f2cConvertion(double fValue) {
   return ((fValue - 32.0) * 5.0) / 9.0;
}
}
[/code]

The client code is generated from the wsdl file using the Axis2
eclipse plugins, and worked fine with the .aar file deployed into the
full axis2 server.
When I run my server, I can even access it via browser, check the
running service and get its wsdl/xsd xml file. Upon running the client
I get this error:

[stacktrace]
org.apache.axis2.AxisFault: Message Receiver not found for
AxisOperation: c2fConvertion
at 
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:512)
at 
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:370)
at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
at 
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
at 
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at 
ws.example.TemperatureConverterStub.c2FConvertion(TemperatureConverterStub.java:474)
at 
ws.example.TemperatureConverterServiceClient.main(TemperatureConverterServiceClient.java:12)

Can someone give me some help here? I'm still noobish at axis2, two
days since I first found its webpage :P

TIA,

-- 
Khristian Alexander Schönrock
http://derkosak.blogspot.com - Meu blógue!

Re: Problem building proper Policy file ...

2009-02-04 Thread m4rkuz

It Worked like a charm!!

So many thanks!!!



Marcus V. Sánchez D.
__
Enterprise Developer.
Sun Certified Java Programmer (SCJP)

PD: Thanks Again!!


On Wed, Feb 4, 2009 at 1:29 PM, Nandana Mihindukulasooriya <
nandana@gmail.com> wrote:

> Hi Marcus,
>  try changing
>
> http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/Never";>
>
> to
>
> http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient
> ">
>
> in the  assertion.
>
> thanks,
> nandana
>
>
> On Wed, Feb 4, 2009 at 11:26 PM, m4rkuz  wrote:
>
>> HI Nandana,
>>
>> Attached to this message is the soap message generated by rampart(the one
>> that fails), is quite different and the first big difference I see is that
>> oracle made soap has two (2) BinarySecurityToken and the rampart made just
>> have one.
>>
>> the error I get in the client side wrap around the soap response message
>> is:
>>
>> *InvalidSecurity FAULT MESSAGE: An invalid token was provided*
>>
>>
>>
>> Any Ideas?
>>
>> I would ask for the Oracle Log, to post it.
>>
>>
>> Marcus V. Sánchez D.
>> __
>> Enterprise Developer.
>> Sun Certified Java Programmer (SCJP)
>>
>>
>> On Wed, Feb 4, 2009 at 12:21 PM, Nandana Mihindukulasooriya <
>> nandana@gmail.com> wrote:
>>
>>> Hi Marcus,
>>>From the first look, it seems the policy you have matches the
>>> success SOAP message. Do you get an error from the OWM side when you use
>>> this policy at the client ? If so what is the error message ? The returning
>>> message may not say what the error is, but if you have access to the OWM
>>> logs, you will be able to find out what the error is. And can you attach the
>>> message generated with this policy in Axis2/Rampart client so we can compare
>>> it.
>>>
>>> thanks,
>>> nandana
>>>
>>>
>>> On Wed, Feb 4, 2009 at 10:37 PM, m4rkuz  wrote:
>>>
 Hi Eeveryone,

 I've trying for a while now to make a proper client for a web service
 made in oracle (OWM ) with Axis2 and Rampart, I had been able to overcome
 some issues about x509v3 and the hole signing process but now in the last
 part the Encription I just don't know how to declare it properly for the
 client to sussesfuly call the WS.

 I had an example of a suscessfull soap message (oracle client generated)
 and a copy of my policy for someone to take a quick look and help me out.


 The files are attached.

 that same policy file and without the encription configuration works
 fine if the WS require only signing, so is not totally wrong.



 If someone had an idea how to mimic that message from axis2, would help
 me a lot,


 Marcus V. Sánchez D.
 __
 Enterprise Developer.
 Sun Certified Java Programmer (SCJP)

>>>
>>>
>>>
>>> --
>>> Nandana Mihindukulasooriya
>>> WSO2 inc.
>>>
>>> http://nandana83.blogspot.com/
>>> http://www.wso2.org
>>>
>>
>>
>
>
> --
> Nandana Mihindukulasooriya
> WSO2 inc.
>
> http://nandana83.blogspot.com/
> http://www.wso2.org
>

Re: Problem building proper Policy file ...

2009-02-04 Thread Nandana Mihindukulasooriya

Hi Marcus,
 try changing

http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/Never";>

to

http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient
">

in the  assertion.

thanks,
nandana

On Wed, Feb 4, 2009 at 11:26 PM, m4rkuz  wrote:

> HI Nandana,
>
> Attached to this message is the soap message generated by rampart(the one
> that fails), is quite different and the first big difference I see is that
> oracle made soap has two (2) BinarySecurityToken and the rampart made just
> have one.
>
> the error I get in the client side wrap around the soap response message
> is:
>
> *InvalidSecurity FAULT MESSAGE: An invalid token was provided*
>
>
>
> Any Ideas?
>
> I would ask for the Oracle Log, to post it.
>
>
> Marcus V. Sánchez D.
> __
> Enterprise Developer.
> Sun Certified Java Programmer (SCJP)
>
>
> On Wed, Feb 4, 2009 at 12:21 PM, Nandana Mihindukulasooriya <
> nandana@gmail.com> wrote:
>
>> Hi Marcus,
>>From the first look, it seems the policy you have matches the
>> success SOAP message. Do you get an error from the OWM side when you use
>> this policy at the client ? If so what is the error message ? The returning
>> message may not say what the error is, but if you have access to the OWM
>> logs, you will be able to find out what the error is. And can you attach the
>> message generated with this policy in Axis2/Rampart client so we can compare
>> it.
>>
>> thanks,
>> nandana
>>
>>
>> On Wed, Feb 4, 2009 at 10:37 PM, m4rkuz  wrote:
>>
>>> Hi Eeveryone,
>>>
>>> I've trying for a while now to make a proper client for a web service
>>> made in oracle (OWM ) with Axis2 and Rampart, I had been able to overcome
>>> some issues about x509v3 and the hole signing process but now in the last
>>> part the Encription I just don't know how to declare it properly for the
>>> client to sussesfuly call the WS.
>>>
>>> I had an example of a suscessfull soap message (oracle client generated)
>>> and a copy of my policy for someone to take a quick look and help me out.
>>>
>>>
>>> The files are attached.
>>>
>>> that same policy file and without the encription configuration works fine
>>> if the WS require only signing, so is not totally wrong.
>>>
>>>
>>>
>>> If someone had an idea how to mimic that message from axis2, would help
>>> me a lot,
>>>
>>>
>>> Marcus V. Sánchez D.
>>> __
>>> Enterprise Developer.
>>> Sun Certified Java Programmer (SCJP)
>>>
>>
>>
>>
>> --
>> Nandana Mihindukulasooriya
>> WSO2 inc.
>>
>> http://nandana83.blogspot.com/
>> http://www.wso2.org
>>
>
>


-- 
Nandana Mihindukulasooriya
WSO2 inc.

http://nandana83.blogspot.com/
http://www.wso2.org

Re: Axis 1.4.1 POJO problem

2009-02-04 Thread Nandana Mihindukulasooriya

No. Take a look at [1]

thanks,
nandana

[1] - http://marc.info/?l=axis-user&m=116242240709383&w=2

On Wed, Feb 4, 2009 at 11:24 PM, Chris van Es wrote:

>  Am I right in assuming to that I should remove the services.xml file and
> place my wsdl file in the META-INF directory?
>
>
>
> *From:* keith chapman [mailto:keithgchap...@gmail.com]
> *Sent:* 04 February 2009 17:23
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Axis 1.4.1 POJO problem
>
>
>
> Hi Chris,
>
> I'm afraid you do not have control over this. Your options could be to save
> the generated WSDL, edit it and pack it into the aar and make Axis2 use that
> WSDL instead of generating one.
>
> Thanks,
> Keith.
>
> On Wed, Feb 4, 2009 at 6:28 PM, Chris van Es 
> wrote:
>
> Hi, I'm recently new to Axis2 and I'm working on a pretty simple web
> service. I'm generating the wsdl from java classes inside a service aar
> file. The resulting wsdl contains minOccurs="0" for all of the operation
> parmaters, is there a way to specify minOccurs="1" or something similar to
> flag these as mandatory paramaters?
>
>
>
> Thanks.
>
>
>
> Chris.
>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>



-- 
Nandana Mihindukulasooriya
WSO2 inc.

http://nandana83.blogspot.com/
http://www.wso2.org

Re: Problem building proper Policy file ...

2009-02-04 Thread m4rkuz

HI Nandana,

Attached to this message is the soap message generated by rampart(the one
that fails), is quite different and the first big difference I see is that
oracle made soap has two (2) BinarySecurityToken and the rampart made just
have one.

the error I get in the client side wrap around the soap response message is:

*InvalidSecurity FAULT MESSAGE: An invalid token was provided*



Any Ideas?

I would ask for the Oracle Log, to post it.


Marcus V. Sánchez D.
__
Enterprise Developer.
Sun Certified Java Programmer (SCJP)


On Wed, Feb 4, 2009 at 12:21 PM, Nandana Mihindukulasooriya <
nandana@gmail.com> wrote:

> Hi Marcus,
>From the first look, it seems the policy you have matches the
> success SOAP message. Do you get an error from the OWM side when you use
> this policy at the client ? If so what is the error message ? The returning
> message may not say what the error is, but if you have access to the OWM
> logs, you will be able to find out what the error is. And can you attach the
> message generated with this policy in Axis2/Rampart client so we can compare
> it.
>
> thanks,
> nandana
>
>
> On Wed, Feb 4, 2009 at 10:37 PM, m4rkuz  wrote:
>
>> Hi Eeveryone,
>>
>> I've trying for a while now to make a proper client for a web service made
>> in oracle (OWM ) with Axis2 and Rampart, I had been able to overcome some
>> issues about x509v3 and the hole signing process but now in the last part
>> the Encription I just don't know how to declare it properly for the client
>> to sussesfuly call the WS.
>>
>> I had an example of a suscessfull soap message (oracle client generated)
>> and a copy of my policy for someone to take a quick look and help me out.
>>
>>
>> The files are attached.
>>
>> that same policy file and without the encription configuration works fine
>> if the WS require only signing, so is not totally wrong.
>>
>>
>>
>> If someone had an idea how to mimic that message from axis2, would help me
>> a lot,
>>
>>
>> Marcus V. Sánchez D.
>> __
>> Enterprise Developer.
>> Sun Certified Java Programmer (SCJP)
>>
>
>
>
> --
> Nandana Mihindukulasooriya
> WSO2 inc.
>
> http://nandana83.blogspot.com/
> http://www.wso2.org
>

http://schemas.xmlsoap.org/soap/envelope/";
	xmlns:xenc="http://www.w3.org/2001/04/xmlenc#";>
	
		http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
			soapenv:mustUnderstand="1">
			
http://www.w3.org/2001/04/xmlenc#rsa-1_5"; />
http://www.w3.org/2000/09/xmldsig#";>
	
		http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary";
			ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier";>G6Vav3SyoYV9uno6UbDKzGaVUeM=
	


	avZMHMrW37IHbzkj0UKvQih7Pwwvk1N4kxzeey9GJr2Pe4kVJ2T59i9OKAFNjkEJCQgaJ1lEj0DaWz2IiHRECKj152aYU4QXbV0wg8QmzW4BIfzEl71mDTpy4CcR/JDb6axRLpFW/UFQ2+3/ZLx+jfPnFIwUGJh1Q/AQ3fSlbrA=


	

			
			http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary";
ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3";
wsu:Id="CertId-909101">MIICXzCCAcigAwIBAgIESYhpJTANBgkqhkiG9w0BAQUFADB0MQswCQYDVQQGEwJGSzEWMBQGA1UECBMNRmFrZSBQcm92aW5jZTESMBAGA1UEBxMJRmFrZSBDSXR5MREwDwYDVQQKEwhGYWtlIE9yZzESMBAGA1UECxMJRmFrZSBVbml0MRIwEAYDVQQDEwlTYW0gRGF2aXMwHhcNMDkwMjAzMTU1NjIxWhcNMDkwNTA0MTU1NjIxWjB0MQswCQYDVQQGEwJGSzEWMBQGA1UECBMNRmFrZSBQcm92aW5jZTESMBAGA1UEBxMJRmFrZSBDSXR5MREwDwYDVQQKEwhGYWtlIE9yZzESMBAGA1UECxMJRmFrZSBVbml0MRIwEAYDVQQDEwlTYW0gRGF2aXMwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAJnZAvXEkOM6iUgpv9WqhR9/N1qBDzK8hYm0uifE8hyLvIc244PNyLHFH7ntTarRkL16L08Jz70cf4qddY9C2sa2EQYdYwCsAF1838SZ/B97KHAJCnXouDBcQZwqqlBPGtaspFLwokoZd6cg4eoCQ+fGJ5mJCYVopMpaeFuUQ6JhAgMBAAEwDQYJKoZIhvcNAQEFBQADgYEAFfwFCDFA+CnOpA+zH+n+oz3nyKrv8b8UgFOd0TWFMv/FltuS6jX1r/3xvazTFiW8lOVIpDGK7IMxpapzGtAoaA2JR4wtuskmbWat2O0Cj61b9nZhSBbDnkWtYADdQhei6yi0ha9wNkfG6mpE36LIBm+xRp9Xk35mWoh/xXEmwew=
			http://www.w3.org/2000/09/xmldsig#";
Id="Signature-3860801">

	http://www.w3.org/2001/10/xml-exc-c14n#"; />
	http://www.w3.org/2000/09/xmldsig#rsa-sha1"; />
	
		
			http://www.w3.org/2001/10/xml-exc-c14n#"; />
		
		http://www.w3.org/2000/09/xmldsig#sha1"; />
		yKlJJwkS91Vsk9u6KAwzjcxn0Xw=
	


	N6MBUwsnlpPhf9W3wdQJ2B08enQfDxN3/pNyM4rrlApgUspuKkHhj2lo/Ri1wcUBzmZCen1WQjn/
	MG78KhsPi0Qen639KSsjqRsNrD44KeaDDeqdukU3uI4KCDKTz+vc9Xry1hc1YxyiYVqf4kEVIQzi
	pi3IK6AxLfSmJi+orao= 

	http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
		wsu:Id="STRId-25610032">
		http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"; />
	

			
		
	
	http://docs.oasis-open.org/wss/2004/01/oasis-200401

RE: Axis 1.4.1 POJO problem

2009-02-04 Thread Chris van Es

Am I right in assuming to that I should remove the services.xml file and
place my wsdl file in the META-INF directory?

From: keith chapman [mailto:keithgchap...@gmail.com] 
Sent: 04 February 2009 17:23
To: axis-user@ws.apache.org
Subject: Re: Axis 1.4.1 POJO problem

Hi Chris,

I'm afraid you do not have control over this. Your options could be to
save the generated WSDL, edit it and pack it into the aar and make Axis2
use that WSDL instead of generating one.

Thanks,
Keith.

On Wed, Feb 4, 2009 at 6:28 PM, Chris van Es 
wrote:

Hi, I'm recently new to Axis2 and I'm working on a pretty simple web
service. I'm generating the wsdl from java classes inside a service aar
file. The resulting wsdl contains minOccurs="0" for all of the operation
parmaters, is there a way to specify minOccurs="1" or something similar
to flag these as mandatory paramaters?

Thanks.

Chris.

-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

Re: Axis 1.4.1 POJO problem

2009-02-04 Thread keith chapman

Hi Chris,

I'm afraid you do not have control over this. Your options could be to save
the generated WSDL, edit it and pack it into the aar and make Axis2 use that
WSDL instead of generating one.

Thanks,
Keith.

On Wed, Feb 4, 2009 at 6:28 PM, Chris van Es wrote:

>  Hi, I'm recently new to Axis2 and I'm working on a pretty simple web
> service. I'm generating the wsdl from java classes inside a service aar
> file. The resulting wsdl contains minOccurs="0" for all of the operation
> parmaters, is there a way to specify minOccurs="1" or something similar to
> flag these as mandatory paramaters?
>
>
>
> Thanks.
>
>
>
> Chris.
>

-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

Re: Problem building proper Policy file ...

2009-02-04 Thread Nandana Mihindukulasooriya

Hi Marcus,
   From the first look, it seems the policy you have matches the success
SOAP message. Do you get an error from the OWM side when you use this policy
at the client ? If so what is the error message ? The returning message may
not say what the error is, but if you have access to the OWM logs, you will
be able to find out what the error is. And can you attach the message
generated with this policy in Axis2/Rampart client so we can compare it.

thanks,
nandana

On Wed, Feb 4, 2009 at 10:37 PM, m4rkuz  wrote:

> Hi Eeveryone,
>
> I've trying for a while now to make a proper client for a web service made
> in oracle (OWM ) with Axis2 and Rampart, I had been able to overcome some
> issues about x509v3 and the hole signing process but now in the last part
> the Encription I just don't know how to declare it properly for the client
> to sussesfuly call the WS.
>
> I had an example of a suscessfull soap message (oracle client generated)
> and a copy of my policy for someone to take a quick look and help me out.
>
>
> The files are attached.
>
> that same policy file and without the encription configuration works fine
> if the WS require only signing, so is not totally wrong.
>
>
>
> If someone had an idea how to mimic that message from axis2, would help me
> a lot,
>
>
> Marcus V. Sánchez D.
> __
> Enterprise Developer.
> Sun Certified Java Programmer (SCJP)
>

-- 
Nandana Mihindukulasooriya
WSO2 inc.

http://nandana83.blogspot.com/
http://www.wso2.org

Problem building proper Policy file ...

2009-02-04 Thread m4rkuz

Hi Eeveryone,

I've trying for a while now to make a proper client for a web service made
in oracle (OWM ) with Axis2 and Rampart, I had been able to overcome some
issues about x509v3 and the hole signing process but now in the last part
the Encription I just don't know how to declare it properly for the client
to sussesfuly call the WS.

I had an example of a suscessfull soap message (oracle client generated) and
a copy of my policy for someone to take a quick look and help me out.


The files are attached.

that same policy file and without the encription configuration works fine if
the WS require only signing, so is not totally wrong.



If someone had an idea how to mimic that message from axis2, would help me a
lot,


Marcus V. Sánchez D.
__
Enterprise Developer.
Sun Certified Java Programmer (SCJP)

http://schemas.xmlsoap.org/soap/envelope/";
	xmlns:xsd="http://www.w3.org/2001/XMLSchema";
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
	xmlns:ns0="http://test.heinsohn.com/types/";>
	
		http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
			xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
			xmlns:env="http://schemas.xmlsoap.org/soap/envelope/";>
			http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3";
EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary";
wsu:Id="aSfsuZGB0yY2p9x2idFRrag22"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";>
MIICYTCCAcqgAwIBAgIESYhp+jANBgkqhkiG9w0BAQUFADB1MQswCQYDVQQGEwJGSzEWMBQGA1UECBMNRmFrZSBQcm92aW5jZTESMBAGA1UEBxMJRmFrZSBDaXR5MREwDwYDVQQKEwhGYWtlIE9yZzESMBAGA1UECxMJRmFrZSBVbml0MRMwEQYDVQQDEwpEYXZlIFNhbWlzMB4XDTA5MDIwMzE1NTk1NFoXDTA5MDUwNDE1NTk1NFowdTELMAkGA1UEBhMCRksxFjAUBgNVBAgTDUZha2UgUHJvdmluY2UxEjAQBgNVBAcTCUZha2UgQ2l0eTERMA8GA1UEChMIRmFrZSBPcmcxEjAQBgNVBAsTCUZha2UgVW5pdDETMBEGA1UEAxMKRGF2ZSBTYW1pczCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA0KGfK7v/xLfKNFVGz2Ja3nhmlSUGQfmI+r/pSw632HDjqjbX8ZzPZPBw4WtVozxKkgymJLaw26Cru07LRW6a++2iUUhoxGkrz7O+3+fp0TdgMEDtWj92QJrn93IoBZOd43wkSHU6urZUOerfCrW7DK18uCxW8M5Pi4qYuAXKGL0CAwEAATANBgkqhkiG9w0BAQUFAAOBgQBo10BPLlr9ZLEhHt8Rfej6varvZGS+rm2WqAXTrZokRiq04i2zpp16jgf1ltCBI4EzU3uHBBAvnq3EhxNbc8Aad95r5K5JyU1Nd+3IdALKZLagasp1JgOiXmB8D1nCQvc1ao/LTuFfzyePNYOXWnsHskpUQ4d5jMfVZDFG5GClEg==
			
			http://www.w3.org/2001/04/xmlenc#";
xmlns:xenc="http://www.w3.org/2001/04/xmlenc#";>
http://www.w3.org/2001/04/xmlenc#rsa-1_5"; />
http://www.w3.org/2000/09/xmldsig#";>
	http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
		xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";>
		http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3";
			xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
			xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"; />
	


	
		k/V7ppQNywzQyu92y2SopAbZGTOHHlPz05i9oUEAkkoLTMJPiR0rcINP9C9BZ6ypPoSbguOYWbfzXHvNghdi1yNV95ahGRcegFWud01ok3q6h1uv6RCF3OudKiyGTtC2124qMP3hpxMBau/4tcebcuXvJLcsG49LBNP9n8quSU4=
	


	

			
			http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3";
EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary";
wsu:Id="_V0HeS0pOYm2iCVmURgcaUw22"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";>
MIICXzCCAcigAwIBAgIESYhpJTANBgkqhkiG9w0BAQUFADB0MQswCQYDVQQGEwJGSzEWMBQGA1UECBMNRmFrZSBQcm92aW5jZTESMBAGA1UEBxMJRmFrZSBDSXR5MREwDwYDVQQKEwhGYWtlIE9yZzESMBAGA1UECxMJRmFrZSBVbml0MRIwEAYDVQQDEwlTYW0gRGF2aXMwHhcNMDkwMjAzMTU1NjIxWhcNMDkwNTA0MTU1NjIxWjB0MQswCQYDVQQGEwJGSzEWMBQGA1UECBMNRmFrZSBQcm92aW5jZTESMBAGA1UEBxMJRmFrZSBDSXR5MREwDwYDVQQKEwhGYWtlIE9yZzESMBAGA1UECxMJRmFrZSBVbml0MRIwEAYDVQQDEwlTYW0gRGF2aXMwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAJnZAvXEkOM6iUgpv9WqhR9/N1qBDzK8hYm0uifE8hyLvIc244PNyLHFH7ntTarRkL16L08Jz70cf4qddY9C2sa2EQYdYwCsAF1838SZ/B97KHAJCnXouDBcQZwqqlBPGtaspFLwokoZd6cg4eoCQ+fGJ5mJCYVopMpaeFuUQ6JhAgMBAAEwDQYJKoZIhvcNAQEFBQADgYEAFfwFCDFA+CnOpA+zH+n+oz3nyKrv8b8UgFOd0TWFMv/FltuS6jX1r/3xvazTFiW8lOVIpDGK7IMxpapzGtAoaA2JR4wtuskmbWat2O0Cj61b9nZhSBbDnkWtYADdQhei6yi0ha9wNkfG6mpE36LIBm+xRp9Xk35mWoh/xXEmwew=
			
			http://www.w3.org/2000/09/xmldsig#";
xmlns:dsig="http://www.w3.org/2000/09/xmldsig#

Re: Axiom bug?

2009-02-04 Thread Andrei Ivanov

On Wed, Feb 4, 2009 at 5:41 PM, Andreas Veithen
 wrote:
> Andrei,
>
> What is the Axiom version you are using? If it is not 1.2.8 or a
> recent snapshot, please check against version 1.2.8. If you can
> confirm that the issue still exists in that version, please open a
> JIRA issue in the WSCOMMONS project.
>
1.2.8... it say right at the end of my email...
I'll open an issue...
Thanks

> Regards,
>
> Andreas
>
> On Wed, Feb 4, 2009 at 16:08, Andrei Ivanov  wrote:
>> Hello,
>> I'm trying to use Sandesha with Rampart and I think I've found a bug.
>> When the server is replying to a CreateSequence message, it gets to
>> RampartSender,
>> which calls org.apache.rampart.MessageBuilder.build(MessageContext msgCtx),
>> which verifies that the security header is empty and tries to remove it:
>>
>> if ( secHeader != null && secHeader.isEmpty(doc) ) {
>>   secHeader.removeSecurityHeader(doc);
>> }
>>
>> WSSecHeader.removeSecurityHeader(Document doc) does this:
>> ...
>> Node parent = securityHeader.getParentNode();
>> parent.removeChild(securityHeader);
>>
>> Parent:
>> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
>> xmlns:wsa="http://www.w3.org/2005/08/addressing";>
>>  > xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
>> soapenv:mustUnderstand="1" />
>>  
>> http://192.168.1.5:6060/axis2/services/personaldataserv...@286914895/
>>  
>> http://www.w3.org/2005/08/addressing/none
>>  urn:uuid:E3FC5985317BCF16351233758322948
>>  
>> http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequenceResponse
>>  urn:uuid:A07FCCC1972C7E06671233758319824
>> 
>>
>> securityHeader:
>> > xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
>> soapenv:mustUnderstand="1" />
>>
>> Then, org.apache.axiom.om.impl.dom.ParentNode.removeChild(Node) is
>> called and it gets to this, begining with line 482:
>> if (this.firstChild == tempNode) {
>>// If this is the first child
>>this.firstChild = null;
>>this.lastChild = null;
>>tempNode.parentNode = null;
>> }
>>
>> tempNode is the security header and it is equal to the firstChild of
>> the envelope header.
>> The firstChild is removed... then the lastChild(which is the relatesTo
>> child) is removed...
>>
>> The resulting envelope header is this:
>> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
>> xmlns:wsa="http://www.w3.org/2005/08/addressing"; />
>>
>> I'm using Axis-1.4.1, Addressing-1.41, Sandesha2-1.3, Rampart-1.4, Axiom 
>> 1.2.8
>> I've looked in the Axiom sources and it seems this code is from before
>> revision 389047 ("Moving doom into ws-commons axiom from axis2")
>>
>> I think this is a bug...
>> Am I right? Should I create an issue?
>>
>

Re: Axiom bug?

2009-02-04 Thread Andreas Veithen

Andrei,

What is the Axiom version you are using? If it is not 1.2.8 or a
recent snapshot, please check against version 1.2.8. If you can
confirm that the issue still exists in that version, please open a
JIRA issue in the WSCOMMONS project.

Regards,

Andreas

On Wed, Feb 4, 2009 at 16:08, Andrei Ivanov  wrote:
> Hello,
> I'm trying to use Sandesha with Rampart and I think I've found a bug.
> When the server is replying to a CreateSequence message, it gets to
> RampartSender,
> which calls org.apache.rampart.MessageBuilder.build(MessageContext msgCtx),
> which verifies that the security header is empty and tries to remove it:
>
> if ( secHeader != null && secHeader.isEmpty(doc) ) {
>   secHeader.removeSecurityHeader(doc);
> }
>
> WSSecHeader.removeSecurityHeader(Document doc) does this:
> ...
> Node parent = securityHeader.getParentNode();
> parent.removeChild(securityHeader);
>
> Parent:
>  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:wsa="http://www.w3.org/2005/08/addressing";>
>   xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
> soapenv:mustUnderstand="1" />
>  
> http://192.168.1.5:6060/axis2/services/personaldataserv...@286914895/
>  
> http://www.w3.org/2005/08/addressing/none
>  urn:uuid:E3FC5985317BCF16351233758322948
>  
> http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequenceResponse
>  urn:uuid:A07FCCC1972C7E06671233758319824
> 
>
> securityHeader:
>  xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> soapenv:mustUnderstand="1" />
>
> Then, org.apache.axiom.om.impl.dom.ParentNode.removeChild(Node) is
> called and it gets to this, begining with line 482:
> if (this.firstChild == tempNode) {
>// If this is the first child
>this.firstChild = null;
>this.lastChild = null;
>tempNode.parentNode = null;
> }
>
> tempNode is the security header and it is equal to the firstChild of
> the envelope header.
> The firstChild is removed... then the lastChild(which is the relatesTo
> child) is removed...
>
> The resulting envelope header is this:
>  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:wsa="http://www.w3.org/2005/08/addressing"; />
>
> I'm using Axis-1.4.1, Addressing-1.41, Sandesha2-1.3, Rampart-1.4, Axiom 1.2.8
> I've looked in the Axiom sources and it seems this code is from before
> revision 389047 ("Moving doom into ws-commons axiom from axis2")
>
> I think this is a bug...
> Am I right? Should I create an issue?
>

RE: Help with SimpleDeserializer encountered a child element

2009-02-04 Thread Dilshener Tezcan (extern HVB IS - UniCredit Group)

Hi 

In the mean time we have solved the problem.

It had to do with the wrong namespace in the WSDL2Java generated client code. 
It should have been 

http://de.hvb.aat.service.values, and was http://values.service.aat.hvb.de

 

So on the client side it was not able to find the registered BeanSerializer and 
used the SimpleDeserializer.

 

HTH to someone.

 

Tezcan

 

From: Dilshener Tezcan (extern HVB IS - UniCredit Group) 
[mailto:tezcan.dilshener.ext...@unicreditgroup.de] 
Sent: Dienstag, 3. Februar 2009 18:59
To: axis-user@ws.apache.org
Subject: Help with SimpleDeserializer encountered a child element

 

Hi,

Further to my help in below email, here is some more details.

The debug tells me that the parser is currently on element  and id id2 of the response.

That is how I figured it out that it fails to when trying to process the second 
element of the AcAATDocument[2] Array

 

Pls help

 

Cheers

Tezcan

 

 

From: Dilshener Tezcan (extern HVB IS - UniCredit Group) 
[mailto:tezcan.dilshener.ext...@unicreditgroup.de] 
Sent: Dienstag, 3. Februar 2009 18:45
To: axis-user@ws.apache.org
Subject: Help with SimpleDeserializer encountered a child element

 

Hi,

When my Axis client tries to parse the response it received from the 
WebService, it fails on an Array instance with the following exception.

org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which 
is NOT expected, in something it was trying to deserialize.

This occurs only when the array has more than one item!!! Otherwise it works 
fine.

I did a TCP/IP monitor and verified that the xml received is valid. 

3 things that makes it frustrating 

1-) another existing Axis WebService has the same method and returns the same 
type.

That works fine, when I compare the response with the one from the failure, I 
do not see any differences apart from order of attributes.

2-) this is Axis1.2RC1 and is for Italy. L(( I have no source code to debug the 
 Axis code, JAD decompiler produces rubbish)

3-) Google search says I should upgrade to latest Axis, but cannot do due to 
infrastructure restrictions !

Anyway, I would be so thankful if someone can give me couple guides to where to 
start looking into before I go mad.

Tezcan Dilshener
Satz Software & Consulting GmbH

HVB Information Services GmbH

Member of UniCredit Group
HII3ES Development Services Client Server
Am Tucherpark 12
D-80538 München 

Tel: +49 89 378-42158
mailto:tezcan.dilshener.ext...@hvbis.com 
 
http://www.hvbis.com   

The legal obligation information of HVB Information Services GmbH can be found 
at: http://www.hvbis.com/is/de/pub/441.htm 
 

Die gesetzlichen Pflichtangaben zur HVB Information Services GmbH finden Sie 
unter: http://www.hvbis.com/is/de/pub/441.htm 
 

Important Note:
This e-mail is only intended for the person or company/organisation named as 
recipient. It may contain trade secrets or undisclosed and

confidential information or information otherwise protected by work-product 
immunity or other legal regulations. If you have received this email by 
mistake, we kindly ask you not to copy this message or use it for any purpose 
nor disclose its contents to any other person. Please inform us immediately and 
delete the original document. In addition, please let us know if you or your 
company object to receiving e-mails for messages of this kind. 

Wichtiger Hinweis:
Diese E-Mail ist nur für die Person oder die Firma/Organisation bestimmt, die 
in der Empfängeradresse benannt ist und enthält u. U. Geschäftsgeheimnisse oder 
vertrauliche Informationen, die dem Schutz von Arbeitsergebnissen unterliegen 
oder sonst rechtlich geschützt sind. Wenn Sie nicht der angegebene Empfänger 
sind, bitten wir Sie, uns unverzüglich zu informieren und diese Nachricht zu 
vernichten und sie insbesondere nicht zu kopieren oder sie für irgendwelche 
anderen Zwecke zu verwenden, noch den Inhalt dieser Nachricht dritten Personen 
zugänglich zu machen. Bitte informieren Sie uns auch unverzüglich, wenn Sie 
oder Ihr Arbeitgeber nicht mit E-Mail Nachrichten dieser Art einverstanden sein 
sollten.

Axiom bug?

2009-02-04 Thread Andrei Ivanov

Hello,
I'm trying to use Sandesha with Rampart and I think I've found a bug.
When the server is replying to a CreateSequence message, it gets to
RampartSender,
which calls org.apache.rampart.MessageBuilder.build(MessageContext msgCtx),
which verifies that the security header is empty and tries to remove it:

if ( secHeader != null && secHeader.isEmpty(doc) ) {
   secHeader.removeSecurityHeader(doc);
}

WSSecHeader.removeSecurityHeader(Document doc) does this:
...
Node parent = securityHeader.getParentNode();
parent.removeChild(securityHeader);

Parent:
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:wsa="http://www.w3.org/2005/08/addressing";>
  http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
soapenv:mustUnderstand="1" />
  
http://192.168.1.5:6060/axis2/services/personaldataserv...@286914895/
  
http://www.w3.org/2005/08/addressing/none
  urn:uuid:E3FC5985317BCF16351233758322948
  
http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequenceResponse
  urn:uuid:A07FCCC1972C7E06671233758319824


securityHeader:
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
soapenv:mustUnderstand="1" />

Then, org.apache.axiom.om.impl.dom.ParentNode.removeChild(Node) is
called and it gets to this, begining with line 482:
if (this.firstChild == tempNode) {
// If this is the first child
this.firstChild = null;
this.lastChild = null;
tempNode.parentNode = null;
}

tempNode is the security header and it is equal to the firstChild of
the envelope header.
The firstChild is removed... then the lastChild(which is the relatesTo
child) is removed...

The resulting envelope header is this:
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:wsa="http://www.w3.org/2005/08/addressing"; />

I'm using Axis-1.4.1, Addressing-1.41, Sandesha2-1.3, Rampart-1.4, Axiom 1.2.8
I've looked in the Axiom sources and it seems this code is from before
revision 389047 ("Moving doom into ws-commons axiom from axis2")

I think this is a bug...
Am I right? Should I create an issue?

RE: Error in signature with X509Token

2009-02-04 Thread Erwin Reinhoud

Hello Tomaz,
 
Try also using rampart version 1.4 io 1.3.
 
Regards,
Erwin

  _  

Van: m4rkuz [mailto:m4r...@gmail.com] 
Verzonden: woensdag 4 februari 2009 15:16
Aan: axis-user@ws.apache.org
Onderwerp: Re: Error in signature with X509Token


Hi Tomaz,

I think you should attach you'r policy.xml file  and your services.xml, and 
maybe an example of the soap message generated, so it could be esiar to help 
you.



Marcus V. Sánchez D.
__
Enterprise Developer.
Sun Certified Java Programmer (SCJP)



On Wed, Feb 4, 2009 at 9:08 AM, TomazM  wrote:


Env:
   OS: Microsoft Windows XP [Version 5.1.2600]
   java: Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
   Tomcat: 6.0.16
   Axis2: 1.4.1
   Rampart: 1.3


I'm trying to sign message with my CallbackHandler and wsp:Policy, keys 
are in keystore of JKS type(server.jks and client.jks)

1) In service.xml  I have:
.

rampart.sign.service.SecurityHandler
   
   
   JKS
   keys\\server.jks
   



2) In client I also have my CallbackHandler and applying RampartConfig 
which use client.jks(contain server key)


The finger print of server and client certificates are the same in both 
keystore.



Error:
org.apache.axis2.AxisFault: Error in signature with X509Token
   at 
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:512)
   at 
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:370)
   at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
   at 
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
   at 
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)




Is anybody have a clue what I'm doing wrong




Best regards, Tomaz

calling webservice from browser

2009-02-04 Thread Asensio, Rodrigo

Hello, I use to do rpc webservices and test them thru a simple web
browser call like this

 

http://server/axis/services/myservice/dosomething?someparam=x

 

Now I'm doing jax-ws and I really don't know how to call the url to
execute the action. Is there any way to figure out ? thanks



Please be advised that this email may contain confidential information.
 If you are not the intended recipient, please do not read, copy or
re-transmit this email.  If you have received this email in error,
please notify us by email by replying to the sender and by telephone
(call us collect at +1 202-828-0850) and delete this message and any
attachments.  Thank you in advance for your cooperation and assistance.

In addition, Danaher and its subsidiaries disclaim that the content of
this email constitutes an offer to enter into, or the acceptance of,
any
contract or agreement or any amendment thereto; provided that the
foregoing disclaimer does not invalidate the binding effect of any
digital or other electronic reproduction of a manual signature that is
included in any attachment to this email.

Re: Error Generating Client Stub Code With Rampart Policy

2009-02-04 Thread Nan Null

Never mind, the message was produced in red color without any label
such as warning, or anything.  So I assume that is an error.  However,
it turns out that the code is generated fine and I have successfully
setup the security using rampart with Transport level security.

One deviation from the instruction is that I have to use
SSLEnabled="true" in the server.xml's HTTPS connector.

Thanks All.

On Wed, Feb 4, 2009 at 9:23 AM, Nan Null  wrote:
> I was following the document at http://wso2.org/library/3190 "Web
> Services Security with Apache Rampart – Part 1 ( Transport Level
> Security )" at the steps that generates the client stub code.
> I can see the service wsdl from the web browser.  The policy is
> essentially identical to that of the example, with the exception of a
> different package name for the PWCBHandler.
>
> I was able to generate the code before without the policy in place.
> With the policy, I get the following errors while generating the
> client stub code:
>
> cannot find a PolicyExtension to process
> http://schemas.xmlsoap.org/ws/2005/07/securitypolicytype assertions
> cannot find a PolicyExtension to process
> http://schemas.xmlsoap.org/ws/2005/07/securitypolicytype assertions
> cannot find a PolicyExtension to process
> http://schemas.xmlsoap.org/ws/2005/07/securitypolicytype assertions
> cannot find a PolicyExtension to process
> http://schemas.xmlsoap.org/ws/2005/07/securitypolicytype assertions
> cannot find a PolicyExtension to process
> http://schemas.xmlsoap.org/ws/2005/07/securitypolicytype assertions
> 
>
> I didn't find much useful info on Google.  Could someone please help?
>

Error Generating Client Stub Code With Rampart Policy

2009-02-04 Thread Nan Null

I was following the document at http://wso2.org/library/3190 "Web
Services Security with Apache Rampart – Part 1 ( Transport Level
Security )" at the steps that generates the client stub code.
I can see the service wsdl from the web browser.  The policy is
essentially identical to that of the example, with the exception of a
different package name for the PWCBHandler.

I was able to generate the code before without the policy in place.
With the policy, I get the following errors while generating the
client stub code:

cannot find a PolicyExtension to process
http://schemas.xmlsoap.org/ws/2005/07/securitypolicytype assertions
cannot find a PolicyExtension to process
http://schemas.xmlsoap.org/ws/2005/07/securitypolicytype assertions
cannot find a PolicyExtension to process
http://schemas.xmlsoap.org/ws/2005/07/securitypolicytype assertions
cannot find a PolicyExtension to process
http://schemas.xmlsoap.org/ws/2005/07/securitypolicytype assertions
cannot find a PolicyExtension to process
http://schemas.xmlsoap.org/ws/2005/07/securitypolicytype assertions


I didn't find much useful info on Google.  Could someone please help?

Re: Error in signature with X509Token

2009-02-04 Thread m4rkuz

Hi Tomaz,

I think you should attach you'r policy.xml file  and your services.xml, and
maybe an example of the soap message generated, so it could be esiar to help
you.



Marcus V. Sánchez D.
__
Enterprise Developer.
Sun Certified Java Programmer (SCJP)


On Wed, Feb 4, 2009 at 9:08 AM, TomazM  wrote:

> Env:
>OS: Microsoft Windows XP [Version 5.1.2600]
>java: Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
>Tomcat: 6.0.16
>Axis2: 1.4.1
>Rampart: 1.3
>
>
> I'm trying to sign message with my CallbackHandler and wsp:Policy, keys are
> in keystore of JKS type(server.jks and client.jks)
>
> 1) In service.xml  I have:
> .
>
> rampart.sign.service.SecurityHandler
>
> provider="org.apache.ws.security.components.crypto.Merlin">
> name="org.apache.ws.security.crypto.merlin.keystore.type">JKS
> name="org.apache.ws.security.crypto.merlin.file">keys\\server.jks
> name="org.apache.ws.security.crypto.merlin.keystore.password">
> 
>
>
> 2) In client I also have my CallbackHandler and applying RampartConfig
> which use client.jks(contain server key)
>
>
> The finger print of server and client certificates are the same in both
> keystore.
>
>
>
> Error:
> org.apache.axis2.AxisFault: Error in signature with X509Token
>at
> org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:512)
>at
> org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:370)
>at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
>at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
>at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
>
>
>
>
> Is anybody have a clue what I'm doing wrong
>
>
>
>
> Best regards, Tomaz
>

Error in signature with X509Token

2009-02-04 Thread TomazM

Env:
OS: Microsoft Windows XP [Version 5.1.2600]
java: Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
Tomcat: 6.0.16
Axis2: 1.4.1
Rampart: 1.3


I'm trying to sign message with my CallbackHandler and wsp:Policy, keys are in 
keystore of JKS type(server.jks and client.jks)

1) In service.xml  I have:
.
rampart.sign.service.SecurityHandler


JKS
keys\\server.jks




2) In client I also have my CallbackHandler and applying RampartConfig which 
use client.jks(contain server key)


The finger print of server and client certificates are the same in both 
keystore.



Error:
org.apache.axis2.AxisFault: Error in signature with X509Token
at 
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:512)
at 
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:370)
at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
at 
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
at 
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)




Is anybody have a clue what I'm doing wrong




Best regards, Tomaz
begin:vcard
fn;quoted-printable:Toma=C5=BE Majerhold
n;quoted-printable:Majerhold;Toma=C5=BE
org:ARNES, Slovenian NREN;Development team
adr:;;Jamova 39;Ljubljana;;;Slovenia
title:Developer
tel;work:+386 14798930
tel;fax:+386 1 479 88 99  
tel;home:+386 1425 38 01
tel;cell:(040) 757-229
url:http://www.arnes.si/
version:2.1
end:vcard

Axis 1.4.1 POJO problem

2009-02-04 Thread Chris van Es

Hi, I'm recently new to Axis2 and I'm working on a pretty simple web
service. I'm generating the wsdl from java classes inside a service aar
file. The resulting wsdl contains minOccurs="0" for all of the operation
parmaters, is there a way to specify minOccurs="1" or something similar
to flag these as mandatory paramaters?

 

Thanks.

 

Chris.

[AXIS2] Migration Issues for Axis1 -> Axis2

2009-02-04 Thread Sumit Gaikaiwari

Hi,

I am working on migration of web-services in our project from Axis1 to Axis2. 
In generating client/server classes I found those are not equivalent to classes 
generated by Axis1 WSDL2Java utility. We have an inheritance hierarchy of data 
classes created in WSDL.

When java classes are created using Axis1 wsdl2java, it adds a multi-value 
constructor to each class which passes values required by super class using 
super(param1, param2...) and instantiates it's own instance variable from 
remaining argument.

Whereas, axis2 wsdl2java do not generate any constructor, so the only 
constructor which can be invoked is default constructor. We were using 
multi-value constructors in earlier business logic, so if we use these new 
classes directly, we will have to change code in all such places. Is there any 
way Axis2 to generate classes in such manner? Please let me know if I should 
add any other option to create such hierarchy. I have tried using ADB and 
XMLBeans binding. Below is the command I tried by using ADB binding-

WSDL2Java -uri PlanIntegrationServices1_0.wsdl -d adb -s -o build2 -u


I have also attached wsdl as well as classes generated by axis1 and axis2 
style; you can notice there is a multiple arg constructor in axis1 style 
classes but not in axis2 generated code.

Kind Regards,
Sumit Gaikaiwari

RE: not showing stack trace when accessing the web service via browser

2009-02-04 Thread Yoav Naveh

More information on this matter.

On my development machine, this seems to work properly. I see an xml format
with a single element 

On my testing machine I see the full stack trace within an 
element (and no  element)

So this seems to be possible, with some configuration.

 

Anyone familiar with this issue?

 

From: Yoav Naveh [mailto:y...@contextin.com] 
Sent: Wednesday, February 04, 2009 11:26 AM
To: axis-user@ws.apache.org
Subject: not showing stack trace when accessing the web service via browser

 

Hi,

 

I have set up a web service that upon error throws an exception as fault.

The web service is accessible through tomcat by using my web browser.

 

Is there any way to have tomcat (I assume it is in charge of this part) not
display the stack trace, in case my service raises a fault?

 

Thanks!

Re: axis2 1.4.1 and rampart 1.4 issue

2009-02-04 Thread Nandana Mihindukulasooriya

You can find the necessary information here [1]. Rampart 1.4 didn't ship the
bouncy castle jars
due a patent issue, so you will have to download it from here [2] and copy
it too to the lib directory
and that will solve your problem.

thanks,
nandana

P.S : As Andrei said, don't cross post both lists [3].

[1] -
http://wso2.org/library/3190#Step_1._Deploying_the_module_and_necessary_jars
[2] - http://www.bouncycastle.org/latest_releases.html
[3] - http://ws.apache.org/axis2/guidelines.html

On Wed, Feb 4, 2009 at 2:47 PM, Andrei Ivanov wrote:

> Don't top post.
>
> On Wed, Feb 4, 2009 at 10:51 AM, Iyengar, Kumar 
> wrote:
> > What missing jars? I added Rampart 1.4 mar file to the modules directory
> > as per the instructions in the ReadMe file. I get the error:
>
> In your first mail, there are some exceptions like these:
> java.lang.ClassNotFoundException: org.apache.rampart.Rampart
>
> These tell you what classes are missing.
> If you search through your rampart jars, you'll find that rampart-core
> contains this class.
> Just copy it to the lib directory.
>

not showing stack trace when accessing the web service via browser

2009-02-04 Thread Yoav Naveh

Hi,

 

I have set up a web service that upon error throws an exception as fault.

The web service is accessible through tomcat by using my web browser.

 

Is there any way to have tomcat (I assume it is in charge of this part) not
display the stack trace, in case my service raises a fault?

 

Thanks!

Re: axis2 1.4.1 and rampart 1.4 issue

2009-02-04 Thread Andrei Ivanov

Don't top post.

On Wed, Feb 4, 2009 at 10:51 AM, Iyengar, Kumar  wrote:
> What missing jars? I added Rampart 1.4 mar file to the modules directory
> as per the instructions in the ReadMe file. I get the error:

In your first mail, there are some exceptions like these:
java.lang.ClassNotFoundException: org.apache.rampart.Rampart

These tell you what classes are missing.
If you search through your rampart jars, you'll find that rampart-core
contains this class.
Just copy it to the lib directory.

RE: axis2 1.4.1 and rampart 1.4 issue

2009-02-04 Thread Iyengar, Kumar

What missing jars? I added Rampart 1.4 mar file to the modules directory
as per the instructions in the ReadMe file. I get the error:

[ERROR] The rampart-1.4.mar module, which is not valid, caused 
> org.apache.rampart.Rampart
>
> org.apache.axis2.deployment.DeploymentException: 
> org.apache.rampart.Rampart
>
> at
> org.apache.axis2.deployment.repository.util.ArchiveReader.readModuleAr
> chive(ArchiveReader.java:531)
>...

Thanks for any help,

--kumar

-Original Message-
From: Andrei Ivanov [mailto:andrei.iva...@gmail.com] 
Sent: Tuesday, February 03, 2009 12:22 AM
To: axis-user@ws.apache.org
Subject: Re: axis2 1.4.1 and rampart 1.4 issue

On Tue, Feb 3, 2009 at 12:54 AM, Iyengar, Kumar 
wrote:
> Hi all,
>
>
>
> I was trying to setup UsernameToken with Axis2 1.4.1 and Rampart 1.4
and get
> the following error below. I checked and found the following entry in
JIRA
> but it does not exactly match the error that I get. Does anyone know
if the
> issue I am seeing is fixed or if there is a workaround?

Why don't you add the missing jars?
You can see in the exception what classes are missing...

>
>
>
> Thanks for any help,
>
>
>
> --kumar
>
>
>
>>>JIRA entry:
>
> Make AXIS2 1.4.1 compatible with Rampart/Rahas/Adressing
>
> 
>
>
>
>  Key: AXIS2-3989
>
>  URL: https://issues.apache.org/jira/browse/AXIS2-3989
>
>  Project: Axis 2.0 (Axis2)
>
>   Issue Type: Improvement
>
> Affects Versions: 1.4.1
>
>  Environment: Win32 (WinXP), AXIS2 1.4.1, Rampart 1.4, Rahas
1.4
>
> Reporter: Thomas Poetter
>
> Priority: Blocker
>
>
>
>
>
> When starting AXIS2 1.4.1 with the existing services and Rampart 1.4,
Rahas
>
> 1.4, the following error messages appear:
>
>
>
> [ERROR] The rahas-1.4.mar module, which is not valid, caused A
>
> ClassNotFoundException error occurred in loading the message receiver
>
> org.apache.rahas.STSMessageReceiver
>
> org.apache.axis2.deployment.DeploymentException: A
ClassNotFoundException
> error
>
> occurred in loading the message receiver
org.apache.rahas.STSMessageReceiver
>
> at
>
>
org.apache.axis2.deployment.repository.util.ArchiveReader.readModuleArch
ive(ArchiveReader.java:531)
>
> at
>
>
org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:71
)
>
> at
>
>
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(De
ploymentFileData.java:136)
>
> at
>
>
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.j
ava:597)
>
> at
>
>
org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.j
ava:237)
>
> at
>
>
org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.
java:68)
>
> at
>
>
org.apache.axis2.deployment.RepositoryListener.(RepositoryListener
.java:63)
>
> at
>
>
org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEn
gine.java:147)
>
> at
>
>
org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(
FileSystemConfigurator.java:133)
>
> at
>
>
org.apache.axis2.context.ConfigurationContextFactory.createConfiguration
Context(Confi
>
>
>
>
>
>>>MY ERROR:
>
> [ERROR] The rampart-1.4.mar module, which is not valid, caused
> org.apache.rampart.Rampart
>
> org.apache.axis2.deployment.DeploymentException:
org.apache.rampart.Rampart
>
> at
>
org.apache.axis2.deployment.repository.util.ArchiveReader.readModuleArch
ive(ArchiveReader.java:531)
>
> at
>
org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:71
)
>
> at
>
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(De
ploymentFileData.java:136)
>
> at
>
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.j
ava:597)
>
> at
>
org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.j
ava:237)
>
> at
>
org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.
java:68)
>
> at
>
org.apache.axis2.deployment.RepositoryListener.(RepositoryListener
.java:63)
>
> at
>
org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEn
gine.java:147)
>
> at
>
org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguratio
n(WarBasedAxisConfigurator.java:229)
>
> at
>
org.apache.axis2.context.ConfigurationContextFactory.createConfiguration
Context(ConfigurationContextFactory.java:68)
>
> at
>
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServle
t.java:516)
>
> at
> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:436)
>
> at
>
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.jav
a:1105)
>
> at
>
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932)
>
> at

Re: sandesha problem

2009-02-04 Thread Andrei Ivanov

Anyone?

On Mon, Feb 2, 2009 at 11:13 AM, Andrei Ivanov  wrote:
> On Mon, Feb 2, 2009 at 8:07 AM, Amila Suriarachchi
>  wrote:
>> Can you try with the axis2 snapshot and sandesha2 snapshot.
> I see that sandesha2 snapshot is using generics... and I use java 1.4
>
>> Try using different INTERNAL_KEY s rather than the SEQUENCE_KEY
> How can I do that?
> AFAIS, in both 1.3 and in snapshot the internal key is defined like this:
> Sandesha2Constants.INTERNAL_SEQUENCE_PREFIX + ":" + to + ":" + sequenceKey
>
> I am providing a different sequence key for each sequence... so this
> should make the internal key different already.
>
>>
>> thanks,
>> Amila.
>>
>> On Sun, Feb 1, 2009 at 9:17 PM, Andrei Ivanov 
>> wrote:
>>>
>>> Hello,
>>> I'm trying to add WS-RM to my services and clients, but I'm having
>>> some problems.
>>> I followed the user guide and when I tried to do some testing, I
>>> noticed some exceptions being thrown.
>>>
>>> I've generated a client stub(PersonalDataServiceStub) from the
>>> services WSDL and I've added these lines to the end
>>> of the constructor(PersonalDataServiceStub(ConfigurationContext
>>> configurationContext, String targetEndpoint, boolean
>>> useSeparateListener)):
>>>
>>> final String sequenceKey = SandeshaUtil.getUUID();
>>> clientOptions.setProperty(SandeshaClientConstants.SEQUENCE_KEY,
>>> sequenceKey);
>>> clientOptions.setProperty(SandeshaClientConstants.LAST_MESSAGE,
>>> Constants.VALUE_TRUE);
>>>
>>> Then, in the test class I created 2 instances of the stub and called
>>> some methods:
>>>
>>> ConfigurationContext configContext =
>>>
>>> ConfigurationContextFactory.createConfigurationContextFromFileSystem(CLIENT_REPO_PATH,
>>> axis2_xml);
>>>
>>> PersonalDataServiceStub stub = new
>>> PersonalDataServiceStub(configurationContext, targetEndpoint, true);
>>> // param was initialized
>>> stub.getPersonalData(param);
>>>
>>> stub = new PersonalDataServiceStub(configurationContext, targetEndpoint,
>>> true);
>>> stub.getFamilyTree(request);
>>>
>>> I'm setting the sequenceKey myself because I want to use 2 separate
>>> sequences for the calls, but something goes wrong.
>>> I used tcpmon to see what it was doing:
>>> Client:
>>> 1. CreateSequence
>>> 2. invoke getPersonalData
>>> 3. CreateSequence (for the 2nd call)
>>> 4. TerminateSequence (for the 1st call)
>>> 5. invoke getFamilyTree
>>> 6. TerminateSequence (for the 2nd call)
>>>
>>> Server:
>>> 1. CreateSequenceResponse
>>> 2. result for getPersonalData
>>> 3. CreateSequenceResponse
>>> 4. TerminateSequence (why is the server trying to end the 1st sequence
>>> itself?)
>>> 5. result for getFamilyTree
>>> 6. Fault, the action
>>> "http://schemas.xmlsoap.org/ws/2005/02/rm/TerminateSequence"; cannot be
>>> processed at the receiver (probably for the 1st TerminateSequence from
>>> the client)
>>> 7. SequenceFault, the 1st sequence is already terminated... probably
>>> at step 4 the server terminated it
>>> 8. TerminateSequence, for the 2nd sequence
>>>
>>>
>>> Am I doing something wrong? or maybe it is a bug in sandesha? remember
>>> that I want to use a different sequence for each operation.
>>> If you need additional data, please tell me.
>>> Thanks
>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>>
>

Error establishing end to end conectivity in axis and jboss

Re: HTTP status

Re: unsubscribe

RE: InOnlyAxisOperation

Re: unsubscribe

unsubscribe

InOnlyAxisOperation

[Axis2] Need help embedding axis2 in desktop application

Re: Problem building proper Policy file ...

Re: Problem building proper Policy file ...

Re: Axis 1.4.1 POJO problem

Re: Problem building proper Policy file ...

RE: Axis 1.4.1 POJO problem

Re: Axis 1.4.1 POJO problem

Re: Problem building proper Policy file ...

Problem building proper Policy file ...

Re: Axiom bug?

Re: Axiom bug?

RE: Help with SimpleDeserializer encountered a child element

Axiom bug?

RE: Error in signature with X509Token

calling webservice from browser

Re: Error Generating Client Stub Code With Rampart Policy

Error Generating Client Stub Code With Rampart Policy

Re: Error in signature with X509Token

Error in signature with X509Token

Axis 1.4.1 POJO problem

[AXIS2] Migration Issues for Axis1 -> Axis2

RE: not showing stack trace when accessing the web service via browser

Re: axis2 1.4.1 and rampart 1.4 issue

not showing stack trace when accessing the web service via browser

Re: axis2 1.4.1 and rampart 1.4 issue

RE: axis2 1.4.1 and rampart 1.4 issue

Re: sandesha problem

34 matches

Site Navigation

Mail list logo

Footer information