November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4931) Fix ejb3 ClientLaucher

by Thomas Diesler (JIRA)

Fix ejb3 ClientLaucher ---------------------- Key: JBAS-4931 URL: http://jira.jboss.com/jira/browse/JBAS-4931 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- 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

17 years, 1 month

2
9
0 / 0

[JBoss JIRA] Created: (JBAS-4982) Add jboss-ejb3-ext-api.jar to jbossall-client.jar for ClientContainer

by Carlo de Wolf (JIRA)

Add jboss-ejb3-ext-api.jar to jbossall-client.jar for ClientContainer --------------------------------------------------------------------- Key: JBAS-4982 URL: http://jira.jboss.com/jira/browse/JBAS-4982 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: JBossAS-5.0.0.Beta3 -- 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

17 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1806) Portlet window state cached when window re-created

by Ovidiu Nichifor (JIRA)

Portlet window state cached when window re-created -------------------------------------------------- Key: JBPORTAL-1806 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1806 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.1 Final Environment: JBoss AS 4.0.5 installed with JEMS 1.2.0.GA Reporter: Ovidiu Nichifor Assigned To: Julien Viet 1. Create a window. 2. Minimize it. 3. Close the window. 4. Re-create the window (exact name, page, coordinates etc). 5. Notice that the window is displayed in the minimized view, instead of normal view. If you re-login to portal or restart the AS it will work properly (the new window is created in normal view). Also note that once a window gets maximized and you re-login/restart the AS the window looses state (is displayed in normal view). -- 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

17 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1749) Consider creating an index

by Chris Laprun (JIRA)

Consider creating an index -------------------------- Key: JBPORTAL-1749 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1749 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Chris Laprun -- 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

17 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1804) WSRP Producer incorrectly sends an InvalidRegistrationFault when a modification to the registration by the consumer is required

by Chris Laprun (JIRA)

WSRP Producer incorrectly sends an InvalidRegistrationFault when a modification to the registration by the consumer is required ------------------------------------------------------------------------------------------------------------------------------- Key: JBPORTAL-1804 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1804 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.2 Final Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6.3 Final OperationFailedFault should be sent instead. Kind of crappy but WSRP 2 will have ModifyRegistrationRequiredFault instead! -- 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

17 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1080) create tutorial for customizing ejb3-interceptors-aop.xml

by William DeCoste (JIRA)

create tutorial for customizing ejb3-interceptors-aop.xml --------------------------------------------------------- Key: EJBTHREE-1080 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1080 Project: EJB 3.0 Issue Type: Task Components: Documentation Reporter: William DeCoste Assigned To: William DeCoste -- 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

17 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-791) make email port in test suite configurable

by Tom Baeyens (JIRA)

make email port in test suite configurable ------------------------------------------ Key: JBPM-791 URL: http://jira.jboss.com/jira/browse/JBPM-791 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Reporter: Tom Baeyens Assigned To: Tom Baeyens we're using dumpster in the test suite for testing emails. but our continuous integration server doesn't allow for ports to be opened under 1024. so we need to find a way to tell dumpster to open up the fake mailserver on a different port. also we need to figure out how to tell the JavaMail API that mails should be sent using this different port... -- 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

17 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4978) Create analogues for the existing LoadBalancePolicy impls that use the new interface

by Brian Stansberry (JIRA)

Create analogues for the existing LoadBalancePolicy impls that use the new interface ------------------------------------------------------------------------------------ Key: JBAS-4978 URL: http://jira.jboss.com/jira/browse/JBAS-4978 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta3 None of the existing LBP impls do anything meaningful anywhere but in "Object chooseTarget(FamilyCIusterInfo)". So, duplicate them all but implementing just the base interface. Existing impls remain in order to ensure backward compatibility. -- 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

17 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4979) Convert HARMIClient and HARMIServer to use new LoadBalancePolicy

by Brian Stansberry (JIRA)

Convert HARMIClient and HARMIServer to use new LoadBalancePolicy ---------------------------------------------------------------- Key: JBAS-4979 URL: http://jira.jboss.com/jira/browse/JBAS-4979 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.Beta3 -- 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

17 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-187) Local instead of remote lookup happens when bean is clustered

by Vijesh (JIRA)

Local instead of remote lookup happens when bean is clustered ------------------------------------------------------------- Key: JBCLUSTER-187 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-187 Project: JBoss Clustering Issue Type: Bug Security Level: Public (Everyone can see) Environment: Linux/Widows Reporter: Vijesh Assigned To: Brian Stansberry 1) Two different ejb 2.1 applications. Let's call them A1 and A2 2) Both has some common beans deployed in them (same jar). Lets call them C1, C2 etc. Each application also has their own bean: let's call them A1-a, A-b etc and A2-x, A2-y etc 3) A1 to A2 communication via remote call is there. And clients can call any beans (common/specific) A1 and A2 also. 4) Let's say a client calls the bean A1-a deployed in A1. A1-a in turn calls the bean C1 in application A2. Though C1 deployed in both servers are same, the data supplied them are different, so the call has to reach A2. The issue. When the beans are not clustered, call from A1-a to C1 in A2 went through as expected (in both all/default configurations). But when the beans are clustered, instead of calling C1 in A2, local lookup is done and invoked C1 in application A1. Expected behaviour: In both clustered and non-clustered configuration, when a remote bean look up is done from application-1 to another bean in application-2, which is also present in application-1, the call should go to application-2 Jboss; 4.0.5 jdk: 1.5_05 ejb; 2.1 stateless beans -- 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

17 years, 1 month

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 2007