Re: Axis2 with Rampart 1.4 - Faults are not getting encrypted

[Prabath Siriwardena]

That is the one Glen hosted as Axis2 1.5.1 (Take2) [1].

Please be in touch with the mailing list to get updates on it's status - 
to be released officially.


Thanks & regards.
-Prabath

[1]:http://www.mail-archive.com/axis-...@ws.apache.org/msg48105.html

Rajan Gupta wrote:

Thanks again Prabhat for the prompt reply. Yes, this version works. Do
you know certification status of this release?

Thanks,
Rajan

-Original Message-
From: Prabath Siriwardena [mailto:prab...@wso2.com] 
Sent: Friday, October 16, 2009 1:13 PM

To: axis-user@ws.apache.org
Subject: Re: Axis2 with Rampart 1.4 - Faults are not getting encrypted

Can you please try with the build available here [1].

Thanks & regards.
-Prabath

[1]:http://people.apache.org/~gdaniels/stagingRepo/org/apache/axis2/dist
ribution/1.5.1/ 



Rajan Gupta wrote:
  

Thanks Prabhat. I tried with Axis2 version 1.5 but encountered the


same
  
issue. I have not tried the nightly build yet. 


Thanks,
Rajan

-Original Message-
From: Prabath Siriwardena [mailto:prab...@wso2.com] 
Sent: Friday, October 16, 2009 11:50 AM

To: axis-user@ws.apache.org
Subject: Re: Axis2 with Rampart 1.4 - Faults are not getting encrypted

Yes - this is fixed in the Axis2 trunk - so the fix was not available 
with 1.4.1


Thanks & regards.
-Prabath

[1]:https://issues.apache.org/jira/browse/RAMPART-164
[2]:https://issues.apache.org/jira/browse/AXIS2-4241

Prabath Siriwardena wrote:
  


AFAIR this issue was fixed after after 1.4.1 release.

I'll verify it for sure and let you know.

Thanks & regards.
-Prabath

Rajan Gupta wrote:

  

Thanks Prabhat for the reply. I am using Axis2 version 1.4.1. Below
  


is
  


an extract from my axis2.xml. I see that I already have "Security"


in
  
  


my
  


OutFaultFlow.










Is this functionality supposed to work in Axis2 1.4.1. Upgrading to
Axis2 1.5 might not be possible for the time being.
Thanks,
Rajan
-Original Message-
From: Prabath Siriwardena [mailto:prab...@wso2.com] Sent: Friday, 
October 16, 2009 10:08 AM

To: axis-user@ws.apache.org
Subject: Re: Axis2 with Rampart 1.4 - Faults are not getting
  


encrypted
  


Hi Rajan;

Security will be applied to all the 'application faults'  if you


have
  
  

  

defined the 'Security' phase under OutFaultFlow in the axis2.xml of 
the service end.


What is the version of Axis2 you use ? Can you please try with Axis2
  


1.5
  


?

Thanks & regards.
- Prabath

Rajan Gupta wrote:
 
  


Hi,

  I am using axis2 with rampart version 1.4. When the operation is 
successful the response from the server is encrypted, contains 
required security headers, and works fine. In case when the 
operation results in a fault, the server sends a clear text 
response, similar to


  
 
  

a response you would get without engaging rampart. The client is 
expecting a secured response and hence fails.


 

Is there anything special I need to do in rampart or axis2 
configuration  for faults?


 


Thanks in advance,

Rajan



  
  
  


  
  




  

BeanSerializer Tutorial

[Jaco le Roux]

Hi all,

I'm looking for an easy tutorial on how to serialize DTOs between client and
server.

So far I have managed to find some documentation on this issue, such as is
located at:
http://www.ibm.com/developerworks/webservices/library/ws-complex.html

, however the problem is that my web service is automatically generated by
Eclipse. I cannot seem to find a WSDD file anywhere in the Web Service
project and therefore do not know how to add a  to the
deployment descriptor.

I'll appreciate any other links and/or feedback, thanks.

Kind regards,

Jaco.

RE: Axis2 with Rampart 1.4 - Faults are not getting encrypted

[Rajan Gupta]

Thanks again Prabhat for the prompt reply. Yes, this version works. Do
you know certification status of this release?

Thanks,
Rajan

-Original Message-
From: Prabath Siriwardena [mailto:prab...@wso2.com] 
Sent: Friday, October 16, 2009 1:13 PM
To: axis-user@ws.apache.org
Subject: Re: Axis2 with Rampart 1.4 - Faults are not getting encrypted

Can you please try with the build available here [1].

Thanks & regards.
-Prabath

[1]:http://people.apache.org/~gdaniels/stagingRepo/org/apache/axis2/dist
ribution/1.5.1/ 


