Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 325877

Summary:	Implementation Defaults to User Library , preventing Finish from first page
Product:	[WebTools] Dali JPA Tools	Reporter:	Zina Mostafia <zina>
Component:	General	Assignee:	Neil Hauge <neil.hauge>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	neil.hauge, paul.fullbright, shaun.smith
Version:	2.3.1
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Zina Mostafia

2010-09-21 12:48:56 EDT

Build Identifier: 3.6

When creating a project with a JPA facet, the 'JPA Facet' panel appears at the end. There is a red error mark because there are no configured JPA libraries for it to use. If the default for this page were to 'Disable Library Configuration' then there wouldn't be a red error, and Finish could be pressed much earlier on in the wizard (taking the subsequent defaults). 

Reproducible: Always

Comment 1 Zina Mostafia

2010-11-01 11:26:29 EDT

Any update on this defect ?

Comment 2 Neil Hauge

2010-11-01 14:55:01 EDT

I think this would be a desirable thing to do if we were able to determine that the selected Target Runtime already contained the necessary libraries.  I think that is the issue in this case, that we would not be able to accurately make this determination in all cases.  That said, we will investigate and determine if this can be done in at least some cases.

Comment 3 Neil Hauge

2011-05-11 16:40:10 EDT

Upon further review we have determined that the current behavior is preferred.  Our thought is that the user should have to see this warning message at least once.  After initial selection the disabled library config will become the default selection and the user would be able to click Finish from the first page of the wizard on subsequent wizard runs.

Another option to avoid this scenario would be to provide your own disabled library provider (named whatever you would prefer) and set this as the highest priority library provider.  This way an adopter who always wanted to default to a particular library provider could do so.

Please reopen if you have any questions or would like to pursue a different solution.