[angryYarn]

Hi,

We are looking for a good strategy to deploy EJBs and Web Services in various existing and new applications in our company.

For EJBs, XDoclet needs to overwrite the existing interfaces and homes. We currently have these checked into source control, which means they must be checked out first. Unfortunately we have one project with 108 version 2.0 session beans, so that is unwieldy. Perhaps interfaces and homes can be generated at deploy time?

We also use ANT scripts to create our production EARs. We don’t want to increase our production deployment time but generating too much during deployment.

A co-worker has had success letting Blue do alot of the deployment work for Web Services, but what should the strategy be for ANT builds?

Any strategies would be appreciated.

Thanks,
Phil

[angryYarn]

Here are some options we are considering for generateing interfaces and homes:

OPTION 1
Generate all interfaces via Xdoclet each time a method signature changes.
The interfaces must be in source control to create production builds via ANT, hence all interfaces must be checked out so Xdoclet can modify them, and checked in afterwards.
OPTION 2
Configure XDoclet to only modify interfaces for beans that have changed. Don’t know if possible. Only requires checkout of changed interfaces.
OPTION 3
Generate all via Xdoclet first time, manually checkout and change method signature changes
OPTION 4
Generate during Blue deployment (don’ think possible, Blue recommends Xdoclet instead)
OPTION 5
Generate during EAR deployment (don’t think possible, else WSAD and Blue would do it)
OPTION 6
Generate during EAR deployment. Don’t check in interfaces. Developer runs XDoclet to generate interfaces locally. For productions build, add an XDoclet task generate interfaces to the ANT build script.

[Riyad Kalla]

Phil,
If you setup XDoclet for your projects inside of Blue, and tell it to instead of using a dynamically generated Xdoclet build file (under project properties > MyEclipse > XDoclet) tell it to generate a build file for you, you can add that Build File, using an Ant Builder I believe, to your list of Builders for your project… so it will be executed on files that change only.

That way your project is always in a consistent state so you just worry about deploying it and viola, no more “when do I run XDoclet” issues I think…

[angryYarn]

Riyad,
That’s a very good idea. I’ve discussed it with the team and I’m going to try to make it work. It was easy enough to generate the Xdoclet build file (xdoclet-build.xml). Now I’m going to work on incorporating it into my main ANT scripts.

Thanks,
Phil.

[Author]

Posts