AOP won't help since the client is going to be in a different JVM the
server. So there is no server logic that can control the client until
the client connects.. and it seems your too late at that point.
On Tue, Sep 2, 2008 at 2:09 PM, Bruce Snyder <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 21, 2008 at 9:19 AM, Bruce Snyder <[EMAIL PROTECTED]> wrote:
>> On Wed, Aug 20, 2008 at 11:03 AM, Bruce Snyder <[EMAIL PROTECTED]> wrote:
>>> On Wed, Aug 20, 2008 at 10:43 AM, James Strachan
>>> <[EMAIL PROTECTED]> wrote:
>>>> The broker doesn't know about a client side connection object until its
>>>> started
>>>
>>> I guess that's because there's no knowledge of the broker until that
>>> point. Is that correct? Hmmm :-(.
>>>
>>> It seems to me that we should be able to intercept the initial request
>>> to create a connection instead of waiting for the client to call
>>> start(). I'd like to add a call to BrokerFilter.addConnection()
>>> earlier in the process. Is there any exposure of a Broker sooner than
>>> the creation of a TransportConnection?
>>>
>>> Well even so, a call to ActiveMQConnection.start() does not call down
>>> into the BrokerFilter.addConnection() method anywhere in the process.
>>
>> Any thoughts on my questions above?
>
> Any additional thoughts here? I'm thinking of using AOP.
>
> 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 Camel - http://activemq.org/camel/
> Apache ServiceMix - http://servicemix.org/
>
> Blog: http://bruceblog.org/
>
--
Regards,
Hiram
Blog: http://hiramchirino.com
Open Source SOA
http://open.iona.com
