[jira] Created: (XFIRE-1040) Using an xfire client with ws-security in a servlet within glassfish causes "NamespaceURI cannot be null"

View: New views
3 Messages — Rating Filter:   Alert me  

[jira] Created: (XFIRE-1040) Using an xfire client with ws-security in a servlet within glassfish causes "NamespaceURI cannot be null"

by JIRA jira@codehaus.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Using an xfire client with ws-security in a servlet within glassfish causes "NamespaceURI cannot be null"
---------------------------------------------------------------------------------------------------------

                 Key: XFIRE-1040
                 URL: http://jira.codehaus.org/browse/XFIRE-1040
             Project: XFire
          Issue Type: Bug
          Components: WS-Security
    Affects Versions: 1.2.6
         Environment: Glassfish V2 Beta 2
Ubuntu Feisty Fawn 7.04
xfire-spring
xfire-ws-security

            Reporter: Michael Lake
            Assignee: Dan Diephouse
         Attachments: xfire_bug.tar.gz

Steps to reproduce:

tar xvzf xfire_bug.tar.gz
cd xfire_bug
mvn clean compile package install
cd token-server
mvn jetty:run  #(this will start up on port 8092)

______Steps to run the client in a seperate jetty server to verify it works properly_______
(in a new console)
cd xfire_bug/token-servlet
mvn jetty:run  #(this will start up on port 8080)
firefox http://localhost:8080/token-servlet/app

Push the button on the web-page and you should show a message in all caps that says "HELLO WORLD"

