August 2011 - forge-issues - Jboss List Archives

[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: ---------------------------------------------- Ok. The distribution is working again, you're good to go. > 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="dataTableRowAction" 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 WidgetBuilder 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, 8 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: ---------------------------------------------- Actually there's a very important question that I need to ask you... not that it's related or influential at all to this situation... Why on earth are you using IE8? (Though I'm glad you are at this moment.) > 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="dataTableRowAction" 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 WidgetBuilder 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-288) Forge XML parser should return its own Node type, not shrinkwrap

by Lincoln Baxter III (JIRA)

Forge XML parser should return its own Node type, not shrinkwrap ---------------------------------------------------------------- Key: SEAMFORGE-288 URL: https://issues.jboss.org/browse/SEAMFORGE-288 Project: Seam Forge Issue Type: Enhancement Components: Parsers / File Manipulation Affects Versions: 1.0.0.Beta1 Reporter: Lincoln Baxter III -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
1
0 / 0

[JBoss JIRA] Commented: (SEAMFORGE-194) PersistencePlugin should provide ability to configure data-sources for each Persistence Container

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-194?page=com.atlassian.jira.plu... ] Lincoln Baxter III commented on SEAMFORGE-194: ---------------------------------------------- Currently forge does not know which container is being targeted. IMO, this is better because you don't really want to couple yourself to an appserver if you can help it when building apps. > PersistencePlugin should provide ability to configure data-sources for each Persistence Container > ------------------------------------------------------------------------------------------------- > > Key: SEAMFORGE-194 > URL: https://issues.jboss.org/browse/SEAMFORGE-194 > Project: Seam Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.0.0.Alpha3 > Reporter: Lincoln Baxter III > > So people do not need to do things like: > 1. Create $JBOSS_HOME/server/default/deploy/mysql-ds.xml > 2. Download and install the driver into $JBOSS_HOME/server/default/lib/my-driver.jar -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (SEAMFORGE-147) JPA settings not correct in persistence.xml

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-147?page=com.atlassian.jira.plu... ] Lincoln Baxter III closed SEAMFORGE-147. ---------------------------------------- Resolution: Done Done. > JPA settings not correct in persistence.xml > ------------------------------------------- > > Key: SEAMFORGE-147 > URL: https://issues.jboss.org/browse/SEAMFORGE-147 > Project: Seam Forge > Issue Type: Bug > Components: Java EE APIs > Reporter: Paul Bakker > Assignee: Lincoln Baxter III > Fix For: 1.0.0.Beta2 > > > With the following command the generated settings in persistence.xml are not correct. This might also be the case for other databases and settings, but I didn't test that yet. > {code} > persistence setup --provider HIBERNATE --container JBOSS_AS6 --database MYSQL_INNODB --jndiDataSource java:demo > {code} > It sets the datasource to: java:/DefaultDS (should be java:demo) > It sets the hibernate dialect to: org.hibernate.dialect.HSQLDialect (which should be MySQL5InnoDBDialect) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Assigned: (SEAMFORGE-147) JPA settings not correct in persistence.xml

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-147?page=com.atlassian.jira.plu... ] Lincoln Baxter III reassigned SEAMFORGE-147: -------------------------------------------- Assignee: Lincoln Baxter III (was: Paul Bakker) > JPA settings not correct in persistence.xml > ------------------------------------------- > > Key: SEAMFORGE-147 > URL: https://issues.jboss.org/browse/SEAMFORGE-147 > Project: Seam Forge > Issue Type: Bug > Components: Java EE APIs > Reporter: Paul Bakker > Assignee: Lincoln Baxter III > Fix For: 1.0.0.Beta2 > > > With the following command the generated settings in persistence.xml are not correct. This might also be the case for other databases and settings, but I didn't test that yet. > {code} > persistence setup --provider HIBERNATE --container JBOSS_AS6 --database MYSQL_INNODB --jndiDataSource java:demo > {code} > It sets the datasource to: java:/DefaultDS (should be java:demo) > It sets the hibernate dialect to: org.hibernate.dialect.HSQLDialect (which should be MySQL5InnoDBDialect) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (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 updated SEAMFORGE-275: -------------------------------------- Description: 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="dataTableRowAction" 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 WidgetBuilder 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? was: 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="dataTableRowAction" 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? > 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="dataTableRowAction" 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 WidgetBuilder 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] Updated: (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 updated SEAMFORGE-275: -------------------------------------- Description: 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="dataTableRowAction" 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? was: 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? > 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="dataTableRowAction" 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] Closed: (SEAMFORGE-247) --database parameter for persistence setup cause null error

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-247?page=com.atlassian.jira.plu... ] Lincoln Baxter III closed SEAMFORGE-247. ---------------------------------------- Assignee: Lincoln Baxter III Fix Version/s: 1.0.0.Beta2 Resolution: Done > --database parameter for persistence setup cause null error > ----------------------------------------------------------- > > Key: SEAMFORGE-247 > URL: https://issues.jboss.org/browse/SEAMFORGE-247 > Project: Seam Forge > Issue Type: Bug > Components: Shell > Affects Versions: 1.0.0.Alpha4 > Environment: MacOSX > java -version > java version "1.6.0_26" > Java(TM) SE Runtime Environment (build 1.6.0_26-b03-384-10M3425) > Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02-384, mixed mode) > Reporter: Bill Meyer > Assignee: Lincoln Baxter III > Fix For: 1.0.0.Beta2 > > > On a newly created Seam Forge project, execute the following: > persistence setup --provider HIBERNATE --container JBOSS_AS7 --database MYSQL > And end up with the following (with 'set VERBOSE true' previously executed): > [ForgeTest] ForgeTest $ persistence setup --provider HIBERNATE --container JBOSS_AS7 --database MYSQL > ***ERROR*** [persistence setup] null > org.jboss.forge.shell.exceptions.CommandExecutionException > at org.jboss.forge.shell.command.Execution.perform(Execution.java:149) > at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:125) > at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:63) > at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:696) > at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:512) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48) > at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125) > at org.jboss.forge.shell.org$jboss$weld$bean-classpath-ManagedBean-org$jboss$forge$shell$ShellImpl[@javax$enterprise$context$ApplicationScoped()]{org$jboss$forge$shell$ShellImpl$commandHolder[@javax$inject$Inject()]$org$jboss$forge$shell$ShellImpl$environment[@javax$inject$Inject()]$org$jboss$forge$shell$ShellImpl$fshRuntime[@javax$inject$Inject()]$org$jboss$forge$shell$ShellImpl$manager[@javax$inject$Inject()]$org$jboss$forge$shell$ShellImpl$parameters[@javax$inject$Inject()@org$jboss$weld$environment$se$bindings$Parameters()]$org$jboss$forge$shell$ShellImpl$postStartup[@javax$inject$Inject()]$org$jboss$forge$shell$ShellImpl$projectContext[@javax$inject$Inject()]$org$jboss$forge$shell$ShellImpl$promptTypeConverter[@javax$inject$Inject()]$org$jboss$forge$shell$ShellImpl$resourceFactory[@javax$inject$Inject()]$org$jboss$forge$shell$ShellImpl$shellConfig[@javax$inject$Inject()]$org$jboss$forge$shell$ShellImpl$shutdown[@javax$inject$Inject()]$org$jboss$forge$shell$ShellImpl$doShell(org$jboss$forge$shell$events$AcceptUserInput[@javax$enterprise$event$Observes(during=IN_PROGRESS,notifyObserver=ALWAYS)])$org$jboss$forge$shell$ShellImpl$init(org$jboss$forge$shell$events$Startup[@javax$enterprise$event$Observes(during=IN_PROGRESS,notifyObserver=ALWAYS)],org$jboss$forge$shell$completer$PluginCommandCompleter)$org$jboss$forge$shell$ShellImpl$teardown(org$jboss$forge$shell$events$Shutdown[@javax$enterprise$event$Observes(during=IN_PROGRESS,notifyObserver=ALWAYS)],javax$enterprise$event$Event<org$jboss$forge$shell$events$PreShutdown>)$}_$$_WeldClientProxy.doShell(org$jboss$weld$bean-classpath-ManagedBean-org$jboss$forge$shell$ShellImpl[@javax$enterprise$context$ApplicationScoped()]{org$jboss$forge$shell$ShellImpl$commandHolder[@javax$inject$Inject()]$org$jboss$forge$shell$ShellImpl$environment[@javax$inject$Inject()]$org$jboss$forge$shell$ShellImpl$fshRuntime[@javax$inject$Inject()]$org$jboss$forge$shell$ShellImpl$manager[@javax$inject$Inject()]$org$jboss$forge$shell$ShellImpl$parameters[@javax$inject$Inject()@org$jboss$weld$environment$se$bindings$Parameters()]$org$jboss$forge$shell$ShellImpl$postStartup[@javax$inject$Inject()]$org$jboss$forge$shell$ShellImpl$projectContext[@javax$inject$Inject()]$org$jboss$forge$shell$ShellImpl$promptTypeConverter[@javax$inject$Inject()]$org$jboss$forge$shell$ShellImpl$resourceFactory[@javax$inject$Inject()]$org$jboss$forge$shell$ShellImpl$shellConfig[@javax$inject$Inject()]$org$jboss$forge$shell$ShellImpl$shutdown[@javax$inject$Inject()]$org$jboss$forge$shell$ShellImpl$doShell(org$jboss$forge$shell$events$AcceptUserInput[@javax$enterprise$event$Observes(during=IN_PROGRESS,notifyObserver=ALWAYS)])$org$jboss$forge$shell$ShellImpl$init(org$jboss$forge$shell$events$Startup[@javax$enterprise$event$Observes(during=IN_PROGRESS,notifyObserver=ALWAYS)],org$jboss$forge$shell$completer$PluginCommandCompleter)$org$jboss$forge$shell$ShellImpl$teardown(org$jboss$forge$shell$events$Shutdown[@javax$enterprise$event$Observes(during=IN_PROGRESS,notifyObserver=ALWAYS)],javax$enterprise$event$Event<org$jboss$forge$shell$events$PreShutdown>)$}_$$_WeldClientProxy.java) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305) > at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) > at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) > at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299) > at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188) > at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:270) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:253) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:222) > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:632) > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:619) > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:613) > at org.jboss.forge.shell.Bootstrap$2.run(Bootstrap.java:93) > at java.lang.Thread.run(Thread.java:680) > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.forge.shell.command.Execution.perform(Execution.java:144) > ... 30 more > Caused by: java.lang.NullPointerException > at org.jboss.forge.shell.ShellMessages.info(ShellMessages.java:47) > at org.jboss.forge.spec.javaee.jpa.container.JavaEEDefaultContainer.setupConnection(JavaEEDefaultContainer.java:52) > at org.jboss.forge.spec.javaee.jpa.PersistencePlugin.setup(PersistencePlugin.java:181) > ... 35 more > No difference if I specify JBOSS_AS6 as the container. The problem occurs when the --database argument is added. Even tried a fully qualified set of arguments: > persistence setup --provider HIBERNATE --container JBOSS_AS7 --database MYSQL5_INNODB --jndiDataSource jdbc/MusicDBDS --jdbcURL "jdbc:mysql://localhost:3306/examples" --jdbcUsername examples --jdbcPassword examples --named MusicDBPU > and no luck. -- 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. ---------------------------------------- Resolution: Done > 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2011