tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Manni-Bucau <rmannibu...@gmail.com>
Subject Re: Port in Arquillian adapter
Date Mon, 19 May 2014 16:51:09 GMT
you are right it is done in: ProtocolMetaData deploy(Archive<?> archive)

tomee.httpPort will say you but not portably. And a http filter added
by an enricher?




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 18:11 GMT+02:00 Alex Soto <asotobu@gmail.com>:

> Well I think that arquillian creates the httpcontext when he knows which
> http context is going ti be deployed (war file) and in auxiliaryappender
> you are creating that war file so i think that for this reason there is no
> httpcontext. Maybe protocolmetadata will work but not sure
>
> El dilluns, 19 maig de 2014, Romain Manni-Bucau <rmannibucau@gmail.com> va
> escriure:
>
> > 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 <asotobu@gmail.com <javascript:;>>:
> >
> > > 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 <rmannibucau@gmail.com
> <javascript:;>>
> > 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 <asotobu@gmail.com<javascript:;><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
> > >
> >
>
>
> --
> Enviat amb Gmail Mobile
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message