I can test it for you if you put the binary build to somewhere I can pick it up. Or let me know how to build 2.1.2. This is a critical bug preventing us going forward with Geronimo.
JIRA [EMAIL PROTECTED] wrote: > > > [ > https://issues.apache.org/jira/browse/GERONIMO-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Jarek Gawor updated GERONIMO-4131: > ---------------------------------- > > Attachment: GERONIMO-4131.patch > > Updated the patch to handle the port property (the port property has two > setters setPort(int) and sertPort(String) so updated the code to also > lookup the setters using the corresponding primitive type (if any)). > > >> Problems with WebSphere MQ RA deployment >> ---------------------------------------- >> >> Key: GERONIMO-4131 >> URL: https://issues.apache.org/jira/browse/GERONIMO-4131 >> Project: Geronimo >> Issue Type: Bug >> Security Level: public(Regular issues) >> Components: connector >> Affects Versions: 2.0.1, 2.0.2, 2.1, 2.1.1, 2.1.2 >> Reporter: Kevan Miller >> Assignee: Jarek Gawor >> Fix For: 2.1.2 >> >> Attachments: GERONIMO-4131.patch, GERONIMO-4131.patch >> >> >> A user reported problems deploying an MQ RA on Geronimo. Looks like there >> are several problems. >> 1) we don't like config-property-name values in ra.xml to start with a >> lower case letter >> 2) our mechanism for introspecting the implementation classes (e.g. >> managedconnectionfactory-class) is not working properly. there can be >> multiple "set" methods taking different parameter types. This is leading >> to type-mismatches as we try to set attributes. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > > > -- View this message in context: http://www.nabble.com/-jira--Created%3A-%28GERONIMO-4131%29-Problems-with-WebSphere-MQ-RA-deployment-tp17991183s134p18495691.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
