You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by mfs <fa...@gmail.com> on 2008/01/30 02:29:56 UTC

Mounting strategies for shared components bundled in a jar ?

Guys,

How would i go about mounting the pages bundled in a jar that are being
re-used by different web apps. 

I don't want to mount them in every web-application that uses them, rather
would prefer keeping the mounting logic in the shared library itself..

Any ideas ? 
-- 
View this message in context: http://www.nabble.com/Mounting-strategies-for-shared-components-bundled-in-a-jar---tp15173739p15173739.html
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Using IInitializer and wicket.properties with Databinder

Posted by Johan Compagner <jc...@gmail.com>.
yes init is called before i do see this:


// Call internal init method of web application for default

// initialization

webApplication.internalInit();

// Call init method of web application

webApplication.init();

// We initialize components here rather than in the constructor or

// in the internal init, because in the init method class aliases

// can be added, that would be used in installing resources in the

// component.

webApplication.initializeComponents();
Look that last part... its meant this way because class alliasses can be
added that are then being used again in the iinitializers

johan



On Feb 4, 2008 3:06 AM, Daniel Walmsley <da...@firesyde.com> wrote:

>  I am currently having great fun (no, I'm not being sarcastic) with
> Wicket's IInitializer plugin mechanism, using it to plug additional
> functionality into a basic CMS framework (e.g. news feeds, video upload,
> etc). Just hit a brick wall though - it seems as through the initializers
> are called too late for me to configure annotated entities for Databinder's
> Hibernate session (which makes sense, I suppose - you need to give the
> WebApplication a chance to run init() before all your other components
> register themselves).
>
> Has anyone else tried to plug data-bound sub-projects into a Wicket
> project? How did you register the plug-in's persistent entities without
> recreating the entire SessionFactory after all the Iinitializers have been
> called? For that matter, how do you _know_ when all the IInitializers have
> been called?
>
> Thanks,
> Dan
>
>   *     Daniel Walmsley
> Director, Firesyde <http://firesyde.com/>
> e: dan@firesyde.com
> m: +61404864141
> *
>
>
>

Using IInitializer and wicket.properties with Databinder

Posted by Daniel Walmsley <da...@firesyde.com>.
I am currently having great fun (no, I'm not being sarcastic) with  
Wicket's IInitializer plugin mechanism, using it to plug additional  
functionality into a basic CMS framework (e.g. news feeds, video  
upload, etc). Just hit a brick wall though - it seems as through the  
initializers are called too late for me to configure annotated  
entities for Databinder's Hibernate session (which makes sense, I  
suppose - you need to give the WebApplication a chance to run init()  
before all your other components register themselves).

Has anyone else tried to plug data-bound sub-projects into a Wicket  
project? How did you register the plug-in's persistent entities  
without recreating the entire SessionFactory after all the  
Iinitializers have been called? For that matter, how do you _know_  
when all the IInitializers have been called?

Thanks,
Dan

Daniel Walmsley
Director, Firesyde
e: dan@firesyde.com
m: +61404864141




Re: Mounting strategies for shared components bundled in a jar ?

Posted by Igor Vaynberg <ig...@gmail.com>.
see IInitializer and its javadoc, you can write one that mounts the
pages and include in the jar that contains the pages. as long as that
jar is on the classpath those pages will get mounted.

-igor


On Jan 29, 2008 5:29 PM, mfs <fa...@gmail.com> wrote:
>
> Guys,
>
> How would i go about mounting the pages bundled in a jar that are being
> re-used by different web apps.
>
> I don't want to mount them in every web-application that uses them, rather
> would prefer keeping the mounting logic in the shared library itself..
>
> Any ideas ?
> --
> View this message in context: http://www.nabble.com/Mounting-strategies-for-shared-components-bundled-in-a-jar---tp15173739p15173739.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Mounting strategies for shared components bundled in a jar ?

Posted by mfs <fa...@gmail.com>.
Thanks...does the job..

mfs wrote:
> 
> Guys,
> 
> How would i go about mounting the pages bundled in a jar that are being
> re-used by different web apps. 
> 
> I don't want to mount them in every web-application that uses them, rather
> would prefer keeping the mounting logic in the shared library itself..
> 
> Any ideas ? 
> 

-- 
View this message in context: http://www.nabble.com/Mounting-strategies-for-shared-components-bundled-in-a-jar---tp15173739p15188775.html
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org