August 2011 - forge-issues - Jboss List Archives

[JBoss JIRA] Reopened: (SEAMFORGE-271) persistence setup creates incorrect persistence.xml for JBoss AS 7

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-271?page=com.atlassian.jira.plu... ] Lincoln Baxter III reopened SEAMFORGE-271: ------------------------------------------ Assignee: Lincoln Baxter III assignee > persistence setup creates incorrect persistence.xml for JBoss AS 7 > ------------------------------------------------------------------ > > Key: SEAMFORGE-271 > URL: https://issues.jboss.org/browse/SEAMFORGE-271 > Project: Seam Forge > Issue Type: Bug > Components: Builtin Plugins > Affects Versions: 1.0.0.Alpha4 > Environment: Mac OS X 10.5, Java 1.6.26, forge 1.0.0.Alpha4, JBoss AS 7 full > Reporter: Philip Reimer > Assignee: Lincoln Baxter III > Labels: datasource, jndi, persistence.xml > Fix For: 1.0.0.Beta1 > > > Executing "persistence setup --provider HIBERNATE --container JBOSS_AS7" creates persistence.xml with the following jata-datasource: "<jta-data-source>java:/H2DS</jta-data-source>" > But AS7 default standalone configuration has "<datasource jndi-name="java:jboss/datasources/ExampleDS" enabled="true" use-java-context="true" pool-name="H2DS">" > This leads to the following exception during deployment: > "[org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "forgetest.war" was rolled back with failure message {"Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"forgetest.war#forge-default\" missing [ jboss.naming.context.java.H2DS ]"]}" > After changing persistence.xml to contain "<jta-data-source>java:jboss/datasources/ExampleDS</jta-data-source>" instead the project successfully compiles. > BTW: "<property name="hibernate.dialect" value="org.hibernate.dialect.HSQLDialect"/>" also does not seem to be the "right" dialect for H2 database. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (SEAMFORGE-271) persistence setup creates incorrect persistence.xml for JBoss AS 7

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-271?page=com.atlassian.jira.plu... ] Lincoln Baxter III closed SEAMFORGE-271. ---------------------------------------- Fix Version/s: 1.0.0.Beta1 Resolution: Done Resolved in Beta1 - Thanks for reporting! > persistence setup creates incorrect persistence.xml for JBoss AS 7 > ------------------------------------------------------------------ > > Key: SEAMFORGE-271 > URL: https://issues.jboss.org/browse/SEAMFORGE-271 > Project: Seam Forge > Issue Type: Bug > Components: Builtin Plugins > Affects Versions: 1.0.0.Alpha4 > Environment: Mac OS X 10.5, Java 1.6.26, forge 1.0.0.Alpha4, JBoss AS 7 full > Reporter: Philip Reimer > Labels: datasource, jndi, persistence.xml > Fix For: 1.0.0.Beta1 > > > Executing "persistence setup --provider HIBERNATE --container JBOSS_AS7" creates persistence.xml with the following jata-datasource: "<jta-data-source>java:/H2DS</jta-data-source>" > But AS7 default standalone configuration has "<datasource jndi-name="java:jboss/datasources/ExampleDS" enabled="true" use-java-context="true" pool-name="H2DS">" > This leads to the following exception during deployment: > "[org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "forgetest.war" was rolled back with failure message {"Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"forgetest.war#forge-default\" missing [ jboss.naming.context.java.H2DS ]"]}" > After changing persistence.xml to contain "<jta-data-source>java:jboss/datasources/ExampleDS</jta-data-source>" instead the project successfully compiles. > BTW: "<property name="hibernate.dialect" value="org.hibernate.dialect.HSQLDialect"/>" also does not seem to be the "right" dialect for H2 database. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Commented: (SEAMFORGE-240) Running "clear" on Forge Console hangs execution

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-240?page=com.atlassian.jira.plu... ] George Gastaldi commented on SEAMFORGE-240: ------------------------------------------- Adding a "Clear console" button on the taskbar would be nice > Running "clear" on Forge Console hangs execution > ------------------------------------------------- > > Key: SEAMFORGE-240 > URL: https://issues.jboss.org/browse/SEAMFORGE-240 > Project: Seam Forge > Issue Type: Bug > Components: JBoss Tools Integration > Environment: Windows 7 > Reporter: George Gastaldi > Assignee: Koen Aers > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Commented: (SEAMFORGE-239) Change default plugin checkout location to use the .forge/plugins-sources directory

