You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jarek Gawor (JIRA)" <ji...@apache.org> on 2007/01/15 16:41:27 UTC

[jira] Created: (GERONIMO-2733) JAXR tests

JAXR tests
----------

                 Key: GERONIMO-2733
                 URL: https://issues.apache.org/jira/browse/GERONIMO-2733
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: webservices
            Reporter: Jarek Gawor
             Fix For: 2.0-M2


The existing JAXR support appears to be broken. For example, any EJB or web application failed with (when using JAXR api):

Caused by: javax.xml.registry.JAXRException: Unable to load JAXR ConnectionFacto
ryClass: org.apache.ws.scout.registry.ConnectionFactoryImpl
        at javax.xml.registry.ConnectionFactory.newInstance(ConnectionFactory.ja
va:53)
        at org.apache.geronimo.test.JAXRTest.<init>(JAXRTest.java:31)
        at org.apache.geronimo.test.JAXRServlet.doGet(JAXRServlet.java:41)
        ... 23 more
Caused by: java.lang.ClassNotFoundException: org.apache.ws.scout.registry.Connec
tionFactoryImpl in classloader JEE5/JAXRServlet/1.1/car
        at org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(Mu
ltiParentClassLoader.java:303)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        at javax.xml.registry.ConnectionFactory.newInstance(ConnectionFactory.ja
va:50)
        ... 25 more


The following patch fixes this problem and contains basic tests to ensure that JAXR API can be used within any EJB or web application (and that the right implementation is used).


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

        

[jira] Updated: (GERONIMO-2733) JAXR tests

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

Jarek Gawor updated GERONIMO-2733:
----------------------------------

    Attachment: jaxr.patch

> JAXR tests
> ----------
>
>                 Key: GERONIMO-2733
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2733
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: webservices
>            Reporter: Jarek Gawor
>             Fix For: 2.0-M2
>
>         Attachments: jaxr.patch
>
>
> The existing JAXR support appears to be broken. For example, any EJB or web application failed with (when using JAXR api):
> Caused by: javax.xml.registry.JAXRException: Unable to load JAXR ConnectionFacto
> ryClass: org.apache.ws.scout.registry.ConnectionFactoryImpl
>         at javax.xml.registry.ConnectionFactory.newInstance(ConnectionFactory.ja
> va:53)
>         at org.apache.geronimo.test.JAXRTest.<init>(JAXRTest.java:31)
>         at org.apache.geronimo.test.JAXRServlet.doGet(JAXRServlet.java:41)
>         ... 23 more
> Caused by: java.lang.ClassNotFoundException: org.apache.ws.scout.registry.Connec
> tionFactoryImpl in classloader JEE5/JAXRServlet/1.1/car
>         at org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(Mu
> ltiParentClassLoader.java:303)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at javax.xml.registry.ConnectionFactory.newInstance(ConnectionFactory.ja
> va:50)
>         ... 25 more
> The following patch fixes this problem and contains basic tests to ensure that JAXR API can be used within any EJB or web application (and that the right implementation is used).

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

        

[jira] Closed: (GERONIMO-2733) JAXR tests

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

David Jencks closed GERONIMO-2733.
----------------------------------

    Resolution: Fixed
      Assignee: David Jencks

Applied in rev 496565, many thanks!

> JAXR tests
> ----------
>
>                 Key: GERONIMO-2733
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2733
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: webservices
>            Reporter: Jarek Gawor
>         Assigned To: David Jencks
>             Fix For: 2.0-M2
>
>         Attachments: jaxr.patch
>
>
> The existing JAXR support appears to be broken. For example, any EJB or web application failed with (when using JAXR api):
> Caused by: javax.xml.registry.JAXRException: Unable to load JAXR ConnectionFacto
> ryClass: org.apache.ws.scout.registry.ConnectionFactoryImpl
>         at javax.xml.registry.ConnectionFactory.newInstance(ConnectionFactory.ja
> va:53)
>         at org.apache.geronimo.test.JAXRTest.<init>(JAXRTest.java:31)
>         at org.apache.geronimo.test.JAXRServlet.doGet(JAXRServlet.java:41)
>         ... 23 more
> Caused by: java.lang.ClassNotFoundException: org.apache.ws.scout.registry.Connec
> tionFactoryImpl in classloader JEE5/JAXRServlet/1.1/car
>         at org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(Mu
> ltiParentClassLoader.java:303)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at javax.xml.registry.ConnectionFactory.newInstance(ConnectionFactory.ja
> va:50)
>         ... 25 more
> The following patch fixes this problem and contains basic tests to ensure that JAXR API can be used within any EJB or web application (and that the right implementation is used).

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