You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by Jarek Gawor <jg...@gmail.com> on 2010/01/11 21:38:59 UTC
Migrating WAR to WAB converter
Hi,
Is anyone planning to migrate the WAR to WAB converter donated by IBM
to trunk any time soon? If not, and if there are no objections I can
work on moving that code to trunk.
Jarek
Re: Migrating WAR to WAB converter
Posted by Lin Sun <li...@gmail.com>.
Hi Valentin, thanks, that sounds right to me, iiuc. :)
Lin
On Tue, Jan 12, 2010 at 1:10 PM, Valentin Mahrwald
<vm...@googlemail.com> wrote:
>
> That's only too true. What I thought actually thought about when I wrote it
> was to implement the webbundle handler through an extension to the
> BundleConverter. (So option 2)
>
> But actually since then I must confess it looks more natural to do it the
> other way around. So the WabConverter service would be a new export from a
> new RFC 66 bundle that is driven by the application converter
> implementation, which would add functionality such as reading out the
> context root from an application.xml if present.
>
> Sounds about right?
>
Re: Migrating WAR to WAB converter
Posted by Valentin Mahrwald <vm...@googlemail.com>.
On 12 Jan 2010, at 17:40, Lin Sun wrote:
> Hi Valentin,
>
> I like the 3rd option too. Having the webbundle url handler is an
> important part of the RFC 66 specification, since we already have it
> in contrib, it is great to have it moved like you decided.
>
> I have one question below.
>
> On Tue, Jan 12, 2010 at 11:58 AM, Valentin Mahrwald
> <vm...@googlemail.com> wrote:
>> My personal preference would be the third choice, keeping a minimum
>> of
>> separation without unnecessary bundle. Also, I think the
>> BundleConverter
>> interface is the more general one. However, that choice would mean
>> the
>> webbundle handler bundle would have imports from application API.
>
> I didn't quite understand why the 3rd choice would require the web
> bundle handler bundle have imports from Application API. I think it
> would be the other way around.
>
> Lin
That's only too true. What I thought actually thought about when I
wrote it was to implement the webbundle handler through an extension
to the BundleConverter. (So option 2)
But actually since then I must confess it looks more natural to do it
the other way around. So the WabConverter service would be a new
export from a new RFC 66 bundle that is driven by the application
converter implementation, which would add functionality such as
reading out the context root from an application.xml if present.
Sounds about right?
Re: Migrating WAR to WAB converter
Posted by Lin Sun <li...@gmail.com>.
Hi Valentin,
I like the 3rd option too. Having the webbundle url handler is an
important part of the RFC 66 specification, since we already have it
in contrib, it is great to have it moved like you decided.
I have one question below.
On Tue, Jan 12, 2010 at 11:58 AM, Valentin Mahrwald
<vm...@googlemail.com> wrote:
> My personal preference would be the third choice, keeping a minimum of
> separation without unnecessary bundle. Also, I think the BundleConverter
> interface is the more general one. However, that choice would mean the
> webbundle handler bundle would have imports from application API.
I didn't quite understand why the 3rd choice would require the web
bundle handler bundle have imports from Application API. I think it
would be the other way around.
Lin
Re: Migrating WAR to WAB converter
Posted by Valentin Mahrwald <vm...@googlemail.com>.
Thanks for the explanation Jarek. It makes much more sense to me now.
Then as far as reusing the same code is concerned there is four choices:
- have a common converter bundle used by the application
BundleConverter as well as the webbundle handler
- make the webbundle handler reuse the BundleConverter
- make the BundleConverter reuse the webbundle handler
- have everything in a single bundle.
My personal preference would be the third choice, keeping a minimum of
separation without unnecessary bundle. Also, I think the
BundleConverter interface is the more general one. However, that
choice would mean the webbundle handler bundle would have imports from
application API. I assume that would not be a problem in Genorimo,
right?
What do people think?
Valentin
On 12 Jan 2010, at 16:05, Jarek Gawor wrote:
> The converter and extender are related but separate parts. In Geronimo
> I think we will have a Geronimo-specific extender but we would like to
> use the converter from Aries. So we want to see the converter code
> (along with the url handler) to be moved to trunk even though there is
> no extender in Aries right now.
>
> Jarek
>
> On Tue, Jan 12, 2010 at 10:55 AM, Alasdair Nottingham
> <no...@apache.org> wrote:
>> The WAR to WAB url handler is pretty useless in the absence of a web
>> application extender which can serve the content. That is why, in my
>> view, it has remained in contrib, not because of lack of interest.
>> Until we have a view on how/where we get a web application extender
>> from I do not think there is a need to create the WAR to WAB url
>> handler. At that time I would expect to want to ensure that the code
>> is reused between the BundleConverter and the WAR to WAB converter.
>>
>> Alasdair
>>
>> 2010/1/12 Valentin Mahrwald <vm...@googlemail.com>:
>>> Hi Lin,
>>>
>>> as it stands I have not moved the webbundle url handler part of
>>> the code.
>>> Rather I have moved the existing code to hook into the
>>> BundleConverter API
>>> that is defined in application manifest. So using the current bundle
>>> (application-converters) you would not get the webbundle url
>>> handler and you
>>> would need to have at least the application API bundle as well.
>>>
>>> The main reason for this setup is that there is an immediate use
>>> case for
>>> the code through the BundleConverter API but I was not sure on the
>>> other
>>> hand if anyone is actually interested in the webbundle url handler
>>> on its
>>> own (seeing how long the code has lingered in /contrib ;).
>>>
>>> Regards,
>>>
>>> Valentin
>>>
>>>
>>> On 12 Jan 2010, at 14:30, Lin Sun wrote:
>>>
>>>> I prefer to keep them separately too. It is possible that people
>>>> may
>>>> just want to consume the webbundle url handler without the app
>>>> management API.
>>>>
>>>> Lin
>>>>
>>>> On Mon, Jan 11, 2010 at 4:46 PM, Alasdair Nottingham <not@apache.org
>>>> >
>>>> wrote:
>>>>>
>>>>> I'm very tempted to suggest putting it out separately so people
>>>>> can
>>>>> choose not to consume it reasonably easily. Also I think it is
>>>>> likely
>>>>> that as we progress we may want to use it in more places and
>>>>> having it
>>>>> slightly to one size should make that simpler.
>>>>>
>>>>> Just my 2 cents worth.
>>>>>
>>>>> Alasdair
>>>>>
>>>>> 2010/1/11 Valentin Mahrwald <vm...@googlemail.com>:
>>>>>>
>>>>>> My current working set has a new converters project under
>>>>>> application
>>>>>> primed
>>>>>> with the WarToWab conversions, but I suppose it could equally
>>>>>> go into
>>>>>> the
>>>>>> existing management project. Any thoughts?
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Valentin
>>>>>>
>>>>>> On 11 Jan 2010, at 21:04, Jarek Gawor wrote:
>>>>>>
>>>>>>> Valentin,
>>>>>>>
>>>>>>> Ok, great! Looking forward to your updates. Will the converter
>>>>>>> be in a
>>>>>>> separate module?
>>>>>>>
>>>>>>> Jarek
>>>>>>>
>>>>>>> On Mon, Jan 11, 2010 at 3:50 PM, Valentin Mahrwald
>>>>>>> <vm...@googlemail.com> wrote:
>>>>>>>>
>>>>>>>> Hi Jarek,
>>>>>>>>
>>>>>>>> I have started just yesterday moving it to the new
>>>>>>>> BundleConverter API
>>>>>>>> but I
>>>>>>>> haven't come round to raise a JIRA for it yet :) I am quite
>>>>>>>> happy to
>>>>>>>> continue with the task.
>>>>>>>>
>>>>>>>> My idea was to take the code out of the context of the RFC 66
>>>>>>>> context
>>>>>>>> it
>>>>>>>> was
>>>>>>>> originally contributed since the RFC 66 bits weren't much
>>>>>>>> more than
>>>>>>>> the
>>>>>>>> conversion logic anyway.
>>>>>>>>
>>>>>>>> Valentin
>>>>>>>>
>>>>>>>> On 11 Jan 2010, at 20:38, Jarek Gawor wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> Is anyone planning to migrate the WAR to WAB converter
>>>>>>>>> donated by IBM
>>>>>>>>> to trunk any time soon? If not, and if there are no
>>>>>>>>> objections I can
>>>>>>>>> work on moving that code to trunk.
>>>>>>>>>
>>>>>>>>> Jarek
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Alasdair Nottingham
>>>>> not@apache.org
>>>>>
>>>
>>>
>>
>>
>>
>> --
>> Alasdair Nottingham
>> not@apache.org
>>
Re: Migrating WAR to WAB converter
Posted by Jarek Gawor <jg...@gmail.com>.
The converter and extender are related but separate parts. In Geronimo
I think we will have a Geronimo-specific extender but we would like to
use the converter from Aries. So we want to see the converter code
(along with the url handler) to be moved to trunk even though there is
no extender in Aries right now.
Jarek
On Tue, Jan 12, 2010 at 10:55 AM, Alasdair Nottingham <no...@apache.org> wrote:
> The WAR to WAB url handler is pretty useless in the absence of a web
> application extender which can serve the content. That is why, in my
> view, it has remained in contrib, not because of lack of interest.
> Until we have a view on how/where we get a web application extender
> from I do not think there is a need to create the WAR to WAB url
> handler. At that time I would expect to want to ensure that the code
> is reused between the BundleConverter and the WAR to WAB converter.
>
> Alasdair
>
> 2010/1/12 Valentin Mahrwald <vm...@googlemail.com>:
>> Hi Lin,
>>
>> as it stands I have not moved the webbundle url handler part of the code.
>> Rather I have moved the existing code to hook into the BundleConverter API
>> that is defined in application manifest. So using the current bundle
>> (application-converters) you would not get the webbundle url handler and you
>> would need to have at least the application API bundle as well.
>>
>> The main reason for this setup is that there is an immediate use case for
>> the code through the BundleConverter API but I was not sure on the other
>> hand if anyone is actually interested in the webbundle url handler on its
>> own (seeing how long the code has lingered in /contrib ;).
>>
>> Regards,
>>
>> Valentin
>>
>>
>> On 12 Jan 2010, at 14:30, Lin Sun wrote:
>>
>>> I prefer to keep them separately too. It is possible that people may
>>> just want to consume the webbundle url handler without the app
>>> management API.
>>>
>>> Lin
>>>
>>> On Mon, Jan 11, 2010 at 4:46 PM, Alasdair Nottingham <no...@apache.org>
>>> wrote:
>>>>
>>>> I'm very tempted to suggest putting it out separately so people can
>>>> choose not to consume it reasonably easily. Also I think it is likely
>>>> that as we progress we may want to use it in more places and having it
>>>> slightly to one size should make that simpler.
>>>>
>>>> Just my 2 cents worth.
>>>>
>>>> Alasdair
>>>>
>>>> 2010/1/11 Valentin Mahrwald <vm...@googlemail.com>:
>>>>>
>>>>> My current working set has a new converters project under application
>>>>> primed
>>>>> with the WarToWab conversions, but I suppose it could equally go into
>>>>> the
>>>>> existing management project. Any thoughts?
>>>>>
>>>>> Regards,
>>>>>
>>>>> Valentin
>>>>>
>>>>> On 11 Jan 2010, at 21:04, Jarek Gawor wrote:
>>>>>
>>>>>> Valentin,
>>>>>>
>>>>>> Ok, great! Looking forward to your updates. Will the converter be in a
>>>>>> separate module?
>>>>>>
>>>>>> Jarek
>>>>>>
>>>>>> On Mon, Jan 11, 2010 at 3:50 PM, Valentin Mahrwald
>>>>>> <vm...@googlemail.com> wrote:
>>>>>>>
>>>>>>> Hi Jarek,
>>>>>>>
>>>>>>> I have started just yesterday moving it to the new BundleConverter API
>>>>>>> but I
>>>>>>> haven't come round to raise a JIRA for it yet :) I am quite happy to
>>>>>>> continue with the task.
>>>>>>>
>>>>>>> My idea was to take the code out of the context of the RFC 66 context
>>>>>>> it
>>>>>>> was
>>>>>>> originally contributed since the RFC 66 bits weren't much more than
>>>>>>> the
>>>>>>> conversion logic anyway.
>>>>>>>
>>>>>>> Valentin
>>>>>>>
>>>>>>> On 11 Jan 2010, at 20:38, Jarek Gawor wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> Is anyone planning to migrate the WAR to WAB converter donated by IBM
>>>>>>>> to trunk any time soon? If not, and if there are no objections I can
>>>>>>>> work on moving that code to trunk.
>>>>>>>>
>>>>>>>> Jarek
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Alasdair Nottingham
>>>> not@apache.org
>>>>
>>
>>
>
>
>
> --
> Alasdair Nottingham
> not@apache.org
>
Re: Migrating WAR to WAB converter
Posted by Alasdair Nottingham <no...@apache.org>.
The WAR to WAB url handler is pretty useless in the absence of a web
application extender which can serve the content. That is why, in my
view, it has remained in contrib, not because of lack of interest.
Until we have a view on how/where we get a web application extender
from I do not think there is a need to create the WAR to WAB url
handler. At that time I would expect to want to ensure that the code
is reused between the BundleConverter and the WAR to WAB converter.
Alasdair
2010/1/12 Valentin Mahrwald <vm...@googlemail.com>:
> Hi Lin,
>
> as it stands I have not moved the webbundle url handler part of the code.
> Rather I have moved the existing code to hook into the BundleConverter API
> that is defined in application manifest. So using the current bundle
> (application-converters) you would not get the webbundle url handler and you
> would need to have at least the application API bundle as well.
>
> The main reason for this setup is that there is an immediate use case for
> the code through the BundleConverter API but I was not sure on the other
> hand if anyone is actually interested in the webbundle url handler on its
> own (seeing how long the code has lingered in /contrib ;).
>
> Regards,
>
> Valentin
>
>
> On 12 Jan 2010, at 14:30, Lin Sun wrote:
>
>> I prefer to keep them separately too. It is possible that people may
>> just want to consume the webbundle url handler without the app
>> management API.
>>
>> Lin
>>
>> On Mon, Jan 11, 2010 at 4:46 PM, Alasdair Nottingham <no...@apache.org>
>> wrote:
>>>
>>> I'm very tempted to suggest putting it out separately so people can
>>> choose not to consume it reasonably easily. Also I think it is likely
>>> that as we progress we may want to use it in more places and having it
>>> slightly to one size should make that simpler.
>>>
>>> Just my 2 cents worth.
>>>
>>> Alasdair
>>>
>>> 2010/1/11 Valentin Mahrwald <vm...@googlemail.com>:
>>>>
>>>> My current working set has a new converters project under application
>>>> primed
>>>> with the WarToWab conversions, but I suppose it could equally go into
>>>> the
>>>> existing management project. Any thoughts?
>>>>
>>>> Regards,
>>>>
>>>> Valentin
>>>>
>>>> On 11 Jan 2010, at 21:04, Jarek Gawor wrote:
>>>>
>>>>> Valentin,
>>>>>
>>>>> Ok, great! Looking forward to your updates. Will the converter be in a
>>>>> separate module?
>>>>>
>>>>> Jarek
>>>>>
>>>>> On Mon, Jan 11, 2010 at 3:50 PM, Valentin Mahrwald
>>>>> <vm...@googlemail.com> wrote:
>>>>>>
>>>>>> Hi Jarek,
>>>>>>
>>>>>> I have started just yesterday moving it to the new BundleConverter API
>>>>>> but I
>>>>>> haven't come round to raise a JIRA for it yet :) I am quite happy to
>>>>>> continue with the task.
>>>>>>
>>>>>> My idea was to take the code out of the context of the RFC 66 context
>>>>>> it
>>>>>> was
>>>>>> originally contributed since the RFC 66 bits weren't much more than
>>>>>> the
>>>>>> conversion logic anyway.
>>>>>>
>>>>>> Valentin
>>>>>>
>>>>>> On 11 Jan 2010, at 20:38, Jarek Gawor wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> Is anyone planning to migrate the WAR to WAB converter donated by IBM
>>>>>>> to trunk any time soon? If not, and if there are no objections I can
>>>>>>> work on moving that code to trunk.
>>>>>>>
>>>>>>> Jarek
>>>>>>
>>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Alasdair Nottingham
>>> not@apache.org
>>>
>
>
--
Alasdair Nottingham
not@apache.org
Re: Migrating WAR to WAB converter
Posted by Valentin Mahrwald <vm...@googlemail.com>.
Hi Lin,
as it stands I have not moved the webbundle url handler part of the
code. Rather I have moved the existing code to hook into the
BundleConverter API that is defined in application manifest. So using
the current bundle (application-converters) you would not get the
webbundle url handler and you would need to have at least the
application API bundle as well.
The main reason for this setup is that there is an immediate use case
for the code through the BundleConverter API but I was not sure on the
other hand if anyone is actually interested in the webbundle url
handler on its own (seeing how long the code has lingered in /
contrib ;).
Regards,
Valentin
On 12 Jan 2010, at 14:30, Lin Sun wrote:
> I prefer to keep them separately too. It is possible that people may
> just want to consume the webbundle url handler without the app
> management API.
>
> Lin
>
> On Mon, Jan 11, 2010 at 4:46 PM, Alasdair Nottingham
> <no...@apache.org> wrote:
>> I'm very tempted to suggest putting it out separately so people can
>> choose not to consume it reasonably easily. Also I think it is likely
>> that as we progress we may want to use it in more places and having
>> it
>> slightly to one size should make that simpler.
>>
>> Just my 2 cents worth.
>>
>> Alasdair
>>
>> 2010/1/11 Valentin Mahrwald <vm...@googlemail.com>:
>>> My current working set has a new converters project under
>>> application primed
>>> with the WarToWab conversions, but I suppose it could equally go
>>> into the
>>> existing management project. Any thoughts?
>>>
>>> Regards,
>>>
>>> Valentin
>>>
>>> On 11 Jan 2010, at 21:04, Jarek Gawor wrote:
>>>
>>>> Valentin,
>>>>
>>>> Ok, great! Looking forward to your updates. Will the converter be
>>>> in a
>>>> separate module?
>>>>
>>>> Jarek
>>>>
>>>> On Mon, Jan 11, 2010 at 3:50 PM, Valentin Mahrwald
>>>> <vm...@googlemail.com> wrote:
>>>>>
>>>>> Hi Jarek,
>>>>>
>>>>> I have started just yesterday moving it to the new
>>>>> BundleConverter API
>>>>> but I
>>>>> haven't come round to raise a JIRA for it yet :) I am quite
>>>>> happy to
>>>>> continue with the task.
>>>>>
>>>>> My idea was to take the code out of the context of the RFC 66
>>>>> context it
>>>>> was
>>>>> originally contributed since the RFC 66 bits weren't much more
>>>>> than the
>>>>> conversion logic anyway.
>>>>>
>>>>> Valentin
>>>>>
>>>>> On 11 Jan 2010, at 20:38, Jarek Gawor wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Is anyone planning to migrate the WAR to WAB converter donated
>>>>>> by IBM
>>>>>> to trunk any time soon? If not, and if there are no objections
>>>>>> I can
>>>>>> work on moving that code to trunk.
>>>>>>
>>>>>> Jarek
>>>>>
>>>>>
>>>
>>>
>>
>>
>>
>> --
>> Alasdair Nottingham
>> not@apache.org
>>
Re: Migrating WAR to WAB converter
Posted by Lin Sun <li...@gmail.com>.
I prefer to keep them separately too. It is possible that people may
just want to consume the webbundle url handler without the app
management API.
Lin
On Mon, Jan 11, 2010 at 4:46 PM, Alasdair Nottingham <no...@apache.org> wrote:
> I'm very tempted to suggest putting it out separately so people can
> choose not to consume it reasonably easily. Also I think it is likely
> that as we progress we may want to use it in more places and having it
> slightly to one size should make that simpler.
>
> Just my 2 cents worth.
>
> Alasdair
>
> 2010/1/11 Valentin Mahrwald <vm...@googlemail.com>:
>> My current working set has a new converters project under application primed
>> with the WarToWab conversions, but I suppose it could equally go into the
>> existing management project. Any thoughts?
>>
>> Regards,
>>
>> Valentin
>>
>> On 11 Jan 2010, at 21:04, Jarek Gawor wrote:
>>
>>> Valentin,
>>>
>>> Ok, great! Looking forward to your updates. Will the converter be in a
>>> separate module?
>>>
>>> Jarek
>>>
>>> On Mon, Jan 11, 2010 at 3:50 PM, Valentin Mahrwald
>>> <vm...@googlemail.com> wrote:
>>>>
>>>> Hi Jarek,
>>>>
>>>> I have started just yesterday moving it to the new BundleConverter API
>>>> but I
>>>> haven't come round to raise a JIRA for it yet :) I am quite happy to
>>>> continue with the task.
>>>>
>>>> My idea was to take the code out of the context of the RFC 66 context it
>>>> was
>>>> originally contributed since the RFC 66 bits weren't much more than the
>>>> conversion logic anyway.
>>>>
>>>> Valentin
>>>>
>>>> On 11 Jan 2010, at 20:38, Jarek Gawor wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Is anyone planning to migrate the WAR to WAB converter donated by IBM
>>>>> to trunk any time soon? If not, and if there are no objections I can
>>>>> work on moving that code to trunk.
>>>>>
>>>>> Jarek
>>>>
>>>>
>>
>>
>
>
>
> --
> Alasdair Nottingham
> not@apache.org
>
Re: Migrating WAR to WAB converter
Posted by Graham Charters <gc...@googlemail.com>.
Hi Charles,
The most current public specification for this is the "Web Container
Specification" in this draft:
http://www.osgi.org/download/osgi-4.2-enterprise-early-draft4.pdf
Regards, Graham.
2010/1/12 Charles Moulliard <cm...@gmail.com>:
> Thxs.
>
> I have found info about RFC 66 here :
> http://blog.springsource.com/2009/05/27/introduction-to-the-osgi-web-container/
>
> Regards,
>
> Charles Moulliard
> Senior Enterprise Architect
> Apache Camel Committer
>
> *****************************
> blog : http://cmoulliard.blogspot.com
> twitter : http://twitter.com/cmoulliard
> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>
> Apache Camel Group :
> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>
>
> On Tue, Jan 12, 2010 at 10:02 AM, Valentin Mahrwald <
> vmahrwald@googlemail.com> wrote:
>
>> Hi Charles,
>>
>> currently there is no WAB container in Apache Aries. The War to Wab
>> converter was initially contributed as a piece towards implementing RFC66
>> but no further work has been done on that (as yet?).
>>
>> However, as part of the application management facilities I have just moved
>> this code to the trunk. Now, I don't believe there is any documentation on
>> it and even the javadoc is as yet non-existent for the most part. I intend
>> to fix at least the latter part in the next week or so (I have raised
>> ARIES-115 to cover it).
>>
>> Regards,
>>
>> Valentin
>>
>>
>> On 12 Jan 2010, at 08:05, Charles Moulliard wrote:
>>
>> Hi,
>>>
>>> Where can we find more info about WAR to WAB converter and added value of
>>> WAB container ?
>>>
>>> Regards,
>>>
>>> Charles Moulliard
>>> Senior Enterprise Architect
>>> Apache Camel Committer
>>>
>>> *****************************
>>> blog : http://cmoulliard.blogspot.com
>>> twitter : http://twitter.com/cmoulliard
>>> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>>>
>>> Apache Camel Group :
>>> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>>>
>>>
>>> On Mon, Jan 11, 2010 at 10:46 PM, Alasdair Nottingham <not@apache.org
>>> >wrote:
>>>
>>> I'm very tempted to suggest putting it out separately so people can
>>>> choose not to consume it reasonably easily. Also I think it is likely
>>>> that as we progress we may want to use it in more places and having it
>>>> slightly to one size should make that simpler.
>>>>
>>>> Just my 2 cents worth.
>>>>
>>>> Alasdair
>>>>
>>>> 2010/1/11 Valentin Mahrwald <vm...@googlemail.com>:
>>>>
>>>>> My current working set has a new converters project under application
>>>>>
>>>> primed
>>>>
>>>>> with the WarToWab conversions, but I suppose it could equally go into
>>>>> the
>>>>> existing management project. Any thoughts?
>>>>>
>>>>> Regards,
>>>>>
>>>>> Valentin
>>>>>
>>>>> On 11 Jan 2010, at 21:04, Jarek Gawor wrote:
>>>>>
>>>>> Valentin,
>>>>>>
>>>>>> Ok, great! Looking forward to your updates. Will the converter be in a
>>>>>> separate module?
>>>>>>
>>>>>> Jarek
>>>>>>
>>>>>> On Mon, Jan 11, 2010 at 3:50 PM, Valentin Mahrwald
>>>>>> <vm...@googlemail.com> wrote:
>>>>>>
>>>>>>>
>>>>>>> Hi Jarek,
>>>>>>>
>>>>>>> I have started just yesterday moving it to the new BundleConverter API
>>>>>>> but I
>>>>>>> haven't come round to raise a JIRA for it yet :) I am quite happy to
>>>>>>> continue with the task.
>>>>>>>
>>>>>>> My idea was to take the code out of the context of the RFC 66 context
>>>>>>>
>>>>>> it
>>>>
>>>>> was
>>>>>>> originally contributed since the RFC 66 bits weren't much more than
>>>>>>> the
>>>>>>> conversion logic anyway.
>>>>>>>
>>>>>>> Valentin
>>>>>>>
>>>>>>> On 11 Jan 2010, at 20:38, Jarek Gawor wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>>
>>>>>>>> Is anyone planning to migrate the WAR to WAB converter donated by IBM
>>>>>>>> to trunk any time soon? If not, and if there are no objections I can
>>>>>>>> work on moving that code to trunk.
>>>>>>>>
>>>>>>>> Jarek
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Alasdair Nottingham
>>>> not@apache.org
>>>>
>>>>
>>
>
Re: Migrating WAR to WAB converter
Posted by Charles Moulliard <cm...@gmail.com>.
Thxs.
I have found info about RFC 66 here :
http://blog.springsource.com/2009/05/27/introduction-to-the-osgi-web-container/
Regards,
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*****************************
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www.linkedin.com/in/charlesmoulliard
Apache Camel Group :
http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
On Tue, Jan 12, 2010 at 10:02 AM, Valentin Mahrwald <
vmahrwald@googlemail.com> wrote:
> Hi Charles,
>
> currently there is no WAB container in Apache Aries. The War to Wab
> converter was initially contributed as a piece towards implementing RFC66
> but no further work has been done on that (as yet?).
>
> However, as part of the application management facilities I have just moved
> this code to the trunk. Now, I don't believe there is any documentation on
> it and even the javadoc is as yet non-existent for the most part. I intend
> to fix at least the latter part in the next week or so (I have raised
> ARIES-115 to cover it).
>
> Regards,
>
> Valentin
>
>
> On 12 Jan 2010, at 08:05, Charles Moulliard wrote:
>
> Hi,
>>
>> Where can we find more info about WAR to WAB converter and added value of
>> WAB container ?
>>
>> Regards,
>>
>> Charles Moulliard
>> Senior Enterprise Architect
>> Apache Camel Committer
>>
>> *****************************
>> blog : http://cmoulliard.blogspot.com
>> twitter : http://twitter.com/cmoulliard
>> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>>
>> Apache Camel Group :
>> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>>
>>
>> On Mon, Jan 11, 2010 at 10:46 PM, Alasdair Nottingham <not@apache.org
>> >wrote:
>>
>> I'm very tempted to suggest putting it out separately so people can
>>> choose not to consume it reasonably easily. Also I think it is likely
>>> that as we progress we may want to use it in more places and having it
>>> slightly to one size should make that simpler.
>>>
>>> Just my 2 cents worth.
>>>
>>> Alasdair
>>>
>>> 2010/1/11 Valentin Mahrwald <vm...@googlemail.com>:
>>>
>>>> My current working set has a new converters project under application
>>>>
>>> primed
>>>
>>>> with the WarToWab conversions, but I suppose it could equally go into
>>>> the
>>>> existing management project. Any thoughts?
>>>>
>>>> Regards,
>>>>
>>>> Valentin
>>>>
>>>> On 11 Jan 2010, at 21:04, Jarek Gawor wrote:
>>>>
>>>> Valentin,
>>>>>
>>>>> Ok, great! Looking forward to your updates. Will the converter be in a
>>>>> separate module?
>>>>>
>>>>> Jarek
>>>>>
>>>>> On Mon, Jan 11, 2010 at 3:50 PM, Valentin Mahrwald
>>>>> <vm...@googlemail.com> wrote:
>>>>>
>>>>>>
>>>>>> Hi Jarek,
>>>>>>
>>>>>> I have started just yesterday moving it to the new BundleConverter API
>>>>>> but I
>>>>>> haven't come round to raise a JIRA for it yet :) I am quite happy to
>>>>>> continue with the task.
>>>>>>
>>>>>> My idea was to take the code out of the context of the RFC 66 context
>>>>>>
>>>>> it
>>>
>>>> was
>>>>>> originally contributed since the RFC 66 bits weren't much more than
>>>>>> the
>>>>>> conversion logic anyway.
>>>>>>
>>>>>> Valentin
>>>>>>
>>>>>> On 11 Jan 2010, at 20:38, Jarek Gawor wrote:
>>>>>>
>>>>>> Hi,
>>>>>>>
>>>>>>> Is anyone planning to migrate the WAR to WAB converter donated by IBM
>>>>>>> to trunk any time soon? If not, and if there are no objections I can
>>>>>>> work on moving that code to trunk.
>>>>>>>
>>>>>>> Jarek
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Alasdair Nottingham
>>> not@apache.org
>>>
>>>
>
Re: Migrating WAR to WAB converter
Posted by Valentin Mahrwald <vm...@googlemail.com>.
Hi Charles,
currently there is no WAB container in Apache Aries. The War to Wab
converter was initially contributed as a piece towards implementing
RFC66 but no further work has been done on that (as yet?).
However, as part of the application management facilities I have just
moved this code to the trunk. Now, I don't believe there is any
documentation on it and even the javadoc is as yet non-existent for
the most part. I intend to fix at least the latter part in the next
week or so (I have raised ARIES-115 to cover it).
Regards,
Valentin
On 12 Jan 2010, at 08:05, Charles Moulliard wrote:
> Hi,
>
> Where can we find more info about WAR to WAB converter and added
> value of
> WAB container ?
>
> Regards,
>
> Charles Moulliard
> Senior Enterprise Architect
> Apache Camel Committer
>
> *****************************
> blog : http://cmoulliard.blogspot.com
> twitter : http://twitter.com/cmoulliard
> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>
> Apache Camel Group :
> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>
>
> On Mon, Jan 11, 2010 at 10:46 PM, Alasdair Nottingham
> <no...@apache.org>wrote:
>
>> I'm very tempted to suggest putting it out separately so people can
>> choose not to consume it reasonably easily. Also I think it is likely
>> that as we progress we may want to use it in more places and having
>> it
>> slightly to one size should make that simpler.
>>
>> Just my 2 cents worth.
>>
>> Alasdair
>>
>> 2010/1/11 Valentin Mahrwald <vm...@googlemail.com>:
>>> My current working set has a new converters project under
>>> application
>> primed
>>> with the WarToWab conversions, but I suppose it could equally go
>>> into the
>>> existing management project. Any thoughts?
>>>
>>> Regards,
>>>
>>> Valentin
>>>
>>> On 11 Jan 2010, at 21:04, Jarek Gawor wrote:
>>>
>>>> Valentin,
>>>>
>>>> Ok, great! Looking forward to your updates. Will the converter be
>>>> in a
>>>> separate module?
>>>>
>>>> Jarek
>>>>
>>>> On Mon, Jan 11, 2010 at 3:50 PM, Valentin Mahrwald
>>>> <vm...@googlemail.com> wrote:
>>>>>
>>>>> Hi Jarek,
>>>>>
>>>>> I have started just yesterday moving it to the new
>>>>> BundleConverter API
>>>>> but I
>>>>> haven't come round to raise a JIRA for it yet :) I am quite
>>>>> happy to
>>>>> continue with the task.
>>>>>
>>>>> My idea was to take the code out of the context of the RFC 66
>>>>> context
>> it
>>>>> was
>>>>> originally contributed since the RFC 66 bits weren't much more
>>>>> than the
>>>>> conversion logic anyway.
>>>>>
>>>>> Valentin
>>>>>
>>>>> On 11 Jan 2010, at 20:38, Jarek Gawor wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Is anyone planning to migrate the WAR to WAB converter donated
>>>>>> by IBM
>>>>>> to trunk any time soon? If not, and if there are no objections
>>>>>> I can
>>>>>> work on moving that code to trunk.
>>>>>>
>>>>>> Jarek
>>>>>
>>>>>
>>>
>>>
>>
>>
>>
>> --
>> Alasdair Nottingham
>> not@apache.org
>>
Re: Migrating WAR to WAB converter
Posted by Charles Moulliard <cm...@gmail.com>.
Hi,
Where can we find more info about WAR to WAB converter and added value of
WAB container ?
Regards,
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*****************************
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www.linkedin.com/in/charlesmoulliard
Apache Camel Group :
http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
On Mon, Jan 11, 2010 at 10:46 PM, Alasdair Nottingham <no...@apache.org>wrote:
> I'm very tempted to suggest putting it out separately so people can
> choose not to consume it reasonably easily. Also I think it is likely
> that as we progress we may want to use it in more places and having it
> slightly to one size should make that simpler.
>
> Just my 2 cents worth.
>
> Alasdair
>
> 2010/1/11 Valentin Mahrwald <vm...@googlemail.com>:
> > My current working set has a new converters project under application
> primed
> > with the WarToWab conversions, but I suppose it could equally go into the
> > existing management project. Any thoughts?
> >
> > Regards,
> >
> > Valentin
> >
> > On 11 Jan 2010, at 21:04, Jarek Gawor wrote:
> >
> >> Valentin,
> >>
> >> Ok, great! Looking forward to your updates. Will the converter be in a
> >> separate module?
> >>
> >> Jarek
> >>
> >> On Mon, Jan 11, 2010 at 3:50 PM, Valentin Mahrwald
> >> <vm...@googlemail.com> wrote:
> >>>
> >>> Hi Jarek,
> >>>
> >>> I have started just yesterday moving it to the new BundleConverter API
> >>> but I
> >>> haven't come round to raise a JIRA for it yet :) I am quite happy to
> >>> continue with the task.
> >>>
> >>> My idea was to take the code out of the context of the RFC 66 context
> it
> >>> was
> >>> originally contributed since the RFC 66 bits weren't much more than the
> >>> conversion logic anyway.
> >>>
> >>> Valentin
> >>>
> >>> On 11 Jan 2010, at 20:38, Jarek Gawor wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> Is anyone planning to migrate the WAR to WAB converter donated by IBM
> >>>> to trunk any time soon? If not, and if there are no objections I can
> >>>> work on moving that code to trunk.
> >>>>
> >>>> Jarek
> >>>
> >>>
> >
> >
>
>
>
> --
> Alasdair Nottingham
> not@apache.org
>
Re: Migrating WAR to WAB converter
Posted by Alasdair Nottingham <no...@apache.org>.
I'm very tempted to suggest putting it out separately so people can
choose not to consume it reasonably easily. Also I think it is likely
that as we progress we may want to use it in more places and having it
slightly to one size should make that simpler.
Just my 2 cents worth.
Alasdair
2010/1/11 Valentin Mahrwald <vm...@googlemail.com>:
> My current working set has a new converters project under application primed
> with the WarToWab conversions, but I suppose it could equally go into the
> existing management project. Any thoughts?
>
> Regards,
>
> Valentin
>
> On 11 Jan 2010, at 21:04, Jarek Gawor wrote:
>
>> Valentin,
>>
>> Ok, great! Looking forward to your updates. Will the converter be in a
>> separate module?
>>
>> Jarek
>>
>> On Mon, Jan 11, 2010 at 3:50 PM, Valentin Mahrwald
>> <vm...@googlemail.com> wrote:
>>>
>>> Hi Jarek,
>>>
>>> I have started just yesterday moving it to the new BundleConverter API
>>> but I
>>> haven't come round to raise a JIRA for it yet :) I am quite happy to
>>> continue with the task.
>>>
>>> My idea was to take the code out of the context of the RFC 66 context it
>>> was
>>> originally contributed since the RFC 66 bits weren't much more than the
>>> conversion logic anyway.
>>>
>>> Valentin
>>>
>>> On 11 Jan 2010, at 20:38, Jarek Gawor wrote:
>>>
>>>> Hi,
>>>>
>>>> Is anyone planning to migrate the WAR to WAB converter donated by IBM
>>>> to trunk any time soon? If not, and if there are no objections I can
>>>> work on moving that code to trunk.
>>>>
>>>> Jarek
>>>
>>>
>
>
--
Alasdair Nottingham
not@apache.org
Re: Migrating WAR to WAB converter
Posted by Valentin Mahrwald <vm...@googlemail.com>.
My current working set has a new converters project under application
primed with the WarToWab conversions, but I suppose it could equally
go into the existing management project. Any thoughts?
Regards,
Valentin
On 11 Jan 2010, at 21:04, Jarek Gawor wrote:
> Valentin,
>
> Ok, great! Looking forward to your updates. Will the converter be in a
> separate module?
>
> Jarek
>
> On Mon, Jan 11, 2010 at 3:50 PM, Valentin Mahrwald
> <vm...@googlemail.com> wrote:
>> Hi Jarek,
>>
>> I have started just yesterday moving it to the new BundleConverter
>> API but I
>> haven't come round to raise a JIRA for it yet :) I am quite happy to
>> continue with the task.
>>
>> My idea was to take the code out of the context of the RFC 66
>> context it was
>> originally contributed since the RFC 66 bits weren't much more than
>> the
>> conversion logic anyway.
>>
>> Valentin
>>
>> On 11 Jan 2010, at 20:38, Jarek Gawor wrote:
>>
>>> Hi,
>>>
>>> Is anyone planning to migrate the WAR to WAB converter donated by
>>> IBM
>>> to trunk any time soon? If not, and if there are no objections I can
>>> work on moving that code to trunk.
>>>
>>> Jarek
>>
>>
Re: Migrating WAR to WAB converter
Posted by Jarek Gawor <jg...@gmail.com>.
Valentin,
Ok, great! Looking forward to your updates. Will the converter be in a
separate module?
Jarek
On Mon, Jan 11, 2010 at 3:50 PM, Valentin Mahrwald
<vm...@googlemail.com> wrote:
> Hi Jarek,
>
> I have started just yesterday moving it to the new BundleConverter API but I
> haven't come round to raise a JIRA for it yet :) I am quite happy to
> continue with the task.
>
> My idea was to take the code out of the context of the RFC 66 context it was
> originally contributed since the RFC 66 bits weren't much more than the
> conversion logic anyway.
>
> Valentin
>
> On 11 Jan 2010, at 20:38, Jarek Gawor wrote:
>
>> Hi,
>>
>> Is anyone planning to migrate the WAR to WAB converter donated by IBM
>> to trunk any time soon? If not, and if there are no objections I can
>> work on moving that code to trunk.
>>
>> Jarek
>
>
Re: Migrating WAR to WAB converter
Posted by Valentin Mahrwald <vm...@googlemail.com>.
Hi Jarek,
I have started just yesterday moving it to the new BundleConverter API
but I haven't come round to raise a JIRA for it yet :) I am quite
happy to continue with the task.
My idea was to take the code out of the context of the RFC 66 context
it was originally contributed since the RFC 66 bits weren't much more
than the conversion logic anyway.
Valentin
On 11 Jan 2010, at 20:38, Jarek Gawor wrote:
> Hi,
>
> Is anyone planning to migrate the WAR to WAB converter donated by IBM
> to trunk any time soon? If not, and if there are no objections I can
> work on moving that code to trunk.
>
> Jarek