[JBoss JIRA] (RF-13060) Issue in initializing the list of selected items in a Picklist
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13060?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-13060.
--------------------------------
Resolution: Done
Removed usage of HashSet, removing the need for data objects to implement hashCode
> Issue in initializing the list of selected items in a Picklist
> --------------------------------------------------------------
>
> Key: RF-13060
> URL: https://issues.jboss.org/browse/RF-13060
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 4.3.2
> Reporter: Jean-Noel Colin
> Assignee: Brian Leathem
> Fix For: 4.3.4, 5-Tracking
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> A picklist uses two list of items: a list of available items and a list of selected items. If this second list has to be initialized, it has to contain the same object instances as those in the available items. So both lists can't be built from two separate DB queries, since they would refer to distinct objects, and in this case, the list of selected items would always be empty. Upon request of Brian Leathem, I have created this JIRA issue after providing a sample application that illustrates the problem.
> /Items.xhtml is the frontend
> Item is the element to be displayed in the list
> ItemBean is the managed bean that builds the available and selected lists
> ItemConverter is the converter
>
> As you see in ItemBean's constructor, depending on the way I build the selectedList, it gets displayed properly or not
>
> the project is using ivy for dependencies, and is build using ant tasks
> ant resolve-dependencies
> ant package
>
> should build the war file in /dist
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (RF-13046) EDT in EDT: when @frozenColumns is equal to number of columns then there is no vertical scroller in EDT
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13046?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-13046.
--------------------------------
Fix Version/s: (was: 5-Tracking)
Resolution: Done
Ignored the frozenColumns attribute when frozenColumns >= total number of columns
> EDT in EDT: when @frozenColumns is equal to number of columns then there is no vertical scroller in EDT
> -------------------------------------------------------------------------------------------------------
>
> Key: RF-13046
> URL: https://issues.jboss.org/browse/RF-13046
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> GlassFish Server Open Source Edition 3.1.2.2
> Java(TM) SE Runtime Environment 1.7.0_21-b11 @ Linux
> Firefox 18.0 @ Linux x86_64
> Reporter: Jiří Štefek
> Assignee: Brian Leathem
> Fix For: 4.3.4
>
> Attachments: EDTinEDTmaxFrozenColumnsNoScrollers.png, EDTinEDTmaxFrozenColumnsScrollersAfterColumnReposition.png, EDTinEDTWhenNoFrozenColsOrWhenFrozenColsLesserThanMaxCols.png
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> EDT(1st) in EDT(2nd), when @frozenColumns (of 1st) is equal to number of columns (of 1st), then there is no vertical scroller in EDT (1st). But when you reorganize the columns (of 1st), the scroller and the 'footer' facet appears (1st).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (RF-13017) richfaces-bom 4.3.2.Final, JSF-API 2.1.0 not compatible
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13017?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-13017.
--------------------------------
Resolution: Done
Changed the JSF API version numbers to match the JSF impl versions
> richfaces-bom 4.3.2.Final, JSF-API 2.1.0 not compatible
> -------------------------------------------------------
>
> Key: RF-13017
> URL: https://issues.jboss.org/browse/RF-13017
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 4.3.2
> Reporter: Himanshu Bhardwaj
> Assignee: Brian Leathem
> Fix For: 4.3.4
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> In the bom of RichFaces, the version of JSF-API being used is
> {code}
> <version.com.sun.faces.jsf-api>2.1.0</version.com.sun.faces.jsf-api>
> {code}
>
> but the version of JSF-IMPL put in use is:
> {code}
> <version.org.jboss.javax.faces.jsf-impl>2.1.19-jbossorg-1</version.org.jboss.javax.faces.jsf-impl>
> {code}
>
> Both the version don't seem to go together. Got the following stack-trace:
>
> {code}
> SEVERE: ContainerBase.addChild: start:
> org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/abc]]
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
> at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
> at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
> at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655)
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.NullPointerException
> at com.sun.faces.config.InitFacesContext.cleanupInitMaps(InitFacesContext.java:281)
> at com.sun.faces.config.InitFacesContext.<init>(InitFacesContext.java:107)
> at com.sun.faces.config.FacesInitializer.onStartup(FacesInitializer.java:115)
> at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5274)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> ... 11 more
>
>
> May 21, 2013 11:30:43 AM org.apache.catalina.startup.HostConfig deployWAR
> SEVERE: Error deploying web application archive F:\DevTools\apache-tomcat-7.0.34\webapps\abc.war
> java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/abc]]
> at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:904)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
> at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
> at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655)
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> {code}
>
> I had to manually delete the 2.1.0 jsf-api jar from the war file and copy 2.1.19, with this I was able to bypass this error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (RF-13017) richfaces-bom 4.3.2.Final, JSF-API 2.1.0 not compatible
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13017?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13017:
------------------------------------
Similarly, the JBoss JSF API should be changed to remain consistent:
_version.org.jboss.spec.javax.faces.jboss-jsf-api_2.1_spec_: 2.0.7.Final -> 2.1.19.1.Final
{code}
<dependency>
<groupId>org.jboss.spec.javax.faces</groupId>
<artifactId>jboss-jsf-api_2.1_spec</artifactId>
<version>2.1.19.1.Final</version>
</dependency>
{code}
http://search.maven.org/#artifactdetails%7Corg.jboss.spec.javax.faces%7Cj...
> richfaces-bom 4.3.2.Final, JSF-API 2.1.0 not compatible
> -------------------------------------------------------
>
> Key: RF-13017
> URL: https://issues.jboss.org/browse/RF-13017
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 4.3.2
> Reporter: Himanshu Bhardwaj
> Assignee: Brian Leathem
> Fix For: 4.3.4
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> In the bom of RichFaces, the version of JSF-API being used is
> {code}
> <version.com.sun.faces.jsf-api>2.1.0</version.com.sun.faces.jsf-api>
> {code}
>
> but the version of JSF-IMPL put in use is:
> {code}
> <version.org.jboss.javax.faces.jsf-impl>2.1.19-jbossorg-1</version.org.jboss.javax.faces.jsf-impl>
> {code}
>
> Both the version don't seem to go together. Got the following stack-trace:
>
> {code}
> SEVERE: ContainerBase.addChild: start:
> org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/abc]]
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
> at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
> at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
> at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655)
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.NullPointerException
> at com.sun.faces.config.InitFacesContext.cleanupInitMaps(InitFacesContext.java:281)
> at com.sun.faces.config.InitFacesContext.<init>(InitFacesContext.java:107)
> at com.sun.faces.config.FacesInitializer.onStartup(FacesInitializer.java:115)
> at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5274)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> ... 11 more
>
>
> May 21, 2013 11:30:43 AM org.apache.catalina.startup.HostConfig deployWAR
> SEVERE: Error deploying web application archive F:\DevTools\apache-tomcat-7.0.34\webapps\abc.war
> java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/abc]]
> at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:904)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
> at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
> at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655)
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> {code}
>
> I had to manually delete the 2.1.0 jsf-api jar from the war file and copy 2.1.19, with this I was able to bypass this error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (RF-13017) richfaces-bom 4.3.2.Final, JSF-API 2.1.0 not compatible
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13017?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13017:
------------------------------------
{code}
<dependency>
<groupId>com.sun.faces</groupId>
<artifactId>jsf-api</artifactId>
<version>2.1.19</version>
</dependency>
{code}
http://search.maven.org/#artifactdetails%7Ccom.sun.faces%7Cjsf-api%7C2.1....
> richfaces-bom 4.3.2.Final, JSF-API 2.1.0 not compatible
> -------------------------------------------------------
>
> Key: RF-13017
> URL: https://issues.jboss.org/browse/RF-13017
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 4.3.2
> Reporter: Himanshu Bhardwaj
> Assignee: Brian Leathem
> Fix For: 4.3.4
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> In the bom of RichFaces, the version of JSF-API being used is
> {code}
> <version.com.sun.faces.jsf-api>2.1.0</version.com.sun.faces.jsf-api>
> {code}
>
> but the version of JSF-IMPL put in use is:
> {code}
> <version.org.jboss.javax.faces.jsf-impl>2.1.19-jbossorg-1</version.org.jboss.javax.faces.jsf-impl>
> {code}
>
> Both the version don't seem to go together. Got the following stack-trace:
>
> {code}
> SEVERE: ContainerBase.addChild: start:
> org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/abc]]
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
> at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
> at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
> at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655)
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.NullPointerException
> at com.sun.faces.config.InitFacesContext.cleanupInitMaps(InitFacesContext.java:281)
> at com.sun.faces.config.InitFacesContext.<init>(InitFacesContext.java:107)
> at com.sun.faces.config.FacesInitializer.onStartup(FacesInitializer.java:115)
> at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5274)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> ... 11 more
>
>
> May 21, 2013 11:30:43 AM org.apache.catalina.startup.HostConfig deployWAR
> SEVERE: Error deploying web application archive F:\DevTools\apache-tomcat-7.0.34\webapps\abc.war
> java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/abc]]
> at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:904)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
> at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
> at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655)
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> {code}
>
> I had to manually delete the 2.1.0 jsf-api jar from the war file and copy 2.1.19, with this I was able to bypass this error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (RF-13106) Quickstart names in the POM files are not consistent and often are not clear
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13106?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-13106.
--------------------------------
Resolution: Done
Changed the maven pom file for the ks and hw quickstarts to use the correctly formatted name
> Quickstart names in the POM files are not consistent and often are not clear
> ----------------------------------------------------------------------------
>
> Key: RF-13106
> URL: https://issues.jboss.org/browse/RF-13106
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Reporter: Sande Gilda
> Assignee: Brian Leathem
> Fix For: 4.3.4
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> Quickstart names in the pom.xml files are not consistent and often are too generic and not clear which quickstart is building.
> When you run `mvn clean install '-Pdefault,!complex-dependencies'` from the root directory of the quickstarts, it often is not clear which quickstart is compiling. Some start with "JBoss AS Quickstarts" and some do not. Some use the quickstart folder name in the description, some don't.
> As described in the CONTRIBUTING.md file, the <name> in the quickstart pom.xml file should follow the template:
> JBoss <target-product> Quickstart: <quickstart-name> < - optional-subfolder-name> where target-product is the Target Product metadata specified in the README.md file, quickstart-name is the quickstart folder name, and optional-subfolder-name is the name of any nested subfolder containing a pom.xml file.
> JDF-430 addressed the EAP and WFK quickstarts. The root build not displays the following. Note the RichFaces and JDG quickstarts need to be updated.
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] JBoss EAP Quickstart: bean-validation
> [INFO] JBoss EAP Quickstart: bmt
> [INFO] JBoss WFK Quickstart: cdi-add-interceptor-binding
> [INFO] JBoss EAP Quickstart: cdi-alternative
> [INFO] JBoss EAP Quickstart: cdi-decorator
> [INFO] JBoss EAP Quickstart: cdi-interceptors
> [INFO] JBoss EAP Quickstart: cdi-injection
> [INFO] JBoss EAP Quickstart: cdi-portable-extension
> [INFO] JBoss EAP Quickstart: cdi-stereotype
> [INFO] JBoss EAP Quickstart: cdi-veto
> [INFO] JBoss WFK Quickstart: deltaspike-authorization
> [INFO] JBoss WFK Quickstart: deltaspike-beanbuilder
> [INFO] JBoss WFK Quickstart: deltaspike-beanmanagerprovider
> [INFO] JBoss WFK Quickstart: deltaspike-deactivatable
> [INFO] JBoss WFK Quickstart: deltaspike-exception-handling
> [INFO] JBoss WFK Quickstart: deltaspike-helloworld-jms
> [INFO] JBoss WFK Quickstart: deltaspike-partialbean-basic
> [INFO] JBoss WFK Quickstart: deltaspike-partialbean-advanced
> [INFO] JBoss WFK Quickstart: deltaspike-projectstage
> [INFO] JBoss EAP Quickstart: ejb-asynchronous
> [INFO] JBoss EAP Quickstart: ejb-asynchronous - ejb
> [INFO] JBoss EAP Quickstart: ejb-asynchronous - client
> [INFO] JBoss EAP Quickstart: ejb-in-ear
> [INFO] JBoss EAP Quickstart: ejb-in-ear - ejb
> [INFO] JBoss EAP Quickstart: ejb-in-ear - web
> [INFO] JBoss EAP Quickstart: ejb-in-ear - ear
> [INFO] JBoss EAP Quickstart: ejb-in-war
> [INFO] JBoss EAP Quickstart: ejb-remote - server-side
> [INFO] JBoss EAP Quickstart: ejb-remote - client
> [INFO] JBoss EAP Quickstart: ejb-remote
> [INFO] JBoss EAP Quickstart: ejb-security
> [INFO] JBoss EAP Quickstart: ejb-security-plus
> [INFO] JBoss EAP Quickstart: ejb-security-interceptors
> [INFO] JBoss EAP Quickstart: ejb-throws-exception
> [INFO] JBoss EAP Quickstart: ejb-throws-exception - ejb-api
> [INFO] JBoss EAP Quickstart: ejb-throws-exception - ejb
> [INFO] JBoss EAP Quickstart: ejb-throws-exception - web
> [INFO] JBoss EAP Quickstart: ejb-throws-exception - ear
> [INFO] JBoss EAP Quickstart: ejb-multi-server
> [INFO] JBoss EAP Quickstart: ejb-multi-server - app-one
> [INFO] JBoss EAP Quickstart: ejb-multi-server - app-one - ejb
> [INFO] JBoss EAP Quickstart: ejb-multi-server - app-one - ear
> [INFO] JBoss EAP Quickstart: ejb-multi-server - app-two
> [INFO] JBoss EAP Quickstart: ejb-multi-server - app-two - ejb
> [INFO] JBoss EAP Quickstart: ejb-multi-server - app-two - ear
> [INFO] JBoss EAP Quickstart: ejb-multi-server - app-main
> [INFO] JBoss EAP Quickstart: ejb-multi-server - app-main - ejb
> [INFO] JBoss EAP Quickstart: ejb-multi-server - app-main - web
> [INFO] JBoss EAP Quickstart: ejb-multi-server - app-main - ear
> [INFO] JBoss EAP Quickstart: ejb-multi-server - app-web
> [INFO] JBoss EAP Quickstart: ejb-multi-server - client
> [INFO] JBoss EAP Quickstart: greeter
> [INFO] JBoss EAP Quickstart: greeter-spring
> [INFO] JBoss EAP Quickstart: helloworld
> [INFO] JBoss WFK Quickstart: helloworld-errai
> [INFO] JBoss WFK Quickstart: helloworld-gwt
> [INFO] JBoss WFK Quickstart: helloworld-html5
> [INFO] JBoss EAP Quickstart: helloworld-jms
> [INFO] JBoss EAP Quickstart: helloworld-mdb
> [INFO] JBoss EAP Quickstart: helloworld-osgi
> [INFO] JBoss EAP Quickstart: helloworld-rs
> [INFO] JBoss EAP Quickstart: helloworld-singleton
> [INFO] JBoss EAP Quickstart: helloworld-ws
> [INFO] JBoss EAP Quickstart: hibernate3
> [INFO] JBoss EAP Quickstart: hibernate4
> [INFO] CarMart Single Node (No Cluster)
> [INFO] Transactional CarMart
> [INFO] JBoss AS Quickstarts: JBoss Data Grid HelloWorld
> [INFO] HotRod Endpoint Example
> [INFO] Memcached Endpoint Example
> [INFO] REST Endpoint Example
> [INFO] JBoss Data Grid Quickstart Parent
> [INFO] JBoss EAP Quickstart: kitchensink
> [INFO] JBoss WFK Quickstart: kitchensink-angularjs
> [INFO] JBoss WFK Quickstart: kitchensink-backbone
> [INFO] JBoss WFK Quickstart: kitchensink-deltaspike
> [INFO] JBoss EAP Quickstart: kitchensink-ear
> [INFO] JBoss EAP Quickstart: kitchensink-ear - ejb
> [INFO] JBoss EAP Quickstart: kitchensink-ear - web
> [INFO] JBoss EAP Quickstart: kitchensink-ear - ear
> [INFO] JBoss WFK Quickstart: kitchensink-html5-mobile
> [INFO] JBoss EAP Quickstart: kitchensink-jsp
> [INFO] JBoss EAP Quickstart: kitchensink-ml
> [INFO] JBoss EAP Quickstart: kitchensink-ml-ear
> [INFO] JBoss EAP Quickstart: kitchensink-ml-ear - ejb
> [INFO] JBoss EAP Quickstart: kitchensink-ml-ear - web
> [INFO] JBoss EAP Quickstart: kitchensink-ml-ear - ear
> [INFO] JBoss EAP Quickstart: kitchensink-spring-asyncrequestmapping
> [INFO] JBoss EAP Quickstart: kitchensink-spring-basic
> [INFO] JBoss EAP Quickstart: kitchensink-spring-controller
> [INFO] JBoss EAP Quickstart: kitchensink-spring-matrixvariables
> [INFO] JBoss EAP Quickstart: kitchensink-spring-springmvctest
> [INFO] JBoss EAP Quickstart: log4j
> [INFO] JBoss EAP Quickstart: logging
> [INFO] JBoss EAP Quickstart: logging-tools
> [INFO] JBoss EAP Quickstart: mail
> [INFO] JBoss EAP Quickstart: numberguess
> [INFO] JBoss EAP Quickstart: payment-cdi-event
> [INFO] JBoss EAP Quickstart: picketlink-authentication-http-basic
> [INFO] JBoss EAP Quickstart: picketlink-authentication-http-digest
> [INFO] JBoss EAP Quickstart: petclinic-spring
> [INFO] JBoss EAP Quickstart: picketlink-authentication-idm-jsf
> [INFO] JBoss EAP Quickstart: picketlink-authentication-idm-multi-tenancy
> [INFO] JBoss EAP Quickstart: picketlink-authentication-jsf
> [INFO] JBoss EAP Quickstart: picketlink-authentication-rs-endpoint
> [INFO] JBoss EAP Quickstart: picketlink-authentication-two-factor
> [INFO] JBoss EAP Quickstart: picketlink-authorization-idm-jpa
> [INFO] JBoss EAP Quickstart: picketlink-authorization-rs-rbac
> [INFO] JBoss WFK Quickstart: picketlink-deltaspike-authorization
> [INFO] JBoss AS Quickstarts: Hello world with JSF front end
> [INFO] JBoss AS Quickstarts: Kitchensink-rf
> [INFO] JBoss AS Quickstarts: RichFaces Bean Validation
> [INFO] JBoss EAP Quickstart: servlet-async
> [INFO] JBoss EAP Quickstart: servlet-filterlistener
> [INFO] JBoss EAP Quickstart: servlet-security
> [INFO] JBoss EAP Quickstart: shopping-cart
> [INFO] JBoss EAP Quickstart: shopping-cart - server
> [INFO] JBoss EAP Quickstart: shopping-cart - client
> [INFO] JBoss WFK Quickstart: shrinkwrap-resolver
> [INFO] JBoss EAP Quickstart: tasks
> [INFO] JBoss EAP Quickstart: tasks-jsf
> [INFO] JBoss EAP Quickstart: tasks-rs
> [INFO] JBoss EAP Quickstart: temperature-converter
> [INFO] JBoss EAP Quickstart: wicket-ear
> [INFO] JBoss EAP Quickstart: wicket-ear - ejb
> [INFO] JBoss EAP Quickstart: wicket-ear - war
> [INFO] JBoss EAP Quickstart: wicket-ear - ear
> [INFO] JBoss EAP Quickstart: wicket-war
> [INFO] JBoss EAP Quickstart: xml-dom4j
> [INFO] JBoss EAP Quickstart: xml-jaxp
> [INFO] JBoss EAP Quickstart: cmt
> [INFO] JBoss EAP Quickstart: jts
> [INFO] JBoss EAP Quickstart: jts - application-component-2
> [INFO] JBoss EAP Quickstart: jts - application-component-1
> [INFO] JBoss EAP Quickstart: jta-crash-rec
> [INFO] JBoss EAP Quickstart: wsat-simple
> [INFO] JBoss EAP Quickstart: wsba-coordinator-completion-simple
> [INFO] JBoss EAP Quickstart: wsba-participant-completion-simple
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (RF-13119) kitchensink-rf test-ds.xml does not use a unique datasource JNDI name
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13119?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-13119.
--------------------------------
Resolution: Done
Changed the test datasource to be unique across the JDF quickstarts.
> kitchensink-rf test-ds.xml does not use a unique datasource JNDI name
> ---------------------------------------------------------------------
>
> Key: RF-13119
> URL: https://issues.jboss.org/browse/RF-13119
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Reporter: Sande Gilda
> Assignee: Brian Leathem
> Fix For: 4.3.4
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The richfaces-quickstarts/kitchensink-rf/src/test/resources/test-ds.xml uses the same datasource JNDI name and connection URL that the kitchensink quickstart test file uses:
> <datasource jndi-name="java:jboss/datasources/KitchensinkQuickstartTestDS"
> <connection-url>jdbc:h2:mem:kitchensink-quickstart-test;DB_CLOSE_DELAY=-1</connection-url>
> This should be changed to a unique name, for example:
> <datasource jndi-name="java:jboss/datasources/KitchensinkrfQuickstartTestDS"
> <connection-url>jdbc:h2:mem:kitchensink-rf-quickstart-test;DB_CLOSE_DELAY=-1</connection-url>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months