October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBPORTAL-875) Test WSRP implementation conformance

by Chris Laprun (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-875?page=all ] Chris Laprun updated JBPORTAL-875: ---------------------------------- Description: Improve the WSRP tests to deliver best in class WSRP implementation. (was: Run WSRPtk to test implementation conformance.) > Test WSRP implementation conformance > ------------------------------------ > > Key: JBPORTAL-875 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-875 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal WSRP > Affects Versions: 2.4 Final > Reporter: Chris Laprun > Assigned To: Chris Laprun > Priority: Critical > Fix For: 2.6.Alpha1 > > Time Spent: 2 days > Remaining Estimate: 0 minutes > > Improve the WSRP tests to deliver best in class WSRP implementation. -- 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

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-402) Seam CRUD framework

by Gavin King (JIRA)

Seam CRUD framework ------------------- Key: JBSEAM-402 URL: http://jira.jboss.com/jira/browse/JBSEAM-402 Project: JBoss Seam Issue Type: Feature Request Components: Framework Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1 A new framework for simple crud-based applications, as a set of built in components that can be reused either via extension or configuration. -- 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

18 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBSEAM-310) Global setting for no-conversation-view-id

by Gavin King (JIRA)

Global setting for no-conversation-view-id ------------------------------------------ Key: JBSEAM-310 URL: http://jira.jboss.com/jira/browse/JBSEAM-310 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1 Currently, no-conversation-view-id is too fine grained. We should allow a global setting to be used as the default if none is defined in pages.xml or the pageflow. Note that another issue asks for no-conversation-view-id at pageflow level instead of node level. This is also useful. -- 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

18 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBSEAM-368) STATELESS component injection rules are not intuitive/undocumented

by Christian Bauer (JIRA)

STATELESS component injection rules are not intuitive/undocumented ------------------------------------------------------------------ Key: JBSEAM-368 URL: http://jira.jboss.com/jira/browse/JBSEAM-368 Project: JBoss Seam Issue Type: Bug Reporter: Christian Bauer Priority: Minor This is probably a non-issue, so feel free to ignore. It took me a while to figure out why this works: @In(create=true) MyStatelessComponent myComponent; but this doesn't: @In MyStatelessComponent myComponent; It was easy to figure out that it apparently is required, but from looking at the documentation this isn't clear. I also found it difficult to think about "creation of a component" when it is already there in the stateless EJB pool. I checked the code and there is some consistency in the internal logic, of course. Users however might read the docs and say: "@In searches all contexts hierarchically, so it should find myComponent in STATELESS, because Seam logged that binding on startup." Also, attempts to remove the create="true" with @In(value = "myComponent", scope = ScopeType.STATELESS) MyStatelessComponent myComponent; resulted in JNDI lookup("myComponent"), which makes not much sense and returns null. I suggest we add something to the documentation about lookup/injection of stateless components (I'm not sure if I'm 100% right about this, otherwise I would have added it). Side note, I found the following additional debug logging lines in Component.java very helpful during development: private Object getInstanceToInject(In in, String name, Object bean, boolean enforceRequired) { Object result; if ( name.startsWith("#") ) { log.debug("Searching for injection variable with value binding expression: " + name); FacesContext facesCtx = FacesContext.getCurrentInstance(); Application application = facesCtx.getApplication(); result = application.createValueBinding(name).getValue(facesCtx); } else if (in.scope()==ScopeType.UNSPECIFIED) { log.debug("Searching hierarchically for injection variable in all scopes: " + name); result = getInstance(name, in.create()); } else { if ( in.create() ) { throw new IllegalArgumentException( "cannot combine create=true with explicit scope on @In: " + getAttributeMessage(name) ); } log.debug("Searching for injection variable in scope: " + name + ", scope: " + in.scope()); result = in.scope().getContext().get(name); } if (result==null && enforceRequired && in.required()) { throw new RequiredException( "In attribute requires value for component: " + getAttributeMessage(name) ); } else { return result; } } -- 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

18 years, 3 months

2
4
0 / 0

