- This topic has 4 replies, 3 voices, and was last updated 18 years, 9 months ago by
.
-
Posts
-
Hi,
I am evaluating Myeclipse for my team. I have a few problems right now (that I did not encounter with Exadel or BEA Workshop).
The JSP preview currently renders struts <html:select> <html:option> elements showing their “value” instead of what is inside the <option> tag. For example, for the JSP code below, the combo box shown has the numbers 1 and 2 in it.
<html:select property=”minMax”>
<html:option value=”1″>Use minimums & maximums</html:option>
<html:option value=”2″>Use fixed #</html:option>
</html:select>What should be shown is, obviously, the text in the tags.
Also, when displaying a java value e.g. <%=Constants.PARAM_MAX%>, the JSP preview shows {Constants.PARAM_MAX} instead of the value that it contains.
Thirdly, using the <bean:message> tag does not render my text from the ApplicationResources.properties file, it renders the key I put in the bean tag, for example ???this.is.the.key???, even though that key exists in the resources file.
Are these bugs due to new JSP preview functionality or is there a way to configure these options? If they are bugs, do you know when they might be fixed?
Thanks.
Lee.
The JSP preview currently renders struts <html:select> <html:option> elements showing their “value” instead of what is inside the <option> tag. For example, for the JSP code below, the combo box shown has the numbers 1 and 2 in it.
<html:select property=”minMax”>
<html:option value=”1″>Use minimums & maximums</html:option>
<html:option value=”2″>Use fixed #</html:option>
</html:select>What should be shown is, obviously, the text in the tags.
Definately sounds like a bug, I’ll file that ASAP, thanks for the heads up.
Also, when displaying a java value e.g. <%=Constants.PARAM_MAX%>, the JSP preview shows {Constants.PARAM_MAX} instead of the value that it contains.
Got it, filing.
Thirdly, using the <bean:message> tag does not render my text from the ApplicationResources.properties file, it renders the key I put in the bean tag, for example ???this.is.the.key???, even though that key exists in the resources file.
Filed this too. IIRC we support the rendering of JSF messages and JSTL messages but the support for bean:message got pushed back, I filed a reminder message for the designer team.
On a side note Lee I appologize this post got overlooked.
Wow – that’s a lot of very fundamental bugs – am re-considering the “MyEclipse” choice. Any idea when JSP rendering will be properly coded and tested and released (included these bug fixes)?
Thanks.
Lee.
@leekleiner wrote:
Thirdly, using the <bean:message> tag does not render my text from the ApplicationResources.properties file, it renders the key I put in the bean tag, for example ???this.is.the.key???, even though that key exists in the resources file.
Can you provide some more information on the topic? I tried to reproduce this issue and was unable to do so.
1. My Struts config has following entry:<message-resources parameter="com.yourcompany.struts.ApplicationResources" />2. My com.yourcompany.struts.ApplicationResources.properties file has following value: test.test=Dotted
3. This simple JSP works as expected:<%@ page language="java" pageEncoding="ISO-8859-1"%> <%@ taglib uri="http://jakarta.apache.org/struts/tags-bean" prefix="bean" %> <%@ taglib uri="http://jakarta.apache.org/struts/tags-html" prefix="html" %> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html:html locale="true"> <body> <bean:message key="test.test"/> </body> </html:html>
