Re: [Wicket-user] View from 30,000 feet of Wicket infrastructure
Johan Compagner schrieb: the problem with myeclipse is that they don't move quickly enough for me. They should be atleast have a version of myeclipse for every milestone build. Else i can't really use there software. Yes, they don't move very fast. Dependencies for web projects are also a big issue for me. They wanted to improve the flexibility of the build process last summer, but AFAIK that's not done yet. On the other hand, support is very good. Timo --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] View from 30,000 feet of Wicket infrastructure
They definitely seem more focused on new features and longer delays on releases. Personally, I don't use half of the features but that's not to say that I never will. I do, however, appreciate the rock-solid stability and the support, so far, has been very good. How is the dependencies feature not flexible? I specifically chose MyEclipse because Webtools 1.0 had a broken dependencies problem and you had to manually add jars to the web project for them to be deployed. On 4/12/06, Timo Stamm [EMAIL PROTECTED] wrote: Johan Compagner schrieb: the problem with myeclipse is that they don't move quickly enough for me. They should be atleast have a version of myeclipse for every milestone build. Else i can't really use there software. Yes, they don't move very fast. Dependencies for web projects are also a big issue for me. They wanted to improve the flexibility of the build process last summer, but AFAIK that's not done yet. On the other hand, support is very good. Timo --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] View from 30,000 feet of Wicket infrastructure
Vincent Jenks schrieb: They definitely seem more focused on new features and longer delays on releases. Personally, I don't use half of the features but that's not to say that I never will. I do, however, appreciate the rock-solid stability and the support, so far, has been very good. I use pretty much every feature except the Struts support. Couldn't live without the DataBase Explorer. Stability is an issue under OS X. Maybe it's better on Windows or Linux. How is the dependencies feature not flexible? I specifically chose MyEclipse because Webtools 1.0 had a broken dependencies problem and you had to manually add jars to the web project for them to be deployed. Maybe it's better than Webtools (never tried that), but you can't inherit anything from a WebProject. This sucks if you have an app that is split into individual projects. Timo --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] View from 30,000 feet of Wicket infrastructure
I also don't use WebTools (if i use it is is purely for the xml/html editors if i install it)I still think webtools is much to bloated. They should contribute there editors to the core of eclipse so that eclipse has nice editors for the basic types. Then i don't have to install webtools at all.For starting tomcat and debugging webapps i use the Sysdeo plugin. Which is easy to use (in my eyes) and does it 'right' (compared to the jetty plugin ;) )johan On 4/10/06, Vincent Jenks [EMAIL PROTECTED] wrote: Hmm...not familiar but it sounds like a beginner might struggle w/ something like that? I could be wrong. The webtools platform was brutally poor until recently when they managed to stabilize it...I was actually impressed the last time I test-drove it. I'll have to check out Merve. Is it simply a plugin that deploys to tomcat? I'm using a lot of Wicket + EJB3 on JBoss 4 these days (zen, if you ask me.) I've been using Eclipse 3.1.2 MyEclipse 4.1...couldn't be happier.On 4/9/06, Daniel Spiewak [EMAIL PROTECTED] wrote: Personally, I prefer vanilla Eclipse 3.2, XMLBuddy and the Merve plugin (very flakey, but it works well once you figure out its idiosyncrasies). DanielOn 4/9/06, Vincent Jenks [EMAIL PROTECTED] wrote: That's tough since there is no ground-up tutorial like this when it comes to Wicket (that I know of.) There's a Wicket book on the way from what I understand but that may not be for a few months or so? The best thing you can do is get a simple Hello World working on your local machine. 1. download and install Tomcat (servlet container, http server)http://tomcat.apache.org/download-55.cgi 2. download and install Eclipse (and Eclipse Webtools) http://www.eclipse.org/downloads/ http://download.eclipse.org/webtools/downloads/3. download wicket, create a User Library in Eclipse and add the Wicket jars http://download.eclipse.org/eclipse/downloads/drops/R-3.0-200406251208/eclipse-news-part5-R3.html - see section on User-defined libraries4. Create a web project in Eclipse, add reference to Wicket User Library from step 3. Also set up Tomcat so you can deploy your test app to it - this should be fairly intuitive while creating your web project. 5. do this tutorialhttp://wicket.sourceforge.net/ExampleHelloWorld.html This should at least give you a few clues on how to get started ASAP on a small scale. The documentation at each of the sites for each of the projects should get you what you need. The best way to get started is to jump in! If you're comfortable w/ Eclipse and want more than Webtools can offer you, MyEclipse is a great plugin for Eclipse...I've been using it for about 4 mo. and I love it. It's not free, however. After all of this, deploying to a linux server or another machine of any platform should be fairly simple. A web project in eclipse webtools can be exported as a .war archive which can be dropped in just about any app server/container. Hope this helps in some way.-v On 4/9/06, Daniel Spiewak [EMAIL PROTECTED] wrote: I can't think of many references that give the kind of overview you're looking for. Having just been (arguably still at) the same point you're at in terms of knowledge of web apps, I really can't say that there is a good solution. What I did is blindly followed the install instructions and then poked around with the various options checking consequences. I found as many references as I could find about wicket component details, as many tutorials as I could dig up on using them, and stumbled my way through configuring Tomcat so I could experiment. If anyone does have any references of this type, I'm interested too. :-)Daniel On 4/9/06, Dave Johnson [EMAIL PROTECTED] wrote:I'm an old COBOL guy who has learned enough Java to be useful in a corporate environment where I can see the need for a new class, generatea _javascript_ proxy to call the Java class from the UI, and build a classwith Eclipse to do the job.Now I'd like to begin developing in Wicket for my own purposes under Windows 2000 / XP.However, when it comes to the infrastructure of webapps, I get mired in details much too quickly.What are some good references that clearly explain the various levels ofsoftware I encounter, such as Linux, Tomcat,Jetty, Hibernate, PHP, MySQL and all the rest, and whether they're on the local machine or theremote server?And which are even needed?Most of what I find seems to assume too much familiarity with theseissues.I need a high-level overview that explains all this stuff without dropping down to 300 feet so quickly.Blindly followinginstallation instructions doesn't work well without knowing theconsequences of various choices.Thanks for any help.Dave ---This SF.Net email is sponsored by xPML, a groundbreaking scripting languagethat extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory!
Re: [Wicket-user] View from 30,000 feet of Wicket infrastructure
On 10/04/06, Dave Johnson [EMAIL PROTECTED] wrote: What are some good references that clearly explain the various levels of software I encounter, such as Linux, Tomcat, Jetty, Hibernate, PHP, MySQL and all the rest, and whether they're on the local machine or the remote server? And which are even needed? Most of what I find seems to assume too much familiarity with these issues. I need a high-level overview that explains all this stuff without dropping down to 300 feet so quickly. Blindly following installation instructions doesn't work well without knowing the consequences of various choices. Hi, I'm not aware of any specific starting point, but there are certainly a number of points that will help once you have managed to get a feel for what belongs where - Hopefully the following (very brief) comments will help though... Linux: Operating System (also WinXP, OSX, Solaris) - Shouldn't make any real difference to the applications being developed as the Java apps run in a java virtual machine, which provides a common environment to the application despite the different OS's. Tomcat, Jetty: Java Servlet Engines/Containers (also Resin). - Server-side apps that host web applications consisting of Java Servlets. Client-side web-browsers make requests, which get passed to the servlets by the servlet engines/containers, which respond with HTML pages. Try one or more, just don't try run more than one at a time unless you configure them to listen on different ports (typically they'll all default to listening on port 8080). (Tomcat is the commonest, but not the easiest to configure nor the clearest when things go wrong - I'd recommend evaluating Jetty Resin too, as they're both good often provide better diagnostics.) MySQL: Relational Database (also Oracle, PostgreSQL, HSQLDB) - Server-side apps that the servlets/web-apps will use to store data. Will involve SQL and JDBC drivers. Hibernate: Persistence framework (also IBatis, JDO Spring SQL) - Helps to map between Object-orientated Java code and the Record-orientated world of relational databases. Leave 'till later! PHP: Scripting language that can be embedded into HTML. - Not related to Java or Servlet engines, but rather an alternative. Runs in web servers such as Apache. The goal of the language is to allow web developers to write dynamically generated pages quickly. Can lead to difficult to maintain code! JSP: Java Server Pages : Java-based scripting language that can be embedded into HTML. - Runs in jsp/servlet engines such as Tomcat. The goal of the language is to allow web developers to write dynamically generated pages quickly. Can lead to difficult to maintain code! Sun's Servlet Docs - http://java.sun.com/products/servlet/docs.html Keep asking questions, though. /Gwyn --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] View from 30,000 feet of Wicket infrastructure
Johan, I agree, the basic types that webtools provides editability for should be built into eclipse...like html, xml, _javascript_, css, etc. However, for a beginner, installing eclipse + webtools gives you everything you need to build a basic Java EE-based web app. It was my experience, when starting out w/ Java about a year ago, that these tools alone got me up and running, building sites very quickly. I was able to work from my Gentoo workstation at home and my Winxp box at work w/ exactly the same tools. As for MyEclipse...that was my only compromise when it came to choosing tools and trying to keep everything open source. After using it, I had to have it! :D I'm glad I did, they have a Matisse editor coming anytime now...should be interesting. On 4/10/06, Daniel Spiewak [EMAIL PROTECTED] wrote: Merve will either deploy to Tomcat or run the webapp in a bundled Tomcat instance. Just to give you a headstart in the flakey-ness, it all has to do with creating the Run Configuration and the webapp context dir. :-) I would use MyEclipse if I was willing to spend the money on it.Daniel On 4/10/06, Vincent Jenks [EMAIL PROTECTED] wrote:Hmm...not familiar but it sounds like a beginner might struggle w/ something like that? I could be wrong. The webtools platform was brutally poor until recently when they managed to stabilize it...I was actually impressed the last time I test-drove it. I'll have to check out Merve. Is it simply a plugin that deploys to tomcat? I'm using a lot of Wicket + EJB3 on JBoss 4 these days (zen, if you ask me.) I've been using Eclipse 3.1.2 MyEclipse 4.1...couldn't be happier.On 4/9/06, Daniel Spiewak [EMAIL PROTECTED] wrote: Personally, I prefer vanilla Eclipse 3.2, XMLBuddy and the Merve plugin (very flakey, but it works well once you figure out its idiosyncrasies). DanielOn 4/9/06, Vincent Jenks [EMAIL PROTECTED] wrote: That's tough since there is no ground-up tutorial like this when it comes to Wicket (that I know of.) There's a Wicket book on the way from what I understand but that may not be for a few months or so? The best thing you can do is get a simple Hello World working on your local machine. 1. download and install Tomcat (servlet container, http server)http://tomcat.apache.org/download-55.cgi 2. download and install Eclipse (and Eclipse Webtools) http://www.eclipse.org/downloads/ http://download.eclipse.org/webtools/downloads/3. download wicket, create a User Library in Eclipse and add the Wicket jars http://download.eclipse.org/eclipse/downloads/drops/R-3.0-200406251208/eclipse-news-part5-R3.html - see section on User-defined libraries4. Create a web project in Eclipse, add reference to Wicket User Library from step 3. Also set up Tomcat so you can deploy your test app to it - this should be fairly intuitive while creating your web project. 5. do this tutorialhttp://wicket.sourceforge.net/ExampleHelloWorld.html This should at least give you a few clues on how to get started ASAP on a small scale. The documentation at each of the sites for each of the projects should get you what you need. The best way to get started is to jump in! If you're comfortable w/ Eclipse and want more than Webtools can offer you, MyEclipse is a great plugin for Eclipse...I've been using it for about 4 mo. and I love it. It's not free, however. After all of this, deploying to a linux server or another machine of any platform should be fairly simple. A web project in eclipse webtools can be exported as a .war archive which can be dropped in just about any app server/container. Hope this helps in some way.-v On 4/9/06, Daniel Spiewak [EMAIL PROTECTED] wrote: I can't think of many references that give the kind of overview you're looking for. Having just been (arguably still at) the same point you're at in terms of knowledge of web apps, I really can't say that there is a good solution. What I did is blindly followed the install instructions and then poked around with the various options checking consequences. I found as many references as I could find about wicket component details, as many tutorials as I could dig up on using them, and stumbled my way through configuring Tomcat so I could experiment. If anyone does have any references of this type, I'm interested too. :-)Daniel On 4/9/06, Dave Johnson [EMAIL PROTECTED] wrote:I'm an old COBOL guy who has learned enough Java to be useful in a corporate environment where I can see the need for a new class, generatea _javascript_ proxy to call the Java class from the UI, and build a classwith Eclipse to do the job.Now I'd like to begin developing in Wicket for my own purposes under Windows 2000 / XP.However, when it comes to the infrastructure of webapps, I get mired in details much too quickly.What are some good references that clearly explain the various levels ofsoftware I encounter, such as Linux, Tomcat,Jetty, Hibernate, PHP, MySQL and all the rest, and whether they're on the local machine or theremote server?And which are even
Re: [Wicket-user] View from 30,000 feet of Wicket infrastructure
See, I look at it the other way around...they release a very stable, feature-rich plugin for the current release and support it well w/ regular upgrades, fixes, etc. I'm sure 5.0 will support Eclipse 3.2 but I'm not entirely sure. I'd rather not be upgrading Eclipse at every milestone and work in a reassuringly stable environment.Personally, I probably won't switch to eclipse 3.2 until it's either a) a final release or b) JDK 1.6 final is released - whichever comes first. I couldn't see anything that compelling about 3.2M6, so far that would make me have to have it just yet...but I haven't looked at it that carefully.On 4/10/06, Johan Compagner [EMAIL PROTECTED] wrote: the problem with myeclipse is that they don't move quickly enough for me.They should be atleast have a version of myeclipse for every milestone build. Else i can't really use there software. Do they have a version for 3.2M6 ?johanOn 4/10/06, Vincent Jenks [EMAIL PROTECTED] wrote: Johan, I agree, the basic types that webtools provides editability for should be built into eclipse...like html, xml, _javascript_, css, etc. However, for a beginner, installing eclipse + webtools gives you everything you need to build a basic Java EE-based web app. It was my experience, when starting out w/ Java about a year ago, that these tools alone got me up and running, building sites very quickly. I was able to work from my Gentoo workstation at home and my Winxp box at work w/ exactly the same tools. As for MyEclipse...that was my only compromise when it came to choosing tools and trying to keep everything open source. After using it, I had to have it! :D I'm glad I did, they have a Matisse editor coming anytime now...should be interesting. On 4/10/06, Daniel Spiewak [EMAIL PROTECTED] wrote: Merve will either deploy to Tomcat or run the webapp in a bundled Tomcat instance. Just to give you a headstart in the flakey-ness, it all has to do with creating the Run Configuration and the webapp context dir. :-) I would use MyEclipse if I was willing to spend the money on it.Daniel On 4/10/06, Vincent Jenks [EMAIL PROTECTED] wrote:Hmm...not familiar but it sounds like a beginner might struggle w/ something like that? I could be wrong. The webtools platform was brutally poor until recently when they managed to stabilize it...I was actually impressed the last time I test-drove it. I'll have to check out Merve. Is it simply a plugin that deploys to tomcat? I'm using a lot of Wicket + EJB3 on JBoss 4 these days (zen, if you ask me.) I've been using Eclipse 3.1.2 MyEclipse 4.1...couldn't be happier.On 4/9/06, Daniel Spiewak [EMAIL PROTECTED] wrote: Personally, I prefer vanilla Eclipse 3.2, XMLBuddy and the Merve plugin (very flakey, but it works well once you figure out its idiosyncrasies). DanielOn 4/9/06, Vincent Jenks [EMAIL PROTECTED] wrote: That's tough since there is no ground-up tutorial like this when it comes to Wicket (that I know of.) There's a Wicket book on the way from what I understand but that may not be for a few months or so? The best thing you can do is get a simple Hello World working on your local machine. 1. download and install Tomcat (servlet container, http server)http://tomcat.apache.org/download-55.cgi 2. download and install Eclipse (and Eclipse Webtools) http://www.eclipse.org/downloads/ http://download.eclipse.org/webtools/downloads/3. download wicket, create a User Library in Eclipse and add the Wicket jars http://download.eclipse.org/eclipse/downloads/drops/R-3.0-200406251208/eclipse-news-part5-R3.html - see section on User-defined libraries4. Create a web project in Eclipse, add reference to Wicket User Library from step 3. Also set up Tomcat so you can deploy your test app to it - this should be fairly intuitive while creating your web project. 5. do this tutorialhttp://wicket.sourceforge.net/ExampleHelloWorld.html This should at least give you a few clues on how to get started ASAP on a small scale. The documentation at each of the sites for each of the projects should get you what you need. The best way to get started is to jump in! If you're comfortable w/ Eclipse and want more than Webtools can offer you, MyEclipse is a great plugin for Eclipse...I've been using it for about 4 mo. and I love it. It's not free, however. After all of this, deploying to a linux server or another machine of any platform should be fairly simple. A web project in eclipse webtools can be exported as a .war archive which can be dropped in just about any app server/container. Hope this helps in some way.-v On 4/9/06, Daniel Spiewak [EMAIL PROTECTED] wrote: I can't think of many references that give the kind of overview you're looking for. Having just been (arguably still at) the same point you're at in terms of knowledge of web apps, I really can't say that there is a good solution. What I did is blindly followed the install instructions and then poked around with the various options checking consequences. I found as many
Re: [Wicket-user] View from 30,000 feet of Wicket infrastructure
i also can't say it why i use for example 3.2M6 UNTIL i help a coworker and i sit behind his eclipse version (still 3.1)Then suddenly it is all clear why i use the latest versions. Shorcuts that i used to for specific features don't work because that feature isn't there specific views not there.. The list goes on.I have to say that the step from 3.0 to 3.1 and the step from 3.1 to 3.2 is not that big. They don't introduce a lot of really neath and nice goodies..But also i want a great 3.2 release so why not help test them? Why do you expect to have a great 3.2 release and never test it and give feedback if needed??I do submit quite some bugs nowadays and the response is mostly great and vast. i can really say that getting integration builds and milestone builds really speeds up my developerment, because the i use the new features very fastand they are mostly very very helpfull.. So saying that it is contra productive is a wrong statement.. I can count the i have to reverse to the previous version on one hand...johanOn 4/10/06, Vincent Jenks [EMAIL PROTECTED] wrote: See, I look at it the other way around...they release a very stable, feature-rich plugin for the current release and support it well w/ regular upgrades, fixes, etc. I'm sure 5.0 will support Eclipse 3.2 but I'm not entirely sure. I'd rather not be upgrading Eclipse at every milestone and work in a reassuringly stable environment.Personally, I probably won't switch to eclipse 3.2 until it's either a) a final release or b) JDK 1.6 final is released - whichever comes first. I couldn't see anything that compelling about 3.2M6, so far that would make me have to have it just yet...but I haven't looked at it that carefully. On 4/10/06, Johan Compagner [EMAIL PROTECTED] wrote: the problem with myeclipse is that they don't move quickly enough for me.They should be atleast have a version of myeclipse for every milestone build. Else i can't really use there software. Do they have a version for 3.2M6 ?johanOn 4/10/06, Vincent Jenks [EMAIL PROTECTED] wrote: Johan, I agree, the basic types that webtools provides editability for should be built into eclipse...like html, xml, _javascript_, css, etc. However, for a beginner, installing eclipse + webtools gives you everything you need to build a basic Java EE-based web app. It was my experience, when starting out w/ Java about a year ago, that these tools alone got me up and running, building sites very quickly. I was able to work from my Gentoo workstation at home and my Winxp box at work w/ exactly the same tools. As for MyEclipse...that was my only compromise when it came to choosing tools and trying to keep everything open source. After using it, I had to have it! :D I'm glad I did, they have a Matisse editor coming anytime now...should be interesting. On 4/10/06, Daniel Spiewak [EMAIL PROTECTED] wrote: Merve will either deploy to Tomcat or run the webapp in a bundled Tomcat instance. Just to give you a headstart in the flakey-ness, it all has to do with creating the Run Configuration and the webapp context dir. :-) I would use MyEclipse if I was willing to spend the money on it.Daniel On 4/10/06, Vincent Jenks [EMAIL PROTECTED] wrote:Hmm...not familiar but it sounds like a beginner might struggle w/ something like that? I could be wrong. The webtools platform was brutally poor until recently when they managed to stabilize it...I was actually impressed the last time I test-drove it. I'll have to check out Merve. Is it simply a plugin that deploys to tomcat? I'm using a lot of Wicket + EJB3 on JBoss 4 these days (zen, if you ask me.) I've been using Eclipse 3.1.2 MyEclipse 4.1...couldn't be happier.On 4/9/06, Daniel Spiewak [EMAIL PROTECTED] wrote: Personally, I prefer vanilla Eclipse 3.2, XMLBuddy and the Merve plugin (very flakey, but it works well once you figure out its idiosyncrasies). DanielOn 4/9/06, Vincent Jenks [EMAIL PROTECTED] wrote: That's tough since there is no ground-up tutorial like this when it comes to Wicket (that I know of.) There's a Wicket book on the way from what I understand but that may not be for a few months or so? The best thing you can do is get a simple Hello World working on your local machine. 1. download and install Tomcat (servlet container, http server)http://tomcat.apache.org/download-55.cgi 2. download and install Eclipse (and Eclipse Webtools) http://www.eclipse.org/downloads/ http://download.eclipse.org/webtools/downloads/3. download wicket, create a User Library in Eclipse and add the Wicket jars http://download.eclipse.org/eclipse/downloads/drops/R-3.0-200406251208/eclipse-news-part5-R3.html - see section on User-defined libraries4. Create a web project in Eclipse, add reference to Wicket User Library from step 3. Also set up Tomcat so you can deploy your test app to it - this should be fairly intuitive while creating your web project. 5. do this tutorialhttp://wicket.sourceforge.net/ExampleHelloWorld.html This should
Re: [Wicket-user] View from 30,000 feet of Wicket infrastructure
Thanks to all who replied to this thread. I'll investigate your helpful ideas. Dave --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] View from 30,000 feet of Wicket infrastructure
That's tough since there is no ground-up tutorial like this when it comes to Wicket (that I know of.) There's a Wicket book on the way from what I understand but that may not be for a few months or so?The best thing you can do is get a simple Hello World working on your local machine. 1. download and install Tomcat (servlet container, http server)http://tomcat.apache.org/download-55.cgi2. download and install Eclipse (and Eclipse Webtools) http://www.eclipse.org/downloads/http://download.eclipse.org/webtools/downloads/3. download wicket, create a User Library in Eclipse and add the Wicket jars http://download.eclipse.org/eclipse/downloads/drops/R-3.0-200406251208/eclipse-news-part5-R3.html - see section on User-defined libraries4. Create a web project in Eclipse, add reference to Wicket User Library from step 3. Also set up Tomcat so you can deploy your test app to it - this should be fairly intuitive while creating your web project. 5. do this tutorialhttp://wicket.sourceforge.net/ExampleHelloWorld.htmlThis should at least give you a few clues on how to get started ASAP on a small scale. The documentation at each of the sites for each of the projects should get you what you need. The best way to get started is to jump in! If you're comfortable w/ Eclipse and want more than Webtools can offer you, MyEclipse is a great plugin for Eclipse...I've been using it for about 4 mo. and I love it. It's not free, however. After all of this, deploying to a linux server or another machine of any platform should be fairly simple. A web project in eclipse webtools can be exported as a .war archive which can be dropped in just about any app server/container. Hope this helps in some way.-vOn 4/9/06, Daniel Spiewak [EMAIL PROTECTED] wrote: I can't think of many references that give the kind of overview you're looking for. Having just been (arguably still at) the same point you're at in terms of knowledge of web apps, I really can't say that there is a good solution. What I did is blindly followed the install instructions and then poked around with the various options checking consequences. I found as many references as I could find about wicket component details, as many tutorials as I could dig up on using them, and stumbled my way through configuring Tomcat so I could experiment. If anyone does have any references of this type, I'm interested too. :-)Daniel On 4/9/06, Dave Johnson [EMAIL PROTECTED] wrote:I'm an old COBOL guy who has learned enough Java to be useful in a corporate environment where I can see the need for a new class, generatea _javascript_ proxy to call the Java class from the UI, and build a classwith Eclipse to do the job.Now I'd like to begin developing in Wicket for my own purposes under Windows 2000 / XP.However, when it comes to the infrastructure of webapps, I get mired in details much too quickly.What are some good references that clearly explain the various levels ofsoftware I encounter, such as Linux, Tomcat,Jetty, Hibernate, PHP, MySQL and all the rest, and whether they're on the local machine or theremote server?And which are even needed?Most of what I find seems to assume too much familiarity with theseissues.I need a high-level overview that explains all this stuff without dropping down to 300 feet so quickly.Blindly followinginstallation instructions doesn't work well without knowing theconsequences of various choices.Thanks for any help.Dave ---This SF.Net email is sponsored by xPML, a groundbreaking scripting languagethat extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___Wicket-user mailing listWicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
