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
hi heiko,
the only way to get around that WAS8 issue is to deactivate
org.apache.deltaspike.jsf.impl.config.view.ViewConfigPathValidator (it
implements Deactivatable).
regards,
gerhard
2014-05-20 11:36 GMT+02:00 it-media.k...@extaccount.com:
Hello,
we've come across an issue with Version
short addition:
please pull the latest change and try it again.
regards,
gerhard
2014-05-20 11:46 GMT+02:00 Gerhard Petracek gerhard.petra...@gmail.com:
hi heiko,
the only way to get around that WAS8 issue is to deactivate
org.apache.deltaspike.jsf.impl.config.view.ViewConfigPathValidator
Hi Heiko!
Side note: You need to distinguish between WAS-8.5.5.x and the liberty profile.
They both have similar version numbers but are really different. E.g. WAS uses
OWB-1.1.0-snapshot whereas liberty uses OWB-1.1.6.
LieGrue,
strub
On Tuesday, 20 May 2014, 12:10, Gerhard Petracek
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
We have something similar at our customer.
Most times using openejb with deltaspike-cdictrl for running our unit tests
(way faster than liberty) and WAS-8.5.5.1 in production.
See [1] and [2] plus a bit maven magic in the poms for a sample setup.
LieGrue,
strub
[1
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
