On Apr 13, 2007, at 11:47 AM, Hiram Chirino wrote:

Hi Jason,

On 4/12/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
I'm confused... why would folks change the ra.xml... this is supposed
to define the resource adapter and how it can be configured via
vendor configuration files.  I would not expect users to need to
change the file bundled in the rar itself.


I can't comment why the J2EE spec choose to recommend folks package
the component implementation and configuration together in the same
rar, but in general this problem even applies to J2EE jars.

Is there any reason why the extra resource adapter configuration
properties are not properly defined?


only required properties are required in the xml.

that's not my understanding of the j2ca spec. Do you know of a javaee app server that only uses the ra.xml and not a vendor plan?

My guess is that many users don't need that extra configuration or
are not using standard J2EE configuration (ie. just using spring etc).


Um. yes.. but still fail to see why it's a bug.  the connector spec
states that you only need to configured required properties via the
RA.xml.. and we have done that.

Again, that's not what I think it says. I think the ra.xml is supposed to be the description of what you can possibly configure in the resource adapter, with descriptions and optional default values. It's the only documentation you should need to produce a fully configured plan for a resource adapter instance.

The unusual feature of most ra.xmls in comparison to say a web.xml is that you really need specific info about the instance and can't go by what a generic ra.xml says, e.g. where is the database you're trying to talk to? with web apps and ejb apps its usually possible to guess reasonable defaults.

thanks
david jencks

--jason


On Apr 12, 2007, at 4:14 PM, Hiram Chirino wrote:

> Hi Jason,
>
> Just because the attribute is not in the xml file does not mean that > it's not supported. The ra.xml is SUPPOSED to be customized for each
> deployment.  We just provide a default one to make it easier for
> folks.
>
> On 4/10/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
>> FYI, I've created an issue for G which lists the missing values (and
>> some which are on the class, but no in the docs):
>>
>>   * https://issues.apache.org/jira/browse/GERONIMO-3089
>>
>> And I created an issue for AMQ to the same affect here:
>>
>>   * http://issues.apache.org/activemq/browse/AMQ-1225
>>
>> --jason
>>
>>
>> On Apr 10, 2007, at 2:33 PM, Jason Dillon wrote:
>>
>> > I was just looking at:
>> >
>> >     http://activemq.apache.org/resource-adapter-properties.html
>> >
>> > Which shows a bunch of configuration values for the resource-
>> > adapter... but then I looked at the META-INF/ra.xml and I only see
>> > config-property elements for:
>> >
>> >  * ServerUrl
>> >  * UserNAme
>> >  * Password
>> >  * Clientid
>> >  * UseInboundSession
>> >  * BrokerXmlConfig
>> >
>> > These, which are on the above page, are not actually configurable
>> > via the RA:
>> >
>> >  * AllPrefetchValues
>> >  * DurableTopicPrefetch
>> >  * QueuePrefetch
>> >  * InputStreamPrefetch
>> >  * TopicPrefetch
>> >  * InitialRedeliveryDelay
>> >  * MaximumRedeliveries
>> >  * RedeliveryBackOffMultiplier
>> >  * RedeliveryUseExponentialBackOff
>> >
>> > How are these settings supposed to be configured in a RA if there
>> > is no config-property for them?
>> >
>> > Did someone forget to update the ra.xml when these were added... or
>> > am I missing some important bit about how to configure resource-
>> > adapters?
>> >
>> > --jason
>>
>>
>
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com




--
Regards,
Hiram

Blog: http://hiramchirino.com

Reply via email to