[denz97]

Hello. I just created a new EJB, configured the XDOCLET (with the ff. settings: deployment descriptor, fileset, homeinterface, and remote interface). I did not include package substitution because i want the interfaces to be in the same package as my ejb bean. I then ran the xdoclet and generated the interface files (home and remote). My question is, …Should the remote interface automatically include the method signatures of my ejb bean? I just dont want to be keying in all my method signatures. What if i have quite a number of beans with lots of methods? I think developers would be more productive if MyEclipse is able to generate all your EJB method in the remote interface.

I appreciate your insights on this.

btw. I just tried Lomboz — this is a far better tool!

[denz97]

I meant MyEclipse is far better than Lomboz.

[Scott Anderson]

Denz97,

I meant MyEclipse is far better than Lomboz.

Thanks for clarifying; you’ll get much better service this way.

Should the remote interface automatically include the method signatures of my ejb bean? I just dont want to be keying in all my method signatures.

You don’t have to key your method signatures again. What kind of help would that be? 😉
XDoclet will include whatever methods you tag with the @ejb.interface-method tag in the javadoc for the method. You can also specify the view-type to specify if the method should be generated only for the remote interface, local interface, or both.

Remember, there is context-sensitive help available for XDoclet tags so just hitting @<ctrl+space> will show you the list of available tags along with regular javadoc help.

–Scott
MyEclipse Support

[denz97]

Yeah, I figured I’d get a better response by that clarification 🙂

Thanks a bunch Scott. Your da Man!!!

[Author]

Posts