February 2012 - seam-issues - Jboss List Archives

[JBoss JIRA] (SOLDER-316) Seam Config throws DeploymentException: WELD-001409 Ambiguous dependencies

by Hendy Irawan (JIRA)

Hendy Irawan created SOLDER-316: ----------------------------------- Summary: Seam Config throws DeploymentException: WELD-001409 Ambiguous dependencies Key: SOLDER-316 URL: https://issues.jboss.org/browse/SOLDER-316 Project: Solder Issue Type: Bug Components: XML Configuration Affects Versions: 3.1.0.Beta2 Environment: Seam Config 3.1.0.Beta2, JBoss AS 7.1.0.CR1b Reporter: Hendy Irawan Simply including seam-config-xml causes {code} Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001409 Ambiguous dependencies for type [ELContext] with qualifiers [@Default] at injection point [[parameter 1] of [constructor] @Inject public org.jboss.seam.solder.el.Expressions(ELContext, ExpressionFactory)]. Possible dependencies [[Producer Method [ELContext] with qualifiers [@Any @Default] declared as [[method] @Produces org.jboss.seam.solder.el.ELContextProducer.createELContext()], Producer Method [ELContext] with qualifiers [@Any @Default] declared as [[method] @Produces org.jboss.solder.el.ELContextProducer.createELContext()]]] at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:277) {code} The webapp works fine without the seam-config-xml dependency. With a configuration file, the problem above persists, and there's another problem with ambiguous dependency on our own beans. Sample configuration: (in src/main/resources/META-INF/beans.xml ) {code} <persistence:ProfilePhotoRepository> <s:modifies /> <s:Named /> <s:ApplicationScoped /> <persistence:uploadPath>/home/ceefour/public_html/satukancinta-media </persistence:uploadPath> <persistence:publicUrl>http://ceefour.annafi/satukancinta-media/ </persistence:publicUrl> </persistence:ProfilePhotoRepository> {code} throws: {code} org.jboss.weld.exceptions.DeploymentException: WELD-001409 Ambiguous dependencies for type [ProfilePhotoRepository] with qualifiers [@Default] at injection point [[field] @Inject com.satukancinta.ui.admin.UserShowAdmin.photoRepo]. Possible dependencies [[Managed Bean [class com.satukancinta.persistence.ProfilePhotoRepository] with qualifiers [@Any @Default], Managed Bean [class com.satukancinta.persistence.ProfilePhotoRepository] with qualifiers [@Any @Default]]] at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:277) {code} I'm unable to use seam-config-xml at all. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBSEAM-4637) Seam does not work with JSF 2.0 faces-config.xml

by Ryan Nideffer (JIRA)

Seam does not work with JSF 2.0 faces-config.xml ------------------------------------------------ Key: JBSEAM-4637 URL: https://jira.jboss.org/jira/browse/JBSEAM-4637 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.2.1.CR1 Reporter: Ryan Nideffer I am attempting to use JSF 2.0 in my Seam application for, among other benefits, composite components. I am able to upgrade the jsf-api.jar and jsf-impl.jar, remove jsf-facelets.jar and my application functions fine, however I am still running in JSF 1.2 mode due to this faces-config.xml: <faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd"> <view-handler>com.sun.facelets.FaceletViewHandler</view-handler> According to thread comments from a Mojarra developer and the Release Notes for Mojarra 2, all thats needed is to remove the view-handler and reference v2.0 in faces-config. http://forums.java.net/jive/message.jspa?messageID=373539 https://javaserverfaces.dev.java.net/nonav/rlnotes/2.0.1/releasenotes.html As soon as I do this though, I get the following exception when my application is deployed: 2010-04-16 11:24:18,249 INFO [javax.enterprise.resource.webcontainer.jsf.config] (Thread-2) Unsanitized stacktrace from failed start... javax.faces.view.facelets.FaceletException: Must have a Constructor that takes in a ComponentConfig at com.sun.faces.facelets.tag.AbstractTagLibrary$UserComponentHandlerFactory.<init>(AbstractTagLibrary.java:289) ... Caused by: java.lang.NoSuchMethodException: org.jboss.seam.ui.handler.CommandButtonParameterComponentHandler.<init>(javax.faces.view.facelets.ComponentConfig) at java.lang.Class.getConstructor0(Class.java:2706) According to Dan Allen, Seam 2 and JSF 2 work together beautifully: http://seamframework.org/Documentation/DoesSeamWorkWithJSF2 -- 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

