July 2010 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3837) JobExecutorServlet as seam component

by Marko Strukelj (JIRA)

JobExecutorServlet as seam component ------------------------------------ Key: JBSEAM-3837 URL: https://jira.jboss.org/jira/browse/JBSEAM-3837 Project: Seam Issue Type: Feature Request Components: BPM Affects Versions: 2.0.3.CR1 Environment: Seam 2.0.3, JBPM 3.2.2 Reporter: Marko Strukelj Priority: Optional JBPM Job Execution using JobExecutorServlet doesn't work in Seam. Attached are modified sources to turn JobExecutorServlet into a Seam component and to have it use Seam's contexts and transactions. This is probably not the best way to do it but it works for me where I'm using it. There is a proper solution in the making - see related issues. -- 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

13 years, 7 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4313) EntityHome created/updated/deleted default messages should come from resource bundle instead of hard-coded messages

by Julien Kronegg (JIRA)

EntityHome created/updated/deleted default messages should come from resource bundle instead of hard-coded messages ------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4313 URL: https://jira.jboss.org/jira/browse/JBSEAM-4313 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.2.GA Reporter: Julien Kronegg Priority: Minor The EntityHome default messages on creation/update/deletion are hard-coded in the org.jboss.seam.framework.Home class: protected void initDefaultMessages() { Expressions expressions = new Expressions(); if (createdMessage == null) { createdMessage = expressions.createValueExpression("Successfully created"); } if (updatedMessage == null) { updatedMessage = expressions.createValueExpression("Successfully updated"); } if (deletedMessage == null) { deletedMessage = expressions.createValueExpression("Successfully deleted"); } } While the messages can be updated in the "messages_en.properties" (using "MyEntityClass_created" key for example), this must be done for each entity class. This is painful! It would be nice if we get the following messages decreasing priority for the entity class MyEntityClass: 1. "MyEntityClass_created" 2. "org.jboss.seam.framework.Home_defaultCreated" 3. static message "Successfully created" Note: the example above is given for the creation message only -- 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

13 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (SEAMXML-5) Change artifact id to seam-xml-config

by Stuart Douglas (JIRA)

Change artifact id to seam-xml-config ------------------------------------- Key: SEAMXML-5 URL: https://jira.jboss.org/browse/SEAMXML-5 Project: Seam XML Bean Config Issue Type: Task Affects Versions: 3.0.0.Alpha1 Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 3.0.0.Alpha2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMXML-6) Distribution artifact final name is wrong

by Pete Muir (JIRA)

Distribution artifact final name is wrong ----------------------------------------- Key: SEAMXML-6 URL: https://jira.jboss.org/browse/SEAMXML-6 Project: Seam XML Bean Config Issue Type: Task Reporter: Pete Muir Priority: Optional It's seam-xml-config-parent-3.0.0.Alpha2-bin.zip, should be seam-xml-config-3.0.0.Alpha2.zip -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (SEAMXML-9) Finalise root namespace and tag names

by Stuart Douglas (JIRA)

Finalise root namespace and tag names ------------------------------------- Key: SEAMXML-9 URL: https://jira.jboss.org/browse/SEAMXML-9 Project: Seam XML Bean Config Issue Type: Task Reporter: Stuart Douglas The root namespace and all the tag names need to be discussed and agreed upon. In particular: - Should the root namespace be changed to urn:java:ee ? - Should <specializes> be changed as it is to close to the @Specializes annotation -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

4
10
0 / 0

[JBoss JIRA] Created: (SEAMXML-7) Seam XML distribution is missing documentation

by Pete Muir (JIRA)

Seam XML distribution is missing documentation ---------------------------------------------- Key: SEAMXML-7 URL: https://jira.jboss.org/browse/SEAMXML-7 Project: Seam XML Bean Config Issue Type: Task Reporter: Pete Muir Priority: Critical Fix For: 3.0.0.Beta1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (SEAMXML-13) Change <override> to <replaces>

by Stuart Douglas (JIRA)

Change <override> to <replaces> ------------------------------- Key: SEAMXML-13 URL: https://jira.jboss.org/browse/SEAMXML-13 Project: Seam XML Bean Config Issue Type: Task Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 3.0.0.Beta1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMXML-1) support interface configuration

by Dan Allen (JIRA)

support interface configuration ------------------------------- Key: SEAMXML-1 URL: https://jira.jboss.org/jira/browse/SEAMXML-1 Project: Seam XML Issue Type: Feature Request Reporter: Dan Allen Assignee: Pete Muir If you try to configure a field or method of a type type that is an interface (such as assign an initial field value), the resolver fails when matching the element to a method or field. If it fails to find a matching method, a NullPointerException is thrown. It always fails to find a field because an interface type has no fields. This issue is a request to support and test configuration of interface types. -- 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

13 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (SEAMXML-8) Review all deviations from the original JSR-299 draft spec

by Stuart Douglas (JIRA)

Review all deviations from the original JSR-299 draft spec ----------------------------------------------------------- Key: SEAMXML-8 URL: https://jira.jboss.org/browse/SEAMXML-8 Project: Seam XML Bean Config Issue Type: Task Reporter: Stuart Douglas There a quite a few changes from the draft spec, I have listed them below: - shorthand field value syntax You can do <ns:MyBean fieldName="fieldValue" /> - Producer method / field syntax was: <ns:Bean> <ns:field> <Producer> <ns:SomeQualifier/> </Producer> </ns:field> </ns:Bean> I have changed this to: <ns:Bean> <ns:field> <Producer/> <ns:SomeQualifier/> </ns:field> </ns:Bean> - Setting initial field values You can now do: <ns:Bean> <ns:field> <Producer/> <value>10</value> </ns:field> <ns:field2>5</ns:field2> <ns:mapField> <entry><key>a</key><value>b</value></entry> <e><k>c</k><v>d</v></e> </ns:mapField/> </ns:Bean> The value key and entry tags can be shorted to just <v><k> and <e> tags. The <value> element was not able to be used like this in the original spec, so it was not possible to apply annotations and set the field value. - <overrides> and <specializes> tags - Change of syntax for constructor and method parameters In the draft spec method parameters are specified as direct children of the method like so: <ns:Bean> <ns:method> <Producer/> <ns:ParamType1><ns:SomeAnntation/></ns:ParamType1> <ns:SomeOtherAnnotation/> <ns:ParamType2/> </ns:method> </ns:Bean> This has been changed to: <ns:Bean> <ns:method> <Producer/> <ns:SomeOtherAnnotation/> <parameters> <ns:ParamType1><ns:SomeAnntation/></ns:ParamType1> <ns:ParamType2/> </parameters/> </ns:method> </ns:Bean> - Interface configuration Annotations / field values applied to an interface via XML are applied to all classes that implement that interface. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
16
0 / 0

[JBoss JIRA] Created: (SEAMXML-2) match XML namespace to package and subpackages (or multiple packages)

by Dan Allen (JIRA)

match XML namespace to package and subpackages (or multiple packages) --------------------------------------------------------------------- Key: SEAMXML-2 URL: https://jira.jboss.org/jira/browse/SEAMXML-2 Project: Seam XML Issue Type: Feature Request Reporter: Dan Allen Assignee: Pete Muir To avoid an explosion of namespace declarations (which increases complexity and reduces readability), there should be a way to have a urn:java namespace URL match not only one Java package, but multiple packages. Perhaps, a namespace will match a package and any sub-packages. Multiple package mapping is done internally to the url:java:seam:core namespace. The user needs a way to do the same. Otherwise, modules will need to use a flat directory structure to avoid burdening the end developer. -- 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

13 years, 8 months

4
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2010