Re: Problem with nested CDATA sections in scripts in a PPR
It's a little bit lame that the primefaces guys never run their tests
with MyFaces.
-Matthias
On Mon, Jul 12, 2010 at 7:21 AM, Marcus Büttner m...@buett.at wrote:
Hi,
I've a similar problem with primefaces and myfaces. The standard f:ajax to
rerender a component works as espected but p:ajax do not update other
primefaces components. I've posted it to the primefaces forum but with
mojarra it seems to work.
my example:
h:form id=myForm
h:selectOneMenu id=selectMenu value=#{myBean.menuValue}
f:selectItem itemValue=true itemLabel=Yes/
f:selectItem itemValue=false itemLabel=No/
p:ajax event=change update=output process=selectMenu/
/h:selectOneMenu
p:inputMask id=output mask= value=#{myBean.menuValue}/
h:commandButton action=action/
/h:form
Could this be the same cause?
Marcus
Bruno Aranda schrieb:
I think you may be right, I have tried to test cases (attached to the
JIRA ticket). One using a primefaces button and the other using a jsf
standard button, and the latter works as expected.
Bruno
On 12 July 2010 15:03, Werner Punz werner.p...@gmail.com wrote:
Superb, as I said I am not entirely sure if myfaces is at fault here, my
personal guess goes towards a custom partial response writer on the
PrimeFaces side, but I am guessing here, because we have fallback code in
our ppr responseWriter which exactly should cover what we have here:
private String postProcess(StackEntry currentElement) throws
IOException
{
currentElement.getWriter().flush();
StringBuffer buffer = currentElement.getDoubleBuffer().getBuffer();
String resultString = buffer.toString();
//section http://www.w3.org/TR/REC-xml/#sec-cdata-sect everything
is
parsed
//until it hits a ]] hence we need to do some mapping here
//ok since our maximum string size is Integer.MAX_VALUE (most JVMs
use char [] as
//representations
//we can work on strings directly, instead of having to go through
streams
//it is absolutely unlikely that we will ever have a buffered
stream
bigger than that
//for our writer!
if (resultString.contains(]])) {
//we now first remove pending javascript CDATA blocks
//the reason is if we leave them the ppr chokes on them
//the syntax from the auto generated CDATA usually is
//\s+![CDATA[
resultString =
resultString.replaceAll(//\\s*((!\\[CDATA\\[)|(\\]\\]\\)), );
//now to fullfill the xml spec we have to replace all ]] with
blocks of cdata
resultString = resultString.replaceAll(\\]\\]\\,
]]![CDATA[![CDATA[);
}
return resultString;
}
The idea is to double buffer a ppr cdata block and do some final
postprocessing by excaping ]] by valid cadata escapes.
So this section should never be rendered that way
//]]/script
would have been crrect
]]![CDATA[![CDATA[/script
instead it should have gotten a split into two cdata blocks.
But we may have a bug here as well.
Werner
Am 12.07.10 15:52, schrieb Bruno Aranda:
I will create a simple test case,
Cheers,
Bruno
On 12 July 2010 14:47, Werner Punzwerner.p...@gmail.com wrote:
Hi Bruno can you file a snippet of the original xhtml markup into
https://issues.apache.org/jira/browse/MYFACES-2811
Werner
Am 12.07.10 15:33, schrieb Werner Punz:
Hi Bruno, please file a bugreport on it. We should fix this before
2.0.1
this is a bug in the ppr responsewriter on the server side. I was
fixing
exactly this issue a few months ago, maybe we have some regression bug
here.
Werner
Am 12.07.10 14:48, schrieb Bruno Aranda:
Hi,
I have a partial response that contains invalid syntax because CDATA
sections are nested. For example, in my app this code is generated in
the partial response:
?xml version=1.0
encoding=UTF-8?partialResponsecomponentscomponentideditorForm/idoutput![CDATA[form
id=editorForm name=editorForm method=post
action=/editor/curate/publication.jsf?conversationContext=2
enctype=application/x-www-form-urlencodedspan
id=growl/spanscript type=text/javascript//![CDATA[
jQuery.gritter.add({title:'Publication saved',text:'AC:
EBI-2637354',image:'/editor/primefaces_resource/2.0.3-SNAPSHOT/primefaces/growl/assets/info.png?conversationContext=2',sticky:false});
//]]/script
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Re: Mark issues for JSF 2.1
+1 on option #1 On Thu, Jul 8, 2010 at 7:01 PM, Michael Concini mconc...@gmail.com wrote: +1 for #1. On 7/8/2010 9:29 PM, Hazem Saleh wrote: +1 for the first option. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
MyFaces PMC += Max Starets
Dear MyFaces community, please welcome our new MyFaces PMC member Max Starets. Max is mostly working on Apache MyFaces Trinidad. Therefore last week there was a vote to invite him to the MyFaces Project Management Committee (PMC) and fortunately he did accept. Max, Please subscribe to the priv...@myfaces.apache.org list and update your status on the site: http://svn.apache.org/repos/asf/myfaces/myfaces-master-pom/trunk/pom.xml Thanks. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
MyFaces PMC += Jan-Kees van Andel
Dear MyFaces community, please welcome our new MyFaces PMC member Jan-Kees van Andel. Jan-Kees is working on several things at Apache MyFaces. Therefore last week there was a vote to invite him to the MyFaces Project Management Committee (PMC) and fortunately he did accept. Jan-Kees, Please subscribe to the priv...@myfaces.apache.org list and update your status on the site: http://svn.apache.org/repos/asf/myfaces/myfaces-master-pom/trunk/pom.xml Thanks. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
MyFaces PMC += Jakob Korherr
Dear MyFaces community, please welcome our new MyFaces PMC member Jakob Korherr. Jakob is working on several things at Apache MyFaces. Therefore last week there was a vote to invite him to the MyFaces Project Management Committee (PMC) and fortunately he did accept. Jakob, Please subscribe to the priv...@myfaces.apache.org list and update your status on the site: http://svn.apache.org/repos/asf/myfaces/myfaces-master-pom/trunk/pom.xml Thanks. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
MyFaces PMC += Blake Sullivan
Dear MyFaces community, please welcome our new MyFaces PMC member Blake Sullivan. Blake is mostly working on Apache MyFaces Trinidad. Therefore last week there was a vote to invite him to the MyFaces Project Management Committee (PMC) and fortunately he did accept. Blake, Please subscribe to the priv...@myfaces.apache.org list and update your status on the site: http://svn.apache.org/repos/asf/myfaces/myfaces-master-pom/trunk/pom.xml Thanks. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [RESULTS] Release MyFaces Portlet Bridge 1.0.0
Hi, did you sent out an announcement for this release, or did I just missed it ? Thanks! Matthias On Wed, Jun 30, 2010 at 10:27 AM, Michael Freedman michael.freed...@oracle.com wrote: The vote for the release of Portlet Bridge 1.0.0 has passed. [1] +1: Grant Smith, Werner Punz, Leonardo Uribe, Mike Freedman, Scott O'Bryan +0: none -1: none Thanks to everyone who voted. Michael Freedman [1] http://www.mail-archive.com/dev@myfaces.apache.org/msg46810.html -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [RESULTS] Release MyFaces Portlet Bridge 1.0.0
Great! Thanks! Matthias On Tue, Jul 6, 2010 at 9:57 AM, Michael Freedman michael.freed...@oracle.com wrote: The announcement will go out as soon as its posted which if things go well will be sometime today. -Mike- On 7/6/2010 8:53 AM, Matthias Wessendorf wrote: Hi, did you sent out an announcement for this release, or did I just missed it ? Thanks! Matthias On Wed, Jun 30, 2010 at 10:27 AM, Michael Freedman michael.freed...@oracle.com wrote: The vote for the release of Portlet Bridge 1.0.0 has passed. [1] +1: Grant Smith, Werner Punz, Leonardo Uribe, Mike Freedman, Scott O'Bryan +0: none -1: none Thanks to everyone who voted. Michael Freedman [1] http://www.mail-archive.com/dev@myfaces.apache.org/msg46810.html -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] release for myfaces core 2.0.1
+1 On Tue, Jul 6, 2010 at 10:37 AM, Mark Struberg strub...@yahoo.de wrote: Hi! 1.) My colleague Bütti fixed a bug today (committed it for him) and I'd like to see this tested by a few others before we go on with the release. 2.) I also like to add ASL headers to all our poms, so our board is happy ;) Hope to get this done in the next 2 days. 3.) What about apache-parent-7 and switching over our release process? I successfully did this for OWB build-tools and currently running the OWB-1.0.0-alpha-1 release, so I can volunteer/guide with the release. LieGrue, strub --- On Tue, 7/6/10, Werner Punz werner.p...@gmail.com wrote: From: Werner Punz werner.p...@gmail.com Subject: Re: [VOTE] release for myfaces core 2.0.1 To: dev@myfaces.apache.org Date: Tuesday, July 6, 2010, 4:07 PM Jepp there were a handful of showstoppers, most have been fixed (but not all) I am glad 2.0.1 did not make it out of the door, this gave us additional time to fix the bugs which have crawled up lately. Werner Am 06.07.10 00:48, schrieb Leonardo Uribe: Hi Yes, the vote has been stopped. In the last weeks we have found some issues, so it is necessary to fix them before propose another release. regards, Leonardo Uribe 2010/7/5 Matthias Wessendorf mat...@apache.org mailto:mat...@apache.org Hi, I was out for a bit, and was wondering if this vote has now been officially stopped ? Thanks! Matthias On Wed, Jun 16, 2010 at 12:00 PM, Leonardo Uribe lu4...@gmail.com mailto:lu4...@gmail.com wrote: Hi That's cool! Thanks!. After release myfaces master pom v 8 I'll propose a release of 2.0.1 again. regards, Leonardo 2010/6/16 Michael Concini mconc...@gmail.com mailto:mconc...@gmail.com Leonardo, I just committed the proper fix for MYFACES-2754 now so as far as 2754 and 2755 we should be good to go. -Mike On 6/16/2010 1:52 PM, Leonardo Uribe wrote: Hi Bernd Ok, thanks. Unfortunately I have to restart all release steps, because there was changes applied on trunk that should be applied, but I'm not have a separate patch to apply it (MYFACES-2755, MYFACES-2754 is in progress, TOMAHAWK). We still have an unresolved problem with myfaces master pom v7 (checkstyle version is snapshot). Since myfaces core 2.0.x depends on this pom and we don't have response from Matthias fix this issue, At this point I have to release myfaces master pom first. regards, Leonardo Uribe 2010/6/16 Bernd Bohmann bernd.bohm...@googlemail.com mailto:bernd.bohm...@googlemail.com Hi Leonardo, thanks a lot. Now it is ok for me. I added some missing licenses on the 2.0.1 branch. Regards Bernd On Tue, Jun 15, 2010 at 11:14 PM, Leonardo Uribe lu4...@gmail.com mailto:lu4...@gmail.com wrote: Hi Bernd I added in api: META-INF/licenses/dojo-LICENSE.TXT META-INF/licenses/j4fry-LICENSE.TXT META-INF/licenses/facelets-LICENSE.TXT in impl META-INF/licenses/glassfish-LICENSE.TXT META-INF/licenses/facelets-LICENSE.TXT because the schemas with CDDL license are on impl jar. The update to NOTICE.txt message was committed too. Anyway to prevent misunderstandings, I'll wait your response about it. regards, Leonardo Uribe 2010/6/15 Bernd Bohmann bernd.bohm...@atanion.com mailto:bernd.bohm...@atanion.com Hello Leonardo, looks ok for me. Can you also add in api META-INF/licenses/dojo-LICENSE.TXT META-INF/licenses/j4fry-LICENSE.TXT META-INF/licenses/glassfish-LICENSE.TXT META-INF/licenses/facelets-LICENSE.TXT and in impl META-INF/licenses/facelets-LICENSE.TXT an example would be http://svn.apache.org/repos/asf/myfaces/tomahawk/trunk/core/src/main/resources/META-INF/licenses/ I have no time to perform the required changes unit tomorrow afternoon. Regards Bernd On Tue, Jun 15, 2010 at 8:11 PM, Leonardo Uribe lu4...@gmail.com mailto:lu4...@gmail.com wrote: Hi I think the NOTICE.txt file on impl module could be like this: This product includes software developed
MyFaces PMC += Max Starets
Dear MyFaces community, please welcome our new MyFaces PMC member Max Starets. Max is mostly working on Apache MyFaces Trinidad. Therefore last week there was a vote to invite him to the MyFaces Project Management Committee (PMC) and fortunately he did accept. Max, Please subscribe to the priv...@myfaces.apache.org list and update your status on the site: http://svn.apache.org/repos/asf/myfaces/myfaces-master-pom/trunk/pom.xml Thanks. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
MyFaces PMC += Jan-Kees van Andel
Dear MyFaces community, please welcome our new MyFaces PMC member Jan-Kees van Andel. Jan-Kees is working on several things at Apache MyFaces. Therefore last week there was a vote to invite him to the MyFaces Project Management Committee (PMC) and fortunately he did accept. Jan-Kees, Please subscribe to the priv...@myfaces.apache.org list and update your status on the site: http://svn.apache.org/repos/asf/myfaces/myfaces-master-pom/trunk/pom.xml Thanks. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
MyFaces PMC += Jakob Korherr
Dear MyFaces community, please welcome our new MyFaces PMC member Jakob Korherr. Jakob is working on several things at Apache MyFaces. Therefore last week there was a vote to invite him to the MyFaces Project Management Committee (PMC) and fortunately he did accept. Jakob, Please subscribe to the priv...@myfaces.apache.org list and update your status on the site: http://svn.apache.org/repos/asf/myfaces/myfaces-master-pom/trunk/pom.xml Thanks. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
MyFaces PMC += Blake Sullivan
Dear MyFaces community, please welcome our new MyFaces PMC member Blake Sullivan. Blake is mostly working on Apache MyFaces Trinidad. Therefore last week there was a vote to invite him to the MyFaces Project Management Committee (PMC) and fortunately he did accept. Blake, Please subscribe to the priv...@myfaces.apache.org list and update your status on the site: http://svn.apache.org/repos/asf/myfaces/myfaces-master-pom/trunk/pom.xml Thanks. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] release for myfaces core 2.0.1
-- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [PORTAL] News about the TCK
good stuff! PS: the JDO TCK is also available via Apache. -Matthias On Tue, Jun 22, 2010 at 2:43 PM, Scott O'Bryan darkar...@gmail.com wrote: Hello everyone, For those of you unfamiliar with the portlet-bridge project, it is essentially the R.I. implementation of JSR-301 and JSR-328. For over a year some core people have been working on getting the R.I. up to par. The one piece that was missing from this was the TCK. Well, Michael Freedman will be announcing the release of Portlet Bridge 1.0, which will become the R.I. for JSR-301 pending approvals. We also got the legalities of the TCK release figured out as well and I wanted to run things by the developers before putting a release of the project to a vote. Essentially, the TCK exists, en total, here at Apache and is run using a plugable maven build script instead of Sun's Portal TCK Harness like we were planning on using initially. What this means is that the TCK will be downloadable by anyone though the TCK project's svn repository right here at MyFaces. To my knowledge I think this is a first for Apache and will hopefully pave the way for continued support of the JCP from the Apache Community. I'd like to start a vote to release the official TCK for JSR-301 tomorrow but I wanted to do one final sanity check from the community to make sure this is still in line with what people want. When we talked about the TCK earlier, there were many questions as to why this TCK could not exist completely in the open source community and, in the end, that's exactly what we did. Thanks, Scott O'Bryan -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: make use of new apache.snapshots repo and apache-parent-7 features?
I'd like that! On Tue, Jun 29, 2010 at 9:22 PM, Leonardo Uribe lu4...@gmail.com wrote: Hi Sounds good. Maybe it is time move to Nexus, but for do that we need a vote. According to https://issues.apache.org/jira/browse/INFRA-1896 many apache projects has already moved. I think there will not be any objections. regards, Leonardo Uribe 2010/6/29 Mark Struberg strub...@yahoo.de Hi! There has been a lot problems with the 'old' apache snapshots repo [1] recently. All the snapshots have basically been moved to the new Nexus based snapshots repo recently due to the upgrade to apache-parent-7. The new distributionManagement section derived from this parent pom now looks like the following: distributionManagement repository idapache.releases.https/id nameApache Release Distribution Repository/name urlhttps://repository.apache.org/service/local/staging/deploy/maven2/url /repository snapshotRepository idapache.snapshots.https/id nameApache Development Snapshot Repository/name urlhttps://repository.apache.org/content/repositories/snapshots/url /snapshotRepository /distributionManagement By upgrading to apache-parent-7 and using the features provided there, we would gain significant benefits: *) Apache wide homogenic release tasks (at least for all projects using maven) *) _real_ source distribution packages and signing (ASF projects must be rebuildable from the source packages) *) Using Nexus for staging makes the release process a lot easier *) move to the new official apache.snapshots repository. The old one really makes a lot troubles under the hood... WDYT? LieGrue, strub [1] scpexe://people.apache.org/www/people.apache.org/builds/myfaces/m2-staging-repository -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [trinidad] new public context param org.apache.myfaces.trinidad.COMPRESS_VIEW_STATE
+1 sounds good On Fri, Jun 11, 2010 at 3:18 PM, Gabrielle Crawford gabrielle.crawf...@oracle.com wrote: Hi, We added a context param a while back to turn on zipping the page state, the param was internal, but would like to make it public, please see: https://issues.apache.org/jira/browse/TRINIDAD-1829 The current name of the param is org.apache.myfaces.trinidadinternal.COMPRESS_VIEW_STATE The proposed name of the param is org.apache.myfaces.trinidad.COMPRESS_VIEW_STATE Any objections let me know Thanks, Gabrielle -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [TRINIDAD] Code modifications :ISSUE -1836 Define public apis for org.apache.myfaces.trinidadinternal.menu
Hi Simarpal, thanks for using Trinidad. If you want to make a change like that the process would be the following: -start a discussion on the change, here on the dev@ list and propose (and explain) the change; including asking for any concerns about the actual possible change etc. -create a jira -add a patch Ask for review of the patch, so that the committers notice you proposed a patch/change. Thanks, Matthias On Mon, Jun 21, 2010 at 1:52 AM, Simarpal Singh simar@gmail.com wrote: Hi, The following JIRA issue for the change in public APIs need approval: https://issues.apache.org/jira/browse/TRINIDAD-1836 Need for this change: As mentioned in the issue description - Some consumers use myfaces trinidad internal private APIs as there are no corresponding public APIs to use. But consumer should be using public APIs because internal APIs are subject to change. We should define public APIs that they can use for the instances where they today rely on a private APIs. This issue tracks the work to define public APIs for usages of org.apache.myfaces.trinidadinternal.menu Description Some consumers use myfaces trinidad internal private APIs as there are no corresponding public APIs to use. But consumer should be using public APIs only because internal APIs are subject to change. We should define public APIs that they can use for the instances where they today rely on a private APIs. This bug tracks the work to define public APIs for usages of org.apache.myfaces.trinidadinternal.menu Show » -- Simarpal Singh Khaira Oracle Corp. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] release for myfaces core 2.0.1
+1 On Sat, Jun 12, 2010 at 10:07 AM, Martin Marinschek mmarinsc...@apache.org wrote: +1, best regards, Martin On Sat, Jun 12, 2010 at 12:15 AM, Leonardo Uribe lu4...@gmail.com wrote: Hi Just one small note, I regenerate all artifacts to include a small fix in MYFACES-2638. It is just move one line of code, so it does not affect anything, but I did all tests again, so we can continue the vote as is. regards, Leonardo Uribe 2010/6/11 Werner Punz werner.p...@gmail.com +1 Werner Am 11.06.10 21:07, schrieb Leonardo Uribe: +1 2010/6/11 Leonardo Uribe lu4...@gmail.com mailto:lu4...@gmail.com Hi, I was running the needed tasks to get the 2.0.1 release of Apache MyFaces core out. The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.2 [1] 2. Maven artifact group org.apache.myfaces.core v2.0.1 [1] 3. Maven artifact group org.apache.myfaces.test v1.0.0-beta-4 [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.1 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] http://people.apache.org/~lu4242/myfaces201 http://people.apache.org/%7Elu4242/myfaces201 [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces201binsrc http://people.apache.org/%7Elu4242/myfaces201binsrc [4] http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12315117 http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12315117 -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [GSOC] myfaces-shared Modification
On Tue, Jun 8, 2010 at 9:17 AM, Ali Ok al...@aliok.com.tr wrote: Hi, myfaces-shared HtmlTextRendererBase : http://svn.apache.org/repos/asf/myfaces/shared/trunk/core/src/main/java/org/apache/myfaces/shared/renderkit/html/HtmlTextRendererBase.java tomahawk HtmlTextRenderer : http://svn.apache.org/repos/asf/myfaces/tomahawk/trunk/core20/src/main/java/org/apache/myfaces/renderkit/html/ext/HtmlTextRenderer.java I saw these two long before, and decided to not to follow that approach. Files are almost identical, even if one extends another. As you see, shared HtmlTextRendererBase is not much extensible, ie. not fragmented into atomic parts or smthg. I want to use that base in my project too. So I made very simple modifications on that class: divided the long renderInput method into two protected methods without changing the behavior. Is it ok to do that? sure, big methods are always a pita. I will create a JIRA ticket and post the patch. +1 -M And I just wonder why authors kept that long method and copy-pasted it on Tomahawk? Is there something I'm not aware of? Regards, -- My Blog: http://blog.aliok.com.tr Twitter: http://twitter.com/aliok_tr -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] release for myfaces core 1.1.8
+1 On Mon, Jun 7, 2010 at 7:11 AM, Leonardo Uribe lu4...@gmail.com wrote: +1 2010/6/7 Leonardo Uribe lu4...@gmail.com Hi, I was running the needed tasks to get the 1.1.8 release of Apache MyFaces core out. The artifacts passed all TCK test. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v2.0.11 [1] 2. Maven artifact group org.apache.myfaces.core v1.1.8 [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 1.1.8 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] http://people.apache.org/~lu4242/myfaces118 [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces118binsrc [4] http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12315115 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] release for myfaces core 1.2.9
+1 On Mon, Jun 7, 2010 at 7:28 AM, Leonardo Uribe lu4...@gmail.com wrote: +1 2010/6/7 Leonardo Uribe lu4...@gmail.com Hi, I was running the needed tasks to get the 1.2.9 release of Apache MyFaces core out. The artifacts passed all TCK test. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v3.0.8 [1] 2. Maven artifact group org.apache.myfaces.core v1.2.9 [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 1.2.9 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] http://people.apache.org/~lu4242/myfaces129 [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces129binsrc [4] http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12315113 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [GSOC] Testing framework for the new testing API
yep, that's right. Apache 2 license On Sat, Jun 5, 2010 at 8:06 PM, Martinconi Cosmin cosmin.martinc...@codebeat.ro wrote: Hi Leonardo, Thanks for the feedback. Yes, as far as I saw it's ASL v2 licensed, so it should be no problem regarding this. Regards, Cosmin On Sat, Jun 5, 2010 at 6:03 PM, Leonardo Uribe lu4...@gmail.com wrote: Hi What license is Arquillian? It is some kind of GPL or LGPL you should read this link: http://www.apache.org/legal/resolved.html Looking some source files of that project it seems it is Apache License v 2.0, so it is ok. I'll take a look at your proposal. regards, Leonardo Uribe 2010/6/5 Martinconi Cosmin cosmin.martinc...@codebeat.ro Hi, I've started working on my GSoC project Automated webapp tests for MyFaces core and extensions, and the first target of the project is to create an testing API that will be used for the project's testing of MyFaces core, and if required for any extensions. For this after some studying and discussions I proposed Arquillian as a framework in order to be integrated into the API. Other frameworks that I considered are HTTPUnit and Canoo WebTest. What do you think about Arquillian, any other ideas, should we reconsider another framework? The scope of the API is to be used for MyFaces core, bot also for any extension and application testing that is needed. For more reference regarding my GSoC proposal and Arquillian documentation you can check out: http://wiki.apache.org/myfaces/GSoC2010_AutomatedTests http://docs.jboss.org/arquillian/reference/latest/en-US/html_single/ Regards, Cosmin -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [GSOC] Inclusion of external code
On Fri, Jun 4, 2010 at 3:06 PM, Ali Ok al...@aliok.com.tr wrote: Hi, I want to keep definitions of pass through attrs of the components and render them. I see that current MyFaces keeps them in org.apache.myfaces.shared.renderkit.html.HTML. As project grows, content of this interface(or my own HTML5 interface) will get ugly, and I think Mojarra's approach[1][2] is better. Mojarra guys took this[1][2] stuff from probably Richfaces, and I want to use their approach in my project too. So, what is the possibility of inclusion of this code in my project? If possible, what do I need to do? It is not possible to *include* the code, since they license is bad. However you can write something similar... I will request for permission from authors for using with Apache license, but is a private email like yes, you can use it enough? If not, I'll come with new stuff, which will use this approach. [1] http://www.docjar.com/html/api/com/sun/faces/renderkit/AttributeManager.java.html [2] http://www.docjar.com/html/api/com/sun/faces/util/CollectionsUtils.java.html -- My Blog: http://blog.aliok.com.tr Twitter: http://twitter.com/aliok_tr -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] Apache Bean Validation 0.1-incubating Release Candidate #2
+1 On Sun, May 30, 2010 at 2:13 PM, Mark Struberg strub...@yahoo.de wrote: +1 md5sum bval-parent-0.1-incubating-source-release.zip.asc OK sha1sum bval-parent-0.1-incubating-source-release.zip.asc OK gpg --keyserver pgpkeys.mit.edu --recv-key gpg D018E6B1 OK gpg bval-parent-0.1-incubating-source-release.zip.asc gpg: Unterschrift vom Mi 26 Mai 2010 18:11:11 CEST mittels RSA-Schlüssel ID D018E6B1 gpg: Korrekte Unterschrift von Donald Ray Woods (Apache code signing key) dwo...@apache.org gpg: WARNUNG: Dieser Schlüssel trägt keine vertrauenswürdige Signatur! gpg: Es gibt keinen Hinweis, daß die Signatur wirklich dem vorgeblichen Besitzer gehört. Haupt-Fingerabdruck = 4982 03CD 9F85 74C5 E8E1 19D9 F8E9 B8C5 D018 E6B1 Is this your Key Donald? then OK mvn clean rat:check OK mvn clean install OK cd bval-tck mvn clean install -Ptck OK svn tag looks good too OK So far the release looks pretty well. I'll try it in my real world app tonight. LieGrue, strub --- On Wed, 5/26/10, Donald Woods dwo...@apache.org wrote: From: Donald Woods dwo...@apache.org Subject: [VOTE] Apache Bean Validation 0.1-incubating Release Candidate #2 To: bval-dev@incubator.apache.org Date: Wednesday, May 26, 2010, 4:54 PM I've created a 0.1-incubating release candidate #2, with the following artifacts up for a vote: SVN source tag (r948483): https://svn.apache.org/repos/asf/incubator/bval/tags/0.1-incubating/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachebval-020/ Source release: https://repository.apache.org/content/repositories/orgapachebval-020/org/apache/bval/bval-parent/0.1-incubating/bval-parent-0.1-incubating-source-release.zip Javadoc staging site: http://people.apache.org/~dwoods/bval/0.1-incubating/staging-site/apidocs/ PGP release keys: https://svn.apache.org/repos/asf/incubator/bval/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [GSOC-HTML5] Prototype hx:video, hx:mediaSource, hx:mediaSources
+1 on the facet
-Matthias
PS: can you add this to the wiki as well ? ;-)
On Tue, Jun 1, 2010 at 9:11 PM, Ali Ok al...@aliok.com.tr wrote:
Hi again,
I couldn't settle the fallback stuff, so I want to discuss it again.
I noticed that a fallback facet may be better.
If HTML5 video[1] is not supported on a browser, it will ignore this element
and render its children:
video
pYour browser does not support Html5 video! This text is ignored on
Html5 video enabled browsers and shown on not supported browsers./p
/video
Respectively, Html5 video enabled browsers will ignore the children of
video element (except source[2]).
And this look like a good use-case of facets to me.
If we limit fallback with two attributes, we will definitely restrict the
users in coming up with their own solutions. With
actionOnNoHTML5VideoSupport and loadAlternatePlayerAction properties,
we're forcing user to write Javascript for playing the alternate video
player.
Let's say, we wrote some javascript function to activate alternate video
player: activateFlashPlayer()
Using attributes, our JSF XHTML will be something like:
script
function activateFlashPlayer(){
// run flash video player (player.swf is down below)
}
/script
...
hx:video loadAlternatePlayerAction=activateFlashPlayer()
...
embed player.swf ./embed
and, which may output an Html page like this:
script
function activateFlashPlayer(){
// run flash video player (player.swf below)
}
/script
...
video
script
activateFlashPlayer();
/script
/video
...
embed player.swf ./embed
On the other hand, using a facet, we'll have a JSF xhtml page like:
hx:video
f:facet name=falback
embed player.swf ./embed
/f:facet
/hx:video
which can output:
video
embed player.swf ./embed
/video
hx:video
= fallBack: does it need to be a facet ?
A late answer, but that's why I think it needs to be a facet :)
I don't like them much (find them not IDE-friendly), but what is the
disadvantage of facet here? Why do you avoid using that?
[1] http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#video
[2] http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#the-source-element
Thanks,
Ali
On Wed, May 26, 2010 at 3:42 PM, Matthias Wessendorf mat...@apache.org
wrote:
On Wed, May 26, 2010 at 2:38 PM, Ali Ok al...@aliok.com.tr wrote:
Hi Matthias,
I couldn't quite understand what you've meant.
Do you mean, (ignore the bad naming)
* having property named something like actionOnNoHTML5VideoSupport :
useFallBack | alert
* and having another property named something like
which can have the JS activation code for some
flash video player?
that's right
Or do you mean automatic fallback to flash video player?
nope :-)
I've done some
research about this before and I couldn't found any ASL or compatible
licensed flash video player to distrubute with the project (I haven't
done
too much research since this seems not practical to me). Assuming there
is
one ASL-compatible flash video player somewhere, is it practical?
Regards,
Ali
On Wed, May 26, 2010 at 3:10 PM, Matthias Wessendorf mat...@apache.org
wrote:
Hi Ali,
looks good so far.
One quick comment:
-hx:video
= fallBack: does it need to be a facet ?
What about alternatePlayer and warning (or alert) ?
-Matthias
On Wed, May 19, 2010 at 10:30 PM, Ali Ok al...@aliok.com.tr wrote:
Hi all,
I've prepared some component prototypes, and your feedback is
appreciated.
There are 20+ components and I want to send them to discuss here, one
by
one; to have a 'cleaner' separation of the discussion.
Also, IMHO, it is better to post prototypes inline.
===
==hx:video
===
REFS:
[0] http://www.whatwg.org/specs/web-apps/current-work/#video
[1] https://developer.mozilla.org/En/HTML/Element/Video
EXTENDS:
May extend a abstract component with hx:audio.
specific ATTRIBUTES:
preload can be:
none: do not preload the media from the server
metadata: fetch metadata (length, quality, etc.)
(default)
auto: load the data from the server, even if user doesnt
play it
showControls:
true: browser's media controls are shown (default)
false: controls are not shown unless page author provides
one
explicitly
loop:
true or false (default)
poster:
image to show when not playing or seeking
width:
width of the video
height:
height of the video
FACETS:
fallBack:
content to display when HTML5 video is not supported.
possible
Re: onclick,onmouseover etc. pass thru properties on h:outputText: MyFaces vs. Mojarra
On Wed, Jun 2, 2010 at 1:18 AM, Ali Ok al...@aliok.com.tr wrote:
Hi,
I see onclick, onmouseover, etc. attributes of h:outputText are passed
thru and rendered.
For:
h:outputText id=... value=test onclick=alert('click'); .../
I got this with MyFaces 2:
span id=... onclick=alert('click'); test/span
However, Mojarra ignores 'onclick':
span id=... test/span
HtmlTextRenderer[0] of MyFaces, which extends HtmlTextRendererBase,
renders[1] pass thru attributes of HTML.COMMON_PASSTROUGH_ATTRIBUTES[2];
while Mojarra ignores onclick on h:outputText.
Is it OK to pass thru some attributes that are not defined in the spec?
since h:outputText is very simple (one reason why it is not a
ClientBehaviorHolder), it's correct
to ignore those attributes... I am actually surprised that something
like this is not triggered by the TCK
On the other hand, it does not cause big issues, other than blowing up
the markup, which is expected
if you are specifying things like the above attrs.
I couldn't find anything about onclick, onmouseover, etc. of h:outputText
in
that's right, not there. It's a (very) simple component.
* JSF spec
* JSF Spec Facelet Taglib doc
: https://javaserverfaces.dev.java.net/nonav/docs/2.0/vdldocs/facelets/h/outputText.html
* JSF Spec RenderKit
doc: https://javaserverfaces.dev.java.net/nonav/docs/2.0/renderkitdocs/HTML_BASIC/javax.faces.Outputjavax.faces.Text.html
* JSF Spec
JavaDoc: http://java.sun.com/javaee/javaserverfaces/2.0/docs/api/javax/faces/component/html/HtmlOutputText.html
[0] http://svn.apache.org/viewvc/myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/renderkit/html/HtmlTextRenderer.java?view=markup
[1] http://svn.apache.org/viewvc/myfaces/shared/trunk/core/src/main/java/org/apache/myfaces/shared/renderkit/html/HtmlTextRendererBase.java?view=markup line
127
[2] http://svn.apache.org/viewvc/myfaces/shared/trunk/core/src/main/java/org/apache/myfaces/shared/renderkit/html/HTML.java?view=markup line
154
BTW, as you can see this is not something special to h:outputText. Most
components have this issue.
Regards,
Ali
--
My Blog: http://blog.aliok.com.tr
Twitter: http://twitter.com/aliok_tr
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Re: [GSOC] HTML5 Prototypes hx:inputText and hx:datalist
I think we could come up, later... with some convenience tags, like
hx:inputSearch / which has the most reasonable attrs.
Regarding the pattern attr, can't we drive something like:
pattern=[0-9][A-Z]{3} via the regEx validatior ?
-Matthias
On Tue, Jun 1, 2010 at 1:04 PM, Ali Ok al...@aliok.com.tr wrote:
Hi,
These were first prototypes I sent to Matthias, and I think didn't send it
to @dev.
For future reference: Wiki for hx:inputText and hx:datalist is
here: https://cwiki.apache.org/confluence/display/MYFACES/GSoC+Html5+Prototypes+inputText+and+datalist
Regards,
Ali
--
My Blog: http://blog.aliok.com.tr
Twitter: http://twitter.com/aliok_tr
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Re: onclick,onmouseover etc. pass thru properties on h:outputText: MyFaces vs. Mojarra
On Wed, Jun 2, 2010 at 9:57 AM, Ali Ok al...@aliok.com.tr wrote:
Hi,
that's right, not there. It's a (very) simple component.
Some of the other components have this situation too, like:
* h:commandButton - align
* h:inputText - checked (doesn't make sense)
* ...
On the other hand, it does not cause big issues, other than blowing up the
markup, which is expected if you are specifying things like the above attrs.
Yes, and I can say they are good and necessary :) But I wish they were
defined in some place.
well, the reason was to keep h:outputText tiny and simple.
The reason I asked this is, decision of using this approach in hx
components.
I understood that it would be better if I add solid fields for this kind
of attributes to expose at IDEs and taglib doc, since I don't have any spec
to follow :)
on tomahawk and trinidad we have those extra attributes, which is totally fine
to have that on your hx:... as well
Thanks,
On Wed, Jun 2, 2010 at 9:51 AM, Matthias Wessendorf mat...@apache.org
wrote:
On Wed, Jun 2, 2010 at 1:18 AM, Ali Ok al...@aliok.com.tr wrote:
Hi,
I see onclick, onmouseover, etc. attributes of h:outputText are passed
thru and rendered.
For:
h:outputText id=... value=test onclick=alert('click'); .../
I got this with MyFaces 2:
span id=... onclick=alert('click'); test/span
However, Mojarra ignores 'onclick':
span id=... test/span
HtmlTextRenderer[0] of MyFaces, which extends HtmlTextRendererBase,
renders[1] pass thru attributes of HTML.COMMON_PASSTROUGH_ATTRIBUTES[2];
while Mojarra ignores onclick on h:outputText.
Is it OK to pass thru some attributes that are not defined in the spec?
since h:outputText is very simple (one reason why it is not a
ClientBehaviorHolder), it's correct
to ignore those attributes... I am actually surprised that something
like this is not triggered by the TCK
On the other hand, it does not cause big issues, other than blowing up
the markup, which is expected
if you are specifying things like the above attrs.
I couldn't find anything about onclick, onmouseover, etc. of
h:outputText
in
that's right, not there. It's a (very) simple component.
* JSF spec
* JSF Spec Facelet Taglib doc
: https://javaserverfaces.dev.java.net/nonav/docs/2.0/vdldocs/facelets/h/outputText.html
* JSF Spec RenderKit
doc: https://javaserverfaces.dev.java.net/nonav/docs/2.0/renderkitdocs/HTML_BASIC/javax.faces.Outputjavax.faces.Text.html
* JSF Spec
JavaDoc: http://java.sun.com/javaee/javaserverfaces/2.0/docs/api/javax/faces/component/html/HtmlOutputText.html
[0] http://svn.apache.org/viewvc/myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/renderkit/html/HtmlTextRenderer.java?view=markup
[1] http://svn.apache.org/viewvc/myfaces/shared/trunk/core/src/main/java/org/apache/myfaces/shared/renderkit/html/HtmlTextRendererBase.java?view=markup line
127
[2] http://svn.apache.org/viewvc/myfaces/shared/trunk/core/src/main/java/org/apache/myfaces/shared/renderkit/html/HTML.java?view=markup line
154
BTW, as you can see this is not something special to h:outputText.
Most
components have this issue.
Regards,
Ali
--
My Blog: http://blog.aliok.com.tr
Twitter: http://twitter.com/aliok_tr
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
--
My Blog: http://blog.aliok.com.tr
Twitter: http://twitter.com/aliok_tr
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Re: [VOTE] Release Tobago 1.0.26
+1 On Wed, Jun 2, 2010 at 3:39 PM, Bernd Bohmann bernd.bohm...@atanion.com wrote: Here is my +1 Regards Bernd On Wed, Jun 2, 2010 at 3:16 PM, Volker Weber v.we...@inexso.de wrote: Hi, +1 , already testet and running in production here :-) Regards, Volker 2010/5/31 Bernd Bohmann bernd.bohm...@atanion.com: Hello, I would like to release Tobago 1.0.26. For a detail list please consult the release notes: http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273styleName=Htmlversion=12314961 The version is available at the staging location and the revision number of the release is 949580 and tagged as tobago-1.0.26. Staging distribution: http://people.apache.org/~bommel/repo Staging repository: http://people.apache.org/~bommel/repo The Vote is open for 72h. [ ] +1 [ ] +0 [ ] -1 -- inexso - information exchange solutions GmbH Bismarckstraße 13 | 26122 Oldenburg Tel.: +49 441 4082 356 | FAX: +49 441 4082 355 | www.inexso.de -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [GSOC] HTML5 Prototype hx:inputDateTime and fx:validateDateRange
for validateDateRange, I'd prefer validateDateTimeRange as its name. I'd also take a look here: http://myfaces.apache.org/trinidad/trinidad-api/tagdoc/tr_validateDateTimeRange.html @copy: note that we have a commons module, which could be the base for your converter/validator extensions. On Tue, Jun 1, 2010 at 9:35 AM, Ali Ok al...@aliok.com.tr wrote: Hi, Here is the prototypes of these components: https://cwiki.apache.org/confluence/display/MYFACES/GSoC+Html5+Prototype+inputDateTime+and+validateDateRange -- My Blog: http://blog.aliok.com.tr Twitter: http://twitter.com/aliok_tr -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [GSOC] HTML5 Prototype hx:inputFileUpload
for the server-side implementation of this, I am fine in just using Servlet 3.0's upload API. -Matthias On Mon, May 31, 2010 at 3:00 PM, Ali Ok al...@aliok.com.tr wrote: Hi all, Here is the wiki https://cwiki.apache.org/confluence/display/MYFACES/GSoC+HTML5+inputFileUpload+Prototype about hx:inputFileUpload. Regards, Ali -- My Blog: http://blog.aliok.com.tr Twitter: http://twitter.com/aliok_tr -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [GSOC] HTML5 Prototype hx:inputNumber
On Fri, May 28, 2010 at 9:49 AM, Ali Ok al...@aliok.com.tr wrote:
would be cool if there would be some client-side validation hook,
instead of just server-side
?
HTML5 input element's min and max attributes are there for it. Form won't
be submitted and a warning will be displayed if value is not between
min-max. This validation is provided by the browser (just Opera yet).
I was wondering if the default looks OK (at least for the beginning), I guess
we are fine with that. thx
A validation with same min-max will be done on server side too.
yes, with a JSF validatior
However, the logic should be driven by a JSF validator.
Ok, code below seems clear:
!-- - - - - - - - - -usage- - - - - - - - - - - - - - - - - - - - -- --
hx:inputNumberSlider value=#{someBean.someNumberField}
fx:validateNumberRange maximum=1000 minimum=100 / !-- New validator
--
/hx:inputNumberSlider
why do we need a new validatior ? why would validateDoubleRange not work ?
!-- expected HTML5 code --
input type=range value= min=100 step=9 max=1000 /
the renderer can check if the validateDoubleRange is present and
simple render out those attrs.
Interesting: since (I think) min/max is poor, I am wondering why they
weren't naming it minimum/maximum :-)
This can do both server-side validation and client-side validation of
input(basically rendering min and max attributes). max and min
attributes can be set by validator on its facelet handler, thus no need to
iterate on children on parent.
But, what about this:
!-- - - - - - - - - -usage- - - - - - - - - - - - - - - - - - - - -- --
hx:inputNumberSlider value=#{someBean.someNumberField}
f:validateLongRange maximum=1000 minimum=100 / !-- JSF Core
validator--
/hx:inputNumberSlider
!-- expected HTML5 code --
input type=range value= min=100 step=9 max=1000 /
If we support this, in order to render min and max attributes of input
element, hx:inputNumberSlider will get those values from its attached
validators.
I would not like parent iterating on validators and looking for certain
types of validators.
Another way to achieve this?
nope, go by the renderer of the input...
-Matthias
Thanks,
Ali
On Thu, May 27, 2010 at 4:53 PM, Matthias Wessendorf mat...@apache.org
wrote:
On Thu, May 27, 2010 at 2:07 PM, Ali Ok al...@aliok.com.tr wrote:
Hi,
why not breaking this into two components ?
hx:inputNumberSpinner and hx:inputNumberSlider
Ok. My initial prototypes were separate already on my workspace.
the min/max should be driven by a range validator component
Then I am removing min and max properties from the component(s).
it is fine to have maximum/minimum on the component itself. However,
the logic should be driven by a JSF validator.
would be cool if there would be some client-side validation hook,
instead of just
server-side
Or, another alternative, should we keep them and allow overriding by a
range
validator? At the initial prototype, an implicit validator will be
attached
with the values of min and max. So, may be we can keep them and if an
explicit validator is not set, implicit one can be attached.
Just an alternative idea, IMHO, removing min and max is better :)
Thanks,
Ali
On Thu, May 27, 2010 at 2:49 PM, Bruno Aranda brunoara...@gmail.com
wrote:
+1 I agree with Matthias.
Thanks!
Bruno
On 27 May 2010 12:44, Matthias Wessendorf mat...@apache.org wrote:
Hi,
why not breaking this into two components ?
hx:inputNumberSpinner and hx:inputNumberSlider
the min/max should be driven by a range validator component
-Matthias
On Thu, May 27, 2010 at 1:11 PM, Ali Ok al...@aliok.com.tr wrote:
Hi,
This is hx:inputNumber, which can render a spinner or a slider.
It may seem so straight forward, but here is the prototype.
===
==hx:inputNumber==
===
REFS:
[0] http://www.whatwg.org/specs/web-apps/current-work/multipage/the-input-element.html#the-input-element
[1] http://www.whatwg.org/specs/web-apps/current-work/multipage/number-state.html#range-state
[2] http://www.whatwg.org/specs/web-apps/current-work/multipage/number-state.html#number-state
[3] http://www.whatwg.org/specs/web-apps/current-work/multipage/the-input-element.html#input-type-attr-summary
EXTENDS:
some input component
ATTRIBUTES not present in ancestor:
type(required): can be
'spinner': which renders a spinner text box
'slider': which renders a slider
suggestions: same suggestion mechanism with hx:inputText
min: minimum value that can be selected. default to 0.
max: maximum that can be selected. default to 100.
step: gap between each segment. if both 'step' and 'segmentCount' is
not
defined, 'step' is default to (max-min)/(100).
segmentCount: used to calculate step with min and max. step ~=
(max-min)/segmentCount. default to 100, if step
Re: [GSOC] HTML5 Prototypes DnD components
div id=dropZone2
ondragenter=dragEnter(event,{'copy','move'}), null,
{'text/x-myfaces-html5-dnd-source'}
ondragover=makeRedBorder(); dragOver(event)
ondragleave=clearRedBorder();
ondrop=makeGreenBorder();drop(event)
!-- RENDERED CONTENT --
/div
!-- - - - - - - - - -usage: fx:dropZone that accepts some specified
mime typed content - - - - - - - - - - - - - - - - - - - - - - --
hx:panel id=dropZone3
!-- SOME CONTENT --
fx:dropZone actions=copy
dropListener=#{someBean.dropListener} acceptMimeTypes=text/plain, URL /
/hx:panel
div id=dropZone3
ondragenter=dragEnter(event,{'copy','move'}, null,
{'text/plain', 'URL'})
ondragover=dragOver(event)
ondrop=drop(event)
!-- RENDERED CONTENT --
/div
script!--
var paramMimeType = 'text/x-myfaces-html5-dnd-param';
var myFacesComponentSourceMimeType = 'text/x-myfaces-html5-dnd-source';
var dropZoneMimeType = 'text/x-myfaces-html5-drop-zone-type';
var myFacesComponentSourceConstant = 'org.apache.myfaces';
/*
* This function is only used by MyFaces generated draggable elements, the
ones that have fx:dragSource behavior.
*/
function dragStart(event, effectAllowed, paramToSendToServer, dropZoneTypes)
{
//set allowed effect
event.dataTransfer.effectAllowed = effectAllowed; //only allow some
specific event
//with this, drop zone will understand that source of this dnd
operation is some MyFaces component
event.dataTransfer.setData(myFacesComponentSourceMimeType,
myFacesComponentSourceConstant);
//this will be set if we want to send an optional parameter to the
server-side drop listener
if(paramToSendToServer)
event.dataTransfer.setData(paramMimeType,
valueToSendToServer);
//this will be set if we want to make the drop only into specific
dropzones with specific types
if(dropZoneType)
event.dataTransfer.setData(dropZoneMimeType, dropZoneTypes);
//in fact, dropZoneTypes is an array. need to iterate
return true;
}
function dragEnter(event, allowedEffects, dropZoneTypes, acceptedMimeTypes)
{
//check allowed mime types first
var found = false;
var foundTypes = acceptedMimeTypes.filter(function (mimeType)
event.dataTransfer.types.contains(mimeType));
//if even one of the event mime types are not allowed, stop DnD
if(foundTypes.length == 0)
return true; //don't cancel the event, thus stop DnD
//check allowed effect
//changeIt: allowedEffects is an array in fact, so need to iterate
if (event.dataTransfer.effectAllowed != allowedEffect)
return true; //don't cancel the event, thus stop DnD
//check drop zone type
//changeIt: in fact these are arrays too. need to iterate or use
contains() function
if (event.dataTransfer.getData(dropZoneMimeType) != dropZoneTypes)
return true; //don't cancel the event, thus stop DnD
//cancel the event. this is necessary for DnD execution
if (event.preventDefault)
event.preventDefault();
return false;
}
function dragOver(event){
//don't check source, allowedEffect and dropZoneType, since they are
checked at dragEnter function
//show same user hint effect specified by drag source
event.dataTransfer.dropEffect = event.dataTransfer.effectAllowed;
//cancel the event, so effect on screen is updated
if (event.preventDefault)
event.preventDefault();
return false;
}
function drop(event, jsf_ajax_request_necessary_stuff){
//cancel the event. this is necessary for DnD execution
if (event.preventDefault)
event.preventDefault();
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Re: [GSOC] HTML5 Prototypes DnD components
+1 sent from my Android phone Am 28.05.2010 21:20 schrieb Jakob Korherr jakob.korh...@gmail.com: Yes, right. I am really looking forward to all this stuff. Sounds just great :) 2010/5/28 Ali Ok al...@aliok.com.tr Ok, I will put these on a cwiki page. But please not that these are not publish-quality stuff... -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: htt...
Re: [GSOC] HTML5 Prototype hx:inputNumber
Hi,
why not breaking this into two components ?
hx:inputNumberSpinner and hx:inputNumberSlider
the min/max should be driven by a range validator component
-Matthias
On Thu, May 27, 2010 at 1:11 PM, Ali Ok al...@aliok.com.tr wrote:
Hi,
This is hx:inputNumber, which can render a spinner or a slider.
It may seem so straight forward, but here is the prototype.
===
==hx:inputNumber==
===
REFS:
[0] http://www.whatwg.org/specs/web-apps/current-work/multipage/the-input-element.html#the-input-element
[1] http://www.whatwg.org/specs/web-apps/current-work/multipage/number-state.html#range-state
[2] http://www.whatwg.org/specs/web-apps/current-work/multipage/number-state.html#number-state
[3] http://www.whatwg.org/specs/web-apps/current-work/multipage/the-input-element.html#input-type-attr-summary
EXTENDS:
some input component
ATTRIBUTES not present in ancestor:
type(required): can be
'spinner': which renders a spinner text box
'slider': which renders a slider
suggestions: same suggestion mechanism with hx:inputText
min: minimum value that can be selected. default to 0.
max: maximum that can be selected. default to 100.
step: gap between each segment. if both 'step' and 'segmentCount' is not
defined, 'step' is default to (max-min)/(100).
segmentCount: used to calculate step with min and max. step ~=
(max-min)/segmentCount. default to 100, if step is not defined too.
either 'step' or 'segmentCount' should be defined, not both!
autocomplete: to override owner form's autocomplete attribute for its
children. can be 'on' 'off' 'default'(default)
datalist: id of hx:datalist for suggestions mechanism. by this way,
suggestion options(datalist) can be shared across several input elements.
NOTES:
Cannot extend hx:inputText, since this doesn't have size attribute! Will
extend an abstract middle component.
--
!-- - - - - - - - - -usage- - - - - - - - - - - - - - - - - - - - -- --
hx:inputNumber type=spinner value=#{someBean.someNumberField}
min=100 max=1000/
!-- expected HTML5 code --
input type=number value= min=100 step=9 max=1000 /
!-- - - - - - - - - -usage- - - - - - - - - - - - - - - - - - - - -- --
hx:inputNumber type=slider value=#{someBean.someNumberField} min=100
max=1000 segmentCount=10/
!-- expected HTML5 code --
input type=range value= min=100 step=90 max=1000 /
Regards,
Ali
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Re: [GSOC] HTML5 Prototype hx:inputColor and hx:inputEmail
On Thu, May 27, 2010 at 1:25 PM, Ali Ok al...@aliok.com.tr wrote:
Hi,
I am posting 2 prototypes inline, since they seem easy convenience tags.
===
==hx:inputColor=
===
REFS:
[0]
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-input-element.html#the-input-element
[1]
http://www.whatwg.org/specs/web-apps/current-work/multipage/number-state.html#color-state
[2]
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-input-element.html#input-type-attr-summary
EXTENDS:
h:inputText
ATTRIBUTES not present in ancestor:
suggestions: same suggestion mechanism with hx:inputText
autocomplete: to override owner form's autocomplete attribute for its
children. can be 'on' 'off' 'default'(default)
NOTES:
Cannot extend hx:inputText, since this doesn't have
size,pattern,placeholder, etc. attributes! Will create an abstract middle
component.
No browser support for this yet!
For suggestions and more, see hx:inputText usage.
!-- - - - - - - - - -usage- - - - - - - - - - - - - - - - - - - - -- --
hx:inputColor value=#{someBean.someField} /
!-- expected HTML5 code --
input type=color value= /
!-- - - - - - - - - -usage- - - - - - - - - - - - - - - - - - - - -- --
hx:inputRange value=#{someBean.someField} suggestions=#00,
#FF/
!-- expected HTML5 code --
input list=idOfDataList type=color /
datalist id=idOfDataList
option value=#00 label=#00 /
option value=#FF label=#FF /
/datalist
Not sure why some generic word like range make the compont turn into
a color range selector; I guess that's not too clear :-)
range can be different, see adf faces' sliders (number and range)
===
==hx:inputEmail==
===
REFS:
[0]
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-input-element.html#the-input-element
[1]
http://www.whatwg.org/specs/web-apps/current-work/multipage/states-of-the-type-attribute.html#e-mail-state
[2]
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-input-element.html#input-type-attr-summary
EXTENDS:
hx:inputText
ATTRIBUTES not present in ancestor:
multiple: email input type supports 'multiple' attribute. can be used with
datalist(suggestions). default to 'false'.
see:
http://www.whatwg.org/specs/web-apps/current-work/multipage/common-input-element-attributes.html#attr-input-multiple
NOTES:
About 'pattern': browsers should make the email validation. this attribute
can be used for extra validation.
For suggestions and more, see hx:inputText usage.
!-- - - - - - - - - -usage- - - - - - - - - - - - - - - - - - - - -- --
hx:inputEmail value=#{someBean.email} suggestions=em...@example.org,
anotherem...@example.org/
!-- expected HTML5 code--
input type=email value= list=idOfDataList/
datalist id=idOfDataList
option value=em...@example.org label=em...@example.org /
option value=anotherem...@example.org label=anotherem...@example.org /
/datalist
!-- - - - - - - - - -usage- - - - - - - - - - - - - - - - - - - - -- --
hx:inputEmail value=#{someBean.email}
suggestions=#{someBean.emailSuggestions} multiple=true/
!-- expected HTML5 code--
input type=email value= list=idOfDataList/
datalist id=idOfDataList
option value=em...@example.org label=Email 1 /
option value=anotherem...@example.org label=Email 2 /
option value=theotherem...@example.org label=Email 3 /
/datalist
looks good, so far.
Q: the validation of a correct email pattern is driven by the
user-agent, right?
-M
Thanks for feedback,
Ali
--
My Blog: http://blog.aliok.com.tr
Twitter: http://twitter.com/aliok_tr
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Re: [GSOC] HTML5 Prototype hx:inputNumber
On Thu, May 27, 2010 at 2:07 PM, Ali Ok al...@aliok.com.tr wrote:
Hi,
why not breaking this into two components ?
hx:inputNumberSpinner and hx:inputNumberSlider
Ok. My initial prototypes were separate already on my workspace.
the min/max should be driven by a range validator component
Then I am removing min and max properties from the component(s).
it is fine to have maximum/minimum on the component itself. However,
the logic should be driven by a JSF validator.
would be cool if there would be some client-side validation hook,
instead of just
server-side
Or, another alternative, should we keep them and allow overriding by a range
validator? At the initial prototype, an implicit validator will be attached
with the values of min and max. So, may be we can keep them and if an
explicit validator is not set, implicit one can be attached.
Just an alternative idea, IMHO, removing min and max is better :)
Thanks,
Ali
On Thu, May 27, 2010 at 2:49 PM, Bruno Aranda brunoara...@gmail.com wrote:
+1 I agree with Matthias.
Thanks!
Bruno
On 27 May 2010 12:44, Matthias Wessendorf mat...@apache.org wrote:
Hi,
why not breaking this into two components ?
hx:inputNumberSpinner and hx:inputNumberSlider
the min/max should be driven by a range validator component
-Matthias
On Thu, May 27, 2010 at 1:11 PM, Ali Ok al...@aliok.com.tr wrote:
Hi,
This is hx:inputNumber, which can render a spinner or a slider.
It may seem so straight forward, but here is the prototype.
===
==hx:inputNumber==
===
REFS:
[0] http://www.whatwg.org/specs/web-apps/current-work/multipage/the-input-element.html#the-input-element
[1] http://www.whatwg.org/specs/web-apps/current-work/multipage/number-state.html#range-state
[2] http://www.whatwg.org/specs/web-apps/current-work/multipage/number-state.html#number-state
[3] http://www.whatwg.org/specs/web-apps/current-work/multipage/the-input-element.html#input-type-attr-summary
EXTENDS:
some input component
ATTRIBUTES not present in ancestor:
type(required): can be
'spinner': which renders a spinner text box
'slider': which renders a slider
suggestions: same suggestion mechanism with hx:inputText
min: minimum value that can be selected. default to 0.
max: maximum that can be selected. default to 100.
step: gap between each segment. if both 'step' and 'segmentCount' is
not
defined, 'step' is default to (max-min)/(100).
segmentCount: used to calculate step with min and max. step ~=
(max-min)/segmentCount. default to 100, if step is not defined too.
either 'step' or 'segmentCount' should be defined, not both!
autocomplete: to override owner form's autocomplete attribute for its
children. can be 'on' 'off' 'default'(default)
datalist: id of hx:datalist for suggestions mechanism. by this way,
suggestion options(datalist) can be shared across several input
elements.
NOTES:
Cannot extend hx:inputText, since this doesn't have size attribute!
Will
extend an abstract middle component.
--
!-- - - - - - - - - -usage- - - - - - - - - - - - - - - - - - - - --
--
hx:inputNumber type=spinner value=#{someBean.someNumberField}
min=100 max=1000/
!-- expected HTML5 code --
input type=number value= min=100 step=9 max=1000 /
!-- - - - - - - - - -usage- - - - - - - - - - - - - - - - - - - - --
--
hx:inputNumber type=slider value=#{someBean.someNumberField}
min=100
max=1000 segmentCount=10/
!-- expected HTML5 code --
input type=range value= min=100 step=90 max=1000 /
Regards,
Ali
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
--
My Blog: http://blog.aliok.com.tr
Twitter: http://twitter.com/aliok_tr
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Re: [GSOC] HTML5 Prototype hx:inputColor and hx:inputEmail
ok
On Thu, May 27, 2010 at 2:13 PM, Ali Ok al...@aliok.com.tr wrote:
hx:inputRange value=#{someBean.someField} suggestions=#00,
#FF/
Copy-paste mistake, sorry :)
It should be hx:inputColor as in the first usecase:
hx:inputColor value=#{someBean.someField} /
and
hx:inputColor value=#{someBean.someField} suggestions=#00,
#FF/
Q: the validation of a correct email pattern is driven by the
user-agent, right?
Right. And an email validator will be attached on the server-side too.
On Thu, May 27, 2010 at 2:49 PM, Matthias Wessendorf mat...@apache.org
wrote:
On Thu, May 27, 2010 at 1:25 PM, Ali Ok al...@aliok.com.tr wrote:
Hi,
I am posting 2 prototypes inline, since they seem easy convenience tags.
===
==hx:inputColor=
===
REFS:
[0]
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-input-element.html#the-input-element
[1]
http://www.whatwg.org/specs/web-apps/current-work/multipage/number-state.html#color-state
[2]
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-input-element.html#input-type-attr-summary
EXTENDS:
h:inputText
ATTRIBUTES not present in ancestor:
suggestions: same suggestion mechanism with hx:inputText
autocomplete: to override owner form's autocomplete attribute for its
children. can be 'on' 'off' 'default'(default)
NOTES:
Cannot extend hx:inputText, since this doesn't have
size,pattern,placeholder, etc. attributes! Will create an abstract
middle
component.
No browser support for this yet!
For suggestions and more, see hx:inputText usage.
!-- - - - - - - - - -usage- - - - - - - - - - - - - - - - - - - - --
--
hx:inputColor value=#{someBean.someField} /
!-- expected HTML5 code --
input type=color value= /
!-- - - - - - - - - -usage- - - - - - - - - - - - - - - - - - - - --
--
hx:inputRange value=#{someBean.someField} suggestions=#00,
#FF/
!-- expected HTML5 code --
input list=idOfDataList type=color /
datalist id=idOfDataList
option value=#00 label=#00 /
option value=#FF label=#FF /
/datalist
Not sure why some generic word like range make the compont turn into
a color range selector; I guess that's not too clear :-)
range can be different, see adf faces' sliders (number and range)
===
==hx:inputEmail==
===
REFS:
[0]
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-input-element.html#the-input-element
[1]
http://www.whatwg.org/specs/web-apps/current-work/multipage/states-of-the-type-attribute.html#e-mail-state
[2]
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-input-element.html#input-type-attr-summary
EXTENDS:
hx:inputText
ATTRIBUTES not present in ancestor:
multiple: email input type supports 'multiple' attribute. can be used
with
datalist(suggestions). default to 'false'.
see:
http://www.whatwg.org/specs/web-apps/current-work/multipage/common-input-element-attributes.html#attr-input-multiple
NOTES:
About 'pattern': browsers should make the email validation. this
attribute
can be used for extra validation.
For suggestions and more, see hx:inputText usage.
!-- - - - - - - - - -usage- - - - - - - - - - - - - - - - - - - - --
--
hx:inputEmail value=#{someBean.email} suggestions=em...@example.org,
anotherem...@example.org/
!-- expected HTML5 code--
input type=email value= list=idOfDataList/
datalist id=idOfDataList
option value=em...@example.org label=em...@example.org /
option value=anotherem...@example.org
label=anotherem...@example.org /
/datalist
!-- - - - - - - - - -usage- - - - - - - - - - - - - - - - - - - - --
--
hx:inputEmail value=#{someBean.email}
suggestions=#{someBean.emailSuggestions} multiple=true/
!-- expected HTML5 code--
input type=email value= list=idOfDataList/
datalist id=idOfDataList
option value=em...@example.org label=Email 1 /
option value=anotherem...@example.org label=Email 2 /
option value=theotherem...@example.org label=Email 3 /
/datalist
looks good, so far.
Q: the validation of a correct email pattern is driven by the
user-agent, right?
-M
Thanks for feedback,
Ali
--
My Blog: http://blog.aliok.com.tr
Twitter: http://twitter.com/aliok_tr
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
--
My Blog: http://blog.aliok.com.tr
Twitter: http://twitter.com/aliok_tr
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Re: [GSOC-HTML5] Prototype hx:video, hx:mediaSource, hx:mediaSources
!-- ---usage --
hx:mediaSource src=http://someaddress/someFile.ogg;
contentType=video/ogg codecs=avc1.42E01E media=screen and
(device-width: 800px)/
!-- expected HTML5 code for usage--
source src='http://someaddress/someFile.ogg' contentType=video/ogg
codecs=avc1.42E01E media=screen and (device-width: 800px) /
!-- ---usage --
hx:mediaSource src=http://someaddress/some3DFile.ogg;
media=3d-glasses /
!-- expected HTML5 code for usage--
source src='someAddress/some3Dfile.ogg' media=3d-glasses/
===
===hx:mediaSources
===
REFS:
[0]
http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#the-source-element
[1] https://developer.mozilla.org/En/HTML/Element/Source
EXTENDS:
--
specific ATTRIBUTES:
items:
binding of a collection which has elements of types having these
methods
public String getSrc(),
public String getContentType(),
public String getMedia(),
public String getCodecs().
(ie.
Collectionorg.apache.myfaces.html5.media.MediaSourceInfo)
'src', 'contentType', 'media' and 'codecs' are explained in
mediaSource.xhtml (w/o 's' at the end)
NOTES:
see mediaSource.xhtml, audio.xhtml and video.xhtml
!-- usage --
hx:mediaSources items=#{audioBean.someAudioFileInfos}/
!-- expected HTML5 code--
source src='someAddress/somefile.ogg' type='video/ogg; codecs=flac' /
source src='http://someaddress/someFile.ogg' media=screen and
(device-width: 800px) /
source src='http://someaddress/someFile.ogg' media=3d-glasses/
Regards,
Ali
--
My Blog: http://blog.aliok.com.tr
Twitter: http://twitter.com/aliok_tr
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Re: [Trinidad][api] - Any objections / counter-proposals for (TRINIDAD-1810) Flash component needs public version of NumberConverter.is[Min/Max][Fraction/Integer]DigitsSet() apis]
+1 On Wed, May 26, 2010 at 1:54 PM, Diar Ahmed diar.ah...@oracle.com wrote: Hi Again, So what we would like to do to fix this issue is to make the following methods on NumberConverter public. - protected boolean isMaximumFractionDigitsSet() - protected boolean isMinimumFractionDigitsSet() - protected boolean isMaximumIntegerDigitsSet() - protected boolean isMinimumIntegerDigitsSet() will become - public boolean isMaximumFractionDigitsSet() - public boolean isMinimumFractionDigitsSet() - public boolean isMaximumIntegerDigitsSet() - public boolean isMinimumIntegerDigitsSet() If this sounds ok, we will go ahead and make this change. Thanks, Diar Diar Ahmed wrote: Resending with [api] to be more specific about this request. Thanks, Diar Diar Ahmed wrote: Hi Trinidad Developers, I just filed (TRINIDAD-1810) -https://issues.apache.org/jira/browse/TRINIDAD-1810Flash component needs public version of NumberConverter.is[Min/Max][Fraction/Integer]DigitsSet() apishttps://issues.apache.org/jira/browse/TRINIDAD-1810and was wondering if anybody has any objections or counter-proposals for addressing this issue. Thanks, Diar Original Message Subject: [jira] Created: (TRINIDAD-1810) Flash component needs public version of NumberConverter.is[Min/Max][Fraction/Integer]DigitsSet() apis Date: Mon, 17 May 2010 17:40:41 -0400 (EDT) From: Diar Ahmed (JIRA) dev@myfaces.apache.org dev@myfaces.apache.org To: diar.ah...@oracle.com Flash component needs public version of NumberConverter.is[Min/Max][Fraction/Integer]DigitsSet() apis - Key: TRINIDAD-1810 URL: https://issues.apache.org/jira/browse/TRINIDAD-1810 Project: MyFaces Trinidad Issue Type: Improvement Components: Components Affects Versions: 1.2.14-core Environment: All Reporter: Diar Ahmed Priority: Blocker ADF Faces has a number of components ( Graph, Gauge, ... ) that accept NumberConverters in order to support number formatting. These converters can be used on the middle tier to support PNG generation, but for Flash based rendering, the NumberConverter's properties are read in the middle tier and pass down to an existing ActionScript number formatting engine. This JIRA is to support the ability to determine whether the the following properties are set on the NumberConverter and should be transferred to Actionscript: MinimumFractionDigits MaximumFractionDigits MinimumIntegerDigits MaximumIntegerDigits since by default, if these properties are not set, they always return 0, which is not the correct min/max fraction/integer digits used by the NumberConverter. Currently, the NumberConverter has protected methods that provide access to whether these properties are set: - protected boolean isMaximumFractionDigitsSet() - protected boolean isMinimumFractionDigitsSet() - protected boolean isMaximumIntegerDigitsSet() - protected boolean isMinimumIntegerDigitsSet() This JIRA is requesting that these APIs ( or alternate APIs ) are made public, to allow us to determine if these attributes are set and should be used when we perform ActionScript based formatting. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [GSOC-HTML5] Prototype hx:video, hx:mediaSource, hx:mediaSources
On Wed, May 26, 2010 at 2:38 PM, Ali Ok al...@aliok.com.tr wrote:
Hi Matthias,
I couldn't quite understand what you've meant.
Do you mean, (ignore the bad naming)
* having property named something like actionOnNoHTML5VideoSupport :
useFallBack | alert
* and having another property named something like
loadAlternatePlayerAction which can have the JS activation code for some
flash video player?
that's right
Or do you mean automatic fallback to flash video player?
nope :-)
I've done some
research about this before and I couldn't found any ASL or compatible
licensed flash video player to distrubute with the project (I haven't done
too much research since this seems not practical to me). Assuming there is
one ASL-compatible flash video player somewhere, is it practical?
Regards,
Ali
On Wed, May 26, 2010 at 3:10 PM, Matthias Wessendorf mat...@apache.org
wrote:
Hi Ali,
looks good so far.
One quick comment:
-hx:video
= fallBack: does it need to be a facet ?
What about alternatePlayer and warning (or alert) ?
-Matthias
On Wed, May 19, 2010 at 10:30 PM, Ali Ok al...@aliok.com.tr wrote:
Hi all,
I've prepared some component prototypes, and your feedback is
appreciated.
There are 20+ components and I want to send them to discuss here, one by
one; to have a 'cleaner' separation of the discussion.
Also, IMHO, it is better to post prototypes inline.
===
==hx:video
===
REFS:
[0] http://www.whatwg.org/specs/web-apps/current-work/#video
[1] https://developer.mozilla.org/En/HTML/Element/Video
EXTENDS:
May extend a abstract component with hx:audio.
specific ATTRIBUTES:
preload can be:
none: do not preload the media from the server
metadata: fetch metadata (length, quality, etc.) (default)
auto: load the data from the server, even if user doesnt
play it
showControls:
true: browser's media controls are shown (default)
false: controls are not shown unless page author provides
one
explicitly
loop:
true or false (default)
poster:
image to show when not playing or seeking
width:
width of the video
height:
height of the video
FACETS:
fallBack:
content to display when HTML5 video is not supported.
possible
actions
can be using a flash player as a fallback or displaying a
message that displays this is not supported.
NOTES:
see hx:mediaSource and hx:mediaSources
new track feature is not included, since there is no browser
support yet (impossible to test). this feature can be added
when a browser starts supporting it
!-- ---usage
--- --
hx:video value=#{videoBean.someVideoFileURL} preload=metadata
poster=somePosterImage.jpg
width=600px height=300px
autoplay=true loop=true showControls=true
f:facet name=fallBack
embed player.swf ./embed
!-- SOME FALLBACK MECHANISM TO PLAY THE FILE (FLASH may be).
or
alerting the user about HTML5 video support. --
/f:facet
/hx:video
!-- expected HTML5 code --
video src=someAddress/someFile.mkv preload=metadata autoplay
loop
controls poster=somePosterImage.jpg
width=600px height=300px
embed player.swf ./embed
/video
!-- ---usage
--- --
hx:video preload=none
autoplay=false loop=false showControls=false
poster=#{videoBean.posterImage}
f:facet name=fallBack
Your browser does not support HTML5 video.
/f:facet
hx:mediaSource src=http://someaddress/someFile.ogg;
contentType=video/ogg codecs=avc1.42E01E media=screen and
(device-width: 800px)
hx:mediaSource src=http://someaddress/some3DFile.ogg;
media=3d-glasses
!-- hx:mediaSources component, not hx:mediaSource --
hx:mediaSources items=#{someBean.mediaInfoList}
/hx:video
!-- expected HTML5 code for usage --
video preload=none poster=somePosterImage.jpg controls=false
autoplay=false
Your browser does not support HTML5 video.
source src='http://someaddress/someFile.ogg' Type='video/ogg;
codecs=avc1.42E01E' media=screen and (device-width: 800px) /
source src='someAddress/some3Dfile.ogg' media=3d-glasses/
!-- elements below are generated with hx:mediaSources --
source src='video.mp4' type='video/mp4; codecs=avc1.42E01E,
mp4a.40.2' media=screen
source src='video.mp4' type='video/mp4; codecs
Re: Build suggestions
I agree that this should be done after the release. Regarding logging: I am fine with JUL. I don't really care too much about that topic these days, hence I am fine with SLF4J, but I think I'd prefer JUL over it :-) -Matthias On Mon, May 24, 2010 at 11:55 PM, Roman Stumm roman.st...@gmx.de wrote: +1 for SLF4J. a no to JUL, but anyway: after the 0.1 release, please. I think there are more important things to be done, which are even more interesting... On 5/24/2010 8:33 PM, Carlos Vara wrote: Hi Gerhard, I think I located the thread in MyFaces mailing list, I will link it here for reference: http://www.mail-archive.com/d...@myfaces.apache.org/msg39139.html I'm not really too much opinionated about logging frameworks. I think that SLF4J usually offers the best compromise and is more flexible, but if more importance is given to other factors like not adding any dependencies or not modifying the current codebase, then JUL and keeping JCL would be the best choices respectively. I vote for SLF4J, but I will also help in an eventual JUL migration if that was the chosen logging framework. Regards, Carlos On Mon, May 24, 2010 at 4:22 PM, Gerhard Petracek gerhard.petra...@gmail.com wrote: hi carlos, i won't join the next long discussion about logging frameworks (just because such a discussion won't lead to a solution which works for most users - there are just too many completely different opinions out there). don't get me wrong - slf4j is a nice framework. in fact my original suggestion was to use it for all myfaces sub-projects. i just provided the result of a lot of very long and detailed discussions in the myfaces community. - we can benefit from these discussions or we just ignore them. (both cases might lead to additional online and/or offline discussions.) regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/5/24 Carlos Varabashfl...@gmail.com there is a jul to slf4j bridge - users would still have the choice. Yep, but if I remember it right, that bridge offers bad performance as there is no way to re-implement jul classes so it has to translate the logging messages. Log4j and commons logging bridges don't have that problem. Regards, Carlos regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/5/24 Donald Woodsdwo...@apache.org Moving to the SLF4J API would be nice, in that then users can choose which logger they want - Log4J, Jul, Simple, None, But, I see this as a 0.2 improvement and not as a stop-ship requirement for a 0.1-incubating release. -Donald On 5/24/10 4:27 AM, Carlos Vara wrote: 3. Is anyone interested in using slf4j instead of commons-logging? I am. At the moment I'm using a config similar to the one described here: http://blog.springsource.com/2009/12/04/logging-dependencies-in-spring/, which adds a bit of complexity in the pom but works fine. However, if dropping commons-logging (before or after the release) is an option, I volunteer to do the necessary changes in the code to migrate to slf4j. Regards, Carlos -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: TrinidadFaceletViewHandler missing
it has been removed since we moved our code to JSF2. http://svn.apache.org/viewvc?view=revisionrevision=824901 Note that Facelets is now part of JSF... -Matthias On Wed, May 12, 2010 at 12:01 AM, Ayhan T tekj...@gmail.com wrote: Hello, I am trying to use JSF 2 with Facelets and Trinidad (trinidad-api-2.0.0-alpha-2). With the latest Trinidad distribution (trinidad-api-2.0.0-alpha-2), I cannot find TrinidadFaceletViewHandler class in org.apache.myfaces.trinidadinternal.facelets. I am not quite sure how to implement Facelets without this class. Any help would be appreciated. Regards, Ayhan -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: About TCK
w00t !!! great job!! -Matthias On Mon, May 3, 2010 at 6:22 PM, Gurkan Erdogdu gurkanerdo...@yahoo.com wrote: Hello folks, Finally I have achieved passing of standalone TCK and Java Web profile TCK on Tomcat :). I have run the CDI-TCK 1.0.2-SNAPSHOT version that resolves some bugs. I have also issued some new bugs for CDI-TCK. On Tomcat, I have excluded on WebService End point injection test. Enjoy! --Gurkan -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Markmail messed up ?
Hi guys, somehow the threads in markmail are broken, aren't they ? E.g: http://markmail.org/message/zaiunaxuqfv7j2ea -M -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] become shared 4.0.x branch trunk
+1 -M On Fri, May 7, 2010 at 9:16 PM, Grant Smith work.gr...@gmail.com wrote: +1 On Fri, May 7, 2010 at 12:05 PM, Jan-Kees van Andel jankeesvanan...@gmail.com wrote: +1 /JK 2010/5/7 Bruno Aranda brunoara...@gmail.com +1 On 7 May 2010 15:46, Leonardo Uribe lu4...@gmail.com wrote: 2010/5/7 Jakob Korherr jakob.korh...@gmail.com +1 It will make things easier! However we have to be careful to not forget to change _every_ reference to shared trunk and 4.0.x_trunk (e.g. from orchestra, portlet-bridge, implee6,...). There are no svn references to shared in any different place (svn references are different to maven ones), so we are ok. Regards, Jakob 2010/5/7 Mark Struberg strub...@yahoo.de +1 I think this will be easier in the end. I did fall into this hole the 2nd time already ;) txs and LieGrue, strub --- Leonardo Uribe lu4...@gmail.com schrieb am Fr, 7.5.2010: Von: Leonardo Uribe lu4...@gmail.com Betreff: Re: [VOTE] become shared 4.0.x branch trunk An: MyFaces Development dev@myfaces.apache.org Datum: Freitag, 7. Mai, 2010 16:08 Uhr +1 2010/5/7 Leonardo Uribe lu4...@gmail.com Hi Right now, shared trunk points to jsf 1.1 version (in this case 2.0.x) and since most of the development is on JSF 2.0 branch we should change so the 4.0.x branch will be trunk. Also, the link on current module points to trunk and in this case jsf 1.1 branch. The change requires first a vote to be done. Please vote +1 if you want to make shared 4.0.x branch trunk, and create a current11 module so you can build jsf 1.1 sources like current12. regards, Leonardo Uribe [1] http://www.apache.org/foundation/voting.html#ReleaseVotes -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at -- Grant Smith - V.P. Information Technology Marathon Computer Systems, LLC. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE][PROPOSAL] Amber incubator
+1 (binding ) sent from my Android phone Am 06.05.2010 07:57 schrieb Gurkan Erdogdu gurkanerdo...@yahoo.com: +1 --Gurkan From: Simone Gianni simo...@apache.org To: general@incubator.apache.org Sent: Wed, May 5, 2010 1:48:46 AM Subject: [VOTE][PROPOSAL] Amber incubator I would like to present for a vote the following proposal to be sponsored by the Shindig PMC for a ...
[FYI] New article on Trinidad and mobile
Hi, a new article on Trinidad/Mobile JSF development: http://twitter.com/lucb_/status/13146979264 -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[FYI] New article on Trinidad and mobile
Hi, a new article on Trinidad/Mobile JSF development: http://twitter.com/lucb_/status/13146979264 -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: OpenEJB 3.1.3
Hi, I am using that too (3.1.3 SNAPSHOT) + OpenJPA2. JEan-Louis made binary preview available. Based on the patch: https://issues.apache.org/jira/browse/OPENEJB-1257 thread: http://markmail.org/message/6bd5p5qz7z2i3jdj On Fri, Apr 30, 2010 at 6:51 AM, Henri Gomez henri.go...@gmail.com wrote: Hi to all, We're currently use OpenEJB 3.1.2 with Tomcat 6 and are very happy with it. We'll have to use JPA 2.0 and someone on the Facebook Fan Page told me it allready works and should be available in OpenEJB 3.1.3. When should be released OpenEJB 3.1.3 ? BTW, did there is a 3.1.3-SNAPSHOT build available somewhere ? Regards -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: Web Profile using OpenEJB OpenWebBeans MyFaces 2 ...
On Mon, Apr 26, 2010 at 9:34 AM, Jean-Louis MONTEIRO jean-louis.monte...@atosorigin.com wrote: Hi all, I've been working for 2 weeks on this area and I (now) have a better understanding (thx Mark, Gurkan). I plan to have a look to some great patches provided by OpenWebBeans community (namely Gurkan, Matthias and Mark). Any body else already started working on that? Kinda: https://issues.apache.org/jira/browse/OWB-362 I tried the patch from Gurkan to even more refactor the jsf sample to use @Named (instead of @ManagedBean, which is used by my patch) Jean-Louis -- View this message in context: http://openejb.979440.n4.nabble.com/Web-Profile-using-OpenEJB-OpenWebBeans-MyFaces-2-tp2064811p2064811.html Sent from the OpenEJB Dev mailing list archive at Nabble.com. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: Web Profile using OpenEJB OpenWebBeans MyFaces 2 ...
ah, that's great. let me know if you need a new patch for https://issues.apache.org/jira/browse/OPENEJB-1264 in order to run/test that example via the 299/330 APIs. But basically I did the following (on-top of the above patch) -added atinject/jcdi as provided scoped dependency -changed the CalculatorBean to use @Named/@RequestScoped (from 299) -changed the @EJB to @Inject When I was running into problems I replaced the @Remote with @Local, and even got completely rid of it, but looks like the invocation part of OWB has a (slight) issue: https://issues.apache.org/jira/browse/OWB-362 -Matthias On Tue, Apr 27, 2010 at 11:48 AM, Jean-Louis MONTEIRO jean-louis.monte...@atosorigin.com wrote: Got that exception too. It seems to me, Gurkan's patch breaks something. BTW, I reverted a small change and it seems to solve this issue. Going ahead JLouis Matthias Wessendorf wrote: On Tue, Apr 27, 2010 at 11:03 AM, Jean-Louis MONTEIRO jean-louis.monte...@atosorigin.com wrote: Hey Matthias, Thanks for the feedback. Actually, i'm still trying to make the whole working with Gurkan's provided patch. I get some exceptions i need to fix. I'm running under Tomcat 6.0.26. have you tried 6.0.14 ? I think that worked for me, Generally I am seeing this: http://markmail.org/message/tb7wz7qr3vpt2ur5 Jean-Louis Matthias Wessendorf wrote: On Mon, Apr 26, 2010 at 9:34 AM, Jean-Louis MONTEIRO jean-louis.monte...@atosorigin.com wrote: Hi all, I've been working for 2 weeks on this area and I (now) have a better understanding (thx Mark, Gurkan). I plan to have a look to some great patches provided by OpenWebBeans community (namely Gurkan, Matthias and Mark). Any body else already started working on that? Kinda: https://issues.apache.org/jira/browse/OWB-362 I tried the patch from Gurkan to even more refactor the jsf sample to use @Named (instead of @ManagedBean, which is used by my patch) Jean-Louis -- View this message in context: http://openejb.979440.n4.nabble.com/Web-Profile-using-OpenEJB-OpenWebBeans-MyFaces-2-tp2064811p2064811.html Sent from the OpenEJB Dev mailing list archive at Nabble.com. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- View this message in context: http://openejb.979440.n4.nabble.com/Web-Profile-using-OpenEJB-OpenWebBeans-MyFaces-2-tp2064811p2067254.html Sent from the OpenEJB Dev mailing list archive at Nabble.com. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- View this message in context: http://openejb.979440.n4.nabble.com/Web-Profile-using-OpenEJB-OpenWebBeans-MyFaces-2-tp2064811p2067299.html Sent from the OpenEJB Dev mailing list archive at Nabble.com. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: Web Profile using OpenEJB OpenWebBeans MyFaces 2 ...
Hrm.. I saw something related to Caused by: javax.naming.NamingException: Aucun Contexte de nommage lié à ce thread at org.apache.naming.ContextBindings.getThreadName(ContextBindings.java:214) but.. I think that lead me to use 6.0.14 On Tue, Apr 27, 2010 at 7:58 AM, Jean-Louis MONTEIRO jean-louis.monte...@atosorigin.com wrote: Did you already get this kind of exception? http://pastebin.com/Y2LUszsM http://pastebin.com/Y2LUszsM Jean-Louis Matthias Wessendorf wrote: ah, that's great. let me know if you need a new patch for https://issues.apache.org/jira/browse/OPENEJB-1264 in order to run/test that example via the 299/330 APIs. But basically I did the following (on-top of the above patch) -added atinject/jcdi as provided scoped dependency -changed the CalculatorBean to use @Named/@RequestScoped (from 299) -changed the @EJB to @Inject When I was running into problems I replaced the @Remote with @Local, and even got completely rid of it, but looks like the invocation part of OWB has a (slight) issue: https://issues.apache.org/jira/browse/OWB-362 -Matthias On Tue, Apr 27, 2010 at 11:48 AM, Jean-Louis MONTEIRO jean-louis.monte...@atosorigin.com wrote: Got that exception too. It seems to me, Gurkan's patch breaks something. BTW, I reverted a small change and it seems to solve this issue. Going ahead JLouis Matthias Wessendorf wrote: On Tue, Apr 27, 2010 at 11:03 AM, Jean-Louis MONTEIRO jean-louis.monte...@atosorigin.com wrote: Hey Matthias, Thanks for the feedback. Actually, i'm still trying to make the whole working with Gurkan's provided patch. I get some exceptions i need to fix. I'm running under Tomcat 6.0.26. have you tried 6.0.14 ? I think that worked for me, Generally I am seeing this: http://markmail.org/message/tb7wz7qr3vpt2ur5 Jean-Louis Matthias Wessendorf wrote: On Mon, Apr 26, 2010 at 9:34 AM, Jean-Louis MONTEIRO jean-louis.monte...@atosorigin.com wrote: Hi all, I've been working for 2 weeks on this area and I (now) have a better understanding (thx Mark, Gurkan). I plan to have a look to some great patches provided by OpenWebBeans community (namely Gurkan, Matthias and Mark). Any body else already started working on that? Kinda: https://issues.apache.org/jira/browse/OWB-362 I tried the patch from Gurkan to even more refactor the jsf sample to use @Named (instead of @ManagedBean, which is used by my patch) Jean-Louis -- View this message in context: http://openejb.979440.n4.nabble.com/Web-Profile-using-OpenEJB-OpenWebBeans-MyFaces-2-tp2064811p2064811.html Sent from the OpenEJB Dev mailing list archive at Nabble.com. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- View this message in context: http://openejb.979440.n4.nabble.com/Web-Profile-using-OpenEJB-OpenWebBeans-MyFaces-2-tp2064811p2067254.html Sent from the OpenEJB Dev mailing list archive at Nabble.com. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- View this message in context: http://openejb.979440.n4.nabble.com/Web-Profile-using-OpenEJB-OpenWebBeans-MyFaces-2-tp2064811p2067299.html Sent from the OpenEJB Dev mailing list archive at Nabble.com. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- View this message in context: http://openejb.979440.n4.nabble.com/Web-Profile-using-OpenEJB-OpenWebBeans-MyFaces-2-tp2064811p2067713.html Sent from the OpenEJB Dev mailing list archive at Nabble.com. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
myfaces CDI extensions
Hi, I see some code in the CDI/extensions folder. I am wondering what's the current status is, or are there some wiki pages (e.g. agenda/roadmap)? Thanks, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: @EJB in Tomcat 6.0.14 and Gurkan's OWB/OEJB patch
I see, but that shouldn't make a big difference :-)
The important part is the same:
-OpenEJB trunk(3.1.3-SNAP) + your patch :-)
So I filed OWB-362 to not forget about it.
-Matthias
On Tue, Apr 27, 2010 at 7:28 AM, Gurkan Erdogdu gurkanerdo...@yahoo.com wrote:
Matthias;
I used Tomcat 6.0.26 and OpenEJB 3.1.3-SNAPSHOT.
Thanks;
--Gurkan
From: Matthias Wessendorf mat...@apache.org
To: dev@openwebbeans.apache.org
Sent: Mon, April 26, 2010 11:38:25 PM
Subject: Re: @EJB in Tomcat 6.0.14 and Gurkan's OWB/OEJB patch
Hi,
I just tried that again (fresh 6.014 TC installation + the patches
from Gurkan on OpenEJB trunk).
I simply want to deploy the the jsf example from OpenEJB (the
299/330 APIs I marked as provided),
after I apply this patch:
https://issues.apache.org/jira/browse/OPENEJB-1264
* Behavior:
-case: JSF/EJB
@ManagedBean/@RequestScoped (the JSF one)
work fine with @EJB
-case: 299/330 and EJB
The @Named and CDI's @RequestScoped work (bean look-up is fine)
Also, dependency injection works fine, IF I use @Inject for any
injection, other than an
EJB (statefull/stateless).
simple interface + implementation = OK
as soon as the implementation has @Stateless, I get the below exception..
IMO it looks like some issue with the proxy (invocation). See below.
Has one seen this before?
@Gurkan:
What was your Tomcat version that you used ?
You are using trunk with V3 of this patch:
https://issues.apache.org/jira/browse/OPENEJB-1257
right ?
==
SEVERE: An exception occurred
javax.faces.el.EvaluationException: javax.el.ELException:
/calculator.xhtml at line 39 and column 64 action=#{calculator.add}:
java.lang.reflect.InvocationTargetException
at
javax.faces.component._MethodExpressionToMethodBinding.invoke(_MethodExpressionToMethodBinding.java:96)
at
org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:100)
at javax.faces.component.UICommand.broadcast(UICommand.java:120)
at javax.faces.component.UIViewRoot._broadcastAll(UIViewRoot.java:890)
at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:234)
at javax.faces.component.UIViewRoot._process(UIViewRoot.java:1202)
at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:623)
at
org.apache.myfaces.lifecycle.InvokeApplicationExecutor.execute(InvokeApplicationExecutor.java:35)
at
org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:143)
at
org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:93)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:189)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.apache.openejb.tomcat.catalina.OpenEJBValve.invoke(OpenEJBValve.java:45)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:584)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
Caused by: javax.el.ELException: /calculator.xhtml at line 39 and
column 64 action=#{calculator.add}:
java.lang.reflect.InvocationTargetException
at
org.apache.myfaces.view.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:95)
at
javax.faces.component._MethodExpressionToMethodBinding.invoke(_MethodExpressionToMethodBinding.java:88)
... 23 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.webbeans.ejb.common.proxy.EjbBeanProxyHandler.invoke(EjbBeanProxyHandler.java:151)
at
org.superbiz.jsf.Calculator_$$_javassist_16.add(Calculator_$$_javassist_16.java)
at org.superbiz.jsf.CalculatorBean.add(CalculatorBean.java:58)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method
Re: @EJB in Tomcat 6.0.14 and Gurkan's OWB/OEJB patch
)
at
org.superbiz.jsf.CalculatorBean_$$_javassist_15.add(CalculatorBean_$$_javassist_15.java)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.el.parser.AstValue.invoke(AstValue.java:131)
at
org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276)
at
org.apache.myfaces.view.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:83)
... 24 more
Caused by: java.lang.NullPointerException
at $Proxy62.add(Unknown Source)
... 45 more
Apr 26, 2010 9:51:42 PM
org.apache.webbeans.ejb.common.proxy.EjbBeanProxyHandler hashCode
WARNING: Calling method on proxy is restricted except
Object.toString(), but current method is Object.hashCode
Apr 26, 2010 9:51:42 PM
org.apache.webbeans.ejb.common.proxy.EjbBeanProxyHandler hashCode
WARNING: Calling method on proxy is restricted except
Object.toString(), but current method is Object.hashCode
Apr 26, 2010 9:51:42 PM
org.apache.webbeans.ejb.common.proxy.EjbBeanProxyHandler hashCode
WARNING: Calling method on proxy is restricted except
Object.toString(), but current method is Object.hashCode
On Sun, Apr 25, 2010 at 10:40 PM, Matthias Wessendorf mat...@apache.org wrote:
good idea, but than I get:
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.webbeans.ejb.common.proxy.EjbBeanProxyHandler.invoke(EjbBeanProxyHandler.java:151)
at
org.superbiz.jsf.Calculator_$$_javassist_15.add(Calculator_$$_javassist_15.java)
at org.superbiz.jsf.CalculatorBean.add(CalculatorBean.java:55)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.webbeans.intercept.InterceptorHandler.invoke(InterceptorHandler.java:265)
at
org.apache.webbeans.intercept.NormalScopedBeanInterceptorHandler.invoke(NormalScopedBeanInterceptorHandler.java:78)
at
org.superbiz.jsf.CalculatorBean_$$_javassist_14.add(CalculatorBean_$$_javassist_14.java)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.el.parser.AstValue.invoke(AstValue.java:131)
at
org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276)
at
org.apache.myfaces.view.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:83)
... 24 more
On Sun, Apr 25, 2010 at 10:08 PM, Gurkan Erdogdu
cgurkanerdo...@gmail.com wrote:
How you use @EJB? Instead of using @EJB, you can directly inject EJBs using
@Inject annotation via Local interface of the EJBs.
Look at http://openejb.apache.org/3.0/jndi-names.html for jndi naming.
2010/4/25 Matthias Wessendorf mat...@apache.org
Hi,
I am on TC 6_0_14, combined w/ Gurkan's cool patch. When I have a CDI bean:
@Named(calculator)
@RequestScoped
public class CalculatorBean {
...
}
with an @EJB injection, I am getting this ClassCastException:
Caused by: java.lang.ClassCastException
at java.lang.Class.cast(Class.java:2990)
at
org.apache.webbeans.ejb.resource.ResourceInjectionProcessor.lookupFieldResource(ResourceInjectionProcessor.java:97)
at
org.apache.webbeans.ejb.resource.ResourceInjectionProcessor.getResourceReference(ResourceInjectionProcessor.java:64)
at
org.apache.webbeans.ejb.resource.ResourceFactory.getResourceReference(ResourceFactory.java:64)
at
org.apache.webbeans.ejb.resource.OpenEjbResourceInjectionService.getResourceReference(OpenEjbResourceInjectionService.java:50)
at
org.apache.webbeans.ejb.resource.OpenEjbResourceInjectionService.injectJavaEEResources(OpenEjbResourceInjectionService.java:78)
at
org.apache.webbeans.component.AbstractInjectionTargetBean.injectResources(AbstractInjectionTargetBean.java:391)
at
org.apache.webbeans.portable.creation.InjectionTargetProducer.inject(InjectionTargetProducer.java:76)
at
org.apache.webbeans.component.InjectionTargetWrapper.inject
Re: IllegalAccessException with TomcatThreadContextListener
In the meantime, I used Tomcat 6.0.14, as a work-around. ;-) On Sat, Apr 24, 2010 at 4:28 PM, Matthias Wessendorf mat...@apache.org wrote: Hi, I checked out the 3.1.2 TAG, applied the following patches: - https://issues.apache.org/jira/browse/OPENEJB-1131 - https://issues.apache.org/jira/browse/OPENEJB-1257 I deployed the openejb.war to Tomcat 6.0.26 and when I deploy (and access the openejb jsf demo (see [1])), I see the following in the openejb.log: 2010-04-24 16:02:34,572 - ERROR - Exception in method getThreadName java.lang.IllegalAccessException: Class org.apache.openejb.tomcat.catalina.TomcatThreadContextListener can not access a member of class org.apache.naming.ContextBindings with modifiers static at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65) at java.lang.reflect.Method.invoke(Method.java:588) at org.apache.openejb.tomcat.catalina.TomcatThreadContextListener.getThreadName(TomcatThreadContextListener.java:109) at org.apache.openejb.tomcat.catalina.TomcatThreadContextListener.contextEntered(TomcatThreadContextListener.java:70) at org.apache.openejb.core.ThreadContext.enter(ThreadContext.java:53) at org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:148) at org.apache.openejb.core.ivm.EjbHomeProxyHandler.create(EjbHomeProxyHandler.java:276) at org.apache.openejb.core.ivm.EjbHomeProxyHandler._invoke(EjbHomeProxyHandler.java:161) at org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:281) at $Proxy34.create(Unknown Source) at org.apache.openejb.core.ivm.naming.BusinessRemoteReference.getObject(BusinessRemoteReference.java:33) at org.apache.openejb.core.ivm.naming.IvmContext.lookup(IvmContext.java:171) at org.apache.openejb.core.ivm.naming.IvmContext.lookup(IvmContext.java:121) at org.apache.openejb.tomcat.common.AbstractObjectFactory.lookup(AbstractObjectFactory.java:60) at org.apache.openejb.tomcat.common.AbstractObjectFactory.getObjectInstance(AbstractObjectFactory.java:47) at org.apache.openejb.tomcat.common.EjbFactory.getObjectInstance(EjbFactory.java:50) at org.apache.naming.factory.EjbFactory.getObjectInstance(EjbFactory.java:161) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304) at org.apache.naming.NamingContext.lookup(NamingContext.java:793) at org.apache.naming.NamingContext.lookup(NamingContext.java:140) at org.apache.naming.NamingContext.lookup(NamingContext.java:781) at org.apache.naming.NamingContext.lookup(NamingContext.java:153) at org.apache.catalina.util.DefaultAnnotationProcessor.lookupFieldResource(DefaultAnnotationProcessor.java:278) at org.apache.catalina.util.DefaultAnnotationProcessor.processAnnotations(DefaultAnnotationProcessor.java:192) at org.apache.myfaces.config.annotation.TomcatAnnotationLifecycleProvider.newInstance(TomcatAnnotationLifecycleProvider.java:46) at org.apache.myfaces.config.ManagedBeanBuilder.buildManagedBean(ManagedBeanBuilder.java:81) at org.apache.myfaces.el.unified.resolver.ManagedBeanResolver.createManagedBean(ManagedBeanResolver.java:196) at org.apache.myfaces.el.unified.resolver.ManagedBeanResolver.getValue(ManagedBeanResolver.java:162) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:54) at org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.access$301(FacesCompositeELResolver.java:46) at org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver$4.invoke(FacesCompositeELResolver.java:108) at org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.invoke(FacesCompositeELResolver.java:148) at org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:104) at org.apache.myfaces.el.VariableResolverImpl.resolveVariable(VariableResolverImpl.java:61) at org.apache.myfaces.el.convert.VariableResolverToELResolver.getValue(VariableResolverToELResolver.java:93) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:54) at org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.access$301(FacesCompositeELResolver.java:46) at org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver$4.invoke(FacesCompositeELResolver.java:108) at org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.invoke(FacesCompositeELResolver.java:148) at org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:104) at org.apache.el.parser.AstIdentifier.getValue(AstIdentifier.java:68) at org.apache.el.parser.AstValue.getTarget(AstValue.java:68) at org.apache.el.parser.AstValue.invoke(AstValue.java:187
Re: @EJB in Tomcat 6.0.14 and Gurkan's OWB/OEJB patch
good idea, but than I get:
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.webbeans.ejb.common.proxy.EjbBeanProxyHandler.invoke(EjbBeanProxyHandler.java:151)
at
org.superbiz.jsf.Calculator_$$_javassist_15.add(Calculator_$$_javassist_15.java)
at org.superbiz.jsf.CalculatorBean.add(CalculatorBean.java:55)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.webbeans.intercept.InterceptorHandler.invoke(InterceptorHandler.java:265)
at
org.apache.webbeans.intercept.NormalScopedBeanInterceptorHandler.invoke(NormalScopedBeanInterceptorHandler.java:78)
at
org.superbiz.jsf.CalculatorBean_$$_javassist_14.add(CalculatorBean_$$_javassist_14.java)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.el.parser.AstValue.invoke(AstValue.java:131)
at
org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276)
at
org.apache.myfaces.view.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:83)
... 24 more
On Sun, Apr 25, 2010 at 10:08 PM, Gurkan Erdogdu
cgurkanerdo...@gmail.com wrote:
How you use @EJB? Instead of using @EJB, you can directly inject EJBs using
@Inject annotation via Local interface of the EJBs.
Look at http://openejb.apache.org/3.0/jndi-names.html for jndi naming.
2010/4/25 Matthias Wessendorf mat...@apache.org
Hi,
I am on TC 6_0_14, combined w/ Gurkan's cool patch. When I have a CDI bean:
@Named(calculator)
@RequestScoped
public class CalculatorBean {
...
}
with an @EJB injection, I am getting this ClassCastException:
Caused by: java.lang.ClassCastException
at java.lang.Class.cast(Class.java:2990)
at
org.apache.webbeans.ejb.resource.ResourceInjectionProcessor.lookupFieldResource(ResourceInjectionProcessor.java:97)
at
org.apache.webbeans.ejb.resource.ResourceInjectionProcessor.getResourceReference(ResourceInjectionProcessor.java:64)
at
org.apache.webbeans.ejb.resource.ResourceFactory.getResourceReference(ResourceFactory.java:64)
at
org.apache.webbeans.ejb.resource.OpenEjbResourceInjectionService.getResourceReference(OpenEjbResourceInjectionService.java:50)
at
org.apache.webbeans.ejb.resource.OpenEjbResourceInjectionService.injectJavaEEResources(OpenEjbResourceInjectionService.java:78)
at
org.apache.webbeans.component.AbstractInjectionTargetBean.injectResources(AbstractInjectionTargetBean.java:391)
at
org.apache.webbeans.portable.creation.InjectionTargetProducer.inject(InjectionTargetProducer.java:76)
at
org.apache.webbeans.component.InjectionTargetWrapper.inject(InjectionTargetWrapper.java:80)
at
org.apache.webbeans.component.AbstractOwbBean.create(AbstractOwbBean.java:157)
at
org.apache.webbeans.context.AbstractContext.getInstance(AbstractContext.java:219)
at
org.apache.webbeans.context.AbstractContext.get(AbstractContext.java:182)
at
org.apache.webbeans.intercept.NormalScopedBeanInterceptorHandler.getContextualInstance(NormalScopedBeanInterceptorHandler.java:117)
at
org.apache.webbeans.intercept.NormalScopedBeanInterceptorHandler.invoke(NormalScopedBeanInterceptorHandler.java:75)
at
org.superbiz.jsf.CalculatorBean_$$_javassist_5.getX(CalculatorBean_$$_javassist_5.java)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at javax.el.BeanELResolver.getValue(BeanELResolver.java:62)
at
javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53)
at
org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:140)
at org.apache.el.parser.AstValue.getValue(AstValue.java:97)
at
org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186
IllegalAccessException with TomcatThreadContextListener
(LifecycleImpl.java:76) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:148) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:147) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.openejb.tomcat.catalina.OpenEJBValve.invoke(OpenEJBValve.java:45) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:852) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) at java.lang.Thread.run(Thread.java:619) The Apache Tomcat class that the TomcatThreadContextListener complains about can be seen here: http://j.mp/bDsgtY Any ideas? Or seen before ? Thanks, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: BeanManagerImpl - improvement on WebBeansConfigurationException ?
ok, thanks
REV: 937626
-M
On Sat, Apr 24, 2010 at 2:42 PM, Gurkan Erdogdu gurkanerdo...@yahoo.com wrote:
Thanks a lot Matthias! Also congratulations for JSF 2.0.0 release.
--Gurkan
From: Matthias Wessendorf mat...@apache.org
To: dev@openwebbeans.apache.org
Sent: Fri, April 23, 2010 11:36:35 PM
Subject: BeanManagerImpl - improvement on WebBeansConfigurationException ?
Hi,
I think that on the BeanManagerImpl class there is (some) room for
improvements.
Below is a patch to have a slightly better exception text.
Does one mind if I commit that ?
Thanks!
Matthias
Index:
webbeans-impl/src/main/java/org/apache/webbeans/container/BeanManagerImpl.java
===
---
webbeans-impl/src/main/java/org/apache/webbeans/container/BeanManagerImpl.java
(revision
937508)
+++
webbeans-impl/src/main/java/org/apache/webbeans/container/BeanManagerImpl.java
(working
copy)
@@ -1008,7 +1008,7 @@
{
if (!bean.getScope().equals(Dependent.class))
{
- throw new WebBeansConfigurationException(Bean
+ bean + scope can not define other scope except @Dependent to inject
InjectionPoint);
+ throw new WebBeansConfigurationException(Bean
+ bean.getBeanClass() + scope can not define other scope except
@Dependent to inject InjectionPoint);
}
}
}
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
BeanManagerImpl - improvement on WebBeansConfigurationException ?
Hi,
I think that on the BeanManagerImpl class there is (some) room for improvements.
Below is a patch to have a slightly better exception text.
Does one mind if I commit that ?
Thanks!
Matthias
Index:
webbeans-impl/src/main/java/org/apache/webbeans/container/BeanManagerImpl.java
===
---
webbeans-impl/src/main/java/org/apache/webbeans/container/BeanManagerImpl.java
(revision
937508)
+++
webbeans-impl/src/main/java/org/apache/webbeans/container/BeanManagerImpl.java
(working
copy)
@@ -1008,7 +1008,7 @@
{
if (!bean.getScope().equals(Dependent.class))
{
-throw new WebBeansConfigurationException(Bean
+ bean + scope can not define other scope except @Dependent to inject
InjectionPoint);
+throw new WebBeansConfigurationException(Bean
+ bean.getBeanClass() + scope can not define other scope except
@Dependent to inject InjectionPoint);
}
}
}
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Re: Ext-Scripting Final Logo
+1 like it too! -M On Tue, Apr 20, 2010 at 5:04 PM, Bruno Aranda brunoara...@gmail.com wrote: Great job! I like it, Cheers, Bruno On 20 April 2010 16:01, Jakob Korherr jakob.korh...@gmail.com wrote: It looks _very_ great and, of course, totally fits into the myfaces design. Regards, Jakob 2010/4/20 Werner Punz werner.p...@gmail.com Hello everyone, Adonis (who designed the other Logos) has given me a final logo it looks now like following: http://people.apache.org/~werpu/ext-script-site/images/extscriptlogo.png respectively in conjunction with the documentation: http://people.apache.org/~werpu/ext-script-site/ I think the logo is more than perfect and fits into our design. Werner -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [Trinidad 2] AJAX branch ready for testing
On Tue, Apr 20, 2010 at 6:40 PM, Andrew Robinson andrew.rw.robin...@gmail.com wrote: On Tue, Apr 20, 2010 at 7:59 AM, Matthias Wessendorf mat...@apache.org wrote: on the pprDemos.jspx stuff, there is a bunch of tests for PPR, one of the has the header Command components with partialSubmit, which does not work (in the trinidad demo) Works fine for me using -Djsf=ri2 except for the selectManyListbox once I did a rebuild and refresh. Thanks for the pointer on the old ri2/myfaces2 profiles. I just removed them, since the ri/myfaces profiles were already pointing to JSF2, so these are no longer needed (have been introduced as a tmp thing, when the JSF2 work started) -Matthias File (in SVN) is located there: https://svn.apache.org/repos/asf/myfaces/trinidad/branches/jsf2_ajax.3/trinidad-examples/trinidad-demo/src/main/webapp/demos/pprDemos.jspx On Tue, Apr 20, 2010 at 6:37 AM, Max Starets max.star...@oracle.com wrote: Matthias, What do you mean when you say 'command components with partialSubmit do not work'? Thanks, Max On Apr 20, 2010, at 3:26 AM, Matthias Wessendorf mat...@apache.org wrote: Checked Mojarra 2.0.1 and MyFaces 2.0.0 (out soon) - both have the NPE filed in TRINIDAD-1786 * Mojarra: -PPR on select* works (exception see above) - Command components with partialSubmit does _not_ work * MyFaces: - all PPR stuff does a full page-refresh I am fine in merging these bits to trunk, but before we acutally do a release, we should check what's going wrong in MyFaces/Trinidad ;-) (I think it must be an issue in MyFaces, so once I have some more time, I will file a bug against that, with a little better description) -Matthias On Tue, Apr 20, 2010 at 9:09 AM, Matthias Wessendorf mat...@apache.org wrote: Ok, looks like you are talking about JSF2's JS/Ajax stuff. The term mojarra is slightly confusing, since I understand it as a specific dependency to that particular implementation. But looks like we do not have that, for the ajax stuff, which is great. -Matthias On Tue, Apr 20, 2010 at 9:05 AM, Matthias Wessendorf mat...@apache.org wrote: On Mon, Apr 19, 2010 at 11:58 PM, Andrew Robinson andrew.rw.robin...@gmail.com wrote: The branch is ready and the issues that were brought up in this thread as well as other issues have been resolved. Unless there are any objections, I will merge the changes into the trunk tomorrow. fine here. Note that Max added a switch to be able to turn off PPR through JSF at the agent level so that mobile browsers that fail with the mojarra JavaScript can go back to the legacy code. not sure I understand: why is that switch mojarra specific ? Or are you just saying that it's a fallback to JSF2 ? -Matthias -Andrew On Wed, Apr 7, 2010 at 8:33 AM, Max Starets max.star...@oracle.com wrote: Just a few minor additions - - PartialViewContext.isAjaxRequest() will be returning true for the requests sent with jsf ajax as well as the legacy partialSubmit=true requests. - Trinidad's partial triggers will be honored for the jsf ajax requests. However, this will currently work only with execute=@all. Once we start adding trigger listeners during the PostRestoreView event processing, instead of decode, this limitation will go away. Max Andrew Robinson wrote: Well after a bit of work, the JSF2 AJAX branch is ready for testing to see if we want to merge it into the trunk. Branch: https://svn.apache.org/repos/asf/myfaces/trinidad/branches/jsf2_ajax.3 Details: - jsf.ajax.request used to submit PPR requests from the request queue - server serves JSF2 payload, differing if an IFRAME submission is detected for Trinidad to send down script libraries - iframe processing through legacy code, but updated to use a valid JSF2 payload - iframe still sends Tr-XHR-Message to let the server know its a legacy request - legacy request supports DOM replacement but none of the new functionality of JSF2 (attribute updates for example) - TrPage integrated with JSF2 events to correctly broadcast DOM change notifications and restore focus - If users find errors in the jsf.js libraries, setting the _useJsfBuiltInAjaxForXhr property of the request queue to false will bypass usage of jsf.ajax. We can add support for a public way of doing this later if necessary. - Server side integration with the JSF2 APIs and client behaviors, JSF2 submission working along side of partialSubmit=true and auto PPR. Thank you, Andrew -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http
Re: [Trinidad 2] AJAX branch ready for testing
Yes, the -Djsf=ri profile works (with the know exception), but default profile (with temporary using MyFaces 2.0.1-SNAPSHOT), I do get a full-page-refresh. See MYFACES-2666 -Matthias On Tue, Apr 20, 2010 at 6:40 PM, Andrew Robinson andrew.rw.robin...@gmail.com wrote: On Tue, Apr 20, 2010 at 7:59 AM, Matthias Wessendorf mat...@apache.org wrote: on the pprDemos.jspx stuff, there is a bunch of tests for PPR, one of the has the header Command components with partialSubmit, which does not work (in the trinidad demo) Works fine for me using -Djsf=ri2 except for the selectManyListbox once I did a rebuild and refresh. File (in SVN) is located there: https://svn.apache.org/repos/asf/myfaces/trinidad/branches/jsf2_ajax.3/trinidad-examples/trinidad-demo/src/main/webapp/demos/pprDemos.jspx On Tue, Apr 20, 2010 at 6:37 AM, Max Starets max.star...@oracle.com wrote: Matthias, What do you mean when you say 'command components with partialSubmit do not work'? Thanks, Max On Apr 20, 2010, at 3:26 AM, Matthias Wessendorf mat...@apache.org wrote: Checked Mojarra 2.0.1 and MyFaces 2.0.0 (out soon) - both have the NPE filed in TRINIDAD-1786 * Mojarra: -PPR on select* works (exception see above) - Command components with partialSubmit does _not_ work * MyFaces: - all PPR stuff does a full page-refresh I am fine in merging these bits to trunk, but before we acutally do a release, we should check what's going wrong in MyFaces/Trinidad ;-) (I think it must be an issue in MyFaces, so once I have some more time, I will file a bug against that, with a little better description) -Matthias On Tue, Apr 20, 2010 at 9:09 AM, Matthias Wessendorf mat...@apache.org wrote: Ok, looks like you are talking about JSF2's JS/Ajax stuff. The term mojarra is slightly confusing, since I understand it as a specific dependency to that particular implementation. But looks like we do not have that, for the ajax stuff, which is great. -Matthias On Tue, Apr 20, 2010 at 9:05 AM, Matthias Wessendorf mat...@apache.org wrote: On Mon, Apr 19, 2010 at 11:58 PM, Andrew Robinson andrew.rw.robin...@gmail.com wrote: The branch is ready and the issues that were brought up in this thread as well as other issues have been resolved. Unless there are any objections, I will merge the changes into the trunk tomorrow. fine here. Note that Max added a switch to be able to turn off PPR through JSF at the agent level so that mobile browsers that fail with the mojarra JavaScript can go back to the legacy code. not sure I understand: why is that switch mojarra specific ? Or are you just saying that it's a fallback to JSF2 ? -Matthias -Andrew On Wed, Apr 7, 2010 at 8:33 AM, Max Starets max.star...@oracle.com wrote: Just a few minor additions - - PartialViewContext.isAjaxRequest() will be returning true for the requests sent with jsf ajax as well as the legacy partialSubmit=true requests. - Trinidad's partial triggers will be honored for the jsf ajax requests. However, this will currently work only with execute=@all. Once we start adding trigger listeners during the PostRestoreView event processing, instead of decode, this limitation will go away. Max Andrew Robinson wrote: Well after a bit of work, the JSF2 AJAX branch is ready for testing to see if we want to merge it into the trunk. Branch: https://svn.apache.org/repos/asf/myfaces/trinidad/branches/jsf2_ajax.3 Details: - jsf.ajax.request used to submit PPR requests from the request queue - server serves JSF2 payload, differing if an IFRAME submission is detected for Trinidad to send down script libraries - iframe processing through legacy code, but updated to use a valid JSF2 payload - iframe still sends Tr-XHR-Message to let the server know its a legacy request - legacy request supports DOM replacement but none of the new functionality of JSF2 (attribute updates for example) - TrPage integrated with JSF2 events to correctly broadcast DOM change notifications and restore focus - If users find errors in the jsf.js libraries, setting the _useJsfBuiltInAjaxForXhr property of the request queue to false will bypass usage of jsf.ajax. We can add support for a public way of doing this later if necessary. - Server side integration with the JSF2 APIs and client behaviors, JSF2 submission working along side of partialSubmit=true and auto PPR. Thank you, Andrew -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http
Re: [Trinidad 2] AJAX branch ready for testing
can you file a jira issue ? On Mon, Apr 19, 2010 at 7:37 PM, Andrew Robinson andrew.rw.robin...@gmail.com wrote: _ajaxOldDomElements is code in Page.js, this looks like a bug in Trinidad that needs to be fixed On Fri, Apr 9, 2010 at 8:52 AM, Matthias Wessendorf mat...@apache.org wrote: looks like the 2.0.1 are just labeled as Mojarra 2.0.2 (SNAPSHOT 20091204) I now updated the pom to 2.0.2 and got this log: INFO: Initializing Mojarra 2.0.2 (FCS b10) But the error is the same on the clientBehaviorHolder.xhtml page -Matthias On Fri, Apr 9, 2010 at 4:33 PM, Matthias Wessendorf mat...@apache.org wrote: eh, funny. the pom is actually configured with 2.0.1. Something is going wrong here :-) On Fri, Apr 9, 2010 at 4:15 PM, Max Starets max.star...@oracle.com wrote: Matthias, Are you getting the same results with Mojarra 2.0.1? Max Matthias Wessendorf wrote: hi, I gave it a quick try. Here are my results: Page: http://localhost:8080/trinidad-demo/faces/demos/clientBehaviorHolder.xhtml JSF_RI (Mojarra 2.0.2 (SNAPSHOT 20091204)) results: I entered some text and clicked submit via JSF Ajax Got this (in an alert JS box): httpError: The Http Transport returned a 0 status code. This is usually the result of mixing ajax and full requests. This is usually undesired, for both performance and data integrity reasons. second click on the same button I got this JS error. mojarra is not defined [Break on this error] var func = new Function(event, handler); === the submit button works. MyFaces 2.0.0-SNAPHOT results: (using snapshot since the ViewExpiredException is gone in latest snapshot ) * submit button gives me this ALERT() box: TypeError: this._ajaxOldDomElements is null followed by this: malformedXML-- * Submit via JSF Ajax: I get this alert() BOX: httpError-httpError-Request failed Are there any other pages where I can test the new functionality ? -Matthias On Wed, Apr 7, 2010 at 4:33 PM, Max Starets max.star...@oracle.com wrote: Just a few minor additions - - PartialViewContext.isAjaxRequest() will be returning true for the requests sent with jsf ajax as well as the legacy partialSubmit=true requests. - Trinidad's partial triggers will be honored for the jsf ajax requests. However, this will currently work only with execute=@all. Once we start adding trigger listeners during the PostRestoreView event processing, instead of decode, this limitation will go away. Max Andrew Robinson wrote: Well after a bit of work, the JSF2 AJAX branch is ready for testing to see if we want to merge it into the trunk. Branch: https://svn.apache.org/repos/asf/myfaces/trinidad/branches/jsf2_ajax.3 Details: - jsf.ajax.request used to submit PPR requests from the request queue - server serves JSF2 payload, differing if an IFRAME submission is detected for Trinidad to send down script libraries - iframe processing through legacy code, but updated to use a valid JSF2 payload - iframe still sends Tr-XHR-Message to let the server know its a legacy request - legacy request supports DOM replacement but none of the new functionality of JSF2 (attribute updates for example) - TrPage integrated with JSF2 events to correctly broadcast DOM change notifications and restore focus - If users find errors in the jsf.js libraries, setting the _useJsfBuiltInAjaxForXhr property of the request queue to false will bypass usage of jsf.ajax. We can add support for a public way of doing this later if necessary. - Server side integration with the JSF2 APIs and client behaviors, JSF2 submission working along side of partialSubmit=true and auto PPR. Thank you, Andrew -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [Trinidad 2] AJAX branch ready for testing
On Mon, Apr 19, 2010 at 11:58 PM, Andrew Robinson andrew.rw.robin...@gmail.com wrote: The branch is ready and the issues that were brought up in this thread as well as other issues have been resolved. Unless there are any objections, I will merge the changes into the trunk tomorrow. fine here. Note that Max added a switch to be able to turn off PPR through JSF at the agent level so that mobile browsers that fail with the mojarra JavaScript can go back to the legacy code. not sure I understand: why is that switch mojarra specific ? Or are you just saying that it's a fallback to JSF2 ? -Matthias -Andrew On Wed, Apr 7, 2010 at 8:33 AM, Max Starets max.star...@oracle.com wrote: Just a few minor additions - - PartialViewContext.isAjaxRequest() will be returning true for the requests sent with jsf ajax as well as the legacy partialSubmit=true requests. - Trinidad's partial triggers will be honored for the jsf ajax requests. However, this will currently work only with execute=@all. Once we start adding trigger listeners during the PostRestoreView event processing, instead of decode, this limitation will go away. Max Andrew Robinson wrote: Well after a bit of work, the JSF2 AJAX branch is ready for testing to see if we want to merge it into the trunk. Branch: https://svn.apache.org/repos/asf/myfaces/trinidad/branches/jsf2_ajax.3 Details: - jsf.ajax.request used to submit PPR requests from the request queue - server serves JSF2 payload, differing if an IFRAME submission is detected for Trinidad to send down script libraries - iframe processing through legacy code, but updated to use a valid JSF2 payload - iframe still sends Tr-XHR-Message to let the server know its a legacy request - legacy request supports DOM replacement but none of the new functionality of JSF2 (attribute updates for example) - TrPage integrated with JSF2 events to correctly broadcast DOM change notifications and restore focus - If users find errors in the jsf.js libraries, setting the _useJsfBuiltInAjaxForXhr property of the request queue to false will bypass usage of jsf.ajax. We can add support for a public way of doing this later if necessary. - Server side integration with the JSF2 APIs and client behaviors, JSF2 submission working along side of partialSubmit=true and auto PPR. Thank you, Andrew -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [Trinidad 2] AJAX branch ready for testing
Ok, looks like you are talking about JSF2's JS/Ajax stuff. The term mojarra is slightly confusing, since I understand it as a specific dependency to that particular implementation. But looks like we do not have that, for the ajax stuff, which is great. -Matthias On Tue, Apr 20, 2010 at 9:05 AM, Matthias Wessendorf mat...@apache.org wrote: On Mon, Apr 19, 2010 at 11:58 PM, Andrew Robinson andrew.rw.robin...@gmail.com wrote: The branch is ready and the issues that were brought up in this thread as well as other issues have been resolved. Unless there are any objections, I will merge the changes into the trunk tomorrow. fine here. Note that Max added a switch to be able to turn off PPR through JSF at the agent level so that mobile browsers that fail with the mojarra JavaScript can go back to the legacy code. not sure I understand: why is that switch mojarra specific ? Or are you just saying that it's a fallback to JSF2 ? -Matthias -Andrew On Wed, Apr 7, 2010 at 8:33 AM, Max Starets max.star...@oracle.com wrote: Just a few minor additions - - PartialViewContext.isAjaxRequest() will be returning true for the requests sent with jsf ajax as well as the legacy partialSubmit=true requests. - Trinidad's partial triggers will be honored for the jsf ajax requests. However, this will currently work only with execute=@all. Once we start adding trigger listeners during the PostRestoreView event processing, instead of decode, this limitation will go away. Max Andrew Robinson wrote: Well after a bit of work, the JSF2 AJAX branch is ready for testing to see if we want to merge it into the trunk. Branch: https://svn.apache.org/repos/asf/myfaces/trinidad/branches/jsf2_ajax.3 Details: - jsf.ajax.request used to submit PPR requests from the request queue - server serves JSF2 payload, differing if an IFRAME submission is detected for Trinidad to send down script libraries - iframe processing through legacy code, but updated to use a valid JSF2 payload - iframe still sends Tr-XHR-Message to let the server know its a legacy request - legacy request supports DOM replacement but none of the new functionality of JSF2 (attribute updates for example) - TrPage integrated with JSF2 events to correctly broadcast DOM change notifications and restore focus - If users find errors in the jsf.js libraries, setting the _useJsfBuiltInAjaxForXhr property of the request queue to false will bypass usage of jsf.ajax. We can add support for a public way of doing this later if necessary. - Server side integration with the JSF2 APIs and client behaviors, JSF2 submission working along side of partialSubmit=true and auto PPR. Thank you, Andrew -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [Trinidad 2] AJAX branch ready for testing
Checked Mojarra 2.0.1 and MyFaces 2.0.0 (out soon) - both have the NPE filed in TRINIDAD-1786 * Mojarra: -PPR on select* works (exception see above) - Command components with partialSubmit does _not_ work * MyFaces: - all PPR stuff does a full page-refresh I am fine in merging these bits to trunk, but before we acutally do a release, we should check what's going wrong in MyFaces/Trinidad ;-) (I think it must be an issue in MyFaces, so once I have some more time, I will file a bug against that, with a little better description) -Matthias On Tue, Apr 20, 2010 at 9:09 AM, Matthias Wessendorf mat...@apache.org wrote: Ok, looks like you are talking about JSF2's JS/Ajax stuff. The term mojarra is slightly confusing, since I understand it as a specific dependency to that particular implementation. But looks like we do not have that, for the ajax stuff, which is great. -Matthias On Tue, Apr 20, 2010 at 9:05 AM, Matthias Wessendorf mat...@apache.org wrote: On Mon, Apr 19, 2010 at 11:58 PM, Andrew Robinson andrew.rw.robin...@gmail.com wrote: The branch is ready and the issues that were brought up in this thread as well as other issues have been resolved. Unless there are any objections, I will merge the changes into the trunk tomorrow. fine here. Note that Max added a switch to be able to turn off PPR through JSF at the agent level so that mobile browsers that fail with the mojarra JavaScript can go back to the legacy code. not sure I understand: why is that switch mojarra specific ? Or are you just saying that it's a fallback to JSF2 ? -Matthias -Andrew On Wed, Apr 7, 2010 at 8:33 AM, Max Starets max.star...@oracle.com wrote: Just a few minor additions - - PartialViewContext.isAjaxRequest() will be returning true for the requests sent with jsf ajax as well as the legacy partialSubmit=true requests. - Trinidad's partial triggers will be honored for the jsf ajax requests. However, this will currently work only with execute=@all. Once we start adding trigger listeners during the PostRestoreView event processing, instead of decode, this limitation will go away. Max Andrew Robinson wrote: Well after a bit of work, the JSF2 AJAX branch is ready for testing to see if we want to merge it into the trunk. Branch: https://svn.apache.org/repos/asf/myfaces/trinidad/branches/jsf2_ajax.3 Details: - jsf.ajax.request used to submit PPR requests from the request queue - server serves JSF2 payload, differing if an IFRAME submission is detected for Trinidad to send down script libraries - iframe processing through legacy code, but updated to use a valid JSF2 payload - iframe still sends Tr-XHR-Message to let the server know its a legacy request - legacy request supports DOM replacement but none of the new functionality of JSF2 (attribute updates for example) - TrPage integrated with JSF2 events to correctly broadcast DOM change notifications and restore focus - If users find errors in the jsf.js libraries, setting the _useJsfBuiltInAjaxForXhr property of the request queue to false will bypass usage of jsf.ajax. We can add support for a public way of doing this later if necessary. - Server side integration with the JSF2 APIs and client behaviors, JSF2 submission working along side of partialSubmit=true and auto PPR. Thank you, Andrew -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [Trinidad 2] AJAX branch ready for testing
on the pprDemos.jspx stuff, there is a bunch of tests for PPR, one of the has the header Command components with partialSubmit, which does not work (in the trinidad demo) File (in SVN) is located there: https://svn.apache.org/repos/asf/myfaces/trinidad/branches/jsf2_ajax.3/trinidad-examples/trinidad-demo/src/main/webapp/demos/pprDemos.jspx On Tue, Apr 20, 2010 at 6:37 AM, Max Starets max.star...@oracle.com wrote: Matthias, What do you mean when you say 'command components with partialSubmit do not work'? Thanks, Max On Apr 20, 2010, at 3:26 AM, Matthias Wessendorf mat...@apache.org wrote: Checked Mojarra 2.0.1 and MyFaces 2.0.0 (out soon) - both have the NPE filed in TRINIDAD-1786 * Mojarra: -PPR on select* works (exception see above) - Command components with partialSubmit does _not_ work * MyFaces: - all PPR stuff does a full page-refresh I am fine in merging these bits to trunk, but before we acutally do a release, we should check what's going wrong in MyFaces/Trinidad ;-) (I think it must be an issue in MyFaces, so once I have some more time, I will file a bug against that, with a little better description) -Matthias On Tue, Apr 20, 2010 at 9:09 AM, Matthias Wessendorf mat...@apache.org wrote: Ok, looks like you are talking about JSF2's JS/Ajax stuff. The term mojarra is slightly confusing, since I understand it as a specific dependency to that particular implementation. But looks like we do not have that, for the ajax stuff, which is great. -Matthias On Tue, Apr 20, 2010 at 9:05 AM, Matthias Wessendorf mat...@apache.org wrote: On Mon, Apr 19, 2010 at 11:58 PM, Andrew Robinson andrew.rw.robin...@gmail.com wrote: The branch is ready and the issues that were brought up in this thread as well as other issues have been resolved. Unless there are any objections, I will merge the changes into the trunk tomorrow. fine here. Note that Max added a switch to be able to turn off PPR through JSF at the agent level so that mobile browsers that fail with the mojarra JavaScript can go back to the legacy code. not sure I understand: why is that switch mojarra specific ? Or are you just saying that it's a fallback to JSF2 ? -Matthias -Andrew On Wed, Apr 7, 2010 at 8:33 AM, Max Starets max.star...@oracle.com wrote: Just a few minor additions - - PartialViewContext.isAjaxRequest() will be returning true for the requests sent with jsf ajax as well as the legacy partialSubmit=true requests. - Trinidad's partial triggers will be honored for the jsf ajax requests. However, this will currently work only with execute=@all. Once we start adding trigger listeners during the PostRestoreView event processing, instead of decode, this limitation will go away. Max Andrew Robinson wrote: Well after a bit of work, the JSF2 AJAX branch is ready for testing to see if we want to merge it into the trunk. Branch: https://svn.apache.org/repos/asf/myfaces/trinidad/branches/jsf2_ajax.3 Details: - jsf.ajax.request used to submit PPR requests from the request queue - server serves JSF2 payload, differing if an IFRAME submission is detected for Trinidad to send down script libraries - iframe processing through legacy code, but updated to use a valid JSF2 payload - iframe still sends Tr-XHR-Message to let the server know its a legacy request - legacy request supports DOM replacement but none of the new functionality of JSF2 (attribute updates for example) - TrPage integrated with JSF2 events to correctly broadcast DOM change notifications and restore focus - If users find errors in the jsf.js libraries, setting the _useJsfBuiltInAjaxForXhr property of the request queue to false will bypass usage of jsf.ajax. We can add support for a public way of doing this later if necessary. - Server side integration with the JSF2 APIs and client behaviors, JSF2 submission working along side of partialSubmit=true and auto PPR. Thank you, Andrew -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [Trinidad 2] AJAX branch ready for testing
Hello Andrew, on my tryouts I used both, see here: http://markmail.org/message/onwsrqwfhu7ai67e -Matthias On Tue, Apr 20, 2010 at 5:00 PM, Andrew Robinson andrew.robin...@oracle.com wrote: Also, are you using JSF RI? MyFaces is known to be bad with Ajax. On 04/20/2010 08:50 AM, Max Starets wrote: Hey Matthias, This works for me: http://adc2100180.us.oracle.com:7101/trinidad-demo-context-root/faces/demos/pprDemos.jspx Are you seeing any errors? Is request showing up in Firebug console? Thanks, Max Matthias Wessendorf wrote: on the pprDemos.jspx stuff, there is a bunch of tests for PPR, one of the has the header Command components with partialSubmit, which does not work (in the trinidad demo) File (in SVN) is located there: https://svn.apache.org/repos/asf/myfaces/trinidad/branches/jsf2_ajax.3/trinidad-examples/trinidad-demo/src/main/webapp/demos/pprDemos.jspx On Tue, Apr 20, 2010 at 6:37 AM, Max Starets max.star...@oracle.com wrote: Matthias, What do you mean when you say 'command components with partialSubmit do not work'? Thanks, Max On Apr 20, 2010, at 3:26 AM, Matthias Wessendorf mat...@apache.org wrote: Checked Mojarra 2.0.1 and MyFaces 2.0.0 (out soon) - both have the NPE filed in TRINIDAD-1786 * Mojarra: -PPR on select* works (exception see above) - Command components with partialSubmit does _not_ work * MyFaces: - all PPR stuff does a full page-refresh I am fine in merging these bits to trunk, but before we acutally do a release, we should check what's going wrong in MyFaces/Trinidad ;-) (I think it must be an issue in MyFaces, so once I have some more time, I will file a bug against that, with a little better description) -Matthias On Tue, Apr 20, 2010 at 9:09 AM, Matthias Wessendorf mat...@apache.org wrote: Ok, looks like you are talking about JSF2's JS/Ajax stuff. The term mojarra is slightly confusing, since I understand it as a specific dependency to that particular implementation. But looks like we do not have that, for the ajax stuff, which is great. -Matthias On Tue, Apr 20, 2010 at 9:05 AM, Matthias Wessendorf mat...@apache.org wrote: On Mon, Apr 19, 2010 at 11:58 PM, Andrew Robinson andrew.rw.robin...@gmail.com wrote: The branch is ready and the issues that were brought up in this thread as well as other issues have been resolved. Unless there are any objections, I will merge the changes into the trunk tomorrow. fine here. Note that Max added a switch to be able to turn off PPR through JSF at the agent level so that mobile browsers that fail with the mojarra JavaScript can go back to the legacy code. not sure I understand: why is that switch mojarra specific ? Or are you just saying that it's a fallback to JSF2 ? -Matthias -Andrew On Wed, Apr 7, 2010 at 8:33 AM, Max Starets max.star...@oracle.com wrote: Just a few minor additions - - PartialViewContext.isAjaxRequest() will be returning true for the requests sent with jsf ajax as well as the legacy partialSubmit=true requests. - Trinidad's partial triggers will be honored for the jsf ajax requests. However, this will currently work only with execute=@all. Once we start adding trigger listeners during the PostRestoreView event processing, instead of decode, this limitation will go away. Max Andrew Robinson wrote: Well after a bit of work, the JSF2 AJAX branch is ready for testing to see if we want to merge it into the trunk. Branch: https://svn.apache.org/repos/asf/myfaces/trinidad/branches/jsf2_ajax.3 Details: - jsf.ajax.request used to submit PPR requests from the request queue - server serves JSF2 payload, differing if an IFRAME submission is detected for Trinidad to send down script libraries - iframe processing through legacy code, but updated to use a valid JSF2 payload - iframe still sends Tr-XHR-Message to let the server know its a legacy request - legacy request supports DOM replacement but none of the new functionality of JSF2 (attribute updates for example) - TrPage integrated with JSF2 events to correctly broadcast DOM change notifications and restore focus - If users find errors in the jsf.js libraries, setting the _useJsfBuiltInAjaxForXhr property of the request queue to false will bypass usage of jsf.ajax. We can add support for a public way of doing this later if necessary. - Server side integration with the JSF2 APIs and client behaviors, JSF2 submission working along side of partialSubmit=true and auto PPR. Thank you, Andrew -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http
Re: [Trinidad 2] AJAX branch ready for testing
implementation of both
implementations (better than the RI, so any bugreport is welcome). But no
offence taken, back to the topic.
But back to the original problem, the first link (Go to Trinidad demos home
page.) issue following xhr post:
Tr-PPR-Message true
_noJavaScript false
event autosub
itxt Change this text
j_id1078059021_4041e82d
javax.faces.ViewState !h19u5lcmm
javax.faces.ViewState !h19u5lcmm
javax.faces.partial.ajax true
javax.faces.partial.event click
javax.faces.partial.execu... null
javax.faces.source null
org.apache.myfaces.trinid... j_id1078059021_4041e08f
partial true
selOne 0
source j_id1078059021_4041e6c3
and the response is following:
?xml version=1.0 ?
partial-responsechangesupdate
id=tr_j_id1078059021_4041e08f_Postscript![CDATA[span
id=tr_j_id1078059021_4041e08f_Postscriptinput type=hidden
name=sourcescript
type=text/javascriptTrPage.getInstance()._addResetFields('j_id1078059021_4041e08f',[source]);/scriptscript
type=text/javascriptvar
j_id1078059021_4041e08f_SF={};/script/span]]/updateupdate
id=javax.faces.ViewState![CDATA[!h19u5lcmm]]/updateeval![CDATA[TrPage.getInstance().__handlePprResponseAction('/trinidad-demo/faces/demos/pprDemos.jspx');]]/eval/changes/partial-response
Not sure what the eval
TrPage.getInstance().__handlePprResponseAction('/trinidad-demo/faces/demos/pprDemos.jspx');
in this case triggers, it should trigger a go to the homepage.
Werner
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Re: [Trinidad 2] AJAX branch ready for testing
Hi Andrew, here is the ticket: https://issues.apache.org/jira/browse/MYFACES-2641 Looks like just a ticket for the _ajaxOldDomElements is missing, right ? http://markmail.org/message/tcoi36bneeultdx2 -Matthias On Tue, Apr 20, 2010 at 6:16 PM, Matthias Wessendorf mat...@apache.org wrote: Hello Andrew, the problem below is already fixed in the up-coming release, which I used to verify this. Let's merge your branch to trunk and work on it to get these other (minor) things fixed. On Tue, Apr 20, 2010 at 6:09 PM, Andrew Robinson andrew.rw.robin...@gmail.com wrote: Werner, sorry for the short reply on that email, the tone probably sounded bad. There are state saving problems when using MyFaces. Unfortunately it is bad enough to make it completely non-functional as all PPR post backs fail to restore the state from what I have seen. We have no such errors when using Mojarra. @Matthias or Max: did one of you guys already file a bug on the MyFaces Core for this or do we still need to? To reproduce: 1) Get a working copy of the jsf2_ajax.3 Trinidad Branch: https://svn.apache.org/repos/asf/myfaces/trinidad/branches/jsf2_ajax.3 2) Run the demo project using Jetty (mvn jetty:run -PjettyConfig) 3) Hit the page: http://localhost:8080/trinidad-demo/faces/demos/ajaxPPRDemos.xhtml 4) Click on one of the buttons at the top (Full Submit button is fine) This error results: SEVERE: An exception occurred javax.faces.application.ViewExpiredException: /demos/ajaxPPRDemos.xhtmlNo saved view state could be found for the view identifier: /demos/ajaxPPRDemos.xhtml at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:114) at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:138) at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:88) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:189) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157) at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:536) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:930) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) Form Data sent: itxt1:Change this text2 sf20%3Aitxt2:Change this text2 it1: org.apache.myfaces.trinidad.faces.FORM:j_id933005119_379c87b2 _noJavaScript:false javax.faces.ViewState:!yabr3gltb : javax.faces.behavior.event:action javax.faces.partial.event:click javax.faces.source:axBtn2 javax.faces.partial.ajax:true javax.faces.partial.execute:axBtn2 javax.faces.partial.render:btnTarget Request Headers: Content-Type:application/x-www-form-urlencoded Faces-Request:partial/ajax Origin:http://localhost:8080 Referer:http://localhost:8080/trinidad-demo/faces/demos/ajaxPPRDemos.xhtml User-Agent:Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/533.2 (KHTML, like Gecko) Chrome/5.0.342.9 Safari/533.2 On Tue, Apr 20, 2010 at 9:37 AM, Werner Punz werner.p...@gmail.com wrote: Am 20.04.10 17:00, schrieb Andrew Robinson: Also, are you using JSF RI? MyFaces is known to be bad with Ajax. Ouch that hit me personally, because I and others spent a load of hours to make the our javascripts as good as possible as the spec allowed (with the help
Re: [Trinidad 2] Announcement: JSF 2 ajax support has been added to the trunk
great news! -Matthias On Tue, Apr 20, 2010 at 9:33 PM, Andrew Robinson arobinso...@apache.org wrote: As of SVN revision 936035, the Trinidad trunk now supports the built in AJAX of JSF2. Details: - Requests through f:ajax supported with Trinidad components - jsf.ajax.request used to submit PPR requests from the Trinidad request queue - Server delivers JSF2 payload, with special handling for Trinidad IFRAME requests to send down script libraries - IFrame processing still possible by bypassing the jsf.ajax code which has yet to be made compatible with file uploads in either Mojarra or MyFaces - Note that there is a limitation that iframe processing only supports the legacy PPR of Trinidad (replacement only, no support for the new insert, delete, attribute change functionality of the JSF2 partial response writer) - Trinidad still supports broadcasting of DOM changes and restores focus by leveraging JSF AJAX events - Agent specific flag to disable AJAX through jsf.ajax to handle use cases where mobile platforms do not function using the Mojarra or MyFaces JavaScript - Integration on the server between JSF 2 rendered IDs and Trinidad partial triggers - Partial submit and client behavior support - Trinidad's partial triggers will be honored for the jsf ajax requests. - However, this will currently work only with execute=@all or if the execute attribute is pointed to each component that is listed as a partial trigger. - Once we start adding trigger listeners during the PostRestoreView event processing, instead of decode, this limitation will go away. We welcome your assistance to test your applications on the current Trunk and report your findings and file issues when found. Thank you, Andrew -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [Trinidad 2] Announcement: JSF 2 ajax support has been added to the trunk
great news! -Matthias On Tue, Apr 20, 2010 at 9:33 PM, Andrew Robinson arobinso...@apache.org wrote: As of SVN revision 936035, the Trinidad trunk now supports the built in AJAX of JSF2. Details: - Requests through f:ajax supported with Trinidad components - jsf.ajax.request used to submit PPR requests from the Trinidad request queue - Server delivers JSF2 payload, with special handling for Trinidad IFRAME requests to send down script libraries - IFrame processing still possible by bypassing the jsf.ajax code which has yet to be made compatible with file uploads in either Mojarra or MyFaces - Note that there is a limitation that iframe processing only supports the legacy PPR of Trinidad (replacement only, no support for the new insert, delete, attribute change functionality of the JSF2 partial response writer) - Trinidad still supports broadcasting of DOM changes and restores focus by leveraging JSF AJAX events - Agent specific flag to disable AJAX through jsf.ajax to handle use cases where mobile platforms do not function using the Mojarra or MyFaces JavaScript - Integration on the server between JSF 2 rendered IDs and Trinidad partial triggers - Partial submit and client behavior support - Trinidad's partial triggers will be honored for the jsf ajax requests. - However, this will currently work only with execute=@all or if the execute attribute is pointed to each component that is listed as a partial trigger. - Once we start adding trigger listeners during the PostRestoreView event processing, instead of decode, this limitation will go away. We welcome your assistance to test your applications on the current Trunk and report your findings and file issues when found. Thank you, Andrew -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] Release Tobago 1.0.25
+1 Sent from my iPod. On 18.04.2010, at 16:34, Werner Punz werner.p...@gmail.com wrote: +1 Am 18.04.10 12:22, schrieb Bernd Bohmann: Hello, I would like to release Tobago 1.0.25. For a detail list please consult the release notes: http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273styleName=Htmlversion=12314527 The version is available at the staging location and the revision number of the release is 935243 and tagged as tobago-1.0.25. Staging distribution: http://people.apache.org/~bommel/repo Staging repository: http://people.apache.org/~bommel/repo The Vote is open for 72h. [ ] +1 [ ] +0 [ ] -1
Re: [VOTE] release of myfaces core 2.0.0
+1 On Fri, Apr 16, 2010 at 5:46 AM, Leonardo Uribe lu4...@gmail.com wrote: +1 2010/4/15 Leonardo Uribe lu4...@gmail.com Hi, I was running the needed tasks to get the 2.0.0 release of Apache MyFaces core out. Minor fixes were done since the latest proposed artifacts (MYFACES-2661 and fix bin assembly remove myfaces-core-assembly artifact), so we can continue with the vote. The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.1 [1] 2. Maven artifact group org.apache.myfaces.core v2.0.0 [1] 3. Maven artifact group org.apache.myfaces.test v1.0.0-beta-3 [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.0 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] http://people.apache.org/~lu4242/myfaces200 [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces200binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: Ext Scripting Quo Vadis
I am fine with doing a _real_ release here -M On Thu, Apr 15, 2010 at 9:37 PM, Werner Punz werner.p...@gmail.com wrote: Hello I just wanted to know a general opinion here, Ext-Scripting has been in beta stage for a while (while we have tagged one none of us had time to make a full blown release given all our other tasks at hand) But I personally think, since the thing at least for me already works really well (used it again this week for prototyping some JSF2 components at a customer) and I did a lot of bugfixing, that I do not want to do another beta release but want to go for a full blown final release with a bugfix release shortly thereafter. The reason is: a) I personally think it is ready, I want to do some additional testing and fixing as time permits next week, as time permits, but I think it is ok to release it b) I want people start using it, which means they will touch it with a final release c) It would be good to get the release out very close to myfaces sort of as a pushing extra for MyFaces 2.0 (my original timeframe was one month after the myfaces release, it could be shorter now) d) I want to start the work on 1.1 so that we get the infrastructure in place to get spring an and have Bernhard starting on his GSOC project which will bring CDI integration, but that means some refactorings which I cannot do as long as I am in beta here (and I do not want to branch again( I personally think that 1.0 is more or less a proof of concept and foundation, and a valuable asset for component writers (thats probably where 1.0 will be used most), once we have Spring and CDI working people really have something on their hands they can work with. So what is the general opinion on this? Werner -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: Unit test failing? (was: Re: [VOTE] release for myfaces core 2.0.0)
These two revisions cause the problem: http://svn.apache.org/viewvc?view=revisionrevision=933814 http://svn.apache.org/viewvc?view=revisionrevision=933812 On Thu, Apr 15, 2010 at 7:43 AM, Matthias Wessendorf mat...@apache.org wrote: Yesterday I mentioned the same, on trunk I am on Linux, Werner is on OS X. Jakob/Leo: r u windoze ? Thx, Matthias PS: I changed the subject to not hijack the vote ;-) On Thu, Apr 15, 2010 at 7:37 AM, Werner Punz werner.p...@gmail.com wrote: Before I am giving my vote here, there is still a unit test failure ... Am 15.04.10 06:39, schrieb Matthias Wessendorf: +1 Thanks for running this Sent from my iPod. On 15.04.2010, at 03:48, Leonardo Uribe lu4...@gmail.com mailto:lu4...@gmail.com wrote: +1 2010/4/14 Leonardo Uribe mailto:lu4...@gmail.comlu4...@gmail.com mailto:lu4...@gmail.com Hi, I was running the needed tasks to get the 2.0.0 release of Apache MyFaces core out. Minor fixes were done since the latest proposed artifacts (MYFACES-2658, MYFACES-2659 and MYFACES-2660), so we can continue with the vote. The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.1 [1] 2. Maven artifact group org.apache.myfaces.core v2.0.0 [1] 3. Maven artifact group org.apache.myfaces.test v1.0.0-beta-3 [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.0 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] http://people.apache.org/%7Elu4242/myfaces200http://people.apache.org/~lu4242/myfaces200 [2] http://www.apache.org/foundation/voting.html#ReleaseVoteshttp://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/%7Elu4242/myfaces200binsrchttp://people.apache.org/~lu4242/myfaces200binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: Unit test failing? (was: Re: [VOTE] release for myfaces core 2.0.0)
that's funny :-) What JDK ? 1.5 ? I am on 1.6.x = mat...@woody:~/work/source/Apache/myfaces/trunk$ mvn -v Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_13 Java home: /java/jdk1.6.0_13/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux version: 2.6.31-19-generic arch: i386 Family: unix On Thu, Apr 15, 2010 at 8:55 AM, Leonardo Uribe lu4...@gmail.com wrote: Hi In my machine works fine. I compiled sources on both Linux and Windows. regards, Leonardo Uribe 2010/4/15 Matthias Wessendorf mat...@apache.org These two revisions cause the problem: http://svn.apache.org/viewvc?view=revisionrevision=933814 http://svn.apache.org/viewvc?view=revisionrevision=933812 On Thu, Apr 15, 2010 at 7:43 AM, Matthias Wessendorf mat...@apache.org wrote: Yesterday I mentioned the same, on trunk I am on Linux, Werner is on OS X. Jakob/Leo: r u windoze ? Thx, Matthias PS: I changed the subject to not hijack the vote ;-) On Thu, Apr 15, 2010 at 7:37 AM, Werner Punz werner.p...@gmail.com wrote: Before I am giving my vote here, there is still a unit test failure ... Am 15.04.10 06:39, schrieb Matthias Wessendorf: +1 Thanks for running this Sent from my iPod. On 15.04.2010, at 03:48, Leonardo Uribe lu4...@gmail.com mailto:lu4...@gmail.com wrote: +1 2010/4/14 Leonardo Uribe mailto:lu4...@gmail.comlu4...@gmail.com mailto:lu4...@gmail.com Hi, I was running the needed tasks to get the 2.0.0 release of Apache MyFaces core out. Minor fixes were done since the latest proposed artifacts (MYFACES-2658, MYFACES-2659 and MYFACES-2660), so we can continue with the vote. The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.1 [1] 2. Maven artifact group org.apache.myfaces.core v2.0.0 [1] 3. Maven artifact group org.apache.myfaces.test v1.0.0-beta-3 [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.0 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] http://people.apache.org/%7Elu4242/myfaces200http://people.apache.org/~lu4242/myfaces200 [2] http://www.apache.org/foundation/voting.html#ReleaseVoteshttp://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/%7Elu4242/myfaces200binsrchttp://people.apache.org/~lu4242/myfaces200binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: svn commit: r934048 - in /myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp: FaceletsOnlyException.java JspViewDeclarationLanguage.java
with a delay of 13 hours, it made it.
Some gave approval, I guess (it may ended up in the moderation queue)
-M
On Wed, Apr 14, 2010 at 8:09 PM, Jakob Korherr jak...@apache.org wrote:
No I cannot, because then its message won't be displayed by the
ExceptionHandler, because the ExceptionHandler extracts the Exception
until it finds the first non-FacesException and then it handles this one.
Thus if I would make it a FacesException, the message will be lost. This was
the reason I created FaceletsOnlyException in the first place...
Regards,
Jakob
2010/4/14 Matthias Wessendorf mat...@apache.org
public class FaceletsOnlyException extends Exception
== can you make that extending FacesException ?
-Matthias
On Wed, Apr 14, 2010 at 7:48 PM, jak...@apache.org wrote:
Author: jakobk
Date: Wed Apr 14 17:48:28 2010
New Revision: 934048
URL: http://svn.apache.org/viewvc?rev=934048view=rev
Log:
MYFACES-2658 Indicate a better error when using Facelet TAGs on JSP(X)
pages
Added:
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java
(with props)
Modified:
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/JspViewDeclarationLanguage.java
(contents, props changed)
Added:
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java
URL:
http://svn.apache.org/viewvc/myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java?rev=934048view=auto
==
---
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java
(added)
+++
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java
Wed Apr 14 17:48:28 2010
@@ -0,0 +1,40 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * License); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+package org.apache.myfaces.view.jsp;
+
+/**
+ * An Exception that indicates that the user uses a
+ * facelets-only feature on a JSP.
+ *
+ * @author Jakob Korherr (latest modification by $Author$)
+ * @version $Revision$ $Date$
+ *
+ * @since 2.0
+ */
+public class FaceletsOnlyException extends Exception
+{
+
+ private static final long serialVersionUID = 4268633427284543647L;
+
+ public FaceletsOnlyException(String message, Throwable cause)
+ {
+ super(message, cause);
+ }
+
+}
Propchange:
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java
--
svn:eol-style = native
Propchange:
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java
--
svn:keywords = Date Author Id Revision HeadURL
Propchange:
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java
--
svn:mime-type = text/plain
Modified:
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/JspViewDeclarationLanguage.java
URL:
http://svn.apache.org/viewvc/myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/JspViewDeclarationLanguage.java?rev=934048r1=934047r2=934048view=diff
==
---
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/JspViewDeclarationLanguage.java
(original)
+++
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/JspViewDeclarationLanguage.java
Wed Apr 14 17:48:28 2010
@@ -1,139 +1,222 @@
-/*
- * Licensed to the Apache Software Foundation (ASF) under one
- * or more contributor license agreements. See the NOTICE file
- * distributed with this work for additional information
- * regarding copyright ownership. The ASF licenses this file
- * to you under the Apache License, Version 2.0 (the
- * License); you may not use this file except
Re: Unit test failing? (was: Re: [VOTE] release for myfaces core 2.0.0)
Hey Jan, these two new methods: http://svn.apache.org/viewvc?view=revisionrevision=933814 http://svn.apache.org/viewvc?view=revisionrevision=933812 On Thu, Apr 15, 2010 at 9:22 AM, Jan-Kees van Andel jankeesvanan...@gmail.com wrote: I just runned the build on Windows Vista x64: D:\dev\work\myfaces2\core_2_0_0mvn --version Maven version: 2.0.10 Java version: 1.6.0_14 OS name: windows vista version: 6.0 arch: amd64 Family: windows The tests worked fine. @Matthias: Can you see which test method is causing the issue and which assertion fails (or which exception is thrown)? /JK 2010/4/15 Matthias Wessendorf mat...@apache.org that's funny :-) What JDK ? 1.5 ? I am on 1.6.x = mat...@woody:~/work/source/Apache/myfaces/trunk$ mvn -v Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_13 Java home: /java/jdk1.6.0_13/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux version: 2.6.31-19-generic arch: i386 Family: unix On Thu, Apr 15, 2010 at 8:55 AM, Leonardo Uribe lu4...@gmail.com wrote: Hi In my machine works fine. I compiled sources on both Linux and Windows. regards, Leonardo Uribe 2010/4/15 Matthias Wessendorf mat...@apache.org These two revisions cause the problem: http://svn.apache.org/viewvc?view=revisionrevision=933814 http://svn.apache.org/viewvc?view=revisionrevision=933812 On Thu, Apr 15, 2010 at 7:43 AM, Matthias Wessendorf mat...@apache.org wrote: Yesterday I mentioned the same, on trunk I am on Linux, Werner is on OS X. Jakob/Leo: r u windoze ? Thx, Matthias PS: I changed the subject to not hijack the vote ;-) On Thu, Apr 15, 2010 at 7:37 AM, Werner Punz werner.p...@gmail.com wrote: Before I am giving my vote here, there is still a unit test failure ... Am 15.04.10 06:39, schrieb Matthias Wessendorf: +1 Thanks for running this Sent from my iPod. On 15.04.2010, at 03:48, Leonardo Uribe lu4...@gmail.com mailto:lu4...@gmail.com wrote: +1 2010/4/14 Leonardo Uribe mailto:lu4...@gmail.comlu4...@gmail.com mailto:lu4...@gmail.com Hi, I was running the needed tasks to get the 2.0.0 release of Apache MyFaces core out. Minor fixes were done since the latest proposed artifacts (MYFACES-2658, MYFACES-2659 and MYFACES-2660), so we can continue with the vote. The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.1 [1] 2. Maven artifact group org.apache.myfaces.core v2.0.0 [1] 3. Maven artifact group org.apache.myfaces.test v1.0.0-beta-3 [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.0 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] http://people.apache.org/%7Elu4242/myfaces200http://people.apache.org/~lu4242/myfaces200 [2] http://www.apache.org/foundation/voting.html#ReleaseVoteshttp://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/%7Elu4242/myfaces200binsrchttp://people.apache.org/~lu4242/myfaces200binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: impl build fails - Re: [VOTE] release for myfaces core 2.0.0
Leo pointed out some other dependencies, you need to build them too... On Thu, Apr 15, 2010 at 10:24 AM, Ganesh gan...@j4fry.org wrote: Sorry for the inconvenience, for me impl build fails on myfaces/current20 (last tried 10 days ago, worked then). It's propably an oversight on my side, but I would have liked to a quick retest with dojofaces for 2.0.0 ... any ideas? [INFO] Compiling 74 source files to C:\projects\MyFaces_current20\core\impl\target\classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure C:\projects\MyFaces_current20\core\impl\src\main\java\org\apache\myfaces\context\servlet\ServletExternalContextImpl.java:[56,51] package org.apache.myfaces.shared_impl.context.flash does not exist C:\projects\MyFaces_current20\core\impl\src\main\java\org\apache\myfaces\context\ExceptionHandlerFactoryImpl.java:[24,45] cannot find symbol symbol : class ExceptionHandlerImpl location: package org.apache.myfaces.shared_impl.context C:\projects\MyFaces_current20\core\impl\src\main\java\org\apache\myfaces\view\facelets\compiler\TagLibraryConfig.java:[616,65] cannot find symbol symbol : method isValidateXML() location: class org.apache.myfaces.shared_impl.config.MyfacesConfig C:\projects\MyFaces_current20\core\impl\src\main\java\org\apache\myfaces\view\facelets\compiler\TagLibraryConfig.java:[684,61] cannot find symbol symbol : method isValidateXML() location: class org.apache.myfaces.shared_impl.config.MyfacesConfig C:\projects\MyFaces_current20\core\impl\src\main\java\org\apache\myfaces\context\servlet\ServletExternalContextImpl.java:[921,15] cannot find symbol symbol : variable FlashImpl location: class org.apache.myfaces.context.servlet.ServletExternalContextImpl C:\projects\MyFaces_current20\core\impl\src\main\java\org\apache\myfaces\config\FacesConfigurator.java:[543,62] cannot find symbol symbol : method isValidateXML() location: class org.apache.myfaces.shared_impl.config.MyfacesConfig C:\projects\MyFaces_current20\core\impl\src\main\java\org\apache\myfaces\config\FacesConfigurator.java:[772,70] cannot find symbol symbol : method isValidateXML() location: class org.apache.myfaces.shared_impl.config.MyfacesConfig C:\projects\MyFaces_current20\core\impl\src\main\java\org\apache\myfaces\config\FacesConfigurator.java:[806,66] cannot find symbol symbol : method isValidateXML() location: class org.apache.myfaces.shared_impl.config.MyfacesConfig C:\projects\MyFaces_current20\core\impl\src\main\java\org\apache\myfaces\config\FacesConfigurator.java:[864,62] cannot find symbol symbol : method isValidateXML() location: class org.apache.myfaces.shared_impl.config.MyfacesConfig C:\projects\MyFaces_current20\core\impl\src\main\java\org\apache\myfaces\view\facelets\compiler\EndElementInstruction.java:[47,33] cannot find symbol symbol : method renderUnhandledFacesMessages(javax.faces.context.FacesContext) location: class org.apache.myfaces.shared_impl.renderkit.html.HtmlRendererUtils [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 minute 12 seconds [INFO] Finished at: Thu Apr 15 10:14:54 CEST 2010 [INFO] Final Memory: 105M/452M [INFO] Best regards, Ganesh Werner Punz schrieb: Before I am giving my vote here, there is still a unit test failure ... Am 15.04.10 06:39, schrieb Matthias Wessendorf: +1 Thanks for running this Sent from my iPod. On 15.04.2010, at 03:48, Leonardo Uribe lu4...@gmail.com mailto:lu4...@gmail.com wrote: +1 2010/4/14 Leonardo Uribe mailto:lu4...@gmail.comlu4...@gmail.com mailto:lu4...@gmail.com Hi, I was running the needed tasks to get the 2.0.0 release of Apache MyFaces core out. Minor fixes were done since the latest proposed artifacts (MYFACES-2658, MYFACES-2659 and MYFACES-2660), so we can continue with the vote. The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.1 [1] 2. Maven artifact group org.apache.myfaces.core v2.0.0 [1] 3. Maven artifact group org.apache.myfaces.test v1.0.0-beta-3 [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.0 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3
Re: [VOTE] release for myfaces core 2.0.0
can you post the archived links, so that folks aren't confused ? Thx, Matthias On Thu, Apr 15, 2010 at 11:20 AM, Jan-Kees van Andel jankeesvanan...@gmail.com wrote: With the issue resolved (the release version is ok AFAICS), I withdraw my -1 and re-vote with a +1. /JK 2010/4/15 Jakob Korherr jakob.korh...@gmail.com Again: it works on my machine.. And I guess you may have forgotten to rebuild shared too, because the test tests results of changes on shared. But until this is really sorted out, my vote also is -1. Regards, Jakob 2010/4/15, Werner Punz werner.p...@gmail.com: Ok here it goes officially -1 until we have resolved the issue upon looking at the test, the test is ok and tests correctly, the code causing the test fail is at fault. That should not happen for a release. As I have posted in another mail I currently have to serve a customer if no one else is able to fix it in between I will have a look late in the afternoon. Werner Am 15.04.10 07:37, schrieb Werner Punz: Before I am giving my vote here, there is still a unit test failure ... Am 15.04.10 06:39, schrieb Matthias Wessendorf: +1 Thanks for running this Sent from my iPod. On 15.04.2010, at 03:48, Leonardo Uribe lu4...@gmail.com mailto:lu4...@gmail.com wrote: +1 2010/4/14 Leonardo Uribe mailto:lu4...@gmail.comlu4...@gmail.com mailto:lu4...@gmail.com Hi, I was running the needed tasks to get the 2.0.0 release of Apache MyFaces core out. Minor fixes were done since the latest proposed artifacts (MYFACES-2658, MYFACES-2659 and MYFACES-2660), so we can continue with the vote. The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.1 [1] 2. Maven artifact group org.apache.myfaces.core v2.0.0 [1] 3. Maven artifact group org.apache.myfaces.test v1.0.0-beta-3 [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.0 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] http://people.apache.org/%7Elu4242/myfaces200http://people.apache.org/~lu4242/myfaces200 [2] http://www.apache.org/foundation/voting.html#ReleaseVoteshttp://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/%7Elu4242/myfaces200binsrchttp://people.apache.org/~lu4242/myfaces200binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890 -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: impl build fails - Re: [VOTE] release for myfaces core 2.0.0
\org\apache\myfaces\config\FacesConfigurator.java:[806,66] cannot find symbol symbol : method isValidateXML() location: class org.apache.myfaces.shared_impl.config.MyfacesConfig C:\projects\MyFaces_current20\core\impl\src\main\java\org\apache\myfaces\config\FacesConfigurator.java:[864,62] cannot find symbol symbol : method isValidateXML() location: class org.apache.myfaces.shared_impl.config.MyfacesConfig C:\projects\MyFaces_current20\core\impl\src\main\java\org\apache\myfaces\view\facelets\compiler\EndElementInstruction.java:[47,33] cannot find symbol symbol : method renderUnhandledFacesMessages(javax.faces.context.FacesContext) location: class org.apache.myfaces.shared_impl.renderkit.html.HtmlRendererUtils [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 minute 12 seconds [INFO] Finished at: Thu Apr 15 10:14:54 CEST 2010 [INFO] Final Memory: 105M/452M [INFO] Best regards, Ganesh Werner Punz schrieb: Before I am giving my vote here, there is still a unit test failure ... Am 15.04.10 06:39, schrieb Matthias Wessendorf: +1 Thanks for running this Sent from my iPod. On 15.04.2010, at 03:48, Leonardo Uribe lu4...@gmail.commailto:lu4...@gmail.com mailto:lu4...@gmail.commailto:lu4...@gmail.com wrote: +1 2010/4/14 Leonardo Uribe mailto:lu4...@gmail.com mailto:lu4...@gmail.comlu4...@gmail.com mailto:lu4...@gmail.com mailto:lu4...@gmail.commailto:lu4...@gmail.com Hi, I was running the needed tasks to get the 2.0.0 release of Apache MyFaces core out. Minor fixes were done since the latest proposed artifacts (MYFACES-2658, MYFACES-2659 and MYFACES-2660), so we can continue with the vote. The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.1 [1] 2. Maven artifact group org.apache.myfaces.core v2.0.0 [1] 3. Maven artifact group org.apache.myfaces.test v1.0.0-beta-3 [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.0 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] http://people.apache.org/%7Elu4242/myfaces200http://people.apache.org/~lu4242/myfaces200 http://people.apache.org/%7Elu4242/myfaces200 [2] http://www.apache.org/foundation/voting.html#ReleaseVoteshttp://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/%7Elu4242/myfaces200binsrchttp://people.apache.org/~lu4242/myfaces200binsrc http://people.apache.org/%7Elu4242/myfaces200binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890 -- There are two kinds of people in the world, those who believe there are two kinds of people and those who don't. — Robert Benchley -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at -- There are two kinds of people in the world, those who believe there are two kinds of people and those who don't. — Robert Benchley -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] release for myfaces core 2.0.0
+1 On Wed, Apr 14, 2010 at 9:05 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: +1 regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/4/14 Leonardo Uribe lu4...@gmail.com +1 2010/4/14 Leonardo Uribe lu4...@gmail.com Hi, I was running the needed tasks to get the 2.0.0 release of Apache MyFaces core out. The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.1 [1] 2. Maven artifact group org.apache.myfaces.core v2.0.0 [1] 3. Maven artifact group org.apache.myfaces.test v1.0.0-beta-3 [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.0 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] http://people.apache.org/~lu4242/myfaces200 [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces200binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[MyFaces 2] Version 2.0.0 does not work as well (was: Re: [Trinidad 2] AJAX branch ready for testing)
Hi, when I (using the 2.0.0) navigate to this page http://localhost:8080/trinidad-demo/faces/demos/pprDemos.jspx I get a full page reload on every click. = works with Mojarra. -Matthias On Fri, Apr 9, 2010 at 2:55 PM, Matthias Wessendorf mat...@apache.org wrote: https://issues.apache.org/jira/browse/MYFACES-2654 On Fri, Apr 9, 2010 at 2:52 PM, Matthias Wessendorf mat...@apache.org wrote: I now checked this page: http://localhost:8080/trinidad-demo/faces/demos/pprDemos.jspx MYFACES_SNAPSHOT: = on any ajax action/click, I get these two alert() boxes: * TypeError: this._ajaxOldDomElements is null * malformedXML-- == I will file a bug against MyFaces JSF RI (2.0.2): == fine On Fri, Apr 9, 2010 at 2:48 PM, Matthias Wessendorf mat...@apache.org wrote: hi, I gave it a quick try. Here are my results: Page: http://localhost:8080/trinidad-demo/faces/demos/clientBehaviorHolder.xhtml JSF_RI (Mojarra 2.0.2 (SNAPSHOT 20091204)) results: I entered some text and clicked submit via JSF Ajax Got this (in an alert JS box): httpError: The Http Transport returned a 0 status code. This is usually the result of mixing ajax and full requests. This is usually undesired, for both performance and data integrity reasons. second click on the same button I got this JS error. mojarra is not defined [Break on this error] var func = new Function(event, handler); === the submit button works. MyFaces 2.0.0-SNAPHOT results: (using snapshot since the ViewExpiredException is gone in latest snapshot ) * submit button gives me this ALERT() box: TypeError: this._ajaxOldDomElements is null followed by this: malformedXML-- * Submit via JSF Ajax: I get this alert() BOX: httpError-httpError-Request failed Are there any other pages where I can test the new functionality ? -Matthias On Wed, Apr 7, 2010 at 4:33 PM, Max Starets max.star...@oracle.com wrote: Just a few minor additions - - PartialViewContext.isAjaxRequest() will be returning true for the requests sent with jsf ajax as well as the legacy partialSubmit=true requests. - Trinidad's partial triggers will be honored for the jsf ajax requests. However, this will currently work only with execute=@all. Once we start adding trigger listeners during the PostRestoreView event processing, instead of decode, this limitation will go away. Max Andrew Robinson wrote: Well after a bit of work, the JSF2 AJAX branch is ready for testing to see if we want to merge it into the trunk. Branch: https://svn.apache.org/repos/asf/myfaces/trinidad/branches/jsf2_ajax.3 Details: - jsf.ajax.request used to submit PPR requests from the request queue - server serves JSF2 payload, differing if an IFRAME submission is detected for Trinidad to send down script libraries - iframe processing through legacy code, but updated to use a valid JSF2 payload - iframe still sends Tr-XHR-Message to let the server know its a legacy request - legacy request supports DOM replacement but none of the new functionality of JSF2 (attribute updates for example) - TrPage integrated with JSF2 events to correctly broadcast DOM change notifications and restore focus - If users find errors in the jsf.js libraries, setting the _useJsfBuiltInAjaxForXhr property of the request queue to false will bypass usage of jsf.ajax. We can add support for a public way of doing this later if necessary. - Server side integration with the JSF2 APIs and client behaviors, JSF2 submission working along side of partialSubmit=true and auto PPR. Thank you, Andrew -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] release for myfaces core 2.0.0
Any chance we can get this into the 2.0.0 release ? https://issues.apache.org/jira/browse/MYFACES-2659 On Wed, Apr 14, 2010 at 4:52 PM, Jakob Korherr jakob.korh...@gmail.com wrote: +1 Regards, Jakob 2010/4/14 Michael Concini mconc...@gmail.com +1 On 4/14/2010 8:29 AM, Bernd Bohmann wrote: +1 Regards Bernd On Wed, Apr 14, 2010 at 11:42 AM, Martin Marinschek martin.marinsc...@gmail.com wrote: +1, great, great. best regards, Martin On Wed, Apr 14, 2010 at 11:31 AM, Bruno Arandabrunoara...@gmail.com wrote: +1 Great news! Thanks! Bruno On 14 April 2010 08:35, Matthias Wessendorfmat...@apache.org wrote: +1 On Wed, Apr 14, 2010 at 9:05 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: +1 regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/4/14 Leonardo Uribelu4...@gmail.com +1 2010/4/14 Leonardo Uribelu4...@gmail.com Hi, I was running the needed tasks to get the 2.0.0 release of Apache MyFaces core out. The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.1 [1] 2. Maven artifact group org.apache.myfaces.core v2.0.0 [1] 3. Maven artifact group org.apache.myfaces.test v1.0.0-beta-3 [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.0 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] http://people.apache.org/~lu4242/myfaces200 [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces200binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] release for myfaces core 2.0.0
Actually I tend to re-vote -1 (b/c of MYFACES-2659)... (not a vote though, just a thought) What do you guys think? BTW. the trunk has some other problems, a test-case fails... On Wed, Apr 14, 2010 at 5:10 PM, Matthias Wessendorf mat...@apache.org wrote: Any chance we can get this into the 2.0.0 release ? https://issues.apache.org/jira/browse/MYFACES-2659 On Wed, Apr 14, 2010 at 4:52 PM, Jakob Korherr jakob.korh...@gmail.com wrote: +1 Regards, Jakob 2010/4/14 Michael Concini mconc...@gmail.com +1 On 4/14/2010 8:29 AM, Bernd Bohmann wrote: +1 Regards Bernd On Wed, Apr 14, 2010 at 11:42 AM, Martin Marinschek martin.marinsc...@gmail.com wrote: +1, great, great. best regards, Martin On Wed, Apr 14, 2010 at 11:31 AM, Bruno Arandabrunoara...@gmail.com wrote: +1 Great news! Thanks! Bruno On 14 April 2010 08:35, Matthias Wessendorfmat...@apache.org wrote: +1 On Wed, Apr 14, 2010 at 9:05 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: +1 regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/4/14 Leonardo Uribelu4...@gmail.com +1 2010/4/14 Leonardo Uribelu4...@gmail.com Hi, I was running the needed tasks to get the 2.0.0 release of Apache MyFaces core out. The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.1 [1] 2. Maven artifact group org.apache.myfaces.core v2.0.0 [1] 3. Maven artifact group org.apache.myfaces.test v1.0.0-beta-3 [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.0 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] http://people.apache.org/~lu4242/myfaces200 [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces200binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [MyFaces 2] Version 2.0.0 does not work as well (was: Re: [Trinidad 2] AJAX branch ready for testing)
damn cache :-) I closed the issue On Wed, Apr 14, 2010 at 3:26 PM, Matthias Wessendorf mat...@apache.org wrote: Hi, when I (using the 2.0.0) navigate to this page http://localhost:8080/trinidad-demo/faces/demos/pprDemos.jspx I get a full page reload on every click. = works with Mojarra. -Matthias On Fri, Apr 9, 2010 at 2:55 PM, Matthias Wessendorf mat...@apache.org wrote: https://issues.apache.org/jira/browse/MYFACES-2654 On Fri, Apr 9, 2010 at 2:52 PM, Matthias Wessendorf mat...@apache.org wrote: I now checked this page: http://localhost:8080/trinidad-demo/faces/demos/pprDemos.jspx MYFACES_SNAPSHOT: = on any ajax action/click, I get these two alert() boxes: * TypeError: this._ajaxOldDomElements is null * malformedXML-- == I will file a bug against MyFaces JSF RI (2.0.2): == fine On Fri, Apr 9, 2010 at 2:48 PM, Matthias Wessendorf mat...@apache.org wrote: hi, I gave it a quick try. Here are my results: Page: http://localhost:8080/trinidad-demo/faces/demos/clientBehaviorHolder.xhtml JSF_RI (Mojarra 2.0.2 (SNAPSHOT 20091204)) results: I entered some text and clicked submit via JSF Ajax Got this (in an alert JS box): httpError: The Http Transport returned a 0 status code. This is usually the result of mixing ajax and full requests. This is usually undesired, for both performance and data integrity reasons. second click on the same button I got this JS error. mojarra is not defined [Break on this error] var func = new Function(event, handler); === the submit button works. MyFaces 2.0.0-SNAPHOT results: (using snapshot since the ViewExpiredException is gone in latest snapshot ) * submit button gives me this ALERT() box: TypeError: this._ajaxOldDomElements is null followed by this: malformedXML-- * Submit via JSF Ajax: I get this alert() BOX: httpError-httpError-Request failed Are there any other pages where I can test the new functionality ? -Matthias On Wed, Apr 7, 2010 at 4:33 PM, Max Starets max.star...@oracle.com wrote: Just a few minor additions - - PartialViewContext.isAjaxRequest() will be returning true for the requests sent with jsf ajax as well as the legacy partialSubmit=true requests. - Trinidad's partial triggers will be honored for the jsf ajax requests. However, this will currently work only with execute=@all. Once we start adding trigger listeners during the PostRestoreView event processing, instead of decode, this limitation will go away. Max Andrew Robinson wrote: Well after a bit of work, the JSF2 AJAX branch is ready for testing to see if we want to merge it into the trunk. Branch: https://svn.apache.org/repos/asf/myfaces/trinidad/branches/jsf2_ajax.3 Details: - jsf.ajax.request used to submit PPR requests from the request queue - server serves JSF2 payload, differing if an IFRAME submission is detected for Trinidad to send down script libraries - iframe processing through legacy code, but updated to use a valid JSF2 payload - iframe still sends Tr-XHR-Message to let the server know its a legacy request - legacy request supports DOM replacement but none of the new functionality of JSF2 (attribute updates for example) - TrPage integrated with JSF2 events to correctly broadcast DOM change notifications and restore focus - If users find errors in the jsf.js libraries, setting the _useJsfBuiltInAjaxForXhr property of the request queue to false will bypass usage of jsf.ajax. We can add support for a public way of doing this later if necessary. - Server side integration with the JSF2 APIs and client behaviors, JSF2 submission working along side of partialSubmit=true and auto PPR. Thank you, Andrew -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] release for myfaces core 2.0.0
Hey Leo, awesome! Patch is attached and already committed to trunk -Matthias On Wed, Apr 14, 2010 at 5:37 PM, Leonardo Uribe lu4...@gmail.com wrote: Hi Matthias Yes, I think we can include it. Just attach a patch and I'll generate all artifacts. regards, Leonardo Uribe 2010/4/14 Matthias Wessendorf mat...@apache.org Actually I tend to re-vote -1 (b/c of MYFACES-2659)... (not a vote though, just a thought) What do you guys think? BTW. the trunk has some other problems, a test-case fails... On Wed, Apr 14, 2010 at 5:10 PM, Matthias Wessendorf mat...@apache.org wrote: Any chance we can get this into the 2.0.0 release ? https://issues.apache.org/jira/browse/MYFACES-2659 On Wed, Apr 14, 2010 at 4:52 PM, Jakob Korherr jakob.korh...@gmail.com wrote: +1 Regards, Jakob 2010/4/14 Michael Concini mconc...@gmail.com +1 On 4/14/2010 8:29 AM, Bernd Bohmann wrote: +1 Regards Bernd On Wed, Apr 14, 2010 at 11:42 AM, Martin Marinschek martin.marinsc...@gmail.com wrote: +1, great, great. best regards, Martin On Wed, Apr 14, 2010 at 11:31 AM, Bruno Arandabrunoara...@gmail.com wrote: +1 Great news! Thanks! Bruno On 14 April 2010 08:35, Matthias Wessendorfmat...@apache.org wrote: +1 On Wed, Apr 14, 2010 at 9:05 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: +1 regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/4/14 Leonardo Uribelu4...@gmail.com +1 2010/4/14 Leonardo Uribelu4...@gmail.com Hi, I was running the needed tasks to get the 2.0.0 release of Apache MyFaces core out. The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.1 [1] 2. Maven artifact group org.apache.myfaces.core v2.0.0 [1] 3. Maven artifact group org.apache.myfaces.test v1.0.0-beta-3 [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.0 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] http://people.apache.org/~lu4242/myfaces200 [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces200binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[MyFaces2] TagDecorator in IMPL and API ...
Hi, in IMPL we have this interface: https://svn.apache.org/repos/asf/myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/facelets/tag/TagDecorator.java However it has been promoted to be an API: https://svn.apache.org/repos/asf/myfaces/core/trunk/api/src/main/java/javax/faces/view/facelets/TagDecorator.java the IMPL one is used in these classes: core/impl/src/main/java/org/apache/myfaces/view/facelets/FaceletViewHandler.java core/impl/src/main/java/org/apache/myfaces/view/facelets/FaceletViewDeclarationLanguage.java core/impl/src/main/java/org/apache/myfaces/view/facelets/compiler/CompilationManager.java core/impl/src/main/java/org/apache/myfaces/view/facelets/compiler/Compiler.java core/impl/src/main/java/org/apache/myfaces/view/facelets/tag/jsf/html/HtmlDecorator.java core/impl/src/main/java/org/apache/myfaces/view/facelets/tag/CompositeTagDecorator.java and this dependency leeds to problems like: SEVERE: Error Loading decorator: oracle.adfinternal.view.faces.facelets.rich.AdfTagDecorator java.lang.ClassCastException: oracle.adfinternal.view.faces.facelets.rich.AdfTagDecorator cannot be cast to org.apache.myfaces.view.facelets.tag.TagDecorator at org.apache.myfaces.view.facelets.FaceletViewDeclarationLanguage.loadDecorators(FaceletViewDeclarationLanguage.java:1645) at org.apache.myfaces.view.facelets.FaceletViewDeclarationLanguage.createCompiler(FaceletViewDeclarationLanguage.java:1286) at org.apache.myfaces.view.facelets.FaceletViewDeclarationLanguage.initialize(FaceletViewDeclarationLanguage.java:1617) at org.apache.myfaces.view.facelets.FaceletViewDeclarationLanguage.init(FaceletViewDeclarationLanguage.java:238) at org.apache.myfaces.view.facelets.FaceletViewDeclarationLanguageStrategy.init(FaceletViewDeclarationLanguageStrategy.java:52) at org.apache.myfaces.view.ViewDeclarationLanguageFactoryImpl.initialize(ViewDeclarationLanguageFactoryImpl.java:106) at org.apache.myfaces.view.ViewDeclarationLanguageFactoryImpl.getViewDeclarationLanguage(ViewDeclarationLanguageFactoryImpl.java:79) at org.apache.myfaces.trinidadinternal.application.ViewDeclarationLanguageFactoryImpl.getViewDeclarationLanguage(ViewDeclarationLanguageFactoryImpl.java:77) at org.apache.myfaces.application.ViewHandlerImpl.getViewDeclarationLanguage(ViewHandlerImpl.java:136) -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [MyFaces2] TagDecorator in IMPL and API ...
https://issues.apache.org/jira/browse/MYFACES-2659 already fixed on trunk... -M On Wed, Apr 14, 2010 at 5:48 PM, Matthias Wessendorf mat...@apache.org wrote: Hi, in IMPL we have this interface: https://svn.apache.org/repos/asf/myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/facelets/tag/TagDecorator.java However it has been promoted to be an API: https://svn.apache.org/repos/asf/myfaces/core/trunk/api/src/main/java/javax/faces/view/facelets/TagDecorator.java the IMPL one is used in these classes: core/impl/src/main/java/org/apache/myfaces/view/facelets/FaceletViewHandler.java core/impl/src/main/java/org/apache/myfaces/view/facelets/FaceletViewDeclarationLanguage.java core/impl/src/main/java/org/apache/myfaces/view/facelets/compiler/CompilationManager.java core/impl/src/main/java/org/apache/myfaces/view/facelets/compiler/Compiler.java core/impl/src/main/java/org/apache/myfaces/view/facelets/tag/jsf/html/HtmlDecorator.java core/impl/src/main/java/org/apache/myfaces/view/facelets/tag/CompositeTagDecorator.java and this dependency leeds to problems like: SEVERE: Error Loading decorator: oracle.adfinternal.view.faces.facelets.rich.AdfTagDecorator java.lang.ClassCastException: oracle.adfinternal.view.faces.facelets.rich.AdfTagDecorator cannot be cast to org.apache.myfaces.view.facelets.tag.TagDecorator at org.apache.myfaces.view.facelets.FaceletViewDeclarationLanguage.loadDecorators(FaceletViewDeclarationLanguage.java:1645) at org.apache.myfaces.view.facelets.FaceletViewDeclarationLanguage.createCompiler(FaceletViewDeclarationLanguage.java:1286) at org.apache.myfaces.view.facelets.FaceletViewDeclarationLanguage.initialize(FaceletViewDeclarationLanguage.java:1617) at org.apache.myfaces.view.facelets.FaceletViewDeclarationLanguage.init(FaceletViewDeclarationLanguage.java:238) at org.apache.myfaces.view.facelets.FaceletViewDeclarationLanguageStrategy.init(FaceletViewDeclarationLanguageStrategy.java:52) at org.apache.myfaces.view.ViewDeclarationLanguageFactoryImpl.initialize(ViewDeclarationLanguageFactoryImpl.java:106) at org.apache.myfaces.view.ViewDeclarationLanguageFactoryImpl.getViewDeclarationLanguage(ViewDeclarationLanguageFactoryImpl.java:79) at org.apache.myfaces.trinidadinternal.application.ViewDeclarationLanguageFactoryImpl.getViewDeclarationLanguage(ViewDeclarationLanguageFactoryImpl.java:77) at org.apache.myfaces.application.ViewHandlerImpl.getViewDeclarationLanguage(ViewHandlerImpl.java:136) -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: svn commit: r934048 - in /myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp: FaceletsOnlyException.java JspViewDeclarationLanguage.java
+ \))
+ {
+ String exceptionMessage = The tag f: + tag +
+ is only available on facelets.;
+ throw new FacesException(exceptionMessage,
+ new
FaceletsOnlyException(exceptionMessage, e.getCause()));
+ }
+ }
+ }
+ else if (message.contains(\h\)
+ || message.contains(\ + HtmlLibrary.Namespace +
\))
+ {
+ // check facelets-only h tags
+ for (String tag : FACELETS_ONLY_H_TAGS)
+ {
+ if (message.contains(\ + tag + \))
+ {
+ String exceptionMessage = The tag h: + tag +
+ is only available on facelets.;
+ throw new FacesException(exceptionMessage,
+ new
FaceletsOnlyException(exceptionMessage, e.getCause()));
+ }
+ }
+ }
+ else
+ {
+ // check facelets-only namespaces
+ String namespace = null;
+ if (message.contains(UILibrary.Namespace))
+ {
+ namespace = UILibrary.Namespace;
+ }
+ else if (message.contains(CompositeLibrary.NAMESPACE))
+ {
+ namespace = CompositeLibrary.NAMESPACE;
+ }
+
+ if (namespace != null)
+ {
+ // the message contains a facelets-only namespace
+ String exceptionMessage = All tags with namespace
+
+ namespace + are only available on
facelets.;
+ throw new FacesException(exceptionMessage,
+ new FaceletsOnlyException(exceptionMessage,
e.getCause()));
+ }
+ }
+ }
+
+ // no rule applied to this Exception - rethrow it
+ throw e;
+ }
+ finally
+ {
+ externalContext.setResponse(response);
+ }
+
+ boolean errorResponse = wrappedResponse.getStatus() 200 ||
wrappedResponse.getStatus() 299;
+ if (errorResponse)
+ {
+ wrappedResponse.flushToWrappedResponse();
+ return;
+ }
+
+ //Skip this step if we are rendering an ajax request, because no
content outside
+ //f:view tag should be output.
+ if (!context.getPartialViewContext().isPartialRequest())
+ {
+ // store the wrapped response in the request, so it is
thread-safe
+ setAfterViewTagResponseWrapper(externalContext, wrappedResponse);
+ }
+ }
+
+ �...@override
+ protected void sendSourceNotFound(FacesContext context, String message)
+ {
+ HttpServletResponse response = (HttpServletResponse)
context.getExternalContext().getResponse();
+ try
+ {
+ context.responseComplete();
+ response.sendError(HttpServletResponse.SC_NOT_FOUND, message);
+ }
+ catch (IOException ioe)
+ {
+ throw new FacesException(ioe);
+ }
+ }
+
+}
Propchange:
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/JspViewDeclarationLanguage.java
--
svn:eol-style = native
Propchange:
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/JspViewDeclarationLanguage.java
--
svn:keywords = Date Author Id Revision HeadURL
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Re: svn commit: r934048 - in /myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp: FaceletsOnlyException.java JspViewDeclarationLanguage.java
On Wed, Apr 14, 2010 at 10:09 PM, Jakob Korherr jakob.korh...@gmail.com wrote:
WTF?
no appropriate wording, here
Did anyone read my mail on that?
nope, where did you sent it ?
It cannot be a FacesException, because
then the message would be lost!
that's fine, we can change that back to original code.
-Matthias
2010/4/14 Leonardo Uribe lu4...@gmail.com
2010/4/14 Matthias Wessendorf mat...@apache.org
public class FaceletsOnlyException extends Exception
== can you make that extending FacesException ?
Yes, no problem. It is done.
-Matthias
On Wed, Apr 14, 2010 at 7:48 PM, jak...@apache.org wrote:
Author: jakobk
Date: Wed Apr 14 17:48:28 2010
New Revision: 934048
URL: http://svn.apache.org/viewvc?rev=934048view=rev
Log:
MYFACES-2658 Indicate a better error when using Facelet TAGs on JSP(X)
pages
Added:
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java
(with props)
Modified:
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/JspViewDeclarationLanguage.java
(contents, props changed)
Added:
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java
URL:
http://svn.apache.org/viewvc/myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java?rev=934048view=auto
==
---
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java
(added)
+++
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java
Wed Apr 14 17:48:28 2010
@@ -0,0 +1,40 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * License); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+package org.apache.myfaces.view.jsp;
+
+/**
+ * An Exception that indicates that the user uses a
+ * facelets-only feature on a JSP.
+ *
+ * @author Jakob Korherr (latest modification by $Author$)
+ * @version $Revision$ $Date$
+ *
+ * @since 2.0
+ */
+public class FaceletsOnlyException extends Exception
+{
+
+ private static final long serialVersionUID = 4268633427284543647L;
+
+ public FaceletsOnlyException(String message, Throwable cause)
+ {
+ super(message, cause);
+ }
+
+}
Propchange:
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java
--
svn:eol-style = native
Propchange:
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java
--
svn:keywords = Date Author Id Revision HeadURL
Propchange:
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java
--
svn:mime-type = text/plain
Modified:
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/JspViewDeclarationLanguage.java
URL:
http://svn.apache.org/viewvc/myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/JspViewDeclarationLanguage.java?rev=934048r1=934047r2=934048view=diff
==
---
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/JspViewDeclarationLanguage.java
(original)
+++
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/JspViewDeclarationLanguage.java
Wed Apr 14 17:48:28 2010
@@ -1,139 +1,222 @@
-/*
- * Licensed to the Apache Software Foundation (ASF) under one
- * or more contributor license agreements. See the NOTICE file
- * distributed with this work for additional information
- * regarding copyright ownership. The ASF licenses this file
- * to you under the Apache License, Version 2.0 (the
- * License); you may not use this file except in compliance
- * with the License. You may obtain a copy of the License at
- *
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required
Re: svn commit: r934048 - in /myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp: FaceletsOnlyException.java JspViewDeclarationLanguage.java
ah! :-)
no, this mail is not visible , or it was lost in Gmail (at least for me).
Ok, so let's revert Leo's commit and add some JavaDoc on why it directly
extends Exception to avoid similar refactorings in the future.
Thanks,
Matthias
On Wed, Apr 14, 2010 at 10:48 PM, Jakob Korherr jakob.korh...@gmail.com wrote:
Forwarded my original mail to this topic since it obviously went wrong the
first time.
-- Forwarded message --
From: Jakob Korherr jak...@apache.org
Date: 2010/4/14
Subject: Re: svn commit: r934048 - in
/myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp:
FaceletsOnlyException.java JspViewDeclarationLanguage.java
To: MyFaces Development dev@myfaces.apache.org
No I cannot, because then its message won't be displayed by the
ExceptionHandler, because the ExceptionHandler extracts the Exception
until it finds the first non-FacesException and then it handles this one.
Thus if I would make it a FacesException, the message will be lost. This was
the reason I created FaceletsOnlyException in the first place...
Regards,
Jakob
2010/4/14 Matthias Wessendorf mat...@apache.org
public class FaceletsOnlyException extends Exception
== can you make that extending FacesException ?
-Matthias
On Wed, Apr 14, 2010 at 7:48 PM, jak...@apache.org wrote:
Author: jakobk
Date: Wed Apr 14 17:48:28 2010
New Revision: 934048
URL: http://svn.apache.org/viewvc?rev=934048view=rev
Log:
MYFACES-2658 Indicate a better error when using Facelet TAGs on JSP(X)
pages
Added:
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java
(with props)
Modified:
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/JspViewDeclarationLanguage.java
(contents, props changed)
Added:
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java
URL:
http://svn.apache.org/viewvc/myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java?rev=934048view=auto
==
---
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java
(added)
+++
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java
Wed Apr 14 17:48:28 2010
@@ -0,0 +1,40 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * License); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+package org.apache.myfaces.view.jsp;
+
+/**
+ * An Exception that indicates that the user uses a
+ * facelets-only feature on a JSP.
+ *
+ * @author Jakob Korherr (latest modification by $Author$)
+ * @version $Revision$ $Date$
+ *
+ * @since 2.0
+ */
+public class FaceletsOnlyException extends Exception
+{
+
+ private static final long serialVersionUID = 4268633427284543647L;
+
+ public FaceletsOnlyException(String message, Throwable cause)
+ {
+ super(message, cause);
+ }
+
+}
Propchange:
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java
--
svn:eol-style = native
Propchange:
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java
--
svn:keywords = Date Author Id Revision HeadURL
Propchange:
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/FaceletsOnlyException.java
--
svn:mime-type = text/plain
Modified:
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/JspViewDeclarationLanguage.java
URL:
http://svn.apache.org/viewvc/myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/JspViewDeclarationLanguage.java?rev=934048r1=934047r2=934048view=diff
==
---
myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/view/jsp/JspViewDeclarationLanguage.java
Re: [VOTE] release for myfaces core 2.0.0
+1 Thanks for running this Sent from my iPod. On 15.04.2010, at 03:48, Leonardo Uribe lu4...@gmail.com wrote: +1 2010/4/14 Leonardo Uribe lu4...@gmail.com Hi, I was running the needed tasks to get the 2.0.0 release of Apache MyFaces core out. Minor fixes were done since the latest proposed artifacts (MYFACES-2658, MYFACES-2659 and MYFACES-2660), so we can continue with the vote. The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.1 [1] 2. Maven artifact group org.apache.myfaces.core v2.0.0 [1] 3. Maven artifact group org.apache.myfaces.test v1.0.0-beta-3 [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.0 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] http://people.apache.org/~lu4242/myfaces200 [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces200binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890
Unit test failing? (was: Re: [VOTE] release for myfaces core 2.0.0)
Yesterday I mentioned the same, on trunk I am on Linux, Werner is on OS X. Jakob/Leo: r u windoze ? Thx, Matthias PS: I changed the subject to not hijack the vote ;-) On Thu, Apr 15, 2010 at 7:37 AM, Werner Punz werner.p...@gmail.com wrote: Before I am giving my vote here, there is still a unit test failure ... Am 15.04.10 06:39, schrieb Matthias Wessendorf: +1 Thanks for running this Sent from my iPod. On 15.04.2010, at 03:48, Leonardo Uribe lu4...@gmail.com mailto:lu4...@gmail.com wrote: +1 2010/4/14 Leonardo Uribe mailto:lu4...@gmail.comlu4...@gmail.com mailto:lu4...@gmail.com Hi, I was running the needed tasks to get the 2.0.0 release of Apache MyFaces core out. Minor fixes were done since the latest proposed artifacts (MYFACES-2658, MYFACES-2659 and MYFACES-2660), so we can continue with the vote. The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.1 [1] 2. Maven artifact group org.apache.myfaces.core v2.0.0 [1] 3. Maven artifact group org.apache.myfaces.test v1.0.0-beta-3 [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.0 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] http://people.apache.org/%7Elu4242/myfaces200http://people.apache.org/~lu4242/myfaces200 [2] http://www.apache.org/foundation/voting.html#ReleaseVoteshttp://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/%7Elu4242/myfaces200binsrchttp://people.apache.org/~lu4242/myfaces200binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314890 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: Cannot get tr:inputDate to work
On Tue, Apr 13, 2010 at 11:47 AM, Eisenträger, Tobias tobias.eisentrae...@arag.de wrote: -Ursprüngliche Nachricht- Von: mwessend...@gmail.com [mailto:mwessend...@gmail.com] Im Auftrag von Matthias Wessendorf Gesendet: Dienstag, 13. April 2010 11:31 An: MyFaces Discussion Betreff: Re: Cannot get tr:inputDate to work does the vanilla demo work for you ? No, gives the error as stated in original email. hrm, I do not see that. checked on here http://svn.apache.org/repos/asf/myfaces/trinidad/branches/trinidad-1.2.x/ in trinidad-examples/trinidad-demo I simply called mvn clean jetty:run -PjettyConfig (After I build the branch) tr:inputDate works fine -M Did you register the TrindadFilter ? filter filter-nametrinidad/filter-name filter-class org.apache.myfaces.trinidad.webapp.TrinidadFilter /filter-class /filter filter-mapping filter-nametrinidad/filter-name servlet-namefaces/servlet-name /filter-mapping filter-mapping filter-nameMyFacesExtensionsFilter/filter-name url-pattern*.jsf/url-pattern /filter-mapping filter-mapping filter-nameMyFacesExtensionsFilter/filter-name url-pattern/faces/*/url-pattern /filter-mapping Do I need more filter mappings - I notice that only the urls with appname/index.jsf work, the ones with /faces/index.jspx do not. Did you add the renderKit (to faces-cfg) ? application !-- Use the Trinidad RenderKit -- default-render-kit-id org.apache.myfaces.trinidad.core /default-render-kit-id !-- Set the user locale -- locale-config default-localede/default-locale supported-localede/supported-locale /locale-config resource-bundle base-namemessages/base-name varmsgs/var /resource-bundle resource-bundle base-namejflowwebclient/base-name varproperties/var /resource-bundle /application -M On Tue, Apr 13, 2010 at 11:23 AM, Eisenträger, Tobias tobias.eisentrae...@arag.de wrote: Hello, I think I am missing a configuration, something for additional resources from ADF, but I cannot remember how to configure that, and where. The problem is that when I use the tr:inputDate from the example at: http://myfaces.apache.org/trinidad/trinidad-api/tagdoc/tr_inputDate.html http://myfaces.apache.org/trinidad/trinidad-api/tagdoc/tr_inputDate.html on click nothing happens - the problem ist, that the browser is looking for: http://server:port/appName/__ADFv__?_t=cdvalue=1271150122202loc=deenc=i so-8859-1 where a 404 is returned. Apr 13, 2010 11:22:54 AM org.apache.myfaces.renderkit.html.HtmlRenderKitImpl getRenderer WARNING: Unsupported component-family/renderer-type: org.apache.myfaces.trinidad.Input/org.apache.myfaces.trinidad.CoreInputTex t Apr 13, 2010 11:22:54 AM org.apache.myfaces.trinidadinternal.renderkit.RenderKitBase getRenderer WARNING: Renderer 'org.apache.myfaces.trinidad.CoreInputText' not found for component family 'org.apache.myfaces.trinidad.Input' Apr 13, 2010 11:22:54 AM org.apache.myfaces.trinidad.component.UIXComponentBase _getRendererImpl WARNING: Could not find renderer for UIXInput[UIXEditableFacesBeanImpl, id=patitoPerez] rendererType = org.apache.myfaces.trinidad.CoreInputText Any tipps? Thanks! Mit freundlichen Grüßen Tobias Eisenträger Softwareentwickler Dokumentenmanagement/Workflow/Internet, AKB 8125 ARAG IT GmbH ARAG Platz 1, 40472 Düsseldorf Tel.: +49 (0)211 964-1937 tobias.eisentrae...@arag.de www.ARAG.de Aufsichtsratsvorsitzender: Gerd Peskes Vorstand: Dr. Paul-Otto Faßbender (Vors.), Dr. Jan-Peter Horst, Dr. Johannes Kathan, Werner Nicoll, Hanno Petersen, Dr. Joerg Schwarze Sitz und Registergericht: Düsseldorf, HRB 1371 USt-ID-Nr.: DE 119 355 995 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
MyFaces JIRA users - please read
From the incident report[1]: If you are a user of the Apache hosted JIRA, Bugzilla, or Confluence, a hashed copy of your password has been compromised. Thanks, -Matthias [1] - https://blogs.apache.org/infra/entry/apache_org_04_09_2010 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
