Ditto, but it does generated that error here. What is your set up?
I imported it as a pure Maven project, did an update and got the error.
I'm very curious as to how our setups are so different as to make this difference?


On Wed, Apr 9, 2014 at 9:46 AM, vinodkiran [via Drools] <[hidden email]> wrote:
Very strange...I have the code running on my local machine and it works fine.

-Thanks,
Vinod




_______________________________________________
rules-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/rules-users



If you reply to this email, your message will be added to the discussion below:
http://drools.46999.n3.nabble.com/No-setter-found-for-property-kBaseName-in-class-org-kie-spring-factorybeans-KBaseFactoryBean-tp4029143p4029181.html
To unsubscribe from No setter found for property 'kBaseName' in class 'org.kie.spring.factorybeans.KBaseFactoryBean', click here.
NAML



--
#########################################################
Matthew R. Versaggi, President & CEO
Versaggi Information Systems, Inc.
Adjunct Professor of eBusiness DePaul University
Email: mailto:[hidden email], [hidden email]
M: 630-292-8422 
LinkedIn:  http://www.linkedin.com/in/versaggi
About Me: http://www.matt-versaggi.com/resume/
#########################################################


View this message in context: Re: [rules-users] No setter found for property 'kBaseName' in class 'org.kie.spring.factorybeans.KBaseFactoryBean'
Sent from the Drools: User forum mailing list archive at Nabble.com.