Summary of a tentative to run seam-booking (from Seam 3 CR3) on WebSphere v8 beta
by Denis Forveille
Here is a summary of the problems I had while trying to run seam-booking (from seam CR3) in websphere v8 beta (march refresh)
I was not able to start the applications
I will make another tentative when the next release os Seam 3 will be out
Some of the JIRA are already resolved.
Denis
PS: For those who would like to try to do the same thing, edit file <app_install_dir>/properties/amm.filter.properties in WAS and
remove references to packag org.jboss.seam in this file before deploying the app.
---------------------------------
Class org.jboss.seam.transaction.TransactionManagerSynchronizations contains an annotation @Remove but this class in not a SFSB..
---> SEAMPERSIST-44
Exception javax.enterprise.inject.UnproxyableResolutionException: WebBeans with api type with normal scope must be proxiable to inject.
javax.el.ExpressionFactory has final methods! CDI doesn't allow that.
---> SOLDER-99
File WEB-INF/seam-beans.xml has problems:
java.lang.Exception: Could not resolve node specializes in namespace urn:java:seam:core at
file:/data/ws/ws_seam3/Test2Web/WebContent/WEB-INF/seam-beans.xml:28
at org.jboss.seam.config.xml.bootstrap.XmlConfigExtension.beforeBeanDiscovery(XmlConfigExtension.java:135)
---> SEAMXML-40
Seam-transaction (TransactionExtension) depends on slf4j instead of jboss-logging as the other modules
---> SEAMPERSIST-42
Version mismatch between sl4j jars:
- slf4j-api.jar is at version 1.6.1
- slf4j-log4j12.jar is at version 1.5.10
---> SEAM-55
Extension that have their constructor in scope "package" instead of "public" that makes the initialization to fail in WAS :
- org.jboss.seam.servlet.ServletExtension
- org.jboss.seam.servlet.logging.TypedMessageBundleAndLoggerExtension
- org.jboss.seam.solder.logging.TypedMessageLoggerExtension
- org.jboss.seam.solder.messages.TypedMessageBundleExtension
- org.jboss.seam.solder.serviceHandler.ServiceHandlerExtension
---> SOLDER-90 created by Dan
---> SEAMSERVLET-31 created by Dan
File META-INF/beans.xml in seam-conversation-spi.jar does not conform to beans.xml file schema
---> no JIRA created
Missing jars:
- ocpsoft-pretty-time.jar
- prettyfaces-jsf2.jar
- commons-beanutils.jar
- commons-digester
---> SEAM-56
14 years, 11 months
Running weld + solder + wicket on GAE
by Marek Śmigielski
Hi,
I have managed to deploy and successfully test simple injection of
weld-servlet, seam-wicket and solder module to GAE. This task involves
making some modifcations in all of this modules.
1. seam-solder
In AbstractJndiBeanManagerProvider I have added catch for
NoClassDefFoundError just after NamingException. GAE can't initialize
InitialContext.
>> java.lang.NoClassDefFoundError: Could not initialize class com.google.apphosting.runtime.security.shared.stub.javax.naming.InitialContext
2. seam-wicket
I have added service ServletContextBeanManagerProvider which resolves
BeanManager from ServletContext as JNDI based providers does not work.
3. weld-core
I have changed catching exception from ResourceLoadingException to
Throwable. It is widest possible catch declaration, in fact catching
specific exceptions would be probably better or GAE exceptions should
be catch deeper and rethrown as ResourceLoadingException.
There is problem with adding this classes during deployment:
org.jboss.seam.solder.bean.generic.GenericBeanExtension$1
org.jboss.seam.solder.util.collections.AbstractMultiset$ElementSet$1
org.jboss.logging.JBossLogManagerProvider
org.jboss.seam.solder.bean.defaultbean.DefaultBeanExtension$1
org.jboss.seam.solder.util.collections.AbstractMultimap$KeySet$1
org.jboss.logging.Log4jLogger
org.jboss.logging.JBossLogManagerLogger
>>Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission accessDeclaredMembers)
4. weld-core
In InstantiatorFactory I have commented out adding
ReflectionFactoryInstantiator. It is not allowed to use
ReflectionFactory on GAE. Adding reflection factory should be check
programmatically before creating new instance in some if clause.
>> java.lang.NoClassDefFoundError: sun.reflect.ReflectionFactory is a restricted class. Please see the Google App Engine developer's guide for more details.
>> at com.google.appengine.runtime.Request.process-609c29691be26e8f(Request.java)
>> at sun.reflect.ReflectionFactory.<clinit>(ReflectionFactory.java)
>> at java.lang.reflect.Method.invoke(Method.java:43)
>> at org.jboss.weld.util.reflection.instantiation.ReflectionFactoryInstantiator.<init>(ReflectionFactoryInstantiator.java:45)
I have not tested yet which solder features are working and which ones
not. In wicket page injection works as expected.
If you are interested in providing support for GAE, I think it would
be great to have this changes apply to master branch. Some of them
(especially 3 and 4) need some more development and propably support
from weld team.
Marek
15 years
Re: [seam-dev] Seam module spotlight series
by Jason Porter
I could, haven't yet though.
On Mon, Apr 11, 2011 at 12:26, José Rodolfo Carrijo de Freitas <
jose.freitas(a)softplan.com.br> wrote:
> Nice, are you going to post in TSS ? or another big it news website?
>
>
>
>
>
> *De:* seam-dev-bounces(a)lists.jboss.org [mailto:
> seam-dev-bounces(a)lists.jboss.org] *Em nome de *Jason Porter
> *Enviada em:* sábado, 9 de abril de 2011 15:08
> *Para:* Shane Bryzak
> *Cc:* seam-dev(a)lists.jboss.org
> *Assunto:* Re: [seam-dev] Seam module spotlight series
>
>
>
> Attached is the markdown file for the first entry.
>
> On Fri, Apr 1, 2011 at 20:36, Shane Bryzak <sbryzak(a)redhat.com> wrote:
>
> Guys,
>
> I'd like to start up a weekly Seam module spotlight. Basically, each
> week I'd like one of you to write up an article that we can publish on
> in.relation.to that shows off the best features of your module.
> Preferably the article would be use-case centric, as opposed to the
> feature-centric style that we generally write with in the reference
> documentation. For example, if I was writing a blog post about the
> persistence module I would make the point that if you're writing POJO
> beans to implement your business layer that I would not have transaction
> support by default, and that is where the transaction features of the
> persistence module come in. I'd also explain how it could be useful in
> other container environments, such as Tomcat or even Java SE.
>
> This style of writing is more likely to get your readers to a point
> where they understand why your module is as cool as we say it is, as
> they can relate its coolness in terms of real life use cases. Whereas
> explaining things from a feature point of view might leave some confused
> as to how they can actually *use* that feature in their own projects.
>
> Anyway, I'm looking for a brave volunteer to go first. Ideally we'd get
> the first spotlight article published by the end of next week (before
> the 9th) so that should leave enough time to put together an informative
> article.
>
> Shane
> _______________________________________________
> seam-dev mailing list
> seam-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
>
>
>
>
> --
> 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
>
--
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
15 years
Naming convention and package organization advice
by Antoine Sabot-Durand
Hi Team,
in Seam social I created bean to deal with social network. I named those Bean with "Handler" suffix : i.e. TwitterHandler. I choose this over "Service" or "Controller" but as there will be other Seam module dealing with high level functional services, I prefer check this naming convention with you. Sharing the same naming convention across modules to have something homogenous is something important.
Antoine SABOT-DURAND
---------------------------------------
Twitter ; http://twitter.com/antoine_sd
LinkedIn : http://fr.linkedin.com/in/antoinesabotdurand
15 years, 1 month
getting code from my dark twin ;-)
by Antoine Sabot-Durand
Guys,
As some of you know, Seam Social project was initiated because of Spring Social and Lincoln (he made me develop it because he had some other obscure project to forge ;-)). Today, Spring social (leaded by Craig Walls) is one year older than Seam Social and a lot of code in this project could benefit mine. My question is "can I get this code ?" (Apache 2 License) and if I can "How do I proceed ? Legally and diplomatically ?". Thank for your feedback
regards,
Antoine SABOT-DURAND
---------------------------------------
Twitter ; http://twitter.com/antoine_sd
LinkedIn : http://fr.linkedin.com/in/antoinesabotdurand
15 years, 1 month
Branch 2.2 is frozen
by Marek Novotny
I am starting to prepare quick 2.2.2.Final release today.
2.2 branch is frozen until I create the tag
for 2.2.2.Final.
Thanks for respecting it.
--
Marek Novotny
--
Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
Email: mnovotny(a)redhat.com
Office phone: +420 532 294 287, ext. 82-62 087
mobile: +420 608 509 230
15 years, 1 month
Seam BOM Forge Facet
by Ken Finnigan
All,
Create simple Forge facet for Seam that adds the BOM as a managed dependency
to a project.
Had originally created SEAM-82 for it, but not sure where it should live
now? As part of Seam or in the Forge plugin repository?
Code is at https://github.com/kenfinnigan/plugin-seam-bom
Regards
Ken Finnigan
15 years, 1 month
