Valid values for muws2:State capability parsed erroneously
----------------------------------------------------------

                 Key: MUSE-300
                 URL: https://issues.apache.org/jira/browse/MUSE-300
             Project: Muse
          Issue Type: Bug
          Components: WSDM MUWS State
    Affects Versions: 2.2.0
         Environment: Issues reproduced with SVN trunk build to date.
            Reporter: Jonas Buys
            Assignee: Dan Jemiolo
            Priority: Minor


I annotated the muws2:State property in the RMD file to contain several state 
values, which I retrieve in the initializeCompleted() to construct 
SimpleStateType objects conforming that I can set in my custom capability.

I start from  <muws2:State 
xmlns:muws2="http://docs.oasis-open.org/wsdm/muws2-2.xsd";><tns:Up 
xmlns:tns="http://pats.ua.ac.be/adss/jb/mplayer";><tns:Playing/></tns:Up></muws2:State>
 (indeed, without newlines) in my RMD file used with the WSDL by wsdl2java.

The generated WebContent\WEB-INF\classes\wsdl\Jmplayer.rmd file inserts 
newlines for readability:
                <muws2:State 
xmlns:muws2="http://docs.oasis-open.org/wsdm/muws2-2.xsd";>
                    <tns:Up xmlns:tns="http://pats.ua.ac.be/adss/jb/mplayer";>
                        <tns:Playing/>
                    </tns:Up>
                </muws2:State>

The result is that the Element values retrieved by 
getWsResource().getResourceProps().getMetadata().getValidValues(MuwsConstants.STATE_QNAME)
 contain 3 child nodes under the <muws2:State> node instead of one.  The first 
child node is a text node with "\n" as value, the second is <tns:Up> and the 
third is again a text node containing a "\n" value.

Could this issue about "newline text nodes" be resolved somehow?



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to