Leo,Agree on the Hibernate part, although it's kindof the de-facto standard for database access I guess. And most people don't use Tacos just-for-fun but will need to implement it in larger environments so this might be a good idea. On the other hand, if you strip the annotations it's just a POJO, so it's kindof irrelevant.
The problem is that I cannot get it work (obiously ;)), debugging output is very minimal at best and when things blow I'm having a very hard time finding things out. This is not really to bad if you have a simple example or very elaborate documentation, but I'm getting the feeling that I'm thrown in the deep end and my swimming skills are somewhat limited. As the standard example uses fileaccess, I can use that a bit but it's not simple enough for me I guess.
So I guess what's lacking is nothing, it's too complete. I can see two main usages for trees, that is filesystems which are are allready in the demo, and data from databases, for which there is no plug-and-play example. I guess a simpler example which addresses the last part would surely help the acceptance/usage of Tacos (atleast overhere).
Kind regards, Dennis Fleurbaaij E: [EMAIL PROTECTED] T: (0031) (0) 6 54 21 53 65 Leonardo Quijano Vincenzi wrote:
Ok, I think we'd need you to dump the Hibernate part since everything you can do with Hibernate can be done with simple Pojos and wired lists, right?What's exactly the difference between this example and the standard example? I mean, what do you see is lacking in the standard examples?
smime.p7s
Description: S/MIME Cryptographic Signature
