January 2010 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1619) support for Glassfish in seam-gen

by Dan Allen (JIRA)

support for Glassfish in seam-gen --------------------------------- Key: JBSEAM-1619 URL: http://jira.jboss.com/jira/browse/JBSEAM-1619 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.0.0.BETA1 Environment: Glassfish V2 Reporter: Dan Allen I believe that adding support for Glassfish will help promote the adoption of Seam. In my mind, Tomcat is not nearly as important because it is not a Java EE-compliant environment and seam-gen is all about creating compliant projects. Supporting Glassfish is actually quite straightforward. There are a couple of assumptions that are made by seam-gen that render it incompatible with a generic Java EE-compliant application server. Here is what needs to change: 1. The java:/ prefix on the data source causes problems with other servers. This can be easily brought into compliance by adding <use-java-context>false</use-java-context> to the *-ds.xml files and removing the java:/ prefix from the persistence-*.xml files in the seam-gen/resources/META-INF directory 2. Glassfish does not use Hibernate EntityManager as the default JPA provider, and therefore does not have any of its jar files. Of course, we could just make everyone copy necessary hibernate jar files into the glassfish installation directory, but that just isn't going to go over well. I think a better approach is to modify the build.xml file to copy the following three libraries if the property hibernate.needed=true is set: hibernate-all.jar thirdparty-all.jar jboss-archive-browsing.jar (not currently in the seam distribution, but stuck inside the jboss-embedded-all.jar file) 3. Make the hibernate.transaction.manager_lookup_class parameterized, perhaps asking during setup 4. Removing the .war suffix on the exploded archive directory (so that Glassfish can deploy the directory using asadmin deploydir) That's it! Then you can have Glassfish working. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

8
21
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1201) Support for Groovy tests in seam-gen

by Emmanuel Bernard (JIRA)

Support for Groovy tests in seam-gen ------------------------------------ Key: JBSEAM-1201 URL: http://jira.jboss.com/jira/browse/JBSEAM-1201 Project: JBoss Seam Issue Type: Feature Request Components: Tools Reporter: Emmanuel Bernard Assigned To: Emmanuel Bernard -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
3
0 / 0

