On Nov 28, 2010, at 4:50 AM, Jan-Kees van Andel wrote: > Hey, > > Dunno how this OWB config creeped in. I guess I copy pasted the wrong > openwebbeans.properties into the project. It's empty now. > > CODI is also in now and I'm starting to use it, but since I have been a bit > CODI-ignorant lately, I guess I'm not using it to it's full extent. > > About Bean Validation, we could also use ExtVal in combination with BV to > support more advanced use cases, but I'm not going to add it until I need it. > When committed, anyone can add this stuff... > > About BVAL, I didn't use it because it's still incubating and I'm not looking > forward to debugging all kinds of crazy integration issues. I want to keep > focus on delivering an app and maybe afterwards migrate it to BVAL. What's > the current state of the library?
BVal works great in geronimo 3 and has been passing standalone tck for months and generally the in-geronimo tck issues have not been with bval but problems with other integrations such as OWB. For maximum portability (?) at least "officially" you might target the app to a javaee 6 web profile container which would include servlets, jsf, web beans, bean validation and ejb 3 lite already. Or you might try packaging it in two ways, one as a web profile app and one as a servlet app with all the extra support included in the war. david jencks > > BTW, it's not a *real* real-world app (it's not running in production for a > client). I'm not allowed to do that. But it's more an example of how it could > look like. > > Are you all okay with my idea to commit it into a sandbox? > > Regards, > Jan-Kees > > 2010/11/27 Mark Struberg <strub...@yahoo.de> > big +1 for the real world app > > > useOwbSpecificXmlConfig=true > > This will be _completely_ removed from OWB in the very near future! This has > been the 'old' XML config from the original webbeans spec. > > I'd also suggest to use Apache bval instead of hibernate validator as JSR-303 > impl. This is also the default impl OpenJPA uses by in it's tests. > > > LieGrue, > strub > > --- On Sat, 11/27/10, Gerhard <gerhard.petra...@gmail.com> wrote: > > From: Gerhard <gerhard.petra...@gmail.com> > Subject: Re: Real world MyFaces 2.0 webapp > To: "MyFaces Development" <dev@myfaces.apache.org> > Date: Saturday, November 27, 2010, 6:01 PM > > hi, > the "codi issue" you saw happens due to an owb config bug (see > org.apache.webbeans.useOwbSpecificXmlConfig=true) > imo we should just use portable features. > > > regards,gerhard > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces > > > > > > 2010/11/27 Gerhard <gerhard.petra...@gmail.com> > > > hi, > we could also use it for extval, codi,... tests. > regards,gerhard > > http://www.irian.at > > > Your JSF powerhouse - > > > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces > > > > > 2010/11/27 Jan-Kees van Andel <jankeesvanan...@gmail.com> > > > > Hey folks, > Somewhere in the past I started working on a real world example webapp. I > guess it's already a year ago. :-) But now I have some free time to work on > this again. > > > > Currently I use MyFaces 2.0 (of course), OpenWebBeans and OpenJPA 2.0. I also > use Hibernate Validator. I got a strange error with CODI, so I skipped it for > now to stay up-to-speed, but I guess we should get that one in. > > > > > My goal with this example app was to bridge the gap between the current set > of example apps and the real world issues that application developers > struggle with.It could also be a nice example of a joint effort between > multiple Apache projects, which would be good for the professional image of > Apache. > > > > > So, this example app has a pretty big domain model, security, layered > architecture, etc. Also stuff like logging, caching and performance is being > taken care of, so people can compare their app with this one. And this app > can serve as a living documentation in which the answers to Frequently Asked > Questions can be found. > > > > > 2 things:1 Since everybody has a different idea of what a "good" app looks > like, I expect a lot of discussions on the mailing list. But I think this is > a good thing, because those discussions are also valuable for developers. > Based on those discussions, they can choose the proper solution for their > context. Those discussions can for example be referenced from the source code. > > > > 2 Where to put the code? My idea for now was to create a top level "sandbox" > directory within MyFaces because this clearly indicates that it's a work in > progress and outsiders shouldn't look at it yet. But then at least it's in > Apache version control. I can also put it into GoogleCode or GitHub, but I > prefer Apache, because I think more people will find it there. > > > > > Status:I currently have a working app with some pages. I want to write some > additional pages before I commit it. Of course every line of code may be > subject to discussion, but I prefer concrete discussions based on working > code. That's why I'd prefer a bigger initial commit, incl. a Wiki page with > architectural decisions etc. > > > > > Wdyt? > Regards,Jan-Kees > > > > > > > > > >
