> in the deployables directory and parsing the > *-service.xml files for > information. If those files contain the
I agree with Hiram, DO NOT put stuff that is not going to be "deployed" it is confusing as hell. Use the EXISTING ONES. > > But what would be a good intuative directory name > to put deployable > > services that are not actually deployed??? I got a > feeling this could > > also cause some confusion. clearly avoid this. > >>> I expect 70% of the users who download this > release to uppack it, > >>> startup with the defaults, copy there .ear or > .war and then load a > >>> webpage in there broweser for confirmation that > it all worked. Jason, PRECISELY, stop talking here is your solution. I would even say that 90% will do just that "does it work?" so that is what you want to do. Do not design for the 10% rest, if they are serious they will figure it out in 10 minutes. But the 90% lazy mass, is our real audience, design for them. marcf _________________________________________________________ View thread online: http://main.jboss.org/thread.jsp?forum=66&thread=12608 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
