Looks like shale-tiles needs to be refactored to use TilesContext.
If no one takes care of it first I'll look at it when I get home.
Greg
On May 27, 2006, at 8:52 PM, Wendy Smoak wrote:
I'm not able to compile Shale Tiles against the latest Standalone
Tiles code, but it works with
Is the shopping cart app using JSF? I thought Don only added it to
the showcase.
I think it is because some of the interceptors defined struts-default.xml is
using JSF stuff, SAF2 will throws exception when loading the interceptors that
requires JSF dependencies.
rgds
- Original Message
Thanks guys... quick update... I took yesterday off, so I'm not quite as
far as I would have liked :) It *is* memorial day weekend after all!
However, I did on Friday get reasonably far... at this moment, I have
XML input working for simple (i.e., non-collection) Action fields, as
well as
Is the shopping cart app using JSF? I thought Don
only added it to
the showcase.
I think it is because some of the interceptors
defined struts-default.xml is using JSF stuff, SAF2
will throws exception when loading the interceptors
that requires JSF dependencies.
I just broke the JSF
On 5/27/06, Ian Roughley [EMAIL PROTECTED] wrote:
I have that very talk that I am doing on the No Fluff Just Stuff - I was
considering submitting it myself.
Hmmm, I was thinking in terms of a one or two day tutorial, rather
than a paper. I already have a straight-up WebWork2/SAF2 training
To get developer traction, can we begin posting beta builds
onto the website? It would be nice to see a 1.3.5 (Beta)
link listed there to view the snapshot website. And why not?
As long as we listd it as not a production build, we can
give it publicility. We have done that with Struts 1.2.x,
so if
Hi Wendy, sorry that I've been non-existent for the last few weeks.
I basically do not have internet access while onsite at my newest
client. I'm hoping to change that very soon though so I'll be able
to get back into the mix.
--
James Mitchell
On May 27, 2006, at 10:40 PM, Wendy
Wendy posted a snapshot to get some preliminary feedback.
* http://www.mail-archive.com/dev%40struts.apache.org/msg22386.html
If Joe's issue is resolved, then the next step would be to tag the
repository, roll the build, and post a release vote. If the vote gets
at least three binding +1s and
The documentation for the 'errorKey' attribute of all the html taglib tags says:
Name of the _request_ _scope_ bean under which our error messages have
been stored. If not present, the name specified by the
Globals.ERROR_KEY constant string will be used.
Is that still correct? I'm thinking of
On 5/29/06, Wendy Smoak [EMAIL PROTECTED] wrote:
The documentation for the 'errorKey' attribute of all the html taglib tags says:
Name of the _request_ _scope_ bean under which our error messages have
been stored. If not present, the name specified by the
Globals.ERROR_KEY constant string will
On 5/28/06, Niall Pemberton [EMAIL PROTECTED] wrote:
Yes it is related and will look in session scope if not found in
request scope - basically its the same as the name attribute on the
html:errors and html:messages tags - they all use
TagUtils.getActionMessages() to retrieve the messages which
Ted,
I am asking about the website, not the builds. I know the developer
builds are always available, but I see no reason why we shouldn't
publish the 1.3.x website on the left-hand bar as we release new
beta versions. We don't need a vote for that.
Paul
--- Ted Husted [EMAIL PROTECTED] wrote:
At 10:57 PM -0400 5/28/06, Ted Husted wrote:
Wendy posted a snapshot to get some preliminary feedback.
* http://www.mail-archive.com/dev%40struts.apache.org/msg22386.html
If Joe's issue is resolved
These two commits cover the things that I knew were issues.
Change your line html:text name=familylist property=rPart[0].repair/
to
html:text name=familylist property=rPart[0].repair readonly=true/
For ur reference
http://struts.apache.org/struts-doc-1.2.7/userGuide/struts-html.html#text
The problem with your bean:write tag could be it doesn't accept
On 5/28/06, Paul Benedict [EMAIL PROTECTED] wrote:
Ted,
I am asking about the website, not the builds. I know the developer
builds are always available, but I see no reason why we shouldn't
publish the 1.3.x website on the left-hand bar as we release new
beta versions. We don't need a vote for
On 5/28/06, Joe Germuska [EMAIL PROTECTED] wrote:
These two commits cover the things that I knew were issues.
http://svn.apache.org/viewvc?view=revrevision=409443
Thanks, Joe. Was there a JIRA issue opened for this one? (It won't
appear in the release notes otherwise.)
There are still a
* Link it to an Apache server (where Wendy's test build is) and
suffer the wrath of the Apache infrastructure group when a huge
number of people try to download it -- given how widely Struts
is used, this is likely to be a very serious hit on the Apache
infrastructure.
* Publish the release
On 5/28/06, Joe Germuska [EMAIL PROTECTED] wrote:
btw, considering my last email, I should point out that Wendy's test
build predates those two commits I made, so either 1.3.5 should be
rebuilt, or it should be skipped. In my mind, 1.3.5 has not been
released yet, and Wendy's test build could
18 matches
Mail list logo
