Gerald Müllan schrieb:
Hi,
I like the idea of having an own attribute for the char encoding and
putting this value to the ajax request. We can set encoding type in
the phaselistener without waiting for the explicit call to the
component itself. Can be done right at the beginning and also
when enter a wrong url or file name, no action are available
Key: TOMAHAWK-446
URL: http://issues.apache.org/jira/browse/TOMAHAWK-446
Project: MyFaces Tomahawk
Type: Bug
Components: File Upload
[
http://issues.apache.org/jira/browse/TOMAHAWK-438?page=comments#action_12413076
]
Jurgen Lust commented on TOMAHAWK-438:
--
Hmm, apparently you did not update the sandbox examples, could you test your
changes on the provided examples, and then also
Hi Sean!
It looks like the key guys are rather busy these days.
What is the current plan and what do we do for current users? Do we
need an
intermediate release that addresses things in a backwards compatible
way?
The current tomahawk head is fixed in a way, that the dummyForm stuff is
There is no 1.1 compliant way of fixing dummyform - there just isn't.
I would have gone with a single branch for 1.2 and checking in TC5.5
compatible stuff only, but Stan has already worked on 1.2, and he has
implemented also TC6 depending things, so no chance to go with this,
except we want to
So does this mean that our Tomahawk releases are no longer compatible
with the RI? That's our current problem right?
Sean
On 5/24/06, Martin Marinschek [EMAIL PROTECTED] wrote:
There is no 1.1 compliant way of fixing dummyform - there just isn't.
I would have gone with a single branch for
No. The current build should be compatible again - if I don't have old
information here...
regards,
Martin
On 5/24/06, Sean Schofield [EMAIL PROTECTED] wrote:
So does this mean that our Tomahawk releases are no longer compatible
with the RI? That's our current problem right?
Sean
On
OK so the only issue with Tomahawk head is that people need to add
h:form around there components right? That will be a pain for users
who are in production but I guess its the best we can do. Do we need
a new core release or is this just tomahawk only? If you think we are
ready I will create
Hi!
OK so the only issue with Tomahawk head is that people need to add
h:form around there components right?
Or - if they use myfaces-impl too - to add some text to their own
faces-config.xml
Do we need a new core release or is this just tomahawk only?
I wont put my mother on it, but I guess
If it's going to be as simple as adding some config to the config file to retain backward compatibility, I'm +1 on releasing with that. If it means adding h:form I'm MOST DEFINITELY -1. We certainly cannot foist this onto our users.
On 5/24/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi! OK so
Or - if they use myfaces-impl too - to add some text to their own
faces-config.xml
This is to be added to the faces-config.xml in tomahawk right? And we
can't add it for them because it will break if they are using myfaces
core? Or is this added to faces-config.xml in their own personal
OK so Stan is past the TC 5.5 point. Why do we need two branches?
Can't we just say that 1.2 depends on TC 6.0 or Glassfish? I still
think we need to do everything we can to avoid multiple branches.
Sean
On 5/24/06, Martin Marinschek [EMAIL PROTECTED] wrote:
No. The current build should be
Please no multiple branches. Thanks.
Dennis Byrne
-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 24, 2006 12:56 PM
To: 'MyFaces Development', [EMAIL PROTECTED]
Subject: Re: JSF 1.2 [was: Cancelled: JavaOne MyFaces Committers/Contributors
meeting]
@Sean: It's easy - I won't put in the work to do it if I can't work
with the version I have at hand. And I can't work with it when it
relies on TC6.0 (and I won't switch over to Glassfish right now). I
guess that I'll not be the only one.
It's as easy as that. I promise to be the one to do the
@Dennis, you don't see the necessities to start with the major
features of the 1.2 implementation right now, even when TC 6.0 is not
yet available?
Yes, 1.2 is important. But I am under the impression I can use facelets until
TC 6 is released. Besides, most of the work I do in core is in Junit
@Martin,
How are you planning to separate the TC 5.5 stuff and TC 6 stuff if
Stan has already done the bulk of the JSF 1.2 work necessary? I agree
that current Tomcat users will likely stick with Tomcat (I know that's
my plan) but to me it seems like the most useful JSF 1.2 stuff is the
content
until TC 6 is released. Besides, most of the work I do in core is in Junit
rather than a container.
if it is just the availability of jsp 2.1 jars, the jetty folks have
their own (public) maven2 repo
-Matthias
For the record, I'm ok with core 1.2 on the trunk and moving core 1.1
to a branch for bug fixes. In fact I recommended this a while ago but
I don't remember hearing a lot of support for that idea.
Let's split the problem in two.
@devs - if you are do not agree with 1.2 on trunk, please speak up
Calendar should ommit next month, prev month ( and ) when readonly is set to
true in non-popup mode.
--
Key: TOMAHAWK-447
URL: http://issues.apache.org/jira/browse/TOMAHAWK-447
Hi!
+1 for branching the current trunk to a core1.1
+1 for working with jsf 1.2 tc5 on the new trunk
+1 to allow Stan to commit its work to a core1.2tc6 branch
whatever we do with this branch, we wont loose Stans work and it will be
best to have it in svn.
Whenever we decide to move our focus
MyFaces Portlet at Weblogic 8.1 SP5: Request Parameter weren't submitted
Key: MYFACES-1311
URL: http://issues.apache.org/jira/browse/MYFACES-1311
Project: MyFaces Core
Type: Bug
Versions:
As far as I can see, we never ever try to release a version out of the
1.2tc6 branch. So no need to do any special maintainance with this
branch - just an archive.
This part confuses me. I was under the impression that Stan was 90%
of the way there. So why would we plan on abandoning this
On 5/24/06, Sean Schofield [EMAIL PROTECTED] wrote:
As far as I can see, we never ever try to release a version out of the 1.2tc6 branch. So no need to do any special maintainance with this branch - just an archive.This part confuses me.I was under the impression that Stan was 90%
of the way
Do we have an ETA on Tomcat 6?
Sean
On 5/24/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 5/24/06, Sean Schofield [EMAIL PROTECTED] wrote:
As far as I can see, we never ever try to release a version out of the
1.2tc6 branch. So no need to do any special maintainance with this
What is the code exactly? I want to use it in the ultimate release
notes, website and email announcement for the next tomahawk version.
Sean
On 5/17/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
So, for now I removed the renderer override in faces-config.xml so parts
of tomahawk should work
dependency injection error with ArrayList
-
Key: MYFACES-1312
URL: http://issues.apache.org/jira/browse/MYFACES-1312
Project: MyFaces Core
Type: Bug
Components: JSR-127
Versions: 1.1.3
Reporter: Rogério
[
http://issues.apache.org/jira/browse/MYFACES-1312?page=comments#action_12413200
]
Rogério Pereira Araújo commented on MYFACES-1312:
-
i'm using saveState in beanA
dependency injection error with ArrayList
Hi ,
how can i dynamically add node to my tree when i click on the parent node
1.e
parent
child1
child2
child3
the node i am bringing it from database table treedata
when i inserted child4 in my database table treedata and commited
and i clicked on parent
parent
28 matches
Mail list logo