12 years, 3 months

7
17
0 / 0

[JBoss JIRA] (SEAM-132) Seam Config throws DeploymentException: WELD-001409 Ambiguous dependencies

by Hendy Irawan (JIRA)

Hendy Irawan created SEAM-132: --------------------------------- Summary: Seam Config throws DeploymentException: WELD-001409 Ambiguous dependencies Key: SEAM-132 URL: https://issues.jboss.org/browse/SEAM-132 Project: Seam 3 Distribution Issue Type: Bug Components: Common Dependencies Affects Versions: 3.1.0.Final Environment: Seam Config 3.1.0.Beta2, JBoss AS 7.1.0.CR1b Reporter: Hendy Irawan I can't find the project for Seam Config, so I'm putting it here. Simply including seam-config-xml causes {code} Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001409 Ambiguous dependencies for type [ELContext] with qualifiers [@Default] at injection point [[parameter 1] of [constructor] @Inject public org.jboss.seam.solder.el.Expressions(ELContext, ExpressionFactory)]. Possible dependencies [[Producer Method [ELContext] with qualifiers [@Any @Default] declared as [[method] @Produces org.jboss.seam.solder.el.ELContextProducer.createELContext()], Producer Method [ELContext] with qualifiers [@Any @Default] declared as [[method] @Produces org.jboss.solder.el.ELContextProducer.createELContext()]]] at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:277) {code} The webapp works fine without the seam-config-xml dependency. Sample configuration: (in src/main/resources/META-INF/beans.xml ) {code} <persistence:ProfilePhotoRepository> <s:modifies /> <s:Named /> <s:ApplicationScoped /> <persistence:uploadPath>/home/ceefour/public_html/satukancinta-media </persistence:uploadPath> <persistence:publicUrl>http://ceefour.annafi/satukancinta-media/ </persistence:publicUrl> </persistence:ProfilePhotoRepository> {code} throws: {code} org.jboss.weld.exceptions.DeploymentException: WELD-001409 Ambiguous dependencies for type [ProfilePhotoRepository] with qualifiers [@Default] at injection point [[field] @Inject com.satukancinta.ui.admin.UserShowAdmin.photoRepo]. Possible dependencies [[Managed Bean [class com.satukancinta.persistence.ProfilePhotoRepository] with qualifiers [@Any @Default], Managed Bean [class com.satukancinta.persistence.ProfilePhotoRepository] with qualifiers [@Any @Default]]] at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:277) {code} I'm unable to use seam-config-xml at all. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
2
0 / 0

