You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Peter Courcoux <pe...@courcoux.biz> on 2003/09/17 13:00:21 UTC
Locating components in a webapp environment
Hi all,
I'm looking at using merlin in a webapp environment and considering the
location of the set of components that merlin should manage. Is there
some standard on this?
I'm considering a hierarchy something like :-
WEB-INF/avalon-components/component1/classes/BLOCK-INF/block.xml
WEB-INF/avalon-components/component1/classes/package/component1.class
WEB-INF/avalon-components/component1/classes/package/component1.xinfo
WEB-INF/avalon-components/component2/classes/BLOCK-INF/block.xml
WEB-INF/avalon-components/component2/classes/package/component2.class
WEB-INF/avalon-components/component2/classes/package/component2.xinfo
WEB-INF/avalon-components/component3/component3-1.0.jar
I would anticipate that the root, in this example
WEB-INF/avalon-components, could be an initialization param set in the
web.xml file.
Has anyone any thoughts, preferences or comments on this.
Regards,
Peter
--
Peter Courcoux <pe...@courcoux.biz>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Locating components in a webapp environment
Posted by Stephen McConnell <mc...@apache.org>.
Peter Courcoux wrote:
>Hi all,
>
>I'm looking at using merlin in a webapp environment and considering the
>location of the set of components that merlin should manage. Is there
>some standard on this?
>
>I'm considering a hierarchy something like :-
>
>WEB-INF/avalon-components/component1/classes/BLOCK-INF/block.xml
>WEB-INF/avalon-components/component1/classes/package/component1.class
>WEB-INF/avalon-components/component1/classes/package/component1.xinfo
>WEB-INF/avalon-components/component2/classes/BLOCK-INF/block.xml
>WEB-INF/avalon-components/component2/classes/package/component2.class
>WEB-INF/avalon-components/component2/classes/package/component2.xinfo
>
Looks fine.
>WEB-INF/avalon-components/component3/component3-1.0.jar
>
This one will be problamatic if the deployment path is a jar: url. If
its a file url then everything will be fine. The problem is that the
URLClassLoader in the JVM does not handle jar files embedded in a jar
file using the jar: protocol.
>
>I would anticipate that the root, in this example
>WEB-INF/avalon-components, could be an initialization param set in the
>web.xml file.
>
>Has anyone any thoughts, preferences or comments on this.
>
>
I'm try to think ahead in terms of seperating the merlin embeded kernel
the web application - but thoughts are a little too random just at the
momement. I'm confident that a lot of things will become clearer as
start dealing with implementations.
Cheers, Steve.
>Regards,
>
>Peter
>
>
>
--
Stephen J. McConnell
mailto:mcconnell@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Locating components in a webapp environment
Posted by Peter Courcoux <pe...@courcoux.biz>.
Niclas,
Thanks. I'll review the cocoon lists.
Peter
On Wed, 2003-09-17 at 12:22, Niclas Hedhman wrote:
> On Wednesday 17 September 2003 19:00, Peter Courcoux wrote:
> > Hi all,
> >
> > I'm looking at using merlin in a webapp environment and considering the
> > location of the set of components that merlin should manage. Is there
> > some standard on this?
> >
> > I'm considering a hierarchy something like :-
> >
> > WEB-INF/avalon-components/component1/classes/BLOCK-INF/block.xml
> > WEB-INF/avalon-components/component1/classes/package/component1.class
> > WEB-INF/avalon-components/component1/classes/package/component1.xinfo
> > WEB-INF/avalon-components/component2/classes/BLOCK-INF/block.xml
> > WEB-INF/avalon-components/component2/classes/package/component2.class
> > WEB-INF/avalon-components/component2/classes/package/component2.xinfo
> > WEB-INF/avalon-components/component3/component3-1.0.jar
> >
> > I would anticipate that the root, in this example
> > WEB-INF/avalon-components, could be an initialization param set in the
> > web.xml file.
> >
> > Has anyone any thoughts, preferences or comments on this.
>
> IIANM, Cocoon is working on their on block system, and have or have had this
> discussion. I think it is a good idea to co-ordinate between the projects.
>
> Niclas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
> For additional commands, e-mail: dev-help@avalon.apache.org
--
Peter Courcoux <pe...@courcoux.biz>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Locating components in a webapp environment
Posted by Geoff Howard <gh...@apache.org>.
Stephen McConnell wrote:
>
>
> Niclas Hedhman wrote:
>
>> On Wednesday 17 September 2003 19:00, Peter Courcoux wrote:
>>
>>
>>> Hi all,
>>>
>>> I'm looking at using merlin in a webapp environment and considering the
>>> location of the set of components that merlin should manage. Is there
>>> some standard on this?
>>>
>>> I'm considering a hierarchy something like :-
>>>
>>> WEB-INF/avalon-components/component1/classes/BLOCK-INF/block.xml
>>> WEB-INF/avalon-components/component1/classes/package/component1.class
>>> WEB-INF/avalon-components/component1/classes/package/component1.xinfo
>>> WEB-INF/avalon-components/component2/classes/BLOCK-INF/block.xml
>>> WEB-INF/avalon-components/component2/classes/package/component2.class
>>> WEB-INF/avalon-components/component2/classes/package/component2.xinfo
>>> WEB-INF/avalon-components/component3/component3-1.0.jar
>>>
>>> I would anticipate that the root, in this example
>>> WEB-INF/avalon-components, could be an initialization param set in the
>>> web.xml file.
>>>
>>> Has anyone any thoughts, preferences or comments on this.
>>>
>>
>>
>> IIANM, Cocoon is working on their on block system, and have or have
>> had this discussion. I think it is a good idea to co-ordinate between
>> the projects.
>>
>
> I agree.
>
> I've been browsing the cocoon list - and yes - there is some
> significant overlaps. The threads related to the Cocoon block
> defintion share many of the same concerns already addressed in the
> composite containment meta model. There is also the notion of
> packaging and inheritance which is included in the Cocoon notion of a
> block but not in the Merlin notion or a block. Under Merlin the
> packaging model is a bar file that is basically a fragment of a
> repository. Merlin does not have a packaging descriptor (at least not
> version 3.0) but I've been looking closely at the jnlp descriptors and
> I think we could eventually arrive at a scenario where a Merlin bar
> file is handled as a jnlp executable application (but keep in mind
> that there is a lot of playing around on the bootstrap side of things
> to make thisb happen).
> Stephen.
As a Cocoon developer and avalon lurker, I'll echo the sentiment that
coordination would be great. It's not clear to me and probably at least
some others how close the current implentation(s) are to meeting this
need as is now. Any help figuring out what can be done now or how to
position ourselves to benefit from what will be possible in the future
will be appreciated.
Geoff Howard
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Locating components in a webapp environment
Posted by Stephen McConnell <mc...@apache.org>.
Niclas Hedhman wrote:
>On Wednesday 17 September 2003 19:00, Peter Courcoux wrote:
>
>
>>Hi all,
>>
>>I'm looking at using merlin in a webapp environment and considering the
>>location of the set of components that merlin should manage. Is there
>>some standard on this?
>>
>>I'm considering a hierarchy something like :-
>>
>>WEB-INF/avalon-components/component1/classes/BLOCK-INF/block.xml
>>WEB-INF/avalon-components/component1/classes/package/component1.class
>>WEB-INF/avalon-components/component1/classes/package/component1.xinfo
>>WEB-INF/avalon-components/component2/classes/BLOCK-INF/block.xml
>>WEB-INF/avalon-components/component2/classes/package/component2.class
>>WEB-INF/avalon-components/component2/classes/package/component2.xinfo
>>WEB-INF/avalon-components/component3/component3-1.0.jar
>>
>>I would anticipate that the root, in this example
>>WEB-INF/avalon-components, could be an initialization param set in the
>>web.xml file.
>>
>>Has anyone any thoughts, preferences or comments on this.
>>
>>
>
>IIANM, Cocoon is working on their on block system, and have or have had this
>discussion. I think it is a good idea to co-ordinate between the projects.
>
I agree.
I've been browsing the cocoon list - and yes - there is some significant
overlaps. The threads related to the Cocoon block defintion share many
of the same concerns already addressed in the composite containment meta
model. There is also the notion of packaging and inheritance which is
included in the Cocoon notion of a block but not in the Merlin notion or
a block. Under Merlin the packaging model is a bar file that is
basically a fragment of a repository. Merlin does not have a packaging
descriptor (at least not version 3.0) but I've been looking closely at
the jnlp descriptors and I think we could eventually arrive at a
scenario where a Merlin bar file is handled as a jnlp executable
application (but keep in mind that there is a lot of playing around on
the bootstrap side of things to make thisb happen).
Stephen.
--
Stephen J. McConnell
mailto:mcconnell@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Locating components in a webapp environment
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Wednesday 17 September 2003 19:00, Peter Courcoux wrote:
> Hi all,
>
> I'm looking at using merlin in a webapp environment and considering the
> location of the set of components that merlin should manage. Is there
> some standard on this?
>
> I'm considering a hierarchy something like :-
>
> WEB-INF/avalon-components/component1/classes/BLOCK-INF/block.xml
> WEB-INF/avalon-components/component1/classes/package/component1.class
> WEB-INF/avalon-components/component1/classes/package/component1.xinfo
> WEB-INF/avalon-components/component2/classes/BLOCK-INF/block.xml
> WEB-INF/avalon-components/component2/classes/package/component2.class
> WEB-INF/avalon-components/component2/classes/package/component2.xinfo
> WEB-INF/avalon-components/component3/component3-1.0.jar
>
> I would anticipate that the root, in this example
> WEB-INF/avalon-components, could be an initialization param set in the
> web.xml file.
>
> Has anyone any thoughts, preferences or comments on this.
IIANM, Cocoon is working on their on block system, and have or have had this
discussion. I think it is a good idea to co-ordinate between the projects.
Niclas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org