Bug 248065 - Proposed Improvement: ExpressionOperator should have an interface
Summary: Proposed Improvement: ExpressionOperator should have an interface
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-21 11:19 EDT by Markus KARG CLA
Modified: 2022-06-09 10:04 EDT (History)
1 user (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 Markus KARG CLA 2008-09-21 11:19:42 EDT 
Sometimes when implementing database platforms one needs very special behaviour of an ExpressionOperator -- behaviour beyond what the current implementation can provide. In that rare case it makes sense to provide a different implementation of ExpressionOperator. Unfortunately, at the moment ExpressionOperator does not implement any interface, so it is more or less unclear what methods must be overrideen, and what methods can be ignored.

It would make sense to have ExpressionOperator refactored in a way that makes it implement some "clean" interface: So another implementation could be provided by a platform without taking care of lots of public functions that actually do not play a role.
Comment 1 Eclipse Webmaster CLA 2022-06-09 10:04:11 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink