Hello Martijn,
we've had the same issue. This is related to the client window handling, that
targets modern browsers supporting HTML5.
Simply add a class to your application with the following content:
@Specializes
public class OurClientWindowConfig extends DefaultClientWindowConfig
{
priva
Hello everybody,
I've come across a situation where we were in the need to use the cdictrl-api
within WebSphere Server 8.0.x. Our use case was the integration of Disruptor,
an implementation of a threaded ringbuffer. Unfortunately, no contexts are
started within the working threads, so we imple
Hello,
I've been trying to start the CDI container during Junit-Testing as described
at the following page,
http://struberg.wordpress.com/2012/03/27/unit-testing-strategies-for-cdi-based-projects/
though I'm using Junit 4 and implemented everything using a new Runner (to
annotate tests with @R
Hello Romain,
thank you for your fast response. Yes I want to intercept the test itself.
I've checked into various ways on how to actually create a bean, however
nothing worked out. You mention to call beanManager.getXXX() but for my point
that is not enough information.
I tried to retrieve th
Hey Romain,
that was the missing piece of the puzzle and lets me step down in embarrassment
for such an idiotic mistake. I've had the assumtion that for a maven surefire
test, the beans.xml provided in src/main/resources/META-INF which IS obviously
used, is enough, but after you pointed this ou
Hello Mark,
thank you for your input. Your idea would have been much easier than what I did
:-)
When you write a Junit Runner, you have the ability to control the test class
creation by overwriting createTest() and returning your instance. By default
this is simply the newInstance() call for t
Seems this way. I think this whole dicussion is becoming ridicuolus. Change it
to comply with the rest. I personally never understood why this very lonely
'module' cdiCtrl is located elsewhere, regardless on whether it has different
dependencies or not. Additionally it does not fit into the nam
Hello,
we've come across an issue with Version 0.7 and even 0.8-SNAPSHOT under
WebSphere 8 in the JSF module. When the application is started the following
stack trace occurs.
I've debugged into this a bit more. The SPI extension ViewConfigExtension is
present and exists and the observers are
Hello Mark,
thank you for pointing this out. This version mess in WebSphere drives me
crazy. Unfortunately the development happens using liberty because its much
more convinient. The integration test happens under WAS 8.0.0.8 cause it's the
productive environment. I guess we have to go back dev
Hello Gerhard,
thank you for your fast response. I did so and it worked, however this problem
seems to occur in almost ALL AppicationScoped classes. I've come across two new
ones after that:
@ApplicationScoped
public class WindowContextProducer
{
@Inject
private DeltaSpikeContextExtensi
Hello Mark,
Sorry to bug you again. Do you by chance have the PMR IFIX number for that? We
are currently running under WAS 8.0.0.8 and this obviously is the latest
version and it does not contain the fix for it. If I knew the IFIX number I
could request the ifix to be installed.
Thank you very
Okay I will fork your project and give it a try.
We tried Liberty (no problem here), we do not have a running WAS 8.5.5 (not
accepted by customer).
If you later find the IFIX number it would be great if you can mail it to me.
Thanks for your help,
Heiko
--
Dr.-Ing. Heiko Kopp
> -Ursprüng
Hello,
we've come across an issue in version 1.0.4 of the Deltaspike JSF module. In
case one manipulates the dswid-Parameter generated by DeltaSpike in the
following way:
http:///pages/mypage.xhtml?dswid=7479%3C/script%3E%3Cscript%3Ealert%281%29%3C/script%3E
and the underlying page 'mypage.xht
Hello,
I've come across an issue when stopping an application that uses the
deltaspike-jsf-module (ee6) (current SNAPSHOT of 1.1-Release). The
JsfSystemEventBroadcaster tries to retrieve the BeanManager and can't do so, as
an IllegalStateException is thrown.
Can you elaborate whether you know
Hey Mark,
Our real project had a EJB project as well. I stripped down the problem to a
single WAR inside an EAR. I used your was_bugs-project on github and created a
sample to demonstrate the bug. A PMR has been opened: IllegalStateException
when accessing BeanManager in JSF SystemEventListen
Hello,
We have a project with the following setup:
EAR
è EJB
o Has access to the Utility-JAR
è Utility-JAR
o PropertyConfigSource named PasConfiguration.class
è WAR
o Has access to the Utility-JAR and the EJB
All modules are CDI-enabled.
When the application starts, it first starts
16 matches
Mail list logo