by Rodney Russ (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-239?page=com.atlassian.jira.plu... ] Rodney Russ commented on SEAMFORGE-239: --------------------------------------- the installFromGit() method already has a checkoutDir option that defines a directory in which to clone the repository. So, I have an implementation that uses this directory if defined, otherwise it prompts with "Would you like to save the source?". If this is true, then it saves to ~/.forge/plugins-src/ otherwise it saves to a temp directory that is removed when done. All in all, there are a total of 3 possibilities: 1) User defines the repository directory 2) User wants to save, but did not supply a directory 3) User does not want to save and a temp directory is used Does this make sense? > Change default plugin checkout location to use the .forge/plugins-sources directory > ----------------------------------------------------------------------------------- > > Key: SEAMFORGE-239 > URL: https://issues.jboss.org/browse/SEAMFORGE-239 > Project: Seam Forge > Issue Type: Task > Components: Shell > Affects Versions: 1.0.0.Alpha4 > Reporter: Lincoln Baxter III > Assignee: Rodney Russ > Fix For: 1.0.0.Beta2 > > > {code}$ forge git-plugin git@github.com:repo/etc{code} > needs to use ~/.forge/plugins-sources/ instead of the /tmp directory - so that developers can hack on installed plugins more easily. > this code lives here: > https://github.com/forge/core/blob/master/shell/src/main/java/org/jboss/f... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-283) Beans plugin adds jboss dependency without <type>pom</type>

by George Gastaldi (JIRA)

Beans plugin adds jboss dependency without <type>pom</type> ----------------------------------------------------------- Key: SEAMFORGE-283 URL: https://issues.jboss.org/browse/SEAMFORGE-283 Project: Seam Forge Issue Type: Bug Reporter: George Gastaldi When running beans setup and choosing the jboss-javaee-6.0 artifact, like the following: {code:java} [forge-web] forge-web $ beans setup Wrote /powerlogic/jcompany55/workspace/forge-web/src/main/webapp/WEB-INF/beans.xml ***SUCCESS*** Installed [forge.spec.cdi] successfully. Do you want to add CDI dependencies? 1 - [org.jboss.spec:jboss-javaee-6.0] 2 - [javax.enterprise:cdi-api] 3 - [no] ? Choose an option by typing the number of the selection: 1 Which version of org.jboss.spec:jboss-javaee-6.0 do you want to install? 1 - [org.jboss.spec:jboss-javaee-6.0:1.0.0.Beta4] 2 - [org.jboss.spec:jboss-javaee-6.0:1.0.0.Beta5] 3 - [org.jboss.spec:jboss-javaee-6.0:1.0.0.Beta6] 4 - [org.jboss.spec:jboss-javaee-6.0:1.0.0.Beta7] 5 - [org.jboss.spec:jboss-javaee-6.0:1.0.0.CR1] 6 - [org.jboss.spec:jboss-javaee-6.0:1.0.0.Final] 7 - [org.jboss.spec:jboss-javaee-6.0:2.0.0.Beta1] 8 - [org.jboss.spec:jboss-javaee-6.0:2.0.0.CR1] 9 - [org.jboss.spec:jboss-javaee-6.0:2.0.0.Final] ? Choose an option by typing the number of the selection: 6 ? Should the scope be 'provided'? [Y/n] Added org.jboss.spec:jboss-javaee-6.0:1.0.0.Final:provided {code} The following <dependency> is placed in pom.xml: {code:xml} <dependencies> <dependency> <groupId>org.jboss.spec</groupId> <artifactId>jboss-javaee-6.0</artifactId> <version>1.0.0.Final</version> <scope>provided</scope> </dependency> </dependencies> {code} However, it is missing the <type>pom</type> element. It should read: {code:xml} <dependencies> <dependency> <groupId>org.jboss.spec</groupId> <artifactId>jboss-javaee-6.0</artifactId> <version>1.0.0.Final</version>  <type>pom</type> <scope>provided</scope> </dependency> </dependencies> {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
2
0 / 0

