February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-469) function name overloading

by Mark Proctor (JIRA)

function name overloading ------------------------- Key: JBRULES-469 URL: http://jira.jboss.com/jira/browse/JBRULES-469 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rule Assemply/SPI Reporter: Mark Proctor Assigned To: Mark Proctor Currently the function resolver is limited with regards to overloading and you can only use the same function name once in a package. We need to have more correct overloading and ofcourse handle multiple versions of the same function name in a package. -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBCOMMON-14) Release JBossCommon 2.0.4.GA

by Dimitris Andreadis (JIRA)

Release JBossCommon 2.0.4.GA ---------------------------- Key: JBCOMMON-14 URL: http://jira.jboss.com/jira/browse/JBCOMMON-14 Project: JBoss Common Issue Type: Task Security Level: Public (Everyone can see) Components: core Reporter: Dimitris Andreadis Fix For: 2.0.4.GA -- 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, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBFORUMS-176) EditNotificationType in MyForums view

by Ryszard Kozmik (JIRA)

EditNotificationType in MyForums view ------------------------------------- Key: JBFORUMS-176 URL: http://jira.jboss.com/jira/browse/JBFORUMS-176 Project: JBoss Forums Issue Type: Sub-task Components: Forum View Layer Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.0.1 RC MyForums view have to support chagning of notification type. -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-676) Delete action for a newly created asset

by Michael Neale (JIRA)

Delete action for a newly created asset --------------------------------------- Key: JBRULES-676 URL: http://jira.jboss.com/jira/browse/JBRULES-676 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1266) CMS Security and User account issue

by Sohil Shah (JIRA)

CMS Security and User account issue ----------------------------------- Key: JBPORTAL-1266 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1266 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.Alpha2, 2.6.Beta1 Reporter: Sohil Shah Assigned To: Roy Russo Priority: Minor Fix For: 2.6.CR1 Steps to reproduce: Take a fresh portal database, use the LDAP Identity Module, Login as user/user Note: make sure the portal database is fresh, otherwise this wont reproduce -- 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, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBSER-84) Improve serialization of immutable objects

by Michael Santos (JIRA)

Improve serialization of immutable objects ------------------------------------------ Key: JBSER-84 URL: http://jira.jboss.com/jira/browse/JBSER-84 Project: JBoss Serialization Issue Type: Feature Request Reporter: Michael Santos Assigned To: Clebert Suconic It is common for objects to contain references to hundreds or thousands of equal immutable object instances, especially java.lang.Number subclasses. Some immutable objects produce a considerable serialized amount of information, such as java.math.BigDecimal. However, there's usually no reason for different instances being used to represent the same value; they only exist due to the way they were produced (parsing &, conversion APIs and JDBC are definitely fine examples of that). Experiments on a particular project have shown replacing all these equal instances by one of them can reduce the serialized size of some objects by half. Therefore, JBoss Serialization should provide way to allow users to tell it's ok to use the same reference for all these immutable instances and which classes are to be considered immutable and replace them during the writing phase. This would be much more efficient and wouldn't require developers to rewrite their code in order to optimize serialization of some objects. A global way, such as system property, of telling the API to do this by default with the most commonly used Java SE classes would be desirable as well. -- 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, 3 months

4
7
0 / 0

[JBoss JIRA] Created: (JBTM-173) Integrate with AS 4.2

by Mark Little (JIRA)

Integrate with AS 4.2 --------------------- Key: JBTM-173 URL: http://jira.jboss.com/jira/browse/JBTM-173 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Release Reporter: Mark Little Assigned To: Jonathan Halliday Fix For: 4.2.3 -- 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, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1184) Update CMS TestSuite with workflow usecases

by Sohil Shah (JIRA)

Update CMS TestSuite with workflow usecases ------------------------------------------- Key: JBPORTAL-1184 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1184 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.Alpha1 Reporter: Sohil Shah Assigned To: Sohil Shah Fix For: 2.6.Beta1 -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1185) Update CMS TestSuite with fine grained security usecases

by Sohil Shah (JIRA)

Update CMS TestSuite with fine grained security usecases -------------------------------------------------------- Key: JBPORTAL-1185 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1185 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.Alpha1 Reporter: Sohil Shah Assigned To: Sohil Shah Fix For: 2.6.Beta1 -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3724) NotFoundInDispatcherException from InvokerLocator when accessing remote calls when on a non default port

by Grant Quimby (JIRA)

NotFoundInDispatcherException from InvokerLocator when accessing remote calls when on a non default port -------------------------------------------------------------------------------------------------------- Key: JBAS-3724 URL: http://jira.jboss.com/jira/browse/JBAS-3724 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services, EJB3, Remoting Affects Versions: JBossAS-4.0.4.GA Environment: One JBoss 4.0.4.GA install with two instances, one on the default ports and one on ports with an increase of 1000 on all port numbers. Reporter: Grant Quimby Assigned To: Dimitris Andreadis Priority: Blocker When trying to access a remote application that is running in a server instance that does not have the default InvokerLocator port (3873) the remote caller recieves a NotFoundInDispatcherException when trying to call a method in the EJB3 Stateless Session Bean as the EJB3 Session Bean's InvokerLocator is at port 4873 and not port 3873 where the Remote Proxy looks. Similar issue for Service Beans at http://www.jboss.com/index.html?module=bb&op=viewtopic&t=89537 This is okay presently but in approximately two weeks we need to be running four instances with Session beans in two of them, which is currently not possible in a production version. -- 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, 3 months

3
2
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 February 2007