August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBMICROCONT-35) Allow retrieval of the collection instance from the bean

by Rashid Kamran (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-35?page=comments#action_123... ] Rashid Kamran commented on JBMICROCONT-35: ------------------------------------------ Just curious .. Why actually we want to use the collection value that bean already has? because this way it would be a little different in the sense that setXXX means to replace the old property value with the newer one ? > Allow retrieval of the collection instance from the bean > -------------------------------------------------------- > > Key: JBMICROCONT-35 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-35 > Project: JBoss MicroContainer > Issue Type: Task > Components: MetaData > Reporter: Adrian Brock > Fix For: JBossMC_2_0_0 final > > > See org.jboss.test.kernel.config.test.CollectionTestCase#TODOtestCustomCollectionPreInstantiated > Same issues apply to Lists, Sets, Maps, Arrays, etc. > i.e. If the bean already has a collection value for the property that can be > retrieved using the getter, we should be able to use that collection instance. > Need to think about the configuration options and rules. > Current rules are: > 1) Use class specified in metadata > 2) Use class specified on setter (if not an interface) > 3) Use ArrayList -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3538) Run server under a Kerberos login

by David Robison (JIRA)

Run server under a Kerberos login --------------------------------- Key: JBAS-3538 URL: http://jira.jboss.com/jira/browse/JBAS-3538 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: System service Affects Versions: JBossAS-4.0.4.GA Reporter: David Robison Assigned To: Dimitris Andreadis Attachments: Main.java I am using JBoss as a container for my JacORB CORBA services. I want to use JacORB's SAS service since JBoss's does not yet support a Kerberos context. To use the JacORB SAS service, the service has to be run under a Kerberos login context (e.g. with a subject.doAs). I've made a modification to the Main.java file and added a -k command line parameter to force a Kerberos login. I've attached the file to this issue. I would like to sugest that it is included in a future release. -- 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

19 years, 11 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBAS-3358) Work directory for the web app shouldn't be deleted on Context Destroy

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3358?page=all ] Anil Saldhana closed JBAS-3358. ------------------------------- > Work directory for the web app shouldn't be deleted on Context Destroy > ---------------------------------------------------------------------- > > Key: JBAS-3358 > URL: http://jira.jboss.com/jira/browse/JBAS-3358 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Affects Versions: JBossAS-4.0.4.GA > Reporter: Javid Jamae > Assigned To: Anil Saldhana > Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1 > > > I tried enabling HTTP session persistence, but found out that the default directory that it writes to is the work directory. Working with JBoss support, I discovered that the work directory is deleted when the server shuts down. > Either the work directory should not be deleted, or the default directory where the persistent HTTP sessions are serialized to a file should be changed to be in a directory other than work (since it is being deleted). -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3358) Work directory for the web app shouldn't be deleted on Context Destroy

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3358?page=all ] Anil Saldhana updated JBAS-3358: -------------------------------- Summary: Work directory for the web app shouldn't be deleted on Context Destroy (was: Work directory shouldn't be deleted on Context Destroy) Fix Version/s: JBossAS-5.0.0.Beta > Work directory for the web app shouldn't be deleted on Context Destroy > ---------------------------------------------------------------------- > > Key: JBAS-3358 > URL: http://jira.jboss.com/jira/browse/JBAS-3358 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Affects Versions: JBossAS-4.0.4.GA > Reporter: Javid Jamae > Assigned To: Anil Saldhana > Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1 > > > I tried enabling HTTP session persistence, but found out that the default directory that it writes to is the work directory. Working with JBoss support, I discovered that the work directory is deleted when the server shuts down. > Either the work directory should not be deleted, or the default directory where the persistent HTTP sessions are serialized to a file should be changed to be in a directory other than work (since it is being deleted). -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPORTAL-897) Define requirements for JBoss Portal look and feel

by Roy Russo (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-897?page=all ] Roy Russo resolved JBPORTAL-897. -------------------------------- Resolution: Done http://jira.jboss.com/jira/browse/JBPORTAL-994 http://jira.jboss.com/jira/browse/JBPORTAL-993 http://jira.jboss.com/jira/browse/JBPORTAL-992 http://jira.jboss.com/jira/browse/JBPORTAL-991 http://jira.jboss.com/jira/browse/JBPORTAL-990 http://jira.jboss.com/jira/browse/JBPORTAL-989 > Define requirements for JBoss Portal look and feel > -------------------------------------------------- > > Key: JBPORTAL-897 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-897 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal Core > Affects Versions: 2.6 Final > Reporter: Julien Viet > Assigned To: Roy Russo > Fix For: 2.6 Final > > > At JBoss World we need to define the deliverable for the JBoss Portal look and feel enhancements. -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBPORTAL-337) remove the unnecessary and add necessary operations from UserPortlet

by Roy Russo (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-337?page=all ] Roy Russo reassigned JBPORTAL-337: ---------------------------------- Assignee: Roy Russo > remove the unnecessary and add necessary operations from UserPortlet > -------------------------------------------------------------------- > > Key: JBPORTAL-337 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-337 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal Core > Affects Versions: 2.0 Branch > Environment: Linux, PostgreSQL, AS 4.0.2 > Reporter: Yang > Assigned To: Roy Russo > Fix For: 2.6 Final > > Attachments: UserPortlet.diff > > Original Estimate: 1 day > Remaining Estimate: 1 day > > For core/src/main/org/jboss/portal/core/portlet/user/UserPortlet.java, the operations like SHOW_LOGIN and SHOW_MENU shouldn't be included in UserPortlet. > However, operations like FORGETPASSWORD and ACTIVATEACCOUNT should be included. -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-337) remove the unnecessary and add necessary operations from UserPortlet

