[William Denton]

One thing that would be really helpful when you release the project import capability (scheduled for 3.0?) would be the ability to import EJB’s in XDoclet form. If XDoclet were the de facto standard for using beans in MyEclipse, then it might make good sense to add in some really good bean wizards and design tools (like visual tools to build CMP/CMR’s)

just a thought..

cheers,
–Bill

[Riyad Kalla]

Bill can you explain this in more detail?

[William Denton]

Riyad..
This really covered two new features that would be really nice. (First of all, let’s assume that MyEclipse will go the direction of using Xdoclet to support building EJBs for various target app servers)

1) Be able to import existing beans (source and deployment descriptors) into XDoclet-based bean projects. In other words, import in EJB source code for bean and interfaces, ejb-jar.xml, and appserver-specific deployment descriptors and generate an Xdoclet-augmented EJB class in the MyEclipse project. (reverse engineer XDoclet-based EJBs from existing beans)

2) Since Xdoclet allows writing EJBs that are much more portable between appservers, it now makes sence to develop EJB design wizards that can be used across target platforms. JBuilder, WSAD, and others both have EJB build tools that are very platform specific. MyEclipse could beat them all out by making nice graphical CMP/CMR build tools that supports all appservers.

cheers,
–Bill

[Riyad Kalla]

Hmm interesting… this is certainly nothing small so let me pass it by the team before we comment.

[Author]

Posts