Hi!
I'm planning to promote s:selectItems to tomahawk. Component satisfies
all of the requirements needed for promotion.
+1
Ciao,
Mario
+1
we already have been using this component in production for some time
without any issues
Manfred
On 11/26/06, Cagatay Civici [EMAIL PROTECTED] wrote:
Hi,
I'm planning to promote s:selectItems to tomahawk. Component satisfies all
of the requirements needed for promotion.
Regards,
Cagatay
Hi,
i didn't know this component before, looks very usefull.
I prefer to have this in the new commons project, to enabel the use in
non tomahawk applications e.g. tobago. There is no renderer specific
stuff involed?
Regards,
Volker
2006/11/26, Cagatay Civici [EMAIL PROTECTED]:
Hi,
I'm
+1
and yes, Volker, no rendering specific stuff involved.
regards,
Martin
On 11/27/06, Volker Weber [EMAIL PROTECTED] wrote:
Hi,
i didn't know this component before, looks very usefull.
I prefer to have this in the new commons project, to enabel the use in
non tomahawk applications e.g.
+1
On 27/11/06, Martin Marinschek [EMAIL PROTECTED] wrote:
+1
and yes, Volker, no rendering specific stuff involved.
regards,
Martin
On 11/27/06, Volker Weber [EMAIL PROTECTED] wrote:
Hi,
i didn't know this component before, looks very usefull.
I prefer to have this in the new commons
that would be great;
from what I got out of that commons thread is that they wanna have
*common utils* in that jar first. no response to the adding
validators/converters proposal so far.
Only Bernd had also something similar (security;fileupload,...)
-M
On 11/27/06, Volker Weber [EMAIL
Move sandbox selectItems to Tomahawk
Key: TOMAHAWK-805
URL: http://issues.apache.org/jira/browse/TOMAHAWK-805
Project: MyFaces Tomahawk
Issue Type: Task
Affects Versions: 1.1.4-SNAPSHOT,
[
http://issues.apache.org/jira/browse/TOMAHAWK-775?page=comments#action_12453562
]
Oliver Pfau commented on TOMAHAWK-775:
--
With the nightly build from today (27.11.2006) the exception of multiple ids
doen't occur anymore.
Duplicated
submittedValue of selectOneMenu is set to an instance of
org.apache.myfaces.shared_impl.renderkit.RendererUtils ???!!!
--
Key: TOMAHAWK-806
URL:
Even if there is no renderer specific stuff involved, this goody is
quite component like. Particularly the tag definition is the thing
that makes it diffult to integrate into commons. We should not have
another TLD in commons with another recommended prefix (c ?!).
Wouldn't that be really
Why not having a commons-component library?
For converters and validators we neet also another TDL with another prefix.
I prefer to follow Bernds suggestion of having multiple commons artifacts.
Alternativly we can put all tag-components
(components/converters/validators/...?)
together into a
Hi,
my +1 to Bernds suggestion of having separated commons packages.
And to move the discussion back to this thread:
If we want to include converters/validators and components into the
new common,
than we need to have new TLDs with new prefixes here.
Regards,
Volker
2006/11/25, Bernd Bohmann
IMO, instead of having different incompatible component libraries
depending on the same abstract classes I would fight to have
completely compatible libraries, so a component in tomahawk could be
used everywhere instead of having different implementations of the
same abstract class. However, I
AFAIK tomahwk is a html renderkid library.
AFAIK jsf is not restricted to render html output.
Why not having renderer independend stuff in a own library to enable
use in applications which render pdf/flash/svg/or whatever
jsf-api is spitted into core and html because of this. And users have
to
Yes, and therefore I propose to keep this new commons thingy as simple
as possible.
That means: No abstract monster classes for different component libs,
no complex component like goodies. Shared is responsible for the
former, tomahawk (or any other component set lib) is responsible for
the
Hello Manfred,
i don't understand you. What is wrong to move all the common renderkit
stuff to a common package. This does't keep you to include this tag in
the tomahawk tld.
Here is my
+1 for moving to tomahawk
and
+1 for moving in a common whatever artifact.
and
+1 for starting a
Ok, now I do not understand anything anymore as well... :-)
Seems, like we got our wires crossed.
What is your exact proposal for the s:selectItems stuff. Moving it to
both tomahawk as well as commons means what?
Having a t:selectItems in tomahawk together with a
This are two related threads,
Cagatay wants to promote the component into tomahawk.
Some (at least me) want to have the component in a renderkid indepenend commons.
I don't like to put it now into tomahawk and next month (or so) from
tomahawk into the new commons.
If we decide to have
Yes, d'accord!
I agree with Zubin that these are two different pairs of shoes.
+1 for moving s:selectItems out of the tomahawk(!) sandbox to tomahawk core
Let's keep an eye on a future
alltogether-compatible-with-everything-components-set but do not not
mix up with the commons jsf utils package
Are you using Facelets?
If yes:
You have to register a handler-class in the tomahawk.taglib.xml:
tag
tag-nametabChangeListener/tag-name
handler-classfacelets.TabChangeListenerHandler/handler-class
/tag
And then include the Handler Class with in your libraries:
/*
* Copyright
[
http://issues.apache.org/jira/browse/TOMAHAWK-620?page=comments#action_12453643
]
Jocelyn Carfantan commented on TOMAHAWK-620:
The problem seems that if not using UTF-8 as character-encoding, the
javascript 'text' is encoded
javax.faces.FacesException: InValid to flush BodyContent: no backing stream
behind it
-
Key: MYFACES-1501
URL: http://issues.apache.org/jira/browse/MYFACES-1501
documentBody needs id, style and styleClass attributes
--
Key: TOMAHAWK-807
URL: http://issues.apache.org/jira/browse/TOMAHAWK-807
Project: MyFaces Tomahawk
Issue Type: Improvement
[ http://issues.apache.org/jira/browse/TOMAHAWK-807?page=all ]
Anil Kommareddi updated TOMAHAWK-807:
-
Status: Patch Available (was: Open)
documentBody needs id, style and styleClass attributes
[
http://issues.apache.org/jira/browse/TOMAHAWK-590?page=comments#action_12453785
]
Robert Wilkinson commented on TOMAHAWK-590:
---
Unless of course you would really like to use this product in production and
not just as a development
We are a little behind on plugin versions for Selenium and HostedQA. I am
bring this up
because :
1) I am seeing failures on the HostedQA's site that I do not see when running
the same test locally.
2) Sometimes mvn package -P hostedqa fails when all of the results are
Passed.
3)
[
http://issues.apache.org/jira/browse/TOMAHAWK-803?page=comments#action_12453804
]
Bruno Marti commented on TOMAHAWK-803:
--
Issue/Correction has been tested on nightly build of 28-Nov-2006.
Works fine.
Thanks for quick fixing.
27 matches
Mail list logo
