Bugs item #669733, was opened at 2003-01-17 05:56
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=669733&group_id=22866

Category: JBossWeb
Group: v3.0 Rabbit Hole
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Laurent Etiemble (letiemble)
Assigned to: Scott M Stark (starksm)
Summary: URL Resource-ref not possible in a WebApp

Initial Comment:
URL Resource-ref cannot be declared successfully in a WebApplication.
I have the following in my web descriptor :
<web>
   ...
   <resource-ref>
      <res-ref-name>url/urlData</res-ref-name>
      <res-type>java.net.URL</res-type>
      <res-auth>Container</res-auth>
   </resource-ref>
   ...
</web>

And the following in my jboss-web descriptor :
<jboss-web>
   ...
   <resource-ref>
      <res-ref-name>url/urlData</res-ref-name>
      <jndi-name>http://orange-mibwas01:18080/Customers/CustomersIndex</jndi-name>
   </resource-ref>
   ...
</jboss-web>

When I deploy the webapp it leads to a DeploymentException.

If I change my jboss-web by removing the DTD reference and the content to :
<jboss-web>
   ...
   <resource-ref>
      <res-ref-name>url/urlData</res-ref-name>
      <res-url>http://localhost:8080/Data</res-url>
   </resource-ref>
   ...
</jboss-web>
It deploys fine.

The exception is raised in the org.jboss.metadata.ResourceRefMetaData class. When 
declaring an URL resource-ref, the searched tag is <res-url> and not <jndi-name>.
To enable URL Resource-ref, modifiy the definition of a resource-ref in jboss-web DTD 
to accept jndi-name OR res-url as child of resource-ref.


----------------------------------------------------------------------

>Comment By: Scott M Stark (starksm)
Date: 2003-01-17 15:24

Message:
Logged In: YES 
user_id=175228

Fixed in 3.0.6+

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=669733&group_id=22866


-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your 
clients even if they use browsers that are limited to 40 bit encryption. 
Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to