August 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELDX-42) mvn install in extensions/trunk/ fails

by Martin Gencur (JIRA)

mvn install in extensions/trunk/ fails -------------------------------------- Key: WELDX-42 URL: https://jira.jboss.org/jira/browse/WELDX-42 Project: Weld Extensions Issue Type: Bug Reporter: Martin Gencur When I check-out http://anonsvn.jboss.org/repos/weld/extensions/trunk/ and then run "mvn install" in the root directory, maven outputs an error during compilation phase: (weld-se in the paths below means trunk/ ) [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] Error building POM (may not be this project's POM). Project ID: org.jboss.weld.servlet:weld-servlet-int POM Location: /home/mgencur/Java/Weld/weld-se/servlet/int/pom.xml Validation Messages: [0] 'dependencies.dependency.version' is missing for org.jboss.weld:weld-logging Reason: Failed to validate POM for project org.jboss.weld.servlet:weld-servlet-int at /home/mgencur/Java/Weld/weld-se/servlet/int/pom.xml [INFO] ------------------------------------------------------------------------ [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Failed to validate POM for project org.jboss.weld.servlet:weld-servlet-int at /home/mgencur/Java/Weld/weld-se/servlet/int/pom.xml at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.project.InvalidProjectModelException: Failed to validate POM for project org.jboss.weld.servlet:weld-servlet-int at /home/mgencur/Java/Weld/weld-se/servlet/int/pom.xml at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:1107) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:877) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:505) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:197) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:534) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:534) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) ... 11 more -- 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

13 years, 8 months

4
8
0 / 0

[JBoss JIRA] Closed: (WELDSERVLET-19) Bind Manager to java:app/Manager on Jetty

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELDSERVLET-19?page=com.atlassian.jira.plug... ] Pete Muir closed WELDSERVLET-19. -------------------------------- > Bind Manager to java:app/Manager on Jetty > ----------------------------------------- > > Key: WELDSERVLET-19 > URL: https://jira.jboss.org/browse/WELDSERVLET-19 > Project: Weld Servlet > Issue Type: Feature Request > Reporter: Pete Muir > Assignee: Dan Allen > Fix For: 1.0.0.CR2 > > Attachments: ManagerReferenceFactory.java > > -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (WELDSERVLET-26) ServletWebBeanDiscovery should scan /META-INF/beans.xml

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELDSERVLET-26?page=com.atlassian.jira.plug... ] Pete Muir closed WELDSERVLET-26. -------------------------------- > ServletWebBeanDiscovery should scan /META-INF/beans.xml > ------------------------------------------------------- > > Key: WELDSERVLET-26 > URL: https://jira.jboss.org/browse/WELDSERVLET-26 > Project: Weld Servlet > Issue Type: Bug > Affects Versions: 1.0.0.CR1 > Reporter: Dan Allen > Assignee: Dan Allen > Fix For: 1.0.0.CR2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > ServletWebBeanDiscovery.scan() looks for beans.xml rather than /META-INF/beans.xml. This should be fixed to match the spec. The intro to chapter 11 reads: > Bean classes must be deployed in an EAR, WAR, EJB-JAR or JAR archive or directory in the application classpath that has a file named beans.xml in the metadata directory (META-INF, or WEB-INF in the case of a WAR). If a bean is deployed to a location that is not in the application classpath, or does not contain a file named beans.xml in the metadata directory, it will not be discovered by the container. -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (WELDSERVLET-18) Fix war:inplace target for Tomcat for numberguess example

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELDSERVLET-18?page=com.atlassian.jira.plug... ] Pete Muir closed WELDSERVLET-18. -------------------------------- > Fix war:inplace target for Tomcat for numberguess example > --------------------------------------------------------- > > Key: WELDSERVLET-18 > URL: https://jira.jboss.org/browse/WELDSERVLET-18 > Project: Weld Servlet > Issue Type: Feature Request > Reporter: Pete Muir > Assignee: Dan Allen > Fix For: 1.0.0.CR2 > > -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (WELDX-47) BeanManager ELResolver should work even if JSF loads before Weld

by Dan Allen (JIRA)

BeanManager ELResolver should work even if JSF loads before Weld ---------------------------------------------------------------- Key: WELDX-47 URL: https://jira.jboss.org/jira/browse/WELDX-47 Project: Weld Extensions Issue Type: Feature Request Components: Servlet Containers Affects Versions: Servlet Containers 1.0.0.CR1 Reporter: Dan Allen Assignee: Dan Allen If the JSF listener starts before the Weld listener, then the BeanManager ELResolver was not making it into the JSF composite resolver chain. The problem is JSF impl specific, but we should safeguard against this problem anyway and use a forwarding ELResolver to accommodate. All details are provided in the linked issue WELDX-44, which is where the problem was discovered. -- 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

