Re: Resource Adapter specific Configurable properties

Thanks for the response, Atul.
Considering that I am only an implementor of a Resource Adapter
how do I make sure that the AppServer does not deploy the RA in
such cases. As I am throwing ResourceAdapterInternalException
how do I convey to the AppServer my intention of not deploying the RA
in such cases. Is there any other exception to be thrown?

I think this area is a bit of a grey area in the JCA spec. As I am not
getting
a perfect solution to my query in it.

Thanks,
Gurdev

Atul Apte wrote:

>In my opinion it will depend on the overall integration environment which is
>managing the adapter and what that integration environment expects the
>adapter to do in case of invalid property values. It also depends on if the
>value is actually wrong or its just that the value cannot be verified at
>deployment time.. For example if the property is an MQSeries message queue
>name and the message queue is not yet created in the MQSeries environment
>then I would expect the resource adapter to be deployed even if the queue is
>not available.. At runtime you will get connection errors if someone uses
>the resource adapter before the queue is created or available.. If on the
>other hand the property is an MQSeries queue name and you provide a database
>URL then you shouldnot deloy the adapter... All this depends on the
>deployment policies you have for integration in general and adapter in
>particular.. If you company doesnot have any deployment policies then you
>may need to define an adapter deployment policy before implementing a
>solution.
>
>Atul
>
>----- Original Message -----
>From: "Gurdev Parmar" <[email protected]>
>To: <[email protected]>
>Sent: Monday, December 09, 2002 1:09 AM
>Subject: Re: Resource Adapter specific Configurable properties
>
>
>
>
>>Hi there,
>>Any one who can throw some light on this query :)
>>
>>Thanks,
>>Gurdev
>>
>>Gurdev Parmar wrote:
>>
>>
>>
>>>Hi,
>>>I am not clear about the behavior of the AppServer and
>>>Resource Adapter when an undefined property is set
>>>in the deployment descriptor as a part of configurable properties
>>>of a resource adapter.  This is for a valid property name but
>>>an invalid property value. Which is a correct behavior:
>>>
>>>1. Resource adapter throws a ResourceAdapterInternalException
>>>and the App Server doesn't deploy the resource adapter.
>>>2. Resource adapter throws a ResourceAdapterInternalException
>>>and the App Server ignores this property and moves ahead and finally
>>>deploys the RA.
>>>3. Resource Adapter sets the property as undefined and lets the
>>>app server go ahead with other properties and finally when a client
>>>tries to access the RA, the RA throws an exception saying that
>>>the property was set wrong.
>>>
>>>Thanks,
>>>Gurdev
>>>
>>>
>>>
>>
>>
>===========================================================================
>
>
>>To unsubscribe, send email to [email protected] and include in the
>>
>>
>body
>
>
>>of the message "signoff CONNECTOR-INTEREST".  For general help, send email
>>
>>
>to
>
>
>>[email protected] and include in the body of the message "help".
>>
>>
>>
>
>===========================================================================
>To unsubscribe, send email to [email protected] and include in the body
>of the message "signoff CONNECTOR-INTEREST".  For general help, send email to
>[email protected] and include in the body of the message "help".
>
>
>
>

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff CONNECTOR-INTEREST".  For general help, send email to
[email protected] and include in the body of the message "help".