On Wednesday 13 December 2006 17:26, A. Zeneski wrote: > I see no reason to maintain the jpublish code in OFBiz. Due to the fact > all future components and enhancements to existing components will all > be widget based. > > If the core OFBiz no longer depends on JPublish, then I see no reason to > maintain the old code. > > On the flip side, older versions of OFBiz which are not being updated to > use the current version will continue to include the JPublish component > and should have no effect on these projects. > > All new contributions to OFBiz should follow the widget pattern, as such > I see no point in maintaining the old JPublish handlers. > > I don't like the idea of new contributions following older patterns. > IMO, the code (ajax) should be converted to use JSON request handler > pattern. I assume that since JPublish was used, this was intended to > follow the XML method for responses. > > Maybe we should open up more discussion regarding new patterns. I see a > number of AJAX being implemented in the near future and my biggest fear > is that all of these will be following different patterns. > > We need to set a standard and follow it through the code base.
I believe there are still screens in some OFBiz applications that depend on JPublish. I may be wrong about that but I think there may be some in the content manager still. I would say that eliminating JPublish while any of the apps in the standard distribution need it is a strange move. -- Ean Schuessler, CTO [EMAIL PROTECTED] 214-720-0700 x 315 Brainfood, Inc. http://www.brainfood.com
