Hello!
I finally got myself to try out the JUnit-CDI tests but the actual
result is dissappointing. I added the following libraries to the build
path of a project:
myfaces-extcdi-base-test-infrastructure-1.0.1.jar
myfaces-extcdi-bundle-jsf20-1.0.1.jar
hi christian,
you need additional test-dependencies. you can have a look at a working
config at [1].
regards,
gerhard
[1]
http://code.google.com/a/apache-extras.org/p/myfaces-codi-examples/source/browse/community/pom.xml
http://www.irian.at
Your JSF/JEE powerhouse -
JEE Consulting,
Am 24.11.2011 13:12, schrieb Gerhard Petracek:
hi christian,
you need additional test-dependencies. you can have a look at a working
config at [1].
regards,
gerhard
[1]
http://code.google.com/a/apache-extras.org/p/myfaces-codi-examples/source/browse/community/pom.xml
http://www.irian.at
Hi Christian!
Since you added all WebSphere-8.0 libs you don't need the openwebbeans-* jars
(WS includes them already).
Btw, the myfaces-extcdi-test was developed to perform quick standalone tests.
For testing a full EE server you might better use Arquillian.
I'm not sure if there is
I already tried to get Arquillian to work but it seems to be very hard
to get it working in IBM RAD without maven.
Just right now I am trying to get all libs I need to successfully run a
test, but as I said, without maven it's a pain...
I still don't understand why these CdiAware tests throw a
hi christian,
as mentioned by mark - it wasn't intended to use those test-modules that
way.
for simple unit tests you need a mocked environment (without libs of the
target application-server).
for htmlunit/cargo tests you need to bootstrap a compatible container (see
the cargo-examples profile).
One of the reasons why you will get a NPE is because the openwebbeans version
shipped with WAS is customized and integrates much deeper with the EJB
container, JPA, JMX etc shipping with WAS. OpenWebBeans provides a lot of SPIs
to extend it's features. And in WAS there are a lot owb-plugins
7 matches
Mail list logo
