[
https://issues.jboss.org/browse/WELDRAD-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602047#comment-12602047
]
Gerry Matte commented on WELDRAD-29:
------------------------------------
Today I was able to create the same example using maven in a dos window as
described at http://seamframework.org/Documentation/CDIQuickstartForMavenUsers
I deployed the webapp using maven not from within eclipse.
Everything worked fine.
I see that the archetype version that is referenced when using the dos maven
method is 1.0.1.CR1 which I am able to see when using Nexus to view the Jboss
community repository.
To successfully deploy the webapp I must use the dos maven command mvn package
jboss:harddeploy
Attempting to import the project into eclipse and deploying from there does not
work at all.
The eclipse errors occurred when I used version 1.0.1.CR2 of the archetype -
which was the only choice I could see when using the JBoss Tool.
Today I also attempted to recreate the problem within a new eclipse project. A
different set of errors occurred causing me to wonder if I've somehow tapped
into a development trunk where a developer is actively changing the archetype
as part of testing .....
> circular injection and target unreachable exception for generated webapp
> using maven archetype jboss-javaee6-webapp
> --------------------------------------------------------------------------------------------------------------------
>
> Key: WELDRAD-29
> URL: https://issues.jboss.org/browse/WELDRAD-29
> Project: Weld Archetypes
> Issue Type: Bug
> Components: javaee6-webapp
> Affects Versions: javaee6-webapp-1.0.1.Beta3
> Environment: Windows 7 x64, Java 1.6.0_24 x64, Jboss Developer 4,
> Maven 3.0.3, JBoss AS 6.0.0.Final, SEAM 3.0.0.Final Bundle
> Reporter: Gerry Matte
> Labels: archetype, weld
> Attachments: pom.xml
>
>
> Within JbDeveloper I created a new Maven project and selected groupId
> org.jboss.weld.archetypes, ArtifactId jboss-javaee6-webapp version 1.0.1.CR2
> to create a new eclipse project(package name and project name are
> irrelevant). I then located the default-ds.xml file and marked it as
> deployable. I then used Jboss Runtime server - clean to republish the
> project and then I started the server.
> There were no errors and only a few warnings.
> When I completed the data form and clicked the submit button, an exception
> was thrown as detailed in the error log below:
> 16:39:29,456 INFO [org.jboss.ejb3.session.SessionSpecContainer] Starting
> jboss.j2ee:jar=weldTest.war,name=SeedDataImporter,service=EJB3
> 16:39:29,456 WARN [org.jboss.ejb3.session.SessionSpecContainer]
> EJBTHREE-2126: container
> jboss.j2ee:jar=weldTest.war,name=SeedDataImporter,service=EJB3 does not
> verify the businessObjectFactory
> 16:39:29,456 INFO [org.jboss.ejb3.EJBContainer] STARTED EJB:
> foo.data.SeedDataImporter ejbName: SeedDataImporter
> 16:39:29,472 WARN [org.jboss.ejb3.TimerServiceContainer] EJBTHREE-2193:
> using deprecated TimerServiceFactory for restoring timers
> 16:39:29,987 WARN [org.jboss.weld.Bean] WELD-000018 Executing producer field
> or method [method] @Produces public
> foo.test.MemberRegistrationTest.produceLog(InjectionPoint) on incomplete
> declaring bean Managed Bean [class foo.test.MemberRegistrationTest] with
> qualifiers [@Any @Default] due to circular injection
> 16:39:30,018 INFO
> [org.jboss.ejb3.nointerface.impl.jndi.AbstractNoInterfaceViewBinder] Binding
> the following entry in Global JNDI for bean:SeedDataImporter
> SeedDataImporter/no-interface -> EJB3.1 no-interface view
> 16:39:30,065 INFO [org.apache.coyote.http11.Http11Protocol] Starting Coyote
> HTTP/1.1 on http-localhost%2F127.0.0.1-8080
> 16:39:30,080 INFO [org.apache.coyote.ajp.AjpProtocol] Starting Coyote
> AJP/1.3 on ajp-localhost%2F127.0.0.1-8009
> 16:39:30,080 INFO [org.jboss.bootstrap.impl.base.server.AbstractServer]
> JBossAS [6.0.0.Final "Neo"] Started in 1m:6s:248ms
> 16:40:16,075 WARN [org.jboss.weld.Bean] WELD-000018 Executing producer field
> or method [method] @Produces public
> foo.test.MemberRegistrationTest.produceLog(InjectionPoint) on incomplete
> declaring bean Managed Bean [class foo.test.MemberRegistrationTest] with
> qualifiers [@Any @Default] due to circular injection
> 16:40:44,725 WARN [org.jboss.weld.Bean] WELD-000018 Executing producer field
> or method [method] @Produces public
> foo.test.MemberRegistrationTest.produceLog(InjectionPoint) on incomplete
> declaring bean Managed Bean [class foo.test.MemberRegistrationTest] with
> qualifiers [@Any @Default] due to circular injection
> 16:40:44,731 WARNING [javax.enterprise.resource.webcontainer.jsf.lifecycle]
> /index.xhtml @21,75 value="#{newMember.name}": Target Unreachable, identifier
> 'newMember' resolved to null: javax.el.PropertyNotFoundException:
> /index.xhtml @21,75 value="#{newMember.name}": Target Unreachable, identifier
> 'newMember' resolved to null
> at
> com.sun.faces.facelets.el.TagValueExpression.getType(TagValueExpression.java:97)
> [:2.0.3-]
> at
> com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getConvertedValue(HtmlBasicInputRenderer.java:91)
> [:2.0.3-]
> at javax.faces.component.UIInput.getConvertedValue(UIInput.java:1023)
> [:2.0.3-]
> NOTE: the Bug form would not allow me to specify the version 1.0.1.CR2 so
> it's possible that I used an artifact that is not supposed to be used.
> However it's the only version of jboss-javaee6-webapp that I could find.
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues
