Difference in Mule 2.2.x and Mule 3.0

[Purohit, Manoj R]

Hello,

Apart from hot deployment, what is the difference between Mule 2.2.x and Mule 3.0 series ?
Specially some high level architectural insight would be helpful to community.
Is it a same code base or drastically different code base ?
What tech we are using to achive hot deployment some third party or mule custom code ?
3.0 is having osgi features ?

Regards,
Manoj

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

    http://xircles.codehaus.org/manage_email

[Andrew Perepelytsya]

On Tue, Jun 30, 2009 at 3:25 PM, Purohit, Manoj R <manoj.r.purohit@...> wrote:

Hello,

Apart from hot deployment, what is the difference between Mule 2.2.x and Mule 3.0 series ?

Some internal changes (at the moment not dramatic), new transports not otherwise available elsewhere (e.g. ajax transport). Per-app ClassLoader isolation (read more about app's lib dir here: http://blog.mulesource.org/2009/06/the-old-new-mule-3x-and-its-hot/ ) It is still a work in progress, in general.
 

Specially some high level architectural insight would be helpful to community.

We will publish detailed migration guides for the release, once it's ready. In the meantime milestone notes will provide interim progress reports.
 

Is it a same code base or drastically different code base ?

Not the same, but not drastically different either. Apart from modifying the config namespace (strip the version from namespace, see hello app example in 3.0.0-M1), Mule 2.x configs should run as is.

 

What tech we are using to achive hot deployment some third party or mule custom code ?

This is a custom code. In its core, any hot deployment in Java does the same, one doesn't need osgi to provide redeployment. 

 

3.0 is having osgi features ?

Not currently.

HTH,
Andrew

[Andrew Perepelytsya]

Hi All,

Just posting an update to pre-empt any refs to that thread in the future. Ross is currently committing major API changes in order to desingletonize the MuleContext. That means that 3.0.0-M2 might have serious changes internally. However, there should be minimum impact on the regular user, if any, changes affect Mule extenders mostly.

As always, a detailed migration guide will be published closer to a release.

HTH,
Andrew