Uploaded image for project: 'JBoss Web Services'
  1. JBoss Web Services
  2. JBWS-222

Is JBossEntityResolver being used in ServiceDeployerJSE?

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • jboss-ws4ee-4.0.3
    • jboss-ws4ee-4.0.1
    • jbossws-native
    • None

      A customer (case 4050) claims that behind a firewall, his webservice does not deploy properly. The reason is that the SAX parser is not able to obtain the web.xml dtd from the Sun site. The JBossEntityResolver should have kicked in.

      Code:org.jboss.webservice.ServiceDeployerJSE

      2005-05-16 08:27:00,732 ERROR [org.jboss.webservice.ServiceDeployer] Cannot startup webservice for: TPS-WS.war
      org.jboss.deployment.DeploymentException: Connection refused Nested exception: Connection refused; - nested throwable: (org.dom4j.DocumentException: Connection refused Nested exception: Connection refused)
      at org.jboss.webservice.ServiceDeployerJSE.modifyWebXML(ServiceDeployerJSE.java:142)
      at org.jboss.webservice.ServiceDeployerJSE.createWebservice(ServiceDeployerJSE.java:95)
      at org.jboss.webservice.ServiceDeployer.handleNotification(ServiceDeployer.java:109)
      at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:138)
      at $Proxy29.handleNotification(Unknown Source)
      at org.jboss.mx.util.JBossNotificationBroadcasterSupport.handleNotification(JBossNotificationBroadcasterSupport.java:112)
      at org.jboss.mx.util.JBossNotificationBroadcasterSupport.sendNotification(JBossNotificationBroadcasterSupport.java:95)
      at org.jboss.deployment.SubDeployerSupport.create(SubDeployerSupport.java:203)
      at org.jboss.web.AbstractWebContainer.create(AbstractWebContainer.java:341)
      at org.jboss.deployment.MainDeployer.create(MainDeployer.java:918)
      at org.jboss.deployment.MainDeployer.create(MainDeployer.java:910)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:774)
      .......

      at org.jboss.Main.boot(Main.java:162)
      at org.jboss.Main$1.run(Main.java:423)
      at java.lang.Thread.run(Thread.java:534)
      Caused by: org.dom4j.DocumentException: Connection refused Nested exception: Connection refused
      at org.dom4j.io.SAXReader.read(SAXReader.java:353)
      at org.dom4j.io.SAXReader.read(SAXReader.java:222)
      at org.jboss.webservice.ServiceDeployerJSE.modifyWebXML(ServiceDeployerJSE.java:119)

      The error goes away when the DOCTYPE defining the dtd in web.xml is removed. Need to test as to why the Entity resolution is not happening locally.

            tdiesler@redhat.com Thomas Diesler
            anil.saldhana Anil Saldanha (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: