February 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMREMOTING-19) Remove Weld dependency

by Shane Bryzak (JIRA)

Remove Weld dependency ---------------------- Key: SEAMREMOTING-19 URL: https://issues.jboss.org/browse/SEAMREMOTING-19 Project: Seam Remoting Issue Type: Task Reporter: Shane Bryzak Assignee: Shane Bryzak Fix For: 3.0.0.CR1 There is some Weld-specific class usage in the remoting code related to conversation management - we need to remove this. An alternative might be to use reflection instead. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
2
0 / 0

[JBoss JIRA] Created: (SEAM-24) Seam 3.0.0.Beta2 distribution missing some images from seam remoting docs in the consolidated reference docs

by Marek Schmidt (JIRA)

Seam 3.0.0.Beta2 distribution missing some images from seam remoting docs in the consolidated reference docs ------------------------------------------------------------------------------------------------------------ Key: SEAM-24 URL: https://issues.jboss.org/browse/SEAM-24 Project: Seam 3 Issue Type: Bug Components: Common Documentation Affects Versions: 3.0.0.Beta2 Reporter: Marek Schmidt Priority: Trivial The consolidated reference documentation in Seam 3.0.0.Beta2 distribution does not contain the following images from seam3/remoting docs: remoting-model-customer-address-uml.png remoting-model-customer-uml-1.png They are missing in the following directories, yet referenced from the HTMLs: seam-3.0.0.Beta2/doc/reference/html_single/images/ seam-3.0.0.Beta2/doc/reference/html/images/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
5
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-24) 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: SEAMREMOTING-24 URL: https://issues.jboss.org/browse/SEAMREMOTING-24 Project: Seam Remoting Issue Type: Bug Affects Versions: 3.0.0.Beta2 Reporter: Martin Gencur 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

15 years

3
8
0 / 0

[JBoss JIRA] Created: (SOLDER-51) Decouple service handler annotation from implementation class

by Dan Allen (JIRA)

Decouple service handler annotation from implementation class ------------------------------------------------------------- Key: SOLDER-51 URL: https://issues.jboss.org/browse/SOLDER-51 Project: Seam Solder Issue Type: Feature Request Components: Core Reporter: Dan Allen The current design of the service handler configuration prevents modules from being able to deliver a service annotation in the api since it requires a direct reference to the implementation class. @ServiceHandler(MyServiceHandler.class) Switch to either a string or adopt the annotation binding concept from CDI (like interceptors) Also, support the use of the service handler annotation on stereotypes. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
7
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-37) Unsatisfied dependencies for type [Messages]...

by Aaron Siri (JIRA)

Unsatisfied dependencies for type [Messages]... ----------------------------------------------- Key: SEAMSECURITY-37 URL: https://issues.jboss.org/browse/SEAMSECURITY-37 Project: Seam Security Issue Type: Bug Affects Versions: 3.0.0.Beta2 Environment: Mac OS X, Glassfish v3.1b42, Java 1.6 Reporter: Aaron Siri Trying to deploy an app with simple security integration I get the following exception: SEVERE: Exception while loading the app : WELD-001408 Unsatisfied dependencies for type [Messages] with qualifiers [@Default] at injection point [[field] @Inject org.jboss.seam.security.SecurityEventMessages.messages] org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [Messages] with qualifiers [@Default] at injection point [[field] @Inject org.jboss.seam.security.SecurityEventMessages.messages] at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:305) at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:139) at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:162) at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:385) at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:371) at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:390) ... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

5
24
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-35) Unable to edit/delete user in the idmconsole example

by Martin Gencur (JIRA)

Unable to edit/delete user in the idmconsole example ---------------------------------------------------- Key: SEAMSECURITY-35 URL: https://issues.jboss.org/browse/SEAMSECURITY-35 Project: Seam Security Issue Type: Bug Affects Versions: 3.0.0.Beta2 Reporter: Martin Gencur Assignee: Shane Bryzak As Richard Barabe stated in SEAMSECURITY-25, it is not possible to edit or delete a user in the application. The other functionality seems to be OK. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
3
0 / 0

