-
1. Re: RC1: Resource Adaptor configuration of non-String types
davidjencks May 10, 2002 12:59 PM (in response to mprudhom)I'll take a look.
-
2. Re: RC1: Resource Adaptor configuration of non-String types
dezzio Jul 18, 2002 11:51 AM (in response to mprudhom)Any news on this?
-
3. Re: RC1: Resource Adaptor configuration of non-String types
davidjencks Jul 20, 2002 9:47 PM (in response to mprudhom)Hmm, this was working for me for a while but I don't seem to have a test case. If this is still broken please file a bug including your version info.
-
4. Re: RC1: Resource Adaptor configuration of non-String types
davidjencks Jul 21, 2002 12:21 AM (in response to mprudhom)I've just added some test code to 3.1 with Integer, Boolean, Double, and URL properties, all of which appear to work fine. If you are having trouble please be very specific.
-
5. Re: RC1: Resource Adaptor configuration of non-String types
neil Jul 22, 2002 8:30 AM (in response to mprudhom)I get the same problem as the others in 3.0.0. What files do you need to see to prove this is happening? I can give you my full RA code if necessary.
- Neil -
6. Re: RC1: Resource Adaptor configuration of non-String types
davidjencks Jul 23, 2002 12:19 AM (in response to mprudhom)Could you see if your adapter deploys ok in jboss 3.1? If not please compare with the test adapter in org.jboss.test.jca.adapter, which is what the test case is based on.
WARNING: I just changed some configuration in 3.1, the JndiName attribute now goes with the ConnectionManager mbean, not the RARDeployment (usually labeled service=LocalTxDS or some such)
It is possible that the code that makes the property editors available only got into jboss 3.0.1, so you might try that or either cvs version also.