ADBException: Unexpected subelement classe

[brunoc]

Hello. 

I created an ADB client for an Axis2 WS. For some reason it's not
recognizing 'classe' as a valid element with respect to the xml schema.
Could someone help me with this issue? I'm attaching the wsdl, request and
response.

http://www.nabble.com/file/p22545691/request.txt request.txt 
http://www.nabble.com/file/p22545691/response.txt response.txt 
http://www.nabble.com/file/p22545691/wsdl.txt wsdl.txt 

Thank you very much!

PS1: I initially tried to use different targetNamespace and
schemaTargetNamespace, but had the same prob.
PS2: This problem doesn't happen when using xmlbeans instead of ADB.
-- 
View this message in context: 
http://www.nabble.com/ADBException%3A-Unexpected-subelement-classe-tp22545691p22545691.html
Sent from the Axis - User mailing list archive at Nabble.com.

Re: Next release of Axis2

[Saurabh Garg]

Hi,

Any ETA for Axis2 1.5 release?

This info will help us make an informed decision about scheduling our
Axis2 related tasks. Hence any relevant info is appreciated.

Regards,
Saurabh



On Fri, Jan 9, 2009 at 1:15 AM, keith chapman  wrote:
> We did an RC late last year, I guess Glen is already working on the release.
> Should be out soon.
>
> Thanks,
> Keith.
>
> On Fri, Jan 9, 2009 at 10:55 AM, Saurabh Garg 
> wrote:
>>
>> Hi Keith,
>>
>> Any updates on the release? Any idea when the new version will be
>> released.
>>
>> Thanks
>> Saurabh
>>
>>
>> On Mon, Nov 24, 2008 at 7:22 AM, keith chapman 
>> wrote:
>>>
>>> Hi Anders,
>>>
>>> We do not have any plans to do a 1.4.2 release. There were some
>>> discussions about a 1.5 release but that didn't materialize either cause
>>> most of the devs were busy. I guess the likely time for a release might be
>>> early next year (my personal opinion).
>>>
>>> Thanks,
>>> Keith.
>>>
>>> On Mon, Nov 24, 2008 at 8:18 PM, Anders Nordström 
>>> wrote:

 Hi,
 We've a problem with the codegen (wsdl2java) in the 1.4.1 release.
 I can see that this is due to a known bug that's reported as
 fixed (http://issues.apache.org/jira/browse/AXIS2-3827).
 So, if possible, I would like to know when in time the next release is
 scheduled for the 1.4.X branch.

 Many thanks in advance,
 Anders Nordström
>>>
>>>
>>>
>>> --
>>> Keith Chapman
>>> Senior Software Engineer
>>> WSO2 Inc.
>>> Oxygenating the Web Service Platform.
>>> http://wso2.org/
>>>
>>> blog: http://www.keith-chapman.org
>>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>

[AXIS2] How to change the service path

[DV]

I am able to call my services via https:///services/MyService

However, I want to add qualified paths to my services. For example:

https:///services/account/v1/MyAccountService
https:///services/account/v2/MyAccountService

etc.

How can this be configured this with Axis2 1.4.1?

Dino


  

Re: [Axis2 1.4] WS-Policy in WSDL 1.1 vs WSDL2.0 using wsdl2java utility

[Leon Searl]

Hi Pradeep,

Thanks you very much!

leon

- Original Message -
From: "Pradeep Fernando" 
To: axis-user@ws.apache.org
Sent: Monday, March 16, 2009 12:38:35 AM GMT -06:00 US/Canada Central
Subject: Re: [Axis2 1.4] WS-Policy in WSDL 1.1 vs WSDL2.0 using wsdl2java  
utility

Hi leon,

I raised a JIRA issue on behalf of you. you can track it here[1].

thanks,
Pradeep Fernando.

[1] https://issues.apache.org/jira/browse/AXIS2-4272

-- 
Leon S. Searl, Software/Hardware Research Engineer
Information and Telecommunication Technology Center, University of Kansas
Nichols Hall, 2335 Irving Hill Road, Lawrence, KS 66045-7612
Ph: 785-864-7820 Fax: 785-864-0387
http://www.ittc.ku.edu

Unexpected port number in auto created WSDL

[tfecw]

Hi, 

I’m working with axis 1.4 and am relying on axis2 to auto generate the wsdl
I’m using from my .aar file.  For most of my environments everything works
fine but as I get closer to the production environments (and the
server/network configuration gets more detailed) I start getting erroneous
ports in my wsdl.

I have axis2 deployed on port 7004, but the port number being auto generated
is 80 and I’m not sure why.  This  
http://www.nabble.com/wsdl-port-address-uses-incorrect-port-number-td19574019.html#a19574019
thread   seemed promising but I’m not really sure it had any answers.  

I tried using modifyUserWSDLPortAddress but I’m not including a wsdl with my
service.  The other suggestion was to update the axis2.xml file and set the
port number for the transport receiver. In my axis2.xml file, that’s
currently set to port 8080, not 80 so I’m not sure where the 80 is coming
from.

Is this a proxy issue? Is there a way to force axis2 to use a certain port
number? 

Thanks

Here’s what is actually generated. 

< wsdl:service name="myService">
−

http://192.168.1.1:80/axis2/services/MyService.MyServiceHttpSoap11Endpoint"/>

−



−





-- 
View this message in context: 
http://www.nabble.com/Unexpected-port-number-in-auto-created-WSDL-tp22537058p22537058.html
Sent from the Axis - User mailing list archive at Nabble.com.

Re: Example for WS-SecurityPolicy in WSDL?

[Dennis Sosnoski]

Thanks for following up on this, Nandana. I tried to build from trunk so 
I could try this WSDL with the current code, but the build doesn't work 
for me at present (I get a failure running 
org.apache.axis2.fastinfoset.FastInfosetTest).


 - Dennis


Nandana Mihindukulasooriya wrote:
Yes, I agree, I will look in to that and see whether we can handle 
this more gracefully. There was an issue [1] and it is now fixed in 
the trunk.


thanks,
nandana

[1] - http://issues.apache.org/jira/browse/RAMPART-176

On Mon, Mar 16, 2009 at 12:37 PM, Dennis Sosnoski > wrote:


Yes, you're right that the WSDL I attached to the last email is
invalid according to the specification. It still needs to be
handled in a better way than just throwing an exception with the
"can't serialize the policy" message, though.

The same serialize problem happens with the attached version of
the WSDL, which does contain the required , but
does not contain an . As far as I can see from the
WSDL documentation, this is allowed. It's also essentially the
same as the sample01/policy.xml in the Rampart distribution, which
hopefully has been checked for validity.

 - Dennis


Nandana Mihindukulasooriya wrote:

Hi Dennis,

If you look at the WS - SecurityPolicy specification, 8.3
TransportBinding Assertion definition, TransportToken is a
mandatory element in the TransportBinding. So I don't think
this is really a bug, the policy in the WSDL seem to be invalid.

thanks,
Nandana

[1] -
http://specs.xmlsoap.org/ws/2005/07/securitypolicy/ws-securitypolicy.pdf


On Mon, Mar 16, 2009 at 9:30 AM, Dennis Sosnoski
mailto:d...@sosnoski.com>
>> wrote:

   Hi Nandana,

   Yes, I understand that the Transport assertion is not
contributing
   anything useful in this case. AFAIK it's still valid,
though, and
   needs to be supported.

   Is the error fixed in the current (and 1.5 branch) codebase? If
   not, should I create a Jira?

   Thanks,

- Dennis


   Nandana Mihindukulasooriya wrote:

   Hi Dennis,

   I think the problem is with the serialization of
Transport
   binding assertion without a transport token. What are your
   security requirements ? If you only need to have the
username
   token , you can remove the Transport binding assertion
   completely and have only the SupportingTokens assertion
in the
   policy. If you also need to enforce https transport,
you can
   add a HttpsToken as a transport token.

   thanks,
   Nandana

   On Mon, Mar 16, 2009 at 4:12 AM, Dennis Sosnoski
   mailto:d...@sosnoski.com>
>
   

>
   
>>
   >
   
 wrote:

 I've been trying to use the client-side code
generation
  support for
 WS-SecurityPolicy in WSDL, with Axis2 1.4.1
and Rampart
  1.4. I've
 tried
 several variations of where I place the policy in
   the WSDL,
  including
 using reference and embedding it directly in the
  , but
 each time I get:

[java] Except

Sandesha sequence auto termination

[Andrei Ivanov]

Hello,
I found the following property:
org.apache.sandesha2.storage.beans.RMSBean.avoidAutoTermination
but I don't understand how it works
AFAIS, the setter for this property is only called on the client side,
so the client can ask Sandesha
not to terminate the sequence?
The problem seems to be that on the server side, the value of the
property isn't set anywhere... so it remains false
and the Sandesha server keeps sending TerminateSequence messages back
to the client, as a response to the
client's own TerminateSequence message(which probably is another bug)

need help on non blocking invocation of an asynchronous service

[Shantha Kumar]

hi,

Used the steps given in the URL
http://ws.apache.org/axis2/1_4_1/adv-userguide.html to create a
webservice client to do non blocking invocation.

Steps followed:

1. Created a asynchronous BPEL process.

2. Got the WSDL of the async BPEL process and added the WS-addressing
information to the WSDL.

3. Ran WSDL2Java command (as shown below)

wsdl2java -uri asyncBPEL.wsdl -d xmlbeans -a

4. To Do a Non-Blocking Invocation section of the above mentioned document says 
as shown below
Non-Blocking Invocation:The stubs also include a method that allows you to do a 
non-blocking
innovation. For each method in the Service, there will be a method
start. These methods accept a callback
object, which would be called when the response is received.

5. But i didn't get any such methods in the stub class.

Can any one please help me to get the callback from the asynchronous service in 
an axis client.

Thanks in advance,
shan



  


  

Re: No crypto propery file supplied for decryption error when using policy

[Håkon Sagehaug]

Hi

I managed to solve it, a bit sloppy work from my side, but now I've got a
different problem you might help me with

I call my sts secured service much like rampart sample 05, setting the
options like this


Token token = stsClient.requestSecurityToken(
loadPolicy("policy/policy.xml"),
"http://localhost:1/axis2/services/EsysbioStSService";,
loadPolicy("policy/sts_policy.xml"), null);

TokenStorage store = TrustUtil.getTokenStore(ctx);
store.add(token);
System.out.println(token.getToken().toString());

STSSecureEchoStub stub = new STSSecureEchoStub(ctx);

ServiceClient client = stub._getServiceClient();
Options endOptions = new Options();
endOptions.setAction("http://bccs.uib.no/STSSecureService/SayHi";);
endOptions.setTo(new EndpointReference(
"http://localhost:1/axis2/services/STSSecureEcho";));
endOptions.setProperty(RampartMessageData.KEY_RAMPART_POLICY,
loadPolicy("policy/policy.xml"));
endOptions.setProperty(RampartMessageData.KEY_CUSTOM_ISSUED_TOKEN,
token.getId());
client.setOptions(endOptions);

but my service replays with

org.apache.rampart.RampartException: SAML Token missing in request

My supporting tokes element looks like this is the service.xml

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

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

http://localhost:8080/axis2/services/StSService



http://schemas.xmlsoap.org/ws/2005/02/trust";>
urn:no:bccs:esysbio:user:role

http://schemas.xmlsoap.org/ws/2005/02/trust";>

http://schemas.xmlsoap.org/ws/2005/02/trust/SymmetricKey

http://schemas.xmlsoap.org/ws/2005/02/trust";>256






http://www.w3.org/2005/08/addressing"; />




I see that my token from the sts is inserted in the request, but it's not a
SAML token but should I not be able to pass in any token?

cheers, Håkon

2009/3/16 Nandana Mihindukulasooriya 

> Can you post the complete servcies.xml ?
>
> thanks,
> nandana
>
> 2009/3/16 Håkon Sagehaug 
>
> Hi all
>>
>> I've got a service with a policy with symmetric binding and a token that
>> is required form a sts service, calling the sts service and inserting the
>> token inside the new request to the service goes fine, but the response back
>> from the service is this
>>
>>  org.apache.ws.security.WSSecurityException: General security error
>> (WSSecurityEngine: No crypto propery file supplied for decryption)
>>
>> My rampart config element in  service.xml file looks like this
>>
>> http://ws.apache.org/rampart/policy";>
>> service
>> client
>>
>> xPWCBHandler
>> 
>> > 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">
>>service.jks
>> 
>> >
>> name="org.apache.ws.security.crypto.merlin.keystore.password">service
>> 
>> 
>> 
>> > 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">service.jks
>> >
>> name="org.apache.ws.security.crypto.merlin.keystore.password">service
>> 
>> 
>> 
>>
>> So as far as I can see rampart has the needed configurations for
>> decryption properties needed, but I might be missing something, do I??
>>
>> cheers, Håkon
>>
>> --
>> Håkon Sagehaug, Scientific Programmer
>> Parallab, Bergen Center for Computational Science (BCCS)
>> UNIFOB AS (University of Bergen Research Company)
>>
>
>
>
> --
> Nandana Mihindukulasooriya
> WSO2 inc.
>
> http://nandana83.blogspot.com/
> 

Regarding validating SOAP responses against the WSDL

[Sneha Nikum]

Hi,

I want to validate the SOAP response structure against the structure of that
response in the WSDL file.

Are there any Axis APIs that would help me in achieving this task?

Please let me know if there are any APIs that would help me do the above
task

-- 
Sneha Anil Nikum
Don't get even with people
get AHEAD of them!

Re: No crypto propery file supplied for decryption error when using policy

[Nandana Mihindukulasooriya]

Can you post the complete servcies.xml ?

thanks,
nandana

2009/3/16 Håkon Sagehaug 

> Hi all
>
> I've got a service with a policy with symmetric binding and a token that is
> required form a sts service, calling the sts service and inserting the token
> inside the new request to the service goes fine, but the response back from
> the service is this
>
>  org.apache.ws.security.WSSecurityException: General security error
> (WSSecurityEngine: No crypto propery file supplied for decryption)
>
> My rampart config element in  service.xml file looks like this
>
> http://ws.apache.org/rampart/policy";>
> service
> client
>
> xPWCBHandler
> 
>  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">
>service.jks
> 
> 
> name="org.apache.ws.security.crypto.merlin.keystore.password">service
> 
> 
> 
>  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">service.jks
> 
> name="org.apache.ws.security.crypto.merlin.keystore.password">service
> 
> 
> 
>
> So as far as I can see rampart has the needed configurations for decryption
> properties needed, but I might be missing something, do I??
>
> cheers, Håkon
>
> --
> Håkon Sagehaug, Scientific Programmer
> Parallab, Bergen Center for Computational Science (BCCS)
> UNIFOB AS (University of Bergen Research Company)
>



-- 
Nandana Mihindukulasooriya
WSO2 inc.

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

Re: Example for WS-SecurityPolicy in WSDL?

[Nandana Mihindukulasooriya]

Yes, I agree, I will look in to that and see whether we can handle this more
gracefully. There was an issue [1] and it is now fixed in the trunk.

thanks,
nandana

[1] - http://issues.apache.org/jira/browse/RAMPART-176

On Mon, Mar 16, 2009 at 12:37 PM, Dennis Sosnoski  wrote:

> Yes, you're right that the WSDL I attached to the last email is invalid
> according to the specification. It still needs to be handled in a better way
> than just throwing an exception with the "can't serialize the policy"
> message, though.
>
> The same serialize problem happens with the attached version of the WSDL,
> which does contain the required , but does not contain an
> . As far as I can see from the WSDL documentation, this is
> allowed. It's also essentially the same as the sample01/policy.xml in the
> Rampart distribution, which hopefully has been checked for validity.
>
>  - Dennis
>
>
> Nandana Mihindukulasooriya wrote:
>
>> Hi Dennis,
>> If you look at the WS - SecurityPolicy specification, 8.3
>> TransportBinding Assertion definition, TransportToken is a mandatory element
>> in the TransportBinding. So I don't think this is really a bug, the policy
>> in the WSDL seem to be invalid.
>>
>> thanks,
>> Nandana
>>
>> [1] -
>> http://specs.xmlsoap.org/ws/2005/07/securitypolicy/ws-securitypolicy.pdf
>>
>>
>> On Mon, Mar 16, 2009 at 9:30 AM, Dennis Sosnoski > d...@sosnoski.com>> wrote:
>>
>>Hi Nandana,
>>
>>Yes, I understand that the Transport assertion is not contributing
>>anything useful in this case. AFAIK it's still valid, though, and
>>needs to be supported.
>>
>>Is the error fixed in the current (and 1.5 branch) codebase? If
>>not, should I create a Jira?
>>
>>Thanks,
>>
>> - Dennis
>>
>>
>>Nandana Mihindukulasooriya wrote:
>>
>>Hi Dennis,
>>
>>I think the problem is with the serialization of Transport
>>binding assertion without a transport token. What are your
>>security requirements ? If you only need to have the username
>>token , you can remove the Transport binding assertion
>>completely and have only the SupportingTokens assertion in the
>>policy. If you also need to enforce https transport, you can
>>add a HttpsToken as a transport token.
>>
>>thanks,
>>Nandana
>>
>>On Mon, Mar 16, 2009 at 4:12 AM, Dennis Sosnoski
>>mailto:d...@sosnoski.com>
>>>> wrote:
>>
>>   Hi Nandana,
>>
>>   I've attached one of several variations I've tried which
>>results
>>   in this error. I did find that if I take out the
>>TransportBinding
>>   part I don't get the error.
>>
>>   Thanks for taking a look!
>>
>>- Dennis
>>
>>
>>   Nandana Mihindukulasooriya wrote:
>>
>>   Hi Dennis,
>>  Can you post the WSDL you are code generating
>>against ?
>>
>>   thanks,
>>   nandana
>>
>>   On Fri, Mar 13, 2009 at 3:09 AM, Dennis Sosnoski
>>   mailto:d...@sosnoski.com>
>>>
>>   
>>>
>>  I've been trying to use the client-side code generation
>>   support for
>>  WS-SecurityPolicy in WSDL, with Axis2 1.4.1 and Rampart
>>   1.4. I've
>>  tried
>>  several variations of where I place the policy in
>>the WSDL,
>>   including
>>  using reference and embedding it directly in the
>>   , but
>>  each time I get:
>>
>> [java] Exception in thread "main"
>>  org.apache.axis2.wsdl.codegen.CodeGenerationException:
>>  org.apache.axis2.wsdl.codegen.CodeGenerationException:
>>  java.lang.RuntimeException: can't serialize the policy
>>  ..
>> [java] at
>>
>>  
>> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271)
>>
>>
>> [java] at
>>  org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
>> [java] at
>>  org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
>> [java] Caused by:
>>  org.apache.axis2.wsdl.codegen.CodeGenerationException:
>>  java.lang.RuntimeException: can't serialize the policy
>>  ..
>> [java] at
>>
>>  
>> org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitStub(AxisServiceBasedMultiLanguageEmitter.java:534)
>>
>>
>> [java] at
>>
>>  
>> org.apache.axis2.wsdl.codegen.Code

