module project anatomy
by Dan Allen
As promised, I have put together a page detailing the anatomy of a module
project in Seam 3. Please consider this a draft document and feel free to
provide feedback if there's something that doesn't seem agreeable to you.
Also, if you think there is an important detail missing, or an inconsistency
appears over time, please let us know.
http://seamframework.org/Seam3/ModuleAnatomy
Keep in mind that there are many different ways we could structure the
modules. What is important is that the structure is reasonable and that it
is consistent across modules. Contributors should be able to comfortable
move between modules and be familiar with how the code is setup.
-Dan
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen
14 years
Move weld-wicket to seam-wicket?
by Pete Muir
Hi all,
Since we've started developing Seam 3, I've started to think that the Wicket support is a better fit for Seam rather than Weld. Most of the Weld sub projects handle integrating Weld into other environments (such as Java SE) or provide support for using Weld (e.g. Weld extensions, archetypes).
There wasn't a consensus in our meeting yesterday, so I wanted to open it up for discussion.
Pete
14 years
Servlet execution threw an exception
by hamid aksasse
hello,im traying to run the register example but i get this error:
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:313)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:206)
org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388)
org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515)
org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
java.lang.Thread.run(Thread.java:619)i need your help.thank you .
********************************
HAMID AKSASSE
Elève Ingénieur en informatique
3eme Année ENSIAS
option :Génie Logiciel
(+212) 672 28 34 85
********************************
14 years
Maven version to use
by Pete Muir
All, whilst reviewing the Seam 3 pages, I noted that the recommendation was to use Maven 2.2. Actually, you should use Maven 2.0.10 if you want to be safe - the build should work with 2.2, but this is not guaranteed.
You're probably wondering why we are still using Maven 2.0.10 - this is based on advice from the Maven team who recommend that if you don't need a feature from 2.1 or 2.2 (we don't) it's best to stick with 2.0.10 until Maven 3 is available.
14 years
persistence module page drafted
by Dan Allen
I have put together an initial draft of the persistence module page [1].
I've outlined the major issues that this module needs to address along with
some rough design notes. The next step is to identify what features to
tackle first by sketching out a roadmap (alpha1, alpha2, etc with bullets
next to them). I'll take the first stab at it.
- If you are a current Seam committer interested in helping with this
module, please add your name to the table and feel free to revise or add to
the design notes.
- If you are not a Seam committer, you can start by helping with the design
notes and we can work you up to committer status as you demonstrate
commitment and expertise.
Like the security module, the persistence module is very important because
it fills a gap that still exists in Java EE (transactions for non-EJB
managed beans). Developers are mostly likely going to need this module to
write an app, primarily if they are trying to avoid using EJBs. I still
believe that we should advocate EJB 3.1, though, despite working on this
module. We could consider it a half-way house for people who have been
burned by EJB in the past :)
-Dan
[1 http://seamframework.org/Seam3/PersistenceModule
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen
14 years