13 years, 8 months

2
2
0 / 0

[JBoss JIRA] Updated: (WELD-1) Add tests for multiple wars in an ear

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELD-1?page=com.atlassian.jira.plugin.syste... ] Pete Muir updated WELD-1: ------------------------- Fix Version/s: 1.1.0.BETA2 (was: 1.1.0.BETA1) > Add tests for multiple wars in an ear > ------------------------------------- > > Key: WELD-1 > URL: https://jira.jboss.org/browse/WELD-1 > Project: Weld > Issue Type: Feature Request > Components: Bootstrap and Metamodel API, Scopes & Contexts > Reporter: Pete Muir > Fix For: 1.1.0.BETA2 > > -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (WELD-59) Clustered WebBeans, no support for sessionscoped (and higher) replication

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELD-59?page=com.atlassian.jira.plugin.syst... ] Pete Muir updated WELD-59: -------------------------- Fix Version/s: 1.1.0.BETA2 (was: 1.1.0.BETA1) > Clustered WebBeans, no support for sessionscoped (and higher) replication > ------------------------------------------------------------------------- > > Key: WELD-59 > URL: https://jira.jboss.org/browse/WELD-59 > Project: Weld > Issue Type: Bug > Components: Scopes & Contexts > Affects Versions: 1.0.0.PREVIEW1 > Environment: JBoss AS 5.1 + JDK 6 > Reporter: John Ament > Fix For: 1.1.0.BETA2 > > Attachments: ClusteredWebBeansTestApp.zip, ClusteredWebBeansTestApp.zip > > > From what I can tell, this is what happens. > Assume you have a 2 node environment w/ apache httpd + mod_jk in front of the jboss servers, used to limit servers exposed + a loadbalancer (F5 ASM) in front of those. The apache servers are only configured to talk to one jboss server each (httpd + jboss are on same box, they only talk to the local client). the f5 serving the initial request is configured for pure round robin (no cookie persistence) and as a result request 1 could go to server 1 and then request 2 goes to server 2. > Now assume that the two jboss servers are clustered together, the EJBs are clustered and have a cache policy (based on the JBoss annotations). They only have local interfaces. In addition, there are some classes that are only POJOs; but they sit in the ejb module. Based on what's happening these objects should be replicated as part of the HTTP session state. > A few problems seem to occur when the request goes to the second server after the first request goes to the first server. > 1. References to the resources required by the EJBs are not injected in the second server. This includes members decorated @Resource or @PersistenceContext > 2. References to EJBs required at the view level are not restored. > In addition, concurrent modification exceptions seem to be more likely when deployed like this, resulting in having to downgrade EJBs to POJOs in order to remain stateful. -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (WELD-80) Passivation of stateful session beans results in a loss of reference to injected object

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELD-80?page=com.atlassian.jira.plugin.syst... ] Pete Muir updated WELD-80: -------------------------- Fix Version/s: 1.1.0.BETA2 (was: 1.1.0.BETA1) > Passivation of stateful session beans results in a loss of reference to injected object > --------------------------------------------------------------------------------------- > > Key: WELD-80 > URL: https://jira.jboss.org/browse/WELD-80 > Project: Weld > Issue Type: Bug > Components: Scopes & Contexts > Environment: JBoss AS 5.1 > Reporter: John Ament > Fix For: 1.1.0.BETA2 > > Attachments: statefulpassivate.zip > > > See forum post -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (WELD-547) Javadoc for InjectionServices

by Kabir Khan (JIRA)

Javadoc for InjectionServices ----------------------------- Key: WELD-547 URL: https://jira.jboss.org/browse/WELD-547 Project: Weld Issue Type: Feature Request Reporter: Kabir Khan Fix For: 1.0.2.CR1 -- 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

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-281) add ForwardingELResolver to SPI

by Dan Allen (JIRA)

add ForwardingELResolver to SPI ------------------------------- Key: WELD-281 URL: https://jira.jboss.org/jira/browse/WELD-281 Project: Weld Issue Type: Feature Request Components: Web Tier integration (JSF, JSP, EL and Servlet) Affects Versions: 1.0.0.CR1 Reporter: Dan Allen Assignee: Pete Muir Priority: Minor Fix For: 1.1.0.BETA1 Move ForwardingELResolver, which appears in both servlet-int and weld-int, to the SPI. -- 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

13 years, 8 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues August 2010