Hi Jim

Thanks for everything! I'll let you know how things develop. Hopefully later this 
evening. (Central European Time :)

/johan


----- Original Message ----- 
From: "jim moore" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 11, 2002 4:20 PM
Subject: Re: [Mav-user] opt-betwixt


> Hi Johan,
> 
> It seems that it is possible to use .betwixt files to customize the xml
> gerated by betwixt. Not sure how much customization is possible, but you may
> look here for more info:
> 
> http://jakarta.apache.org/commons/betwixt/overview.html
> 
> Scroll down to the section "Customizing the mapping of a bean to XML"
> 
> --jim
> 
> 
> ----- Original Message -----
> From: "Johan Lundberg" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, September 11, 2002 10:49 AM
> Subject: Re: [Mav-user] opt-betwixt
> 
> 
> > Yes, it was a configuration error. Before switching to Betwixt I
> > upgraded to the latest Maverick dist. I previously had Maverick 2.0
> > release candidate 1 and didn't adjust the web.xml nor maverick.xml
> > appropriately after the upgrade. Ooops.
> >
> > Betwixt renders Date objects differently than Domify. Domify shows the
> > details of the Date object but Beswixt only writes out the date like one
> > String in a very long format. I need the hour and minute details but
> > this is probably very easy to work around.
> >
> >
> > /johan
> >
> >
> >
> > jim moore wrote:
> >
> > > Yes. maxTransforms worked perfectly for me in friendbook-betwixt.
> > >
> > > --jim
> > >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED]] On Behalf Of Schnitzer,
> > > Jeff
> > > Sent: Tuesday, September 10, 2002 7:24 PM
> > > To: '[EMAIL PROTECTED]'
> > > Subject: RE: [Mav-user] opt-betwixt
> > >
> > >
> > > All good points.  Sure, let everything coexist.
> > >
> > > maxTransforms should work no matter what view/transformation technology
> > > you use.  Are you defining the servlet init-param properly in your
> > > web.xml?
> > >
> > > <!--
> > > This allows an extra query parameter to be added
> > > to any request which halts the transformation
> > > process
> > > after that number of steps, e.g.
> > > blah.m?maxTransforms=0
> > > -->
> > > <init-param>
> > > <param-name>limitTransformsParam</param-name>
> > > <param-value>maxTransforms</param-value>
> > > </init-param>
> > >
> > > Jeff Schnitzer
> > > [EMAIL PROTECTED]
> > >
> > >
> > >>-----Original Message-----
> > >>From: Johan Lundberg [mailto:[EMAIL PROTECTED]]
> > >>Sent: Tuesday, September 10, 2002 6:05 PM
> > >>To: [EMAIL PROTECTED]
> > >>Subject: Re: [Mav-user] opt-betwixt
> > >>
> > >>I have to agree with Jim on this. Having done the first tests with
> > >>opt-betwixt it seems that the Bean -> XML doesn't render identical
> > >>XML. Most parts of my app looks fine but the opt-domify compatible XSL
> > >>
> > >
> > >>templates have in some nodes trouble with the Betwixt XML. I don't
> > >>think that it is difficult to adjust the XSL templates but imposing a
> > >>XSL template rewrite on other developers might not be a good thing.
> > >>Most people seem happy with opt-domify... at the moment.
> > >>
> > >>The problem for me right now it to make the 'maxTransforms' to work
> > >>for me now that Betwixt has taken over. Any hints would be welcome ;)
> > >>
> > >>I have not come to the point where I can test the cyclic reference
> > >>graphs, but I'll get back on that when I have tested this.
> > >>
> > >>/johan
> > >>
> > >>
> > >>
> > >>jim moore wrote:
> > >>
> > >>
> > >>>I would vote for letting them co-exist for a while. At least until
> > >>>
> > >>betwixt
> > >>
> > >>>is officially released. (I'm kind of nervous about deprecating
> > >>>
> > >>production
> > >>
> > >>>code and replacing it with pre-release code).
> > >>>
> > >>>Once jakarta officially releases betwixt, then we can re-examine how
> > >>>
> > >
> > >>>(or
> > >>>
> > >>if)
> > >>
> > >>>to deprecate opt-domify.
> > >>>
> > >>>As for all of the optional packages, I agree that it seems to be
> > >>>getting
> > >>>
> > >>a
> > >>
> > >>>bit unwieldy (and I'm probably heavily responsible). Maybe we should
> > >>>
> > >
> > >>>do something like nant (http://nant.sourceforge.net) does and have a
> > >>>
> > >>separate
> > >>
> > >>>project on sourceforge--mavcontrib or opt-mav or something--for all
> > >>>of
> > >>>
> > >>the
> > >>
> > >>>optional files. Then people new to maverick wouldn't be overwhelmed
> > >>>by
> > >>>
> > >>all
> > >>
> > >>>the optional stuff on the files page, but it would all still be
> > >>>pretty readily available should they need it.
> > >>>
> > >>>On the other hand, having the optional packages in the maverick
> > >>>project probably keeps its sourceforge activity statistics higher
> > >>>than they
> > >>>
> > >>would
> > >>
> > >>>be, so from a public relations point of view, maybe its better to
> > >>>keep
> > >>>
> > >>them
> > >>
> > >>>together.
> > >>>
> > >>>--jim
> > >>>
> > >>>----- Original Message -----
> > >>>From: "Schnitzer, Jeff" <[EMAIL PROTECTED]>
> > >>>To: <[EMAIL PROTECTED]>
> > >>>Sent: Tuesday, September 10, 2002 4:31 PM
> > >>>Subject: RE: [Mav-user] opt-betwixt
> > >>>
> > >>>
> > >>>Cool!
> > >>>
> > >>>I didn't realize that betwixt had a SAX (or stream) generator in it.
> > >>>
> > >
> > >>>That is really nice.
> > >>>
> > >>>Any suggestions for a deprecation strategy for Domify?  Thoughts:
> > >>>
> > >>>1. Publish opt-betwixt (or opt-saxify?) and let them coexist. 2. Add
> > >>>
> > >
> > >>>the betwixt adapter to opt-domify and let them coexist in the same
> > >>>package. 3. Replace the domify adapter with the betwixt adapter
> > >>>inside opt-domify.
> > >>>4. ?
> > >>>
> > >>>I'm a little worried that people are getting confused by all the
> > >>>optional packages.  Putting an explanation in the docs would
> > >>>probably help (maybe this weekend).  I'm somewhat partial to putting
> > >>>
> > >
> > >>>all the "stuff for people interested in using XSL as a templating
> > >>>technology" in one package.
> > >>>
> > >>>Jeff Schnitzer
> > >>>[EMAIL PROTECTED]
> > >>>
> > >>>
> > >>>
> > >>>>-----Original Message-----
> > >>>>From: jim moore [mailto:[EMAIL PROTECTED]]
> > >>>>Sent: Tuesday, September 10, 2002 12:32 PM
> > >>>>To: [EMAIL PROTECTED]
> > >>>>Subject: [Mav-user] opt-betwixt
> > >>>>
> > >>>>Okay a little more playing around and I've gotten a betwixt view
> > >>>>
> > >>>>
> > >>>working.
> > >>>
> > >>>
> > >>>>The trouble seemed to be with their SAXBeanWriter. They have another
> > >>>>
> > >
> > >>>>BeanWriter that simply writes to a stream. Using this I got it to
> > >>>>
> > >>>>
> > >>>work. I
> > >>>
> > >>>
> > >>>>assume that it's not going to be as efficient as the SAXBeanWriter,
> > >>>>
> > >>>>
> > >>>but it
> > >>>
> > >>>
> > >>>>works. And it should prove a good place holder until their
> > >>>>
> > >>>>
> > >>>SAXBeanWriter
> > >>>
> > >>>
> > >>>>is
> > >>>>working. Once it is, we should be able to simply update opt-betwixt.
> > >>>>
> > >
> > >>>>I assume that the xml produced will be the same, so no one should
> > >>>>even
> > >>>>
> > >>>>
> > >>>have
> > >>>
> > >>>
> > >>>>to
> > >>>>update their projects.
> > >>>>
> > >>>>You can get it here:
> > >>>>
> > >>>>http://www.scolamoore.com/jim/opt-betwixt-20020910.zip
> > >>>>
> > >>>>It's pretty heavily based on opt-domify, so Jeff and Scott deserve
> > >>>>
> > >>>>
> > >>>much of
> > >>>
> > >>>
> > >>>>the credit.
> > >>>>There is a friendbook-betwixt in there that works if you want an
> > >>>>
> > >>>>
> > >>>example.
> > >>>
> > >>>
> > >>>>--jim
> > >>>>
> > >>>>----- Original Message -----
> > >>>>From: "jim moore" <[EMAIL PROTECTED]>
> > >>>>To: <[EMAIL PROTECTED]>
> > >>>>Sent: Tuesday, September 10, 2002 12:39 PM
> > >>>>Subject: [Mav-user] jxv and betwixt views
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>>So I spent a little while this morning screwing around with making
> > >>>>>
> > >>>>>
> > >>>jxv
> > >>>
> > >>>
> > >>>>and
> > >>>>
> > >>>>
> > >>>>>betwixt views. JXV contains DOMSource and SAXSource objects (not
> > >>>>>the
> > >>>>>
> > >>>>>
> > >>>>exact
> > >>>>
> > >>>>
> > >>>>>names, but close enough) that should be able to passed to
> > >>>>>
> > >>>>>
> > >>>TransformSteps
> > >>>
> > >>>
> > >>>>>though step.go(source). Unfortunately, both break in different
> > >>>>>ways.
> > >>>>>
> > >>>>>Betwixt has a SAXBeanWriter object that is created from a SAX
> > >>>>>ContentHandler, so theoretically we should be able to use it in
> > >>>>>
> > >>>>>
> > >>>maverick
> > >>>
> > >>>
> > >>>>as
> > >>>>
> > >>>>
> > >>>>>so:
> > >>>>>
> > >>>>>TransformStep next = vctx.getNextStep();
> > >>>>>SAXBeanWriter sbw = new SAXBeanWriter(next.getSAXHandler());
> > >>>>>try {
> > >>>>>   sbw.write(vctx.getModel());
> > >>>>>} catch (SAXException ex) {
> > >>>>>   throw new ServletException(ex);
> > >>>>>} catch (IntrospectionException ex) {
> > >>>>>   throw new ServletException(ex);
> > >>>>>}
> > >>>>>next.done();
> > >>>>>
> > >>>>>Unfortunately this too blows up with some pretty cryptic errors.
> > >>>>>
> > >>>>>The problem with both packages does not seem to be with Maverick
> > >>>>>but
> > >>>>>
> > >>>>>
> > >>>>rather
> > >>>>
> > >>>>
> > >>>>>with jxv and betwixt themselves. Neither has release versions
> > >>>>>
> > >>>>>
> > >>>available
> > >>>
> > >>>
> > >>>>(I
> > >>>>
> > >>>>
> > >>>>>had to build both from cvs) and I think for now they are still too
> > >>>>>
> > >>>>>
> > >>>>unstable
> > >>>>
> > >>>>
> > >>>>>to be useful.
> > >>>>>
> > >>>>>On the upside though, once they are stable, it shouldn't take too
> > >>>>>
> > >>>>>
> > >>>long
> > >>>
> > >>>
> > >>>>to
> > >>>>
> > >>>>
> > >>>>>write maverick views for them (it took me about 30 minutes total to
> > >>>>>
> > >>>>>
> > >>>>write
> > >>>>
> > >>>>
> > >>>>>both views, basing them on opt-domify).
> > >>>>>
> > >>>>>--jim
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>-------------------------------------------------------
> > >>>>>This sf.net email is sponsored by: OSDN - Tired of that same old
> > >>>>>cell phone?  Get a new here for FREE!
> > >>>>>https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> > >>>>>_______________________________________________
> > >>>>>Mav-user mailing list
> > >>>>>[EMAIL PROTECTED]
> > >>>>>https://lists.sourceforge.net/lists/listinfo/mav-user
> > >>>>>Archives are available at http://www.mail-archive.com/
> > >>>>>
> > >>>>>
> > >>>>
> > >>>>
> > >>>>-------------------------------------------------------
> > >>>>This sf.net email is sponsored by: OSDN - Tired of that same old
> > >>>>cell phone?  Get a new here for FREE!
> > >>>>https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> > >>>>_______________________________________________
> > >>>>Mav-user mailing list
> > >>>>[EMAIL PROTECTED]
> > >>>>https://lists.sourceforge.net/lists/listinfo/mav-user
> > >>>>Archives are available at http://www.mail-archive.com/
> > >>>>
> > >>>>
> > >>>
> > >>>-------------------------------------------------------
> > >>>This sf.net email is sponsored by: OSDN - Tired of that same old
> > >>>cell phone?  Get a new here for FREE!
> > >>>https://www.inphonic.com/r.asp?r=urceforge1&refcode1=3390
> > >>>_______________________________________________
> > >>>Mav-user mailing list
> > >>>[EMAIL PROTECTED]
> > >>>https://lists.sourceforge.net/lists/listinfo/mav-user
> > >>>Archives are available at http://www.mail-archive.com/
> > >>>
> > >>>
> > >>>
> > >>>-------------------------------------------------------
> > >>>This sf.net email is sponsored by: OSDN - Tired of that same old
> > >>>cell phone?  Get a new here for FREE!
> > >>>https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> > >>>_______________________________________________
> > >>>Mav-user mailing list
> > >>>[EMAIL PROTECTED]
> > >>>https://lists.sourceforge.net/lists/listinfo/mav-user
> > >>>Archives are available at http://www.mail-archive.com/
> > >>>
> > >>>
> > >>>
> > >>>
> > >>
> > >>
> > >>
> > >>-------------------------------------------------------
> > >>In remembrance
> > >>www.osdn.com/911/ _______________________________________________
> > >>Mav-user mailing list
> > >>[EMAIL PROTECTED]
> > >>https://lists.sourceforge.net/lists/listinfo/mav-user
> > >>Archives are available at http://www.mail-archive.com/
> > >>
> > >
> > >
> > > -------------------------------------------------------
> > > In remembrance
> > > www.osdn.com/911/ _______________________________________________
> > > Mav-user mailing list
> > > [EMAIL PROTECTED]
> > > https://lists.sourceforge.net/lists/listinfo/mav-user
> > > Archives are available at http://www.mail-archive.com/
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > In remembrance
> > > www.osdn.com/911/
> > > _______________________________________________
> > > Mav-user mailing list
> > > [EMAIL PROTECTED]
> > > https://lists.sourceforge.net/lists/listinfo/mav-user
> > > Archives are available at http://www.mail-archive.com/
> > >
> > >
> > >
> >
> >
> >
> >
> > -------------------------------------------------------
> > In remembrance
> > www.osdn.com/911/
> > _______________________________________________
> > Mav-user mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/mav-user
> > Archives are available at http://www.mail-archive.com/
> 
> 
> 
> -------------------------------------------------------
> In remembrance
> www.osdn.com/911/
> _______________________________________________
> Mav-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/mav-user
> Archives are available at http://www.mail-archive.com/
> 



-------------------------------------------------------
In remembrance
www.osdn.com/911/
_______________________________________________
Mav-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mav-user
Archives are available at http://www.mail-archive.com/

Reply via email to