+1
On Thu, Feb 24, 2011 at 8:28 AM, Freeman Fang wrote:
> +1
>
> Freeman
> On 2011-2-24, at 上午4:30, Daniel Kulp wrote:
>
>>
>>
>> We've resolved over 50 issues since 2.3.2. Thus, we really should get
>> 2.3.3 out, especially since 2.3.2 contained an issue preventing it from
>> being used as a
+1
Alessio
On 02/23/2011 09:30 PM, Daniel Kulp wrote:
We've resolved over 50 issues since 2.3.2. Thus, we really should get 2.3.3
out, especially since 2.3.2 contained an issue preventing it from being used as
a JAX-WS implementation for J2EE
containers.
List of issues:
https://issues.a
Hi Sergey,
On Thu, Feb 17, 2011 at 12:34 PM, Sergey Beryozkin wrote:
> Hi Tomasz
>
> 1. LogBrowser has a showstopper bug which I'm sure is due to the fact we
> just did not look at it for a while :-). Basically, when I go and generate
> the logs, and then click 'refresh' on the en
+1
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: 23 February 2011 20:31
To: dev@cxf.apache.org
Subject: [VOTE] Apache CXF 2.3.3
We've resolved over 50 issues since 2.3.2. Thus, we really should get 2.3.3
out, especially since 2.3.2 contained an issue preventin
+1
Glen
On 2/23/2011 6:23 PM, Eric Johnson wrote:
+1
On Wed, Feb 23, 2011 at 6:04 PM, Sergey Beryozkin wrote:
+1
thanks, Sergey
On Wed, Feb 23, 2011 at 8:30 PM, Daniel Kulp wrote:
We've resolved over 50 issues since 2.3.2. Thus, we really should get 2.3.3
out, especially since 2.3.2
Hi Willem
Are you planning to commit to the trunk ? Just wondering why you
started from the 2.3.x branch...
Cheers, Sergey
On Thu, Feb 24, 2011 at 11:58 AM, wrote:
> Author: ningjiang
> Date: Thu Feb 24 11:58:26 2011
> New Revision: 1074119
>
> URL: http://svn.apache.org/viewvc?rev=1074119&vie
+1.
Colm.
On Thu, Feb 24, 2011 at 11:52 AM, Glen Mazza wrote:
> +1
>
> Glen
>
> On 2/23/2011 6:23 PM, Eric Johnson wrote:
>>
>> +1
>>
>> On Wed, Feb 23, 2011 at 6:04 PM, Sergey Beryozkin
>> wrote:
>>>
>>> +1
>>>
>>> thanks, Sergey
>>>
>>> On Wed, Feb 23, 2011 at 8:30 PM, Daniel Kulp wrote:
>>>
The Web Application Description Language (WADL) is new to me.
Does CXF support WADLs in any way, relative to the REST style?
Also, what would be more applicable, WADLs or WSDLs in support of
JMS/RESTful services?
Thanks!
Hi all,
I'm hoping someone can help me out here...
We recently upgraded CXF from 2.2.3 to 2.3.1. In doing so, it would appear
that some of our webservices have been broken in the process.
Specifically, the issue we're having is that our client is passing across a
field like NaN, which previousl
You can at least view the WADL using ?_wadl at the end of the service
string in a browser.
Unsure, but JMS/REST would seem to be a contradiction, because REST is
based on the HTTP transport.
Glen
On 2/24/2011 9:17 AM, robert wrote:
The Web Application Description Language (WADL) is new to m
Thanks for the info... I'm still trying to figure some things out
though...
Looks like WSDLs for REST are supported with WSDL 2.0:
http://www.ibm.com/developerworks/webservices/library/ws-restwsdl/.
So with REST... should the target be in using WSDLs (i.e. 2.0), WADLs,
or neither... or it depend
On 2/24/11 9:17 AM, robert wrote:
Also, what would be more applicable, WADLs or WSDLs in support of
JMS/RESTful services?
Check out HornetQ's REST interface:
http://jboss.org/hornetq/rest
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
Best to ask on the CXF User's list, devs are on both, but many more
people are on Users.
You can look over the wire to see what is being sent/received[1]
differently--it could be something different, or in addition to, the NaN
issue. I believe we went from JAXB 2.1 to 2.2 between CXF 2.2 and
>> Check out HornetQ's REST interface:
>>
>> http://jboss.org/hornetq/rest
>>
> This is of course a fine effort, but it's off-topic for the CXF dev list :-)
though supporting the interface you've built for HornetQ might be an
interesting option - but I guess it would be more of interest to the
Act
Hi Bill
On Thu, Feb 24, 2011 at 2:45 PM, Bill Burke wrote:
>
>
> On 2/24/11 9:17 AM, robert wrote:
>>
>> Also, what would be more applicable, WADLs or WSDLs in support of
>> JMS/RESTful services?
>>
>
> Check out HornetQ's REST interface:
>
> http://jboss.org/hornetq/rest
>
This is of course a fi
Is Apache WSIF JMS extensions considered dead too (in addition to the
main project Apache WSIF) ?
http://ws.apache.org/wsif/providers/wsdl_extensions/jms_extension.html
Exactly what is going on with WSIF? Is it still hanging on? Or did
someone make the move to make it a TLP and retire it?
Hi
On Thu, Feb 24, 2011 at 2:37 PM, robert wrote:
>
> Thanks for the info... I'm still trying to figure some things out
> though...
>
> Looks like WSDLs for REST are supported with WSDL 2.0:
> http://www.ibm.com/developerworks/webservices/library/ws-restwsdl/.
>
> So with REST... should the targe
I'm looking at the ActiveMQ REST Interface documentation now...
http://activemq.apache.org/rest.html
Thanks!
Robert
On Thu, 24 Feb 2011 15:19:19 +, Sergey Beryozkin
wrote:
>>> Check out HornetQ's REST interface:
>>>
>>> http://jboss.org/hornetq/rest
>>>
>> This is of course a fine effort, b
My bad... I posted the same message to the users and dev mailing
lists... as I thought the users post did not go through (as I thought
the delay meant I was unsubscribed).
... sorry about the clutter... on this one too.
-- Robert
I think you'll find that the reliability guarantees just don't exist in
ActiveMQ's REST interface and that it is very feature-light. (FYI, not
saying ActiveMQ can't guarantee reliability, just that its REST
interface is kinda weak).
On 2/24/11 10:27 AM, robert wrote:
I'm looking at the Acti
CXF supports SOAP over JMS; http://www.w3.org/TR/soapjms/.
Should the bindings and service extensions defined by this spec be
better suited in a supported WSDL or WADL?
I assume WADL as supported by CXF?
Thanks!
Hi
On Thu, Feb 24, 2011 at 3:48 PM, robert wrote:
> CXF supports SOAP over JMS; http://www.w3.org/TR/soapjms/.
>
> Should the bindings and service extensions defined by this spec be better
> suited in a supported WSDL or WADL?
>
> I assume WADL as supported by CXF?
Yes but only JAX-RS endpoints
Actually, Benson, that might not be the case (I hope it isn't) -- if you
look on the Attic: http://attic.apache.org/ they have four Jakarta
subprojects listed, and none of the four were TLPs. (Only Jakarta
itself is.) Same with Crimson (XML TLP) I suppose.
Glen
On 01.02.2011 19:42, Benson
On Thursday 24 February 2011 9:22:28 AM Aaron Ehrensberger wrote:
> Hi all,
>
> I'm hoping someone can help me out here...
>
> We recently upgraded CXF from 2.2.3 to 2.3.1. In doing so, it would appear
> that some of our webservices have been broken in the process.
>
> Specifically, the issue w
Does CXF use something in place of the WSDL JMS Extension and this
namespace: http://schemas.xmlsopa.org/wsdl/jms?
Thanks!
The User's list would be more appropriate for this question, also is it
not already answered within our user's guide?
Glen
On 2/24/2011 2:26 PM, robert wrote:
Does CXF use something in place of the WSDL JMS Extension and this
namespace: http://schemas.xmlsopa.org/wsdl/jms?
Thanks!
I'll take a look and try to post to the appropriate forums, thanks!
-- Robert
On Thu, 24 Feb 2011 14:29:05 -0500, Glen Mazza
wrote:
> The User's list would be more appropriate for this question, also is
> it not already answered within our user's guide?
>
> Glen
>
> On 2/24/2011 2:26 PM, rober
Perfect!
It would appear that we need to investigate our flex client then because it
seems to be passing along valid NaNs for floats and doubles, but it's also
passing them for integers and we'll need to figure that out.
Thanks for the help.
Aaron
On Thu, Feb 24, 2011 at 2:06 PM, Daniel Kulp
On Thursday 24 February 2011 2:26:08 PM robert wrote:
> Does CXF use something in place of the WSDL JMS Extension and this
> namespace: http://schemas.xmlsopa.org/wsdl/jms?
At the last minute, the spec was "changed" so the namespace that is supposed
to be used is:
http://www.w3.org/2010/soapjms/
Thanks... that namespace isn't on this page though:
http://cxf.apache.org/docs/schemas-and-namespaces.html.
-- Robert
On Thu, 24 Feb 2011 15:06:44 -0500, Daniel Kulp
wrote:
> On Thursday 24 February 2011 2:26:08 PM robert wrote:
>> Does CXF use something in place of the WSDL JMS Extension and th
CXF JMS transport supports JMS URI which is part of JMS over SOAP spec
out of box. I think you can use it with JAXRS frontend without any
trouble.
2011/2/24, robert :
> CXF supports SOAP over JMS; http://www.w3.org/TR/soapjms/.
>
> Should the bindings and service extensions defined by this spec be
31 matches
Mail list logo