On Thu, Jan 23, 2014 at 11:00 PM, Isuru Udana isu...@wso2.com wrote:
Hi,
Class Mediators created from Dev Studio can be deployed into ESB using a
CAR.
But current implementation of this feature has lot of known issues. So we
are in the process of implementing this using a different approach.
All artifact types starting from lib/, get installed as an osgi bundle
by the carbon.application.deployer which is placed in the kernel.
For the new implementation we need to stop this for artifact type
lib/synapse/mediator since deployment is handled at the synapse level.
We cannot change the artifact type of Mediators to a different one because
it will cause configuration migration issues (previously created CARs will
not work).
I don't think we need to be backward compatible with previously created
CARs for any server extension projects instead we can provide some
tool/guideline to migrate CAR to new type. At least from beginning of
2012 we are keep educating users not to use CAR projects to develop/deploy
server extensions as it fundamentally incorrect so we better to focus on
clear solution instead of backward compatibility. Basically hosted
artifacts and server extensions having two different lifecycles and need to
be managed separately. Here Axis2 Modules, Class and custom Mediators,
custom transport and message processors should consider as
server extensions.
Thanks !
The only option I see is to skip the above osgi bundle installation for
lib/synapse/mediator type at the kernel.
That will introduce a check for this particular artifact type at the
kernel. So this is not a elegant solution.
However we already have a logic specific to service/dataservice artifact
type at the kernel capp deployer.
Do we have any other option ?
Thank you.
--
*Isuru Udana*
Senior
* Software Engineer*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Sagara Gunathunga
Senior Technical Lead; WSO2, Inc.; http://wso2.com
V.P Apache Web Services;http://ws.apache.org/
Linkedin; http://www.linkedin.com/in/ssagara
Blog ; http://ssagara.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
