[chandra_goliva]

Hi there,

I have Myeclipse 5.0 GA over Eclipse 3.2.0 and ‘m attempting to deploy a J2EE app on to weblogic 8.1/9.2 servers.

Structure:
earapp
-APP-INF/lib/<<shared library jars>>
(weblogic automatically makes them available for all modules so I no manifest edits)
-earappEJB
-META-INF/manifest.mf
(I had to put a ‘Class-Path: .’ to make it to load)
-earappWeb
…WEB-INF/lib/<<webapp specific library jars>>

I have a couple of issues that I wanted to bring to your notice. Please feel free to split these items into different discussion topics if you want for better managibility.

1. My app has 2 bean managed read-only entity ejbs and remaining all stateless. The example app(TraderX) demonstrated XDoclet usage which I could download and see it working well. For some reason my XDoclet creates a weblogic-cmp-rdbms-jar.xml though I don’t need it. Then my build shows it as an error so I delete it after doclet run manually. What is causing this?

2. Is the weblogic task in XDoclet supports Weblogic Server 9.2 yet? I think have tried putting the value as “9.2” and “9” but it didn’t like it. Please confirm.

3. I think it would be nice to have the exported jars from dependent projects (or EJB/Web modules) directed to an explicitly defined path under EAR root directory (like in my case ‘/APP-INF/lib’ under root. (I guess the default behavior is that jars all be placed under root directly). Since weblogic custom deployment structure takes anything under AP-INF/lib dynamically at parent class loader level and eliminating manifest file manipulations.

4. I had to put a period(.) in the manifest classpath to deploy ejbs, without it the container complained it could not load the ejb impl classes!! All classes are under root of ‘earappEJB’ but it still can’t find it. I just wanted to minimize my manifest file dependencies. Is there any way I can mandate IDE to generate an ejb-jar file instead of exploded dir. for ejb module then I know my server would not need any .mf entry.

5. Seems to me like you recommend using manifest file for ejb module deployment but the EJB project build does not seem to be using the class-path that I manually put in to its .mf file. So, I had to add the resp jar files as libraries to project. This would be good to have feature so that we could get to see how a target J2EE complaint container would load them during deployment.

6. I have been seeing deploy successful message upon deploying my app but in reality my container failed to load it correctly when its started. so, I believe this is due to the diffs in MyEclipse IDE dependency strategy and J2EE containers deploy strategy.

I have a complex system which I can’t strip easily for you to understand what I want to achieve but if you take a combination of stateless, entity ejb in your ejb project and try deploy the ear on weblogic 8.1 you would see what is involved in it. All item 4, 5, 6 could be related in way.

Help is appreciated.

Thanks,
Chandra
Genentech, Inc.
Subscriber Code for MyEclipse: genentechca-UL3-EX2007-09-06

[Riyad Kalla]

1) I’m not entirely sure. Please try double checking your EJB doclet settings and see if you have some weblogic property turned on to generate that or a subtask enabled to generate that file.

2) I do not believe so. XDoclet development has all but stopped for quite a while now, I doubt there will be another release. At this point I would consider Xdoclet a legacy technology.

3) This is a good idea, I’ll file this.

4) You need to use packages. It is a very bad practice to not use packages. It may work in some app servers, but not all and is generally the cause of some errors (class loading)

5) Good point.

6) We will look into this internally. We made some improvements to deployment in the next release and will continue to enhance it.

[chandra_goliva]

Hello Riyad,
Thanks for the quick follow-up and some answers.

Re. 1:
I will check this one up more closely and let you know. I think have not enabled anything more than required
but will double check.

Re. 2:
Is there an alternative for javadoc attributes driven development if the XDoclet is considered a legacy? What is Myeclipse strategy for its future releases? Would it still support future weblogic versions?

Re. 4:
Could you elaborate bit more on this? Using packages or some kind of jar packages?(If you meant java packages, we do have them already)

Thanks very much,
Chandra

[Riyad Kalla]

1) Thank you.

2) Well what is replacing XDoclet is the use of annotations with JEE 5 which MyEclipse will be adding support for starting at the end of this year and into next. While I still think Xdoclet is a great technology, the 1.2.2 release they last made is 3 years old or so and they haven’t made a release since then that why I made the comment “legacy”. I believe the future use of annotations is going to replace the need of things like XDoclet.

4) I might have misunderstood, I took your comment to mean that your classes were being compiled into the base default package so you had to use “.” as the classpath to get it to load. Given that, I was saying that you should be using java packages (com.company.xxx), but it sounds like you are already doing this.

[Author]

Posts