[JBoss JIRA] (JBSEAM-4899) Rendering multiple <p:piechart> using seam-pdf causes the data to overlap

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-4899?page=com.atlassian.jira.plugi... ] Marek Novotny updated JBSEAM-4899: ---------------------------------- Summary: Rendering multiple <p:piechart> using seam-pdf causes the data to overlap (was: CLONE - Rendering multiple <p:piechart> using seam-pdf causes the data to overlap) Environment: (was: EAP 5.1.2 Seam 2.2.4.EAP5) > Rendering multiple <p:piechart> using seam-pdf causes the data to overlap > ------------------------------------------------------------------------- > > Key: JBSEAM-4899 > URL: https://issues.jboss.org/browse/JBSEAM-4899 > Project: Seam 2 > Issue Type: Bug > Components: PDF > Affects Versions: 2.2.2.Final, 2.3.0.ALPHA > Reporter: Ilia Vassilev > Assignee: Marek Novotny > Fix For: 2.3.0.Final > > Attachments: files.tar.gz > > > If <p:piechart> is included in <ui:repeat>, the series from the first iteration is accumulated with the second and so on. A test case is attached [1]. > [1] files.tar.gz -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-4899) CLONE - Rendering multiple <p:piechart> using seam-pdf causes the data to overlap

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-4899?page=com.atlassian.jira.plugi... ] Marek Novotny moved JBPAPP-8039 to JBSEAM-4899: ----------------------------------------------- Project: Seam 2 (was: JBoss Enterprise Application Platform) Key: JBSEAM-4899 (was: JBPAPP-8039) Affects Version/s: 2.3.0.ALPHA 2.2.2.Final (was: EAP_EWP 5.1.2) Component/s: PDF (was: Seam2) Security: (was: Public) Fix Version/s: 2.3.0.Final (was: EAP_EWP 5.1.3) Docs QE Status: (was: NEW) > CLONE - Rendering multiple <p:piechart> using seam-pdf causes the data to overlap > --------------------------------------------------------------------------------- > > Key: JBSEAM-4899 > URL: https://issues.jboss.org/browse/JBSEAM-4899 > Project: Seam 2 > Issue Type: Bug > Components: PDF > Affects Versions: 2.3.0.ALPHA, 2.2.2.Final > Environment: EAP 5.1.2 > Seam 2.2.4.EAP5 > Reporter: Ilia Vassilev > Assignee: Marek Novotny > Fix For: 2.3.0.Final > > Attachments: files.tar.gz > > > If <p:piechart> is included in <ui:repeat>, the series from the first iteration is accumulated with the second and so on. A test case is attached [1]. > [1] files.tar.gz -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SEAMSECURITY-143) org.jboss.seam.security.management.picketlink.JpaIdentityStore.removeRelationship() ignores a parameter 'relationshipName'

by Aleftina Plotnikov (JIRA)

Aleftina Plotnikov created SEAMSECURITY-143: ----------------------------------------------- Summary: org.jboss.seam.security.management.picketlink.JpaIdentityStore.removeRelationship() ignores a parameter 'relationshipName' Key: SEAMSECURITY-143 URL: https://issues.jboss.org/browse/SEAMSECURITY-143 Project: Seam Security Issue Type: Bug Affects Versions: 3.1.0.CR1 Environment: jboss-as-7.0.2.Final, jboss-as-7.1.0.CR1b Reporter: Aleftina Plotnikov Affected Version is actually 3.1.0.Final When I do a call org.picketlink.idm.api.IdentitySession.getRoleManager().removeRole(role); an exception "javax.persistence.NonUniqueResultException: result returns more than one elements" is thrown. It happens when a user is having more than one role in database; and the role name is the only difference, ie FROM_IDENTITY_ID, TO_IDENTITY_ID and RELATIONSHIP_TYPE_ID are the same; in other words the User is playing more than one role in the same Group. When debugging I found that a parameter 'relationshipName', role name in my case, is ignored in a method org.jboss.seam.security.management.picketlink.JpaIdentityStore.removeRelationship(), so it's not a part of JPA criteria. Similar issue I found, but with a different version affected: https://issues.jboss.org/browse/SEAMSECURITY-141 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMPERSIST-59) Implement EntityHome from Seam 2

by Sheng Gu (JIRA)

Implement EntityHome from Seam 2 -------------------------------- Key: SEAMPERSIST-59 URL: https://issues.jboss.org/browse/SEAMPERSIST-59 Project: Seam Persistence Issue Type: Feature Request Affects Versions: 3.0.0.Final Environment: Upgrading to Seam 3 Reporter: Sheng Gu Fix For: 3.0.1.CR1 Migrating Seam 2 to Seam 3 is very hard to find a replacement for Seam 2's EntityHome. Also it looks that EntityHome is very important for Seam persist. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

5
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2012