December 2011 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-348) Update MetaWidget dependencies to not bring in metawidget-all

by Lincoln Baxter III (Commented) (JIRA)

[ https://issues.jboss.org/browse/FORGE-348?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-348: ------------------------------------------ Just for clarification, the latest release is currently SNAPSHOT. > Update MetaWidget dependencies to not bring in metawidget-all > ------------------------------------------------------------- > > Key: FORGE-348 > URL: https://issues.jboss.org/browse/FORGE-348 > Project: Forge > Issue Type: Task > Reporter: Andrew Rubinger > Assignee: Lincoln Baxter III > Fix For: 1.0.0.Alpha4 > > > We don't need MetaWidget-all, which will also bring in Spring core classes (breaking in AS7 deployments). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-348) Update MetaWidget dependencies to not bring in metawidget-all

by Richard Kennard (Commented) (JIRA)

[ https://issues.jboss.org/browse/FORGE-348?page=com.atlassian.jira.plugin.... ] Richard Kennard commented on FORGE-348: --------------------------------------- Christy, To be fair, we've spent a lot of time making sure Metawidget *is* fine for Real Life projects. And lots of Real Life projects use it in production. If there is an area where Metawidget doesn't work for you, please explain it on the Metawidget forums. I'd love to improve it for you. Having said that, Forge is not tied to Metawidget. In the latest release, Forge outputs static JSF tags with no Metawidget dependencies. Regards, Richard. > Update MetaWidget dependencies to not bring in metawidget-all > ------------------------------------------------------------- > > Key: FORGE-348 > URL: https://issues.jboss.org/browse/FORGE-348 > Project: Forge > Issue Type: Task > Reporter: Andrew Rubinger > Assignee: Lincoln Baxter III > Fix For: 1.0.0.Alpha4 > > > We don't need MetaWidget-all, which will also bring in Spring core classes (breaking in AS7 deployments). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-348) Update MetaWidget dependencies to not bring in metawidget-all

by M Chisty (Commented) (JIRA)

[ https://issues.jboss.org/browse/FORGE-348?page=com.atlassian.jira.plugin.... ] M Chisty commented on FORGE-348: -------------------------------- Using forge, it is expected that using Metawidget should be an option, not a mandatory feature. However this was found that when we use Forge to create a SEAM3 project from scratch, we must use metawidget. We have to understand the fact that Metawidget just creates some auto-generated xhtml codes from POJOs (good for simple CRUD based apps). But real life project is much more complicated. It is not always the direct table -> POJO - > xhtml mapping. What if we don't need metawidget at all, but we still want to use Forge to build up SEAM3 project using Richfcaes, JB7 etc... Do we have the option? Do we always need to use metawidget and then remove the config files (metawidget releted) manually to make our project metawidget free? > Update MetaWidget dependencies to not bring in metawidget-all > ------------------------------------------------------------- > > Key: FORGE-348 > URL: https://issues.jboss.org/browse/FORGE-348 > Project: Forge > Issue Type: Task > Reporter: Andrew Rubinger > Assignee: Lincoln Baxter III > Fix For: 1.0.0.Alpha4 > > > We don't need MetaWidget-all, which will also bring in Spring core classes (breaking in AS7 deployments). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-306) Field plugin should work on bean classes

by Lincoln Baxter III (Commented) (JIRA)

[ https://issues.jboss.org/browse/FORGE-306?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-306: ------------------------------------------ Yeah, plugin inheritance should be fine. Actually, I haven't tried that before. We should probably add some tests around this case to make sure that Forge picks up the new plugin the way it should (e.g. that the name is correct.) > Field plugin should work on bean classes > ---------------------------------------- > > Key: FORGE-306 > URL: https://issues.jboss.org/browse/FORGE-306 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.0.0.Alpha3 > Reporter: Dan Allen > > The field plugin should be available for any Java bean class. Adding the field would add the associated getters and setters (or prompt for which ones to create). > It should also be possible to add getters and setters for a field (or all fields) after the fact. > We should also support creating a constructor from fields. > This feature would drastically speed up prototyping coding (without having an IDE handy). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-306) Field plugin should work on bean classes

by Ivan St. Ivanov (Commented) (JIRA)

[ https://issues.jboss.org/browse/FORGE-306?page=com.atlassian.jira.plugin.... ] Ivan St. Ivanov commented on FORGE-306: --------------------------------------- Hi! Is it OK that a plugin extends another plugin? Or we want to definitely avoid inheritance? Cheers! Ivan > Field plugin should work on bean classes > ---------------------------------------- > > Key: FORGE-306 > URL: https://issues.jboss.org/browse/FORGE-306 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.0.0.Alpha3 > Reporter: Dan Allen > > The field plugin should be available for any Java bean class. Adding the field would add the associated getters and setters (or prompt for which ones to create). > It should also be possible to add getters and setters for a field (or all fields) after the fact. > We should also support creating a constructor from fields. > This feature would drastically speed up prototyping coding (without having an IDE handy). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-284) UOE on AS 7.0.2

by Richard Kennard (Resolved) (JIRA)

[ https://issues.jboss.org/browse/FORGE-284?page=com.atlassian.jira.plugin.... ] Richard Kennard resolved FORGE-284. ----------------------------------- Resolution: Done > UOE on AS 7.0.2 > --------------- > > Key: FORGE-284 > URL: https://issues.jboss.org/browse/FORGE-284 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 1.0.0.Beta2 > Reporter: Pete Muir > > Stuff still seems to work (maybe just a cache though?) > 19:01:28,966 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host]] (http--127.0.0.1-8080-5) Exception Processing ErrorPage[errorCode=404, location=/404.jsf]: javax.servlet.ServletException: no transaction > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:606) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at com.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:134) [rewrite-impl-servlet-1.0.0.Alpha4.jar:] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:734) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:543) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:479) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:407) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:528) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:454) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at java.lang.Thread.run(Thread.java:680) [:1.6.0_26] > Caused by: java.lang.UnsupportedOperationException: no transaction > at org.jboss.seam.transaction.NoTransaction.begin(NoTransaction.java:47) [seam-persistence-3.0.0.Final.jar:] > at org.jboss.seam.transaction.DefaultSeamTransaction.begin(DefaultSeamTransaction.java:102) [seam-persistence-3.0.0.Final.jar:] > at org.jboss.seam.transaction.Work.workInTransaction(Work.java:51) [seam-persistence-3.0.0.Final.jar:] > at org.jboss.seam.transaction.TransactionInterceptor.aroundInvoke(TransactionInterceptor.java:188) [seam-persistence-3.0.0.Final.jar:] > at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source) [:1.6.0_26] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26] > at org.jboss.interceptor.proxy.InterceptorInvocation$InterceptorMethodInvocation.invoke(InterceptorInvocation.java:72) [jboss-interceptor-core-2.0.0.Alpha3.jar:2.0.0.Alpha3] > at org.jboss.interceptor.proxy.SimpleInterceptionChain.invokeNextInterceptor(SimpleInterceptionChain.java:82) [jboss-interceptor-core-2.0.0.Alpha3.jar:2.0.0.Alpha3] > at org.jboss.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:133) [jboss-interceptor-core-2.0.0.Alpha3.jar:2.0.0.Alpha3] > at org.jboss.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:112) [jboss-interceptor-core-2.0.0.Alpha3.jar:2.0.0.Alpha3] > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:65) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at com.acme.view.-2068363872$Proxy$_$$_WeldSubclass.getItemType(-2068363872$Proxy$_$$_WeldSubclass.java) [classes:] > at com.acme.view.MemberBean$Proxy$_$$_WeldClientProxy.getItemType(MemberBean$Proxy$_$$_WeldClientProxy.java) [classes:] > at org.metawidget.forge.navigation.Navigation.getListItems(Navigation.java:47) [metawidget-forge-scaffold-1.0.0-20110922.190837-19.jar:] > at org.metawidget.forge.navigation.Navigation$Proxy$_$$_WeldClientProxy.getListItems(Navigation$Proxy$_$$_WeldClientProxy.java) [metawidget-forge-scaffold-1.0.0-20110922.190837-19.jar:] > at sun.reflect.GeneratedMethodAccessor23.invoke(Unknown Source) [:1.6.0_26] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26] > at javax.el.BeanELResolver.getValue(BeanELResolver.java:302) [jboss-el-api_2.2_spec-1.0.0.Final.jar:1.0.0.Final] > at com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at org.apache.el.parser.AstValue.getValue(AstValue.java:134) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.el.parser.AstEmpty.getValue(AstEmpty.java:45) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.el.parser.AstNot.getValue(AstNot.java:42) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:187) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:55) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.ComponentStateHelper.eval(ComponentStateHelper.java:194) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:413) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1750) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1759) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1759) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:401) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:131) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.ocpsoft.rewrite.faces.RewriteViewHandler.renderView(RewriteViewHandler.java:154) [rewrite-integration-faces-1.0.0.Alpha4.jar:] > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > ... 19 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-284) UOE on AS 7.0.2

by Richard Kennard (Commented) (JIRA)

[ https://issues.jboss.org/browse/FORGE-284?page=com.atlassian.jira.plugin.... ] Richard Kennard commented on FORGE-284: --------------------------------------- I've reworked the scoping (ConversationScoped) and transaction management (Extended PersistenceContext) of the BackingBean. This should now be resolved. > UOE on AS 7.0.2 > --------------- > > Key: FORGE-284 > URL: https://issues.jboss.org/browse/FORGE-284 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 1.0.0.Beta2 > Reporter: Pete Muir > > Stuff still seems to work (maybe just a cache though?) > 19:01:28,966 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host]] (http--127.0.0.1-8080-5) Exception Processing ErrorPage[errorCode=404, location=/404.jsf]: javax.servlet.ServletException: no transaction > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:606) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at com.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:134) [rewrite-impl-servlet-1.0.0.Alpha4.jar:] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:734) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:543) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:479) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:407) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:528) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:454) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at java.lang.Thread.run(Thread.java:680) [:1.6.0_26] > Caused by: java.lang.UnsupportedOperationException: no transaction > at org.jboss.seam.transaction.NoTransaction.begin(NoTransaction.java:47) [seam-persistence-3.0.0.Final.jar:] > at org.jboss.seam.transaction.DefaultSeamTransaction.begin(DefaultSeamTransaction.java:102) [seam-persistence-3.0.0.Final.jar:] > at org.jboss.seam.transaction.Work.workInTransaction(Work.java:51) [seam-persistence-3.0.0.Final.jar:] > at org.jboss.seam.transaction.TransactionInterceptor.aroundInvoke(TransactionInterceptor.java:188) [seam-persistence-3.0.0.Final.jar:] > at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source) [:1.6.0_26] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26] > at org.jboss.interceptor.proxy.InterceptorInvocation$InterceptorMethodInvocation.invoke(InterceptorInvocation.java:72) [jboss-interceptor-core-2.0.0.Alpha3.jar:2.0.0.Alpha3] > at org.jboss.interceptor.proxy.SimpleInterceptionChain.invokeNextInterceptor(SimpleInterceptionChain.java:82) [jboss-interceptor-core-2.0.0.Alpha3.jar:2.0.0.Alpha3] > at org.jboss.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:133) [jboss-interceptor-core-2.0.0.Alpha3.jar:2.0.0.Alpha3] > at org.jboss.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:112) [jboss-interceptor-core-2.0.0.Alpha3.jar:2.0.0.Alpha3] > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:65) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at com.acme.view.-2068363872$Proxy$_$$_WeldSubclass.getItemType(-2068363872$Proxy$_$$_WeldSubclass.java) [classes:] > at com.acme.view.MemberBean$Proxy$_$$_WeldClientProxy.getItemType(MemberBean$Proxy$_$$_WeldClientProxy.java) [classes:] > at org.metawidget.forge.navigation.Navigation.getListItems(Navigation.java:47) [metawidget-forge-scaffold-1.0.0-20110922.190837-19.jar:] > at org.metawidget.forge.navigation.Navigation$Proxy$_$$_WeldClientProxy.getListItems(Navigation$Proxy$_$$_WeldClientProxy.java) [metawidget-forge-scaffold-1.0.0-20110922.190837-19.jar:] > at sun.reflect.GeneratedMethodAccessor23.invoke(Unknown Source) [:1.6.0_26] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26] > at javax.el.BeanELResolver.getValue(BeanELResolver.java:302) [jboss-el-api_2.2_spec-1.0.0.Final.jar:1.0.0.Final] > at com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at org.apache.el.parser.AstValue.getValue(AstValue.java:134) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.el.parser.AstEmpty.getValue(AstEmpty.java:45) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.el.parser.AstNot.getValue(AstNot.java:42) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:187) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:55) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.ComponentStateHelper.eval(ComponentStateHelper.java:194) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:413) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1750) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1759) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1759) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:401) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:131) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.ocpsoft.rewrite.faces.RewriteViewHandler.renderView(RewriteViewHandler.java:154) [rewrite-integration-faces-1.0.0.Alpha4.jar:] > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > ... 19 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-393) PersistencePlugin should create Lists, not Sets, for @OneToMany

by Richard Kennard (Created) (JIRA)

PersistencePlugin should create Lists, not Sets, for @OneToMany --------------------------------------------------------------- Key: FORGE-393 URL: https://issues.jboss.org/browse/FORGE-393 Project: Forge Issue Type: Enhancement Reporter: Richard Kennard It would be cleaner for the UI if the persistence plugin could base its collections on Lists, rather than Sets. This is because JSF's built-in h:dataTable needs something with a defined ordering. It is possible to work around this in various ways, such as adding special getters to the view Bean, but I think for the sake of clear, concise code the easiest way would be to make the generated code be a List. For example: @OneToMany private List<Grocery> groceries = new ArrayList<Grocery>(); public List<Grocery> getGroceries() { return this.groceries; } public void setGroceries(final List<Grocery> groceries) { this.groceries = groceries; } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
2
0 / 0

[JBoss JIRA] (FORGE-386) PersistencePlugin needs to generate hashCode and equals based on Id

by Richard Kennard (Created) (JIRA)

PersistencePlugin needs to generate hashCode and equals based on Id ------------------------------------------------------------------- Key: FORGE-386 URL: https://issues.jboss.org/browse/FORGE-386 Project: Forge Issue Type: Enhancement Reporter: Richard Kennard Assignee: Lincoln Baxter III Domain classes generated by Forge need to override hashCode/equals if they are to be useful in a UI (among other places). This is hard to do if we know nothing about the semantics of the class, but the PersistencePlugin *does* know something: namely, the Id. The following implementation would suffice for my purposes: @Override public boolean equals(Object that) { if (this == that) { return true; } if (that == null) { return false; } if (getClass() != that.getClass()) { return false; } if (id != null) { return id.equals(((Employer) that).id); } return super.equals(that); } @Override public int hashCode() { if (id != null) { return id.hashCode(); } return super.hashCode(); } But I'm happy for other implementations too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
4
0 / 0

[JBoss JIRA] (FORGE-388) Better support for multi-modules projects in FORGE

by Serhiy V (Created) (JIRA)

Better support for multi-modules projects in FORGE -------------------------------------------------- Key: FORGE-388 URL: https://issues.jboss.org/browse/FORGE-388 Project: Forge Issue Type: Feature Request Components: Forge Build, Maven Integration, Shell Affects Versions: 1.0.0.Beta3 Environment: Any Reporter: Serhiy V By default "new-project" command creates a simple "war" project with everything inside. This is good for simple projects. But in real world scenario you will most likely would like to split your project on few modules - e.g. "common", "integration", "business" and "ui". How to do this with FORGE? Well, it's still a maven projects so you can manually edit pom.xml files and add necessary dependencies and changes. But will FORGE be able to setup JPA in "integration" module (should be packaged as jar) and use it "ui" module which should be packages as war? Same questions with other functionality like ability to have EJBs in "business" and test them with arquillian. And what about EAR support? I can't find any documentation or samples howto do this with current FORGE. List of all available commands does not return anything that can be used to break projects into modules or add existing projects to the current project as new modules. There is a FORGE-120 issue. ButI've just downloaded forge-distribution-1.0.0.Beta3.zip and there is no such functionality there. >From my point of view it is really important to support complex projects but not just simple single war projects. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

6
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues December 2011