[weld-issues] [JBoss JIRA] (WELD-398) Unable to run translator example with settings for cluster
[ https://issues.jboss.org/browse/WELD-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12671921#comment-12671921 ] Marek Schmidt commented on WELD-398: Clustered translator now works on AS7, so I believe this issue can now be closed. Unable to run translator example with settings for cluster -- Key: WELD-398 URL: https://issues.jboss.org/browse/WELD-398 Project: Weld Issue Type: Task Components: Clustering, Examples Affects Versions: 1.0.0.GA Reporter: Martin Gencur Fix For: 1.2.0.Beta1 Attachments: jboss-server-log.txt, web-browser-report.txt When I try to go to http://localhost:8080/weld-translator after deploying the translator example to JBossAS 6.0.0.M1, exceptions are thrown both at server.log and web browser. The exception are attached as separated files. Steps to reproduce: 1) add distributable/ tag to web.xml as it's first tag (at WELD/examples/jsf/translator/war/src/main/webapp/WEB-INF/web.xml) 2) add this content to jboss.xml file at WELD/examples/jsf/translator/ejb/src/main/resources/META-INF/jboss.xml : ?xml version=1.0 encoding=UTF-8? jboss xmlns=http://www.jboss.com/xml/ns/javaee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://www.jboss.com/xml/ns/javaee jboss_5_0.xsd version=5.0 enterprise-beans session !-- stateless bean -- ejb-nameSentenceTranslator/ejb-name clusteredtrue/clustered /session session !-- stateful bean -- ejb-nameTranslatorControllerBean/ejb-name clusteredtrue/clustered /session /enterprise-beans /jboss 3) download jboss-6.0.0.M1 (for example from http://reports.qa.atl.jboss.com/release_tests/binaries/JBossAS/jboss-6.0.0.M1.zip) 4) unzip it twice to different folders 5) now you have to update both the JBoss AS instances with current version of WELD core (from WELD/core) 6) run the first instance from its bin directory: ./run.sh -c all -g DocsPartition -u 239.255.101.101 -b localhost -Djboss.messaging.ServerPeerID=1 -Djboss.service.binding.set=ports-default 7) run the second instance from its bin directory: ./run.sh -c all -g DocsPartition -u 239.255.101.101 -b localhost -Djboss.messaging.ServerPeerID=2 -Djboss.service.binding.set=ports-01 8) clean and build the application: run mvn clean package in examples/jsf/translator 9) copy resulting ear file (weld-numberguess.war) from translator/ear/target/ directory to serve/all/farm directory at first jbossAS instance 10) go to http://localhost:8080/weld-translator 11) now you can see both exception in server.log and web browser When i try to set clusteredfalse/clustered in jboss.xml, the application shows properly when I go to web browser. But then the application is not working in cluster (EJBs' state is not replicated between nodes of cluster). -- 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 ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-398) Unable to run translator example with settings for cluster
[ https://issues.jboss.org/browse/WELD-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ales Justin resolved WELD-398. -- Assignee: Marek Schmidt Resolution: Done Unable to run translator example with settings for cluster -- Key: WELD-398 URL: https://issues.jboss.org/browse/WELD-398 Project: Weld Issue Type: Task Components: Clustering, Examples Affects Versions: 1.0.0.GA Reporter: Martin Gencur Assignee: Marek Schmidt Fix For: 1.2.0.Beta1 Attachments: jboss-server-log.txt, web-browser-report.txt When I try to go to http://localhost:8080/weld-translator after deploying the translator example to JBossAS 6.0.0.M1, exceptions are thrown both at server.log and web browser. The exception are attached as separated files. Steps to reproduce: 1) add distributable/ tag to web.xml as it's first tag (at WELD/examples/jsf/translator/war/src/main/webapp/WEB-INF/web.xml) 2) add this content to jboss.xml file at WELD/examples/jsf/translator/ejb/src/main/resources/META-INF/jboss.xml : ?xml version=1.0 encoding=UTF-8? jboss xmlns=http://www.jboss.com/xml/ns/javaee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://www.jboss.com/xml/ns/javaee jboss_5_0.xsd version=5.0 enterprise-beans session !-- stateless bean -- ejb-nameSentenceTranslator/ejb-name clusteredtrue/clustered /session session !-- stateful bean -- ejb-nameTranslatorControllerBean/ejb-name clusteredtrue/clustered /session /enterprise-beans /jboss 3) download jboss-6.0.0.M1 (for example from http://reports.qa.atl.jboss.com/release_tests/binaries/JBossAS/jboss-6.0.0.M1.zip) 4) unzip it twice to different folders 5) now you have to update both the JBoss AS instances with current version of WELD core (from WELD/core) 6) run the first instance from its bin directory: ./run.sh -c all -g DocsPartition -u 239.255.101.101 -b localhost -Djboss.messaging.ServerPeerID=1 -Djboss.service.binding.set=ports-default 7) run the second instance from its bin directory: ./run.sh -c all -g DocsPartition -u 239.255.101.101 -b localhost -Djboss.messaging.ServerPeerID=2 -Djboss.service.binding.set=ports-01 8) clean and build the application: run mvn clean package in examples/jsf/translator 9) copy resulting ear file (weld-numberguess.war) from translator/ear/target/ directory to serve/all/farm directory at first jbossAS instance 10) go to http://localhost:8080/weld-translator 11) now you can see both exception in server.log and web browser When i try to set clusteredfalse/clustered in jboss.xml, the application shows properly when I go to web browser. But then the application is not working in cluster (EJBs' state is not replicated between nodes of cluster). -- 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 ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-815) Add some design time readable metadata to weld-*.jars for tooling
[ https://issues.jboss.org/browse/WELD-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ales Justin resolved WELD-815. -- Resolution: Won't Fix See CDI-113. Add some design time readable metadata to weld-*.jars for tooling - Key: WELD-815 URL: https://issues.jboss.org/browse/WELD-815 Project: Weld Issue Type: Feature Request Components: Tooling Reporter: Max Rydahl Andersen Assignee: Ales Justin Working on JBIDE-8017 it became obvious that it would be good if Weld (and other spec implementations) jars could say which services they implement (and optionally how) so tooling could validate and navigate based on the classpath. Opening this issue to not forget - suggested approach was to see if one could use the seam-beans.xml format (but under a different name, i.e. design-time-beans.xml) to help guide tooling. This is to include not only spec required services but also additonal ones as for example http://docs.jboss.org/weld/reference/1.1.0.CR1/en-US/html/contexts.html#d0e5515 -- 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 ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1062) Superclass of a modified AnnotatedType is ignored
[ https://issues.jboss.org/browse/WELD-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12671985#comment-12671985 ] Ales Justin commented on WELD-1062: --- * https://github.com/alesj/core/tree/weld-1062 Superclass of a modified AnnotatedType is ignored - Key: WELD-1062 URL: https://issues.jboss.org/browse/WELD-1062 Project: Weld Issue Type: Bug Affects Versions: 1.1.5.Final, 2.0.0.Alpha1 Reporter: Gert Palok Assignee: Ales Justin Attachments: annotatedtype-superclass.zip When modifying an AnnotatedType in ProcessAnnotatedType event, the resulting Bean instance will have Object as its superclass instead of the real superclass, causing inherited injection points to be ignored -- 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 ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-693) Add a way to get the active context easily
[ https://issues.jboss.org/browse/WELD-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12672013#comment-12672013 ] Pete Muir commented on WELD-693: What else would be injected? Add a way to get the active context easily -- Key: WELD-693 URL: https://issues.jboss.org/browse/WELD-693 Project: Weld Issue Type: Feature Request Components: Scopes Contexts Reporter: Pete Muir Fix For: TBC For example @Inject @Active ConversationContext ctx; which would inject null if there was no active context -- 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 ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1062) Superclass of a modified AnnotatedType is ignored
[
https://issues.jboss.org/browse/WELD-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12672117#comment-12672117
]
Gert Palok commented on WELD-1062:
--
Thanks!
In my project I copied WeldClassImpl and replaced relevant code with:
{code}
if (rawType.getSuperclass() != null) {
this.superclass = classTransformer.loadClass(rawType.getSuperclass());
} else if (modified) {
this.superclass = classTransformer.loadClass(Object.class);
} else {
this.superclass = null;
}
{code}
But since I couldn't get the tests running, I was unable to verify the fix
Superclass of a modified AnnotatedType is ignored
-
Key: WELD-1062
URL: https://issues.jboss.org/browse/WELD-1062
Project: Weld
Issue Type: Bug
Affects Versions: 1.1.5.Final, 2.0.0.Alpha1
Reporter: Gert Palok
Assignee: Ales Justin
Attachments: annotatedtype-superclass.zip
When modifying an AnnotatedType in ProcessAnnotatedType event, the resulting
Bean instance will have Object as its superclass instead of the real
superclass, causing inherited injection points to be ignored
--
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
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1062) Superclass of a modified AnnotatedType is ignored
[ https://issues.jboss.org/browse/WELD-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12672163#comment-12672163 ] Ales Justin commented on WELD-1062: --- But since I couldn't get the tests running, I was unable to verify the fix You over-complicated things. :-) See my test port, simply adjusted your test to run against Arquillian. I'm trying your patch / fix now. Superclass of a modified AnnotatedType is ignored - Key: WELD-1062 URL: https://issues.jboss.org/browse/WELD-1062 Project: Weld Issue Type: Bug Affects Versions: 1.1.5.Final, 2.0.0.Alpha1 Reporter: Gert Palok Assignee: Ales Justin Attachments: annotatedtype-superclass.zip When modifying an AnnotatedType in ProcessAnnotatedType event, the resulting Bean instance will have Object as its superclass instead of the real superclass, causing inherited injection points to be ignored -- 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 ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1062) Superclass of a modified AnnotatedType is ignored
[ https://issues.jboss.org/browse/WELD-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ales Justin resolved WELD-1062. --- Fix Version/s: 1.2.0.Beta1 Resolution: Done Superclass of a modified AnnotatedType is ignored - Key: WELD-1062 URL: https://issues.jboss.org/browse/WELD-1062 Project: Weld Issue Type: Bug Affects Versions: 1.1.5.Final, 2.0.0.Alpha1 Reporter: Gert Palok Assignee: Ales Justin Fix For: 1.2.0.Beta1 Attachments: annotatedtype-superclass.zip When modifying an AnnotatedType in ProcessAnnotatedType event, the resulting Bean instance will have Object as its superclass instead of the real superclass, causing inherited injection points to be ignored -- 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 ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1007) Weld SE startup fails.
[
https://issues.jboss.org/browse/WELD-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12672241#comment-12672241
]
Sam Corbett commented on WELD-1007:
---
Enabling trace output, the logging immediately preceding the exception is:
{code}
16:04:04,058 TRACE [org.jboss.modules] (MSC service thread 1-3) Finding class
org.jboss.as.weld.services.WeldService from Module org.jboss.logmanager:main
from local module loader @67d225a7 (roots:
/Users/sam/code/jboss-as-7.0.0.Final/modules)
16:04:04,058 TRACE [org.jboss.modules] (MSC service thread 1-3) Class
org.jboss.as.weld.services.WeldService not found from Module
org.jboss.logmanager:main from local module loader @67d225a7 (roots:
/Users/sam/code/jboss-as-7.0.0.Final/modules)
a dozen similar class not found messages
16:04:04,076 TRACE [org.jboss.modules] (MSC service thread 1-3) Finding class
org.jboss.weld.introspector.jlr.WeldClassImpl from Module
org.jboss.logmanager:main from local module loader @67d225a7 (roots:
/Users/sam/code/jboss-as-7.0.0.Final/modules)
16:04:04,076 TRACE [org.jboss.modules] (MSC service thread 1-3) Class
org.jboss.weld.introspector.jlr.WeldClassImpl not found from Module
org.jboss.logmanager:main from local module loader @67d225a7 (roots:
/Users/sam/code/jboss-as-7.0.0.Final/modules)
16:04:04,077 TRACE [org.jboss.modules] (MSC service thread 1-3) Finding class
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass from Module
org.jboss.logmanager:main from local module loader @67d225a7 (roots:
/Users/sam/code/jboss-as-7.0.0.Final/modules)
16:04:04,077 TRACE [org.jboss.modules] (MSC service thread 1-3) Class
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass not found
from Module org.jboss.logmanager:main from local module loader @67d225a7
(roots: /Users/sam/code/jboss-as-7.0.0.Final/modules)
exception
{code}
My mention of Guava 10.0.1 previously should have read 11.0.1. As an experiment
I replaced my jar's copy of Guava 11.0.1 with r06 and redeployed to AS 7.0.0.
This time the jar deployed as I would expect: it complained that certain Guava
classes were unavailable but didn't throwing any ArrayOutOfBounds exceptions.
Weld SE startup fails.
--
Key: WELD-1007
URL: https://issues.jboss.org/browse/WELD-1007
Project: Weld
Issue Type: Bug
Components: Java SE Support
Affects Versions: 1.1.1.Final, 1.1.2.Final, 1.1.3.Final
Environment: Arch Linux, Linux kernel 3.0.7
java version 1.7.0_02-ea
Java(TM) SE Runtime Environment (build 1.7.0_02-ea-b11)
Java HotSpot(TM) Server VM (build 22.0-b08, mixed mode)
java version 1.6.0_26
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode)
Reporter: Konstantin Gribov
Attachments: weld-se-test.tar.gz
I use {{org.jboss.weld.environment.se.StartMain}} to bootstrap weld se
environment. Project is compiled and packaged by maven. When starting
assembly it fails with such stacktrace:
{quote}
Exception in thread main com.google.common.collect.ComputationException:
java.lang.ArrayIndexOutOfBoundsException: 3
at
com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:218)
at
com.google.common.collect.ComputingConcurrentHashMap.apply(ComputingConcurrentHashMap.java:100)
at
com.google.common.collect.MapMaker$ComputingMapAdapter.get(MapMaker.java:515)
at
org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:183)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.init(WeldClassImpl.java:128)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:98)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:54)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:42)
at
com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:206)
at
com.google.common.collect.ComputingConcurrentHashMap.apply(ComputingConcurrentHashMap.java:100)
at
com.google.common.collect.MapMaker$ComputingMapAdapter.get(MapMaker.java:515)
at
org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:183)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.init(WeldClassImpl.java:128)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:98)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:54)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:42)
at
