April 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCL-96) Expose Module callback registration in ClassLoading

by Ales Justin (JIRA)

Expose Module callback registration in ClassLoading --------------------------------------------------- Key: JBCL-96 URL: https://jira.jboss.org/jira/browse/JBCL-96 Project: JBoss ClassLoader Issue Type: Task Components: Modules Affects Versions: JBossCL.2.0.4.GA Reporter: Ales Justin Assignee: Ales Justin Fix For: 2.0.5.GA Currently Module registration to ClassLoading is done two ways: * via contextual callback * direct programmatic usage in describe deployer Any other bean/service that monitors Module creation should plug into ClassLoading in order to get the Module in the right state. This can be done via ModuleRegistry. See forum (actually it's jboss-dev) discussion for more info. -- 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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBXB-195) SingletonSchemaResolverFactory should use Service Provider SPI to allow for dynamic additions

by Carlo de Wolf (JIRA)

SingletonSchemaResolverFactory should use Service Provider SPI to allow for dynamic additions --------------------------------------------------------------------------------------------- Key: JBXB-195 URL: https://jira.jboss.org/jira/browse/JBXB-195 Project: JBoss XML Binding (JBossXB) Issue Type: Feature Request Reporter: Carlo de Wolf See http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html#Service%20Provider So I should be able to create META-INF/services/org.jboss.xb.spi.JaxbSchema with: org.jboss.reloaded.repoclassloader.schema.ReportClassLoaderSchema class RepoClassLoaderSchema implements JaxbSchema { String getNamespace() { return "urn:jboss:repoclassloader:1.0" }; Class<?> getReference() { return RepoClassLoaderFactory10.class }; } -- 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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBMAN-70) DeploymentTemplateInfoFactory does not honor @MetaMapping

by Scott M Stark (JIRA)

DeploymentTemplateInfoFactory does not honor @MetaMapping --------------------------------------------------------- Key: JBMAN-70 URL: https://jira.jboss.org/jira/browse/JBMAN-70 Project: JBoss Managed Issue Type: Bug Components: managedobject Affects Versions: JBossMan.2.1.0.CR5 Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossMan.2.1.0.CR6 When a template property has its type mapping override via a @MetaMapping: @ManagementProperty(includeInTemplate=true) @MetaMapping(StringObjectNameMetaMapper.class) public ObjectName getNameAsString() Creating a template via the DeploymentTemplateInfoFactory fails to show the expected type on the property. -- 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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBMAN-71) Unwrapping null primitive SimpleValues should return non-null

by Scott M Stark (JIRA)

Unwrapping null primitive SimpleValues should return non-null ------------------------------------------------------------- Key: JBMAN-71 URL: https://jira.jboss.org/jira/browse/JBMAN-71 Project: JBoss Managed Issue Type: Feature Request Components: metatype Affects Versions: JBossMan.2.1.0.CR5 Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossMan.2.1.0.CR6 When a SimpleValue that corresponds to a primitive has a null value, unwrapping that should return the corresponding non-null uninitialized value the primitive would have. -- 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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Commented: (JBAS-6718) AS5 plugin: If the "use-java-context" property is left unset when creating a datasource, it now gets set to "false" by default instead of to "true"

by Scott M Stark (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-6718?page=com.atlassian.jira.plug... ] Scott M Stark commented on JBAS-6718: ------------------------------------- I'm not seeing this. If I comment out the setting of the use-java-context in the ProfileServivceUnitTestCase.testAddDataSource, I do see the use-java-context set to true: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <datasources> <local-tx-datasource> <jndi-name>TestLocalTxDs</jndi-name> <rar-name>jboss-local-jdbc.rar</rar-name> <use-java-context>true</use-java-context> ... This is the default value in the template as well: static { // populate the default values defaultValues.put("use-java-context", new SimpleValueSupport(SimpleMetaType.BOOLEAN_PRIMITIVE, true)); defaultValues.put("min-pool-size", new SimpleValueSupport(SimpleMetaType.INTEGER_PRIMITIVE, 0)); defaultValues.put("max-pool-size", new SimpleValueSupport(SimpleMetaType.INTEGER_PRIMITIVE, 10)); defaultValues.put("blocking-timeout-millis", new SimpleValueSupport(SimpleMetaType.LONG_PRIMITIVE, 3000)); defaultValues.put("idle-timeout-minutes", new SimpleValueSupport(SimpleMetaType.INTEGER_PRIMITIVE, 30)); defaultValues.put("background-validation", new SimpleValueSupport(SimpleMetaType.BOOLEAN_PRIMITIVE, false)); defaultValues.put("background-validation-millis", new SimpleValueSupport(SimpleMetaType.LONG_PRIMITIVE, 0)); defaultValues.put("validate-on-match", new SimpleValueSupport(SimpleMetaType.BOOLEAN_PRIMITIVE, true)); defaultValues.put("interleaving", new SimpleValueSupport(SimpleMetaType.BOOLEAN_PRIMITIVE, false)); defaultValues.put("allocation-retry", new SimpleValueSupport(SimpleMetaType.INTEGER_PRIMITIVE, 0)); defaultValues.put("allocation-retry-wait-millis", new SimpleValueSupport(SimpleMetaType.INTEGER_PRIMITIVE, 5000)); defaultValues.put("prepared-statement-cache-size", new SimpleValueSupport(SimpleMetaType.INTEGER_PRIMITIVE, 0)); defaultValues.put("share-prepared-statements", new SimpleValueSupport(SimpleMetaType.BOOLEAN_PRIMITIVE, false)); defaultValues.put("set-tx-query-timeout", new SimpleValueSupport(SimpleMetaType.BOOLEAN_PRIMITIVE, false)); defaultValues.put("query-timeout", new SimpleValueSupport(SimpleMetaType.INTEGER_PRIMITIVE, 0)); } > AS5 plugin: If the "use-java-context" property is left unset when creating a datasource, it now gets set to "false" by default instead of to "true" > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBAS-6718 > URL: https://jira.jboss.org/jira/browse/JBAS-6718 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ProfileService > Environment: JBoss AS Branch_5_x r86370, embjopr r256 > Reporter: Farah Juma > Assignee: Scott M Stark > Priority: Critical > Fix For: JBossAS-5.1.0.CR1 > > > Steps to reproduce: > Create a new datasource and leave the "Use Java Context" property unset. If you check the "use-java-context" property of the ManagedComponent or look at the -ds.xml file that was created, you'll see that "use-java-context" is set to "false". Until recently, this property was being set to "true" by default. -- 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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBMAN-69) Add activation config setting to ManagedProperty

