I'd agree, but I never really liked xml files for configuration (I blame ant for that for the most part). It took me a long time to warm up to them for providing remote services too. And I still think things like SOAP and XML-RPC don't really have a place in the world. They're not really good for web services because they're not simple and not accessible from any client (like web browsers and some others) and are far too inefficient for linking together systems that are inherently tightly coupled to one another.
Rich On Fri, Aug 1, 2008 at 6:26 PM, Rickard Öberg <[EMAIL PROTECTED]>wrote: > Richard Wallace wrote: > > I guess the main thing that really annoys me is having to configure the > > actions in the struts.xml. That's the biggest burden. If it was just a > > matter of using a method to do something like > > > > addActionComposite(module, ListItems.class) > > or > > addActionObject(module, ListItems.class) > > > > and that inspected the ListItems class and checked for annotations and > > such and configured struts then that would be enough to make me happy. > > That's the biggest benefit I get from the autodetection is not having to > > write and maintain a separate xml file. > > Isn't it ironic that we use XML files to make it easier for us, and then > it gets so hard that we have to add new complexities to get around the > problems of the first solution. > > If there were no solutions there would be no problems :-) > > /Rickard > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev >
_______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
