May 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1319) s:selectDate does not work on rich:modalPanel

by Chris Sweeney (JIRA)

s:selectDate does not work on rich:modalPanel --------------------------------------------- Key: JBSEAM-1319 URL: http://jira.jboss.com/jira/browse/JBSEAM-1319 Project: JBoss Seam Issue Type: Bug Environment: OS: Mac OS X, Windows 2000 Pro Browser: Firefox, IE Reporter: Chris Sweeney Fix For: 1.2.1.GA If s:selectDate is used on a rich:modalPanel, it does not appear when the icon is clicked. This is because the z-index for the calendar div is not set. I have a patch (included below) to /org/jboss/seam/ui/resource/date/calendar.js (contained within jboss-seam-ui.jar). The patch is not as elegant as I would have liked - I would have preferred to navigate up the DOM tree from the target element and set the z-index based on where the target element lived. Unfortunately, my efforts at doing so have been unsuccessful. Tested on: Mac OS X 10.4.9, Firefox version Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3 Windows 2000 Pro, IE 6.0.2800.1106, SP1, Q823353 Windows 2000 Pro, Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7 Note: rich:modalPanel doesn't work on Safari (yet), so no way to test... __Calendar.prototype.popup = function (locX, locY) { var selectedDate = __calendarFactory.parseDateValue(getObject(this.name).value); if (selectedDate) { this.selectedMonth = selectedDate.getMonth() + 1; this.selectedYear = selectedDate.getFullYear(); } this.isPopup = true; __calendarFactory.documentmousedown = document.onmousedown; var popupDiv = getObject(POPUP_DIV); if (!popupDiv) { popupDiv = document.createElement('div'); popupDiv.id = POPUP_DIV; popupDiv.style.position = "absolute"; window.document.body.appendChild(popupDiv) } popupDiv.className = this.styleClass; getStyleObject(POPUP_DIV).left = locX + "px"; getStyleObject(POPUP_DIV).top = locY + "px"; /*BEGIN PATCH - set zIndex... C. Sweeney, May 10, 2007 */ var all_divs = document.getElementsByTagName("div"); var maxZIndex = 0; for(i = 0; i < all_divs.length; i++){ if(all_divs[i].id && all_divs[i].id != ""){ var divStyle = getStyleObject(all_divs[i].id); if(divStyle && divStyle.zIndex && divStyle.zIndex > maxZIndex){ maxZIndex = divStyle.zIndex; } } } getStyleObject(POPUP_DIV).zIndex = maxZIndex + 1; /* END PATCH */ popupDiv.innerHTML = this.getHTML(); changeObjectVisibility(POPUP_DIV, "visible"); document.onmousedown = this.documentmousedown; popupDiv.onmousedown = this.mousedown; popupDiv.onmouseup = this.mouseup; }; -- 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, 9 months

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-942) Optimistic locking an seam persistence context replication

by Gavin King (JIRA)

Optimistic locking an seam persistence context replication ---------------------------------------------------------- Key: JBSEAM-942 URL: http://jira.jboss.com/jira/browse/JBSEAM-942 Project: JBoss Seam Issue Type: Bug Components: Core Reporter: Gavin King Assigned To: Gavin King Priority: Critical Fix For: 1.2.1.GA We should replicate and check the version numbers of entities. -- 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, 9 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1031) Transaction rollback rules for Seam JavaBean components

by Gavin King (JIRA)

Transaction rollback rules for Seam JavaBean components ------------------------------------------------------- Key: JBSEAM-1031 URL: http://jira.jboss.com/jira/browse/JBSEAM-1031 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.2.0.GA Reporter: Gavin King Assigned To: Gavin King Fix For: 1.2.1.GA Currently, the only way to define exception rollback rules is @ApplicationException, which is a dependency to EJB3. For some reason I closed JBSEAM-467 without a better solution for this. There really needs to be two things: (1) An API to call to set the current tx to rollback only (2) some kind of @Exception annotation that allows control of rollback and, potentially, ending the conversation We should possibly even deprecate the end() member of @HttpError and @Redirect if we have this new thing. -- 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, 9 months

1
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-798) MDB + JBPM - problem with transaction

by Bradley Smith (JIRA)

MDB + JBPM - problem with transaction ------------------------------------- Key: JBSEAM-798 URL: http://jira.jboss.com/jira/browse/JBSEAM-798 Project: JBoss Seam Issue Type: Bug Components: BPM, Core, EJB3 Affects Versions: 1.1.6.GA Reporter: Bradley Smith I have an MDB that invokes a SLSB method - the method does some persistence work and signals a jBPM ProcessInstance. I am consistently getting an exception related to transactions from jBPM. 09:23:10,158 ERROR [StdServerSession] failed to commit/rollback org.jboss.tm.JBossRollbackException: Unable to commit, tx=TransactionImpl:XidImpl[FormatId=257, Glob alId=DEIBKST-6KZFT61/14, BranchQual=, localId=14] status=STATUS_NO_TRANSACTION; - nested throwable: (java.lang.NullPointerException) at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:372) at org.jboss.tm.TxManager.commit(TxManager.java:240) at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:351) at progress.message.jimpl.Session.dU_(Unknown Source) at progress.message.jimpl.Session.run(Unknown Source) at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:196) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.NullPointerException at org.jboss.seam.core.ManagedJbpmContext.beforeCompletion(ManagedJbpmContext.java:94) at org.jboss.tm.TransactionImpl.doBeforeCompletion(TransactionImpl.java:1491) at org.jboss.tm.TransactionImpl.beforePrepare(TransactionImpl.java:1110) at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:324) ... 7 more all the details can be found in the supplied JBoss Forum Reference -- 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, 9 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1094) Javadoc enhancement for @CreateProcess (add note about handling of null result)