by Scott M Stark (JIRA)

Add activation config setting to ManagedProperty ------------------------------------------------ Key: JBMAN-69 URL: https://jira.jboss.org/jira/browse/JBMAN-69 Project: JBoss Managed Issue Type: Feature Request Components: managedobject Affects Versions: JBossMan.2.1.0.CR5 Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossMan.2.1.0.CR6 For JBAS-6689, we need a notion of the property value can be applied to a component: enum ActivationPolicy { IMMEDIATE, COMPONENT_RESTART, DEPLOYMENT_RESTART, SERVER_RESTART } -- 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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBMAN-68) Add ManagedProperty.isModified

by Scott M Stark (JIRA)

Add ManagedProperty.isModified ------------------------------ Key: JBMAN-68 URL: https://jira.jboss.org/jira/browse/JBMAN-68 Project: JBoss Managed Issue Type: Feature Request Components: managedobject Affects Versions: JBossMan.2.1.0.CR5 Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossMan.2.1.0.CR6 Add support for isModified to indicate if a property value has been changed. -- 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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Updated: (JBAS-6719) AS5 plugin: After creating a new Topic or Queue, the configuration properties are set to their default values instead of to the values that were specified during creation

by Charles Crouch (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-6719?page=com.atlassian.jira.plug... ] Charles Crouch updated JBAS-6719: --------------------------------- Component/s: ProfileService > AS5 plugin: After creating a new Topic or Queue, the configuration properties are set to their default values instead of to the values that were specified during creation > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBAS-6719 > URL: https://jira.jboss.org/jira/browse/JBAS-6719 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ProfileService > Environment: JBoss AS Branch_5_x r86203, embjopr r251 > Reporter: Farah Juma > Assignee: Emanuel Muckenhuber > Priority: Critical > Fix For: JBossAS-5.1.0.CR1 > > > Steps to reproduce: > Create a new Topic or Queue and set values for each of the properties (eg. Clustered, Down Cache Size, Full Size, Max Delivery Attempts, etc.). After clicking "Save", navigate to the "Configuration" page for the new resource. The property values that appear on the page seem to be the default values instead of the values that were specified during creation. -- 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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-6717) AS5 plugin: The value of "Connections In Use Count" that gets displayed in the result of the "List Formatted Sub Pool Statistics" operation does not get updated after connections are closed

by Charles Crouch (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-6717?page=com.atlassian.jira.plug... ] Charles Crouch updated JBAS-6717: --------------------------------- Component/s: ProfileService > AS5 plugin: The value of "Connections In Use Count" that gets displayed in the result of the "List Formatted Sub Pool Statistics" operation does not get updated after connections are closed > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBAS-6717 > URL: https://jira.jboss.org/jira/browse/JBAS-6717 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ProfileService > Environment: JBoss Branch_5_x r85739, embjopr r209 > Reporter: Farah Juma > Assignee: Jesper Pedersen > Priority: Critical > Fix For: JBossAS-5.1.0.CR1 > > > Steps to reproduce: > Create a new -ds.xml file. Set values for min-pool-size and max-pool-size. Request multiple connections from the connection pool. Then, close a few of these connections. Perform the "List Formatted Sub Pool Statistics" operation for this datasource. The value of "Connections In Use Count" in the result of the operation is not updated to reflect the closed connections. > For example, when min-pool-size=5, max-pool-size=20, and there are 10 connections in use, the following is the result of the "List Formatted Sub Pool Statistics" operation after closing 2 connections: > Sub Pool Statistics: > Sub Pool Count: 1 > ------------------------------------------------------ > Track By Transaction: true > Available Connections Count: 12 > Max Connections In Use Count:10 > Connections Destroyed Count:0 > **Connections In Use Count:10** > Total Block Time:0 > Average Block Time For Sub Pool:0 > Maximum Wait Time For Sub Pool:0 > Total Timed Out:0 > The value of "Connections In Use Count" should be 8 in this case. -- 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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-6716) add back securityConfig config property to JMS destination resources

by Charles Crouch (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-6716?page=com.atlassian.jira.plug... ] Charles Crouch updated JBAS-6716: --------------------------------- Component/s: ProfileService > add back securityConfig config property to JMS destination resources > --------------------------------------------------------------------- > > Key: JBAS-6716 > URL: https://jira.jboss.org/jira/browse/JBAS-6716 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ProfileService > Reporter: Charles Crouch > Assignee: Emanuel Muckenhuber > Priority: Critical > Fix For: JBossAS-5.1.0.CR1 > > Attachments: MyQueueWithSecurityConfig-service.xml > > > e.g. > <c:map-property required="false" name="securityConfig" description="The destination's security configuration"> > <c:simple-property required="false" name="tagName"/> > </c:map-property> -- 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

15 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2009