OPENEJB-1298 Update the jaxb tree to model the ee 6 schemas
Hi David J. and all, I did some changes to the Jaxb tree regarding JPA 2.0 support. Yet, i fulfill PersistenceXmlTest test case in order to marshall/unmarshall JPA 2.0 persistence.xml files. We also have a tree for orm.xml files. As far as I know, it's only used for CMP beans (internally). IMHO, with JPA, the persistence provider is responsible for parsing orm files. We don't care about that. Am i wrong? If not, the question is: do we actually need to update orm subtree? Thanks, Jean-Louis -- View this message in context: http://openejb.979440.n4.nabble.com/OPENEJB-1298-Update-the-jaxb-tree-to-model-the-ee-6-schemas-tp2718648p2718648.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Jetty Integration
Hi Jean-Louis, I've been doing some work on integration with Jetty 7. I currently have Jetty and OpenEJB working together in a unit test in the openejb-jetty-common module, and this is running one of example war files. I've got a fair bit of stuff working - I think most of the JNDI wiring is there, and I've done a security service. It still needs to be put into standalone Jetty container, and needs a way of installing itself, like the Tomcat integration. There's also a few things that won't work yet, like webservice support. I've been a bit stalled on this due to work and other commitments but should hopefully get back into the swing of it this weekend and next week. I'll start putting some issues in Jira for this work so we can keep track of how we're getting on. Jon On Wed, Sep 29, 2010 at 10:02 AM, Jean-Louis MONTEIRO jean-louis.monte...@atosorigin.com wrote: Hello guys, Using Jetty is quite convenient to use and faster than Tomcat. Moreover, it's simpler to use with maven. I actually would like to know what is the status of our Jetty integration compared with Tomcat integration. What is supposed to work ... ? Thanks a lot. Jean-Louis -- View this message in context: http://openejb.979440.n4.nabble.com/Jetty-Integration-tp1457408p2718570.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
trimming whitespace in xml with jaxb
I think that most javaee schema string element content is supposed to have whitespace trimmed off before trying to interpret it, and I think that jaxb doesn't do that by default unless you specify a suitable XmlJavaTypeAdapter. A few fields in our jee tree use the CollapsedStringAdapter but IIUC that also does something to whitespace inside the string. So I'm wondering if there's any reason I shouldn't write a TrimStringAdapter that just trims strings and use it with all the fields that are supposed to be trimmed but not collapsed? An example of a field that should not be trimmed is an env-entry value. whitespace is a legal value here. thanks david jencks
Re: OPENEJB-1257
On Mon, Sep 27, 2010 at 6:49 PM, David Blevins david.blev...@visi.com wrote: On Sep 27, 2010, at 5:21 PM, Matthias Wessendorf wrote: Hey David, On Sun, Sep 26, 2010 at 8:33 PM, David Blevins david.blev...@visi.com wrote: On Sep 25, 2010, at 7:03 PM, Matthias Wessendorf wrote: Hi guys, I wondering about the state of OPENEJB-1257 Is it still needed? If yes, will it be committed ? :) Hi Matthias! Missed you at JavaOne. Didn't realize you were heading over till too late. Let me know if you're coming to ApacheCon NA. Nope. No more travel to the US this year :-) We had that patch in for a bit then decided to go with a much deeper integration. Now we have OWB working right in the openejb-core code. The integration is still in flux but generally working. I haven't tried any JSF/CDI stuff, but you're more than welcome to dig in. The more the merrier. Check out openejb3/assembly/openejb-tomcat/openejb-tomcat-bundle/. That's basically a Web Profile stack. There's a TCK setup for it as well. Let me chekc the that one, when back in Germany. Regarding the TCK. Is there some plan to apply for Web Profile certification, within OpenEJB ? Check out the Tomcat integration. It's pretty much been web profile for years now. yeah I know - I really collapsed EAR approach :-) Would be nice to get an official nod if we can. Indeed, that would be sweat! -Matthias -David -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: trimming whitespace in xml with jaxb
Agree to have a trim adapter, actually, most fields should be trimmed. While looking at the web deployment codes in Geronimo, too many trim() methods are invoked on those web elements, e.g. servlet-class. http-method ... 2010/9/30 David Jencks david_jen...@yahoo.com I think that most javaee schema string element content is supposed to have whitespace trimmed off before trying to interpret it, and I think that jaxb doesn't do that by default unless you specify a suitable XmlJavaTypeAdapter. A few fields in our jee tree use the CollapsedStringAdapter but IIUC that also does something to whitespace inside the string. So I'm wondering if there's any reason I shouldn't write a TrimStringAdapter that just trims strings and use it with all the fields that are supposed to be trimmed but not collapsed? An example of a field that should not be trimmed is an env-entry value. whitespace is a legal value here. thanks david jencks -- Ivan
