hey,
now it works ;-)))))
i've moved the client SocketConnector from the /app container to the /app/net4j/socket/client container...
This confirms that you dealing with the same issue as before - namely the problem concerning composite redirection.
what can i do to declare several clients (with different configs) without touching the nested net4j container?
Umm .. not knowing your scenario the immediate thing that comes to mind is "just declare several clients with different configs" - but I have a hunch that perhaps this is not the answer you want.
I would have assumed that you would simply declare some additional client components ..
<component class="MyClientComponent" name="another-client">
<!-- something specific -->
</component>If on the other-hand you constructing client dynamically then all you need to do is to create a new profile per client and use this to construct a new singleton client component.
Steve.
/eike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
|---------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org | |---------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
