Community
Participate
Working Groups
Currently it isn't possible to create a JAXB 2.2 project due to facet library validation. Disabling the library validation doesn't help. Oddly, if you create a JAXB 2.1 project, you are then able to create a JAXB 2.2 project. Also, the library validation messages still say JPA.
I don't get this behavior. I'm able to create a JAXB project with even no library selected. In fact, I don't even believe that JAXB libraries are hooked up to library validators. Any further info on this?
I think you need to reproduce in a clean workspace. If other JAXB projects exist or have existed then you won't see the problem. One workaround I have found is to go back one wizard page from the JAXB Facet page and then go forward again. At this point the Finish button becomes enabled.
Considering the extreme situation required to reproduce this and the easy workaround, I have a hard time giving this a "major".
(In reply to comment #3) > Considering the extreme situation required to reproduce this and the easy > workaround, I have a hard time giving this a "major". Consider the situation: -User wants to try new JAXB functionality -User tries to create JAXB project using default selections (2.2 facet, Generic 2.2 platform) -User sees error message indicating a user library needs to be selected, Finish button is disabled -User configures and selects appropriate user library but message does not go away, Finish button still disabled -User Disables Library Configuration, but message does not go away, Finish button still disabled -User cancels wizard and tries again with the same result -User assumes that a JAXB project cannot be created Workspace doesn't have to be completely clean, just no existing or previously existing JAXB faceted projects.
I'm going to just add this to this bug, since it's somewhat related. If you choose to 'Disable Library Configuration' for the JAXB project, you see a message below it that says 'The JPA facet requires a JPA...', this needs to be changed for JAXB.
Committed changes (along with props/prefs reorg) for M4
Fixed Disable Library Configuration message for JAXB projects mentioned in comment 0 and comment 5. (for M5)
Verified you can create JAXB 2.1 and JAXB 2.2 projects and that that library configuration gave the correct messages for JAXB verses JPA. To see manual test steps go to - http://wiki.eclipse.org/Dali_4.0_M4 Automated Test Suites are being created as well go to http://wiki.eclipse.org/Dali_Automated_Smoke_Test Verified in Stable Build: S-3.3.0M5-20110127064115
