May 2008 - seam-dev - Jboss List Archives

Caching issues with JSF rendered attribute

by Christian Bauer

If any JSF guru knows how to control rendered="true|false" evaluation better, that would be useful: http://jira.jboss.com/jira/browse/JBSEAM-3008

12 years, 9 months

4
3
0 / 0

Page fragment cache with JBoss Treecache, ehcache and a FileSystemCache

by Sebastian Hennebrueder

Hello, I was working on the http://jira.jboss.com/jira/browse/JBSEAM-1891 and created three caching alternatives which can now be plugged in. As this is the first thing I write, I would appreciate a feedback, if the provided solution is what Christian was actually looking for and if I should continue this or made something completely useless. I attached the files and testng tests. If this is considered useful, I can provide a SVN patch as well. All files are new anyway. Cache Provider: JBoss TreeCache 1.4 API changes a lot from 1.4 to 2, so we must be careful once the I did not use the PojoCache as we have only simple Strings and no complex beans. In that case PojoCache provides only overhead. (info taken from pojocache wiki). Eh-Cache I did not enforce any Transaction guaranties (like READ_COMMITED) as we have in Hibernate for example. FileSystemCache Manually written, idea: a large site cannot be hold in a cache being present in memory. This cache has a small in memory area holding very frequent files (size can be configured) and fetches files from disk. Though the operation system caches access to disk, this is still a lot slower than memory access but probably faster than having complex queries to the database (see Seam Wiki queries) The Cache can already be used in a web application using a custom renderer kit. example for components.xml <component class="org.jboss.seam.cache.PageFragmentCache"> <property name="provider">#{filecache}</property> </component> <component class="org.jboss.seam.cache.FileSystemCacheProvider" name="filecache"> <property name="boostBufferSize">50</property> <property name="enableStatistics">true</property> </component> <component class="org.jboss.seam.statistics.StatisticsManager" /> Another idea: I introduces a StatisticsManger component which might be used by any components providing statistic information. This would provide one place to access statistics of the application or to print a report. If you like the idea, I would add a MBean wrapping this StatisticsManager else I'll just remove it from the cache providers. Some questions: I did not find a way to access the name of the application (web context) to use it as prefix for the JBoss TreeCache in case we use multiple applications on the same system. Is there a common way to load resources like configuration files? I saw different approaches in the core code. Best Regards Sebastian Hennebrueder laliluna.de

12 years, 9 months

4
5
0 / 0

Seam Guice integration

by Dan Allen

Given that we have Spring integration in the IoC module, it makes sense that we would have Guice in there as well. Paul, would you be interested in seeing the Guice module become part of the Seam project? Seam devs, would this be something we want to see in Seam? I think it should. Granted, I know that there is the whole Web Beans coming down the pike, but given that this integration is already implemented, why not make it available in Seam 2.1? -Dan -- Dan Allen Software consultant | Author of Seam in Action http://www.mojavelinux.com http://manning.com/dallen NOTE: While I make a strong effort to keep up with my email on a daily basis, life and work come first and, at times, keep me away from my mail for a while. If you contact me, then don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention.

12 years, 10 months

4
6
0 / 0

Metawidget

by Emmanuel Bernard

Has anyone looked at it? http://kennardconsulting.blogspot.com/2008/04/using-metawidget-with-seam-... How does it stand? Emmanuel

12 years, 10 months

4
3
0 / 0

Dependency nightmares

by Sebastian Hennebrueder

Hello, I am using Seam outside of the 'seam-gen give me some megbyte of libs approach' using only a minimal set of libs required to have a seam app running. IMHO dependencies should be minimized to allow better intregration in all directions as well. Frontend Frameworks, Persistence -> we are currently seeing the alternative provider discussion, backend -> Integration with whatever. A blank Seam app requires even if not using transaction management and not using JPA the following libs ejb-api.jar persistence-api.jar hibernate-commons-annotations.jar hibernate-validator.jar (OK we use it for validation but ...) -- which in turn requires hibernate.jar And I haven't checked all possible use cases. So there might be even more. What do you think? Best Regards Sebastian Hennebrueder

12 years, 11 months

2
2
0 / 0

Seam Design Document

by Steve Roy

Hello, Is there some type of Seam Design document candidate contributing developers can review? - steve

12 years, 11 months

1
0
0 / 0

Re: Seam and modules

by Gavin King

