Hi Richard. > 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.
>From my original post: <quote> All of these naming conventions should be user-defined at a project (and project default) level. </quote> I wouldn't expect everyone to have the same naming conventions, just to be consistent within a single project. I tend to agree with Eugene, that the definitive way to do this is to look in an ejb-jar.xml file to see which files are associated with one another. (User-defined) pattern-matching would simply be an easy-to-implement workaround for now. > 3. Eugene: I worry about size of the EJB support and general > slow-down of the tool. Could that be an optional module? (I know this was directed at Eugene, but anyway...) there is already pretty good support for JSPs, even for those of us who never (or rarely) use them. Having rudimentary support for EJBs would be a natural progression. No-one is suggesting any bloated "enterprise" functionality such as app server deployment, just basic code navigation between associated source files. Of course, assistance with creating the deployment files such as ejb-jar.xml would be lovely too :o) Cheers, Dan *************************************************************************************** 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
