[JBoss JIRA] Created: (SOLDER-116) BeanBuilder create beans that don't support InjectionPoint injection
by Antoine Sabot-Durand (JIRA)
BeanBuilder create beans that don't support InjectionPoint injection
--------------------------------------------------------------------
Key: SOLDER-116
URL: https://issues.jboss.org/browse/SOLDER-116
Project: Seam Solder
Issue Type: Bug
Components: Builders
Affects Versions: 3.0.0.Final
Environment: MacOS X 10.7 (apple jdk 6) with Arquillian and weld-ee-embedded-1.1 container or JBoss AS 7
Reporter: Antoine Sabot-Durand
Priority: Critical
I wrote a bean like this one :
{code:java}
@MyQualifier
public class MyBean {
@Inject
InjectionPoint ip;
public String saySomething() {
String value = "";
if (ip != null)
value = ip.getAnnotated().getAnnotation(MyQualifier.class).value();
return "Hello CDI World " + value;
}
}
{code}
with MyQualifier being a simple qualifier with a non binding parameter value.
And I wrote an extension which register another version of this bean without Qualifier
{code:java}
public class MyExtension implements Extension {
@SuppressWarnings({ "unchecked", "rawtypes" })
public void afterBeanDiscovery(@Observes AfterBeanDiscovery abd, BeanManager bm) {
AnnotatedTypeBuilder annoBuilder = new AnnotatedTypeBuilder().readFromType(MyBean.class).removeFromClass(
MyQualifier.class);
AnnotatedType myAnnotatedType = annoBuilder.create();
BeanBuilder beanBuilder = new BeanBuilder(bm).readFromType(myAnnotatedType);
abd.addBean(beanBuilder.create());
}
}
{code}
When bootstrapping Weld I have the following exception :
{noformat}
org.jboss.weld.exceptions.DefinitionException: WELD-001405 Cannot inject [field] @Inject org.jboss.solderbug.MyBean.ip in a class which isnt a bean
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:280)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:139)
at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:389)
at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:371)
at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:390)
at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.TestContainer.startContainer(TestContainer.java:257)
at org.jboss.arquillian.container.weld.ee.embedded_1_1.WeldEEMockContainer.deploy(WeldEEMockContainer.java:98)
...
{noformat}
If I comment the @Inject line in the bean everything is fine and I can use both version of the bean (with or without qualifier)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (SEAMPERSIST-63) Query Interface
by Frank Cornelis (JIRA)
Query Interface
---------------
Key: SEAMPERSIST-63
URL: https://issues.jboss.org/browse/SEAMPERSIST-63
Project: Seam Persistence
Issue Type: Feature Request
Reporter: Frank Cornelis
Priority: Minor
The query interface allows for easy usage of JPA queries. Basically you annotate an interface as follows:
{code}
public interface QueryInterface {
@QueryMethod("person.query.all")
List<Person> getAll();
@QueryMethod("person.select.by.name")
Person getPersonByName(@QueryParam("name") String name);
@QueryMethod(value = "person.select.by.name", nullable = true)
Person findPersonByName(@QueryParam("name") String name);
@QueryMethod("person.query.all")
Query getAllQuery();
@QueryMethod(query = "SELECT COUNT(*) FROM Person")
Long countAll();
}
{code}
Using some inject QueryInterfaceFactory you can get a proxy on this interface that will interpret the annotations towards JPA queries. See attached patch for a basic implementation.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] (SEAMWICKET-48) cannot deploy numberguess example
by Tomas Remes (Created) (JIRA)
cannot deploy numberguess example
---------------------------------
Key: SEAMWICKET-48
URL: https://issues.jboss.org/browse/SEAMWICKET-48
Project: Seam for Apache Wicket
Issue Type: Bug
Affects Versions: 3.1.0.Beta4
Reporter: Tomas Remes
Fix For: 3.1.0.Beta5
cannot deploy to AS7 due to:
ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.deployment.unit."wicket-numberguess.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."wicket-numberguess.war".WeldService: 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.solder.el.ELContextProducer.createELContext()], Producer Method [ELContext] with qualifiers [@Any @Default] declared as [[method] @Produces org.jboss.seam.solder.el.ELContextProducer.createELContext()]]]
at org.jboss.as.weld.services.WeldService.start(WeldService.java:96)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
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.solder.el.ELContextProducer.createELContext()], Producer Method [ELContext] with qualifiers [@Any @Default] declared as [[method] @Produces org.jboss.seam.solder.el.ELContextProducer.createELContext()]]]
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:274)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:106)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:129)
at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:351)
at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:336)
at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:404)
at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82)
at org.jboss.as.weld.services.WeldService.start(WeldService.java:89)
... 5 more
--
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
14 years, 4 months
[JBoss JIRA] Created: (SEAMSECURITY-75) security-openid-rp/op examples fail on AS7 with 0x704: I/O transport error
by Marek Schmidt (JIRA)
security-openid-rp/op examples fail on AS7 with 0x704: I/O transport error
--------------------------------------------------------------------------
Key: SEAMSECURITY-75
URL: https://issues.jboss.org/browse/SEAMSECURITY-75
Project: Seam Security
Issue Type: Bug
Environment: jboss-7.0.0.Beta4-SNAPSHOT, build 1199
Reporter: Marek Schmidt
Fix For: Future
Attachments: server.log
The openid examples fail on AS7 with the following HTTP 400 error. Note that the steps to reproduce are the same SEAMSECURITY-67, but this is a different issue, as this is a different error message and also occurs with OpenID4Java 0.9.5
{quote}
HTTP Status 400 - 0x704: I/O transport error:
type Status report
message 0x704: I/O transport error:
description The request sent by the client was syntactically incorrect (0x704: I/O transport error: ).
{quote}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (SEAMFACES-169) Seam Faces does not work with OWB
by Thomas Andraschko (JIRA)
Seam Faces does not work with OWB
---------------------------------
Key: SEAMFACES-169
URL: https://issues.jboss.org/browse/SEAMFACES-169
Project: Seam Faces
Issue Type: Bug
Components: Build & Distribution, CDI Integration
Affects Versions: 3.0.1
Environment: Tomcat 7, OWB 1.1.0, MyFaces 2.0.5 or 2.1.0, SeamFaces 3.0.1, SeamPersistence 3.0.0, SeamXmlConfig 3.0.0
Reporter: Thomas Andraschko
SeamFaces does not work with OWB.
Following exception occurs:
07.06.2011 13:25:17 org.apache.myfaces.webapp.AbstractFacesInitializer initFaces
SCHWERWIEGEND: An error occured while initializing MyFaces: null
java.util.NoSuchElementException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:796)
at java.util.HashMap$KeyIterator.next(HashMap.java:828)
at org.jboss.seam.faces.event.AbstractListener.getListeners(AbstractListener.java:25)
at org.jboss.seam.faces.event.DelegatingSystemEventListener.getEventListeners(DelegatingSystemEventListener.java:43)
at org.jboss.seam.faces.event.DelegatingSystemEventListener.processEvent(DelegatingSystemEventListener.java:34)
at javax.faces.event.SystemEvent.processListener(SystemEvent.java:43)
at org.apache.myfaces.application.ApplicationImpl._traverseListenerList(ApplicationImpl.java:2105)
at org.apache.myfaces.application.ApplicationImpl.access$000(ApplicationImpl.java:118)
at org.apache.myfaces.application.ApplicationImpl$SystemListenerEntry.publish(ApplicationImpl.java:2292)
at org.apache.myfaces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:537)
at javax.faces.application.ApplicationWrapper.publishEvent(ApplicationWrapper.java:329)
at org.apache.myfaces.webapp.AbstractFacesInitializer._dispatchApplicationEvent(AbstractFacesInitializer.java:248)
at org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:140)
at org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:111)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4521)
at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5004)
at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:4999)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
07.06.2011 13:25:17 org.apache.catalina.core.StandardContext startInternal
SCHWERWIEGEND: Error listenerStart
07.06.2011 13:25:17 org.apache.catalina.core.StandardContext startInternal
SCHWERWIEGEND: Context [/my-webapp] startup failed due to previous errors
07.06.2011 13:25:17 org.apache.webbeans.web.lifecycle.WebContainerLifecycle afterStopApplication
INFO: OpenWebBeans Container was stopped for context path, [/my-webapp]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (SEAMFACES-28) ObjectConverter and EntityConverter
by Pete Muir (JIRA)
ObjectConverter and EntityConverter
-----------------------------------
Key: SEAMFACES-28
URL: https://jira.jboss.org/browse/SEAMFACES-28
Project: Seam Faces
Issue Type: Feature Request
Components: Transactions & Persistence, Validation & Conversion
Reporter: Pete Muir
Priority: Critical
Given
class Foo {
Bar bar;
// Getters and setters
List<Bar> bars;
// Getters and setters
}
<h:selectOneMenu value="#{foo.bar}" >
<f:selectItems value="#{foo.bars}" var="bar" itemLabel="#{bar.label}" itemValue="#{bar}" />
<s:convertEntity /> || <s:convertObject />
</h:selectOneMenu>
I want to be able to have my setter/getter reference an object and not write the boilerplate for converting to/from a string.
I also want to reference a managed entity, and have that managed entity set back into the setter so I can see the changes updated in the database with no boilerplate, and avoid LIEs.
--
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
14 years, 5 months