+1 for 3
that sounds like a great idea. maybe something like
<group name='test classes'>
<class className='Foo'/>
<class type='Test'
className='FooTest'
extends='junit.framework.TestCase'
template='my/templates/directory/testcase.java'/>
</group>
<group name='ejb classes'>
<class type='Bean'
name='FooBean'
template='my/templates/directory/ejb.bean.java'/>
<class type='Remote Interface'
name='FooRemote'/>
<class type='Facade'
name='FooFacade'
extends='my.package.Facade'/>
...
</group>
(we call our interfaces facades)
what do people think?
> >3) To generalize 1) we could define relationship between
> files through
> >naming patterns and class semantics (extends from a certain
> base class)
> >and have customizable navigation shortcuts. That way you can
> speed up your
> >frameworks navigation tremendously:
> >The EJB framework is a good example:
> >bean -> remote interface -> interface -> home -> ejb-jar = a
> navigation
> >toggle could be implemented that would cycle through or navigation
> >directly to 1 EJB related files. Potential create them if
> they do not
> >exist based on a template.
> >The Junit testclass -> class relationship is just one
> application of this
> >generic principle for the junit framework.
_______________________________________________
Eap-features mailing list
[EMAIL PROTECTED]
http://www.intellij.com/mailman/listinfo/eap-features
