Is this supported in AS7? I don't see anyway to configure Remoting to expose HTTP (or any protocol settings) unless it's in one of the free-form properties. Thanks -Bill

As far as I know those features are no longer there

It will have to be a 7.2+ / EAP 6.1 thing unless we get significant customer demand. JAX-RS is always an option if you really want HTTP invocation. On 4/4/12 1:07 PM, William DeCoste wrote: > Thanks Andy. I don't think they are either - at least not yet - from > what I see in the EJB, Remoting, and Messaging schema. Is there a plan > to add this? IMO, these are critical features for EAP for dealing with > firewalls. Also, we need it to expose remote EJB and Messaging to > OpenShift. > > On 4/4/12 11:04 AM, Andrig Miller wrote: >> As far as I know those features are no longer there >

HornetQ has a servlet you could deploy, although you would have to take care to secure it. There is nothing else out of the box. EJB over HTTP is on the roadmap, it's just lower priority than other items and we have less than a month until we have to code freeze. On 4/4/12 1:43 PM, William DeCoste wrote: > Yikes, ok. For JAX-RS ... there isn't anything OOTB now to integrate > with JNDI, EJB, and Messaging right? I'd have to implement the REST > integration? > > On 4/4/12 11:40 AM, Jason T. Greene wrote: >> It will have to be a 7.2+ / EAP 6.1 thing unless we get significant >> customer demand. JAX-RS is always an option if you really want HTTP >> invocation. >> >> On 4/4/12 1:07 PM, William DeCoste wrote: >>> Thanks Andy. I don't think they are either - at least not yet - from >>> what I see in the EJB, Remoting, and Messaging schema. Is there a plan >>> to add this? IMO, these are critical features for EAP for dealing with >>> firewalls. Also, we need it to expose remote EJB and Messaging to >>> OpenShift. >>> >>> On 4/4/12 11:04 AM, Andrig Miller wrote: >>>> As far as I know those features are no longer there >>> >> >> >

I probably am. I am going to get these components working withing OpenShift 1st and then I'm going to look at exposing them externally. On 4/4/12 11:59 AM, Jason T. Greene wrote: > BTW it's not a lot a work, so if anyone is interested in contributing > ping me. > > On 4/4/12 1:53 PM, Jason T. Greene wrote: >> HornetQ has a servlet you could deploy, although you would have to take >> care to secure it. >> >> There is nothing else out of the box. EJB over HTTP is on the roadmap, >> it's just lower priority than other items and we have less than a month >> until we have to code freeze. >> >> On 4/4/12 1:43 PM, William DeCoste wrote: >>> Yikes, ok. For JAX-RS ... there isn't anything OOTB now to integrate >>> with JNDI, EJB, and Messaging right? I'd have to implement the REST >>> integration? >>> >>> On 4/4/12 11:40 AM, Jason T. Greene wrote: >>>> It will have to be a 7.2+ / EAP 6.1 thing unless we get significant >>>> customer demand. JAX-RS is always an option if you really want HTTP >>>> invocation. >>>> >>>> On 4/4/12 1:07 PM, William DeCoste wrote: >>>>> Thanks Andy. I don't think they are either - at least not yet - from >>>>> what I see in the EJB, Remoting, and Messaging schema. Is there a >>>>> plan >>>>> to add this? IMO, these are critical features for EAP for dealing >>>>> with >>>>> firewalls. Also, we need it to expose remote EJB and Messaging to >>>>> OpenShift. >>>>> >>>>> On 4/4/12 11:04 AM, Andrig Miller wrote: >>>>>> As far as I know those features are no longer there >>>>> >>>> >>>> >>> >> >> > >