Hi Stefan, we have talked about something like this, and have prototyped a plugin architecture in Seam Wiki. However, we are not ready to productize it yet... On Tue, May 27, 2008 at 2:42 AM, Stefan Nilsson <thalerion(a)gmail.com> wrote: > Hi Gavin! > > My name is Stefan Nilsson, a developer from Sweden, and I am a huge fan of > Jboss Seam. I work at an company which creates webbased quality registers > for the Health care sector. We are in a phase when we are going to create a > platform and I am going to pitch that we use Seam. One questions if you > don´t mind as I am sure you get a lot of email like this. One goal with the > platform is that is going to be modulerized. We will be developing an API > that would allow us to develop plugins/modules for the applications built on > the platform. Once the basic portal/application is up it would be able > start/stop modules and the modules would integrate directly with existing > components in the system, with autenticating, and permission handling. My > knowledge of Seam is only basic and I wonder if there is support for > handling components like this in seam or if we must add anoter framework to > do the job. Do you any frameworks/platforms that would integrate with Seam > like this? My first ideas was to build on Jboss Portal and developing > portlets as modules which would share context through the portal context but > is this the best idea? > > Best regards > Stefan Nilsson > > > -- Gavin King gavin.king(a)gmail.com http://in.relation.to/Bloggers/Gavin http://hibernate.org http://seamframework.org

12 years, 11 months

3
2
0 / 0

Re: A question from Venezuela. Integrating Seam with LifeRay Portal..

by Gavin King

Hola Alfredo, muchas gracias por tus palabras :-) I'm not sure if anyone has done work on Liferay support, I'm cc-ing the team... On Wed, May 21, 2008 at 2:15 PM, Alfredo Rico <alfredorico(a)gmail.com> wrote: > Hi Gavin, my name is Alfredo Rico and I'm from Venezuela.. > My english is not so good, please apologize. > > I'm so thankful about JBoss Seam.. It's a amazing framework that has > become my life even more happy ;-) > > I have this question if you could answer.. > > It would be possible to integrate seam applications with LifeRay > portal (by means of portlets)? I think that LifeRay portal is a > powerful Java EE portal and even Sun MicroSystem has joined to LifeRay > team to make it a better product. > > So, I'm thinking (at glance) to use JBoss Seam as a core bussines > software (raw, application per se ) embedded on portlets at LifeRay > and take advantage of the layout, security, and administration > infrastructure that Liferay provides. > > What do you think about it?.. Any suggest?.. > > Greetings!.. > > > Kind regards.. > > -- > Saludos Cordiales.- > Alfredo Rico. > San Cristóbal - Venezuela. > -- Gavin King gavin.king(a)gmail.com http://in.relation.to/Bloggers/Gavin http://hibernate.org http://seamframework.org

12 years, 11 months

2
1
0 / 0

lobbying for alternative JPA provider support in 2.0.2.SP1

by Dan Allen

Seam devs, I am bringing a topic that happened in a private e-mail between Jay and I to the list. The main issue that I really want to see included in 2.0.2.SP1 is this fix for the PersistenceProvider (JBSEAM-3030). It bothers me that we are blatantly not supporting other JPA providers, even though we all know how important manual flushing is (trust that I find it the single most lacking feature in JPA). This is not a regression, but it sure feels like one. The backstory is that if you have at least one component with a persistence context (e.g. @In private EntityManager entityManager or @PersistenceContext private EntityManager entityManager), then Seam will attempt to put it into manual flush mode before rendering. When that happens, you are using the generic JPA provider, an exception is thrown, failing the rendering process. The only way around this issue is to implement your own PersistenceProvider and override the setManualFlushMode() to do nothing. My fix changes this exception to a log warning message. -Dan -- Dan Allen Software consultant | Author of Seam in Action http://www.mojavelinux.com http://manning.com/dallen NOTE: While I make a strong effort to keep up with my email on a daily basis, life and work come first and, at times, keep me away from my mail for a while. If you contact me, then don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention.

12 years, 11 months

3
4
0 / 0

Starting release of 2.0.2.SP1

by Jay Balunas

People, Except for the outcome of the discussion on Dan's email "lobbying for alternative JPA provider support in 2.0.2.SP1" all the issues scheduled for Seam 2.0.2.SP1 are now closed, so we are moving to tag, port, and test for the release. This is a very targeted release and will only include a few changes. However please do not commit any changes to the Seam_2_0 branch until the issues have been ported to the SP1 tag. You need to pre-clear any commits with Jay. The porting of these changes should not take too long. Any changes needed from Dan's email will ported as required. Thanks

12 years, 11 months

1
0
0 / 0

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

seam-dev May 2008