[JBoss JIRA] Commented: (SEAMFORGE-275) Scaffolded entities are not editable on Internet Explorer 8

by Richard Kennard (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-275?page=com.atlassian.jira.plu... ] Richard Kennard commented on SEAMFORGE-275: ------------------------------------------- No. Metawidget correctly applies the z-index to the XHTML output, but it still doesn't work in IE8. Even if it did, it's a very brittle solution that isn't likely to work on all browsers IMHO. I think Option 1 (above) would be much better. It's almost as easy as what you've done. Instead of... <m:metawidget value="#{entity}" readOnly="true" style="z-index: -50;"/> ...just put... <m:metawidget value="#{entity}" readOnly="true" rendererType="simple"/> That should work in all browsers. You'll need a bit of CSS to push the spans apart a little, but that's it. > Scaffolded entities are not editable on Internet Explorer 8 > ----------------------------------------------------------- > > Key: SEAMFORGE-275 > URL: https://issues.jboss.org/browse/SEAMFORGE-275 > Project: Seam Forge > Issue Type: Bug > Reporter: Richard Kennard > > The entity list produced by scaffold/.../list.xhtml is not editable on IE 8. Probably because the table tags produced by Metawidget are considered to be 'above' (in z-index) the anchor tag, and stop the anchor tag being clicked. > A few possible workarounds: > 1. Change the Metawidget tag to be... > <m:metawidget value="#{entity}" readOnly="true" rendererType="simple"/> > ...the 'simple' renderer will output spans, not table tags, and so the link is still clickable. You may want a little CSS to space the table tags apart. > 2. Change the Metawidget tag to be... > <m:metawidget value="#{customerBean.list}"> > <f:param name="dataTableRowEditAction" value="customerBean.load"/> > </m:metawidget> > Now Metawidget will render the collection as a DataTable, with a extra column for a 'load' action. It will need a little help to do this. Specifically: a) CustomerBean.getList will need to return a ListDataModel, so that CustomerBean.load can use .getRowData to determine which row was clicked. This is standard JSF behaviour. b) Customer will need either a decent .toString (for a single column table) or some required fields like @Column(nullable = false) getName() so that Metawidget can choose which fields are 'summary' fields for use in table columns > 3. Add in a custom Metawidget renderer to render the list just the way you want it > 4. Tweak the z-index order in the CSS, although this may lead to further browser incompatibilities > Probably 1) is easiest for now? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Commented: (SEAMFORGE-275) Scaffolded entities are not editable on Internet Explorer 8

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-275?page=com.atlassian.jira.plu... ] Lincoln Baxter III commented on SEAMFORGE-275: ---------------------------------------------- Richard, could you please try this again from trunk? Let me know if it works with the Z-Index fix. I think that's possibly the easiest for now. Folks can tweak if they need. Thanks, Lincoln > Scaffolded entities are not editable on Internet Explorer 8 > ----------------------------------------------------------- > > Key: SEAMFORGE-275 > URL: https://issues.jboss.org/browse/SEAMFORGE-275 > Project: Seam Forge > Issue Type: Bug > Reporter: Richard Kennard > > The entity list produced by scaffold/.../list.xhtml is not editable on IE 8. Probably because the table tags produced by Metawidget are considered to be 'above' (in z-index) the anchor tag, and stop the anchor tag being clicked. > A few possible workarounds: > 1. Change the Metawidget tag to be... > <m:metawidget value="#{entity}" readOnly="true" rendererType="simple"/> > ...the 'simple' renderer will output spans, not table tags, and so the link is still clickable. You may want a little CSS to space the table tags apart. > 2. Change the Metawidget tag to be... > <m:metawidget value="#{customerBean.list}"> > <f:param name="dataTableRowEditAction" value="customerBean.load"/> > </m:metawidget> > Now Metawidget will render the collection as a DataTable, with a extra column for a 'load' action. It will need a little help to do this. Specifically: a) CustomerBean.getList will need to return a ListDataModel, so that CustomerBean.load can use .getRowData to determine which row was clicked. This is standard JSF behaviour. b) Customer will need either a decent .toString (for a single column table) or some required fields like @Column(nullable = false) getName() so that Metawidget can choose which fields are 'summary' fields for use in table columns > 3. Add in a custom Metawidget renderer to render the list just the way you want it > 4. Tweak the z-index order in the CSS, although this may lead to further browser incompatibilities > Probably 1) is easiest for now? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-276) Missing context path on error pages

