from y.jar cause the problem
--
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
}
> the result of the call to getActualTypeArguments()[0] is GenericArrayType
> with component type Foo (not sure why... I'd expect it to be Class).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http
ments()[0] is GenericArrayType
> with component type Foo (not sure why... I'd expect it to be Class).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrato
ignable to
{{Foo>}} (if Baz extends Bar), but it is NOT assignable to
{{Foo>}} just because Bar is not assignable from Integer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://
; URL: https://issues.jboss.org/browse/WELD-1105
> Project: Weld
> Issue Type: Bug
> Components: Interceptors and Decorators
>Affects Versions: 1.1.6.Final
>Reporter: Marko Lukša
>Assignee: Marko Lukša
>
--
Th
org/browse/WELD-1105
Project: Weld
Issue Type: Bug
Components: Interceptors and Decorators
Affects Versions: 1.1.6.Final
Reporter: Marko Lukša
Assignee: Marko Lukša
--
This message is automatically generated by JIRA.
If you think i
named XBean, default name of a managed bean should be xBean.
> However, in runtime with Weld 1.1.5, this name is not available in EL,
> instead name XBean is available.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA adm
converting the first character to
> lower case."
> For a class named XBean, default name of a managed bean should be xBean.
> However, in runtime with Weld 1.1.5, this name is not available in EL,
> instead name XBean is available.
--
This message is automatically generated b
character to
> lower case."
> For a class named XBean, default name of a managed bean should be xBean.
> However, in runtime with Weld 1.1.5, this name is not available in EL,
> instead name XBean is available.
--
This message is automatically generated by JIRA.
If you think i
inal.jar:2012-02-10 15:31]
> at
> org.jboss.weld.bean.proxy.DecorationHelper.getNextDelegate(DecorationHelper.java:94)
> [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
> at
> org.jboss.weld.bean.SessionBean.applyDecorators(SessionBean.java:319)
> [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31
g.jboss.weld.bean.proxy.DecorationHelper.getNextDelegate(DecorationHelper.java:94)
> [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
> at
> org.jboss.weld.bean.SessionBean.applyDecorators(SessionBean.java:319)
> [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
> at org
> The required type of inherited injection point on {{Foo}} is {{Baz}} but
> should be {{Baz}}.
--
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.j
e required type of inherited injection point on {{Foo}} is {{Baz}} but
> should be {{Baz}}.
--
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
er converting the first character to
> lower case."
> For a class named XBean, default name of a managed bean should be xBean.
> However, in runtime with Weld 1.1.5, this name is not available in EL,
> instead name XBean is available.
--
This message is automatically gener
(section 2.7.5.1. says
> 'stereotype declarations are transitive'); and annotation @Named added to a
> stereotype A gives EL name to a bean annotated with A, as if it is annotated
> with @Named explicitly. Is it enough to answer 'yes' to the question above,
ember-level metadata*.
> {code}
> class Bar {
> @Inject Baz baz;
> }
> class Foo extends Bar {}
> {code}
> The required type of inherited injection point on {{Foo}} is {{Baz}} but
> should be {{Baz}}.
--
This message is automatically generated by JIRA.
If you think it wa
class TissCodiWindowContextConfig extends WindowContextConfig { ..
> The TissCodiWindowContextConfig is in my project jar, the parent class in
> codi-jsf.jar, both in my WEB-INF/lib folders of my webapp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrec
0 15:31]
> at
> org.jboss.weld.bean.SessionBean.applyDecorators(SessionBean.java:319)
> [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
> at org.jboss.weld.bean.SessionBean.create(SessionBean.java:298)
> [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
> ... 36 more
>
es.
--
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.atlassi
s LicenceException {
> return new Service() {
> @Override
> public int dummy() {
> return 0;
> }
> };
> }
> @Inject
> private Service ser
t; private Service service;
> @Test
> public void checkInjection() throws Exception {
> Assert.assertEquals(0, service.dummy());
> }
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact y
ee the spec *4.2. Inheritance of member-level metadata*.
> {code}
> class Bar {
> @Inject Baz baz;
> }
> class Foo extends Bar {}
> {code}
> The required type of inherited injection point on {{Foo}} is {{Baz}} but
> should be {{Baz}}.
--
This message is automatically gen
ed out as an integration test,
but I later realized I could strip it down to simply test TypeVariableResolver
directly, but forgot to move it.
I'll move it to the correct location when I fix the failing test (there's a new
jira task for it: WELD-1127)
> Inher
> to simply copy annotations during on-the-fly byte-code creation of the Proxy.
> The Problem is btw also true for javas built in Dynamic Proxy: using it you
> also loose Annotations.
> Hope you can fix that
--
This message is automatically generated by JIRA.
If you think it was sent incorrect
t in Case of a
> "transparent" WELD proxy I'd expect they should be there. Probably you have
> to simply copy annotations during on-the-fly byte-code creation of the Proxy.
> The Problem is btw also true for javas built in Dynamic Proxy: using it you
> also loo
using {{TypeLiteral}}
and simply use {{Integer[].class}} as the expected value. However,
{{TypeVariableResolver}} should also be modified so it never returns
{{GenericArrayType}}, when the array isn't generic.
--
This message is automatically generated by JIRA.
If you think it was sent i
; Since {{Integer[]}} is not a generic array, we can skip using {{TypeLiteral}}
> and simply use {{Integer[].class}} as the expected value. However,
> {{TypeVariableResolver}} should also be modified so it never returns
> {{GenericArrayType}}, when the array isn't generic.
--
This messag
generic array, we can skip using {{TypeLiteral}}
> and simply use {{Integer[].class}} as the expected value. However,
> {{TypeVariableResolver}} should also be modified so it never returns
> {{GenericArrayType}}, when the array isn't generic.
--
This message is automatically genera
jection point on {{Foo}} is {{Baz}} but
> should be {{Baz}}.
--
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
[
https://issues.jboss.org/browse/WELD-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12691626#comment-12691626
]
Marko Lukša commented on WELD-1127:
---
I've opened a new jira for the failing test -
" WELD proxy I'd expect they should be there. Probably you have
> to simply copy annotations during on-the-fly byte-code creation of the Proxy.
> The Problem is btw also true for javas built in Dynamic Proxy: using it you
> also loose Annotations.
> Hope you can fix that
--
.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393)
> {code}
> This line is the causing issue: Class arrayClass =
> Array.newInstance(Reflections.getRawType(genericComponentType), 0).getClass();
> genericComponentType is
> sun.reflect.generics.reflectiveObjects.TypeVariableImpl.
&g
ed in
> corrupted state.
--
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/ji
ply copy annotations during on-the-fly byte-code creation of the Proxy.
> The Problem is btw also true for javas built in Dynamic Proxy: using it you
> also loose Annotations.
> Hope you can fix that
--
This message is automatically generated by JIRA.
If you thi
return 0;
> }
> };
> }
> @Inject
> private Service service;
> @Test
> public void checkInjection() throws Exception {
> Assert.assertEquals(0, service.dummy());
> }
> }
--
This mess
ollect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393)
> {code}
> This line is the causing issue: Class arrayClass =
> Array.newInstance(Reflections.getRawType(genericComponentType), 0).getClass();
> genericComponentType is
> sun.reflect.generics.reflectiveObjects.TypeVariableIm
> {{Integer[].class}}.
> Since {{Integer[]}} is not a generic array, we can skip using {{TypeLiteral}}
> and simply use {{Integer[].class}} as the expected value. However,
> {{TypeVariableResolver}} should also be modified so it never returns
> {{GenericArrayType}}, when the
My specific use-case in which I got the error was that I was trying to get
> the weld-osgi branch to work which is provided by Ales Justin (JBoss Weld
> lead) under: https://github.com/alesj/core.git
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, pl
LD proxy I'd expect they should be there. Probably you have
> to simply copy annotations during on-the-fly byte-code creation of the Proxy.
> The Problem is btw also true for javas built in Dynamic Proxy: using it you
> also loose Annotations.
> Hope you can fix that
--
This me
s executed first sometimes.
Thus, correct order of execution should be enforced, for example by annotating
the methods with {{@org.jboss.arquillian.junit.InSequence}} or by eliminating
dependence between test methods.
--
This message is automatically generated by JIRA.
If you think it was sent i
xecution is arbitrary, {{permanentLinkTest}}
> actually gets executed first sometimes.
> Thus, correct order of execution should be enforced, for example by
> annotating the methods with {{@org.jboss.arquillian.junit.InSequence}} or by
> eliminating dependence between test met
order of test execution is arbitrary, {{permanentLinkTest}}
> actually gets executed first sometimes.
> Thus, correct order of execution should be enforced, for example by
> annotating the methods with {{@org.jboss.arquillian.junit.InSequence}} or by
> eliminating dependence between test met
xecution is arbitrary, {{permanentLinkTest}}
> actually gets executed first sometimes.
> Thus, correct order of execution should be enforced, for example by
> annotating the methods with {{@org.jboss.arquillian.junit.InSequence}} or by
> eliminating dependence between test met
t; actually gets executed first sometimes.
> Thus, correct order of execution should be enforced, for example by
> annotating the methods with {{@org.jboss.arquillian.junit.InSequence}} or by
> eliminating dependence between test methods.
--
This message is automatically generated
ution is arbitrary, {{permanentLinkTest}}
> actually gets executed first sometimes.
> Thus, correct order of execution should be enforced, for example by
> annotating the methods with {{@org.jboss.arquillian.junit.InSequence}} or by
> eliminating dependence between test met
strap.WeldBootstrap.validateBeans(WeldBootstrap.java:380)
> at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:83)
> at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
> ... 5 more
> {noformat}
> Also note that the
> src/t
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information
e/pull/208
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/sof
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) ... 92 more{code}
This message is automatically generated by JIRA
constructors that are marked (instead of all enums).
This message is automatically generated by JIRA.
If you think it was sent
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http
generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
weld-issues
– comment removed –
Bah, I commented on the wrong jira task
This message is automatically generated by JIRA
generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
weld-issues
:
https://github.com/weld/core/pull/215
This message is automatically generated by JIRA.
If you think it was sent
())
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
Rejected
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA,
e/pull/216
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more info
anB, beanA
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/sof
4 was fixed.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues ma
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
ution:
Done
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administr
d1144
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more inform
now, this was broken, anyway.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, ple
l/218
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software
ViewScoped, right?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact
/main
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For
ution:
Cannot Reproduce Bug
This message is automatically generated by JIRA.
If you think it was
Final
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
Scope
Yes, sure.
This message is automatically generated by JIRA.
If you think it was
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA
this.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software
Hendy, the original bug described by this jira is not the same as the one you're facing.
The original bug AFAICT was about having an Event inside MySuperClass and a subclass MySubClass extends MySuperClass. The expected behavior would be that firing the event inside MySubClass shou
Issue
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
I created a pull request: https://github.com/weld/core/pull/220
This message is automatically generated by JIRA
enable bean B in beans.xml, right?
This message is automatically generated by JIRA.
If you think it was sent incorrectly
ent type.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, s
ent type.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, s
t Pull Request:
https://github.com/weld/core/pull/222
This message is automatically generated b
Marko Lukša
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information
Resolution:
Done
This message is automatically generated by JIRA
automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
weld
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com
:
https://github.com/weld/core/pull/226
This message is automatically generated by JIRA.
If you think it was sent incorrectly
:
Marko Lukša
This message is automatically generated by JIRA.
If you think it was sent
:
https://github.com/weld/core/pull/227
This message is automatically generated by JIRA.
If you think it was sent incorrectly
, https://github.com/weld/core/pull/229
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please
Gábor Farkas
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassi
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com
automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
weld
automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
weld
is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
601 - 700 of 15173 matches
Mail list logo