____Steps to produce error on Glassfish V2 Beta 2____ (make sure the jetty server for "token-servlet" is shutdown with CTRL-C

download glassfish from here: https://glassfish.dev.java.net//downloads/v2-b41d.html

cd glassfish
lib/ant/bin/ant -f setup.xml
./bin/asadmin start-domain domain1
cp ~/xfire_bug/token-servlet/target/token-servlet.war ~/glassfish/domains/domain1/autodeploy/

(let it start up)
then access http://localhost:8080/token-servlet/app
push the button to get the error: org.codehaus.xfire.fault.XFireFault: NamespaceURI cannot be null

HINT: you can turn on remote debugging via glassfish's admin console at
http://localhost:4848/
user: admin
password: adminadmin



--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email


[jira] Commented: (XFIRE-1040) Using an xfire client with ws-security in a servlet within glassfish causes "NamespaceURI cannot be null"

by JIRA jira@codehaus.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


    [ http://jira.codehaus.org/browse/XFIRE-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=193557#action_193557 ]

ricky martin commented on XFIRE-1040:
-------------------------------------

I faced this problem today. I realized that the problem is Glassfish uses sjsxp (https://sjsxp.dev.java.net/) as XML streaming parser implementation and xfire is bundled with woodstox one (wstx-asl). I think some namespace check in sjsxp is causing the exception.

To workaround this issue the woodstox parser can be specified to glassfish. Just add this java properties to the instance:

-Djavax.xml.stream.XMLEventFactory=com.ctc.wstx.stax.WstxEventFactory
-Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory
-Djavax.xml.stream.XMLOutputFactory=com.ctc.wstx.stax.WstxOutputFactory

In my opinion this issue should be renamed to something like:
Using an xfire client with ws-security and sjsxp parser causes "NamespaceURI cannot be null"

Hope it helps somebody.

> Using an xfire client with ws-security in a servlet within glassfish causes "NamespaceURI cannot be null"
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: XFIRE-1040
>                 URL: http://jira.codehaus.org/browse/XFIRE-1040
>             Project: XFire
>          Issue Type: Bug
>          Components: WS-Security
>    Affects Versions: 1.2.6
>         Environment: Glassfish V2 Beta 2
> Ubuntu Feisty Fawn 7.04
> xfire-spring
> xfire-ws-security
>            Reporter: Michael Lake
>            Assignee: Dan Diephouse
>         Attachments: xfire_bug.tar.gz
>
>
> Steps to reproduce:
> tar xvzf xfire_bug.tar.gz
> cd xfire_bug
> mvn clean compile package install
> cd token-server
> mvn jetty:run  #(this will start up on port 8092)
> ______Steps to run the client in a seperate jetty server to verify it works properly_______
> (in a new console)
> cd xfire_bug/token-servlet
> mvn jetty:run  #(this will start up on port 8080)
> firefox http://localhost:8080/token-servlet/app
> Push the button on the web-page and you should show a message in all caps that says "HELLO WORLD"
> ____Steps to produce error on Glassfish V2 Beta 2____ (make sure the jetty server for "token-servlet" is shutdown with CTRL-C
> download glassfish from here: https://glassfish.dev.java.net//downloads/v2-b41d.html
> cd glassfish
> lib/ant/bin/ant -f setup.xml
> ./bin/asadmin start-domain domain1
> cp ~/xfire_bug/token-servlet/target/token-servlet.war ~/glassfish/domains/domain1/autodeploy/
> (let it start up)
> then access http://localhost:8080/token-servlet/app
> push the button to get the error: org.codehaus.xfire.fault.XFireFault: NamespaceURI cannot be null
> HINT: you can turn on remote debugging via glassfish's admin console at
> http://localhost:4848/
> user: admin
> password: adminadmin

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



[jira] Commented: (XFIRE-1040) Using an xfire client with ws-security in a servlet within glassfish causes "NamespaceURI cannot be null"

by JIRA jira@codehaus.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


    [ http://jira.codehaus.org/browse/XFIRE-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=193557#action_193557 ]

ricky martin commented on XFIRE-1040:
-------------------------------------

I faced this problem today. I realized that the problem is Glassfish uses sjsxp (https://sjsxp.dev.java.net/) as XML streaming parser implementation and xfire is bundled with woodstox one (wstx-asl). I think some namespace check in sjsxp is causing the exception.

To workaround this issue the woodstox parser can be specified to glassfish. Just add this java properties to the instance:

-Djavax.xml.stream.XMLEventFactory=com.ctc.wstx.stax.WstxEventFactory
-Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory
-Djavax.xml.stream.XMLOutputFactory=com.ctc.wstx.stax.WstxOutputFactory

In my opinion this issue should be renamed to something like:
Using an xfire client with ws-security and sjsxp parser causes "NamespaceURI cannot be null"

Hope it helps somebody.

> Using an xfire client with ws-security in a servlet within glassfish causes "NamespaceURI cannot be null"
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: XFIRE-1040
>                 URL: http://jira.codehaus.org/browse/XFIRE-1040
>             Project: XFire
>          Issue Type: Bug
>          Components: WS-Security
>    Affects Versions: 1.2.6
>         Environment: Glassfish V2 Beta 2
> Ubuntu Feisty Fawn 7.04
> xfire-spring
> xfire-ws-security
>            Reporter: Michael Lake
>            Assignee: Dan Diephouse
>         Attachments: xfire_bug.tar.gz
>
>
> Steps to reproduce:
> tar xvzf xfire_bug.tar.gz
> cd xfire_bug
> mvn clean compile package install
> cd token-server
> mvn jetty:run  #(this will start up on port 8092)
> ______Steps to run the client in a seperate jetty server to verify it works properly_______
> (in a new console)
> cd xfire_bug/token-servlet
> mvn jetty:run  #(this will start up on port 8080)
> firefox http://localhost:8080/token-servlet/app
> Push the button on the web-page and you should show a message in all caps that says "HELLO WORLD"
> ____Steps to produce error on Glassfish V2 Beta 2____ (make sure the jetty server for "token-servlet" is shutdown with CTRL-C
> download glassfish from here: https://glassfish.dev.java.net//downloads/v2-b41d.html
> cd glassfish
> lib/ant/bin/ant -f setup.xml
> ./bin/asadmin start-domain domain1
> cp ~/xfire_bug/token-servlet/target/token-servlet.war ~/glassfish/domains/domain1/autodeploy/
> (let it start up)
> then access http://localhost:8080/token-servlet/app
> push the button to get the error: org.codehaus.xfire.fault.XFireFault: NamespaceURI cannot be null
> HINT: you can turn on remote debugging via glassfish's admin console at
> http://localhost:4848/
> user: admin
> password: adminadmin

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email