by Roy Russo (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-337?page=all ] Roy Russo updated JBPORTAL-337: ------------------------------- Fix Version/s: 2.6 Final > remove the unnecessary and add necessary operations from UserPortlet > -------------------------------------------------------------------- > > Key: JBPORTAL-337 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-337 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal Core > Affects Versions: 2.0 Branch > Environment: Linux, PostgreSQL, AS 4.0.2 > Reporter: Yang > Assigned To: Roy Russo > Fix For: 2.6 Final > > Attachments: UserPortlet.diff > > Original Estimate: 1 day > Remaining Estimate: 1 day > > For core/src/main/org/jboss/portal/core/portlet/user/UserPortlet.java, the operations like SHOW_LOGIN and SHOW_MENU shouldn't be included in UserPortlet. > However, operations like FORGETPASSWORD and ACTIVATEACCOUNT should be included. -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBPORTAL-585) Sorting and Localization for Navigation Portlet

by Roy Russo (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-585?page=all ] Roy Russo reassigned JBPORTAL-585: ---------------------------------- Assignee: Roy Russo > Sorting and Localization for Navigation Portlet > ----------------------------------------------- > > Key: JBPORTAL-585 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-585 > Project: JBoss Portal > Issue Type: Patch > Security Level: Public(Everyone can see) > Affects Versions: 2.2 Final, 2.4 Final > Reporter: Doug Schnelzer > Assigned To: Roy Russo > Fix For: 2.6 Final > > Attachments: default-object.xml, NavigationPortlet.java, Resource.properties > > > The navigation portlet currently only supports sorting by the page name. This patch adds support for sorting by a Declared Property named "order" in the -objects.xml. This patch also supports using a resource properties file for looking up page labels. The Declared Property name for the resource properties file key is "resourceKey". An example -object.xml file is attached. The relevant section is: > <page> > <page-name>default</page-name> > <properties> > <property> > <name>order</name> > <value>1</value> > </property> > <property> > <name>resourceKey</name> > <value>home</value> > </property> > </properties> > ... -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBSEAM-279) Component lifetimes not guaranteed for SFSB backed components.

by ryan dewell (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-279?page=comments#action_12341524 ] ryan dewell commented on JBSEAM-279: ------------------------------------ The work around for EJBNoObjectException in Seam is to use the JBoss annotation @CacheInfo and manually configure it to the same timeout as the Seam component. We'll all have to do this until someone at Seam comes up with a better solution. For example, here's a session scoped component that successfully works around this Seam / SFSB problem: -- @Stateful(name="orderSession") @Scope(ScopeType.SESSION) @CacheConfig(idleTimeoutSeconds=1800) // Same value as HttpSession timeout @Name("orderSession") @Interceptors(SeamInterceptor.class) -- To make it easier on yourself, put the 1800 value as a final constant in some utility class. Same situation for conversation scoped. For application scoped components you can use an idletimoutSeconds of Integer.MAX_VALUE and probably be relatively safe. > Component lifetimes not guaranteed for SFSB backed components. > -------------------------------------------------------------- > > Key: JBSEAM-279 > URL: http://jira.jboss.com/jira/browse/JBSEAM-279 > Project: JBoss Seam > Issue Type: Bug > Components: Core > Affects Versions: 1.0.1 > Reporter: ryan dewell > > Seam does not guarantee component lifecycles for SFSB backed components. > The container controls when SFSB's are removed / timed out. When Seam accesses an SFSB that has been removed by the container, it results in an EJBNoSuchObjectException. > The JBoss specific workaround for Session scoped components is to use the @CacheConfig annotation, setting the idle timeout to match the HttpSession timeout. Similar changes would have to be made to any Conversation scoped component that uses a timeout greater than the default SFSB timeout of 5 minutes (which just happens to be the default timeout for Seam conversations). > There is no workaround for Application scoped components. Once removed by the container, EJBNoSuchObjectException's will continue to be thrown as Seam tries to access them. > Seam's context model needs to somehow guarantee that its SFSB instances aren't removed by the container before Seam is finished with them. And/or, it needs to recover from EJBNoSuchObjectException's more gracefully, especially with regards to Application scoped components for which there is no workaround. -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCLUSTER-125) Port http sessioin passivation to tc6

by Hany Mesha (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-125?page=all ] Hany Mesha resolved JBCLUSTER-125. ---------------------------------- Resolution: Done Committed revision 56126 to svn repository. I'll open a new JIRA to add docs on how to enable and use session passivation > Port http sessioin passivation to tc6 > ------------------------------------- > > Key: JBCLUSTER-125 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-125 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: Q3Y6 > Reporter: Hany Mesha > Assigned To: Hany Mesha > Fix For: Q3Y6 > > > Port http session passivation implementation from tc5 to tc6 -- 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

19 years, 11 months

1
0
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 August 2006