I'm pretty sure that's by design. XML "cdata" includes whitespace. If an application chooses to ignore whitespace, I beleive DOM spec complient parsers can auto-ignore whitespace.
It makes though that JBoss would accept whitespace in an "env-entry-value" for java.lang.String, since whitespace characters are valid for strings. (In your case the whitespace is a nuisance, but it may be needed in other cases.) Mike ----- Original Message ----- From: "Christopher D. Audley" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 11, 2002 3:37 PM Subject: [JBoss-user] env-entry and XML > XML tells me that the following should be equivalent > > <env-entry> > <env-entry-name>password</env-entry-name> > <env-entry-type>java.lang.String</env-entry-type> > <env-entry-value>password</env-entry-value> > </env-entry> > > <env-entry> > <env-entry-name>credentials</env-entry-name> > <env-entry-type>java.lang.String</env-entry-type> > <env-entry-value> > password > </env-entry-value> > </env-entry> > > However, if I place the latter in my ejb-jar.xml, JBoss gives me the > password > with whitespace and carriage returns around it. > > I would be inclined to say this is a bug in JBoss, thoughts? > > Cheers > Chris > > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
