Blocked threads
by Dan Allen
> Also problematic seems to be the ManagedEntityIdentityInterceptor (I think
> we really could use a "no JavaBean clustering" switch that disables it -
> need some input from Gavin who initially wrote it if that is feasible):
I have concluded the *exact* same thing in my local tests and have it
written down on my notepad to ask about such a switch. I thoroughly
agree that for smaller scale or high throughput applications, we
absolutely don't need to incur the overhead of "swizzling" all of
these references, especially given that it is doing more work than it
has to do:
//TODO: could do better by checking if the
// collection really contains an entity
As for the transaction issue, why are we doing a JNDI lookup so many
times in one request? Shouldn't it only be needed once when the
Seam-managed global transaction is started? All subsequent calls such
use the one already discovered.
-Dan
--
Dan Allen
Software consultant | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction
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.
--
Dan Allen
Software consultant | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction
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.
17 years, 12 months
Releases of Seam 2.0 for JBoss AS 5
by Pete Muir
People,
As AS5 CR1 is due to come out soon, and Seam is (again) not working
right, we are going to need to do a release of the 2.0 branch so we
have a compatible release.
Stan has asked for release before/when AS5 CR1 is out, but we may well
end up having to do a Seam 2.0.3.CR2 once AS5 CR1 is out which
accounts for last minute changes in the AS5 codebase [1]. I guess less
work for us would be to test right up to the last minute with Seam_2_0
head, then put a tag in once the AS5 CR1 tag is in. Our release
process takes around 2 - 3 days, how long is the AS release process?
Will this fit timewise, Stan?
Stan, do you think this sounds sensible? Do you know what the time lag
between AS5 CR releases is going to be? i.e. do we then move Seam
2.0.3 to GA straight away, or do we hang around waiting for AS 5 GA.
Jay, can you fit this into your schedule?
Thanks,
[1] the problem that bit us last time is that we had Seam working a
couple of days before the tag, but some last minute change broke it.
On 3 Jun 2008, at 19:05, Stan Silvert wrote:
> I think it would be best to have that new Seam release for CR1,
> especially since this is supposed to be a "release candidate". But
> that's another debate on another thread.
>
> Of course, there is the risk that something else will come up that
> requires yet another Seam release before AS 5 final.
18 years
Name of generic type for persistence context
by Dan Allen
One of the comments from a reviewer of Seam in Action with regard to
org.jboss.seam.framework.PersistenceController et al
If you know why they chose to use "T" instead of, say, PM or P, that
would be good to say. "T" doesn't really make a lot of sense unless
they were talking about a "Transacton" manager … but this is a
persistence thing, right? Why not use "P"?
Is this worth a JIRA or explanation? Personally, I always interpreted
as being short for "type".
-Dan
--
Dan Allen
Software consultant | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction
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.
18 years
Seam and Tide?
by Cameron Ingram
Hi All!
We(GraniteDS) have released our Flex Seam integration. Tide significantly advances on my first implementation of combining the two techs. We would really be interested in being considered to be included in your examples distro. Tide currently in RC 1 has been integrated with Seam booking using the Seam code provided by the booking example with no changes. We got rid of all of those annoying issues that my first iteration had(constant updating of the flex-config, having to provide a declaration in AS for each Seam comp, no bijection integration, raw code). We think that we exemplify the concept of just using Seam.
All Seam components can be accessed from the Flex side without any additional configuration. What this means is that once you add the configuration files, which can be copied from project to project you never need to touch them again. Tide is very similar to Seam remoting.
i.e. (abbreviated to just include the interesting parts. )
<s:remote include="customerAction,accountAction"/>
Seam.Component.getInstance("helloAction").sayHello(name, sayHelloCallback);
The Tide flex code would look something like this
Seam.getInstance().getSeamContext().helloAction.sayHello(txtName.txt, sayHelloCallback);
Works in progress
- Tighter integration with Seam events(Synchronous and Asynchronous)
- An option to use Strong typing instead of dynamic
- A better Lazy loading implementation, on the Flex side
- Tighter security
Thanks for your time!
Cameron Ingram
________________________________
-----------------------------------------------------------------------
This e-mail is intended for the addressee shown.
It contains information that is confidential and
protected from disclosure. Any review, dissemination
or use of this transmission or its contents by persons
or unauthorized employees of the intended organizations
is strictly prohibited.
The contents of this email do not necessarily represent
the views or policies of PSCU Financial Services.
18 years
JUG presentation
by Chris Wash
Pardon the intrusion here I¹ve been following the list for a while and
think this may be an appropriate place to ask this my apologies if it¹s
not.
Would anyone be available and willing to speak at a local JUG in Richmond,
VA sometime? I know everyone¹s super busy, but I told some folks I would
ask.
Thanks!
Chris
18 years
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
18 years
