Hi Ruchith,

In the axis2.xml I have default configuration: First I have transport phase, 
with the URI Based dispatcher and SOAPAction Based dispatcher. The next phase 
is security and then are Predispatch and Dispatch phases. Is this correct or 
should I change it??

Whenever I engage rampart per operation in services.xml I receive this 
exception:

org.apache.axis2.AxisFault: java.util.MissingResourceException: Can't find 
resource for bundle org.apache.axis2.i18n.ProjectResourceBundle, key 
spec.FAULT_ACTION_NOT_SUPPORTED_REASON
    
           at 
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:178)
   
 
           at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
 
   
           at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
 
   
           at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    
           at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    
           at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:228)
    
           at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
    
           at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
    
           at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
    
           at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    
           at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:216)
    
           at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
 
   
           at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:634)
    
           at 
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:445)
    
           at java.lang.Thread.run(Unknown Source)
           
Caused by: java.util.MissingResourceException: Can't find resource for bundle 
org.apache.axis2.i18n.ProjectResourceBundle, key 
spec.FAULT_ACTION_NOT_SUPPORTED_REASON
    
        at java.util.ResourceBundle.getObject(Unknown Source)
    
        at java.util.ResourceBundle.getString(Unknown Source)
    
        at 
org.apache.axis2.i18n.MessageBundle.getMessage(MessageBundle.java:191)
    
        at 
org.apache.axis2.i18n.MessageBundle.getMessage(MessageBundle.java:80)
    
        at 
org.apache.axis2.addressing.i18n.AddressingMessages.getMessage(AddressingMessages.java:61)
    
        at 
org.apache.axis2.addressing.AddressingFaultsHelper.triggerActionNotSupportedFault(AddressingFaultsHelper.java:317)
    
        at 
org.apache.axis2.handlers.addressing.AddressingValidationHandler.checkAction(AddressingValidationHandler.java:137)
    
        at 
org.apache.axis2.handlers.addressing.AddressingValidationHandler.invoke(AddressingValidationHandler.java:50)
    
        at org.apache.axis2.engine.Phase.invoke(Phase.java:383)
    
        at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203)
  
  
        at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:131)
 
   
        at 
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:279)
    
        at 
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:116)
   
 
        ... 14 more



I receive the same exception when the services.xml is not well formed but in 
this case I verified it and everything seems to be ok. The problem dissapear if 
I engage module for the service. I put this on one operation:

<operation name="validateSystem" mep="http://www.w3.org/ns/wsdl/in-out";>
            <module ref="rampart"/>
            <parameter name="InflowSecurity">
                <action>
                    <items>Timestamp Signature Encrypt</items>
                    
<passwordCallbackClass>medici_link.service.PWCBHandler</passwordCallbackClass>
                    
<signaturePropFile>medici-link-cert.properties</signaturePropFile>
                </action>
            </parameter>
            <parameter name="OutflowSecurity">
                <action>
                    <items>Timestamp Encrypt Signature</items>
                    <encryptionUser>useReqSigCert</encryptionUser>
                    <user>medici-link</user>
                    
<signaturePropFile>medici-link-cert.properties</signaturePropFile>
                    
<passwordCallbackClass>medici_link.service.PWCBHandler</passwordCallbackClass>
                    
<signatureParts>{Element}{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd}Timestamp</signatureParts>
                </action>
            </parameter>
            <actionMapping>urn:validateSystem</actionMapping>
            <outputActionMapping>urn:validateSystem</outputActionMapping>
            <faultActionMapping 
faultName="ValidationFault">http://service.medici_link/Medici_LinkPortType/validateSystem/Fault/ValidationFault</faultActionMapping>
            <faultActionMapping 
faultName="DataAccessFault">http://service.medici_link/Medici_LinkPortType/validateSystem/Fault/DataAccessFault</faultActionMapping>
        </operation>


Thanks a lot,

Jorge Fernández

Ruchith Fernando <[EMAIL PROTECTED]> escribió: You can engage rampart per 
operation by adding the "
ref="rampart"/>" in the operation element of the services.xml. If the
operation dispatching happens before the message reaches the security
in handler then it should work.

Thanks,
Ruchith

On 7/6/07, Jorge Fernandez  wrote:
> While this issue is not fixed, Is there a way I can engage the rampart
> module per operation, so I can desactivate it for those operations having
> problems??? I tried in the services.xml but it's not possible.
>
> Thanks,
>
> Jorge Fernández
>
> Jorge Fernandez  escribió:
>  https://issues.apache.org/jira/browse/RAMPART-53 created
>
> Davanum Srinivas  escribió:
>  Jorge,
>
> Please log a new bug with your test case.
>
> thanks,
> dims
>
> On 7/4/07, Jorge Fernandez wrote:
> > Hi,
> >
> > Some months ago, I had some problems with the use of hierarchies with adb
> > and xmlbeans. Apparently they were resolved with adb but know, I'm getting
> > the same error.
> >
> > For example: I have an array of an object called "parent" and I put into
> > that array instances of "child1" or "child2" (those inherit from parent).
> In
> > the xml generated from that array should appear the xsi:type attribute but
> > when I engage rampart module, that attribute dissapears. So maybe that was
> > the cause of the problems I had before. See
> > https://issues.apache.org/jira/browse/XMLBEANS-329 and
> > https://issues.apache.org/jira/browse/AXIS2-2578.
> >
> >
> >
> >
> > ________________________________
> >
> > ¡Descubre una nueva forma de obtener respuestas a tus preguntas!
> > Entra en Yahoo! Respuestas.
> >
> >
> >
>
>
> --
> Davanum Srinivas :: http://davanum.wordpress.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>  ________________________________
>
> ¡Descubre una nueva forma de obtener respuestas a tus preguntas!
> Entra en Yahoo! Respuestas.
>
>
>
>  ________________________________
>
> Sé un Mejor Amante del Cine
> ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! .
>
>
>


-- 
www.ruchith.org
www.wso2.org


       
---------------------------------

Sé un Mejor Viajero
¿Quieres saber cómo? ¡Deja que otras personas te ayuden! .

Reply via email to