Rajan Gupta wrote:
> Thanks Prabhat. I tried with Axis2 version 1.5 but encountered the
same
> issue. I have not tried the nightly build yet. 
>
> Thanks,
> Rajan
>
> -Original Message-
> From: Prabath Siriwardena [mailto:prab...@wso2.com] 
> Sent: Friday, October 16, 2009 11:50 AM
> To: axis-user@ws.apache.org
> Subject: Re: Axis2 with Rampart 1.4 - Faults are not getting encrypted
>
> Yes - this is fixed in the Axis2 trunk - so the fix was not available 
> with 1.4.1
>
> Thanks & regards.
> -Prabath
>
> [1]:https://issues.apache.org/jira/browse/RAMPART-164
> [2]:https://issues.apache.org/jira/browse/AXIS2-4241
>
> Prabath Siriwardena wrote:
>   
>> AFAIR this issue was fixed after after 1.4.1 release.
>>
>> I'll verify it for sure and let you know.
>>
>> Thanks & regards.
>> -Prabath
>>
>> Rajan Gupta wrote:
>> 
>>> Thanks Prabhat for the reply. I am using Axis2 version 1.4.1. Below
>>>   
> is
>   
>>> an extract from my axis2.xml. I see that I already have "Security"
in
>>>   
> my
>   
>>> OutFaultFlow.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>
>>> Is this functionality supposed to work in Axis2 1.4.1. Upgrading to
>>> Axis2 1.5 might not be possible for the time being.
>>> Thanks,
>>> Rajan
>>> -Original Message-
>>> From: Prabath Siriwardena [mailto:prab...@wso2.com] Sent: Friday, 
>>> October 16, 2009 10:08 AM
>>> To: axis-user@ws.apache.org
>>> Subject: Re: Axis2 with Rampart 1.4 - Faults are not getting
>>>   
> encrypted
>   
>>> Hi Rajan;
>>>
>>> Security will be applied to all the 'application faults'  if you
have
>>>   
>
>   
>>> defined the 'Security' phase under OutFaultFlow in the axis2.xml of 
>>> the service end.
>>>
>>> What is the version of Axis2 you use ? Can you please try with Axis2
>>>   
> 1.5
>   
>>> ?
>>>
>>> Thanks & regards.
>>> - Prabath
>>>
>>> Rajan Gupta wrote:
>>>  
>>>   
 Hi,

   I am using axis2 with rampart version 1.4. When the operation is 
 successful the response from the server is encrypted, contains 
 required security headers, and works fine. In case when the 
 operation results in a fault, the server sends a clear text 
 response, similar to
 
 
>>>  
>>>   
 a response you would get without engaging rampart. The client is 
 expecting a secured response and hence fails.

  

 Is there anything special I need to do in rampart or axis2 
 configuration  for faults?

  

 Thanks in advance,

 Rajan

 
 
>>>   
>>>   
>> 
>
>
>   

Re: Axis2 with Rampart 1.4 - Faults are not getting encrypted

[Prabath Siriwardena]

Can you please try with the build available here [1].

Thanks & regards.
-Prabath

[1]:http://people.apache.org/~gdaniels/stagingRepo/org/apache/axis2/distribution/1.5.1/ 



Rajan Gupta wrote:

Thanks Prabhat. I tried with Axis2 version 1.5 but encountered the same
issue. I have not tried the nightly build yet. 


Thanks,
Rajan

-Original Message-
From: Prabath Siriwardena [mailto:prab...@wso2.com] 
Sent: Friday, October 16, 2009 11:50 AM

To: axis-user@ws.apache.org
Subject: Re: Axis2 with Rampart 1.4 - Faults are not getting encrypted

Yes - this is fixed in the Axis2 trunk - so the fix was not available 
with 1.4.1


Thanks & regards.
-Prabath

[1]:https://issues.apache.org/jira/browse/RAMPART-164
[2]:https://issues.apache.org/jira/browse/AXIS2-4241

Prabath Siriwardena wrote:
  

AFAIR this issue was fixed after after 1.4.1 release.

I'll verify it for sure and let you know.

Thanks & regards.
-Prabath

Rajan Gupta wrote:


Thanks Prabhat for the reply. I am using Axis2 version 1.4.1. Below
  

is
  

an extract from my axis2.xml. I see that I already have "Security" in
  

my
  

OutFaultFlow.










Is this functionality supposed to work in Axis2 1.4.1. Upgrading to
Axis2 1.5 might not be possible for the time being.
Thanks,
Rajan
-Original Message-
From: Prabath Siriwardena [mailto:prab...@wso2.com] Sent: Friday, 
October 16, 2009 10:08 AM

To: axis-user@ws.apache.org
Subject: Re: Axis2 with Rampart 1.4 - Faults are not getting
  

encrypted
  

Hi Rajan;

Security will be applied to all the 'application faults'  if you have
  


  
defined the 'Security' phase under OutFaultFlow in the axis2.xml of 
the service end.


What is the version of Axis2 you use ? Can you please try with Axis2
  

1.5
  

?

Thanks & regards.
- Prabath

Rajan Gupta wrote:
 
  

Hi,

  I am using axis2 with rampart version 1.4. When the operation is 
successful the response from the server is encrypted, contains 
required security headers, and works fine. In case when the 
operation results in a fault, the server sends a clear text 
response, similar to


 
  
a response you would get without engaging rampart. The client is 
expecting a secured response and hence fails.


 

Is there anything special I need to do in rampart or axis2 
configuration  for faults?


 


Thanks in advance,

Rajan



  
  




  

RE: Axis2 with Rampart 1.4 - Faults are not getting encrypted

[Rajan Gupta]

Thanks Prabhat. I tried with Axis2 version 1.5 but encountered the same
issue. I have not tried the nightly build yet. 

Thanks,
Rajan

-Original Message-
From: Prabath Siriwardena [mailto:prab...@wso2.com] 
Sent: Friday, October 16, 2009 11:50 AM
To: axis-user@ws.apache.org
Subject: Re: Axis2 with Rampart 1.4 - Faults are not getting encrypted

Yes - this is fixed in the Axis2 trunk - so the fix was not available 
with 1.4.1

Thanks & regards.
-Prabath

[1]:https://issues.apache.org/jira/browse/RAMPART-164
[2]:https://issues.apache.org/jira/browse/AXIS2-4241

Prabath Siriwardena wrote:
> AFAIR this issue was fixed after after 1.4.1 release.
>
> I'll verify it for sure and let you know.
>
> Thanks & regards.
> -Prabath
>
> Rajan Gupta wrote:
>> Thanks Prabhat for the reply. I am using Axis2 version 1.4.1. Below
is
>> an extract from my axis2.xml. I see that I already have "Security" in
my
>> OutFaultFlow.
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>
>> Is this functionality supposed to work in Axis2 1.4.1. Upgrading to
>> Axis2 1.5 might not be possible for the time being.
>> Thanks,
>> Rajan
>> -Original Message-
>> From: Prabath Siriwardena [mailto:prab...@wso2.com] Sent: Friday, 
>> October 16, 2009 10:08 AM
>> To: axis-user@ws.apache.org
>> Subject: Re: Axis2 with Rampart 1.4 - Faults are not getting
encrypted
>>
>> Hi Rajan;
>>
>> Security will be applied to all the 'application faults'  if you have

>> defined the 'Security' phase under OutFaultFlow in the axis2.xml of 
>> the service end.
>>
>> What is the version of Axis2 you use ? Can you please try with Axis2
1.5
>> ?
>>
>> Thanks & regards.
>> - Prabath
>>
>> Rajan Gupta wrote:
>>  
>>> Hi,
>>>
>>>   I am using axis2 with rampart version 1.4. When the operation is 
>>> successful the response from the server is encrypted, contains 
>>> required security headers, and works fine. In case when the 
>>> operation results in a fault, the server sends a clear text 
>>> response, similar to
>>> 
>>
>>  
>>> a response you would get without engaging rampart. The client is 
>>> expecting a secured response and hence fails.
>>>
>>>  
>>>
>>> Is there anything special I need to do in rampart or axis2 
>>> configuration  for faults?
>>>
>>>  
>>>
>>> Thanks in advance,
>>>
>>> Rajan
>>>
>>> 
>>
>>
>>   
>
>

generating wsdl for complex return types

[Doug Price]

I was able to get a simple web service running w/ Axis2/C using the approach 
shown here, which creates a WSDL file from a Java 
interface using the Axis2 java2wsdl and then uses the WSDL file to create the C 
skeleton and stubs using wsdl2c.  So far so good.  Now I'd like to create a 
more sophisticated interface.  For example, what if I need to return multiple 
values, or a list of objects?

For example, let's say I have some data that represents a user (e.g. name, 
password, id, etc.) and my service has two methods getUser and getActiveUsers.  
The first would return the data for the user w/ the given id and the second 
would return the data for all users that are currently logged onto the system.  
I'd expect the SOAP responses to be something like the following:



fred
...



< getActiveUsersResponse>

fred
...


barney
...



How do I write the Java interface to produce such a result w/ java2wsdl?  I 
would have hoped something like the following would have done it, but that WSDL 
generated seems like it wants to pass the object reference instead.  Any help 
would be greatly appreciated.

class User {
string name;
...
}

interface MyInterface {
public User getUser(int id);
public User [] getActiveUsers();
}


--
Doug Price
Research Director | Presagis

T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399

