I posted this to JIRA (http://issues.apache.org/jira/browse/TOMAHAWK-399), but
was told to post it here instead:
After having used the 1.1.1 release for a while, I attempted to use the 1.1.3
Snapshot with very disappointing results at compile time. Public classes and
methods
+12006/5/2, Matthias Wessendorf [EMAIL PROTECTED]:
Sean,On 5/2/06, Sean Schofield [EMAIL PROTECTED] wrote: Hmmm I still think we should release since there is a work around.ItAgreed,
will take almost as much time to do a brand new 1.1.4 release with the latest and greatest as it will be to
[ http://issues.apache.org/jira/browse/TOMAHAWK-408?page=all ]
Sharath Reddy updated TOMAHAWK-408:
---
Status: Patch Available (was: Open)
Child combo box that will be reloaded via ajax call when the parent combo
box's value is changed
Sandbox 'form' code not working
---
Key: TOMAHAWK-409
URL: http://issues.apache.org/jira/browse/TOMAHAWK-409
Project: MyFaces Tomahawk
Type: Bug
Versions: 1.1.3-SNAPSHOT
Environment: MyFaces 1.1.2, Tomahawk 1.1.3-SNAPSHOT (CVS
[ http://issues.apache.org/jira/browse/TOMAHAWK-409?page=all ]
Peter Muir updated TOMAHAWK-409:
Status: Patch Available (was: Open)
Sandbox 'form' code not working
---
Key: TOMAHAWK-409
URL:
Below is a message from the Continuum server,
http://myfaces.zones.apache.org:8080/continuum.
Provider message: The svn command failed.
Command output:
---
svn: PROPFIND request failed on '/repos/asf/myfaces/core/trunk'
[ http://issues.apache.org/jira/browse/TOMAHAWK-127?page=all ]
Petr Bouska updated TOMAHAWK-127:
-
Status: Patch Available (was: Open)
Some components do not render valid html
Key: TOMAHAWK-127
On 5/2/06, me [EMAIL PROTECTED] wrote:
After having used the 1.1.1 release for a while, I attempted to use the 1.1.3
Snapshot
with very disappointing results at compile time. Public classes and methods had
moved and vanished wholesale. I looked back at the 1.1.1 code and did not see
deprecation
Hello. It is not a comlete proposal, but I rather want to know your opinion
on the project i'm working on. It is not straight myfaces codebase related,
but you seem as most appropriate mentor. I planned to work on it before I
knew that there is SoC. But may be you will convince me of its
(6) +1 votes.
I didn't count Werner or Mike since we are in fact going to release a
new version of core. So I assume they are no longer 0 or -1. We will
release both Tomahawk 1.1.2 and Core 1.1.3 on Monday (peding the
successful core vote.)
Sean
On 4/22/06, Dennis Byrne [EMAIL PROTECTED]
JSF *really* needs this agility with CRUD scaffolding. I've been thinking
though with JEE 5 and the EJB 3 adoption, that you couldn't produce something
similar to your proposal that works off of pure EJB 3 metadata define the
pages. Something like:
ejb:form
ejb:field
ejb:dataTable
Please check out hbm2seam ( Hibernate Tools suite ) before a lot of hard work
is poured into this. There may be a large duplication of effort. The last I
checked, this was in alpha.
Dennis Byrne
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May
I've been chatting with Gavin about this for some time-- the code generation
vs. dynamic generation for scaffolding. I believe the tooling coming from
seam/hbm is all code generation where I would think there would be advantages
to having component sets that dynamically determine validators
Hi!
I developed Faces Freeway to archive this dynamic generation:
http://facesfreeway.l3x.net/sample.html
The samples are not up to date, much more can be done already.
For those wanting to browse the source code:
http://facesfreeway.l3x.net/xref/index.html
It extracts metadata from your entites
Hi!
http://facesfreeway.l3x.net/xref/index.html
The xref is not up-to-date, please use the svn
http://l3x.net/svn/facesfreeway/trunk/ to skim through the source.
Ciao,
Mario
Could only manage to run some basic tests so far, but in the spirit of
release early, release often here is my
+1
for core release 1.1.3.
Manfred
On 5/3/06, Jurgen Lust [EMAIL PROTECTED] wrote:
+1
2006/5/2, Matthias Wessendorf [EMAIL PROTECTED]:
Sean,
On 5/2/06, Sean Schofield [EMAIL
Would it be possible to include this patch into tomahawk 1.1.2/1.1.3 before the Monday release?http://issues.apache.org/jira/browse/TOMAHAWK-388Thanks,
--MikeOn 5/3/06, Sean Schofield [EMAIL PROTECTED] wrote:
(6) +1 votes.I didn't count Werner or Mike since we are in fact going to release anew
- work around available
- release early, release often
- time issue
Pssst ... what's the work around?
-Matthias
Dennis Byrne
Sean,
what you are proposing is something like this:
.../myfaces/core/branches/1_1/1_1_2
.../myfaces/core/branches/1_1/1_1_3
.../myfaces/core/trunk -- JSF 1.2
Right?
What about the following solution:
.../myfaces/core_1_1/trunk
.../myfaces/core_1_1/branches/1_1_2
Sorry, that release is locked down and the vote is closed. We don't
like to inject last minute stuff into the release. Besides all of the
work that goes into preparting and testing a release, we may break
something.
I will take a look and see if I can't apply the patch in the nightly
trunk for
[
http://issues.apache.org/jira/browse/TOMAHAWK-388?page=comments#action_12377617
]
sean schofield commented on TOMAHAWK-388:
-
Shouldn't there also be changes to the TLD and tags? What do other committers
feel about this functionality?
Add
inputCalendar doesn't respect displayValueOnly attribute
Key: TOMAHAWK-410
URL: http://issues.apache.org/jira/browse/TOMAHAWK-410
Project: MyFaces Tomahawk
Type: Bug
Components: Calendar
Versions:
Pssst ... what's the work around?
See the JIRA issue. Use client side state saving or [change]
org.apache.myfaces.NUMBER_OF_VIEWS_IN_SESSION parameter to a large
(500) value
Dennis Byrne
Sean
Well, I am just as frustrated as anyone else w/ this release, but to me this is
asking a lot from users. I am not going to take back my +1, but if anyone does
get the urge to compile a new 1.1.3 or a 1.1.4, I can retest it Friday night at
the latest.
Dennis Byrne
-Original Message-
Hi Sean!
Pssst ... what's the work around?
See the JIRA issue. Use client side state saving
this is a workaround - even if not an adequate one as - depending on the
rest of the configuration - a change to client side state saving must
not necessarily work.
or [change]
I'm not doing the work, but I think this is a blocker issue for anyone
using server-side state saving. Fortunately, that's not the case for
me. I don't think telling people to switch to client-side state
saving is realistic, nor is expecting them to guess a number big
enough to avoid the bug
I agree its non trivial but its easier to release another version in
ten days then it is to start all of this over. Every release we seem
to have these showstoppers so undoubtedly there is another one that
will be fixed tomorrow that everyone needs. Do we know when this bug
was introduced? Was
[
http://issues.apache.org/jira/browse/TOMAHAWK-388?page=comments#action_12377629
]
Mikhail Grushinskiy commented on TOMAHAWK-388:
--
In TLD only documentation change
In tomahawk.tld
attribute
namevarDetailToggler/name
I use oracle ADF with Facelets, almost every components work well, except two
problem.
1) af:table. If I defined af:commandLink for the column
af:column
af:commandLink action=editTeam immediate=true/
/af:column
If you want to enter the link in the first row of the table, your click it
once and
Sean,Few added methods which are not called from anywhere in the code can't possibly break something.The risk that this breaks something is minimal. If you look at the patch it is all it does - adds 4 new methods to a class
Release early, release often. I think you could have included it into
So in the next 24 - 48 hours you guys should figure out what you want
to do. If you want to hold up the release, then be prepared to spend
sometime doing the legwork. I will try to help the best I can.
OK. If someone can get a release candidate :
* in the zone
* with this fix only
* from the
On 5/3/06, sdfreetiger [EMAIL PROTECTED] wrote:
I use oracle ADF with Facelets, almost every components work well, except two
problem.
The [EMAIL PROTECTED] mailing list is for discussing the development of the
MyFaces JSF implementation. General JSF questions should be posted
to [EMAIL
On 5/3/06, Manfred Geiler [EMAIL PROTECTED] wrote:
Sean,
what you are proposing is something like this:
.../myfaces/core/branches/1_1/1_1_2
.../myfaces/core/branches/1_1/1_1_3
.../myfaces/core/trunk -- JSF 1.2
Right?
What about the following solution:
.../myfaces/core_1_1/trunk
On 5/3/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Added: myfaces/tomahawk/trunk/sandbox/core/src/main/resources/org/apache/myfaces/custom/pagelet/resource/cpaint2.inc.jsURL:
Craig McClanahan schrieb:
On 5/3/06, [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]*
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
Added:
myfaces/tomahawk/trunk/sandbox/core/src/main/resources/org/apache/myfaces/custom/pagelet/resource/cpaint2.inc.js
URL:
Craig McClanahan schrieb:
On 5/3/06, [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]*
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
Added:
myfaces/tomahawk/trunk/sandbox/core/src/main/resources/org/apache/myfaces/custom/pagelet/resource/cpaint2.inc.js
URL:
Craig McClanahan schrieb:
On 5/3/06, [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]*
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
Added:
myfaces/tomahawk/trunk/sandbox/core/src/main/resources/org/apache/myfaces/custom/pagelet/resource/cpaint2.inc.js
URL:
Theme jars cannot be loaded inside IBM WebSphere
Key: TOBAGO-64
URL: http://issues.apache.org/jira/browse/TOBAGO-64
Project: MyFaces Tobago
Type: Bug
Versions: 1.0.7
Reporter: Arvid Hülsebus
Assigned to:
[ http://issues.apache.org/jira/browse/TOBAGO-64?page=all ]
Arvid Hülsebus resolved TOBAGO-64:
--
Resolution: Fixed
wsjar is now supported
Theme jars cannot be loaded inside IBM WebSphere
Werner Punz schrieb:
Craig McClanahan schrieb:
On 5/3/06, [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]*
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
Added:
myfaces/tomahawk/trunk/sandbox/core/src/main/resources/org/apache/myfaces/custom/pagelet/resource/cpaint2.inc.js
URL:
Besides the reasons I mentioned earlier, you are proposing adding
functionality to an existing component (as opposed to fixing broken
functionality.) Such changes require deliberation because we don't
want to pile a bunch of stuff into the existing components if there is
another way to do this.
Hi everybody,
We are now very, very close to JavaOne and I just want give you some
heads-up regarding the annual MyFaces party. I'm pleased to say that we
are going to host this party in the same venue as last year - Thirsty
Bear - and that it is sponsored by: CA + Oracle = free beer/wine
Can it at least be submitted into trunk for tomahawk 1.1.3 so I could pick it up from nightly snapshot and test?Thanks,--MGOn 5/3/06, Sean Schofield
[EMAIL PROTECTED] wrote:
Besides the reasons I mentioned earlier, you are proposing addingfunctionality to an existing component (as opposed to
[ http://issues.apache.org/jira/browse/TOMAHAWK-162?page=all ]
sean schofield resolved TOMAHAWK-162:
-
Fix Version: 1.1.3-SNAPSHOT
Resolution: Fixed
I can't remember if there was a reason for this interface to not be public.
After looking
[ http://issues.apache.org/jira/browse/TOMAHAWK-180?page=all ]
sean schofield updated TOMAHAWK-180:
Status: Open (was: Patch Available)
Tree2 state problem when using dynamic trees
Key:
[
http://issues.apache.org/jira/browse/TOMAHAWK-180?page=comments#action_12377683
]
sean schofield commented on TOMAHAWK-180:
-
Cancelling Patch Available status since the patch is way old and will not
likely work with all of the svn and tree2
[
http://issues.apache.org/jira/browse/TOMAHAWK-384?page=comments#action_12377685
]
sean schofield commented on TOMAHAWK-384:
-
Can you submit an SVN patch instead of sending the source files? Its much
faster to apply patches this way. If you are
Once things go into SVN (trunk or branch) things tend to stay there.
So that is not really a a good place to test a single user's personal
solution. I still don't understand why you can't just compile your
own snapshot to test. Just install maven and follow the wiki. Post
on the users list if
48 matches
Mail list logo
