Thank you Martin for the info! It is strange that the application works on
OWB
Many thanks,
Emily
===
Emily Jiang
WebSphere Application Server, CDI Development Lead
MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN
Phone: +44 (0)1962 816278 Internal: 246278
Hi Martin,
Why not carrying on releasing these jira fixes on 2.3.x branches?
Weld-1574 is useful. Do you plan to
WELD-1574 [3] - remove the dependency on Google Guava and reduce the
footprint to Weld 2.3.x?
Many thanks,
Emily
===
Emily Jiang
WebSphere Application
Thanks Matej for the info! From the issue list as per Martin's notes,
sounds like the major change is to remove the dependency on Guava.
Many thanks,
Emily
===
Emily Jiang
WebSphere Application Server, CDI Development Lead
MP 211, DE3A20, Winchester, Hampshire, En
Thanks Martin for the detailed list! From the migration point of view, are
there any other items except the guava dependency changes?
Many thanks,
Emily
===
Emily Jiang
WebSphere Application Server, CDI Development Lead
MP 211, DE3A20, Winchester, Hampshire, England
If I understand you question correctly, the reason that the interceptor is
not working is that it directly calls the method instead of going through
the proxy. It is a known feature.
Many thanks,
Emily
===
Emily Jiang
WebSphere Application Server, CDI Development Lead
nks,
Emily
=======
Emily Jiang
WebSphere Application Server, CDI & MicroProfile Development Lead
MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN
Phone: +44 (0)1962 816278 Internal: 246278
Email: emiji...@uk.ibm.com
Lotus Notes: Emily Jiang/UK/IBM@IBMGB
Unless stated otherwise abo
nterceptors-spec/issues/27
[2] https://github.com/javaee/interceptors-spec/issues/23
Many thanks,
Emily
===
Emily Jiang
WebSphere Application Server, CDI & MicroProfile Development Lead
MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN
Phone: +44 (0)1962 816278 Int
No, Martin. I am talking about the new maintenance release of Interceptor
spec, JSR318. The sentence as per my email is on page 32.
Many thanks,
Emily
===
Emily Jiang
WebSphere Application Server, CDI & MicroProfile Development Lead
MP 211, DE3A20, Winchester, Hamps
There was a discussion on proxying the signed jars. Can you confirm
whether Weld can deal with proxying classes from a signed jar?
Many thanks,
Emily
===
Emily Jiang
WebSphere Application Server, CDI & MicroProfile Development Lead
MP 211, DE3A20, Winchester, Hamps
, what is the scope
for the Principal bean?
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
___
weld-dev mailing list
weld-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
Does this mean it functions as a Request scoped bean even though it is a
Dependent bean?
Many thanks,
Emily
===
Emily Jiang
WebSphere Application Server, CDI & MicroProfile Development Lead
MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN
Phone: +44 (0)
Hi Matej/Martin,
I am looking at the CDI 2.0 tck on JavaSE. I saw they are under the groups
of "SE". Should the tcks be exercised by JavaEE runtime, e.g. wildfly,
glassfish, Liberty etc? Which profile did you package the JavaSE tck?
Many thanks,
Emily
=======
E
le", "web
profile" for us to filter them out. You have answered my question.
Many thanks,
Emily
===
Emily Jiang
WebSphere Application Server, CDI & MicroProfile Development Lead
MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN
Phone: +44 (0)1962 8
===
Emily Jiang
WebSphere Application Server, CDI & MicroProfile Development Lead
MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN
Phone: +44 (0)1962 816278 Internal: 246278
Email: emiji...@uk.ibm.com
Lotus Notes: Emily Jiang/UK/IBM@IBMGB
From: M
ok. Thanks Martin!
Many thanks,
Emily
===
Emily Jiang
WebSphere Application Server, CDI & MicroProfile Development Lead
MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN
Phone: +44 (0)1962 816278 Internal: 246278
Email: emiji...@uk.ibm.com
Lotus Notes: E
Hi Martin/Matej,
We hit the following problem with Jdk 8.
Caused by: java.lang.BootstrapMethodError: java.lang.IllegalAccessException: 'org.jboss.weld.event.ObserverNotifier$ObserverExceptionHandler' no access to: 'org.jboss.weld.event.ObserverNotifier$ObserverExceptionHandler' at org.jb
-From: Martin Kouba Sent by: weld-dev-boun...@lists.jboss.orgTo: Emily Jiang Cc: weld-dev@lists.jboss.orgSubject: Re: [weld-dev] illegal access exception on org.jboss.weld.event.ObserverNotifier$ObserverExceptionHandlerDate: Wed, Nov 1, 2017 7:23 AM
Hi Emily,the exception message looks odd. Do you
England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
- Original message -From: Martin Kouba Sent by: weld-dev-boun...@lists.jboss.orgTo: Emily Jiang Cc: weld-dev@lists.jboss.orgSubject: Re: [weld-dev] illegal access exception on
Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
- Original message -From: Martin Kouba Sent by: weld-dev-boun...@lists.jboss.orgTo: Emily Jiang Cc: weld-dev@lists.jboss.orgSubject: Re: [weld-dev] illegal access exception
- Original message -From: Martin Kouba Sent by: weld-dev-boun...@lists.jboss.orgTo: Emily Jiang Cc: weld-dev@lists.jboss.orgSubject: Re: [weld-dev] illegal access exception on org.jboss.weld.event.ObserverNotifier$ObserverExceptionHandlerDate: Thu, Nov 2, 2017 11:48 AM
Well, the issue is closed and the
Hi Martin/Matej,
For using Jandex to improve bootstrap performance of CDI application, do you know any application server (e.g. Wildfly) normally requires the index files to be generated before hand or it can generate on the fly and then persist it? Do you know whether there is much performance
Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU-weld-dev-boun...@lists.jboss.org wrote: -To: Emily Jiang <emiji...@uk.ibm.com>, weld-dev@lists.jboss.orgFrom: Martin Kouba Sent by: weld-dev-boun...@lists.jboss.orgDate: 11/16/2017 04:19PMSubject: Re: [we
nks,
Emily
=======
Emily Jiang
WebSphere Application Server, CDI & MicroProfile Development Lead
MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN
Phone: +44 (0)1962 816278 Internal: 246278
Email: emiji...@uk.ibm.com
Lotus Notes: Emily Jiang/UK/IBM@IBMGB
From: Mat
SDK distributions require JDK 7 Update 65 and above or JDK 8
Update 20 and above.
Many thanks,
Emily
===
Emily Jiang
WebSphere Application Server, CDI & MicroProfile Development Lead
MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN
Phone: +44 (0)1962 816278 I
I have not found anywhere to suggest JDK 7 should not work with Java EE7.
If you feel the links cannot be trusted, please reach out to the spec lead
of Java EE7 for confirmation.
Many thanks,
Emily
===
Emily Jiang
WebSphere Application Server, CDI & MicroPro
This issue https://issues.jboss.org/browse/WELD-1130 has been around for a
while. Can some investigation be done? We are happy to assist with testing
a patch if needed.
Many thanks,
Emily
===
Emily Jiang
WebSphere Application Server, CDI & MicroProfile Development
Hi Martin,
Ben on cc proposed a PR. Can you please take a look and provide comments
on whether the solution was ok? Your help is very much appreciated!
Many thanks,
Emily
===
Emily Jiang
WebSphere Application Server, CDI & MicroProfile Development Lead
MP 211, DE
think it should be
eliminate disqualified ones and leave all qualified at least.
I am sending to cdi-dev for clarification. Antoine, please comment.
Many thanks,
Emily
===
Emily Jiang
WebSphere Application Server, Liberty Architect for MicroProfile and CDI
MP 211, DE3A20
Emily
===
Emily Jiang
WebSphere Application Server, Liberty Architect for MicroProfile and CDI
MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN
Phone: +44 (0)1962 816278 Internal: 246278
Email: emiji...@uk.ibm.com
Lotus Notes: Emily Jiang/UK/IBM@IBMGB
From: M
Matej,
Since @Inject can only work with a qualifier annotation not anything other
annotations, do you think adding a validation criteria to assert that is
acceptable?
For IDE validation, it is quite limited because a lot of work needs to be
done via runtime to figure out whether the 2nd annotation
spec reference
implemenatation (RI) or RI consumer.
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
___
weld-dev mailing list
weld-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
last EJB interceptor to be invoked?
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
___
weld-dev mailing list
weld-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
to explain why the tck test was done this way? Is it
accurate?
--
Thanks
Emily
=====
Emily Jiang
eji...@apache.org
___
weld-dev mailing list
weld-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
s used instead for that particular jar.
>
> HTH,
>
> Jozef
>
>
> On 04/30/2015 11:34 PM, Emily Jiang wrote:
>
>Thanks Jozef! I figured out why I did not get an error:
>
> my war:
> web-inf\beans.xml (containing invalid class as alternatives)
> web-i
https://issues.jboss.org/browse/CDITCK.
> >
> > As for this particular one I am not sure why the
> Contexts.getRequestContext() method is still used in the tests.
> BeanManager.getContext(RequestScoped.class) should IMHO be used instead.
> >
> > Jozef
> >
>
support interceptors on Servlet.
Anything I missed?
Thanks
Emily
On Thu, May 7, 2015 at 8:22 AM, Jozef Hartinger wrote:
> Hi Emily, comments inline.
>
> On 05/06/2015 05:38 PM, Emily Jiang wrote:
>
> I have a few questions on ejb integration on Weld.
>
> 1)Does Weld handle
wse/CDITCK.
> > >
> > > As for this particular one I am not sure why the
> Contexts.getRequestContext() method is still used in the tests.
> BeanManager.getContext(RequestScoped.class) should IMHO be used instead.
> > >
> > > Jozef
>
the JavaEE component
classes are created, right? By the way, how can the container make sure to
destroy the interceptors?
--
Thanks
Emily
=====
Emily Jiang
eji...@apache.org
___
weld-dev mailing list
weld-dev@lists.jboss.org
https://lists
missed?
On Tue, May 12, 2015 at 7:50 AM, Jozef Hartinger
wrote:
> On 05/11/2015 03:47 PM, Emily Jiang wrote:
>
>
> I have a few questions on interceptors:
>
> 1. CDI Interceptors on cdi beans
> Will the interceptors share the same creational context as the bean it is
> asso
);
Thanks
Emily
On Fri, May 8, 2015 at 11:29 AM, Emily Jiang
wrote:
> Thank you Jozef for your helpful response! I have another clarification on
> the interceptors on JavaEE component classes.
>
> EE7 spec states the JavaEE component classes, listed in Table EE.5-1, need
> to s
;t seem to use this SPI at all when handling static producer
fields. Can someone confirm or give me some pointers how to fix this
problem?
--
Thanks
Emily
=====
Emily Jiang
eji...@apache.org
___
weld-dev mailing list
weld-dev@lists.jboss
, Martin Kouba wrote:
> Dne 13.5.2015 v 00:27 Emily Jiang napsal(a):
>
>> Thank you Jozef for the helpful info. I have another question on
>> interceptor:
>> EE7 spec states the JavaEE component classes, listed in Table EE.5-1,
>> need to support interceptors. Take
oops. yes. Can you shed some lights on this problem?
On Mon, May 18, 2015 at 8:48 AM, Martin Kouba wrote:
> Emily,
>
> I believe this one belongs rather to the weld-dev ML.
>
> Martin
>
> Dne 18.5.2015 v 09:23 Emily Jiang napsal(a):
>
>>
>> In CDI1.2
ly integration code and it makes use of
> org.jboss.weld.manager.api.WeldManager.createInjectionTargetBuilder(AnnotatedType)
> for EE components, i.e. delegates validation to weld implemetation.
>
> M
>
> Dne 18.5.2015 v 09:51 Emily Jiang napsal(a):
>
>> oops. yes. Can you s
maintaining CDI 1.1 cts and only runs against CDI
1.2 cts?
We found the same test does different things between CDI 1.1 cts and CDI
1.2 cts.
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
___
weld-dev mailing list
weld-dev@lists.jboss.org
https
Thank you Jozef for your quick reply!
On Fri, May 22, 2015 at 10:10 AM, Jozef Hartinger
wrote:
> Weld 2.2 should be run against CDI 1.2 TCK. There were changes between
> CDI 1.1 and 1.2 due to which it won't pass CDI 1.1 TCK entirely.
>
>
> On 05/22/2015 10:55 AM, Emily Jia
ot be any bean
archives. Can someone tell me what I might done wrong? Will integrator need
to do something to cater for all of the java.x classes or Weld should
handle this?
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
___
weld-dev ma
should be updated to send the first request first
before checking the size of the obsevers.
I did not directly send to cdi tck as I would like to get some input from
weld dev list first.
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
ITCK-484
>
> Jozef
>
>
> On 05/24/2015 04:21 PM, Emily Jiang wrote:
>
> I am trying to run the cdi tck:
> org.jboss.cdi.tck.tests.context.application.event.ApplicationScopeEventMultiWarTest
> Method: testDeployment
>
> It seems this test is to verify whether bo
inish(AfterBeanDiscoveryImpl.java:186)
> ... 15 more
>
> It seems that Custom bean was added by an extension but the bean
> implements Bean. Surely the java.lang.Interger should not be any
> bean archives. Can someone tell me what I might done wrong? Will integrator
> need to do som
Thank you Tom and Jozef!
On Mon, May 25, 2015 at 9:39 AM, Tomas Remes wrote:
>
> Hi Emily,
>
> Yes I am already working on that. As I commented on the isssue.
>
> Thank's
> Tom
>
> - Original Message -
> From: "Emily Jiang"
> To: &qu
we should not use
injectiontarget.produce(). Am I right to say that we need to call into the
correct constructor with the resolved arguments?
On Thu, May 21, 2015 at 1:25 PM, Jozef Hartinger
wrote:
> On 05/13/2015 12:35 AM, Emily Jiang wrote:
>
> A further question on EJB injectio
y, I think this annotation needs to be treated
differently.
--
Thanks
Emily
=====
Emily Jiang
eji...@apache.org
___
weld-dev mailing list
weld-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
lementation will call the @Inject constructor
> passing in the dependencies or call the no-arg constructor. What "correct
> constructor with the resolved arguments" did you mean?
>
> Jozef
>
>
> On 05/27/2015 01:04 AM, Emily Jiang wrote:
>
> Thank you Jozef for
omponent
> initialization (i.e. cache the IT for a component,
> similarly to how javax.enterprise.inject.spi.Unmanaged works) and before
> an EE component instance is instantiated.
>
> Martin
>
> Dne 18.5.2015 v 11:38 Emily Jiang napsal(a):
>
>> Thank you Martin! I did a
Thanks Jozef! I agree with you that it is best to create bda according to
classloading and wire the graph according to classloading hierarchy.
On Mon, May 25, 2015 at 11:08 AM, Jozef Hartinger
wrote:
>
> On 05/25/2015 11:07 AM, Emily Jiang wrote:
>
> Thank you Jozef! I also figu
it to be handled by the integrator. What is the best way to
find out which class is JavaEE component class? I don't like to idea of
building a long hardcoded list from the EE.5-1 table of the JavaEE7 spec.
--
Thanks
Emily
=
Emily Jiang
eji...@apach
ess all
> classes in the bda and fire events for each JavaEE component classes as
> Weld leaves it to be handled by the integrator. What is the best way to
> find out which class is JavaEE component class? I don't like to idea of
> building a long hardcoded list from the EE.5-1 tab
point on the non-cdi interceptors are not injected when Weld
creates the interceptor instances.
Is there anything I have missed or this is a bug?
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
___
weld-dev mailing list
weld-dev
to
> customize this behavior, e.g:
>
> beanManager.createInjectionTargetBuilder(type)
> .setDecorationEnabled(false)
> .setInterceptionEnabled(false)
> .setTargetClassLifecycleCallbacksEnabled(false)
> .setResourceInjectionEnabled(true)
> .build()
>
provided by Weld.
>
> Jozef
>
>
> On 06/03/2015 11:25 AM, Emily Jiang wrote:
>
>> I might have missed your point. Please elaborate a bit more.
>>
>
>
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
__
zef Hartinger wrote:
> Oops, sorry. Ignore my last e-mail. How do you obtain the InjectionTarget
> for the non-CDI interceptor?
>
>
> On 06/03/2015 12:52 PM, Emily Jiang wrote:
>
> Jozef,
> The PlainInterceptorFactory is weld class. Here is the stack when we
> created
/browse/WELD-1963 to track this issue.
>
> Jozef
>
>
> On 06/03/2015 03:41 PM, Emily Jiang wrote:
>
> Hi Jozef,
> The non-CDI interceptor was created by Weld when I called
> injectionTarget.produce() on a ManagedBean class. I have no control of it.
> Please see above f
/org.eclipse.persistence.core/src/org/eclipse/persistence/internal/sessions/cdi/EntityListenerInjectionManagerImpl.java?h=2.6_WAS
]
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
___
weld-dev mailing list
weld-dev@lists.jboss.org
https://lists.jboss.org/mailman
/weld/javadoc/2.2/weld-spi/org/jboss/weld/manager/api/WeldManager.html#fireProcessInjectionTarget-javax.enterprise.inject.spi.AnnotatedType-javax.enterprise.inject.spi.InjectionTarget-
> on Weld BeanManager and use the returned value as the InjectionTarget.
>
> HTH,
>
> Jozef
>
>
thanks Jozef!
On Sun, Jun 21, 2015 at 10:58 PM, Emily Jiang
wrote:
> Jozef,
> The implementation is in eclipse link. I guess they don't want to depend
> on a specific CDI implementation.
> Thanks
> Emily
>
> On Sun, Jun 21, 2015 at 8:42 PM, Jozef Hartinger
> wro
Jozef,
Just re-iterate my concern:
The implementation is in eclipse link. I guess they don't want to depend on
a specific CDI implementation. Therefore, what you suggested may not be
accepted by the eclipse link project.
Thanks
Emily
On Sun, Jun 21, 2015 at 10:59 PM, Emily Jiang
eir
> notify() method to deliver the event. Exception handling needs to be
> implemented to match the spec.
>
> We should update the spec to define a more direct route and for the JPA
> spec to mention this requirement.
>
> Jozef
>
>
> On 06/22/2015 02:25 PM, Emily Jiang
Raised https://issues.jboss.org/browse/CDI-537.
On Tue, Jun 23, 2015 at 2:00 PM, Jozef Hartinger
wrote:
> Yes please.
>
>
> On 06/23/2015 02:56 PM, Emily Jiang wrote:
>
> +1 on revisiting this on the CDI spec. I think adding an additional method
> on the BeanMana
Is it possible to get the following jira fix committed to 2.2.15.Final?
https://issues.jboss.org/browse/WELD-1931
I would like to consume this and see how much improvement has been made.
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
ually do the release? I can prepare a
> separate branch or send you a binary. I would like to see how much
> improvement this makes in your benchmark.
>
> Jozef
>
>
> On 07/01/2015 06:19 PM, Emily Jiang wrote:
>
> Is it possible to get the following jira fix committed to 2.2.
weld-osgi bundle only
On Thu, Jul 2, 2015 at 9:31 AM, Jozef Hartinger wrote:
> Yes, which artifact are you using? weld-core, weld-core-impl or weld-osgi
> bundle?
>
>
> On 07/02/2015 10:30 AM, Emily Jiang wrote:
>
> Thanks Jozef! Sure. Sending me a binary will be good.
m. Would it be possible for you to test the
> performance improvement before we actually do the release? I can prepare a
> separate branch or send you a binary. I would like to see how much
> improvement this makes in your benchmark.
>
> Jozef
>
>
> On 07/01/2015 06:19 PM, Emi
3% additional overhead seems to me too much. Would it be
> possible to share your performance test case / test application? We could
> run similar tests in our environment and verify that there's no integration
> problem.
>
> Martin
>
> [1]
> https://issues.jboss.org/bro
Jozef
>
> On 20.7.2015 14:43, Emily Jiang wrote:
>
>> The test applications we used were attached to the jira
>> https://developer.jboss.org/message/926035#926035.
>>
>> You can compare the responding time between two servlet requests.
>>
>> Can you com
bean
names in multiple wars. Is it possible to switch off the unique bean name
checks for some extensions? Do you have any suggestions on how to resolve
the problem.
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
___
weld-dev mailing list
Hartinger
wrote:
> Hi Emily,
>
> can you elaborate a bit more how your extension looks like? If the bean
> registered by an extension is really shared across wars there should be no
> ambiguous resolutions.
>
> Jozef
>
>
> On 21.7.2015 22:35, Emily Jiang wrote:
>
&
validation
for some bdas or only throw an exception when it cannot resolve el
successfully?
On Wed, Jul 22, 2015 at 9:14 AM, Emily Jiang
wrote:
> Hi Jozef,
>
> The extension I am referred to is jsf extension, FlowBuilderCDIExtension,
> which registers the bean FlowBuilderFacto
2)?
>
> Jozef
>
> On 22.7.2015 10:19, Emily Jiang wrote:
>
>> continued:
>> The issue is that when it comes to do the validation, Weld insists all
>> bean names must be unique among all the beans which this extension can
>> see. This extension does not need to use e
Hi Jozef/Martin,
Can you please commit the performance changes for this jar and release
2.2.15.Final as soon as possible?
Thanks
Emily
On Tue, Jul 21, 2015 at 12:31 PM, Emily Jiang
wrote:
> Thank you Jozef and Martin! I am looking forward to consume 2.2.15.Final.
>
> On Mon, Jul 20,
:
> Hi Emily,
>
> Weld 2.2.15 has been released (available in maven central, see also
> http://weld.cdi-spec.org/download/).
>
> Martin
>
> Dne 2.8.2015 v 23:45 Emily Jiang napsal(a):
>
>> Hi Jozef/Martin,
>> Can you please commit the performance changes for
(ResourceInjector.java:69)
--
Is there anything wrong? For some reason, it does not call back to the
ResourceReferenceFactory service to get hold of an instance of an factory.
Thanks
Emily
=
Emily Jiang
eji...@apache.org
___
weld-dev mailing list
weld
into 2.2 branch (see also
> https://github.com/weld/core/commits/2.2). I've updated the "Fix Version"
> in the JIRA.
>
> Martin
>
> Dne 3.8.2015 v 22:34 Emily Jiang napsal(a):
>
>> Thanks Martin for your comments! The issue is that the current jira
>> ht
you have ResourceInjectionServices implemented properly?
>
> Martin
>
> Dne 4.8.2015 v 00:37 Emily Jiang napsal(a):
>
>> I am trying to use Weld to inject ManagedBean instance but got the
>> following NPE.
>> [javatest.batch] Caused by: java.lang.NullPoin
injection targets for EJB-style interceptors? Am I missing
something?
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
___
weld-dev mailing list
weld-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
etimes from the
> registerResourceInjectionPoint() method? Is that possible? I'll add checks
> to Weld to validate the preconditions upfront instead of run time.
>
> Jozef
>
>
> On 4.8.2015 10:19, Emily Jiang wrote:
>
>> How can I verify whether the ResourceInjecti
Builder and then fire the event using the aforementioned
> method.
>
> HTH,
>
> Jozef
>
> On 6.8.2015 12:16, Emily Jiang wrote:
>
>> According to the CDI 1.2 spec, the container must fire Processing
>> Injection Target event for all Java EE component classes. Th
ort injection in these archives. These
archives are ignored basically. Right?
The spec does say an extension can exist in a non-bean archive but it does
not say anything about JavaEE component classes.
--
Thanks
Emily
=====
Emily Jiang
eji...@apache.
Hi Emily,
>
> Dne 18.8.2015 v 11:36 Emily Jiang napsal(a):
>
>> From CDI spec,
>> An archive which:
>> • contains a beans.xml file with the bean-discovery-mode of none, or,
>> • contains an extension and no beans.xml file
>> is not a bean archive.
>>
>&g
vider licenses the
> code under the Apache License, Version 2 (
> http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas
> provided on this list, the provider waives all patent and other
> intellectual property rights inherent in such information.
>
--
Thanks
Emily
==
CDI-527.
OpenWebBeans fixed this via the jira
(https://issues.apache.org/jira/browse/OWB-616).
Can Weld fix this in the 2.3 or 2.2 trunk?
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
___
weld-dev mailing list
weld-dev
ected static
final methods.
Thanks
Emily
On Wed, Oct 21, 2015 at 11:50 AM, Martin Kouba wrote:
> Hi Emily,
>
> commments inline.
>
> Dne 21.10.2015 v 11:02 Emily Jiang napsal(a):
>
>> CDI specification does not allow proxying a class with non-private final
>> me
doh. You were right that the OWB-616 was for a different issue rather than
the one I am interested.
Do you have any suggestions about working around the unproxiable Hashtable
issue?
On Wed, Oct 21, 2015 at 12:38 PM, Martin Kouba wrote:
> Dne 21.10.2015 v 13:20 Emily Jiang napsa
What about legacy applications running on new JDK7? The only workaround is
that the customers have to update the app. Otherwise, their app won't
start. This is not nice.
On Wed, Oct 21, 2015 at 2:57 PM, Martin Kouba wrote:
> Dne 21.10.2015 v 13:54 Emily Jiang napsal(a):
>
>> do
t was wrong?
Many thanks,
Emily
===
Emily Jiang
WebSphere Application Server, CDI Development Lead
MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN
Phone: +44 (0)1962 816278 Internal: 246278
Email: emiji...@uk.ibm.com
Lotus Notes: Emily Jiang/UK/IBM@
===
Emily Jiang
WebSphere Application Server, CDI Development Lead
MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN
Phone: +44 (0)1962 816278 Internal: 246278
Email: emiji...@uk.ibm.com
Lotus Notes: Emily Jiang/UK/IBM@IBMGB
Unless stated otherwise above:
IBM
out.
Many thanks,
Emily
===
Emily Jiang
WebSphere Application Server, CDI Development Lead
MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN
Phone: +44 (0)1962 816278 Internal: 246278
Email: emiji...@uk.ibm.com
Lotus Notes: Emily Jiang/UK/IBM@IBMGB
From: M
nly).
Many thanks,
Emily
===
Emily Jiang
WebSphere Application Server, CDI Development Lead
MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN
Phone: +44 (0)1962 816278 Internal: 246278
Email: emiji...@uk.ibm.com
Lotus Notes: Emily Jiang/UK/IBM@IBMGB
From: Mar
the
specialized bean disabled a second bean but itself is not active.
ok. I'll post the question on cdi-dev.
Many thanks,
Emily
===
Emily Jiang
WebSphere Application Server, CDI Development Lead
MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN
Phone: +
Jiang
WebSphere Application Server, CDI Development Lead
MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN
Phone: +44 (0)1962 816278 Internal: 246278
Email: emiji...@uk.ibm.com
Lotus Notes: Emily Jiang/UK/IBM@IBMGB
From: Martin Kouba
To: Emily Jiang/UK/IBM@IBMGB,
Cc: Weld
1 - 100 of 103 matches
Mail list logo
