Weblogic Integration

I tried the Weblogic Integration in build 992 and after some time I managed to start a local server. Starting failed with lots of exceptions which I did not examine further. There is one thing I did not figure out how to achieve (maybe it is not possible at all?):

You can specify additional classpath entries but the weblogic.jar always comes first. How about patches from BEA which have to be put before the weblogic.jar in the classpath? Maybe weblogic.jar should appear in the classpath box as a read-only entry with the ability to change to order (just like in the module settings).

Michael

11 comments
Comment actions Permalink

I assume that you are referring to exceptions as are shown in: http://www.intellij.net/tracker/idea/viewSCR?publicId=23095
How did you get past the exceptions that caused startup to fail?
Did you also get debugging the local server to work?

0
Comment actions Permalink

Well, this was the first one. You need to put weblogic.jar into IDEA's
lib directory. But lots of other exceptions occured then and the server
failed to start.

Tim Haley wrote:

I assume that you are referring to exceptions as are shown in: http://www.intellij.net/tracker/idea/viewSCR?publicId=23095
How did you get past the exceptions that caused startup to fail?
Did you also get debugging the local server to work?


0
Comment actions Permalink

On Wed, 10 Dec 2003 20:02:24 +0100, Michael Descher wrote:

Well, this was the first one. You need to put weblogic.jar into IDEA's lib
directory. But lots of other exceptions occured then and the server failed
to start.


I can't even get Tomcat to start with a webapp correctly so I don't know
that it's a weblogic thing. You might have to setup a web module to get
things to run properly, but I've had a pretty nice nightmare of a time
trying to get even a simple webmodule to work as expected.


Tim Haley wrote:

>> I assume that you are referring to exceptions as are shown in:
>> http://www.intellij.net/tracker/idea/viewSCR?publicId=23095 How did you
>> get past the exceptions that caused startup to fail? Did you also get
>> debugging the local server to work?

0
Comment actions Permalink

things to run properly, but I've had a pretty nice nightmare of a time
trying to get even a simple webmodule to work as expected.


Yes, I really hope that web module support will become much better soon.
It really should be integrated nicely into the dialog where java modules
are configured. Strange enough that you can see web modules in this
dialog after creating them in a completely different way. Editing a
previously created web module (e.g. adding roots) still is not possible
if I did not oversee something.

0
Comment actions Permalink

On Thu, 11 Dec 2003 16:41:11 +0100, Michael Descher wrote:

>> things to run properly, but I've had a pretty nice nightmare of a time
>> trying to get even a simple webmodule to work as expected.


Yes, I really hope that web module support will become much better soon.
It really should be integrated nicely into the dialog where java modules
are configured. Strange enough that you can see web modules in this dialog
after creating them in a completely different way. Editing a previously
created web module (e.g. adding roots) still is not possible if I did not
oversee something.


Well in their defense, it does have a nice big far red disclaimer on there
saying it's going to change soon. There has been a lot of changes to J2EE
stuff in the last 2 builds, and I'm guessing that this is where their
efforts are being concentrated. The rest of the features are in place and
are undergoing bug fixes more than anything.

I'd give it a couple of builds before we see something very usable.
Alexey requested that I send him my web app setup so they can get the web
module working with it. I'm not saying that my way of doing things is by
any means a standar mode of operation, but IMHO it sure is a lot closer
than what they thought it should be like :)

R

0
Comment actions Permalink

Alexey requested that I send him my web app setup so
they can get the web module working with it.


