October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-284) Error accessing overridden fields

by Kabir Khan (JIRA)

Error accessing overridden fields --------------------------------- Key: JBAOP-284 URL: http://jira.jboss.com/jira/browse/JBAOP-284 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kabir Khan Fix For: 2.0 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=89343 -- 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, 7 months

1
3
0 / 0

[JBoss JIRA] Commented: (JBAOP-253) Before release, submit the jar to the Messaging team for testing

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-253?page=comments#action_12344992 ] Kabir Khan commented on JBAOP-253: ---------------------------------- AOP 2.0 alpha1 can be downloaded from sourceforge - please try it out > Before release, submit the jar to the Messaging team for testing > ---------------------------------------------------------------- > > Key: JBAOP-253 > URL: http://jira.jboss.com/jira/browse/JBAOP-253 > Project: JBoss AOP > Issue Type: Task > Reporter: Ovidiu Feodorov > Assigned To: Kabir Khan > Fix For: 2.0.0.alpha2 > > -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-400) Dirty checking for @Mutable components

by Gavin King (JIRA)

Dirty checking for @Mutable components -------------------------------------- Key: JBSEAM-400 URL: http://jira.jboss.com/jira/browse/JBSEAM-400 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Introduce a Mutable interface with isDirty() to optimize replication of built-in components. -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-506) Exception thrown when retract, reassert and retract again

by Leo Liang (JIRA)

Exception thrown when retract, reassert and retract again --------------------------------------------------------- Key: JBRULES-506 URL: http://jira.jboss.com/jira/browse/JBRULES-506 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.4, 3.0.1 Reporter: Leo Liang Assigned To: Mark Proctor Attachments: Fact.java, test.drl, TestDriver.java In one rule retract the object and re-assert it, then retract the object again in the following activated rule. A null pointer exception will occur at this time. java.lang.NullPointerException at org.drools.reteoo.TerminalNode.retractTuple(TerminalNode.java:216) at org.drools.reteoo.LeftInputAdapterNode.retractObject(LeftInputAdapterNode.java:207) at org.drools.reteoo.ObjectSource.propagateRetractObject(ObjectSource.java:141) at org.drools.reteoo.ObjectTypeNode.retractObject(ObjectTypeNode.java:180) at org.drools.reteoo.Rete.retractObject(Rete.java:150) at org.drools.reteoo.ReteooRuleBase.retractObject(ReteooRuleBase.java:207) at org.drools.reteoo.ReteooWorkingMemory.doRetract(ReteooWorkingMemory.java:77) at org.drools.common.AbstractWorkingMemory.retractObject(AbstractWorkingMemory.java:668) at org.drools.base.DefaultKnowledgeHelper.retractObject(DefaultKnowledgeHelper.java:86) at com.ericsson.ruletest.debug.Rule_test2_0.consequence(Rule_test2_0.java:8) at com.ericsson.ruletest.debug.Rule_test2_0ConsequenceInvoker.evaluate(Rule_test2_0ConsequenceInvoker.java:22) at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:437) at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:407) at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:269) at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:256) at com.ericsson.ruletest.TestDriver.main(TestDriver.java:26) The given test case is the the simplified from my production code. --------------- test.drl ------------------------ package com.ericsson.ruletest.debug import com.ericsson.ruletest.Fact; rule "test1" salience 10 no-loop true when input:Fact(); then retract(input); assert(input); end; rule "test2" salience 0 no-loop true when input:Fact(); then retract(input); end; -- 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, 7 months

3
8
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1073) UserPortlet UI redone

by Roy Russo (JIRA)

UserPortlet UI redone --------------------- Key: JBPORTAL-1073 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1073 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.Alpha1 Reporter: Roy Russo Assigned To: Roy Russo Fix For: 2.6.Alpha1 -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-601) Place Messaging artifacts in the repository

by Richard Achmatowicz (JIRA)