DISCLAIMER: This e-mail message is for the sole use of the intended 
recipient(s) and may contain confidential and/or proprietary information. Do 
not read, copy, or disseminate this message unless you are the addressee. Any 
unauthorized review, use, disclosure or distribution is strictly prohibited. If 
you have received this message in error, please contact the sender by reply 
e-mail and delete the original and any copies from your system.




--
Doug Price
Research Director | Presagis

T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399

DISCLAIMER: This e-mail message is for the sole use of the intended 
recipient(s) and may contain confidential and/or proprietary information. Do 
not read, copy, or disseminate this message unless you are the addressee. Any 
unauthorized review, use, disclosure or distribution is strictly prohibited. If 
you have received this message in error, please contact the sender by reply 
e-mail and delete the original and any copies from your system.

Re: Problemes throwing faults when rampart is enabled using Axis2-1.5

[Prabath Siriwardena]

Hi;

Your issue may be related to [1] - this is fixed in Axis2 trunk.

Can you please test your scenario with the Axis2 distribution available 
at [2].


Thanks & regards.
-Prabath

[1]:https://issues.apache.org/jira/browse/AXIS2-4241
[2]:http://people.apache.org/~gdaniels/stagingRepo/org/apache/axis2/distribution/1.5.1/

Håkon Sagehaug wrote:

Hi all,

I've got a service with rampart enabled, when one of the operation 
throws a fault message this is what I get back from the server, 
captured through tcpmon


 
 
 http://localhost:1/axis2/"/>   
 Axis2 :: Internal server error   
 type="text/css"/>   
 
...

I'm now running axis2-1.5, I had the same issue when running 
axis2-1.4.1 the fix then was to move from axiom-1.2.8 to 
1.2.9-snapshot. I've got axiom 1.2.9 now in axis2/WEB-Inf/lib folder, 
but still the same error. My other services with out rampart enabled 
throws the fault messages correct. Any tips on how to solve this issue??


cheers, håkon

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

Re: Axis2 with Rampart 1.4 - Faults are not getting encrypted

[Prabath Siriwardena]

Yes - this is fixed in the Axis2 trunk - so the fix was not available 
with 1.4.1


Thanks & regards.
-Prabath

[1]:https://issues.apache.org/jira/browse/RAMPART-164
[2]:https://issues.apache.org/jira/browse/AXIS2-4241

Prabath Siriwardena wrote:

AFAIR this issue was fixed after after 1.4.1 release.

I'll verify it for sure and let you know.

Thanks & regards.
-Prabath

Rajan Gupta wrote:

Thanks Prabhat for the reply. I am using Axis2 version 1.4.1. Below is
an extract from my axis2.xml. I see that I already have "Security" in my
OutFaultFlow.










Is this functionality supposed to work in Axis2 1.4.1. Upgrading to
Axis2 1.5 might not be possible for the time being.
Thanks,
Rajan
-Original Message-
From: Prabath Siriwardena [mailto:prab...@wso2.com] Sent: Friday, 
October 16, 2009 10:08 AM

To: axis-user@ws.apache.org
Subject: Re: Axis2 with Rampart 1.4 - Faults are not getting encrypted

Hi Rajan;

Security will be applied to all the 'application faults'  if you have 
defined the 'Security' phase under OutFaultFlow in the axis2.xml of 
the service end.


What is the version of Axis2 you use ? Can you please try with Axis2 1.5
?

Thanks & regards.
- Prabath

Rajan Gupta wrote:
 

Hi,

  I am using axis2 with rampart version 1.4. When the operation is 
successful the response from the server is encrypted, contains 
required security headers, and works fine. In case when the 
operation results in a fault, the server sends a clear text 
response, similar to



 
a response you would get without engaging rampart. The client is 
expecting a secured response and hence fails.


 

Is there anything special I need to do in rampart or axis2 
configuration  for faults?


 


Thanks in advance,

Rajan





  

Help -- Not in GZIP format

[Mark_Huang]

1. Server side: I developed a web service using Axis2 and deployed in JBoss.

2. Client side: I tried to send a big XML file to this web service using
MTOM mechanism

2.1. If I don't set MC_GZIP_REQUEST at client side, every thing works fine

2.2. If I set org.apache.axis2.transport.http.HTTPConstants.MC_GZIP_REQUEST
to TRUE, I got "Not in GZIP format". 

As the file is very big and I want to zip it before sending to the Web
Service. It seems MC_GZIP_REQUEST is the one needed for my scenario.

Do I miss any configuration for AXIS2 GZIP feature?

Any help is greatly appreciated,

Mark



-- 
View this message in context: 
http://www.nabble.com/HelpNot-in-GZIP-format-tp25930026p25930026.html
Sent from the Axis - User mailing list archive at Nabble.com.

