html tags in message resources
I'd like to put some html tags in an ActionMessage that I read in from my message resources (to create some links in the event of an error). Unfortunately, the html is being escaped when it displayed on the page (using html:messages/bean:write etc). I didn't think it would be a problem because I can use html with on a page. Any advice/alternate solutions much appreciated. Wes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Prevent display of JspException
No. It would be thrown by struts code, say if somebody mucked with my ApplicationResources.properties and a certain message key couldn't be found. This is something that would happen when the JSPs are compiled. There is really only an off chance of this occuring in production, just wanted to see if something could be done should it arise. -Original Message- From: Mike Jasnowski [mailto:[EMAIL PROTECTED] Sent: Monday, September 29, 2003 9:40 AM To: Struts Users Mailing List Subject: RE: Prevent display of JspException your own... -Original Message- From: Mike Jasnowski [mailto:[EMAIL PROTECTED] Sent: Monday, September 29, 2003 12:37 PM To: Struts Users Mailing List Subject: RE: Prevent display of JspException Is this exception coming from you're own code? Can you do a File.exists() first and throw something more app specific that a Struts exception handler could catch? -Original Message----- From: Wes Kubo [mailto:[EMAIL PROTECTED] Sent: Monday, September 29, 2003 12:42 PM To: Struts Users Mailing List Subject: Prevent display of JspException I've been doing some refactoring with my ApplicationResources.properties and every once in a while I get a page that shows a JspException when I've mistyped a property name or whatever. Is there anyway of catching the JspException at this compilcation point and displaying a different message (or none at all)? Theoretically, this should never happen once we deploy, but if someone mucks with an image path or something is missing, I'd rather the client deal with a missing image rather than see the JspException trace. Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Prevent display of JspException
I've been doing some refactoring with my ApplicationResources.properties and every once in a while I get a page that shows a JspException when I've mistyped a property name or whatever. Is there anyway of catching the JspException at this compilcation point and displaying a different message (or none at all)? Theoretically, this should never happen once we deploy, but if someone mucks with an image path or something is missing, I'd rather the client deal with a missing image rather than see the JspException trace. Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Force initialization of RequestProcessor?
In my J2EE/struts app I'm initializing a class for handling properties within the RequestProcessor (actually a custom subclass of TilesRequestProcessor). This works fine in practice, because the EJB tier is always accessed through the web tier and the properties are always initialized ok. The problem is that during testing, the web tier is never called and the initialization doesn't happen. Is there any way to force the RequestProcessor to initialize, even before its called? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with tiles and protected jsps
I originally had my jsps under WEB-INF to prevent them from direct access, which worked just fine. However, the standards I'm working with dictate that the jsps be located above WEB-INF. In order to prevent access to my jsps I added a security-constraint in web.xml, blocking access to the jsps. Unfortunately, now none of my tiles display properly, instead I get the error message: [Exception in:/jsp/body/home_body.jsp] Response has already been committed for all the protected pages. The problem is that for each protected page, its trying to authenticate the user using the FORM authentication that I have set-up for parts of the application (this is a separate security-constraint from the jsp protection). All I want to prevent is direct access to the jsp, not access through other means (e.g. action/tile). Thanks. Wes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Response committed exception with tiles and protected jsps
Sorry for the repost...but I didn't get any response and this problem is a real show-stopper: Due to standards beyond my control I had to move my jsps from beneath /WEB-INF/jsp to /jsp. In order to prevent access to my jsps I added a security-constraint, blocking access to the jsps. Unfortunately, now none of my tiles display properly, instead I get the error message: [Exception in:/jsp/body/home_body.jsp] Response has already been committed for all the protected pages. The problem is that for each protected page, its trying to authenticate the user using the FORM authentication that I have set-up (this is a separate security-constraint from the jsp protection). All I want to prevent is direct access to the jsp, not access through other means (e.g. action/tile). Thanks. Wes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Response committed exception with tiles and protected jsps
Due to standards beyond my control I had to move my jsps from beneath /WEB-INF/jsp to /jsp. In order to prevent access to my jsps I added a security-constraint, blocking access to the jsps. Unfortunately, now none of my tiles display properly, instead I get the error message: [Exception in:/jsp/body/home_body.jsp] Response has already been committed for all the protected pages. The problem is that for each protected page, its trying to authenticate the user using the FORM authentication that I have set-up (this is a separate security-constraint from the jsp protection). All I want to prevent is direct access to the jsp, not access through other means (e.g. action/tile). Thanks. Wes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Getting hashmap value based on bean value.
In my jsp I have a collection of beans and a hashmap. One of the things that I need to display is the name, e.g. Note that the beanA contains a beanB. Now what I want to is get a value out of my hashmap based on beanB.id. Theoretically, I want something like: Which I know doesn't work. I had to resort to using bean:define to define the id as a scripting variable and then using a scriplet to display the hashmap, e.g. <%= myHashMap.get(beanBId)%>. I want to avoid scriptlets but can't figure out how to do this. Thanks. Wes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Getting hashmap value based on bean value.
Thanks. Works fine and is much cleaner. Wes -Original Message- From: Bailey, Shane C. [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 12, 2003 11:56 AM To: 'Struts Users Mailing List' Subject: RE: Getting hashmap value based on bean value. Will this work: -Original Message----- From: Wes Kubo [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 12, 2003 2:38 PM To: Struts Users Mailing List Subject: Getting hashmap value based on bean value. In my jsp I have a collection of beans and a hashmap. One of the things that I need to display is the name, e.g. Note that the beanA contains a beanB. Now what I want to is get a value out of my hashmap based on beanB.id. Theoretically, I want something like: Which I know doesn't work. I had to resort to using bean:define to define the id as a scripting variable and then using a scriplet to display the hashmap, e.g. <%= myHashMap.get(beanBId)%>. I want to avoid scriptlets but can't figure out how to do this. Thanks. Wes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
