migrating to a different java and tomcat version

> i developed an application using j2sdk1.4 and tomcat

> 4.1.

>

> is it possible to deploy that in j2ee and tomcat5?

> will there be any problems?

j2sdk 1.4 migration to j2ee - what did you develop using j2sdk1.4 alone that was deployed in tomcat 4.1 ? :)

Tomcat 5 will accomodate any java web application upto j2ee 1.3 (ie servlets 2.3 and jsp 1.1). I havent worked on tomcat for earlier versions, so I cant tell much about that.

If you have developed a web application on tomcat 4.1 and wish to migrate to 5.0, your code as such would work fine I guess (though there may be better ways to do a lot of things). The things to look out for would be the application deployment itself - like setting up connection pools etc. Anyways give it a shot and post here when you have specific issues.

cheers,

ram.

Madathil_Prasada at 2007-7-15 17:59:19 >

>i did a web application using jsp and java beans in j2se with tomcat4.1

That would be j2ee.

j2se is the java standard environment which doesnt contain functionalities for jsp, servlets and the like.

Regarding the migration, all i said in the previous post holds.

ram.

Madathil_Prasada at 2007-7-15 17:59:19 >

Nops, jsps are still converted to servlets remember.

And the servlet library is not contained in j2se's jar. It works because tomcat by default has the servlet's jar files in its library. (in common/lib)

Also at development time, you dont have to compile anything if its pure jsps. At runtime, they become servlets which then accesses libraries not found in j2se. But since tomcat provides it by default, it still works.

Yes, beans do not require any j2ee specific pkgs.

ram.

Madathil_Prasada at 2007-7-15 17:59:19 >

As I said in my first post, code-wise I dont think anything would break for a straight forward applications. You will have to setup the jar files that you use in the application in the new server ....blah blah.

If your application depends on some server admin specific setup in server.xml like datasources for connection pooling, then you need to know if there's a difference in the way things were done in 4.1 and are done in 5.x.

By what you are saying, its pretty simple and straightforward (only jsp and beans) and I think you will not have any problems.

Oh, one thing - I dont know if tomcat 4.1 enforces that the bean class have to be packaged. I hope you have them so anyways, else it wouldnt work in 5.x

The only way to find out otherwise is to go for it. There will be issues, of that Iam sure, though none would be blockers. Set it up on your local machine and try it out.

cheers,

ram.

Madathil_Prasada at 2007-7-15 17:59:19 >

> just a follow up and some clarifications regarding

> j2se running on tomcat.

>

> since it runs because tomcat by default has the

> servlet jars in its library,would jsps in j2se still

> run if another application server, other than tomcat,

> was used?

yes, most servers would have the api jars in their classpath. It may have a different name, but nonetheless present.

cheers,

ram.

Madathil_Prasada at 2007-7-15 17:59:19 >

Oh and btw, I think both stl and jsf jars are subsets of j2ee jars (just like the servlet-api.jar which provides servlet and jsp apis ).

Hence I think they would be available in the j2ee jars in those versions that include jstl and jsf (j2ee 1.4, I guess). Which in turn means that if you use an app server that supports j2ee 1.4 (not tomcat, that's a webserver), the server would provide you with a jar file that would include jstl/jsf etc.

Ram.

Madathil_Prasada at 2007-7-20 14:34:43 >

>

> so ur saying that if i use j2ee and i have a mail

> service, i wouldn't have to download the javamail

> api?

> because i used mail service and had to download the

> api because i am using j2ee.

>

sorry, i meant i was using j2SE and still had to download javamail

shuinia at 2007-7-20 14:34:43 >

> >j2ee just basically provides more convenience.....

>

> Yes, its kind of that, though I dont know if I would

> use the word 'convenience', lol :)

>

There's a bigger issue here - that of versioning. Assume you have the j2ee1.4.jar available. That would ensure that you would be using the

1. servlet 2.4 spec

2. jsp 1.2 spec

3. ejb 2.1 spec and so on........

Java's versioing of j2ee and the individual components that make it is pure hell, to say the least.

So using a j2ee version specific jar would ensure that your individual components support the version they have to abide by in the j2ee spec.

What that means is that theoretically, its possible that you may download a version of servlet/jsp (that abides by the j2ee 1.3 spec), a version of javamail (thata abides by the j2ee 1.4 spec) and a version of, say ejb (that goes by the 1.2 spec). Needless to say, that's version hell, one that you can do without :)

ram.

Madathil_Prasada at 2007-7-20 14:34:43 >