Steve,

Try a mapping. Sounds like default component paths are screwy on JBoss.

thanks,

Dave

On 2/15/07, Steve Brownlee <[EMAIL PROTECTED]> wrote:
Dang, that didn't work either.  Still getting the same error.  The only
thing I can think of now is the fact that I'm running this on Jboss
rather than JRun (or some other supported application server).  One more
thing to note, I didn't set up ColdSpring directory as a mapping, it's
installed in the webroot.

An odd thing I did notice is that if I call the getParent() method on
the DefaultXmlBeanFactory instance, it does return the correct type
without errors: component coldspring.beans.AbstractBeanFactory

Not sure why that would succeed but any instance created via
createObject() would not return the "correct" type.  I've tried it with
other components as well with the same error.

I'll investigate by digging down into the guts again and see if I can
provide some feedback on this.


Steve Brownlee
http://www.fusioncube.net/


-----Original Message-----
From: [email protected]
[mailto:[EMAIL PROTECTED] On Behalf Of Steve
Brownlee
Sent: Thursday, February 15, 2007 7:49 AM
To: [email protected]
Subject: [coldspring-dev] Step 1 failure

Sean:

Still running 7.0.0.  I'll install 7.0.2 and try again.

-----Original Message-----
From: [email protected]
[mailto:[EMAIL PROTECTED] On Behalf Of Sean
Corfield
Sent: Tuesday, February 13, 2007 11:31 PM
To: [email protected]
Subject: [coldspring-dev] Step 1 failure

On 2/13/07, Steve Brownlee <[EMAIL PROTECTED]> wrote:
> The value returned from function init() is not of type
> coldspring.beans.DefaultXmlBeanFactory.
>
> I don't understand why the init() function's return type is the entire

> package for the component anyway...
>
>         <cffunction name="init" access="public"
> returntype="coldspring.beans.DefaultXmlBeanFactory"
> output="false"
>
> As soon as I take out the package designation and just return the
> component name, everything works fine as I expected it would.

Exactly what version of ColdFusion are you running? What hot fixes etc?

There was a version or hot fix put out somewhere in the 7.0.x frame that
broken return types under mappings. Updating to the latest 7.0.x will
fix it.
--
Sean A Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/

"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood





Reply via email to