Hmm, this sounds wrong, Arquillian starts the container before "creating" the archive. Is it a cache archive appender? Maybe use an archive processor
Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-05-19 17:50 GMT+02:00 Alex Soto <[email protected]>: > i have tought that but in archiveappender where I could put the properties > file httpcontext is null > > El dilluns, 19 maig de 2014, Romain Manni-Bucau <[email protected]> va > escriure: > > > I think System.getProperty("tomee.http") would work? > > > > Best for you is to put this port from client side (HTTPContext) in > > yourextension.properties in the war then get it from TCCL. > > > > > > > > Romain Manni-Bucau > > Twitter: @rmannibucau > > Blog: http://rmannibucau.wordpress.com/ > > LinkedIn: http://fr.linkedin.com/in/rmannibucau > > Github: https://github.com/rmannibucau > > > > > > 2014-05-19 17:40 GMT+02:00 Alex Soto <[email protected] <javascript:;>>: > > > > > Hello I am developing an Arquillian extension and I need a way to know > in > > > which port has been deployed an application. When running as client, > > there > > > is no problem because I can get the HTTPContext and get all the > > > information, but when running within container, this information is not > > > available. The problem is not a big problem if developer where in > charge > > of > > > defining running port, but because TomEE can be started up in random > > port, > > > there is no way to know it for sure. Does Arquillian adapter provides > any > > > enrichment/util class to know this information? > > > > > > Thank you so much. > > > > > > -- > > > +----------------------------------------------------------+ > > > Alex Soto Bueno > > > www.lordofthejars.com > > > +----------------------------------------------------------+ > > > > > > > > -- > Enviat amb Gmail Mobile >
