The tooling generates one resource (persisted) by default because that allows all new users to test their resource immediately with little hassle. What you probably want to do is:
1. remove the <persistence/> element under <router/> in muse.xml 2. remove any 'use-router-persistence' attributes on <resource-type/> in muse.xml 3. remove the /WEB-INF/services/muse/router-entries directory. There you go - no persistence of any kind. Although, I think you are going to want persistence for *one* resource type - some kind of factory resource that is going to create the resources dynamically as described in your third paragraph? Dan "Vinh Nguyen \(vinguye2\)" <[EMAIL PROTECTED]> wrote on 11/02/2006 03:55:36 PM: > Hi all, > According to the docs, the default resource persistence feature in Muse > is file-based. Also, persistence is turned off by default, which I > assume means no file-based either. I think this is the reason why I > don't see much content in the router-entries.xml files when testing the > samples. > > The question I have is: > If persistence is defaulted to off, and we leave it this way, what would > the effects be? Would Muse's "discovery" ability still work properly? > Or, do we have to choose a persistence option to work with (i.e. > file-based, or implement our own code to programatically manage > persistence)? > > Basically, we would like our project to be as "stateless" as possible. > Since our resources can be very dynamic, we'd prefer not having it > file-based. We also would like to avoid having this Muse layer store > resource data, like in a database. We want this Muse layer be a > pass-thru layer as much as possible, with little or no configuration > needed once it is deployed. How far can we get with this? > -Vinh > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
