January 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAM-13) Ensure all modules build using Java 5

by Pete Muir (JIRA)

Ensure all modules build using Java 5 ------------------------------------- Key: SEAM-13 URL: https://jira.jboss.org/browse/SEAM-13 Project: Seam 3 Issue Type: Task Components: Build Infrastructure Reporter: Pete Muir Priority: Critical -- 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, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (SEAMPERSIST-22) Remove jboss-logging dependency

by Jozef Hartinger (JIRA)

Remove jboss-logging dependency ------------------------------- Key: SEAMPERSIST-22 URL: https://issues.jboss.org/browse/SEAMPERSIST-22 Project: Seam Persistence Issue Type: Task Environment: 3.0.0.Beta3 Reporter: Jozef Hartinger Assignee: Shane Bryzak Since version 3.0.0.Beta2 Seam Solder bundles jboss-logging. Thus, there is no need to declare an explicit dependency. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-27) Unable to build a Seamspace application

by Martin Gencur (JIRA)

Unable to build a Seamspace application --------------------------------------- Key: SEAMSECURITY-27 URL: https://issues.jboss.org/browse/SEAMSECURITY-27 Project: Seam Security Issue Type: Bug Affects Versions: 3.0.0.Beta1 Reporter: Martin Gencur I guess the example is not finished yet. I created this issue just for completeness of our testing. I'm getting the following error during running "mvn package": [ERROR] The project org.jboss.seam.security:seam-security-seamspace-example:3.0.0-SNAPSHOT (/home/mgencur/Java/seam3testing/security/examples/seamspace/pom.xml) has 2 errors [ERROR] 'dependencies.dependency.version' for org.jboss.seam.xml:seam-xml-config:jar is missing. @ line 57, column 19 [ERROR] 'dependencies.dependency.version' for javax.transaction:jta:jar is missing. @ line 68, column 19 [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (SEAMREST-23) Forge plugin

by Jozef Hartinger (JIRA)

Forge plugin ------------ Key: SEAMREST-23 URL: https://issues.jboss.org/browse/SEAMREST-23 Project: Seam REST Issue Type: Feature Request Components: Tooling Affects Versions: 3.0.0.Beta1 Reporter: Jozef Hartinger Plugin for Seam Forge - this would be a killer feature The plugin (seam-rest) should contain the following commands * enable-jaxrs ** add a new javax.ws.rs.core.Application subclass annotated with @ApplicationPath - ask user for class name and base URI. Besides, scan for existing Application subclass and abort command if found. * enable-seam-rest ** same as enable-jaxrs but also adds seam-rest dependencies to pom.xml. * enable-request-validation ** enable the ValidationInterceptor in beans.xml ** iterate over JAX-RS methods and ask user whether Bean Validation should be enabled for that particular method * new-exception-mapping ** add a new @ExceptionMapping to the Application subclass Furthermore, consider commands for exception-mapping management like list-exception-mapping etc. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Deleted: (SEAMXML-31) Manifest.mf files in jars generated from the module contain unreachable Implementation-URL

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/SEAMXML-31?page=com.atlassian.jira.plugin... ] Martin Gencur deleted SEAMXML-31: --------------------------------- > Manifest.mf files in jars generated from the module contain unreachable Implementation-URL > ------------------------------------------------------------------------------------------ > > Key: SEAMXML-31 > URL: https://issues.jboss.org/browse/SEAMXML-31 > Project: Seam Config > Issue Type: Bug > Reporter: Martin Gencur > Assignee: Jason Porter > Priority: Minor > > The URL is specified in each module's pom.xml via <url>....</url>. You can override it for submodules, otherwise it will be inherited. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMXML-31) Manifest.mf files in jars generated from the module contain unreachable Implementation-URL

by Martin Gencur (JIRA)

