Changing Web Container

[akash_bansal]

I have some JSP tag libraries which are working fine on weblogic 10.3 but when I used them on jboss, it complains that attributes of tags should be in small case.

Apart from this one more issue is : in one of my jsp I am using <jsp:useBean> tag two times with the same id, and jboss gives following error:

useBean: Duplicate bean name

While this code is working fine on weblogic 10.3

Is there any way I can change web container in jboss 7.1?

[jaikiran]

akash bansal wrote:

I have some JSP tag libraries which are working fine on weblogic 10.3 but when I used them on jboss, it complains that attributes of tags should be in small case.

Please add more details about this one.

akash bansal wrote:

Apart from this one more issue is : in one of my jsp I am using <jsp:useBean> tag two times with the same id, and jboss gives following error:

useBean: Duplicate bean name

ids are meant to be unique.

[akash_bansal]

I apologies for replying late.

I am using following struts tag:

<html:textarea property="address" cols="50" rows="10" onKeyPress="validate();"/>

Jboss complains that onKeyPress attribute should be "onkeypress". While this works fine in weblogic 10.3 even if onKeyPress is in capital letters or in small letters or in camel case.

Second thing, in my jsp, I am having following code written, here I am ussing "address" as id for both <use:Bean> tag.

<%{%>
<jsp:useBean id="address" class="AddressBean" scope="session" />
<%}%>
<jsp:useBean id="address" class="AddressBean" scope="session" />

This was working fine in weblogic 10.3, but when I deployed same in jboss 7.1, it gave following error:

useBean: Duplicate bean name

[sfcoy]

Hi there,

It looks like WebLogic is broken in both respects here.

The tag declarations are xml, and xml is always case sensitive.

Furthermore, the JSP spec* has the following to say about the id of a jsp:useBean tag:

{quote}
The id=”name” attribute/value tuple in a jsp:useBean action has special meaning to a JSP container, at page translation time and at client request processing time. In particular:
• the name must be unique within the translation unit, and identifies the particular element in which it appears to the JSP container and page.
Duplicate id’s found in the same translation unit shall result in a fatal translation error.
{quote}

* and has done so since at least 2001