Hi Mohammad, I did some initial research into what kind of config files are available in WAS. Seems like configuration is split in multiple files (.xmi files). Will continue to explore. I'd say version 6 and 7 would be the targets. Objective is to 1. Allow easy migration from WAS where folks can simply drop a EAR into TomEE 2. Have TomEE read the WAS configuration and spit out its own corresponding configuration which folks could use after migration.
Any input or guidance would be great. On Mon, Jul 30, 2012 at 8:39 AM, Mohammad Nour El-Din < [email protected]> wrote: > Hi Karan... > > Any progress in that regard ? Asking just out of interest > > I started by supporting WAS 6.0 as at that time it was the commonly found > in most of already existing production environments, I am not sure if that > is still the case or not. > > Would you please explain what are the use case scenarios for the need of > such feature ? which versions are required to be supported ? > > On Wed, Jul 11, 2012 at 9:26 AM, Romain Manni-Bucau > <[email protected]>wrote: > > > You basically need to add WAS descriptor in openejb-jee (in a was8 > > package?) > > > > then as said JL add a WASConverter implementing DynamicDeployer > > > > then add WAS8 to vendors and in ConfigurationFactory respect the property > > selecting activated conversions: > > "final Set<Vendor> support = > > SystemInstance.get().getOptions().getAll("openejb.vendor.config", > > Vendor.values());" > > > > typically you'll do: > > > > if (support.contains(Vendor.WAS8)) { > > chain.add(new Was8Conversion()); > > } > > > > > > - Romain > > > > > > 2012/7/11 dsh <[email protected]> > > > > > Well WAS V6 is a bit outdated... the latest and greates is V8.5 ;) > > > > > > On Wed, Jul 11, 2012 at 9:09 AM, Jean-Louis MONTEIRO < > [email protected] > > > > > > wrote: > > > > Hi Karan, > > > > > > > > Mohammad already started the same kind of work a year ago (or so). > > > > He started creating JaxB tree from WAS XSD. I guess, some of them are > > > > already available for WAS v6 (AFAIR). > > > > All should be in container/openejb-jee > > > > > > > > Then, I guess you just need to create a new DynamicDeployer (have a > > look > > > to > > > > OpenEjb2Conversion, WlsConversion, SunConversion and so on). > > > > > > > > All the stuff is then added in ConfigurationFactory depending on the > > > vendor > > > > you wanna deal with. As soon as you get your converter created, just > > add > > > it > > > > to the chain. > > > > > > > > Hope it helps, > > > > Jean-Louis > > > > > > > > > > > > > > > > 2012/7/11 Karan Malhi <[email protected]> > > > > > > > >> I want to start working on the ability to migrate apps deployed on > > > >> Websphere onto TomEE. Can anybody give me some guidance on how to > get > > > >> started on it? > > > >> > > > >> -- > > > >> > > > >> Karan Singh Malhi > > > >> twitter.com/KaranSinghMalhi > > > >> > > > > > > > > > -- > Thanks > - Mohammad Nour > ---- > "Life is like riding a bicycle. To keep your balance you must keep moving" > - Albert Einstein > -- Karan Singh Malhi twitter.com/KaranSinghMalhi
