Re: Skinning the showDetail component
OK, I'll leave my CSS in place, and wait until the showDetail link can be skinned individually. Do I open an issue for this? Thanks, Henk Adam Winer wrote: There isn't currently any good way to skin the prompt of the showDetail. The link uses the OraLink style, and there's no style on the showDetail as a whole, so there's no way to detect just showDetail links. Most of the SkinSelectors are in SkinSelectors.java in the org.apache.myfaces.trinidadinternal.renderkit.core.xhtml package. But not all. -- Adam On 4/22/07, Henk Vanhoe [EMAIL PROTECTED] wrote: Hi, (As nobody seems to know the answer to my previous question...) Is the list of selectors in http://incubator.apache.org/adffaces/skin-selectors.html complete? If not, does anybody know in what (source-)file these selectors are defined, so I can look them up myself (I looked through the source-code of Trinidad, but I didn't find any file listing these selectors)... Thanks, Henk Henk Vanhoe wrote: Hi, I'm using the tr:showDetail component. I would like to change the color of the prompt (the text next to the hide/show icon). Is it possible to do that with a standard skinning selector? I did not find a suitable selector in the list of selectors on this page: http://incubator.apache.org/adffaces/skin-selectors.html. (I managed to change the colour by using standard CSS, but as I am explicitly referencing HTML elements generated by Trinidad, my stylesheet might be broken in a future release...) Kind regards, Henk
Re: Using Trinidad under Java 1.4?
Hi, retroweaver works with trinidad, but you need to put this class in your classpath Gary VanMatre wrote: From: Bhringer Jochen [EMAIL PROTECTED] Hello, I am doing some research for a new project. It is a web application whose user interface should be programmed using JSF. The application server we are running in the target environment is WebSphere Application Server 5.1. Unfortunately the latest JDK supported by this WebSphere version is 1.4.2 :-( The installation instructions of Trinidad do note Java 5 as a dependency. So is this a showstopper for Trinidad in this project? Perhaps the only 1.5 features used are generics and these can also be interpreted by a 1.4 jdk on bytecodelevel... I have used Trinidad in other projects and would really like to use it again... So my question in one sentence: Is it possible to run Trinidad on a 1.4 JDK with small amount of adaptation or should I stop thinking about it immediately? Maybe retroweaver would work? http://retroweaver.sourceforge.net/overview.html Best regards, Jochen Gary -- Arnaud Mergey | Software Developer | Oracle Fusion Middleware 300 rn6 69760 Limonest package net.sourceforge.retroweaver.runtime.java.lang; public class ThreadLocal_ { public static void remove(ThreadLocal threadLocal) { threadLocal.set(null); } }
Re: Using Trinidad with Facelet Bug
1.1.11 On 4/24/07, Gareth Paglinawan [EMAIL PROTECTED] wrote: Please tell me what's the version of facelet should I use. I recently join the company and Im planning to introduce the trinidad in the existing development. I have not notice the facelet version they are using. What should be the Trinidad and Facelet should I use? Regards, Gareth On 4/23/07, Gareth Paglinawan [EMAIL PROTECTED] wrote: Hi Adam, This is the stacktrace I am getting java.lang.NullPointerException: charsetName java.io.OutputStreamWriter .init(OutputStreamWriter.java:81) java.net.URLEncoder.encode( URLEncoder.java:189) org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.addParameterToHref (HtmlLinkRendererBase.java:445) org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.addChildParametersToHref (HtmlLinkRendererBase.java:383) org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.renderOutputLinkStart (HtmlLinkRendererBase.java:399) org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.encodeBegin (HtmlLinkRendererBase.java:101) javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:512) com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive( ComponentSupport.java:232) com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive( ComponentSupport.java:239) com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive( ComponentSupport.java:239) com.sun.facelets.FaceletViewHandler.renderView( FaceletViewHandler.java:580) org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView (ViewHandlerImpl.java:181) de.mindmatters.faces.spring.context.servlet.FacesExternalResourceView.render (FacesExternalResourceView.java:72) de.mindmatters.faces.spring.context.servlet.AbstractFacesView.renderMergedOutputModel (AbstractFacesView.java:111) org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:250) org.springframework.web.servlet.DispatcherServlet.render( DispatcherServlet.java:961) de.mindmatters.faces.spring.context.servlet.DispatcherServlet.render( DispatcherServlet.java:121) org.springframework.web.servlet.DispatcherServlet.doDispatch( DispatcherServlet.java:738) org.springframework.web.servlet.DispatcherServlet.doService( DispatcherServlet.java:658) de.mindmatters.faces.spring.context.servlet.DispatcherServlet.doService( DispatcherServlet.java:86) org.springframework.web.servlet.FrameworkServlet.processRequest( FrameworkServlet.java:392) org.springframework.web.servlet.FrameworkServlet.doGet( FrameworkServlet.java:347) javax.servlet.http.HttpServlet.service( HttpServlet.java:689) javax.servlet.http.HttpServlet.service( HttpServlet.java:802) org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter (TrinidadFilterImpl.java:329) org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl (TrinidadFilterImpl.java:293) org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter( TrinidadFilterImpl.java:216) org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter( TrinidadFilter.java:93) org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter( FilterChainProxy.java:292) org.acegisecurity.intercept.web.FilterSecurityInterceptor.invoke( FilterSecurityInterceptor.java:116) org.acegisecurity.intercept.web.FilterSecurityInterceptor.doFilter( FilterSecurityInterceptor.java:79) org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter( FilterChainProxy.java:303) org.acegisecurity.ui.ExceptionTranslationFilter.doFilter( ExceptionTranslationFilter.java:143) org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter( FilterChainProxy.java:303) org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter( HttpSessionContextIntegrationFilter.java:220) com._24translate.web.support.HttpSessionContextIntegrationFilter.doFilter( HttpSessionContextIntegrationFilter.java:75) org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter( FilterChainProxy.java:303) org.acegisecurity.util.FilterChainProxy.doFilter(FilterChainProxy.java:173) org.acegisecurity.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:120) org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter( ExtensionsFilter.java:144) org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal( CharacterEncodingFilter.java:75) org.springframework.web.filter.OncePerRequestFilter.doFilter( OncePerRequestFilter.java:76) com._24translate.web.support.RequestTimeMeasurementFilter.doFilter( RequestTimeMeasurementFilter.java:158) org.springframework.web.filter.DelegatingFilterProxy.doFilter( DelegatingFilterProxy.java:137) com._24translate.ui.hibernate.HibernateSessionAwareCleanUpListener.doFilter( HibernateSessionAwareCleanUpListener.java:56) This was raised here http://mail-archives.apache.org/mod_mbox/incubator-adffaces-user/200702.mbox/[EMAIL PROTECTED] Gareth On 4/23/07, Adam Winer
Re: Installing Maven Trinidad Archetype
Hi Matthias, I'm sorry you're going to have to be a bit more specific - this isn't very clear to me: -checkout of adffaces folder cd plugin what do you mean by the adffdaces folder? Where is the link? Can you be a bit more expicit? Thanks a lot Andy On 4/21/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: Hey Andy, I was updating a minor thing inside the archetype; nothing related to your issue. In oder to get the archetype working I did this: -checkout of adffaces folder cd plugin mvn clean install cd ../trinidad mvn clean install ...go somewhere, where you'd like to have your projects... mvn archetype:create -DarchetypeGroupId=org.apache.myfaces.trinidadbuild -DarchetypeArtifactId=myfaces-archetype-trinidad -DarchetypeVersion=1.0.1-incubating-SNAPSHOT -DgroupId=com.apachecon.amsterdam.workshop -DartifactId=trinidad that generates a project skeleton. Now, mvn -PjettyConfig clean jetty:run the jetty container comes up and servers your page http://localhost:8080/trinidad/faces/index.jspx Does that solve your issues ? Greetings, Matthias On 4/17/07, Andy Birchall [EMAIL PROTECTED] wrote: So is there something wrong with the Archtype? FYI after I build Trinidad I have the maven-plugin-parent\1.0.0-incubating directory in my local repository, but with no jar file. Thanks a lot Andy On 4/15/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: yeah, I'll check the archetype On 4/14/07, Adam Winer [EMAIL PROTECTED] wrote: Perhaps, but shouldn't the archetype be pointing at 1.0.0 plugins, not 1.0.1-SNAPSHOT? -- Adam On 4/14/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: perhaps it hasn't the incubator repo in. -M On 4/14/07, Simon Lessard [EMAIL PROTECTED] wrote: Hello, mvn install in the plugins directory to build it. However, I don't see why this is needed, if this is really the issue since he built plugin can be found in maven repos. On 4/14/07, Andy Birchall [EMAIL PROTECTED] wrote: Ah, I wasn't aware that I had to do that. I thought that these instructions were building the Archetype plugin: http://wiki.apache.org/myfaces/Trinidad_Archetype No? Can you point me to the page which tells me how to build the plugins? Thanks a lot Andy On 4/14/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: did you build the plugins as well ? On 4/13/07, Andy Birchall [EMAIL PROTECTED] wrote: Yes I did. I built it using the instructions here: http://wiki.apache.org/myfaces/Building_ADF_With_Maven and it all built fine. Thanks On 4/13/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: did you build trinidad ? On 4/13/07, Andy Birchall [EMAIL PROTECTED] wrote: Hello, I've been trying to install the Trinidad Archetype to my Maven 2 installation but without success. I have followed the instructions on here: http://wiki.apache.org/myfaces/Trinidad_Archetype i.e. I have checked out the source and typed 'mvn install' in the trinidad-archetype directory But this results in this error: C:\Temp\trinidad-archetypemvn install [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.myfaces.trinidadbuild ArtifactId: maven-plugin-parent Version: 1.0.1-incubating-SNAPSHOT Reason: Unable to download the artifact from any repository org.apache.myfaces.trinidadbuild:maven-plugin-parent:pom:1.0.1-incubating-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Cannot find parent: org.apache.myfaces.trinidadbuild:maven-plugin-parent for project: org.apache.myfaces.trinidadbuild:myfaces-arc hetype-trinidad:maven-plugin:1.0.1-incubating-SNAPSHOT So it seems it is looking for the Trinidad artifact in the central maven repository but obviously can't find it. Do I have to set another repository for it to look in to download? I'm probably missing something obvious but can't seem to find a solution. Sorry, I'm pretty new to this. Thanks Andy -- Matthias Wessendorf
Re: Installing Maven Trinidad Archetype
the svn folder for trinidad is currently named ADFFACES, because, when coming to Apache that was the name of the product. http://svn.apache.org/viewvc/incubator/adffaces/trunk/ that contains plugins and trinidad (meaning the core, the jsf components) -M On 4/24/07, Andy Birchall [EMAIL PROTECTED] wrote: Hi Matthias, I'm sorry you're going to have to be a bit more specific - this isn't very clear to me: -checkout of adffaces folder cd plugin what do you mean by the adffdaces folder? Where is the link? Can you be a bit more expicit? Thanks a lot Andy On 4/21/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: Hey Andy, I was updating a minor thing inside the archetype; nothing related to your issue. In oder to get the archetype working I did this: -checkout of adffaces folder cd plugin mvn clean install cd ../trinidad mvn clean install ...go somewhere, where you'd like to have your projects... mvn archetype:create -DarchetypeGroupId=org.apache.myfaces.trinidadbuild -DarchetypeArtifactId=myfaces-archetype-trinidad -DarchetypeVersion=1.0.1-incubating-SNAPSHOT -DgroupId=com.apachecon.amsterdam.workshop -DartifactId=trinidad that generates a project skeleton. Now, mvn -PjettyConfig clean jetty:run the jetty container comes up and servers your page http://localhost:8080/trinidad/faces/index.jspx Does that solve your issues ? Greetings, Matthias On 4/17/07, Andy Birchall [EMAIL PROTECTED] wrote: So is there something wrong with the Archtype? FYI after I build Trinidad I have the maven-plugin-parent\1.0.0-incubating directory in my local repository, but with no jar file. Thanks a lot Andy On 4/15/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: yeah, I'll check the archetype On 4/14/07, Adam Winer [EMAIL PROTECTED] wrote: Perhaps, but shouldn't the archetype be pointing at 1.0.0 plugins, not 1.0.1-SNAPSHOT? -- Adam On 4/14/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: perhaps it hasn't the incubator repo in. -M On 4/14/07, Simon Lessard [EMAIL PROTECTED] wrote: Hello, mvn install in the plugins directory to build it. However, I don't see why this is needed, if this is really the issue since he built plugin can be found in maven repos. On 4/14/07, Andy Birchall [EMAIL PROTECTED] wrote: Ah, I wasn't aware that I had to do that. I thought that these instructions were building the Archetype plugin: http://wiki.apache.org/myfaces/Trinidad_Archetype No? Can you point me to the page which tells me how to build the plugins? Thanks a lot Andy On 4/14/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: did you build the plugins as well ? On 4/13/07, Andy Birchall [EMAIL PROTECTED] wrote: Yes I did. I built it using the instructions here: http://wiki.apache.org/myfaces/Building_ADF_With_Maven and it all built fine. Thanks On 4/13/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: did you build trinidad ? On 4/13/07, Andy Birchall [EMAIL PROTECTED] wrote: Hello, I've been trying to install the Trinidad Archetype to my Maven 2 installation but without success. I have followed the instructions on here: http://wiki.apache.org/myfaces/Trinidad_Archetype i.e. I have checked out the source and typed 'mvn install' in the trinidad-archetype directory But this results in this error: C:\Temp\trinidad-archetypemvn install [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.myfaces.trinidadbuild ArtifactId: maven-plugin-parent Version: 1.0.1-incubating-SNAPSHOT Reason: Unable to download the artifact from any repository org.apache.myfaces.trinidadbuild:maven-plugin-parent:pom:1.0.1-incubating-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Cannot find parent: org.apache.myfaces.trinidadbuild:maven-plugin-parent for project: org.apache.myfaces.trinidadbuild:myfaces-arc hetype-trinidad:maven-plugin:1.0.1-incubating-SNAPSHOT So it seems it is looking for
AW: Using Trinidad under Java 1.4?
Hello Arnaud, Thanks for this hint! I am a bit confused because of Adam Winer writing that Trinidad uses some Java5 specific APIs. I think Retroweaver does not provide these specific APIs (like ConcurrentHashMap). But you wrote it works for you, so I think you have done a build. Would you provide me that build? Best regards Jochen Von: Arnaud Mergey [mailto:[EMAIL PROTECTED] Hi, retroweaver works with trinidad, but you need to put this class in your classpath Gary VanMatre wrote: From: Böhringer Jochen [EMAIL PROTECTED] Hello, I am doing some research for a new project. It is a web application whose user interface should be programmed using JSF. The application server we are running in the target environment is WebSphere Application Server 5.1. Unfortunately the latest JDK supported by this WebSphere version is 1.4.2 :-( The installation instructions of Trinidad do note Java 5 as a dependency. So is this a showstopper for Trinidad in this project? Perhaps the only 1.5 features used are generics and these can also be interpreted by a 1.4 jdk on bytecodelevel... I have used Trinidad in other projects and would really like to use it again... So my question in one sentence: Is it possible to run Trinidad on a 1.4 JDK with small amount of adaptation or should I stop thinking about it immediately? Maybe retroweaver would work? http://retroweaver.sourceforge.net/overview.html Best regards, Jochen Gary -- Arnaud Mergey | Software Developer | Oracle Fusion Middleware 300 rn6 69760 Limonest
tr:document and accessibility-mode
Hello Why must the accessibility-mode switched to inaccessible for the usage of initialFocusId in tr:document? Is there a special reason for this? I would like to set the focus to a special component on every page. Is there an other possibility to do this? Regards Michael
Re: Skinning the showDetail component
Yes, please do. (Of course, an issue + a patch is even better.) -- Adam On 4/24/07, Henk Vanhoe [EMAIL PROTECTED] wrote: OK, I'll leave my CSS in place, and wait until the showDetail link can be skinned individually. Do I open an issue for this? Thanks, Henk Adam Winer wrote: There isn't currently any good way to skin the prompt of the showDetail. The link uses the OraLink style, and there's no style on the showDetail as a whole, so there's no way to detect just showDetail links. Most of the SkinSelectors are in SkinSelectors.java in the org.apache.myfaces.trinidadinternal.renderkit.core.xhtml package. But not all. -- Adam On 4/22/07, Henk Vanhoe [EMAIL PROTECTED] wrote: Hi, (As nobody seems to know the answer to my previous question...) Is the list of selectors in http://incubator.apache.org/adffaces/skin-selectors.html complete? If not, does anybody know in what (source-)file these selectors are defined, so I can look them up myself (I looked through the source-code of Trinidad, but I didn't find any file listing these selectors)... Thanks, Henk Henk Vanhoe wrote: Hi, I'm using the tr:showDetail component. I would like to change the color of the prompt (the text next to the hide/show icon). Is it possible to do that with a standard skinning selector? I did not find a suitable selector in the list of selectors on this page: http://incubator.apache.org/adffaces/skin-selectors.html. (I managed to change the colour by using standard CSS, but as I am explicitly referencing HTML elements generated by Trinidad, my stylesheet might be broken in a future release...) Kind regards, Henk
Change value of SelectOneChoice in background
Hello all, I have next problem with SelectOneChoice component: 1. value is binded to backing bean and taken for example from database 2. when query page, component show correct value 3. now another process change value (in database) 4. page is reloaded (by reload button in browser), then component show bad, old value 5. only new query for page show correct value of component Moreover, if page is submitted (by another component), then bad old value of SelectOneChoice component is saved into database. I am using latest Trinidad 1.0.1 SNAPSHOT. Thanks for any help, Peter I'm simulated this in next test. Changing value by button or SelectOneChoice is OK. When I change value of socTestVal in session backing bean in debuger (simulating backgroung value change), component don't reflect this change, when page is only reloading. index.jsp test page: !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN http://www.w3.org/TR/html4/loose.dtd; %@ page contentType=text/html;charset=UTF-8% %@ taglib uri=http://java.sun.com/jsf/core; prefix=f% %@ taglib uri=http://myfaces.apache.org/trinidad; prefix=tr% %@ taglib uri=http://myfaces.apache.org/trinidad/html; prefix=trh% f:view trh:html trh:head meta http-equiv=Content-Type content=text/html; charset=UTF-8/ titleSelect One Choice Test/title /trh:head trh:body tr:form id=TestForm tr:selectOneChoice autoSubmit=true label=Selection: value=#{IndexBean.socTestValue} tr:selectItem label=One value=1/ tr:selectItem label=Two value=2/ /tr:selectOneChoice tr:commandButton text=Set One actionListener=#{IndexBean.ChoiceOneAction}/ /tr:form /trh:body /trh:html /f:view Session backing bean: package test.backing; import javax.faces.event.ActionEvent; public class IndexBean { short socTestVal; public IndexBean() { socTestVal = 2; } public Short getSocTestValue() { return socTestVal; } public void setSocTestValue(Short newVal) { socTestVal = newVal.shortValue(); } public void ChoiceOneAction(ActionEvent actionEvent) { socTestVal = 1; } }
Re: Change value of SelectOneChoice in background
Maybe this is what you're looking for: http://www.nabble.com/Re%3A-Programatically-updating-the-model-p9961060.html On 4/24/07, Petr Kotek [EMAIL PROTECTED] wrote: Hello all, I have next problem with SelectOneChoice component: 1. value is binded to backing bean and taken for example from database 2. when query page, component show correct value 3. now another process change value (in database) 4. page is reloaded (by reload button in browser), then component show bad, old value 5. only new query for page show correct value of component Moreover, if page is submitted (by another component), then bad old value of SelectOneChoice component is saved into database. I am using latest Trinidad 1.0.1 SNAPSHOT. Thanks for any help, Peter I'm simulated this in next test. Changing value by button or SelectOneChoice is OK. When I change value of socTestVal in session backing bean in debuger (simulating backgroung value change), component don't reflect this change, when page is only reloading. index.jsp test page: !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN http://www.w3.org/TR/html4/loose.dtd; %@ page contentType=text/html;charset=UTF-8% %@ taglib uri=http://java.sun.com/jsf/core; prefix=f% %@ taglib uri=http://myfaces.apache.org/trinidad; prefix=tr% %@ taglib uri=http://myfaces.apache.org/trinidad/html; prefix=trh% f:view trh:html trh:head meta http-equiv=Content-Type content=text/html; charset=UTF-8/ titleSelect One Choice Test/title /trh:head trh:body tr:form id=TestForm tr:selectOneChoice autoSubmit=true label=Selection: value=#{IndexBean.socTestValue} tr:selectItem label=One value=1/ tr:selectItem label=Two value=2/ /tr:selectOneChoice tr:commandButton text=Set One actionListener=#{IndexBean.ChoiceOneAction}/ /tr:form /trh:body /trh:html /f:view Session backing bean: package test.backing; import javax.faces.event.ActionEvent; public class IndexBean { short socTestVal; public IndexBean() { socTestVal = 2; } public Short getSocTestValue() { return socTestVal; } public void setSocTestValue(Short newVal) { socTestVal = newVal.shortValue(); } public void ChoiceOneAction(ActionEvent actionEvent) { socTestVal = 1; } }
Re: AW: Using Trinidad under Java 1.4?
Arnaud, this has been asked sometimes before, can you try to add some infos on the wiki ? Thx, Matthias On 4/24/07, Arnaud Mergey [EMAIL PROTECTED] wrote: Hi, Retroweaver weave the bytecode and replace automatically specific java 1.5API by backported API. for ConcurrentHashMap retroweaver replace java.util.concurrent by util.concurrent backport wich is provided with retroweaver, so if you retroweave trinidad you need to put in your classpath runtime jar of retroweaver backport-util-concurrent.jar and the class provided in my mail. regards, Arnaud Böhringer Jochen wrote: Hello Arnaud, Thanks for this hint! I am a bit confused because of Adam Winer writing that Trinidad uses some Java5 specific APIs. I think Retroweaver does not provide these specific APIs (like ConcurrentHashMap). But you wrote it works for you, so I think you have done a build. Would you provide me that build? Best regards Jochen Von: Arnaud Mergey [mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]] Hi, retroweaver works with trinidad, but you need to put this class in your classpath Gary VanMatre wrote: From: Böhringer Jochen [EMAIL PROTECTED] [EMAIL PROTECTED] Hello, I am doing some research for a new project. It is a web application whose user interface should be programmed using JSF. The application server we are running in the target environment is WebSphere Application Server 5.1. Unfortunately the latest JDK supported by this WebSphere version is 1.4.2 :-( The installation instructions of Trinidad do note Java 5 as a dependency. So is this a showstopper for Trinidad in this project? Perhaps the only 1.5 features used are generics and these can also be interpreted by a 1.4 jdk on bytecodelevel... I have used Trinidad in other projects and would really like to use it again... So my question in one sentence: Is it possible to run Trinidad on a 1.4 JDK with small amount of adaptation or should I stop thinking about it immediately? Maybe retroweaver would work? http://retroweaver.sourceforge.net/overview.html Best regards, Jochen Gary -- [image: Oracle Email Signature Logo] Arnaud Mergey | Software Developer | Oracle Fusion Middleware 300 rn6 69760 Limonest -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
Re: Installing Maven Trinidad Archetype
Ah ok thanks for the link. I did the same as you and the plugins and trinidad built and installed ok, with no errors. However when I run the archetype:create I get this error from Maven: [INFO] Starting Jakarta Velocity v1.4 [INFO] RuntimeInstance initializing. [INFO] Default Properties File: org\apache\velocity\runtime\defaults\velocity.properties [INFO] Default ResourceManager initializing. (class org.apache.velocity.runtime.resource.R esourceManagerImpl) [INFO] Resource Loader Instantiated: org.codehaus.plexus.velocity.ContextClassLoaderResour ceLoader [INFO] ClasspathResourceLoader : initialization starting. [INFO] ClasspathResourceLoader : initialization complete. [INFO] ResourceCache : initialized. (class org.apache.velocity.runtime.resource.ResourceCa cheImpl) [INFO] Default ResourceManager initialization complete. [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Include [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach [INFO] Created: 20 parsers. [INFO] Velocimacro : initialization starting. [INFO] Velocimacro : adding VMs from VM library template : VM_global_library.vm [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any resource l oader. [INFO] Velocimacro : error using VM library template VM_global_library.vm : org.apache.ve locity.exception.ResourceNotFoundException: Unable to find resource 'VM_global_library.vm' [INFO] Velocimacro : VM library template macro registration complete. [INFO] Velocimacro : allowInline = true : VMs can be defined inline in templates [INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may NOT replace pr evious VM definitions [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be global in scop e if allowed. [INFO] Velocimacro : initialization complete. [INFO] Velocity successfully started. [INFO] [archetype:create] [INFO] Defaulting package to group ID: uk.org.aqa [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.myfaces.trinidadbuild ArtifactId: myfaces-archetype-trinidad Version: 1.0.1-incubating-SNAPSHOT Reason: Unable to download the artifact from any repository On 4/24/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: the svn folder for trinidad is currently named ADFFACES, because, when coming to Apache that was the name of the product. http://svn.apache.org/viewvc/incubator/adffaces/trunk/ that contains plugins and trinidad (meaning the core, the jsf components) -M On 4/24/07, Andy Birchall [EMAIL PROTECTED] wrote: Hi Matthias, I'm sorry you're going to have to be a bit more specific - this isn't very clear to me: -checkout of adffaces folder cd plugin what do you mean by the adffdaces folder? Where is the link? Can you be a bit more expicit? Thanks a lot Andy On 4/21/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: Hey Andy, I was updating a minor thing inside the archetype; nothing related to your issue. In oder to get the archetype working I did this: -checkout of adffaces folder cd plugin mvn clean install cd ../trinidad mvn clean install ...go somewhere, where you'd like to have your projects... mvn archetype:create -DarchetypeGroupId=org.apache.myfaces.trinidadbuild -DarchetypeArtifactId=myfaces-archetype-trinidad -DarchetypeVersion=1.0.1-incubating-SNAPSHOT -DgroupId=com.apachecon.amsterdam.workshop -DartifactId=trinidad that generates a project skeleton. Now, mvn -PjettyConfig clean jetty:run the jetty container comes up and servers your page http://localhost:8080/trinidad/faces/index.jspx Does that solve your issues ? Greetings, Matthias On 4/17/07, Andy Birchall [EMAIL PROTECTED] wrote: So is there something wrong with the Archtype? FYI after I build Trinidad I have the maven-plugin-parent\1.0.0-incubating directory in my local repository, but with no jar file. Thanks a lot Andy On 4/15/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: yeah, I'll check the archetype On 4/14/07, Adam Winer [EMAIL PROTECTED] wrote: Perhaps, but shouldn't the archetype be pointing at 1.0.0 plugins, not 1.0.1-SNAPSHOT? -- Adam On 4/14/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: perhaps it hasn't the incubator repo in. -M On 4/14/07, Simon Lessard [EMAIL PROTECTED] wrote: Hello, mvn install in the plugins directory to build it. However, I don't see why this is needed, if this is really the issue since he built plugin
Calendar Pop-up of selectInputDate fails with 404
Hi all! I use the selectInputDate component for entering a date value. Everthing works fine, but it fails if I click on the calendar icon that should open the Calendar pop-up. 404 Not Found /myapp/myapp/__ADFv__.jsf Does anybody have an idea? Many thanks in advance. Kuno My web.xml looks like this: ?xml version=1.0 encoding=UTF-8? web-app xmlns=http://java.sun.com/xml/ns/j2ee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; id=WebApp_ID version=2.4 xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd; display-nameEDIS/display-name context-param param-namelog4jConfigLocation/param-name param-value/WEB-INF/classes/log4j.xml/param-value /context-param context-param param-namecontextConfigLocation/param-name param-valueclasspath:applicationContext.xml classpath:applicationContextJSF.xml /WEB-INF/acegi.xml/param-value /context-param !-- Use documents saved as *.xhtml for Facelets -- context-param param-namejavax.faces.DEFAULT_SUFFIX/param-name param-value.xhtml/param-value /context-param !-- FaceletViewHandler configuration -- context-param param-nameorg.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER/param-name param-valuecom.sun.facelets.FaceletViewHandler/param-value /context-param !-- Special Debug Output for Development -- context-param param-namefacelets.DEVELOPMENT/param-name param-valuetrue/param-value /context-param !-- Optional JSF-RI Parameters to Help Debug -- context-param param-namecom.sun.faces.validateXml/param-name param-valuetrue/param-value /context-param context-param param-namecom.sun.faces.verifyObjects/param-name param-valuetrue/param-value /context-param context-param param-namejavax.faces.STATE_SAVING_METHOD/param-name param-valueclient/param-value /context-param context-param param-name org.apache.myfaces.trinidad.DEBUG_JAVASCRIPT /param-name param-valuefalse/param-value /context-param context-param param-name org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION /param-name param-valuetrue/param-value /context-param context-param param-name org.apache.myfaces.trinidad.resource.DEBUG /param-name param-valuetrue/param-value /context-param context-param param-name org.apache.myfaces.trinidad.CACHE_VIEW_ROOT /param-name param-valuefalse/param-value /context-param !-- Log4j -- listener listener-classorg.springframework.web.util.Log4jConfigListener/listener-class /listener !-- Spring -- listener listener-classorg.springframework.web.context.ContextLoaderListener/listener-class /listener listener listener-classorg.springframework.web.context.request.RequestContextListener/listener-class /listener !-- MyFaces -- listener listener-classorg.apache.myfaces.webapp.StartupServletContextListener/listener-class /listener !-- Spracheinstellungen -- filter filter-namelocaleFilter/filter-name filter-classch.bkw.edis.web.LocaleFilter/filter-class /filter filter filter-nametrinidad/filter-name filter-classorg.apache.myfaces.trinidad.webapp.TrinidadFilter/filter-class /filter filter-mapping filter-namelocaleFilter/filter-name url-pattern/*/url-pattern /filter-mapping filter filter-nameCharacterEncodingFilter/filter-name filter-classorg.springframework.web.filter.CharacterEncodingFilter/filter-class init-param param-nameencoding/param-name param-valueUTF-8/param-value /init-param /filter filter-mapping filter-nameCharacterEncodingFilter/filter-name url-pattern*.jsf/url-pattern /filter-mapping filter-mapping filter-nameCharacterEncodingFilter/filter-name url-pattern*.xhtml/url-pattern /filter-mapping !-- OpenSessionInViewFilter -- !-- Bitte auskommentieren um eine LazyInitializationException zu provozieren -- filter filter-namehibernateFilter/filter-name filter-classorg.springframework.orm.hibernate3.support.OpenSessionInViewFilter/filter-class /filter filter-mapping filter-namehibernateFilter/filter-name url-pattern*.jsf/url-pattern /filter-mapping !-- Ende OpenSessionInViewFilter -- !-- Acegi -- filter filter-nameAcegiFilter/filter-name filter-classorg.acegisecurity.util.FilterToBeanProxy/filter-class init-param param-nametargetClass/param-name param-valueorg.acegisecurity.util.FilterChainProxy/param-value /init-param /filter filter-mapping filter-nameAcegiFilter/filter-name url-pattern/*/url-pattern dispatcherFORWARD/dispatcher dispatcherREQUEST/dispatcher /filter-mapping filter-mapping
Re: tr:subform and autoSubmit bug
It's a known limitation of how subforms are implemented: they look for FacesEvents queued during processDecodes() to see if that subtree should be further processed. However, autoSubmit components don't queue a FacesEvent until ValueChangeEvent, which happens later in the cycle. It should get fixed, though. -- Adam On 4/24/07, D. Cardon [EMAIL PROTECTED] wrote: Hi, I've done some more testing with the subform functionality in Trinidad and think I've isolated a bug with a very simple test case. To reproduce this functionality, a few modifications need to be made to the blank project that is found in the trinidad repository. Here's what to do: - Modify the index.jspx entry for the tr:inputText, replacing it with: tr:inputText label=Your name id=input1 value=#{helloWorldBacking.name} autoSubmit=true valueChangeListener=#{helloWorldBacking.changeMethod} / Then, implement the changeMethod in the backing bean: public void changeMethod( ValueChangeEvent event ) { System.out.println( Change method called! ); } Now, test the page by entering a value into the test field and then tabbing away from it. This will fire the field to be submitted. In your console, you should see the Change method called! message appearing--this behaves as expected. To reproduce the invalid behavior with a subform, alter index.jspx slightly, by wrapping the inputText (or its containing component) in a tr:subform tag. Reloading the page and performing the test again, you should no longer see the Change method called! message. This behavior appears to be the same for any component set to autoSubmit. After digging into the code somewhat, it appears that the subform is unaware that the inputText component has changed and so it does not run its children through the necessary phases. The root of this symptom actually relates to a lot of other problems with the subform tag. For example, using the subform to isolate regions for validation does not work at all due to this issue, because validations are not processed and model values are not updated for the components in the subform. Since I'm a new Trinidad user, I don't really know how this should be reported. I did sign up for JIRA, but I'm not sure what the severity of the issue should be. Also, it would be reassuring if someone else can reproduce this, that would verify that it's not just some problem with my machine / setup. Thanks, --David __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: how do I refresh a table component after selecting and deleting one or more rows ?
Problem solved; thank you. Simon Lessard wrote: Add table:discard_selected as partialTarget, tr:table is a naming container, and I don't think we have a children trigger detection algorithm implemented yet. Thank you for the information. I didn't have to use partialTarget; I , instead, added an action attribute to my commandButton component to force page refresh. Also, you should not keep a a bound component in session (using binding attribute). I read that you want to keep the bean session scoped, so you'll have to split it in two beans: I've removed the binding attribute from the table component. regards. -- Edmond/
Re: tr:subform and autoSubmit bug
That's exactly how it's supposed to work :-) I don't know the syntax for (or even if it's possible with) Trinidad's subform, but the Tomahawk sandbox subform can be submitted by explicitly providing an actionFor attribute on your t:commandButton which lists out which subForms should be submitted. I think I saw a previous post where this hadn't been added to the Trinidad subform yet. h:form sandbox:subForm id=mysubform tr:inputText value=#{pageFlowScope.inputValue} label=Input required=true / sandbox:subForm t:commandButton text=Submit actionFor=mysubform action=doIt/ /tr:form On 4/24/07, D. Cardon [EMAIL PROTECTED] wrote: I don't know if this is a related issue (it seems to be to me), but subform validation does not occur when a parent form is submitted. I.e., say that I have a form with a subform in it and a submit button outside of the subform---like this: tr:form tr:subform tr:inputText value=#{pageFlowScope.inputValue} label=Input required=true / /tr:subform tr:commandButton text=Submit action=doIt/ /tr:form If I press the command button, then the parent form will submit even if the required field is left empty! It doesn't seem as if that is how it is supposed to work, but I don't know. --David --- Adam Winer [EMAIL PROTECTED] wrote: It's a known limitation of how subforms are implemented: they look for FacesEvents queued during processDecodes() to see if that subtree should be further processed. However, autoSubmit components don't queue a FacesEvent until ValueChangeEvent, which happens later in the cycle. It should get fixed, though. -- Adam On 4/24/07, D. Cardon [EMAIL PROTECTED] wrote: Hi, I've done some more testing with the subform functionality in Trinidad and think I've isolated a bug with a very simple test case. To reproduce this functionality, a few modifications need to be made to the blank project that is found in the trinidad repository. Here's what to do: - Modify the index.jspx entry for the tr:inputText, replacing it with: tr:inputText label=Your name id=input1 value=#{helloWorldBacking.name} autoSubmit=true valueChangeListener=#{helloWorldBacking.changeMethod} / Then, implement the changeMethod in the backing bean: public void changeMethod( ValueChangeEvent event ) { System.out.println( Change method called! ); } Now, test the page by entering a value into the test field and then tabbing away from it. This will fire the field to be submitted. In your console, you should see the Change method called! message appearing--this behaves as expected. To reproduce the invalid behavior with a subform, alter index.jspx slightly, by wrapping the inputText (or its containing component) in a tr:subform tag. Reloading the page and performing the test again, you should no longer see the Change method called! message. This behavior appears to be the same for any component set to autoSubmit. After digging into the code somewhat, it appears that the subform is unaware that the inputText component has changed and so it does not run its children through the necessary phases. The root of this symptom actually relates to a lot of other problems with the subform tag. For example, using the subform to isolate regions for validation does not work at all due to this issue, because validations are not processed and model values are not updated for the components in the subform. Since I'm a new Trinidad user, I don't really know how this should be reported. I did sign up for JIRA, but I'm not sure what the severity of the issue should be. Also, it would be reassuring if someone else can reproduce this, that would verify that it's not just some problem with my machine / setup. Thanks, --David __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: Using Trinidad with Facelet Bug
i got another error. You know what is this? 2007-04-24 18:46:30,848 DEBUG UserCounterListener.attributeAdded - event.name: javax.faces.request.charset Apr 24, 2007 6:46:31 PM com.sun.facelets.FaceletViewHandler * handleRenderException* SEVERE: Error Rendering View[/underwriting.xhtml] *java.lang.NullPointerException*: Text must not be null. at org.apache.myfaces.shared_tomahawk.renderkit.html.HtmlResponseWriterImpl.writeText (*HtmlResponseWriterImpl.java:395*) at org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.AccessKeyUtils.renderAccessKeyText (*AccessKeyUtils.java:92*) at org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.AccessKeyUtils.renderAccessKeyText (*AccessKeyUtils.java:110*) at org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.GoLinkRenderer.encodeBegin (*GoLinkRenderer.java:111*) at org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.CommandLinkRenderer.encodeBegin (*CommandLinkRenderer.java:110*) at org.apache.myfaces.trinidad.render.CoreRenderer.encodeBegin(* CoreRenderer.java:185*) at org.apache.myfaces.trinidadinternal.renderkit.htmlBasic.HtmlCommandLinkRenderer.encodeEnd (*HtmlCommandLinkRenderer.java:68*) at javax.faces.component.UIComponentBase.encodeEnd(* UIComponentBase.java:536*) at org.apache.myfaces.custom.datascroller.HtmlDataScrollerRenderer.renderFacet( *HtmlDataScrollerRenderer.java:295*) at org.apache.myfaces.custom.datascroller.HtmlDataScrollerRenderer.renderScroller (*HtmlDataScrollerRenderer.java:237*) at org.apache.myfaces.custom.datascroller.HtmlDataScrollerRenderer.encodeEnd(* HtmlDataScrollerRenderer.java:202*) at javax.faces.component.UIComponentBase.encodeEnd(* UIComponentBase.java:536*) at org.apache.myfaces.shared_impl.renderkit.RendererUtils.renderChild(* RendererUtils.java:442*) at org.apache.myfaces.shared_impl.renderkit.html.HtmlGridRendererBase.renderChildren (*HtmlGridRendererBase.java:216*) at org.apache.myfaces.shared_impl.renderkit.html.HtmlGridRendererBase.encodeEnd (*HtmlGridRendererBase.java:98*) at javax.faces.component.UIComponentBase.encodeEnd(* UIComponentBase.java:536*) at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(* ComponentSupport.java:252*) at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(* ComponentSupport.java:249*) at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(* ComponentSupport.java:249*) at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(* ComponentSupport.java:249*) at com.sun.facelets.FaceletViewHandler.renderView(* FaceletViewHandler.java:573*) at org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(* ViewHandlerImpl.java:181*) at org.apache.myfaces.lifecycle.LifecycleImpl.render(* LifecycleImpl.java:384*) at javax.faces.webapp.FacesServlet.service(*FacesServlet.java:138*) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter( *ApplicationFilterChain.java:237*) at org.apache.catalina.core.ApplicationFilterChain.doFilter(* ApplicationFilterChain.java:157*) at halo.webapp.filter.JAMonServletFilter.doFilterInternal(* JAMonServletFilter.java:65*) at org.springframework.web.filter.OncePerRequestFilter.doFilter(* OncePerRequestFilter.java:75*) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter( *ApplicationFilterChain.java:186*) at org.apache.catalina.core.ApplicationFilterChain.doFilter(* ApplicationFilterChain.java:157*) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(* FilterChainProxy.java:264*) at org.acegisecurity.intercept.web.FilterSecurityInterceptor.invoke( *FilterSecurityInterceptor.java:107*) at org.acegisecurity.intercept.web.FilterSecurityInterceptor.doFilter(* FilterSecurityInterceptor.java:72*) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(* FilterChainProxy.java:274*) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(* ExceptionTranslationFilter.java:110*) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(* FilterChainProxy.java:274*) at org.acegisecurity.wrapper.SecurityContextHolderAwareRequestFilter.doFilter(* SecurityContextHolderAwareRequestFilter.java:81*) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(* FilterChainProxy.java:274*) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(* AbstractProcessingFilter.java:217*) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(* FilterChainProxy.java:274*) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(* HttpSessionContextIntegrationFilter.java:229*) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(* FilterChainProxy.java:274*) at