[
https://issues.apache.org/jira/browse/TRINIDAD-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500184
]
Adam Winer commented on TRINIDAD-44:
Adding
+ argLine-enableassertions/argLine
+ forkModeonce
[
https://issues.apache.org/jira/browse/TRINIDAD-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-44.
Resolution: Fixed
Fix Version/s: 1.0.1-core
Fixed. See subversion commits for the issues
behavior in the RI.
Anyway, I'd say don't bother.
-- Adam
On 5/29/07, Bruno Aranda [EMAIL PROTECTED] wrote:
But then why the RI uses it to fall into old view and state management
behaviour in case of a postback if the artifact is implemented using
1.2. In our case, without that, in case of postback
I agree, we should have a lot more documentation, and
also be deploying a plugins site in general.
Also, yes, the code is written to target Java 5. All of
the current consumers (MyFaces 1.2 and Trinidad) require
Java 5, so that hasn't been a problem up to this point.
-- Adam
On 5/28/07
is
only consulted to determine how to parse the faces-config file,
and has no runtime effect other than that.
-- Adam
The resulting error of not tracking the version can be observed when
running the sandbox with myfaces 1.2, in the convertNumber example.
cd tomahawk/sandbox/examples
mvn -PjettyConfig
. Yuck.
-- Adam
On 5/24/07, Paul McMahan [EMAIL PROTECTED] wrote:
This line was removed from javax/faces/webapp/UIComponentTagBase as
part of rev 540403.
protected static Logger log = Logger.getLogger
(javax.faces.webapp);
From the commit log it seems that line was removed for binary
It's working now. Thanks, Manfred!
-- Adam
On 5/22/07, Manfred Geiler [EMAIL PROTECTED] wrote:
yes I am.
Adam, please try again.
(The project roles for trinidad where not properly assigned to the groups)
--Manfred
On 5/21/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
I mailed Martin
[
https://issues.apache.org/jira/browse/TRINIDAD-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer updated TRINIDAD-24:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
JspUtils.getEncoding() blindly
of Javadoc is cut-and-pasted from LongRangeValidator,
it would seem... Thankfully, there's an instanceof check,
so no ClassCastExceptions but this code has to just be broken...
-- Adam
On 5/22/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
On 5/22/07, Adam Winer [EMAIL PROTECTED] wrote:
The Trinidad subclass of LengthValidator needs some work.
Changes I plan to make - feedback appreciated:
- The messages are copied from the LongRangeValidator, so
we say Enter a value
On 5/22/07, Blake Sullivan [EMAIL PROTECTED] wrote:
Adam Winer wrote:
The Trinidad subclass of LengthValidator needs some work.
Changes I plan to make - feedback appreciated:
- The messages are copied from the LongRangeValidator, so
we say Enter a value greater than or equal to 5 instead
: Adam Winer
Assigned To: Adam Winer
Fix For: 1.0.1-core
The inline validation code suffers from a couple of problems when
rapidly clicking submit repeatedly:
- Sometimes validation goes through to the server
- When there are server error messages, you end up getting
double
[
https://issues.apache.org/jira/browse/TRINIDAD-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497985
]
Adam Winer commented on TRINIDAD-29:
Resolved the first problem. It's still the case that if you get
some
Versions: 1.0.0-incubating-core
Reporter: Adam Winer
Assigned To: Adam Winer
Priority: Minor
The only messages shown on the client are min and max.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
Custom messages on tr:validateLength are not used
-
Key: TRINIDAD-31
URL: https://issues.apache.org/jira/browse/TRINIDAD-31
Project: MyFaces Trinidad
Issue Type: Bug
Reporter: Adam
[
https://issues.apache.org/jira/browse/TRINIDAD-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497986
]
Adam Winer commented on TRINIDAD-31:
The .java code in LengthValidator does not use any of the custom messages
Affects Versions: 1.0.1-core
Reporter: Adam Winer
Assigned To: Adam Winer
The messages in validateLength are along the lines of value is too large, must
be less than 4, instead of value is too long, must be shorter than 4
characters
--
This message is automatically generated
: Improvement
Affects Versions: 1.0.0-incubating-core
Reporter: Adam Winer
Assigned To: Adam Winer
Priority: Minor
If the minimum and maximum are 5, it's better to say the length isn't 5
characters than the length must be between 5 and 5 characters
--
This message
Project: MyFaces Trinidad
Issue Type: Bug
Affects Versions: 1.0.0-incubating-core
Reporter: Adam Winer
Assigned To: Adam Winer
NOT_IN_RANGE messages are shown when only one of min and max are set, not when
both are set.
--
This message is automatically generated
[
https://issues.apache.org/jira/browse/TRINIDAD-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer updated TRINIDAD-28:
---
Resolution: Fixed
Fix Version/s: 1.0.1-core
Status: Resolved (was: Patch
[
https://issues.apache.org/jira/browse/TRINIDAD-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-34.
Resolution: Fixed
Fix Version/s: 1.0.1-core
Fixed.
tr:longRangeValidator
[
https://issues.apache.org/jira/browse/TRINIDAD-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-33.
Resolution: Fixed
Fix Version/s: 1.0.1-core
Fixed.
tr:lengthValidator: provide better
[
https://issues.apache.org/jira/browse/TRINIDAD-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-32.
Resolution: Fixed
Fix Version/s: 1.0.1-core
Fixed.
tr:validateLength messages are poor
[
https://issues.apache.org/jira/browse/TRINIDAD-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498004
]
Adam Winer commented on TRINIDAD-33:
We have a new org.apache.myfaces.trinidad.validator.LengthValidator.EXACT
[
https://issues.apache.org/jira/browse/TRINIDAD-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-31.
Resolution: Fixed
Fix Version/s: 1.0.1-core
Assignee: Adam Winer
Custom messages
[
https://issues.apache.org/jira/browse/TRINIDAD-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-30.
Resolution: Fixed
Fix Version/s: 1.0.1-core
Fixed.
tr:validateLength does not send range
[
https://issues.apache.org/jira/browse/TRINIDAD-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-3.
---
Resolution: Won't Fix
The behavior is required by the spec. See the MYFACES issue for discussion
[
https://issues.apache.org/jira/browse/TRINIDAD-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-15.
Resolution: Fixed
Fix Version/s: 1.0.1-core
Assignee: Adam Winer
Fixed
Sounds great. I know we've got a lot of fixes ready
for 1.0.1 too - is there anything unpatched that someone's
waiting on?
-- Adam
On 5/22/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi,
my guess is, that we need to release the plugins, before we start to
release the CORE.
Why? Because
: MyFaces Trinidad
Issue Type: Bug
Affects Versions: 1.0.0-incubating-core
Reporter: Adam Winer
MenuContentHandlerImpl.setRootModelRowKey() is a non-static method, but it
sets a static field. One or the other is wrong!
--
This message is automatically generated by JIRA
[
https://issues.apache.org/jira/browse/TRINIDAD-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-36.
Resolution: Fixed
Fix Version/s: 1.0.1-core
Assignee: Adam Winer
Checked in patch
[
https://issues.apache.org/jira/browse/TRINIDAD-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498103
]
Adam Winer commented on TRINIDAD-37:
What would be best is if inline validation always fired with onblur
: Bug
Components: Components
Affects Versions: 1.0.1-incubating-core-SNAPSHOT
Reporter: Adam Winer
Priority: Critical
List.subList() does not return a serializable object, because it can return a
RandomAccessSubList, which is not serializable
[
https://issues.apache.org/jira/browse/TRINIDAD-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-27.
Resolution: Fixed
Fix Version/s: 1.0.1-incubating-core-SNAPSHOT
Fixed - we now make
[
https://issues.apache.org/jira/browse/TRINIDAD-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497522
]
Adam Winer commented on TRINIDAD-24:
Fixed. Having problems with JIRA, so can't update the status
I'm having a series of problems with the new JIRA TRINIDAD
group. I can't change the status of
http://issues.apache.org/jira/browse/TRINIDAD-24,
and I've not been able to assign any of the issues.
Should I be filing infrastructure bugs?
-- Adam
Yeah, looks like a good fix. I doubt the optimization of caching
here is buying us much of anything.
-- Adam
On 5/17/07, Martin Koci [EMAIL PROTECTED] wrote:
Hi,
I probably found a problem with BindingFacesMessage class. If calling
getMessage() it resolves value binding only once
Components: Facelets
Affects Versions: 1.0.1-incubating-core-SNAPSHOT
Reporter: Adam Winer
These two attributes aren't yet supported.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Issue Type: Bug
Components: Facelets
Affects Versions: 1.0.1-incubating-core-SNAPSHOT
Reporter: Adam Winer
Priority: Minor
These two attributes aren't supported on Facelets.
--
This message is automatically generated by JIRA.
-
You can reply
Welcome to the gang, Gab!
-- Adam
On 5/18/07, Matt Cooper [EMAIL PROTECTED] wrote:
Congratulations Gabrielle!
On 5/18/07, Manfred Geiler [EMAIL PROTECTED] wrote:
Although the world's end is close: I'm a good swimmer and I'm not
afraid of sharks Mr Grant Pirate Smith!
:)
On 5/18/07
I think we should release all of the plugins at once;
they're one project. Would this be 1.2.0 or 2.0.0
of this project?
-- Adam
On 5/17/07, Bruno Aranda [EMAIL PROTECTED] wrote:
Hi,
As part of preparing the release for myfaces 1.2 the
maven-faces-plugin 1.2 needs to be released. Although I
There's never a reason to cast anything to
a specific subtype of Number if you're just
going to extract a primitive from it. Casting
to Number (the MyFaces way) is better.
-- Adam
On 5/17/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
FYI
-- Forwarded message --
From
I'm curious - why? 1.2 seems the more obvious choice
for a version number, especially since we haven't really
changed APIs. I'd rather save 2.0 for an API overhaul.
-- Adam
On 5/17/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
I'd like 2.0.0 more
.M
On 5/17/07, Adam Winer [EMAIL
(\u00a0) - not mentioned in
the commit message, though.
-- Adam
On 5/15/07, Wendy Smoak [EMAIL PROTECTED] wrote:
Were the changes to the xml files intentional? I don't see anything
relevant in the commit message.
On 5/15/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: awiner
Date: Tue May
I assume he means getting JIRA changes sent out to the
same place as tomahawk/core/tobago JIRA changes.
One thing I've just noticed is that my admin JIRA rights
seem to be off. When I click the Administration tab,
I see MyFaces Core, MyFaces Tobago, and MyFaces
Tomahawk - no Trinidad!
-- Adam
No, I think the client-side should get either null or undefined
in this case. You always want to minimize the instances
of floating point equality comparisons; code like:
foo == 4.9e-324
is error-prone.
-- Adam
On 5/16/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi,
for some reasons
I'm not sure if Double.MAX-VALUE * -1 is appropriate.
We might consider using Double.POSITIVE_INFINITY
and Double.NEGATIVE_INFINITY instead.
-- Adam
On 5/16/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
they question is also
should the range not be the following:
(for double)
Form
Affects Versions: 1.0.1-incubating-core-SNAPSHOT
Reporter: Adam Winer
If you use the dialog framework to launch a page, then submit multiple times on
the dialog, then hit return, you'll get an error, as the view state for the
parent page has expired. The view state for the parent needs
[
https://issues.apache.org/jira/browse/TRINIDAD-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-21.
Resolution: Fixed
Fix Version/s: 1.0.1-incubating-core-SNAPSHOT
Fixed.
dialog framework
Hi Dave,
I'm reluctant to put too much work into the existing PPR JS codebase;
a big hope of mine is to switch that codebase over to a modern
XMLHTTP basis, at which point blocking could be much more
sensibly implemented.
-- Adam
On 5/15/07, David Brunette [EMAIL PROTECTED] wrote:
Hi
Components: website
Reporter: Adam Winer
Assigned To: Adam Winer
Trinidad's out of incubator, and needs to be added as a project link.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/MYFACES-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer updated MYFACES-1630:
Status: Patch Available (was: Open)
Update the website now that Trinidad is out of incubator
For
http://issues.apache.org/jira/browse/MYFACES-1630
... I assumed I could check in the attached patch myself,
but got:
adam-winers-computer:~/Work/myfaces-site awiner$ svn commit
Sendingsrc/site/apt/index.apt
subversion/libsvn_client/commit.c:873: (apr_err=175002)
svn: Commit failed
ADFFACES is now read-only. You need to create issues
on https://issues.apache.org/jira/browse/TRINIDAD
-- Adam
On 5/15/07, Jijun Wang [EMAIL PROTECTED] wrote:
Hello:
Could someone reopen the issue?
https://issues.apache.org/jira/browse/ADFFACES-441
I think I only have my changes on logging
No, that's a good point: swapping out the PPR code
for XMLHttp would just change how we do blocking
for partial submits - it wouldn't affect blocking for
full submits at all.
-- Adam
On 5/15/07, David Brunette [EMAIL PROTECTED] wrote:
Thanks Adam.
If the PPR code is going
I had a lot less gray hair when JSF started. But I've always
been this gender. :)
-- Adam
On 5/15/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Adam is one of the main driver of the JSF spec and works on the
Trinidad. He follows MyFaces since the old SF days.
the old san francisco
And another admin for awiner?
Thanks,
Adam
On 5/14/07, Manfred Geiler [EMAIL PROTECTED] wrote:
Hello Wendy,
one more admin please: manolito
Thanks,
Manfred
On 5/14/07, Mathias Brökelmann [EMAIL PROTECTED] wrote:
Hi Wendy,
can you also add my account (mbr) to the administrator group
to fix that design mistake.
-- Adam
On 5/14/07, Danny Robinson [EMAIL PROTECTED] wrote:
Adam,
Great to finally meet face-to-face at JavaOne. During our conversation we
talked about PPR performance and how we could make some optimizations. One
suggestion you had was to implement a naming
Mathias or I will take care of this once we're admins;
I don't think Wendy should have to set up the individual
projects.
Cheers,
Adam
On 5/14/07, Beelen, Marco [EMAIL PROTECTED] wrote:
Hello Wendy,
While you are working on the build definitions, could you please also
look at the publication
+1
-- Adam
On 5/14/07, Manfred Geiler [EMAIL PROTECTED] wrote:
+1
--Manfred
On 5/13/07, Wendy Smoak [EMAIL PROTECTED] wrote:
I'd like to create [EMAIL PROTECTED] for automated
messages from Continuum.
I feel that more people are interested in watching commits than
notifications
Looks fine by me. This code is purely for debugging, so
efficiency isn't a big concern. However, we should probably
consider switching to a HashSet.
-- Adam
On 5/14/07, Matt Cooper [EMAIL PROTECTED] wrote:
Hi Jeanne,
That is fine. It should cause no problems.
If pretty-printing is used
How can we start deploying our site to
http://myfaces.apache.org/trinidad/index.html
? Any special magic?
-- Adam
I don't really get the point. No other apache projects
would do this. So, -1.
-- Adam
On 5/11/07, Jijun Wang [EMAIL PROTECTED] wrote:
Hello:
For solution to localize logging message/exception string (see
https://issues.apache.org/jira/browse/ADFFACES-441), it would be helpful
if we could
some checkins last week to
http://issues.apache.org/jira/browse/ADFFACES-135
Mea culpa!
-- Adam
On 5/10/07, Mike Kienenberger [EMAIL PROTECTED] wrote:
Just an FYI that the standard MyFaces practice is that all non-sandbox
commits should have JIRA issues (and references in the commit log
OK, great! Let me know if (or, rather, *when*) I slip again. :)
-- Adam
On 5/12/07, Mike Kienenberger [EMAIL PROTECTED] wrote:
Yes, my original message said non-trivial, non-sandbox, but when I
typed it in again, I didn't include it. Sorry for the confusion.
On 5/12/07, Adam Winer [EMAIL
Sorry for the bit-rot... I'll have a look soon - hopefully
I can fit it in between J1 sessions (or during the
boring ones :)
-- Adam
On 5/8/07, Danny Robinson [EMAIL PROTECTED] wrote:
Adam,
I've uploaded the latest patch to ensure it works after the move to myfaces,
and any recent changes
attention to the technical keynote. :)
-- Adam
On 5/8/07, Adam Winer [EMAIL PROTECTED] wrote:
Sorry for the bit-rot... I'll have a look soon - hopefully
I can fit it in between J1 sessions (or during the
boring ones :)
-- Adam
On 5/8/07, Danny Robinson [EMAIL PROTECTED] wrote:
Adam,
I've
intent.)
-- Adam
Regards
Bernd
Adam Winer wrote:
No, write() calls must close a starting element.
Otherwise the following sequence:
h:outputLink ...
h:outputText verbatim=true .../
/h:outputLink
... would fail.
-- Adam
On 5/4/07, Matthias Wessendorf [EMAIL PROTECTED
@Matthias - are you looking at this one?
-- Adam
On 5/4/07, Luka Surija [EMAIL PROTECTED] wrote:
Hi,
is there any chance that this issue will be fixed any time soon. For me
it is a handicap because I can't use new versions of Trinidad because of
that issue.
Best regards,
--
Luka Surija
for outputText and panel components.
-- Adam
On 5/4/07, Danny Robinson [EMAIL PROTECTED] wrote:
I noted Eric created issue ADFFACES-482 to have tabindex added to all
components. I know this has come up before and general comments were around
its limitations, however even with its limitations (ie
) was suggesting that the faces Maven
plugin (currently in Trinidad) should be part of Commons.
Obviously, a Maven plugin lives in its own JAR. I'm OK
with having shared build tools in a common SVN tree,
just so it's clearer for someone working on the project.
Make sense?
-- Adam
No, write() calls must close a starting element.
Otherwise the following sequence:
h:outputLink ...
h:outputText verbatim=true .../
/h:outputLink
... would fail.
-- Adam
On 5/4/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Udo,
I think you are right, since the write methods
.
-- Adam
On 5/3/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Greetings from the ApacheCon in Amsterdam.
It was discussed a lot on the list and Bernd and I are now taking the
time to layout a apache-myfaces-commons-[SUBSET]-VERSION.jar file.
Commons:
-What should go into a commons JAR?
Non
to merit splitting them.
Mike, what about the two makes you want to split
them?
Cheers,
Adam
On 5/3/07, Mike Kienenberger [EMAIL PROTECTED] wrote:
Adam,
Our past discussion on commons was to provide JSF
components/validators/converters that could be used in any component
library, even
On 4/30/07, Adam Winer [EMAIL PROTECTED] wrote:
On 4/30/07, Tim McConnell [EMAIL PROTECTED] wrote:
Hi Adam, thanks very much for reviewing my patches so promptly. Here are
my
comments to your comments:
ADFFACES-475:
- If the method name is immaterial at runtime then the only change
+1
On 5/1/07, Gabrielle Crawford [EMAIL PROTECTED] wrote:
+1
On 5/1/2007 4:49 AM, Matthias Wessendorf wrote:
Hi,
during the Incubation process we noticed that Matt Cooper was active
on the mailing lists and with patches via Jira as well. So we, the
Trinidad PPMC (now part of MyFaces)
[
https://issues.apache.org/jira/browse/MYFACES-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492803
]
Adam Winer commented on MYFACES-1599:
-
The change in method name is meaningless - method names have no effect
small tooling benefit to the change. I think the simplest change
to make is removing the current CAN_COERCE check in the code,
instead of hardcoding binding and converter as special attrs.
-- Adam
On 4/30/07, Tim McConnell [EMAIL PROTECTED] wrote:
Hi Adam, thanks very much for reviewing my patches so promptly. Here are
my
comments to your comments:
ADFFACES-475:
- If the method name is immaterial at runtime then the only change for the
companion MYFACES-1599 JIRA would be to update
a metadata flag that
forces the deferred-value to java.lang.String for spec
compliance, but I'd recommend against using it anywhere
that your hands aren't completely tied.
Cheers,
Adam
I guess I qualify as part of the MyFaces community now? :)
I'll be at J1, would be happy to be around at the BOF is possible
(haven't checked the schedule yet).
Cheers,
Adam
On 4/28/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
Great idea!
I'll try to send something by Monday.
Ciao
[
https://issues.apache.org/jira/browse/MYFACES-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer updated MYFACES-1467:
Resolution: Fixed
Status: Resolved (was: Patch Available)
There is no conflict
Environment: tobago 1.0.10
IE 6.x
Reporter: Adam Henne
submitting actions with defaultCommand=true the progressbar isn't shown.
tc:button action=#{myForm.doSearch} label=Search //tc:button =
progressbar
tc:button action=#{myForm.doSearch} label=Search defaultCommand=true
//tc:button
[
https://issues.apache.org/jira/browse/TOMAHAWK-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472019
]
Adam Jenkins commented on TOMAHAWK-784:
---
I have hit this issue also...the javascript method in the onclick
[
https://issues.apache.org/jira/browse/TOMAHAWK-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472022
]
Adam Jenkins commented on TOMAHAWK-784:
---
***WORK AROUND*
Hi All,
Until this issue
it and which don't. Anything more is, well,
very 20th century.
Regards,
Adam Winer
On 10/26/06, Jesse Alexander (KSFD 121)
[EMAIL PROTECTED] wrote:
The newest JSF-RI release (1.2_03) does not emmit anymore JS according
to Ed.
Only exception is the command-link... and for that one I discussed
-public.dev.java.net/would be a good thing. :)-- Adam
On 10/21/06, Bruno Aranda [EMAIL PROTECTED] wrote:
Hi,I have a doubt about the spec. In the description of sections 9.4.3(f:convertDateTime) and 9.4.4 (f:convertNumber) it says that thesetags should extend the now deprecated
[
http://issues.apache.org/jira/browse/MYFACES-1467?page=comments#action_12443127
]
Adam Winer commented on MYFACES-1467:
-
It cannot be fixed in UIInput once for all, because the spec describes how
UIInput must behave
[
http://issues.apache.org/jira/browse/MYFACES-1467?page=comments#action_12442459
]
Adam Winer commented on MYFACES-1467:
-
With regards to the original issue: the bug is *not* in UIInput, but is in
fact in the decode() implementation
: Portlet_Support
Affects Versions: 1.1.4
Environment: JBoss 4.0 - JBoss 4.0.4
Reporter: Adam Warski
If I have a JSF portlet, and it is given the chance to initialize the session,
after redeploying the application I get an NPE:
Caused by: java.lang.NullPointerException
Martin,
Hey, very cool! Have you written up anything describing (a)?
I'm very curious about the strategy chosen.
-- Adam
On 9/13/06, Martin Haimberger [EMAIL PROTECTED] wrote:
Hy everyone,
my name is Martin Haimberger and i took part in the GSoC 2006 with the
Partial State Saving project
Wrong list, sure, but since you opened up the can of worms...Is Shale really planning on getting into the HTML-renderingbusiness?-- AdamOn 8/24/06,
Sean Schofield [EMAIL PROTECTED] wrote:
Doh.Wrong list again.On 8/24/06, Sean Schofield [EMAIL PROTECTED] wrote: I think it would be highly desirable
On 8/24/06, Sean Schofield [EMAIL PROTECTED] wrote:
I suspect what Adam is asking about is Shale getting in the business of
creating visual components like buttons in order to implement the
Next/Previous type of thing. That's an area I have wanted to shy away from,
and this kind of thing
Problem #2 should not be happening if the MyFaces state management code is properly factored; the FormRenderer - anyone's form renderer - should be calling the ResponseStateManager, which should be rendering the sequence. Last time I looked, the MyFaces FormRenderer was directly encoding the
One might also have a look at the Trinidad RenderKit test framework,
which does a lot of work to make writing unit tests for renderers
oh so trivial, including parsing faces-config.xmls on the classpath.
http://wiki.apache.org/myfaces/Trinidad_RenderKit_test_framework
-- Adam
On 8/20/06
Even easier than that - there''s a link right off the main
Browse Project page... Look under Project Summary
at http://issues.apache.org/jira/browse/MYFACES
-- Adam
On 8/20/06, Sean Schofield [EMAIL PROTECTED] wrote:
Is there any way to search for Patch Available issues?
I haven't been able
... but I'd really like to add a flag to maven-faces-pluginto turn Trinidad-specific superclasses on and off. (IIRC, theFacelet generator is actually already generic). If I got thisdone, would someone on the Tomahawk side use it?
-- AdamOn 8/4/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
There
[
http://issues.apache.org/jira/browse/TOMAHAWK-565?page=comments#action_12423378
]
Adam Winer commented on TOMAHAWK-565:
-
The technique we used in Trinidad for a similar scenario was to substitute the
URL of an image in the webapp
in Trinidad generally received quite a lot of team
design effort, so it's usually the case that we *did* havea reason for designing things the way we did.)-- Adam
Later, when we see that we really need a client side converter we canimplement this stuff too, we dont need it for date and number
that are different will just make the merge that much harder(and push it off even further). Plus, there is quite an advantageto taking a codebase that has already been debugged and shipped.-- Adam
And Cagatay has something right now, why not take it in?
regards,MartinOn 7/13/06, Mario Ivankovits
[EMAIL
401 - 500 of 721 matches
Mail list logo
