.
--
This message is automatically generated by JIRA.
-
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
at
org.jboss.weld.bean.proxy.ProxyFactory.getProxyClass(ProxyFactory.java:285)
[:6.0.0.Final]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
weld-issues@lists.jboss.org
https
when associate() was called
at
org.jboss.weld.context.AbstractConversationContext.getCurrentConversation(AbstractConversationContext.java:413)'
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
using org.jboss.weld.extensions.beanManager.BeanManagerProvider, which
no longer exists in Seam Solder.
Also it looks like the same code is still in Git repository in the latest
version.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http
by JIRA.
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
remains in file path instead of proper URL decoding.
For example file:/C:/with%20space is converted to /C:/with%20space
instead of C:/with space.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
to remove this project dependency and use only
{{maven-checkstyle-plugin}} dependency (which is currently configured too):
https://github.com/weld/core/blob/e20e1b9b7f5d22e2bff3d3f1d2812b1ff8f99b42/pom.xml#L539
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly
any details about this behaviour in
JSR299.
weld and weld-core version is 1.1.5.Final
scenario project: https://github.com/milenkovicm/examples/tree/master/weld
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
types after
AfterBeanDiscovery phase. I can't find any details about this behaviour in
JSR299.
weld and weld-core version is 1.1.5.Final
scenario project: https://github.com/milenkovicm/examples/tree/master/weld
--
This message is automatically generated by JIRA.
If you think it was sent
/examples/tree/master/weld
--
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
://github.com/papegaaij/wicket-cdi demonstrates the problem, clone the
project in a directory with a space in the name, and run 'mvn install
-Dwicket.version=1.5-RC5.1'.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
decoding.
For example file:/C:/with%20space is converted to /C:/with%20space
instead of C:/with space.
--
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
Assignee: Marko Lukša
Priority: Critical
Fix For: 1.2.0.Beta1
--
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
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
the quickstart to explicitly make the producer an
alternative.
Pete
{quote}
--
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
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
and use only
{{maven-checkstyle-plugin}} dependency (which is currently configured too):
https://github.com/weld/core/blob/e20e1b9b7f5d22e2bff3d3f1d2812b1ff8f99b42/pom.xml#L539
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA
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
org.jboss.weld.tests.interceptors.binding.transitivity.InterceptorBindingTransitivityTest
--
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
Project: Weld
Issue Type: Bug
Reporter: Stuart Douglas
Assignee: Marko Lukša
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure
and be recognized as application exception in the EJB sense.
Of course, checked application exceptions are a bigger problem that would
probably require a more sofisticated solution, that could be resolved later.
--
This message is automatically generated by JIRA.
If you think it was sent
also if the
method's binding conflicts with a binding declared on the stereotype that is
declared on the method.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure
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
/535.11)
--
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
Fix For: 1.2.0.Beta1
See
org.jboss.weld.tests.interceptors.binding.transitivity.InterceptorBindingTransitivityTest
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure
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
Reporter: Stuart Douglas
Assignee: Marko Lukša
--
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
by the
same interceptor instance
* when invoking different methods on the same bean instance, every method is
intercepted by a different interceptor instance - which is wrong
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
that does not follow that should cause a DefinitionException.
In current impl they are registered, enabled but can not be resolved on Bean
lookup.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https
{{InterceptorBindingType}}s, a lot of the code would be clearer and we'd also
probably have no bugs related to the proxy.equals bug.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure
providing extension-points to
work around the broken @Alternative spec. section.
--
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
;
}
}
@Inject
SomeService someService;
@Test
public void testStatelessCall() {
Assert.assertEquals(test, someService.someMethod());
}
}
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA
the broken @Alternative spec. section.
--
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
method (e.g. foo()) are intercepted by the
same interceptor instance
* when invoking different methods on the same bean instance, every method is
intercepted by a different interceptor instance - which is wrong
--
This message is automatically generated by JIRA.
If you think it was sent
/idea/lib/idea_rt.jar
com.intellij.rt.execution.application.AppMain
org.jboss.weld.environment.se.StartMain
{quote}
I think, it's dependencies interfere problem, but haven't yet found the
solution.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please
.
--
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
written a test for it but git on Windows is... a bit nonlinear at
times.
--
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
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
--
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
org.jboss.weld.environment.se.StartMain
{quote}
I think, it's dependencies interfere problem, but haven't yet found the
solution.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure
}
I think, it's dependencies interfere problem, but haven't yet found the
solution.
--
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
) of a bean which is placed in a custom defined scope, the
interceptor isn't executed.
--
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
is wrong.
--
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
Assignee: Marko Lukša
Like discribed in forum i have the same problem but one diference;
I have several jar... when i the interceptor should intercept an class from a
x.jar and this class extends another from y.jar cause the problem
--
This message is automatically generated by JIRA
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/ContactAdministrators!default.jspa
For more information on JIRA
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/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-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 it was sent
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 administrators:
https://issues.jboss.org
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 administrators:
https://issues.jboss.org/secure/ContactAdministrators
.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
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA
]
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
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure
}} but
should be {{BazString}}.
--
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
be {{BazString}}.
--
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
, 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 administrators:
https
;
}
class Foo extends BarString {}
{code}
The required type of inherited injection point on {{Foo}} is {{BazT}} but
should be {{BazString}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org
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 incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
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
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 your JIRA administrators
;
}
};
}
@Inject
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 your JIRA
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
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)
Inheritance of member-level metadata
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
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 incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
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
[].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 incorrectly, please contact your JIRA administrators
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 incorrectly, please contact your JIRA administrators:
https://issues.jboss.org
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
[
https://issues.jboss.org/browse/WELD-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12691626#comment-12691626
]
Marko Lukša commented on WELD-1127:
---
I've opened a new jira for the failing test - WELD-1132
you can fix that
--
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
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 bean types of Y. If X does not have some
bean type of Y, the container automatically detects the problem and treats it
as a definition error.
However definition error is not detected and application is deployed in
corrupted state.
--
This message is automatically generated by JIRA.
If you think
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 message is automatically generated by JIRA.
If you
());
}
}
--
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
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
}}
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 incorrectly, please contact
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, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more
: using it you
also loose Annotations.
Hope you can fix that
--
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
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 incorrectly
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 incorrectly, please contact your JIRA administrators:
https
, 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 incorrectly, please contact your JIRA administrators:
https://issues.jboss.org
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 incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more
, 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 incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure
will fail
if @Inject is used to inject the arrays instead of the arquillian enrichment.
--
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
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information
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
}
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
for 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
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 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
was fixed.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your 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
1 - 100 of 14698 matches
Mail list logo
