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: [email protected] > 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: [email protected] > 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 <module ref="rampart"> 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] > >
