RE: NewBie Question
You took the words right out of my mouth! -Original Message- From: Karapiperis Dimitris [mailto:[EMAIL PROTECTED] Sent: Friday, April 04, 2003 6:56 AM To: Struts Users Mailing List Subject: RE: NewBie Question Vangeli, ta Struts framework den einai tpt allo apo thn efarmogh toy MVC design pattern. Ta Struts soy prosferoyn enan dynato Controller kai aforoyn th domi ths efarmoghs. Sto view enapokeitai se esena ti tha xrhsimopoihseis. Sto .jsp alloste mporeis na exeis JavaScript. XSLT logika tha mporeis na xrhsimpopoihses, den vlepo to logo gia to antitheto. my warmest regards, - Dimitrios Karapiperis Software Engineer Metropolis Informatics SA tel: +30 2310 225815 fax +30 2310 256259 -Original Message- From: Vangelis Konstantinis [mailto:[EMAIL PROTECTED] Sent: Friday, April 04, 2003 2:42 PM To: [EMAIL PROTECTED] Subject: NewBie Question Hi to all, I am new to Struts-Tiles(1-day), I am new to this technology, i would to use it in a web-application, My questions is: Can the Struts-Tile colloborate Ok with JavaScript and XSLT. In other words can in a Jsp Page use Java Script XSLT with Tiles and work OK? Thanks in advance. E.K. - 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: [tiles] tiles:insert not working for relative path
Volker, When you use the tiles:insert with a page attribute, it automatically inserts the context path (without the trailing slash), so the final URI would be something like myAppMyJSP.jsp. Tai -Original Message- From: Volker Krebs [mailto:[EMAIL PROTECTED] Sent: Monday, March 24, 2003 4:23 AM To: [EMAIL PROTECTED] Subject: [tiles] tiles:insert not working for relative path Hello, I've just updated our system from struts-1.1b2 to struts-1.1rc1. It seems that tiles:insert page=/ only works for an absolute Path now. tiles:insert page=/path/to/jsp/MyJSP.jsp flush=true/ is working while tiles:insert page=MyJSP.jsp flush=true/ is not working. MyJSP.jsp is in the same Directory the other JSP is. Can anyone confirm that ? I didn't find a bug entry for that. Or has something changed in RC1 ? Thanks. Volker - 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: Nesting tile definitions
Logic tags will not work because they get evaluated after Tiles tags. If you define your default values at the parent definition level (.standardPage), you would only need to specify override attributes in child definitions. The values you specify in .standardPage.header are overridden in any case, so you can leave them blank. So, if you had: definition name=.standardPage path=/WEB-INF/common/layouts/standardLayout.jsp put name=title value=NO TITLE DEFINED / put name=header value=.standardPage.header / put name=footer value=/WEB-INF/common/footer.jsp / put name=content value=NO CONTENT DEFINED / put name=right value=/WEB-INF/common/common-right.jsp/ put name=leftvalue=/WEB-INF/common/common-left.jsp/ /definition Then you could have: definition name=page1 extends=.standardPage put name=title value=Page 1/ put name=content value=/WEB-INF/pages/page1.jsp/ /definition definition name=page2 extends=.standardPage put name=title value=Page 2/ put name=content value=/WEB-INF/pages/page2.jsp/ put name=right value=/WEB-INF/common/other-right.jsp/ /definition -Original Message- From: Kevin Cramer [mailto:[EMAIL PROTECTED] Sent: Monday, March 24, 2003 2:04 AM To: Struts Users Mailing List Subject: Re: Nesting tile definitions I don't think I explained it very well. As I understand it I would do the following using the method you mentioned below: definition name=page1 extends=.standardPage put name=title value=Page 1/ put name=content value=/WEB-INF/pages/page1.jsp/ put name=right value=/WEB-INF/common/common-right.jsp/ put name=left value=/WEB-INF/common/common-left.jsp/ /definition definition name=page2 extends=.standardPage put name=title value=Page 2/ put name=content value=/WEB-INF/pages/page2.jsp/ put name=right value=/WEB-INF/common/other-right.jsp/ put name=left value=/WEB-INF/common/common-left.jsp/ /definition This allows me to change the values of left and right at the highest/page level. In my application the value of right and left is usually a certain value and in a few cases they are overriden. That is why I was wondering if there is anyway I could have this work: definition name=page1 extends=.standardPage put name=title value=Page 1/ put name=content value=/WEB-INF/pages/page1.jsp/ /definition definition name=page2 extends=.standardPage put name=title value=Page 2/ put name=content value=/WEB-INF/pages/page2.jsp/ put name=right value=/WEB-INF/common/other-right.jsp/ /definition definition name=.standardPage.header path=/WEB-INF/common/header.jsp put name=bar value=.standardPage.header.bar/ put name=right value=/WEB-INF/common/common-right.jsp/ put name=left value=/WEB-INF/common/common-left.jsp/ /definition In the above, I only specify the right and left in the page definitions where it differs from the usual values which are defined in .standardPage.header. Is it possible to do this? I had no luck messing around with the tiles:put tags and the logic tags. I thought I could conditionally do the tiles:put using the logic:present tag to see if right and left were set. This is what I tried but it didn't work: tiles:insert attribute=bar logic:present name=right tiles:put name=right beanName=right beanScope=tile / /logic:present logic:present name=left tiles:put name=left beanName=left beanScope=tile / /logic:present /tiles:insert I tried various settings and changing the scope on the logic:present but I could not figure out how to detect if the tile definition included the attribute right or left. Thanks, Kevin On Mon, Mar 24, 2003 at 12:45:21AM -0500, Tai Nguyen wrote: Kevin, I'm pretty sure that once you have the attribute inheritance set up, it won't be possible to override the attribute at a lower level. However, if I get you right, you could simply define a child definition for page2 which extends .standardPage. In short, it shouldn't matter at what level you override an attribute. Tai -Original Message- From: Kevin Cramer [mailto:[EMAIL PROTECTED] Sent: Sunday, March 23, 2003 9:48 PM To: Struts Users Mailing List Subject: Re: Nesting tile definitions Thank you. I have this working. The side effect is that it would require me to define all the attributes at the highest level. What if I would like to define the attributes at a lower level and then override it when it changes for a certain page? In my example I would like to define right at the .standardPage.header or .standardPage.header.bar level and override it for page2. I tried using logic:present name=right/ tags around the tiles:put you specified below but that didn't help. It seems that when you use the tiles:put it overrides that attribute in the subtiles. If the attribute is not defined
RE: Nesting tile definitions
Kevin, I'm pretty sure that once you have the attribute inheritance set up, it won't be possible to override the attribute at a lower level. However, if I get you right, you could simply define a child definition for page2 which extends .standardPage. In short, it shouldn't matter at what level you override an attribute. Tai -Original Message- From: Kevin Cramer [mailto:[EMAIL PROTECTED] Sent: Sunday, March 23, 2003 9:48 PM To: Struts Users Mailing List Subject: Re: Nesting tile definitions Thank you. I have this working. The side effect is that it would require me to define all the attributes at the highest level. What if I would like to define the attributes at a lower level and then override it when it changes for a certain page? In my example I would like to define right at the .standardPage.header or .standardPage.header.bar level and override it for page2. I tried using logic:present name=right/ tags around the tiles:put you specified below but that didn't help. It seems that when you use the tiles:put it overrides that attribute in the subtiles. If the attribute is not defined at the highest level then you don't get the setting at lower levels. Thanks, Kevin On Sat, Mar 22, 2003 at 06:42:10PM -0500, Tai Nguyen wrote: Kevin, To make an attribute available to a nested tile you need to pass it along when you call the tile. For example: tiles:insert attribute=bar tiles:put name=right beanName=right beanScope=tile / tiles:put name=left beanName=left beanScope=tile / /tiles:insert Where beanName is the name of the attribute you want to pass and name is what you want to pass it as and scope is tile context. In your case, you would also need to add a similar declaration in your .standardPage.header tile since you need to pass it along twice. Once you've done all that, you would actually specify the tiles attribute values in the parent definition. This can be very helpful in keeping all the attributes for a given view in one definition instead of scattered all over your tiles-def.xml. Tai -Original Message- From: Kevin Cramer [mailto:[EMAIL PROTECTED] Sent: Thursday, March 20, 2003 6:19 PM To: Struts Users Mailing List Subject: Re: Nesting tile definitions I got it working. It was a problem with something else. I didn't catch it. It can be hard to find problems with the lack of debug messages that come back from the server. My next question was how do I use attributes from supertiles? I want to take a page and split it into tiles, one of which is the header. I also wanted to further divide the header into subtiles. In particular there is a part of a subtile in the header tile which can vary depending on which page you are on. I'm wondering what is the easiest way to deal with it. I'm doing all of this using the XML Tile definitions. I put an example below with just the relevant parts. If I want page1 to use one value for the right and page2 to use another value for right how do I do that? right is defined 2 levels down from the standard page tile. It would be nice to override it at the highest level. Perhaps I am doing things wrong. It seems wrong to define multiple intermediate tiles for the different combinations. tiles-definitions definition name=.standardPage path=/WEB-INF/common/layouts/standardLayout.jsp put name=title value=NO TITLE DEFINED / put name=header value=.standardPage.header / put name=footer value=/WEB-INF/common/footer.jsp / put name=content value=NO CONTENT DEFINED / /definition definition name=.standardPage.header path=/WEB-INF/common/header.jsp put name=bar value=.standardPage.header.bar/ /definition definition name=.standardPage.header.bar path=/WEB-INF/common/bar.jsp put name=right value=/WEB-INF/common/qsearch.jsp/ put name=left value=/WEB-INF/common/comp1.jsp/ /definition definition name=.page1 extends=.standardPage put name=title value=Page 1/ put name=content value=/WEB-INF/pages/page1.jsp/ /definition definition name=.page2 extends=.standardPage put name=title value=Page 2/ put name=content value=/WEB-INF/pages/page2.jsp/ /definition /tiles-definitions Kevin On Wed, Mar 19, 2003 at 05:07:04PM -0500, Tai Nguyen wrote: Kevin, First if all, it is possible to use attributes from supertiles, but that's another issue. The definitions you have posted look fine, so I would guess that it's a problem with your header.jsp file. Can you post that so we can look at it, as well as the full error message you are getting? Thanks, Tai -Original Message- From: Kevin Cramer [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 4:43 PM To: [EMAIL PROTECTED] Subject: Nesting tile definitions I am trying to have
RE: Validation and Reset
Jeremy, This is because your image button is a submit button, regardless of what the text on it may say. The link you provided didn't say anything about reset methodology so I'm not sure what you are referring to there, but the easiest way to avoid triggering the validate method is to not submit the form! For example, make the button a simple image (instead of an input image button), and reset the form with a javascript onclick event (e.g. document.myform.reset();) Tai -Original Message- From: Weber, Jeremy [mailto:[EMAIL PROTECTED] Sent: Friday, March 21, 2003 9:27 AM To: 'Struts Users Mailing List' (E-mail) Subject: Validation and Reset Hello all! It seems when I click my reset button my form is validated. Is there anyway to keep this from happening? I am using html:image and the reset methodology here http://www.husted.com/struts/tips/001.html Jeremy Weber Eventra, Inc. Sr. SCM Specialist 203-882-9988 x2631 [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]
RE: struts-config.xml
Tell me about it! ClearCase XML merges are completely useless. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, March 21, 2003 2:23 AM To: [EMAIL PROTECTED] Subject: RE: struts-config.xml I work with ClearCase and WSAD 4.0.3 and can tell you that merging xml files of the size you are talking about is terrible. We have about 100+ different xml files about 2/3 the size or larger than what you describe, and I can tell you that of the 8 developers here, that is what we hate the most. We loose more time on xml merges than any other merge by double. Of coarse it might just be clearcase and WSAD _ Thank You Mick Knutson Sr. Designer - Project Trust aUBS AG, Financial - Zürich Office: +41 (0)1/234.42.75 Internal: 48194 Mobile: 079.726.14.26 _ -Original Message- From: Pat Young [mailto:[EMAIL PROTECTED] Sent: Thursday, March 20, 2003 10:23 PM To: Struts Users Mailing List Subject: RE: struts-config.xml Yes, I have looked at sub-applications and we are considering it. Using sub-applications does have some technical considerations that have to be accounted for.I realize that we could use a merge feature of a versioning tool also. I was curious if anyone had any other creative ideas around this problem or if there was a feature in Struts that I had missed. Pat Young --- Mike Jasnowski [EMAIL PROTECTED] wrote: Well, version control considerations aside (for issues around merges when new struts-config.xml are checked in), Have you also looked at Struts sub-applications? Each can have it's own struts-config.xml. -Original Message- From: Pat Young [mailto:[EMAIL PROTECTED] Sent: Thursday, March 20, 2003 4:14 PM To: [EMAIL PROTECTED] Subject: struts-config.xml I am curious as to how others are working with the struts-config.xml file. I am working on a large project with a team of 8 other developers. So far we have over 200 actions. The struts-config.xml is becoming a bottle neck, because each developer needs to update the file at the same with entries into this file. Does anyone have any ideas as to how to make working with this file any easier? Thanks in advance. Pay Young __ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com - 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] __ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Visit our website at http://www.ubswarburg.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. - 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: Searching the Struts Mail List Archive
Occasionally I do. -Original Message- From: Cruz, Edward J. [mailto:[EMAIL PROTECTED] Sent: Thursday, March 20, 2003 9:50 AM To: Struts Users Mailing List Subject: RE: Searching the Struts Mail List Archive Has anyone been getting a Bad Gateway Error when trying to use the second search page? http://nagoya.apache.org/eyebrowse/SummarizeList?listId=42 Jamie Cruz Software Engineering [EMAIL PROTECTED] (301)688-1430 -Original Message- From: James Watkin [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2003 4:27 PM To: [EMAIL PROTECTED] Subject: Searching the Struts Mail List Archive I'd like to give some constructive feedback on the two different interfaces to the Struts Mail List Archive. http://www.mail-archive.com/[EMAIL PROTECTED]/ and http://nagoya.apache.org/eyebrowse/SummarizeList?listId=42 The second interface seems to give more relevant search results. Have others found this to be true? - Jim __ James Watkin ACIS Software Development The Anderson School at UCLA [EMAIL PROTECTED] Voice: 1-310-825-5030 Fax: 1-310-825-4835 __ - 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]
RE: Nesting tile definitions
Kevin, To make an attribute available to a nested tile you need to pass it along when you call the tile. For example: tiles:insert attribute=bar tiles:put name=right beanName=right beanScope=tile / tiles:put name=left beanName=left beanScope=tile / /tiles:insert Where beanName is the name of the attribute you want to pass and name is what you want to pass it as and scope is tile context. In your case, you would also need to add a similar declaration in your .standardPage.header tile since you need to pass it along twice. Once you've done all that, you would actually specify the tiles attribute values in the parent definition. This can be very helpful in keeping all the attributes for a given view in one definition instead of scattered all over your tiles-def.xml. Tai -Original Message- From: Kevin Cramer [mailto:[EMAIL PROTECTED] Sent: Thursday, March 20, 2003 6:19 PM To: Struts Users Mailing List Subject: Re: Nesting tile definitions I got it working. It was a problem with something else. I didn't catch it. It can be hard to find problems with the lack of debug messages that come back from the server. My next question was how do I use attributes from supertiles? I want to take a page and split it into tiles, one of which is the header. I also wanted to further divide the header into subtiles. In particular there is a part of a subtile in the header tile which can vary depending on which page you are on. I'm wondering what is the easiest way to deal with it. I'm doing all of this using the XML Tile definitions. I put an example below with just the relevant parts. If I want page1 to use one value for the right and page2 to use another value for right how do I do that? right is defined 2 levels down from the standard page tile. It would be nice to override it at the highest level. Perhaps I am doing things wrong. It seems wrong to define multiple intermediate tiles for the different combinations. tiles-definitions definition name=.standardPage path=/WEB-INF/common/layouts/standardLayout.jsp put name=title value=NO TITLE DEFINED / put name=header value=.standardPage.header / put name=footer value=/WEB-INF/common/footer.jsp / put name=content value=NO CONTENT DEFINED / /definition definition name=.standardPage.header path=/WEB-INF/common/header.jsp put name=bar value=.standardPage.header.bar/ /definition definition name=.standardPage.header.bar path=/WEB-INF/common/bar.jsp put name=right value=/WEB-INF/common/qsearch.jsp/ put name=left value=/WEB-INF/common/comp1.jsp/ /definition definition name=.page1 extends=.standardPage put name=title value=Page 1/ put name=content value=/WEB-INF/pages/page1.jsp/ /definition definition name=.page2 extends=.standardPage put name=title value=Page 2/ put name=content value=/WEB-INF/pages/page2.jsp/ /definition /tiles-definitions Kevin On Wed, Mar 19, 2003 at 05:07:04PM -0500, Tai Nguyen wrote: Kevin, First if all, it is possible to use attributes from supertiles, but that's another issue. The definitions you have posted look fine, so I would guess that it's a problem with your header.jsp file. Can you post that so we can look at it, as well as the full error message you are getting? Thanks, Tai -Original Message- From: Kevin Cramer [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 4:43 PM To: [EMAIL PROTECTED] Subject: Nesting tile definitions I am trying to have a tile definition include another definition but it doesn't seem to be working. Can I do this and if so then how do I do it? Here is an example of what I am trying to do. I would like the header of a standard page to be another tile so I can further divide it into pieces. However, when I try to create a definition that extends the .standardPage I get an error at the top of the page. It just says that there has been a ServletException in /WEB-INF/common/layouts/header.jsp. I understand that a tile cannot use attributes from subtiles or supertiles and I don't think that is the problem. tiles-definitions definition name=.standardPage path=/WEB-INF/common/layouts/standardLayout.jsp put name=title value=NO TITLE DEFINED / put name=std_jscript value=/WEB-INF/common/std-jscript.jsp / put name=header value=.standardPage.header / put name=footer value=/WEB-INF/common/footer.jsp / put name=content value=NO CONTENT DEFINED / /definition definition name=.standardPage.header path=/WEB-INF/common/layouts/header.jsp put name=tagline.left value=/WEB-INF/common/qsearch.jsp/ put name=tagline.right value=/WEB-INF/common/instBanner.jsp/ /definition /tiles-definitions Thanks, Kevin
RE: images in html buttons
Wayne, You can use standard HTML to render your button, but you lose the advantages of automatic context path maintenance. Is there a specific reason you don't want to use html:image buttons? Tai -Original Message- From: Wayne A Christian [mailto:[EMAIL PROTECTED] Sent: Thursday, March 20, 2003 12:38 PM To: struts user (E-mail) Subject: images in html buttons Within the body of a standard HTML button tag, I can place HTML, such as the img tag and this will get rendered as the button image. With struts html:button tag, this doesn't work and I get the raw text rendered as the button text. Is there a way around this other than going to image maps which don't work the same way as buttons do? Wayne Christian Sr. Staff Software Engineer Genesys Telecommunications Labs 2100 Gateway Centre Blvd. Suite 300 Morrisville, NC 27560 ? Office: (919) 466-6151 Fax:(919) 466-6157 ? EMail: mailto:[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]
RE: [TILES] Inserting a definition in an other definition ?
Lionel, The short answer to your question is yes. Not only is this possible, but I can't imagine a good design that doesn't do this. Nesting of definitions is one of the most powerful features of Tiles. However, you have a small syntax error in that your default definition refers to the content definition as .content when its name is content. Also, you should have all definitions in one tiles-definition tag... I'm pretty sure? Tai -Original Message- From: Lionel Roux [mailto:[EMAIL PROTECTED] Sent: Saturday, March 22, 2003 11:46 AM To: [EMAIL PROTECTED] Subject: [TILES] Inserting a definition in an other definition ? Is it possible to insert a definition in an other definition ? tiles-definitions definition name=default path=/layouts/defaultLayout.jsp put name=header value=/common/header.jsp / put name=content value=.content / put name=copyright value=/common/copyright.jsp / /definition /tiles-definitions tiles-definitions definition name=content path=/layouts/contentLayout.jsp put name=menu value=/common/menu.jsp / put name=body value=/common/body.jsp / /definition /tiles-definitionsIs this possible? Is ther an other better solution ?__ Lionel Roux mail: [EMAIL PROTECTED] cell: +33 6 60 51 49 83 __ This messages is certified virus free by NAV 2003 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Beginner question
Joshua, The reset method is called BEFORE the form bean is populated from the request. Therefore, it is not possible to lose any data from the user's form post. So, the basic flow is: create or reuse Form bean reset populate validate Action perform or execute return forward. Tai -Original Message- From: White, Joshua A (CASD, IT) [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 10:17 AM To: '[EMAIL PROTECTED]'; [EMAIL PROTECTED] Subject: RE: Beginner question This suggestion brings up another question. To properly set my boolean values (radio buttons), my reset method sets my booleans to false. If I leave my form in session, doesn't the controller call the reset method after every after every request? If my booleans equal true, by the time I get to my viewIt action, won't they be reset to false? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 8:07 AM To: [EMAIL PROTECTED] Subject: RE: Beginner question Have you tried putting itemId into session context instead of request context? _ Thank You Mick Knutson Sr. Designer - Project Trust aUBS AG, Financial - Zürich Office: +41 (0)1/234.42.75 Internal: 48194 Mobile: 079.726.14.26 _ -Original Message- From: White, Joshua A (CASD, IT) [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 2:00 PM To: Struts Users Mailing List Subject: Beginner question I have two struts actions: insertIt - adds an item to the database. When successful, this action forwards to the viewIt action putting the newly inserted items itemId into the request. viewIt - views an item by itemId (retrieves itemId from request) When insertIt successfully completes, It forwards to viewIt without a redirect. As many of you know, if the user then refreshes the page, the insert action is performed again. To solve this problem, I changed the redirect attribute to true. The refresh problem disappears. However, the request variable itemId gets lost because of the redirect. I know this is something every struts developer has worked through. Could someone suggest a pattern for this type of transaction? Regards, Joshua This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Visit our website at http://www.ubswarburg.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. - 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: Tiles
Nathan, Is your question, what is better, creating definitions in JSP's or in the XML? If so, it's better to create definitions in tiles-def.xml, as is it easier to maintain all your definitions if they are one place. It also allows you to have definitions which stay in application scope, as opposed to having to include a JSP file with all your definitions which incurs overhead. Tai -Original Message- From: Nathan Steiner [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 12:07 PM To: 'Struts Users Mailing List' Subject: Tiles I am fairly new to struts, and was just getting comfortable with templates, and now must dig into tiles. With tiles, from what I can gather, you can compose your definitions in jsp's and/or tiles-def xml file, and extend them, yada, yada, yada. I guess my question is what are the pros-cons for both? Thanks, Nate - 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: Tiles
You can configure your web.xml to have multiple tiles-def.xml files for easier maintenance. -Original Message- From: Nathan Steiner [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 2:24 PM To: 'Struts Users Mailing List' Subject: RE: Tiles Yes, you are correct on the point of my question. As for placing them all in the tiles-def.xml, does maintenance of that file become cumbersome for a large site? Are there performance issues related to the size of the xml file? Thanks, Nate -Original Message- From: Tai Nguyen [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 12:29 PM To: 'Struts Users Mailing List' Subject: RE: Tiles Nathan, Is your question, what is better, creating definitions in JSP's or in the XML? If so, it's better to create definitions in tiles-def.xml, as is it easier to maintain all your definitions if they are one place. It also allows you to have definitions which stay in application scope, as opposed to having to include a JSP file with all your definitions which incurs overhead. Tai -Original Message- From: Nathan Steiner [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 12:07 PM To: 'Struts Users Mailing List' Subject: Tiles I am fairly new to struts, and was just getting comfortable with templates, and now must dig into tiles. With tiles, from what I can gather, you can compose your definitions in jsp's and/or tiles-def xml file, and extend them, yada, yada, yada. I guess my question is what are the pros-cons for both? Thanks, Nate - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Nesting tile definitions
Kevin, First if all, it is possible to use attributes from supertiles, but that's another issue. The definitions you have posted look fine, so I would guess that it's a problem with your header.jsp file. Can you post that so we can look at it, as well as the full error message you are getting? Thanks, Tai -Original Message- From: Kevin Cramer [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 4:43 PM To: [EMAIL PROTECTED] Subject: Nesting tile definitions I am trying to have a tile definition include another definition but it doesn't seem to be working. Can I do this and if so then how do I do it? Here is an example of what I am trying to do. I would like the header of a standard page to be another tile so I can further divide it into pieces. However, when I try to create a definition that extends the .standardPage I get an error at the top of the page. It just says that there has been a ServletException in /WEB-INF/common/layouts/header.jsp. I understand that a tile cannot use attributes from subtiles or supertiles and I don't think that is the problem. tiles-definitions definition name=.standardPage path=/WEB-INF/common/layouts/standardLayout.jsp put name=title value=NO TITLE DEFINED / put name=std_jscript value=/WEB-INF/common/std-jscript.jsp / put name=header value=.standardPage.header / put name=footer value=/WEB-INF/common/footer.jsp / put name=content value=NO CONTENT DEFINED / /definition definition name=.standardPage.header path=/WEB-INF/common/layouts/header.jsp put name=tagline.left value=/WEB-INF/common/qsearch.jsp/ put name=tagline.right value=/WEB-INF/common/instBanner.jsp/ /definition /tiles-definitions Thanks, Kevin - 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]
