The problem with resin is that it does not recognize the modified java classes.
I am trying hard for three days to configure wicket 1.2 with either resin 2 or 3 or tomcat 6.
I feel like crying. I cannot believe java web development can be soo terrible.
No matter what I do, tomcat 6 would not do the wicket homepage rediection. So I struggle with resin 2 or 3.
The problem with resin is that it does not recognize the modified java classes. Please help me, ask decent money and I will gladly pay. All I want is a resin or tomcat configured with wicket 1.2 that will see the changed java classes. I cannot have the .html files in the /WEB-INF/classes directory as the stupid IDEA 6 will, on compilation, delete the .html files even if they are declared as resources, such as .properties.
Why, Why, Why does it have to be so hair-pulling to work with java stuff? Why please things don't just work as promised. Why, why ruby and php do at least what they say? Why, why? Three days and one night untill 3 am!
Please somebody help so I can finally start working on my application.
I need resin 2 or 3 to see the changed .class files. Of, I make even my family miserable.
OS: XP Java: 1.4,1.5,1.6
[ April 27, 2007: Message edited by: Florin Gheorghies ] [ April 27, 2007: Message edited by: Bear Bibeault ]
Ok, so reading some more documentation (have you done this?) since I don't know much about resin, it looks like the source= is not what you want. It's the classpath id that needs to be the full path to your classes folder, so something like:
It's not working either. If I could get Tomcat work, wou'd be fine. If you do any web stuff, what's the setup that works for you? I don't care what it is, I just need something that works with wicket 1.2.
Why would the 'id' be the full path!? How confusing can that be!