September 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3395) GWT Example not working

by Dan Mihai Ile (JIRA)

GWT Example not working ----------------------- Key: JBSEAM-3395 URL: https://jira.jboss.org/jira/browse/JBSEAM-3395 Project: Seam Issue Type: Bug Components: GWT Affects Versions: 2.1.0.BETA1, 2.0.3.CR1, 2.0.2.SP1 Environment: Windows XP, Java 5, jboss-4.2.3.GA, apache-ant-1.7.1 Reporter: Dan Mihai Ile I am trying to deploy the examples/remote/gwt example using ant, but jboss AS gives an error on deploying. I understand that GWT support is porr in seam but at least make sure that the example works out of the box. Note that I didn't recompile anything, just deployed using "ant.bat deploy" Maybe there is an easy fix for this, if someone could check I would appreciate. Thank you. Begining of error log: 15:50:39,531 INFO [EARDeployer] Init J2EE application: file:/C:/Tools/programe/ jboss-4.2.3.GA/server/default/deploy/jboss-seam-gwt.ear 15:51:12,796 WARN [ServiceController] Problem creating service jboss.j2ee:servi ce=EJB3,module=jboss-seam-gwt.jar java.lang.NullPointerException at org.jboss.ejb3.security.JaccHelper.initialiseJacc(JaccHelper.java:73) at org.jboss.ejb3.Ejb3JmxDeployment.createPolicyConfiguration(Ejb3JmxDep loyment.java:53) ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3173) Additional @Create documentation

by Mikael (JIRA)

Additional @Create documentation -------------------------------- Key: JBSEAM-3173 URL: https://jira.jboss.org/jira/browse/JBSEAM-3173 Project: Seam Issue Type: Task Components: Documentation Issues Affects Versions: 2.1.0.A1, 2.0.3.CR1, 2.0.2.SP1, 2.0.2.GA, 2.0.2.CR2, 2.0.2.CR1, 2.0.1.GA Reporter: Mikael Please add a little documentation saying that @Create annotated methods executes in the render response phase and thus Seam exception handling (navigation to error pages) won't work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2455) seam-gen dev profile does not read "WEB-INF/dev" directory for class files on Weblogic 10

by Jay Balunas (JIRA)

seam-gen dev profile does not read "WEB-INF/dev" directory for class files on Weblogic 10 ------------------------------------------------------------------------------------------ Key: JBSEAM-2455 URL: http://jira.jboss.com/jira/browse/JBSEAM-2455 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.1.GA Environment: RHEL 5 x86 JDK 1.6.0_02 Weblogic 10.3.TP Reporter: Jay Balunas A WAR application generated by seam-gen and modified as described in the new "Weblogic" chapter in the reference guide does not pick up the class files that deployed into the "WEB-INF/dev" directory. The easiest way to describe duplicating it is to refer to the reference guide chapter. What the user sees is that no matter what is entered into the login page it is a failed login - with no errors in the logs If the class files in the "WEB-INF/dev" directory are moved to the "WEB-INF/classes" directory the login page behaves as expected. Note the weblogic chapter to the reference guide is currently being finalized and I will note when it is checked in. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1508) Decouple framework from JSF

by Gavin King (JIRA)

Decouple framework from JSF --------------------------- Key: JBSEAM-1508 URL: http://jira.jboss.com/jira/browse/JBSEAM-1508 Project: JBoss Seam Issue Type: Feature Request Components: Framework Reporter: Gavin King Assigned To: Gavin King Fix For: 1.3.0.BETA2 We have dependencies there that we don't really need. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

4
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2680) conversationId doc change

by Samuel Mendenhall (JIRA)

conversationId doc change ------------------------- Key: JBSEAM-2680 URL: http://jira.jboss.com/jira/browse/JBSEAM-2680 Project: JBoss Seam Issue Type: Bug Components: Documentation Issues Reporter: Samuel Mendenhall Priority: Minor references to conversationId=#{conversation.id} in the docs should be changed to #{manager.conversationIdParameter}=#{conversation.id}, ex. http://docs.jboss.com/seam/2.0.1.GA/reference/en/html_single/#d0e4594 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-541) ConversationEntry reports the wrong description

by Norman Richards (JIRA)

ConversationEntry reports the wrong description ----------------------------------------------- Key: JBSEAM-541 URL: http://jira.jboss.com/jira/browse/JBSEAM-541 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.1.0.CR1 Reporter: Norman Richards Assigned To: Gavin King The linked forum post shows one example of this bug, though it is not directly the issue the poster is complaining of. Using the forum application as a guide, start a conversation and then start a nested conversation. End the nested conversation. The description of the parent conversation in the converstion list on will be incorrect. (it will have the name of the current conversation that just ended) This happens because of the following code: public String getDescription() { if ( isCurrent() ) { String desc = Conversation.instance().description; if (desc!=null) return desc; } return description; } public boolean isCurrent() { Manager manager = Manager.instance(); if ( manager.isLongRunningConversation() ) { return id.equals( manager.getCurrentConversationId() ); } else if ( manager.isNestedConversation() ) { return id.equals( manager.getParentConversationId() ); } else { return false; } } The parent conversation entry is considered "current". (isLongRunning() is false and isNestedConversation() is true) Because of this, the ConversationEntry description is ignored in favor of Conversation.instance().description. (Again, Conversation.instance(), is the nested conversation that just ended) Subsequent requests display the conversation description correctly since they are done in the context of the correct conversation. The isNestedConversation() check looks to be the source of the problem. I can't figure out what case that would make sense for. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3369) No active conversation context (natural conversations)