[JBoss JIRA] Created: (SEAMFACES-88) DeploymentException: WELD-001408 Unsatisfied dependencies for type [Messages]

by Brian Leathem (JIRA)

DeploymentException: WELD-001408 Unsatisfied dependencies for type [Messages] ----------------------------------------------------------------------------- Key: SEAMFACES-88 URL: https://issues.jboss.org/browse/SEAMFACES-88 Project: Seam Faces Issue Type: Bug Environment: Glassfish 3.1-b43 Reporter: Brian Leathem Fix For: 3.0.0.Final When deploying an application I get the deployment exception below. Updating glassfish to the latest Weld 1.2-SNAPSHOT resolves this deployment exception. Faces needs to either avoid this issue, or document the workaround. Stacktrace: ---------- SEVERE: Exception while loading the app : WELD-001408 Unsatisfied dependencies for type [Messages] with qualifiers [@Default] at injection point [[field] @Inject org.jboss.seam.faces.status.MessagesAdapter.messages] org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [Messages] with qualifiers [@Default] at injection point [[field] @Inject org.jboss.seam.faces.status.MessagesAdapter.messages] at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:305) at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:139) at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:162) at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:385) at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:371) at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:390) at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:190) at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:128) at org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:298) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:461) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240) at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:370) at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:355) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:370) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1067) at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:96) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1247) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1235) at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:465) at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:222) at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:168) at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117) at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:234) at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:822) at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:719) at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1013) at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225) at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90) at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79) at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54) at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59) at com.sun.grizzly.ContextTask.run(ContextTask.java:71) at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532) at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
3
0 / 0

[JBoss JIRA] Created: (SEAMFACES-81) NoClassDefFoundError: org/jboss/seam/exception/control/ExceptionToCatch

by Brian Leathem (JIRA)

NoClassDefFoundError: org/jboss/seam/exception/control/ExceptionToCatch ----------------------------------------------------------------------- Key: SEAMFACES-81 URL: https://issues.jboss.org/browse/SEAMFACES-81 Project: Seam Faces Issue Type: Bug Environment: Glassfish 3.1 M2 (b41) Reporter: Brian Leathem Assignee: Brian Leathem Fix For: 3.0.0.Beta3 I have an app that has a JSF 2 ExceptionHandlerWrapper. After handling it's exception, it calls getWrapped().handle() which calls into the Seam CatchExceptionHandler. The Seam CatchExceptionHanlder in turn throws a NoClassDefFoundError is Seam Catch is not present: java.lang.NoClassDefFoundError: org/jboss/seam/exception/control/ExceptionToCatch The Seam CatchExceptionHanlder is not supposed to be registered if Seam Catch is not present, but it seems to be registering regardless. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
2
0 / 0

[JBoss JIRA] Created: (SEAM-22) Error running the Hotel Booking example on Seam 3

by Nadim Rafehi (JIRA)

Error running the Hotel Booking example on Seam 3 ------------------------------------------------- Key: SEAM-22 URL: https://issues.jboss.org/browse/SEAM-22 Project: Seam 3 Issue Type: Bug Components: Shared Examples Affects Versions: 3.0.0.Beta1 Environment: Running under Windows 7 with JBoss AS 6.0.0 Final. Project built and compiled using Maven 3.0. Reporter: Nadim Rafehi I downloaded the javaee-booking (hotel booking) example from Git and compiled it using Maven. It deployed without error. When starting the application, I'm able to view the home screen however when I click to register a new user, a JSF error is being shown. The error is: /register.xhtml @35,40 <p:input> The following attribute(s) are required, but no values have been supplied for them: label. To fix, simple give each input a label attribute. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
1
0 / 0

[JBoss JIRA] Created: (SEAM-18) seam/build/checkout.sh have wrong repo name for Remoting module

by Marek Novotny (JIRA)

seam/build/checkout.sh have wrong repo name for Remoting module --------------------------------------------------------------- Key: SEAM-18 URL: https://issues.jboss.org/browse/SEAM-18 Project: Seam 3 Issue Type: Bug Reporter: Marek Novotny Checkout.sh script contains list of all Seam 3 module repos for cloning modules. Remoting module is there as js-remoting instead of remoting. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2011