Re: [dali-dev] Dependency between getDefaultDiscoverAnnotatedClasses and

[Neil Hauge <neil.hauge@xxxxxxxxxx>]

We are just trying to set a default value in the project creation wizard, based on whether there is a target application server, and whether that app server states support for EJB 3.0.  If it does, we default to class discovery, as this is a spec based feature that all EJB 3.0 containers would provide.  The user can still change the default value to require class listing, but in general most people tend to use the auto discovery that is provided by their application server.

All of that said, we recently introduced a product customization setting that you could try out if you like.  It adds the ability for adopters to override this default logic.  See this bug for more info:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=387586

It would be great if you tested this out from the product adopter side so we could tweak as needed before the release.

Neil

On 12/11/2012 9:19 AM, Kazakov, Peter wrote:

Dear all,

 

We investigated a problem that whenever runtime supports jst.ejb facet and we add JPA facet in the configuration, default option in the wizard is changed from “Annotated classes must be listed … ” to “Discover annotated classes automatically”.

For us this is undesired behavior.

It turns out that this behavior is programmed in getDefaultDiscoverAnnotatedClasses function of  JpaFacetInstallDataModelProvider class.

What are the reasons to refer to runtimeSupportsEjb30() in the following code:

 

              return Boolean.valueOf((discoverAnnotatedClassesDefaultPreference == null) ?

                           this.runtimeSupportsEjb30() : discoverAnnotatedClassesDefaultPreference.equals("true")); //$NON-NLS-1$

 

This introduces dependency between the Dynamic Web project that we create and the EJB facet that is hardcoded.

 

Kind regards,
Peter

_______________________________________________
dali-dev mailing list
dali-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dali-dev