June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCLUSTER-157) Server Shutdown Latency and Session replication and Forwarding

by Shankar Pattabiraman (JIRA)

Server Shutdown Latency and Session replication and Forwarding -------------------------------------------------------------- Key: JBCLUSTER-157 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-157 Project: JBoss Clustering Issue Type: Bug Security Level: Public (Everyone can see) Environment: Java 1.5.0_05, Win XP,Red Hat 3 JBoss 4.0.5 Apache Reporter: Shankar Pattabiraman Assigned To: Brian Stansberry Priority: Minor Setup a cluster with 2 nodes. Be in a session where a server is servicing. Try to give a Control Z to kill the server while servicing. The latency involved in shutting down the server never gives a chance for the server to switch to the other. The session in the latency period of shutdown never gets successfully switched to the other node in the cluster. Apache-2 Node Jboss Cluster and a Trivial JEE Application. Check this out whether it is a configuration issue or a real issue. -- 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

16 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-686) Bidirectional @OneToOne with CascadeType.ALL and optional=false on the non-owning side:

by Jeremy Norris (JIRA)

Bidirectional @OneToOne with CascadeType.ALL and optional=false on the non-owning side: --------------------------------------------------------------------------------------- Key: EJBTHREE-686 URL: http://jira.jboss.com/jira/browse/EJBTHREE-686 Project: EJB 3.0 Issue Type: Bug Components: EJB3 Extensions Affects Versions: EJB 3.0 RC8 - FD, EJB 3.0 RC7 - FD, EJB 3.0 RC6 - PFD Reporter: Jeremy Norris Consider the following two classes: ----- class X: @Entity @Table(name="x") public class X { private Integer id; private Y y; public X() { this.y = new Y(this); } @Id @GeneratedValue @Column(name = "id", nullable=false, updatable=false) public Integer getId() { return id; } protected void setId(Integer id) { this.id = id; } @OneToOne(cascade={CascadeType.ALL}, mappedBy="x") public Y getY() { return y; } protected void setY(Y y) { this.y = y; } } ----- class Y: @Entity @Table(name="y") public class Y { private Integer id; private X x; protected Y() { } public Y(X x) { this.x = x; x.setY(this); } @Id @GeneratedValue @Column(name = "id", nullable=false, updatable=false) public Integer getId() { return id; } protected void setId(Integer id) { this.id = id; } @OneToOne @JoinColumn(name="x_id", nullable=false) public X getX() { return x; } protected void setX(X x) { this.x = x; } } ----- X is persisted as follows: // Note: The constructor creates a new dependent Y instance, and hooks it up appropriately: X x = new X(); em.persist(x); ----- This works fine and persists as expected. However, if I add "optional=false" to the X.@OneToOne declaration, it fails with the following exception: javax.ejb.EJBTransactionRolledbackException: javax.persistence.PersistenceException: org.hibernate.PropertyValueException: not-null property references a null or transient value: ... Y.x Y.x definitely set. Also, "x == x.getY().getX()" is true. (Interestingly, this only happens if I put the "optional=false" on the X side. "optional=false" on the Y side is fine). This seems like a bug unless there is something I don't understand about "optional", but it seems pretty simply - The spec says the following about this attribute: (Optional) Whether the association is optional. If set to false then a non-null relationship must always exist. -- 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

16 years, 6 months

4
3
0 / 0

[JBoss JIRA] Created: (GPD-27) Make transitions identifiable by position

by Koen Aers (JIRA)

Make transitions identifiable by position ----------------------------------------- Key: GPD-27 URL: http://jira.jboss.com/jira/browse/GPD-27 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Reporter: Koen Aers Assigned To: Koen Aers Priority: Minor Try and implement a strategy where transitions are identified by their position in the list of transitions rather than by a name. This should be done to eliminate the need for a transition name. When this is done the bendpoints in the gpd.xml file can be associated with their transition based on the position. -- 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

16 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (GPD-14) Lay out Algorithm

by Koen Aers (JIRA)

