Built with Seam
You can find the full source code for this website in the Seam package in the directory /examples/wiki. It is licensed under the LGPL.
| Online: | 10 Members of 4089 |
| Forum: Seam Users |
 |
01. Oct 2008, 18:32 CET | Link |
Seam 2.1.0.CR1 is out.
[Download] [Reference Documentation] [JIRA] [Release Notes]
You can get the full details from the blog, but I suspect everyone here has a good idea of what is in 2.1 already. I would like to emphasize the importance of testing it out with your apps. I think we'd all rather find problems before the release rather than after the release.
Congratulations! Great job, Seam team!!!
I couldn't find any mention in the docs or blog posting/ changelog of what 'Built in support for URL rewriting' entails.
Can it finally handle rewriting of urls that point to custom servlets? Any additional details would be appreciated as I was just starting to hack on the urlrewrite src to add some additional features.
thanks much, and great job :)
-Dustin
I'm guessing: Resteasy
See http://docs.jboss.org/seam/2.1.0.CR1/reference/en-US/html/configuration.html#d0e22490, section 29.1.4.3
Read about how to report a bug.
Thanks Daniel, looks like resteasy will help solve my custom servlet delema in the future (though, doesn't help with my current codebase).
Thanks Pete for pointing the urlrewrite section of the docs, exciting stuff :) (looks like that section is missing from the doc index page).
To answer the question, the rewriting is intended to be a super-trivial way to write bi-directional rewrite rules for Seam URLs. There's no way to specify rules for non-Seam URLs.
I'm not sure exactly what you mean by custom servlets, but in general mapping to another servlet is hard. One of the big problems is that although you can easily retarget a request to a different servlet, you can't do so while maintaing the full chain of servlet filters. I don't know any way to do that within the scope of the Servlet spec, so if that's the problem you are trying to solve with urlrewrite, I'd love to know what your solution is. If that's not your problem, then I'm really not sure what you are finding you can't do with urlrewrite.
Hi, I can't geenerate documentation. I get this:
[java] [INFO] [jdocbook:generate] [java] 2-ott-2008 12.36.59 org.apache.fop.hyphenation.Hyphenator getHyphenationTree [java] GRAVE: Couldn't find hyphenation pattern en [java] 2-ott-2008 12.37.01 org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm updateData2 [java] AVVERTENZA: Line 1 of a paragraph overflows the available area. (fo:block, location: -1/-1) [java] [INFO] ------------------------------------------------------------------------ [java] [ERROR] FATAL ERROR [java] [INFO] ------------------------------------------------------------------------ [java] [INFO] null [java] [INFO] ------------------------------------------------------------------------ [java] [INFO] Trace [java] java.lang.NullPointerException [java] at org.apache.fop.render.pdf.FopPDFImage.setup(FopPDFImage.java:144) [java] at org.apache.fop.pdf.PDFDocument.addImage(PDFDocument.java:726) [java] at org.apache.fop.render.pdf.PDFRenderer.putImage(PDFRenderer.java:1464)Something wrong in my system?
Thx, N
https://jira.jboss.org/jira/browse/JBSEAM-3490
Read about how to report a bug.
Hi there,
When I tested Seam 2.1.0.CR1, I felt that it is slower than Seam 2.0.3.CR1, but it is much better thant Seam 2.1.0.BETA. And it seems that Seam 2.1.0.CR1 consumed more CPU on every call. It will be great if Seam 2.1.0.GA can include this jira https://jira.jboss.org/jira/browse/JBSEAM-2704. Thanks.
Hi,
Great job, Seam is just getting better and more attractive!
Did find something that resembles a bug, application is quite big, so hard to copy; but it looks like with Seam 2.1CR1 I am seeing application initialization events being called all at request time.
The application have a number of methods that use this annotation to setup one-time startup things (such as scheduled timers etc):
@org.jboss.seam.annotations.Observer()
It looks like those methods are being called at full page (HTTP) requests and at Ajax (Ajax4J) requests as well (used in the app when leaving a field, using the a4j:support (with an event type of onblur) tag.
This behavior did no occur using Seam 2.0.2, before upgrading the app to 2.1.0.CR1 we did not see this behavior.
Console output, when going from one field to another in a form (the CustomRequestHandlerManager output below is from a @org.jboss.seam.annotations.Observer() annotation. Also it looks like Seam triggers a refresh of all libraries as well?
09:31:46,699 INFO [RewriteFilter] incoming URL is /z/library/community/blog/view.seam 09:31:46,699 INFO [RewriteFilter] known patterns are [Pattern(/z/library/community/blog/edit-post.seam:/blog/entry/edit/{blogid}/{id}), Pattern(/accelerator/swedish/index.seam:/accelerator/swedish), Pattern(/about/index.seam:/about), Pattern(/investors/index.seam:/investors), Pattern(/login.seam:/login), Pattern(/z/library/community/blog/new-post.seam:/blog/entry/new/{blogid}), Pattern(/tradesale/index.seam:/tradesale), Pattern(/accelerator/services/index.seam:/accelerator/services), Pattern(/business-lab/index.seam:/business-lab), Pattern(/z/library/community/blog/view.seam:/blog/{blogid}/{year}/{month}/{day}/{name}), Pattern(/index.seam:), Pattern(/signup.seam:/signup), Pattern(/z/library/community/blog/rss.seam:/blog/rss/{blogid}), Pattern(/accelerator/index.seam:/accelerator), Pattern(/about/contact/index.seam:/about/contact), Pattern(/about/people/index.seam:/about/people), Pattern(/accelerator/companies/index.seam:/accelerator/companies), Pattern(/z/library/community/blog/list.seam:/blog/{blogid})] 09:31:46,724 INFO [CustomRequestHandlerManager] Added mapping for '/blog/rss' -> com.saguru.sisp.blog.rssRenderer 09:31:46,741 INFO [BlogEntryViewer] View by name: /blog/1/2008/10/3/Test 09:31:46,786 ERROR [STDERR] Oct 6, 2008 9:31:46 AM com.sun.facelets.impl.DefaultFacelet refresh INFO: Facelet[/file:/Users/nicolaiw/Projects/lib/jboss/jboss-4.2.2.GA/server/default/tmp/deploy/tmp65214testapp-website.ear-contents/lib/saguru-seam-cms-0.0.1-SNAPSHOT.jar!/META-INF/facelet-tags/community/blog/blogEntry.xhtml] was modified @ 9:31:46 AM, flushing component applied @ 9:31:40 AM 09:31:46,786 ERROR [STDERR] Oct 6, 2008 9:31:46 AM com.sun.facelets.impl.DefaultFacelet refresh INFO: Facelet[/file:/Users/nicolaiw/Projects/lib/jboss/jboss-4.2.2.GA/server/default/tmp/deploy/tmp65214testapp-website.ear-contents/lib/saguru-seam-cms-0.0.1-SNAPSHOT.jar!/META-INF/facelet-tags/community/blog/blogEntry.xhtml] was modified @ 9:31:46 AM, flushing component applied @ 9:31:40 AM 09:31:46,787 ERROR [STDERR] Oct 6, 2008 9:31:46 AM com.sun.facelets.impl.DefaultFacelet refresh INFO: Facelet[/file:/Users/nicolaiw/Projects/lib/jboss/jboss-4.2.2.GA/server/default/tmp/deploy/tmp65214testapp-website.ear-contents/lib/saguru-seam-cms-0.0.1-SNAPSHOT.jar!/META-INF/facelet-tags/community/blog/blogEntry.xhtml] was modified @ 9:31:46 AM, flushing component applied @ 9:31:40 AM 09:31:46,787 ERROR [STDERR] Oct 6, 2008 9:31:46 AM com.sun.facelets.impl.DefaultFacelet refresh INFO: Facelet[/file:/Users/nicolaiw/Projects/lib/jboss/jboss-4.2.2.GA/server/default/tmp/deploy/tmp65214testapp-website.ear-contents/lib/saguru-seam-cms-0.0.1-SNAPSHOT.jar!/META-INF/facelet-tags/community/blog/blogEntry.xhtml] was modified @ 9:31:46 AM, flushing component applied @ 9:31:40 AM 09:31:46,788 ERROR [STDERR] Oct 6, 2008 9:31:46 AM com.sun.facelets.impl.DefaultFacelet refresh INFO: Facelet[/file:/Users/nicolaiw/Projects/lib/jboss/jboss-4.2.2.GA/server/default/tmp/deploy/tmp65214testapp-website.ear-contents/lib/saguru-seam-cms-0.0.1-SNAPSHOT.jar!/META-INF/facelet-tags/community/blog/blogEntry.xhtml] was modified @ 9:31:46 AM, flushing component applied @ 9:31:40 AM 09:31:46,788 ERROR [STDERR] Oct 6, 2008 9:31:46 AM com.sun.facelets.impl.DefaultFacelet refresh INFO: Facelet[/file:/Users/nicolaiw/Projects/lib/jboss/jboss-4.2.2.GA/server/default/tmp/deploy/tmp65214testapp-website.ear-contents/lib/saguru-seam-cms-0.0.1-SNAPSHOT.jar!/META-INF/facelet-tags/community/blog/blogEntry.xhtml] was modified @ 9:31:46 AM, flushing component applied @ 9:31:40 AM 09:31:46,789 ERROR [STDERR] Oct 6, 2008 9:31:46 AM com.sun.facelets.impl.DefaultFacelet refresh INFO: Facelet[/file:/Users/nicolaiw/Projects/lib/jboss/jboss-4.2.2.GA/server/default/tmp/deploy/tmp65214testapp-website.ear-contents/lib/saguru-seam-cms-0.0.1-SNAPSHOT.jar!/META-INF/facelet-tags/community/blog/blogEntry.xhtml] was modified @ 9:31:46 AM, flushing component applied @ 9:31:40 AM 09:31:46,789 ERROR [STDERR] Oct 6, 2008 9:31:46 AM com.sun.facelets.impl.DefaultFacelet refresh INFO: Facelet[/file:/Users/nicolaiw/Projects/lib/jboss/jboss-4.2.2.GA/server/default/tmp/deploy/tmp65214testapp-website.ear-contents/lib/saguru-seam-cms-0.0.1-SNAPSHOT.jar!/META-INF/facelet-tags/community/blog/blogEntry.xhtml] was modified @ 9:31:46 AM, flushing component applied @ 9:31:40 AM 09:31:46,789 ERROR [STDERR] Oct 6, 2008 9:31:46 AM com.sun.facelets.impl.DefaultFacelet refresh INFO: Facelet[/file:/Users/nicolaiw/Projects/lib/jboss/jboss-4.2.2.GA/server/default/tmp/deploy/tmp65214testapp-website.ear-contents/lib/saguru-seam-cms-0.0.1-SNAPSHOT.jar!/META-INF/facelet-tags/community/blog/blogEntry.xhtml] was modified @ 9:31:46 AM, flushing component applied @ 9:31:40 AM 09:31:46,795 ERROR [STDERR] Oct 6, 2008 9:31:46 AM com.sun.facelets.impl.DefaultFacelet refresh INFO: Facelet[/file:/Users/nicolaiw/Projects/lib/jboss/jboss-4.2.2.GA/server/default/tmp/deploy/tmp65214testapp-website.ear-contents/lib/saguru-seam-cms-0.0.1-SNAPSHOT.jar!/META-INF/facelet-tags/community/blog/blogEntryComments.xhtml] was modified @ 9:31:46 AM, flushing component applied @ 9:31:40 AM 09:31:46,821 INFO [RewritingResponse] encodeURL /a4j_3_2_0-SNAPSHOTorg/richfaces/renderkit/html/css/basic_classes.xcss/DATB/eAGbPPdfKgAGiAKU -> /a4j_3_2_0-SNAPSHOTorg/richfaces/renderkit/html/css/basic_classes.xcss/DATB/eAGbPPdfKgAGiAKU 09:31:46,822 INFO [lifecycle] WARNING: FacesMessage(s) have been enqueued, but may not have been displayed. sourceId=j_id70:j_id74:j_id87:name:j_id93[severity=(ERROR 2), summary=(j_id70:j_id74:j_id87:name:j_id93: Validation Error: Value is required.), detail=(j_id70:j_id74:j_id87:name:j_id93: Validation Error: Value is required.)] sourceId=j_id70:j_id74:j_id87:email:j_id99[severity=(ERROR 2), summary=(j_id70:j_id74:j_id87:email:j_id99: Validation Error: Value is required.), detail=(j_id70:j_id74:j_id87:email:j_id99: Validation Error: Value is required.)] sourceId=j_id70:j_id74:content:j_id113[severity=(ERROR 2), summary=(j_id70:j_id74:content:j_id113: Validation Error: Value is required.), detail=(j_id70:j_id74:content:j_id113: Validation Error: Value is required.)] sourceId=j_id70:j_id74:j_id87:captcha:verifyCaptcha[severity=(ERROR 2), summary=(j_id70:j_id74:j_id87:captcha:verifyCaptcha: Validation Error: Value is required.), detail=(j_id70:j_id74:j_id87:captcha:verifyCaptcha: Validation Error: Value is required.)]I think I fixed this in trunk, please try a nightly build
Read about how to report a bug.