The following comment has been added to this issue:
Author: Andrew Stevens
Created: Tue, 3 Jun 2003 1:43 AM
Body:
Can you upload an example of how the "CMPs break under Windows"? I don't have any
problem with them...
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/xdoclet/secure/ViewIssue.jspa?key=XDT-464
Here is an overview of the issue:
---------------------------------------------------------------------
Key: XDT-464
Summary: XDoclet 1.2 beta 3 qualifies as yet generated classes differently per OS
platform (OSX, Windows, Linux)
Type: Bug
Status: Assigned
Priority: Major
Time Spent: Unknown
Estimate: 0 minutes
Project: XDoclet
Components:
EJB Module
Versions:
1.2 Beta 3
Assignee: xdoclet-devel (Use for new issues)
Reporter: Weston M. Price
Created: Wed, 30 Apr 2003 5:41 PM
Updated: Wed, 30 Apr 2003 5:41 PM
Environment: Mac OS X 10.2.5, Powerbook G4, 1GB memory
Windows 2000, Dell 768 GB Memory
Linux SuSe 8.1
Description:
When using XDoclet to generate CMP Entity Beans classes that are referenced within
the CMP but that are generated by XDoclet, ie ValueObject, PrimaryKeys etc. different
behavior exists between MacOSX and Linux/Windows.
The following import statement refers to a package that is created with package
substitution. All interfaces generated by XDoclet (remote and local) are placed into
this package as well as the result of the valueobject and entity-pk subtasks.
import com.xxx.yyy.interfaces.*;
On OSX, the source generation qualifies the generated Value Objects and PK's as
belonging to the orignal package prior to the substitution (in this case ejb). As a
result, compilation fails due to the incorrect reference. However, if the fully
qualified name of each class is used the generation-->compilation proceeds
successfully.
On Windows and Linux the process is exactly the opposite. Fully qualifed class names
to ValueObjects and PK's result in the incorrect source being generated, and as a
result, the compilation fails.
To say the least, this behavior is inconsistent and confusing. It would seem that
the behavior should be consistent regardless of platform. Further, this behavior
persists regardless of the order in which the XDoclet sub tasks are performed.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/xdoclet/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