Manifest.mf files in jars generated from the module contain unreachable Implementation-URL ------------------------------------------------------------------------------------------ Key: SEAMXML-31 URL: https://issues.jboss.org/browse/SEAMXML-31 Project: Seam Config Issue Type: Bug Components: Build Infrastructure Affects Versions: 3.0.0.Beta2 Reporter: Martin Gencur Assignee: Jason Porter Priority: Minor Fix For: 3.0.0.Beta3 The URL is specified in each module's pom.xml via <url>....</url>. You can override it for submodules, otherwise it will be inherited. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (SEAMCATCH-43) Manifest.mf files in jars generated from the module contain unreachable Implementation-URL

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/SEAMCATCH-43?page=com.atlassian.jira.plug... ] Martin Gencur updated SEAMCATCH-43: ----------------------------------- Priority: Minor (was: Major) > Manifest.mf files in jars generated from the module contain unreachable Implementation-URL > ------------------------------------------------------------------------------------------- > > Key: SEAMCATCH-43 > URL: https://issues.jboss.org/browse/SEAMCATCH-43 > Project: Seam Catch > Issue Type: Bug > Components: Build Infrastructure > Affects Versions: 3.0.0.Beta1 > Reporter: Martin Gencur > Assignee: Jason Porter > Priority: Minor > Fix For: 3.0.0.Beta2 > > > The URL is specified in each module's pom.xml via <url>....</url>. You can override it for submodules, otherwise it will be inherited. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (SEAMREST-23) Forge plugin

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/SEAMREST-23?page=com.atlassian.jira.plugi... ] Jozef Hartinger updated SEAMREST-23: ------------------------------------ Description: Seam REST Plugin for Seam Forge - this would be a killer feature The plugin (seam-rest) should contain the following commands * enable-jaxrs ** add a new javax.ws.rs.core.Application subclass annotated with @ApplicationPath - ask user for class name and base URI. Besides, scan for existing Application subclass and abort command if found. * enable-seam-rest ** same as enable-jaxrs but also adds seam-rest dependencies to pom.xml. * enable-request-validation ** enable the ValidationInterceptor in beans.xml ** iterate over JAX-RS methods and ask user whether Bean Validation should be enabled for that particular method * new-exception-mapping ** add a new @ExceptionMapping to the Application subclass Furthermore, consider commands for exception-mapping management like list-exception-mapping etc. was: Plugin for Seam Forge - this would be a killer feature The plugin (seam-rest) should contain the following commands * enable-jaxrs ** add a new javax.ws.rs.core.Application subclass annotated with @ApplicationPath - ask user for class name and base URI. Besides, scan for existing Application subclass and abort command if found. * enable-seam-rest ** same as enable-jaxrs but also adds seam-rest dependencies to pom.xml. * enable-request-validation ** enable the ValidationInterceptor in beans.xml ** iterate over JAX-RS methods and ask user whether Bean Validation should be enabled for that particular method * new-exception-mapping ** add a new @ExceptionMapping to the Application subclass Furthermore, consider commands for exception-mapping management like list-exception-mapping etc. > Forge plugin > ------------ > > Key: SEAMREST-23 > URL: https://issues.jboss.org/browse/SEAMREST-23 > Project: Seam REST > Issue Type: Feature Request > Components: Tooling > Affects Versions: 3.0.0.Beta1 > Reporter: Jozef Hartinger > > Seam REST Plugin for Seam Forge - this would be a killer feature > The plugin (seam-rest) should contain the following commands > * enable-jaxrs > ** add a new javax.ws.rs.core.Application subclass annotated with @ApplicationPath - ask user for class name and base URI. Besides, scan for existing Application subclass and abort command if found. > * enable-seam-rest > ** same as enable-jaxrs but also adds seam-rest dependencies to pom.xml. > * enable-request-validation > ** enable the ValidationInterceptor in beans.xml > ** iterate over JAX-RS methods and ask user whether Bean Validation should be enabled for that particular method > * new-exception-mapping > ** add a new @ExceptionMapping to the Application subclass > Furthermore, consider commands for exception-mapping management like list-exception-mapping etc. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMREST-22) Provide JSP-based TemplatingProvider

by Jozef Hartinger (JIRA)

Provide JSP-based TemplatingProvider ------------------------------------ Key: SEAMREST-22 URL: https://issues.jboss.org/browse/SEAMREST-22 Project: Seam REST Issue Type: Feature Request Components: Templating Affects Versions: 3.0.0.Beta1 Reporter: Jozef Hartinger Similarly to the FreeMarker and Velocity templating providers, provide an implementation capable of using good old JSP's for transforming JAX-RS invocations into HTTP responses. http://docs.jboss.org/seam/3/rest/latest/reference/en-US/html/rest.templa... http://stackoverflow.com/questions/1075827/execute-jsp-directly-from-java... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (SOLDER-70) MessageBundle Loading for SeamServlet

by Matthias Unverzagt (JIRA)

MessageBundle Loading for SeamServlet ------------------------------------- Key: SOLDER-70 URL: https://issues.jboss.org/browse/SOLDER-70 Project: Seam Solder Issue Type: Bug Affects Versions: 3.0.0.Beta3 Environment: Jan 30th: SNAPSHOT-3.0.0 of seam-servlet and seam-solder Reporter: Matthias Unverzagt Interplay of the two libraries cause the following problem: Caused by: java.lang.IllegalArgumentException: Invalid bundle interface org.jboss.seam.servlet.messages.ServletMessages (implementation not found) at org.jboss.seam.solder.logging.Messages.getBundle(Messages.java:97) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2011