again, the trick is adding references to a library without coding it.
Tapestry defines in the hivemind registry the service point :

tapestry.parse.SpecificationSource

which is responsible for reading the specification from files - I would
think that to make dynamic libraries load, you need to implement this
service a new:

create a single library which is "dynamic", all other libraries will
delegate to the tapestry implementation.

for your dynamic library, create a specification which is dynamically
generated according to a hivemind configuration point.

Never done this, but was often thinking about it...

Cheers,
Ron


Pedro Abelleira Seco wrote:
> Thanks for your response.
> 
> What I have in mind is to be in the situation of
> having a general web application with a common set of
> services and components (including the a general
> Border, etc.) and getting different contractors to
> develop different parts of the app in parallel without
> having to touch any single file in the main app or any
> other plugin to put them into production.
> 
> Then the warranty and support agreement from each
> contractor would be clearly separated and future
> modifications or additions of new plugins could be
> done by the best bidder.
> 
> Do you think the technical possibilities are enough
> for such scenario?
> 
> Cheers
> Pedro
> 
> 
> --- Ron Piterman <[EMAIL PROTECTED]> escribió:
> 
>> It could be done, but above all needs restarting of
>> the servlet
>> container for every change-
>>
>> Since hivemind lets you peekup configuration from
>> every jar on the
>> classpath, configuration isn't an issue.
>>
>> However, adding a library without making an explicit
>> reference to it
>> should be quite difficult - You may need to create a
>> custom Library spec
>> source.
>>
>> Cheers,
>> Ron
>>
>>
>> Pedro Abelleira Seco wrote:
>>> Hello all,
>>>
>>> I has been a happy user of Tapestry 3 and since
>> then
>>> stepped out of web development for a while. But I
>> have
>>> to return there at some point.
>>>
>>> I would like to be able to do in a web application
>> the
>>> same kind of things that are possible in client
>>> applications with respect to plugins.
>>>
>>> The idea would be to be able to drop a library in
>> the
>>> classpath which contained components and _pages_
>> and
>>> that could:
>>>
>>> 1.- Add entries (links) to a menu in a page of the
>>> application.
>>> 2.- When the user clicks on one of those links to
>>> display the corresponding page, which would be
>> located
>>> in the library.
>>>
>>> Do you think that would be possible with Tapestry?
>>>
>>> Thank you
>>> Pedro
>>>
>>>
>>>
>>>     
>>>     
>>>             
>>> ______________________________________________ 
>>> LLama Gratis a cualquier PC del Mundo. 
>>> Llamadas a fijos y móviles desde 1 céntimo por
>> minuto. 
>>> http://es.voice.yahoo.com
>>>
>>>
> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail:
>> [EMAIL PROTECTED]
>>> For additional commands, e-mail:
>> [EMAIL PROTECTED]
>>>
>>
>>
> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> [EMAIL PROTECTED]
>> For additional commands, e-mail:
>> [EMAIL PROTECTED]
>>
>>
> 
> 
> 
>               
> ______________________________________________ 
> LLama Gratis a cualquier PC del Mundo. 
> Llamadas a fijos y móviles desde 1 céntimo por minuto. 
> http://es.voice.yahoo.com
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to