by Arron Ferguson (JIRA)

No active conversation context (natural conversations) ------------------------------------------------------ Key: JBSEAM-3369 URL: https://jira.jboss.org/jira/browse/JBSEAM-3369 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.0.3.CR1 Environment: Linux Ubuntu 7.10, Intel Pentium 4, 3GHz, 1 GB RAM, Tomcat 6.0.16 Reporter: Arron Ferguson Priority: Blocker Natural conversations and rules in your pages.xml file are suppose to enforce navigation rules whereby if the user types a URL from a previous state of the conversation (or uses a bookmark), the rules set in the pages.xml should work and redirect the user without exceptions being generated. Setup Instructions: Please see https://jira.jboss.org/jira/browse/JBSEAM-3368 and use the exact same files. If you want to see the conversation actually existing then add the following to the template.xhtml file: <ui:insert name="conversationlist"> <h:dataTable value="#{conversationList}" var="entry" rendered="#{not empty conversationList}"> <h:column> <f:facet name="header">Workspace</f:facet> <h:commandLink action="#{entry.select}" value="#{entry.description}"/> <h:outputText value="[current]" rendered="#{entry.current}"/> </h:column> <h:column> <f:facet name="header">Activity</f:facet> <h:outputText value="#{entry.startDatetime}"> <f:convertDateTime type="time" pattern="hh:mm a"/> </h:outputText> <h:outputText value=" - "/> <h:outputText value="#{entry.lastDatetime}"> <f:convertDateTime type="time" pattern="hh:mm a"/> </h:outputText> </h:column> <h:column> <f:facet name="header">Action</f:facet> <h:commandButton action="#{entry.select}" value="#{msg.Switch}"/> <h:commandButton action="#{entry.destroy}" value="#{msg.Destroy}"/> </h:column> </h:dataTable> </ui:insert> Which will indeed display a conversation in memory. Steps to reproduce bug: 1.) Start web app inside of Tomcat 6 2.) using your browser, click on the buttons and take yourself all the way up to register4.xhtml but *do not* click on the Seam link labeled "back to home". Instead type in your browser's URL text field register1.xhtml. What happens is that the register1.xhtml page shows and an exception is generated: java.lang.IllegalStateException: No active conversation context The correct response should be for the Seam app to redirect the user back to the register3.xhtml page (based on the pages.xml rules, again see https://jira.jboss.org/jira/browse/JBSEAM-3368 for more details). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2669) Document @AutoCreate overriding @Observer(create = false)

by Christian Bauer (JIRA)

Document @AutoCreate overriding @Observer(create = false) --------------------------------------------------------- Key: JBSEAM-2669 URL: http://jira.jboss.com/jira/browse/JBSEAM-2669 Project: JBoss Seam Issue Type: Task Components: Documentation Issues Reporter: Christian Bauer I'm not even sure this is semantically correct but a component with @AutoCreate is always instantiated when it is referenced. The documentation only mentions the "when @In does not specify create=true" case. However, if you have an @AutoCreate component and it has an @Observer method, setting @Observer(create = false) has no effect, the component will be instantiated when the event occurs. We definitely need to document this or discuss it further. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3461) Documentation for installing embedded JBoss needs to be updated

by Shane Bryzak (JIRA)

Documentation for installing embedded JBoss needs to be updated --------------------------------------------------------------- Key: JBSEAM-3461 URL: https://jira.jboss.org/jira/browse/JBSEAM-3461 Project: Seam Issue Type: Task Components: Documentation Issues Affects Versions: 2.1.0.CR1 Reporter: Shane Bryzak Priority: Blocker Fix For: 2.1.0.GA The instructions for installing Embedded JBoss in the configuration chapter fail under the latest version of Tomcat (6.0.18). Specifically, adding the EmbeddedJBossBootstrapListener to server.xml causes the server to crash while starting, and adding the WebinfScanner listener to context.xml causes exceptions during startup. For reference, here's a link to the installation instructions on the JBoss Embedded wiki: http://wiki.jboss.org/wiki/Tomcat6.0.x?action=e&windowstate=normal&mode=view -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2716) Glassfish Integration reference guide chapter

by Jay Balunas (JIRA)

Glassfish Integration reference guide chapter --------------------------------------------- Key: JBSEAM-2716 URL: http://jira.jboss.com/jira/browse/JBSEAM-2716 Project: JBoss Seam Issue Type: Task Components: Platform interoperability Affects Versions: 2.1.0.A1, 2.0.1.GA Reporter: Jay Balunas Assigned To: Jay Balunas Priority: Minor Following the existing interop reference guide chapters create a glassfish integration chapter. Likely version: glassfish v2ur1-b09d References: http://weblogs.java.net/blog/bleonard/archive/2006/06/running_jboss_s_1.html http://weblogs.java.net/blog/rogerk/archive/2006/05/seam_on_glassfi.html http://www.coffeecrew.org/docs/html/netbeansFaceletsSeamEjb3/netbeansFace... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues September 2008