Krzysztof,
I've FINALLY had a chance to look at this. I've gone ahead and added it into
the soap binding and wired it into the normal soap transport.It's
definitely a good start. Still plenty of work to do, but the simple case is
working.
I've even tested it a bit with the Sun Glassf
I'd prefer not to have a bunch of different init(..) methods on the interface
itself that everyone HAS to implement.
Ok, given this argument, I'm happy with having a single
void initialize(Map properties)
I guess I could've argued that perhaps only DataBindings shipped with CXF would implement
Basically, I think we should have:
interface PropertiesInitializedDataBinding extends Databinding {
void initialize(Map properties);
}
Then, we make our AbstractDataBinding implement that interface and add a
method like:
void initialize(Map properties) {
Service svc = properties.get("...S
Hi
I think what might make sense for a short term "binary compatible" type
approach is to add a new interface like "ClassSetDataBinding" or something
that defines the init(...) method that is needed for JAXRS. JAX-RS can then
do instanceof on the databinding to see if it WILL work for it.
I think what might make sense for a short term "binary compatible" type
approach is to add a new interface like "ClassSetDataBinding" or something
that defines the init(...) method that is needed for JAXRS. JAX-RS can then
do instanceof on the databinding to see if it WILL work for it. That
Hi Gary
I added a simple test confirming Jettison can output the data meeting the
natural notation criteria. I thought I'd need to add a simple STAX writer
wrapper (which is something one can easily do now with JSONProvider anyway
whenever one wants to customize somehow the output being produced)
+1
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: 29 July 2009 18:56
To: dev@cxf.apache.org
Subject: [VOTE] Release CXF 2.2.3
his is a vote to release CXF 2.2.3
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2
+1
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: 29 July 2009 18:54
To: dev@cxf.apache.org
Subject: [VOTE] Release CXF 2.1.6
This is a vote to release CXF 2.1.6
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the
+1
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: 29 July 2009 18:36
To: dev@cxf.apache.org
Subject: [VOTE] Release CXF 2.0.12
This is a vote to release CXF 2.0.12
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to th
+1
/Eoghan
2009/7/29 Daniel Kulp :
>
> his is a vote to release CXF 2.2.3
>
> Once again, there have been a bunch of bug fixes and enhancements that
> have been done compared to the 2.2.2 release. Over 86 JIRA issues
> are resolved for 2.2.3.
>
>
> List of issues:
> https://issues.apache.org/ji
+1
/Eoghan
2009/7/29 Daniel Kulp :
>
>
> This is a vote to release CXF 2.1.6
>
> Once again, there have been a bunch of bug fixes and enhancements that
> have been done compared to the 2.1.5 release. Over 74 JIRA issues
> are resolved for 2.1.6
>
>
> List of issues:
>
> The Maven staging area i
+1
/Eoghan
2009/7/29 Daniel Kulp :
>
> This is a vote to release CXF 2.0.12
>
> Once again, there have been a bunch of bug fixes and enhancements that
> have been done compared to the 2.0.11 release. Over 32 JIRA issues
> are resolved for 2.0.12
>
> *Note:* as announced earlier this will be th
12 matches
Mail list logo
