You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Ryan McKinley <ry...@gmail.com> on 2009/03/24 20:33:39 UTC

wicketstuff / ki / jsecurity

Hi-

I've been looking to integrate a complex security model with wicket --  
jsecurity seems really good.  I tried messing with: http://code.google.com/p/wicket-jsecurity/

This appears to be a starting place, but does not have any running  
example.

In an effort to get things running (and learn JSecurity) i took that +  
wicket-auth-roles and tried to make a functioning core + example.   
I've got something running and would love to share it...

Should I post this to the google code site?

It makes more sense (to me) if we keep it in the wicketstuff repos --  
that way we get the benefit of Jeremy's work to make wickettuff-core  
much cleaner.

Thoughts?

Ryan



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


RE: newbie question: HTTP 404 on the quickstart project

Posted by "Chenini, Mohamed " <MC...@geico.com>.
Thanks for this advice. I agree I should perhaps switch to "Wicket in Action" since I do have the entire book in addition to the chapter 15 bonus.

Regards,
Mohamed

-----Original Message-----
From: Martijn Dashorst [mailto:martijn.dashorst@gmail.com] 
Sent: Wednesday, March 25, 2009 9:29 AM
To: users@wicket.apache.org
Subject: Re: newbie question: HTTP 404 on the quickstart project

Pro Wicket has been written during Wicket 1.2 availability. Therefore
you should not expect everything to work directly. If you use the
wicket-quickstart download from Wicket 1.2 the example should match.

Instead of using this part from Pro Wicket, why don't you download the
free bonus chapter from Wicket in Action, and use that as your
starting point: it is up to date regarding Wicket 1.3, and has an
explanation for both ant and maven users.

You can download the bonus chapter (and 2 other free chapters) from
the official companion site to Wicket in Action:
http://wicketinaction.com/downloads/

Martijn

