Nabble - seam-dev

JProfiler 6 license

2009-11-04T17:29:00Z

Hey guys,

Do we have a license key for JProfiler 6? The key I have is only for
JProfiler 5, and of course it doesn't work with v6. Please respond to
me off-list if you can help out.

Shane
_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Seam and SSO

2009-11-01T03:05:20Z

Please direct your question to the user forum at http://seamframework.org
.

Thanks!

On 26 Oct 2009, at 01:02, cllai wrote:

>
> hi, i working on sso and seam too. can u pls send me example to how to
> integrate jboss sso and seam?
>
>
> Raphael Duarte Paiva wrote:
>>
>> I wrote my own solution to SSO integration with seam and Jboss AS.
>> Its a pretty Simple LoginModule for Jboss AS, who calls a session
>> bean
>> that
>> query the user from the database and store its principal into the
>> container
>> itself.
>>
>> Then I wrote a seam component that is called every time a user
>> enters a
>> module (a service of the major project). It just retrieve the
>> principal
>> from
>> the container (using jacc) and authenticate it in seam (populating
>> the
>> Identity component).
>>
>> If you need more details, feel free to contact me.
>>
>> On Thu, Sep 24, 2009 at 22:14, xin wu <alartin@...> wrote:
>>
>>> Hi all,
>>>
>>> I think the SSO is a big issue when we suggest clients to adopt
>>> Seam. I
>>> try
>>> the CAS SSO and rewrite Authenticator and Pages classes
>>> according to CAS wiki but it does not work properly. Even I can
>>> use SSO
>>> in
>>> two Seam applications, the seam application does not work same as
>>> before. The reason seems that Seam can not handle
>>> navigation(pages.xml/x.page.xml) correctly any more. For example,
>>> when I
>>> login a simple CRUD Seam application and create a new entity,
>>> after I
>>> click
>>> save button, the entity is created successfully but I am not
>>> navigated to
>>> the Entity.xhtml and stayed at the same edit page. When I click list
>>> page,
>>> and click View/Edit link of the entity, the entity's information
>>> is not
>>> shown at the corresponding fields. They are all empty.
>>> In fact, the CAS SSO adds some filters in web.xml. Does them affect
>>> Seam's
>>> navigation? After I remove CAS SSO configuration, all works fine.
>>> SSO is a common requirement of many clients. Can somebody help to
>>> figure
>>> out what happened? Thanks.
>>>
>>>
>>> --
>>>
>>> Sean Wu
>>> JBoss Solution Architect
>>> RedHat Service Center, P.R.China
>>> Email: seanwu@...
>>> Mobile: 13911868610
>>>
>>> _______________________________________________
>>> seam-dev mailing list
>>> seam-dev@...
>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>
>>>
>>
>>
>> --
>> Abraços
>> Raphael Duarte Paiva
>> Graduando em Ciência da Computação
>>
>> "For millions of years, mankind lived just like the animals. Then
>> something
>> happened which unleashed the power of our imagination. We learned
>> to talk
>> [...]" - Stephen Hawking, 1993
>>
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev@...
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Seam-and-SSO-tp25692711p26053510.html
> Sent from the seam-dev mailing list archive at Nabble.com.
>
>
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Seam and SSO

2009-10-25T18:02:01Z

hi, i working on sso and seam too. can u pls send me example to how to
integrate jboss sso and seam?

Raphael Duarte Paiva wrote:

>
> I wrote my own solution to SSO integration with seam and Jboss AS.
> Its a pretty Simple LoginModule for Jboss AS, who calls a session bean
> that
> query the user from the database and store its principal into the
> container
> itself.
>
> Then I wrote a seam component that is called every time a user enters a
> module (a service of the major project). It just retrieve the principal
> from
> the container (using jacc) and authenticate it in seam (populating the
> Identity component).
>
> If you need more details, feel free to contact me.
>
> On Thu, Sep 24, 2009 at 22:14, xin wu <alartin@...> wrote:
>
>> Hi all,
>>
>> I think the SSO is a big issue when we suggest clients to adopt Seam. I
>> try
>> the CAS SSO and rewrite Authenticator and Pages classes
>> according to CAS wiki but it does not work properly. Even I can use SSO
>> in
>> two Seam applications, the seam application does not work same as
>> before. The reason seems that Seam can not handle
>> navigation(pages.xml/x.page.xml) correctly any more. For example, when I
>> login a simple CRUD Seam application and create a new entity, after I
>> click
>> save button, the entity is created successfully but I am not navigated to
>> the Entity.xhtml and stayed at the same edit page. When I click list
>> page,
>> and click View/Edit link of the entity, the entity's information is not
>> shown at the corresponding fields. They are all empty.
>> In fact, the CAS SSO adds some filters in web.xml. Does them affect
>> Seam's
>> navigation? After I remove CAS SSO configuration, all works fine.
>> SSO is a common requirement of many clients. Can somebody help to figure
>> out what happened? Thanks.
>>
>>
>> --
>>
>> Sean Wu
>> JBoss Solution Architect
>> RedHat Service Center, P.R.China
>> Email: seanwu@...
>> Mobile: 13911868610
>>
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev@...
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>
>>
>
>
> --
> Abraços
> Raphael Duarte Paiva
> Graduando em Ciência da Computação
>
> "For millions of years, mankind lived just like the animals. Then
> something
> happened which unleashed the power of our imagination. We learned to talk
> [...]" - Stephen Hawking, 1993
>
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev
>
>

--
View this message in context: http://www.nabble.com/Seam-and-SSO-tp25692711p26053510.html
Sent from the seam-dev mailing list archive at Nabble.com.

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: [weld-dev] Weld 1.0.0 CR1 out

2009-10-15T17:31:53Z

Awesome! Congratulations, Pete, and all!

Sent from my iPhone

On Oct 15, 2009, at 5:26 PM, Pete Muir <pmuir@...> wrote:

> All,
>
> http://in.relation.to/Bloggers/Weld100CR1Available
>
> And I just want to say thanks to everyone who has participated in this
> - although I (tried to) call out the major contributors on the blog,
> there are many many more people who have tried out the software,
> blogged or talked about it, given us beer when we were low etc. So,
> thanks again, and onward to CR2 :-)
>
> Pete
> _______________________________________________
> weld-dev mailing list
> weld-dev@...
> https://lists.jboss.org/mailman/listinfo/weld-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Weld 1.0.0 CR1 out

2009-10-15T14:26:03Z

All,

http://in.relation.to/Bloggers/Weld100CR1Available

And I just want to say thanks to everyone who has participated in this
- although I (tried to) call out the major contributors on the blog,
there are many many more people who have tried out the software,
blogged or talked about it, given us beer when we were low etc. So,
thanks again, and onward to CR2 :-)

Pete
_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Seam and SSO

2009-10-02T06:50:02Z

Please use the forums for such questions.

Thanks!

On 25 Sep 2009, at 03:14, xin wu wrote:

> Hi all,
>
> I think the SSO is a big issue when we suggest clients to adopt
> Seam. I try the CAS SSO and rewrite Authenticator and Pages classes
> according to CAS wiki but it does not work properly. Even I can use
> SSO in two Seam applications, the seam application does not work
> same as
> before. The reason seems that Seam can not handle navigation
> (pages.xml/x.page.xml) correctly any more. For example, when I login
> a simple CRUD Seam application and create a new entity, after I
> click save button, the entity is created successfully but I am not
> navigated to the Entity.xhtml and stayed at the same edit page. When
> I click list page, and click View/Edit link of the entity, the
> entity's information is not shown at the corresponding fields. They
> are all empty.
> In fact, the CAS SSO adds some filters in web.xml. Does them affect
> Seam's navigation? After I remove CAS SSO configuration, all works
> fine.
> SSO is a common requirement of many clients. Can somebody help to
> figure out what happened? Thanks.
>
>
> --
>
> Sean Wu
> JBoss Solution Architect
> RedHat Service Center, P.R.China
> Email: seanwu@...
> Mobile: 13911868610
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Seam and SSO

2009-10-01T07:09:02Z

I wrote my own solution to SSO integration with seam and Jboss AS.