No crypto propery file supplied for decryption error when using policy

[Håkon Sagehaug]

Hi all

I've got a service with a policy with symmetric binding and a token that is
required form a sts service, calling the sts service and inserting the token
inside the new request to the service goes fine, but the response back from
the service is this

 org.apache.ws.security.WSSecurityException: General security error
(WSSecurityEngine: No crypto propery file supplied for decryption)

My rampart config element in  service.xml file looks like this

http://ws.apache.org/rampart/policy";>
service
client

xPWCBHandler


JKS

   service.jks

service




JKS
service.jks
service




So as far as I can see rampart has the needed configurations for decryption
properties needed, but I might be missing something, do I??

cheers, Håkon

-- 
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)

Re: Example for WS-SecurityPolicy in WSDL?

[Dennis Sosnoski]

Yes, you're right that the WSDL I attached to the last email is invalid 
according to the specification. It still needs to be handled in a better 
way than just throwing an exception with the "can't serialize the 
policy" message, though.


The same serialize problem happens with the attached version of the 
WSDL, which does contain the required , but does not 
contain an . As far as I can see from the WSDL 
documentation, this is allowed. It's also essentially the same as the 
sample01/policy.xml in the Rampart distribution, which hopefully has 
been checked for validity.


 - Dennis


Nandana Mihindukulasooriya wrote:

