January 2012 - seam-dev - Jboss List Archives

by Jason Porter

I'll be up late / early depending on how you look at it with the forum migration. I also don't have anything to really talk about. -- 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

14 years, 9 months

1
0
0 / 0

JBoss Seam 2.3 Archetype for maven

by Daniel Hinojosa

Since 2.3 is mavenized should there a be a mvn archetype : jboss-seam-2.3-ear and jboss-seam-2.3-war? There are currently jboss-javaee6-webapp-archetype but I think those are WELD/CDI based applications.

14 years, 9 months

3
2
0 / 0

Moving Oauth authenticator to Seam Security

by Antoine Sabot-Durand

Hi All, Marek did a great job by creating an Oauth authenticator for Seam Security in Seam Social. Now I think it would be better to move it to Security external modules (beside OpenId). From a user point of view I think it would be more consistent to have all authentication module in the same place. If there are no objection I'll move the code (Shane gave me right on Security looooong ago) or provide a pull request. regards, Antoine SABOT-DURAND

14 years, 9 months

3
4
0 / 0

Crowd-sourcing for a forum answer

by Jason Porter

http://seamframework.org/Community/SeamFacesCausesExceptionInJBossAS7EarD... Anyone have a working EAR that's updated to 3.1.0.Final with Faces? Really seems like we need an example, if someone has one ready :) -- 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

14 years, 9 months

3
10
0 / 0

Meeting 2012-25-01

by Jason Porter

I don't have anything for this week's meeting, but I will be online if people have things to discuss. I am also looking for people to help migrate [1] to [2] to help our migration efforts. It seems like we're pretty much using textile for the markup language in the wiki. You can clone the repo by using instructions at [3]. I haven't received any pull requests yet, so I don't exactly know how that will work, but I'd like to find out ;) I have also posted a forum question [3] to see where the community would like the next few Seam 3 releases to go. I haven't had a lot of feedback however. I'm not sure if that's because people are no longer interested in Seam 3, they've just given up, or some other reason. As it currently stands we'll be doing documentation, examples (please, if you have docs you would like to see updated or examples to contribute send us some pull requests) and minor bug fixes. As always, thank you all for your help and support! [1] http://seamframework.org/Seam3/Seam2ToSeam3MigrationNotes [2] https://github.com/seam/migration/wiki [3] https://github.com/seam/migration/wiki/_access [4] http://seamframework.org/Community/TheNextFewSeamReleases -- 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

14 years, 9 months

1
0
0 / 0

Meeting 2012-01-18

by Jason Porter

Agenda - Migration Repository (10 minutes) - Call for examples (10 minutes) - Call for Documentation (10 minutes) The idea is mostly to follow up with what we discussed last week and also along with the forum post I mentioned earlier. -- 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

14 years, 9 months

2
3
0 / 0

Seam REST and WELD-001303 No active contexts

by Ove Ranheim

Hi guys, I'm getting a "WELD-001303 No active contexts for scope type javax.enterprise.context.ConversationScoped" when making a call to a REST service that invokes a ConversationScoped bean. Did I miss a configuration setting, or isn't ConversationScoped supported? Ove javax.ejb.EJBTransactionRolledbackException: WELD-001303 No active contexts for scope type javax.enterprise.context.ConversationScoped org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(CMTTxInterceptor.java:133) org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:196) org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:286) org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:182) org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) org.jboss.as.ejb3.component.session.SessionInvocationContextInterceptor.processInvocation(SessionInvocationContextInterceptor.java:71) org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:146) org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:76) com.parts.apartment.management.ApartmentService$$$view2.listApartmentUnits(Unknown Source) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305) org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299) org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:125) org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:62) org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125) com.parts.apartment.management.ApartmentService$Proxy$_$$_Weld$Proxy$.listApartmentUnits(ApartmentService$Proxy$_$$_Weld$Proxy$.java) com.parts.apartment.management.ApartmentService$Proxy$_$$_WeldClientProxy.listApartmentUnits(ApartmentService$Proxy$_$$_WeldClientProxy.java) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:140) org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:255) org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:220) org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:209) org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:519) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:496) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119) org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) javax.servlet.http.HttpServlet.service(HttpServlet.java:847) org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) org.jboss.solder.servlet.exception.CatchExceptionFilter.doFilter(CatchExceptionFilter.java:65) org.jboss.solder.servlet.event.ServletEventBridgeFilter.doFilter(ServletEventBridgeFilter.java:74) com.ocpsoft.pretty.PrettyFilter.doFilter(PrettyFilter.java:126)

