Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JAXB adaptation #4

Open
WitchsCat opened this issue Nov 12, 2012 · 2 comments
Open

JAXB adaptation #4

WitchsCat opened this issue Nov 12, 2012 · 2 comments
Assignees

Comments

@WitchsCat
Copy link
Owner

We have to introduce special handling for JAXB-generated classes. Since the structure of JAXB based classes is to complicated, we have to introduce a simplification mechanism for this case. On top of that we have to introduce an additional mechanism for mapping the results from UI back to the model

@ghost ghost assigned BrownFurSeal Nov 12, 2012
@BrownFurSeal
Copy link
Collaborator

Cannot find JAXB at all. Did you mean XStream serializer? Not sure about "Since the structure of JAXB based classes is to complicated" - if you meant XStream, it uses classes from classpath.
Regarding to mapping from UI to model - there is a method ModelViewController#applyChanges. Do you want to enhance it? It doesn't produce IllegalArgumentException or something else so far when I enter letters for Integer field. I'll see what's the problem.

@WitchsCat
Copy link
Owner Author

I mean if you use WSDL2Java you get gava classes that istead of fileds have something like JAXBElement
this is the most common stuff that you get when generating for webservices. I can add a couple of examples tommorow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants