March 2011 - seam-dev - Jboss List Archives

by Emmanuel Bernard

Hi Gunnar, I was reading your doc on Seam Validation http://docs.jboss.org/seam/3/validation/latest/reference/en-US/html_singl... I was thinking that we might be able to go one step further with the "Dependency injection for constraint validators". Today you ask people to configure the ConstraintValidatorFactory using some XML snippet. How about Seam transparently configure it. You can do it programmatically at two levels: 1. during the construction of ValidatorFactory ValidatorFactory factory = Validation .byDefaultProvider().configure() .constraintValidatorFactory( new InjectingConstraintValidatorFactory() ) .buildValidatorFactory(); 2. or during the Validator construction validator .usingContext() .constraintValidatorFactory( new InjectingConstraintValidatorFactory() ) .getValidator(); WDYT?

13 years, 8 months

2
1
0 / 0

The push to the finish line

by Shane Bryzak

Hi team, I'd just like to thank everyone for all the hard work that you've done to get Seam 3 to its CR1 release. At this stage the plan is to release CR2 this coming weekend, mainly so that we can get Forge integrated into the bundled release. This doesn't mean I expect everyone to have a CR2 release prepared for their modules, so don't panic ;) What I would like everyone to do though is to spend some time going over their module, checking the examples, making sure the documentation is free from any spelling or grammar errors, and reviewing any outstanding issues you may still have in JIRA. If you think that your module looks complete enough in these areas, it might be time to consider releasing it as a final. After the CR2 release goes out this weekend, I would really like to start wrapping everything up for the final release in the following 2 weeks, with a target date around the weekend of the 19th/20th of March (though please don't announce this date to anyone just yet!). Our QE team will still be busy testing CR1 this week, so if you *do* think your module is ready for a final release, please hold off until Monday next week to give them time to complete their testing and report any last minute issues found. Once your module is ready for final release please let me know and I'll give it a quick review to make sure it all looks ok. Thanks! Shane

13 years, 8 months

2
4
0 / 0

Re: [seam-dev] Seam Mail and Render

by Lincoln Baxter, III

Ah, ok, in the case of Database-loaded templates with Seam Render, that's the reason why I made the *TemplateResolver *class in the first place. The template path in render is actually an extensible lookup scheme. *So:* @include{"db:users/1/order/12/template"}@end{} *Could be interpreted by a TemplateResolver which would perform the DB lookup and provide the template.* You'd need a *DatabaseTemplateResolver *and *DatabaseTemplateResource*. Once that's done, and you define your path scheme, you're all set! The resolver will handle lookups automatically! Caching templates so that you don't hammer the database might be a few extra steps. * First, you register the resolver in the services file:* /META-INF/services/org.jboss.seam.render.spi.TemplateResolver com.example.myapp.DatabaseTemplateResolver *Then it's then as simple as:* @Inject TemplateCompiler compiler; TemplateResource<?> template = compiler.compile("db:nameOfTemplate/id12/param2/"); template.render(); //already integrated with CDI internally :) // or the template lookup can be as simple as a name or id, but I still recommend the use a "prefix:" // "db:passwordRecovery" *Templates of any resource type can reference templates of another type: * TemplateResource<?> template = compiler.compile("db:nameOfTemplate/id12/param2/"); // the template above contains an include statement to a classpath template, which in turn includes another database template. @include{"/org/jboss/seam/mail/basicHtmlTemplate.render"} @end{} ----> @include{"db:templateThatChangesFrequently"} @end{} // This from within your database template, will perform a classpath or filesystem lookup (using the included resolvers.) So you can do cool things like cross-resolver referencing of templates. ~Lincoln On Mon, Mar 7, 2011 at 3:57 PM, Cody Lerum <cody.lerum(a)gmail.com> wrote: > You definitely want the ability to send in the template content via > inputstream however like I do with mail template. > > I for example store my templates in the database. > > -C > > On Mon, Mar 7, 2011 at 1:19 PM, Lincoln Baxter, III > <lincolnbaxter(a)gmail.com> wrote: > > :) > > > > BTW. RenderTemplate would look something like this... since Render has > its > > own TemplateResolver SPI, it wouldn't be very complicated from Seam > Mail's > > end. > > > > I don't think there's a real way that the MailTemplate interface would go > > with Render, unless an additional render TemplateResource implementation > > were provided to wrap it internally here. The only issue is that Render > > attempts to resolve relative paths in templates, so using MailTemplate > > doesn't really make sense here. Really render already implements a good > deal > > of what you are having to do in mail by trying to abstract the template > > input stream from the templating system itself... I believe you'll have a > > similar problem with Freemarker (or even with velocity if folks use any > > @Include("templateName.path") declarations. > > > > Thoughts? > > > > /* > > * JBoss, Home of Professional Open Source > > * Copyright 2011, Red Hat, Inc., and individual contributors > > * by the @authors tag. See the copyright.txt in the distribution for a > > * full listing of individual contributors. > > * > > * Licensed under the Apache License, Version 2.0 (the "License"); > > * you may not use this file except in compliance with the License. > > * You may obtain a copy of the License at > > * http://www.apache.org/licenses/LICENSE-2.0 > > * Unless required by applicable law or agreed to in writing, software > > * distributed under the License is distributed on an "AS IS" BASIS, > > * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or > implied. > > * See the License for the specific language governing permissions and > > * limitations under the License. > > */ > > > > package org.jboss.seam.mail.templating.render; > > > > import java.io.InputStream; > > import java.util.HashMap; > > import java.util.Map; > > > > import org.jboss.seam.mail.templating.MailTemplate; > > import org.jboss.seam.mail.templating.TemplateImpl; > > import org.jboss.seam.render.TemplateCompiler; > > import org.jboss.seam.render.spi.TemplateResolver; > > import org.jboss.seam.render.spi.TemplateResource; > > import org.jboss.seam.render.template.CompiledTemplateResource; > > > > /** > > * @author <a href="mailto:lincolnbaxter@gmail.com">Lincoln Baxter, > III</a> > > */ > > public class RenderTemplate implements TemplateImpl > > { > > private final CompiledTemplateResource template; > > > > public RenderTemplate(TemplateCompiler compiler, final MailTemplate > > template) > > { > > // not sure this integration really makes sense. Render should > > probably be responsible only for delivering a java.lang.String as output. > > TemplateResource<InputStream> resource = new > > TemplateResource<InputStream>() > > { > > @Override > > public String getPath() > > { > > return template.getTemplateName(); > > } > > > > @Override > > public InputStream getInputStream() > > { > > return template.getInputStream(); > > } > > > > @Override > > public long getLastModified() > > { > > return 0; > > } > > > > @Override > > public InputStream getUnderlyingResource() > > { > > return getInputStream(); > > } > > > > @Override > > public TemplateResolver<InputStream> getResolvedBy() > > { > > return new TemplateResolver<InputStream>() > > { > > @Override > > public TemplateResource<InputStream> resolve(String > target) > > { > > // render will throw an error if this is reached > > return null; > > } > > > > @Override > > public TemplateResource<InputStream> > > resolveRelative(TemplateResource<InputStream> origin, String target) > > { > > // render will throw an error if this is reached > > return null; > > } > > }; > > } > > }; > > > > this.template = compiler.compile(resource); > > } > > > > public RenderTemplate(TemplateCompiler compiler, String path) > > { > > template = compiler.compile(path); > > } > > > > public RenderTemplate(TemplateCompiler compiler, TemplateResource<?> > > resource) > > { > > template = compiler.compile(resource); > > } > > > > public RenderTemplate(CompiledTemplateResource template) > > { > > this.template = template; > > } > > > > @Override > > public String merge(Map<String, Object> context) > > { > > Map<Object, Object> map = new HashMap<Object, Object>(); > > map.putAll(context); > > > > String rendered = template.render(map); > > return rendered; > > } > > } > > > > > -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple"

13 years, 8 months

1
0
0 / 0

Out standing pull requests

by Jason Porter

Hello module leads, I'm going through the list of modules looking for outstanding pull requests. Below are the list of requests I have found. If for whatever reason you are not able to get these (probably within this week) please let me know and I will merge in the requests. If I find problems or questions I cannot easily resolve I will let you know. Thank you for all the hard work that has gone into all of the modules thus far! https://github.com/seam/security/pull/12 https://github.com/seam/security/pull/8 https://github.com/seam/persistence/pull/1 (very old [December], is it still applicable?) https://github.com/seam/solder/pull/19 https://github.com/seam/solder/pull/20 https://github.com/seam/solder/pull/18 https://github.com/seam/solder/pull/13 https://github.com/seam/rest/pull/4 https://github.com/seam/config/pull/3 https://github.com/seam/config/pull/2 https://github.com/seam/wicket/pull/3 https://github.com/seam/jms/pull/6 https://github.com/seam/drools/pull/1 (dated back to October) -- Jason Porter http://lightguard-jp.blogspot.com http://twitter.com/lightguardjp Software Engineer Open Source Advocate Author of Seam Catch - Next Generation Java Exception Handling PGP key id: 926CCFF5 PGP key available at: keyserver.net, pgp.mit.edu

13 years, 8 months

1
0
0 / 0

Seam 3.0.0.CR1 testing status

by Ondřej Skutka

Hi! Seam QE has finished testing Seam 3.0.0.CR1 What has been tested: * Unit tests for each module - Remoting no tests! - Rest tests disabled ("fixed" upstream) those that would be enabled doesn't work in jbossas-managed-6, but they work fine in current master - Security no test in impl! (some tests in external) one test disabled due to known issue SEAMSECURITY-33 - Servlet test skipped! tests OK if I enable them in remote - Solder without -Djboss.i18n.generate-proxies=true we still get SOLDER-49 - Wicket no tests! * Ensure that the tagged version of a module is the same as the bundled jar (diffJars) * Verify that all dependencies are bundled in the dist zip * Search for broken links * Functional tests for all examples in CR1 distribution - helloworld example - SEAMREMOTING-28 - idmconsole - SEAMSECURITY-35 (just added this version to "affects version") - wicket-numberguess - cannot be deployed, there was a problem with slf4j - dependency when running in JBossAS, this is already fixed in upstream (Merge branch 'ftest' of https://github.com/jharting/seam-wicket into jharting-ftest ) - validation-helloworld - SEAMVALIDATE-4 (pull request with the fix already sent) - SEAMVALIDATE-5 - seam-tasks - SEAMREST-34 - validation - JBIDE-8499 (at first this was manned to be a feature request for JBTools), already fixed in upstream in Seam/Remoting module * JBossTools 3.2 - Creating of a new project, enabling a CDI facet - Code completion in JSF files, beans.xml - Using tools for creating new Annotation Literal, Bean, Decorator, beans.xml, Interceptor, Interceptor Binding Annotation, Qualifier Annotation, Scope Annotation, Stereotype Annotation from validation I tested only one option: checking unsatisfiable dependencies - Imported all examples from Seam 3 CR1 release, built them and deployed into JBossAS from within Eclipse. All of these things seemed to work properly. * Documentation spot checking Tests requiring a container have been tested against JBoss AS 6.0.0.Final server. Seam-rest, validation-helloworld and seam-tasks have been also tested on GlassFish 3.1 Final What has been found in the CR1? 2 critical issue 15 major issues 2 minor issues 1 trivial issue Note that besides the CR1 issues [1] there are still lots of open Beta1 and Beta2 issues [2],[3] mostly also affecting CR1. Ondra [1] Seam 3.0.0.CR1 issues https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&requestId=1... [1] Seam 3.0.0.Beta2 issues https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&requestId=1... [2] Seam 3.0.0.Beta1 issues https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&requestId=1...

13 years, 8 months

1
0
0 / 0

Code coverage for servlet module

by Martin Gencur

Just FYI, if you plan adding any tests to the Seam Servlet module you can now find a code coverage trend at: http://hudson.qa.jboss.com/hudson/view/Seam%203/job/Seam-3.X-servlet-CI/ For example the code coverage regarding methods is only around 50% -- Martin Gencur Seam QA Associate

13 years, 8 months

1
0
0 / 0

Seam 3 CR1 testing status (my part)

by Martin Gencur

Hi, I finished my part of testing. The following things were checked: ===Seam 3 Examples=== -functional tests for all examples in CR1 distribution -> issues filed: helloworld example - SEAMREMOTING-28 idmconsole - SEAMSECURITY-35 (just added this version to "affects version") wicket-numberguess - cannot be deployed, there was a problem with slf4j dependency when running in JBossAS, this is already fixed in upstream (Merge branch 'ftest' of https://github.com/jharting/seam-wicket into jharting-ftest ) validation-helloworld - SEAMVALIDATE-4 (pull request with the fix already sent) - SEAMVALIDATE-5 seam-tasks - SEAMREST-34 validation - JBIDE-8499 (at first this was manned to be a feature request for JBTools), already fixed in upstream in Seam/Remoting module ===JBossTools 3.2=== I tested both Seam 3 and Seam 2 use cases. Seam 2 - standard release cycle (importing projects generated with seam-gen - both war and ear, creating new projects, running testng tests, querying in hibernate console) - only JBIDE-7958 found (was created earlier) Seam 3 - creating of a new project, enabling a CDI facet - code completion in JSF files, beans.xml - using tools for creating new Annotation Literal, Bean, Decorator, beans.xml, Interceptor, Interceptor Binding Annotation, Qualifier Annotation, Scope Annotation, Stereotype Annotation - from validation I tested only one option: checking unsatisfiable dependencies - I also imported all example from Seam 3 CR1 release, built them and deployed into JBossAS from within Eclipse. All of these things seemed to work properly, I didn't find any problem. -- Martin Gencur Seam QA Associate

13 years, 8 months

2
1
0 / 0

polishing booking 3.0 for bundling

by Dan Allen

The Seam petstore..cough..I mean booking example is back in EE 6 fashion [1], running on CDI 1.0, JSF 2.0 and Seam 3. Thanks to Jose Freitas for resurrecting it from its partially migrated state and giving it a new l&f. [image: booking30.png] There are a couple of things that need to be polished before we bundle it though. 1. Explanations in the sidebar need to be updated 2. The popup to explain how the conversation works is missing (and likely needs to be restated anyway) 3. Consider adding some margin below the main content div so that it doesn't run up against the footer 4. Seam Faces is logging excessive messages (so the fix needs to happen in Seam Faces) https://issues.jboss.org/browse/SEAMFACES-92 - info message about catch integration being enabled should only happen once - warning message when looking up the validator instance should be downgraded to a debug message Give it a try and provide feedback if you notice any other issues or have suggestions. -Dan [1] http://github.com/seam/examples (javaee-booking) -- Dan Allen Principal Software Engineer, Red Hat | Author of Seam in Action Registered Linux User #231597 http://www.google.com/profiles/dan.j.allen#about http://mojavelinux.com http://mojavelinux.com/seaminaction

13 years, 8 months

1
0
0 / 0

Demo app with CR1 + Seam2-Seam3 migration strategy?

by Denis Forveille

Sorry if I missed this information or if it has been answered elsewhere but is there an "integrated" test/demo application coming with CR1 like the booking app in Seam 2? If so, I could start running it on WebSphere 8 beta (and at the same time educate myself on CDI, Weld and Seam 3..) If not, what are the plans for such a demo application? Also have someone already think about the strategy around the seam2-seam3 migration? Thanks Denis.

13 years, 8 months

3
2
0 / 0

SEAMINTL-27

by José Rodolfo Carrijo de Freitas

Morning guys, Im working at the issue https://issues.jboss.org/browse/SEAMINTL-27 and the problem here is caused by an optional dependency. <dependency> <groupId>joda-time</groupId> <artifactId>joda-time</artifactId> <optional>true</optional> </dependency> So, I was talking with ken, and there´re two suggested approaches: 1. Mark the implementation classes that use joda-time with @Veto and require the developer to override that setting through XML Config if they want to use them 2. Mark the set of JDK dateTime and joda-time classes as two Alternative options and require the developer to specify which one to use. What option do you think is the better approach? Do you have any other idea? Either way we require the developer to say what he wants to use, This could be useful in some situations, but I guess that most of times, people just want to use the feature regarding what seam uses in its back. What do you think?

13 years, 8 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

seam-dev March 2011