14 years, 10 months

4
17
0 / 0

Going forward

by Jason Porter

Part of this mail is going to be open thoughts from me, so if you don't agree, that's fine, it's really open for discussion. I'm wondering what everyone wants to focus on for Seam 3.2.0. Obviously we need to support those currently running on Seam 3, and we'll also continue to work on DeltaSpike. I think eventually we will cut a Seam 3 release that's based on DeltaSpike Core instead of Solder, which should make things much easier for people when migration time comes, or if they want to use MyFaces CODI extensions as well. We currently have 369 issues against Seam 3. I'm not sure how many we squashed during the Seam 3.1 cycle, but I know it was quite a bit, maybe 150+. I'd like to hear from the community as well as the module leads what they feel like we should be working on for this next Seam development cycle. I know we have said we were going to focus on documentation and examples, and I still believe that needs to happen. Obviously we need to do some other dev as well. Maybe a good example though will drive some of that development. Right now the current examples are very weak and typically only focus on one or two modules. I have my Confbuzz example [1] which is up to date with Seam 3.1.0.Final, but is really lacking features. It could be a good place to start if nothing else. Does anyone else have any thoughts or a direction they'd like to see things move? [1] https://github.com/seam/seam-example-confbuzz -- 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

14 years, 10 months

6
6
0 / 0

Seam 3.1 Final released

by Shane Bryzak

Hi team, We've now announced the release of Seam 3.1 Final: http://in.relation.to/Bloggers/JBossSeam31FinalReleased There were a few minor hiccups with building the distribution which delayed the release for a few days, however I'm happy to say we eventually got them sorted out. I'd like to thank everyone involved with this release, it's quite a solid upgrade with 6 new modules and well over 200 bugs fixed since Seam 3.0. As for what comes next, we plan to do a Seam 3.1.1 release in a couple of months. This will be a stop-gap release to address any bug fixes with the 3.1 release and/or give us a chance to implement any outstanding feature requests. After this, I imagine that DeltaSpike will have at least a complete-ish release of deltaspike-core and we should be able to concentrate our efforts going forward on migrating our modules to DS. With this in mind, if you have any fixes that you would like to include in 3.1.1, please add this version to your module in JIRA (or ask Jason or I to do it) so we can keep track of it. Thanks! Shane

14 years, 10 months

1
0
0 / 0

[Security] How to set custom IdentityStore implementation?

by michal.kaplon＠poczta.fm

Hello, Recently we found a bug in JpaIdentityStore class. In line 2114 query string is build this way: queryString.append("select distinct ior. " + modelProperties.get(PROPERTY_RELATIONSHIP_TO).getName() + "from " which produces unparseable query. Since it is in 3.1.0.Final, waiting for the next release probably isn't the best solution :) That's why I need to replace default JpaIdentityStore with my custom implementation. How can I do that? I've tried to reconfigure JpaIdentityStoreConfiguration via XML, but identityStoreClass remains unchanged. Very strange thing, especially that server log says the bean is reconfigured. Is that because IdentityStoreConfiguration.identityStoreClass is private field? IdentityStoreConfiguration itself cannot be configured, because it is abstract. Next try was to @Specialize JpaIdentityStoreConfiguration, however it also failed. This issue smells like @AplicationScoped beans cannot be specialized, which is also weird. Any help will be appreciated. -- Best regards, Michal

14 years, 10 months

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

seam-dev January 2012