[RIVER-116] Multiple jar files with conflicting lists need facilities to map the chosen preferred value

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: jtsk_2.1
• Fix Version/s: River_2.1.2
• Component/s: com_sun_jini_tool
• Bugtraq ID: 6353590
• Assignee: Mark Brouwer
• Reporter: Ronald Mann
• Created: 27/Jul/07 18:41
• Updated: 06/Jan/10 06:03
• Resolved: 15/Mar/08 12:08

Description

Bugtraq Id 6353590
Submitted by Mark Brouwer:
"In case you wrap 2 or more JAR files and the preferred list for these files result in a preferences conflict an IOException is thrown. I would
like to have a facility to provide a map of classes (namespaces?) with their associated preferred value that will be the authority to decide
what the desired value for a class must be and that wrapping will continue.

The use case is that Seven adds code to the service proxy and the download JAR files for the container added code contains a preferred
list that might conflict with that of the JSC Service download JAR file. It is possible that from the perspective of the JSC Service proxy a
class is an implementation detail but from the perspective of the container is API. Currently this results in a preferences conflict when
JAR wrapping.

I don't want a JSC Service developer to have knowledge of the implementation details of a JSC compliant container and to take that
knowledge into account when they create their download JAR files."

Issue Links

• duplicates: RIVER-115 Multiple jar files with conflicting lists need facilities to map the chosen preferred value