Bugs item #669731, was opened at 2003-01-17 05:54
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=669731&group_id=22866
Category: JBossWeb
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Laurent Etiemble (letiemble)
>Assigned to: Scott M Stark (starksm)
Summary: res-auth case problem
Initial Comment:
A web application compliant with the 2.2 servlet specs and which contains :
...
<resource-ref>
<res-ref-name>...</res-ref-name>
<res-type>...</res-type>
<res-auth>CONTAINER</res-auth>
</resource-ref>
...
will not deploy successfully.
According to the Servlet Specs 2.2 (Section 13.2) the <res-auth> tag in a web
descriptor can only contain "CONTAINER" or "SERVLET".
According to the Servlet Specs 2.3 (Section 13.3) the <res-auth> tag in a web
descriptor can only contain "Container" or "Application".
The org.jboss.metadata.ResourceRefMetaData class only accepts "Container" or
"Application" values, that's why the deployment of a 2.2 compliant web application
containing <resource-ref> tags will failed.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=669731&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
