[JBoss-dev] [ jboss-Bugs-436550 ] ClassCastException for ENC retrieval(fwd)
Is there any reason why this should not be done for all values as they are loaded from xml into metadata objects? I ran into a similar problem where lookup would fail for something like: res-jndi-name java:/JmsXA /res-jndi-name In this case it would be safe to trim(), but are there cases where it is not? --jason -- Forwarded message -- Date: Tue, 26 Jun 2001 15:51:33 -0700 From: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [JBoss-dev] [ jboss-Bugs-436550 ] ClassCastException for ENC retrieval Bugs item #436550, was opened at 2001-06-26 15:51 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=436550group_id=22866 Category: JBossServer Group: v2.2 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Sebastien Sahuc (ssahuc) Assigned to: Nobody/Anonymous (nobody) Summary: ClassCastException for ENC retrieval Initial Comment: When using the ORIGINAL Weblogic Bean example into JBoss, A ClassCastException is thrown by the bean at the following line : Integer tl = (Integer) ic.lookup (java:/comp/env/tradeLimit); An this, simply because the Envirnment entry is declared in ejb-jar.xml with a SPACE char, as shown below: [...] env-entry env-entry-nametradeLimit/env-entry-name env-entry-typejava.lang.Integer /env-entry-type !-- ^ -- !-- | -- !-- | -- !-- Notice the SPACE Char causing the issue -- env-entry-value500/env-entry-value /env-entry Thus removing the SPACE char resolved the exception. So my guess is that the value should be trim() before being actually resolved into a java class !!! Thanks, Sebastien -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=436550group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [ jboss-Bugs-436550 ] ClassCastException for ENC retrieval (fwd)
White space is significant in xml and we can't blindly strip it out of every element. A jndi-name is a very arbitrary form and I don't agree that its safe to strip the white space. - Original Message - From: Jason Dillon [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, June 27, 2001 6:18 PM Subject: [JBoss-dev] [ jboss-Bugs-436550 ] ClassCastException for ENC retrieval (fwd) Is there any reason why this should not be done for all values as they are loaded from xml into metadata objects? I ran into a similar problem where lookup would fail for something like: res-jndi-name java:/JmsXA /res-jndi-name In this case it would be safe to trim(), but are there cases where it is not? --jason ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [ jboss-Bugs-436550 ] ClassCastException for ENC retrieval (fwd)
Its an unbounded set of names and access protocols so how should I know? - Original Message - From: Jason Dillon [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, June 27, 2001 7:32 PM Subject: Re: [JBoss-dev] [ jboss-Bugs-436550 ] ClassCastException for ENC retrieval (fwd) Is it possible to specify a JNDI name that contains whitespace? --jason On Wed, 27 Jun 2001, Scott M Stark wrote: White space is significant in xml and we can't blindly strip it out of every element. A jndi-name is a very arbitrary form and I don't agree that its safe to strip the white space. ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-436550 ] ClassCastException for ENC retrieval
Bugs item #436550, was opened at 2001-06-26 15:51 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=436550group_id=22866 Category: JBossServer Group: v2.2 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Sebastien Sahuc (ssahuc) Assigned to: Nobody/Anonymous (nobody) Summary: ClassCastException for ENC retrieval Initial Comment: When using the ORIGINAL Weblogic Bean example into JBoss, A ClassCastException is thrown by the bean at the following line : Integer tl = (Integer) ic.lookup (java:/comp/env/tradeLimit); An this, simply because the Envirnment entry is declared in ejb-jar.xml with a SPACE char, as shown below : [...] env-entry env-entry-nametradeLimit/env-entry-name env-entry-typejava.lang.Integer /env-entry-type !-- ^ -- !-- | -- !-- | -- !-- Notice the SPACE Char causing the issue -- env-entry-value500/env-entry-value /env-entry Thus removing the SPACE char resolved the exception. So my guess is that the value should be trim() before being actually resolved into a java class !!! Thanks, Sebastien -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=436550group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