Its a pretty Simple LoginModule for Jboss AS, who calls a session bean that query the user from the database and store its principal into the container itself.

Then I wrote a seam component that is called every time a user enters a module (a service of the major project). It just retrieve the principal from the container (using jacc) and authenticate it in seam (populating the Identity component).

If you need more details, feel free to contact me.

On Thu, Sep 24, 2009 at 22:14, xin wu <alartin@...> wrote:

Hi all,

I think the SSO is a big issue when we suggest clients to adopt Seam. I try the CAS SSO and rewrite Authenticator and Pages classes
according to CAS wiki but it does not work properly. Even I can use SSO in two Seam applications, the seam application does not work same as
before. The reason seems that Seam can not handle navigation(pages.xml/x.page.xml) correctly any more. For example, when I login a simple CRUD Seam application and create a new entity, after I click save button, the entity is created successfully but I am not navigated to the Entity.xhtml and stayed at the same edit page. When I click list page, and click View/Edit link of the entity, the entity's information is not shown at the corresponding fields. They are all empty.
In fact, the CAS SSO adds some filters in web.xml. Does them affect Seam's navigation? After I remove CAS SSO configuration, all works fine.
SSO is a common requirement of many clients. Can somebody help to figure out what happened? Thanks.

--

Sean Wu
JBoss Solution Architect
RedHat Service Center, P.R.China
Email: seanwu@...
Mobile: 13911868610

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

--
Abraços
Raphael Duarte Paiva
Graduando em Ciência da Computação

"For millions of years, mankind lived just like the animals. Then something happened which unleashed the power of our imagination. We learned to talk [...]" - Stephen Hawking, 1993

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Seam and SSO

2009-09-24T18:14:14Z

Hi all,

I think the SSO is a big issue when we suggest clients to adopt Seam. I try the CAS SSO and rewrite Authenticator and Pages classes
according to CAS wiki but it does not work properly. Even I can use SSO in two Seam applications, the seam application does not work same as
before. The reason seems that Seam can not handle navigation(pages.xml/x.page.xml) correctly any more. For example, when I login a simple CRUD Seam application and create a new entity, after I click save button, the entity is created successfully but I am not navigated to the Entity.xhtml and stayed at the same edit page. When I click list page, and click View/Edit link of the entity, the entity's information is not shown at the corresponding fields. They are all empty.
In fact, the CAS SSO adds some filters in web.xml. Does them affect Seam's navigation? After I remove CAS SSO configuration, all works fine.
SSO is a common requirement of many clients. Can somebody help to figure out what happened? Thanks.

--

Sean Wu
JBoss Solution Architect
RedHat Service Center, P.R.China
Email: seanwu@...
Mobile: 13911868610

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: About Seam 2.2.0 and Drools 5

2009-09-15T20:47:46Z

Ingo Jobling wrote:
> Ha ha it just depends on the many meanings of support you take, which means
> so many wasted hours and maybe even failed projects ;-)
>
Why so negative ? :)
What exactly are you looking for which does not work for you?

Thanks.

> ----- Original Message -----
> From: "Pete Muir" <pmuir@...>
> To: "Diego de Oliveira Martins" <dioliver1988@...>
> Cc: <seam-dev@...>
> Sent: Tuesday, September 01, 2009 10:32 AM
> Subject: Re: [seam-dev] About Seam 2.2.0 and Drools 5
>
>
> Hi Diego,
>
> Seam 2.2 allows you to use Drools 5. With Seam 3, we will introduce
> additional features that are new in Drools 5.
>
> So basically, it just depends on which of the many meanings of support
> you take ;-)
>
> On 26 Aug 2009, at 21:29, Diego de Oliveira Martins wrote:
>
>
>> Hello,
>>
>> I got a doubt about the support to Drools 5 announced on Seam 2.2.0
>> release notes (and posts on blogs all over the internet, like the In
>> Relation To...).
>>
>> It says:
>>
>> "We've also moved our Drools support from Drools 4 to Drools 5"
>>
>> Maybe I'm misunderstanding exactly what Seam team intended to say,
>> but I got confused.
>>
>> In SVN, there's another branch, called Seam_2_2_Drools5, and there's
>> a lot of commits trying to integrate Seam and the Drools 5 API. On
>> the otherhand, the branch Seam_2_2 really doesn't seems to support
>> this API (KnowledgeBase and other new stuff).
>>
>> It looks like I still have to use the old drools 4 api to make Seam
>> 2.2.0 work with Drools.
>>
>> Am I wrong?
>>
>> Thanks,
>>
>> Diego
>>
>> --
>> Diego Martins
>> Graduando do Departamento de Ciência da Computação
>> Universidade Federal do Rio de Janeiro
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev@...
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>
>
>
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev
>
>
> --------------------------------------------------------------------------------
>
>
>
> Internal Virus Database is out of date.
> Checked by AVG - www.avg.com
> Version: 8.5.392 / Virus Database: 270.13.35/2270 - Release Date: 07/29/09
> 06:12:00
>
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev
>
>

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: About Seam 2.2.0 and Drools 5

2009-09-14T21:14:00Z

Ha ha it just depends on the many meanings of support you take, which means
so many wasted hours and maybe even failed projects ;-)

----- Original Message -----
From: "Pete Muir" <pmuir@...>
To: "Diego de Oliveira Martins" <dioliver1988@...>
Cc: <seam-dev@...>
Sent: Tuesday, September 01, 2009 10:32 AM
Subject: Re: [seam-dev] About Seam 2.2.0 and Drools 5

Hi Diego,

Seam 2.2 allows you to use Drools 5. With Seam 3, we will introduce
additional features that are new in Drools 5.

So basically, it just depends on which of the many meanings of support
you take ;-)

On 26 Aug 2009, at 21:29, Diego de Oliveira Martins wrote:

> Hello,
>
> I got a doubt about the support to Drools 5 announced on Seam 2.2.0
> release notes (and posts on blogs all over the internet, like the In
> Relation To...).
>
> It says:
>
> "We've also moved our Drools support from Drools 4 to Drools 5"
>
> Maybe I'm misunderstanding exactly what Seam team intended to say,
> but I got confused.
>
> In SVN, there's another branch, called Seam_2_2_Drools5, and there's
> a lot of commits trying to integrate Seam and the Drools 5 API. On
> the otherhand, the branch Seam_2_2 really doesn't seems to support
> this API (KnowledgeBase and other new stuff).
>
> It looks like I still have to use the old drools 4 api to make Seam
> 2.2.0 work with Drools.
>
> Am I wrong?
>
> Thanks,
>
> Diego
>
> --
> Diego Martins
> Graduando do Departamento de Ciência da Computação
> Universidade Federal do Rio de Janeiro
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

--------------------------------------------------------------------------------

Internal Virus Database is out of date.
Checked by AVG - www.avg.com
Version: 8.5.392 / Virus Database: 270.13.35/2270 - Release Date: 07/29/09
06:12:00

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Expansion of a previous benchmark

2009-09-14T11:00:56Z

http://ptrthomas.wordpress.com/2009/09/14/perfbench-update-tapestry-5-and-grails/
_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Implementing REQUIRES_NEW for seam transaction management

2009-09-02T18:48:56Z

I have attached a new patch to the issue that contains some integration
tests and prevents the propagation of the seam managed persistence
context into the new transaction.

Stuart

On Thu, 2009-09-03 at 06:55 +1000, Stuart Douglas wrote:

>
> It is pluggable, you create a component that extends
> SeamTransactionManager and install it over the top of the default
> implementation, or if the TransactionManager is in jndi but in a
> different location then that can be configured through components.xml
> as well.
>
> I'm not going to write app server specific components and
> documentation until after I have got the rest of the patch complete.
>
>
> Stuart
>
>
> -----Original Message-----
> From: Pete Muir [mailto:pmuir@...]
> Sent: Thu 3/09/2009 12:58 AM
> To: Denis Forveille
> Cc: Stuart Douglas; seam-dev@...
> Subject: Re: [seam-dev] Implementing REQUIRES_NEW for seam transaction
> management
>
>
> On 2 Sep 2009, at 09:44, Denis Forveille wrote:
>
> > Stuart,
> >
> > I don't agree with the proposed patch as it assume that the
> > "TransactionManager" is exposed and accessible to the applications
> and
> > is bound in JNDI (you assume "java:/TransactionManager" as the
> > default name)
> >
> > As said before, this is not part of the J2EE contract for the AS to
> > expose their TransactionManager and some do not, like WebSphere.
>
> This is correct, and has not been fixed in Java EE.
>
> If you really need a portable way to get the TM, you would need to
> make this a pluggable service provider.
>
> >
> > To my knowledge, there is no "standard" way to get this object in
> J2EE
> > and every AS may have their way, some may not exposes it at all.
> >
> > If you want to know what WebSphere officially exposes to users
> > concerning transactions management, , you should read this article
> in
> > the WebSphere information center :
> >
> http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.express.doc/info/exp/ae/cjta_extjta.html
> >
> > One "easy" solution could be to declare that this functionality is
> > only available to AS that expose their TransactionManager via JNDI,
> > but thsi is not very elegant for a framework like Seam to do that
> > IMHO.
> >
> > Denis
> >
> >
> >
> > 2009/9/2 Stuart Douglas <stuart@...>:
> >> I have attached the first version of the REQUIRES_NEW patch to
> >> JBSEAM-4391.
> >>
> >>
> >> It seems to work ok, however I have not yet created the tests for
> it,
> >> and at the moment I have only supplied a simple transaction
> manager
> >> that
> >> looks up the JTA TransactionManager from JNDI.
> >>
> >> I do however have a few questions about the best way to handle
> >> persistence context propagation. The SMPC does not properly support
> >> REQUIRES_NEW on EJB's (you should use @PersistenceContext
> instead),
> >> and
> >> it also will not properly support REQUIRES_NEW on seam components.
> >>
> >> This is a much bigger problem for seam components, as there is not
> >> direct equivalent of @PersistenceContext. I have a few solutions in
> >> mind:
> >>
> >> 1) When suspending the transaction pull all persistence contexts
> >> out of
> >> all scopes and store them in a map, when the original transaction
> >> resumes put them back (there is more to it that this, like do we
> >> flush
> >> the PC's that are created in the new transaction).
> >>
> >> 2) Place some kind of warning in the log whenever a user accesses a
> >> persistence context that they shouldn't. This would probably
> require
> >> hacking up the ManagedPersistenceContext class, and would not
> really
> >> help the use get hold of an EntityManager they are allowed to use.
> >>
> >> 3) Do nothing, but document this in the manual. The user would
> have
> >> to
> >> create their own entity managers by getting hold of an
> >> EntityManagerFactory.
> >>
> >>
> >> Comments?
> >>
> >> Stuart
> >>
> >>
> >>
> >>
> >>
> >>
> >> On Mon, 2009-08-31 at 14:36 -0400, Dan Allen wrote:
> >>> On Wed, Aug 26, 2009 at 8:55 PM, Stuart Douglas
> >>> <stuart@...> wrote:
> >>> I would like to implement REQUIRES_NEW as a transaction
> type
> >>> for the
> >>> @Transactional annotation. My basic plan is:
> >>>
> >>> - Create a TransactionManager component that can be
> >>> installed
> >>> into
> >>> components.xml, and give the option to configure the JNDI
> >>> location of
> >>> the JTA TransactionManager.
> >>>
> >>> - modify the Work.workInTransaction method to check if the
> >>> existing
> >>> transaction need to be suspended, as if so use the
> >>> TransactionManager
> >>> component to suspend and resume the transaction.
> >>>
> >>> I can't help thinking that there is some problem with this
> >>> approach,
> >>> otherwise someone else would have already done it.
> >>>
> >>> Try it, create some tests and if it works, prove it.
> >>>
> >>>
> >>>
> >>> I also know that TransactionManager is not supposed to be
> >>> used
> >>> by the
> >>> application, does anyone know if this will cause problems?
> >>>
> >>> Spring has been doing this for a long time. It's of course app
> >>> server
> >>> dependent, but the general feeling is that using it is so common
> to
> >>> consider it a public API.
> >>>
> >>>
> >>>
> >>> I would also like to implement the ability to control seam
> >>> global
> >>> transactions based on a flag in pages.xml, so they can be
> >>> disabled for
> >>> specific views. Would anyone have any objections to this?
> >>>
> >>> I've always been in favor of this idea.
> >>>
> >>> -Dan
> >>>
> >>>
> >>> --
> >>> Dan Allen
> >>> Senior Software Engineer, Red Hat | Author of Seam in Action
> >>> Registered Linux User #231597
> >>>
> >>> http://mojavelinux.com
> >>> http://mojavelinux.com/seaminaction
> >>> http://in.relation.to/Bloggers/Dan
> >> _______________________________________________
> >> seam-dev mailing list
> >> seam-dev@...
> >> https://lists.jboss.org/mailman/listinfo/seam-dev
> >>
> >
> > _______________________________________________
> > seam-dev mailing list
> > seam-dev@...
> > https://lists.jboss.org/mailman/listinfo/seam-dev
>
>
>
>
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Implementing REQUIRES_NEW for seam transaction management

2009-09-02T13:55:55Z

RE: [seam-dev] Implementing REQUIRES_NEW for seam transaction management

It is pluggable, you create a component that extends SeamTransactionManager and install it over the top of the default implementation, or if the TransactionManager is in jndi but in a different location then that can be configured through components.xml as well.

I'm not going to write app server specific components and documentation until after I have got the rest of the patch complete.

Stuart

-----Original Message-----
From: Pete Muir [pmuir@...]
Sent: Thu 3/09/2009 12:58 AM
To: Denis Forveille
Cc: Stuart Douglas; seam-dev@...
Subject: Re: [seam-dev] Implementing REQUIRES_NEW for seam transaction management

On 2 Sep 2009, at 09:44, Denis Forveille wrote:

> Stuart,
>
> I don't agree with the proposed patch as it assume that the
> "TransactionManager" is exposed and accessible to the applications and
> is bound in JNDI (you assume "java:/TransactionManager" as the
> default name)
>
> As said before, this is not part of the J2EE contract for the AS to
> expose their TransactionManager and some do not, like WebSphere.

This is correct, and has not been fixed in Java EE.

If you really need a portable way to get the TM, you would need to
make this a pluggable service provider.

>
> To my knowledge, there is no "standard" way to get this object in J2EE
> and every AS may have their way, some may not exposes it at all.
>
> If you want to know what WebSphere officially exposes to users
> concerning transactions management, , you should read this article in
> the WebSphere information center :
> http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.express.doc/info/exp/ae/cjta_extjta.html
>
> One "easy" solution could be to declare that this functionality is
> only available to AS that expose their TransactionManager via JNDI,
> but thsi is not very elegant for a framework like Seam to do that
> IMHO.
>
> Denis
>
>
>
> 2009/9/2 Stuart Douglas <stuart@...>:
>> I have attached the first version of the REQUIRES_NEW patch to
>> JBSEAM-4391.
>>
>>
>> It seems to work ok, however I have not yet created the tests for it,
>> and at the moment I have only supplied a simple transaction manager
>> that
>> looks up the JTA TransactionManager from JNDI.
>>
>> I do however have a few questions about the best way to handle
>> persistence context propagation. The SMPC does not properly support
>> REQUIRES_NEW on EJB's (you should use @PersistenceContext instead),
>> and
>> it also will not properly support REQUIRES_NEW on seam components.
>>
>> This is a much bigger problem for seam components, as there is not
>> direct equivalent of @PersistenceContext. I have a few solutions in
>> mind:
>>
>> 1) When suspending the transaction pull all persistence contexts
>> out of
>> all scopes and store them in a map, when the original transaction
>> resumes put them back (there is more to it that this, like do we
>> flush
>> the PC's that are created in the new transaction).
>>
>> 2) Place some kind of warning in the log whenever a user accesses a
>> persistence context that they shouldn't. This would probably require
>> hacking up the ManagedPersistenceContext class, and would not really
>> help the use get hold of an EntityManager they are allowed to use.
>>
>> 3) Do nothing, but document this in the manual. The user would have
>> to
>> create their own entity managers by getting hold of an
>> EntityManagerFactory.
>>
>>
>> Comments?
>>
>> Stuart
>>
>>
>>
>>
>>
>>
>> On Mon, 2009-08-31 at 14:36 -0400, Dan Allen wrote:
>>> On Wed, Aug 26, 2009 at 8:55 PM, Stuart Douglas
>>> <stuart@...> wrote:
>>>         I would like to implement REQUIRES_NEW as a transaction type
>>>         for the
>>>         @Transactional annotation. My basic plan is:
>>>
>>>         - Create a TransactionManager component that can be
>>> installed
>>>         into
>>>         components.xml, and give the option to configure the JNDI
>>>         location of
>>>         the JTA TransactionManager.
>>>
>>>         - modify the Work.workInTransaction method to check if the
>>>         existing
>>>         transaction need to be suspended, as if so use the
>>>         TransactionManager
>>>         component to suspend and resume the transaction.
>>>
>>>         I can't help thinking that there is some problem with this
>>>         approach,
>>>         otherwise someone else would have already done it.
>>>
>>> Try it, create some tests and if it works, prove it.
>>>
>>>
>>>
>>>         I also know that TransactionManager is not supposed to be
>>> used
>>>         by the
>>>         application, does anyone know if this will cause problems?
>>>
>>> Spring has been doing this for a long time. It's of course app
>>> server
>>> dependent, but the general feeling is that using it is so common to
>>> consider it a public API.
>>>
>>>
>>>
>>>         I would also like to implement the ability to control seam
>>>         global
>>>         transactions based on a flag in pages.xml, so they can be
>>>         disabled for
>>>         specific views. Would anyone have any objections to this?
>>>
>>> I've always been in favor of this idea.
>>>
>>> -Dan
>>>
>>>
>>> --
>>> Dan Allen
>>> Senior Software Engineer, Red Hat | Author of Seam in Action
>>> Registered Linux User #231597
>>>
>>> http://mojavelinux.com
>>> http://mojavelinux.com/seaminaction
>>> http://in.relation.to/Bloggers/Dan
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev@...
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>
>
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Implementing REQUIRES_NEW for seam transaction management

2009-09-02T07:58:46Z

On 2 Sep 2009, at 09:44, Denis Forveille wrote:

> Stuart,
>
> I don't agree with the proposed patch as it assume that the
> "TransactionManager" is exposed and accessible to the applications and
> is bound in JNDI (you assume "java:/TransactionManager" as the
> default name)
>
> As said before, this is not part of the J2EE contract for the AS to
> expose their TransactionManager and some do not, like WebSphere.

This is correct, and has not been fixed in Java EE.

If you really need a portable way to get the TM, you would need to
make this a pluggable service provider.

>
> To my knowledge, there is no "standard" way to get this object in J2EE
> and every AS may have their way, some may not exposes it at all.
>
> If you want to know what WebSphere officially exposes to users
> concerning transactions management, , you should read this article in
> the WebSphere information center :
> http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.express.doc/info/exp/ae/cjta_extjta.html
>
> One "easy" solution could be to declare that this functionality is
> only available to AS that expose their TransactionManager via JNDI,
> but thsi is not very elegant for a framework like Seam to do that
> IMHO.
>
> Denis
>
>
>
> 2009/9/2 Stuart Douglas <stuart@...>:
>> I have attached the first version of the REQUIRES_NEW patch to
>> JBSEAM-4391.
>>
>>
>> It seems to work ok, however I have not yet created the tests for it,
>> and at the moment I have only supplied a simple transaction manager
>> that
>> looks up the JTA TransactionManager from JNDI.
>>
>> I do however have a few questions about the best way to handle
>> persistence context propagation. The SMPC does not properly support
>> REQUIRES_NEW on EJB's (you should use @PersistenceContext instead),
>> and
>> it also will not properly support REQUIRES_NEW on seam components.
>>
>> This is a much bigger problem for seam components, as there is not
>> direct equivalent of @PersistenceContext. I have a few solutions in
>> mind:
>>
>> 1) When suspending the transaction pull all persistence contexts
>> out of
>> all scopes and store them in a map, when the original transaction
>> resumes put them back (there is more to it that this, like do we
>> flush
>> the PC's that are created in the new transaction).
>>
>> 2) Place some kind of warning in the log whenever a user accesses a
>> persistence context that they shouldn't. This would probably require
>> hacking up the ManagedPersistenceContext class, and would not really
>> help the use get hold of an EntityManager they are allowed to use.
>>
>> 3) Do nothing, but document this in the manual. The user would have
>> to
>> create their own entity managers by getting hold of an
>> EntityManagerFactory.
>>
>>
>> Comments?
>>
>> Stuart
>>
>>
>>
>>
>>
>>
>> On Mon, 2009-08-31 at 14:36 -0400, Dan Allen wrote:
>>> On Wed, Aug 26, 2009 at 8:55 PM, Stuart Douglas
>>> <stuart@...> wrote:
>>> I would like to implement REQUIRES_NEW as a transaction type
>>> for the
>>> @Transactional annotation. My basic plan is:
>>>
>>> - Create a TransactionManager component that can be
>>> installed
>>> into
>>> components.xml, and give the option to configure the JNDI
>>> location of
>>> the JTA TransactionManager.
>>>
>>> - modify the Work.workInTransaction method to check if the
>>> existing
>>> transaction need to be suspended, as if so use the
>>> TransactionManager
>>> component to suspend and resume the transaction.
>>>
>>> I can't help thinking that there is some problem with this
>>> approach,
>>> otherwise someone else would have already done it.
>>>
>>> Try it, create some tests and if it works, prove it.
>>>
>>>
>>>
>>> I also know that TransactionManager is not supposed to be
>>> used
>>> by the
>>> application, does anyone know if this will cause problems?
>>>
>>> Spring has been doing this for a long time. It's of course app
>>> server
>>> dependent, but the general feeling is that using it is so common to
>>> consider it a public API.
>>>
>>>
>>>
>>> I would also like to implement the ability to control seam
>>> global
>>> transactions based on a flag in pages.xml, so they can be
>>> disabled for
>>> specific views. Would anyone have any objections to this?
>>>
>>> I've always been in favor of this idea.
>>>
>>> -Dan
>>>
>>>
>>> --
>>> Dan Allen
>>> Senior Software Engineer, Red Hat | Author of Seam in Action
>>> Registered Linux User #231597
>>>
>>> http://mojavelinux.com
>>> http://mojavelinux.com/seaminaction
>>> http://in.relation.to/Bloggers/Dan
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev@...
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>
>
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Implementing REQUIRES_NEW for seam transaction management

2009-09-02T07:44:34Z

Stuart,

I don't agree with the proposed patch as it assume that the
"TransactionManager" is exposed and accessible to the applications and
is bound in JNDI (you assume "java:/TransactionManager" as the
default name)

As said before, this is not part of the J2EE contract for the AS to
expose their TransactionManager and some do not, like WebSphere.

To my knowledge, there is no "standard" way to get this object in J2EE
and every AS may have their way, some may not exposes it at all.

If you want to know what WebSphere officially exposes to users
concerning transactions management, , you should read this article in
the WebSphere information center :
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.express.doc/info/exp/ae/cjta_extjta.html

One "easy" solution could be to declare that this functionality is
only available to AS that expose their TransactionManager via JNDI,
but thsi is not very elegant for a framework like Seam to do that
IMHO.

Denis

2009/9/2 Stuart Douglas <stuart@...>:

