Are we building an examples package as part of a release? Martin's
comment in http://issues.apache.org/jira/browse/TOMAHAWK-629 makes it
sound like we are, but I can't find them in any of the usual expected
places.
We need to correct the link in this issue if so. Otherwise, this
issue really
Ok, Martin.
I went to fix this and realized that there is indeed a setMessage
method in ValidatorBase. So I was wrong about that.
However, the getters here don't hold value bindings like they should.
I'm fixing this instead and renaming the issue.
Also, for some reason, you prefixed the file
An FYI:
I hit the following build error just now, even though MyFaces had
built fine a little bit ago.
===
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to configure plugin parameters for:
[ http://issues.apache.org/jira/browse/TOMAHAWK-683?page=all ]
Mike Kienenberger resolved TOMAHAWK-683.
Fix Version/s: 1.1.5-SNAPSHOT
Resolution: Fixed
r448673 lost ValueBinding support for message/detailMessage/summaryMessage
Hi Mike,
no need to feel bad. I thought we open jira issues for important
changes, like new components or changes to MyFaces core. I did not
knew that we have to open a jira issue for new component attributes. I
will consider this in the future.
-Thomas
On 9/20/06, Mike Kienenberger [EMAIL
Hey Thomas,
We're now opening jira issues for any non-trivial change change to
Core or Tomahawk (Sandbox is still optional although recommended).
This is how we're generating change-logs, release notes for new releases.
On 9/22/06, Thomas Spiegl [EMAIL PROTECTED] wrote:
Hi Mike,
no need to
[
http://issues.apache.org/jira/browse/TOMAHAWK-519?page=comments#action_12436779
]
Mathias Werlitz commented on TOMAHAWK-519:
--
Well, I recently managed with heavy css hacking to style the tabs completly
different, but I had to
[
http://issues.apache.org/jira/browse/TOMAHAWK-584?page=comments#action_12436780
]
Mike Kienenberger commented on TOMAHAWK-584:
Well, this is going to be a bit more work.
tree2 was done in apt format, and I'll have to convert it
Yeah, thanks - I didn't prefix it, it was the user who submitted the patch.
regards,
Martin
On 9/22/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
Ok, Martin.
I went to fix this and realized that there is indeed a setMessage
method in ValidatorBase. So I was wrong about that.
However, the
[
http://issues.apache.org/jira/browse/TOMAHAWK-520?page=comments#action_12436782
]
Mathias Werlitz commented on TOMAHAWK-520:
--
Ok, but generating inavlid HTML is still a major bug ... unfortunatly I don't
have the time to provide a
[
http://issues.apache.org/jira/browse/TOMAHAWK-519?page=comments#action_12436786
]
Martin Marinschek commented on TOMAHAWK-519:
Ok, so you have more than one tabbed-pane, and you want to have different
styles per component. Well,
In JSF1.2, the tree is built before the rendering happens - so
everything that is plain HTML is converted into a part of the
component tree anyways. Maybe we should just wait for this to happen
;) ?
Facelets is another question. No clue.
regards,
Martin
On 9/22/06, Gerald Müllan [EMAIL
Oh thanks, I was bothered by this one as well ;)
regards,
Martin
On 9/22/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
An FYI:
I hit the following build error just now, even though MyFaces had
built fine a little bit ago.
===
[ERROR] BUILD ERROR
[INFO]
Is an additional attribute always a non-trivial change? In the
specific case it was a trivial change from my point of view. How
should we handle this in the future?
On 9/22/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
Hey Thomas,
We're now opening jira issues for any non-trivial change
A trivial change is fixing a typo in the javadoc or reformatting code.
Anything that changes the behavior of MyFaces or Tomahawk is not a
trivial change.
Commits without a reference to a jira issue should be rare.
We'd still like to get a jira issue opened up for this change as well
so it'll
Is it just me, or does mvn site take way too long to run?
I can build the jar files faster, which is saying somethinig.
Is there any way to improve the mvn site speed? Trying to work on
documentation is kinda hard when turnaround time is 20 minutes.
I think we should let the developer decide if he wants a trivial
change (and adding an attribute might be trivial) to show up in the
release notes.
As the tabbed-pane is a major component, I'd love to have an
additional attribute in the relase-notes, though.
If the developer decides for no, it
I'd love to have mvn speed improved for everything. I hate it to wait
for 5min. until I can checkout my changes.
regards,
Martin
On 9/22/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
Is it just me, or does mvn site take way too long to run?
I can build the jar files faster, which is saying
Yeah, it's kinda why I don't do many patches.
It takes me 10 minutes to download a new svn snapshot, and 10 minutes
to build it. In the good old days of cvs and ant, it seemed to go
a lot faster.
On 9/22/06, Martin Marinschek [EMAIL PROTECTED] wrote:
I'd love to have mvn speed improved for
Why don't you do svn updates?
and could it be that using mvn site it downloads mvn-plugins that
somehow
don't make it into the cache? Or has it to do with the deep dependency
structure?
regards
Alexander
-Original Message-
From: Mike Kienenberger [mailto:[EMAIL PROTECTED]
Sent:
We'd still like to get a jira issue opened up for this change as well
so it'll be picked up in the next release.
that definitely makes sense. I'll open an issue.
On 9/22/06, Martin Marinschek [EMAIL PROTECTED] wrote:
I think we should let the developer decide if he wants a trivial
change (and
On 9/22/06, Jesse Alexander (KSFD 121)
[EMAIL PROTECTED] wrote:
Why don't you do svn updates?
I had too many issues in the past where this didn't catch everything.
Maybe it's not so much of an issue now that we've finally settled on
a directory layout, but every other bug report was fixed by
New attribute activePanelTabVar for HtmlPanelTabbedPane
---
Key: TOMAHAWK-684
URL: http://issues.apache.org/jira/browse/TOMAHAWK-684
Project: MyFaces Tomahawk
Issue Type: New Feature
you are right Mike, that's the point.
On 9/22/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
The problem with this approach is that the developer doesn't care if
it's in the release notes, but end users do, as do other developers.
When someone upgrades, any change that might affect them should
On 9/22/06, Thomas Spiegl [EMAIL PROTECTED] wrote:
We'd still like to get a jira issue opened up for this change as well
so it'll be picked up in the next release.
that definitely makes sense. I'll open an issue.
Thanks!
I pasted in the revision URL as a jira comment. I think that's the
[
http://issues.apache.org/jira/browse/TOMAHAWK-684?page=comments#action_12436799
]
Mike Kienenberger commented on TOMAHAWK-684:
Author: tomsp
Date: Wed Sep 20 04:50:22 2006
New Revision: 448171
URL:
On 8/22/06, L Frohman [EMAIL PROTECTED] wrote:
Where are they?
This stuff is actually all in the standard myfaces-example-simple project.
See this issue:
TOMAHAWK-263 - Sandbox examples are missing myfaces-example-simple
classes, resources, and configuration files
Martin says it's fixed
On 8/17/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
I think we should get rid of the wish issue type.
I don't see that we're likely to have someone surfing the jira issue
tracker looking for things to do.
If someone wants to wish for something, the user list (or maybe a wiki
page) seems
[
http://issues.apache.org/jira/browse/TOMAHAWK-584?page=comments#action_12436805
]
Mike Kienenberger commented on TOMAHAWK-584:
Ok. Converted to xdoc. Still need to make all of these other changes, though.
Improve the Tree 2
On 9/22/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
On 8/17/06, Mike Kienenberger [EMAIL PROTECTED] wrote: I think we should get rid of the wish issue type. I don't see that we're likely to have someone surfing the jira issue
tracker looking for things to do. If someone wants to wish for
org.apache.myfaces.custom.radio.HtmlRadio has this renderer declared:
private static final String DEFAULT_RENDERER_TYPE =
org.apache.myfaces.Radio;
public HtmlRadio()
{
setRendererType(DEFAULT_RENDERER_TYPE);
}
org.apache.myfaces.custom.radio.HtmlRadioTag has this:
Just created the MyFaces Issue Type Scheme but were unable to assign
it to MyFaces Core because there are still 6 Test and 3 Wish
issues.
The Sub-Task seems to be a special type and it looks like it is
mandatory in some way.
Mike, I just gave you jira-admin permissions. Feel free to reorganize
[ http://issues.apache.org/jira/browse/TOMAHAWK-684?page=all ]
Manfred Geiler reopened TOMAHAWK-684:
-
The new attribute is called _activePanelTabVar.
Should be activePanelTabVar, right?
New attribute activePanelTabVar for
[
http://issues.apache.org/jira/browse/TOMAHAWK-684?page=comments#action_12436844
]
Thomas Spiegl commented on TOMAHAWK-684:
Manfred the jokey chest :)
New attribute activePanelTabVar for HtmlPanelTabbedPane
I think there may be a LiteralText or LiteralTextBlock element in
facelets. Whether it's internal only or available as a public
component, I don't know.
On 9/22/06, Thomas Spiegl [EMAIL PROTECTED] wrote:
Is there a new component in JSF 1.2 to store HTML output?
On 9/22/06, Mike Kienenberger
[
http://issues.apache.org/jira/browse/MYFACES-1420?page=comments#action_12436856
]
Mike Kienenberger commented on MYFACES-1420:
Can you provide this in the form of a unified diff, uploaded as a file
attachment to this issue?
The goal with JSF 1.2's rendering is that the ViewHandler, while it
builds the view, shouldn't render anything at all. So using JSP as your
view or Facelets as your view, the act of evaluating those artifacts
shouldn't push anything to the response.
Once you have the full component tree from
Thanks, Manfred. I forgot to check for closed issues.
I'll take care of those, and make the change when I've done so.
On 9/22/06, Manfred Geiler [EMAIL PROTECTED] wrote:
Just created the MyFaces Issue Type Scheme but were unable to assign
it to MyFaces Core because there are still 6 Test and 3
A sure NPE in CompareToValidator
Key: TOMAHAWK-685
URL: http://issues.apache.org/jira/browse/TOMAHAWK-685
Project: MyFaces Tomahawk
Issue Type: Bug
Components: Validators
Affects Versions:
[ http://issues.apache.org/jira/browse/MYFACES-738?page=all ]
Nikolay Petrov updated MYFACES-738:
---
Status: Patch Available (was: Open)
Exceptions thrown during processing of EL statements are not displayed with
the underlying cause, and there is
[ http://issues.apache.org/jira/browse/TOMAHAWK-685?page=all ]
Mike Kienenberger resolved TOMAHAWK-685.
Resolution: Fixed
Fixed. Thanks for catching that!
NPE during ClassCastException in CompareToValidator
[
http://issues.apache.org/jira/browse/MYFACES-1420?page=comments#action_12436864
]
Horia Barca commented on MYFACES-1420:
--
Sorry, I'm new here. What is a unified diff?
Null Pointer Exception in SelectItemsIterator.next() if binding is
From: "Mike Kienenberger" [EMAIL PROTECTED] Like JSP 1.2, Facelets builds the tree before rendering. Facelets might even have originated the idea :-)
Actually, Clay was sitting in a bugzilla ticket as a proposed enhancement to the shale subview component before Jacob started facelets
[ http://issues.apache.org/jira/browse/MYFACES-990?page=all ]
Martin Marinschek updated MYFACES-990:
--
Status: Patch Available (was: Open)
Unhelpful stack trace when tag value binding returns wrong type.
On 9/22/06, Gary VanMatre [EMAIL PROTECTED] wrote:
Actually, Clay was sitting in a bugzilla ticket as a proposed enhancement to
the shale subview component before Jacob started facelets
(http://weblogs.java.net/blog/edburns/archive/2005/04/javaserver_face_1.html).
Clay also builds the tree
[
http://issues.apache.org/jira/browse/MYFACES-1420?page=comments#action_12436877
]
Mike Kienenberger commented on MYFACES-1420:
It's a standard format that programs generate for creating patches.
Here's a pretty good explanation:
[ http://issues.apache.org/jira/browse/MYFACES-1420?page=all ]
Horia Barca updated MYFACES-1420:
-
Status: Open (was: Patch Available)
Null Pointer Exception in SelectItemsIterator.next() if binding is null
[ http://issues.apache.org/jira/browse/MYFACES-1420?page=all ]
Horia Barca updated MYFACES-1420:
-
Status: Patch Available (was: Open)
Null Pointer Exception in SelectItemsIterator.next() if binding is null
[ http://issues.apache.org/jira/browse/MYFACES-1420?page=all ]
Horia Barca updated MYFACES-1420:
-
Status: Patch Available (was: Open)
Null Pointer Exception in SelectItemsIterator.next() if binding is null
[ http://issues.apache.org/jira/browse/MYFACES-1420?page=all ]
Horia Barca updated MYFACES-1420:
-
Status: Open (was: Patch Available)
Null Pointer Exception in SelectItemsIterator.next() if binding is null
There is a special startup script that Bernd wrote. Apparently the
standard solaris script wasn't sufficient b/c of the processors used
on the zone.
/usr/local/continuum/bin/solaris-amd64/run.sh start
I have always started it as the mrmaven user but it might be
possible to start as yourself.
Sean,Thanks, we managed to figure it out. There is now a WIKI page describing some of the Continuum maintenance. Glad to hear your child is feeling better.On 9/22/06,
Sean Schofield [EMAIL PROTECTED] wrote:
There is a special startup script that Bernd wrote.Apparently thestandard solaris script
Declaring subviews and ajax regions is only a partial solution-- when JSF in fact should be able to re-render any component without being explicitly declared as a refreshable region (that's what we were pushing out of Facelets and JSF 1.2). Ajax4Jsf does this by decoration of existing, non-ajax
Hi all,When I use mvn idea:idea to create all the IDEA project and module files, I still have one small problem. Because of the way maven is doing the in-build package refactoring for the shared project, IDEA doesn't know which package to use and shows some of these imports as errors. This is
No, there is none. It would be nice to have a script (be it Ant, be it
a Maven plugin or whatever) which changes the shared_tomahawk / _impl
imports back to shared while developing. Before committing, we'd then
need to run this script again. I'd love that. Anyone care to write
something like this
That patch doesn't help you with the shared-project. It helps with all
other sub-projects, but not with shared.
regards,
Martin
On 9/22/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 9/22/06, Grant Smith [EMAIL PROTECTED] wrote:
When I use mvn idea:idea to create all the IDEA project and
From: [EMAIL PROTECTED]
Declaring subviews and ajax regions is only a partial solution-- when JSF in fact
should be able to re-render any component without being explicitly declared as a
refreshable region (that's what we were pushing out of Facelets and JSF 1.2).
Ajax4Jsf does this by
Hi Martin!
It would be nice to have a script (be it Ant, be it
a Maven plugin or whatever) which changes the shared_tomahawk / _impl
imports back to shared while developing.
Or being able to configure maven in a way that it will NOT refactor the
sources, instead it should simply create a shared
The UIViewRoot unique id must be persisted to guarantee that no matter the
state saving lifecycle of the component tree, that the UIViewRoot can always
produce a unique ID, despite changes to the structure of the view at 'build
time'.
I understand what you are going for with Verbatims and
Hey.
Or being able to configure maven in a way that it will NOT refactor the
sources, instead it should simply create a shared and shared-source jar.
said that, wouldn't it be possible to revert the shared_ stuff in svn at
all? And refactor tomahawk and impl itself only for the release
Hi Gary,
yes, this is what we are doing, exactly. And for the same reasons. I
haven't found a better way - without JspIdConsumers around ;).
regards,
Martin
On 9/22/06, Gary VanMatre [EMAIL PROTECTED] wrote:
From: [EMAIL PROTECTED]
Declaring subviews and ajax regions is only a partial
That option we didn't follow, cause the user would have classes then
for which he wouldn't find the sources in svn.
If part of the release-build would be that the generated sources are
also stored in both svn and as a jar-file, then the world might look
different.
regards,
Martin
On 9/22/06,
Hello Nikolay,
when I traced into myfaces source code I saw the code you are describing so it
was even more surprising to see it continue to RENDER_RESPONSE instead of
exiting.
Did you try to run Sun's Progress Bar with JSF and AJAX Sample with myfaces
libraries? The behavior I am describing
From: [EMAIL PROTECTED] The UIViewRoot unique id must be persisted to guarantee that no matter the state saving lifecycle of the component tree, that the UIViewRoot can always produce a unique ID, despite changes to the structure of the view at 'build time'. I understand what you are going for
Can we please have MyFaces versions 1.1.1 and 1.1.4 listed under the section
reading :
The following projects have officially tested and passed the TCK for their
specific technology:
Dennis Byrne
Hi Leonid,
Please send me the sample because I still heat up it all these stuff. Thanks.
Best Regards,
Nikolay Petrov
On 9/22/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hello Nikolay,
when I traced into myfaces source code I saw the code you are describing so it
was even more surprising
[
http://issues.apache.org/jira/browse/MYFACES-1328?page=comments#action_12436990
]
Nikolay Petrov commented on MYFACES-1328:
-
I really don't see a reason to put conversion:
if(converter != null itemValue instanceof
[ http://issues.apache.org/jira/browse/MYFACES-968?page=all ]
Nikolay Petrov updated MYFACES-968:
---
Status: Patch Available (was: Open)
LifecycleImpl's restoreView throws NPE when viewId is null in a portlet
context
[ http://issues.apache.org/jira/browse/TOMAHAWK-686?page=all ]
Eric Bartley updated TOMAHAWK-686:
--
Status: Patch Available (was: Open)
select message not displayed for popup
--
Key: TOMAHAWK-686
select message not displayed for popup
--
Key: TOMAHAWK-686
URL: http://issues.apache.org/jira/browse/TOMAHAWK-686
Project: MyFaces Tomahawk
Issue Type: Bug
Components: Calendar
Affects
[ http://issues.apache.org/jira/browse/TOMAHAWK-686?page=all ]
Eric Bartley updated TOMAHAWK-686:
--
Status: Patch Available (was: Open)
select message not displayed for popup
--
Key: TOMAHAWK-686
[ http://issues.apache.org/jira/browse/TOMAHAWK-686?page=all ]
Eric Bartley updated TOMAHAWK-686:
--
Status: Open (was: Patch Available)
select message not displayed for popup
--
Key: TOMAHAWK-686
[ http://issues.apache.org/jira/browse/TOMAHAWK-687?page=all ]
Eric Bartley updated TOMAHAWK-687:
--
Status: Patch Available (was: Open)
clicking on next/prev month doesn't scroll for popup
clicking on next/prev month doesn't scroll for popup
Key: TOMAHAWK-687
URL: http://issues.apache.org/jira/browse/TOMAHAWK-687
Project: MyFaces Tomahawk
Issue Type: Bug
timer to quick to hide months/year
--
Key: TOMAHAWK-688
URL: http://issues.apache.org/jira/browse/TOMAHAWK-688
Project: MyFaces Tomahawk
Issue Type: Bug
Components: Calendar
Affects Versions:
[ http://issues.apache.org/jira/browse/TOMAHAWK-688?page=all ]
Eric Bartley updated TOMAHAWK-688:
--
Status: Patch Available (was: Open)
timer to quick to hide months/year
--
Key: TOMAHAWK-688
expose javascript popup themes
--
Key: TOMAHAWK-690
URL: http://issues.apache.org/jira/browse/TOMAHAWK-690
Project: MyFaces Tomahawk
Issue Type: Improvement
Components: Calendar
Affects Versions:
expose javascript popup show week
-
Key: TOMAHAWK-691
URL: http://issues.apache.org/jira/browse/TOMAHAWK-691
Project: MyFaces Tomahawk
Issue Type: Improvement
Components: Calendar
Affects
improve t:column to generate colgroup
-
Key: TOMAHAWK-692
URL: http://issues.apache.org/jira/browse/TOMAHAWK-692
Project: MyFaces Tomahawk
Issue Type: Improvement
Components: Column
[
http://issues.apache.org/jira/browse/TOMAHAWK-606?page=comments#action_12437022
]
Mahbub Rahman commented on TOMAHAWK-606:
All tomahawk links (commandLink/commandSortHeader..) are working for me. Thanks
Martin.
Mahbub
Martin and Jacob,
Thanks for the info. I'll take a better look at the new JspIdConsumer.
Gary
-- Original message -- From: "Martin Marinschek" [EMAIL PROTECTED] Hi Gary, yes, this is what we are doing, exactly. And for the same reasons. I haven't found a better way
81 matches
Mail list logo
