Hi Dan,
OK, thanks. For now I've added that just to the
systests/container-integration/grizzly; I'll try to get in touch with
someone at Sun/Oracle to push the artifacts to central.
Cheers
Alessio
On 09/14/2010 09:43 PM, Daniel Kulp wrote:
Bascially, I have "less" problems with using java.ne
Hi Folks,
looking at the org.apache.cxf.Bus interface, I see there's no way to set
features there. The getFeatures() /
setFeatures(Collection features) methods are only in
the CXFBusImpl implementation. Is there a design reason behind this?
I'm thinking it might be interesting to add the featu
On 09/15/2010 10:56 AM, Alessio Soldano wrote:
Hi Folks,
looking at the org.apache.cxf.Bus interface, I see there's no way to
set features there. The getFeatures() /
setFeatures(Collection features) methods are only in
the CXFBusImpl implementation. Is there a design reason behind this?
Re
On Wednesday 15 September 2010 8:37:05 am Alessio Soldano wrote:
> On 09/15/2010 10:56 AM, Alessio Soldano wrote:
> > Hi Folks,
> >
> > looking at the org.apache.cxf.Bus interface, I see there's no way to
> > set features there. The getFeatures() /
> > setFeatures(Collection features) methods a
This is from the java_first_jms sample that I cleaned up. Why is the URL in
the server factory trivial? Why doesn't it need to state the host and the
port? Is 61616 some sort of a default?
Also, how would this look using the JAX-WS Endpoint class?
boolean amqBroker = args.length > 0 && "-active
On Wednesday 15 September 2010 2:33:47 pm Benson Margulies wrote:
> This is from the java_first_jms sample that I cleaned up. Why is the URL in
> the server factory trivial? Why doesn't it need to state the host and the
> port? Is 61616 some sort of a default?
This is part of what Willem and I wer
