Seam JMS and AS7
by John D. Ament
Hey all
So I was testing Seam JMS on AS7 last night. Now today I saw that the
default example container is going to be AS7.. I have an issue with that.
Specifically, JMS doesn't work correctly on AS7 in general. The web profile
deployment does not include hornetq. The preview release has hornetq, but
there are a few issues with it. Specifically, the classloader architecture
does not work correctly with ObjectMessages. This is pretty crucial for the
behavior of Seam JMS (specifically, the CDI events as JMS Messages
feature). I already have an issue open, but no update yet.
John
15 years
Seam 3 Module pages vandalized
by Jason Porter
It came to my attention via some post on the forums that some of our module
pages have been vandalized. I've corrected the problem (rolled back to the
correct version) and locked down the pages to admin edit access only. If you
have problems editing your page please talk to Shane, Dan or myself and
we'll get you setup properly.
--
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
New hires!
by Ondřej Skutka
Hi!
After Martin Genčúr left to EDG team, we've been struggling with lack of resources. Now I want to announce that we've hired two new people to Seam QE team. Let them introduce themselves:
Martin Kouba ['marcɪn 'kouba] (mart-yin ko-bah) - taking responsibility for CDI-TCK
> "I was born and live right now in Sušice. For about eight years I try to use and understand various open source technologies. Last six years I worked as a JEE senior developer / >architect at IT Systems in České Budějovice. I heavily used several JBoss community projects such as JBoss AS, Hibernate, Seam, RichFaces, RESTEasy... and that's probably >what brings me to Red Hat. I like comics, ZX spectrum games, D&D miniatures and sometimes play basketball, tennis and squash."
Tomáš Remeš -- ['tomaːʃ 'rɛmɛʃ] (toe-mush reh-mesh) Working on Seam / Weld QA
> "I am 25 years old. I finished the studies this year and i already have some basic experience with software development in czech company using various technologies like Seam, >JSF, Spring, Wicket, Hibernate, Maven, MySQL. I like music, riding bike, playing floorball, meeting friends, travelling. I am not married yet and have no children."
Help me welcoming them and feel free to ping them on irc or write them an email (or to seam-qa-list) if you need any help from QE.
And you, new guys, good luck and a lot of bugs found!
Ondra
15 years, 1 month
Issues with testing and emma
by John D. Ament
I just noticed this morning that emma reports very low code coverage on my
code. However, when I switch the injection points from say "SomeBean" to
"SomeBeanImpl" then my code coverage sudden jumps up. I expect it to be
higher. It seems like Emma has some issues dealing with CDI proxies, or
possibly arquillian. Has anyone else noticed this?
John
15 years, 1 month
Re: [seam-dev] Following modules left to move to git-flow
by Jason Porter
The work has been completed for all modules. Thanks to George Gastaldi for
the help in completing this task!
On Mon, Jul 11, 2011 at 17:36, George Gastaldi <gegastaldi(a)gmail.com> wrote:
> All done ! Branches created !
>
>
> 2011/7/11 Jason Porter <lightguard.jp(a)gmail.com>
>
>> Excellent, thanks George.
>>
>>
>> On Mon, Jul 11, 2011 at 15:34, George Gastaldi <gegastaldi(a)gmail.com>wrote:
>>
>>> Ok, no problem on that. I´ll create the develop branches then of these
>>> projects and let you know.
>>>
>>>
>>> 2011/7/11 Jason Porter <lightguard.jp(a)gmail.com>
>>>
>>>> No, you probably do not. As neither of them are a lot of work, shall we
>>>> say I'll do the admin on github?
>>>>
>>>>
>>>> On Mon, Jul 11, 2011 at 15:28, George Gastaldi <gegastaldi(a)gmail.com>wrote:
>>>>
>>>>> Cool, wanna split up ? I think I don´t have the necessary privileges to
>>>>> change the default branch in github for these projects.
>>>>>
>>>>> 2011/7/11 Jason Porter <lightguard.jp(a)gmail.com>
>>>>>
>>>>>> Heads up to all the module leads for the following modules:
>>>>>>
>>>>>> Cron
>>>>>> JMS
>>>>>> compatibility
>>>>>> validation
>>>>>> security
>>>>>> mail
>>>>>> wicket
>>>>>> Conversation
>>>>>> config
>>>>>>
>>>>>> Myself and George will be moving the modules over to use git flow and
>>>>>> the default branch will be "develop" instead of master.
>>>>>>
>>>>>> --
>>>>>> 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
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>
>
>
--
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, 1 month
Re: [seam-dev] [seam-persistence] ManagedPersistenceContextExtension
by Mark Struberg
There are a few problems which can happen:
a.) EmtityManager#lock(java.lang.Object o, javax.persistence.LockModeType lockModeType); and others with LockType#PESSIMISTIC_*
b.) Consider you have an Entity dirty or a fresh one created with em.persist(). And now you do a non-trivial query. In order to guarantee that this new/modified entity gets evaluated properly, JPA _explicitly_ allows the EntityManager to write those values into the database. Voila, you have your open transaction! Not too many people are aware of that but yes, querying from the database can lead to a SQL INSERT or SQL UPDATE into the database! Of course, you better _not_ commit those changes immediately ;)
LieGrue,
strub
--- On Sun, 7/10/11, John D. Ament <john.d.ament(a)gmail.com> wrote:
From: John D. Ament <john.d.ament(a)gmail.com>
Subject: Re: [seam-dev] [seam-persistence] ManagedPersistenceContextExtension
To: "Mark Struberg" <struberg(a)yahoo.de>
Cc: "Stuart Douglas" <stuart.w.douglas(a)gmail.com>, seam-dev(a)lists.jboss.org
Date: Sunday, July 10, 2011, 11:29 PM
But is the select for update done inside the entitymanager object or a query instance? I don't think EntityManager.find(Class,Id) does any type of hold on the object found.
John
On Sun, Jul 10, 2011 at 7:15 PM, Mark Struberg <struberg(a)yahoo.de> wrote:
Stu, whenever you do a "select for update" or any manual locking, you will end up with an EntityManager which cannot be transfered to another node. Even if hibernate marks it's EntityManager Serializable, it just isn't if I didn't miss something!
LieGrue,
strub
--- On Sun, 7/10/11, Stuart Douglas <stuart.w.douglas(a)gmail.com> wrote:
> From: Stuart Douglas <stuart.w.douglas(a)gmail.com>
> Subject: Re: [seam-dev] [seam-persistence] ManagedPersistenceContextExtension
> To: "Mark Struberg" <struberg(a)yahoo.de>
> Cc: seam-dev(a)lists.jboss.org
> Date: Sunday, July 10, 2011, 11:07 PM
>
> On 11/07/2011, at 4:07 AM, Mark Struberg wrote:
>
> > Hi folks!
> >
> > While reviewing an OWB bug report, 2 questions came
> up:
> >
> > a.) EnvironmentUtils#isEEEnvironment() relies on the
> absence of 'javax.ejb.Stateless' to decide if a
> PersitenceUnit gets injected or if you need to do it
> yourself. I think this is an unrelieable assumption. E.g.
> there are a few Extensions which emulate Stateless Session
> beans via a CDI Extension by morphing them into
> @ApplicationScoped.
>
> This is not ideal, but I don't think there is really any
> portable way to detect if the environment is an EE
> environment or not. I was originally planning to add a
> method for configuring this, but it appears I did not get
> around to it.
>
> >
> > b.) in
> ManagedPersistenceContextExtension#registerManagedPersistenceContext
> you register the bean for the EntityManager as
> passivationCapable. This is never _never_ NEVER true. The
> EntityManager is not Serializable! There is imo no way to
> have an EntityManager in a bean scoped other than
> @RequestScoped or shorter (e.g. @TransactionalScoped). Any
> other trick is not working in a portable way. This is mainly
> caused by JPA still supporting pessimistic locking (_real_
> locks in the database) as first class citizens.
> >
>
> Without this it is not possible to have a conversation
> scoped entity manager. The hibernate EntityManager is in
> fact Serializable. Locks should not be a problem as long as
> you do not attempt to serialise the EM in the middle of a
> transaction.
>
> Stuart
>
>
> > But I'd be happy if anyone could enlighten me and tell
> us how it works ;)
> >
> > LieGrue,
> > strub
> > _______________________________________________
> > seam-dev mailing list
> > seam-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/seam-dev
>
>
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
15 years, 1 month
[seam-persistence] ManagedPersistenceContextExtension
by Mark Struberg
Hi folks!
While reviewing an OWB bug report, 2 questions came up:
a.) EnvironmentUtils#isEEEnvironment() relies on the absence of 'javax.ejb.Stateless' to decide if a PersitenceUnit gets injected or if you need to do it yourself. I think this is an unrelieable assumption. E.g. there are a few Extensions which emulate Stateless Session beans via a CDI Extension by morphing them into @ApplicationScoped.
b.) in ManagedPersistenceContextExtension#registerManagedPersistenceContext you register the bean for the EntityManager as passivationCapable. This is never _never_ NEVER true. The EntityManager is not Serializable! There is imo no way to have an EntityManager in a bean scoped other than @RequestScoped or shorter (e.g. @TransactionalScoped). Any other trick is not working in a portable way. This is mainly caused by JPA still supporting pessimistic locking (_real_ locks in the database) as first class citizens.
But I'd be happy if anyone could enlighten me and tell us how it works ;)
LieGrue,
strub
15 years, 1 month
