-
15. Re: Datasource Connection Properties using CollectionMetaTyp
starksm64 Feb 7, 2008 4:48 PM (in response to bytor99999)I added logging of the untested ManagedPropertys and this shows the following types:
1763 [main] WARN ProfileServiceUnitTestCase - testAddNoTxDataSource> untested properties: [connectionDestroyedCount, local-transaction, security-domain, maxConnectionsInUseCount, connection-properties, connectionCreatedCount, inUseConnectionCount, metadata, availableConnectionCount, minSize, maxSize, config-property, poolJndiName, connectionCount] 1763 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{connectionDestroyedCount,connectionDestroyedCount,metaType=SimpleMetaType:java.lang.Integer} 1763 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{local-transaction,localTransactions,metaType=SimpleMetaType:java.lang.Boolean} 1763 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{security-domain,securityMetaData,metaType=GenericMetaType:org.jboss.managed.api.ManagedObject} 1763 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{maxConnectionsInUseCount,maxConnectionsInUseCount,metaType=SimpleMetaType:java.lang.Long} 1763 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{connection-properties,dataSourceConnectionProperties,metaType=MapCompositeMetaType{java.util.Map}} 1764 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{connectionCreatedCount,connectionCreatedCount,metaType=SimpleMetaType:java.lang.Integer} 1764 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{inUseConnectionCount,inUseConnectionCount,metaType=SimpleMetaType:java.lang.Long} 1764 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{metadata,DBMSMetaData,metaType=MutableCompositeMetaType{org.jboss.resource.metadata.mcf.DBMSMetaData items=[name=typeMapping type=java.lang.String]}} 1764 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{availableConnectionCount,availableConnectionCount,metaType=SimpleMetaType:java.lang.Long} 1765 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{minSize,minSize,metaType=SimpleMetaType:java.lang.Integer} 1765 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{maxSize,maxSize,metaType=SimpleMetaType:java.lang.Integer} 1765 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{config-property,managedConnectionFactoryProperties,metaType=MapCompositeMetaType{java.util.Map}} 1765 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{poolJndiName,poolJndiName,metaType=SimpleMetaType:java.lang.String} 1765 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{connectionCount,connectionCount,metaType=SimpleMetaType:java.lang.Integer}
-
16. Re: Datasource Connection Properties using CollectionMetaTyp
bytor99999 Feb 7, 2008 4:56 PM (in response to bytor99999)When I print out the actual values from the DefaultDS ManagedComponent, I do see it as a Map. So I wonder what I saw in the DeploymentTemplateInfo?
Could they be different and cause any problems? -
17. Re: Datasource Connection Properties using CollectionMetaTyp
starksm64 Feb 7, 2008 5:10 PM (in response to bytor99999)Oh, yes, let me check that. It will be a problem because you would create the input connection-properties from the template, and the type would be wrong. One of the things we need to fix is that the template info properties are not derived from the management annotations, and therefore have to be duplicated and they get out of sync. The ManagementProperty annotation needs an includeInTemplate flag:
http://jira.jboss.com/jira/browse/JBMICROCONT-239 -
18. Re: Datasource Connection Properties using CollectionMetaTyp
starksm64 Feb 7, 2008 5:22 PM (in response to bytor99999)It looks like the xa ds template xa-datasource-properties should also have the wrong type, but those appear to be working. I'll look into why.
-
19. Re: Datasource Connection Properties using CollectionMetaTyp
starksm64 Feb 7, 2008 5:29 PM (in response to bytor99999)It turns out the ManagedProperty.setValue call is not validating the input MetaValue against the ManagedProperty MetaType, so if you input the right value it works as the server side ManagedProperty is of the correct type. I'll update the template types anyway.