RE: MessageFormat
Hi, I noticed that the issue still has the status 'patch available'. By convention, shouldn't this be changed to resolved? Regards, Erik-Berndt Van: Veit Guna [mailto:[EMAIL PROTECTED] Verzonden: di 11-3-2008 9:17 Aan: MyFaces Development Onderwerp: Re: MessageFormat At least a little bit I can contribute back :). Original-Nachricht Datum: Tue, 11 Mar 2008 00:06:15 +0100 Von: Thomas Spiegl [EMAIL PROTECTED] An: MyFaces Development dev@myfaces.apache.org Betreff: Re: MessageFormat fixed, thanks for your patch! Thomas On Mon, Mar 10, 2008 at 11:22 PM, Thomas Spiegl [EMAIL PROTECTED] wrote: Hi, I'll have a look at it. -Thomas On Mon, Mar 10, 2008 at 11:17 PM, Veit Guna [EMAIL PROTECTED] wrote: Hi. Is there any chance that this patch will be included in the 1.1.6 release or even in the 1.1.5 version in a fix-release? https://issues.apache.org/jira/browse/MYFACES-1827 -- http://www.irian.at http://www.irian.at/ Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- http://www.irian.at http://www.irian.at/ Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger Disclaimer: This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. winmail.dat
RE: [site] new pages ?
I prefer the confluence wiki used by quite a few other apache projects, such as http://cwiki.apache.org/CXF/. Regards, Erik-Berndt -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Matthias Wessendorf Verzonden: maandag 5 november 2007 8:23 Aan: MyFaces Development Onderwerp: Re: [site] new pages ? I think we will continue to use moin-moin wiki, which is OpenSource. -Matthias On 11/4/07, Ron Smits [EMAIL PROTECTED] wrote: Hi Matthias Looks real nice, but if we start doing pages like that could we please do something about the styling of the wiki? Before adding more pages would it not be real nice if we had a nicer looking wiki? JSF is meant to be a good framework to develop modern looking sites. should the wiki not reflect that? Ron On 11/4/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: Hi, I found these two site: http://geronimo.apache.org/get-involved.html http://geronimo.apache.org/found-a-bug.html I think we should add similar version to our MyFaces homepage as well. It would also be very nice to have a page, that is similar to this as well: http://geronimo.apache.org/events.html WDYT ? -Matthias -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org -- I reject your reality and substitute my own --- Adam Savage, the mythbusters -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org Disclaimer: This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
RE: [VOTE] release of Apache MyFaces Orchestra 1.0 (II)
Hi, Wouldn't the wiki be a more appropriate place to document this? Regards, Erik-Berndt -Oorspronkelijk bericht- Van: Mario Ivankovits [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 9 oktober 2007 20:54 Aan: MyFaces Development Onderwerp: Re: [VOTE] release of Apache MyFaces Orchestra 1.0 (II) Hi Dan! Do you have instructions how to deal with latest changes with LocalFrameworkAdapter? Speaking in code it should be something like this LocalFrameworkAdapter frameworkAdapter = new LocalFrameworkAdapter(); frameworkAdapter.setConversationMessager(new LogConversationMessager()); FrameworkAdapter.setCurrentInstance(frameworkAdapter); where the LogConversationMessager could be replaced by your own implementation and you should be able to set it up through your spring config. Dan, thanks for staying with us and sorry for the inconvenience lately, but once we have settled for the 1.0 release this api should be freezed for a longer period ... :-) Ciao, Mario Disclaimer: This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Compatability matrix / tomahawk 1.1.5 release
Hi, I noticed that the new compatibility matrix refers to Tomahawk SNAPSHOT 1.1.5 However, the rc2 of tomahawk has already been mirrored across apache sites. (see for example http://apache.cs.uu.nl/dist/myfaces/binaries/ or http://apache.cs.uu.nl/dist/myfaces/source/) When is the download page going to be updated (so that the wiki can be updated too)? Regards Erik-Berndt -Oorspronkelijk bericht- Van: Paul Spencer [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 17 april 2007 14:39 Aan: MyFaces Development Onderwerp: Re: What is the status of [VOTE] MyFaces Tomahawk 1.1.5 (rc2) ? Manfred, Thank you for the update and you efforts. Paul Spencer Manfred Geiler wrote: current status is: release manager (=me) needs some free minutes to copy the artifacts and assemblies and change the site will try it in the evening (european time) --Manfred On 4/17/07, Paul Spencer [EMAIL PROTECTED] wrote: This vote has been open for 4+ days with a bunch of +1, few +0 and no -1. When will the voting process close? How long after the vote closes will the release be posted? Paul Spencer. Disclaimer: This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
RE: Use 1.2 as current now
Sounds like a good idea. One question however: Tomcat 6 requires JDK 5. Does this mean that the trunk will drop JDK 1.4 compatibility? Regards, Erik-Berndt -Oorspronkelijk bericht- Van: Martin Marinschek [mailto:[EMAIL PROTECTED] Verzonden: woensdag 18 april 2007 10:07 Aan: MyFaces Development Onderwerp: Use 1.2 as current now Hi *, I wonder if we should switch the trunk to be the 1.2 branch now, cause our next release will surely be fully 1.2 compatible (Tomcat 6 is out now, so the sooner we're done, the better)... We'll have a lot better testing of 1.2 if we do it like this - wdyt? regards, Martin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces Disclaimer: This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
RE: [Announce] Release of Apache Trinidad Podling's 1.0.0-incubating
Hi, Congratulations on the first incubating release! However, I am sorry to find that the source jars are missing for both the examples and binaries. I know these can be retrieved from svn (URL?), but is it possible to add them in upcoming releases? Many thanks and regards, Erik-Berndt -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Matthias Wessendorf Verzonden: zondag 25 maart 2007 17:06 Aan: MyFaces Development; MyFaces Discussion Onderwerp: [Announce] Release of Apache Trinidad Podling's 1.0.0-incubating The Apache Trinidad Podling is pleased to announce the release of Trinidad Core 1.0.0-incubating. Apache Trinidad is a JavaServer(tm) Faces 1.1 component library. Apache Trinidad Core 1.0.0-incubating is available in both binary and source distributions: * http://incubator.apache.org/adffaces/download.html Apache Trinidad is also available in the incubator Maven repository under Group ID org.apache.myfaces.trinidad. (http://people.apache.org/repo/m2-incubating-repository/) Release Notes: http://wiki.apache.org/myfaces/ADF_Faces/core_release_1_0_0-incubating Enjoy! -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com Disclaimer: This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
RE: [VOTE] New Apache MyFaces Fusion Name
[x] Apache MyFaces Orchestra [ ] Apache MyFaces Aurora [ ] Apache MyFaces Connections Regards, Erik-Berndt Disclaimer: This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
RE: Tomahawk 1.1.5 release plans?
I agree. The old 1.1.4 RC is getting really aged now. However, it seems strange to just throw it away and follow-up 1.1.3 by 1.1.5 Regards, Erik-Berndt Van: Cagatay Civici [mailto:[EMAIL PROTECTED] Verzonden: vr 23-2-2007 9:27 Aan: MyFaces Development Onderwerp: Re: Tomahawk 1.1.5 release plans? Hi, +1 for throwing away 1.1.4, creating a new branch using current trunk and releasing 1.1.4. Cagatay On 2/23/07, Manfred Geiler [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Ok folks, I will try to start the release process for tomahawk next week. Well, regarding the branch there are various possibilities: - use the already existing 1.1.4 branch from Nov. 2006 and release 1.1.4 - throw away existing 1.1.4 branch, create new branch and release 1.1.4 - (optionally) throw away existing 1.1.4 branch, create new 1.1.5 branch, skip version number 1.1.4 and release 1.1.5 If we use one of the two create new branch strategies, which revision is stable enough. Current head? Thanks, Manfred On 2/22/07, Jeff Bischoff [EMAIL PROTECTED] wrote: +1 on this idea. Tomahawk has settled down since the Dojo move and has been running relatively stable. Best to ensure the next release is branched sometime before any more big changes. (Tomahawk 1.1.4 RC is very good too) :) Paul Spencer wrote: We just completed a MyFaces 1.1.5 release, which resolved blockers related to Tomahawk. Can we get a Tomahawk release done before we start changing things for Fusion? Paul Spencer Disclaimer: This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. winmail.dat
RE: [ANNOUNCE] MyFaces Core v1.1.5 Release
Hi, I noticed that there is no tag for 1.1.5 yet in https://svn.apache.org/repos/asf/myfaces/core/tags/ Regards, Erik-Berndt -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Manfred Geiler Verzonden: maandag 19 februari 2007 12:51 Aan: announce@apache.org; announce@myfaces.apache.org CC: MyFaces Development; MyFaces Discussion Onderwerp: [ANNOUNCE] MyFaces Core v1.1.5 Release The Apache MyFaces team is pleased to announce the release of MyFaces Core 1.1.5. MyFaces Core is a JavaServer(tm) Faces 1.1 implementation as specified by JSR-127. MyFaces Core has passed Sun's JSR-127 TCK and is 100% compliant with the JSR-127 specification. MyFaces Core 1.1.5 is available in both binary and source distributions. * http://myfaces.apache.org/download.html MyFaces Core is also available in the central Maven repository under Group ID org.apache.myfaces.core. Release Notes - MyFaces Core - Version 1.1.5 ** Fixed Bugs * [MYFACES-437] - f:attribute does not work with x:dataTable * [MYFACES-660] - (Patch provided) request scoping from Portlet Action- to RenderRequest should not occur via Attribute Request Map * [MYFACES-689] - PropertyResolverImpl.getType(Object base, int index) return null if base instanceof Object[] * [MYFACES-731] - selectManyListbox calls converter getAsString passing in string value during form post * [MYFACES-828] - HtmlCheckboxRenderer ignores readonly * [MYFACES-968] - LifecycleImpl's restoreView throws NPE when viewId is null in a portlet context * [MYFACES-1025] - panelGrid does always render a border-attribute * [MYFACES-1029] - Duplicate sibling ids allowed * [MYFACES-1304] - DigesterFacesConfigDispenserImpl shuld respect order of registered renderkits * [MYFACES-1328] - UISelectOne and UISelectMany fail with custom converter that returns java.lang.String from getAsObject() method. * [MYFACES-1368] - Fix case sensitivity for context params * [MYFACES-1384] - After switch from myfaces-impl-1.1.3 (release) to myfaces-1.1.5-SNAPSHOT, javascript throw error 'Object expected' * [MYFACES-1386] - PropertyResolverImpl.setProperty lacks usefull error mesage if write method not found * [MYFACES-1393] - MyFaces state information is rendered by MyFaces Form * [MYFACES-1397] - getValidJavascriptNameAsInRI throws java.lang.IllegalArgumentException: Illegal group reference * [MYFACES-1406] - Core and Shared project has dependency on myfaces:myfaces-api version 1.1.1 * [MYFACES-1407] - JS oamSubmitForm() params order incorrect * [MYFACES-1410] - CLONE -PropertyResolverImpl.getType(Object base, int index) return null if base instanceof Object[] * [MYFACES-1412] - Restore view phase does not conforms specification * [MYFACES-1413] - JS error in function oamSubmitForm(...) * [MYFACES-1415] - WebXmlParser needs to be aware of changes in web.xml in version 2.4 of the Servlet spec * [MYFACES-1420] - Null Pointer Exception in SelectItemsIterator.next() if binding is null * [MYFACES-1421] - MyFaces not working with Struts Faces Form * [MYFACES-1425] - wrong text for link in getting started * [MYFACES-1427] - Error restoring view * [MYFACES-1428] - Application cannot be started with Snapshot 1.1.5 of 27th Sept./1st Oct. * [MYFACES-1430] - selectOneMenu looses values after clicking immediate link (since 1.1.4) * [MYFACES-1479] - SerialFactory breaks Portlet bridge * [MYFACES-1481] - MyFacesGenericPortlet does not work in a cluster * [MYFACES-1486] - Error Handling in Property-Resolver-Impl * [MYFACES-1489] - ExternalContext Maps * [MYFACES-1490] - DateTimeConverter exception on parsing time * [MYFACES-1495] - client side state saving bug * [MYFACES-1500] - Default values in standard-faces-config.xml * [MYFACES-1510] - h:form does not render accept-charset ** Improvements * [MYFACES-652] - Findbugs ant-tasks * [MYFACES-1032] - use a javascript method in commondLink for lesser html size * [MYFACES-1366] - Error in javascript function * [MYFACES-1373] - Add exception to logger for output exception stack trace * [MYFACES-1385] - Remove all of the unused code, variables, and import statements identified by Eclipse 3.1.2 * [MYFACES-1405] - Interoperability with Facelets * [MYFACES-1411] - Lifecycle phase executions repetitions * [MYFACES-1418] - javax.faces.validator - DoubleRangeValidator, LengthValidator, LongRangeValidator are very similar, refactor common behaviour * [MYFACES-1419] - javax.faces.convert - refactor common behaviour + DateTimeConverter changes * [MYFACES-1422] - findNestingForm() tests only against component family and against instanceof UIForm * [MYFACES-1423] - Log jar-files on startup * [MYFACES-1469] - State-saving now uses the parameter javax.faces.ViewState - as proposed by the 1.2 spec * [MYFACES-1488] - ASF Source Header and Copyright Notice Policy
Any sandbox components eligible for promotion?
Hi, Now that a new myfaces core release seems near, I hope the same will happen for tomahawk. Since the branch for tomahawk 1.1.4 is rather outdated by now, I wondered whether there are any sandbox components eligible for promotion, including the dojo components. It has been some time since the dojoInitializer was promoted, and I have not seen many issues for it. Any opinions? Regards, Erik-Berndt Disclaimer: This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
RE: MyFaces 1.1.5 Status (again)?
I seem to remember one of the things was the ICLA required for the contributor of the patch for https://issues.apache.org/jira/browse/MYFACES-1411. However, according to the the list on http://people.apache.org/~jim/committers.html, this should no longer be an issue. -Oorspronkelijk bericht- Van: Michael Hartman [mailto:[EMAIL PROTECTED] Verzonden: donderdag 1 februari 2007 16:39 Aan: dev@myfaces.apache.org Onderwerp: MyFaces 1.1.5 Status (again)? Pardon me for the pithy post but, what is holding up this release? I see only 7 issues reported against 1.1.5-SNAPSHOT, none of which are blockers and it's been 4 months since 1.1.4 with 50 fixes reported as Resolved or Closed for 1.1.5-SNAPSHOT. -- View this message in context: http://www.nabble.com/MyFaces-1.1.5-Status-%28again%29--tf3155536.html#a 8750366 Sent from the My Faces - Dev mailing list archive at Nabble.com. Disclaimer: This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
RE: Core Release 1.1.5
Great news! How about the current blocking issues for core 1.1.5? Shouldn't they be fixed first? E.g. https://issues.apache.org/jira/browse/MYFACES-1488 -- ASF source header + copyright notice And https://issues.apache.org/jira/browse/MYFACES-1479 -- SerialFactory breaks portlet bridge Also there are some 1.1.5 issues with patch available status. Any chance that these might be included? Regards, Erik-Berndt Scheper -Oorspronkelijk bericht- Van: Thomas Spiegl [mailto:[EMAIL PROTECTED] Verzonden: woensdag 8 november 2006 15:40 Aan: MyFaces Development Onderwerp: Core Release 1.1.5 We should release Core 1.1.5 soon, as it's needed for the next tomahawk release. Therefore I tested the current trunk against Sun's TCK and fixed all issues. MyFaces core is new 100 % compatible. I have some time to prepare the release, but will need help from some of you (eg. Wendy). First of all I will create a branch for core 1.1.5 and shared 2.0.5 and start the release process. -Thomas -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces Disclaimer: This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
RE: [jira] Created: (TOMAHAWK-768) t:datascroller and sort headers don't work with ajax4jsf
Hi, See the jira issue below. Isn't there a policy against using fake names? Regards, Erik-Berndt Scheper -Oorspronkelijk bericht- Van: Popcorn (JIRA) [mailto:[EMAIL PROTECTED] Verzonden: vrijdag 3 november 2006 6:51 Aan: dev@myfaces.apache.org Onderwerp: [jira] Created: (TOMAHAWK-768) t:datascroller and sort headers don't work with ajax4jsf t:datascroller and sort headers don't work with ajax4jsf Key: TOMAHAWK-768 URL: http://issues.apache.org/jira/browse/TOMAHAWK-768 Project: MyFaces Tomahawk Issue Type: Bug Components: Data Scroller, Sort Header Affects Versions: 1.1.3 Reporter: Popcorn The datascroller and sort headers stop working inside an ajax-rendered area with Ajax4jsf. The components need to be patched. For details, see this link: http://marc.theaimsgroup.com/?l=myfaces-userm=116237031123948w=2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira Disclaimer: This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
RE: next tomahawk release
Hi, Well, we're currently waiting for release 1.1.4 to be finished. This release is blocked until myfaces core 1.1.5 is released. See http://wiki.apache.org/myfaces/TomahawkRelease114 So put your hopes on core 1.1.5 first (and submit the patches for blocking issues ;-) See https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truemod e=hidesorter/order=DESCsorter/field=priorityresolution=-1pid=10600f ixfor=12311960 for the open issues on core 1.1.5 Snapshots are always available in the nightlies directory. http://people.apache.org/builds/myfaces/nightly/ Regards, Erik-Berndt Scheper -Oorspronkelijk bericht- Van: Sebastian Menge [mailto:[EMAIL PROTECTED] Verzonden: donderdag 2 november 2006 11:12 Aan: dev@myfaces.apache.org Onderwerp: next tomahaw release Hi 1) I read somewhere, that tomahawk 1.1.5-SNAPSHOT will soon be released as 1.1.4. Is that true? Can you estimate when? (Q4 2006, Q1/2/3 2007) ?? 2) Is there a maven repository where we can get latest tomahawk-1.1.5-SNAPSHOT? TIA, Seb. Disclaimer: This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
RE: Tomahawk 1.1.4 - STATUS
Hi, I'm sorry that I cannot the assembly, since it requires a myfaces snapshot. Is a release schedule available for the new core release? However, for new users it would be very nice to have a complete tomahawk distribution again. I.e. one archive with binaries, a second archive with sources and a third archive with the sample apps. This was the case before the move towards maven, and I have sincerely missed these recently. Regards, Erik-Berndt Van: Wendy Smoak [mailto:[EMAIL PROTECTED] Verzonden: do 19-10-2006 18:19 Aan: MyFaces Development Onderwerp: Re: Tomahawk 1.1.4 - STATUS On 10/17/06, Thomas Spiegl [EMAIL PROTECTED] wrote: Just moved 21 unresolved issues from fixed version 1.1.4-SNAPSHOT to 1.1.5-SNAPSHOT. Thanks. I should have only moved the resolved issues to 1.1.4. Any comments on the proposed release assemblies? * http://people.apache.org/builds/myfaces/tomahawk-1.1.x/ Are the example apps supposed to be included? -- Wendy Disclaimer: This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. winmail.dat
RE: how do we handle old taglib definitions in the sandbox
Isn't that the risk of using components of the sandbox? IMHO, sandbox components should always be subject to change without notice. If they are promoted to 'production quality', then so much the better. Therefore, my personal preference would be to remove all references in the sandbox after the promotion. I think -correct me if I'm wrong- that the same was done for the schedule component, which was the last to be moved from sandbox to tomahawk. It is easy enough to change the namespace in the jsp's after an upgrade (global search and replace) and -as I said- everyone should know that sandbox components are used at your own risk. -Oorspronkelijk bericht- Van: news [mailto:[EMAIL PROTECTED] Namens Werner Punz Verzonden: donderdag 12 oktober 2006 23:19 Aan: dev@myfaces.apache.org Onderwerp: how do we handle old taglib definitions in the sandbox Now that I am finally moving the first dojo component out I have one last remaining structural problem, how do we handle the taglib issue. As far as I can see, once I move a component from the sandbox to tomahawk I will break the namespace. Not that I mind a clear cut on this issue, but some users already have started to use the sandbox components. Now theoretically it should be possible to leave the tld defs in the sandbox while the code is moved upwards. for the time being, with a slow deprecation of the affected entries over time. How are we going to handle this issue. I need a good answer here so that I finally can set the dojo migration to resolved. Disclaimer: This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
RE: [ANNOUNCE] MyFaces Tomahawk 1.1.2 Released
Hi, I have just downloaded the new tomahawk and myfaces releases. However, on the download page there are no download packages for the sources and examples. It would be very nice if these could be added to the download page (http://myfaces.apache.org/download.html) Regards, Erik-Berndt -Oorspronkelijk bericht- Van: Manfred Geiler [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 9 mei 2006 10:25 Aan: announce@apache.org; announce@myfaces.apache.org; dev@myfaces.apache.org; users@myfaces.apache.org Onderwerp: [ANNOUNCE] MyFaces Tomahawk 1.1.2 Released Hi All, The MyFaces PMC is proud to announce a new and great release of MyFaces Tomahawk [1]. MyFaces Tomahawk 1.1.2 is a set of JavaServer(tm) Faces 1.1 compatible custom and extended standard components and other JSF goodies. Please note: This is the first Tomahawk release that is fully independent of the MyFaces Core Implementation. From now on you can use any Tomahawk release with any MyFaces Core release with a release number greater than 1.1.2 as well as any other JavaServer(tm) Faces 1.1 compliant implementation. Find below a list of bugs that have been fixed in this release. There is also a number of new features and improvements. Enjoy! Manfred [1] http://myfaces.apache.org/tomahawk/ Release Notes - MyFaces Tomahawk - Version 1.1.2 ** Bug * [TOMAHAWK-20] - pageDirection layout for selectManyCheckbox not rendered correctly * [TOMAHAWK-104] - dataScroller divide by zero error should be changed to a missing row attribute error * [TOMAHAWK-132] - ExtensionsFilter calls addResource.parseResponse() on non-HTML responses * [TOMAHAWK-136] - Schedule component: Add rowheight property to the detailed view (Day View) similar to MonthRowHeight, compactWeekRowHeight * [TOMAHAWK-139] - Some fixes to inputSuggestAjax component * [TOMAHAWK-150] - custom ScheduleEntryRenderer is applied to all schedule components in the same application * [TOMAHAWK-152] - t:selectOneRadio and t:radio should do the same when check the selected item * [TOMAHAWK-156] - DataList doesn't validate or update model in 1.1.2 nightlies * [TOMAHAWK-164] - CompareToValidator and EqualValidator does not work on generic EditableValueHolders, only UIInput subclasses (ADF Faces) * [TOMAHAWK-172] - UIColumns does not support java.util.Set * [TOMAHAWK-181] - Picklist does not support non-string values * [TOMAHAWK-187] - ClassCastException using panelTabbedPane in nightly build * [TOMAHAWK-196] - PopupCalendar base href= tag * [TOMAHAWK-198] - Extra jar in simple examples * [TOMAHAWK-201] - Null pointer exception in org.apache.myfaces.shared_tomahawk.renderkit.html.HtmlRendererUtils.sele ctContentType * [TOMAHAWK-203] - Triggering of JavaScript with JSCookMenu broken. * [TOMAHAWK-215] - The content of the facet detailStamp in t:datatable is not decoded/validated/updated * [TOMAHAWK-216] - TabChangeListener not invoked * [TOMAHAWK-219] - stateChangedNotifier does not use ValueBinding for the confirmation message * [TOMAHAWK-239] - aliasbean + aliasing a member + binding = fails * [TOMAHAWK-242] - AddResourceFactory throws Exception * [TOMAHAWK-257] - tomahawk xml parser: Ignored element 'servlet-name' as child of 'filter-mapping'. * [TOMAHAWK-266] - Master-detail example not working * [TOMAHAWK-267] - Collapsible panel in datatable gets jammed * [TOMAHAWK-268] - Date tag does not display properly, javascript errors are returned * [TOMAHAWK-269] - JSCookMenu can't be used as a child of a form, and AddResources code for custom themes is incomplete * [TOMAHAWK-270] - The first part of the examples-config.xml file for the sandbox examples is missing * [TOMAHAWK-271] - AddResource has changes that break custom classes and JSP pages using javascriptLocation * [TOMAHAWK-272] - commandLink not working inside dataList * [TOMAHAWK-273] - t:inputCalendar/ stops working with Facelets * [TOMAHAWK-274] - HtmlDataTable.getClientId() should use info() not warn() when using forcedIdIndex * [TOMAHAWK-275] - No way to make selection from code in Tree2 * [TOMAHAWK-276] - The facet for popup component only accept components with children * [TOMAHAWK-277] - inputCalendar localized month names problem * [TOMAHAWK-278] - t:tree2: javascript error in some version of IE * [TOMAHAWK-279] - InputSuggestAjax does not work when javax.faces.STATE_SAVING_METHOD=server * [TOMAHAWK-280] - selectOne[Country/[EMAIL PROTECTED] VB ignored * [TOMAHAWK-281] - tree2 affected by changes to UIViewRoot * [TOMAHAWK-282] - AddResource should use the current character encoding * [TOMAHAWK-283] - InputDate(s) within dataTable submitting incorrect dates * [TOMAHAWK-284] - Calendar popup is incorrectly positioned inside scrolling div * [TOMAHAWK-285] - HtmlCalendarRenderer doesn't respect
RE: Myfaces running on WebSphere Application Server v6.1
Yes, this should work. Sometimes you have to set the classloader for the EAR to parent_last as well (especially if you include jar's in the EAR and add them to the manifest in the war file. The cause of this issue is that IBM has packaged its own (and very buggy I might add) version of the JSF reference implementation with WAS 6.0. The same is required if you want to use commons logging within your web application as IBM has wisely included its own version of this as well (without updating the package structure). Regards, Erik-Berndt Scheper Sogeti Nederland BV Van: [EMAIL PROTECTED] namens Eric Hedström Verzonden: wo 26-4-2006 21:36 Aan: MyFaces Development Onderwerp: Re: Myfaces running on WebSphere Application Server v6.1 The better approach is to set the classloader policy for your web module in the Enterprise Application to Parent last. This tells WebSphere that for your application, you want it to favor the libraries in the WAR over those bundled with WebSphere. We've run into this problem with several JARs (JDOM, Mozilla Rhino js.jar, etc.) for which Websphere includes an older version or its own custom version. Customers definitely prefer this approach to hacking on the app server itself. The app I'm working on now is using the Sun RI impl with Tomahawk 1.1. Without the classloader setting it chokes even on the Sun RI. Eric On 4/20/06, Thomas Spiegl [EMAIL PROTECTED] wrote: You may find this helpful http://wiki.apache.org/myfaces/Websphere_Installation On 4/20/06, Graham Crooks [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I am porting on behalf of a software house, an application that is currenly running on Tomcat Server under Redhat Linux. The developer has made extensive use of the MyfacesTomahawk extensions and these seem to work fine in Tomcat but within WebSphere Appication Server anything that is declared between the tomahawk specific tags is not displayed. The message I am seeing is: ERROR [org.apache.myfaces.lifecycle.LifecycleImpl] - Assumed extension mapping, but there is no extension in /software/ [org.apache.myfaces.lifecycle.LifecycleImpl.deriveViewId(LifecycleImpl.java :422)] After lots of log setting I know that this error is NOT being produced by Websphere in fact it appears in the /home/user1/logs/error.log, and I believe this is being written to by: org/apache/myfaces/lifecycle/LifecycleImpl.java This is the MyFaces extension declarations within the web.xml filter filter-nameMyFacesExtensionsFilter/filter-name filter-classorg.apache.myfaces.component.html.util.ExtensionsFilter/filter-class init-param param-namemaxFileSize/param-name param-value20m/param-value /init-param /filter filter-mapping filter-nameMyFacesExtensionsFilter/filter-name url-pattern/software/url-pattern /filter-mapping /software resolves to the JSF servlet. I have tried changing around the /software to /*.jsf etc but this doesn't make any difference. Can anyone tell me where I might start trying to look to figure this through.Tks -- View this message in context: http://www.nabble.com/Myfaces-running-on-WebSphere-Application-Server-v6.1-t1480412.html#a4006869 Sent from the My Faces - Dev forum at Nabble.com. -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces Disclaimer: This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. winmail.dat
RE: Myfaces running on WebSphere Application Server v6.1
Sorry, I misread the initial post. I thought Eric suggested setting the classloader for the web module to parent_last (yes, there are two places to set this). That's the first one I usually set. Hence my suggestion you might also need to set the classloader for the EAR. To solve all classloader issues like this, google for mustgather classloader issues site:ibm.com, and you are shown all IBM mustgather pages for the various incarnations of WAS. They show you how to enable tracing and using trace.log you can find the jar used to load your classes. BTW: typical you need google to find anything on the IBM site ;-) Regards, Erik-Berndt Scheper Van: Scheper, Erik-Berndt [mailto:[EMAIL PROTECTED] Verzonden: wo 26-4-2006 21:43 Aan: MyFaces Development Onderwerp: RE: Myfaces running on WebSphere Application Server v6.1 Yes, this should work. Sometimes you have to set the classloader for the EAR to parent_last as well (especially if you include jar's in the EAR and add them to the manifest in the war file. The cause of this issue is that IBM has packaged its own (and very buggy I might add) version of the JSF reference implementation with WAS 6.0. The same is required if you want to use commons logging within your web application as IBM has wisely included its own version of this as well (without updating the package structure). Regards, Erik-Berndt Scheper Sogeti Nederland BV Van: [EMAIL PROTECTED] namens Eric Hedström Verzonden: wo 26-4-2006 21:36 Aan: MyFaces Development Onderwerp: Re: Myfaces running on WebSphere Application Server v6.1 The better approach is to set the classloader policy for your web module in the Enterprise Application to Parent last. This tells WebSphere that for your application, you want it to favor the libraries in the WAR over those bundled with WebSphere. We've run into this problem with several JARs (JDOM, Mozilla Rhino js.jar, etc.) for which Websphere includes an older version or its own custom version. Customers definitely prefer this approach to hacking on the app server itself. The app I'm working on now is using the Sun RI impl with Tomahawk 1.1. Without the classloader setting it chokes even on the Sun RI. Eric On 4/20/06, Thomas Spiegl [EMAIL PROTECTED] wrote: You may find this helpful http://wiki.apache.org/myfaces/Websphere_Installation On 4/20/06, Graham Crooks [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I am porting on behalf of a software house, an application that is currenly running on Tomcat Server under Redhat Linux. The developer has made extensive use of the MyfacesTomahawk extensions and these seem to work fine in Tomcat but within WebSphere Appication Server anything that is declared between the tomahawk specific tags is not displayed. The message I am seeing is: ERROR [org.apache.myfaces.lifecycle.LifecycleImpl] - Assumed extension mapping, but there is no extension in /software/ [org.apache.myfaces.lifecycle.LifecycleImpl.deriveViewId(LifecycleImpl.java :422)] After lots of log setting I know that this error is NOT being produced by Websphere in fact it appears in the /home/user1/logs/error.log, and I believe this is being written to by: org/apache/myfaces/lifecycle/LifecycleImpl.java This is the MyFaces extension declarations within the web.xml filter filter-nameMyFacesExtensionsFilter/filter-name filter-classorg.apache.myfaces.component.html.util.ExtensionsFilter/filter-class init-param param-namemaxFileSize/param-name param-value20m/param-value /init-param /filter filter-mapping filter-nameMyFacesExtensionsFilter/filter-name url-pattern/software/url-pattern /filter-mapping /software resolves to the JSF servlet. I have tried changing around the /software to /*.jsf etc but this doesn't make any difference. Can anyone tell me where I might start trying to look to figure this through.Tks -- View this message in context: http://www.nabble.com/Myfaces-running-on-WebSphere-Application-Server-v6.1-t1480412.html#a4006869 Sent from the My Faces - Dev forum at Nabble.com. -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces Disclaimer: This message contains information that may be privileged or confidential and is the property
