Book a Demo

Author Topic: Java Code Engineering and Javadoc  (Read 5238 times)

stepheny

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
  • I love YaBB 1 Gold!
    • View Profile
Java Code Engineering and Javadoc
« on: February 16, 2002, 01:35:20 pm »
Hi

 Just notice one thing on the Code Engineering. When EA try to reservse engineering a java source file, the following code will not be able to pick up the throw exception part:

Code: [Select]

public foo()
 throws FooException {
}


 Also right now EA use "Tag" to record what kind of exception can be thrown in each method. Could it be possible to make the input screen more intergrated? Like a simliar screen for inputting the parameter. If there is a dropdown for all the available Exception or any Throwable classes than it will be much better :)

 Another feature I would like is the generation of the Javadoc comment. We just need to define the parameter and the Exception it throw and it will generate the Javadoc comment. plus some additional input box so that you can input @see, @author, @version, @depecate.... etc.

 Also if we can also import .jar file or .class file, it will be great

-Stephen Yau

Anibal Rojas

  • EA Novice
  • *
  • Posts: 12
  • Karma: +0/-0
  • I love YaBB 1 Gold!
    • View Profile
Re: Java Code Engineering and Javadoc
« Reply #1 on: February 20, 2002, 08:40:24 am »
I would appreciate the Javadoc comment feature.
____________________
Aníbal Rojas
[email protected]

gsparks

  • EA User
  • **
  • Posts: 325
  • Karma: +0/-0
  • I love YaBB 1 Gold!
    • View Profile
Re: Java Code Engineering and Javadoc
« Reply #2 on: February 21, 2002, 01:58:29 am »
Hi,

I will check out the bug asap.

We will also try and look at the Javadoc possibility in the next few weeks - it is a popular request and one that should not be too difficult to accomodate.

As regards the layout of the operations etc - I agree that some streamlininig is in order here - too often you have to flip backwards and forwards between tabs. I will see what can be done to improve this area.

Geoff Sparks