Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 362722 - Schema generation doesn't actually create the file named in the arguments.
Summary: Schema generation doesn't actually create the file named in the arguments.
Status: RESOLVED WORKSFORME
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-02 16:54 EDT by Paul Fullbright CLA
Modified: 2022-06-09 10:10 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 Paul Fullbright CLA 2011-11-02 16:54:12 EDT 
Whether or not the name of the file is specified in the arguments, moxy generates its own file name based on the namespace.  Even then, it won't overwrite the file if it exists, it generates a new name.

This causes problems in Dali, because we can't do anything with the schema post-generate.  It also makes the process of regeneration cumbersome, because the user ends up with multiple similarly (incorrectly) named schemas all in the same place.
Comment 1 Paul Fullbright CLA 2012-02-23 21:35:46 EST 
I'm not sure what didn't work before, but I'm getting what I *think* should be the correct behavior.

Closing.
Comment 2 Eclipse Webmaster CLA 2022-06-09 10:10:47 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink