November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-5009) HttpNamingContextFactory does neither support multiple URLs, nor load balancing nor failover

by Galder Zamarreno (JIRA)

HttpNamingContextFactory does neither support multiple URLs, nor load balancing nor failover -------------------------------------------------------------------------------------------- Key: JBAS-5009 URL: http://jira.jboss.com/jira/browse/JBAS-5009 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering, Naming Affects Versions: JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta2, JBossAS-4.0.5.GA Reporter: Galder Zamarreno Assigned To: Brian Stansberry HttpNamingContextFactory doesn't have to logic built into it to parse multiple URLs. Also, the naming proxy you'll get won't have automatic loadbalancing, failure detection and failover in it. -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-208) ClassCastException after redeploying ejb to cluster

by Brett Cave (JIRA)

ClassCastException after redeploying ejb to cluster --------------------------------------------------- Key: JBCLUSTER-208 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-208 Project: JBoss Clustering Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Environment: jboss-4.2.2 on centos, with jdk-1.5.0_15 Reporter: Brett Cave Assignee: Brian Stansberry deploying 2 EARs. node1 is the deployment server, where application is hot-deployed into farm. node2 is a cluster member. EAR1: baseEJB1-ejb.jar, packaged in base-ear.ear (contains ejb class BaseManagerBean which implements interface BaseManager). EAR2: alpha.war and alpha-ejb.jar, packaged in alpha-ear.ear. A class in alpha-ejb (ProcessHandlerBean) instantiates the ejb, as follows: public class ProcessHandlerBean implements ProcessHandler { @EJB(beanName="BaseManagerBean") protected BaseManager baseman; ... } Rebuild and deploy EAR2 to the cluster, causes no problems Running jboss with a single node (non-clustered) and rebuild and redeploy EAR1, then rebuild and redeploy EAR2 has no problems. In a clustered environment If i rebuild EAR1, redeploy it, then rebuild EAR2 (including the jar from EAR1 in the classpath for the libraries) and deploy, I get ClassCastException from a class in alpha-ejb that instantiates the ejb from baseEJB, but only on my deployment node, node1. The other node, node2, has no classcast exceptions. However, if i stop the deployment node1 and start it up again, then I get the ClassCastException on node2, and node1 has no errors. Restarting node2 then resolves CCE error. -- 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, 2 months

2
4
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

15 years, 2 months

4
3
0 / 0

[JBoss JIRA] Created: (JBAS-6122) Regression: Unable to deploy self referencing EJB3 session bean

by Radu Radutiu (JIRA)

Regression: Unable to deploy self referencing EJB3 session bean --------------------------------------------------------------- Key: JBAS-6122 URL: https://jira.jboss.org/jira/browse/JBAS-6122 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-5.0.0.CR2 Environment: Fedora Linux 9, Sun JDK 1.6.0_06 Reporter: Radu Radutiu Assignee: Carlo de Wolf The following stateless EJB which has a self reference using @EJBs() annotation deploys fine on jboss-4.2.3 but fails to deploy on jboss-5.0.0CR2. package test; import javax.ejb.*; @EJBs({@EJB(name="TestSessionBean/local",beanInterface=LocalTestSession.class,beanName="TestSessionBean")}) @Stateless(name="TestSessionBean") public class TestSessionBean implements LocalTestSession { public String test() { try { InitialContext ic = new InitialContext(); LocalTestSession lc = (LocalTestSession) ic.lookup("java:comp/env/TestSessionBean/local"); System.out.println(lc.test1()); } catch (NamingException e) { e.printStackTrace(); } return "test"; } public String test1() { return "test1"; } } When deploying the jar on jboss-5.0.0CR2 I get the following error: 09:57:19,227 WARN [HDScanner] Failed to process changes org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State} jboss.j2ee:ear=test.jar,jar=test.jar,name=TestSessionBean,service=EJB3 -> <UNKNOWN jboss.j2ee:ear=test.jar,jar=test.jar,name=TestSessionBean,service=EJB3>{Described:** UNRESOLVED Demands 'jndi:TestSessionBean/local-test.LocalTestSession' **} *** CONTEXTS IN ERROR: Name -> Error <UNKNOWN jboss.j2ee:ear=test.jar,jar=test.jar,name=TestSessionBean,service=EJB3> -> ** UNRESOLVED Demands 'jndi:TestSessionBean/local-test.LocalTestSession' ** -- 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, 2 months