[JBoss JIRA] Closed: (JBSEAM-265) Inject via method parameters

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-265?page=com.atlassian.jira.plu... ] Pete Muir closed JBSEAM-265. ---------------------------- Resolution: Out of Date Assignee: Pete Muir (was: Gavin King) Supported in CDI > Inject via method parameters > ---------------------------- > > Key: JBSEAM-265 > URL: https://jira.jboss.org/jira/browse/JBSEAM-265 > Project: Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assignee: Pete Muir > > public void login(@In("user") User user) { > ... > } > is ugly, but we should support it anyway. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBSEAM-355) Constructor injection of component dependencies

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-355?page=com.atlassian.jira.plu... ] Pete Muir closed JBSEAM-355. ---------------------------- Resolution: Out of Date Assignee: Pete Muir Supported in CDI > Constructor injection of component dependencies > ----------------------------------------------- > > Key: JBSEAM-355 > URL: https://jira.jboss.org/jira/browse/JBSEAM-355 > Project: Seam > Issue Type: Feature Request > Components: Core > Reporter: Christian Bauer > Assignee: Pete Muir > Priority: Minor > > Take the registration example. The 'user' component is instantiated by Seam when JSF first looks for 'user' in a page. It is then put in the SESSION context (think CONVERSATION for other use cases of what I'm proposing). Seam uses the default constructor to instantiate the component. > Now imagine that some attributes of User are immutable and that the only way to set their values is through a different constructor. Also imagine that these values are actually present when Seam instantiates the 'user' component, e.g. in the current CONVERSATION. I'd like to tell Seam to call my constructor and use EL to bind the arguments. > Without this feature, immutable properties need to have public setter methods that I call later in an action method to wire in the required attributes manually. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBSEAM-121) Support per-token variables in jBPM

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-121?page=com.atlassian.jira.plu... ] Pete Muir closed JBSEAM-121. ---------------------------- Resolution: Out of Date Assignee: Pete Muir (was: Gavin King) Close, and reconsider in light of jBPM 4 > Support per-token variables in jBPM > ----------------------------------- > > Key: JBSEAM-121 > URL: https://jira.jboss.org/jira/browse/JBSEAM-121 > Project: Seam > Issue Type: Feature Request > Components: BPM > Reporter: Gavin King > Assignee: Pete Muir > > jBPM variables can be scoped to the entire process instance, or to a single path of execution (Token). Currently Seam does not support the second kind of variable. This is not sufficient. Do we need a new PROCESS_PATH context?? Even this may not be enough in theory, since jBPM actually supports a kind of Token hierarchy. Is there some other solution? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBSEAM-119) @CancelTask

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-119?page=com.atlassian.jira.plu... ] Pete Muir reassigned JBSEAM-119: -------------------------------- Assignee: Piotr Steininger Another one to think about for Seam 3 integration > @CancelTask > ----------- > > Key: JBSEAM-119 > URL: https://jira.jboss.org/jira/browse/JBSEAM-119 > Project: Seam > Issue Type: Feature Request > Components: BPM > Reporter: Gavin King > Assignee: Piotr Steininger > > I am still arguing with Tom about whether @CancelTask is needed but I think it is. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBSEAM-198) jBPM packaging

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-198?page=com.atlassian.jira.plu... ] Pete Muir reassigned JBSEAM-198: -------------------------------- Assignee: Piotr Steininger Piotr, one for you to think about :-) > jBPM packaging > -------------- > > Key: JBSEAM-198 > URL: https://jira.jboss.org/jira/browse/JBSEAM-198 > Project: Seam > Issue Type: Feature Request > Components: BPM > Reporter: Gavin King > Assignee: Piotr Steininger > > When the jBPM guys come up with some welldefined packaging, we should have a scanner that automagically discovers process and pageflow definitions, instead of having to list these things explicitly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBSEAM-139) support to Rich Client Applications

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-139?page=com.atlassian.jira.plu... ] Pete Muir closed JBSEAM-139. ---------------------------- Resolution: Out of Date Assignee: Pete Muir Weld SE provides such functionality for Seam 3 apps > support to Rich Client Applications > ----------------------------------- > > Key: JBSEAM-139 > URL: https://jira.jboss.org/jira/browse/JBSEAM-139 > Project: Seam > Issue Type: Feature Request > Reporter: Mauro Silva > Assignee: Pete Muir > > Support to rich client applications, like eclipse RCP -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBSEAM-53) Decide whether we should decouple EVENT from REQUEST context

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-53?page=com.atlassian.jira.plug... ] Pete Muir closed JBSEAM-53. --------------------------- Resolution: Out of Date Assignee: Pete Muir (was: Gavin King) CDI has not gone this way > Decide whether we should decouple EVENT from REQUEST context > ------------------------------------------------------------ > > Key: JBSEAM-53 > URL: https://jira.jboss.org/jira/browse/JBSEAM-53 > Project: Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assignee: Pete Muir > > Possibly, it would be better to have multiple event contexts per web request. (ie. JSF events, jBPM events all taking place in distinct contexts belonging to the request context) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBSEAM-115) Internal Session, Request and Application abstractions

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-115?page=com.atlassian.jira.plu... ] Pete Muir closed JBSEAM-115. ---------------------------- Resolution: Out of Date Assignee: Pete Muir (was: Gavin King) Weld handles contexts this way > Internal Session, Request and Application abstractions > ------------------------------------------------------ > > Key: JBSEAM-115 > URL: https://jira.jboss.org/jira/browse/JBSEAM-115 > Project: Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assignee: Pete Muir > Priority: Critical > Attachments: seam-req-ses-app-patch > > > We need a "strong" internal abstraction of the notions of Session, Request and Application. Currently we have code variously dealing with HttpSession, ExternalContext, etc. > It woudl probably be best to bind these things to a threadlocal. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2010