WebApps and 1002

WOW these guys move fast.

ok a couple of things gone (thank God) from webapps, so ignore them from
the mini how to...

1- No more senseless web root. Now the exploded directory is where it
points to. Now THIS makes sense! Nice work!

2- No more need for checking settings twice. it all sets up the first time.

These 2 are huge for changes. All deployment spots are set under Child
Modules in Web App tab. Perfect.

It took me a total of 10 minutes to setup a new web module. This is not
bad at all. It could be better, with some of the suggestions I made,
but man THIS NOW IS STARTING TO SMELL LIKE TEEN SPIRIT!

Way to go JetSons.

R

5 comments
Comment actions Permalink

WOWOWOWOW! JSP Tag libs work now too!!!! HOLLY SMOKES I am NOT
letting go of this BUILD!

YEEEEEHHHAAA!

R

Robert S. Sfeir wrote:

WOW these guys move fast.

ok a couple of things gone (thank God) from webapps, so ignore them from
the mini how to...

1- No more senseless web root. Now the exploded directory is where it
points to. Now THIS makes sense! Nice work!

2- No more need for checking settings twice. it all sets up the first
time.

These 2 are huge for changes. All deployment spots are set under Child
Modules in Web App tab. Perfect.

It took me a total of 10 minutes to setup a new web module. This is not
bad at all. It could be better, with some of the suggestions I made,
but man THIS NOW IS STARTING TO SMELL LIKE TEEN SPIRIT!

Way to go JetSons.

R

0
Comment actions Permalink

WOW! I have jsps as a module, and just setting them to be dependant on
a web module allowed them to recognize the taglibs!

man this is pretty sweet. I hope everyone tries this, because this is
by FAR the best J2EE support I've seen in a while... perhaps anywhere!
I can flip JSP modules and resouces like little switches, and I get a
whole new web module!

I love this!

JEKA and Alexey you guys RULE! (if anyone else worked on this quietly
you do too!)

R

Robert S. Sfeir wrote:

WOW these guys move fast.

ok a couple of things gone (thank God) from webapps, so ignore them from
the mini how to...

1- No more senseless web root. Now the exploded directory is where it
points to. Now THIS makes sense! Nice work!

2- No more need for checking settings twice. it all sets up the first
time.

These 2 are huge for changes. All deployment spots are set under Child
Modules in Web App tab. Perfect.

It took me a total of 10 minutes to setup a new web module. This is not
bad at all. It could be better, with some of the suggestions I made,
but man THIS NOW IS STARTING TO SMELL LIKE TEEN SPIRIT!

Way to go JetSons.

R

0
Comment actions Permalink

Robert S. Sfeir wrote:

WOW! I have jsps as a module, and just setting them to be dependant on
a web module allowed them to recognize the taglibs!


Spoke too soon on this. Still busted. If anyone figures out how to
properly resolve tag libs, please let us know.

R

0
Comment actions Permalink

Though settings get saved now, under most circumstances, if you modify a
library which web module has checked off in the libs it uses, like
removing jar from that library, this removed the child settings for the
web module completely. They need to be reset.

R

0
Comment actions Permalink

Turns out you CAN get a simple web app to recognize the tag libs and it works quite well. The trick is to have everything under one module, the web module. So setup the web module like you would your webroot.

Something like:
web-mod-root
jsps here
WEB-INF
web.xml
tld
tld.dtds here
classes
lib

This should be the structure of the simple web module. Now make the webmodule deploy everything to a webroot directory so the structure ends up being the same in there, and in the ide settings turn on Web, and like the old times point the webapp to the root of your web-module. That should do the trick.

If you have multiple modules like I do, you're out of luck :)

R

0

Please sign in to leave a comment.