[ https://issues.jboss.org/browse/FORGE-617?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-617: --------------------------------------- Are you sure this is not a App server issue ? Can you provide a test case showing that Forge should be doing that ? thanks -- 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

[ https://issues.jboss.org/browse/FORGE-617?page=com.atlassian.jira.plugin.... ] Luca Masini commented on FORGE-617: ----------------------------------- I'm not sure, but I tried it also under TomEE with the same effect. I think that the "this" object under JBoss is also the EJB, something not true for other App Server. I solved this way: 1) Letting the EJB class implements the Converter: @Named @Stateful @ConversationScoped public class ItemBean implements Serializable, Converter { ... ... 2) Moving the two implementation into the top level EJB class: @Override public Object getAsObject(FacesContext context, UIComponent component, String value) { return ItemBean.this.entityManager.find(Item.class, Long.valueOf(value)); } @Override public String getAsString(FacesContext context, UIComponent component, Object value) { if (value == null) { return ""; } return String.valueOf(((Item) value).getId()); } Of course I needed to change the reference inside the .xhtml file: <h:selectOneMenu converter="#{itemBean}" ... > This way the scaffolded creating page works under WLS and TomEE. -- 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

[ https://issues.jboss.org/browse/FORGE-617?page=com.atlassian.jira.plugin.... ] Luca Masini updated FORGE-617: ------------------------------ Component/s: (was: Java EE APIs) -- 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

[ https://issues.jboss.org/browse/FORGE-617?page=com.atlassian.jira.plugin.... ] Luca Masini commented on FORGE-617: ----------------------------------- My fault, I never updated this issue with the comments on the forge-dev mailing list. With Richard we've done some experiments, because he thinks (and I'm with him) that things must be done in a simple way without using strange tricks or utility classes. We tried with FacesConverter but he noticed that a weird bug that will be fixed in JSF 2.2 doesn't allow us to have a global converter for every domain object. Then we tried with a ManagedBean and an injected EntityManager, but also this way we was not in the right direction, principally because the injected EM is not the EXTENED one linked to the SFSB. At this point we think that a good solution can be to have a findById method inside the EJB (may be we can modify the retrieve method for that) and use the Session Context to call the right bean. In almost-pseudo code: @Resource SessionContext sessionContext; public Converter getConverter() { final GroupBean ejbProxy = sessionContext.getBusinessObject(GroupBean.class); return new Converter() { @Override public Object getAsObject(FacesContext context, UIComponent component, String value) { return ejbProxy.findById(Long.valueOf(value)); } @Override public String getAsString(FacesContext context, UIComponent component, Object value) { if (value == null) { return ""; } return String.valueOf(((Group) value).getId()); } }; } What do you think ?? -- 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

[ https://issues.jboss.org/browse/FORGE-617?page=com.atlassian.jira.plugin.... ] Richard Kennard commented on FORGE-617: --------------------------------------- Luca has been very patient in exhausting lots of possibilities! He and I think this is the best mix of simplicity/compatibility to work on all app servers. The JSF 2.2 bug we need fixed is here: http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-763. This would make the code a *lot* nicer. Pull request opened: https://github.com/forge/core/pull/187 -- 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

[ https://issues.jboss.org/browse/FORGE-617?page=com.atlassian.jira.plugin.... ] Richard Kennard commented on FORGE-617: --------------------------------------- Luca could you please test? All unit tests/integration tests pass, but they don't try with WebLogic/TomEE. -- 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

[ https://issues.jboss.org/browse/FORGE-617?page=com.atlassian.jira.plugin.... ] Luca Masini edited comment on FORGE-617 at 8/9/12 3:22 PM: ----------------------------------------------------------- Sure, but I need a repository where I can upload two artifacts: 1) WebLogic 12c 2) weblogic-maven-plugin These are officially supported by Oracle, but they don't upload in any repository. I got them in my local Nexus but it is not visible outside my Intranet. Any suggestion ? was (Author: luca.masini): Sure, but I need a repository where I can upload two artifact: 1) WebLogic 12c 2) weblogic-maven-plugin These are officially supported by Oracle, but they don't upload in any repository. I got them in my local Nexus but is not visible outside my Intranet. Any suggestion ? -- 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

[ https://issues.jboss.org/browse/FORGE-617?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-617: ---------------------------------- Fix Version/s: 1.0.7.Final (was: 1.0.6.Final) -- 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

[ https://issues.jboss.org/browse/FORGE-617?page=com.atlassian.jira.plugin.... ] Luca Masini commented on FORGE-617: ----------------------------------- Any news for this issue ?? There is a public Maven repo where I can upload those artifacts ? -- 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

[ https://issues.jboss.org/browse/FORGE-617?page=com.atlassian.jira.plugin.... ] Luca Masini commented on FORGE-617: ----------------------------------- We need a public repository, but we a bit scared about licenses. I open a Service Request to Oracle (I own the rights to do that) and they answered that we can upload WLS and wls-maven-plugin on any repository that do "automatic testing". I also checked the online license when you download WLS: http://www.oracle.com/technetwork/licenses/wls-dev-license-1703567.html but may be my english is too basic to understand it :( What do you think ? Can we proceed ?? Or should we skip testing with WLS ??? -- 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

[ https://issues.jboss.org/browse/FORGE-617?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-617: --------------------------------------- Create another JIRA about this and let's close this one if it's ok. We can discuss that in the next Forge meeting -- 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