aslak

Untitled

Mar 16th, 2010
94
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.22 KB | None | 0 0
  1. <aslak> :)
  2. ok.. that's 'almost' doable the way it is now
  3. running against a remote container will use a http request to call the testcase inside the container
  4. so.. you have a active request, but no facesservlet setup
  5. and pr now, the 'default' Packager wrapps up your deployment in ear/ with the servlet-protocol war as ear/war
  6. lbaxter, this is the default EE packager in alpha-1, http://anonsvn.jboss.org/repos/common/arquillian/trunk/packagers/javaee/src/main/java/org/jboss/arquillian/packager/javaee/EEDeploymentPackager.java
  7. applicationArchive is you @Deployment and auxiliaryArchives are arquillian-core/junit/servlet-protocol/testrunners etc
  8. lbaxter, you can register the FacesServlet using the new ee 6 web fragments i guess?
  9. so.. what you can do for now.. if you want.. is to write your own Packager
  10. 1. using the AuxiliaryArchiveAppender SPI, add a Faces fragment War
  11. 2. using the Packager SPI, create a packager that add all AuxiliaryArchive into the Servlet-Protocol AuxiliaryArchive war as addLibrary
  12. 3. exclude the Packager dep from the remote container and provide your own
  13. Faces fragment jar i mean.. :)
  14. lbaxter, this of course will be supported by Arquillian in the future, but for not i mean..
  15. now/now
Add Comment
Please, Sign In to add comment