[jboss-jira] [JBoss JIRA] (WFLY-4085) XML Marshalling problems without -jaxpmodule on start scrtipts.

[victor frança (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

victor frança updated WFLY-4085:
--------------------------------
    Description: 
I was using a fresh installation of wildfly 8.1.0.final and i faced a very weird situation with a SLSB of mines that uses javax.xml.bind.Marshaller for marshalling an object.
The result of the marshalling process was an incomplete XML. I was sure that there was no problems with the application itself because i could run the code with a main method and get the complete marshalled XML.
Also, i noticed that i could get the right results if I start the Wildfly through my Eclipse Luna.
So, i realized that the problem just comes up if i start directly via standalone.sh.
Then i decided to compare standalone.sh and eclipse's configurations for wildfly initialization.
The answer for the entire problem was that eclipse still adds the parameter -jaxpmodule that it is not present on standalone.sh with wildfly 8.1.0.final.
I found another issue about this parameter removing here WFLY-425.
Well, i could make things works just adding this parameter back to wildfly standalone.sh. But, i have a feeling that something has to be done to make JAXB works without this parameter that was removed.

Best regards!

  was:
I was using a fresh installation of wildfly 8.1.0.final and i faced a very weird situation with a SLSB of mines that uses javax.xml.bind.Marshaller for marshalling an object.
The result of the marshalling process was an incomplete XML. I was sure that there was no problems with the application itself because i could run the code with a main method and get the complete marshalled XML.
Also, i noticed that i could get the right results if I start the Wildfly through my Eclipse Luna.
So, i realized that the problem just comes up if i start directly via standalone.sh.
Then i decided to compare standalone.sh and eclipse's configurations for wildfly initialization.
The answer for the entire problem was that eclipse still adds the parameter -jaxpmodule that it is not present on standalone.sh with wildfly 8.1.0.final.
A found another issue about this parameter removing here WFLY-425.
Well, i could make things works just adding this parameter back to wildfly standalone.sh. But, i have a feeling that something has to be done to make JAXB works without this parameter that was removed.

Best regards!



> XML Marshalling problems without -jaxpmodule on start scrtipts.
> ---------------------------------------------------------------
>
>                 Key: WFLY-4085
>                 URL: https://issues.jboss.org/browse/WFLY-4085
>             Project: WildFly
>          Issue Type: Quality Risk
>          Components: XML Frameworks
>    Affects Versions: 8.1.0.Final
>            Reporter: victor frança
>            Assignee: Jason Greene
>              Labels: jaxb, jaxpmodule, marshalling, xml
>
> I was using a fresh installation of wildfly 8.1.0.final and i faced a very weird situation with a SLSB of mines that uses javax.xml.bind.Marshaller for marshalling an object.
> The result of the marshalling process was an incomplete XML. I was sure that there was no problems with the application itself because i could run the code with a main method and get the complete marshalled XML.
> Also, i noticed that i could get the right results if I start the Wildfly through my Eclipse Luna.
> So, i realized that the problem just comes up if i start directly via standalone.sh.
> Then i decided to compare standalone.sh and eclipse's configurations for wildfly initialization.
> The answer for the entire problem was that eclipse still adds the parameter -jaxpmodule that it is not present on standalone.sh with wildfly 8.1.0.final.
> I found another issue about this parameter removing here WFLY-425.
> Well, i could make things works just adding this parameter back to wildfly standalone.sh. But, i have a feeling that something has to be done to make JAXB works without this parameter that was removed.
> Best regards!



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)