On 9/4/07, André Szdzuy <[EMAIL PROTECTED]> wrote:
>
> Hm, I think we also have a problem with system properties here because we can
> have several users at the same time. So one request could change the user
> property while another one is still in process, right?
>
> The perfect solution for me would be if the username is handled like the
> locationURI: the value set in the xbean.xml can be overwritten by setting a
> property in the NormalizedMessage. For locationURI this was implemented for
> JIRA SM-695.
>
> If I add the following lines in the process() method in class
> org.apache.servicemix.http.processors.ProviderProcessor, line 132,
> everything is fine:
>
> Object username = nm.getProperty("user");
> if (username != null) {
> context.setProperty("user", username);
> log.debug("Use username from NormalizedMessage: " + username);
> }
>
> nm is the NormalizedMessage and context the
> org.apache.servicemix.soap.Context object that is passed to the onSend()
> method of WSSecurityHandler class.
>
> Should I raise a JIRA for that?
You could also consider writing your own marshaler that you plug in
via the xbean.xml. This would allow you to do anything you want to the
normalized message.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Castor - http://castor.org/
