RE: iLearn Wicket - Please reply with your feedback
Hi, I think that Wicket Users tend to use more Jetty than Tomcat as the application server. Regards, Mohamed -Original Message- From: Jeremy Thomerson [mailto:jer...@wickettraining.com] Sent: Monday, April 13, 2009 12:25 PM To: users@wicket.apache.org Subject: Re: iLearn Wicket - Please reply with your feedback I'm not so sure that a 404 page will be very informative :) -- Jeremy Thomerson http://www.wickettraining.com On Sat, Apr 11, 2009 at 10:58 AM, Null kühl null.k...@gmail.com wrote: Dear All, I have been comparing between many component based frameworks around that follows the MVC architecture, as i ended up comparing between JSF and Wicket, however i have seen more advantages in Wicket rather than JSF, however one of the cons on wicket size was its educational resources, as JSF exists since some time now there are quite many tutorials and books for it. So i decided to start up an elearning series that aims to get people to be familiar with wicket, starting at a java programmer level. I understand that there are some good tutorials around but i do believe that video tutorials are quire more explanatory than text tutorials. I have started doing some scratch videos already that will act later on as the back bone of the series,(will probably be redesigned and published in a more professional way) kindly check it out : http://ilearnzone.com/wicket.html Please reply with your feedback, so that i know if i should continue on it, or just throw it away and stop wasting my time. Also if anyone would like to participate, he is more than welcomed. Regards, 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-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: debugging a Wicket application running under Jetty-6.1 in Eclipse
It is working now. I am debugging in Eclipse. Thanks a lot -Original Message- From: jcgarciam [mailto:jcgarc...@gmail.com] Sent: Thursday, April 09, 2009 6:06 PM To: users@wicket.apache.org Subject: Re: debugging a Wicket application running under Jetty-6.1 in Eclipse I'll suggest to do it in the Wicket Way, you will have much more benefits. If you made your project from the QuickStart, you will notice a 'Start' class under your 'test' source. that what it does is just start an embedded jetty pointing to your webapp directory and mounting your application under / context. so just right click on it and click Debug as - Java Application and you're done. Even if you are working on a multi-module maven project this will work, just make sure your module are installed on your local repository, issuing 'mvn install' on the root project. If you have question regarding the 'Start.java' class just let us know. mchenini wrote: Hi, This is about debugging a Wicket application running under Jetty-6.1 in Eclipse. I followed the steps shown at: http://docs.codehaus.org/display/JETTY/Debugging+with+the+Maven+Jetty+Pl ugin+inside+Eclipse But I am getting this exception: java.lang.NoClassDefFoundError: org/codehaus/classworlds/Launcher Exception in thread main Any help? The steps I followed are: Step 1 Go to the Run/External Tools/External Tools ... menu item on the Run menu bar. Select Program and click the New button. On the Main tab, fill in the Location: as the full path to your mvn executable. C:\java\DEVTOOLS\MAIN\maven2\bin For the Working Directory: select the workspace that matches your webapp. For Arguments: add jetty:run. Move to the Environment tab and click the New button to add a new variable named MAVEN_OPTS with the value: -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=4000,server=y,suspend=y If you supply suspend=n instead of suspend=y you can start immediately without running the debugger and launch the debugger at anytime you really wish to debug. Step 2 Then, pull up the Run/Debug/Debug ... menu item and select Remote Java Application and click the New button. Fill in the dialog by selecting your webapp project for the Project: field, and ensure you are using the same port number as you specified in the address= property above. Now all you need to do is to Run/External Tools and select the name of the maven tool setup you created in step 1 to start the plugin and then Run/Debug and select the name of the debug setup you setup in step2. 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. -- View this message in context: http://www.nabble.com/debugging-a-Wicket-application-running-under-Jetty -6.1-in-Eclipse-tp22979929p22980041.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@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-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
debugging a Wicket application running under Jetty-6.1 in Eclipse
Hi, This is about debugging a Wicket application running under Jetty-6.1 in Eclipse. I followed the steps shown at: http://docs.codehaus.org/display/JETTY/Debugging+with+the+Maven+Jetty+Pl ugin+inside+Eclipse But I am getting this exception: java.lang.NoClassDefFoundError: org/codehaus/classworlds/Launcher Exception in thread main Any help? The steps I followed are: Step 1 Go to the Run/External Tools/External Tools ... menu item on the Run menu bar. Select Program and click the New button. On the Main tab, fill in the Location: as the full path to your mvn executable. C:\java\DEVTOOLS\MAIN\maven2\bin For the Working Directory: select the workspace that matches your webapp. For Arguments: add jetty:run. Move to the Environment tab and click the New button to add a new variable named MAVEN_OPTS with the value: -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=4000,server=y,suspend=y If you supply suspend=n instead of suspend=y you can start immediately without running the debugger and launch the debugger at anytime you really wish to debug. Step 2 Then, pull up the Run/Debug/Debug ... menu item and select Remote Java Application and click the New button. Fill in the dialog by selecting your webapp project for the Project: field, and ensure you are using the same port number as you specified in the address= property above. Now all you need to do is to Run/External Tools and select the name of the maven tool setup you created in step 1 to start the plugin and then Run/Debug and select the name of the debug setup you setup in step2. 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: VOTE: Rename Apache Wicket to Apache WicketFX
Same concern here. Why the FX suffix? -Original Message- From: Johan Compagner [mailto:jcompag...@gmail.com] Sent: Wednesday, April 01, 2009 9:33 AM To: users@wicket.apache.org Subject: Re: VOTE: Rename Apache Wicket to Apache WicketFX Failed eXtremely On Wed, Apr 1, 2009 at 15:08, Ames, Tim tim.a...@promedica.org wrote: Please excuse my EXTREME ignorance, but what exactly does or will the FX mean from a Wicket standpoint? What does it do or allow a developer to do that would designate it as FX? -Original Message- From: David Leangen [mailto:wic...@leangen.net] Sent: Wednesday, April 01, 2009 4:08 AM To: users@wicket.apache.org Subject: Re: VOTE: Rename Apache Wicket to Apache WicketFX Or... WTF! (Wicket The Framework) +1 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ EMAIL CONFIDENTIALITY NOTICE This Email message, and any attachments, may contain confidential patient health information that is legally protected. This information is intended only for the use of the individual or entity named above. The authorized recipient of this information is prohibited from disclosing this information to any other party unless required to do so by law or regulation and is required to destroy the information after its stated need has been fulfilled. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or action taken in reliance on the contents of this message is strictly prohibited. If you have received this information in error, please notify the sender immediately by replying to this message and delete the message from your system. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@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-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: newbie question: HTTP 404 on the quickstart project
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.dasho...@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 mchen...@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:jer...@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
mchen...@geico.comwrote:
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
Argsrc/webapp/Arg
/Call
-Original Message-
From: Jeremy Thomerson [mailto:jer...@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
mchen...@geico.comwrote:
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
socketconnec...@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
RE: Looking for a book on the jetty server
Are you implying that in a production environment Glassfish, Tomcat, or JBoss are better to use with Wicket than jetty? I was planning to learn jetty to use it in development and in production and the 'Pro Wicket' book states that it [Wicket] was is a good fit for developing Wicket applications Please advise. Thanks, Mohamed -Original Message- From: Martijn Dashorst [mailto:martijn.dasho...@gmail.com] Sent: Wednesday, March 25, 2009 9:25 AM To: users@wicket.apache.org Subject: Re: Looking for a book on the jetty server I'm not sure if most actually *deploy* their production servers on Jetty (there's nothing holding anyone back), but I think that Tomcat, Glassfish and JBoss are also very popular. Jetty is most commonly used during development because it is so easy to embed. AFAIK no books have been written for Jetty. Martijn - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@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.
RE: Looking for a book on the jetty server
Thanks to all for your feedback. -Original Message- From: Luther Baker [mailto:lutherba...@gmail.com] Sent: Wednesday, March 25, 2009 10:52 AM To: users@wicket.apache.org Subject: Re: Looking for a book on the jetty server I've asked this general question myself and came away with a few valuable thoughts: http://www.theserverside.com/news/thread.tss?thread_id=15073 http://developers.slashdot.org/developers/02/08/19/2042235.shtml?tid=108 http://www.webtide.com/choose/jetty.jsp http://raibledesigns.com/rd/entry/jetty_vs_tomcat_vs_resin -Luther On Wed, Mar 25, 2009 at 9:42 AM, Martijn Dashorst martijn.dasho...@gmail.com wrote: No, I'm implying that more people use Jetty pure for development, and deploy on different production containers. Jetty is just fine afiak. Our company just uses tomcat (and one instance of glassfish) for production/test. Our devs use tomcat (with sysdeo plugin) and jetty (quickstart) in their daily development. Martijn On Wed, Mar 25, 2009 at 3:13 PM, Chenini, Mohamed mchen...@geico.com wrote: Are you implying that in a production environment Glassfish, Tomcat, or JBoss are better to use with Wicket than jetty? I was planning to learn jetty to use it in development and in production and the 'Pro Wicket' book states that it [Wicket] was is a good fit for developing Wicket applications Please advise. Thanks, Mohamed -Original Message- From: Martijn Dashorst [mailto:martijn.dasho...@gmail.com] Sent: Wednesday, March 25, 2009 9:25 AM To: users@wicket.apache.org Subject: Re: Looking for a book on the jetty server I'm not sure if most actually *deploy* their production servers on Jetty (there's nothing holding anyone back), but I think that Tomcat, Glassfish and JBoss are also very popular. Jetty is most commonly used during development because it is so easy to embed. AFAIK no books have been written for Jetty. Martijn - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@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. -- 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-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@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-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: newbie question: HTTP 404 on the quickstart project
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:jer...@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
mchen...@geico.comwrote:
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
Argsrc/webapp/Arg
/Call
-Original Message-
From: Jeremy Thomerson [mailto:jer...@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
mchen...@geico.comwrote:
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
socketconnec...@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:jer...@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
mchen...@geico.comwrote:
I tried http://localhost:8081/quickstart
And the content of web.xml
RE: newbie question: HTTP 404 on the quickstart project
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
socketconnec...@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:jer...@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
mchen...@geico.comwrote:
I tried http://localhost:8081/quickstart
And the content of web.xml is:
filter
filter-namewicket.QuickStart/filter-name
filter-classorg.apache.wicket.protocol.http.WicketFilter/filter-class
init-param
param-nameapplicationClassName/param-name
param-valuecom.mycompany.app.WicketApplication/param-value
/init-param
/filter
filter-mapping
filter-namewicket.QuickStart/filter-name
url-pattern/*/url-pattern
/filter-mapping
-Original Message-
From: Jeremy Thomerson [mailto:jer...@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
mchen...@geico.comwrote:
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
RE: newbie question: HTTP 404 on the quickstart project
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
Argsrc/webapp/Arg
/Call
-Original Message-
From: Jeremy Thomerson [mailto:jer...@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
mchen...@geico.comwrote:
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
socketconnec...@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:jer...@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
mchen...@geico.comwrote:
I tried http://localhost:8081/quickstart
And the content of web.xml is:
filter
filter-namewicket.QuickStart/filter-name
filter-classorg.apache.wicket.protocol.http.WicketFilter/filter-class
init-param
param-nameapplicationClassName/param-name
param-valuecom.mycompany.app.WicketApplication/param-value
/init-param
/filter
filter-mapping
filter-namewicket.QuickStart/filter-name
url-pattern/*/url-pattern
/filter-mapping
-Original Message-
From: Jeremy Thomerson [mailto:jer...@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
mchen...@geico.comwrote:
Hi,
I setup the quickstart project using the imbedded jetty server
and
started the jetty server from
Looking for a book on the jetty server
Hi, Is there a good book on the jetty server to learn more on it? Since Wicket users seems to use Jetty as the Servlet/Web container. 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.