Place Messaging artifacts in the repository ------------------------------------------- Key: JBMESSAGING-601 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-601 Project: JBoss Messaging Issue Type: Task Components: Tests and Performance Reporter: Richard Achmatowicz Assigned To: Ovidiu Feodorov Priority: Critical Fix For: 1.2.0.Beta1 In order to test Messaging within the AS testsuite, we need a scoped deployment of Messaging (as Messaging currently uses modified versions of Remoting and other jars). We also want to use release-admin.xml to create the Messaging configuration for the application server. (NOTE: All of this assumes a JMX-based deployment and testing context, as discussed in our recent conversion concerning JMX vs MC based-deployments.) I need to get these artifacts (jboss-messagings-coped.sar, release-admin.xml) somehow, for each release of Messaging which is to be tested. This means placing copies in repository.jboss.com. As for the contents of the scoped sar, I need a version which includes the following: (i) all the Messaging classes (ii) the modified jars for remoting etc. and a service descriptor to turn on scoping (iii) service descriptors for deployment of the Messaging MBeans via JMX The contents reflect the fact that this sar will be used together with release-admin,xml to create a Messaging configuration which can be used to start the AS with and run integration tests against Messaging. This sar need not contain any test-related deployments, as the testsuite can manage those separately. Because we may want to test differing versions of Messaging, such a sar (e.g. named jboss-messaging-scoped.sar) and a copy of release-admin.xml should be available for each version in the repository. At present, the repository supports two versions of Messaging: 1.0.1.CR4, and snapshot. I suppose these could be placed in a resources subdirectory on the repository. -- 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, 7 months

2
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-734) Run-As principal is not properly identified by the Run As Security Interceptor

by Anil Saldhana (JIRA)

Run-As principal is not properly identified by the Run As Security Interceptor ------------------------------------------------------------------------------ Key: EJBTHREE-734 URL: http://jira.jboss.com/jira/browse/EJBTHREE-734 Project: EJB 3.0 Issue Type: Bug Components: Security Affects Versions: EJB 3.0 RC9 - FD Reporter: Anil Saldhana Fix For: EJB 3.0 RC10 - FD Consider the scenario: a) EJB3 beans have the RunAs annotations. b) There is an override of security-identity in jboss.xml The current metamodel built in ejb3 layer does not build the security-identity metadata correctly(builds only if ejb-jar.xml was existent). -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-187) Update the Transformation Service interface to use the ESB Message type

by Tom Fennelly (JIRA)

Update the Transformation Service interface to use the ESB Message type ----------------------------------------------------------------------- Key: JBESB-187 URL: http://jira.jboss.com/jira/browse/JBESB-187 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.0 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.0 -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-795) listIterator in a cached list throws exception on empty list

by Nitzan Niv (JIRA)

listIterator in a cached list throws exception on empty list ------------------------------------------------------------ Key: JBCACHE-795 URL: http://jira.jboss.com/jira/browse/JBCACHE-795 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Reporter: Nitzan Niv Assigned To: Ben Wang executing listIterator() on an empty cached List throws Exception even though it should be a valid operation that returns a valid iterator. This also affects equals() (when the object is a Java empty list and the parameter is a cached empty list). The following changes in CachedListImpl fix this: in MyListIterator constructor: if(index < 0 || index > list_.size()) ... in hasNext(): return (index < list_.size()); -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-170) ObjectToCVSString needs to inform invoker of errors

by Mark Little (JIRA)

ObjectToCVSString needs to inform invoker of errors --------------------------------------------------- Key: JBESB-170 URL: http://jira.jboss.com/jira/browse/JBESB-170 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Core Reporter: Mark Little Assigned To: Tom Fennelly Priority: Minor Fix For: 4.0 [junit] 14:12:30,626 ERROR ObjectToCSVString:113 - Bean method: getId not found/accessible on message object org.jboss.soa.esb.actions.converters.ObjectToCSVStringUnitTest$TestBean [junit] java.lang.NoSuchMethodException: org.jboss.soa.esb.actions.converters.ObjectToCSVStringUnitTest$TestBean.getId() [junit] at java.lang.Class.getMethod(Class.java:1581) is thrown if a method signature is not available. Should be configurable whether or not the processor continues to operate. Also, if it does then it would be good if it flagged in the output that the signature was invalid. -- 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, 7 months

2
1
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 October 2006