March 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMSECURITY-47) security-openid-rp - fails to deploy on GlassFish

by Jozef Hartinger (JIRA)

security-openid-rp - fails to deploy on GlassFish ------------------------------------------------- Key: SEAMSECURITY-47 URL: https://issues.jboss.org/browse/SEAMSECURITY-47 Project: Seam Security Issue Type: Bug Affects Versions: 3.0.0.CR3 Reporter: Jozef Hartinger Priority: Critical Fix For: 3.0.0.Final Looks like a bug in Seam, since nor I am able to locate an assignable implementation of OpenIdRelyingPartyApi [#|2011-03-24T11:50:30.349+0100|SEVERE|glassfish3.1|javax.enterprise.system.tools.admin.org.glassfish.deployment.admin|_ThreadID=61;_ThreadName=Thread-1;|Exception while loading the app : WELD-001408 Unsatisfied dependencies for type [OpenIdRelyingPartyApi] with qualifiers [@Default] at injection point [[field] @Inject private org.jboss.seam.security.external.openid.OpenIdAuthenticator.openIdApi] org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [OpenIdRelyingPartyApi] with qualifiers [@Default] at injection point [[field] @Inject private org.jboss.seam.security.external.openid.OpenIdAuthenticator.openIdApi] 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:396) 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:662) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
11
0 / 0

[JBoss JIRA] Created: (SEAMFACES-118) Deployment to Glassfish 3.1 fails with "WELD-001409 Ambiguous dependencies for type [Flash]"

by Craig Ringer (JIRA)

Deployment to Glassfish 3.1 fails with "WELD-001409 Ambiguous dependencies for type [Flash]" -------------------------------------------------------------------------------------------- Key: SEAMFACES-118 URL: https://issues.jboss.org/browse/SEAMFACES-118 Project: Seam Faces Issue Type: Bug Components: CDI Integration Affects Versions: 3.0.0.CR2 Environment: Glassfish 3.1 Apache Maven 3.0.2 (r1056850; 2011-01-09 08:58:10+0800) Java version: 1.6.0_24, vendor: Sun Microsystems Inc. Java home: C:\Program Files\Java\jdk1.6.0_24\jre Default locale: en_AU, platform encoding: Cp1252 OS name: "windows 7", version: "6.1", arch: "x86", family: "windows" Reporter: Craig Ringer Deploying Seam Faces to Glassfish 3.1 fails if a class is present that has an injection point for the Flash scope, ie "@Inject private javax.faces.context.Flash flash". The deployment failure suggests that there is an ambiguous dependency caused by multiple Flash producers within Seam Faces its self: SEVERE: Exception while loading the app : WELD-001409 Ambiguous dependencies for type [Flash] with qualifiers [@Default] at injection point [[field] @Inject private transient au.com.postnewspapers.classads.webui.AdSearchController.flashScope]. Possible dependencies [[Producer Method [Flash] with qualifiers [@Any @Default] declared as [[method] @Produces @RequestScoped public org.jboss.seam.faces.environment.FacesFlashProducer.getFlash()], Producer Method [Flash] with qualifiers [@Any @Default] declared as [[method] @Produces @RequestScoped public org.jboss.seam.faces.context.FlashProducer.getFlash()]]] Full exception and server log here: https://github.com/ringerc/scrapcode/blob/master/testcases/javaee/glassfi... I've put together a minimal test case here: https://github.com/ringerc/scrapcode/tree/master/testcases/javaee/glassfi... -- 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-71) Document setup for event observer in EJB JAR

by Dan Allen (JIRA)

Document setup for event observer in EJB JAR -------------------------------------------- Key: SEAMFACES-71 URL: https://issues.jboss.org/browse/SEAMFACES-71 Project: Seam Faces Issue Type: Task Components: Documentation, Event Bridge Affects Versions: 3.0.0.Beta2 Reporter: Dan Allen Fix For: 3.0.0.Beta3 Add a tip pointing out that beans.xml must be in WEB-INF and inside the EJB JAR containing the observer. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
4
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-49) remove slf4j usage

by Dan Allen (JIRA)

remove slf4j usage ------------------ Key: SEAMSECURITY-49 URL: https://issues.jboss.org/browse/SEAMSECURITY-49 Project: Seam Security Issue Type: Task Affects Versions: 3.0.0.CR3 Reporter: Dan Allen Assignee: Shane Bryzak Priority: Blocker Fix For: 3.0.0.Final ./impl/src/main/java/org/jboss/seam/security/management/IdmAuthenticator.java ./impl/src/main/java/org/jboss/seam/security/permission/PermissionManager.java ./impl/src/main/java/org/jboss/seam/security/permission/JpaPermissionStore.java ./impl/src/main/java/org/jboss/seam/security/permission/SecurityRuleProducer.java ./impl/src/main/java/org/jboss/seam/security/IdentityImpl.java ./impl/src/main/java/org/jboss/seam/security/jaas/JaasAuthenticator.java ./external/src/test/java/org/jboss/seam/security/externaltest/integration/client/IntegrationTest.java ./external/src/main/java/org/jboss/seam/security/external/saml/SamlSignatureUtilForPostBinding.java -- 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-60) Update examples.txt

by Jozef Hartinger (JIRA)

