Re: Problem with engaging security module in Axis2 1.4 version

[Hari Prasad]

Thanks a lot Vinh!

Indeed this was the problem. From somewhere I had copied axis2-security.jar
into the lib folder which contained a rampart class.
Once I removed this jar, the module is getting loaded (i guess as there are
no error which I used to get). But now I am running into a different
exception which
I guess, again due to some class conflict. But I'm having difficulty in
resolving it. Here is the error

java.lang.NoSuchMethodError: java.lang.Integer.valueOf(I)Ljava/lang/Integer;

at org.apache.rampart.util.HandlerParameterDecoder.processParameters(*
HandlerParameterDecoder.java:151*)

at org.apache.rampart.handler.WSDoAllSender.processBasic(*
WSDoAllSender.java:94*)
SO what should be the classpath and order of the jars?

Regards
Hari P



On 5/9/08, Vinh Nguyen (vinguye2) <[EMAIL PROTECTED]> wrote:
>
>  Normally, classloaders look up classes using the full package path and
> class name, not just the class name.  So it's not likely that the problem is
> because of clashes between classes that have the same name but different
> packages.
>
> More likely, the NoClassDefFoundError is occuring because no such jar
> exists with that package and class name.  Or, as I encountered this a few
> times before, the class does exist but in multiple jars, so the classloader
> doesn't know which to load.
> -Vinh
>
>  --
> *From:* Nandana Mihindukulasooriya [mailto:[EMAIL PROTECTED]
> *Sent:* Thursday, May 08, 2008 7:48 PM
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Problem with engaging security module in Axis2 1.4 version
>
>
>  Hari,
>
>   I have this class in the class path but what I found out is the
>> ModulePolicyExtension class belongs to
>> org.apache.axis2.wsdl.codegen.extension
>>
>> But the error I am getting is for this class org*/*apache*/*axis2*/*
>> modules*/*ModulePolicyExtension
>> Some where the code is looking for
>> org.apache.axis2.modules.ModulePolicyExtension class
>>
>> Any inputs?
>>
>
> This seems to be strange. look at this commit [1]. It seems that Axis2 has
> replaced org.apache.axis2.modules.ModulePolicyExtension class with
> org.apache.axis2.wsdl.codegen.extension.ModulePolicyExtension . So there
> is no way Rampart 1.4 could refer to this class.  Just guessing, is there a
> chance that there is Rampart 1.1 or 1.2 jars in your class path.
>
> thanks,
> nandana
>
> [1] -
> http://markmail.org/message/6vx7ijlhgsdrym6t?q=list:org%2Eapache%2Ews%2Eaxis-cvs+org%2Eapache%2Eaxis2%2Emodules%2EModulePolicyExtension
>
>
>
>>  On 5/8/08, Nandana Mihindukulasooriya <[EMAIL PROTECTED]> wrote:
>>>
>>> Hi Hari,
>>> do you have axis2-codegen-1.4.jar in your classpath ? If not, please
>>> add this jar in to your classpath. This jar ships with Axis2 binary
>>> distribution under lib. Even if you download the war distribution or create
>>> the distribution using maven, it is there. But if you create the war using
>>> the ant task in binary distribution, that script explicitly excludes this
>>> jar. :( .
>>>
>>> thanks,
>>> nandana
>>>
>>>
>>>  On 5/8/08, Hari Prasad <[EMAIL PROTECTED]> wrote:

 Hi Nandana,

 Thanks for the tips on debugging. I debugged the code and found that the
 faulty modules has this 'rampart' module in it.
 The error is the following

 java
 *.*lang*.*NoClassDefFoundError*:* org*/*apache*/*axis2*/*modules*/*
 ModulePolicyExtension
 Which axis2 jar contains this class? I searched in all jars but could
 not find this class. I downloaded the axis2-1.4 binaries yesterday.
 Regards
 Hari P

  On 5/8/08, Nandana Mihindukulasooriya <[EMAIL PROTECTED]> wrote:
>
> Hi Hari,
>
>  There are no compilation errors but when I run the program , I get
>> the same error
>> "org.apache.axis2.AxisFault: The system is attempting to engage a
>> module that is not available: rampart"
>>
>
> The possible reason is Rampart might not have been deployed correctly.
> Did you add all dependency jars to your classpath ? And if you can debug,
> you can check ConfigurationContext ->
> axisConfiguration -> faultyModules to check the reason why it has
> actually failed to deploy.
>
> BTW, Are you using a custom axis2.xml ?
>
> thanks,
> nandana
>
>
>>
>> On 5/8/08, Nandana Mihindukulasooriya <[EMAIL PROTECTED]> wrote:
>>>
>>> Hi Hari,
>>>
 Not knowing what else needs to be done?. I tried using rampart with
 1.4 It didn't work. Does Rampart
 supported with axis2 1.4?

>>>
>>> Yes, you can download Rampart 1.4 RC2 here [1]. Configuration should
>>> be like this.
>>>
>>> 
>>>
>>> 
>>> 
>>> UsernameToken Timestamp
>>> bob
>>>
>>> org.apache.rampart.samples.sample02.PWCBHandler
>>> 
>>> 
>>>
>>> you can find the complete axis2.xml here [2]. You can go through the
>>> sa

Re: Getting Class not found error

[Deepal Jayasinghe]

Hello there,

I am getting DeploymentException: java.land.NoClassDefFoundError for 
one of my external library used in my java class. I checked that jar 
file is in classpath while I creating "service.aar"

There should be some mistake with your service. Please double check.

Thank you!
Deepal


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

RE: Problem with engaging security module in Axis2 1.4 version

[Vinh Nguyen (vinguye2)]

Normally, classloaders look up classes using the full package path and
class name, not just the class name.  So it's not likely that the
problem is because of clashes between classes that have the same name
but different packages.
 
More likely, the NoClassDefFoundError is occuring because no such jar
exists with that package and class name.  Or, as I encountered this a
few times before, the class does exist but in multiple jars, so the
classloader doesn't know which to load.
-Vinh



From: Nandana Mihindukulasooriya [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 08, 2008 7:48 PM
To: axis-user@ws.apache.org
Subject: Re: Problem with engaging security module in Axis2 1.4 version


Hari,



 I have this class in the class path but what I found out is the
ModulePolicyExtension class belongs to 
org.apache.axis2.wsdl.codegen.extension
 
But the error I am getting is for this class
org/apache/axis2/modules/ModulePolicyExtension 
Some where the code is looking for
org.apache.axis2.modules.ModulePolicyExtension class
 
Any inputs?


This seems to be strange. look at this commit [1]. It seems that Axis2
has replaced org.apache.axis2.modules.ModulePolicyExtension class with
org.apache.axis2.wsdl.codegen.extension.ModulePolicyExtension . So there
is no way Rampart 1.4 could refer to this class.  Just guessing, is
there a chance that there is Rampart 1.1 or 1.2 jars in your class path.


thanks,
nandana

[1] -
http://markmail.org/message/6vx7ijlhgsdrym6t?q=list:org%2Eapache%2Ews%2E
axis-cvs+org%2Eapache%2Eaxis2%2Emodules%2EModulePolicyExtension

 

On 5/8/08, Nandana Mihindukulasooriya <[EMAIL PROTECTED]>
wrote: 


Hi Hari,
do you have axis2-codegen-1.4.jar in your classpath
? If not, please add this jar in to your classpath. This jar ships with
Axis2 binary distribution under lib. Even if you download the war
distribution or create the distribution using maven, it is there. But if
you create the war using the ant task in binary distribution, that
script explicitly excludes this jar. :( .
 
thanks,
nandana

 

On 5/8/08, Hari Prasad <[EMAIL PROTECTED]> wrote: 

Hi Nandana,
 
Thanks for the tips on debugging. I debugged the
code and found that the faulty modules has this 'rampart' module in it.
The error is the following
java

.lang.NoClassDefFoundError:
org/apache/axis2/modules/ModulePolicyExtension 
Which axis2 jar contains this class? I searched
in all jars but could not find this class. I downloaded the axis2-1.4
binaries yesterday. 
 
Regards
Hari P
 

On 5/8/08, Nandana Mihindukulasooriya
<[EMAIL PROTECTED]> wrote: 

Hi Hari,




There are no compilation errors but when
I run the program , I get the same error
"org.apache.axis2.AxisFault: The system
is attempting to engage a module that is not available: rampart" 


The possible reason is Rampart might not
have been deployed correctly. Did you add all dependency jars to your
classpath ? And if you can debug, you can check ConfigurationContext ->
axisConfiguration -> faultyModules to
check the reason why it has actually failed to deploy.

BTW, Are you using a custom axis2.xml ?
 
thanks,
nandana






On 5/8/08, Nandana Mihindukulasooriya
<[EMAIL PROTECTED]> wrote: 

Hi Hari,



Not knowing what else needs to be done?.
I tried using rampart with 1.4 It didn't work. Does Rampart
supported with axis2 1.4?


Yes, you can download Rampart 1.4 RC2
here [1]. Configuration should be like this. 





UsernameToken
Timestamp
bob
 

Re: can I use use rampart with JAX-WS style webservice

[Nandana Mihindukulasooriya]

Hi Alex,

Declaring the rampart in axis2.xml global config (and putting the
> rampart.mar in WEB-INF/modules, of course) would engage it globally for all
> services. If you only have one service running, this might be what you need.
> I haven't found a way to engage a module ona per-service basis, though.


I didn't get the time to try this out, but I think it is worth giving a try.
As you have said, engage rampart globally. But you can apply policies in the
WSDL. AFAIK, when the service being deployed, Axis2 should pick the policy
from the WSDL. So only the services you need to secure has security
policies. Even though every service is engaged Rampart, only the ones having
security policies will be effectively secured. This is because, with in the
Rampart module, we check for the presence of security policies before
actually securing the messages.

thanks,
nandana



> -Original Message-
> From: [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED]
> Sent: May 8, 2008 7:43 AM
> To: axis-user@ws.apache.org
> Subject: AW: can I use use rampart with JAX-WS style webservice
>
> Hi
> thanks for your answer.
> Unfortunately it does not seem to do the trick.
> I am getting the following error.
>
> [ERROR] com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 32 counts
> of IllegalAnnotationExceptions
> org.apache.axiom.attachments.lifecycle.LifecycleManager is an interface, and
> JAXB can't handle interfaces.
>
> I am beginning to think that it is not possible to engage Rampart with
> annotations.
>
> cheers
> Tezcan
> -Ursprüngliche Nachricht-
> Von: Ruchith Fernando [mailto:[EMAIL PROTECTED]
> Gesendet: Dienstag, 6. Mai 2008 09:57
> An: axis-user@ws.apache.org
> Betreff: Re: can I use use rampart with JAX-WS style webservice
>
>
> I haven't tried this but I think the following solution will work:
>
> - first implement lifecycle management on the service [1]
> - now in the "init" method you can get hold of the AxisService instance and
> then you can engage the rampart module on it.
> - Finally you can load the policy from a file as an
> org.apache.neethi.Policy object and add that to the AxisService instance as
> well.
>
> Now you have a WS-Sec enabled service :-)
>
> HTH
>
> Thanks,
> Ruchith
>
> p.s. You can also try WSO2 WSAS [2] and try the WS-Sec support available as
> well!
>
> 1.
> http://ws.apache.org/axis2/1_3/api/org/apache/axis2/service/Lifecycle.html
> 2. http://wso2.org/downloads/wsas
> On Wed, Apr 30, 2008 at 8:39 PM,  <[EMAIL PROTECTED]>
> wrote:
> >
> >
> >
> > Hi
> >
> > I have a web service developed using jax-ws style annotations. So it
> > does not require a services.xml, It is deployed to axis2 as jar file
> > under WEB-INF\servicejars directory.
> >
> > Now if I want to secure this service using rampart how do I link the
> > policy.xml?
> >
> > Where do I add the stuff such as  that one
> > usually adds into services.xml ?
> >
> >
> > cheers
> > Tezcan
>
>
>
> --
> http://blog.ruchith.org
> http://wso2.org
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> 
> NOTICE OF CONFIDENTIALITY
> This communication including any information transmitted with it is
> intended only for the use of the addressees and is confidential.
> If you are not an intended recipient or responsible for delivering
> the message to an intended recipient, any review, disclosure,
> conversion to hard copy, dissemination, reproduction or other use
> of any part of this communication is strictly prohibited, as is the
> taking or omitting of any action in reliance upon this communication.
> If you receive this communication in error or without authorization
> please notify us immediately by return e-mail or otherwise and
> permanently delete the entire communication from any computer,
> disk drive, or other storage medium.
>
> If the above disclaimer is not properly readable, it can be found at
> www.td.com/legal
>
> AVERTISSEMENT DE CONFIDENTIALITE
> Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement
> aux destinataires susmentionnés,  est confidentiel.  Si vous
> n'êtes pas le destinataire prévu ou un agent responsable de la
> livraison de ce courriel, tout examen, divulgation, copie, impression,
> reproduction, distribution, ou autre utilisation d'une partie de ce
> courriel est strictement interdit de même que toute intervention ou
> abstraction à cet égard.  Si vous avez reçu ce message par erreur ou
> sans autorisation, veuillez en aviser immédiatement l'expéditeur par
> retour de courriel ou par un autre moyen et supprimer immédiatement
> cette communication entière de tout système électronique.
>
> Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous
> pouv

Re: Problem with engaging security module in Axis2 1.4 version

[Nandana Mihindukulasooriya]

Hari,

 I have this class in the class path but what I found out is the
> ModulePolicyExtension class belongs to
> org.apache.axis2.wsdl.codegen.extension
>
> But the error I am getting is for this class org*/*apache*/*axis2*/*
> modules*/*ModulePolicyExtension
> Some where the code is looking for
> org.apache.axis2.modules.ModulePolicyExtension class
>
> Any inputs?
>

This seems to be strange. look at this commit [1]. It seems that Axis2 has
replaced org.apache.axis2.modules.ModulePolicyExtension class with
org.apache.axis2.wsdl.codegen.extension.ModulePolicyExtension . So there is
no way Rampart 1.4 could refer to this class.  Just guessing, is there a
chance that there is Rampart 1.1 or 1.2 jars in your class path.

thanks,
nandana

[1] -
http://markmail.org/message/6vx7ijlhgsdrym6t?q=list:org%2Eapache%2Ews%2Eaxis-cvs+org%2Eapache%2Eaxis2%2Emodules%2EModulePolicyExtension



> On 5/8/08, Nandana Mihindukulasooriya <[EMAIL PROTECTED]> wrote:
>>
>> Hi Hari,
>> do you have axis2-codegen-1.4.jar in your classpath ? If not, please
>> add this jar in to your classpath. This jar ships with Axis2 binary
>> distribution under lib. Even if you download the war distribution or create
>> the distribution using maven, it is there. But if you create the war using
>> the ant task in binary distribution, that script explicitly excludes this
>> jar. :( .
>>
>> thanks,
>> nandana
>>
>>
>>  On 5/8/08, Hari Prasad <[EMAIL PROTECTED]> wrote:
>>>
>>> Hi Nandana,
>>>
>>> Thanks for the tips on debugging. I debugged the code and found that the
>>> faulty modules has this 'rampart' module in it.
>>> The error is the following
>>>
>>> java
>>> *.*lang*.*NoClassDefFoundError*:* org*/*apache*/*axis2*/*modules*/*
>>> ModulePolicyExtension
>>> Which axis2 jar contains this class? I searched in all jars but could not
>>> find this class. I downloaded the axis2-1.4 binaries yesterday.
>>> Regards
>>> Hari P
>>>
>>>  On 5/8/08, Nandana Mihindukulasooriya <[EMAIL PROTECTED]> wrote:

 Hi Hari,

  There are no compilation errors but when I run the program , I get the
> same error
> "org.apache.axis2.AxisFault: The system is attempting to engage a
> module that is not available: rampart"
>

 The possible reason is Rampart might not have been deployed correctly.
 Did you add all dependency jars to your classpath ? And if you can debug,
 you can check ConfigurationContext ->
 axisConfiguration -> faultyModules to check the reason why it has
 actually failed to deploy.

 BTW, Are you using a custom axis2.xml ?

 thanks,
 nandana


>
> On 5/8/08, Nandana Mihindukulasooriya <[EMAIL PROTECTED]> wrote:
>>
>> Hi Hari,
>>
>>> Not knowing what else needs to be done?. I tried using rampart with
>>> 1.4 It didn't work. Does Rampart
>>> supported with axis2 1.4?
>>>
>>
>> Yes, you can download Rampart 1.4 RC2 here [1]. Configuration should
>> be like this.
>>
>> 
>>
>> 
>> 
>> UsernameToken Timestamp
>> bob
>>
>> org.apache.rampart.samples.sample02.PWCBHandler
>> 
>> 
>>
>> you can find the complete axis2.xml here [2]. You can go through the
>> samples come with Rampart distribution to get a better understanding.
>>
>>
>> [1] - 
>> http://people.apache.org/~nandana/rampart-1.4/RC2/dist/
>> [2] -
>> http://svn.apache.org/repos/asf/webservices/rampart/trunk/java/modules/rampart-samples/basic/sample02/client.axis2.xml
>>
>>
>> thanks,
>> nandana
>>
>>
>
>>>
>>
>>
>> --
>> Nandana Mihindukulasooriya
>> WSO2 inc.
>>
>> http://nandana83.blogspot.com/
>> http://nandanasm.wordpress.com/
>>
>
>

Re: Axis2: Error while trying to use Wsdl2Java eclipse plugin

[Shawn Talbot]

It works now! Thank-you for pointing the solution to the problem.
This was driving me bonkers.

Thanks,
Shawn

Tom Seelbach wrote:
Looks like same problem as 
https://issues.apache.org/jira/browse/AXIS2-3792
The backport-util-concurrent-3.1.jar  is in the lib directory of the 
main 1.4 binary distro, but not in the 
eclipse-codegen-wizard-1.4.zip.  Try adding it and see if it helps.


-Tom
 Original Message 
Subject: Re: Axis2: Error while trying to use Wsdl2Java eclipse 
plugin

Date: Thu, 08 May 2008 16:16:22 -0400
From: Shawn Talbot <[EMAIL PROTECTED]>
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
References: <[EMAIL PROTECTED]>



Hello,

Could I please have some suggestions on how to get the 1.4 codegen 
plugin to work in eclipse?


I have attached copies of the error output from when I ran eclipse in 
debug mode and some wsdl I am attempting to generate stubs for.


Any help would be much appreciated.

Thanks,
Shawn


Shawn Talbot wrote:

Hello,

My problem is that I have been unable to generate client stubs for 
any WSDL using the eclipse Wsdl2Java tool.


I have just downloaded the latest axis2 1.4 binary distribution and 
eclipse tools.


At the last step, when I click finish I always get a "An error 
occurred while completing process 
-java.lang.reflect.InvocationTargetException" pop-up in eclipse.
I have tried this under both eclipse 3.3 and eclipse 3.4-m6. (with 
the axis2 home directory set, and the eclipse axis2 preferences field 
pointed to the axis2 1.4 directory)
The tool will not even work for me with using the default Version 
service that comes with axis2.
(I have also noticed that the plugins for axis2 1.4 are called 1.3.0 
in the eclipse plugin xml file...)

I am running windows xp, and JDK 6.
Please note that I had used axis2 1.3 on this same machine 
successfully for the past 4 months.


Has anyone else encountered this error? Can someone help me to get 
axis2 1.4 up and running on my dev machine under eclipse?


Any help is appreciated

Thanks,
Shawn





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





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

Direct access to Axis APIs to parse SOAP XML

[chinmaya sn (chins)]

Hi,
I have a WSDL + XSD file. I used axis to implement a server for the given
WSDL.
So I used the Java Objects and Skeleton generated by Axis' wsdl2java.

Now I have a requirement where I have a soap XML file which will be same as
SOAP request XML. Only difference is instead of getting it over HTTP
I will be reading it from a flat file.

Now I want to use Axis to execute SOAP operation based on this XML file.

So.. Can I feed this SOAP xml file to any AXIS APIs so that it calls
my current server implementation (the one which implements skeleton).

Thanks
Chinmaya

Re: Axis2: Error while trying to use Wsdl2Java eclipse plugin

[Tom Seelbach]

Looks like same problem as https://issues.apache.org/jira/browse/AXIS2-3792
The backport-util-concurrent-3.1.jar  is in the lib directory of the 
main 1.4 binary distro, but not in the eclipse-codegen-wizard-1.4.zip.  
Try adding it and see if it helps.


-Tom
 Original Message 
Subject:Re: Axis2: Error while trying to use Wsdl2Java eclipse plugin
Date:   Thu, 08 May 2008 16:16:22 -0400
From:   Shawn Talbot <[EMAIL PROTECTED]>
Reply-To:   axis-user@ws.apache.org
To: axis-user@ws.apache.org
References: <[EMAIL PROTECTED]>



Hello,

Could I please have some suggestions on how to get the 1.4 codegen 
plugin to work in eclipse?


I have attached copies of the error output from when I ran eclipse in 
debug mode and some wsdl I am attempting to generate stubs for.


Any help would be much appreciated.

Thanks,
Shawn


Shawn Talbot wrote:

Hello,

My problem is that I have been unable to generate client stubs for any 
WSDL using the eclipse Wsdl2Java tool.


I have just downloaded the latest axis2 1.4 binary distribution and 
eclipse tools.


At the last step, when I click finish I always get a "An error 
occurred while completing process 
-java.lang.reflect.InvocationTargetException" pop-up in eclipse.
I have tried this under both eclipse 3.3 and eclipse 3.4-m6. (with the 
axis2 home directory set, and the eclipse axis2 preferences field 
pointed to the axis2 1.4 directory)
The tool will not even work for me with using the default Version 
service that comes with axis2.
(I have also noticed that the plugins for axis2 1.4 are called 1.3.0 
in the eclipse plugin xml file...)

I am running windows xp, and JDK 6.
Please note that I had used axis2 1.3 on this same machine 
successfully for the past 4 months.


Has anyone else encountered this error? Can someone help me to get 
axis2 1.4 up and running on my dev machine under eclipse?


Any help is appreciated

Thanks,
Shawn





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

Re: Axis2: Error while trying to use Wsdl2Java eclipse plugin

[Shawn Talbot]

Hello,

Could I please have some suggestions on how to get the 1.4 codegen 
plugin to work in eclipse?


I have attached copies of the error output from when I ran eclipse in 
debug mode and some wsdl I am attempting to generate stubs for.


Any help would be much appreciated.

Thanks,
Shawn


Shawn Talbot wrote:

Hello,

My problem is that I have been unable to generate client stubs for any 
WSDL using the eclipse Wsdl2Java tool.


I have just downloaded the latest axis2 1.4 binary distribution and 
eclipse tools.


At the last step, when I click finish I always get a "An error 
occurred while completing process 
-java.lang.reflect.InvocationTargetException" pop-up in eclipse.
I have tried this under both eclipse 3.3 and eclipse 3.4-m6. (with the 
axis2 home directory set, and the eclipse axis2 preferences field 
pointed to the axis2 1.4 directory)
The tool will not even work for me with using the default Version 
service that comes with axis2.
(I have also noticed that the plugins for axis2 1.4 are called 1.3.0 
in the eclipse plugin xml file...)

I am running windows xp, and JDK 6.
Please note that I had used axis2 1.3 on this same machine 
successfully for the past 4 months.


Has anyone else encountered this error? Can someone help me to get 
axis2 1.4 up and running on my dev machine under eclipse?


Any help is appreciated

Thanks,
Shawn



Retrieving document at 'c:\\helloservice.xml'.
Retrieving document at 'c:\\helloservice.xml'.
java.lang.reflect.InvocationTargetException
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalCont
ext.java:422)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:347)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:934)
at org.apache.axis2.tool.codegen.eclipse.CodeGenWizard.doFinishWSDL2Java
(CodeGenWizard.java:353)
at org.apache.axis2.tool.codegen.eclipse.CodeGenWizard.performFinish(Cod
eGenWizard.java:171)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java
:742)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java
:373)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:
227)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:83)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1002)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3773)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3372)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(Wiz
ardHandler.java:260)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.
java:280)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.ja
va:273)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)

