Why would you be against adding a mapping? Especially since you are running an unsupported app server, I think you should try to get it running with a mapping so you have a known working set up first, and then if you actually have the time to invest, you can seek out a different solution. Also, is this the ber from cvs or the released 1.1 version?



On Feb 15, 2007, at 9:52 AM, Steve Brownlee wrote:

Dave:

Yes I'm going to give that a shot, but I'm also going to figure out if I
can get it working without a mapping.  I just have to! 

- Steve

-----Original Message-----
[mailto:[email protected]] On Behalf Of Dave Ross
Sent: Thursday, February 15, 2007 9:11 AM
Subject: [coldspring-dev] Step 1 failure

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



Reply via email to