thanks for your reply. i already solved the problem.
I missed something that it is said in this site:
http://getahead.ltd.uk/dwr/getstarted
The new creator that we used above uses the public no-args constructor that
all JavaBeans must have
the class ListaLocalidadSqlMapDao had this
Toby's done most of the work with the snippet plugin so far, though
I'm looking forward to making good use of it in the tutorials, and to
document some of our shiney new classes :)
My main concern right now is exporting the wiki to HTML. Do we use a
macro or other utility to do this at OS? I've
Pat, Ted,
I am having problem letting snippet display properly. Have a look at
http://confluence.twdata.org/display/WW/web.xml for examplÄ— The snippet doesn't
display properly.
Are any others experiencing this as well? Is it because the license for that
confluence has expired?
Thx in
Ted,
Good list. The two I would add as important to add from the Rough Spots are:
Gabe #2 *only* the part about removing '#' and putting / setting all variables
on the value stack, not the deprecation of the push tag. Also here:
http://jira.opensymphony.com/browse/XW-329
I think we should
Greg Reddin ha scritto:
As long as your layout is completely defined in one JSP page this will
all work. It breaks down if your layout has separate pages for
header, footer, etc. See below:
definition name=tileA path=/layout.jsp
put name=header value=/header1.jsp/
put name=headerGraphic
Yep, that's come up before. Personally, I don't like the idea.
Think about how complicated that could become with nested, nested
defs. I'd prefer better support for including other definitions as a
tile attribute. Maybe that support is there already and i just
haven't tried it.
Greg
Thanks Patrick, I'm interested to see how this will go, any light that
Bob could shed would be useful.
dave
On Wed, 2006-06-07 at 11:23 -0500, Patrick Lightbody wrote:
Dave,
I think you are thinking about this the same way we are. Bob Lee and I agreed
when we met up during JavaOne that there
Atlassian gave us an open source license to use, so it's not expired.
-Ted.
On 6/8/06, tm jee [EMAIL PROTECTED] wrote:
Pat, Ted,
I am having problem letting snippet display properly. Have a look at
http://confluence.twdata.org/display/WW/web.xml for examplÄ— The snippet doesn't
display
From: Greg Reddin [EMAIL PROTECTED]
Yep, that's come up before. Personally, I don't like the idea.
Think about how complicated that could become with nested, nested
defs. I'd prefer better support for including other definitions as a
tile attribute. Maybe that support is there already and
The root issue is how to handle optional interceptors. Currently, I believe we
do print out stack traces, but only at a debug level, and the processing of the
configuration continues.
I'd like to be able to include optional interceptors in the struts-default.xml
file, as it makes it easier
The Jasper result was in fact transitioned to Struts Action 2, however, it was
moved to the extras module. ASF is ok with us shipping code that depends on
LGPL jars as long as:
1. The jars aren't included in our distribution
2. The default build doesn't automatically retrieve the jars
3.
On 6/7/06, Wendy Smoak [EMAIL PROTECTED] wrote:
The Shale Blank app is now set up to run its integration tests.
http://svn.apache.org/viewvc?rev=412639view=rev
The includes/excludes are working (thanks David!) and we're using the
Cargo Java API to start and stop Tomcat. (Yesterday's
I've been working on adding support in Strecks
(http://strecks.sourceforge.net/) for the chained request processor,
that is, ComposableRequestProcessor. On the whole, the job has been
pretty straightforward. I have had to tweak a couple of the interfaces
so that they map one to one with
I have a couple of questions/thoughts/observations that have arisen:
- the chain configuration appears to apply across the application as
a whole rather than per module. This differs from the 1.2 request
processor which can be varied/subclassed on a per module basis. (Of
course, you can still
\On 6/8/06, Craig McClanahan [EMAIL PROTECTED] wrote:
I've seen that convention, but have a question for you ... since the unit
tests for webapps built from these examples are going to use the mock
objects in the Shale Test Framework anyway, what would you think of having a
convenience abstract
I was just flipping through some Yahoo widgets, and I came across this:
http://widgets.yahoo.com/gallery/view.php?widget=38936
Thought you all might be interested, if you weren't aware of it already.
Frank
--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
The webwork renaming issue goes deeper than just those 3 or so files
and affects things like template variables, the static resources
prefix, the dojo package, etc. Currently, they have all be renamed to
'struts' consistently, however if we switched to 'struts-action' or
even 'action', I'm not
17 matches
Mail list logo