It looks to me as if someone took an ra.xml for the amq resource adapter, changed the namespace, and added an environment section. That's not a valid or useful geronimo-ra.xml in any possibly way.
Inbound resource adapters are configured via the mdb that they drive. The mdb implements the appropriate interface which selects the message-listener. Then you specify the activation spec properties for the mdb. Admin objects are configured in geronimo-ra.xml, but you specify the class and then have admin-object-instance elements nested for the admin objects of that class. And you need config-property values to do any good at all :-) thanks for noticing this. Anyone have time to fix it? thanks david jencks On Dec 19, 2012, at 9:53 AM, Murray Todd Williams wrote: > I'm in the process of developing a bi-directional JCA adapter, and I'm trying > to deploy the skeleton to Geronimo. While writing the deployment plan > (geronimo-ra.xml) my Eclipse editor is complaining that the schema > (http://geronimo.apache.org/xml/ns/j2ee/connector-1.2) doesn't allow for an > <inbound-resourceadapter> element. > > In other words, the sample plan in the Geronimo v2.2 docs: > > https://cwiki.apache.org/GMOxDOC22/geronimo-raxml.html#geronimo-ra.xml-%3Cadminobject%3E > > doesn't validate! > > Am I missing something? > > > > -- > View this message in context: > http://apache-geronimo.328035.n3.nabble.com/JCA-deployment-plan-schema-doesn-t-include-inbound-resourceadapter-tp3986165.html > Sent from the Users mailing list archive at Nabble.com.
