[#CASTOR-1829] CollectionInfo.createRemoveByIndexMethod() creates illegal code if there's a class generated of type 'Object' from an XML schema artefact - jira.codehaus.org

Details

Type: Bug
Status: Closed
Priority: Blocker
Resolution: Fixed
Affects Version/s: 1.1 M1, 1.1 M2
Fix Version/s: 1.1 M3
Component/s: XML code generator
Labels:
None

Number of attachments :
1

Description

Basically, the code generated for the remove<Entity>At method should read

java.lang.Object obj = ...

instead of ...

Object obj = ...

More Options
- Sort By Name
- Sort By Date
- Ascending
- Descending
- Download All

Attachments

patch.c1829.20070112.txt

12/Jan/07 3:44 PM

0.6 kB

Werner Guttmann

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Werner Guttmann added a comment - 12/Jan/07 3:44 PM

Final patch for review.

Show

Werner Guttmann added a comment - 12/Jan/07 3:44 PM Final patch for review.

Hide

Permalink

Edward Kuns added a comment - 12/Jan/07 3:53 PM

Good catch. Yes, we need to fully qualify all class references in generated code (except for the rare reference to other generated code that we catch via import).

Show

Edward Kuns added a comment - 12/Jan/07 3:53 PM Good catch. Yes, we need to fully qualify all class references in generated code (except for the rare reference to other generated code that we catch via import). +1

People

Assignee:

Werner Guttmann

Reporter:

Werner Guttmann

Vote (0)

Watch (0)

Dates

Created:

12/Jan/07 3:12 PM

Updated:

20/Apr/07 10:23 AM

Resolved:

12/Jan/07 4:26 PM

Time Tracking

Estimated:

15m

Remaining:

Logged:

15m

castor

CollectionInfo.createRemoveByIndexMethod() creates illegal code if there's a class generated of type 'Object' from an XML schema artefact