May 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCL-129) Implement missing features suggested by the OSGi Spec

by Adrian Brock (JIRA)

Implement missing features suggested by the OSGi Spec ----------------------------------------------------- Key: JBCL-129 URL: https://jira.jboss.org/jira/browse/JBCL-129 Project: JBoss ClassLoader Issue Type: Feature Request Components: Modules Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossCL.2.0.9.GA , JBossCL.2.2.0.Alpha See the subtasks for this ongoing work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (JBCL-178) Add declarative translators metadata

by Ales Justin (JIRA)

Add declarative translators metadata ------------------------------------ Key: JBCL-178 URL: https://issues.jboss.org/browse/JBCL-178 Project: JBoss ClassLoader Issue Type: Feature Request Components: ClassLoader Affects Versions: JBossCL.2.2.0.Beta1 Reporter: Ales Justin Assignee: Ales Justin Allow for declarative translator addition. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCL-176) Allow for declarative domain configuration

by Ales Justin (JIRA)

Allow for declarative domain configuration ------------------------------------------ Key: JBCL-176 URL: https://jira.jboss.org/browse/JBCL-176 Project: JBoss ClassLoader Issue Type: Feature Request Components: ClassLoaderSystem, MetaData Reporter: Ales Justin Assignee: Ales Justin Fix For: JBossCL.2.2.0.Beta1 We should allow for more fine-grained CL domain configuration. e.g. jboss-cl-domain.xml or <parent-policy> inside jboss-classloading.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCL-131) Add a notion of on demand resolution

by Adrian Brock (JIRA)

Add a notion of on demand resolution ------------------------------------ Key: JBCL-131 URL: https://jira.jboss.org/jira/browse/JBCL-131 Project: JBoss ClassLoader Issue Type: Sub-task Components: Dependencies Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossCL.2.0.9.GA , JBossCL.2.2.0.Alpha OSGi has a notion where a dependent classloader/bundle is not rcreated/resolved until somebody wants to import one of its exports. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
18
0 / 0

[JBoss JIRA] Created: (JBMETA-331) Infinite loop in JBossAppMetaDataParser

by Stuart Douglas (JIRA)

Infinite loop in JBossAppMetaDataParser --------------------------------------- Key: JBMETA-331 URL: https://issues.jboss.org/browse/JBMETA-331 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Components: ear Reporter: Stuart Douglas Priority: Critical JBossAppMetaDataParser goes into an infinite loop on line 143, as the next element is never read from the stream. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-789) JPA subsystem: empty default DS

by Heiko Rupp (JIRA)

JPA subsystem: empty default DS ------------------------------- Key: AS7-789 URL: https://issues.jboss.org/browse/AS7-789 Project: Application Server 7 Issue Type: Bug Reporter: Heiko Rupp Assignee: Jason Greene Resource description for the JPA subsystem says default-datasource is required [domain@localhost:9999 subsystem=jpa] :read-resource-description(include-runtime=true,recursive=true) { "outcome" => "success", "result" => { "description" => "The configuration of the JPA subsystem.", "head-comment-allowed" => true, "tail-comment-allowed" => true, "namespace" => "urn:jboss:domain:jpa:1.0", "attributes" => {"default-datasource" => { "description" => "The name of the default global datasource.", "type" => STRING, "required" => true, "min-length" => 0, "access-type" => "read-write", "storage" => "configuration" }}, "operations" => undefined, "children" => undefined }, "compensating-operation" => undefined } But reading the resource shows an empty value This looks wrong, as an empty value is for sure no valid data source name. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (AS7-716) "server-config/jvm<name>:remove()" creates inconsistent state

by Heiko Braun (JIRA)

"server-config/jvm<name>:remove()" creates inconsistent state ------------------------------------------------------------- Key: AS7-716 URL: https://issues.jboss.org/browse/AS7-716 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.CR1 After removing the jvm resource I get this: [domain@localhost:9999 /] /host=local/server-config=server-one:read-resource(recursive=true) { "outcome" => "success", "result" => { "path" => undefined, "system-property" => undefined, "interface" => undefined, "jvm" => {}, "socket-binding-group" => undefined, "socket-binding-port-offset" => undefined, "name" => "server-one", "group" => "main-server-group", "auto-start" => true }, "compensating-operation" => undefined } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (AS7-692) Ability to modify server-group, subresource jvm

by Heiko Braun (JIRA)

Ability to modify server-group, subresource jvm ----------------------------------------------- Key: AS7-692 URL: https://issues.jboss.org/browse/AS7-692 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.Beta4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2976) DefaultMarshaller does not use supplied ObjectMarshallingStrategies

by Laird Nelson (JIRA)

DefaultMarshaller does not use supplied ObjectMarshallingStrategies ------------------------------------------------------------------- Key: JBRULES-2976 URL: https://issues.jboss.org/browse/JBRULES-2976 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.2.0.M1, 5.2.0.M2, 5.2.0.CR1 Reporter: Laird Nelson Assignee: Mark Proctor DefaultMarshaller.java does not use the supplied ObjectMarshallingStrategy as far as I can tell. When you create a Marshaller like this: {code} final Marshaller marshaller = MarshallerFactory.newMarshaller(knowledgeBase, new ObjectMarshallingStrategy[] { myStrategy }); assert marshaller != null; {code} And then use it like this (or similar): {code} final ByteArrayOutputStream baos = new ByteArrayOutputStream(); final ObjectOutputStream oos = new ObjectOutputStream(baos); final DroolsObjectOutputStream doos = new DroolsObjectOutputStream(oos); marshaller.marshall(doos, this.droolsSession); {code} ...the supplied strategy's read() and write() methods are never called. This is because DefaultMarshaller.java line 132 does not use the DefaultMarshaller's strategy, but the strategy of the incoming StatefulKnowledgeSession instead. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-3034) CompositeMaxDurationTrigger is not determining times correctly

by Mark Proctor (JIRA)

CompositeMaxDurationTrigger is not determining times correctly -------------------------------------------------------------- Key: JBRULES-3034 URL: https://issues.jboss.org/browse/JBRULES-3034 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor the logic for CompositeMaxDurationTrigger is wrong. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
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 May 2011