Using seda-optimised

[Martin Serrano]

Hello,

I want to try seda-optimised for one of my configurations.  I have set up several components that implement the Initialisable and Disposable interfaces.  What I have discovered is that initialise and dispose are not called by the OptimisedMuleProxy class.  Is this an oversight, or is there something about OptimisedSeda that prohibits initialise and dispose?

Thanks,
Martin

[Martin Serrano]

I was able to get this working fine.  I moved my initialise and dispose methods to be start and stop and all was well.  BTW, in one test, this switch gave me an almost 10% performance boost.

Martin Serrano wrote:

Hello,

I want to try seda-optimised for one of my configurations.  I have set up several components that implement the Initialisable and Disposable interfaces.  What I have discovered is that initialise and dispose are not called by the OptimisedMuleProxy class.  Is this an oversight, or is there something about OptimisedSeda that prohibits initialise and dispose?

Thanks,
Martin

[Will Johnson-2]

It also appears that using SEDA-Optimised causes any
UMODescriptorAware.setDescriptor methods to be ignored.  From looking at the
code it seems like the SEDA mule mode calls:

umo = model.getLifecycleAdapterFactory().create(component, descriptor,
resolver);

which handles all the lifecycle events (which I assume is why martin ran
into the initialise issue)

however optimized seda just does the following in its constructor:

umo = component;

am I missing something or should optimized seda also support the
UMODescriptor aware design pattern? (not to mention initialize and dispose)

- will





-----Original Message-----
From: MartinSerrano [mailto:martin.serrano@...]
Sent: Friday, October 19, 2007 8:24 PM
To: user@...
Subject: Re: [mule-user] Using seda-optimised


I was able to get this working fine.  I moved my initialise and dispose
methods to be start and stop and all was well.  BTW, in one test, this
switch gave me an almost 10% performance boost.


Martin Serrano wrote:

>
> Hello,
>
> I want to try seda-optimised for one of my configurations.  I have set up
> several components that implement the Initialisable and Disposable
> interfaces.  What I have discovered is that initialise and dispose are not
> called by the OptimisedMuleProxy class.  Is this an oversight, or is there
> something about OptimisedSeda that prohibits initialise and dispose?
>
> Thanks,
> Martin
>
>
>

--
View this message in context:
http://www.nabble.com/Using-seda-optimised-tf4655805.html#a13305289
Sent from the Mule - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email


---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

[Will Johnson-2]

http://mule.mulesource.org/jira/browse/MULE-2626

- will

-----Original Message-----
From: MartinSerrano [mailto:martin.serrano@...]
Sent: Friday, October 19, 2007 8:24 PM
To: user@...
Subject: Re: [mule-user] Using seda-optimised


I was able to get this working fine.  I moved my initialise and dispose
methods to be start and stop and all was well.  BTW, in one test, this
switch gave me an almost 10% performance boost.


Martin Serrano wrote:

>
> Hello,
>
> I want to try seda-optimised for one of my configurations.  I have set up
> several components that implement the Initialisable and Disposable
> interfaces.  What I have discovered is that initialise and dispose are not
> called by the OptimisedMuleProxy class.  Is this an oversight, or is there
> something about OptimisedSeda that prohibits initialise and dispose?
>
> Thanks,
> Martin
>
>
>

--
View this message in context:
http://www.nabble.com/Using-seda-optimised-tf4655805.html#a13305289
Sent from the Mule - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email


---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email