Axis 1.4 and ArraySerializer

[Kevin Richards]

Hi,

We're currently using Axis 1.4 to connect to a WebSphere webservice
(no other webservice library coould be found to work!) and we are
having a problem sending a message which consists of a Map where one
of the values is a String[].  Websphere wants the value element to
specify the soapenc otherwise it doesn't work.

name<\key>

 Fred
 Dave




However looking at the code for the ArraySerializer the only way to
make this happen would be to set the encodingstyle of the whole
message to be soap, in which case everything is soapenc including
strings.

How can I make axis provide the soapenc attributes on the array value?

Regards

Kevin

Re: Axis2 with Rampart 1.4 - Faults are not getting encrypted

[Prabath Siriwardena]

AFAIR this issue was fixed after after 1.4.1 release.

I'll verify it for sure and let you know.

Thanks & regards.
-Prabath

Rajan Gupta wrote:

Thanks Prabhat for the reply. I am using Axis2 version 1.4.1. Below is
an extract from my axis2.xml. I see that I already have "Security" in my
OutFaultFlow. 












Is this functionality supposed to work in Axis2 1.4.1. Upgrading to
Axis2 1.5 might not be possible for the time being. 


Thanks,
Rajan
-Original Message-
From: Prabath Siriwardena [mailto:prab...@wso2.com] 
Sent: Friday, October 16, 2009 10:08 AM

To: axis-user@ws.apache.org
Subject: Re: Axis2 with Rampart 1.4 - Faults are not getting encrypted

Hi Rajan;

Security will be applied to all the 'application faults'  if you have 
defined the 'Security' phase under OutFaultFlow in the axis2.xml of the 
service end.


What is the version of Axis2 you use ? Can you please try with Axis2 1.5
?

Thanks & regards.
- Prabath

Rajan Gupta wrote:
  

Hi,

  I am using axis2 with rampart version 1.4. When the operation is 
successful the response from the server is encrypted, contains 
required security headers, and works fine. In case when the operation 
results in a fault, the server sends a clear text response, similar to



  
a response you would get without engaging rampart. The client is 
expecting a secured response and hence fails.


 

Is there anything special I need to do in rampart or axis2 
configuration  for faults?


 


Thanks in advance,

Rajan





  

RE: Axis2 with Rampart 1.4 - Faults are not getting encrypted

[Rajan Gupta]

Thanks Prabhat for the reply. I am using Axis2 version 1.4.1. Below is
an extract from my axis2.xml. I see that I already have "Security" in my
OutFaultFlow. 











Is this functionality supposed to work in Axis2 1.4.1. Upgrading to
Axis2 1.5 might not be possible for the time being. 

Thanks,
Rajan
-Original Message-
From: Prabath Siriwardena [mailto:prab...@wso2.com] 
Sent: Friday, October 16, 2009 10:08 AM
To: axis-user@ws.apache.org
Subject: Re: Axis2 with Rampart 1.4 - Faults are not getting encrypted

Hi Rajan;

Security will be applied to all the 'application faults'  if you have 
defined the 'Security' phase under OutFaultFlow in the axis2.xml of the 
service end.

What is the version of Axis2 you use ? Can you please try with Axis2 1.5
?

Thanks & regards.
- Prabath

Rajan Gupta wrote:
>
> Hi,
>
>   I am using axis2 with rampart version 1.4. When the operation is 
> successful the response from the server is encrypted, contains 
> required security headers, and works fine. In case when the operation 
> results in a fault, the server sends a clear text response, similar to

> a response you would get without engaging rampart. The client is 
> expecting a secured response and hence fails.
>
>  
>
> Is there anything special I need to do in rampart or axis2 
> configuration  for faults?
>
>  
>
> Thanks in advance,
>
> Rajan
>

Re: Axis2 with Rampart 1.4 - Faults are not getting encrypted

[Prabath Siriwardena]

Hi Rajan;

Security will be applied to all the 'application faults'  if you have 
defined the 'Security' phase under OutFaultFlow in the axis2.xml of the 
service end.


What is the version of Axis2 you use ? Can you please try with Axis2 1.5 ?

Thanks & regards.
- Prabath

Rajan Gupta wrote:


Hi,

  I am using axis2 with rampart version 1.4. When the operation is 
successful the response from the server is encrypted, contains 
required security headers, and works fine. In case when the operation 
results in a fault, the server sends a clear text response, similar to 
a response you would get without engaging rampart. The client is 
expecting a secured response and hence fails.


 

Is there anything special I need to do in rampart or axis2 
configuration  for faults?


 


Thanks in advance,

Rajan

New to Axis2 - Unable to see service

[mule_user]