at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(Para
meterizedCommand.java:508)
at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(Handle
rService.java:169)
at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(S
laveHandlerService.java:247)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAct
ion.java:157)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection
(ActionContributionItem.java:582)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContri
butionItem.java:499)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionC
ontributionItem.java:410)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:83)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1002)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3773)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3372)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2375)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2339)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2205)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:478)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.ja
va:288)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.jav
a:473)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEAppli
cation.java:106)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandl
e.java:193)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runAppli
cation(EclipseAppLaun

RE: WLS 10 MP1 - Axis 2 1.3 - BouncyCastle problem

[Simon Nunn]

Anyone?

 

From: Simon Nunn [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, March 05, 2008 8:46 AM
To: 'axis-user@ws.apache.org'
Subject: RE: WLS 10 MP1 - Axis 2 1.3 - BouncyCastle problem

 

Has anyone run into this?  Any suggestions would be appreciated.

 

Thanks,

 Simon

 

From: Simon Nunn [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 11:16 AM
To: axis-user@ws.apache.org
Subject: WLS 10 MP1 - Axis 2 1.3 - BouncyCastle problem

 

I am using WLS 10MP1 with Axis 2 v 1.3.  I am running into the same problem
that was described/fixed for http://issues.apache.org/jira/browse/AXIS2-811.
However, this bug was reported against an older version.  Has anyone else
ran into this problem?  I verified that the jar was indeed in the lib
directory, etc.  I had to use the "workaround" of modifying my java.security
file, and adding the bcprov-jdk15-132 .jar to my extensions directory.

 

Has anyone else ran into this and got it to work without modifying the
java.security file and copying the jar?

 

Thanks,

 Simon

RE: can I use use rampart with JAX-WS style webservice

[Savitsky, Alex]

Forgot to mention that we're using JAX-WS on the client side, too. There's no 
ServiceClient there. No ConfigurationContext, either. Any ideas? 
javax.xml.ws.Service is notoriously bad at exposing anything useful...


From: Nandana Mihindukulasooriya [mailto:[EMAIL PROTECTED]
Sent: May 8, 2008 1:18 PM
To: axis-user@ws.apache.org
Subject: Re: can I use use rampart with JAX-WS style webservice


How did you set the username/password on the client side? I can't find a way to 
get a hold on service Options...

http://wso2.org/library/3190#Step_3._Engaging_Rampart_and_setting_authentication_information


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: May 8, 2008 11:41 AM
To: axis-user@ws.apache.org
Subject: AW: can I use use rampart with JAX-WS style webservice

Hi Alex,
WOW..!!now I copied the policy.xml into axis2.xml config and the whole scenario 
(JAX-WS+Rampart policy) works fine.

As you said it in your mail, since I only have one service running, engaging 
rampart globally in axis2.xml and specifying the policy in there does the trick 
for me.

Cheers
Tezcan


-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 8. Mai 2008 17:16
An: axis-user@ws.apache.org
Betreff: AW: can I use use rampart with JAX-WS style webservice


Hi Alex,
I have pasted the policy into my wsdl for the time being and am refering to it 
in my service using wsdlLocation as shown below. The service is deployed in a 
jar file under WEB-INF\servicejars.
My client engages the addressing and rampart before calling the service.

If I comment out the  block in my wsdl and engage only 
addressing in my client the whole thing works just fine.

HTH

cheers
Tezcan


@WebService(endpointInterface = "demo.rampart.policy.sample.SimpleService",
   serviceName = "SecuredEcho",
   wsdlLocation="WEB-INF/wsdl/SecuredEcho.wsdl"
   )

@Addressing(enabled=true, required=true)

public class SimpleServiceImpl implements SimpleService{

   public String echo(String arg) {
   System.out.println("the server side echo==>"+arg);
   return arg;
   }
}
-Ursprüngliche Nachricht-
Von: Savitsky, Alex [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 8. Mai 2008 16:34
An: axis-user@ws.apache.org
Betreff: RE: can I use use rampart with JAX-WS style webservice


Not yet - I see the rampart deployment messages in the server log, and it seem 
to send the "must understand" headers, but no password is either sent or 
checked.

Where did you put your policy? I've placed mine in the axis config itself.

I'll keep you (and everyone here) posted.

HTH,

Alex

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: May 8, 2008 10:05 AM
To: axis-user@ws.apache.org
Subject: AW: can I use use rampart with JAX-WS style webservice

Hi Alex
thnx for the tip but this gives me my original exception "Must Understand check 
failed for headers" found in thread [1].:-( Does this work for you at global 
level?

cheers
Tezcan


[1]http://markmail.org/search/?q=list%3Aorg.apache.ws.axis-user+What+is+%22Must#query:list%3Aorg.apache.ws.axis-user%20What%20is%20%22Must+page:1+mid:jlc64h7qnvsoyfff+state:results

-Ursprüngliche Nachricht-
Von: Savitsky, Alex [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 8. Mai 2008 15:39
An: axis-user@ws.apache.org
Betreff: RE: can I use use rampart with JAX-WS style webservice


Declaring the rampart in axis2.xml global config (and putting the rampart.mar 
in WEB-INF/modules, of course) would engage it globally for all services. If 
you only have one service running, this might be what you need. I haven't found 
a way to engage a module ona per-service basis, though.

HTH,

Alex

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: May 8, 2008 7:43 AM
To: axis-user@ws.apache.org
Subject: AW: can I use use rampart with JAX-WS style webservice

Hi
thanks for your answer.
Unfortunately it does not seem to do the trick.
I am getting the following error.

[ERROR] com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 32 counts of 
IllegalAnnotationExceptions 
org.apache.axiom.attachments.lifecycle.LifecycleManager is an interface, and 
JAXB can't handle interfaces.

I am beginning to think that it is not possible to engage Rampart with 
annotations.

cheers
Tezcan
-Ursprüngliche Nachricht-
Von: Ruchith Fernando [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 6. Mai 2008 09:57
An: axis-user@ws.apache.org

Re: Problem with engaging security module in Axis2 1.4 version

[Hari Prasad]

Hi Nandana,

Yes I have this class in the class path but what I found out is the
ModulePolicyExtension class belongs to
org.apache.axis2.wsdl.codegen.extension

But the error I am getting is for this class org*/*apache*/*axis2*/*modules*
/*ModulePolicyExtension
Some where the code is looking for
org.apache.axis2.modules.ModulePolicyExtension class

Any inputs?

Regards
Hari P

On 5/8/08, Nandana Mihindukulasooriya <[EMAIL PROTECTED]> wrote:
>
> Hi Hari,
> do you have axis2-codegen-1.4.jar in your classpath ? If not, please
> add this jar in to your classpath. This jar ships with Axis2 binary
> distribution under lib. Even if you download the war distribution or create
> the distribution using maven, it is there. But if you create the war using
> the ant task in binary distribution, that script explicitly excludes this
> jar. :( .
>
> thanks,
> nandana
>
>
>  On 5/8/08, Hari Prasad <[EMAIL PROTECTED]> wrote:
> >
> > Hi Nandana,
> >
> > Thanks for the tips on debugging. I debugged the code and found that the
> > faulty modules has this 'rampart' module in it.
> > The error is the following
> >
> > java
> > *.*lang*.*NoClassDefFoundError*:* org*/*apache*/*axis2*/*modules*/*
> > ModulePolicyExtension
> > Which axis2 jar contains this class? I searched in all jars but could
> > not find this class. I downloaded the axis2-1.4 binaries yesterday.
> > Regards
> > Hari P
> >
> >  On 5/8/08, Nandana Mihindukulasooriya <[EMAIL PROTECTED]> wrote:
> > >
> > > Hi Hari,
> > >
> > >  There are no compilation errors but when I run the program , I get
> > > > the same error
> > > > "org.apache.axis2.AxisFault: The system is attempting to engage a
> > > > module that is not available: rampart"
> > > >
> > >
> > > The possible reason is Rampart might not have been deployed correctly.
> > > Did you add all dependency jars to your classpath ? And if you can debug,
> > > you can check ConfigurationContext ->
> > > axisConfiguration -> faultyModules to check the reason why it has
> > > actually failed to deploy.
> > >
> > > BTW, Are you using a custom axis2.xml ?
> > >
> > > thanks,
> > > nandana
> > >
> > >
> > > >
> > > > On 5/8/08, Nandana Mihindukulasooriya <[EMAIL PROTECTED]> wrote:
> > > > >
> > > > > Hi Hari,
> > > > >
> > > > > > Not knowing what else needs to be done?. I tried using rampart
> > > > > > with 1.4 It didn't work. Does Rampart
> > > > > > supported with axis2 1.4?
> > > > > >
> > > > >
> > > > > Yes, you can download Rampart 1.4 RC2 here [1]. Configuration
> > > > > should be like this.
> > > > >
> > > > > 
> > > > >
> > > > > 
> > > > > 
> > > > > UsernameToken Timestamp
> > > > > bob
> > > > >
> > > > > org.apache.rampart.samples.sample02.PWCBHandler
> > > > > 
> > > > > 
> > > > >
> > > > > you can find the complete axis2.xml here [2]. You can go through
> > > > > the samples come with Rampart distribution to get a better 
> > > > > understanding.
> > > > >
> > > > >
> > > > > [1] - 
> > > > > http://people.apache.org/~nandana/rampart-1.4/RC2/dist/
> > > > > [2] -
> > > > > http://svn.apache.org/repos/asf/webservices/rampart/trunk/java/modules/rampart-samples/basic/sample02/client.axis2.xml
> > > > >
> > > > >
> > > > > thanks,
> > > > > nandana
> > > > >
> > > > >
> > > >
> >
>
>
> --
> Nandana Mihindukulasooriya
> WSO2 inc.
>
> http://nandana83.blogspot.com/
> http://nandanasm.wordpress.com/
>

Re: [Rampart] What is the correct way to secure a JAX-WS service?

[Davanum Srinivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Yep. looks like we forgot to yank that.

- -- dims

Paul Fremantle wrote:
| I was confused by:
| axis2-1.3\samples\jaxws-calculator\resources\META-INF\services.xml
|
| Paul
|
| On Thu, May 8, 2008 at 3:25 PM, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
| Paul,
|
| No. You can't use a services.xml with JAX-WS.
|
| thanks,
| -- dims
|
| Paul Fremantle wrote:
| | Isn't it possible to use a services.xml together with JAX-WS - at
| | least to get this working?
| |
| | Paul
| |
| | On Thu, May 8, 2008 at 2:59 PM, Nandana Mihindukulasooriya
| | <[EMAIL PROTECTED]> wrote:
| |> Hi Alex,
| |>
| |>> especially that it doesn't look like anyone from Axis team has tried
| this
| |>> particular (JAX-WS + Rampart) configuration just yet (I hope the JAX-WS
| will
| |>> be addressed in more details in Rampart 1.4).
| |> Yes, it is not in the Road map of Rampart 1.4. Anyway we think this is
| |> something we should support. So we will look in to this and try to see if
| we
| |> can find a way to get this working before the Rampart 1.4 release.
| |>
| |>> Nevertheless, I will continue my investigations, bugs or not. I believe
| |>> I'm close...
| |> That is great news. Please let us know if you need any information from
| |> Rampart side.
| |>
| |> thanks,
| |> nandana
| |>
| |>> 
| |>> From: Nandana Mihindukulasooriya [mailto:[EMAIL PROTECTED]
| |>> Sent: May 7, 2008 11:51 PM
| |>> To: axis-user@ws.apache.org
| |>> Subject: Re: [Rampart] What is the correct way to secure a JAX-WS
| service?
| |>>
| |>> Hi Alex,
| |>>   Have you looked at  this thread  [1] ?
| |>>
| |>> thanks,
| |>> nandana
| |>>
| |>> [1] -
| |>>
| 
http://markmail.org/message/dkwjvskrh3gysvnw?q=list:org%2Eapache%2Ews%2Eaxis-user+can+I+use+use+rampart
| |>>
| |>>
| |>> On Wed, May 7, 2008 at 10:26 PM, Savitsky, Alex
| |>> <[EMAIL PROTECTED]> wrote:
| |>>> Hi,
| |>>>
| |>>> Usually, Axis2 services are secured using Rampart, by engaging the
| |>>> module, and specifying the policy in services.xml. However, this won't
| do
| |>>> for services deployed via JAX-WS annotations, as there's no
| services.xml
| |>>> file there. The module could still be deployed, as long as it's placed
| in
| |>>> WEB-INF/modules - but where would one have to place the policy file,
| for it
| |>>> to be picked up by the Rampart? Are there any annotations one has to
| specify
| |>>> on the service endpoint, to specify that the service is using
| WS-Security?
| |>>>
| |>>> I looked at the @HandlerCHain annotation, but the Rampart handlers are
| |>>> not based on the JAX-WS handler interfaces, but on some internal Axis2
| ones,
| |>>> and thus cannot be used in JAX-WS handler chains
| |>>>
| |>>> And final question - does Rampart even support JAX-WS style services?
| |>>>
| |>>> Thanks,
| |>>>
| |>>> Alex
| |>>>
| |>>> 
| |>>> NOTICE OF CONFIDENTIALITY
| |>>> This communication including any information transmitted with it is
| |>>> intended only for the use of the addressees and is confidential.
| |>>> If you are not an intended recipient or responsible for delivering
| |>>> the message to an intended recipient, any review, disclosure,
| |>>> conversion to hard copy, dissemination, reproduction or other use
| |>>> of any part of this communication is strictly prohibited, as is the
| |>>> taking or omitting of any action in reliance upon this communication.
| |>>> If you receive this communication in error or without authorization
| |>>> please notify us immediately by return e-mail or otherwise and
| |>>> permanently delete the entire communication from any computer,
| |>>> disk drive, or other storage medium.
| |>>>
| |>>> If the above disclaimer is not properly readable, it can be found at
| |>>> www.td.com/legal
| |>>>
| |>>> AVERTISSEMENT DE CONFIDENTIALITE
| |>>> Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement
| |>>> aux destinataires susmentionnés,  est confidentiel.  Si vous
| |>>> n'êtes pas le destinataire prévu ou un agent responsable de la
| |>>> livraison de ce courriel, tout examen, divulgation, copie, impression,
| |>>> reproduction, distribution, ou autre utilisation d'une partie de ce
| |>>> courriel est strictement interdit de même que toute intervention ou
| |>>> abstraction à cet égard.  Si vous avez reçu ce message par erreur ou
| |>>> sans autorisation, veuillez en aviser immédiatement l'expéditeur par
| |>>> retour de courriel ou par un autre moyen et supprimer immédiatement
| |>>> cette communication entière de tout système électronique.
| |>>>
| |>>> Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous
| |>>> pouvez le consulter à www.td.com/francais/legale
| |
| |
| |
|>
- -
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
|>
|>

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)

iD8DBQFIIzZfgNg6eWEDv

Re: can I use use rampart with JAX-WS style webservice

[Nandana Mihindukulasooriya]

> How did you set the username/password on the client side? I can't find a
> way to get a hold on service Options...


http://wso2.org/library/3190#Step_3._Engaging_Rampart_and_setting_authentication_information


>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED]
> Sent: May 8, 2008 11:41 AM
> To: axis-user@ws.apache.org
> Subject: AW: can I use use rampart with JAX-WS style webservice
>
> Hi Alex,
> WOW..!!now I copied the policy.xml into axis2.xml config and the whole
> scenario (JAX-WS+Rampart policy) works fine.
>
> As you said it in your mail, since I only have one service running,
> engaging rampart globally in axis2.xml and specifying the policy in there
> does the trick for me.
>
> Cheers
> Tezcan
>
>
> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED]
> Gesendet: Donnerstag, 8. Mai 2008 17:16
> An: axis-user@ws.apache.org
> Betreff: AW: can I use use rampart with JAX-WS style webservice
>
>
> Hi Alex,
> I have pasted the policy into my wsdl for the time being and am refering
> to it in my service using wsdlLocation as shown below. The service is
> deployed in a jar file under WEB-INF\servicejars.
> My client engages the addressing and rampart before calling the service.
>
> If I comment out the  block in my wsdl and engage
> only addressing in my client the whole thing works just fine.
>
> HTH
>
> cheers
> Tezcan
>
>
> @WebService(endpointInterface =
> "demo.rampart.policy.sample.SimpleService",
>serviceName = "SecuredEcho",
>wsdlLocation="WEB-INF/wsdl/SecuredEcho.wsdl"
>)
>
> @Addressing(enabled=true, required=true)
>
> public class SimpleServiceImpl implements SimpleService{
>
>public String echo(String arg) {
>System.out.println("the server side echo==>"+arg);
>return arg;
>}
> }
> -Ursprüngliche Nachricht-
> Von: Savitsky, Alex [mailto:[EMAIL PROTECTED]
> Gesendet: Donnerstag, 8. Mai 2008 16:34
> An: axis-user@ws.apache.org
> Betreff: RE: can I use use rampart with JAX-WS style webservice
>
>
> Not yet - I see the rampart deployment messages in the server log, and it
> seem to send the "must understand" headers, but no password is either sent
> or checked.
>
> Where did you put your policy? I've placed mine in the axis config itself.
>
> I'll keep you (and everyone here) posted.
>
> HTH,
>
> Alex
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED]
> Sent: May 8, 2008 10:05 AM
> To: axis-user@ws.apache.org
> Subject: AW: can I use use rampart with JAX-WS style webservice
>
> Hi Alex
> thnx for the tip but this gives me my original exception "Must Understand
> check failed for headers" found in thread [1].:-( Does this work for you at
> global level?
>
> cheers
> Tezcan
>
>
> [1]
> http://markmail.org/search/?q=list%3Aorg.apache.ws.axis-user+What+is+%22Must#query:list%3Aorg.apache.ws.axis-user%20What%20is%20%22Must+page:1+mid:jlc64h7qnvsoyfff+state:results
>
> -Ursprüngliche Nachricht-
> Von: Savitsky, Alex [mailto:[EMAIL PROTECTED]
> Gesendet: Donnerstag, 8. Mai 2008 15:39
> An: axis-user@ws.apache.org
> Betreff: RE: can I use use rampart with JAX-WS style webservice
>
>
> Declaring the rampart in axis2.xml global config (and putting the
> rampart.mar in WEB-INF/modules, of course) would engage it globally for all
> services. If you only have one service running, this might be what you need.
> I haven't found a way to engage a module ona per-service basis, though.
>
> HTH,
>
> Alex
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED]
> Sent: May 8, 2008 7:43 AM
> To: axis-user@ws.apache.org
> Subject: AW: can I use use rampart with JAX-WS style webservice
>
> Hi
> thanks for your answer.
> Unfortunately it does not seem to do the trick.
> I am getting the following error.
>
> [ERROR] com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 32 counts
> of IllegalAnnotationExceptions
> org.apache.axiom.attachments.lifecycle.LifecycleManager is an interface, and
> JAXB can't handle interfaces.
>
> I am beginning to think that it is not possible to engage Rampart with
> annotations.
>
> cheers
> Tezcan
> -Ursprüngliche Nachricht-
> Von: Ruchith Fernando [mailto:[EMAIL PROTECTED]
> Gesendet: Dienstag, 6. Mai 2008 09:57
> An: axis-user@ws.apache.org
> Betreff: Re: can I use use rampart with JAX-WS style webservice
>
>
> I haven't tried this but I think the following solution will work:
>
> - first implement lifecycle management on the service [1]
> - now in the "init" method you can get hold of the AxisService instance
> and then you can engage the rampart module on it.
> - Finally you can load the policy from a file as an
> org.apache.neethi.Policy object and add that to the AxisService instance as
> well.
>
> Now you have a WS-Sec enabled service :-)
>
> HTH
>
> Thanks,
> Ruchith
>
> p.s. You can also try WSO2 WSAS [2] and try the WS-Sec supp

Getting Class not found error

[Minal Satpute]

Hello there, I am getting DeploymentException:
java.land.NoClassDefFoundError for one of my external library used in my java
class. I checked that jar file is in classpath while I creating
"service.aar"Please help.Thanks & Kind Regards,Minal Satpute


_
Make Windows Vista more reliable and secure with Windows Vista Service Pack 1.
http://www.windowsvista.com/SP1?WT.mc_id=hotmailvistasp1banner

Re: Problem with engaging security module in Axis2 1.4 version

[Nandana Mihindukulasooriya]

Hi Hari,
do you have axis2-codegen-1.4.jar in your classpath ? If not, please add
this jar in to your classpath. This jar ships with Axis2 binary distribution
under lib. Even if you download the war distribution or create the
distribution using maven, it is there. But if you create the war using the
ant task in binary distribution, that script explicitly excludes this jar.
:( .

thanks,
nandana


On 5/8/08, Hari Prasad <[EMAIL PROTECTED]> wrote:
>
> Hi Nandana,
>
> Thanks for the tips on debugging. I debugged the code and found that the
> faulty modules has this 'rampart' module in it.
> The error is the following
>
> java
> *.*lang*.*NoClassDefFoundError*:* org*/*apache*/*axis2*/*modules*/*
> ModulePolicyExtension
> Which axis2 jar contains this class? I searched in all jars but could not
> find this class. I downloaded the axis2-1.4 binaries yesterday.
> Regards
> Hari P
>
>  On 5/8/08, Nandana Mihindukulasooriya <[EMAIL PROTECTED]> wrote:
> >
> > Hi Hari,
> >
> >  There are no compilation errors but when I run the program , I get the
> > > same error
> > > "org.apache.axis2.AxisFault: The system is attempting to engage a
> > > module that is not available: rampart"
> > >
> >
> > The possible reason is Rampart might not have been deployed correctly.
> > Did you add all dependency jars to your classpath ? And if you can debug,
> > you can check ConfigurationContext ->
> > axisConfiguration -> faultyModules to check the reason why it has
> > actually failed to deploy.
> >
> > BTW, Are you using a custom axis2.xml ?
> >
> > thanks,
> > nandana
> >
> >
> > >
> > > On 5/8/08, Nandana Mihindukulasooriya <[EMAIL PROTECTED]> wrote:
> > > >
> > > > Hi Hari,
> > > >
> > > > > Not knowing what else needs to be done?. I tried using rampart
> > > > > with 1.4 It didn't work. Does Rampart
> > > > > supported with axis2 1.4?
> > > > >
> > > >
> > > > Yes, you can download Rampart 1.4 RC2 here [1]. Configuration should
> > > > be like this.
> > > >
> > > > 
> > > >
> > > > 
> > > > 
> > > > UsernameToken Timestamp
> > > > bob
> > > >
> > > > org.apache.rampart.samples.sample02.PWCBHandler
> > > > 
> > > > 
> > > >
> > > > you can find the complete axis2.xml here [2]. You can go through the
> > > > samples come with Rampart distribution to get a better understanding.
> > > >
> > > >
> > > > [1] - 
> > > > http://people.apache.org/~nandana/rampart-1.4/RC2/dist/
> > > > [2] -
> > > > http://svn.apache.org/repos/asf/webservices/rampart/trunk/java/modules/rampart-samples/basic/sample02/client.axis2.xml
> > > >
> > > >
> > > > thanks,
> > > > nandana
> > > >
> > > >
> > >
>


-- 
Nandana Mihindukulasooriya
WSO2 inc.

http://nandana83.blogspot.com/
http://nandanasm.wordpress.com/

RE: question about CommonHTTPTransportSender

[Beth Ayres]

Can the keystore, truststore, and password be set in the axis2.xml config?  If 
so, what is the syntax?

From: Upul Godage [mailto:[EMAIL PROTECTED]
Sent: Monday, April 28, 2008 5:39 AM
To: axis-user@ws.apache.org
Subject: Re: question about CommonHTTPTransportSender

Like the "http" transport sender, there is an "https" transport sender defined 
in the axis2.xml. You may need to set the key stores.

Upul

On Mon, Apr 28, 2008 at 1:06 PM, mathieu fabre <[EMAIL PROTECTED]> wrote:
Hi,

I work on a webapp and i use Axis2 to expose my services.

my webapp is managed by jetty (like tomcat but lightweight).
Jetty listen on port 8443 with HTTPS (SSL) and on port 8080 with HTTP (no SSL)
I wrote a little client which create a RPCServiceClient to send a request.

Here a piece of code :

//Create an empty configuration context
config = 
ConfigurationContextFactory.createConfigurationContextFromFileSystem(null, 
null);
// Create a transport out description
TransportOutDescription transpOut = new 
TransportOutDescription(Constants.TRANSPORT_HTTP);
transpOut.addParameter(new Parameter(HTTPConstants.PROTOCOL_VERSION, 
"HTTP/1.1"));
//create the HTTP sender
CommonsHTTPTransportSender sender = new CommonsHTTPTransportSender();
//initialize the sender
sender.init(config, transpOut);
transpOut.setSender(sender);
config.getAxisConfiguration().addTransportOut(transpOut);
//create the RPCServiceClient
RPCServiceClient serviceClient = new RPCServiceClient(config, null);
Options options = serviceClient.getOptions();
EndpointReference targetEPR = new EndpointReference(url);
options.setTo(targetEPR);

run the request with invokeBlocking


with HTTP, it work correctly, but i don't know what to do in order to use HTTPS
The server does not expect to authenticate the client for the moment.
If i try to view the wsd of on of my services with mozilla, it's working (i 
accept the certificate)
So i would like to do the same in the code

Do you know what i must do ...?

Thanks,

Mat

Re: [Rampart] What is the correct way to secure a JAX-WS service?

[Paul Fremantle]

I was confused by:
axis2-1.3\samples\jaxws-calculator\resources\META-INF\services.xml

Paul

On Thu, May 8, 2008 at 3:25 PM, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Paul,
>
> No. You can't use a services.xml with JAX-WS.
>
> thanks,
> - -- dims
>
> Paul Fremantle wrote:
> | Isn't it possible to use a services.xml together with JAX-WS - at
> | least to get this working?
> |
> | Paul
> |
> | On Thu, May 8, 2008 at 2:59 PM, Nandana Mihindukulasooriya
> | <[EMAIL PROTECTED]> wrote:
> |> Hi Alex,
> |>
> |>> especially that it doesn't look like anyone from Axis team has tried
> this
> |>> particular (JAX-WS + Rampart) configuration just yet (I hope the JAX-WS
> will
> |>> be addressed in more details in Rampart 1.4).
> |> Yes, it is not in the Road map of Rampart 1.4. Anyway we think this is
> |> something we should support. So we will look in to this and try to see if
> we
> |> can find a way to get this working before the Rampart 1.4 release.
> |>
> |>> Nevertheless, I will continue my investigations, bugs or not. I believe
> |>> I'm close...
> |> That is great news. Please let us know if you need any information from
> |> Rampart side.
> |>
> |> thanks,
> |> nandana
> |>
> |>> 
> |>> From: Nandana Mihindukulasooriya [mailto:[EMAIL PROTECTED]
> |>> Sent: May 7, 2008 11:51 PM
> |>> To: axis-user@ws.apache.org
> |>> Subject: Re: [Rampart] What is the correct way to secure a JAX-WS
> service?
> |>>
> |>> Hi Alex,
> |>>   Have you looked at  this thread  [1] ?
> |>>
> |>> thanks,
> |>> nandana
> |>>
> |>> [1] -
> |>>
> http://markmail.org/message/dkwjvskrh3gysvnw?q=list:org%2Eapache%2Ews%2Eaxis-user+can+I+use+use+rampart
> |>>
> |>>
> |>> On Wed, May 7, 2008 at 10:26 PM, Savitsky, Alex
> |>> <[EMAIL PROTECTED]> wrote:
> |>>> Hi,
> |>>>
> |>>> Usually, Axis2 services are secured using Rampart, by engaging the
> |>>> module, and specifying the policy in services.xml. However, this won't
> do
> |>>> for services deployed via JAX-WS annotations, as there's no
> services.xml
> |>>> file there. The module could still be deployed, as long as it's placed
> in
> |>>> WEB-INF/modules - but where would one have to place the policy file,
> for it
> |>>> to be picked up by the Rampart? Are there any annotations one has to
> specify
> |>>> on the service endpoint, to specify that the service is using
> WS-Security?
> |>>>
> |>>> I looked at the @HandlerCHain annotation, but the Rampart handlers are
> |>>> not based on the JAX-WS handler interfaces, but on some internal Axis2
> ones,
> |>>> and thus cannot be used in JAX-WS handler chains
> |>>>
> |>>> And final question - does Rampart even support JAX-WS style services?
> |>>>
> |>>> Thanks,
> |>>>
> |>>> Alex
> |>>>
> |>>> 
> |>>> NOTICE OF CONFIDENTIALITY
> |>>> This communication including any information transmitted with it is
> |>>> intended only for the use of the addressees and is confidential.
> |>>> If you are not an intended recipient or responsible for delivering
> |>>> the message to an intended recipient, any review, disclosure,
> |>>> conversion to hard copy, dissemination, reproduction or other use
> |>>> of any part of this communication is strictly prohibited, as is the
> |>>> taking or omitting of any action in reliance upon this communication.
> |>>> If you receive this communication in error or without authorization
> |>>> please notify us immediately by return e-mail or otherwise and
> |>>> permanently delete the entire communication from any computer,
> |>>> disk drive, or other storage medium.
> |>>>
> |>>> If the above disclaimer is not properly readable, it can be found at
> |>>> www.td.com/legal
> |>>>
> |>>> AVERTISSEMENT DE CONFIDENTIALITE
> |>>> Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement
> |>>> aux destinataires susmentionnés,  est confidentiel.  Si vous
> |>>> n'êtes pas le destinataire prévu ou un agent responsable de la
> |>>> livraison de ce courriel, tout examen, divulgation, copie, impression,
> |>>> reproduction, distribution, ou autre utilisation d'une partie de ce
> |>>> courriel est strictement interdit de même que toute intervention ou
> |>>> abstraction à cet égard.  Si vous avez reçu ce message par erreur ou
> |>>> sans autorisation, veuillez en aviser immédiatement l'expéditeur par
> |>>> retour de courriel ou par un autre moyen et supprimer immédiatement
> |>>> cette communication entière de tout système électronique.
> |>>>
> |>>> Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous
> |>>> pouvez le consulter à www.td.com/francais/legale
> |
> |
> |
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.5 (Cygwin)
>
> iD8DBQFIIw1JgNg6eWEDv1kRAs6kAJ9t8KDRjrDRXl/1sPDLag3Cf/in5QCgoGxo
> JK3czxxikJYPSWQSiKvY23I=
> =VHFk
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional com

Re: Problem with engaging security module in Axis2 1.4 version

[Hari Prasad]

Hi Nandana,

Thanks for the tips on debugging. I debugged the code and found that the
faulty modules has this 'rampart' module in it.
The error is the following

java*.*lang*.*NoClassDefFoundError*:* org*/*apache*/*axis2*/*modules*/*
ModulePolicyExtension
Which axis2 jar contains this class? I searched in all jars but could not
find this class. I downloaded the axis2-1.4 binaries yesterday.

Regards
Hari P

On 5/8/08, Nandana Mihindukulasooriya <[EMAIL PROTECTED]> wrote:
>
> Hi Hari,
>
>  There are no compilation errors but when I run the program , I get the
> > same error
> > "org.apache.axis2.AxisFault: The system is attempting to engage a module
> > that is not available: rampart"
> >
>
> The possible reason is Rampart might not have been deployed correctly. Did
> you add all dependency jars to your classpath ? And if you can debug, you
> can check ConfigurationContext ->
> axisConfiguration -> faultyModules to check the reason why it has actually
> failed to deploy.
>
> BTW, Are you using a custom axis2.xml ?
>
> thanks,
> nandana
>
>
> >
> > On 5/8/08, Nandana Mihindukulasooriya <[EMAIL PROTECTED]> wrote:
> > >
> > > Hi Hari,
> > >
> > > > Not knowing what else needs to be done?. I tried using rampart with
> > > > 1.4 It didn't work. Does Rampart
> > > > supported with axis2 1.4?
> > > >
> > >
> > > Yes, you can download Rampart 1.4 RC2 here [1]. Configuration should
> > > be like this.
> > >
> > > 
> > >
> > > 
> > > 
> > > UsernameToken Timestamp
> > > bob
> > >
> > > org.apache.rampart.samples.sample02.PWCBHandler
> > > 
> > > 
> > >
> > > you can find the complete axis2.xml here [2]. You can go through the
> > > samples come with Rampart distribution to get a better understanding.
> > >
> > >
> > > [1] - 
> > > http://people.apache.org/~nandana/rampart-1.4/RC2/dist/
> > > [2] -
> > > http://svn.apache.org/repos/asf/webservices/rampart/trunk/java/modules/rampart-samples/basic/sample02/client.axis2.xml
> > >
> > >
> > > thanks,
> > > nandana
> > >
> > >
> >

RE: can I use use rampart with JAX-WS style webservice

[Savitsky, Alex]

How did you set the username/password on the client side? I can't find a way to 
get a hold on service Options...

Thanks,

Alex

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: May 8, 2008 11:41 AM
To: axis-user@ws.apache.org
Subject: AW: can I use use rampart with JAX-WS style webservice

Hi Alex,
WOW..!!now I copied the policy.xml into axis2.xml config and the whole scenario 
(JAX-WS+Rampart policy) works fine.

As you said it in your mail, since I only have one service running, engaging 
rampart globally in axis2.xml and specifying the policy in there does the trick 
for me.

Cheers
Tezcan


-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 8. Mai 2008 17:16
An: axis-user@ws.apache.org
Betreff: AW: can I use use rampart with JAX-WS style webservice


Hi Alex,
I have pasted the policy into my wsdl for the time being and am refering to it 
in my service using wsdlLocation as shown below. The service is deployed in a 
jar file under WEB-INF\servicejars.
My client engages the addressing and rampart before calling the service.

If I comment out the  block in my wsdl and engage only 
addressing in my client the whole thing works just fine.

HTH

cheers
Tezcan


@WebService(endpointInterface = "demo.rampart.policy.sample.SimpleService",
serviceName = "SecuredEcho",
wsdlLocation="WEB-INF/wsdl/SecuredEcho.wsdl"
)

@Addressing(enabled=true, required=true)

public class SimpleServiceImpl implements SimpleService{

public String echo(String arg) {
System.out.println("the server side echo==>"+arg);
return arg;
}
}
-Ursprüngliche Nachricht-
Von: Savitsky, Alex [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 8. Mai 2008 16:34
An: axis-user@ws.apache.org
Betreff: RE: can I use use rampart with JAX-WS style webservice


Not yet - I see the rampart deployment messages in the server log, and it seem 
to send the "must understand" headers, but no password is either sent or 
checked.

Where did you put your policy? I've placed mine in the axis config itself.

I'll keep you (and everyone here) posted.

HTH,

Alex

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: May 8, 2008 10:05 AM
To: axis-user@ws.apache.org
Subject: AW: can I use use rampart with JAX-WS style webservice

Hi Alex
thnx for the tip but this gives me my original exception "Must Understand check 
failed for headers" found in thread [1].:-( Does this work for you at global 
level?

cheers
Tezcan


[1]http://markmail.org/search/?q=list%3Aorg.apache.ws.axis-user+What+is+%22Must#query:list%3Aorg.apache.ws.axis-user%20What%20is%20%22Must+page:1+mid:jlc64h7qnvsoyfff+state:results

-Ursprüngliche Nachricht-
Von: Savitsky, Alex [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 8. Mai 2008 15:39
An: axis-user@ws.apache.org
Betreff: RE: can I use use rampart with JAX-WS style webservice


Declaring the rampart in axis2.xml global config (and putting the rampart.mar 
in WEB-INF/modules, of course) would engage it globally for all services. If 
you only have one service running, this might be what you need. I haven't found 
a way to engage a module ona per-service basis, though.

HTH,

Alex

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: May 8, 2008 7:43 AM
To: axis-user@ws.apache.org
Subject: AW: can I use use rampart with JAX-WS style webservice

Hi
thanks for your answer.
Unfortunately it does not seem to do the trick.
I am getting the following error.

[ERROR] com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 32 counts of 
IllegalAnnotationExceptions 
org.apache.axiom.attachments.lifecycle.LifecycleManager is an interface, and 
JAXB can't handle interfaces.

I am beginning to think that it is not possible to engage Rampart with 
annotations.

cheers
Tezcan
-Ursprüngliche Nachricht-
Von: Ruchith Fernando [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 6. Mai 2008 09:57
An: axis-user@ws.apache.org
Betreff: Re: can I use use rampart with JAX-WS style webservice


I haven't tried this but I think the following solution will work:

- first implement lifecycle management on the service [1]
- now in the "init" method you can get hold of the AxisService instance and 
then you can engage the rampart module on it.
- Finally you can load the policy from a file as an org.apache.neethi.Policy 
object and add that to the AxisService instance as well.

Now you have a WS-Sec enabled service :-)

HTH

Thanks,
Ruchith

p.s. You can also try WSO2 WSAS [2] and try the WS-Sec support available as 
well!

1. http://ws.apache.org/axis2/1_3/api/org/apache/axis2/service/Lifecycle.html
2. http://wso2.org/downloads/wsas
On Wed, Apr 30, 2008 at 8:39 PM,  <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi
>
> I have a web service developed using jax-ws style annotations. So it
> does not require a services.xml, It is deployed to a

Casting AxisFault from InvocationTargetException.getTargetException)

[Larry Tan]

Hi,
I'm currently using Java Reflection to load my service locator, getting 
ports and invoke operations. Everything works fine for me apart from catching 
exceptions. As I'm currently aware, whatever AxisFault thrown by the web 
service call is wrapped under my InvocationTargetException which is available 
to me via the getCause() or getTargetException() method.

However, I cannot seem to cast the AxisFault into my specific exceptions. 
Given my port type operation signature is like this

public void myop(pars... ) throws ... MyPackage.StringMessage;

My (reflection) Java code are as follows

try {
Method methodOp;
Class serviceLocatorClass = Class.forName("...");
Object serviceLocator = serviceLocatorClass.newInstance();
Method getPortMethod = serviceLocatorClass.getMethod("");
Object port = getPortMethod.invoke(serviceLocator, null);
Method webServiceOp = port.getClass().getMethod("myop", parClasses);
Object result = webServiceOp.invoke(port, pars);
} catch (InvocationTargetException ex) {
if (ex.getTargetException() instanceof AxisFault) {
Class stringMessage = //  do loading of StringMessage via 
forName

ex.getTargetException().getClass().getName();// returns 
"AxisFault" which is not what i want as i'm expecting StringMessage
stringMessage.cast(ex.getTargetException());// 
encountered ClassCastException
}
} 

When my webs service throws StringMessage exception (I'm certain this is 
the thrown), I cannot seem to cast it successfully. I found out that 
ex.getTargetException().getClass().getName() returns me AxisFault instead of 
StringMessage.

I then try the static way, which
try {
port.myOp(...);
} catch (AxisFault ex) {
 ex.getTargetException().getClass().getName();// returns 
StringMessage!
}


Would appreciate advice on this! Many thanks in advance!

Best Regards,
Larry
-- 
The University of Stirling (a charity registered in Scotland, number
SC 011159) is a university established in Scotland by charter at Stirling,
FK9 4LA.  Privileged/Confidential Information may be contained in this
message.  If you are not the addressee indicated in this message (or
responsible for delivery of the message to such person), you may not
disclose, copy or deliver this message to anyone and any action taken or
omitted to be taken in reliance on it, is prohibited and may be unlawful.
In such case, you should destroy this message and kindly notify the sender
by reply email.  Please advise immediately if you or your employer do not
consent to Internet email for messages of this kind.

Re: axis2 1.4 incorrect wsdl with policy

[jason zhang]

Hi, Sanka
This does not work.
My original wsdl is like this

    ...
    
    ...


My service.xml is like this

    
        
       ...
false
true

            xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy">
            
                
                
            
            
   
...
          
The generated wsdl does not have policy element at all.

thanks

-jason

Sanka Samaranayake wrote:

  
If you want to attach a policy to a particular binding you should do
that in the services.xml as follows.
  
 
  
http://schemas.xmlsoap.org/ws/2004/09/policy">
  
    
    
  
  
   ...  

  
 
  

  
HTH
  
Sanka
 
  
  
  
  
  On Sun, May 4, 2008 at 2:48 PM, jason zhang <[EMAIL PROTECTED]>
wrote:
  Hi, all
I am using axis2 1.4 with rampart 1.4 RC1. My services.xml is like this
--


  
       ...
      
         xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
          xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
          xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
          
      
  


Then I retrieve the generated wsdl from web interface (http://localhost:8080/cmdportal1/services/programws?wsdl)
My wsdl is like this
-


  http://schemas.xmlsoap.org/ws/2004/09/policy"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utilit
y-1.0.xsd" wsu:Id="UToverHTTP">
      ...
  
  programws
  
   ...
 
 


Should the policy element  be the first element of ?

thanks

-jason







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

  
  
  
  
  
-- 
Sanka Samaranayake
WSO2 Inc.
  
  http://sankas.blogspot.com/
  http://www.wso2.org/





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

AW: can I use use rampart with JAX-WS style webservice

[Tezcan.Dilshener.extern]

Hi Alex,
WOW..!!now I copied the policy.xml into axis2.xml config and the whole scenario 
(JAX-WS+Rampart policy) works fine.

As you said it in your mail, since I only have one service running, engaging 
rampart globally in axis2.xml and specifying the policy in there does the trick 
for me.

Cheers
Tezcan


-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Gesendet: Donnerstag, 8. Mai 2008 17:16
An: axis-user@ws.apache.org
Betreff: AW: can I use use rampart with JAX-WS style webservice


Hi Alex,
I have pasted the policy into my wsdl for the time being
and am refering to it in my service using wsdlLocation as shown below. The 
service is deployed in a jar file under WEB-INF\servicejars. 
My client engages the addressing and rampart before calling the service.

If I comment out the  block in my wsdl and engage only 
addressing in my client the whole thing works just fine.

HTH 

cheers
Tezcan


@WebService(endpointInterface = "demo.rampart.policy.sample.SimpleService",
serviceName = "SecuredEcho",
wsdlLocation="WEB-INF/wsdl/SecuredEcho.wsdl"
)

@Addressing(enabled=true, required=true)

public class SimpleServiceImpl implements SimpleService{

public String echo(String arg) {
System.out.println("the server side echo==>"+arg);
return arg;
}
}
-Ursprüngliche Nachricht-
Von: Savitsky, Alex [mailto:[EMAIL PROTECTED] 
Gesendet: Donnerstag, 8. Mai 2008 16:34
An: axis-user@ws.apache.org
Betreff: RE: can I use use rampart with JAX-WS style webservice


Not yet - I see the rampart deployment messages in the server log, and it seem 
to send the "must understand" headers, but no password is either sent or 
checked.

Where did you put your policy? I've placed mine in the axis config itself.

I'll keep you (and everyone here) posted.

HTH,

Alex

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: May 8, 2008 10:05 AM
To: axis-user@ws.apache.org
Subject: AW: can I use use rampart with JAX-WS style webservice

Hi Alex
thnx for the tip but this gives me my original exception "Must Understand check 
failed for headers" found in thread [1].:-( Does this work for you at global 
level?

cheers
Tezcan


[1]http://markmail.org/search/?q=list%3Aorg.apache.ws.axis-user+What+is+%22Must#query:list%3Aorg.apache.ws.axis-user%20What%20is%20%22Must+page:1+mid:jlc64h7qnvsoyfff+state:results

-Ursprüngliche Nachricht-
Von: Savitsky, Alex [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 8. Mai 2008 15:39
An: axis-user@ws.apache.org
Betreff: RE: can I use use rampart with JAX-WS style webservice


Declaring the rampart in axis2.xml global config (and putting the rampart.mar 
in WEB-INF/modules, of course) would engage it globally for all services. If 
you only have one service running, this might be what you need. I haven't found 
a way to engage a module ona per-service basis, though.

HTH,

Alex

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: May 8, 2008 7:43 AM
To: axis-user@ws.apache.org
Subject: AW: can I use use rampart with JAX-WS style webservice

Hi
thanks for your answer.
Unfortunately it does not seem to do the trick.
I am getting the following error.

[ERROR] com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 32 counts of 
IllegalAnnotationExceptions 
org.apache.axiom.attachments.lifecycle.LifecycleManager is an interface, and 
JAXB can't handle interfaces.

I am beginning to think that it is not possible to engage Rampart with 
annotations.

cheers
Tezcan
-Ursprüngliche Nachricht-
Von: Ruchith Fernando [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 6. Mai 2008 09:57
An: axis-user@ws.apache.org
Betreff: Re: can I use use rampart with JAX-WS style webservice


I haven't tried this but I think the following solution will work:

- first implement lifecycle management on the service [1]
- now in the "init" method you can get hold of the AxisService instance and 
then you can engage the rampart module on it.
- Finally you can load the policy from a file as an org.apache.neethi.Policy 
object and add that to the AxisService instance as well.

Now you have a WS-Sec enabled service :-)

HTH

Thanks,
Ruchith

p.s. You can also try WSO2 WSAS [2] and try the WS-Sec support available as 
well!

1. http://ws.apache.org/axis2/1_3/api/org/apache/axis2/service/Lifecycle.html
2. http://wso2.org/downloads/wsas
On Wed, Apr 30, 2008 at 8:39 PM,  <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi
>
> I have a web service developed using jax-ws style annotations. So it
> does not require a services.xml, It is deployed to axis2 as jar file 
> under WEB-INF\servicejars directory.
>
> Now if I want to secure this service using rampart how do I link the
> policy.xml?
>
> Where do I add the stuff such as  that one
> usually adds into services.xml ?
>
>
> cheers
> Tezcan



--
http://blog.ruchith.org
http://wso2.org

-

AW: can I use use rampart with JAX-WS style webservice

[Tezcan.Dilshener.extern]

Hi Alex,
I have pasted the policy into my wsdl for the time being
and am refering to it in my service using wsdlLocation as shown below.
The service is deployed in a jar file under WEB-INF\servicejars. 
My client engages the addressing and rampart before calling the service.

If I comment out the  block in my wsdl and
engage only addressing in my client the whole thing works just fine.

HTH 

cheers
Tezcan


@WebService(endpointInterface = "demo.rampart.policy.sample.SimpleService",
serviceName = "SecuredEcho",
wsdlLocation="WEB-INF/wsdl/SecuredEcho.wsdl"
)

@Addressing(enabled=true, required=true)

public class SimpleServiceImpl implements SimpleService{

public String echo(String arg) {
System.out.println("the server side echo==>"+arg);
return arg;
}
}
-Ursprüngliche Nachricht-
Von: Savitsky, Alex [mailto:[EMAIL PROTECTED] 
Gesendet: Donnerstag, 8. Mai 2008 16:34
An: axis-user@ws.apache.org
Betreff: RE: can I use use rampart with JAX-WS style webservice


Not yet - I see the rampart deployment messages in the server log, and it seem 
to send the "must understand" headers, but no password is either sent or 
checked.

Where did you put your policy? I've placed mine in the axis config itself.

I'll keep you (and everyone here) posted.

HTH,

Alex

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: May 8, 2008 10:05 AM
To: axis-user@ws.apache.org
Subject: AW: can I use use rampart with JAX-WS style webservice

Hi Alex
thnx for the tip but this gives me my original exception "Must Understand check 
failed for headers" found in thread [1].:-( Does this work for you at global 
level?

cheers
Tezcan


[1]http://markmail.org/search/?q=list%3Aorg.apache.ws.axis-user+What+is+%22Must#query:list%3Aorg.apache.ws.axis-user%20What%20is%20%22Must+page:1+mid:jlc64h7qnvsoyfff+state:results

-Ursprüngliche Nachricht-
Von: Savitsky, Alex [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 8. Mai 2008 15:39
An: axis-user@ws.apache.org
Betreff: RE: can I use use rampart with JAX-WS style webservice


Declaring the rampart in axis2.xml global config (and putting the rampart.mar 
in WEB-INF/modules, of course) would engage it globally for all services. If 
you only have one service running, this might be what you need. I haven't found 
a way to engage a module ona per-service basis, though.

HTH,

Alex

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: May 8, 2008 7:43 AM
To: axis-user@ws.apache.org
Subject: AW: can I use use rampart with JAX-WS style webservice

Hi
thanks for your answer.
Unfortunately it does not seem to do the trick.
I am getting the following error.

[ERROR] com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 32 counts of 
IllegalAnnotationExceptions 
org.apache.axiom.attachments.lifecycle.LifecycleManager is an interface, and 
JAXB can't handle interfaces.

I am beginning to think that it is not possible to engage Rampart with 
annotations.

cheers
Tezcan
-Ursprüngliche Nachricht-
Von: Ruchith Fernando [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 6. Mai 2008 09:57
An: axis-user@ws.apache.org
Betreff: Re: can I use use rampart with JAX-WS style webservice


I haven't tried this but I think the following solution will work:

- first implement lifecycle management on the service [1]
- now in the "init" method you can get hold of the AxisService instance and 
then you can engage the rampart module on it.
- Finally you can load the policy from a file as an org.apache.neethi.Policy 
object and add that to the AxisService instance as well.

Now you have a WS-Sec enabled service :-)

HTH

Thanks,
Ruchith

p.s. You can also try WSO2 WSAS [2] and try the WS-Sec support available as 
well!

1. http://ws.apache.org/axis2/1_3/api/org/apache/axis2/service/Lifecycle.html
2. http://wso2.org/downloads/wsas
On Wed, Apr 30, 2008 at 8:39 PM,  <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi
>
> I have a web service developed using jax-ws style annotations. So it 
> does not require a services.xml, It is deployed to axis2 as jar file 
> under WEB-INF\servicejars directory.
>
> Now if I want to secure this service using rampart how do I link the 
> policy.xml?
>
> Where do I add the stuff such as  that one 
> usually adds into services.xml ?
>
>
> cheers
> Tezcan



--
http://blog.ruchith.org
http://wso2.org

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


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



NOTICE OF CONFIDENTIALITY
This communication including any information transmitted with it is intended 
only for the use of the addressees and is confidential. If you are not an 
intended recipient or respo

Re: Problem with engaging security module in Axis2 1.4 version

[Hari Prasad]

Hi Nandana,

As I indicated, I added the rampart jars into the axis2 lib directory and
then I have added all the jars under axis2-1.4/lib directory to the
classpath in the eclispe build path. I Copied the axis2-1.4/conf/axis2.xml
to my source directory and added the lines I have indicated.

Ok. I will download the axis source and try to debug. Btw, what's the actual
deployment procedure for rampart? is the steps i have followed not enough?

Thanks again

Regards
Hari P

On 5/8/08, Nandana Mihindukulasooriya <[EMAIL PROTECTED]> wrote:
>
> Hi Hari,
>
>  There are no compilation errors but when I run the program , I get the
> > same error
> > "org.apache.axis2.AxisFault: The system is attempting to engage a module
> > that is not available: rampart"
> >
>
> The possible reason is Rampart might not have been deployed correctly. Did
> you add all dependency jars to your classpath ? And if you can debug, you
> can check ConfigurationContext ->
> axisConfiguration -> faultyModules to check the reason why it has actually
> failed to deploy.
>
> BTW, Are you using a custom axis2.xml ?
>
> thanks,
> nandana
>
>
> >
> > On 5/8/08, Nandana Mihindukulasooriya <[EMAIL PROTECTED]> wrote:
> > >
> > > Hi Hari,
> > >
> > > > Not knowing what else needs to be done?. I tried using rampart with
> > > > 1.4 It didn't work. Does Rampart
> > > > supported with axis2 1.4?
> > > >
> > >
> > > Yes, you can download Rampart 1.4 RC2 here [1]. Configuration should
> > > be like this.
> > >
> > > 
> > >
> > > 
> > > 
> > > UsernameToken Timestamp
> > > bob
> > >
> > > org.apache.rampart.samples.sample02.PWCBHandler
> > > 
> > > 
> > >
> > > you can find the complete axis2.xml here [2]. You can go through the
> > > samples come with Rampart distribution to get a better understanding.
> > >
> > >
> > > [1] - 
> > > http://people.apache.org/~nandana/rampart-1.4/RC2/dist/
> > > [2] -
> > > http://svn.apache.org/repos/asf/webservices/rampart/trunk/java/modules/rampart-samples/basic/sample02/client.axis2.xml
> > >
> > >
> > > thanks,
> > > nandana
> > >
> > >
> >

Re: Problem with engaging security module in Axis2 1.4 version

[Nandana Mihindukulasooriya]

Hi Hari,

There are no compilation errors but when I run the program , I get the same
> error
> "org.apache.axis2.AxisFault: The system is attempting to engage a module
> that is not available: rampart"
>

The possible reason is Rampart might not have been deployed correctly. Did
you add all dependency jars to your classpath ? And if you can debug, you
can check ConfigurationContext ->
axisConfiguration -> faultyModules to check the reason why it has actually
failed to deploy.

BTW, Are you using a custom axis2.xml ?

thanks,
nandana


>
> On 5/8/08, Nandana Mihindukulasooriya <[EMAIL PROTECTED]> wrote:
> >
> > Hi Hari,
> >
> > > Not knowing what else needs to be done?. I tried using rampart with
> > > 1.4 It didn't work. Does Rampart
> > > supported with axis2 1.4?
> > >
> >
> > Yes, you can download Rampart 1.4 RC2 here [1]. Configuration should be
> > like this.
> >
> > 
> >
> > 
> > 
> > UsernameToken Timestamp
> > bob
> >
> > org.apache.rampart.samples.sample02.PWCBHandler
> > 
> > 
> >
> > you can find the complete axis2.xml here [2]. You can go through the
> > samples come with Rampart distribution to get a better understanding.
> >
> >
> > [1] - 
> > http://people.apache.org/~nandana/rampart-1.4/RC2/dist/
> > [2] -
> > http://svn.apache.org/repos/asf/webservices/rampart/trunk/java/modules/rampart-samples/basic/sample02/client.axis2.xml
> >
> >
> > thanks,
> > nandana
> >
> >
>

Re: Problem with engaging security module in Axis2 1.4 version

[Hari Prasad]

Hi Nandana,

Thanks for your immediate reply. I downloaded the rampart1.4 RC1 & followed
the following steps

1. Copied the rampart jar files into my axis2-1.4/lib directory
2. Copied the .mar files to axis2-1.4/repository/modules directory
3. Added the following lines to my axis2.xml file

 

 
 
 UsernameToken Timestamp
 MIG

 
com.hp.dsl.learning.service.PWCallback
 MIG
 passwordText
   


4. I am building and running the my test program in eclipse. Hence I added
the rampart jar files
   in to the buildpath

There are no compilation errors but when I run the program , I get the same
error
"org.apache.axis2.AxisFault: The system is attempting to engage a module
that is not available: rampart"

So what could be the problem? Am I missing something?

Thanks & Regards
Hari P


On 5/8/08, Nandana Mihindukulasooriya <[EMAIL PROTECTED]> wrote:
>
> Hi Hari,
>
> > Not knowing what else needs to be done?. I tried using rampart with 1.4
> > It didn't work. Does Rampart
> > supported with axis2 1.4?
> >
>
> Yes, you can download Rampart 1.4 RC2 here [1]. Configuration should be
> like this.
>
> 
>
> 
> 
> UsernameToken Timestamp
> bob
>
> org.apache.rampart.samples.sample02.PWCBHandler
> 
> 
>
> you can find the complete axis2.xml here [2]. You can go through the
> samples come with Rampart distribution to get a better understanding.
>
>
> [1] - http://people.apache.org/~nandana/rampart-1.4/RC2/dist/
> [2] -
> http://svn.apache.org/repos/asf/webservices/rampart/trunk/java/modules/rampart-samples/basic/sample02/client.axis2.xml
>
>
> thanks,
> nandana
>
>

Extension Mapper Conflict

[Nick Alex]

I am using xsd2java command for generating standard Java Bean classes from
XML Schema.

I have multiple services and schemas. Some services share common schemas
too.

I want to keep common Java Beans Classes for all in a single jar.

So I used "xsd2java.bat" for all schemas & generating classes in a same
directory and common genearted classes get overwritten.

it also creates Extension Mapper class and same time overwrite it with
Extension Mapper of other schema.

For other classes like Stub, Skeleton, MsgReceiverInOut and others, we are
using wsdl2java utility which creates its own Extension Mapper.

How should we use these Extension Mapper classes (One that created by using
wsdl2java and other created from xsd2java)?

Please suggest.

Or is there some other way to get common Java Beans classes for multiple
services.

--Thanks In Advance

Nick~~

RE: can I use use rampart with JAX-WS style webservice

[Savitsky, Alex]

Not yet - I see the rampart deployment messages in the server log, and it seem 
to send the "must understand" headers, but no password is either sent or 
checked.

Where did you put your policy? I've placed mine in the axis config itself.

I'll keep you (and everyone here) posted.

HTH,

Alex

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: May 8, 2008 10:05 AM
To: axis-user@ws.apache.org
Subject: AW: can I use use rampart with JAX-WS style webservice

Hi Alex
thnx for the tip but this gives me my original exception "Must Understand check 
failed for headers" found in thread [1].:-( Does this work for you at global 
level?

cheers
Tezcan


[1]http://markmail.org/search/?q=list%3Aorg.apache.ws.axis-user+What+is+%22Must#query:list%3Aorg.apache.ws.axis-user%20What%20is%20%22Must+page:1+mid:jlc64h7qnvsoyfff+state:results

-Ursprüngliche Nachricht-
Von: Savitsky, Alex [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 8. Mai 2008 15:39
An: axis-user@ws.apache.org
Betreff: RE: can I use use rampart with JAX-WS style webservice


Declaring the rampart in axis2.xml global config (and putting the rampart.mar 
in WEB-INF/modules, of course) would engage it globally for all services. If 
you only have one service running, this might be what you need. I haven't found 
a way to engage a module ona per-service basis, though.

HTH,

Alex

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: May 8, 2008 7:43 AM
To: axis-user@ws.apache.org
Subject: AW: can I use use rampart with JAX-WS style webservice

Hi
thanks for your answer.
Unfortunately it does not seem to do the trick.
I am getting the following error.

[ERROR] com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 32 counts of 
IllegalAnnotationExceptions 
org.apache.axiom.attachments.lifecycle.LifecycleManager is an interface, and 
JAXB can't handle interfaces.

I am beginning to think that it is not possible to engage Rampart with 
annotations.

cheers
Tezcan
-Ursprüngliche Nachricht-
Von: Ruchith Fernando [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 6. Mai 2008 09:57
An: axis-user@ws.apache.org
Betreff: Re: can I use use rampart with JAX-WS style webservice


I haven't tried this but I think the following solution will work:

- first implement lifecycle management on the service [1]
- now in the "init" method you can get hold of the AxisService instance and 
then you can engage the rampart module on it.
- Finally you can load the policy from a file as an org.apache.neethi.Policy 
object and add that to the AxisService instance as well.

Now you have a WS-Sec enabled service :-)

HTH

Thanks,
Ruchith

p.s. You can also try WSO2 WSAS [2] and try the WS-Sec support available as 
well!

1. http://ws.apache.org/axis2/1_3/api/org/apache/axis2/service/Lifecycle.html
2. http://wso2.org/downloads/wsas
On Wed, Apr 30, 2008 at 8:39 PM,  <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi
>
> I have a web service developed using jax-ws style annotations. So it
> does not require a services.xml, It is deployed to axis2 as jar file
> under WEB-INF\servicejars directory.
>
> Now if I want to secure this service using rampart how do I link the
> policy.xml?
>
> Where do I add the stuff such as  that one
> usually adds into services.xml ?
>
>
> cheers
> Tezcan



--
http://blog.ruchith.org
http://wso2.org

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


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



NOTICE OF CONFIDENTIALITY
This communication including any information transmitted with it is intended 
only for the use of the addressees and is confidential.
If you are not an intended recipient or responsible for delivering the message 
to an intended recipient, any review, disclosure, conversion to hard copy, 
dissemination, reproduction or other use of any part of this communication is 
strictly prohibited, as is the taking or omitting of any action in reliance 
upon this communication.
If you receive this communication in error or without authorization please 
notify us immediately by return e-mail or otherwise and permanently delete the 
entire communication from any computer, disk drive, or other storage medium.

If the above disclaimer is not properly readable, it can be found at 
www.td.com/legal

AVERTISSEMENT DE CONFIDENTIALITE
Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement aux 
destinataires susmentionnés,  est confidentiel.  Si vous n'êtes pas le 
destinataire prévu ou un agent responsable de la livraison de ce courriel, tout 
examen, divulgation, copie, impression, reproduction, distribution, ou autre 
utilisation d'une partie de ce courriel est strictement interdit de même que 
toute intervention ou abstraction à cet égard.  

Re: [Rampart] What is the correct way to secure a JAX-WS service?

[Davanum Srinivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Paul,

No. You can't use a services.xml with JAX-WS.

thanks,
- -- dims

Paul Fremantle wrote:
| Isn't it possible to use a services.xml together with JAX-WS - at
| least to get this working?
|
| Paul
|
| On Thu, May 8, 2008 at 2:59 PM, Nandana Mihindukulasooriya
| <[EMAIL PROTECTED]> wrote:
|> Hi Alex,
|>
|>> especially that it doesn't look like anyone from Axis team has tried this
|>> particular (JAX-WS + Rampart) configuration just yet (I hope the JAX-WS will
|>> be addressed in more details in Rampart 1.4).
|> Yes, it is not in the Road map of Rampart 1.4. Anyway we think this is
|> something we should support. So we will look in to this and try to see if we
|> can find a way to get this working before the Rampart 1.4 release.
|>
|>> Nevertheless, I will continue my investigations, bugs or not. I believe
|>> I'm close...
|> That is great news. Please let us know if you need any information from
|> Rampart side.
|>
|> thanks,
|> nandana
|>
|>> 
|>> From: Nandana Mihindukulasooriya [mailto:[EMAIL PROTECTED]
|>> Sent: May 7, 2008 11:51 PM
|>> To: axis-user@ws.apache.org
|>> Subject: Re: [Rampart] What is the correct way to secure a JAX-WS service?
|>>
|>> Hi Alex,
|>>   Have you looked at  this thread  [1] ?
|>>
|>> thanks,
|>> nandana
|>>
|>> [1] -
|>> 
http://markmail.org/message/dkwjvskrh3gysvnw?q=list:org%2Eapache%2Ews%2Eaxis-user+can+I+use+use+rampart
|>>
|>>
|>> On Wed, May 7, 2008 at 10:26 PM, Savitsky, Alex
|>> <[EMAIL PROTECTED]> wrote:
|>>> Hi,
|>>>
|>>> Usually, Axis2 services are secured using Rampart, by engaging the
|>>> module, and specifying the policy in services.xml. However, this won't do
|>>> for services deployed via JAX-WS annotations, as there's no services.xml
|>>> file there. The module could still be deployed, as long as it's placed in
|>>> WEB-INF/modules - but where would one have to place the policy file, for it
|>>> to be picked up by the Rampart? Are there any annotations one has to 
specify
|>>> on the service endpoint, to specify that the service is using WS-Security?
|>>>
|>>> I looked at the @HandlerCHain annotation, but the Rampart handlers are
|>>> not based on the JAX-WS handler interfaces, but on some internal Axis2 
ones,
|>>> and thus cannot be used in JAX-WS handler chains
|>>>
|>>> And final question - does Rampart even support JAX-WS style services?
|>>>
|>>> Thanks,
|>>>
|>>> Alex
|>>>
|>>> 
|>>> NOTICE OF CONFIDENTIALITY
|>>> This communication including any information transmitted with it is
|>>> intended only for the use of the addressees and is confidential.
|>>> If you are not an intended recipient or responsible for delivering
|>>> the message to an intended recipient, any review, disclosure,
|>>> conversion to hard copy, dissemination, reproduction or other use
|>>> of any part of this communication is strictly prohibited, as is the
|>>> taking or omitting of any action in reliance upon this communication.
|>>> If you receive this communication in error or without authorization
|>>> please notify us immediately by return e-mail or otherwise and
|>>> permanently delete the entire communication from any computer,
|>>> disk drive, or other storage medium.
|>>>
|>>> If the above disclaimer is not properly readable, it can be found at
|>>> www.td.com/legal
|>>>
|>>> AVERTISSEMENT DE CONFIDENTIALITE
|>>> Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement
|>>> aux destinataires susmentionnés,  est confidentiel.  Si vous
|>>> n'êtes pas le destinataire prévu ou un agent responsable de la
|>>> livraison de ce courriel, tout examen, divulgation, copie, impression,
|>>> reproduction, distribution, ou autre utilisation d'une partie de ce
|>>> courriel est strictement interdit de même que toute intervention ou
|>>> abstraction à cet égard.  Si vous avez reçu ce message par erreur ou
|>>> sans autorisation, veuillez en aviser immédiatement l'expéditeur par
|>>> retour de courriel ou par un autre moyen et supprimer immédiatement
|>>> cette communication entière de tout système électronique.
|>>>
|>>> Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous
|>>> pouvez le consulter à www.td.com/francais/legale
|
|
|
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)

iD8DBQFIIw1JgNg6eWEDv1kRAs6kAJ9t8KDRjrDRXl/1sPDLag3Cf/in5QCgoGxo
JK3czxxikJYPSWQSiKvY23I=
=VHFk
-END PGP SIGNATURE-

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

Re: [Rampart] What is the correct way to secure a JAX-WS service?

[Paul Fremantle]

Isn't it possible to use a services.xml together with JAX-WS - at
least to get this working?

Paul

On Thu, May 8, 2008 at 2:59 PM, Nandana Mihindukulasooriya
<[EMAIL PROTECTED]> wrote:
> Hi Alex,
>
>> especially that it doesn't look like anyone from Axis team has tried this
>> particular (JAX-WS + Rampart) configuration just yet (I hope the JAX-WS will
>> be addressed in more details in Rampart 1.4).
>
> Yes, it is not in the Road map of Rampart 1.4. Anyway we think this is
> something we should support. So we will look in to this and try to see if we
> can find a way to get this working before the Rampart 1.4 release.
>
>>
>> Nevertheless, I will continue my investigations, bugs or not. I believe
>> I'm close...
>
> That is great news. Please let us know if you need any information from
> Rampart side.
>
> thanks,
> nandana
>
>> 
>> From: Nandana Mihindukulasooriya [mailto:[EMAIL PROTECTED]
>> Sent: May 7, 2008 11:51 PM
>> To: axis-user@ws.apache.org
>> Subject: Re: [Rampart] What is the correct way to secure a JAX-WS service?
>>
>> Hi Alex,
>>   Have you looked at  this thread  [1] ?
>>
>> thanks,
>> nandana
>>
>> [1] -
>> http://markmail.org/message/dkwjvskrh3gysvnw?q=list:org%2Eapache%2Ews%2Eaxis-user+can+I+use+use+rampart
>>
>>
>> On Wed, May 7, 2008 at 10:26 PM, Savitsky, Alex
>> <[EMAIL PROTECTED]> wrote:
>>>
>>> Hi,
>>>
>>> Usually, Axis2 services are secured using Rampart, by engaging the
>>> module, and specifying the policy in services.xml. However, this won't do
>>> for services deployed via JAX-WS annotations, as there's no services.xml
>>> file there. The module could still be deployed, as long as it's placed in
>>> WEB-INF/modules - but where would one have to place the policy file, for it
>>> to be picked up by the Rampart? Are there any annotations one has to specify
>>> on the service endpoint, to specify that the service is using WS-Security?
>>>
>>> I looked at the @HandlerCHain annotation, but the Rampart handlers are
>>> not based on the JAX-WS handler interfaces, but on some internal Axis2 ones,
>>> and thus cannot be used in JAX-WS handler chains
>>>
>>> And final question - does Rampart even support JAX-WS style services?
>>>
>>> Thanks,
>>>
>>> Alex
>>>
>>> 
>>> NOTICE OF CONFIDENTIALITY
>>> This communication including any information transmitted with it is
>>> intended only for the use of the addressees and is confidential.
>>> If you are not an intended recipient or responsible for delivering
>>> the message to an intended recipient, any review, disclosure,
>>> conversion to hard copy, dissemination, reproduction or other use
>>> of any part of this communication is strictly prohibited, as is the
>>> taking or omitting of any action in reliance upon this communication.
>>> If you receive this communication in error or without authorization
>>> please notify us immediately by return e-mail or otherwise and
>>> permanently delete the entire communication from any computer,
>>> disk drive, or other storage medium.
>>>
>>> If the above disclaimer is not properly readable, it can be found at
>>> www.td.com/legal
>>>
>>> AVERTISSEMENT DE CONFIDENTIALITE
>>> Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement
>>> aux destinataires susmentionnés,  est confidentiel.  Si vous
>>> n'êtes pas le destinataire prévu ou un agent responsable de la
>>> livraison de ce courriel, tout examen, divulgation, copie, impression,
>>> reproduction, distribution, ou autre utilisation d'une partie de ce
>>> courriel est strictement interdit de même que toute intervention ou
>>> abstraction à cet égard.  Si vous avez reçu ce message par erreur ou
>>> sans autorisation, veuillez en aviser immédiatement l'expéditeur par
>>> retour de courriel ou par un autre moyen et supprimer immédiatement
>>> cette communication entière de tout système électronique.
>>>
>>> Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous
>>> pouvez le consulter à www.td.com/francais/legale



-- 
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair

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

"Oxygenating the Web Service Platform", www.wso2.com

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

RE: WSDL2Java in Axis1.4 code generation errors.

[Krystian Szczesny]

XmlSchema libraries have changed in 1.4 release to a snapshot version.

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: 08 May 2008 15:08
To: axis-user@ws.apache.org
Cc: axis-user@ws.apache.org
Subject: RE: WSDL2Java in Axis1.4 code generation errors.

 


Ok, this for Axis 1.4 version though

Regards, 
Aravind R Yarram
email: [EMAIL PROTECTED]  



"Krystian Szczesny" <[EMAIL PROTECTED]> 

05/08/2008 10:02 AM

Please respond to
axis-user@ws.apache.org

To



cc


Subject

RE: WSDL2Java in Axis1.4 code generation errors.

 






Hi guys,
 
Actually I think it’s less Axis2 issue and more XmlSchema ws commons project 
issue.
I have created a bug report in jira: 
https://issues.apache.org/jira/browse/WSCOMMONS-342 
 
I suggest you start debugging and see where it takes you.
 
Best regards,
Krystian
 
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: 08 May 2008 14:38
To: axis-user@ws.apache.org
Cc: axis-user@ws.apache.org
Subject: Re: WSDL2Java in Axis1.4 code generation errors.
 

Hi, i am also facing the same kind of issuesi havent got any help so far!

Regards, 
Aravind R Yarram

<[EMAIL PROTECTED]>

05/08/2008 05:09 AM

 

Please respond to
axis-user@ws.apache.org

 

To



cc


Subject

WSDL2Java in Axis1.4 code generation errors.


 

 








Hello all, 

In the past with axis upto 1.2, I have used the bundled wsdl2java tool with a 
lot of confidence. 
Recently however, I have discovered some code generation errors when using the 
tool. 
For instance, a Class X was generated such that: 
public class ListOfIDXRefDataTypeIdXRefAppInstanceAppID  implements 
java.io.Serializable, org.apache.axis.encoding.SimpleType.

This class had the following constructor, generated: 
public ListOfIDXRefDataTypeIdXRefAppInstanceAppID(org.apache.axis.types.Token 
_value) { 
  super(_value);
  } 

As you can see from the Class declaration, it does not extend any other class 
(other than java.lang.Object by default). Hence compilation of this class fails 
because Object(value) is not present and super(value) is illegal. 

Has anyone else come across similar or same errors? Is there a resolution for 
these errors, other than modifying the classes oneself. 

Please advise. 

Thanks 

Cheers 
Gautham Kasinath 

Gautham KASINATH

HBF/Ajilon 
William Street
Perth
Phone: +61 8 9214 6754


===
HBF Health Funds Inc ARBN 126 884 786 incorporated in Western Australia
is a Private Health Insurer under the Private Health Insurance Act 2007.
The liability of its constitutional members is limited; HBF Insurance 
Pty Ltd ABN 11 009 268 277; HBF Financial Services Pty Ltd 
ABN 18 009 123 675. The information contained in this email and any 
attachment is intended solely for the named recipients. It may contain 
material or information that is confidential and/or legally privileged 
material. It is also subject to copyright. If you are not the intended 
recipient please advise us immediately by return email or contact a 
Member Service Advisor on 133 423 and delete the email and any 
attachments. Any use or disclosure of the contents of either is 
unauthorised and may be unlawful. Any personal information in this email
must be handled in accordance with the Privacy Act 1988 (Cth). The views
expressed in this email are those of the author and do not represent 
those of HBF unless clearly indicated.
===




This message contains information from Equifax Inc. which may be confidential 
and privileged. If you are not an intended recipient, please refrain from any 
disclosure, copying, distribution or use of this information and note that such 
actions are prohibited. If you have received this transmission in error, please 
notify by e-mail [EMAIL PROTECTED]
--

This e-mail and any attachments are confidential and may also be legally 
privileged and/or copyright material of Intec Telecom Systems PLC (or its 
affiliated companies). If you are not an intended or authorised recipient 
of this e-mail or have received it in error, please delete it immediately 
and notify the sender by e-mail. In such a case, reading, reproducing, 
printing or further dissemination of this e-mail or its contents is strictly 
prohibited and may be unlawful. 
Intec Telecom Systems PLC does not represent or warrant that an attachment 
hereto is free from computer viruses or other defects. The opinions 
expressed in this e-mail and any attachments may be those of the author and 
are not necessarily those of Intec Telecom Systems PLC.

This message contains information from Equifax Inc. which may be confidential 
and privileged. If you are not an intended recipient, please refrain from any 
disclosure, copying, distribution or use of this information and note that such 
actions are proh

RE: WSDL2Java in Axis1.4 code generation errors.

[Aravind . Yarram]

Ok, this for Axis 1.4 version though

Regards, 
Aravind R Yarram
email: [EMAIL PROTECTED] 



"Krystian Szczesny" <[EMAIL PROTECTED]> 
05/08/2008 10:02 AM
Please respond to
axis-user@ws.apache.org


To

cc

Subject
RE: WSDL2Java in Axis1.4 code generation errors.






Hi guys,
 
Actually I think it’s less Axis2 issue and more XmlSchema ws commons 
project issue.
I have created a bug report in jira: 
https://issues.apache.org/jira/browse/WSCOMMONS-342
I suggest you start debugging and see where it takes you.
 
Best regards,
Krystian
 
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: 08 May 2008 14:38
To: axis-user@ws.apache.org
Cc: axis-user@ws.apache.org
Subject: Re: WSDL2Java in Axis1.4 code generation errors.
 

Hi, i am also facing the same kind of issuesi havent got any help so 
far!

Regards, 
Aravind R Yarram


<[EMAIL PROTECTED]>
05/08/2008 05:09 AM


Please respond to
axis-user@ws.apache.org



To

cc

Subject
WSDL2Java in Axis1.4 code generation errors.
 









Hello all, 

In the past with axis upto 1.2, I have used the bundled wsdl2java tool 
with a lot of confidence. 
Recently however, I have discovered some code generation errors when using 
the tool. 
For instance, a Class X was generated such that: 
public class ListOfIDXRefDataTypeIdXRefAppInstanceAppID  implements 
java.io.Serializable, org.apache.axis.encoding.SimpleType.

This class had the following constructor, generated: 
public 
ListOfIDXRefDataTypeIdXRefAppInstanceAppID(org.apache.axis.types.Token 
_value) { 
   super(_value); 
   } 

As you can see from the Class declaration, it does not extend any other 
class (other than java.lang.Object by default). Hence compilation of this 
class fails because Object(value) is not present and super(value) is 
illegal. 

Has anyone else come across similar or same errors? Is there a resolution 
for these errors, other than modifying the classes oneself. 

Please advise. 

Thanks 

Cheers 
Gautham Kasinath 

Gautham KASINATH

HBF/Ajilon 
William Street
Perth
Phone: +61 8 9214 6754


===
HBF Health Funds Inc ARBN 126 884 786 incorporated in Western Australia
is a Private Health Insurer under the Private Health Insurance Act 2007.
The liability of its constitutional members is limited; HBF Insurance 
Pty Ltd ABN 11 009 268 277; HBF Financial Services Pty Ltd 
ABN 18 009 123 675. The information contained in this email and any 
attachment is intended solely for the named recipients. It may contain 
material or information that is confidential and/or legally privileged 
material. It is also subject to copyright. If you are not the intended 
recipient please advise us immediately by return email or contact a 
Member Service Advisor on 133 423 and delete the email and any 
attachments. Any use or disclosure of the contents of either is 
unauthorised and may be unlawful. Any personal information in this email
must be handled in accordance with the Privacy Act 1988 (Cth). The views
expressed in this email are those of the author and do not represent 
those of HBF unless clearly indicated.
===


This message contains information from Equifax Inc. which may be 
confidential and privileged. If you are not an intended recipient, please 
refrain from any disclosure, copying, distribution or use of this 
information and note that such actions are prohibited. If you have 
received this transmission in error, please notify by e-mail 
[EMAIL PROTECTED]
--
This e-mail and any attachments are confidential and may also be legally 
privileged and/or copyright material of Intec Telecom Systems PLC (or its 
affiliated companies). If you are not an intended or authorised recipient 
of this e-mail or have received it in error, please delete it immediately 
and notify the sender by e-mail. In such a case, reading, reproducing, 
printing or further dissemination of this e-mail or its contents is 
strictly 
prohibited and may be unlawful. 
Intec Telecom Systems PLC does not represent or warrant that an attachment 

hereto is free from computer viruses or other defects. The opinions 
expressed in this e-mail and any attachments may be those of the author 
and 
are not necessarily those of Intec Telecom Systems PLC.

This message contains information from Equifax Inc. which may be confidential 
and privileged.  If you are not an intended recipient, please refrain from any 
disclosure, copying, distribution or use of this information and note that such 
actions are prohibited.  If you have received this transmission in error, 
please notify by e-mail [EMAIL PROTECTED]
--

AW: can I use use rampart with JAX-WS style webservice

[Tezcan.Dilshener.extern]

Hi Alex
thnx for the tip but this gives me my original exception "Must Understand check 
failed for headers" found in thread [1].:-(
Does this work for you at global level?

cheers
Tezcan


[1]http://markmail.org/search/?q=list%3Aorg.apache.ws.axis-user+What+is+%22Must#query:list%3Aorg.apache.ws.axis-user%20What%20is%20%22Must+page:1+mid:jlc64h7qnvsoyfff+state:results

-Ursprüngliche Nachricht-
Von: Savitsky, Alex [mailto:[EMAIL PROTECTED] 
Gesendet: Donnerstag, 8. Mai 2008 15:39
An: axis-user@ws.apache.org
Betreff: RE: can I use use rampart with JAX-WS style webservice


Declaring the rampart in axis2.xml global config (and putting the rampart.mar 
in WEB-INF/modules, of course) would engage it globally for all services. If 
you only have one service running, this might be what you need. I haven't found 
a way to engage a module ona per-service basis, though.

HTH,

Alex

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: May 8, 2008 7:43 AM
To: axis-user@ws.apache.org
Subject: AW: can I use use rampart with JAX-WS style webservice

Hi
thanks for your answer.
Unfortunately it does not seem to do the trick.
I am getting the following error.

[ERROR] com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 32 counts of 
IllegalAnnotationExceptions 
org.apache.axiom.attachments.lifecycle.LifecycleManager is an interface, and 
JAXB can't handle interfaces.

I am beginning to think that it is not possible to engage Rampart with 
annotations.

cheers
Tezcan
-Ursprüngliche Nachricht-
Von: Ruchith Fernando [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 6. Mai 2008 09:57
An: axis-user@ws.apache.org
Betreff: Re: can I use use rampart with JAX-WS style webservice


I haven't tried this but I think the following solution will work:

- first implement lifecycle management on the service [1]
- now in the "init" method you can get hold of the AxisService instance and 
then you can engage the rampart module on it.
- Finally you can load the policy from a file as an org.apache.neethi.Policy 
object and add that to the AxisService instance as well.

Now you have a WS-Sec enabled service :-)

HTH

Thanks,
Ruchith

p.s. You can also try WSO2 WSAS [2] and try the WS-Sec support available as 
well!

1. http://ws.apache.org/axis2/1_3/api/org/apache/axis2/service/Lifecycle.html
2. http://wso2.org/downloads/wsas
On Wed, Apr 30, 2008 at 8:39 PM,  <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi
>
> I have a web service developed using jax-ws style annotations. So it 
> does not require a services.xml, It is deployed to axis2 as jar file 
> under WEB-INF\servicejars directory.
>
> Now if I want to secure this service using rampart how do I link the 
> policy.xml?
>
> Where do I add the stuff such as  that one 
> usually adds into services.xml ?
>
>
> cheers
> Tezcan



--
http://blog.ruchith.org
http://wso2.org

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


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



NOTICE OF CONFIDENTIALITY
This communication including any information transmitted with it is 
intended only for the use of the addressees and is confidential. 
If you are not an intended recipient or responsible for delivering 
the message to an intended recipient, any review, disclosure, 
conversion to hard copy, dissemination, reproduction or other use 
of any part of this communication is strictly prohibited, as is the 
taking or omitting of any action in reliance upon this communication. 
If you receive this communication in error or without authorization 
please notify us immediately by return e-mail or otherwise and 
permanently delete the entire communication from any computer, 
disk drive, or other storage medium.

If the above disclaimer is not properly readable, it can be found at 
www.td.com/legal
   
AVERTISSEMENT DE CONFIDENTIALITE   
Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement 
aux destinataires susmentionnés,  est confidentiel.  Si vous 
n'êtes pas le destinataire prévu ou un agent responsable de la 
livraison de ce courriel, tout examen, divulgation, copie, impression, 
reproduction, distribution, ou autre utilisation d'une partie de ce 
courriel est strictement interdit de même que toute intervention ou 
abstraction à cet égard.  Si vous avez reçu ce message par erreur ou 
sans autorisation, veuillez en aviser immédiatement l'expéditeur par 
retour de courriel ou par un autre moyen et supprimer immédiatement 
cette communication entière de tout système électronique.

Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous 
pouvez le consulter à www.td.com/francais/legale

---

RE: WSDL2Java in Axis1.4 code generation errors.

[Krystian Szczesny]

Hi guys,

 

Actually I think it's less Axis2 issue and more XmlSchema ws commons
project issue.

I have created a bug report in jira:
https://issues.apache.org/jira/browse/WSCOMMONS-342

I suggest you start debugging and see where it takes you.

 

Best regards,

Krystian

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: 08 May 2008 14:38
To: axis-user@ws.apache.org
Cc: axis-user@ws.apache.org
Subject: Re: WSDL2Java in Axis1.4 code generation errors.

 


Hi, i am also facing the same kind of issuesi havent got any help so
far!

Regards, 
Aravind R Yarram



<[EMAIL PROTECTED]>

05/08/2008 05:09 AM

Please respond to
axis-user@ws.apache.org

To



cc


Subject

WSDL2Java in Axis1.4 code generation errors.

 







Hello all, 

In the past with axis upto 1.2, I have used the bundled wsdl2java tool
with a lot of confidence. 
Recently however, I have discovered some code generation errors when
using the tool. 
For instance, a Class X was generated such that: 
public class ListOfIDXRefDataTypeIdXRefAppInstanceAppID  implements
java.io.Serializable, org.apache.axis.encoding.SimpleType.

This class had the following constructor, generated: 
public
ListOfIDXRefDataTypeIdXRefAppInstanceAppID(org.apache.axis.types.Token
_value) { 
   super(_value); 
   } 

As you can see from the Class declaration, it does not extend any other
class (other than java.lang.Object by default). Hence compilation of
this class fails because Object(value) is not present and super(value)
is illegal. 

Has anyone else come across similar or same errors? Is there a
resolution for these errors, other than modifying the classes oneself. 

Please advise. 

Thanks 

Cheers 
Gautham Kasinath 

Gautham KASINATH

HBF/Ajilon 
William Street
Perth
Phone: +61 8 9214 6754


===
HBF Health Funds Inc ARBN 126 884 786 incorporated in Western Australia
is a Private Health Insurer under the Private Health Insurance Act 2007.
The liability of its constitutional members is limited; HBF Insurance 
Pty Ltd ABN 11 009 268 277; HBF Financial Services Pty Ltd 
ABN 18 009 123 675. The information contained in this email and any 
attachment is intended solely for the named recipients. It may contain 
material or information that is confidential and/or legally privileged 
material. It is also subject to copyright. If you are not the intended 
recipient please advise us immediately by return email or contact a 
Member Service Advisor on 133 423 and delete the email and any 
attachments. Any use or disclosure of the contents of either is 
unauthorised and may be unlawful. Any personal information in this email
must be handled in accordance with the Privacy Act 1988 (Cth). The views
expressed in this email are those of the author and do not represent 
those of HBF unless clearly indicated.
===



This message contains information from Equifax Inc. which may be
confidential and privileged. If you are not an intended recipient,
please refrain from any disclosure, copying, distribution or use of this
information and note that such actions are prohibited. If you have
received this transmission in error, please notify by e-mail
[EMAIL PROTECTED]
--
This e-mail and any attachments are confidential and may also be legally 
privileged and/or copyright material of Intec Telecom Systems PLC (or its 
affiliated companies).  If you are not an intended or authorised recipient 
of this e-mail or have received it in error, please delete it immediately 
and notify the sender by e-mail. In such a case, reading, reproducing, 
printing or further dissemination of this e-mail or its contents is strictly 
prohibited and may be unlawful. 
Intec Telecom Systems PLC does not represent or warrant that an attachment 
hereto is free from computer viruses or other defects. The opinions 
expressed in this e-mail and any attachments may be those of the author and 
are not necessarily those of Intec Telecom Systems PLC.

Re: [Rampart] What is the correct way to secure a JAX-WS service?

[Nandana Mihindukulasooriya]

Hi Alex,

especially that it doesn't look like anyone from Axis team has tried this
> particular (JAX-WS + Rampart) configuration just yet (I hope the JAX-WS will
> be addressed in more details in Rampart 1.4).
>

Yes, it is not in the Road map of Rampart 1.4. Anyway we think this is
something we should support. So we will look in to this and try to see if we
can find a way to get this working before the Rampart 1.4 release.


>  Nevertheless, I will continue my investigations, bugs or not. I believe
> I'm close...
>

That is great news. Please let us know if you need any information from
Rampart side.

thanks,
nandana

 --
> *From:* Nandana Mihindukulasooriya [mailto:[EMAIL PROTECTED]
> *Sent:* May 7, 2008 11:51 PM
> *To:* axis-user@ws.apache.org
> *Subject:* Re: [Rampart] What is the correct way to secure a JAX-WS
> service?
>
> Hi Alex,
>   Have you looked at  this thread  [1] ?
>
> thanks,
> nandana
>
> [1] -
> http://markmail.org/message/dkwjvskrh3gysvnw?q=list:org%2Eapache%2Ews%2Eaxis-user+can+I+use+use+rampart
>
>
> On Wed, May 7, 2008 at 10:26 PM, Savitsky, Alex <
> [EMAIL PROTECTED]> wrote:
>
>>  Hi,
>>
>> Usually, Axis2 services are secured using Rampart, by engaging the module,
>> and specifying the policy in services.xml. However, this won't do for
>> services deployed via JAX-WS annotations, as there's no services.xml file
>> there. The module could still be deployed, as long as it's placed in
>> WEB-INF/modules - but where would one have to place the policy file, for it
>> to be picked up by the Rampart? Are there any annotations one has to specify
>> on the service endpoint, to specify that the service is using WS-Security?
>>
>> I looked at the @HandlerCHain annotation, but the Rampart handlers are not
>> based on the JAX-WS handler interfaces, but on some internal Axis2 ones, and
>> thus cannot be used in JAX-WS handler chains
>>
>> And final question - does Rampart even support JAX-WS style services?
>>
>> Thanks,
>>
>> Alex
>>
>> 
>> NOTICE OF CONFIDENTIALITY
>> This communication including any information transmitted with it is
>> intended only for the use of the addressees and is confidential.
>> If you are not an intended recipient or responsible for delivering
>> the message to an intended recipient, any review, disclosure,
>> conversion to hard copy, dissemination, reproduction or other use
>> of any part of this communication is strictly prohibited, as is the
>> taking or omitting of any action in reliance upon this communication.
>> If you receive this communication in error or without authorization
>> please notify us immediately by return e-mail or otherwise and
>> permanently delete the entire communication from any computer,
>> disk drive, or other storage medium.
>>
>> If the above disclaimer is not properly readable, it can be found at 
>> www.td.com/legal
>>
>> AVERTISSEMENT DE CONFIDENTIALITE
>> Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement
>> aux destinataires susmentionnés,  est confidentiel.  Si vous
>> n'êtes pas le destinataire prévu ou un agent responsable de la
>> livraison de ce courriel, tout examen, divulgation, copie, impression,
>> reproduction, distribution, ou autre utilisation d'une partie de ce
>> courriel est strictement interdit de même que toute intervention ou
>> abstraction à cet égard.  Si vous avez reçu ce message par erreur ou
>> sans autorisation, veuillez en aviser immédiatement l'expéditeur par
>> retour de courriel ou par un autre moyen et supprimer immédiatement
>> cette communication entière de tout système électronique.
>>
>> Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous
>> pouvez le consulter à www.td.com/francais/legale
>>
>>

RE: can I use use rampart with JAX-WS style webservice

[Savitsky, Alex]

Declaring the rampart in axis2.xml global config (and putting the rampart.mar 
in WEB-INF/modules, of course) would engage it globally for all services. If 
you only have one service running, this might be what you need. I haven't found 
a way to engage a module ona per-service basis, though.

HTH,

Alex

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: May 8, 2008 7:43 AM
To: axis-user@ws.apache.org
Subject: AW: can I use use rampart with JAX-WS style webservice

Hi
thanks for your answer.
Unfortunately it does not seem to do the trick.
I am getting the following error.

[ERROR] com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 32 counts of 
IllegalAnnotationExceptions 
org.apache.axiom.attachments.lifecycle.LifecycleManager is an interface, and 
JAXB can't handle interfaces.

I am beginning to think that it is not possible to engage Rampart with 
annotations.

cheers
Tezcan
-Ursprüngliche Nachricht-
Von: Ruchith Fernando [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 6. Mai 2008 09:57
An: axis-user@ws.apache.org
Betreff: Re: can I use use rampart with JAX-WS style webservice


I haven't tried this but I think the following solution will work:

- first implement lifecycle management on the service [1]
- now in the "init" method you can get hold of the AxisService instance and 
then you can engage the rampart module on it.
- Finally you can load the policy from a file as an org.apache.neethi.Policy 
object and add that to the AxisService instance as well.

Now you have a WS-Sec enabled service :-)

HTH

Thanks,
Ruchith

p.s. You can also try WSO2 WSAS [2] and try the WS-Sec support available as 
well!

1. http://ws.apache.org/axis2/1_3/api/org/apache/axis2/service/Lifecycle.html
2. http://wso2.org/downloads/wsas
On Wed, Apr 30, 2008 at 8:39 PM,  <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi
>
> I have a web service developed using jax-ws style annotations. So it
> does not require a services.xml, It is deployed to axis2 as jar file
> under WEB-INF\servicejars directory.
>
> Now if I want to secure this service using rampart how do I link the
> policy.xml?
>
> Where do I add the stuff such as  that one
> usually adds into services.xml ?
>
>
> cheers
> Tezcan



--
http://blog.ruchith.org
http://wso2.org

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


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



NOTICE OF CONFIDENTIALITY
This communication including any information transmitted with it is 
intended only for the use of the addressees and is confidential. 
If you are not an intended recipient or responsible for delivering 
the message to an intended recipient, any review, disclosure, 
conversion to hard copy, dissemination, reproduction or other use 
of any part of this communication is strictly prohibited, as is the 
taking or omitting of any action in reliance upon this communication. 
If you receive this communication in error or without authorization 
please notify us immediately by return e-mail or otherwise and 
permanently delete the entire communication from any computer, 
disk drive, or other storage medium.

If the above disclaimer is not properly readable, it can be found at 
www.td.com/legal
   
AVERTISSEMENT DE CONFIDENTIALITE   
Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement 
aux destinataires susmentionnés,  est confidentiel.  Si vous 
n’êtes pas le destinataire prévu ou un agent responsable de la 
livraison de ce courriel, tout examen, divulgation, copie, impression, 
reproduction, distribution, ou autre utilisation d’une partie de ce 
courriel est strictement interdit de même que toute intervention ou 
abstraction à cet égard.  Si vous avez reçu ce message par erreur ou 
sans autorisation, veuillez en aviser immédiatement l’expéditeur par 
retour de courriel ou par un autre moyen et supprimer immédiatement 
cette communication entière de tout système électronique.

Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous 
pouvez le consulter à www.td.com/francais/legale

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

Re: WSDL2Java in Axis1.4 code generation errors.

[Aravind . Yarram]

Hi, i am also facing the same kind of issuesi havent got any help so 
far!

Regards, 
Aravind R Yarram



<[EMAIL PROTECTED]> 
05/08/2008 05:09 AM
Please respond to
axis-user@ws.apache.org


To

cc

Subject
WSDL2Java in Axis1.4 code generation errors.







Hello all, 

In the past with axis upto 1.2, I have used the bundled wsdl2java tool 
with a lot of confidence. 
Recently however, I have discovered some code generation errors when using 
the tool. 
For instance, a Class X was generated such that: 
public class ListOfIDXRefDataTypeIdXRefAppInstanceAppID  implements 
java.io.Serializable, org.apache.axis.encoding.SimpleType. 

This class had the following constructor, generated: 
public 
ListOfIDXRefDataTypeIdXRefAppInstanceAppID(org.apache.axis.types.Token 
_value) { 
super(_value); 
} 

As you can see from the Class declaration, it does not extend any other 
class (other than java.lang.Object by default). Hence compilation of this 
class fails because Object(value) is not present and super(value) is 
illegal. 

Has anyone else come across similar or same errors? Is there a resolution 
for these errors, other than modifying the classes oneself. 

Please advise. 

Thanks 

Cheers 
Gautham Kasinath 

Gautham KASINATH

HBF/Ajilon 
William Street
Perth
Phone: +61 8 9214 6754


===
HBF Health Funds Inc ARBN 126 884 786 incorporated in Western Australia
is a Private Health Insurer under the Private Health Insurance Act 2007.
The liability of its constitutional members is limited; HBF Insurance 
Pty Ltd ABN 11 009 268 277; HBF Financial Services Pty Ltd 
ABN 18 009 123 675. The information contained in this email and any 
attachment is intended solely for the named recipients. It may contain 
material or information that is confidential and/or legally privileged 
material. It is also subject to copyright. If you are not the intended 
recipient please advise us immediately by return email or contact a 
Member Service Advisor on 133 423 and delete the email and any 
attachments. Any use or disclosure of the contents of either is 
unauthorised and may be unlawful. Any personal information in this email
must be handled in accordance with the Privacy Act 1988 (Cth). The views
expressed in this email are those of the author and do not represent 
those of HBF unless clearly indicated.
===


This message contains information from Equifax Inc. which may be confidential 
and privileged.  If you are not an intended recipient, please refrain from any 
disclosure, copying, distribution or use of this information and note that such 
actions are prohibited.  If you have received this transmission in error, 
please notify by e-mail [EMAIL PROTECTED]
--

RE: [Rampart] What is the correct way to secure a JAX-WS service?

[Savitsky, Alex]

Tezcan,

It will be helpful if you could share the work on this subject you've done so 
far. What approaches have you tried? What were the roadblocks? Meanwhile, I'm 
going to continue my attempts, and will definitely share the results once there 
are some :)

Thanks,

Alex

P.S. I don't think the approach at [1] works at all...


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: May 8, 2008 8:30 AM
To: axis-user@ws.apache.org
Cc: Savitsky, Alex
Subject: AW: [Rampart] What is the correct way to secure a JAX-WS service?

Hi Alex
since for a long time I am trying to get the rampart to engage in my jax-ws 
service without any success.
I am begining to think that rampart is not so far to be used in jax-ws style 
webservices.
Anyway, if you get it to work, this way or with the way that it was mentioned 
to me at [1], please let me know.
I will stop my trials and tribulations with axis2 / rampart here for now and 
look into CXF.

Cheers
Tezcan
-Ursprüngliche Nachricht-
Von: Nandana Mihindukulasooriya [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 8. Mai 2008 05:51
An: axis-user@ws.apache.org
Betreff: Re: [Rampart] What is the correct way to secure a JAX-WS service?

Hi Alex,
  Have you looked at  this thread  [1] ?

thanks,
nandana

[1] -  
http://markmail.org/message/dkwjvskrh3gysvnw?q=list:org%2Eapache%2Ews%2Eaxis-user+can+I+use+use+rampart


On Wed, May 7, 2008 at 10:26 PM, Savitsky, Alex <[EMAIL 
PROTECTED]> wrote:
Hi,

Usually, Axis2 services are secured using Rampart, by engaging the module, and 
specifying the policy in services.xml. However, this won't do for services 
deployed via JAX-WS annotations, as there's no services.xml file there. The 
module could still be deployed, as long as it's placed in WEB-INF/modules - but 
where would one have to place the policy file, for it to be picked up by the 
Rampart? Are there any annotations one has to specify on the service endpoint, 
to specify that the service is using WS-Security?

I looked at the @HandlerCHain annotation, but the Rampart handlers are not 
based on the JAX-WS handler interfaces, but on some internal Axis2 ones, and 
thus cannot be used in JAX-WS handler chains

And final question - does Rampart even support JAX-WS style services?

Thanks,

Alex


NOTICE OF CONFIDENTIALITY
This communication including any information transmitted with it is
intended only for the use of the addressees and is confidential.
If you are not an intended recipient or responsible for delivering
the message to an intended recipient, any review, disclosure,
conversion to hard copy, dissemination, reproduction or other use
of any part of this communication is strictly prohibited, as is the
taking or omitting of any action in reliance upon this communication.
If you receive this communication in error or without authorization
please notify us immediately by return e-mail or otherwise and
permanently delete the entire communication from any computer,
disk drive, or other storage medium.

If the above disclaimer is not properly readable, it can be found at
www.td.com/legal

AVERTISSEMENT DE CONFIDENTIALITE
Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement
aux destinataires susmentionnés,  est confidentiel.  Si vous
n'êtes pas le destinataire prévu ou un agent responsable de la
livraison de ce courriel, tout examen, divulgation, copie, impression,
reproduction, distribution, ou autre utilisation d'une partie de ce
courriel est strictement interdit de même que toute intervention ou
abstraction à cet égard.  Si vous avez reçu ce message par erreur ou
sans autorisation, veuillez en aviser immédiatement l'expéditeur par
retour de courriel ou par un autre moyen et supprimer immédiatement
cette communication entière de tout système électronique.

Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous
pouvez le consulter à 
www.td.com/francais/legale

RE: [Rampart] What is the correct way to secure a JAX-WS service?

[Savitsky, Alex]

Hi Nandana,

Yes, I looked at this thread, and it's confusing, at best. I can deploy the 
rampart module all right (one doesn't need the Lifecycle for that, just drop 
rampart.mar in the WEB-INF/modules), but the problem is - it doesn't load the 
policy (specified in the axis2.xml, as there's no other place to put it, 
really). Looking at the source code, it seems that the policyInclude that was 
used to hold the policy in 1.3, was deprecated in 1.4 in favor of policySubject 
- but there's no consensus between the Axis classes on which one to use. The 
policy is correctly loaded into the AxisConfiguration's policySubject property 
at Axis startup (verified via debugger), but the subsequent service loading 
(via JAXWSDeployer) doesn't seem to care about the policySubject, using the 
deprecated policyInclude instead. I suspect this is a bug, especially that it 
doesn't look like anyone from Axis team has tried this particular (JAX-WS + 
Rampart) configuration just yet (I hope the JAX-WS will be addressed in more 
details in Rampart 1.4).

Nevertheless, I will continue my investigations, bugs or not. I believe I'm 
close...

Regards,

Alex


From: Nandana Mihindukulasooriya [mailto:[EMAIL PROTECTED]
Sent: May 7, 2008 11:51 PM
To: axis-user@ws.apache.org
Subject: Re: [Rampart] What is the correct way to secure a JAX-WS service?

Hi Alex,
  Have you looked at  this thread  [1] ?

thanks,
nandana

[1] -  
http://markmail.org/message/dkwjvskrh3gysvnw?q=list:org%2Eapache%2Ews%2Eaxis-user+can+I+use+use+rampart


On Wed, May 7, 2008 at 10:26 PM, Savitsky, Alex <[EMAIL 
PROTECTED]> wrote:
Hi,

Usually, Axis2 services are secured using Rampart, by engaging the module, and 
specifying the policy in services.xml. However, this won't do for services 
deployed via JAX-WS annotations, as there's no services.xml file there. The 
module could still be deployed, as long as it's placed in WEB-INF/modules - but 
where would one have to place the policy file, for it to be picked up by the 
Rampart? Are there any annotations one has to specify on the service endpoint, 
to specify that the service is using WS-Security?

I looked at the @HandlerCHain annotation, but the Rampart handlers are not 
based on the JAX-WS handler interfaces, but on some internal Axis2 ones, and 
thus cannot be used in JAX-WS handler chains

And final question - does Rampart even support JAX-WS style services?

Thanks,

Alex


NOTICE OF CONFIDENTIALITY
This communication including any information transmitted with it is
intended only for the use of the addressees and is confidential.
If you are not an intended recipient or responsible for delivering
the message to an intended recipient, any review, disclosure,
conversion to hard copy, dissemination, reproduction or other use
of any part of this communication is strictly prohibited, as is the
taking or omitting of any action in reliance upon this communication.
If you receive this communication in error or without authorization
please notify us immediately by return e-mail or otherwise and
permanently delete the entire communication from any computer,
disk drive, or other storage medium.

If the above disclaimer is not properly readable, it can be found at
www.td.com/legal

AVERTISSEMENT DE CONFIDENTIALITE
Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement
aux destinataires susmentionnés,  est confidentiel.  Si vous
n'êtes pas le destinataire prévu ou un agent responsable de la
livraison de ce courriel, tout examen, divulgation, copie, impression,
reproduction, distribution, ou autre utilisation d'une partie de ce
courriel est strictement interdit de même que toute intervention ou
abstraction à cet égard.  Si vous avez reçu ce message par erreur ou
sans autorisation, veuillez en aviser immédiatement l'expéditeur par
retour de courriel ou par un autre moyen et supprimer immédiatement
cette communication entière de tout système électronique.

Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous
pouvez le consulter à 
www.td.com/francais/legale

AW: [Rampart] What is the correct way to secure a JAX-WS service?

[Tezcan.Dilshener.extern]

Hi Alex
since for a long time I am trying to get the rampart to engage in my jax-ws 
service without any success. 
I am begining to think that rampart is not so far to be used in jax-ws style 
webservices.
Anyway, if you get it to work, this way or with the way that it was mentioned 
to me at [1], please let me know.
I will stop my trials and tribulations with axis2 / rampart here for now and 
look into CXF.
 
Cheers
Tezcan

-Ursprüngliche Nachricht-
Von: Nandana Mihindukulasooriya [mailto:[EMAIL PROTECTED] 
Gesendet: Donnerstag, 8. Mai 2008 05:51
An: axis-user@ws.apache.org
Betreff: Re: [Rampart] What is the correct way to secure a JAX-WS 
service?


Hi Alex,
  Have you looked at  this thread  [1] ?

thanks,
nandana

[1] -  
http://markmail.org/message/dkwjvskrh3gysvnw?q=list:org%2Eapache%2Ews%2Eaxis-user+can+I+use+use+rampart



On Wed, May 7, 2008 at 10:26 PM, Savitsky, Alex <[EMAIL PROTECTED]> 
wrote:


Hi,
 
Usually, Axis2 services are secured using Rampart, by engaging 
the module, and specifying the policy in services.xml. However, this won't do 
for services deployed via JAX-WS annotations, as there's no services.xml file 
there. The module could still be deployed, as long as it's placed in 
WEB-INF/modules - but where would one have to place the policy file, for it to 
be picked up by the Rampart? Are there any annotations one has to specify on 
the service endpoint, to specify that the service is using WS-Security?
 
I looked at the @HandlerCHain annotation, but the Rampart 
handlers are not based on the JAX-WS handler interfaces, but on some internal 
Axis2 ones, and thus cannot be used in JAX-WS handler chains
 
And final question - does Rampart even support JAX-WS style 
services?
 
Thanks,
 
Alex

NOTICE OF CONFIDENTIALITY
This communication including any information transmitted with 
it is 
intended only for the use of the addressees and is 
confidential. 
If you are not an intended recipient or responsible for 
delivering 
the message to an intended recipient, any review, disclosure, 
conversion to hard copy, dissemination, reproduction or other 
use 
of any part of this communication is strictly prohibited, as is 
the 
taking or omitting of any action in reliance upon this 
communication. 
If you receive this communication in error or without 
authorization 
please notify us immediately by return e-mail or otherwise and 
permanently delete the entire communication from any computer, 
disk drive, or other storage medium.

If the above disclaimer is not properly readable, it can be 
found at 
www.td.com/legal
   
AVERTISSEMENT DE CONFIDENTIALITE   
Ce courriel, ainsi que tout renseignement ci-inclus, destiné 
uniquement 
aux destinataires susmentionnés,  est confidentiel.  Si vous 
n'êtes pas le destinataire prévu ou un agent responsable de la 
livraison de ce courriel, tout examen, divulgation, copie, 
impression, 
reproduction, distribution, ou autre utilisation d'une partie 
de ce 
courriel est strictement interdit de même que toute 
intervention ou 
abstraction à cet égard.  Si vous avez reçu ce message par 
erreur ou 
sans autorisation, veuillez en aviser immédiatement 
l'expéditeur par 
retour de courriel ou par un autre moyen et supprimer 
immédiatement 
cette communication entière de tout système électronique.

Si l'avis de non-responsabilité ci-dessus n'est pas lisible, 
vous 
pouvez le consulter à www.td.com/francais/legale

AW: What is "Must Understand check failed for headers" error?

[Tezcan.Dilshener.extern]

Hi Nandana
thanks for your quick response.
I was affraid of this answer because it is exactly where I am having 
difficulties at.
My service is developed with JAX-WS style annotations.
I can engage addressing using the @Addressing tag but I fail to see how I can 
engage the rampart.
Any ideas on that?
Is rampart so far to be used within JAX-WS?
 
cheers
Tezcan
 

-Ursprüngliche Nachricht-
Von: Nandana Mihindukulasooriya [mailto:[EMAIL PROTECTED] 
Gesendet: Donnerstag, 8. Mai 2008 13:42
An: axis-user@ws.apache.org
Betreff: Re: What is "Must Understand check failed for headers" error?


Hi, 
Have you correctly engaged Rampart to the service ? It seems that 
service receives a SOAP message with a security header and security header is 
not processed.  To process this header you must have Rampart module engaged to 
the service. 

thanks,
nandana
  

On Thu, May 8, 2008 at 4:53 PM, <[EMAIL PROTECTED]> wrote:


Hi # 
my service is issuing the following error that I do not 
understand why. 
Can someone assist me regarding why and how to resolve this 
please? 

cheers 
Tezcan 
[ERROR] Must Understand check failed for headers: 
{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security
 

 

org.apache.axis2.AxisFault: Must Understand check failed for 
headers: 
{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security
 

 

at 
org.apache.axis2.jaxws.handler.HandlerUtils.checkMustUnderstand(HandlerUtils.java:157)
 
at 
org.apache.axis2.jaxws.server.EndpointController.handleRequest(EndpointController.java:256)
 
at 
org.apache.axis2.jaxws.server.EndpointController.invoke(EndpointController.java:97)
 
at 
org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessageReceiver.java:171)
 
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:131) 
at 
javax.servlet.http.HttpServlet.service(HttpServlet.java:709) 
at 
javax.servlet.http.HttpServlet.service(HttpServlet.java:802) 
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
 
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
 
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
 
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
 
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) 
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) 
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
 
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) 
at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825) 
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:738)
 
at 
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:526)
 
at 
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
 
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
 
at java.lang.Thread.run(Thread.java:595) 

AW: can I use use rampart with JAX-WS style webservice

[Tezcan.Dilshener.extern]

Hi
thanks for your answer.
Unfortunately it does not seem to do the trick.
I am getting the following error.

[ERROR] com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 32 counts of 
IllegalAnnotationExceptions
org.apache.axiom.attachments.lifecycle.LifecycleManager is an interface, and 
JAXB can't handle interfaces. 

I am beginning to think that it is not possible to engage Rampart with 
annotations.

cheers
Tezcan
-Ursprüngliche Nachricht-
Von: Ruchith Fernando [mailto:[EMAIL PROTECTED] 
Gesendet: Dienstag, 6. Mai 2008 09:57
An: axis-user@ws.apache.org
Betreff: Re: can I use use rampart with JAX-WS style webservice


I haven't tried this but I think the following solution will work:

- first implement lifecycle management on the service [1]
- now in the "init" method you can get hold of the AxisService instance and 
then you can engage the rampart module on it.
- Finally you can load the policy from a file as an org.apache.neethi.Policy 
object and add that to the AxisService instance as well.

Now you have a WS-Sec enabled service :-)

HTH

Thanks,
Ruchith

p.s. You can also try WSO2 WSAS [2] and try the WS-Sec support available as 
well!

1. http://ws.apache.org/axis2/1_3/api/org/apache/axis2/service/Lifecycle.html
2. http://wso2.org/downloads/wsas
On Wed, Apr 30, 2008 at 8:39 PM,  <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi
>
> I have a web service developed using jax-ws style annotations. So it 
> does not require a services.xml, It is deployed to axis2 as jar file 
> under WEB-INF\servicejars directory.
>
> Now if I want to secure this service using rampart how do I link the 
> policy.xml?
>
> Where do I add the stuff such as  that one 
> usually adds into services.xml ?
>
>
> cheers
> Tezcan



-- 
http://blog.ruchith.org
http://wso2.org

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


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

Re: What is "Must Understand check failed for headers" error?

[Nandana Mihindukulasooriya]

Hi,
Have you correctly engaged Rampart to the service ? It seems that
service receives a SOAP message with a security header and security header
is not processed.  To process this header you must have Rampart module
engaged to the service.

thanks,
nandana

On Thu, May 8, 2008 at 4:53 PM, <[EMAIL PROTECTED]> wrote:

>  Hi #
> my service is issuing the following error that I do not understand why.
> Can someone assist me regarding why and how to resolve this please?
>
> cheers
> Tezcan
> [ERROR] Must Understand check failed for headers: {***
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security
> *
>
> org.apache.axis2.AxisFault: Must Understand check failed for headers: {***
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security
> *
>
> at
> org.apache.axis2.jaxws.handler.HandlerUtils.checkMustUnderstand(*
> HandlerUtils.java:157*)
> at org.apache.axis2.jaxws.server.EndpointController.handleRequest(
> *EndpointController.java:256*)
> at org.apache.axis2.jaxws.server.EndpointController.invoke(*
> EndpointController.java:97*)
> at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(*
> JAXWSMessageReceiver.java:171*)
> 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:131*)
> at javax.servlet.http.HttpServlet.service(*HttpServlet.java:709*)
> at javax.servlet.http.HttpServlet.service(*HttpServlet.java:802*)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(*
> ApplicationFilterChain.java:252*)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(*
> ApplicationFilterChain.java:173*)
> at org.apache.catalina.core.StandardWrapperValve.invoke(*
> StandardWrapperValve.java:214*)
> at org.apache.catalina.core.StandardContextValve.invoke(*
> StandardContextValve.java:178*)
> at org.apache.catalina.core.StandardHostValve.invoke(*
> StandardHostValve.java:126*)
> at org.apache.catalina.valves.ErrorReportValve.invoke(*
> ErrorReportValve.java:105*)
> at org.apache.catalina.core.StandardEngineValve.invoke(*
> StandardEngineValve.java:107*)
> at org.apache.catalina.connector.CoyoteAdapter.service(*
> CoyoteAdapter.java:148*)
> at org.apache.coyote.http11.Http11Processor.process(*
> Http11Processor.java:825*)
> at
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(
> *Http11Protocol.java:738*)
> at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(*
> PoolTcpEndpoint.java:526*)
> at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(*
> LeaderFollowerWorkerThread.java:80*)
> at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(*
> ThreadPool.java:684*)
> at java.lang.Thread.run(*Thread.java:595*)
>

What is "Must Understand check failed for headers" error?

[Tezcan.Dilshener.extern]

Hi #
my service is issuing the following error that I do not understand why.
Can someone assist me regarding why and how to resolve this please?

cheers
Tezcan
[ERROR] Must Understand check failed for headers:
{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-sece
xt-1.0.xsd}Security
org.apache.axis2.AxisFault: Must Understand check failed for headers:
{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-sece
xt-1.0.xsd}Security
at
org.apache.axis2.jaxws.handler.HandlerUtils.checkMustUnderstand(HandlerU
tils.java:157)
at
org.apache.axis2.jaxws.server.EndpointController.handleRequest(EndpointC
ontroller.java:256)
at
org.apache.axis2.jaxws.server.EndpointController.invoke(EndpointControll
er.java:97)
at
org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessageR
eceiver.java:171)
at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostReques
t(HTTPTransportUtils.java:275)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:131)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:214)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:178)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:1
48)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:82
5)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC
onnection(Http11Protocol.java:738)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint
.java:526)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollow
erWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
.java:684)
at java.lang.Thread.run(Thread.java:595)

RE: WSDL2Java Exception

[fadila.mumbasic]

Hi Keith,

here is the wsdl created by axis:

   
- http://schemas.xmlsoap.org/wsdl/";
xmlns:ns4="http://bank.ws.uniserv";
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/";
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/";
xmlns:ns0="http://bank.ws.uniserv/xsd"; xmlns:ns1="http://ws.uniserv/xsd";
xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl";
xmlns:ns3="http://io.java/xsd"; xmlns:ns2="http://rmi.java/xsd";
xmlns:xs="http://www.w3.org/2001/XMLSchema";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
targetNamespace="http://bank.ws.uniserv";>
  BankValidator 
- 
- http://bank.ws.uniserv/xsd";
attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://bank.ws.uniserv/xsd";>
- 
- 
   
   
   
   
   
   
  
  
- 
- 
   
   
   
   
   
   
  
  
- 
- 
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
  
  
  
- http://ws.uniserv/xsd";
attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://ws.uniserv/xsd";>
- 
- 
   
   
  
  
  
- http://rmi.java/xsd";
attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://rmi.java/xsd";>
- 
- 
- 
- 
   
   
   
  
  
  
  
  
- http://io.java/xsd";
attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://io.java/xsd";>
- 
- 
- 
   
  
  
  
  
- http://bank.ws.uniserv";
attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://bank.ws.uniserv";>
- 
- 
   
  
  
- 
- 
- 
   
  
  
  
- 
- 
- 
   
   
   
  
  
  
- 
- 
- 
   
  
  
  
  
  
- 
   
  
- 
   
  
- 
   
  
- 
- 
   
   
   
  
  
- 
  http://schemas.xmlsoap.org/soap/http";
style="document" /> 
- 
   
- 
   
  
- 
   
  
- 
   
  
  
  
- 
  http://schemas.xmlsoap.org/soap/http";
style="document" /> 
- 
   
- 
   
  
- 
   
  
- 
   
  
  
  
- 
   
- 
   
- 
   
  
- 
   
  
  
  
- 
- 
  http://linux/axis2/services/BankValidator"; /> 
  
- 
  http://linux/axis2/services/BankValidator";
/> 
  
- 
  http://linux/axis2/services/BankValidator"; /> 
  
  
   


Thanks,
Fadila

 
-Original Message-
From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 07, 2008 5:32 PM
To: axis-user@ws.apache.org
Subject: Re: WSDL2Java Exception

Hi Fadila,

Would it be possible for you to post your WSDL and schema here please.
That'll make it easy for us to help you out.  And which axis version is
your server using?

Thanks,
Keith.


On Wed, May 7, 2008 at 5:02 PM, <[EMAIL PROTECTED]> wrote:



Hi,

I'm using axis2 1.3. I've deployed a new webservice and I can
see it in
the list of deployed services.
I would like to generate the client stub using the wsdl created
by axis.

But whenn I call WSDL2Java the following exception is thrown:

 [java] org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException
[java] at

org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:180)
[java] at
org.apache.tools.ant.taskdefs.Java.run(Java.java:710)
...
 [java] Caused by:
org.apache.axis2.schema.SchemaCompilationException:
Missing name attribute! Please check your schema!
[java] at

org.apache.axis2.schema.SchemaCompiler.process(SchemaCompiler.java:2089)
[java] at

org.apache.axis2.schema.SchemaCompiler.processParticle(SchemaCompiler.ja
va:1788)
[java] at

org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompiler
.java:977)
[java] at

org.apache.axis2.schema.SchemaCompiler.processAnonymousComplexSchemaType
(SchemaCompiler.java:886)
[java] at

org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java
:867)

I'm a bit confused because the wsdl is created by axis.

Any help is welcome!

Thanks,
Fadila


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






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

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

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

Re: Problem with engaging security module in Axis2 1.4 version

[Nandana Mihindukulasooriya]

Hi Hari,

> Not knowing what else needs to be done?. I tried using rampart with 1.4 It
> didn't work. Does Rampart
> supported with axis2 1.4?
>

Yes, you can download Rampart 1.4 RC2 here [1]. Configuration should be like
this.





UsernameToken Timestamp
bob

org.apache.rampart.samples.sample02.PWCBHandler



you can find the complete axis2.xml here [2]. You can go through the samples
come with Rampart distribution to get a better understanding.


[1] - http://people.apache.org/~nandana/rampart-1.4/RC2/dist/
[2] -
http://svn.apache.org/repos/asf/webservices/rampart/trunk/java/modules/rampart-samples/basic/sample02/client.axis2.xml


thanks,
nandana

Problem with engaging security module in Axis2 1.4 version

[Hari Prasad]

Hi,

I am trying to run a Sample test to connect to one of our webservices using
axis2 1.4 version generated
client. The wbeservice requires the security headers to be sent. But
whaterver I do, I am getting the following error

org.apache.axis2.AxisFault: The system is attempting to engage a module that
is not available: security

I added the following to the axis2.xml :



 
  
   UsernameToken Timestamp
   MIG
   
com.hp.dsl.learning.service.PWCallback
   MIG
   passwordText
  
 


Not knowing what else needs to be done?. I tried using rampart with 1.4 It
didn't work. Does Rampart

supported with axis2 1.4?

I am trying to create the configContext like this

ConfigurationContext ctx *=* ConfigurationContextFactory*.**
createConfigurationContextFromFileSystem**(*
"C:/Installations/axis2-1.4/repository/"*,* "C:/StarTeam
Projects/KIM-PORTAL/View/ATHP_PORTAL_MIG2/LEARNING/src/axis2.xml"*);*

*Could any on throw some light on this?*

*Thanks In Advance*

*Regards*

*Hari P
*

WSDL2Java in Axis1.4 code generation errors.

[Gautham.Kasinath]

Hello all, 

In the past with axis upto 1.2, I have used the bundled wsdl2java tool 
with a lot of confidence. 
Recently however, I have discovered some code generation errors when using 
the tool. 
For instance, a Class X was generated such that: 
public class ListOfIDXRefDataTypeIdXRefAppInstanceAppID  implements 
java.io.Serializable, org.apache.axis.encoding.SimpleType.

This class had the following constructor, generated: 
public 
ListOfIDXRefDataTypeIdXRefAppInstanceAppID(org.apache.axis.types.Token 
_value) {
super(_value);
}

As you can see from the Class declaration, it does not extend any other 
class (other than java.lang.Object by default). Hence compilation of this 
class fails because Object(value) is not present and super(value) is 
illegal. 

Has anyone else come across similar or same errors? Is there a resolution 
for these errors, other than modifying the classes oneself. 

Please advise. 

Thanks

Cheers
Gautham Kasinath

Gautham KASINATH

HBF/Ajilon 
William Street
Perth
Phone: +61 8 9214 6754
===
HBF Health Funds Inc ARBN 126 884 786 incorporated in Western Australia
is a Private Health Insurer under the Private Health Insurance Act 2007.
The liability of its constitutional members is limited; HBF Insurance 
Pty Ltd ABN 11 009 268 277; HBF Financial Services Pty Ltd 
ABN 18 009 123 675. The information contained in this email and any 
attachment is intended solely for the named recipients. It may contain 
material or information that is confidential and/or legally privileged 
material. It is also subject to copyright. If you are not the intended 
recipient please advise us immediately by return email or contact a 
Member Service Advisor on 133 423 and delete the email and any 
attachments. Any use or disclosure of the contents of either is 
unauthorised and may be unlawful. Any personal information in this email
must be handled in accordance with the Privacy Act 1988 (Cth). The views
expressed in this email are those of the author and do not represent 
those of HBF unless clearly indicated.
===

RE: Axis 2 1.4 Version

[Johan Östrand XX]

It has been availabe since may 2 /Johan



From: Nick Alex [mailto:[EMAIL PROTECTED] 
Sent: den 8 maj 2008 10:55
To: axis-user@ws.apache.org
Subject: Axis 2 1.4 Version


Can anybody tell,
when axis2 Version 1.4 will be available

--Cheers
Nick

Axis2 sources in Eclipse

[Krystian Szczesny]

Hi,

 

Anyone knows how to load axis2 sources to Eclipse properly?

I've done like it's written on the webpage - mvn eclipse:eclipse and set
classpath variable.

But when I load the projects I get lots of errors like:

Project X is missing required source folders [that's not a problem, I
can create them]

Project X is missing required Java project: 'axis2' [what??]

Project 'Axis2-CodegenWizard' is missing required library:
'lib/[EMAIL PROTECTED]@.jar' [how to fix that??]

Unbound classpath variable: 'M2_REPO/antlr/antlr/2.7.7/antlr-2.7.7.jar'
in project 'axis2-corba' [file does exist in that location]

 

Some help would be appreciated,

 

-- 

Krystian Szczesny
This e-mail and any attachments are confidential and may also be legally 
privileged and/or copyright material of Intec Telecom Systems PLC (or its 
affiliated companies).  If you are not an intended or authorised recipient 
of this e-mail or have received it in error, please delete it immediately 
and notify the sender by e-mail. In such a case, reading, reproducing, 
printing or further dissemination of this e-mail or its contents is strictly 
prohibited and may be unlawful. 
Intec Telecom Systems PLC does not represent or warrant that an attachment 
hereto is free from computer viruses or other defects. The opinions 
expressed in this e-mail and any attachments may be those of the author and 
are not necessarily those of Intec Telecom Systems PLC.

Axis 2 1.4 Version

[Nick Alex]

Can anybody tell,
when axis2 Version 1.4 will be available

--Cheers
Nick

Re: axis2 1.4 incorrect wsdl with policy

[Sanka Samaranayake]

If you want to attach a policy to a particular binding you should do that in
the services.xml as follows.



http://schemas.xmlsoap.org/ws/2004/09/policy";>
  


  

   ...   

 



HTH

Sanka





On Sun, May 4, 2008 at 2:48 PM, jason zhang <[EMAIL PROTECTED]>
wrote:

> Hi, all
> I am using axis2 1.4 with rampart 1.4 RC1. My services.xml is like this
> --
> 
> 
>   
>...
> xmlns:wsu="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
> "
>   xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy";
>   xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>
>   
>   
>   
> 
>
> Then I retrieve the generated wsdl from web interface (
> http://localhost:8080/cmdportal1/services/programws?wsdl)
> My wsdl is like this
> -
> 
> 
>   http://schemas.xmlsoap.org/ws/2004/09/policy";
> xmlns:wsu="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utilit
> y-1.0.xsd" wsu:Id="UToverHTTP">
>   ...
>   
>   programws
>   
>...
>  
>  
> 
>
> Should the policy element  be the first element of ?
>
> thanks
>
> -jason
>
>
>
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Sanka Samaranayake
WSO2 Inc.

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

RE: Sharing data among services in same service group.

[Subhro Moitra (smoitra)]

stub1 = new
MultiPortTypes1Stub("http://localhost:8080/axis2/services/MultiPortTypes
1");
 
stub1._getServiceClient().getOptions().setProperty(org.apache.axis2.tran
sport.http.HTTPConstants.REUSE_HTTP_CLIENT,new Boolean(true));
 
stub1._getServiceClient().getOptions().setProperty(org.apache.axis2.tran
sport.http.HTTPConstants.SO_TIMEOUT /* CONNECTION_TIMEOUT */,new
Integer("720")); // 2hr for now.
 
stub1._getServiceClient().getOptions().setTimeOutInMilliSeconds(720L
);
  stub1._getServiceClient().getOptions().setManageSession(true);
  
  
  stub2 = new
MultiPortTypes2Stub("http://localhost:8080/axis2/services/MultiPortTypes
2");
 
stub2._getServiceClient().getOptions().setProperty(org.apache.axis2.tran
sport.http.HTTPConstants.REUSE_HTTP_CLIENT,new Boolean(true));
 
stub2._getServiceClient().getOptions().setProperty(org.apache.axis2.tran
sport.http.HTTPConstants.SO_TIMEOUT /* CONNECTION_TIMEOUT */,new
Integer("720")); // 2hr for now.
 
stub2._getServiceClient().getOptions().setTimeOutInMilliSeconds(720L
);
  stub2._getServiceClient().getOptions().setManageSession(true);
 
The browser is returning some "XML Parsing error" not only for this
service but all other services as well.
Is something wrong with the axis installation?
 
Thanks,
Subhro.



From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 08, 2008 1:15 PM
To: axis-user@ws.apache.org
Subject: Re: Sharing data among services in same service group.


How is your client implemented? as I said before transport sessions uses
the HTTPSession to maintain state. So unless your client is using the
same HTTPSessions this will not work. Try invoking the two services via
a browser.

Thanks,
Keith.


On Thu, May 8, 2008 at 12:21 PM, Subhro Moitra (smoitra)
<[EMAIL PROTECTED]> wrote:


Thanks Keith For replying.
I did what you said. Both the scopes are "transportsession".
 
But still the stub2.newOperation1() call is returning null.
 
Please help!!
 
Thanks,
Subhro.



From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 07, 2008 8:54 PM
To: axis-user@ws.apache.org
Subject: Re: Sharing data among services in same service group.


Hi,

I think the problem here is that the two services are in two
scopes. When transport session is used its the underlying transport that
depends how the session is managed. For e.g when http is used the
HTTPSession is used to manage the session. Can you try deploying both
services on the same scope, then this should work.

Thanks,
Keith.


On Wed, May 7, 2008 at 7:18 PM, Subhro Moitra (smoitra)
<[EMAIL PROTECTED]> wrote:


 
Hi All,
 
I have the following services.xml
 



http://www.w3.org/ns/wsdl/in-out";
class="com.xx..z.service.xmlbeans.MultiPortTypes2Message
ReceiverInOut"/>

com.xx..z.service.xmlbeans.MultiPort
Types2Skeleton
service



http://www.w3.org/ns/wsdl/in-out";
class="com.xx..z.service.xmlbeans.MultiPortTypes1Message
ReceiverInOut"/>

com.xx..z.service.xmlbeans.MultiPort
Types1Skeleton
service


 

How can i share data between "MultiPortTypes1" and
"MultiPortTypes2"?
 

In MultiPortTypes1 we have an operation with the below
code.
MessageContext
mc=MessageContext.getCurrentMessageContext();
 if(mc!=null){
  ServiceGroupContext
sgc=mc.getServiceGroupContext();
  if(sgc!=null)sgc.setProperty("sessionId",
"10");
  else System.out.println("\t\t SGC is null cannot
set sesionId");
  
  SessionContext sc=mc.getSessionContext();
  if(sc!=null) sc.setProperty("sessionId",
"sessiontransport");
  else System.out.println("\t\t session context is
null cannot set sessionId");
  
 }
 
In MultiPortTypes2 we have an operation with the below
code:
 
MessageContext
mc=MessageContext.getCurrentMessageContext();
 if(mc!=null){
  System.out.println("\t\t MCCtx:
"+mc.getProperty("sessionId"));
  ServiceGroupContext
sgc=mc.getServiceGroupContext(

RE: How to write a non axis2 client

[Narula, Manish]

I am using the RPCServiceClient which is an implementation of axis2. Is
there any other way out where I can invoke the service independent of
axis2.

 

  

RPCServiceClient serviceClient = new RPCServiceClient();



Options options = serviceClient.getOptions();

 

EndpointReference targetEPR 

= new EndpointReference(

 
"http://localhost:/axis2/services/WeatherSpringService";); 



options.setTo(targetEPR);

 

Regards,

Manish Narula



From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 08, 2008 1:21 PM
To: axis-user@ws.apache.org
Subject: Re: How to write a non axis2 client

 

If you like to try and invoke this service using JavaScript you can try
out the WSO2 Mashup Server [1] which is released under Apache License.
It can generate a JavaScript stub for you or you can invoke your service
directly using a built in JavaScript Object which is called WSRequest.

[1] http://wso2.org/projects/mashup

Thanks,
Keith.

On Thu, May 8, 2008 at 12:25 PM, Narula, Manish <[EMAIL PROTECTED]>
wrote:

Hi,

I used a sample given by axis2 to write a webservice called
pojospringguide. The aar file is deployed, now I want to invoke the web
service using non axis2 client. 

 

Regards,

Manish Narula

 



This message and any attachments are intended only for the use of the
addressee and may contain information that is privileged and
confidential. If the reader of the message is not the intended recipient
or an authorized representative of the intended recipient, you are
hereby notified that any dissemination of this communication is strictly
prohibited. If you have received this communication in error, notify the
sender immediately by return email and delete the message and any
attachments from your system. 




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

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




-
This message and any attachments are intended only for the use of
the addressee and may contain information that is privileged and
confidential. If the reader of the message is not the intended
recipient or an authorized representative of the intended
recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this
communication in error, notify the sender immediately by return
email and delete the message and any attachments from your system.

Re: How to write a non axis2 client

[keith chapman]

If you like to try and invoke this service using JavaScript you can try out
the WSO2 Mashup Server [1] which is released under Apache License. It can
generate a JavaScript stub for you or you can invoke your service directly
using a built in JavaScript Object which is called WSRequest.

[1] http://wso2.org/projects/mashup

Thanks,
Keith.

On Thu, May 8, 2008 at 12:25 PM, Narula, Manish <[EMAIL PROTECTED]>
wrote:

>  Hi,
>
> I used a sample given by axis2 to write a webservice called
> pojospringguide. The aar file is deployed, now I want to invoke the web
> service using non axis2 client.
>
>
>
> Regards,
>
> Manish Narula
>
>
>
> --
>
> * This message and any attachments are intended only for the use of the
> addressee and may contain information that is privileged and confidential.
> If the reader of the message is not the intended recipient or an authorized
> representative of the intended recipient, you are hereby notified that any
> dissemination of this communication is strictly prohibited. If you have
> received this communication in error, notify the sender immediately by
> return email and delete the message and any attachments from your system.
> *
>



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

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

Re: Sharing data among services in same service group.

[keith chapman]

How is your client implemented? as I said before transport sessions uses the
HTTPSession to maintain state. So unless your client is using the same
HTTPSessions this will not work. Try invoking the two services via a
browser.

Thanks,
Keith.

On Thu, May 8, 2008 at 12:21 PM, Subhro Moitra (smoitra) <[EMAIL PROTECTED]>
wrote:

>  Thanks Keith For replying.
> I did what you said. Both the scopes are "transportsession".
>
> But still the stub2.newOperation1() call is returning null.
>
> Please help!!
>
> Thanks,
> Subhro.
>
>  --
> *From:* keith chapman [mailto:[EMAIL PROTECTED]
> *Sent:* Wednesday, May 07, 2008 8:54 PM
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Sharing data among services in same service group.
>
> Hi,
>
> I think the problem here is that the two services are in two scopes. When
> transport session is used its the underlying transport that depends how the
> session is managed. For e.g when http is used the HTTPSession is used to
> manage the session. Can you try deploying both services on the same scope,
> then this should work.
>
> Thanks,
> Keith.
>
> On Wed, May 7, 2008 at 7:18 PM, Subhro Moitra (smoitra) <[EMAIL PROTECTED]>
> wrote:
>
> >
> >  Hi All,
> >
> > I have the following services.xml
> >
> > 
> >  > class="com.xx..z.service.xmlbeans.MultiPortTypes2Skeleton">
> > 
> > http://www.w3.org/ns/wsdl/in-out";
> > class="com.xx..z.service.xmlbeans.MultiPortTypes2MessageReceiverInOut"/>
> > 
> >  > name="ServiceClass">com.xx..z.service.xmlbeans.MultiPortTypes2Skeleton
> > service
> > 
> >  > class="com.xx..z.service.xmlbeans.MultiPortTypes1Skeleton">
> > 
> > http://www.w3.org/ns/wsdl/in-out";
> > class="com.xx..z.service.xmlbeans.MultiPortTypes1MessageReceiverInOut"/>
> > 
> >  > name="ServiceClass">com.xx..z.service.xmlbeans.MultiPortTypes1Skeleton
> > service
> > 
> > 
> >
> >
> > How can i share data between "MultiPortTypes1" and "MultiPortTypes2"?
> >
> >
> > In MultiPortTypes1 we have an operation with the below code.
> > MessageContext mc=MessageContext.getCurrentMessageContext();
> >  if(mc!=null){
> >   ServiceGroupContext sgc=mc.getServiceGroupContext();
> >   if(sgc!=null)sgc.setProperty("sessionId", "10");
> >   else System.out.println("\t\t SGC is null cannot set sesionId");
> >
> >   SessionContext sc=mc.getSessionContext();
> >   if(sc!=null) sc.setProperty("sessionId", "sessiontransport");
> >   else System.out.println("\t\t session context is null cannot set
> > sessionId");
> >
> >  }
> >
> > In MultiPortTypes2 we have an operation with the below code:
> >
> > MessageContext mc=MessageContext.getCurrentMessageContext();
> >  if(mc!=null){
> >   System.out.println("\t\t MCCtx: "+mc.getProperty("sessionId"));
> >   ServiceGroupContext sgc=mc.getServiceGroupContext();
> >   if(sgc!=null) System.out.println(" \t\t ServiceGroupContext:
> > "+sgc.getProperty("sessionId"));
> >   else System.out.println("\t\t SGC is null");
> >
> >   SessionContext sc=mc.getSessionContext();
> >   if(sc!=null) System.out.println("\t\t sessionContext:
> > "+sc.getProperty("sessionId"));
> >   else System.out.println("\t\t session context is null cannot set
> > sessionId");
> >
> >  }
> >
> > The output for "MultiPortTypes2 " is null. Please help.
> >
> > Thanks,
> > Subhro.
> >
>
>
>
> --
> 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