Update examples.txt ------------------- Key: SEAM-60 URL: https://issues.jboss.org/browse/SEAM-60 Project: Seam 3 Distribution Issue Type: Task Affects Versions: 3.0.0.CR3 Reporter: Jozef Hartinger Fix For: 3.0.0.Final Use correct example names (folder name == context path of the deployed example) * booking -> seam-booking * catch-basic -> catch-basic-servlet * princess-rescue -> config-princess-rescue rework REST section rest-tasks - Demonstrates Seam REST module rest-exceptions - Demonstrates declarative exception handling and Seam Catch integration rest-client - Demonstrates Seam REST Client remove security-openid-rp (to reflect SEAM-59) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
4
0 / 0

[JBoss JIRA] Created: (SEAMFACES-101) First request in the short.ly example returns weird action URL due to a bug in prettyfaces on JBossAS 6

by Marek Schmidt (JIRA)

First request in the short.ly example returns weird action URL due to a bug in prettyfaces on JBossAS 6 ------------------------------------------------------------------------------------------------------- Key: SEAMFACES-101 URL: https://issues.jboss.org/browse/SEAMFACES-101 Project: Seam Faces Issue Type: Bug Environment: jbossas6 Reporter: Marek Schmidt Priority: Minor The first request in a session to the deployed short.ly example produces a form with weird action URL, such as action="/short.ly/;jsessionid=cc08b47dabc51c5c65ccfb747ba004e9;jsessionid=CC08B47DABC51C5C65CCFB747BA004E9", which is handled incorrectly on the postback, interpreting the first jsessionid as a redirect key. This appears to be a bug in prettyfaces. Updating to prettyfaces 3.2.0 seems to fix the problem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

4
4
0 / 0

[JBoss JIRA] Created: (SEAMWICKET-30) numberguess example - integration tests are always skipped

by Jozef Hartinger (JIRA)

numberguess example - integration tests are always skipped ---------------------------------------------------------- Key: SEAMWICKET-30 URL: https://issues.jboss.org/browse/SEAMWICKET-30 Project: Seam for Apache Wicket Issue Type: Bug Affects Versions: 3.0.0.CR1 Reporter: Jozef Hartinger Priority: Minor Fix For: 3.0.0.Final Even when running the example with an integration test profile ("mvn test -Pitest-jbossas-remote"), the tests are skipped --- maven-surefire-plugin:2.6:test (default-test) @ seam-wicket-example-numberguess --- [INFO] Tests are skipped. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
2
0 / 0

[JBoss JIRA] Created: (SEAMWICKET-29) Use default profile names for integration tests

by Jozef Hartinger (JIRA)

Use default profile names for integration tests ----------------------------------------------- Key: SEAMWICKET-29 URL: https://issues.jboss.org/browse/SEAMWICKET-29 Project: Seam for Apache Wicket Issue Type: Bug Affects Versions: 3.0.0.CR1 Reporter: Jozef Hartinger Priority: Minor Fix For: 3.0.0.Final In the numberguess example, use profile name "jbossas-remote-6" instead of "itest-jbossas-remote" to follow the convention used in other modules. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
2
0 / 0

[JBoss JIRA] Updated: (SEAMWICKET-5) Allow Wicket support to be used with any 299 impl

by Shane Bryzak (JIRA)

[ https://issues.jboss.org/browse/SEAMWICKET-5?page=com.atlassian.jira.plug... ] Shane Bryzak updated SEAMWICKET-5: ---------------------------------- Fix Version/s: The future (was: 3.0.0.Final) > Allow Wicket support to be used with any 299 impl > ------------------------------------------------- > > Key: SEAMWICKET-5 > URL: https://issues.jboss.org/browse/SEAMWICKET-5 > Project: Seam for Apache Wicket > Issue Type: Feature Request > Reporter: Pete Muir > Assignee: Clint Popetz > Priority: Blocker > Fix For: The future > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Updated: (SEAMWICKET-10) numberguess example does not deploy on tomcat

by Shane Bryzak (JIRA)

[ https://issues.jboss.org/browse/SEAMWICKET-10?page=com.atlassian.jira.plu... ] Shane Bryzak updated SEAMWICKET-10: ----------------------------------- Fix Version/s: The future (was: 3.0.0.Final) > numberguess example does not deploy on tomcat > --------------------------------------------- > > Key: SEAMWICKET-10 > URL: https://issues.jboss.org/browse/SEAMWICKET-10 > Project: Seam for Apache Wicket > Issue Type: Bug > Affects Versions: 1.0.0.Beta1 > Environment: Tomcat 6.0.18 > JDK 5 update 16 > Reporter: Jozef Hartinger > Assignee: Clint Popetz > Fix For: The future > > > Application throws the following exception during deployment: > Apr 24, 2009 10:45:39 AM org.apache.catalina.core.StandardContext filterStart > SEVERE: Exception starting filter wicket.numberguess-example > java.lang.NoClassDefFoundError: org/jboss/webbeans/manager/api/WebBeansManager > at org.jboss.webbeans.wicket.WebBeansApplication.<init>(WebBeansApplication.java:37) > at org.jboss.webbeans.examples.wicket.SampleApplication.<init>(SampleApplication.java:5) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:513) > at java.lang.Class.newInstance0(Class.java:355) > at java.lang.Class.newInstance(Class.java:308) > at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:72) > at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:49) > at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:552) > at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275) > at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397) > at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:108) > at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3709) > at org.apache.catalina.core.StandardContext.start(StandardContext.java:4363) > at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) > at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) > at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) > at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:830) > at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:719) > at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490) > at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1217) > at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:293) > at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) > at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1337) > at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1601) > at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610) > at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1590) > at java.lang.Thread.run(Thread.java:619) > Caused by: java.lang.ClassNotFoundException: org.jboss.webbeans.manager.api.WebBeansManager > at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1387) > at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1233) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) > ... 30 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
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 March 2011