[ADFEMG-104] Save JDeveloper application workings sets in the application workspace Created: 02/Feb/13  Updated: 07/Jul/14  Resolved: 07/Jul/14

Status: Closed
Project: adfemg
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Minor
Reporter: Torsten Kleiber Assignee: Unassigned
Resolution: Incomplete Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Save JDeveloper application workings sets in the application workspace


If you create for an example a big adf application you may want to add all of your entities to one base application for reuse labels, validation and and so on. If you have a big database schema than in short time you have a problem to find your entity.

In JDeveloper there is a neat feature to overcome this problem: working sets! With this you can easily group your entities or other artefacts in logical working set, eg. for a sub application. Unfortunatly working sets are saved per user. There are several description how to share this between your team members. But a better way would to distinct between user and application working sets. Application working set should be saved consequently in the application workspace (jws).

Therefore I have created enhancent request bug 15841657 : SAVE APPLICATION WORKING SETS IN THE APPLICATION WORKSPACE JWS. This er is public viewable.

See http://develishdevelopment.wordpress.com/2012/12/04/save-jdeveloper-application-workings-sets-in-the-application-workspace-please-vote-for-this-enhancement-request/

Comment by Jan Vervecken [ 07/Feb/13 ]

hi tkleiber

Just wanted to confirm that I have been able to find enhancement request 15841657, "SAVE APPLICATION WORKING SETS IN THE APPLICATION WORKSPACE JWS", on My Oracle Support.

Although I don't have much experience with Working Sets myself, it seems to be a reasonable enhancement request.

Jan Vervecken

Comment by chriscmuir [ 15/Jul/13 ]

Scheduled for fix in


Comment by chriscmuir [ 07/Jul/14 ]

So I don't have to keep on tracking this issue, I'm going to close it, and leave development to prioritize the ER as per their own guidelines.


Generated at Tue Feb 21 04:00:45 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.