Solved it by explicitly instructing JAXB to serialize the id field. Still,
seems like a weird design decision that the defaults don't process protected
setters.
@XmlElement
| private Long fooId;
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4093956#4093956
I have a SLSB with @WebService. I find that pojos have their @Id field set to
null when marshalled despite it have a value in the SLSB. In the code fragment
below you can see the field has a protected setters. When this signature is
changed to public it works as expected.
Problem is that, by
When selecting two items from selectManyListbox I get the following validation
error:
anonymous wrote : Conversion Error setting value '7 9' for
'#{workgroupSelectedStudents}'.
Evidently person with Id 7 and 9 were selected, but what is causing this
validation error? I tried overriding
Oops, meant to say Deploying this with 2.0.0.CR1, not 2.0.0.GA
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4090268#4090268
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4090268
I'm tearing my hair out over this simple thing I'd like to do: a conversation
spanning two pages. Basically I have a table in which the user can click edit
on a certain row. This will redirect the user to an edit page and the edit page
gets populated with the selected item. So far so good. Upon
Given this enumeration:
| public enum Gender {
|
| MALE (M), FEMALE (F);
|
| private String codeInDatabase;
|
| private Gender(String codeInDatabase) {
| this.codeInDatabase = codeInDatabase;
| }
|
| public String