I am new to Axis2, but familiar with Axis1. I am trying to see the service
using the Axis2 admin console. I am unable to see the service. That can mean
many things. Any suggestion will be appreciated. Following are the steps I
ahve taken:

1. Deployed axis2.war. As such, I can successfully see
http://localhost:9081/axis2/services/listServices But obviously, the new
service created by me is not in that list.

2. Created a Java web project and deployed it in the same server where axis2
admin application was deployed. The structure of the Java project is:

Axis2WebWs
|
src
|   |
|   org.ncc.server
|   |
|Calculator.java
|ICalculator.java
|
---WebContent
|
META-INF
||
|services.xml
|
WEB-INF  
  |
  -lib (has all the jar folders from Axis2)
  |
  web.xml


package org.ncc.server;

public class Calculator implements ICalculator{
 public int add(int a, int b) {  
 return a + b;   
}   
}
/  
package org.ncc.server;

public interface ICalculator {
int add (int x, int y);
}
//


Simple Calculator Service


org.ncc.server.Calculator




 



http://java.sun.com/xml/ns/j2ee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd";>

Axis2WebWs

Apache-Axis Servlet
AxisServlet

org.apache.axis2.transport.http.AxisServlet
1



AxisServlet
/servlet/AxisServlet


AxisServlet
*.jws


AxisServlet
/services/*


//
I create a EAR file for this project and deploy it. Axis2WebWs gets deployed
successfully. I am not (nor do want to) use Axis2 Admin console for deploy.
I was hoping that the url below will show my service add:
http://localhost:9081/axis2/services/listServices 

Instead it only lists getVersion method from Axis2 Admin console.

What am I missing?

Even though I do not want to deploy it using Axis2 Admin console, but for
troubleshooting purposes, I changed ear file to aar file and wanted to
upload that aar file using Axis2 Admin console. When I looked for the
service, it mentioned faulty service. I said that cannot find services.xml.

Any suggestion will be appreciated. Again, I want to deploy the EAR file
using Admin console of the app server only (will be scripted eventually),
instead of relying on Axis2 Admin console.


-- 
View this message in context: 
http://www.nabble.com/New-to-Axis2---Unable-to-see-service-tp25928644p25928644.html
Sent from the Axis - User mailing list archive at Nabble.com.

Axis2 with Rampart 1.4 - Faults are not getting encrypted

[Rajan Gupta]

Hi,

  I am using axis2 with rampart version 1.4. When the operation is
successful the response from the server is encrypted, contains required
security headers, and works fine. In case when the operation results in
a fault, the server sends a clear text response, similar to a response
you would get without engaging rampart. The client is expecting a
secured response and hence fails. 

 

Is there anything special I need to do in rampart or axis2 configuration
for faults?

 

Thanks in advance,

Rajan

Help troubleshooting org.apache.axis2.AxisFault: Read timed out

[laredotornado]

Hi,

I am running a JUnit test that makes several hundred calls (one after the
other) to a web service, running locally.  At a certain point, the tests die
with the Axis Fault: read timed out.  But this will always happen at a
different point -- some times after 375 tests, sometimes after 400, and so
on.

Any advice on how to troubleshoot this?  Read time out is happening after 30
seconds.  No errors in my application or axis2 logs, although I included a
little bit of the Axis 2 log after the stack trace.  

Thanks, - Dave

===The stack trace=
org.apache.axis2.AxisFault: Read timed out
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:195)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:327)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:206)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:396)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at
myco.dor.dmv.driver.matching.soap.MatchingServiceStub.match(MatchingServiceStub.java:246)
at
myco.dor.dmv.driver.matching.test.MatchingServiceTest._testMatch(MatchingServiceTest.java:16831)
at
myco.dor.dmv.driver.matching.test.MatchingServiceTest._testMatch(MatchingServiceTest.java:16807)
at
myco.dor.dmv.driver.matching.test.MatchingServiceTest._testMatchCaseType(MatchingServiceTest.java:16607)
at
myco.dor.dmv.driver.matching.test.MatchingServiceTest._testMatchHyphenatedCase(MatchingServiceTest.java:16347)
at
myco.dor.dmv.driver.matching.test.MatchingServiceTest.test413MatchValid_Hyphen(MatchingServiceTest.java:1935)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at junit.framework.TestCase.runTest(TestCase.java:164)
at junit.framework.TestCase.runBare(TestCase.java:130)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:120)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:297)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeInVM(JUnitTask.java:1072)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:682)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitTask.java:1434)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:632)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:195)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:250)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186)
at
org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:250)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186)
at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:250)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186)
at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:42)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:250)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:83)
at
org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:116)
at org.apache.maven.werkz.Goal.fire(Goal.java:691)
at org.apache.maven.werkz.G

Problemes throwing faults when rampart is enabled using Axis2-1.5

[Håkon Sagehaug]

Hi all,

I've got a service with rampart enabled, when one of the operation throws a
fault message this is what I get back from the server, captured through
tcpmon


  
 http://localhost:1/axis2/"/>
 Axis2 :: Internal server error
 
 
  

...

I'm now running axis2-1.5, I had the same issue when running axis2-1.4.1 the
fix then was to move from axiom-1.2.8 to 1.2.9-snapshot. I've got axiom
1.2.9 now in axis2/WEB-Inf/lib folder, but still the same error. My other
services with out rampart enabled throws the fault messages correct. Any
tips on how to solve this issue??

cheers, håkon

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

Re: Possible to get more information from an AxisFault?

[Amila Suriarachchi]

please see the handling exception part here[1].

thanks,
Amila.

[1] http://wso2.org/library/2935

On Tue, Oct 13, 2009 at 8:03 PM, laredotornado wrote:

>
> Thanks for this feedback.  Although it is good to know I can put more
> information in the logs, my JUnit tests are not smart enough to read and
> parse through the logs.  So is there no way I can generate different types
> of exceptions for the clients or include other messages?
>
> Are there other types of clients other than Axis2 that I should consider
> using if I want to create something to meet my goal?
>
>  - Dave
>
>
>
> Christian Gosch-2 wrote:
> >
> > That would be a nice thing to have indeed!!
> >
> > When Axis2 WS client code decides to classify an error situation as an
> > AxisFault, the client application seems to have no chance to find out
> > what has happened behind the scenes. It's just like saying "failed." and
> > nothing more. This can be very odd when the used Axis2 configuration is
> > just "idiosyncratic" about what happens on the wire, and you simply do
> > not know about that.
> >
> > But it is possible to force the HTTP base implementation usually used by
> > Axis2 (which is commons-httpclient) to log the HTTP traffic, regardless
> > of using https on the actual connection: commons-httpclient internally
> > uses commons-logging, and there you can enable the category / filter
> > "org.apache.commons.httpclient.wire" to get the http traffic logged.
> >
> > Usually this helps a lot in dev/test environments, but is not accessible
> > by the application for "self examination".
> >
> > Christian
> >
> >> -Original Message-
> >> From: laredotornado [mailto:laredotorn...@gmail.com]
> >> Sent: Tuesday, October 13, 2009 4:04 PM
> >> To: axis-user@ws.apache.org
> >> Subject: Possible to get more information from an AxisFault?
> >>
> >>
> >> Hi,
> >>
> >>
> >> We''ve written a web service and a client that connects to it, both in
> >> Java
> >> (client generated using the code below) ...
> >>
> >> 
> >>   
> >>  >> value="target/MatchingService.wsdl"
> >> />
> >>  >>
> > src="http://localhost:8080//apps/dor/dmv/myapp/myfn//services/MatchingSe
> > rv
> >> ice?wsdl"
> >>  dest="${downloadedWSDL}"
> >>  username="username"
> >>  password="password" />
> >> 
> >>  >> classpathref="maven.dependency.classpath">
> >>   
> >>   
> >>   
> >>   
> >> 
> >>  >>   debug="true"
> >>   debuglevel="vars,lines,source"
> >>   destdir="${maven.build.dest}"
> >>   excludes="**/package.html"
> >>   srcdir="${basedir}/target/src" >
> >>  
> >>   
> >>  
> >> 
> >>   
> >> 
> >>
> >>
> >> I wanted to know how to get axis faults to send back more information
> > than
> >> simply what we are seeing below.  Regardless of the exception
> > generated by
> >> the web service, the exception thrown in the client is the same.  Is
> > there
> >> a
> >> way to add a message into the client so at least we know greater
> > detail
> >> about what caused the error?
> >>
> >>
> >> org.apache.axis2.AxisFault: Exception occurred while trying to invoke
> >> service method verifyAge
> >> at
> >>
> > org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java
> > :4
> >> 86)
> >> at
> >>
> > org.apache.axis2.description.OutInAxisOperationClient.handleResponse(Out
> > In
> >> AxisOperation.java:343)
> >> at
> >>
> > org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper
> > at
> >> ion.java:389)
> >> at
> >>
> > org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInA
> > xi
> >> sOperation.java:211)
> >> at
> >>
> > org.apache.axis2.client.OperationClient.execute(OperationClient.java:163
> > )
> >> at
> >>
> > myco.dor.dmv.driver.matching.soap.MatchingServiceStub.verifyAge(Matching
> > Se
> >> rviceStub.java:522)
> >> at
> >>
> > myco.dor.dmv.driver.matching.test.AgeVerifyTests.testVerifyAgeWithNullId
> > en
> >> tityParams(AgeVerifyTests.java:62)
> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >> at
> >>
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
> > a:
> >> 39)
> >> at
> >>
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> > Im
> >> pl.java:25)
> >> at java.lang.reflect.Method.invoke(Method.java:585)
> >> at junit.framework.TestCase.runTest(TestCase.java:164)
> >> at junit.framework.TestCase.runBare(TestCase.java:130)
> >> at junit.framework.TestResult$1.protect(TestResult.java:106)
> >> at
> > junit.framework.TestResult.runProtected(TestResult.java:124)
> >> at junit.framework.TestResult.run(TestResult.java:109)
> >> at junit.framework.TestCase.run(TestCase.java:120)
> >> at junit.framework.TestSuite.runTest(TestSuite.java:230)
> >> at junit.framework.TestSuite.run(TestSuite.jav

Re: ClassNotFoundException: org.hibernate.hql.ast.HqlToken

[Amila Suriarachchi]

where you have put your hibernate jars? in aar/lib?

try setting the ServiceTCCL to composite.

see here[1] to understand how axis2 handles class loading.

thanks,

Amila.

On Fri, Jun 20, 2008 at 12:55 PM, DOMINGUEZ Felipe <
felipe.doming...@eurocontrol.int> wrote:

>
> Hello
>
> I am having problem to run hibernate (3.2.6 ga) on axis2 (1.4)   and use
> HQL queries.
>
> I get the following exception  ClassNotFoundException:
> org.hibernate.hql.ast.HqlToken.
>
> When I run the application as a stand alone, it works fine, but when I
> run it as web service on axis2 it does not.
>
>
> It seems that some more people have had the same problem, and the
> solution they suggest is to copy file antlr-XX.jar into
> axis2/WEB-INF/lib.
> I have done so but it does not stop the problem. Anyway, it think this
> would not really be a solution since the axis administrator may refuse
> to do it, claiming that it may have an effect on other web services
> running on the same engine.
>
> Does any body knows a solution or a work around?  Or can suggest a way
> to trouble suit it. I have been looking on Google for the enter day but
> did not find any (except to copy the file)
>
>
>
> Thanks in advance.
>
> Felipe
> 
>
> This message and any files transmitted with it are legally privileged and
> intended for the sole use of the individual(s) or entity to whom they are
> addressed. If you are not the intended recipient, please notify the sender
> by reply and delete the message and any attachments from your system. Any
> unauthorised use or disclosure of the content of this message is strictly
> prohibited and may be unlawful.
>
> Nothing in this e-mail message amounts to a contractual or legal commitment
> on the part of EUROCONTROL, unless it is confirmed by appropriately signed
> hard copy.
>
> Any views expressed in this message are those of the sender.
>
>
> -
> To unsubscribe, e-mail: axis-user-unsubscr...@ws.apache.org
> For additional commands, e-mail: axis-user-h...@ws.apache.org
>
>


-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: temporary generated wsdl's use

[Amila Suriarachchi]

On Sun, Oct 11, 2009 at 9:31 PM, Asma MAALEJ  wrote:

> Hello
>
> I time ago, using axis1 environment, I have established a java class which
> allows to recover operations's parameters of a service web by parsing its
> wsdl file already generated.
>

it is not clear about your requirement. with axis2 wsdl is generated
according to the method parameters.
 thanks,
Amila.

Now, by trying to upgrade it under axis2-1.4.1 version, I noticed that the
> wsdl file becomes temporary and I have anymore a copy on the hard disk. So
> that I can't use it any more in my class just by specifying its path.
> I just wondered if I should made this wsdl file manually in order to obtain
> a copy on the disk which I will use later, or is there an other solution
> proposed for the wsdl file use with the arrival of axis2.
>
> I would appreciate help.
> Thanks,
>



-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: Avoid the "marshalling" of a field

[Lorenzo Carnevale]

Thank you very much Greg!

- Original Message - 
From: "Greg Logan" 

To: 
Sent: Thursday, October 15, 2009 6:42 PM
Subject: Re: Avoid the "marshalling" of a field



Lorenzo Carnevale wrote:
The class Bean is a plain pojo that contains some "useful" fields that I 
DON'T want to send back.


Can I tell somehow to Axis2 to NOT serialize (i.e. not to put it in the 
SOAP answer!) one or some of these fields contained in Bean?


Try http://wso2.org/library/2893, search for How to exclude "Bean 
properties?" and "Exclude Methods"


G


Thanks

  Lorenzo

Re: ClassNotFoundException: org.hibernate.hql.ast.HqlToken

[anagnost68]

I have the same problem.  Does anyone have an update on a solution?
-- 
View this message in context: 
http://www.nabble.com/ClassNotFoundException%3A-org.hibernate.hql.ast.HqlToken-tp18024472p25920754.html
Sent from the Axis - User mailing list archive at Nabble.com.