This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 341429 - Enhance mechanism to specify extensions
Summary: Enhance mechanism to specify extensions
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P4 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL: http://wiki.eclipse.org/EclipseLink/D...
Whiteboard:
Keywords:
Depends on: 340192
Blocks:
  Show dependency tree
 
Reported: 2011-03-30 18:00 EDT by Mitesh Meswani CLA
Modified: 2022-06-09 10:18 EDT (History)
2 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 Mitesh Meswani CLA 2011-03-30 18:00:11 EDT 
The current mechanism to specify extension is to use equivalent of following code

ExtensionManager extMgr = serverSession.getDescriptor(entityClass).getExtensionManager();
extMgr.addExtension(fieldName,...); 

As you can see, a descriptor for given entity is required to add extension. Getting to descriptor results in deploy(). It would be nice to have a mechanism that does not trigger deploy. Filling this as a tracking RFE as per discussion with Doug.
Comment 1 Tom Ware CLA 2011-03-31 08:53:52 EDT 
Added to requirements for Flex Column feature
Comment 2 Tom Ware CLA 2011-03-31 13:53:35 EDT 
We will need to discuss what happens if a non-connected session has an extension added that already exists and is simply not visible because we have not connected yet.
Comment 3 Tom Ware CLA 2011-03-31 13:54:38 EDT 
How does the non-connected use case work?  i.e. how would the user add extensions in this case?
Comment 4 Eclipse Webmaster CLA 2022-06-09 10:18:53 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink