Re: Modular Application
@James
Everything works if I don't have a sub-class of WebPage outside the war
project.
@Pedro
>From command line or on the parent project I get the same error.
Also deleted the org/apache/wicket directory out of my .m2 repository and
re-downloaded.
On Tue, Oct 13, 2009 at 4:19 PM, Pedro Santos wrote:
> Isn't it the case for you manually run mvn install on your parent project?
> Your local repository may have old .class bytecodes
>
> On Tue, Oct 13, 2009 at 5:11 PM, Ben Tilford wrote:
>
> > No base page is in a common module (probably will be used by more than 1
> > app
> > in the end).
> >
> > The wicket dependency is declared in a parent project (I've tried moving
> > thinking maybe there was something odd going on there). Using Netbeans I
> > can
> > see the dependency is resolved and on the classpath. Looking at the
> > dependency graph there is only 1 version of wicket in any of the modules
> > and
> > they all have 1.4.2. I did see a conflict with log4j versions but after
> > fixing that I'm still getting the same compilation error.
> >
> > To me its a bit odd that its the add method of WebPage that can't be
> found.
> >
> > On Tue, Oct 13, 2009 at 4:00 PM, James Carman
> > wrote:
> >
> > > Is BasePage in your webapp module and you have other pages in other
> > > modules? If so, you're going to have a circular dependency. What you
> > > could do is set up a web-commons module which contains stuff like
> > > BasePage and have your other modules use that. Then, your web module
> > > declares all of them as dependencies. That's what we do.
> > >
> > > On Tue, Oct 13, 2009 at 3:36 PM, Ben Tilford
> > wrote:
> > > > Something other than?
> > > >
> > > >org.apache.wicket
> > > >wicket
> > > >${wicket.version}
> > > >
> > > >
> > > >
> > > >
> > > > On Tue, Oct 13, 2009 at 3:30 PM, Igor Vaynberg <
> > igor.vaynb...@gmail.com
> > > >wrote:
> > > >
> > > >> your module still needs a wicket dependency
> > > >>
> > > >> -igor
> > > >>
> > > >> On Tue, Oct 13, 2009 at 12:20 PM, Ben Tilford >
> > > >> wrote:
> > > >> > Are there any examples of a modular wicket application? I'm
> > > specifically
> > > >> > having trouble getting maven to compile a jar which contains a
> > > sub-class
> > > >> of
> > > >> > WebPage.
> > > >> >
> > > >> > Using 1.4.2 and have attempted with 1.4.1/1.4.0, packaging a Panel
> > > etc...
> > > >> > all seems to work fine.
> > > >> >
> > > >> > demo/locator/web/components/BasePage.java:[17,8] cannot find
> symbol
> > > >> >> symbol : method add(org.apache.wicket.markup.html.basic.Label)
> > > >> >> location: class demo.locator.web.components.BasePage
> > > >> >>
> > > >> >
> > > >>
> > > >>
> -
> > > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > > >> For additional commands, e-mail: users-h...@wicket.apache.org
> > > >>
> > > >>
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > > For additional commands, e-mail: users-h...@wicket.apache.org
> > >
> > >
> >
>
>
>
> --
> Pedro Henrique Oliveira dos Santos
>
Re: Modular Application
Isn't it the case for you manually run mvn install on your parent project?
Your local repository may have old .class bytecodes
On Tue, Oct 13, 2009 at 5:11 PM, Ben Tilford wrote:
> No base page is in a common module (probably will be used by more than 1
> app
> in the end).
>
> The wicket dependency is declared in a parent project (I've tried moving
> thinking maybe there was something odd going on there). Using Netbeans I
> can
> see the dependency is resolved and on the classpath. Looking at the
> dependency graph there is only 1 version of wicket in any of the modules
> and
> they all have 1.4.2. I did see a conflict with log4j versions but after
> fixing that I'm still getting the same compilation error.
>
> To me its a bit odd that its the add method of WebPage that can't be found.
>
> On Tue, Oct 13, 2009 at 4:00 PM, James Carman
> wrote:
>
> > Is BasePage in your webapp module and you have other pages in other
> > modules? If so, you're going to have a circular dependency. What you
> > could do is set up a web-commons module which contains stuff like
> > BasePage and have your other modules use that. Then, your web module
> > declares all of them as dependencies. That's what we do.
> >
> > On Tue, Oct 13, 2009 at 3:36 PM, Ben Tilford
> wrote:
> > > Something other than?
> > >
> > >org.apache.wicket
> > >wicket
> > >${wicket.version}
> > >
> > >
> > >
> > >
> > > On Tue, Oct 13, 2009 at 3:30 PM, Igor Vaynberg <
> igor.vaynb...@gmail.com
> > >wrote:
> > >
> > >> your module still needs a wicket dependency
> > >>
> > >> -igor
> > >>
> > >> On Tue, Oct 13, 2009 at 12:20 PM, Ben Tilford
> > >> wrote:
> > >> > Are there any examples of a modular wicket application? I'm
> > specifically
> > >> > having trouble getting maven to compile a jar which contains a
> > sub-class
> > >> of
> > >> > WebPage.
> > >> >
> > >> > Using 1.4.2 and have attempted with 1.4.1/1.4.0, packaging a Panel
> > etc...
> > >> > all seems to work fine.
> > >> >
> > >> > demo/locator/web/components/BasePage.java:[17,8] cannot find symbol
> > >> >> symbol : method add(org.apache.wicket.markup.html.basic.Label)
> > >> >> location: class demo.locator.web.components.BasePage
> > >> >>
> > >> >
> > >>
> > >> -
> > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > >> For additional commands, e-mail: users-h...@wicket.apache.org
> > >>
> > >>
> > >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
>
--
Pedro Henrique Oliveira dos Santos
Re: Modular Application
Does the maven build work?
On Tue, Oct 13, 2009 at 4:11 PM, Ben Tilford wrote:
> No base page is in a common module (probably will be used by more than 1 app
> in the end).
>
> The wicket dependency is declared in a parent project (I've tried moving
> thinking maybe there was something odd going on there). Using Netbeans I can
> see the dependency is resolved and on the classpath. Looking at the
> dependency graph there is only 1 version of wicket in any of the modules and
> they all have 1.4.2. I did see a conflict with log4j versions but after
> fixing that I'm still getting the same compilation error.
>
> To me its a bit odd that its the add method of WebPage that can't be found.
>
> On Tue, Oct 13, 2009 at 4:00 PM, James Carman
> wrote:
>
>> Is BasePage in your webapp module and you have other pages in other
>> modules? If so, you're going to have a circular dependency. What you
>> could do is set up a web-commons module which contains stuff like
>> BasePage and have your other modules use that. Then, your web module
>> declares all of them as dependencies. That's what we do.
>>
>> On Tue, Oct 13, 2009 at 3:36 PM, Ben Tilford wrote:
>> > Something other than?
>> >
>> > org.apache.wicket
>> > wicket
>> > ${wicket.version}
>> >
>> >
>> >
>> >
>> > On Tue, Oct 13, 2009 at 3:30 PM, Igor Vaynberg > >wrote:
>> >
>> >> your module still needs a wicket dependency
>> >>
>> >> -igor
>> >>
>> >> On Tue, Oct 13, 2009 at 12:20 PM, Ben Tilford
>> >> wrote:
>> >> > Are there any examples of a modular wicket application? I'm
>> specifically
>> >> > having trouble getting maven to compile a jar which contains a
>> sub-class
>> >> of
>> >> > WebPage.
>> >> >
>> >> > Using 1.4.2 and have attempted with 1.4.1/1.4.0, packaging a Panel
>> etc...
>> >> > all seems to work fine.
>> >> >
>> >> > demo/locator/web/components/BasePage.java:[17,8] cannot find symbol
>> >> >> symbol : method add(org.apache.wicket.markup.html.basic.Label)
>> >> >> location: class demo.locator.web.components.BasePage
>> >> >>
>> >> >
>> >>
>> >> -
>> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> >> For additional commands, e-mail: users-h...@wicket.apache.org
>> >>
>> >>
>> >
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Modular Application
No base page is in a common module (probably will be used by more than 1 app
in the end).
The wicket dependency is declared in a parent project (I've tried moving
thinking maybe there was something odd going on there). Using Netbeans I can
see the dependency is resolved and on the classpath. Looking at the
dependency graph there is only 1 version of wicket in any of the modules and
they all have 1.4.2. I did see a conflict with log4j versions but after
fixing that I'm still getting the same compilation error.
To me its a bit odd that its the add method of WebPage that can't be found.
On Tue, Oct 13, 2009 at 4:00 PM, James Carman
wrote:
> Is BasePage in your webapp module and you have other pages in other
> modules? If so, you're going to have a circular dependency. What you
> could do is set up a web-commons module which contains stuff like
> BasePage and have your other modules use that. Then, your web module
> declares all of them as dependencies. That's what we do.
>
> On Tue, Oct 13, 2009 at 3:36 PM, Ben Tilford wrote:
> > Something other than?
> >
> >org.apache.wicket
> >wicket
> >${wicket.version}
> >
> >
> >
> >
> > On Tue, Oct 13, 2009 at 3:30 PM, Igor Vaynberg >wrote:
> >
> >> your module still needs a wicket dependency
> >>
> >> -igor
> >>
> >> On Tue, Oct 13, 2009 at 12:20 PM, Ben Tilford
> >> wrote:
> >> > Are there any examples of a modular wicket application? I'm
> specifically
> >> > having trouble getting maven to compile a jar which contains a
> sub-class
> >> of
> >> > WebPage.
> >> >
> >> > Using 1.4.2 and have attempted with 1.4.1/1.4.0, packaging a Panel
> etc...
> >> > all seems to work fine.
> >> >
> >> > demo/locator/web/components/BasePage.java:[17,8] cannot find symbol
> >> >> symbol : method add(org.apache.wicket.markup.html.basic.Label)
> >> >> location: class demo.locator.web.components.BasePage
> >> >>
> >> >
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >> For additional commands, e-mail: users-h...@wicket.apache.org
> >>
> >>
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
Re: Modular Application
Is BasePage in your webapp module and you have other pages in other
modules? If so, you're going to have a circular dependency. What you
could do is set up a web-commons module which contains stuff like
BasePage and have your other modules use that. Then, your web module
declares all of them as dependencies. That's what we do.
On Tue, Oct 13, 2009 at 3:36 PM, Ben Tilford wrote:
> Something other than?
>
> org.apache.wicket
> wicket
> ${wicket.version}
>
>
>
>
> On Tue, Oct 13, 2009 at 3:30 PM, Igor Vaynberg wrote:
>
>> your module still needs a wicket dependency
>>
>> -igor
>>
>> On Tue, Oct 13, 2009 at 12:20 PM, Ben Tilford
>> wrote:
>> > Are there any examples of a modular wicket application? I'm specifically
>> > having trouble getting maven to compile a jar which contains a sub-class
>> of
>> > WebPage.
>> >
>> > Using 1.4.2 and have attempted with 1.4.1/1.4.0, packaging a Panel etc...
>> > all seems to work fine.
>> >
>> > demo/locator/web/components/BasePage.java:[17,8] cannot find symbol
>> >> symbol : method add(org.apache.wicket.markup.html.basic.Label)
>> >> location: class demo.locator.web.components.BasePage
>> >>
>> >
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Modular Application
Looks like you have an project dependency compiled with other Wicket
version. That can to be easy detected with eclipse maven pluging, using the
hierarchy view
On Tue, Oct 13, 2009 at 4:36 PM, Ben Tilford wrote:
> Something other than?
>
>org.apache.wicket
>wicket
>${wicket.version}
>
>
>
>
> On Tue, Oct 13, 2009 at 3:30 PM, Igor Vaynberg >wrote:
>
> > your module still needs a wicket dependency
> >
> > -igor
> >
> > On Tue, Oct 13, 2009 at 12:20 PM, Ben Tilford
> > wrote:
> > > Are there any examples of a modular wicket application? I'm
> specifically
> > > having trouble getting maven to compile a jar which contains a
> sub-class
> > of
> > > WebPage.
> > >
> > > Using 1.4.2 and have attempted with 1.4.1/1.4.0, packaging a Panel
> etc...
> > > all seems to work fine.
> > >
> > > demo/locator/web/components/BasePage.java:[17,8] cannot find symbol
> > >> symbol : method add(org.apache.wicket.markup.html.basic.Label)
> > >> location: class demo.locator.web.components.BasePage
> > >>
> > >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
>
--
Pedro Henrique Oliveira dos Santos
Re: Modular Application
Something other than?
org.apache.wicket
wicket
${wicket.version}
On Tue, Oct 13, 2009 at 3:30 PM, Igor Vaynberg wrote:
> your module still needs a wicket dependency
>
> -igor
>
> On Tue, Oct 13, 2009 at 12:20 PM, Ben Tilford
> wrote:
> > Are there any examples of a modular wicket application? I'm specifically
> > having trouble getting maven to compile a jar which contains a sub-class
> of
> > WebPage.
> >
> > Using 1.4.2 and have attempted with 1.4.1/1.4.0, packaging a Panel etc...
> > all seems to work fine.
> >
> > demo/locator/web/components/BasePage.java:[17,8] cannot find symbol
> >> symbol : method add(org.apache.wicket.markup.html.basic.Label)
> >> location: class demo.locator.web.components.BasePage
> >>
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
Re: Modular Application
your module still needs a wicket dependency -igor On Tue, Oct 13, 2009 at 12:20 PM, Ben Tilford wrote: > Are there any examples of a modular wicket application? I'm specifically > having trouble getting maven to compile a jar which contains a sub-class of > WebPage. > > Using 1.4.2 and have attempted with 1.4.1/1.4.0, packaging a Panel etc... > all seems to work fine. > > demo/locator/web/components/BasePage.java:[17,8] cannot find symbol >> symbol : method add(org.apache.wicket.markup.html.basic.Label) >> location: class demo.locator.web.components.BasePage >> > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Modular Application
Are there any examples of a modular wicket application? I'm specifically having trouble getting maven to compile a jar which contains a sub-class of WebPage. Using 1.4.2 and have attempted with 1.4.1/1.4.0, packaging a Panel etc... all seems to work fine. demo/locator/web/components/BasePage.java:[17,8] cannot find symbol > symbol : method add(org.apache.wicket.markup.html.basic.Label) > location: class demo.locator.web.components.BasePage >
Re: How to deal with session in a modular application?
hehe, after think more about it I found a solution. As I'm using Google Guice, I can create objects in Session scope, so instead of have a wicket session I can have a session object per module, something like SecuritySession and inject this object when I need it, I just need to figure out that I have to clean this object when the data inside of it isn't necessary anymore, in this case it wont be necessary because the session will be invalidated when the user logs off. Thanks anyway, Eduardo S. Nunes On Tue, Apr 21, 2009 at 8:26 PM, Eduardo Nunes wrote: > Hello guys, > > I'm developing a framework to build modular applications with > Guice+Wicket+Hibernate. My main problem now is how I must deal with > objects that must be saved in session in a modular environment. I want > some suggestions or tips to do it without dealing directly with the > httpsession. An example is a security module, it will define an > authentication service, authorization service and a security entity to > store user/password/roles in the database. This module must keep the > current user in the session. I don't want to create a wicket session > class that is directly connected to this module. Do you have some > suggestions? > > Thanks, > Eduardo S. Nunes > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
How to deal with session in a modular application?
Hello guys, I'm developing a framework to build modular applications with Guice+Wicket+Hibernate. My main problem now is how I must deal with objects that must be saved in session in a modular environment. I want some suggestions or tips to do it without dealing directly with the httpsession. An example is a security module, it will define an authentication service, authorization service and a security entity to store user/password/roles in the database. This module must keep the current user in the session. I don't want to create a wicket session class that is directly connected to this module. Do you have some suggestions? Thanks, Eduardo S. Nunes - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
