Couple of comments: 1. Dan: the pattern based would work if everybody used same or similar patterns. Sometimes you see patterns like XYZBeanHome, XYZBeanRemote, XYZBean, sometimes the home and remote interfaces HAVE to live in a different package than the bean impl. 2. Dan: the methods usually follow 3 name patterns: ejbMethod for standard EJB methods (like create(...), findXYZ...), ejbHomeMethod for homeMethod and businessMethod for businessMethod 3. Eugene: I worry about size of the EJB support and general slow-down of the tool. Could that be an optional module? 4. Eugene: on the other side, probably most of IDEA users have to deal with EJBs at least sometimes. And they (we!) would love to have the EJB support available. 5. One of most important features for me would be "Find usages" going through the EJB interface boundary.
r. > -----Original Message----- > From: Eugene Belyaev [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, November 21, 2001 9:35 AM > To: [EMAIL PROTECTED] > Subject: RE: [Eap-features] EJB - go to declaration and interfaces > > > Dan, > > Well, actually there will be much more meta information about > EJBs that > IDEA will need to consider. And usually this information is specified > in various deployment descriptor. I would argue with the J2EE spec > authors since they have put bean configuration and deployment-specific > settings altogether, but well, that's something we live with now. > Despite the pattern-based approach for helping you find sets > of related > classes that form an EJB, there needs to be a mechanism for storing > other info about the EJBs, and I'm thinking of either MyBean.ijb xml > files that are basically xml files like deployment descriptors for a > single EJB component or using specified ejb-jar.xml files for > storing/retrieving this info. > > Best regards, > > Eugene Belyaev > IntelliJ Software, http://www.intellij.com > "Develop with pleasure" > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]] On Behalf Of North D > > Sent: Wednesday, November 21, 2001 5:14 PM > > To: '[EMAIL PROTECTED]' > > Subject: RE: [Eap-features] EJB - go to declaration and interfaces > > > > > > Hi Eugene. > > > > I think the pattern-based approach would be easiest for you > > guys to implement and would work in 99% of cases. > > > > 1) Pattern based file relationships: Foo is the remote > > interface implemented in FooEJB (or FooBean), with a FooHome > > home interface, and optionally a FooContract business > > interface. All of these naming conventions should be > > user-defined at a project (and project default) level. > > > > 2) Pattern based method relationships: someMethod in a home > > interface is implemented as ejbSomeMethod in an EJB class. > > > > Another possibility would be to use javadoc tags (like > > Together does), but that would involve a whole heap of work :o) > > > > My $0.02+VAT > > > > Cheers, > > Dan/tastapod > > > > > -----Original Message----- > > > From: Eugene Belyaev [mailto:[EMAIL PROTECTED]] > > > Sent: 21 November 2001 12:09 > > > To: [EMAIL PROTECTED] > > > Subject: RE: [Eap-features] EJB - go to declaration and interfaces > > > > > > > > > We've had some discussions on this before. The main > > question here is > > > how IDEA will know that the three classes should be treated as a > > > single EJB. Obviously, IDEA have to store this information > > somewhere. > > > > > > There are a couple of ways: > > > > > > 1) It should round-trip some ejb-jar.xml > > > Cons: bound to a specific ejb-jar. If the bean is used in > > > more than one > > > ejb-jar it won't work. > > > > > > 2) Have some IDEA specific ejb information > > > Pros: not bound to any deployment related stuff > > > Cons: will have to specify the same information in > different places > > > > > > So here we are, your suggestions are welcome. > > > > > > Best regards, > > > > > > Eugene Belyaev > > > IntelliJ Software, http://www.intellij.com > > > "Develop with pleasure" > > > > > > > > > > -----Original Message----- > > > > From: [EMAIL PROTECTED] > > > > [mailto:[EMAIL PROTECTED]] On Behalf Of Stephan > > > > J. Schmidt > > > > Sent: Wednesday, November 21, 2001 1:49 PM > > > > To: Descher, Michael > > > > Cc: [EMAIL PROTECTED] > > > > Subject: Re: [Eap-features] EJB - go to declaration and > interfaces > > > > > > > > > > > > > > > > > > If you put all business methods in the remote > interface without > > > > > another interface class, your EJB class of course does not > > > > implement > > > > > the interface. In this case you would need the ability to > > > > specify some > > > > > sort of naming convention to help IDEA find the bean > > > class for the > > > > > remote interface. > > > > > > > > > > > > > +1 > > > > > > > > A lot of IDEA features do not work for us, because > > > > we have EJBs. (Person, PersonBean, PersonHome,...) > > > > It would be nice if IDEA could recognize (naming > > > > convention) relationships between these classes, > > > > > > > > bye > > > > -stephan > > > > > > > > > > > > _______________________________________________ > > > > Eap-features mailing list > > > > [EMAIL PROTECTED] > > > > http://www.intellij.com/mailman/listinfo/eap-> features > > > > > > > > > > > > > _______________________________________________ > > > Eap-features mailing list > > > [EMAIL PROTECTED] > > > http://www.intellij.com/mailman/listinfo/eap-features > > > > > > > > > ************************************************************** > > ************************* > > This email and any files transmitted with it are confidential > > and intended > > solely for the use of the individual or entity to whom they > > are addressed. > > If you have received this email in error please notify > > [EMAIL PROTECTED] immediately. > > > > This footnote also confirms that this email message has been > > swept for the > > presence of computer viruses. > > ************************************************************** > > ************************* > > > > _______________________________________________ > > Eap-features mailing list > > [EMAIL PROTECTED] > > http://www.intellij.com/mailman/listinfo/eap-features > > > > > _______________________________________________ > Eap-features mailing list > [EMAIL PROTECTED] > http://www.intellij.com/mailman/listinfo/eap-features > _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-features