[JBoss JIRA] Updated: (JBSEAM-95) Have Seam handle "concurrent access to stateful bean" exceptions elegantly.

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-95?page=all ] Gavin King updated JBSEAM-95: ----------------------------- Priority: Minor (was: Major) Now that we have the single-concurrent-request-per-conversation model, this is basically solved. We could still implement the idea in this, but it is no longer as useful/important. > Have Seam handle "concurrent access to stateful bean" exceptions elegantly. > --------------------------------------------------------------------------- > > Key: JBSEAM-95 > URL: http://jira.jboss.com/jira/browse/JBSEAM-95 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Affects Versions: 1.0 beta 1 > Reporter: Ryan Dewell > Priority: Minor > > See the rejected issue: EJBTHREE-313 > This can be duplicated in the demo app (or any other app), by simply double clicking a commandLink/commandButton. If Seam could detect the double postback, and just ignore one of them, that would be ideal. Perhaps JSF 1.2 provides better postback detection handling? -- 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

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBSEAM-183) Catch concurrent submits

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-183?page=all ] Gavin King closed JBSEAM-183. ----------------------------- Fix Version/s: 1.1 Resolution: Done > Catch concurrent submits > ------------------------ > > Key: JBSEAM-183 > URL: http://jira.jboss.com/jira/browse/JBSEAM-183 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Reporter: Gavin King > Assigned To: Gavin King > Priority: Critical > Fix For: 1.1 > > Attachments: SyncFacesContextFactoryImpl.java, SyncFacesContextImpl.java > > > We need to put some proper thought into handling of concurrent requests in a conversation, and also duplicate form submission (second is probably not an issue, 'cos conversations mainly solve the problem). At least we should catch the standard exception that EJB3 throws from concurrent access to an SFSB. -- 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

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBSEAM-183) Catch concurrent submits

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-183?page=all ] Gavin King reopened JBSEAM-183: ------------------------------- > Catch concurrent submits > ------------------------ > > Key: JBSEAM-183 > URL: http://jira.jboss.com/jira/browse/JBSEAM-183 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Reporter: Gavin King > Assigned To: Gavin King > Priority: Critical > Fix For: 1.1 > > Attachments: SyncFacesContextFactoryImpl.java, SyncFacesContextImpl.java > > > We need to put some proper thought into handling of concurrent requests in a conversation, and also duplicate form submission (second is probably not an issue, 'cos conversations mainly solve the problem). At least we should catch the standard exception that EJB3 throws from concurrent access to an SFSB. -- 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

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-335) NullPointerException if user quikcly decides to click a different link or button before the page renders

by Keith Naas (JIRA)

NullPointerException if user quikcly decides to click a different link or button before the page renders -------------------------------------------------------------------------------------------------------- Key: JBSEAM-335 URL: http://jira.jboss.com/jira/browse/JBSEAM-335 Project: JBoss Seam Issue Type: Bug Environment: Seam 1.0.1.GA. JBoss 4.0.4, Windows XP, Facelets, MyFaces, Hibernate Reporter: Keith Naas When a user is on one of our screens, they can decide to click a link before the next page loads. Sometimes, when this do this quickly enough, it causes a NullPointerException in Manager.touchConversationStack at line 181. Somehow, the currentConversationEntry is null and it breaks when it executes getCurrentConversationEntry().touch(). I tried unsuccessfully to duplicate this scenario on the Hotel and DVD Store demos hosted on JBoss. Stack Trace java.lang.NullPointerException at org.jboss.seam.core.Manager.touchConversationStack(Manager.java:181) at org.jboss.seam.core.Manager.storeConversation(Manager.java:368) at org.jboss.seam.jsf.AbstractSeamPhaseListener.storeAnyConversationContext(AbstractSeamPhaseListener.java:69) at org.jboss.seam.jsf.SeamStateManager.saveSerializedView(SeamStateManager.java:45) at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:578) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:384) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:138) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) ..... -- 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

18 years, 3 months

2
5
0 / 0

[JBoss JIRA] Closed: (JBSEAM-183) Catch concurrent submits

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-183?page=all ] Gavin King closed JBSEAM-183. ----------------------------- Resolution: Done Fixed, but in a diff way. :) > Catch concurrent submits > ------------------------ > > Key: JBSEAM-183 > URL: http://jira.jboss.com/jira/browse/JBSEAM-183 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Reporter: Gavin King > Assigned To: Gavin King > Priority: Critical > Attachments: SyncFacesContextFactoryImpl.java, SyncFacesContextImpl.java > > > We need to put some proper thought into handling of concurrent requests in a conversation, and also duplicate form submission (second is probably not an issue, 'cos conversations mainly solve the problem). At least we should catch the standard exception that EJB3 throws from concurrent access to an SFSB. -- 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

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAOP-284) Error accessing overridden fields

by Kabir Khan (JIRA)

Error accessing overridden fields --------------------------------- Key: JBAOP-284 URL: http://jira.jboss.com/jira/browse/JBAOP-284 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kabir Khan Fix For: 2.0 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=89343 -- 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

18 years, 3 months

1
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2006