by George Gastaldi (JIRA)

Missing context path on error pages ----------------------------------- Key: SEAMFORGE-276 URL: https://issues.jboss.org/browse/SEAMFORGE-276 Project: Seam Forge Issue Type: Bug Components: Scaffold Reporter: George Gastaldi The error pages 404.html and 500.html are missing the context path on the CSS and images declaration. When an error 404 occurs, the page shown misses these resources. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
1
0 / 0

[JBoss JIRA] Closed: (SEAMFORGE-274) Pagination in Scaffolding can only go two pages deep

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-274?page=com.atlassian.jira.plu... ] Lincoln Baxter III closed SEAMFORGE-274. ---------------------------------------- Assignee: Lincoln Baxter III Fix Version/s: 1.0.0.Beta2 Resolution: Done > Pagination in Scaffolding can only go two pages deep > ---------------------------------------------------- > > Key: SEAMFORGE-274 > URL: https://issues.jboss.org/browse/SEAMFORGE-274 > Project: Seam Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.0.0.Beta1 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 1.0.0.Beta2 > > > http://seamframework.org/162255.lace > this pagination code of https://github.com/forge/core/blob/master/scaffold-metawidget/src/main/re..., > {code}pagination = new PaginationHelper<xyz.class>(10){code} > will get executed every time next button is pressed (as the backing bean is requestscope) hence will not be able to navigate to 3 rd page, this should be bug in my opinion. I have given short term work around for this, let see what experts have to say. > {code}public PaginationHelper<@{entity.getName()}> getPagination(){ > if (pagination == null){ > pagination = new PaginationHelper<@{entity.getName()}>(10){ > @Override > public int getItemsCount() { > return count((a){entity.getName()}.class); > } > @Override > public List<@{entity.getName()}> createPageDataModel(){ > return new ArrayList<@{entity.getName()}>(findAll((a){entity.getName()}.class, > getPageFirstItem(), getPageSize() )); > } > }; > } > return pagination; > }{code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Commented: (SEAMFORGE-274) Pagination in Scaffolding can only go two pages deep

by Liu Jianhong (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-274?page=com.atlassian.jira.plu... ] Liu Jianhong commented on SEAMFORGE-274: ---------------------------------------- BackingBean.jv should annotated by "@SessionScoped" DatasourceProducer annotated by "@ConversationScoped" also have some bugs so I use transaction-type="RESOURCE_LOCAL" > Pagination in Scaffolding can only go two pages deep > ---------------------------------------------------- > > Key: SEAMFORGE-274 > URL: https://issues.jboss.org/browse/SEAMFORGE-274 > Project: Seam Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.0.0.Beta1 > Reporter: Lincoln Baxter III > > http://seamframework.org/162255.lace > this pagination code of https://github.com/forge/core/blob/master/scaffold-metawidget/src/main/re..., > {code}pagination = new PaginationHelper<xyz.class>(10){code} > will get executed every time next button is pressed (as the backing bean is requestscope) hence will not be able to navigate to 3 rd page, this should be bug in my opinion. I have given short term work around for this, let see what experts have to say. > {code}public PaginationHelper<@{entity.getName()}> getPagination(){ > if (pagination == null){ > pagination = new PaginationHelper<@{entity.getName()}>(10){ > @Override > public int getItemsCount() { > return count((a){entity.getName()}.class); > } > @Override > public List<@{entity.getName()}> createPageDataModel(){ > return new ArrayList<@{entity.getName()}>(findAll((a){entity.getName()}.class, > getPageFirstItem(), getPageSize() )); > } > }; > } > return pagination; > }{code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2011