exactly the same :)

the issue with multi line properties was it was uncommon for a lot of case
(in fact only our properties attribute uses it). So we just asked them to
add a special handling (@multiline) for decorated properties.

This way next version uses 1.1.1.Final without configuration change.

*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*



2013/8/13 dinabandhu <[email protected]>

> Hi,
>
> Thank you :).
>
> I was using 1.1.1.Final. Downgrading to 1.0.3.Final solved it and I an see
> the service being configured successfully.
>
> What is the correct way to configure these properties for later versions
> via
> arquilian.xml? I tried setting each property separately like -
>
>             <property name="db1">new://Resource?type=DataSource</property>
>             <property name="db1.JdbcUrl">jdbc:hsqldb:mem:db1</property>
>
> But this does not work and I get a configuration warning -
>
> WARNING - Configuration contain properties not supported by the backing
> object org.apache.openejb.arquillian.openejb.OpenEJBConfiguration
> Unused property entries: {db1=new://Resource?type=DataSource,
> db1.JdbcUrl=jdbc:hsqldb:mem:db1}
> Supported property names: [properties]
>
> Thanks again for your help.
>
> Regards,
> Dinabandhu
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/Problem-configuring-properties-in-arquillian-xml-tp4664614p4664621.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>

Reply via email to