All,
So I tried 1) [Forging ahead with a 1.6 Snapshot...] and didn't get very
far after removing the SpringInterceptor (Interceptor.Classes param in
web.xml) as I then hit the DynamicMapping filter issue in 1.5.3 that
made me initially jump to 1.5.4 Snapshot... . After reluctantly putting
back the extra StripesFilter mapping junk I then hit some other
exception (w/ the NamingResolver) and started to realize that the fixes
in 1.5.4 have not made it into the trunk... . Not horribly surprising
as enhancements are usually merged into the trunk once they are stable
and set in the branch but nonetheless not a pleasant realization.
i.e. that although I can get nested Stripes Layouts to work by going
with a 1.6 Snapshot that I really am not that much better off than 1.5.3
save for perhaps an easier way to integrate w/ Spring but that isn't
relevant.
So I skipped 2) [Staying on 1.5.4 Snapshot but using another template
engine such as Tiles or SiteMesh] and went to 3) [Going back to 1.5.3...
stable... but not a desirable option in my case] and am hoping that some
day soon 4) [Waiting for this to be resolved in 1.5.4...] will occur.
Sucks to have to take steps backwards because of this but then I again I
knew full well that Stripes biggest weakness was its "low" active
development and community size... just hope I don't regret that
decision... .
Hope this info helps anyone else skirting with 1.5.3 and beyond... (at
this moment in time).
Cheers,
--Nikolaos
Nikolaos Giannopoulos wrote:
Ben,
First on the confusion: The JIRA ticket I filed is against "Release
1.5.4". I didn't label it as such but if it is confusing then perhaps
that needs to be remedied by perhaps renaming "Release 1.5.4" in JIRA
to "Release 1.5.x" or something. I fully understand 1.5.4 is not
released and that I am working with a snapshot of 1.5.X... and as such
refer to 1.5.4 as 1.5.4 Snapshot as much as possible (see subject line
of thread :-)
I now distinctly remember some reports of issues with testing nested
layouts with 1.5.4 Snapshot but didn't realize that those issues never
got resolved. I also am not surprised that you fatigued at looking at
the code as you were making quite a few updates back in May / June. I
for one am very much appreciative of all the efforts made by yourself
and the entire Stripe Developer team as overall I am quite happy with
both Stripes and Stripersist.
However there were reasons why we flipped over to using 1.5.4
Snapshots and those reasons pertained to issues with 1.5.3... one of
the more annoying being the IIRC Stripes Filter / Dispatcher null
pointer exception and duplicate web.xml coding that caused all sorts
of issues and was fixed in 1.5.4 Snapshot. Off the top of my head
there were other things that were resolved as well but I can't recall
them as its been quite a few months since.
Although both you and Freddy suggest flipping back to 1.5.3 to get
nested layouts to work the problem is that this suggestion can't be
taken in a vacuum... as it is taking a big step backwards with
everything else outside of Stripes Layouts i.e. in isolation stepping
back for working Stripes Layout functionality is wonderful but when
looking at the entire picture the recommendation is problematic.
So here are the options I see and in the order of most to least likely:
1) Forging ahead with a 1.6 Snapshot...
2) Staying on 1.5.4 Snapshot but using another template engine such as
Tiles or SiteMesh
3) Going back to 1.5.3... stable... but not a desirable option in my case
4) Waiting for this to be resolved in 1.5.4... sounds like this may
not be so trivial and who knows when this might occur
I think I am going to try 1) and then if that doesn't bode well move
to 2) which will be an unfortunate shame as I have used Tiles before
and liked what Stripes Layout had to offer in 1.5.x but its useless
for my project if it doesn't correctly support nested layout
functionality.
Thanks,
--Nikolaos
Ben Gunter wrote:
Nikolaos, let's not confuse things by calling this 1.5.4 since there
has been no 1.5.4 release yet. I am aware that nested components
don't work with that branch at the moment. To be frank, when I
realized that was a problem I had to step away from it for a while
because I had grown sick of looking at that code. It will be fixed
before 1.5.4 is released. In the meantime, I recommend sticking with
1.5.3 if the layout code from the branch doesn't suit your needs.
I will gladly use the sample JSPs you submitted with the JIRA ticket
for testing. I know there are others out there who have layout
examples that don't work with the 1.5.x branch. Please attach those
to the JIRA ticket, and I will use yours as well.
-Ben
On Sun, Aug 29, 2010 at 3:18 PM, Nikolaos Giannopoulos
<nikol...@brightminds.org <mailto:nikol...@brightminds.org>> wrote:
Feddy,
Thanks for testing it out and letting me know it isn't just me.
I'll write up a JIRA ticket ASAP.
As I am on a tight schedule and there haven't been any updates to
1.5.4 since the flurry of activity this past June I think I have
little choice but to take a snapshot of the 1.6 trunk. As such,
are there any gotchas that you could pass on with its current
state... I am using JPA / Stripersist quite heavily and plan on
using Stripe Layouts heavily as well for a production app. Any
pitfall pointers would be appreciated.
Also have the flurry of enhancements in June made it to 1.6 or
where they already there... thinking of the "streaming" Layout
stuff that Ben put in... .
Thanks,
--Nikolaos
Freddy Daoud wrote:
Either something is "seriously" broken with Nested Layout Components in
1.5.4 OR I am "seriously" confused.
Well, I can tell you that your example works as expected with 1.5.2
and with the trunk. I think you are correct -- something is broken
in the 1.5.x branch. I don't get the (unexpected) output that you
mentioned; rather, I get this exception:
java.lang.NoSuchMethodError:
net.sourceforge.stripes.tag.layout.LayoutRenderTag.doAfterBody()I
org.apache.jsp.test_jsp._jspx_meth_s_005flayout_002drender_005f0(test_jsp.java:139)
org.apache.jsp.test_jsp._jspService(test_jsp.java:81)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
Either way, looking at the SVN log, work was done on the layout
tags in 1.5.4 which may have caused the issue that you encountered.
Please open a JIRA ticket.
Cheers,
Freddy
------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of
netbook users
worldwide. Take advantage of special opportunities to increase
revenue and
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
<mailto:Stripes-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/stripes-users
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users