Parsing of *-ds.xml does not handle ws in *-property element

SourceForge Submitter: starksm .
The handling of connection-property and
xa-datasource-property by the JCA deployer layer does
not deal with whitespace. For example, the following
oraccle-ds.xml descriptor:

<datasources>
<xa-datasource>
<xa-datasource>
<jndi-name>Pool2</jndi-name>
<track-connection-by-tx>
true
</track-connection-by-tx>
<isSameRM-override-value>
false
</isSameRM-override-value>
<xa-datasource-class>
oracle.jdbc.xa.client.OracleXADataSource
</xa-datasource-class>
<xa-datasource-property name="URL">
jdbc:oracle:thin:@localhost:1521:test
</xa-datasource-property>
<xa-datasource-property name="User">
yyyyy
</xa-datasource-property>
<xa-datasource-property name="Password">
yyyyy
</xa-datasource-property>
<exception-sorter-class-name>

org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter
</exception-sorter-class-name>
</xa-datasource>
</datasources>

Results in the following Properties stream which is not
parsed correctly due to the new lines which are seperators:

2003-08-05 21:14:07,935 DEBUG
[org.jboss.resource.connectionmanager.RARDeploymen
t] setting property: XADataSourceProperties to value URL=
jdbc:oracle:thin:@localhost:1521:test

User=
xxxxxx

Password=
xxxxxx

URL=
jdbc:oracle:thin:@localhost:1521:test

User=
xxxxxx

Password=
xxxxxx

This ends up producing this non-sensical error when the
properties are applied to the XADataSource using
JavaBean style reflection:

Could not find accessor on XADataSource: ; - nested
throwable: (java.lang.NoSuchMethodException:
oracle.jdbc.xa.client.OracleXADataSource.setxxxxxx(java.lang.String));