[ 
http://www.stripesframework.org/jira/browse/STS-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12169#comment-12169
 ] 

Nick Stuart commented on STS-788:
---------------------------------

Of course you went and fixed that after I changed all my jsps around!  :)   
(layouts not being outermost tags)

But really, thanks for all the work Ben! My main issue of the jsp:include works 
fine now, and I can test out the inner layouts at some point as well.

Here's why I was using the 'inner' layouts to begin with, maybe we can come up 
with a better solution. Basically, I was using it for small, shared 
'components' that can be used all around our app. The main reason I was using 
the layout tag, and a simple 'jsp:include' is because the layout tag lets you 
pass in any parameters you like and have them set in the page context of the 
layout which is really handy. jsp:include forces you to use <c:set/> before and 
set it to 'request' scope so the variable is visible on the page being 
included. It works, but just seems messier to me.

So I was really using it to get around complete lack of 'components' or 
templates in JSP itself. I know their are jsp fragements, but those act weird 
and not fully comfortable using them for our needs.

Any thoughts?


> Layout issues after upgrade from 1.5.3
> --------------------------------------
>
>                 Key: STS-788
>                 URL: http://www.stripesframework.org/jira/browse/STS-788
>             Project: Stripes
>          Issue Type: Bug
>          Components: Tag Library
>    Affects Versions: Release 1.5.4, Release 1.5.5
>         Environment: jetty-6.1.15, Java(TM) SE Runtime Environment (build 
> 1.6.0_22-b04-307-10M3261)
>            Reporter: David Dundua
>            Assignee: Ben Gunter
>             Fix For: Release 1.5.5, Release 1.5.6
>
>         Attachments: example.tar.gz, stripes-bug-2.zip, stripes-bug-3.zip, 
> stripes-bug.zip
>
>
> Guys, I have a couple of layout scenarios which stopped working after 
> upgrading to 1.5.4.  I have created a couple of test cases demonstrating 
> these issues.   I am attaching maven2 project.
> 1. mvn jetty:run
> 2. http://localhost:8080/stripes-bug  
> 3. take a look at the output of each test under 1.5.4
> 4. change the stripes dependency to 1.5.3
> 5. mvn clean jetty:run 
> 6. observe the difference in the output

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
Gaining the trust of online customers is vital for the success of any company
that requires sensitive data to be transmitted over the Web.   Learn how to 
best implement a security strategy that keeps consumers' information secure 
and instills the confidence they need to proceed with transactions.
http://p.sf.net/sfu/oracle-sfdevnl 
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development

Reply via email to