You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "Bryant Luk (JIRA)" <ji...@apache.org> on 2009/07/01 02:20:47 UTC

[jira] Created: (WINK-23) Change JAXBElement test for namespace attribute reordering

Change JAXBElement test for namespace attribute reordering
----------------------------------------------------------

                 Key: WINK-23
                 URL: https://issues.apache.org/jira/browse/WINK-23
             Project: Wink
          Issue Type: Test
            Reporter: Bryant Luk
            Assignee: Bryant Luk
            Priority: Minor


On some JDKs, the ordering of attributes within the XML elements is different than the expected content string but the test should still pass.

This is one of the failures that Mike ran into I believe so I'll fix it with this JIRA.

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


[jira] Updated: (WINK-23) Change JAXBElement test for namespace attribute reordering

Posted by "Bryant Luk (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WINK-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryant Luk updated WINK-23:
---------------------------

          Component/s: Server
    Affects Version/s: 0.1
        Fix Version/s: 0.1

> Change JAXBElement test for namespace attribute reordering
> ----------------------------------------------------------
>
>                 Key: WINK-23
>                 URL: https://issues.apache.org/jira/browse/WINK-23
>             Project: Wink
>          Issue Type: Test
>          Components: Server
>    Affects Versions: 0.1
>            Reporter: Bryant Luk
>            Assignee: Bryant Luk
>            Priority: Minor
>             Fix For: 0.1
>
>
> On some JDKs, the ordering of attributes within the XML elements is different than the expected content string but the test should still pass.
> This is one of the failures that Mike ran into I believe so I'll fix it with this JIRA.

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


[jira] Resolved: (WINK-23) Change JAXBElement test for namespace attribute reordering

Posted by "Bryant Luk (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WINK-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryant Luk resolved WINK-23.
----------------------------

    Resolution: Fixed

Should be fixed in 790008 I think.

> Change JAXBElement test for namespace attribute reordering
> ----------------------------------------------------------
>
>                 Key: WINK-23
>                 URL: https://issues.apache.org/jira/browse/WINK-23
>             Project: Wink
>          Issue Type: Test
>            Reporter: Bryant Luk
>            Assignee: Bryant Luk
>            Priority: Minor
>
> On some JDKs, the ordering of attributes within the XML elements is different than the expected content string but the test should still pass.
> This is one of the failures that Mike ran into I believe so I'll fix it with this JIRA.

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


[jira] Closed: (WINK-23) Change JAXBElement test for namespace attribute reordering

Posted by "Bryant Luk (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WINK-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryant Luk closed WINK-23.
--------------------------


> Change JAXBElement test for namespace attribute reordering
> ----------------------------------------------------------
>
>                 Key: WINK-23
>                 URL: https://issues.apache.org/jira/browse/WINK-23
>             Project: Wink
>          Issue Type: Test
>            Reporter: Bryant Luk
>            Assignee: Bryant Luk
>            Priority: Minor
>
> On some JDKs, the ordering of attributes within the XML elements is different than the expected content string but the test should still pass.
> This is one of the failures that Mike ran into I believe so I'll fix it with this JIRA.

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