December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (GPD-33) remember the previous form generation data fields

by Koen Aers (JIRA)

remember the previous form generation data fields ------------------------------------------------- Key: GPD-33 URL: http://jira.jboss.com/jira/browse/GPD-33 Project: JBoss jBPM GPD Issue Type: Feature Request Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha3 In the form generation, we currently start from the data entered in the task controller (if any) Whenever a form is generated, I would like the form generation data to be stored in the gpd.xml. Then, whenever the user does a second generation, the taskform generation form is prefilled with the previous data instead of starting from the controller data again. The motivation for this is that mostly people will not have controllers. Then if they have 5 data items to display and collect, it takes a lot of clicking. Users don't want to redo this effort for every little change they want to make to the form (additions and removals of fields). I think users should be able to live with the fact that controller data items are not kept automatically in sync with the task form data items. -- 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

14 years, 8 months

3
10
0 / 0

[JBoss JIRA] Created: (GPD-20) refactor naming strategy

by Koen Aers (JIRA)

refactor naming strategy ------------------------ Key: GPD-20 URL: http://jira.jboss.com/jira/browse/GPD-20 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha3 1) generate default node names when nodes are created: {node1, node2, ...}. use this naming strategy for each node type. 2) do not generate a node name for the start-state. users should be able to give the start-state a name, though. 3) use the following naming strategy for end states: {end, end2, end3, end4, ...} 4) do not generate names for transitions. the problem reporting should generate warnings if a node-type requires named nodes. the correlation between the graphical information and the processdefinition.xml will be done based on the position (index), rather then on the name. 5) disallow slashes in names in a process definition (nodes, transitions, process definition, actions, ...) Because slashes will be used as a separator in hierarchical names. We should also investigate if it would be useful to specify a strict set of chars that can be used like e.g. 0-9,a-z,A-Z,space,dot -- 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

14 years, 8 months

2
11
0 / 0

[JBoss JIRA] Created: (GPD-31) Make sure all tasks in a process definition have a unique name

by Koen Aers (JIRA)

Make sure all tasks in a process definition have a unique name -------------------------------------------------------------- Key: GPD-31 URL: http://jira.jboss.com/jira/browse/GPD-31 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha3 When retrieving all tasks from a process definition like so: processDefinition.getTaskMgmtDefinition().getTasks() it returns a MAP of tasks, keyed by task name. This is a problem if two tasks anywhere in the same process definition have the same name. By default, the GPD creates all tasks as "task1" when it is the first task on a task node. If none of these were renamed, you would only get a single task when trying to get all of them for the process definition. -- 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

14 years, 8 months

2
9
0 / 0

[JBoss JIRA] Created: (GPD-15) add a readme in the create-project wizard

by Koen Aers (JIRA)

add a readme in the create-project wizard ----------------------------------------- Key: GPD-15 URL: http://jira.jboss.com/jira/browse/GPD-15 Project: JBoss jBPM GPD Issue Type: Feature Request Reporter: Koen Aers Assigned To: Koen Aers all features that help beginner get started are vital imho. therefor, i think the forum user points out a good opportunity for us: we could create a readme.txt in the root of the generated project. that readme is opened when the wizard creates the project and it explains the contents of the project and what do to next. -- 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

14 years, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (GPD-17) jpdl designer user guide and documentation

by Koen Aers (JIRA)

jpdl designer user guide and documentation ------------------------------------------ Key: GPD-17 URL: http://jira.jboss.com/jira/browse/GPD-17 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers A new user guide using screenshots of the new product should be written. -- 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

14 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBCOMMON-35) NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock .

by Vicky Kak (JIRA)

NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock . ------------------------------------------------------------------------------ Key: JBCOMMON-35 URL: http://jira.jboss.com/jira/browse/JBCOMMON-35 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Components: common-old Affects Versions: 1.0.0.GA Reporter: Vicky Kak Assigned To: Vicky Kak Fix For: 2.2.2.GA, 2.0.6.GA, 1.2.2.GA, 1.0.5.GA http://forum.java.sun.com/thread.jspa?threadID=752201 -- 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

14 years, 8 months

2
15
0 / 0

[JBoss JIRA] Created: (JBAS-4595) Inconclusive exception thrown by HttpNamingContextFactory

by Carlo de Wolf (JIRA)

