Menu
▾
▴
springframework-developer
|
From: <jue...@we...> - 2003-12-05 07:24:17
|
Darren, =20 Orion 2.0.2's JSP engine is hopelessly broken. Have a look at the = following issue that I submitted back in July: http://bugs.orionserver.com/issue/view.jsp?id=3D1081 =20 Noone seems to care about it, even though that definitely is a major bug = in terms of JSP 1.2 compatibility. What you're experiencing seems to be = another Orion bug: It can't load tag library descriptors from the jar = files in WEB-INF\lib, as required by JSP 1.2 (a very convenient feature, = BTW - no manual TLD declarations in web.xml anymore). =20 Therefore, let's simply forget about Orion - it's effectively an = abandoned product. We recently had to use Oracle's OC4J at werk3AT: It's = far ahead in terms of the JSP engine - everything works nicely. OC4J has = its problems in the EJB container, though, but that doesn't worry me at = all. =20 BTW, I do Petclinic and Countries tests on Tomcat 4.0 (which is still = the most popular IDE plugin), Tomcat 4.1 (which has a completely = rewritten JSP compiler), and Resin 2.1 before each release. Starting = with 1.0 RCs, I'll add Tomcat 5.0 and Resin 3.0 (heavily rewritten) to = my mix. I would be happy if we could do regular tests on JBoss/Jetty = 3.2, OC4J 9.0.3, WebLogic 8.1, WebSphere 5.0 too. =20 Juergen =20 ________________________________ Von: spr...@li... im Auftrag = von Darren Davison Gesendet: Fr 05.12.2003 01:04 An: spr...@li... Betreff: [Springframework-developer] Orion 2.0.2 has anyone deployed petclinic on Orion 2.0.2? I'm trying to do it as = part of the autobuilds and app testing, but I get an error trying to access = the default page: 500 Internal Server Error Error parsing JSP page /petclinic/index.jsp Error loading taglib at http://www.springframework.org/tags: META-INF/taglib.tld Seems ok on Tomcat, haven't tried jboss yet. -- Darren Davison Public Key: http://www.davison.uk.net/key.jsp ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's Free Linux Tutorials. Learn everything from the bash shell to sys = admin. Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: <jue...@we...> - 2003-12-05 09:56:04
|
Good point. Since Greg Wilkins joined Core Developers Network, the JBoss = Group doesn't like Jetty anymore ;-) JBoss-Jetty isn't really important, = I agree. We could test on Jetty 4.2 standalone though, as effectively = none of our sample applications requires any particular JBoss services. =20 Juergen =20 ________________________________ Von: spr...@li... im Auftrag = von Darren Davison Gesendet: Fr 05.12.2003 10:18 An: spr...@li... Betreff: Re: [Springframework-developer] Orion 2.0.2 > (heavily rewritten) to my mix. I would be happy if we could do > regular tests on JBoss/Jetty 3.2, OC4J 9.0.3, WebLogic 8.1, Do you want jboss-jetty to be used for autobuilds rather than (or in = addition to) the standard jboss which includes Tomcat? I know it essentially = partly duplicates the Tomcat testing, but their SF d/l stats show appx 55000 downloads for standard jboss-3.2.2 final and appx. 1800 for = jboss-jetty-3.2.2 final. -- Darren Davison Public Key: http://www.davison.uk.net/key.jsp ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's Free Linux Tutorials. Learn everything from the bash shell to sys = admin. Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Rod J. <rod...@in...> - 2003-12-05 10:04:55
|
>Good point. Since Greg Wilkins joined Core Developers Network, the JBoss Group doesn't like Jetty anymore ;-) JBoss-Jetty isn't really important, I agree. We could test on Jetty 4.2 standalone though, as effectively none of our sample applications requires any particular JBoss services. I would like to see Jetty included for standalone. I was just talking to someone last night who claimed it's still superior to Tomcat. Looking at the depth of the Tomcat stack traces vs those from WebLogic during my Spring performance tests recently, it wasn't hard to see why WebLogic was 2-4x faster than JBoss/Tomcat. |
|
From: Darren D. <dda...@kg...> - 2003-12-05 11:42:24
|
> >Good point. Since Greg Wilkins joined Core Developers Network, the JBoss > Group doesn't like Jetty anymore ;-) JBoss-Jetty isn't really > important, I agree. We could test on Jetty 4.2 standalone though, as > effectively none of our sample applications requires any particular > JBoss services. > > I would like to see Jetty included for standalone. I was just > talking to someone last night who claimed it's still superior to > Tomcat. Looking at the depth of the Tomcat stack traces vs those > from WebLogic during my Spring performance tests recently, it wasn't > hard to see why WebLogic was 2-4x faster than JBoss/Tomcat. no problem. I'll add Jetty configs to the sources. -- Darren Davison Public Key: http://www.davison.uk.net/key.jsp |
|
From: Darren D. <da...@da...> - 2003-12-06 01:03:16
|
> > I would like to see Jetty included for standalone. I was just > > talking to someone last night who claimed it's still superior to > > Tomcat. Looking at the depth of the Tomcat stack traces vs those > > from WebLogic during my Spring performance tests recently, it wasn't > > hard to see why WebLogic was 2-4x faster than JBoss/Tomcat. > > no problem. I'll add Jetty configs to the sources. looks suspiciously like the same problem we saw on Orion. Using Jetty 4.2.14 and a petclinic deployment.. 00:55:30.733 WARN!! [Listener-4]org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:592)11> Exception for / org.apache.jasper.JasperException: /index.jsp(0,0) This absolute uri (http://www.springframework.org/tags) cannot be resolved in either web.xml or the jar files deployed with this application at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:94) at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:428) ... ... Tomcat 4.1 and 5.0 are both OK (presumably therefore JBoss/Tomcat will be too). Anyone tried this on Resin yet? -- Darren Davison Public Key: http://www.davison.uk.net/key.jsp |
|
From: Darren D. <da...@da...> - 2003-12-06 01:30:46
|
On Saturday 06 December 2003 01:03, Darren Davison wrote: > looks suspiciously like the same problem we saw on Orion. Using Jetty > 4.2.14 and a petclinic deployment.. dammit. I just did a cvs update between test runs, and now I get a different error (at application load): java.lang.NoClassDefFoundError: com/ibatis/common/exception/NestedRuntimeException Same error on Jetty 4, Tomct 4 and Tomcat 5. Has petclinic changed or something in spring.jar? I need to get some sleep, I'll look at this again on Sunday at some point. -- Darren Davison Public Key: http://www.davison.uk.net/key.jsp |
|
From: Darren D. <dda...@kg...> - 2003-12-08 08:17:00
|
> looks suspiciously like the same problem we saw on Orion. Using > Jetty > 4.2.14 and a petclinic deployment.. > > 00:55:30.733 WARN!! > [Listener- > 4]org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:592)11> Exception for / org.apache.jasper.JasperException: /index.jsp(0,0) This absolute uri > (http://www.springframework.org/tags) cannot be resolved in either > web.xml or the jar files deployed with this application at > org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:94) at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:428) ... ... > > Tomcat 4.1 and 5.0 are both OK (presumably therefore JBoss/Tomcat > will be too). Anyone tried this on Resin yet? I've now tried Resin 2.1x and it's OK too. So Jetty 4.2x is a no-go along with Orion 2.0x at present. Regards, -- Darren Davison Public Key: http://www.davison.uk.net/key.jsp |
|
From: Darren D. <dda...@kg...> - 2003-12-05 08:46:17
|
> Darren, > > Orion 2.0.2's JSP engine is hopelessly broken. ok, I'll drop the orion stuff from the autobuilds tree - I didn't realise it was in such a state. > BTW, I do Petclinic and Countries tests on Tomcat 4.0 (which is > still the most popular IDE plugin), Tomcat 4.1 (which has a > completely rewritten JSP compiler), and Resin 2.1 before each > release. Starting with 1.0 RCs, I'll add Tomcat 5.0 and Resin 3.0 > (heavily rewritten) to my mix. I would be happy if we could do > regular tests on JBoss/Jetty 3.2, OC4J 9.0.3, WebLogic 8.1, > WebSphere 5.0 too. Tomcat 4.1.x is setup to go already in the project and JBoss will be by tonight. I've never used Resin but I'll grab a copy and add configs for it too. I can do Tomcat 5.x also. The 'infrastructure' for auto deploying and configuring various servers is done, so adding new servers is fairly simple. I know zip about WebLogic but from snippets I hear, it sounds like it's not too difficult to configure (xml files?) so that can be added as a server option too. WebSphere is a different kettle of fish as I've probably mentioned before and there's no realistic chance of it being added as an option for the autobuilds stuff I'm doing. However I can always build the sample apps here at work and run them on a manual basis for each release. -- Darren Davison Public Key: http://www.davison.uk.net/key.jsp |
|
From: Rod J. <rod...@in...> - 2003-12-05 09:36:27
|
> I know zip about WebLogic but from snippets I hear, it sounds like it's not > too difficult to configure (xml files?) so that can be added as a server > option too. WLS is pretty easy. Config is held in config.xml. Basically all you have to do is set up a datasource. You can do this easily in the console and then copy the generated config.xml. You also need weblogic.xml in the WEB-INF directory to resolve mappings. I've checked in an example for the benchmark/cmt application. Also 8.1 has a year-long license, which is nice. Regards, Rod |
|
From: <tri...@tr...> - 2003-12-05 14:45:56
|
WebLogic 8.1 also comes with ant and some custom ant tasks for creating a WebLogic domain and data sources, JMS queues etc. from a script. It's worth looking into if you need to do more dynamic configurations. There is also WLShell that lets you create and manipulate WebLogic MBeans from a scripting environment (http://www.wlshell.com). Thomas Quoting Rod Johnson <rod...@in...>: > > I know zip about WebLogic but from snippets I hear, it sounds like it's > not > > too difficult to configure (xml files?) so that can be added as a server > > option too. > WLS is pretty easy. Config is held in config.xml. Basically all you have to > do is set up a datasource. You can do this easily in the console and then > copy the generated config.xml. > > You also need weblogic.xml in the WEB-INF directory to resolve mappings. > I've checked in an example for the benchmark/cmt application. > > Also 8.1 has a year-long license, which is nice. > > Regards, > Rod > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Darren D. <dda...@kg...> - 2003-12-05 09:18:32
|
> (heavily rewritten) to my mix. I would be happy if we could do > regular tests on JBoss/Jetty 3.2, OC4J 9.0.3, WebLogic 8.1, Do you want jboss-jetty to be used for autobuilds rather than (or in addition to) the standard jboss which includes Tomcat? I know it essentially partly duplicates the Tomcat testing, but their SF d/l stats show appx 55000 downloads for standard jboss-3.2.2 final and appx. 1800 for jboss-jetty-3.2.2 final. -- Darren Davison Public Key: http://www.davison.uk.net/key.jsp |
|
From: Rod J. <rod...@in...> - 2003-12-05 09:47:03
|
>Orion 2.0.2's JSP engine is hopelessly broken. Have a look at the following issue that I submitted back in July: http://bugs.orionserver.com/issue/view.jsp?id=1081 >Therefore, let's simply forget about Orion - it's effectively an abandoned product. We recently had to use Oracle's OC4J at werk3AT: It's far ahead in terms of the JSP engine - everything works nicely. OC4J has its problems in the EJB container, though, but that doesn't worry me at all. It's a pity, I used to like Orion. I did most of the early work on the book and what became Spring on Orion (1.5.2 I think). There are also EJB problems in Orion. A few months ago I was doing a prototype for work project involving remote SLSBs, and couldn't get Orion 2.0.1 to pass parameters of types other than int (I think) over RMI. I was wondering whether or not there was some dreadful bug in the Spring AOP stuff I was using on the client side until I switched to WLS 8.1. Not only did everything work perfectly in WLS (although I did later run into a more complicated problem with RMI that required upgrading to the latest service pack), but I found that WLS 8.1 is a joy to develop on. Just drop the Jar in the applications directory and you're done. I now tend to use JBoss 3.2.2 and WebLogic 8.1 interchangeably for my own projects, with deployment descriptors for both. Regards, Rod |
|
From: Patrick B. <spr...@pa...> - 2003-12-05 13:54:40
|
Rod Johnson wrote: > Not only did everything work perfectly in WLS (although I did later run into > a more complicated problem with RMI that required upgrading to the latest > service pack), but I found that WLS 8.1 is a joy to develop on. Just drop > the Jar in the applications directory and you're done. > > I now tend to use JBoss 3.2.2 and WebLogic 8.1 interchangeably for my own > projects, with deployment descriptors for both. > > Regards, > Rod > [OT slightly] Man, I guess Weblogic has come a long way since 5.1 in terms of enjoyment to use. Good to hear that for the people who use it. We switched to Macromedia's Jrun 4 and have never looked back. The cost savings alone made my boss jump for joy. And the development cycle time changed so much for the better, the developers were jumping for joy as well. Really not intended as an ad for Jrun, but I know it tends to get a bad rep in the industry. 4.0 has come a long way for them. I find between deploying on Jrun and Jboss, I can find all the places where our code isn't up to spec. In the conversion from Weblogic to Jrun, we found many places in our app where the code broke spec and should have never worked in the first place. Best example is member variables in SLSBs that are set in one remote method invocation, and used in another. Thanks, Patrick |
|
From: Peter d. H. <pe...@de...> - 2003-12-05 17:57:33
|
We found another Orion 2.0.2 bug recently: when deploying two Spring-based webapps on the same Orion server, we got into major classloading issues where loaded in one application would end up in the other. The problem turned out to be that, Orion does not seem to correctly set the Thread context classloader for the second and subsequent webapps that it initialises. Because Spring uses the context classloader throughout this means that any class loaded by name during Spring initialisation will get loaded from the wrong webapp. Oops. We ended up creating a version of org.springframework.web.context.ContextLoaderServlet with one extra line in init(): Thread.currentThread().setContextClassLoader(getClass().getClassLoader()); Suddenly all our problems disappeared. - Peter |
|
From: Mike Cannon-B. <mi...@at...> - 2003-12-06 01:09:43
|
I believe you just need to speficy -userThreads on the command line to make this work. (Thread context classloaders in user spawned threads) Cheers, Mike On 6/12/03 5:00 AM, "Peter den Haan" (pe...@de...) penned the words: > We found another Orion 2.0.2 bug recently: when deploying two Spring-based > webapps on the same Orion server, we got into major classloading issues > where loaded in one application would end up in the other. > > The problem turned out to be that, Orion does not seem to correctly set the > Thread context classloader for the second and subsequent webapps that it > initialises. Because Spring uses the context classloader throughout this > means that any class loaded by name during Spring initialisation will get > loaded from the wrong webapp. Oops. > > We ended up creating a version of > org.springframework.web.context.ContextLoaderServlet with one extra line in > init(): > > > Thread.currentThread().setContextClassLoader(getClass().getClassLoader()); > > Suddenly all our problems disappeared. > > - Peter > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer |
