Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 133415 - [api] Some APIs provided by J2EEProjectUtilities should be made public
Summary: [api] Some APIs provided by J2EEProjectUtilities should be made public
Status: CLOSED FIXED
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 1.5   Edit
Hardware: PC Windows 2000
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Chuck Bridgham CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-27 14:35 EST by Leho Nigul CLA
Modified: 2010-02-16 18:10 EST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Leho Nigul CLA 2006-03-27 14:35:40 EST 
In our code we use "is" methods of J2EEProjectUtilities to determine the type of specific project (DynamicWebProject, EJB project, etc). Since this is a rather common operation we believe that that functionality should be supported by external API.
Comment 1 Matt Marum CLA 2006-04-13 13:06:38 EDT 
We'd like to see J2EEProjectUtilities made a public API as well.  We use the same "is" methods described above.
Comment 2 Michael D. Elder CLA 2006-06-07 17:25:25 EDT 
The proper path for API finalization should refactor any methods out of J2EEProjectUtilities and into another class with well defined dependencies that doesn't pull along alot of other plugins, as J2EEProjectUtilities can do.
Comment 3 Chris Chiu CLA 2006-11-16 17:58:39 EST 
We would like to use isDynamicWebProject and isProjectOfType as well.  We have our own custom facet for a web project.  These methods allow us to quickly verify the project contains our prerequisites.
Comment 4 Carl Anderson CLA 2010-02-16 18:10:06 EST 
Use JavaEEProjectUtilities.  It is public API.