+1,
-- Ulhas Bhole
On Fri, Mar 19, 2010 at 1:21 AM, Daniel Kulp wrote:
>
> Once again, there have been a bunch of bug fixes and enhancements that
> have been done compared to the 2.2.6 release. Over 55 JIRA issues
> are resolved for 2.2.7.
>
> List of issues:
>
> https://issues.apache.org/jir
Thanks Eoghan for quick reply. I will try to update build.xml target and
check. I was putting cxf.xml in $CXF_HOME/samples/wsdl_first_rpclit
directory and I think it was picked up because when I ran client it did got
AddressAlreadyInUse for JMX port and also I could connect to the server
using JCon
Hi Eoghan,
I did a few tests and it looks like if I try to connect to the process from
JConsole it doesn't show CXF JMX stats. If I create a new connection using
JMX URL and username/password (cxf/cxf) I do see the CXF MBean appearing.
Thanks for the help.
Regards,
Ulhas Bhole
I just did a few
+1 !
Sergey
On Fri, Mar 19, 2010 at 1:21 AM, Daniel Kulp wrote:
>
> Once again, there have been a bunch of bug fixes and enhancements that
> have been done compared to the 2.2.6 release. Over 55 JIRA issues
> are resolved for 2.2.7.
>
> List of issues:
>
> https://issues.apache.org/jira/secur
Javascript attribute support, he writes lamely.
On Thu, Mar 18, 2010 at 10:24 PM, Daniel Kulp wrote:
>
> The Google Summer of Code program is starting up. Last year, we had a very
> good project completed (SOAP/JMS Spec) and significant work started toward the
> SOAP/TCP stuff.
>
> At this poin
A-ha, my bad, I assumed you were using the remote process option ... so you
just can't see the CXF MBeans when you connect via the jconsole local
process option?
That's easy, just ensure your injected InstrumentationManager bean picks up
the *platform* MBeanServer as opposed to creating a fresh on
+1
/Eoghan
On 19 March 2010 01:21, Daniel Kulp wrote:
>
> Once again, there have been a bunch of bug fixes and enhancements that
> have been done compared to the 2.2.6 release. Over 55 JIRA issues
> are resolved for 2.2.7.
>
> List of issues:
>
> https://issues.apache.org/jira/secure/ReleaseN
- Simple and lightweight Atom HTML-based browser supporting feed links
(next/previous/first/last) based on the existing CXF JAXRS WebClient API to
be added to a rt/management-web component and which will be used for
browsing the CXF logs. This browser will let users see the contents of the
current
Hi
I need to update a JAXRS JAXBElementProvider to create attachment
marshallers/unmarshallers for a xop packaging format be supported.
cxf-rt-databinding-jaxb/org.apache.cxf.jaxb.attachment has all the classes I
need but I'm not sure I should add a strong dependency on
cxf-rt-databinding-jaxb at
+1
Jeff
On Mar 18, 2010, at 6:21 PM, Daniel Kulp wrote:
>
> Once again, there have been a bunch of bug fixes and enhancements that
> have been done compared to the 2.2.6 release. Over 55 JIRA issues
> are resolved for 2.2.7.
>
> List of issues:
> https://issues.apache.org/jira/secure/Releas
Hmm...Those classes depend on the CXF Attachment class which lives in the
api module built after the common-utilities.
Moving it into rt/core, org.apache.cxf.attachment.jaxb, may not be the best
idea. I'll probably just add copies to a rt/frontend/jaxrs, given that there
won't be a need to override
How about doing an integration with ZooKeeper that would allow web/rest
service instances to automatically register their existence with a
run-time registry: at run-time, clients could then mint a reference to
any one of the backend services. This would start as a mechanism to
provide true loca
Nice - thanks Dan. Do you know of any plans for CXF to support WSDL 2.0
soon?
So in the CXF design, the client requests a javascript script through a
URL-based
command and then that script is used for the invocation of the remote
(REST) service.
Is the script on the server side generated at
Uh, no.
The generated Javascript talks SOAP, not REST. We don't have a
generator for REST clients.
On Fri, Mar 19, 2010 at 2:57 PM, Demetris wrote:
>
> Nice - thanks Dan. Do you know of any plans for CXF to support WSDL 2.0
> soon?
>
> So in the CXF design, the client requests a javascript scri
On Friday 19 March 2010 2:57:49 pm Demetris wrote:
> Nice - thanks Dan. Do you know of any plans for CXF to support WSDL 2.0
> soon?
>
> So in the CXF design, the client requests a javascript script through a
> URL-based
> command and then that script is used for the invocation of the remote
> (RE
On Friday 19 March 2010 2:57:49 pm Demetris wrote:
> Nice - thanks Dan. Do you know of any plans for CXF to support WSDL 2.0
> soon?
Forgot to answer this one
Not really unless someone steps up to do it. Really not much demand and very
poor interopability with it since few toolkits support
16 matches
Mail list logo
