Hi,
I am using DynaActionForm, one of the form bean property is a indexed
type.
I can not specify the size attribute for this property I am keeping this
form bean in Session scope.
When I submit to an action class, it is working fine, after submitting
to the action, if I refresh the JSP
[
http://issues.apache.org/struts/browse/STR-2388?page=comments#action_37385 ]
Ralf Hauser commented on STR-2388:
--
see also SB-20 for enum support
> [taglib] enhance bean:write with optional "timezone" attribute if property
> data is a Date type
> ---
[
http://issues.apache.org/struts/browse/STR-2435?page=comments#action_37384 ]
Ralf Hauser commented on STR-2435:
--
see also SB-20
> [taglib] enhance bean:write with a "decorator" attribute for tailored
> formatting
> --
[
http://issues.apache.org/struts/browse/STR-1892?page=comments#action_37383 ]
Ralf Hauser commented on STR-1892:
--
see also STR-2435 and SB-20
> timezone support for bean:write tag
> ---
>
> Key: STR-1892
>
Of course this is what Craig wanted the whole time. Lord! And, it is what
the rest of the world has been trying to avoid. Now, it comes again in the
back door. Don't any committers know where the front door is?
On 5/21/06, Don Brown <[EMAIL PROTECTED]> wrote:
In the Action 2 approach, you s
Since Kito is committed and has been to JSF Central, why pretend that he
needs to know about this. These are like those paid 1 hour commercials we
have to put up with on Sunday mornings that attempt to distort the truth.
Give us a break.
On 5/21/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
Are there any figures on this market junk? Or is this more Bush-Speak, lies
to get someone thinking your way?
On 5/21/06, Kito D. Mann <[EMAIL PROTECTED]> wrote:
Congrats, Don! I'm very encouraged, and I'm anxious to check it out. This
will allow SAF2 developers to work with JSF components (an
Sounds like Ted. Let me say that anyone that says web services is a
half-baked CICS is really not worth listening to. That is ridiculous. I am
really amazed at the nutty things said on this list. If you think that web
services is coincident with SOA that is equal madness. Do you guys think
th
In the Action 2 approach, you should be able to use any feature of
Shale, or any other JSF extension, that doesn't involve a custom
NavigationHandler, since that is overridden to defer to Action 2-style
navigation, or a custom Lifecycle. By leaving JSF alone otherwise, you
should be able to us
I've opened SB-21 to take a look at the multiple Tiles taglib
attributes that seem to mean the same thing. I can't find the
original discussion, but I remember at one point talking about
consolidating these to a single attribute.
Does anyone remember that discussion, or have an opinion either wa
On 5/21/06, Kito D. Mann <[EMAIL PROTECTED]> wrote:
Congrats, Don! I'm very encouraged, and I'm anxious to check it out. This
will allow SAF2 developers to work with JSF components (and the market is
growing nicely).
I wonder how well Shale will run in this context...
Don and I had a chance
Congrats, Don! I'm very encouraged, and I'm anxious to check it out. This
will allow SAF2 developers to work with JSF components (and the market is
growing nicely).
I wonder how well Shale will run in this context...
~~~
Kito D. Mann
>From: "Dakota Jack" <[EMAIL PROTECTED]>
>
> Of course you aren't, Gary, because my panties are not in a bunch.
> You are the one with his panties in a bunch because you are here for
> JSF and JSF alone anyway and you don't like me having pointed out that
> your contributions did not merit your
Of course you aren't, Gary, because my panties are not in a bunch.
You are the one with his panties in a bunch because you are here for
JSF and JSF alone anyway and you don't like me having pointed out that
your contributions did not merit your status. You can side with
Kamini if you like, but sh
>From: "Dakota Jack" <[EMAIL PROTECTED]>
>
> You are right, for once. I only speak for myself. Those who are
> unwilling to listen to others are condemned by their own choice to a
> life of ignorance.
>
Sheese, sorry this got your panties in a bunch.
> On 5/21/06, Kimani Darisha wrote:
> >
Like I said before, use Shale to fork from, adding the JSP to it. (or if
shale adds JSP tags, no reason for SAF2).
.V
Jason Carreira wrote:
I think it's interesting to think of the JSF lifecycle as a particular profile
of our interceptor lifecycle. Similarly, the Portlet support is a diff
On 5/21/06, Jason Carreira <[EMAIL PROTECTED]> wrote:
Wendy, will this create the IDEA modules with all dependencies for extras and
showcase? Are all of the jars downloading now? I had to fix this by hand on the
plane yesterday, so I don't want to blow them away if I have to do it again.
If
Wendy, will this create the IDEA modules with all dependencies for extras and
showcase? Are all of the jars downloading now? I had to fix this by hand on the
plane yesterday, so I don't want to blow them away if I have to do it again.
> Be sure to update and install from the top level of
> Actio
On 5/21/06, Rainer Hermanns <[EMAIL PROTECTED]> wrote:
Otherwise, I think the showcase webapp can now be included in the default
build.
Thanks! The snapshots are updated, and now include the showcase:
http://people.apache.org/maven-snapshot-repository/org/apache/struts/action2/
To update t
It is acceptable to distribute CDDL code in binary form, so RIFE isn't a
problem.
Don
Rainer Hermanns wrote:
Regardless, showcase should be split up so we can ship a functional app
with no LGPL problems.
Don, I just removed the deps on JasperReports which were the last real
LGPL code dep
On 5/21/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
Once the LGPL-dependent examples are removed from the showcase, it can
be part of the normal build, and the 'extras' profile can build both
struts-extras.jar and a separate extras example app.
... which would put us right back in the original
> Regardless, showcase should be split up so we can ship a functional app
> with no LGPL problems.
Don, I just removed the deps on JasperReports which were the last real
LGPL code dependency. However, there is still an example with
continuations based on RIFE. Since RIFE is dual licensed (CDDL and
You are right, for once. I only speak for myself. Those who are
unwilling to listen to others are condemned by their own choice to a
life of ignorance.
On 5/21/06, Kimani Darisha <[EMAIL PROTECTED]> wrote:
To anyone following these thread, please ignore this fool. He does
not speak for anyone
This post shows who the limited person is. It is you, Ma'am.
On 5/21/06, Kimani Darisha <[EMAIL PROTECTED]> wrote:
Oh wonderful, more comments from the list idiot.
K.
On 5/21/06, Dakota Jack <[EMAIL PROTECTED]> wrote:
> Who wants these frameworks combined? This is what has been killing Strut
On 5/21/06, Don Brown <[EMAIL PROTECTED]> wrote:
This is an interesting question - do we want to include pre-built
example webapps that are missing their LGPL deps? Or, would it be
better not to build them at all?
Regardless, showcase should be split up so we can ship a functional app
with no
Cool! Thanks :)
Frank
Don Brown wrote:
You can inherit packages and their defined defaults. Therefore, in this
case, you could define the default interceptor stack and result type for
a root package then not have to specify it in any action configs of that
package or child packages.
Don
Agreed. Are we going to move XWork to Subversion for 2.0 or stick with
CVS for now?
Don
Jason Carreira wrote:
So on the plane home I was able to get some work done. Well, first I had to set
up lots of libraries for the extras and showcase modules, since maven didn't
set them up, but then I
You can inherit packages and their defined defaults. Therefore, in this
case, you could define the default interceptor stack and result type for
a root package then not have to specify it in any action configs of that
package or child packages.
Don
Frank W. Zammetti wrote:
A bit of a tangent
Ted Husted wrote:
Struts Action 1 does not utilizes Spring, but SAF2 uses Spring as its
internal object factory by default, and, optionally, Shale can use
Spring as a factory for managed beans.
More precisely, SAF2 *can* use Spring as its internal object factory,
and that is indeed the recomme
A bit of a tangential question here... does Webwork support inheritance
of some sort with regard to Action mappings? Or perhaps some sort of
prototype? I think it's great that you can set things on a per-mapping
basis, that makes things very flexible and powerful... but one can
imagine where
Struts Action 1 does not utilizes Spring, but SAF2 uses Spring as its
internal object factory by default, and, optionally, Shale can use
Spring as a factory for managed beans.
-Ted.
On 5/21/06, Paul Benedict <[EMAIL PROTECTED]> wrote:
Struts does not have Spring as a dependency.
-
I am not opposed to having JSF and Action2 work together.
If they can play together, and you can find a business case to
parts of each in a project, I think that's a big win. As long
as they can still be used separately, then I am +1.
--- Bob Lee <[EMAIL PROTECTED]> wrote:
> Don, this is *very*
Frank W. Zammetti wrote:
I've been historically pretty anti-JSF, so I hope this means something
in light of that history: this is *very* interesting and I
congratulate you on making it happen! I've had the same "I think it
can be done" thoughts about mixing the two, just never actually did
an
Wendy Smoak wrote:
I published snapshots with 'mvn deploy':
http://people.apache.org/maven-snapshot-repository/org/apache/struts/action2/
What about 'extras'? It seems like the profile needs to be split up.
Right now if I do 'mvn deploy -P extras' it's going to upload the both
struts-extr
I published snapshots with 'mvn deploy':
http://people.apache.org/maven-snapshot-repository/org/apache/struts/action2/
What about 'extras'? It seems like the profile needs to be split up.
Right now if I do 'mvn deploy -P extras' it's going to upload the both
struts-extras.jar and the showcase
I've been historically pretty anti-JSF, so I hope this means something
in light of that history: this is *very* interesting and I congratulate
you on making it happen! I've had the same "I think it can be done"
thoughts about mixing the two, just never actually did anything with the
idea, so I
Jason Carreira wrote:
Great work Don! This is very cool. I've been saying we could do this for a long
time, but it's good to know I wasn't just making that up :-)
Heh, I know. After bragging about it after many beers at JavaOne, I
figured it was time to put up or shut up :)
I think it's
> Don, this is *very* interesting. Nice work. I've been
> wondering for a
> while if we could reuse off-the-shelf JSF components.
> It looks like
> you may have figured out how!
>
> It also proves that you can think of the JSF
> lifecycle as a more
> complex, higher level of abstraction of our
> i
Be sure to update and install from the top level of Action 2 to pick
up the changed artifactId.
svn up
mvn install -P extras
Also remove the old ide config files and re-generate them, for example
with IDEA:
rm project.i*
mvn idea:idea -P extras
--
Wendy
On 5/21/06, [EMAIL PROTECTED] <[EMAIL PRO
On 5/21/06, Jason Carreira <[EMAIL PROTECTED]> wrote:
So on the plane home I was able to get some work done. Well, first I had
to set up lots of libraries for the extras and showcase modules, since maven
didn't set them up, but then I got some work done. (BTW, can we get that
fixed, along with t
Hmmm, I added the Spring dependency to the POMs used by the
aplications on May 9 (r405529). I'm getting a general build failure on
my own checkout right now, so I can't verify whether it's bundling the
Spring JARs in the WARs, as it should. If it doesn't, for now, you may
need to drop the Spring J
Don, this is *very* interesting. Nice work. I've been wondering for a
while if we could reuse off-the-shelf JSF components. It looks like
you may have figured out how!
It also proves that you can think of the JSF lifecycle as a more
complex, higher level of abstraction of our interceptor lifecycl
Struts does not have Spring as a dependency.
--- Jason Lenhart <[EMAIL PROTECTED]> wrote:
> Thank you for your help. Sorry ... but I just want it to work ...
> and after 3 hours it gets a bit daunting and makes me just give up.
>
> I am just wondering why the spring web jar is not listed as a
To anyone following these thread, please ignore this fool. He does
not speak for anyone, and is only here to confuse people.
K.
On 5/21/06, Dakota Jack <[EMAIL PROTECTED]> wrote:
I have seen no "very popular need". This is like Bush-Speak. Baloney
parading as truth.
On 5/21/06, Don Brown <[
Oh wonderful, more comments from the list idiot.
K.
On 5/21/06, Dakota Jack <[EMAIL PROTECTED]> wrote:
Who wants these frameworks combined? This is what has been killing Struts.
This is anything but a lofty goal. It is architectural suicide. There is
Shale, which could not really do this. W
So on the plane home I was able to get some work done. Well, first I had to set
up lots of libraries for the extras and showcase modules, since maven didn't
set them up, but then I got some work done. (BTW, can we get that fixed, along
with the problems downloading libraries?)
So anyway, I did
Thank you for your help. Sorry ... but I just want it to work ...
and after 3 hours it gets a bit daunting and makes me just give up.
I am just wondering why the spring web jar is not listed as a
dependency on the wiki?
My guess is that the jar that houses this class is packaged in Jetty
I have seen no "very popular need". This is like Bush-Speak. Baloney
parading as truth.
On 5/21/06, Don Brown <[EMAIL PROTECTED]> wrote:
After talking with several on this list about the possibility of
combining the best of JSF and Action 2 in a unified framework from a
user perspective, I ha
Who wants these frameworks combined? This is what has been killing Struts.
This is anything but a lofty goal. It is architectural suicide. There is
Shale, which could not really do this. Why is that not enough or in fact
way too much? This is ridiculous. I hope people on this list see this
e
After talking with several on this list about the possibility of
combining the best of JSF and Action 2 in a unified framework from a
user perspective, I have completed a first cut at JSF support in Action
2 with this loftly goal.
From a user perspective, you still have one configuration file,
50 matches
Mail list logo
