Re: Accessing scope attributes with dotted names using JSTL
Try this:
"requestScope" is an EL implicit object.
Bruce
On Wednesday, June 4, 2003, at 05:10 AM, Steve Raeburn wrote:
Is it possible to access a scoped attribute if the attribute name
contains a
dot?
For example, if I set a request attribute:
request.setAttribute("mydomain.mybean", bean);
I'd like to access it like this:
-
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]
Accessing scope attributes with dotted names using JSTL
Is it possible to access a scoped attribute if the attribute name contains a
dot?
For example, if I set a request attribute:
request.setAttribute("mydomain.mybean", bean);
I'd like to access it like this:
Re: Bluedemons "Can't Resolve URI" Problem
Wow! It works now! Thanks a million. Now you taught me another important thing: Look at these logs. I had never done that before. Writing the web.xml as a total newbie to web app dev was a matter of guessing, copying and pasting... It ran well at first, but JSTL slapped me... ;-) Again, thanks a lot for your help! Karsten Michael Duffy wrote: Hi Karsten, I took a look at your app and I know exactly why you're having all the problems you are: your web.xml file is not correct. It doesn't match the DTD, so the parser is throwing exceptions before you ever try to process a page. I've attached the corrected web.xml. Once I corrected the problems I was able to use JSTL with your stuff in Tomcat. You can find out about these things from the Tomcat logs. I'd get into the habit of looking there first when you run into problems. I'd also recommend a good JSTL book before going much further. I like Shawn Bayern's "JSTL In Action" by Manning, but there are others out there. Good luck. - MOD __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com http://java.sun.com/dtd/web-app_2_3.dtd";> TV Dieburg Blue Demons TV Dieburg Blue Demons webmaster [EMAIL PROTECTED] The email address of the website administrator. front-controller The front controller in the MVC architecture used in this application de.bluedemons.servlet.MainServletFC 5 front-controller /MainServletFC 30 - 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]
Bluedemons "Can't Resolve URI" Problem
Hi Karsten, I took a look at your app and I know exactly why you're having all the problems you are: your web.xml file is not correct. It doesn't match the DTD, so the parser is throwing exceptions before you ever try to process a page. I've attached the corrected web.xml. Once I corrected the problems I was able to use JSTL with your stuff in Tomcat. You can find out about these things from the Tomcat logs. I'd get into the habit of looking there first when you run into problems. I'd also recommend a good JSTL book before going much further. I like Shawn Bayern's "JSTL In Action" by Manning, but there are others out there. Good luck. - MOD __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com http://java.sun.com/dtd/web-app_2_3.dtd";> TV Dieburg Blue Demons TV Dieburg Blue Demons webmaster [EMAIL PROTECTED] The email address of the website administrator. front-controller The front controller in the MVC architecture used in this application de.bluedemons.servlet.MainServletFC 5 front-controller /MainServletFC 30 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: tag forEach
"guidelines on how to interoperate with JSTL" sheez.. already starting to think like a lawyer. ;) -Tim -Original Message- From: Shawn Bayern [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 03, 2003 12:13 PM To: Tag Libraries Users List Subject: RE: tag forEach On 3 Jun 2003, Dave Newton wrote: > One way around this might be just to say that if you want your tags to > play nice with JSTL tags (break in particular) that it should > implement J. Random Interface (or whatever) that deals with this > parent tag communication issue. But then page authors would need to know which tags they could use and which they couldn't use around . The problem isn't how to support tag developers; if that were the issue, we could already give them guidelines on how to interoperate with JSTL (in this case, they'd need to rethrow the exception if they caught it). Instead, the goal is to simplify things for page authors. -- Shawn Bayern "JSTL in Action" http://www.manning.com/bayern - 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]
RE: tag forEach
On 3 Jun 2003, Dave Newton wrote: > One way around this might be just to say that if you want your tags to > play nice with JSTL tags (break in particular) that it should > implement J. Random Interface (or whatever) that deals with this > parent tag communication issue. But then page authors would need to know which tags they could use and which they couldn't use around . The problem isn't how to support tag developers; if that were the issue, we could already give them guidelines on how to interoperate with JSTL (in this case, they'd need to rethrow the exception if they caught it). Instead, the goal is to simplify things for page authors. -- Shawn Bayern "JSTL in Action" http://www.manning.com/bayern - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: tag forEach
On Tue, 2003-06-03 at 11:23, Chen, Gin wrote: > could be implemented better if it threw an exception meant to be > caught using JSP 1.2's TryCatchFinally interface, but the implementation > would still not be fully operable when custom tags were involved. In a > situation like > > > > > > > > the handler for would, if it implemented TryCatchFinally, > need to know to re-throw the exception that the inner tag throws. > If it didn't, then 's message would be lost and it would have no > effect. A tag that we couldn't guarantee to work wouldn't be much > of a tag! One way around this might be just to say that if you want your tags to play nice with JSTL tags (break in particular) that it should implement J. Random Interface (or whatever) that deals with this parent tag communication issue. DAve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: tag forEach
Shawn gave a great answer to this question before: In the future please search the archives first. Shawn's response: "New tags would be required for this, but they are not implementable in JSP 1.2 and have thus are not planned for JSPTL 1.0. The problem is how a tag would signal the completion of a loop and cause the loop to terminate immediately. could be implemented merely as a 'signal' to the containing tag to halt iteration after the current round of iteration, but this would not be a true break and would be confusing because of its differences with Java's 'break' keyword. could be implemented better if it threw an exception meant to be caught using JSP 1.2's TryCatchFinally interface, but the implementation would still not be fully operable when custom tags were involved. In a situation like the handler for would, if it implemented TryCatchFinally, need to know to re-throw the exception that the inner tag throws. If it didn't, then 's message would be lost and it would have no effect. A tag that we couldn't guarantee to work wouldn't be much of a tag! is even more problematic, since the TryCatchFinally implementation would be completely untenable: once an exception is caught by doCatch(), there is no mechanism to "restart" the tag. Thus, and are not planned as JSPTL tags, at least not in JSPTL 1.0. You can emulate their behavior with proper structuring of tags. While more verbose, this latter usage is more closely in line with what's seen as a more typical JSP pattern: JSP, being used mostly for presentation, needs less intricate control flow than the Java language itself provides. Shawn Bayern JSPTL reference-implementation lead" -Original Message- From: MARCIO JULIÃO [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 03, 2003 10:40 AM To: Tag Libraries Users List Subject: tag forEach Hi, Is there a way to break the flow inside the tag forEach ? Example: ... Márcio Julião RiskControl Serviços Ltda. Email:[EMAIL PROTECTED] Tel: (21) 2514-8253 Fax: (21) 2514-8233 Acesse o site: http://www.riskcontrol.com.br - Esta mensagem contém informações confidenciais e foi enviada somente ao(s) destinatário(s) acima. Caso você não seja a pessoa endereçada, náo deverá divulgar, distribuir ou copiar esta mensagem. Se você a recebeu por engano, favor notificar imediatamente o remetente e em seguida destruí-la. This message contains confidential information and is intended only for the individual named. If you are not the addressee you should not disseminate, distribute or copy this message. Please notify the sender immediately if you have received this message by mistake and then destroy it. - 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]
Re: tag forEach
You can use a differnt syntax for iterating a certain number of times. http://www.onjava.com/lpt/a/2611 Karsten MARCIO JULIÃO wrote: Hi, Is there a way to break the flow inside the tag forEach ? Example: ... Márcio Julião RiskControl Serviços Ltda. Email:[EMAIL PROTECTED] Tel: (21) 2514-8253 Fax: (21) 2514-8233 Acesse o site: http://www.riskcontrol.com.br - Esta mensagem contém informações confidenciais e foi enviada somente ao(s) destinatário(s) acima. Caso você não seja a pessoa endereçada, náo deverá divulgar, distribuir ou copiar esta mensagem. Se você a recebeu por engano, favor notificar imediatamente o remetente e em seguida destruí-la. This message contains confidential information and is intended only for the individual named. If you are not the addressee you should not disseminate, distribute or copy this message. Please notify the sender immediately if you have received this message by mistake and then destroy it. - 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]
tag forEach
Hi, Is there a way to break the flow inside the tag forEach ? Example: ... Márcio Julião RiskControl Serviços Ltda. Email:[EMAIL PROTECTED] Tel: (21) 2514-8253 Fax: (21) 2514-8233 Acesse o site: http://www.riskcontrol.com.br - Esta mensagem contém informações confidenciais e foi enviada somente ao(s) destinatário(s) acima. Caso você não seja a pessoa endereçada, náo deverá divulgar, distribuir ou copiar esta mensagem. Se você a recebeu por engano, favor notificar imediatamente o remetente e em seguida destruí-la. This message contains confidential information and is intended only for the individual named. If you are not the addressee you should not disseminate, distribute or copy this message. Please notify the sender immediately if you have received this message by mistake and then destroy it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