by Arjan van Bentem (JIRA)

Javadoc enhancement for @CreateProcess (add note about handling of null result) ------------------------------------------------------------------------------- Key: JBSEAM-1094 URL: http://jira.jboss.com/jira/browse/JBSEAM-1094 Project: JBoss Seam Issue Type: Bug Components: BPM Affects Versions: 1.2.0.GA Environment: IDE inline help Reporter: Arjan van Bentem Priority: Trivial The Javadoc for org.jboss.seam.annotations.CreateProcess states at http://fisheye.jboss.com/browse/JBoss/jboss-seam/src/main/org/jboss/seam/... Marks a method creating a jBPM {@link org.jbpm.graph.exe.ProcessInstance process} so long as the method does not throw an exception. However, returning null for a non-void method also does not signal jBPM to start the process. So, for the sake of inline help in the IDE's I guess this should read: Marks a method creating a jBPM {@link org.jbpm.graph.exe.ProcessInstance process} when the method returns a non-null outcome without exception. When intentionally never returning a value then the method should be declared void. By the way: the documentation is correct, and states at http://fisheye.jboss.com/browse/JBoss/jboss-seam/doc/reference/en/modules... Creates a new jBPM process instance when the method returns a non-null outcome without exception. The ProcessInstance object will be available in a context variable named processInstance. Thanks! Arjan. -- 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, 9 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1249) Remoting calls do not work with session cookies disabled

by Dan Allen (JIRA)

Remoting calls do not work with session cookies disabled -------------------------------------------------------- Key: JBSEAM-1249 URL: http://jira.jboss.com/jira/browse/JBSEAM-1249 Project: JBoss Seam Issue Type: Bug Components: Remoting Affects Versions: 1.2.1.GA Environment: Sun Java 5, Linux, Firefox Reporter: Dan Allen Assigned To: Shane Bryzak Priority: Minor Ajax calls in Seam Remoting do not use encoded urls. Therefore, when session cookies are disabled, the ";jsessionid=" portion of the url is not sent with the request. Therefore, all remoting calls that rely on the HttpSession fail (gracefully). A fix would simply augment the Seam.Remoting.sendAjaxRequest to consider the jsessionid if it were present in the initial request. -- 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, 9 months

2
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-943) Collections and DataModels containing entities + persistence context replication

by Gavin King (JIRA)

Collections and DataModels containing entities + persistence context replication -------------------------------------------------------------------------------- Key: JBSEAM-943 URL: http://jira.jboss.com/jira/browse/JBSEAM-943 Project: JBoss Seam Issue Type: Bug Components: Core Reporter: Gavin King Assigned To: Gavin King Fix For: 1.2.1.GA need to recurse into collections -- 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, 9 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1102) Seam Remoting for GWT

by Michael Neale (JIRA)

Seam Remoting for GWT --------------------- Key: JBSEAM-1102 URL: http://jira.jboss.com/jira/browse/JBSEAM-1102 Project: JBoss Seam Issue Type: Patch Components: Remoting Affects Versions: 1.2.0.GA Reporter: Michael Neale Assigned To: Shane Bryzak Please find attached my contrib for making GWT remoting work with Seam Remoting. Works with GWT up to latest version 1.3. New unreleased GWT version 1.4 should also work - however it can be refactored to use the RPC utility class, and also be wired into Seam more deeply. Expect future patches for JSF level integration from Rob Jellinghaus. Summary of features/components: * There is a generic remoting servlet (this *may* be able to be retired and use generic Seam functionality - however I recommend GWT 1.4 for this, but it certainly is possible - if you look at the servlet there isn't anything too magical in there). * Uses @WebRemote to expose methods on a RPC API that GWT uses * All that is needed to use is to have a Seam component with a name the same as the RPC interface that GWT uses - Seam will do the rest. -- 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, 9 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-506) jBPM async calls and scheduling

by Gavin King (JIRA)

jBPM async calls and scheduling ------------------------------- Key: JBSEAM-506 URL: http://jira.jboss.com/jira/browse/JBSEAM-506 Project: JBoss Seam Issue Type: Feature Request Components: BPM Reporter: Gavin King Assigned To: Gavin King Priority: Critical Fix For: 1.2.0.BETA1 Extend the jBPM/Seam integration to async and scheduled processing. -- 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, 9 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1085) Automagically associate the processinstance with the thread in action and decision handlers

by Gavin King (JIRA)

Automagically associate the processinstance with the thread in action and decision handlers ------------------------------------------------------------------------------------------- Key: JBSEAM-1085 URL: http://jira.jboss.com/jira/browse/JBSEAM-1085 Project: JBoss Seam Issue Type: Feature Request Components: BPM Reporter: Gavin King Assigned To: Gavin King Fix For: 1.3.0.BETA1 We need an interceptor for this. -- 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, 9 months

1
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2007