Hi Dennis,
 If you look at the WS - SecurityPolicy specification, 8.3 
TransportBinding Assertion definition, TransportToken is a mandatory 
element in the TransportBinding. So I don't think this is really a 
bug, the policy in the WSDL seem to be invalid.


thanks,
Nandana

[1] - 
http://specs.xmlsoap.org/ws/2005/07/securitypolicy/ws-securitypolicy.pdf



On Mon, Mar 16, 2009 at 9:30 AM, Dennis Sosnoski > wrote:


Hi Nandana,

Yes, I understand that the Transport assertion is not contributing
anything useful in this case. AFAIK it's still valid, though, and
needs to be supported.

Is the error fixed in the current (and 1.5 branch) codebase? If
not, should I create a Jira?

Thanks,

 - Dennis


Nandana Mihindukulasooriya wrote:

Hi Dennis,

I think the problem is with the serialization of Transport
binding assertion without a transport token. What are your
security requirements ? If you only need to have the username
token , you can remove the Transport binding assertion
completely and have only the SupportingTokens assertion in the
policy. If you also need to enforce https transport, you can
add a HttpsToken as a transport token.

thanks,
Nandana

On Mon, Mar 16, 2009 at 4:12 AM, Dennis Sosnoski
mailto:d...@sosnoski.com>
>> wrote:

   Hi Nandana,

   I've attached one of several variations I've tried which
results
   in this error. I did find that if I take out the
TransportBinding
   part I don't get the error.

   Thanks for taking a look!

- Dennis


   Nandana Mihindukulasooriya wrote:

   Hi Dennis,
  Can you post the WSDL you are code generating
against ?

   thanks,
   nandana

   On Fri, Mar 13, 2009 at 3:09 AM, Dennis Sosnoski
   mailto:d...@sosnoski.com>
>