On Tue, Mar 24, 2009 at 9:57 PM, Chenini, Mohamed <MC...@geico.com> wrote:
> OK! I guess I was mixing two examples scenarios:
> - One from the Wicket website (quickstart)
> - And the second from the "Pro Wicket" book, also (quickstart).
>
> I will work on it to make the example from the book works.
>
> Thanks for your feedback.
>
> Regards,
> Mohamed
>
> -----Original Message-----
> From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
> Sent: Tuesday, March 24, 2009 4:44 PM
> To: users@wicket.apache.org
> Subject: Re: newbie question: HTTP 404 on the quickstart project
>
> Because you're not using jetty-config.xml - look at Start.java - you are
> mounting the app on /
>
>  WebAppContext bb = new WebAppContext();
>               bb.setServer(server);
>               bb.setContextPath("/");
>               bb.setWar("src/main/webapp");
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
> On Tue, Mar 24, 2009 at 3:41 PM, Chenini, Mohamed
> <MC...@geico.com>wrote:
>
>> Why URL http://localhost:8081/quickstart
>>
>> Results on this error:
>>
>> HTTP ERROR: 404
>> NOT_FOUND
>> RequestURI=/QuickStart
>>
>>
>> While jetty-config.xml has this entry:
>>
>>
>> <Call name="addWebApplication">
>>    <Arg>/QuickStart</Arg>
>>    <Arg>src/webapp</Arg>
>> </Call>
>>
>> -----Original Message-----
>> From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
>> Sent: Tuesday, March 24, 2009 4:30 PM
>> To: users@wicket.apache.org
>> Subject: Re: newbie question: HTTP 404 on the quickstart project
>>
>> Okay - you found it.  What's the question?
>>
>> --
>> Jeremy Thomerson
>> http://www.wickettraining.com
>>
>>
>>
>> On Tue, Mar 24, 2009 at 3:28 PM, Chenini, Mohamed
>> <MC...@geico.com>wrote:
>>
>> >
>> > Launching http://localhost:8081  produces this output:
>> >
>> > Wicket Quickstart Archetype Homepage
>> >
>> > If you see this message wicket is properly configured and running
>> >
>> >
>> >
>> > The jetty server is started and the console log shows this:
>> >
>> >
>> > INFO  - WebApplication             - [WicketApplication] Started
>> Wicket
>> > version 1.4-rc2 in development mode
>> > ********************************************************************
>> > *** WARNING: Wicket is running in DEVELOPMENT mode.              ***
>> > ***                               ^^^^^^^^^^^                    ***
>> > *** Do NOT deploy to your live server(s) without changing this.  ***
>> > *** See Application#getConfigurationType() for more information. ***
>> > ********************************************************************
>> > INFO  - log                        - Started
>> > SocketConnector@0.0.0.0:8081
>> >
>> >
>> >
>> > The Start.java code is as follows:
>> >
>> >
>> > mport org.mortbay.jetty.Connector;
>> > import org.mortbay.jetty.Server;
>> > import org.mortbay.jetty.bio.SocketConnector;
>> > import org.mortbay.jetty.webapp.WebAppContext;
>> >
>> > public class Start {
>> >
>> >        public static void main(String[] args) throws Exception {
>> >                Server server = new Server();
>> >                SocketConnector connector = new SocketConnector();
>> >
>> >                // Set some timeout options to make debugging easier.
>> >                connector.setMaxIdleTime(1000 * 60 * 60);
>> >                connector.setSoLingerTime(-1);
>> >                connector.setPort(8081);
>> >                server.setConnectors(new Connector[] { connector });
>> >
>> >                WebAppContext bb = new WebAppContext();
>> >                bb.setServer(server);
>> >                bb.setContextPath("/");
>> >                bb.setWar("src/main/webapp");
>> >
>> >                // START JMX SERVER
>> >                // MBeanServer mBeanServer =
>> > ManagementFactory.getPlatformMBeanServer();
>> >                // MBeanContainer mBeanContainer = new
>> > MBeanContainer(mBeanServer);
>> >                //
>> > server.getContainer().addEventListener(mBeanContainer);
>> >                // mBeanContainer.start();
>> >
>> >                server.addHandler(bb);
>> >
>> >                try {
>> >                        System.out.println(">>> STARTING EMBEDDED
> JETTY
>> > SERVER, PRESS ANY KEY TO STOP");
>> >                        server.start();
>> >                        System.in.read();
>> >                        System.out.println(">>> STOPPING EMBEDDED
> JETTY
>> > SERVER");
>> >            // while (System.in.available() == 0) {
>> >                        //   Thread.sleep(5000);
>> >                        // }
>> >                        server.stop();
>> >                        server.join();
>> >                } catch (Exception e) {
>> >                        e.printStackTrace();
>> >                        System.exit(100);
>> >                 }
>> >        }
>> > }
>> >
>> >
>> > -----Original Message-----
>> > From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
>> > Sent: Tuesday, March 24, 2009 4:23 PM
>> > To: users@wicket.apache.org
>> > Subject: Re: newbie question: HTTP 404 on the quickstart project
>> >
>> > Try http://localhost:8080 and http://localhost:8081
>> >
>> > The answer really will be in Start.java - see what port it is on and
>> > where
>> > the app is mounted.  Then make that into a URL.
>> >
>> > --
>> > Jeremy Thomerson
>> > http://www.wickettraining.com
>> >
>> >
>> >
>> > On Tue, Mar 24, 2009 at 3:19 PM, Chenini, Mohamed
>> > <MC...@geico.com>wrote:
>> >
>> > > I tried http://localhost:8081/quickstart
>> > >
>> > > And the content of web.xml is:
>> > >
>> > >
>> > > <filter>
>> > >        <filter-name>wicket.QuickStart</filter-name>
>> > >
>> > >
>> >
>>
> <filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class
>> > > >
>> > >        <init-param>
>> > >                <param-name>applicationClassName</param-name>
>> > >
>> > > <param-value>com.mycompany.app.WicketApplication</param-value>
>> > >        </init-param>
>> > > </filter>
>> > >
>> > > <filter-mapping>
>> > >  <filter-name>wicket.QuickStart</filter-name>
>> > >        <url-pattern>/*</url-pattern>
>> > > </filter-mapping>
>> > >
>> > >
>> > > -----Original Message-----
>> > > From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
>> > > Sent: Tuesday, March 24, 2009 4:17 PM
>> > > To: users@wicket.apache.org
>> > > Subject: Re: newbie question: HTTP 404 on the quickstart project
>> > >
>> > > Have you tried going to http://localhost:8081/quickstart ? or
> simply
>> > > http://localhost:8081 ?
>> > >
>> > > --
>> > > Jeremy Thomerson
>> > > http://www.wickettraining.com
>> > >
>> > >
>> > >
>> > > On Tue, Mar 24, 2009 at 3:09 PM, Chenini, Mohamed
>> > > <MC...@geico.com>wrote:
>> > >
>> > > > Hi,
>> > > >
>> > > > I setup the "quickstart" project using the imbedded jetty server
>> and
>> > > > started the jetty server from inside Eclipse (Right-click on
>> > > > src/main/java and then click  on "Run as" "Java Application"
>> > > >
>> > > > But when I enter on the browser (IE) this URL:
>> > > > http://localhost:8081/QuickStart
>> > > >
>> > > > I got this error:
>> > > >
>> > > >
>> > > > HTTP ERROR: 404
>> > > > NOT_FOUND
>> > > > RequestURI=/QuickStart
>> > > > I can send pieces of the code I am using if necessary to help
>> > > determine
>> > > > what is wrong.
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > Thanks,
>> > > > Mohamed
>> > > > ====================
>> > > > This email/fax message is for the sole use of the intended
>> > > > recipient(s) and may contain confidential and privileged
>> > information.
>> > > > Any unauthorized review, use, disclosure or distribution of this
>> > > > email/fax is prohibited. If you are not the intended recipient,
>> > please
>> > > > destroy all paper and electronic copies of the original message.
>> > > >
>> > > ====================
>> > > This email/fax message is for the sole use of the intended
>> > > recipient(s) and may contain confidential and privileged
>> information.
>> > > Any unauthorized review, use, disclosure or distribution of this
>> > > email/fax is prohibited. If you are not the intended recipient,
>> please
>> > > destroy all paper and electronic copies of the original message.
>> > >
>> > ====================
>> > This email/fax message is for the sole use of the intended
>> > recipient(s) and may contain confidential and privileged
> information.
>> > Any unauthorized review, use, disclosure or distribution of this
>> > email/fax is prohibited. If you are not the intended recipient,
> please
>> > destroy all paper and electronic copies of the original message.
>> >
>> ====================
>> This email/fax message is for the sole use of the intended
>> recipient(s) and may contain confidential and privileged information.
>> Any unauthorized review, use, disclosure or distribution of this
>> email/fax is prohibited. If you are not the intended recipient, please
>> destroy all paper and electronic copies of the original message.
>>
> ====================
> This email/fax message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged information.
> Any unauthorized review, use, disclosure or distribution of this
> email/fax is prohibited. If you are not the intended recipient, please
> destroy all paper and electronic copies of the original message.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

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

====================
This email/fax message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution of this
email/fax is prohibited. If you are not the intended recipient, please
destroy all paper and electronic copies of the original message.


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


Re: newbie question: HTTP 404 on the quickstart project

Posted by Martijn Dashorst <ma...@gmail.com>.
Pro Wicket has been written during Wicket 1.2 availability. Therefore
you should not expect everything to work directly. If you use the
wicket-quickstart download from Wicket 1.2 the example should match.

Instead of using this part from Pro Wicket, why don't you download the
free bonus chapter from Wicket in Action, and use that as your
starting point: it is up to date regarding Wicket 1.3, and has an
explanation for both ant and maven users.

You can download the bonus chapter (and 2 other free chapters) from
the official companion site to Wicket in Action:
http://wicketinaction.com/downloads/

Martijn

On Tue, Mar 24, 2009 at 9:57 PM, Chenini, Mohamed <MC...@geico.com> wrote:
> OK! I guess I was mixing two examples scenarios:
> - One from the Wicket website (quickstart)
> - And the second from the "Pro Wicket" book, also (quickstart).
>
> I will work on it to make the example from the book works.
>
> Thanks for your feedback.
>
> Regards,
> Mohamed
>
> -----Original Message-----
> From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
> Sent: Tuesday, March 24, 2009 4:44 PM
> To: users@wicket.apache.org
> Subject: Re: newbie question: HTTP 404 on the quickstart project
>
> Because you're not using jetty-config.xml - look at Start.java - you are
> mounting the app on /
>
>  WebAppContext bb = new WebAppContext();
>               bb.setServer(server);
>               bb.setContextPath("/");
>               bb.setWar("src/main/webapp");
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
> On Tue, Mar 24, 2009 at 3:41 PM, Chenini, Mohamed
> <MC...@geico.com>wrote:
>
>> Why URL http://localhost:8081/quickstart
>>
>> Results on this error:
>>
>> HTTP ERROR: 404
>> NOT_FOUND
>> RequestURI=/QuickStart
>>
>>
>> While jetty-config.xml has this entry:
>>
>>
>> <Call name="addWebApplication">
>>    <Arg>/QuickStart</Arg>
>>    <Arg>src/webapp</Arg>
>> </Call>
>>
>> -----Original Message-----
>> From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
>> Sent: Tuesday, March 24, 2009 4:30 PM
>> To: users@wicket.apache.org
>> Subject: Re: newbie question: HTTP 404 on the quickstart project
>>
>> Okay - you found it.  What's the question?
>>
>> --
>> Jeremy Thomerson
>> http://www.wickettraining.com
>>
>>
>>
>> On Tue, Mar 24, 2009 at 3:28 PM, Chenini, Mohamed
>> <MC...@geico.com>wrote:
>>
>> >
>> > Launching http://localhost:8081  produces this output:
>> >
>> > Wicket Quickstart Archetype Homepage
>> >
>> > If you see this message wicket is properly configured and running
>> >
>> >
>> >
>> > The jetty server is started and the console log shows this:
>> >
>> >
>> > INFO  - WebApplication             - [WicketApplication] Started
>> Wicket
>> > version 1.4-rc2 in development mode
>> > ********************************************************************
>> > *** WARNING: Wicket is running in DEVELOPMENT mode.              ***
>> > ***                               ^^^^^^^^^^^                    ***
>> > *** Do NOT deploy to your live server(s) without changing this.  ***
>> > *** See Application#getConfigurationType() for more information. ***
>> > ********************************************************************
>> > INFO  - log                        - Started
>> > SocketConnector@0.0.0.0:8081
>> >
>> >
>> >
>> > The Start.java code is as follows:
>> >
>> >
>> > mport org.mortbay.jetty.Connector;
>> > import org.mortbay.jetty.Server;
>> > import org.mortbay.jetty.bio.SocketConnector;
>> > import org.mortbay.jetty.webapp.WebAppContext;
>> >
>> > public class Start {
>> >
>> >        public static void main(String[] args) throws Exception {
>> >                Server server = new Server();
>> >                SocketConnector connector = new SocketConnector();
>> >
>> >                // Set some timeout options to make debugging easier.
>> >                connector.setMaxIdleTime(1000 * 60 * 60);
>> >                connector.setSoLingerTime(-1);
>> >                connector.setPort(8081);
>> >                server.setConnectors(new Connector[] { connector });
>> >
>> >                WebAppContext bb = new WebAppContext();
>> >                bb.setServer(server);
>> >                bb.setContextPath("/");
>> >                bb.setWar("src/main/webapp");
>> >
>> >                // START JMX SERVER
>> >                // MBeanServer mBeanServer =
>> > ManagementFactory.getPlatformMBeanServer();
>> >                // MBeanContainer mBeanContainer = new
>> > MBeanContainer(mBeanServer);
>> >                //
>> > server.getContainer().addEventListener(mBeanContainer);
>> >                // mBeanContainer.start();
>> >
>> >                server.addHandler(bb);
>> >
>> >                try {
>> >                        System.out.println(">>> STARTING EMBEDDED
> JETTY
>> > SERVER, PRESS ANY KEY TO STOP");
>> >                        server.start();
>> >                        System.in.read();
>> >                        System.out.println(">>> STOPPING EMBEDDED
> JETTY
>> > SERVER");
>> >            // while (System.in.available() == 0) {
>> >                        //   Thread.sleep(5000);
>> >                        // }
>> >                        server.stop();
>> >                        server.join();
>> >                } catch (Exception e) {
>> >                        e.printStackTrace();
>> >                        System.exit(100);
>> >                 }
>> >        }
>> > }
>> >
>> >
>> > -----Original Message-----
>> > From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
>> > Sent: Tuesday, March 24, 2009 4:23 PM
>> > To: users@wicket.apache.org
>> > Subject: Re: newbie question: HTTP 404 on the quickstart project
>> >
>> > Try http://localhost:8080 and http://localhost:8081
>> >
>> > The answer really will be in Start.java - see what port it is on and
>> > where
>> > the app is mounted.  Then make that into a URL.
>> >
>> > --
>> > Jeremy Thomerson
>> > http://www.wickettraining.com
>> >
>> >
>> >
>> > On Tue, Mar 24, 2009 at 3:19 PM, Chenini, Mohamed
>> > <MC...@geico.com>wrote:
>> >
>> > > I tried http://localhost:8081/quickstart
>> > >
>> > > And the content of web.xml is:
>> > >
>> > >
>> > > <filter>
>> > >        <filter-name>wicket.QuickStart</filter-name>
>> > >
>> > >
>> >
>>
> <filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class
>> > > >
>> > >        <init-param>
>> > >                <param-name>applicationClassName</param-name>
>> > >
>> > > <param-value>com.mycompany.app.WicketApplication</param-value>
>> > >        </init-param>
>> > > </filter>
>> > >
>> > > <filter-mapping>
>> > >  <filter-name>wicket.QuickStart</filter-name>
>> > >        <url-pattern>/*</url-pattern>
>> > > </filter-mapping>
>> > >
>> > >
>> > > -----Original Message-----
>> > > From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
>> > > Sent: Tuesday, March 24, 2009 4:17 PM
>> > > To: users@wicket.apache.org
>> > > Subject: Re: newbie question: HTTP 404 on the quickstart project
>> > >
>> > > Have you tried going to http://localhost:8081/quickstart ? or
> simply
>> > > http://localhost:8081 ?
>> > >
>> > > --
>> > > Jeremy Thomerson
>> > > http://www.wickettraining.com
>> > >
>> > >
>> > >
>> > > On Tue, Mar 24, 2009 at 3:09 PM, Chenini, Mohamed
>> > > <MC...@geico.com>wrote:
>> > >
>> > > > Hi,
>> > > >
>> > > > I setup the "quickstart" project using the imbedded jetty server
>> and
>> > > > started the jetty server from inside Eclipse (Right-click on
>> > > > src/main/java and then click  on "Run as" "Java Application"
>> > > >
>> > > > But when I enter on the browser (IE) this URL:
>> > > > http://localhost:8081/QuickStart
>> > > >
>> > > > I got this error:
>> > > >
>> > > >
>> > > > HTTP ERROR: 404
>> > > > NOT_FOUND
>> > > > RequestURI=/QuickStart
>> > > > I can send pieces of the code I am using if necessary to help
>> > > determine
>> > > > what is wrong.
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > Thanks,
>> > > > Mohamed
>> > > > ====================
>> > > > This email/fax message is for the sole use of the intended
>> > > > recipient(s) and may contain confidential and privileged
>> > information.
>> > > > Any unauthorized review, use, disclosure or distribution of this
>> > > > email/fax is prohibited. If you are not the intended recipient,
>> > please
>> > > > destroy all paper and electronic copies of the original message.
>> > > >
>> > > ====================
>> > > This email/fax message is for the sole use of the intended
>> > > recipient(s) and may contain confidential and privileged
>> information.
>> > > Any unauthorized review, use, disclosure or distribution of this
>> > > email/fax is prohibited. If you are not the intended recipient,
>> please
>> > > destroy all paper and electronic copies of the original message.
>> > >
>> > ====================
>> > This email/fax message is for the sole use of the intended
>> > recipient(s) and may contain confidential and privileged
> information.
>> > Any unauthorized review, use, disclosure or distribution of this
>> > email/fax is prohibited. If you are not the intended recipient,
> please
>> > destroy all paper and electronic copies of the original message.
>> >
>> ====================
>> This email/fax message is for the sole use of the intended
>> recipient(s) and may contain confidential and privileged information.
>> Any unauthorized review, use, disclosure or distribution of this
>> email/fax is prohibited. If you are not the intended recipient, please
>> destroy all paper and electronic copies of the original message.
>>
> ====================
> This email/fax message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged information.
> Any unauthorized review, use, disclosure or distribution of this
> email/fax is prohibited. If you are not the intended recipient, please
> destroy all paper and electronic copies of the original message.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

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


RE: newbie question: HTTP 404 on the quickstart project

Posted by "Chenini, Mohamed " <MC...@geico.com>.
OK! I guess I was mixing two examples scenarios:
- One from the Wicket website (quickstart)
- And the second from the "Pro Wicket" book, also (quickstart).

I will work on it to make the example from the book works.

Thanks for your feedback.

Regards,
Mohamed

-----Original Message-----
From: Jeremy Thomerson [mailto:jeremy@wickettraining.com] 
Sent: Tuesday, March 24, 2009 4:44 PM
To: users@wicket.apache.org
Subject: Re: newbie question: HTTP 404 on the quickstart project

Because you're not using jetty-config.xml - look at Start.java - you are
mounting the app on /

 WebAppContext bb = new WebAppContext();
               bb.setServer(server);
               bb.setContextPath("/");
               bb.setWar("src/main/webapp");

--
Jeremy Thomerson
http://www.wickettraining.com



On Tue, Mar 24, 2009 at 3:41 PM, Chenini, Mohamed
<MC...@geico.com>wrote:

> Why URL http://localhost:8081/quickstart
>
> Results on this error:
>
> HTTP ERROR: 404
> NOT_FOUND
> RequestURI=/QuickStart
>
>
> While jetty-config.xml has this entry:
>
>
> <Call name="addWebApplication">
>    <Arg>/QuickStart</Arg>
>    <Arg>src/webapp</Arg>
> </Call>
>
> -----Original Message-----
> From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
> Sent: Tuesday, March 24, 2009 4:30 PM
> To: users@wicket.apache.org
> Subject: Re: newbie question: HTTP 404 on the quickstart project
>
> Okay - you found it.  What's the question?
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
> On Tue, Mar 24, 2009 at 3:28 PM, Chenini, Mohamed
> <MC...@geico.com>wrote:
>
> >
> > Launching http://localhost:8081  produces this output:
> >
> > Wicket Quickstart Archetype Homepage
> >
> > If you see this message wicket is properly configured and running
> >
> >
> >
> > The jetty server is started and the console log shows this:
> >
> >
> > INFO  - WebApplication             - [WicketApplication] Started
> Wicket
> > version 1.4-rc2 in development mode
> > ********************************************************************
> > *** WARNING: Wicket is running in DEVELOPMENT mode.              ***
> > ***                               ^^^^^^^^^^^                    ***
> > *** Do NOT deploy to your live server(s) without changing this.  ***
> > *** See Application#getConfigurationType() for more information. ***
> > ********************************************************************
> > INFO  - log                        - Started
> > SocketConnector@0.0.0.0:8081
> >
> >
> >
> > The Start.java code is as follows:
> >
> >
> > mport org.mortbay.jetty.Connector;
> > import org.mortbay.jetty.Server;
> > import org.mortbay.jetty.bio.SocketConnector;
> > import org.mortbay.jetty.webapp.WebAppContext;
> >
> > public class Start {
> >
> >        public static void main(String[] args) throws Exception {
> >                Server server = new Server();
> >                SocketConnector connector = new SocketConnector();
> >
> >                // Set some timeout options to make debugging easier.
> >                connector.setMaxIdleTime(1000 * 60 * 60);
> >                connector.setSoLingerTime(-1);
> >                connector.setPort(8081);
> >                server.setConnectors(new Connector[] { connector });
> >
> >                WebAppContext bb = new WebAppContext();
> >                bb.setServer(server);
> >                bb.setContextPath("/");
> >                bb.setWar("src/main/webapp");
> >
> >                // START JMX SERVER
> >                // MBeanServer mBeanServer =
> > ManagementFactory.getPlatformMBeanServer();
> >                // MBeanContainer mBeanContainer = new
> > MBeanContainer(mBeanServer);
> >                //
> > server.getContainer().addEventListener(mBeanContainer);
> >                // mBeanContainer.start();
> >
> >                server.addHandler(bb);
> >
> >                try {
> >                        System.out.println(">>> STARTING EMBEDDED
JETTY
> > SERVER, PRESS ANY KEY TO STOP");
> >                        server.start();
> >                        System.in.read();
> >                        System.out.println(">>> STOPPING EMBEDDED
JETTY
> > SERVER");
> >            // while (System.in.available() == 0) {
> >                        //   Thread.sleep(5000);
> >                        // }
> >                        server.stop();
> >                        server.join();
> >                } catch (Exception e) {
> >                        e.printStackTrace();
> >                        System.exit(100);
> >                 }
> >        }
> > }
> >
> >
> > -----Original Message-----
> > From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
> > Sent: Tuesday, March 24, 2009 4:23 PM
> > To: users@wicket.apache.org
> > Subject: Re: newbie question: HTTP 404 on the quickstart project
> >
> > Try http://localhost:8080 and http://localhost:8081
> >
> > The answer really will be in Start.java - see what port it is on and
> > where
> > the app is mounted.  Then make that into a URL.
> >
> > --
> > Jeremy Thomerson
> > http://www.wickettraining.com
> >
> >
> >
> > On Tue, Mar 24, 2009 at 3:19 PM, Chenini, Mohamed
> > <MC...@geico.com>wrote:
> >
> > > I tried http://localhost:8081/quickstart
> > >
> > > And the content of web.xml is:
> > >
> > >
> > > <filter>
> > >        <filter-name>wicket.QuickStart</filter-name>
> > >
> > >
> >
>
<filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class
> > > >
> > >        <init-param>
> > >                <param-name>applicationClassName</param-name>
> > >
> > > <param-value>com.mycompany.app.WicketApplication</param-value>
> > >        </init-param>
> > > </filter>
> > >
> > > <filter-mapping>
> > >  <filter-name>wicket.QuickStart</filter-name>
> > >        <url-pattern>/*</url-pattern>
> > > </filter-mapping>
> > >
> > >
> > > -----Original Message-----
> > > From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
> > > Sent: Tuesday, March 24, 2009 4:17 PM
> > > To: users@wicket.apache.org
> > > Subject: Re: newbie question: HTTP 404 on the quickstart project
> > >
> > > Have you tried going to http://localhost:8081/quickstart ? or
simply
> > > http://localhost:8081 ?
> > >
> > > --
> > > Jeremy Thomerson
> > > http://www.wickettraining.com
> > >
> > >
> > >
> > > On Tue, Mar 24, 2009 at 3:09 PM, Chenini, Mohamed
> > > <MC...@geico.com>wrote:
> > >
> > > > Hi,
> > > >
> > > > I setup the "quickstart" project using the imbedded jetty server
> and
> > > > started the jetty server from inside Eclipse (Right-click on
> > > > src/main/java and then click  on "Run as" "Java Application"
> > > >
> > > > But when I enter on the browser (IE) this URL:
> > > > http://localhost:8081/QuickStart
> > > >
> > > > I got this error:
> > > >
> > > >
> > > > HTTP ERROR: 404
> > > > NOT_FOUND
> > > > RequestURI=/QuickStart
> > > > I can send pieces of the code I am using if necessary to help
> > > determine
> > > > what is wrong.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Thanks,
> > > > Mohamed
> > > > ====================
> > > > This email/fax message is for the sole use of the intended
> > > > recipient(s) and may contain confidential and privileged
> > information.
> > > > Any unauthorized review, use, disclosure or distribution of this
> > > > email/fax is prohibited. If you are not the intended recipient,
> > please
> > > > destroy all paper and electronic copies of the original message.
> > > >
> > > ====================
> > > This email/fax message is for the sole use of the intended
> > > recipient(s) and may contain confidential and privileged
> information.
> > > Any unauthorized review, use, disclosure or distribution of this
> > > email/fax is prohibited. If you are not the intended recipient,
> please
> > > destroy all paper and electronic copies of the original message.
> > >
> > ====================
> > This email/fax message is for the sole use of the intended
> > recipient(s) and may contain confidential and privileged
information.
> > Any unauthorized review, use, disclosure or distribution of this
> > email/fax is prohibited. If you are not the intended recipient,
please
> > destroy all paper and electronic copies of the original message.
> >
> ====================
> This email/fax message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged information.
> Any unauthorized review, use, disclosure or distribution of this
> email/fax is prohibited. If you are not the intended recipient, please
> destroy all paper and electronic copies of the original message.
>
====================
This email/fax message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution of this
email/fax is prohibited. If you are not the intended recipient, please
destroy all paper and electronic copies of the original message.


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


Re: newbie question: HTTP 404 on the quickstart project

Posted by Jeremy Thomerson <je...@wickettraining.com>.
Why do you so badly want it to be on "/QuickStart"?  It was working for you
on "/" - now start learning Wicket with it - that was the intention of the
quickstart.

--
Jeremy Thomerson
http://www.wickettraining.com



On Wed, Mar 25, 2009 at 4:01 PM, Chenini, Mohamed <MC...@geico.com>wrote:

> Hi,
>
> Can you, please, be more explicit when you said " Because you're not
> using jetty-config.xml "
>
> I changed   bb.setContextPath("/"); to bb.setContextPath("/QuickStart");
>
> And the result is the same.
>
> But I do not see how can I refer to the "jetty-config.xml" in the
> Start.java file.
>
> Regards.
> Mohamed
>
>
> -----Original Message-----
> From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
> Sent: Tuesday, March 24, 2009 4:44 PM
> To: users@wicket.apache.org
> Subject: Re: newbie question: HTTP 404 on the quickstart project
>
> Because you're not using jetty-config.xml - look at Start.java - you are
> mounting the app on /
>
>  WebAppContext bb = new WebAppContext();
>               bb.setServer(server);
>               bb.setContextPath("/");
>               bb.setWar("src/main/webapp");
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
> On Tue, Mar 24, 2009 at 3:41 PM, Chenini, Mohamed
> <MC...@geico.com>wrote:
>
> > Why URL http://localhost:8081/quickstart
> >
> > Results on this error:
> >
> > HTTP ERROR: 404
> > NOT_FOUND
> > RequestURI=/QuickStart
> >
> >
> > While jetty-config.xml has this entry:
> >
> >
> > <Call name="addWebApplication">
> >    <Arg>/QuickStart</Arg>
> >    <Arg>src/webapp</Arg>
> > </Call>
> >
> > -----Original Message-----
> > From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
> > Sent: Tuesday, March 24, 2009 4:30 PM
> > To: users@wicket.apache.org
> > Subject: Re: newbie question: HTTP 404 on the quickstart project
> >
> > Okay - you found it.  What's the question?
> >
> > --
> > Jeremy Thomerson
> > http://www.wickettraining.com
> >
> >
> >
> > On Tue, Mar 24, 2009 at 3:28 PM, Chenini, Mohamed
> > <MC...@geico.com>wrote:
> >
> > >
> > > Launching http://localhost:8081  produces this output:
> > >
> > > Wicket Quickstart Archetype Homepage
> > >
> > > If you see this message wicket is properly configured and running
> > >
> > >
> > >
> > > The jetty server is started and the console log shows this:
> > >
> > >
> > > INFO  - WebApplication             - [WicketApplication] Started
> > Wicket
> > > version 1.4-rc2 in development mode
> > > ********************************************************************
> > > *** WARNING: Wicket is running in DEVELOPMENT mode.              ***
> > > ***                               ^^^^^^^^^^^                    ***
> > > *** Do NOT deploy to your live server(s) without changing this.  ***
> > > *** See Application#getConfigurationType() for more information. ***
> > > ********************************************************************
> > > INFO  - log                        - Started
> > > SocketConnector@0.0.0.0:8081
> > >
> > >
> > >
> > > The Start.java code is as follows:
> > >
> > >
> > > mport org.mortbay.jetty.Connector;
> > > import org.mortbay.jetty.Server;
> > > import org.mortbay.jetty.bio.SocketConnector;
> > > import org.mortbay.jetty.webapp.WebAppContext;
> > >
> > > public class Start {
> > >
> > >        public static void main(String[] args) throws Exception {
> > >                Server server = new Server();
> > >                SocketConnector connector = new SocketConnector();
> > >
> > >                // Set some timeout options to make debugging easier.
> > >                connector.setMaxIdleTime(1000 * 60 * 60);
> > >                connector.setSoLingerTime(-1);
> > >                connector.setPort(8081);
> > >                server.setConnectors(new Connector[] { connector });
> > >
> > >                WebAppContext bb = new WebAppContext();
> > >                bb.setServer(server);
> > >                bb.setContextPath("/");
> > >                bb.setWar("src/main/webapp");
> > >
> > >                // START JMX SERVER
> > >                // MBeanServer mBeanServer =
> > > ManagementFactory.getPlatformMBeanServer();
> > >                // MBeanContainer mBeanContainer = new
> > > MBeanContainer(mBeanServer);
> > >                //
> > > server.getContainer().addEventListener(mBeanContainer);
> > >                // mBeanContainer.start();
> > >
> > >                server.addHandler(bb);
> > >
> > >                try {
> > >                        System.out.println(">>> STARTING EMBEDDED
> JETTY
> > > SERVER, PRESS ANY KEY TO STOP");
> > >                        server.start();
> > >                        System.in.read();
> > >                        System.out.println(">>> STOPPING EMBEDDED
> JETTY
> > > SERVER");
> > >            // while (System.in.available() == 0) {
> > >                        //   Thread.sleep(5000);
> > >                        // }
> > >                        server.stop();
> > >                        server.join();
> > >                } catch (Exception e) {
> > >                        e.printStackTrace();
> > >                        System.exit(100);
> > >                 }
> > >        }
> > > }
> > >
> > >
> > > -----Original Message-----
> > > From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
> > > Sent: Tuesday, March 24, 2009 4:23 PM
> > > To: users@wicket.apache.org
> > > Subject: Re: newbie question: HTTP 404 on the quickstart project
> > >
> > > Try http://localhost:8080 and http://localhost:8081
> > >
> > > The answer really will be in Start.java - see what port it is on and
> > > where
> > > the app is mounted.  Then make that into a URL.
> > >
> > > --
> > > Jeremy Thomerson
> > > http://www.wickettraining.com
> > >
> > >
> > >
> > > On Tue, Mar 24, 2009 at 3:19 PM, Chenini, Mohamed
> > > <MC...@geico.com>wrote:
> > >
> > > > I tried http://localhost:8081/quickstart
> > > >
> > > > And the content of web.xml is:
> > > >
> > > >
> > > > <filter>
> > > >        <filter-name>wicket.QuickStart</filter-name>
> > > >
> > > >
> > >
> >
> <filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class
> > > > >
> > > >        <init-param>
> > > >                <param-name>applicationClassName</param-name>
> > > >
> > > > <param-value>com.mycompany.app.WicketApplication</param-value>
> > > >        </init-param>
> > > > </filter>
> > > >
> > > > <filter-mapping>
> > > >  <filter-name>wicket.QuickStart</filter-name>
> > > >        <url-pattern>/*</url-pattern>
> > > > </filter-mapping>
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
> > > > Sent: Tuesday, March 24, 2009 4:17 PM
> > > > To: users@wicket.apache.org
> > > > Subject: Re: newbie question: HTTP 404 on the quickstart project
> > > >
> > > > Have you tried going to http://localhost:8081/quickstart ? or
> simply
> > > > http://localhost:8081 ?
> > > >
> > > > --
> > > > Jeremy Thomerson
> > > > http://www.wickettraining.com
> > > >
> > > >
> > > >
> > > > On Tue, Mar 24, 2009 at 3:09 PM, Chenini, Mohamed
> > > > <MC...@geico.com>wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I setup the "quickstart" project using the imbedded jetty server
> > and
> > > > > started the jetty server from inside Eclipse (Right-click on
> > > > > src/main/java and then click  on "Run as" "Java Application"
> > > > >
> > > > > But when I enter on the browser (IE) this URL:
> > > > > http://localhost:8081/QuickStart
> > > > >
> > > > > I got this error:
> > > > >
> > > > >
> > > > > HTTP ERROR: 404
> > > > > NOT_FOUND
> > > > > RequestURI=/QuickStart
> > > > > I can send pieces of the code I am using if necessary to help
> > > > determine
> > > > > what is wrong.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Thanks,
> > > > > Mohamed
> > > > > ====================
> > > > > This email/fax message is for the sole use of the intended
> > > > > recipient(s) and may contain confidential and privileged
> > > information.
> > > > > Any unauthorized review, use, disclosure or distribution of this
> > > > > email/fax is prohibited. If you are not the intended recipient,
> > > please
> > > > > destroy all paper and electronic copies of the original message.
> > > > >
> > > > ====================
> > > > This email/fax message is for the sole use of the intended
> > > > recipient(s) and may contain confidential and privileged
> > information.
> > > > Any unauthorized review, use, disclosure or distribution of this
> > > > email/fax is prohibited. If you are not the intended recipient,
> > please
> > > > destroy all paper and electronic copies of the original message.
> > > >
> > > ====================
> > > This email/fax message is for the sole use of the intended
> > > recipient(s) and may contain confidential and privileged
> information.
> > > Any unauthorized review, use, disclosure or distribution of this
> > > email/fax is prohibited. If you are not the intended recipient,
> please
> > > destroy all paper and electronic copies of the original message.
> > >
> > ====================
> > This email/fax message is for the sole use of the intended
> > recipient(s) and may contain confidential and privileged information.
> > Any unauthorized review, use, disclosure or distribution of this
> > email/fax is prohibited. If you are not the intended recipient, please
> > destroy all paper and electronic copies of the original message.
> >
> ====================
> This email/fax message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged information.
> Any unauthorized review, use, disclosure or distribution of this
> email/fax is prohibited. If you are not the intended recipient, please
> destroy all paper and electronic copies of the original message.
>

RE: newbie question: HTTP 404 on the quickstart project

Posted by "Chenini, Mohamed " <MC...@geico.com>.
Hi,

Can you, please, be more explicit when you said " Because you're not
using jetty-config.xml "

I changed   bb.setContextPath("/"); to bb.setContextPath("/QuickStart");

And the result is the same.

But I do not see how can I refer to the "jetty-config.xml" in the
Start.java file.

Regards.
Mohamed


-----Original Message-----
From: Jeremy Thomerson [mailto:jeremy@wickettraining.com] 
Sent: Tuesday, March 24, 2009 4:44 PM
To: users@wicket.apache.org
Subject: Re: newbie question: HTTP 404 on the quickstart project

Because you're not using jetty-config.xml - look at Start.java - you are
mounting the app on /

 WebAppContext bb = new WebAppContext();
               bb.setServer(server);
               bb.setContextPath("/");
               bb.setWar("src/main/webapp");

--
Jeremy Thomerson
http://www.wickettraining.com



On Tue, Mar 24, 2009 at 3:41 PM, Chenini, Mohamed
<MC...@geico.com>wrote:

> Why URL http://localhost:8081/quickstart
>
> Results on this error:
>
> HTTP ERROR: 404
> NOT_FOUND
> RequestURI=/QuickStart
>
>
> While jetty-config.xml has this entry:
>
>
> <Call name="addWebApplication">
>    <Arg>/QuickStart</Arg>
>    <Arg>src/webapp</Arg>
> </Call>
>
> -----Original Message-----
> From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
> Sent: Tuesday, March 24, 2009 4:30 PM
> To: users@wicket.apache.org
> Subject: Re: newbie question: HTTP 404 on the quickstart project
>
> Okay - you found it.  What's the question?
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
> On Tue, Mar 24, 2009 at 3:28 PM, Chenini, Mohamed
> <MC...@geico.com>wrote:
>
> >
> > Launching http://localhost:8081  produces this output:
> >
> > Wicket Quickstart Archetype Homepage
> >
> > If you see this message wicket is properly configured and running
> >
> >
> >
> > The jetty server is started and the console log shows this:
> >
> >
> > INFO  - WebApplication             - [WicketApplication] Started
> Wicket
> > version 1.4-rc2 in development mode
> > ********************************************************************
> > *** WARNING: Wicket is running in DEVELOPMENT mode.              ***
> > ***                               ^^^^^^^^^^^                    ***
> > *** Do NOT deploy to your live server(s) without changing this.  ***
> > *** See Application#getConfigurationType() for more information. ***
> > ********************************************************************
> > INFO  - log                        - Started
> > SocketConnector@0.0.0.0:8081
> >
> >
> >
> > The Start.java code is as follows:
> >
> >
> > mport org.mortbay.jetty.Connector;
> > import org.mortbay.jetty.Server;
> > import org.mortbay.jetty.bio.SocketConnector;
> > import org.mortbay.jetty.webapp.WebAppContext;
> >
> > public class Start {
> >
> >        public static void main(String[] args) throws Exception {
> >                Server server = new Server();
> >                SocketConnector connector = new SocketConnector();
> >
> >                // Set some timeout options to make debugging easier.
> >                connector.setMaxIdleTime(1000 * 60 * 60);
> >                connector.setSoLingerTime(-1);
> >                connector.setPort(8081);
> >                server.setConnectors(new Connector[] { connector });
> >
> >                WebAppContext bb = new WebAppContext();
> >                bb.setServer(server);
> >                bb.setContextPath("/");
> >                bb.setWar("src/main/webapp");
> >
> >                // START JMX SERVER
> >                // MBeanServer mBeanServer =
> > ManagementFactory.getPlatformMBeanServer();
> >                // MBeanContainer mBeanContainer = new
> > MBeanContainer(mBeanServer);
> >                //
> > server.getContainer().addEventListener(mBeanContainer);
> >                // mBeanContainer.start();
> >
> >                server.addHandler(bb);
> >
> >                try {
> >                        System.out.println(">>> STARTING EMBEDDED
JETTY
> > SERVER, PRESS ANY KEY TO STOP");
> >                        server.start();
> >                        System.in.read();
> >                        System.out.println(">>> STOPPING EMBEDDED
JETTY
> > SERVER");
> >            // while (System.in.available() == 0) {
> >                        //   Thread.sleep(5000);
> >                        // }
> >                        server.stop();
> >                        server.join();
> >                } catch (Exception e) {
> >                        e.printStackTrace();
> >                        System.exit(100);
> >                 }
> >        }
> > }
> >
> >
> > -----Original Message-----
> > From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
> > Sent: Tuesday, March 24, 2009 4:23 PM
> > To: users@wicket.apache.org
> > Subject: Re: newbie question: HTTP 404 on the quickstart project
> >
> > Try http://localhost:8080 and http://localhost:8081
> >
> > The answer really will be in Start.java - see what port it is on and
> > where
> > the app is mounted.  Then make that into a URL.
> >
> > --
> > Jeremy Thomerson
> > http://www.wickettraining.com
> >
> >
> >
> > On Tue, Mar 24, 2009 at 3:19 PM, Chenini, Mohamed
> > <MC...@geico.com>wrote:
> >
> > > I tried http://localhost:8081/quickstart
> > >
> > > And the content of web.xml is:
> > >
> > >
> > > <filter>
> > >        <filter-name>wicket.QuickStart</filter-name>
> > >
> > >
> >
>
<filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class
> > > >
> > >        <init-param>
> > >                <param-name>applicationClassName</param-name>
> > >
> > > <param-value>com.mycompany.app.WicketApplication</param-value>
> > >        </init-param>
> > > </filter>
> > >
> > > <filter-mapping>
> > >  <filter-name>wicket.QuickStart</filter-name>
> > >        <url-pattern>/*</url-pattern>
> > > </filter-mapping>
> > >
> > >
> > > -----Original Message-----
> > > From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
> > > Sent: Tuesday, March 24, 2009 4:17 PM
> > > To: users@wicket.apache.org
> > > Subject: Re: newbie question: HTTP 404 on the quickstart project
> > >
> > > Have you tried going to http://localhost:8081/quickstart ? or
simply
> > > http://localhost:8081 ?
> > >
> > > --
> > > Jeremy Thomerson
> > > http://www.wickettraining.com
> > >
> > >
> > >
> > > On Tue, Mar 24, 2009 at 3:09 PM, Chenini, Mohamed
> > > <MC...@geico.com>wrote:
> > >
> > > > Hi,
> > > >
> > > > I setup the "quickstart" project using the imbedded jetty server
> and
> > > > started the jetty server from inside Eclipse (Right-click on
> > > > src/main/java and then click  on "Run as" "Java Application"
> > > >
> > > > But when I enter on the browser (IE) this URL:
> > > > http://localhost:8081/QuickStart
> > > >
> > > > I got this error:
> > > >
> > > >
> > > > HTTP ERROR: 404
> > > > NOT_FOUND
> > > > RequestURI=/QuickStart
> > > > I can send pieces of the code I am using if necessary to help
> > > determine
> > > > what is wrong.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Thanks,
> > > > Mohamed
> > > > ====================
> > > > This email/fax message is for the sole use of the intended
> > > > recipient(s) and may contain confidential and privileged
> > information.
> > > > Any unauthorized review, use, disclosure or distribution of this
> > > > email/fax is prohibited. If you are not the intended recipient,
> > please
> > > > destroy all paper and electronic copies of the original message.
> > > >
> > > ====================
> > > This email/fax message is for the sole use of the intended
> > > recipient(s) and may contain confidential and privileged
> information.
> > > Any unauthorized review, use, disclosure or distribution of this
> > > email/fax is prohibited. If you are not the intended recipient,
> please
> > > destroy all paper and electronic copies of the original message.
> > >
> > ====================
> > This email/fax message is for the sole use of the intended
> > recipient(s) and may contain confidential and privileged
information.
> > Any unauthorized review, use, disclosure or distribution of this
> > email/fax is prohibited. If you are not the intended recipient,
please
> > destroy all paper and electronic copies of the original message.
> >
> ====================
> This email/fax message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged information.
> Any unauthorized review, use, disclosure or distribution of this
> email/fax is prohibited. If you are not the intended recipient, please
> destroy all paper and electronic copies of the original message.
>
====================
This email/fax message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution of this
email/fax is prohibited. If you are not the intended recipient, please
destroy all paper and electronic copies of the original message.

Re: newbie question: HTTP 404 on the quickstart project

Posted by Jeremy Thomerson <je...@wickettraining.com>.
Because you're not using jetty-config.xml - look at Start.java - you are
mounting the app on /

 WebAppContext bb = new WebAppContext();
               bb.setServer(server);
               bb.setContextPath("/");
               bb.setWar("src/main/webapp");

--
Jeremy Thomerson
http://www.wickettraining.com



On Tue, Mar 24, 2009 at 3:41 PM, Chenini, Mohamed <MC...@geico.com>wrote:

> Why URL http://localhost:8081/quickstart
>
> Results on this error:
>
> HTTP ERROR: 404
> NOT_FOUND
> RequestURI=/QuickStart
>
>
> While jetty-config.xml has this entry:
>
>
> <Call name="addWebApplication">
>    <Arg>/QuickStart</Arg>
>    <Arg>src/webapp</Arg>
> </Call>
>
> -----Original Message-----
> From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
> Sent: Tuesday, March 24, 2009 4:30 PM
> To: users@wicket.apache.org
> Subject: Re: newbie question: HTTP 404 on the quickstart project
>
> Okay - you found it.  What's the question?
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
> On Tue, Mar 24, 2009 at 3:28 PM, Chenini, Mohamed
> <MC...@geico.com>wrote:
>
> >
> > Launching http://localhost:8081  produces this output:
> >
> > Wicket Quickstart Archetype Homepage
> >
> > If you see this message wicket is properly configured and running
> >
> >
> >
> > The jetty server is started and the console log shows this:
> >
> >
> > INFO  - WebApplication             - [WicketApplication] Started
> Wicket
> > version 1.4-rc2 in development mode
> > ********************************************************************
> > *** WARNING: Wicket is running in DEVELOPMENT mode.              ***
> > ***                               ^^^^^^^^^^^                    ***
> > *** Do NOT deploy to your live server(s) without changing this.  ***
> > *** See Application#getConfigurationType() for more information. ***
> > ********************************************************************
> > INFO  - log                        - Started
> > SocketConnector@0.0.0.0:8081
> >
> >
> >
> > The Start.java code is as follows:
> >
> >
> > mport org.mortbay.jetty.Connector;
> > import org.mortbay.jetty.Server;
> > import org.mortbay.jetty.bio.SocketConnector;
> > import org.mortbay.jetty.webapp.WebAppContext;
> >
> > public class Start {
> >
> >        public static void main(String[] args) throws Exception {
> >                Server server = new Server();
> >                SocketConnector connector = new SocketConnector();
> >
> >                // Set some timeout options to make debugging easier.
> >                connector.setMaxIdleTime(1000 * 60 * 60);
> >                connector.setSoLingerTime(-1);
> >                connector.setPort(8081);
> >                server.setConnectors(new Connector[] { connector });
> >
> >                WebAppContext bb = new WebAppContext();
> >                bb.setServer(server);
> >                bb.setContextPath("/");
> >                bb.setWar("src/main/webapp");
> >
> >                // START JMX SERVER
> >                // MBeanServer mBeanServer =
> > ManagementFactory.getPlatformMBeanServer();
> >                // MBeanContainer mBeanContainer = new
> > MBeanContainer(mBeanServer);
> >                //
> > server.getContainer().addEventListener(mBeanContainer);
> >                // mBeanContainer.start();
> >
> >                server.addHandler(bb);
> >
> >                try {
> >                        System.out.println(">>> STARTING EMBEDDED JETTY
> > SERVER, PRESS ANY KEY TO STOP");
> >                        server.start();
> >                        System.in.read();
> >                        System.out.println(">>> STOPPING EMBEDDED JETTY
> > SERVER");
> >            // while (System.in.available() == 0) {
> >                        //   Thread.sleep(5000);
> >                        // }
> >                        server.stop();
> >                        server.join();
> >                } catch (Exception e) {
> >                        e.printStackTrace();
> >                        System.exit(100);
> >                 }
> >        }
> > }
> >
> >
> > -----Original Message-----
> > From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
> > Sent: Tuesday, March 24, 2009 4:23 PM
> > To: users@wicket.apache.org
> > Subject: Re: newbie question: HTTP 404 on the quickstart project
> >
> > Try http://localhost:8080 and http://localhost:8081
> >
> > The answer really will be in Start.java - see what port it is on and
> > where
> > the app is mounted.  Then make that into a URL.
> >
> > --
> > Jeremy Thomerson
> > http://www.wickettraining.com
> >
> >
> >
> > On Tue, Mar 24, 2009 at 3:19 PM, Chenini, Mohamed
> > <MC...@geico.com>wrote:
> >
> > > I tried http://localhost:8081/quickstart
> > >
> > > And the content of web.xml is:
> > >
> > >
> > > <filter>
> > >        <filter-name>wicket.QuickStart</filter-name>
> > >
> > >
> >
> <filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class
> > > >
> > >        <init-param>
> > >                <param-name>applicationClassName</param-name>
> > >
> > > <param-value>com.mycompany.app.WicketApplication</param-value>
> > >        </init-param>
> > > </filter>
> > >
> > > <filter-mapping>
> > >  <filter-name>wicket.QuickStart</filter-name>
> > >        <url-pattern>/*</url-pattern>
> > > </filter-mapping>
> > >
> > >
> > > -----Original Message-----
> > > From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
> > > Sent: Tuesday, March 24, 2009 4:17 PM
> > > To: users@wicket.apache.org
> > > Subject: Re: newbie question: HTTP 404 on the quickstart project
> > >
> > > Have you tried going to http://localhost:8081/quickstart ? or simply
> > > http://localhost:8081 ?
> > >
> > > --
> > > Jeremy Thomerson
> > > http://www.wickettraining.com
> > >
> > >
> > >
> > > On Tue, Mar 24, 2009 at 3:09 PM, Chenini, Mohamed
> > > <MC...@geico.com>wrote:
> > >
> > > > Hi,
> > > >
> > > > I setup the "quickstart" project using the imbedded jetty server
> and
> > > > started the jetty server from inside Eclipse (Right-click on
> > > > src/main/java and then click  on "Run as" "Java Application"
> > > >
> > > > But when I enter on the browser (IE) this URL:
> > > > http://localhost:8081/QuickStart
> > > >
> > > > I got this error:
> > > >
> > > >
> > > > HTTP ERROR: 404
> > > > NOT_FOUND
> > > > RequestURI=/QuickStart
> > > > I can send pieces of the code I am using if necessary to help
> > > determine
> > > > what is wrong.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Thanks,
> > > > Mohamed
> > > > ====================
> > > > This email/fax message is for the sole use of the intended
> > > > recipient(s) and may contain confidential and privileged
> > information.
> > > > Any unauthorized review, use, disclosure or distribution of this
> > > > email/fax is prohibited. If you are not the intended recipient,
> > please
> > > > destroy all paper and electronic copies of the original message.
> > > >
> > > ====================
> > > This email/fax message is for the sole use of the intended
> > > recipient(s) and may contain confidential and privileged
> information.
> > > Any unauthorized review, use, disclosure or distribution of this
> > > email/fax is prohibited. If you are not the intended recipient,
> please
> > > destroy all paper and electronic copies of the original message.
> > >
> > ====================
> > This email/fax message is for the sole use of the intended
> > recipient(s) and may contain confidential and privileged information.
> > Any unauthorized review, use, disclosure or distribution of this
> > email/fax is prohibited. If you are not the intended recipient, please
> > destroy all paper and electronic copies of the original message.
> >
> ====================
> This email/fax message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged information.
> Any unauthorized review, use, disclosure or distribution of this
> email/fax is prohibited. If you are not the intended recipient, please
> destroy all paper and electronic copies of the original message.
>

RE: newbie question: HTTP 404 on the quickstart project

Posted by "Chenini, Mohamed " <MC...@geico.com>.
Why URL http://localhost:8081/quickstart

Results on this error:

HTTP ERROR: 404
NOT_FOUND
RequestURI=/QuickStart


While jetty-config.xml has this entry:


<Call name="addWebApplication">
    <Arg>/QuickStart</Arg>
    <Arg>src/webapp</Arg>
</Call>

-----Original Message-----
From: Jeremy Thomerson [mailto:jeremy@wickettraining.com] 
Sent: Tuesday, March 24, 2009 4:30 PM
To: users@wicket.apache.org
Subject: Re: newbie question: HTTP 404 on the quickstart project

Okay - you found it.  What's the question?

--
Jeremy Thomerson
http://www.wickettraining.com



On Tue, Mar 24, 2009 at 3:28 PM, Chenini, Mohamed
<MC...@geico.com>wrote:

>
> Launching http://localhost:8081  produces this output:
>
> Wicket Quickstart Archetype Homepage
>
> If you see this message wicket is properly configured and running
>
>
>
> The jetty server is started and the console log shows this:
>
>
> INFO  - WebApplication             - [WicketApplication] Started
Wicket
> version 1.4-rc2 in development mode
> ********************************************************************
> *** WARNING: Wicket is running in DEVELOPMENT mode.              ***
> ***                               ^^^^^^^^^^^                    ***
> *** Do NOT deploy to your live server(s) without changing this.  ***
> *** See Application#getConfigurationType() for more information. ***
> ********************************************************************
> INFO  - log                        - Started
> SocketConnector@0.0.0.0:8081
>
>
>
> The Start.java code is as follows:
>
>
> mport org.mortbay.jetty.Connector;
> import org.mortbay.jetty.Server;
> import org.mortbay.jetty.bio.SocketConnector;
> import org.mortbay.jetty.webapp.WebAppContext;
>
> public class Start {
>
>        public static void main(String[] args) throws Exception {
>                Server server = new Server();
>                SocketConnector connector = new SocketConnector();
>
>                // Set some timeout options to make debugging easier.
>                connector.setMaxIdleTime(1000 * 60 * 60);
>                connector.setSoLingerTime(-1);
>                connector.setPort(8081);
>                server.setConnectors(new Connector[] { connector });
>
>                WebAppContext bb = new WebAppContext();
>                bb.setServer(server);
>                bb.setContextPath("/");
>                bb.setWar("src/main/webapp");
>
>                // START JMX SERVER
>                // MBeanServer mBeanServer =
> ManagementFactory.getPlatformMBeanServer();
>                // MBeanContainer mBeanContainer = new
> MBeanContainer(mBeanServer);
>                //
> server.getContainer().addEventListener(mBeanContainer);
>                // mBeanContainer.start();
>
>                server.addHandler(bb);
>
>                try {
>                        System.out.println(">>> STARTING EMBEDDED JETTY
> SERVER, PRESS ANY KEY TO STOP");
>                        server.start();
>                        System.in.read();
>                        System.out.println(">>> STOPPING EMBEDDED JETTY
> SERVER");
>            // while (System.in.available() == 0) {
>                        //   Thread.sleep(5000);
>                        // }
>                        server.stop();
>                        server.join();
>                } catch (Exception e) {
>                        e.printStackTrace();
>                        System.exit(100);
>                 }
>        }
> }
>
>
> -----Original Message-----
> From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
> Sent: Tuesday, March 24, 2009 4:23 PM
> To: users@wicket.apache.org
> Subject: Re: newbie question: HTTP 404 on the quickstart project
>
> Try http://localhost:8080 and http://localhost:8081
>
> The answer really will be in Start.java - see what port it is on and
> where
> the app is mounted.  Then make that into a URL.
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
> On Tue, Mar 24, 2009 at 3:19 PM, Chenini, Mohamed
> <MC...@geico.com>wrote:
>
> > I tried http://localhost:8081/quickstart
> >
> > And the content of web.xml is:
> >
> >
> > <filter>
> >        <filter-name>wicket.QuickStart</filter-name>
> >
> >
>
<filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class
> > >
> >        <init-param>
> >                <param-name>applicationClassName</param-name>
> >
> > <param-value>com.mycompany.app.WicketApplication</param-value>
> >        </init-param>
> > </filter>
> >
> > <filter-mapping>
> >  <filter-name>wicket.QuickStart</filter-name>
> >        <url-pattern>/*</url-pattern>
> > </filter-mapping>
> >
> >
> > -----Original Message-----
> > From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
> > Sent: Tuesday, March 24, 2009 4:17 PM
> > To: users@wicket.apache.org
> > Subject: Re: newbie question: HTTP 404 on the quickstart project
> >
> > Have you tried going to http://localhost:8081/quickstart ? or simply
> > http://localhost:8081 ?
> >
> > --
> > Jeremy Thomerson
> > http://www.wickettraining.com
> >
> >
> >
> > On Tue, Mar 24, 2009 at 3:09 PM, Chenini, Mohamed
> > <MC...@geico.com>wrote:
> >
> > > Hi,
> > >
> > > I setup the "quickstart" project using the imbedded jetty server
and
> > > started the jetty server from inside Eclipse (Right-click on
> > > src/main/java and then click  on "Run as" "Java Application"
> > >
> > > But when I enter on the browser (IE) this URL:
> > > http://localhost:8081/QuickStart
> > >
> > > I got this error:
> > >
> > >
> > > HTTP ERROR: 404
> > > NOT_FOUND
> > > RequestURI=/QuickStart
> > > I can send pieces of the code I am using if necessary to help
> > determine
> > > what is wrong.
> > >
> > >
> > >
> > >
> > >
> > > Thanks,
> > > Mohamed
> > > ====================
> > > This email/fax message is for the sole use of the intended
> > > recipient(s) and may contain confidential and privileged
> information.
> > > Any unauthorized review, use, disclosure or distribution of this
> > > email/fax is prohibited. If you are not the intended recipient,
> please
> > > destroy all paper and electronic copies of the original message.
> > >
> > ====================
> > This email/fax message is for the sole use of the intended
> > recipient(s) and may contain confidential and privileged
information.
> > Any unauthorized review, use, disclosure or distribution of this
> > email/fax is prohibited. If you are not the intended recipient,
please
> > destroy all paper and electronic copies of the original message.
> >
> ====================
> This email/fax message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged information.
> Any unauthorized review, use, disclosure or distribution of this
> email/fax is prohibited. If you are not the intended recipient, please
> destroy all paper and electronic copies of the original message.
>
====================
This email/fax message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution of this
email/fax is prohibited. If you are not the intended recipient, please
destroy all paper and electronic copies of the original message.

Re: newbie question: HTTP 404 on the quickstart project

Posted by Jeremy Thomerson <je...@wickettraining.com>.
Okay - you found it.  What's the question?

--
Jeremy Thomerson
http://www.wickettraining.com



On Tue, Mar 24, 2009 at 3:28 PM, Chenini, Mohamed <MC...@geico.com>wrote:

>
> Launching http://localhost:8081  produces this output:
>
> Wicket Quickstart Archetype Homepage
>
> If you see this message wicket is properly configured and running
>
>
>
> The jetty server is started and the console log shows this:
>
>
> INFO  - WebApplication             - [WicketApplication] Started Wicket
> version 1.4-rc2 in development mode
> ********************************************************************
> *** WARNING: Wicket is running in DEVELOPMENT mode.              ***
> ***                               ^^^^^^^^^^^                    ***
> *** Do NOT deploy to your live server(s) without changing this.  ***
> *** See Application#getConfigurationType() for more information. ***
> ********************************************************************
> INFO  - log                        - Started
> SocketConnector@0.0.0.0:8081
>
>
>
> The Start.java code is as follows:
>
>
> mport org.mortbay.jetty.Connector;
> import org.mortbay.jetty.Server;
> import org.mortbay.jetty.bio.SocketConnector;
> import org.mortbay.jetty.webapp.WebAppContext;
>
> public class Start {
>
>        public static void main(String[] args) throws Exception {
>                Server server = new Server();
>                SocketConnector connector = new SocketConnector();
>
>                // Set some timeout options to make debugging easier.
>                connector.setMaxIdleTime(1000 * 60 * 60);
>                connector.setSoLingerTime(-1);
>                connector.setPort(8081);
>                server.setConnectors(new Connector[] { connector });
>
>                WebAppContext bb = new WebAppContext();
>                bb.setServer(server);
>                bb.setContextPath("/");
>                bb.setWar("src/main/webapp");
>
>                // START JMX SERVER
>                // MBeanServer mBeanServer =
> ManagementFactory.getPlatformMBeanServer();
>                // MBeanContainer mBeanContainer = new
> MBeanContainer(mBeanServer);
>                //
> server.getContainer().addEventListener(mBeanContainer);
>                // mBeanContainer.start();
>
>                server.addHandler(bb);
>
>                try {
>                        System.out.println(">>> STARTING EMBEDDED JETTY
> SERVER, PRESS ANY KEY TO STOP");
>                        server.start();
>                        System.in.read();
>                        System.out.println(">>> STOPPING EMBEDDED JETTY
> SERVER");
>            // while (System.in.available() == 0) {
>                        //   Thread.sleep(5000);
>                        // }
>                        server.stop();
>                        server.join();
>                } catch (Exception e) {
>                        e.printStackTrace();
>                        System.exit(100);
>                 }
>        }
> }
>
>
> -----Original Message-----
> From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
> Sent: Tuesday, March 24, 2009 4:23 PM
> To: users@wicket.apache.org
> Subject: Re: newbie question: HTTP 404 on the quickstart project
>
> Try http://localhost:8080 and http://localhost:8081
>
> The answer really will be in Start.java - see what port it is on and
> where
> the app is mounted.  Then make that into a URL.
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
> On Tue, Mar 24, 2009 at 3:19 PM, Chenini, Mohamed
> <MC...@geico.com>wrote:
>
> > I tried http://localhost:8081/quickstart
> >
> > And the content of web.xml is:
> >
> >
> > <filter>
> >        <filter-name>wicket.QuickStart</filter-name>
> >
> >
> <filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class
> > >
> >        <init-param>
> >                <param-name>applicationClassName</param-name>
> >
> > <param-value>com.mycompany.app.WicketApplication</param-value>
> >        </init-param>
> > </filter>
> >
> > <filter-mapping>
> >  <filter-name>wicket.QuickStart</filter-name>
> >        <url-pattern>/*</url-pattern>
> > </filter-mapping>
> >
> >
> > -----Original Message-----
> > From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
> > Sent: Tuesday, March 24, 2009 4:17 PM
> > To: users@wicket.apache.org
> > Subject: Re: newbie question: HTTP 404 on the quickstart project
> >
> > Have you tried going to http://localhost:8081/quickstart ? or simply
> > http://localhost:8081 ?
> >
> > --
> > Jeremy Thomerson
> > http://www.wickettraining.com
> >
> >
> >
> > On Tue, Mar 24, 2009 at 3:09 PM, Chenini, Mohamed
> > <MC...@geico.com>wrote:
> >
> > > Hi,
> > >
> > > I setup the "quickstart" project using the imbedded jetty server and
> > > started the jetty server from inside Eclipse (Right-click on
> > > src/main/java and then click  on "Run as" "Java Application"
> > >
> > > But when I enter on the browser (IE) this URL:
> > > http://localhost:8081/QuickStart
> > >
> > > I got this error:
> > >
> > >
> > > HTTP ERROR: 404
> > > NOT_FOUND
> > > RequestURI=/QuickStart
> > > I can send pieces of the code I am using if necessary to help
> > determine
> > > what is wrong.
> > >
> > >
> > >
> > >
> > >
> > > Thanks,
> > > Mohamed
> > > ====================
> > > This email/fax message is for the sole use of the intended
> > > recipient(s) and may contain confidential and privileged
> information.
> > > Any unauthorized review, use, disclosure or distribution of this
> > > email/fax is prohibited. If you are not the intended recipient,
> please
> > > destroy all paper and electronic copies of the original message.
> > >
> > ====================
> > This email/fax message is for the sole use of the intended
> > recipient(s) and may contain confidential and privileged information.
> > Any unauthorized review, use, disclosure or distribution of this
> > email/fax is prohibited. If you are not the intended recipient, please
> > destroy all paper and electronic copies of the original message.
> >
> ====================
> This email/fax message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged information.
> Any unauthorized review, use, disclosure or distribution of this
> email/fax is prohibited. If you are not the intended recipient, please
> destroy all paper and electronic copies of the original message.
>

RE: newbie question: HTTP 404 on the quickstart project

Posted by "Chenini, Mohamed " <MC...@geico.com>.
Launching http://localhost:8081  produces this output:

Wicket Quickstart Archetype Homepage 

If you see this message wicket is properly configured and running



The jetty server is started and the console log shows this:


INFO  - WebApplication             - [WicketApplication] Started Wicket
version 1.4-rc2 in development mode
********************************************************************
*** WARNING: Wicket is running in DEVELOPMENT mode.              ***
***                               ^^^^^^^^^^^                    ***
*** Do NOT deploy to your live server(s) without changing this.  ***
*** See Application#getConfigurationType() for more information. ***
********************************************************************
INFO  - log                        - Started
SocketConnector@0.0.0.0:8081



The Start.java code is as follows:


mport org.mortbay.jetty.Connector;
import org.mortbay.jetty.Server;
import org.mortbay.jetty.bio.SocketConnector;
import org.mortbay.jetty.webapp.WebAppContext;

public class Start {

	public static void main(String[] args) throws Exception {
		Server server = new Server();
		SocketConnector connector = new SocketConnector();
		
		// Set some timeout options to make debugging easier.
		connector.setMaxIdleTime(1000 * 60 * 60);
		connector.setSoLingerTime(-1);
		connector.setPort(8081);
		server.setConnectors(new Connector[] { connector });

		WebAppContext bb = new WebAppContext();
		bb.setServer(server);
		bb.setContextPath("/");
		bb.setWar("src/main/webapp");
		
		// START JMX SERVER
		// MBeanServer mBeanServer =
ManagementFactory.getPlatformMBeanServer();
		// MBeanContainer mBeanContainer = new
MBeanContainer(mBeanServer);
		//
server.getContainer().addEventListener(mBeanContainer);
		// mBeanContainer.start();
		
		server.addHandler(bb);

		try {
			System.out.println(">>> STARTING EMBEDDED JETTY
SERVER, PRESS ANY KEY TO STOP");
			server.start();
			System.in.read();
			System.out.println(">>> STOPPING EMBEDDED JETTY
SERVER"); 
            // while (System.in.available() == 0) {
			//   Thread.sleep(5000);
			// }
			server.stop();
			server.join();
		} catch (Exception e) {
			e.printStackTrace();
			System.exit(100);
		}
	}
}


-----Original Message-----
From: Jeremy Thomerson [mailto:jeremy@wickettraining.com] 
Sent: Tuesday, March 24, 2009 4:23 PM
To: users@wicket.apache.org
Subject: Re: newbie question: HTTP 404 on the quickstart project

Try http://localhost:8080 and http://localhost:8081

The answer really will be in Start.java - see what port it is on and
where
the app is mounted.  Then make that into a URL.

--
Jeremy Thomerson
http://www.wickettraining.com



On Tue, Mar 24, 2009 at 3:19 PM, Chenini, Mohamed
<MC...@geico.com>wrote:

> I tried http://localhost:8081/quickstart
>
> And the content of web.xml is:
>
>
> <filter>
>        <filter-name>wicket.QuickStart</filter-name>
>
>
<filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class
> >
>        <init-param>
>                <param-name>applicationClassName</param-name>
>
> <param-value>com.mycompany.app.WicketApplication</param-value>
>        </init-param>
> </filter>
>
> <filter-mapping>
>  <filter-name>wicket.QuickStart</filter-name>
>        <url-pattern>/*</url-pattern>
> </filter-mapping>
>
>
> -----Original Message-----
> From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
> Sent: Tuesday, March 24, 2009 4:17 PM
> To: users@wicket.apache.org
> Subject: Re: newbie question: HTTP 404 on the quickstart project
>
> Have you tried going to http://localhost:8081/quickstart ? or simply
> http://localhost:8081 ?
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
> On Tue, Mar 24, 2009 at 3:09 PM, Chenini, Mohamed
> <MC...@geico.com>wrote:
>
> > Hi,
> >
> > I setup the "quickstart" project using the imbedded jetty server and
> > started the jetty server from inside Eclipse (Right-click on
> > src/main/java and then click  on "Run as" "Java Application"
> >
> > But when I enter on the browser (IE) this URL:
> > http://localhost:8081/QuickStart
> >
> > I got this error:
> >
> >
> > HTTP ERROR: 404
> > NOT_FOUND
> > RequestURI=/QuickStart
> > I can send pieces of the code I am using if necessary to help
> determine
> > what is wrong.
> >
> >
> >
> >
> >
> > Thanks,
> > Mohamed
> > ====================
> > This email/fax message is for the sole use of the intended
> > recipient(s) and may contain confidential and privileged
information.
> > Any unauthorized review, use, disclosure or distribution of this
> > email/fax is prohibited. If you are not the intended recipient,
please
> > destroy all paper and electronic copies of the original message.
> >
> ====================
> This email/fax message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged information.
> Any unauthorized review, use, disclosure or distribution of this
> email/fax is prohibited. If you are not the intended recipient, please
> destroy all paper and electronic copies of the original message.
>
====================
This email/fax message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution of this
email/fax is prohibited. If you are not the intended recipient, please
destroy all paper and electronic copies of the original message.

Re: newbie question: HTTP 404 on the quickstart project

Posted by Jeremy Thomerson <je...@wickettraining.com>.
Try http://localhost:8080 and http://localhost:8081

The answer really will be in Start.java - see what port it is on and where
the app is mounted.  Then make that into a URL.

--
Jeremy Thomerson
http://www.wickettraining.com



On Tue, Mar 24, 2009 at 3:19 PM, Chenini, Mohamed <MC...@geico.com>wrote:

> I tried http://localhost:8081/quickstart
>
> And the content of web.xml is:
>
>
> <filter>
>        <filter-name>wicket.QuickStart</filter-name>
>
> <filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class
> >
>        <init-param>
>                <param-name>applicationClassName</param-name>
>
> <param-value>com.mycompany.app.WicketApplication</param-value>
>        </init-param>
> </filter>
>
> <filter-mapping>
>  <filter-name>wicket.QuickStart</filter-name>
>        <url-pattern>/*</url-pattern>
> </filter-mapping>
>
>
> -----Original Message-----
> From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
> Sent: Tuesday, March 24, 2009 4:17 PM
> To: users@wicket.apache.org
> Subject: Re: newbie question: HTTP 404 on the quickstart project
>
> Have you tried going to http://localhost:8081/quickstart ? or simply
> http://localhost:8081 ?
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
> On Tue, Mar 24, 2009 at 3:09 PM, Chenini, Mohamed
> <MC...@geico.com>wrote:
>
> > Hi,
> >
> > I setup the "quickstart" project using the imbedded jetty server and
> > started the jetty server from inside Eclipse (Right-click on
> > src/main/java and then click  on "Run as" "Java Application"
> >
> > But when I enter on the browser (IE) this URL:
> > http://localhost:8081/QuickStart
> >
> > I got this error:
> >
> >
> > HTTP ERROR: 404
> > NOT_FOUND
> > RequestURI=/QuickStart
> > I can send pieces of the code I am using if necessary to help
> determine
> > what is wrong.
> >
> >
> >
> >
> >
> > Thanks,
> > Mohamed
> > ====================
> > This email/fax message is for the sole use of the intended
> > recipient(s) and may contain confidential and privileged information.
> > Any unauthorized review, use, disclosure or distribution of this
> > email/fax is prohibited. If you are not the intended recipient, please
> > destroy all paper and electronic copies of the original message.
> >
> ====================
> This email/fax message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged information.
> Any unauthorized review, use, disclosure or distribution of this
> email/fax is prohibited. If you are not the intended recipient, please
> destroy all paper and electronic copies of the original message.
>

RE: newbie question: HTTP 404 on the quickstart project

Posted by "Chenini, Mohamed " <MC...@geico.com>.
I tried http://localhost:8081/quickstart

And the content of web.xml is:


<filter>
	<filter-name>wicket.QuickStart</filter-name>
	
<filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class
>
	<init-param>
		<param-name>applicationClassName</param-name>
	
<param-value>com.mycompany.app.WicketApplication</param-value>
	</init-param>
</filter>

<filter-mapping>
  <filter-name>wicket.QuickStart</filter-name>
	<url-pattern>/*</url-pattern>
</filter-mapping>	


-----Original Message-----
From: Jeremy Thomerson [mailto:jeremy@wickettraining.com] 
Sent: Tuesday, March 24, 2009 4:17 PM
To: users@wicket.apache.org
Subject: Re: newbie question: HTTP 404 on the quickstart project

Have you tried going to http://localhost:8081/quickstart ? or simply
http://localhost:8081 ?

--
Jeremy Thomerson
http://www.wickettraining.com



On Tue, Mar 24, 2009 at 3:09 PM, Chenini, Mohamed
<MC...@geico.com>wrote:

> Hi,
>
> I setup the "quickstart" project using the imbedded jetty server and
> started the jetty server from inside Eclipse (Right-click on
> src/main/java and then click  on "Run as" "Java Application"
>
> But when I enter on the browser (IE) this URL:
> http://localhost:8081/QuickStart
>
> I got this error:
>
>
> HTTP ERROR: 404
> NOT_FOUND
> RequestURI=/QuickStart
> I can send pieces of the code I am using if necessary to help
determine
> what is wrong.
>
>
>
>
>
> Thanks,
> Mohamed
> ====================
> This email/fax message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged information.
> Any unauthorized review, use, disclosure or distribution of this
> email/fax is prohibited. If you are not the intended recipient, please
> destroy all paper and electronic copies of the original message.
>
====================
This email/fax message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution of this
email/fax is prohibited. If you are not the intended recipient, please
destroy all paper and electronic copies of the original message.

Re: newbie question: HTTP 404 on the quickstart project

Posted by Jeremy Thomerson <je...@wickettraining.com>.
Have you tried going to http://localhost:8081/quickstart ? or simply
http://localhost:8081 ?

--
Jeremy Thomerson
http://www.wickettraining.com



On Tue, Mar 24, 2009 at 3:09 PM, Chenini, Mohamed <MC...@geico.com>wrote:

> Hi,
>
> I setup the "quickstart" project using the imbedded jetty server and
> started the jetty server from inside Eclipse (Right-click on
> src/main/java and then click  on "Run as" "Java Application"
>
> But when I enter on the browser (IE) this URL:
> http://localhost:8081/QuickStart
>
> I got this error:
>
>
> HTTP ERROR: 404
> NOT_FOUND
> RequestURI=/QuickStart
> I can send pieces of the code I am using if necessary to help determine
> what is wrong.
>
>
>
>
>
> Thanks,
> Mohamed
> ====================
> This email/fax message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged information.
> Any unauthorized review, use, disclosure or distribution of this
> email/fax is prohibited. If you are not the intended recipient, please
> destroy all paper and electronic copies of the original message.
>

newbie question: HTTP 404 on the quickstart project

Posted by "Chenini, Mohamed " <MC...@geico.com>.
Hi,

I setup the "quickstart" project using the imbedded jetty server and
started the jetty server from inside Eclipse (Right-click on
src/main/java and then click  on "Run as" "Java Application"

But when I enter on the browser (IE) this URL:
http://localhost:8081/QuickStart

I got this error:


HTTP ERROR: 404
NOT_FOUND
RequestURI=/QuickStart
I can send pieces of the code I am using if necessary to help determine
what is wrong.





Thanks,
Mohamed
====================
This email/fax message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution of this
email/fax is prohibited. If you are not the intended recipient, please
destroy all paper and electronic copies of the original message.

Re: wicketstuff / ki / jsecurity

Posted by nino martinez wael <ni...@gmail.com>.
2009/3/25 Martin Funk <ma...@googlemail.com>:
>
> Am 25.03.2009 um 10:17 schrieb nino martinez wael:
>
>> The problem with wicket stuff have been cleared up a bit, the part about
>> which projects are dead and not.. Those in wicketstuff-core are alive, and
>> if they become incompatible with the current version of wicket they will
>> be
>> kicked..
>
> are they? I mean alive.

AFAIK inmethod are not part of wicketstuff core
> Locking here:
> http://wicketstuff.org/teamcity/viewLog.html?buildId=3486&tab=buildResultsDiv&buildTypeId=bt35
> I'd say it's at least not compiling no more.
>
> Could someone please fix that?
>
> mf
>
>>
>>
>> 2009/3/25 Maarten Bosteels <mb...@gmail.com>
>>
>>> Hi Ryan,
>>>
>>> I added you to the Project Members, so feel free to commit your examples.
>>> Unfortunately, until now I haven't had time to work on it myself
>>>
>>> The idea was to let the code mature in
>>> http://code.google.com/p/wicket-jsecurity/
>>> and maybe move it to wicket-stuff later on.
>>>
>>> Maybe we should move it to wicket-stuff already.
>>> My main problem with wicket-stuff is/was that it's not always very clear
>>> which projects are still alive and maintained and which are practically
>>> dead. And at the time, wicket-stuff had some problems with continuous
>>> integration, IIRC.
>>>
>>> Les, what do you think ?
>>> We should change the project name to wicket-ki anyway.
>>>
>>> regards,
>>> Maarten
>>>
>>> On Wed, Mar 25, 2009 at 7:47 AM, nino martinez wael <
>>> nino.martinez.wael@gmail.com> wrote:
>>>
>>>> Yeah I've for one always been very pro for wicketstuff.. It's nice
>>>
>>> keeping
>>>>
>>>> things in one place.. Plus as you write if we share a somewhat similar
>>>> structure it's potentially easier to maintain..
>>>>
>>>> 2009/3/24 Ryan McKinley <ry...@gmail.com>
>>>>
>>>>> Hi-
>>>>>
>>>>> I've been looking to integrate a complex security model with wicket --
>>>>> jsecurity seems really good.  I tried messing with:
>>>>> http://code.google.com/p/wicket-jsecurity/
>>>>>
>>>>> This appears to be a starting place, but does not have any running
>>>>
>>>> example.
>>>>>
>>>>> In an effort to get things running (and learn JSecurity) i took that +
>>>>> wicket-auth-roles and tried to make a functioning core + example.  I've
>>>>
>>>> got
>>>>>
>>>>> something running and would love to share it...
>>>>>
>>>>> Should I post this to the google code site?
>>>>>
>>>>> It makes more sense (to me) if we keep it in the wicketstuff repos --
>>>>
>>>> that
>>>>>
>>>>> way we get the benefit of Jeremy's work to make wickettuff-core much
>>>>> cleaner.
>>>>>
>>>>> Thoughts?
>>>>>
>>>>> Ryan
>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> 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
>
>

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


Re: wicketstuff / ki / jsecurity

Posted by Ryan McKinley <ry...@gmail.com>.
dooh -- totally my fault.  I unintentionally posted some local changes:

/trunk/wicketstuff-core/inmethod-grid-parent/inmethod-grid/src/main/ 
java/com/inmethod/grid/DataProviderAdapter.java
/trunk/wicketstuff-core/inmethod-grid-parent/inmethod-grid/src/main/ 
java/com/inmethod/grid/IDataSource.java
/trunk/wicketstuff-core/inmethod-grid-parent/inmethod-grid-examples/ 
pom.xml
/trunk/wicketstuff-core/inmethod-grid-parent/inmethod-grid-examples/ 
src/main/java/com/inmethod/grid/examples/WicketApplication.java
/trunk/wicketstuff-core/inmethod-grid-parent/inmethod-grid-examples/ 
src/main/java/com/inmethod/grid/examples/contact/ 
DetachableContactModel.java
/trunk/wicketstuff-core/inmethod-grid-parent/inmethod-grid-examples/ 
src/main/java/com/inmethod/grid/examples/pages/BaseExamplePage.html
/trunk/wicketstuff-core/inmethod-grid-parent/inmethod-grid-examples/ 
src/main/java/com/inmethod/grid/examples/pages/datagrid/ 
ContactDataSource.java
/trunk/wicketstuff-core/inmethod-grid-parent/inmethod-grid-examples/ 
src/main/java/com/inmethod/grid/examples/pages/datagrid/ 
ContactDataSourceWithUnknownItemCount.java

now I'll figure out how to revert that...

ryan


On Mar 25, 2009, at 11:59 AM, Jeremy Thomerson wrote:

> http://www.wickettraining.com/continuum/buildResult.action?buildId=6786&projectId=248&projectGroupId=2
>
> That shows what commit it started failing on, etc.
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
> On Wed, Mar 25, 2009 at 10:53 AM, Ryan McKinley <ry...@gmail.com>  
> wrote:
>
>> Hymm.  I'm not sure what it could be...  I did copy the inmethod- 
>> grid pom
>> to cuild the ki-secuity pom, but I think i got rid of any conflicts.
>>
>> What is the error the Continuum server spits out?  Perhaps it has  
>> something
>> to do with syringe?  (committed about the same time as ki- 
>> security)  When I
>> try to build wicketstuff-core now, I get the following error:
>>
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Failed to resolve artifact.
>>
>> Missing:
>> ----------
>> 1) org.apache.commons:commons-proxy:jar:1.1-SNAPSHOT
>>
>> Try downloading the file manually from the project website.
>>
>> Then, install it using the command:
>>     mvn install:install-file -DgroupId=org.apache.commons
>> -DartifactId=commons-proxy -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file
>>
>> Alternatively, if you host your own repository you can deploy the  
>> file
>> there:
>>     mvn deploy:deploy-file -DgroupId=org.apache.commons
>> -DartifactId=commons-proxy -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>
>> Path to dependency:
>>       1) org.wicketstuff:wicket-syringe:jar:1.4-SNAPSHOT
>>       2) org.apache.commons:commons-proxy:jar:1.1-SNAPSHOT
>>
>> ----------
>> 1 required artifact is missing.
>>
>> for artifact:
>> org.wicketstuff:wicket-syringe:jar:1.4-SNAPSHOT
>>
>> from the specified remote repositories:
>> wicket-snaps (http://wicketstuff.org/maven/repository),
>> central (http://repo1.maven.org/maven2)
>>
>>
>>
>>
>> On Mar 25, 2009, at 11:21 AM, Jeremy Thomerson wrote:
>>
>> I run Continuum on my server and just started receiving  
>> notifications two
>>> days ago that inmethod grid was not compiling.  It showed up right  
>>> after
>>> the
>>> commit of this ki security stuff.
>>>
>>> I haven't looked at it yet, hoping that someone who was working  
>>> with ki
>>> security or inmethod would do so.
>>>
>>> --
>>> Jeremy Thomerson
>>> http://www.wickettraining.com
>>>
>>>
>>>
>>> On Wed, Mar 25, 2009 at 5:48 AM, Martin Funk <mafulafunk@googlemail.com
>>>> wrote:
>>>
>>>
>>>> Am 25.03.2009 um 10:17 schrieb nino martinez wael:
>>>>
>>>> The problem with wicket stuff have been cleared up a bit, the  
>>>> part about
>>>>
>>>>> which projects are dead and not.. Those in wicketstuff-core are  
>>>>> alive,
>>>>> and
>>>>> if they become incompatible with the current version of wicket  
>>>>> they will
>>>>> be
>>>>> kicked..
>>>>>
>>>>> are they? I mean alive.
>>>> Locking here:
>>>>
>>>>
>>>> http://wicketstuff.org/teamcity/viewLog.html?buildId=3486&tab=buildResultsDiv&buildTypeId=bt35
>>>> I'd say it's at least not compiling no more.
>>>>
>>>> Could someone please fix that?
>>>>
>>>> mf
>>>>
>>>>
>>>>
>>>>
>>>>> 2009/3/25 Maarten Bosteels <mb...@gmail.com>
>>>>>
>>>>> Hi Ryan,
>>>>>
>>>>>>
>>>>>> I added you to the Project Members, so feel free to commit your
>>>>>> examples.
>>>>>> Unfortunately, until now I haven't had time to work on it myself
>>>>>>
>>>>>> The idea was to let the code mature in
>>>>>> http://code.google.com/p/wicket-jsecurity/
>>>>>> and maybe move it to wicket-stuff later on.
>>>>>>
>>>>>> Maybe we should move it to wicket-stuff already.
>>>>>> My main problem with wicket-stuff is/was that it's not always  
>>>>>> very
>>>>>> clear
>>>>>> which projects are still alive and maintained and which are  
>>>>>> practically
>>>>>> dead. And at the time, wicket-stuff had some problems with  
>>>>>> continuous
>>>>>> integration, IIRC.
>>>>>>
>>>>>> Les, what do you think ?
>>>>>> We should change the project name to wicket-ki anyway.
>>>>>>
>>>>>> regards,
>>>>>> Maarten
>>>>>>
>>>>>> On Wed, Mar 25, 2009 at 7:47 AM, nino martinez wael <
>>>>>> nino.martinez.wael@gmail.com> wrote:
>>>>>>
>>>>>> Yeah I've for one always been very pro for wicketstuff.. It's  
>>>>>> nice
>>>>>>
>>>>>>>
>>>>>>> keeping
>>>>>>
>>>>>> things in one place.. Plus as you write if we share a somewhat  
>>>>>> similar
>>>>>>> structure it's potentially easier to maintain..
>>>>>>>
>>>>>>> 2009/3/24 Ryan McKinley <ry...@gmail.com>
>>>>>>>
>>>>>>> Hi-
>>>>>>>
>>>>>>>>
>>>>>>>> I've been looking to integrate a complex security model with  
>>>>>>>> wicket
>>>>>>>> --
>>>>>>>> jsecurity seems really good.  I tried messing with:
>>>>>>>> http://code.google.com/p/wicket-jsecurity/
>>>>>>>>
>>>>>>>> This appears to be a starting place, but does not have any  
>>>>>>>> running
>>>>>>>>
>>>>>>>> example.
>>>>>>>
>>>>>>>
>>>>>>>> In an effort to get things running (and learn JSecurity) i  
>>>>>>>> took that
>>>>>>>> +
>>>>>>>> wicket-auth-roles and tried to make a functioning core +  
>>>>>>>> example.
>>>>>>>> I've
>>>>>>>>
>>>>>>>> got
>>>>>>>
>>>>>>> something running and would love to share it...
>>>>>>>>
>>>>>>>> Should I post this to the google code site?
>>>>>>>>
>>>>>>>> It makes more sense (to me) if we keep it in the wicketstuff  
>>>>>>>> repos --
>>>>>>>>
>>>>>>>> that
>>>>>>>
>>>>>>> way we get the benefit of Jeremy's work to make wickettuff- 
>>>>>>> core much
>>>>>>>> cleaner.
>>>>>>>>
>>>>>>>> Thoughts?
>>>>>>>>
>>>>>>>> Ryan
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> 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
>>>>
>>>>
>>>>
>>
>> ---------------------------------------------------------------------
>> 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: wicketstuff / ki / jsecurity

Posted by Jeremy Thomerson <je...@wickettraining.com>.
http://www.wickettraining.com/continuum/buildResult.action?buildId=6786&projectId=248&projectGroupId=2

That shows what commit it started failing on, etc.

--
Jeremy Thomerson
http://www.wickettraining.com



On Wed, Mar 25, 2009 at 10:53 AM, Ryan McKinley <ry...@gmail.com> wrote:

> Hymm.  I'm not sure what it could be...  I did copy the inmethod-grid pom
> to cuild the ki-secuity pom, but I think i got rid of any conflicts.
>
> What is the error the Continuum server spits out?  Perhaps it has something
> to do with syringe?  (committed about the same time as ki-security)  When I
> try to build wicketstuff-core now, I get the following error:
>
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> Missing:
> ----------
> 1) org.apache.commons:commons-proxy:jar:1.1-SNAPSHOT
>
>  Try downloading the file manually from the project website.
>
>  Then, install it using the command:
>      mvn install:install-file -DgroupId=org.apache.commons
> -DartifactId=commons-proxy -Dversion=1.1-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
>
>  Alternatively, if you host your own repository you can deploy the file
> there:
>      mvn deploy:deploy-file -DgroupId=org.apache.commons
> -DartifactId=commons-proxy -Dversion=1.1-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>  Path to dependency:
>        1) org.wicketstuff:wicket-syringe:jar:1.4-SNAPSHOT
>        2) org.apache.commons:commons-proxy:jar:1.1-SNAPSHOT
>
> ----------
> 1 required artifact is missing.
>
> for artifact:
>  org.wicketstuff:wicket-syringe:jar:1.4-SNAPSHOT
>
> from the specified remote repositories:
>  wicket-snaps (http://wicketstuff.org/maven/repository),
>  central (http://repo1.maven.org/maven2)
>
>
>
>
> On Mar 25, 2009, at 11:21 AM, Jeremy Thomerson wrote:
>
>  I run Continuum on my server and just started receiving notifications two
>> days ago that inmethod grid was not compiling.  It showed up right after
>> the
>> commit of this ki security stuff.
>>
>> I haven't looked at it yet, hoping that someone who was working with ki
>> security or inmethod would do so.
>>
>> --
>> Jeremy Thomerson
>> http://www.wickettraining.com
>>
>>
>>
>> On Wed, Mar 25, 2009 at 5:48 AM, Martin Funk <mafulafunk@googlemail.com
>> >wrote:
>>
>>
>>> Am 25.03.2009 um 10:17 schrieb nino martinez wael:
>>>
>>> The problem with wicket stuff have been cleared up a bit, the part about
>>>
>>>> which projects are dead and not.. Those in wicketstuff-core are alive,
>>>> and
>>>> if they become incompatible with the current version of wicket they will
>>>> be
>>>> kicked..
>>>>
>>>>  are they? I mean alive.
>>> Locking here:
>>>
>>>
>>> http://wicketstuff.org/teamcity/viewLog.html?buildId=3486&tab=buildResultsDiv&buildTypeId=bt35
>>> I'd say it's at least not compiling no more.
>>>
>>> Could someone please fix that?
>>>
>>> mf
>>>
>>>
>>>
>>>
>>>> 2009/3/25 Maarten Bosteels <mb...@gmail.com>
>>>>
>>>> Hi Ryan,
>>>>
>>>>>
>>>>> I added you to the Project Members, so feel free to commit your
>>>>> examples.
>>>>> Unfortunately, until now I haven't had time to work on it myself
>>>>>
>>>>> The idea was to let the code mature in
>>>>> http://code.google.com/p/wicket-jsecurity/
>>>>> and maybe move it to wicket-stuff later on.
>>>>>
>>>>> Maybe we should move it to wicket-stuff already.
>>>>> My main problem with wicket-stuff is/was that it's not always very
>>>>> clear
>>>>> which projects are still alive and maintained and which are practically
>>>>> dead. And at the time, wicket-stuff had some problems with continuous
>>>>> integration, IIRC.
>>>>>
>>>>> Les, what do you think ?
>>>>> We should change the project name to wicket-ki anyway.
>>>>>
>>>>> regards,
>>>>> Maarten
>>>>>
>>>>> On Wed, Mar 25, 2009 at 7:47 AM, nino martinez wael <
>>>>> nino.martinez.wael@gmail.com> wrote:
>>>>>
>>>>> Yeah I've for one always been very pro for wicketstuff.. It's nice
>>>>>
>>>>>>
>>>>>>  keeping
>>>>>
>>>>>  things in one place.. Plus as you write if we share a somewhat similar
>>>>>> structure it's potentially easier to maintain..
>>>>>>
>>>>>> 2009/3/24 Ryan McKinley <ry...@gmail.com>
>>>>>>
>>>>>> Hi-
>>>>>>
>>>>>>>
>>>>>>> I've been looking to integrate a complex security model with wicket
>>>>>>> --
>>>>>>> jsecurity seems really good.  I tried messing with:
>>>>>>> http://code.google.com/p/wicket-jsecurity/
>>>>>>>
>>>>>>> This appears to be a starting place, but does not have any running
>>>>>>>
>>>>>>>  example.
>>>>>>
>>>>>>
>>>>>>> In an effort to get things running (and learn JSecurity) i took that
>>>>>>> +
>>>>>>> wicket-auth-roles and tried to make a functioning core + example.
>>>>>>>  I've
>>>>>>>
>>>>>>>  got
>>>>>>
>>>>>>  something running and would love to share it...
>>>>>>>
>>>>>>> Should I post this to the google code site?
>>>>>>>
>>>>>>> It makes more sense (to me) if we keep it in the wicketstuff repos --
>>>>>>>
>>>>>>>  that
>>>>>>
>>>>>>  way we get the benefit of Jeremy's work to make wickettuff-core much
>>>>>>> cleaner.
>>>>>>>
>>>>>>> Thoughts?
>>>>>>>
>>>>>>> Ryan
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> 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
>>>
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

Re: wicketstuff / ki / jsecurity

Posted by James Carman <jc...@carmanconsulting.com>.
The commons-proxy snapshots will be in the repository on the build
server, because it's also running in the build server.

On Wed, Mar 25, 2009 at 11:53 AM, Ryan McKinley <ry...@gmail.com> wrote:
> Hymm.  I'm not sure what it could be...  I did copy the inmethod-grid pom to
> cuild the ki-secuity pom, but I think i got rid of any conflicts.
>
> What is the error the Continuum server spits out?  Perhaps it has something
> to do with syringe?  (committed about the same time as ki-security)  When I
> try to build wicketstuff-core now, I get the following error:
>
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> Missing:
> ----------
> 1) org.apache.commons:commons-proxy:jar:1.1-SNAPSHOT
>
>  Try downloading the file manually from the project website.
>
>  Then, install it using the command:
>      mvn install:install-file -DgroupId=org.apache.commons
> -DartifactId=commons-proxy -Dversion=1.1-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
>
>  Alternatively, if you host your own repository you can deploy the file
> there:
>      mvn deploy:deploy-file -DgroupId=org.apache.commons
> -DartifactId=commons-proxy -Dversion=1.1-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>  Path to dependency:
>        1) org.wicketstuff:wicket-syringe:jar:1.4-SNAPSHOT
>        2) org.apache.commons:commons-proxy:jar:1.1-SNAPSHOT
>
> ----------
> 1 required artifact is missing.
>
> for artifact:
>  org.wicketstuff:wicket-syringe:jar:1.4-SNAPSHOT
>
> from the specified remote repositories:
>  wicket-snaps (http://wicketstuff.org/maven/repository),
>  central (http://repo1.maven.org/maven2)
>
>
>
> On Mar 25, 2009, at 11:21 AM, Jeremy Thomerson wrote:
>
>> I run Continuum on my server and just started receiving notifications two
>> days ago that inmethod grid was not compiling.  It showed up right after
>> the
>> commit of this ki security stuff.
>>
>> I haven't looked at it yet, hoping that someone who was working with ki
>> security or inmethod would do so.
>>
>> --
>> Jeremy Thomerson
>> http://www.wickettraining.com
>>
>>
>>
>> On Wed, Mar 25, 2009 at 5:48 AM, Martin Funk
>> <ma...@googlemail.com>wrote:
>>
>>>
>>> Am 25.03.2009 um 10:17 schrieb nino martinez wael:
>>>
>>> The problem with wicket stuff have been cleared up a bit, the part about
>>>>
>>>> which projects are dead and not.. Those in wicketstuff-core are alive,
>>>> and
>>>> if they become incompatible with the current version of wicket they will
>>>> be
>>>> kicked..
>>>>
>>> are they? I mean alive.
>>> Locking here:
>>>
>>>
>>> http://wicketstuff.org/teamcity/viewLog.html?buildId=3486&tab=buildResultsDiv&buildTypeId=bt35
>>> I'd say it's at least not compiling no more.
>>>
>>> Could someone please fix that?
>>>
>>> mf
>>>
>>>
>>>
>>>>
>>>> 2009/3/25 Maarten Bosteels <mb...@gmail.com>
>>>>
>>>> Hi Ryan,
>>>>>
>>>>> I added you to the Project Members, so feel free to commit your
>>>>> examples.
>>>>> Unfortunately, until now I haven't had time to work on it myself
>>>>>
>>>>> The idea was to let the code mature in
>>>>> http://code.google.com/p/wicket-jsecurity/
>>>>> and maybe move it to wicket-stuff later on.
>>>>>
>>>>> Maybe we should move it to wicket-stuff already.
>>>>> My main problem with wicket-stuff is/was that it's not always very
>>>>> clear
>>>>> which projects are still alive and maintained and which are practically
>>>>> dead. And at the time, wicket-stuff had some problems with continuous
>>>>> integration, IIRC.
>>>>>
>>>>> Les, what do you think ?
>>>>> We should change the project name to wicket-ki anyway.
>>>>>
>>>>> regards,
>>>>> Maarten
>>>>>
>>>>> On Wed, Mar 25, 2009 at 7:47 AM, nino martinez wael <
>>>>> nino.martinez.wael@gmail.com> wrote:
>>>>>
>>>>> Yeah I've for one always been very pro for wicketstuff.. It's nice
>>>>>>
>>>>> keeping
>>>>>
>>>>>> things in one place.. Plus as you write if we share a somewhat similar
>>>>>> structure it's potentially easier to maintain..
>>>>>>
>>>>>> 2009/3/24 Ryan McKinley <ry...@gmail.com>
>>>>>>
>>>>>> Hi-
>>>>>>>
>>>>>>> I've been looking to integrate a complex security model with wicket
>>>>>>> --
>>>>>>> jsecurity seems really good.  I tried messing with:
>>>>>>> http://code.google.com/p/wicket-jsecurity/
>>>>>>>
>>>>>>> This appears to be a starting place, but does not have any running
>>>>>>>
>>>>>> example.
>>>>>>
>>>>>>>
>>>>>>> In an effort to get things running (and learn JSecurity) i took that
>>>>>>> +
>>>>>>> wicket-auth-roles and tried to make a functioning core + example.
>>>>>>>  I've
>>>>>>>
>>>>>> got
>>>>>>
>>>>>>> something running and would love to share it...
>>>>>>>
>>>>>>> Should I post this to the google code site?
>>>>>>>
>>>>>>> It makes more sense (to me) if we keep it in the wicketstuff repos --
>>>>>>>
>>>>>> that
>>>>>>
>>>>>>> way we get the benefit of Jeremy's work to make wickettuff-core much
>>>>>>> cleaner.
>>>>>>>
>>>>>>> Thoughts?
>>>>>>>
>>>>>>> Ryan
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> 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
>>>
>>>
>
>
> ---------------------------------------------------------------------
> 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: wicketstuff / ki / jsecurity

Posted by Ryan McKinley <ry...@gmail.com>.
Hymm.  I'm not sure what it could be...  I did copy the inmethod-grid  
pom to cuild the ki-secuity pom, but I think i got rid of any conflicts.

What is the error the Continuum server spits out?  Perhaps it has  
something to do with syringe?  (committed about the same time as ki- 
security)  When I try to build wicketstuff-core now, I get the  
following error:


[INFO]  
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]  
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) org.apache.commons:commons-proxy:jar:1.1-SNAPSHOT

   Try downloading the file manually from the project website.

   Then, install it using the command:
       mvn install:install-file -DgroupId=org.apache.commons - 
DartifactId=commons-proxy -Dversion=1.1-SNAPSHOT -Dpackaging=jar - 
Dfile=/path/to/file

   Alternatively, if you host your own repository you can deploy the  
file there:
       mvn deploy:deploy-file -DgroupId=org.apache.commons - 
DartifactId=commons-proxy -Dversion=1.1-SNAPSHOT -Dpackaging=jar - 
Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

   Path to dependency:
   	1) org.wicketstuff:wicket-syringe:jar:1.4-SNAPSHOT
   	2) org.apache.commons:commons-proxy:jar:1.1-SNAPSHOT

----------
1 required artifact is missing.

for artifact:
   org.wicketstuff:wicket-syringe:jar:1.4-SNAPSHOT

from the specified remote repositories:
   wicket-snaps (http://wicketstuff.org/maven/repository),
   central (http://repo1.maven.org/maven2)



On Mar 25, 2009, at 11:21 AM, Jeremy Thomerson wrote:

> I run Continuum on my server and just started receiving  
> notifications two
> days ago that inmethod grid was not compiling.  It showed up right  
> after the
> commit of this ki security stuff.
>
> I haven't looked at it yet, hoping that someone who was working with  
> ki
> security or inmethod would do so.
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
> On Wed, Mar 25, 2009 at 5:48 AM, Martin Funk <mafulafunk@googlemail.com 
> >wrote:
>
>>
>> Am 25.03.2009 um 10:17 schrieb nino martinez wael:
>>
>> The problem with wicket stuff have been cleared up a bit, the part  
>> about
>>> which projects are dead and not.. Those in wicketstuff-core are  
>>> alive, and
>>> if they become incompatible with the current version of wicket  
>>> they will
>>> be
>>> kicked..
>>>
>> are they? I mean alive.
>> Locking here:
>>
>> http://wicketstuff.org/teamcity/viewLog.html?buildId=3486&tab=buildResultsDiv&buildTypeId=bt35
>> I'd say it's at least not compiling no more.
>>
>> Could someone please fix that?
>>
>> mf
>>
>>
>>
>>>
>>> 2009/3/25 Maarten Bosteels <mb...@gmail.com>
>>>
>>> Hi Ryan,
>>>>
>>>> I added you to the Project Members, so feel free to commit your  
>>>> examples.
>>>> Unfortunately, until now I haven't had time to work on it myself
>>>>
>>>> The idea was to let the code mature in
>>>> http://code.google.com/p/wicket-jsecurity/
>>>> and maybe move it to wicket-stuff later on.
>>>>
>>>> Maybe we should move it to wicket-stuff already.
>>>> My main problem with wicket-stuff is/was that it's not always  
>>>> very clear
>>>> which projects are still alive and maintained and which are  
>>>> practically
>>>> dead. And at the time, wicket-stuff had some problems with  
>>>> continuous
>>>> integration, IIRC.
>>>>
>>>> Les, what do you think ?
>>>> We should change the project name to wicket-ki anyway.
>>>>
>>>> regards,
>>>> Maarten
>>>>
>>>> On Wed, Mar 25, 2009 at 7:47 AM, nino martinez wael <
>>>> nino.martinez.wael@gmail.com> wrote:
>>>>
>>>> Yeah I've for one always been very pro for wicketstuff.. It's nice
>>>>>
>>>> keeping
>>>>
>>>>> things in one place.. Plus as you write if we share a somewhat  
>>>>> similar
>>>>> structure it's potentially easier to maintain..
>>>>>
>>>>> 2009/3/24 Ryan McKinley <ry...@gmail.com>
>>>>>
>>>>> Hi-
>>>>>>
>>>>>> I've been looking to integrate a complex security model with  
>>>>>> wicket --
>>>>>> jsecurity seems really good.  I tried messing with:
>>>>>> http://code.google.com/p/wicket-jsecurity/
>>>>>>
>>>>>> This appears to be a starting place, but does not have any  
>>>>>> running
>>>>>>
>>>>> example.
>>>>>
>>>>>>
>>>>>> In an effort to get things running (and learn JSecurity) i took  
>>>>>> that +
>>>>>> wicket-auth-roles and tried to make a functioning core +  
>>>>>> example.  I've
>>>>>>
>>>>> got
>>>>>
>>>>>> something running and would love to share it...
>>>>>>
>>>>>> Should I post this to the google code site?
>>>>>>
>>>>>> It makes more sense (to me) if we keep it in the wicketstuff  
>>>>>> repos --
>>>>>>
>>>>> that
>>>>>
>>>>>> way we get the benefit of Jeremy's work to make wickettuff-core  
>>>>>> much
>>>>>> cleaner.
>>>>>>
>>>>>> Thoughts?
>>>>>>
>>>>>> Ryan
>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> 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
>>
>>


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


Re: wicketstuff / ki / jsecurity

Posted by Jeremy Thomerson <je...@wickettraining.com>.
I run Continuum on my server and just started receiving notifications two
days ago that inmethod grid was not compiling.  It showed up right after the
commit of this ki security stuff.

I haven't looked at it yet, hoping that someone who was working with ki
security or inmethod would do so.

--
Jeremy Thomerson
http://www.wickettraining.com



On Wed, Mar 25, 2009 at 5:48 AM, Martin Funk <ma...@googlemail.com>wrote:

>
> Am 25.03.2009 um 10:17 schrieb nino martinez wael:
>
>  The problem with wicket stuff have been cleared up a bit, the part about
>> which projects are dead and not.. Those in wicketstuff-core are alive, and
>> if they become incompatible with the current version of wicket they will
>> be
>> kicked..
>>
> are they? I mean alive.
> Locking here:
>
> http://wicketstuff.org/teamcity/viewLog.html?buildId=3486&tab=buildResultsDiv&buildTypeId=bt35
> I'd say it's at least not compiling no more.
>
> Could someone please fix that?
>
> mf
>
>
>
>>
>> 2009/3/25 Maarten Bosteels <mb...@gmail.com>
>>
>>  Hi Ryan,
>>>
>>> I added you to the Project Members, so feel free to commit your examples.
>>> Unfortunately, until now I haven't had time to work on it myself
>>>
>>> The idea was to let the code mature in
>>> http://code.google.com/p/wicket-jsecurity/
>>> and maybe move it to wicket-stuff later on.
>>>
>>> Maybe we should move it to wicket-stuff already.
>>> My main problem with wicket-stuff is/was that it's not always very clear
>>> which projects are still alive and maintained and which are practically
>>> dead. And at the time, wicket-stuff had some problems with continuous
>>> integration, IIRC.
>>>
>>> Les, what do you think ?
>>> We should change the project name to wicket-ki anyway.
>>>
>>> regards,
>>> Maarten
>>>
>>> On Wed, Mar 25, 2009 at 7:47 AM, nino martinez wael <
>>> nino.martinez.wael@gmail.com> wrote:
>>>
>>>  Yeah I've for one always been very pro for wicketstuff.. It's nice
>>>>
>>> keeping
>>>
>>>> things in one place.. Plus as you write if we share a somewhat similar
>>>> structure it's potentially easier to maintain..
>>>>
>>>> 2009/3/24 Ryan McKinley <ry...@gmail.com>
>>>>
>>>>  Hi-
>>>>>
>>>>> I've been looking to integrate a complex security model with wicket --
>>>>> jsecurity seems really good.  I tried messing with:
>>>>> http://code.google.com/p/wicket-jsecurity/
>>>>>
>>>>> This appears to be a starting place, but does not have any running
>>>>>
>>>> example.
>>>>
>>>>>
>>>>> In an effort to get things running (and learn JSecurity) i took that +
>>>>> wicket-auth-roles and tried to make a functioning core + example.  I've
>>>>>
>>>> got
>>>>
>>>>> something running and would love to share it...
>>>>>
>>>>> Should I post this to the google code site?
>>>>>
>>>>> It makes more sense (to me) if we keep it in the wicketstuff repos --
>>>>>
>>>> that
>>>>
>>>>> way we get the benefit of Jeremy's work to make wickettuff-core much
>>>>> cleaner.
>>>>>
>>>>> Thoughts?
>>>>>
>>>>> Ryan
>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> 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: wicketstuff / ki / jsecurity

Posted by Martin Funk <ma...@googlemail.com>.
Am 25.03.2009 um 10:17 schrieb nino martinez wael:

> The problem with wicket stuff have been cleared up a bit, the part  
> about
> which projects are dead and not.. Those in wicketstuff-core are  
> alive, and
> if they become incompatible with the current version of wicket they  
> will be
> kicked..
are they? I mean alive.
Locking here:
http://wicketstuff.org/teamcity/viewLog.html?buildId=3486&tab=buildResultsDiv&buildTypeId=bt35
I'd say it's at least not compiling no more.

Could someone please fix that?

mf

>
>
> 2009/3/25 Maarten Bosteels <mb...@gmail.com>
>
>> Hi Ryan,
>>
>> I added you to the Project Members, so feel free to commit your  
>> examples.
>> Unfortunately, until now I haven't had time to work on it myself
>>
>> The idea was to let the code mature in
>> http://code.google.com/p/wicket-jsecurity/
>> and maybe move it to wicket-stuff later on.
>>
>> Maybe we should move it to wicket-stuff already.
>> My main problem with wicket-stuff is/was that it's not always very  
>> clear
>> which projects are still alive and maintained and which are  
>> practically
>> dead. And at the time, wicket-stuff had some problems with continuous
>> integration, IIRC.
>>
>> Les, what do you think ?
>> We should change the project name to wicket-ki anyway.
>>
>> regards,
>> Maarten
>>
>> On Wed, Mar 25, 2009 at 7:47 AM, nino martinez wael <
>> nino.martinez.wael@gmail.com> wrote:
>>
>>> Yeah I've for one always been very pro for wicketstuff.. It's nice
>> keeping
>>> things in one place.. Plus as you write if we share a somewhat  
>>> similar
>>> structure it's potentially easier to maintain..
>>>
>>> 2009/3/24 Ryan McKinley <ry...@gmail.com>
>>>
>>>> Hi-
>>>>
>>>> I've been looking to integrate a complex security model with  
>>>> wicket --
>>>> jsecurity seems really good.  I tried messing with:
>>>> http://code.google.com/p/wicket-jsecurity/
>>>>
>>>> This appears to be a starting place, but does not have any running
>>> example.
>>>>
>>>> In an effort to get things running (and learn JSecurity) i took  
>>>> that +
>>>> wicket-auth-roles and tried to make a functioning core +  
>>>> example.  I've
>>> got
>>>> something running and would love to share it...
>>>>
>>>> Should I post this to the google code site?
>>>>
>>>> It makes more sense (to me) if we keep it in the wicketstuff  
>>>> repos --
>>> that
>>>> way we get the benefit of Jeremy's work to make wickettuff-core  
>>>> much
>>>> cleaner.
>>>>
>>>> Thoughts?
>>>>
>>>> Ryan
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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: wicketstuff / ki / jsecurity

Posted by nino martinez wael <ni...@gmail.com>.
The problem with wicket stuff have been cleared up a bit, the part about
which projects are dead and not.. Those in wicketstuff-core are alive, and
if they become incompatible with the current version of wicket they will be
kicked..

2009/3/25 Maarten Bosteels <mb...@gmail.com>

> Hi Ryan,
>
> I added you to the Project Members, so feel free to commit your examples.
> Unfortunately, until now I haven't had time to work on it myself
>
> The idea was to let the code mature in
> http://code.google.com/p/wicket-jsecurity/
> and maybe move it to wicket-stuff later on.
>
> Maybe we should move it to wicket-stuff already.
> My main problem with wicket-stuff is/was that it's not always very clear
> which projects are still alive and maintained and which are practically
> dead. And at the time, wicket-stuff had some problems with continuous
> integration, IIRC.
>
> Les, what do you think ?
> We should change the project name to wicket-ki anyway.
>
> regards,
> Maarten
>
> On Wed, Mar 25, 2009 at 7:47 AM, nino martinez wael <
> nino.martinez.wael@gmail.com> wrote:
>
> > Yeah I've for one always been very pro for wicketstuff.. It's nice
> keeping
> > things in one place.. Plus as you write if we share a somewhat similar
> > structure it's potentially easier to maintain..
> >
> > 2009/3/24 Ryan McKinley <ry...@gmail.com>
> >
> > > Hi-
> > >
> > > I've been looking to integrate a complex security model with wicket --
> > > jsecurity seems really good.  I tried messing with:
> > > http://code.google.com/p/wicket-jsecurity/
> > >
> > > This appears to be a starting place, but does not have any running
> > example.
> > >
> > > In an effort to get things running (and learn JSecurity) i took that +
> > > wicket-auth-roles and tried to make a functioning core + example.  I've
> > got
> > > something running and would love to share it...
> > >
> > > Should I post this to the google code site?
> > >
> > > It makes more sense (to me) if we keep it in the wicketstuff repos --
> > that
> > > way we get the benefit of Jeremy's work to make wickettuff-core much
> > > cleaner.
> > >
> > > Thoughts?
> > >
> > > Ryan
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
>

Re: wicketstuff / ki / jsecurity

Posted by Ryan McKinley <ry...@gmail.com>.
On Mar 25, 2009, at 4:12 AM, Maarten Bosteels wrote:

> Hi Ryan,
>
> I added you to the Project Members, so feel free to commit your  
> examples.
> Unfortunately, until now I haven't had time to work on it myself
>

Thanks Maarten


> The idea was to let the code mature in
> http://code.google.com/p/wicket-jsecurity/
> and maybe move it to wicket-stuff later on.
>
> Maybe we should move it to wicket-stuff already.
> My main problem with wicket-stuff is/was that it's not always very  
> clear
> which projects are still alive and maintained and which are  
> practically
> dead. And at the time, wicket-stuff had some problems with continuous
> integration, IIRC.
>

yes, wicketstuff has some issues, but at least it has a continuous  
integration process in place -- and there is greater motivation for  
keeping it running as it gets more usage.

Jeremy has done a lot of work to get wicketstuff-core projects working  
well, and the hope is that things in that directory are actively  
maintained for the current release.  This directory will have branches  
for the various wicket releases etc.

I vote we move any wicket/jsecurity/ki attention to the wicketstuff  
repository.

We can add a big NOTICE describing the state of the project...  it is  
currently broken as I try to figure out what an "Enterprise Session"  
is :)  -- I'm following up on Les' suggestion on jsecurity-user@incubator.apache.org 
  now...


ryan

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


Re: wicketstuff / ki / jsecurity

Posted by Les Hazlewood <lh...@apache.org>.
Yep, I agree - please feel free to contribute.

We might want to hold off on the name change though.  There *might* be a
name discrepancy with ki and another project in the interwebs.  We're still
waiting on what we should do per the project Mentors after they come back
from Apache Con, where they're currently discussing the situation with other
ASF members.

Regards,

Les

On Wed, Mar 25, 2009 at 4:12 AM, Maarten Bosteels
<mb...@gmail.com>wrote:

> Hi Ryan,
>
> I added you to the Project Members, so feel free to commit your examples.
> Unfortunately, until now I haven't had time to work on it myself
>
> The idea was to let the code mature in
> http://code.google.com/p/wicket-jsecurity/
> and maybe move it to wicket-stuff later on.
>
> Maybe we should move it to wicket-stuff already.
> My main problem with wicket-stuff is/was that it's not always very clear
> which projects are still alive and maintained and which are practically
> dead. And at the time, wicket-stuff had some problems with continuous
> integration, IIRC.
>
> Les, what do you think ?
> We should change the project name to wicket-ki anyway.
>
> regards,
> Maarten
>
> On Wed, Mar 25, 2009 at 7:47 AM, nino martinez wael <
> nino.martinez.wael@gmail.com> wrote:
>
> > Yeah I've for one always been very pro for wicketstuff.. It's nice
> keeping
> > things in one place.. Plus as you write if we share a somewhat similar
> > structure it's potentially easier to maintain..
> >
> > 2009/3/24 Ryan McKinley <ry...@gmail.com>
> >
> > > Hi-
> > >
> > > I've been looking to integrate a complex security model with wicket --
> > > jsecurity seems really good.  I tried messing with:
> > > http://code.google.com/p/wicket-jsecurity/
> > >
> > > This appears to be a starting place, but does not have any running
> > example.
> > >
> > > In an effort to get things running (and learn JSecurity) i took that +
> > > wicket-auth-roles and tried to make a functioning core + example.  I've
> > got
> > > something running and would love to share it...
> > >
> > > Should I post this to the google code site?
> > >
> > > It makes more sense (to me) if we keep it in the wicketstuff repos --
> > that
> > > way we get the benefit of Jeremy's work to make wickettuff-core much
> > > cleaner.
> > >
> > > Thoughts?
> > >
> > > Ryan
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
>

Re: wicketstuff / ki / jsecurity

Posted by Maarten Bosteels <mb...@gmail.com>.
Hi Ryan,

I added you to the Project Members, so feel free to commit your examples.
Unfortunately, until now I haven't had time to work on it myself

The idea was to let the code mature in
http://code.google.com/p/wicket-jsecurity/
and maybe move it to wicket-stuff later on.

Maybe we should move it to wicket-stuff already.
My main problem with wicket-stuff is/was that it's not always very clear
which projects are still alive and maintained and which are practically
dead. And at the time, wicket-stuff had some problems with continuous
integration, IIRC.

Les, what do you think ?
We should change the project name to wicket-ki anyway.

regards,
Maarten

On Wed, Mar 25, 2009 at 7:47 AM, nino martinez wael <
nino.martinez.wael@gmail.com> wrote:

> Yeah I've for one always been very pro for wicketstuff.. It's nice keeping
> things in one place.. Plus as you write if we share a somewhat similar
> structure it's potentially easier to maintain..
>
> 2009/3/24 Ryan McKinley <ry...@gmail.com>
>
> > Hi-
> >
> > I've been looking to integrate a complex security model with wicket --
> > jsecurity seems really good.  I tried messing with:
> > http://code.google.com/p/wicket-jsecurity/
> >
> > This appears to be a starting place, but does not have any running
> example.
> >
> > In an effort to get things running (and learn JSecurity) i took that +
> > wicket-auth-roles and tried to make a functioning core + example.  I've
> got
> > something running and would love to share it...
> >
> > Should I post this to the google code site?
> >
> > It makes more sense (to me) if we keep it in the wicketstuff repos --
> that
> > way we get the benefit of Jeremy's work to make wickettuff-core much
> > cleaner.
> >
> > Thoughts?
> >
> > Ryan
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>

Re: wicketstuff / ki / jsecurity

Posted by nino martinez wael <ni...@gmail.com>.
Yeah I've for one always been very pro for wicketstuff.. It's nice keeping
things in one place.. Plus as you write if we share a somewhat similar
structure it's potentially easier to maintain..

2009/3/24 Ryan McKinley <ry...@gmail.com>

> Hi-
>
> I've been looking to integrate a complex security model with wicket --
> jsecurity seems really good.  I tried messing with:
> http://code.google.com/p/wicket-jsecurity/
>
> This appears to be a starting place, but does not have any running example.
>
> In an effort to get things running (and learn JSecurity) i took that +
> wicket-auth-roles and tried to make a functioning core + example.  I've got
> something running and would love to share it...
>
> Should I post this to the google code site?
>
> It makes more sense (to me) if we keep it in the wicketstuff repos -- that
> way we get the benefit of Jeremy's work to make wickettuff-core much
> cleaner.
>
> Thoughts?
>
> Ryan
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>