+1
/Eoghan
+1
/Eoghan
+1
/Eoghan
Hi Benson,
Do you mean using an NIO MappedByteBuffer?
That would be an interesting thing to look at doing.
Obviously limiting it to MTOM attachments sortta simplifies things,
but of course there's also the possibility to go the whole hog and
write a full-blown transport based on shared memory. N
I'd suspect you've a mismatch between the version of
cxf-rt-frontend-jaxrs and the cxf-api jars.
The former depends on the Message.REQUEST_URI field, which is defined
in the latter.
This field was introduced on 2008-10-21, so you'll need a version of
the API jar from after this date (2.0.10/2.1.4
/systest/jaxrs/BookStoreJaxrsJaxws.java
2009/4/29 Eoghan Glynn :
> I'd suspect you've a mismatch between the version of
> cxf-rt-frontend-jaxrs and the cxf-api jars.
>
> The former depends on the Message.REQUEST_URI field, which is defined
> in the latter.
>
> This fie
What sort of failure are you seeing?
2009/4/29 cybercxf :
>
> I did but I am not sure if I am using right annotations of Restful services.
> Can you verify that for me by taking a look at the code I had attached in
> my first post.
>
> thanks.
Folks,
I'm calling a vote to release CXF Distributed OSGi 1.0.
The dOSGi subproject of CXF provides the Reference Implementation of
the Distribution Software (DSW) component of the Distributed OSGi
Specification[1].
The staging area can be found at:
http://people.apache.org/~eglynn/stage_cxf_
Sent this earlier to dkulp individually, I meant to reply-all.
-- Forwarded message --
From: Eoghan Glynn
Date: 2009/5/5 10:13
Subject: Re: [VOTE] Release CXF dOSGi 1.0
To: Daniel Kulp
2009/5/4 Daniel Kulp :
> On Mon May 4 2009 5:30:49 pm Eoghan Glynn wrote:
>
>>
s to be respun, let's get that cleaned up.
>> >
>> > 3) For the "distribution" builds, the LICENSE file needs to have at least
>> > the pointers to the LICENSES of the bundled deps appended to it. See
>> > the LICENSE in the cxf distributions.
gt;
> Thanks!
> Dan
>
>
> On Wed May 6 2009 9:10:18 am Eoghan Glynn wrote:
>> 2009/5/5 Daniel Kulp :
>> > OK. That kind of make sense (along with what Eoghan said).
>> >
>> > However, I really think there needs to at least be a "README" in the
Folks,
I'm calling a second vote to release CXF Distributed OSGi 1.0.
The main differences between this and the first take are:
- addition of a sources distro
- LICENSE file now contains references to licenses for 3rd party dependencies
- removal of extraneous NOTICEs
- addition of top-l
2009/5/7 Daniel Kulp :
>
> Eoghan,
>
> Could the version be passed into the xslt via an xslt param? That would
> avoid needing to modify it as part of the builds and such.
>
> Dan
Yeah, sure it could.
The literal version in the xslt was just a quick'n'dirty fix for a
minor issue in the OSGi co
Hi Folks,
I'm going to call this result as carried with six +1s and no dissenting votes.
For the record, the aye-sayers were:
eglynn, davidb, sberyozkin, ubhole, dkulp, jgenender
Cheers,
Eoghan
The Apache CXF dOSGi team is proud to announce the availability of our
first full release, 1.0.
The dOSGi subproject of CXF provides the Reference Implementation of
the Distribution Software (DSW) component of the Distributed OSGi
Specification[1].
Download information may be found here[2]
The b
Sorry that should be 7 aye-sayers:
eglynn, davidb, sberyozkin, seanoc, ubhole, dkulp, jgenender
-Original Message-
From: Eoghan Glynn [mailto:eogl...@gmail.com]
Sent: Wed 13/05/2009 17:44
To: dev@cxf.apache.org
Subject: [VOTE][RESULT] Release CXF dOSGi 1.0
Hi Folks,
I'm goi
+1
/Eoghan
2009/5/22 Daniel Kulp :
>
> This is a vote to release CXF 2.2.2
>
> With only 23 JIRA's resolved for 2.2.2, this doesn't have as many "fixes" as
> many of the previous patch releases. HOWEVER, there is a one major new
> feature: the JAX-RS 1.0 TCK now passes. Thus, it's worth a r
+1
/Eoghan
2009/6/8 Daniel Kulp :
>
> Alessio has been one of the primary driving forces behind getting CXF to be a
> certified JAX-WS provider for JBoss. As part of that work, he has identified
> several bugs/issues in CXF and has provided patches for many of them. He has
> also been helping
2009/6/12 David Bosschaert :
>
> 2009/6/11 Sergey Beryozkin :
> ...
>> The only question I have is where this model info should reside, in
>> META-INF/cxf-dosgi ? I'll check with Favid/Eoghan
>
> We already use OSGI-INF/cxf/intents for our CXF-DOSGi specific intents
> files, so maybe somewhere in t
One thing I've had at the back of my mind is WS-RM 1.1 support.
Is that something that would be of interest to you?
Cheers,
Eoghan
2009/6/12 Richard Opalka :
> Hi CXF Team,
>
> what's the current CXF roadmap from WS-* point of view?
> What specs are you going to work on next and what is the sch
Hi Richard,
Apologies for the delay in replying. Please see my comments in-line.
2009/6/15 Richard Opalka :
> what's the current state of CXF WS-RM?
See below.
> I'm asking because we'd like to integrate probably
> WS-RM in our JBossWS CXF integration.
Great that you're thinking of using CXF
S spec", do you mean in
2.3? I haven't heard that JAX-WS 2.2 will address this.
Cheers,
Eoghan
2009/6/18 Richard Opalka
> Hi Eoghan,
>
> see in lined comments below:
>
> Richard
>
> Eoghan Glynn wrote:
>
>> Hi Richard,
>>
>> Apologies for th
Note that in order for any CXF MBean to actually be exposed, you'll
have to enable the IntrumentationManager (which is disabled by
default).
See [1] for details.
Cheers,
Eoghan
[1] http://cwiki.apache.org/CXF20DOC/jmx-management.html
2009/7/21 Rao, Sameer V :
> CXF Asynch processing creates a
+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
+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 :
>
> 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
Thanks for the patch, Dan. Your efforts are much appreciated.
I've committed the fix just now in r809738.
Cheers,
Eoghan
2009/8/27 Daniel Kulp
>
> Please file a JIRA and submit the changes as a patch. This is excellent!
>
> https://issues.apache.org/jira/browse/CXF
>
>
> Dan
>
> On Thu Augus
+1
/Eoghan
2009/10/8 Daniel Kulp
>
> This is a vote to release CXF 2.2.4
>
> Once again, there have been a bunch of bug fixes and enhancements that
> have been done compared to the 2.2.3 release. Over 59 JIRA issues
> are resolved for 2.2.4.
>
>
> List of issues:
> https://issues.apache.org/j
+1
/Eoghan
2009/10/8 Daniel Kulp
>
> This is a vote to release CXF 2.1.7
>
> Once again, there have been a bunch of bug fixes and enhancements that
> have been done compared to the 2.1.6 release. Over 25 JIRA issues
> are resolved for 2.1.7
>
>
> List of issues:
>
> The Maven staging area is
+1
2009/11/15 Daniel Kulp
>
> This is a vote to release CXF 2.2.5
>
> Once again, there have been a bunch of bug fixes and enhancements that
> have been done compared to the 2.2.4 release. Over 90 JIRA issues
> are resolved for 2.2.5
>
>
> List of issues:
>
> The Maven staging area is at:
> ht
+1
/Eoghan
2009/11/15 Daniel Kulp
>
> This is a vote to release CXF 2.1.8
>
> Once again, there have been a bunch of bug fixes and enhancements that
> have been done compared to the 2.1.7 release. Over 25 JIRA issues
> are resolved for 2.1.8
>
>
> List of issues:
>
> https://issues.apache.org
Folks,
I'm calling a vote to release CXF Distributed OSGi 1.1.
The dOSGi subproject of CXF provides the Reference Implementation of the
Remote Services Specification version 1.0, Chapter 13 in the OSGi Compendium
Specification [1].
The release notes contain a description of new features and issu
Folks,
I'm going to declare this vote as passed, with the following votes cast:
+1 (binding): Sergey Beryozkin, David Bosschaert, Sean O'Callaghan, Ulhas
Bhole, Eoghan Glynn
+1 (non binding): Andres Olarte
I've promoted the artifacts to central and will copy the distributions t
+1
Cheers,
Eoghan
2009/12/3 Daniel Kulp
>
>
> Cyrille has submitted several patches to various management and logging
> related things for CXF starting way back in February. I think he's up to
> 7
> or 8 submitted patches.He's also been hanging around the user list for
> almost a year ans
> Hope everyone is ok with this.
Go for it!
And welcome to the project, Marc.
Cheers,
Eoghan
Hmmm ... smells like a Nexus issue.
If I follow that link, I'm redirected to:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/cxf/dosgi/cxf-dosgi-remote-service-admin-interfaces/1.0.0/cxf-dosgi-remote-service-admin-interfaces-1.0.0.jar
with the message:
Item not foun
+1
Cheers,
Eoghan
2010/1/20 Freeman Fang
> +1
>
> Freeman
>
> On 2010-1-20, at 上午9:44, Daniel Kulp wrote:
>
>
>> This is a vote to release CXF 2.2.6
>>
>> Once again, there have been a bunch of bug fixes and enhancements that
>> have been done compared to the 2.2.5 release. Over 78 JIRA issue
+1
Cheers,
Eoghan
2010/1/20 Daniel Kulp
>
> This is a vote to release CXF 2.1.9
>
> Once again, there have been a bunch of bug fixes and enhancements that
> have been done compared to the 2.1.8 release. Over 43 JIRA issues
> are resolved for 2.1.9
>
> *Note:* as announced earlier this will be
David,
One thing to note about pax-exam is that its doesn't AFAIK have a feature
analogous to the spring-osgi-test support for accessing and adding to the
manifest for the on-the-fly bundle.
Now I don't know whether we could possibly live without this
manifest-mangling as currently done by the dO
cent tiny bundles integration could take care
> of this. Have a look at the bottom example in
> http://wiki.ops4j.org/display/paxexam/ExamAndTinybundles. Do you think
> that will do it?
>
> Cheers,
>
> David
>
> 2010/1/22 Eoghan Glynn :
> >
> > David,
> >
&g
Have you considered just using the ServiceMix versions of the JSR-311 spec?
Code here:
http://svn.apache.org/repos/asf/servicemix/smx4/specs/trunk/jsr311-api-1.0/
http://svn.apache.org/repos/asf/servicemix/smx4/specs/trunk/jsr311-api-1.1/
Artefacts here:
http://repo2.maven.org/maven2/org/apache/s
+1
Cheers,
Eoghan
On 9 March 2010 16:09, David Bosschaert wrote:
> Hi all,
>
> I would like to propose Marc Schaaf as a committer for CXF. Marc has
> written a tremendous amount of code for CXF-DOSGi (which he provided
> as patches to JIRA), making it compliant with the OSGi 4.2 Remote
> Servic
+1
/Eoghan
On 10 March 2010 14:29, Daniel Kulp wrote:
>
> David's been doing a good job lately of answering questions on the
> mailing lists and getting involved there. He's also submitted several
> high
> quality patches for the ws-security and security-policy stuff. The patches
> are all v
Ulhas,
How are you picking up the config file?
For example, if you're running the server via ant, you'd need to change the
server target defined in $CXF_HOME/samples/wsdl_first_rpclit/build.xml from:
to:
Alternatively, you could change the
$CXF_HOME/sampl
for JMX port and also I could connect to the server
> > using JConsole.
> >
> > I will try your route.
> >
> > Regards,
> >
> > Ulhas Bhole
> >
> >
> > On Thu, Mar 18, 2010 at 10:05 PM, Eoghan Glynn
> wrote:
> >
> >> Ulhas,
&
+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
> Tasks left would be:
> * When the above is done, cut the actual release candidate(s).
I can help cutting the release when you're ready to go.
Cheers,
Eoghan
On 11 June 2010 16:53, David Bosschaert wrote:
> Great, thanks Marc!
>
> I think we're getting close to something that is releasable.
Have you tried overriding the org.osgi.framework.system.packages property in
felix/conf/config.properties, with a list of packages specifically excluding
javax.xml.ws.*?
This is the approach taken by SMX to get around these sort of issues. See
for ex:
wget
https://www.apache.org/dist/servicemix/s
..
>
> I'm just curious, why was the CXF import updated to include 0.0.0 ?
>
> cheers, Sergey
>
>
> On Mon, Jun 28, 2010 at 5:55 PM, Eoghan Glynn wrote:
>
> > Have you tried overriding the org.osgi.framework.system.packages property
> > in
> > fel
ugh most of the
> > > config.properties are probably reusable across diff versions)
> > > DOSGI RI does only ship the fragments of config properties which are
> > built
> > > during the multi-bundle build...
> > >
> > > I'm just curious, why was the
> A more long-term option might to ship an entire distro of karaf with
dOSGi,
> I'm also opposed to turning the CXF-DOSGi distribution into a Karaf
> distro as OSGi is all about reusable components that can be used in
> any compliant OSGi Framework. We shouldn't have to ship a tweaked
> runtime for
> I think we're ready for a release!
Great!
> Eoghan would you have some cycles?
Yeah.
A couple of things before I go ahead and cut the release:
- can you update the release notes[1] with a summary of what's new in this
release?
- does this TimeoutException[2] in TestExportService.testAccessE
happy that I'm seeing a
phantom issue here.
Cheers,
Eoghan
On 19 July 2010 10:30, wrote:
> Hi Eoghan,
>
> On 17 July 2010 12:59, Eoghan Glynn wrote:
> >> Eoghan would you have some cycles?
> >
> > Yeah.
>
> Excellent!
>
> > A couple of things
tweaking to run on
> all machines (including yours - if you have any tips I would love to
> hear them :)
>
> Cheers,
>
> David
>
> On 19 July 2010 12:35, Eoghan Glynn wrote:
> >
> > Hi David,
> >
> >> This exception happens when the remot
Folks,
I'm calling a vote to release CXF Distributed OSGi 1.2.
In addition to providing the Reference Implementation to the OSGi Remote
Services Specification, the CXF Distributed OSGi 1.2 release now also
provides the Reference Implementation of the OSGi Remote Service Admin
Specification versio
Also tags to both 1.1 and 1.2 are in there...
>
> Cheers,
>
> David
>
> On 19 July 2010 23:45, Eoghan Glynn wrote:
> > Folks,
> >
> > I'm calling a vote to release CXF Distributed OSGi 1.2.
> >
> > In addition to providing the Reference Implement
emos and
> > it works fine.
> >
> > Here's my +1
> >
> > David
> >
> > On 20 July 2010 08:42, Eoghan Glynn wrote:
> > > Here's the raw text with the link formatting removed:
> > >
> > >
> > > Folks,
>
Folks,
I'm pulling this release after noticing that the release notes in the
multi-bundle distro weren't updated for 1.2.
I'll cut a take-two and call another vote later on today.
Cheers,
Eoghan
On 20 July 2010 08:42, Eoghan Glynn wrote:
>
> Here's the raw tex
Folks,
Now that the release notes are all fixed up, I'm calling a second vote to
release
CXF Distributed OSGi 1.2.
The release notes contain a description of new features and bugs fixed
in this release:
http://svn.apache.org/repos/asf/cxf/dosgi/trunk/distribution/sources/src/main/release/releas
Folks,
I'm going to declare this vote as passed, with the following votes cast:
+1: Sean O'Callaghan, Sergey Beryozkin, David Bosschaert, Marc Schaaf, Jeff
Genender, Dan Kulp, Eoghan Glynn
I've promoted the artifacts to central and copied the distributions to the
cxf/dosgi
+1
/Eoghan
Daniel Kulp wrote:
This is a vote to release CXF 2.1.
Obviously, this is a pretty big release with a bunch of new things like
JAX-WS 2.1 support, the JAX-RS stuff, the javascripts stuff, the CORBA
binding from yoko, etc
Of course, the other MAJOR new feature: it's no longer
+1 (take 2)
Daniel Kulp wrote:
This is a vote to release CXF 2.1.
Obviously, this is a pretty big release with a bunch of new things like
JAX-WS 2.1 support, the JAX-RS stuff, the javascripts stuff, the CORBA
binding from yoko, etc
Of course, the other MAJOR new feature: it's no longer
+1
/Eoghan
Daniel Kulp wrote:
This is a vote to release CXF 2.0.6
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.0.5 release. Over 20 JIRA issues are
marked as resolved for 2.0.6.
Of course, the other MAJOR new feature: it's no lo
Folks,
Does this error ring a bell with anyone?
"java.lang.AbstractMethodError:
org.apache.xerces.dom.DeferredDocumentImpl.getInputEncoding()Ljava/lang/String;"
On a clean checkout of CXF trunk, I'm seeing a bunch of system tests
fail with this error, seemingly triggered by a call into the
---
Peter Jones wrote:
Hi Eoghan,
On Fri, May 23, 2008 at 04:51:01PM +0100, Eoghan Glynn wrote:
Folks,
Does this error ring a bell with anyone?
"java.lang.AbstractMethodError:
org.apache.xerces.dom.DeferredDocumentImpl.getInputEncoding()Ljava/lang/String;"
I saw this error rece
Margulies wrote:
Have you been redecorating your 'endorsed' directory, or has your
distro been doing that behind your back? Do you have some specific
Xerces version in a POM someplace?
On Fri, May 23, 2008 at 11:51 AM, Eoghan Glynn <[EMAIL PROTECTED]> wrote:
Folks,
Does thi
Benson Margulies wrote:
Are you sure you got this on the trunk?
Yep, I think so ...
/work/cxf/work_23May2008/trunk> svn info .
Path: .
URL: http://svn.apache.org/repos/asf/cxf/trunk
Repository Root: http://svn.apache.org/repos/asf
Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
Revision:
Benson Margulies wrote:
Fix committed on trunk.
Thanks Benson, I just picked up your change.
Slight tweak required, as the catch clause on Exception that you added
around the factory.setBuilder() call doesn't catch AbstractMethodError.
But switching to a more generic catch Throwable and
Daniel Kulp wrote:
On May 27, 2008, at 12:26 PM, Eoghan Glynn wrote:
Thanks Dan,
Following the instructions on [1] I've run into an authentication
failure after only a few modules are deployed to the repo.
Is there a way of rolling back the partially deployed artifacts, do
you
Benson Margulies wrote:
PKI already works. Just put your ssh key into your people.apache.org .ssh
dir.
Thanks Benson ... I was sure I'd copied over my public key ages ago, but
just checked my home dir on people.apache.org and I didn't even have
a ~/.ssh dir, never mind an authorized_keys
Hi Dan,
I had to do an manual install of opensaml-1.1.jar in my local repo in
order to get a 2.0.x build to work.
Is the opensaml stuff up on some obscure maven-repo that I need to add
to my ~/.m2/settings.xml?
Cheers,
Eoghan
[EMAIL PROTECTED] wrote:
Author: dkulp
Date: Wed Jun 4 07:58
+1
Daniel Kulp wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is a vote to release CXF 2.1.1
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.1 release. Over 74 JIRA issues are
resolved for 2.1.1 which is a large number of f
+1
Daniel Kulp wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is a vote to release CXF 2.0.7
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.0.7 release. Over 48 JIRA issues are
resolved for 2.0.7 which is a large number o
Daniel Kulp wrote:
5) OSGi stuff - I know there are some OSGi enhancements in the works
that could be pulled in:
a) osgi http transport - this currently lives in ServiceMix, but
could be pulled into CXF to work with other OSGi runtimes
b) Distributed OSGi (RFC 119) - there is work being
Christian Schneider wrote:
I would really like to see good osgi integration as we plan to rely
quite heavily on osgi in the future. But as I myself are only starting
on this I don´t know much about the details. Basically I would like to
be able to connect the osgi internal services with cxf t
Folks,
Does anyone know if svnmerge.py can be used to report on the commits to
trunk that have been "blocked" wrt to merging out to the 2.0.x_fixes branch?
Its sortta like a retrospective "avail" option that I'm after, i.e.
gimme all the commits that were available for merging, but were sele
use subversion 1.5 which I'm not
sure if everyone is ready to do or not.
Dan
On Jul 17, 2008, at 8:54 AM, Eoghan Glynn wrote:
Folks,
Does anyone know if svnmerge.py can be used to report on the commits
to trunk that have been "blocked" wrt to merging out to the
2.0.x_fixes br
+1
Daniel Kulp wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is a vote to release CXF 2.0.8
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.0.8 release. Over 28 JIRA issues are
resolved for 2.0.8. Most importantly, thi
+1
Daniel Kulp wrote:
This is a vote to release CXF 2.1.2
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.1.1 release. Over 67 JIRA issues
are resolved for 2.1.2.
List of issues:
https://issues.apache.org/jira/secure/ReleaseNote.jsp
-1 to decommissioning the CXF JMS transport.
If there are perceived shortcomings in the CXF JMS transport config,
lets identify these issues, raise corresponding JIRAs, and get them fixed.
/Eoghan
Benson Margulies wrote:
My question is dumber. If Camel, a part of Apache, is a superior
comes
Dunno if I'd agree with this JIRA, if I've understood it correctly.
For a request-response MEP, WS-RM can be configured so that a "202
Accepted" response is immediately sent back to the client (possibly
including an eager ACK) and then whenever it becomes available the real
response is sent o
, Eoghan Glynn <[EMAIL PROTECTED]> wrote:
Dunno if I'd agree with this JIRA, if I've understood it correctly.
For a request-response MEP, WS-RM can be configured so that a "202
Accepted" response is immediately sent back to the client (possibly
including an eager ACK) an
David Bosschaert wrote:
Hi all,
I'm trying to get rid of the exception that shows up when you distribute
a service in a bundle that doesn't provide an intent-map.xml file.
Currently this seems to work well, but an exception comes up on the
screen. If a user doesn't provide this map, simply th
Daniel Kulp wrote:
Eoghan,
On Thursday 11 September 2008 5:52:20 am Eoghan Glynn wrote:
Next question.
When I expose a service registered under multiple interfaces, what is it
supposed to do in today's codebase?
Will it somehow expose both interfaces over the wire or does it just
pic
+1
/Eoghan
Daniel Kulp wrote:
Christian has been doing quite a bit of very good work doing an almost "ground
up" re-write of the JMS transport which is a very challenging and complicated
task.
He's done quite a bit of work documenting various JMS things on the Wiki and
even wrote an article
Thanks for this David,
I'll apply your patch now.
Cheers,
Eoghan
David Bosschaert wrote:
Hi all,
I attached a patch for a compilation failure of the dosgi code in the
sandbox to bug https://issues.apache.org/jira/browse/CXF-1830
Would greatly appreciate if someone could apply.
Many thanks
Thanks David,
Just applied the patch.
Cheers,
Eoghan
David Bosschaert wrote:
Hi all,
I've attached a patch that implements the first part of
https://issues.apache.org/jira/browse/CXF-1836 to this bug.
New unit tests are included too.
Would greatly appreciate if someone could apply the pat
Now applied, thanks ...
/Eoghan
David Bosschaert wrote:
Hi all,
I've attached a patch with the implementation of the
DistributionProvider.getRemoteServices() API to
https://issues.apache.org/jira/browse/CXF-1836
New unit tests included too.
Small changes - frequent commits :) If larger pa
Thanks for the patch David, now applied.
/Eoghan
David Bosschaert wrote:
Hi all,
I attached a further patch for CXF-1811 to this bug:
https://issues.apache.org/jira/secure/attachment/12391563/property_rename2.patch
The patch is called 'property_rename2.patch'. A direct link to the
patch:
Hi Dan,
Dan Diephouse made a similar proposal about 18 months ago, and I was
opposed at the time as it didn't accomodate what was trying to acheive
with ConduitSelectors.
That discussion was also conflated with a bunch of other proposed
changes, but in retrospect I think the bean had the
Daniel Kulp wrote:
- ensuring the multiplicity of conduit beans configured alongside a
failover selector is consistent with the set of ports defined in the
WSDL, as the CXF static failover strategy is based on burning the
alternate ports into a multi-port service definition in the WSDL.
Well,
Thanks David, patch applied.
/Eoghan
David Bosschaert wrote:
Hi all,
I've attached another patch to
https://issues.apache.org/jira/browse/CXF-1836 that implements the
required Service Properties on the DistributionProvider service. The
patch is called DistributionProvider-properties.patch
Thanks David,
However svn-apply got a bit confused when I tried to apply the patch.
Did you create some new elements in your working copy and then move them
a different directory?
For example, svn-apply complains that the patch attempts to delete the
non-existent:
dsw/cxf-dsw/src/main/res
/remote-services in a
few places...
FYI I created the patch using Tortoise 1.5.0 on Windows...
Cheers,
David
Eoghan Glynn wrote:
Thanks David,
However svn-apply got a bit confused when I tried to apply the patch.
Did you create some new elements in your working copy and then move
them a
this works.
Cheers,
David
Eoghan Glynn wrote:
Did you do the moves as a single step, or more like moving a to c via:
mv a b
mv b c
David Bosschaert wrote:
Yeah, I moved intent-map.xml from META-INF/osgi into a new directory
called OSGI-INF/cxf/intents in a few places. I also mov
Thanks David, patch applied.
David Bosschaert wrote:
Hi all,
I've attached a patch to https://issues.apache.org/jira/browse/CXF-1854
which contains the beginning of a distribution of the DOSGi stuff. The
distribution contains all the required dependencies (OSGi bundles) is
built as part of
+1
Willem Jiang wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is a vote to release CXF 2.0.9
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.0.9 release. Over 37 JIRA issues
are resolved for 2.0.9 which is a large number
Thanks David, applied.
Cheers,
Eoghan
-Original Message-
From: David Bosschaert [mailto:[EMAIL PROTECTED]
Sent: Thu 16/10/2008 12:03
To: dev@cxf.apache.org
Subject: [DOSGi] Patch for CXF-1876
Hi all,
I've attached a patch to https://issues.apache.org/jira/browse/CXF-1876
Would greatly
Thanks David for this summary!
> There is a lot of work that still needs to be done:
> ...
> - We need better documentation.
On the subject of docco for dOSGi, I wrote up a quick "getting started" guide a
while back. It would need a bit of updating as it dates from before the
donation of the
tests. Would appreciate if they could be applied too.
Cheers,
David
2008/10/16 Eoghan Glynn <[EMAIL PROTECTED]>:
>
> Thanks David, applied.
> Cheers,
> Eoghan
>
> -Original Message-
> From: David Bosschaert [mailto:[EMAIL PROTECTED]
> Sent: Thu 16/10/2008 12:03
1 - 100 of 128 matches
Mail list logo