> I have attached the first version of the REQUIRES_NEW patch to
> JBSEAM-4391.
>
>
> It seems to work ok, however I have not yet created the tests for it,
> and at the moment I have only supplied a simple transaction manager that
> looks up the JTA TransactionManager from JNDI.
>
> I do however have a few questions about the best way to handle
> persistence context propagation. The SMPC does not properly support
> REQUIRES_NEW on EJB's (you should use @PersistenceContext instead), and
> it also will not properly support REQUIRES_NEW on seam components.
>
> This is a much bigger problem for seam components, as there is not
> direct equivalent of @PersistenceContext. I have a few solutions in
> mind:
>
> 1) When suspending the transaction pull all persistence contexts out of
> all scopes and store them in a map, when the original transaction
> resumes put them back (there is more to it that this, like do we flush
> the PC's that are created in the new transaction).
>
> 2) Place some kind of warning in the log whenever a user accesses a
> persistence context that they shouldn't. This would probably require
> hacking up the ManagedPersistenceContext class, and would not really
> help the use get hold of an EntityManager they are allowed to use.
>
> 3) Do nothing, but document this in the manual. The user would have to
> create their own entity managers by getting hold of an
> EntityManagerFactory.
>
>
> Comments?
>
> Stuart
>
>
>
>
>
>
> On Mon, 2009-08-31 at 14:36 -0400, Dan Allen wrote:
>> On Wed, Aug 26, 2009 at 8:55 PM, Stuart Douglas
>> <stuart@...> wrote:
>> I would like to implement REQUIRES_NEW as a transaction type
>> for the
>> @Transactional annotation. My basic plan is:
>>
>> - Create a TransactionManager component that can be installed
>> into
>> components.xml, and give the option to configure the JNDI
>> location of
>> the JTA TransactionManager.
>>
>> - modify the Work.workInTransaction method to check if the
>> existing
>> transaction need to be suspended, as if so use the
>> TransactionManager
>> component to suspend and resume the transaction.
>>
>> I can't help thinking that there is some problem with this
>> approach,
>> otherwise someone else would have already done it.
>>
>> Try it, create some tests and if it works, prove it.
>>
>>
>>
>> I also know that TransactionManager is not supposed to be used
>> by the
>> application, does anyone know if this will cause problems?
>>
>> Spring has been doing this for a long time. It's of course app server
>> dependent, but the general feeling is that using it is so common to
>> consider it a public API.
>>
>>
>>
>> I would also like to implement the ability to control seam
>> global
>> transactions based on a flag in pages.xml, so they can be
>> disabled for
>> specific views. Would anyone have any objections to this?
>>
>> I've always been in favor of this idea.
>>
>> -Dan
>>
>>
>> --
>> Dan Allen
>> Senior Software Engineer, Red Hat | Author of Seam in Action
>> Registered Linux User #231597
>>
>> http://mojavelinux.com
>> http://mojavelinux.com/seaminaction
>> http://in.relation.to/Bloggers/Dan
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev
>

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Maven Seam version within a Seam distribution

2009-09-02T04:58:31Z

We need somehow to distinguish enterprise editions from community
releases, if you have any idea or suggestion how to number it, please
don't hesitate to share with me ;-)

for now use the same version - 2.2.0.EAP5

/max

Snjezana Peco píše v Út 01. 09. 2009 v 20:23 +0200:

Pete Muir wrote:

On 29 Aug 2009, at 13:08, Snjezana Peco wrote:

Does that mean that the mavenized Seam Web Project wizard wouldn't work
with EAP 5.0 or we would use the 2.2.0.GA Maven Seam version?
Currently, if the user chooses Seam facet 2.2, the JBoss Maven
Integration facet offers the 2.2.0.GA version that the user can change.

Snjeza

Max Rydahl Andersen wrote:

Looking in the manifest is the correct place to look afaik.

As long as there are no Maven repo for our products we can only make
the maven integration work with .org versions.

/max

Snjezana Peco wrote:

I have tried to find Maven versions of Seam and required libraries in
order to fix https://jira.jboss.org/jira/browse/JBIDE-4813.
I have succeeded to find versions of the required libraries in
<SEAM_HOME>/build/root.pom.xml, but haven't succeeded  to find the
version of Seam (root.pom.xml contains @seam.version@).

These are replaced at build time with the current version of Seam.

I have also
tried to find the version of Seam within the jboss-seam.jar file. For
EAP 5.0, the jboss-seam.jar file contains the 2.2.0.EAP version that
isn't any Maven version.
Is it possible to find the Maven version of Seam within any Seam
distribution?

Look in build/default.build.properties

Within the EAP 5.0 distribution, this file contains 2.2.0.EAP5 which is 
not a Maven version.

Snjeza
_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev


_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Maven Seam version within a Seam distribution

2009-09-01T23:40:47Z

We need somehow to distinguish enterprise editions from community
releases, if you have any idea or suggestion how to number it, please
don't hesitate to share with me ;-)

Snjezana Peco píše v Út 01. 09. 2009 v 20:23 +0200:

> Pete Muir wrote:
> >
> > On 29 Aug 2009, at 13:08, Snjezana Peco wrote:
> >
> >> Does that mean that the mavenized Seam Web Project wizard wouldn't work
> >> with EAP 5.0 or we would use the 2.2.0.GA Maven Seam version?
> >> Currently, if the user chooses Seam facet 2.2, the JBoss Maven
> >> Integration facet offers the 2.2.0.GA version that the user can change.
> >>
> >> Snjeza
> >>
> >> Max Rydahl Andersen wrote:
> >>> Looking in the manifest is the correct place to look afaik.
> >>>
> >>> As long as there are no Maven repo for our products we can only make
> >>> the maven integration work with .org versions.
> >>>
> >>> /max
> >>>
> >>> Snjezana Peco wrote:
> >>>> I have tried to find Maven versions of Seam and required libraries in
> >>>> order to fix https://jira.jboss.org/jira/browse/JBIDE-4813.
> >>>> I have succeeded to find versions of the required libraries in
> >>>> <SEAM_HOME>/build/root.pom.xml, but haven't succeeded to find the
> >>>> version of Seam (root.pom.xml contains @seam.version@).
> >
> > These are replaced at build time with the current version of Seam.
> >
> >>>> I have also
> >>>> tried to find the version of Seam within the jboss-seam.jar file. For
> >>>> EAP 5.0, the jboss-seam.jar file contains the 2.2.0.EAP version that
> >>>> isn't any Maven version.
> >>>> Is it possible to find the Maven version of Seam within any Seam
> >>>> distribution?
> >
> > Look in build/default.build.properties
>
>
> Within the EAP 5.0 distribution, this file contains 2.2.0.EAP5 which is
> not a Maven version.
>
> Snjeza
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev

Marek Novotny
--
JBoss Seam Product Lead

Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno

Email: mnovotny@...
Office phone: +420 532 294 287, ext. 82-62 087
mobile: +420 608 509 230

------------------------------------------------------
Looking to carve out IT costs?
www.europe.redhat.com/promo/carveoutcosts/

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

signature.asc (204 bytes) Download Attachment

Re: Implementing REQUIRES_NEW for seam transaction management

2009-09-01T22:59:31Z

I have attached the first version of the REQUIRES_NEW patch to
JBSEAM-4391.

It seems to work ok, however I have not yet created the tests for it,
and at the moment I have only supplied a simple transaction manager that
looks up the JTA TransactionManager from JNDI.

I do however have a few questions about the best way to handle
persistence context propagation. The SMPC does not properly support
REQUIRES_NEW on EJB's (you should use @PersistenceContext instead), and
it also will not properly support REQUIRES_NEW on seam components.

This is a much bigger problem for seam components, as there is not
direct equivalent of @PersistenceContext. I have a few solutions in
mind:

1) When suspending the transaction pull all persistence contexts out of
all scopes and store them in a map, when the original transaction
resumes put them back (there is more to it that this, like do we flush
the PC's that are created in the new transaction).

2) Place some kind of warning in the log whenever a user accesses a
persistence context that they shouldn't. This would probably require
hacking up the ManagedPersistenceContext class, and would not really
help the use get hold of an EntityManager they are allowed to use.

3) Do nothing, but document this in the manual. The user would have to
create their own entity managers by getting hold of an
EntityManagerFactory.

Comments?

Stuart

On Mon, 2009-08-31 at 14:36 -0400, Dan Allen wrote:

> On Wed, Aug 26, 2009 at 8:55 PM, Stuart Douglas
> <stuart@...> wrote:
> I would like to implement REQUIRES_NEW as a transaction type
> for the
> @Transactional annotation. My basic plan is:
>
> - Create a TransactionManager component that can be installed
> into
> components.xml, and give the option to configure the JNDI
> location of
> the JTA TransactionManager.
>
> - modify the Work.workInTransaction method to check if the
> existing
> transaction need to be suspended, as if so use the
> TransactionManager
> component to suspend and resume the transaction.
>
> I can't help thinking that there is some problem with this
> approach,
> otherwise someone else would have already done it.
>
> Try it, create some tests and if it works, prove it.
>
>
>
> I also know that TransactionManager is not supposed to be used
> by the
> application, does anyone know if this will cause problems?
>
> Spring has been doing this for a long time. It's of course app server
> dependent, but the general feeling is that using it is so common to
> consider it a public API.
>
>
>
> I would also like to implement the ability to control seam
> global
> transactions based on a flag in pages.xml, so they can be
> disabled for
> specific views. Would anyone have any objections to this?
>
> I've always been in favor of this idea.
>
> -Dan
>
>
> --
> Dan Allen
> Senior Software Engineer, Red Hat | Author of Seam in Action
> Registered Linux User #231597
>
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
> http://in.relation.to/Bloggers/Dan

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Maven Seam version within a Seam distribution

2009-09-01T11:23:49Z

Pete Muir wrote:

>
> On 29 Aug 2009, at 13:08, Snjezana Peco wrote:
>
>> Does that mean that the mavenized Seam Web Project wizard wouldn't work
>> with EAP 5.0 or we would use the 2.2.0.GA Maven Seam version?
>> Currently, if the user chooses Seam facet 2.2, the JBoss Maven
>> Integration facet offers the 2.2.0.GA version that the user can change.
>>
>> Snjeza
>>
>> Max Rydahl Andersen wrote:
>>> Looking in the manifest is the correct place to look afaik.
>>>
>>> As long as there are no Maven repo for our products we can only make
>>> the maven integration work with .org versions.
>>>
>>> /max
>>>
>>> Snjezana Peco wrote:
>>>> I have tried to find Maven versions of Seam and required libraries in
>>>> order to fix https://jira.jboss.org/jira/browse/JBIDE-4813.
>>>> I have succeeded to find versions of the required libraries in
>>>> <SEAM_HOME>/build/root.pom.xml, but haven't succeeded to find the
>>>> version of Seam (root.pom.xml contains @seam.version@).
>
> These are replaced at build time with the current version of Seam.
>
>>>> I have also
>>>> tried to find the version of Seam within the jboss-seam.jar file. For
>>>> EAP 5.0, the jboss-seam.jar file contains the 2.2.0.EAP version that
>>>> isn't any Maven version.
>>>> Is it possible to find the Maven version of Seam within any Seam
>>>> distribution?
>
> Look in build/default.build.properties

Within the EAP 5.0 distribution, this file contains 2.2.0.EAP5 which is
not a Maven version.

Snjeza
_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Please add a link to download the "latest 2.2 unstable nightly build" on the Wiki

2009-09-01T07:39:33Z

Done - thanks!

On 31 Aug 2009, at 07:31, Denis Forveille wrote:

> Could someone that has the rights to edit the "Seam Download" page of
> the Wiki , add a link to download the "latest 2.2 unstable nightly
> build"?
> Thanks
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: About Seam 2.2.0 and Drools 5

2009-09-01T07:32:25Z

Hi Diego,

Seam 2.2 allows you to use Drools 5. With Seam 3, we will introduce
additional features that are new in Drools 5.

So basically, it just depends on which of the many meanings of support
you take ;-)

On 26 Aug 2009, at 21:29, Diego de Oliveira Martins wrote:

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Maven Seam version within a Seam distribution

2009-09-01T07:30:54Z

On 29 Aug 2009, at 13:08, Snjezana Peco wrote:

> Does that mean that the mavenized Seam Web Project wizard wouldn't
> work
> with EAP 5.0 or we would use the 2.2.0.GA Maven Seam version?
> Currently, if the user chooses Seam facet 2.2, the JBoss Maven
> Integration facet offers the 2.2.0.GA version that the user can
> change.
>
> Snjeza
>
> Max Rydahl Andersen wrote:
>> Looking in the manifest is the correct place to look afaik.
>>
>> As long as there are no Maven repo for our products we can only make
>> the maven integration work with .org versions.
>>
>> /max
>>
>> Snjezana Peco wrote:
>>> I have tried to find Maven versions of Seam and required libraries
>>> in
>>> order to fix https://jira.jboss.org/jira/browse/JBIDE-4813.
>>> I have succeeded to find versions of the required libraries in
>>> <SEAM_HOME>/build/root.pom.xml, but haven't succeeded to find the
>>> version of Seam (root.pom.xml contains @seam.version@).

These are replaced at build time with the current version of Seam.

>>> I have also
>>> tried to find the version of Seam within the jboss-seam.jar file.
>>> For
>>> EAP 5.0, the jboss-seam.jar file contains the 2.2.0.EAP version that
>>> isn't any Maven version.
>>> Is it possible to find the Maven version of Seam within any Seam
>>> distribution?

Look in build/default.build.properties
_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Reaching the seam-dev mailing list is a nightmare (Second try)

2009-08-31T15:18:44Z

On the latest e-mail that Denis sent the moderate flag was turned on - I've removed it so all future messages should go through without delay.

On 01/09/09 04:04, Dan Allen wrote:

Shane, I believe you are one of the moderators. Can you see if Denis' gmail address is listed properly. I would take care of this if I had access to the admin interface, but I don't.

-Dan

On Mon, Aug 31, 2009 at 11:33 AM, Denis Forveille <denis.forveille@...> wrote:

That will be cool but when will this be in place?

I send a message this morning and it didnt' reach the mailing
list...Just received the usual "Your message is waiting moderator
approval..." so i put you, Pete and Dan, in CC

Thx

On Wed, Aug 26, 2009 at 8:05 AM, Pete Muir <pmuir at redhat.com> wrote:

> Yes, assuming that the person who moderates the post checks accept for both
> this message, and one of "clear this members moderate flag" or "add this
> sender to the accepts filter". And, of course, this is all based on the
> address you use to post.

Excellent.

-Dan

--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://in.relation.to/Bloggers/Dan
_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev
  

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Implementing REQUIRES_NEW for seam transaction management

2009-08-31T11:57:03Z

2009/8/31 Dan Allen <dan.j.allen@...>:

> On Wed, Aug 26, 2009 at 8:55 PM, Stuart Douglas
> <stuart@...> wrote:
>>
>> I would like to implement REQUIRES_NEW as a transaction type for the
>> @Transactional annotation. My basic plan is:
>>
>> - Create a TransactionManager component that can be installed into
>> components.xml, and give the option to configure the JNDI location of
>> the JTA TransactionManager.
>>
>> - modify the Work.workInTransaction method to check if the existing
>> transaction need to be suspended, as if so use the TransactionManager
>> component to suspend and resume the transaction.
>>
>> I can't help thinking that there is some problem with this approach,
>> otherwise someone else would have already done it.
>
> Try it, create some tests and if it works, prove it.
>
>>
>> I also know that TransactionManager is not supposed to be used by the
>> application, does anyone know if this will cause problems?
>
> Spring has been doing this for a long time. It's of course app server
> dependent, but the general feeling is that using it is so common to consider
> it a public API.
>

WebSphere v6.x/v7.x does not expose its TransactionManager as it is
not part of the J2EE contract.
For hibernate, have a look at the
org.hibernate.transaction.WebSphereExtendedJTATransactionLookup class
to have an idea how they access it (in a non supported way..)
I don't know how Spring did it, maybe look at
org.springframework.transaction.jta.WebSphereUowTransactionManager

>>
>> I would also like to implement the ability to control seam global
>> transactions based on a flag in pages.xml, so they can be disabled for
>> specific views. Would anyone have any objections to this?
>
> I've always been in favor of this idea.
>
> -Dan
>
> --
> Dan Allen
> Senior Software Engineer, Red Hat | Author of Seam in Action
> Registered Linux User #231597
>
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
> http://in.relation.to/Bloggers/Dan
>
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev
>
>

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: seam-gen

2009-08-31T11:38:39Z

This list is not the proper place for this question. Either use the Seam in Action forums:

http://www.manning-sandbox.com/forum.jspa?forumID=354

or the Seam Framework community forums:

http://seamframework.org/Community/SeamUsers

Thanks for understanding. If we answer one support question here, we will have to answer them all...and it just isn't the right forum for that.

-Dan

On Fri, Aug 28, 2009 at 7:34 PM, Info <info@...> wrote:

Hi

I am using Dan Allens book ( Seam in Action) and have been following the
instructions to get seam-gen going. I have hit an error in 'seam
generate' related to Hibernate and I am unsure of how to troubleshoot
it. If anyone has any ideas I would appreciate it. Find below the output:

C:\Documents and Settings\paulmeehan\My
Documents\Development\jboss-seam-2.2.0.GA>seam generate
SEAM_HOME: C:\Documents and Settings\paulmeehan\My
Documents\Development\jboss-seam-2.2.0.GA
Using seam-gen sources from: C:\Documents and Settings\paulmeehan\My
Documents\Development\jboss-seam-2.2.0.GA\seam-gen
Buildfile: C:\Documents and Settings\paulmeehan\My
Documents\Development\jboss-seam-2.2.0.GA\seam-gen\build.xml

init:

init-properties:
[echo] C:/Documents and Settings/paulmeehan/My
Documents/Development/jboss-4.2.2.GA

validate-workspace:

validate-project:

init-generate:

generate-model:
[echo] Reverse engineering database using JDBC driver C:Documents
and SettingspaulmeehanMy DocumentsDevelopmentseaminactionli
ar
[echo] project=c:/Documents and Settings/paulmeehan/My
Documents/Development/open18
[echo] model=com.mydomain.open18.model
[hibernate] Executing Hibernate Tool with a JDBC Configuration (for
reverse engineering)
[hibernate] 1. task: hbm2java (Generates a set of .java files)
[hibernate] log4j:WARN No appenders could be found for logger
(org.hibernate.cfg.Environment).
[hibernate] log4j:WARN Please initialize the log4j system properly.
[hibernate] An exception occurred while running exporter #2:hbm2java
(Generates a set of .java files)
[hibernate] To get the full stack trace run ant with -verbose
[hibernate] org.hibernate.HibernateException: JDBC Driver class not
found: org.h2.Driver
[hibernate] java.lang.ClassNotFoundException: org.h2.Driver
[hibernate] A class were not found in the classpath of the Ant task.
[hibernate] Ensure that the classpath contains the classes needed for
Hibernate and your code are in the classpath.

BUILD FAILED
C:\Documents and Settings\paulmeehan\My
Documents\Development\jboss-seam-2.2.0.GA\seam-gen\build.xml:1564:
org.hibernate.Hibernate
tion: JDBC Driver class not found: org.h2.Driver

thanks
Paul Meehan
--

========================
Zuonics Ltd

The makers of 'ZoeOS'

info@...

http://www.zuonics.com
========================

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://in.relation.to/Bloggers/Dan

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Implementing REQUIRES_NEW for seam transaction management

2009-08-31T11:36:48Z

On Wed, Aug 26, 2009 at 8:55 PM, Stuart Douglas <stuart@...> wrote:

I would like to implement REQUIRES_NEW as a transaction type for the
@Transactional annotation. My basic plan is:

- Create a TransactionManager component that can be installed into
components.xml, and give the option to configure the JNDI location of
the JTA TransactionManager.

- modify the Work.workInTransaction method to check if the existing
transaction need to be suspended, as if so use the TransactionManager
component to suspend and resume the transaction.

I can't help thinking that there is some problem with this approach,
otherwise someone else would have already done it.

Try it, create some tests and if it works, prove it.

I also know that TransactionManager is not supposed to be used by the
application, does anyone know if this will cause problems?

Spring has been doing this for a long time. It's of course app server dependent, but the general feeling is that using it is so common to consider it a public API.

I would also like to implement the ability to control seam global
transactions based on a flag in pages.xml, so they can be disabled for
specific views. Would anyone have any objections to this?

I've always been in favor of this idea.

-Dan

Re: Reaching the seam-dev mailing list is a nightmare (Second try)

2009-08-31T11:04:34Z

Shane, I believe you are one of the moderators. Can you see if Denis' gmail address is listed properly. I would take care of this if I had access to the admin interface, but I don't.

-Dan

On Mon, Aug 31, 2009 at 11:33 AM, Denis Forveille <denis.forveille@...> wrote:

That will be cool but when will this be in place?

I send a message this morning and it didnt' reach the mailing
list...Just received the usual "Your message is waiting moderator
approval..." so i put you, Pete and Dan, in CC

Thx

On Wed, Aug 26, 2009 at 8:05 AM, Pete Muir <pmuir at redhat.com> wrote:

> Yes, assuming that the person who moderates the post checks accept for both
> this message, and one of "clear this members moderate flag" or "add this
> sender to the accepts filter". And, of course, this is all based on the
> address you use to post.

Excellent.

-Dan

Reaching the seam-dev mailing list is a nightmare (Second try)

2009-08-31T08:33:41Z

That will be cool but when will this be in place?

I send a message this morning and it didnt' reach the mailing
list...Just received the usual "Your message is waiting moderator
approval..." so i put you, Pete and Dan, in CC

Thx

On Wed, Aug 26, 2009 at 8:05 AM, Pete Muir <pmuir at redhat.com> wrote:

> Yes, assuming that the person who moderates the post checks accept for both
> this message, and one of "clear this members moderate flag" or "add this
> sender to the accepts filter". And, of course, this is all based on the
> address you use to post.

Excellent.

-Dan
_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Please add a link to download the "latest 2.2 unstable nightly build" on the Wiki

2009-08-31T05:31:44Z

Could someone that has the rights to edit the "Seam Download" page of
the Wiki , add a link to download the "latest 2.2 unstable nightly
build"?
Thanks
_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Importing the photoalbum maven application to m2eclipse/JBoss Tools

2009-08-30T18:45:40Z

I have tried to import the photoalbum application from
http://jboss.org/downloading/?projectId=jbossrichfaces&url=http://download.jboss.com/jboss-richfaces/richfaces-examples-3.3.1.GA.zip
to Eclipse.
There are a few issues related to m2eclipse and WTP.

In order to import the application to Eclipse and configure it to work
with m2eclipse and JBoss Tools, it is necessary to do the following:

1. ejb, ear, web modules
- change the names of the modules to:
photoalbum-ear
photoalbum-ejb
photoalbum-web

2. ear module
- set the version to 5 in maven-ear-plugin
- set photoalbum-ear final-name to photoalbum-ear and add bundleFileName
to the web and ejb module of maven-ear-plugin - obliged because the WTP
deployer ignores deployName - see
https://jira.jboss.org/jira/browse/JBIDE-4655 i
https://issues.sonatype.org/browse/MNGECLIPSE-1564
- create application.xml and jboss-app.xml in
src/main/application/META-INF - see
https://jira.jboss.org/jira/browse/JBIDE-4809
- change context-root from photoalbum to photoalbum-web in pom.xml and
application.xml because m2eclipse ignores context-root - see
https://issues.sonatype.org/browse/MNGECLIPSE-1564

3. ejb module
- move component.properties from src/main/resources-filtered to
src/main/resources with the following contents:
#
#Mon Sep 15 14:29:32 EEST 2008
jndiPattern=photoalbum-ear/#{ejbName}/local
embeddedEjb=false
and remove src/main/resources-filtered
- remove the configuration of maven-resource-plugin
I haven't succeeded to configure Maven resource filtering within
m2eclipse. But, as it is, Maven resource filtering is unnecessary here
because I have had to change the EAR's final name.

4) There is a bug in org.jboss.tools.jsf/PostInstallJsfFacetDelegate -
this class calls IProject.refreshLocal within the facet install
procedure which, sometimes, throws an exception. Until the bug is fixed,
you can workaround it by calling Maven>Update Project Configuration on
the EAR project

In order to test importing the photoalbum application, you can do the
following:

- install/update m2eclipse >= 0.9.9.20090820
- install the latest JBoss Tools trunk
- define Seam Runtime 2.1.1.GA and the DefaultDS connection profile
(they can be set after checking out Maven projects)
- call Import>Check out Maven Projects from SCM
- select svn for SCM URL and enter
http://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/photoalbum
- finish the Import wizard

You will get the photoalbum application containing the JBoss Tools settings.

Snjeza
_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Maven Seam version within a Seam distribution

2009-08-29T11:08:09Z

Does that mean that the mavenized Seam Web Project wizard wouldn't work
with EAP 5.0 or we would use the 2.2.0.GA Maven Seam version?
Currently, if the user chooses Seam facet 2.2, the JBoss Maven
Integration facet offers the 2.2.0.GA version that the user can change.

Snjeza

Max Rydahl Andersen wrote:

> Looking in the manifest is the correct place to look afaik.
>
> As long as there are no Maven repo for our products we can only make
> the maven integration work with .org versions.
>
> /max
>
> Snjezana Peco wrote:
>> I have tried to find Maven versions of Seam and required libraries in
>> order to fix https://jira.jboss.org/jira/browse/JBIDE-4813.
>> I have succeeded to find versions of the required libraries in
>> <SEAM_HOME>/build/root.pom.xml, but haven't succeeded to find the
>> version of Seam (root.pom.xml contains @seam.version@). I have also
>> tried to find the version of Seam within the jboss-seam.jar file. For
>> EAP 5.0, the jboss-seam.jar file contains the 2.2.0.EAP version that
>> isn't any Maven version.
>> Is it possible to find the Maven version of Seam within any Seam
>> distribution?
>>
>> Snjeza
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev@...
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Maven Seam version within a Seam distribution

2009-08-28T22:47:33Z

Looking in the manifest is the correct place to look afaik.

As long as there are no Maven repo for our products we can only make the
maven integration work with .org versions.

/max

Snjezana Peco wrote:

> I have tried to find Maven versions of Seam and required libraries in
> order to fix https://jira.jboss.org/jira/browse/JBIDE-4813.
> I have succeeded to find versions of the required libraries in
> <SEAM_HOME>/build/root.pom.xml, but haven't succeeded to find the
> version of Seam (root.pom.xml contains @seam.version@). I have also
> tried to find the version of Seam within the jboss-seam.jar file. For
> EAP 5.0, the jboss-seam.jar file contains the 2.2.0.EAP version that
> isn't any Maven version.
> Is it possible to find the Maven version of Seam within any Seam
> distribution?
>
> Snjeza
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev
>

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

seam-gen

2009-08-28T16:34:51Z

Hi

I am using Dan Allens book ( Seam in Action) and have been following the
instructions to get seam-gen going. I have hit an error in 'seam
generate' related to Hibernate and I am unsure of how to troubleshoot
it. If anyone has any ideas I would appreciate it. Find below the output:

C:\Documents and Settings\paulmeehan\My
Documents\Development\jboss-seam-2.2.0.GA>seam generate
SEAM_HOME: C:\Documents and Settings\paulmeehan\My
Documents\Development\jboss-seam-2.2.0.GA
Using seam-gen sources from: C:\Documents and Settings\paulmeehan\My
Documents\Development\jboss-seam-2.2.0.GA\seam-gen
Buildfile: C:\Documents and Settings\paulmeehan\My
Documents\Development\jboss-seam-2.2.0.GA\seam-gen\build.xml

init:

init-properties:
[echo] C:/Documents and Settings/paulmeehan/My
Documents/Development/jboss-4.2.2.GA

validate-workspace:

validate-project:

init-generate:

generate-model:
[echo] Reverse engineering database using JDBC driver C:Documents
and SettingspaulmeehanMy DocumentsDevelopmentseaminactionli
ar
[echo] project=c:/Documents and Settings/paulmeehan/My
Documents/Development/open18
[echo] model=com.mydomain.open18.model
[hibernate] Executing Hibernate Tool with a JDBC Configuration (for
reverse engineering)
[hibernate] 1. task: hbm2java (Generates a set of .java files)
[hibernate] log4j:WARN No appenders could be found for logger
(org.hibernate.cfg.Environment).
[hibernate] log4j:WARN Please initialize the log4j system properly.
[hibernate] An exception occurred while running exporter #2:hbm2java
(Generates a set of .java files)
[hibernate] To get the full stack trace run ant with -verbose
[hibernate] org.hibernate.HibernateException: JDBC Driver class not
found: org.h2.Driver
[hibernate] java.lang.ClassNotFoundException: org.h2.Driver
[hibernate] A class were not found in the classpath of the Ant task.
[hibernate] Ensure that the classpath contains the classes needed for
Hibernate and your code are in the classpath.

BUILD FAILED
C:\Documents and Settings\paulmeehan\My
Documents\Development\jboss-seam-2.2.0.GA\seam-gen\build.xml:1564:
org.hibernate.Hibernate
tion: JDBC Driver class not found: org.h2.Driver

thanks
Paul Meehan
--

========================
Zuonics Ltd

The makers of 'ZoeOS'

info@...

http://www.zuonics.com
========================

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Maven Seam version within a Seam distribution

2009-08-28T15:15:27Z

I have tried to find Maven versions of Seam and required libraries in
order to fix https://jira.jboss.org/jira/browse/JBIDE-4813.
I have succeeded to find versions of the required libraries in
<SEAM_HOME>/build/root.pom.xml, but haven't succeeded to find the
version of Seam (root.pom.xml contains @seam.version@). I have also
tried to find the version of Seam within the jboss-seam.jar file. For
EAP 5.0, the jboss-seam.jar file contains the 2.2.0.EAP version that
isn't any Maven version.
Is it possible to find the Maven version of Seam within any Seam
distribution?

Snjeza
_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Subtle changes in seam-gen affecting JBDS :)

2009-08-28T08:43:02Z

Sigh. I have explained this before, but I take the blame for not making this information part of the official documentation. Perhaps I should.

Here's the story. The purpose of the tokenized file is to allow the same build to target different application servers. Right now, JBoss AS 5 and GlassFish are supported. This cannot be done at project setup time because the point of supporting multiple servers is to demonstrate portability of an application, hence a switch at build time.

Before raising objection to token replacements, know that I have set it up so that the JBoss Tools sees files in the place it expects to see them with explicit values. The tokenized files are only used by Ant when running the build for GlassFish or with an alternative profile (in theory).

With that said, there could be bugs in this setup. The problem is that people keep changing the files without a full understand of how everything works. I know, it is confusing as hell. We have established already that seam-gen is just not going to get any better until it is rethought. It was never designed to support JBoss Tools. Therefore, we have these problems.

We really need to just leave seam-gen as it is at this point because the complexity is too high for it to be stable with so many hands in the pot. I know Pete said that a year ago, but we really need to support GlassFish to fix the perception that Seam only worked on JBoss AS. Yes, it was risky, but it has expanded our user base, so it was worth the effort.

-Dan

On Mon, Aug 17, 2009 at 8:12 AM, Pete Muir <pmuir@...> wrote:

Regarding whether JBT can use the tokenized-war, I don't think it can
as it relies on ant replacement tokens.

Dan, could we achieve the same thing using an ftl at generation time?

In general, for the next major rev of Seam-gen, we should use ftl for
every template file, no matter how trivial, as it gives us a lot more
flexibility in the future to add features.

On 17 Aug 2009, at 13:04, Pete Muir wrote:

> Ok, I will respond on the issue.
>
> On 17 Aug 2009, at 12:36, Max Rydahl Andersen wrote:
>
>> Hi,
>>
>> I've added Pete as a watcher on https://jira.jboss.org/jira/browse/JBDS-828
>> but if someone else knows about what components-war-tokenized.xml is
>> and why
>> components.xml is not targeting AS5 so JBoss Tools/JBDS breaks...then
>> please feel free to comment.
>>
>> p.s. I assume the tokenized.xml is to add some flexibility and that
>> is
>> great, but adding that flexibility to JBDS
>> this close to codefreeze is something I would like to avoid if
>> possible.
>> Next version we should sync on what
>> flexibilities were added since I got a feeling that more than this
>> were
>> added to seam-gen recently ;)
>>
>> /max
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev@...
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev