#: Johan Compagner changed the world a bit at a time by saying on  11/14/2005 
12:28 PM :#
why would you use more then one application object inside 1 web application?
Examples is just the strange one that woudn't happen normally


I have given the reasons in my first mail:

1/ able to configure different render strategies for parts of the application (f.e. you can have some read-only access in which case I don't see why not to use the ONE_PASS_RENDER)
2/ to be able to handle some kind of namespaces.

Still my question is valid, needing to better understand the reasons behind 1 application vs multiple applications :-).

./alex
--
.w( the_mindstorm )p.


On 11/14/05, Alexandru Popescu <[EMAIL PROTECTED]> wrote:

#: Johan Compagner changed the world a bit at a time by saying on
11/14/2005 12:04 PM :#
> it is recommended but not really a requirement
> (it works for the examples project just fine to have multiply
Applications
> in one WebApplication)
>

Is there anything else than what I mentioned when deciding which way to
go?

./alex
--
.w( the_mindstorm )p.

>
> On 11/13/05, Alexandru Popescu <[EMAIL PROTECTED]>
wrote:
>>
>> #: Martijn Dashorst changed the world a bit at a time by saying on
>> 8/17/2005 9:41 PM :#
>> > Huy Do wrote:
>> >
>> >> Perfect sense. Thanks Igor and Gili for your help.
>> >>
>> >> It was just a bit confusing looking at all the examples (cdapp etc)
>> >> and seeing the way things are structured.
>> >>
>> > Yeah, I can see that it is confusing. The examples are in fact
different
>> > applications put into one war. Normally you'd only have one
Application
>> > object for your WAR.
>> >
>> > Martijn
>> >
>>
>> Sorry for reviving this quite old thread, but it was the only reference
I
>> could find on Wicket
>> application concept and still I cannot find a good explanation for this
>> :-S.
>>
>> It looks to me that the decission upon how you organize the web
>> application from the pov of
>> WebApplications must take into account:
>>
>> i/ the ApplicationSettings you are using (and probably the most
important
>> is the rendering strategy)
>> ii/ defining some kind of namespaces (f.e. <context>/users for user
>> management, <context>/roles for
>> roles management, etc.).
>>
>> Does this make sense or it is mandatory/required/recommended to always
use
>> a single WebApplication
>> for the whole web application?
>>
>> ./alex
>> --
>> .w( the_mindstorm )p.
>>
>>



-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to