5
6
0 / 0

[JBoss JIRA] Created: (JBNAME-2) Need to improve the exception msg on discovery failures

by Scott M Stark (JIRA)

Need to improve the exception msg on discovery failures ------------------------------------------------------- Key: JBNAME-2 URL: http://jira.jboss.com/jira/browse/JBNAME-2 Project: JBoss Naming Issue Type: Feature Request Components: jnp-client Affects Versions: 5.0.0.CR1 Reporter: Scott M Stark When a discovery failure occurs we are only reporting the original exception that triggered discovery. This codeblock does not try to incorporate the discovery exception seen if there already is a serverEx: try { naming = discoverServer(refEnv); } catch (Exception e) { discoveryFailure = e; if (serverEx == null) serverEx = e; } We should be building a better nested exception to show both problem.s -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBNAME-9) Tree Based ACL

by Anil Saldhana (JIRA)

Tree Based ACL -------------- Key: JBNAME-9 URL: https://jira.jboss.org/jira/browse/JBNAME-9 Project: JBoss Naming Issue Type: Feature Request Components: jnpserver Reporter: Anil Saldhana Assignee: Scott M Stark JIRA issue for Scott to take a look. -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2063) Ability to impersonatee Users

by Magesh Kumar B (JIRA)

Ability to impersonatee Users ----------------------------- Key: JBPORTAL-2063 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2063 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Security Affects Versions: 2.6.5 SP1 Reporter: Magesh Kumar B Assigned To: Julien Viet It would be nice to have Administrator impersonating Users. For e.g. an Administrator could view a Dashboard page of another user to see how it behaves without logging in to the system as that user. -- 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, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (GPD-140) when working with large process definitions, screen jumps to top whenever new nodes added in designer

by Ross McDonald (JIRA)

when working with large process definitions, screen jumps to top whenever new nodes added in designer ----------------------------------------------------------------------------------------------------- Key: GPD-140 URL: http://jira.jboss.com/jira/browse/GPD-140 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0.beta2 Environment: osx macbook pro, eclipse 3.3.0, designer plugin 3.1.0 beta 1, beta 2, CR1 Reporter: Ross McDonald Assigned To: Koen Aers Priority: Trivial Hi, when working with large process diagrams, if I am scrolled down to the bottom of the view, and add a new node, when the screen is updated it jumps back up to the top, so I need to scroll down again. Obviously when adding many nodes, this costs time, its just a trivial thing. Cheers Ross -- 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, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (GPD-206) Show simlane assignment in task node

by Rubￃﾩn Marrero (JIRA)

Show simlane assignment in task node ------------------------------------ Key: GPD-206 URL: http://jira.jboss.com/jira/browse/GPD-206 Project: JBoss jBPM GPD Issue Type: Feature Request Components: jpdl Reporter: Rubￃﾩn Marrero Assigned To: Koen Aers Priority: Trivial It would be very useful if the task would show which swimlane is assigned to. Thanks -- 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, 2 months

4
3
0 / 0

[JBoss JIRA] Created: (GPD-209) Transition Tag in Sourcecode not parsed correctly when open and close in same tag

by Norgan Han (JIRA)

Transition Tag in Sourcecode not parsed correctly when open and close in same tag --------------------------------------------------------------------------------- Key: GPD-209 URL: http://jira.jboss.com/jira/browse/GPD-209 Project: JBoss jBPM GPD Issue Type: Bug Environment: Eclipse 3.3, Java 6 Reporter: Norgan Han Assigned To: Koen Aers Priority: Optional When I copy & paste the source code examples from the alfresco wiki into the source files in eclipse, a switch fro SOURCE to DIAGRAM view, all transactions point to the same point in the diagram and cannot be assigned to another target. Sourcecode Bug: <transition name="" to="end" /> Sourcefoce Fix : <transition name="" to="end" ></transition> -- 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, 2 months

2
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 November 2008