???
the correct address definitely is: [EMAIL PROTECTED]
--Manfred
On 6/12/07, Grant Smith [EMAIL PROTECTED] wrote:
Ooops.. I mean: myfaces-user, not user :)
On 6/12/07, Grant Smith [EMAIL PROTECTED] wrote:
It should be users , not user.
On 6/12/07, Jan Linders [EMAIL PROTECTED]
yes,
there was a typo in trinidad, already fixed.
users is fine, but there WAS user (with ending s)..
On 6/13/07, Manfred Geiler [EMAIL PROTECTED] wrote:
???
the correct address definitely is: [EMAIL PROTECTED]
--Manfred
On 6/12/07, Grant Smith [EMAIL PROTECTED] wrote:
Ooops.. I mean:
[
https://issues.apache.org/jira/browse/TOMAHAWK-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manfred Geiler resolved TOMAHAWK-1021.
--
Resolution: Duplicate
TOMAHAWK-983
CVE-2007-3101
-
[
https://issues.apache.org/jira/browse/TOMAHAWK-983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504163
]
Manfred Geiler commented on TOMAHAWK-983:
-
Thanks rajat for submitting this issue.
Sorry for the delay. A
Hi,
I was running the needed tasks to get the 120 release of the Trinidad
MyFaces Plugins out. This is the first release of the 1.2 plugins.
The artifacts are deployed to my private Apache account ([1]).
Please take a look at the 1.2.0 artifacts and vote
+1
On 6/13/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi,
I was running the needed tasks to get the 120 release of the Trinidad
MyFaces Plugins out. This is the first release of the 1.2 plugins.
The artifacts are deployed to my private Apache account ([1]).
Please take a look at the
+1
On 13/06/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
+1
On 6/13/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi,
I was running the needed tasks to get the 120 release of the Trinidad
MyFaces Plugins out. This is the first release of the 1.2 plugins.
The artifacts are deployed
[
https://issues.apache.org/jira/browse/TOMAHAWK-983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manfred Geiler resolved TOMAHAWK-983.
-
Resolution: Fixed
Cross-site scripting in autoscroll parameter
I just started since
a) MyFaces core needs this release as well
b) not hard to come up with a 1.2.1 very soon, in case of...
-M
On 6/12/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi,
the 1.0.1 is kind of released (not yet mirrored), so time to move forward.
Trinidad 1.2 plugins are
Hello,
thanks for pointing me this expected behaviour of UIInput.
To resume situation,
(1) tabbed pane should call the processValidators of each of his child
according to specs (which it does not right now)
(2) tabbed pane should, however, keep backward compatibility with old
behaviour to not
While you are releasing - would you mind to include the
maven-prototypes of both MyFaces and Trinidad (your babies ;) in the
list?
regards,
Martin
On 6/13/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
I just started since
a) MyFaces core needs this release as well
b) not hard to come up
[
https://issues.apache.org/jira/browse/TOBAGO-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504180
]
Guido Dubois commented on TOBAGO-394:
-
Have you an example for this?
Link should support confirmation facet
I have no clue, what you are talking about.
Are you talking about the Maven-Faces-Plugin ?
That is part of the *bundle*. And I pinged Bruno since
I want to make sure we release the plugin, that was used for working
on MyFaces 1.2
-M
On 6/13/07, Martin Marinschek [EMAIL PROTECTED] wrote:
While
Tab switching fails if selectedIndex is vb and first tab rendered=false
---
Key: TOBAGO-421
URL: https://issues.apache.org/jira/browse/TOBAGO-421
Project: MyFaces Tobago
The Apache MyFaces team is pleased to announce the release of MyFaces
Tomahawk 1.1.6.
Please note: This release is a security update that fixes a severe
cross-site scripting vulnerability when using the autoscroll feature
(CVE-2007-3101).
MyFaces Tomahawk provides a series of JavaServer Faces
facelets - gridlayout with cellspacing=0 has no effect
Key: TOBAGO-422
URL: https://issues.apache.org/jira/browse/TOBAGO-422
Project: MyFaces Tobago
Issue Type: Bug
Affects
[
https://issues.apache.org/jira/browse/TOBAGO-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volker Weber resolved TOBAGO-421.
-
Resolution: Fixed
Tab switching fails if selectedIndex is vb and first tab rendered=false
markup attribute did not support multiple markups when using valueBindig
-
Key: TOBAGO-423
URL: https://issues.apache.org/jira/browse/TOBAGO-423
Project: MyFaces Tobago
[
https://issues.apache.org/jira/browse/TOBAGO-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volker Weber resolved TOBAGO-423.
-
Resolution: Fixed
markup attribute did not support multiple markups when using valueBindig
This mail is sent from time to time and is meant to remind you, that
the [EMAIL PROTECTED] and dev@myfaces.apache.org mailing lists
- like most of the ASF lists - are subscribers only. This means that
you MUST subscribe BEFORE you post to one of the lists.
Please make sure, that you post your
For our applications we utilize the flowScope in preference to the session
given it's ability to clean-up and support multiple flowScopes for multiple
windows. So its an invaluable feature in Trinidad, but sadly it's only
possible via code to add new Managed Beans to the flowScope map. This
[
https://issues.apache.org/jira/browse/MYFACES-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504224
]
Sebastian Kolb commented on MYFACES-518:
It still does not work with version 1.1.5 and 1.1.6.
inputDate
Hey good news.
The converter now works fine for me.
I am going to write a patch for tomahawk but I think someone who has more
knowlege about tomahawk should look over the code because I think that I
have code in there which does not fit in your convention.
Where can I post some of my code?
Hi Matthias,
I meant to say archetype not prototype ;)
regards,
Martin
On 6/13/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
I have no clue, what you are talking about.
Are you talking about the Maven-Faces-Plugin ?
That is part of the *bundle*. And I pinged Bruno since
I want to make
ah,
the archetype is (currently) part of the plugins release.
But I am thinking about to release everytime AFTER we released a CORE,
since they depend much more on the latest greates CORE than the rest
of the plugins.
So, perhaps we should just remove them from the current root pom in plugins/
Has the MyFaces archetype ever been released so far?
the Trinidad one has, I know.
regards,
Martin
On 6/13/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
ah,
the archetype is (currently) part of the plugins release.
But I am thinking about to release everytime AFTER we released a CORE,
the myfaces not,
the trinidad because is part of plugins...
let me finish all my release, and I'll release myfaces archetype AND
trinidad archetype
(myfaces for 1.1.5 and trinidad for 1.0.1 / 1.2.0)
-M
On 6/13/07, Martin Marinschek [EMAIL PROTECTED] wrote:
Has the MyFaces archetype ever been
What is the purpose of calling the validators on the components in the
non-selected tab? I don't see why this is necessary, as there will
never be submitted values from the components inside those tabs, and
thus always valid, and thus calling the validators just wastes CPU
time.
Remember, the
Hey Renderkit guys. We have an open question on the 301 EG regarding
namespacing clientId's. As you well know, Faces does not currently
namespace it's client id's. Although we're looking at asking that this
be added to Faces 2.0, it's not in Faces 1.2. We've discussed many
options and the
possibility to have a onclick event on a sheet column
-
Key: TOBAGO-424
URL: https://issues.apache.org/jira/browse/TOBAGO-424
Project: MyFaces Tobago
Issue Type: Improvement
Affects
Why are we releasing the 1.2 plugins before the Trinidad core?I ask because
what I'd like to do is rebranch 1.2 from 1.0.1,
so that 1.2.0 == 1.0.1 + JSF 1.2 support, which is a good
pattern going forward. But we can't do that unless we release
Trinidad 1.0.1.
-- Adam
On 6/13/07, Bruno
On 6/13/07, Scott O'Bryan [EMAIL PROTECTED] wrote:
Hey Renderkit guys. We have an open question on the 301 EG regarding
namespacing clientId's. As you well know, Faces does not currently
namespace it's client id's. Although we're looking at asking that this
be added to Faces 2.0, it's not in
OK, so here's an idea:- Release 1.2.0 plugins for MyFaces core
- Don't release 1.2.0 core
- Rebranch 1.2 off of 1.0.1
- Release 1.2.1 plugins and core
This way, 1.2.1 == 1.0.1 + JSF 1.2, and the
version numbers line up all pretty. :) The cost
is an extra release of the plugins.
-- Adam
On
Thomas,
Jeanne is probably better to answer this question but I'll take a quick
stab at it. Right now we have a portlet skin in Trinidad. It defers to
the JSR-168 style classes where appropriate and then adds the additional
styles we need. I believe it's based off the simple skin. It does
On 6/13/07, Adam Winer [EMAIL PROTECTED] wrote:
OK, so here's an idea:
- Release 1.2.0 plugins for MyFaces core
- Don't release 1.2.0 core
- Rebranch 1.2 off of 1.0.1
- Release 1.2.1 plugins and core
that's good. So, feel free to cast your vote for 1.2 plugins.
This way, 1.2.1 == 1.0.1 + JSF
All that said, shouldn't we be starting the 1.0.1 TrinidadCore release now
too?
-- Adam
On 6/13/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
On 6/13/07, Adam Winer [EMAIL PROTECTED] wrote:
OK, so here's an idea:
- Release 1.2.0 plugins for MyFaces core
- Don't release 1.2.0 core
-
yes..
I am about to create the branch,
nothing else in the queue ?
On 6/13/07, Adam Winer [EMAIL PROTECTED] wrote:
All that said, shouldn't we be starting the 1.0.1 Trinidad
Core release now too?
-- Adam
On 6/13/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
On 6/13/07, Adam Winer
Adam,
Thanks for the input. Big help. You're right about the renderer kit
thing, I've been up working on this pretty late and it's all a mush at
this point. :) I totally agree that I don't even know if it's
practial to do that. They were talking about wrapping the renderers
coming out
tc:style tc:script is not loaded if clicking on a tc:link with
actionListener
-
Key: TOBAGO-425
URL: https://issues.apache.org/jira/browse/TOBAGO-425
Project:
Definitely option 2) - invokeOnComponent won't work with convertClientId
(convertClientId should IMHO be deprecated).
regards,
Martin
On 6/13/07, Scott O'Bryan [EMAIL PROTECTED] wrote:
Adam,
Thanks for the input. Big help. You're right about the renderer kit
thing, I've been up working on
Nothing I know of...
--- Adam
On 6/13/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
yes..
I am about to create the branch,
nothing else in the queue ?
On 6/13/07, Adam Winer [EMAIL PROTECTED] wrote:
All that said, shouldn't we be starting the 1.0.1 Trinidad
Core release now too?
--
Have we tried logging a bug against the 1.2 ref impl that simply says
clientId's are not namespaced and see where that gets us? :)
Scott O'Bryan wrote:
Thomas,
Jeanne is probably better to answer this question but I'll take a
quick stab at it. Right now we have a portlet skin in Trinidad.
Hi,
On 6/12/2007 9:36 AM, Adam Winer wrote:
Does anyone have high-priority issues they'd like resolved
for 1.0.1?
I'd very much like to switch the default validation mechanism
from ALERT to INLINE, as I think that's the killer feature
for this release.
has this has any accessibility
Hello myface community,
I am recruiting for my oldest client, a professional services firm based in
Silicon Valley. They have been doing some work for several years now with
the State of NY. One of the Web Engineers on their current project is ill
and will not return to the project anytime
That's a good point Martin. InvokeOnComponent is not something we
discussed but totally should have. The initial spec for this changed at
the last minute (from option 1 to option 2) and I don't think everything
was taken into account. We had some issues right off (of course) when
someone
Hi,
currently (in trunk)
you run mvn install
and get all (build, api, impl, demo)
I'd like to change that.
The default (mvn install) should create only
build, api and impl
to get all (above + examples (blank and demo))
mvn install -Pall-modules
I'd like to introduce this all-modules
On 6/13/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
currently (in trunk) you run mvn install and get all (build, api, impl, demo)
I'd like to change that. The default (mvn install) should create only build,
api and impl
to get all (above + examples (blank and demo)) mvn install
Dialog framework documentation errors
-
Key: TRINIDAD-57
URL: https://issues.apache.org/jira/browse/TRINIDAD-57
Project: MyFaces Trinidad
Issue Type: Bug
Components: Documentation
Affects
On 6/13/07, Wendy Smoak [EMAIL PROTECTED] wrote:
On 6/13/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
currently (in trunk) you run mvn install and get all (build, api, impl,
demo)
I'd like to change that. The default (mvn install) should create only build,
api and impl
to get all
On 6/13/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
ok, perhaps I introduce an assembly profile
so that :prepare does the prepartion on all *important* artifacts.
an optional profile like CORE could be introduced to just create
build, api and impl
I'd like to see a new person be able to
On 6/13/07, Wendy Smoak [EMAIL PROTECTED] wrote:
On 6/13/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
ok, perhaps I introduce an assembly profile
so that :prepare does the prepartion on all *important* artifacts.
an optional profile like CORE could be introduced to just create
build,
I'd like to see a new person be able to check out the project, type
'mvn install', and build *everything* including the release
assemblies. (They need to be 'assembly:attached' for this to work.)
assembly:attached?
not assembly:assembly ?
ok, good point.
Needing to know secrets like
[
https://issues.apache.org/jira/browse/TRINIDAD-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-57.
Resolution: Fixed
Fix Version/s: 1.0.2-core
Dialog framework documentation errors
Deprecate - and stop using - CoreRenderer.toUri()
-
Key: TRINIDAD-58
URL: https://issues.apache.org/jira/browse/TRINIDAD-58
Project: MyFaces Trinidad
Issue Type: Improvement
On 6/13/07, Gabrielle Crawford [EMAIL PROTECTED] wrote:
Hi,
On 6/12/2007 9:36 AM, Adam Winer wrote:
Does anyone have high-priority issues they'd like resolved
for 1.0.1?
I'd very much like to switch the default validation mechanism
from ALERT to INLINE, as I think that's the killer
Simple (I imagine) question:
For a link's href, should we be calling encodeResourceURL()
or encodeActionURL()?
I've always assumed these are action URLs. I see other
code out there (MyFaces outputLink, for example) that
considers these resource URLs.
(Whatever answer we arrive at should apply
Invoking ResourceServlet via FacesServlet leads to NPE
--
Key: TRINIDAD-59
URL: https://issues.apache.org/jira/browse/TRINIDAD-59
Project: MyFaces Trinidad
Issue Type: Bug
Affects
[
https://issues.apache.org/jira/browse/TRINIDAD-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-59.
Resolution: Fixed
Fix Version/s: 1.0.2-core
Assignee: Adam Winer
Fixed.
On 6/13/2007 3:59 PM, Adam Winer wrote:
On 6/13/07, Gabrielle Crawford
[EMAIL PROTECTED]
wrote:
Hi,
On 6/12/2007 9:36 AM, Adam Winer wrote:
Does anyone have high-priority issues they'd like resolved
for 1.0.1?
I'd very much like to switch the default validation mechanism
Definitely encodeActionUrl, yes, from what I read in the portlet spec.
Obviously the original link implementors thought the distinction was
about form post versus get - but the distinction is about query
links/form submissions versus inclusion of resources in the page.
regards,
Martin
On
60 matches
Mail list logo