Would you mind posting your web app example here? I would like to compare it with my preferred setup to see if it matches my needs (to prevent Alexey's modifications from beeing too Sfeir-specific...).

0
Comment actions Permalink

On Thu, 11 Dec 2003 16:46:52 +0000, Martin Fuhrer wrote:

>> Alexey requested that I send him my web app setup so they can get the
>> web module working with it.


Would you mind posting your web app example here? I would like to compare
it with my preferred setup to see if it matches my needs (to prevent
Alexey's modifications from beeing too Sfeir-specific...).


hahaha we're cracking up at this one here at work. Sfeir-specific.

Ok I don't want to post the whole damn thing, but here is my file
structure (or at least preferred), and hopefuly it's reasonable enough
that you'll see that things can be moved to fit just about anything.

mesquite(my app's root dir)
ext (extras-module)
database scripts
server specific scripts
jsps(mesquite-jsp-module)
common
header.jsp
...
index.jsp
security
login.jsp
...
libs (mesquite-libs-module)
struts.jar
db-ojb.jar
...
media (mesquite-media-module)
css
mesquite.css
...
images
myCool.gif
...
resources (mesquite-resources-module)
struts-config.xml
repository.xml
web.xml
tlds
struts.tld
...
...
src (mesquite-source)
com
codepuccino
...
classes (just a dir to post as an output path, this won't be needed soon)
build (dir with build.xml and things like that)

webapp(this is my real webroot where I compile and copy the files on make)
(jsps-module content)
(media-module content)
WEB-INF
web.xml
classes
(resources module content)
(src-module content)
lib
(library module content)
tlds
(tld module content)


As you can see when the whole enchilada is built, it builds it into what
the final webapp 'should' look like. If you have multiple webapps, what I
do is I create a directory under webapp, give it the name of the web app,
and setup the same structure underneath it.

I don't think there is anything Sfeir specifc about this ;)

R

0
Comment actions Permalink

I don't think there is anything Sfeir specifc about
this ;)


Oh, I don't know yet. I will try to de-Sfeir-ize it... :)

No, seriously: thanks, I will compare it to my own pitifully attempts.

But just to be sure: you didn't get it working, did you? I gave up after several attempts and switched back to the previous build.

0
Comment actions Permalink

I don't think there is anything Sfeir specifc about this ;)


I couldn't resist : it is a Sfeirical directory structure :))

--
Guillaume Laforge
http://glaforge.free.fr/weblog/index.php?catid=2&blogid=1


0
Comment actions Permalink

On Thu, 11 Dec 2003 22:32:41 +0100, Guillaume Laforge wrote:

>> I don't think there is anything Sfeir specifc about this ;)


I couldn't resist : it is a Sfeirical directory structure :))

hahaha except that it's pronounced like Sphair not Sphere... no round
stuff here... except for my bald head LOL!

R

0
Comment actions Permalink

On Thu, 11 Dec 2003 21:32:27 +0000, Martin Fuhrer wrote:

>> I don't think there is anything Sfeir specifc about this ;)


Oh, I don't know yet. I will try to de-Sfeir-ize it... :)

No, seriously: thanks, I will compare it to my own pitifully attempts.

But just to be sure: you didn't get it working, did you? I gave up after
several attempts and switched back to the previous build.


No in fact it didn't work. Lots of trouble. A few issues popped up
including the fact that web.xml kept showing up in red because it was in
the resources module and not in a content directory of the web module. I
didn't show the web module in the list because that had nothing to do with
my structure and how I think modules should be setup for web apps. The
web module should not have anything in it except which other modules it
depends on, including src, and the settings for deployment and location of
web.xml.

Second issue is that web.xml needs to be with resources, since a lot of
the info in web.xml requires other xml files to resolve properly. If I
move it on its own I get other problems.

Third issue is that when you DO make the whole project:
a- Make just doesn't cut it, I don't want to make the whole project, just
the web module and the files which it depends on. MAKING causes the
whole enchilada to compile, and some other web modules are just not ready
yet.
b- WEB-INF is created, with web.xml inside, but nothing else compiles
into WEB-INF/classes, nor is anything copied over to the same dir. It
seems though, that WEB-INF/lib is copied correctly from a preset module.

Fourth issue is that in the current setup, as it was explained to me by
Alexey, and hopefuly he will read this and correct me, is that what they
mean by webroot, is actually the root of my project (mesquite in my
example) and that's just ugly, who wants to have all the files in
jsps-module, lib-modle, resouces etc... created at the root of the
project? Right now if you try it the correct way and make webroot / (root
of project) you end up with WEB-INF at the root of the project, proving my
point.

Fifth issue is that no matter what I do, pressing the run/debug button did
not compile the appropriate web module. It just started up Tomcat, and
nothing else. Dead in the water.

Sixth issue is that if you DO get things to compile you end up with
recursively compiled directories somehow. So in WEB-INF/classes I ended
up with:
WEB-INF/classes
com
codepuccino
...
jsps
lib
resources
src
com
codepuccino
...
jsps
lib
resources
src
com
codepuccino

Nasty.

Seventh issue, and this is where I gave up, there is no way to edit all
the parameters of the web module. Once you set which web.xml you want to
use, that's it, use this one or else. if you chose the name and
location of your webroot, you're stuck with it. You have to delete the
whole enchilada and re create it. That proved to be too much for my
patience.

I'm pretty sure I've filed bugs for all this.

You guys might add more to it I'm sure, but after all this stuff I just
lost hope and ran out of patience, though I must admit, I am trying to
setup a very simple web module right now, just to run my web app, since
the 'traditional' web app is completely disabled.

R

0

Please sign in to leave a comment.