Constructor property support

[arinban]

Tibcos EMS Queue implementation doesn't support a setDestination method, so a dynamic, named Queue can only be created by passing the name into the constructor. This means they can't be created using an ActivationSpec.

Suggest adding support for specifying constructor properties in the ActivationSpec. This could either be a specific named property or the DestinationProperty could be used to hold constructor properties, for example: ConstructorArg=x.y.z,OtherProp=xxx or assume a no name property is a constructor argument: =x.y.z,OtherProp=xxx multiple args could also be supported ConstructorArg[0]=x.y.z,ConstructorArg[1]=a.b.c,OtherProp=xxx

This would (at minimum) only involve changes in the ObjectBuilderFactory.ClassObjectBuilder.createObject() method and would support all objects created by the ObjectBuilder

Environment

Operating System: All Platform: All

Affected Versions

[current]

[arinban]

• Issue Imported From: https://github.com/ari-ban/test1/issues/6
• Original Issue Raised By:@arinban
• Original Issue Assigned To: @glassfishrobot

[arinban]

@arinban Commented

• Issue Imported From: https://github.com/ari-ban/glassfish-genericjmsra/issues/6
• Original Issue Raised By:@arinban
• Original Issue Assigned To: @glassfishrobot

[arinban]

@arinban Commented @arinban Commented

• Issue Imported From: https://github.com/javaee/glassfish-genericjmsra/issues/6
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @glassfishrobot

[arinban]

@arinban Commented @arinban Commented @glassfishrobot Commented Reported by andrewsmallbone

[arinban]

@arinban Commented @arinban Commented @glassfishrobot Commented binod said: Re assigning this issue to Andrew.

[arinban]

@arinban Commented @arinban Commented @glassfishrobot Commented @sivakumart said: Andrew,

Suggest adding support for specifying constructor properties in the ActivationSpec. This issue could be solved using the above mechanism. However, wouldn't it be more useful if we could have a generic mechanism for solving such customizations. In one of our earlier discussions while starting the project, one idea was to have a generic factory based implementation to create CF/Admin Objects etc. We could have MoM product-specific factory implementations (classes) [i.e an implementation for Tibco, one for Sonic MQ and so on] that could have their own custom means of creating and initializing these objects. Users could then while configuring the RA choose which MoM-Factory implementation they want to work with and properties specific to that Factory implementation.

Would this approach be useful? Could we consider this as well while fixing this issue?

[arinban]

@arinban Commented @arinban Commented @glassfishrobot Commented Was assigned to andrewsmallbone

[arinban]

@arinban Commented @arinban Commented @glassfishrobot Commented This issue was imported from java.net JIRA GENERICJMSRA-6

[arinban]

Closing this as this issue is migrated to https://github.com/ari-ban/test1/issues/6