Inconclusive exception thrown by HttpNamingContextFactory --------------------------------------------------------- Key: JBAS-4595 URL: http://jira.jboss.com/jira/browse/JBAS-4595 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.1.GA Environment: Hudson only Sun VM 1.5.0_12-b04 Ubuntu 6.06 Reporter: Carlo de Wolf Priority: Minor Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA javax.naming.NamingException: Failed to retrieve Naming interface [Root exception is java.net.ConnectException: Connection refused] at org.jboss.naming.HttpNamingContextFactory.getInitialContext(HttpNamingContextFactory.java:84) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247) at javax.naming.InitialContext.init(InitialContext.java:223) at javax.naming.InitialContext.<init>(InitialContext.java:197) at org.jboss.ejb3.test.invoker.unit.InvokerTestCase.testHttp(InvokerTestCase.java:55) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) Caused by: java.net.ConnectException: Connection refused at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1223) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1217) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:906) at org.jboss.naming.HttpNamingContextFactory.getNamingServer(HttpNamingContextFactory.java:133) at org.jboss.naming.HttpNamingContextFactory.getInitialContext(HttpNamingContextFactory.java:80) ... 26 more Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.Socket.connect(Socket.java:519) at java.net.Socket.connect(Socket.java:469) at sun.net.NetworkClient.doConnect(NetworkClient.java:157) at sun.net.www.http.HttpClient.openServer(HttpClient.java:382) at sun.net.www.http.HttpClient.openServer(HttpClient.java:509) at sun.net.www.http.HttpClient.<init>(HttpClient.java:231) at sun.net.www.http.HttpClient.New(HttpClient.java:304) at sun.net.www.http.HttpClient.New(HttpClient.java:316) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:813) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:765) at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:690) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:934) at sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:1903) at java.net.URLConnection.getHeaderFieldInt(URLConnection.java:573) at java.net.URLConnection.getContentLength(URLConnection.java:468) at org.jboss.naming.HttpNamingContextFactory.getNamingServer(HttpNamingContextFactory.java:128) ... 27 more -- 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

14 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3521) OptimisticLockUnitTestCase Intermittently Fails

by Matt Wringe (JIRA)

OptimisticLockUnitTestCase Intermittently Fails ----------------------------------------------- Key: JBAS-3521 URL: http://jira.jboss.com/jira/browse/JBAS-3521 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-4.0.4.GA Environment: Sun 1.4.2_12 JVM RHEL 4, Linux Kernel 2.6.9 Reporter: Matt Wringe The OptimisticLockUnitTestCase testBug1006723 test seems to fail randomly. This is a known issue, and is described here: http://wiki.jboss.org/wiki/Wiki.jsp?page=TestsuiteTroubleShooting But there does not appear to be a bug filed about this issue, nor can I find bug 1006723 "Problem OptimisticLockUnitTestCase fails Suite: org.jboss.test.cmp2.optimisticlock.test.OptimisticLockUnitTestCase Test: testBug1006723 Type: error Exception: javax.ejb.CreateException Message: Error checking if entity exists:java.sql.SQLException: Column not found: \ OIDCMP in statement SELECT COUNT(*) FROM ENTITYA WHERE OIDCMP=? This test passes intermintently. Run it a few times" -- 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

14 years, 9 months

6
9
0 / 0

[JBoss JIRA] Created: (JBAS-4598) TimerHandle failed to retrieve timer after JBoss restart

by Linoux Linoux (JIRA)

TimerHandle failed to retrieve timer after JBoss restart -------------------------------------------------------- Key: JBAS-4598 URL: http://jira.jboss.com/jira/browse/JBAS-4598 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Environment: Windows XP / PostgreSQL Reporter: Linoux Linoux Creating a timer, store the associated TimerHandle in DB. Restart JBoss server, try to get the Timer using the stored TimerHandle : javax.ejb.NoSuchObjectLocalException is thrown. ---------------------------------------------------------- //In a Stateless Session : @TransactionAttribute(TransactionAttributeType.REQUIRED) public void createTimer() throws OgpException { TimerService ts = ctx.getTimerService(); Timer newTimer = ts.createTimer(getTimerStartDate(), DateUtil.MILLIS_IN_DAY, testAge); conf.setTestCleanTimerHandle(newTimer.getHandle()); // Store conf in DB } private Timer getCurrentTimer(DbConfiguration conf) throws OgpException { if (conf.getTestCleanTimerHandle() == null) return null; try { return conf.getTestCleanTimerHandle().getTimer(); } catch (NoSuchObjectLocalException e) { log.warn("Can't retrieve timer : it could be caused by the application redeployment", e); return null; } } ---------------------------------------------------------- Using this code, call to getCurrentTimer after calling createTimer works fine, but after a JBoss restart, call to getCurrentTimer ends with a NoSuchObjectLocalException : javax.ejb.NoSuchObjectLocalException: Timer not available: [target=jboss.j2ee:service=EJB3,ear=ogp-app.ear,jar=ogp-ejb.jar,name=AdminCleanDbSessionBean] at org.jboss.ejb.txtimer.TimerHandleImpl.getTimer(TimerHandleImpl.java:203) at com.sts.ogp.ejb.admin.AdminCleanDbSessionBean.getCurrentTimer(AdminCleanDbSessionBean.java:157) [...] -- 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

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1262) DSL Parser "eval"

by M H (JIRA)

DSL Parser "eval" ----------------- Key: JBRULES-1262 URL: http://jira.jboss.com/jira/browse/JBRULES-1262 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.1 Reporter: M H Assigned To: Mark Proctor [when]of type Item=Item() [when]- Title equals "{value}"=eval(title.isEqual("{value}") [when]- Event equals "{value}"=eval(id.isEqual("{value}") [then]Log : "{message}"=System.out.println("{message}"); the dslr File: expander Test.dsl rule "Your First Rule" when $p : of type Item - Title equals "test" - Event equals "test" then #actions end resolves to (could be seen in the drl viewer) rule "Your First Rule" when $p :Item( eval(title.isEqual("test", eval(id.isEqual("test") ) ) then #actions end -- 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

14 years, 9 months

5
18
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2007