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

Bug 341429

Summary:	Enhance mechanism to specify extensions
Product:	z_Archived	Reporter:	Mitesh Meswani <mitesh.meswani>
Component:	Eclipselink	Assignee:	Nobody - feel free to take it <nobody>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P4	CC:	martin.grebac, tom.ware
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
URL:	http://wiki.eclipse.org/EclipseLink/DesignDocs/340192
Whiteboard:
Bug Depends on:	340192
Bug Blocks:

Description Mitesh Meswani

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

2011-03-31 08:53:52 EDT

Added to requirements for Flex Column feature

Comment 2 Tom Ware

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

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

2022-06-09 10:18:53 EDT

The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink