May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1395) Checking "Use WSDL" and then "Return to list" from the WSRP Consumer configuration causes previous URLs to be lost

by Chris DeLashmutt (JIRA)

Checking "Use WSDL" and then "Return to list" from the WSRP Consumer configuration causes previous URLs to be lost ------------------------------------------------------------------------------------------------------------------ Key: JBPORTAL-1395 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1395 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6.CR2 Reporter: Chris DeLashmutt Fix For: 2.6 Final It seems that the "Return to list" button on the WSRP Consumer Configuration view doesn't discard changes that were made in the UI. For instance, if I follow these steps: 1. Click "configure" for a WSRP consumer configuration that is not using WSDL (such as the "self" consumer) 2. Check the "Use WSRP" check box. 3. Click "Return to list". 4. An error message shows up at the top of the WSRP Consumer portlet about a field being left blank 5. Click "Configure" on the consumer that was "Configured" in step 1. At this point, the previous settings have been wiped out. -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-4420) Separate classloader leak tests from the 'all' tests

by Brian Stansberry (JIRA)

Separate classloader leak tests from the 'all' tests ---------------------------------------------------- Key: JBAS-4420 URL: http://jira.jboss.com/jira/browse/JBAS-4420 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta2 Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.1.CR1 The classloader leak unit tests may generate enough garbage to fill 99.9% of free memory if there is a leak or if some SoftReference prevents collection of the classloader for a while. The memory is released as part of the test (which includes System.gc() calls in finally blocks to make sure the gc runs to clean it up before the next test.) Still, filling the heap like that is potentially disruptive to the VM, so these tests should be separated into their own test run, segregated from the main 'all' tests. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAOP-367) Add JBoss EULA to aop 2.0 distribution

by Kabir Khan (JIRA)

Add JBoss EULA to aop 2.0 distribution -------------------------------------- Key: JBAOP-367 URL: http://jira.jboss.com/jira/browse/JBAOP-367 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha3 -- 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, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-4419) DatabaseServerLoginModule and JaasSecurityManagerService DefaultCacheTimeout

by Magesh Kumar B (JIRA)

DatabaseServerLoginModule and JaasSecurityManagerService DefaultCacheTimeout ---------------------------------------------------------------------------- Key: JBAS-4419 URL: http://jira.jboss.com/jira/browse/JBAS-4419 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.4.GA Reporter: Magesh Kumar B Assigned To: Scott M Stark According to this WIKI http://wiki.jboss.org/wiki/Wiki.jsp?page=CachingLoginCredentials when DefaultCacheTimeout is set to zero, the login information is lost and the client has to relogin again. Now the understanding is if a simple client uses the JndiLoginInitialContextFactory then until the user logsout or the context is expired the the Credentials has to be cached. This happens perfectly when using UsersRolesLoginModule. But the same principal is not working when using DatabaseServerLoginModule. I have tested this with both the JBoss versions 4.0.4 GA and 4.0.5 GA. Attached are two test cases ejb3-UserRolesLoginModule.zip and ejb3-DatabaseServerLoginModule.zip each testing the loginmodule behaviours. For the ejb3-DatabaseServerLoginModule please add the following configuration to the login-config.xml <application-policy name = "purchase"> <authentication> <login-module code = "org.jboss.security.auth.spi.DatabaseServerLoginModule" flag = "required"> <module-option name = "unauthenticatedIdentity">guest</module-option> <module-option name = "dsJndiName">java:/DefaultDS</module-option> <module-option name = "principalsQuery">SELECT PASSWD FROM JMS_USERS WHERE USERID=?</module-option> <module-option name = "rolesQuery">SELECT ROLEID, 'Roles' FROM JMS_ROLES WHERE USERID=?</module-option> </login-module> <login-module code = "org.jboss.security.ClientLoginModule" flag = "required"/> </authentication> </application-policy> The contents of the zip files are straight forward and each has a Client.java class that calls their respective ejbs. -- 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, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-927) enhance Calendar to make it more reusable

by Martin Goldhahn (JIRA)

enhance Calendar to make it more reusable ----------------------------------------- Key: JBPM-927 URL: http://jira.jboss.com/jira/browse/JBPM-927 Project: JBoss jBPM Issue Type: Patch Components: Core Engine Environment: Java Reporter: Martin Goldhahn Assigned To: Tom Baeyens Attachments: calendar.patch The patch provided adds a new constructor to the org.jbpm.calendar.BusinessCalendar class that makes it possible to instantiate a callendar with a set of holidays other than the one provided in the system setting: Index: src/java.jbpm/org/jbpm/calendar/BusinessCalendar.java =================================================================== RCS file: /cvsroot/jbpm/jbpm.3/src/java.jbpm/org/jbpm/calendar/BusinessCalendar.java,v retrieving revision 1.6 diff -u -r1.6 BusinessCalendar.java --- src/java.jbpm/org/jbpm/calendar/BusinessCalendar.java 4 Jan 2006 15:18:50 -0000 1.6 +++ src/java.jbpm/org/jbpm/calendar/BusinessCalendar.java 4 Apr 2007 12:20:59 -0000 @@ -52,8 +52,11 @@ } public BusinessCalendar() { + this(getBusinessCalendarProperties()); + } + + public BusinessCalendar(Properties calendarProperties) { try { - Properties calendarProperties = getBusinessCalendarProperties(); weekDays = Day.parseWeekDays(calendarProperties, this); holidays = Holiday.parseHolidays(calendarProperties, this); -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWEB-80) The server gives out of memory error if i hot deploy a web application by changing the timestamp of the web.xml

by yogendra g (JIRA)

The server gives out of memory error if i hot deploy a web application by changing the timestamp of the web.xml --------------------------------------------------------------------------------------------------------------- Key: JBWEB-80 URL: http://jira.jboss.com/jira/browse/JBWEB-80 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBoss Web Standalone 4.0.4 RC1 Environment: jdk1.4.2_08 , windows xp Reporter: yogendra g Assigned To: Mladen Turk During the development i do not restart the app server. I touch the web.xml and my web application gets redployed. I keep doing this, and at a point of time "The server gives OutOfMemory error" I dont have solution for this because i have not delved into the jboss code, but I am staunchest supporter of jboss, and i made other projects out here to use jboss app server, and now during developement its giving this problem. Is it fixed in any of the latest releases? -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Resolved: (JBMICROCONT-23) Lifecycle

by Ales Justin (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-23?page=all ] Ales Justin resolved JBMICROCONT-23. ------------------------------------ Resolution: Done Added xml attribute to lifecycleType: ignore xsd:boolean optional default=false. All lifecycle annotations have been fixed as well. This change is checked at LifecycleAction. In case of existing ignore=true attribute whole install/uninstall invocation is passed. > Lifecycle > --------- > > Key: JBMICROCONT-23 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-23 > Project: JBoss MicroContainer > Issue Type: Task > Components: Dependency > Reporter: Adrian Brock > Assigned To: Ales Justin > Fix For: JBossMC-2.0.0.GA > > > Add support for lifecycle annotations > @CreateLifeCycle > @StartLifeCycle > @StopLifeCycle > @DestroyLifeCycle > and annotate org.jboss.system.Service. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAOP-312) Package retroed deployer for JBoss 4 on jdk1.4

by Kabir Khan (JIRA)

Package retroed deployer for JBoss 4 on jdk1.4 ---------------------------------------------- Key: JBAOP-312 URL: http://jira.jboss.com/jira/browse/JBAOP-312 Project: JBoss AOP Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-852) Bug on download deployment snapshot

by Fernando Meyer (JIRA)

Bug on download deployment snapshot ------------------------------------ Key: JBRULES-852 URL: http://jira.jboss.com/jira/browse/JBRULES-852 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Fernando Meyer Assigned To: Fernando Meyer -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Reopened: (JBMICROCONT-23) Lifecycle

by Ales Justin (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-23?page=all ] Ales Justin reopened JBMICROCONT-23: ------------------------------------ Add ability to ignore (default) lifecycle metadata. See http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045566. > Lifecycle > --------- > > Key: JBMICROCONT-23 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-23 > Project: JBoss MicroContainer > Issue Type: Task > Components: Dependency > Reporter: Adrian Brock > Assigned To: Ales Justin > Fix For: JBossMC-2.0.0.GA > > > Add support for lifecycle annotations > @CreateLifeCycle > @StartLifeCycle > @StopLifeCycle > @DestroyLifeCycle > and annotate org.jboss.system.Service. -- 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, 2 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 May 2007