Lay out Algorithm ----------------- Key: GPD-14 URL: http://jira.jboss.com/jira/browse/GPD-14 Project: JBoss jBPM GPD Issue Type: Feature Request Components: jpdl Reporter: Koen Aers Assigned To: Koen Aers Integrate a layout algorithm that is used when users add nodes to the xml directly to lay out the newly created components in an orderly fashion on the graphical canvas. -- 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

16 years, 6 months

4
8
0 / 0

[JBoss JIRA] Created: (GPD-67) GPD support for editing non-files (any IEditorInput, not just FileEditorInput)

by John Ruud (JIRA)

GPD support for editing non-files (any IEditorInput, not just FileEditorInput) ------------------------------------------------------------------------------ Key: GPD-67 URL: http://jira.jboss.com/jira/browse/GPD-67 Project: JBoss jBPM GPD Issue Type: Feature Request Reporter: John Ruud Assigned To: Koen Aers Priority: Minor We need to edit process defs that are stored in a DB, as opposed to the processdefinition.xml, gpd.xml files stored in the workspace. There are currently many dependencies to FileEditorInput/File throughout GPD (as is the case for a lot of other Eclipse editors BTW). It would be very helpful if it would be feasible to separate out the code that deals with a particular type of IEditorInput from the rest of the editor, possibly into a separete delegate class. For FileEditorInput the delegate would deal with reading, writing, and syncronizing the view (resource listeners), plus whatever else I may have forgotten. We could then replace the default "file" delegate with our own that knows how to deal our DB (by subclassing of the editor would be fine). Probably not the #1 GPD issue for many other users, but hopefully something you would keep in mind... -- 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

16 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (GPD-35) enhancement drawing transitions

by Koen Aers (JIRA)

enhancement drawing transitions ------------------------------- Key: GPD-35 URL: http://jira.jboss.com/jira/browse/GPD-35 Project: JBoss jBPM GPD Issue Type: Feature Request Components: jpdl Reporter: Koen Aers Assigned To: Koen Aers When the mousepointer is in the outer area of a node/state/task/.... but within it's boundaries, it should be possible to draw a transition. This is makes using the gpd a lot faster (not switching in the toolbar) Maybe it should only be in the 'middle areas' of top, bottom, left and right and not the corners -- 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

16 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (GPD-39) Adapt property sheet according to context in xml tab

by Koen Aers (JIRA)

Adapt property sheet according to context in xml tab ---------------------------------------------------- Key: GPD-39 URL: http://jira.jboss.com/jira/browse/GPD-39 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Reporter: Koen Aers Assigned To: Koen Aers Currently the property sheet does not reflect the context when editing the process definition in the xml source tab. Solution : define a selection listener that activates the model object corresponding to the cursor location in the xml source tab. -- 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

16 years, 6 months

2
7
0 / 0

[JBoss JIRA] Created: (GPD-36) Choose to have classpath container or expanded libraries

by Koen Aers (JIRA)

Choose to have classpath container or expanded libraries -------------------------------------------------------- Key: GPD-36 URL: http://jira.jboss.com/jira/browse/GPD-36 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Reporter: Koen Aers Assigned To: Koen Aers It would be good to be able to choose between expanded libraries or a classpath container when creating a process project with the new... wizard. -- 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

16 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-991) secure the gpd deployment servlet

by Tom Baeyens (JIRA)

secure the gpd deployment servlet --------------------------------- Key: JBPM-991 URL: http://jira.jboss.com/jira/browse/JBPM-991 Project: JBoss jBPM Issue Type: Task Components: Core Engine Reporter: Tom Baeyens Assigned To: Tom Baeyens Fix For: jBPM jPDL 3.2.2 the gpd deployment servlet should be secured. the gpd should add authentication information in the url like e.g. http://gpd:gpd:localhost/jbpm-console/upload or something like that. then the users will be able to control the authorization through the web interface itself. -- 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

16 years, 6 months

2
8
0 / 0

[JBoss JIRA] Created: (GPD-19) Endpoint Editing

by Koen Aers (JIRA)

Endpoint Editing ---------------- Key: GPD-19 URL: http://jira.jboss.com/jira/browse/GPD-19 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 Move endpoints of connections to wherever location on the edge of a node. Involves implementing a particular form of anchor point. -- 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

16 years, 6 months

2
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2007