a18725bf6cd1f27e824a7e9
> >
>
> Here is my +1
>
>
> --
> Daniel Kulp
> dk...@apache.org <mailto:dk...@apache.org> - http://dankulp.com/blog <
> http://dankulp.com/blog>
> Talend Community Coder - http://talend.com <http://coders.talend.com/>
>
--
Guillaume Nodet
the jetty version
> seems more reasonable.
> >
> > Any thoughts?
> >
> > Thanks!
> > －
> > Freeman(Yue) Fang
> >
> > Red Hat, Inc.
> > FuseSource is now part of Red Hat
> >
> >
> >
>
> --
> Daniel Kulp
;>>> cxf-core
> >>>>>
> >>>>> Hi Christian,
> >>>>>
> >>>>> Regarding Karaf4 and OSGi: as Guillaume says the Spring DM isn't
> >>>>>
> >>>> supported
> >>>
>
gt;> > -Original Message-
> >> > From: Christian Schneider [mailto:cschneider...@gmail.com] On Behalf
> >> > Of Christian Schneider
> >> > Sent: Freitag, 23. September 2016 17:29
> >> > To: dev@cxf.apache.org
> >> > Subj
t should guarantee that all modules work
>>> as before. This change should make sure that refreshs only happen to
>>> modules that provide namespaces.
>>> As a second step we should then check if we can improve on that. This
>>> all of course depends if we find a feasible
It looks like nobody objects, so I'll go ahead and drop Karaf 3 support.
2016-09-20 22:48 GMT+02:00 Guillaume Nodet :
> Sounds good to me.
> It would be obviously easier to maintain.
>
> 2016-09-20 15:06 GMT+02:00 Daniel Kulp :
>
>> Looking at Guillaume’s changes for
mailto:dk...@apache.org> - http://dankulp.com/blog <
> http://dankulp.com/blog>
> Talend Community Coder - http://coders.talend.com <
> http://coders.talend.com/>
>
--
Guillaume Nodet
Red Hat, Open Source Int
-
> Daniel Kulp
> dk...@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>
--
Guillaume Nodet
Red Hat, Open Source Integration
Email: gno...@redhat.com
Web: http://fusesource.com
Blog: http://gnodet.blogspot.com/
I think we should do differently ;-)
But this is not a blocking issue, so I'll try to propose something for
3.1.2.
Ideally, I'd like to have a complete and verified feature descriptor for
karaf 4.0.0 (the karaf maven plugin can now do an OSGi resolution to ensure
the feature is complete). CXF also
tions comes with a
cxf-tools feature which can't be used anymore in 3.x.
Given I'm verifying those features, which way should I go ? Remove this
feature or change the maven packaging to bundle ?
Cheers,
Guillaume Nodet
tence-work-for-WS-Notification-tp5598400p5598400.html
> Sent from the cxf-dev mailing list archive at Nabble.com.
>
--
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
FuseSource, Integration everywhere
http://fusesource.com
gets to go next.
--
----
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
===
> --- cxf/trunk/parent/pom.xml (original)
> +++ cxf/trunk/parent/pom.xml Tue Oct 11 21:02:14 2011
> @@ -56,7 +56,10 @@
>
>
> 1.1.2
> +
> 5.4.2
> +5.5.0
> 10.2.2.0
>
> 2.1
>
>
>
--
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
On Tue, Oct 11, 2011 at 22:34, Daniel Kulp wrote:
> On Tuesday, October 11, 2011 10:28:11 PM Guillaume Nodet wrote:
> > I tried to minimize the number of dependencies installed by not
> installing
> > the whole activemq and cxf features.
>
> Well, it NEEDS the CXF fea
=
> --- cxf/trunk/services/wsn/wsn-osgi/pom.xml (original)
> +++ cxf/trunk/services/wsn/wsn-osgi/pom.xml Tue Oct 11 20:19:25 2011
> @@ -34,7 +34,7 @@
>
>
>
> -org.apache.cxf
> +org.apache.cxf.services.wsn
> cxf-services-wsn-core
> ${project.version}
>
>
>
>
--
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
tuff currently being tied to ActiveMQ and options around that:
>>
>> http://irclogs.dankulp.com/**logs/irclogger_log/cxf?date=**
>> 2011-10-05,Wed&sel=194#l190<http://irclogs.dankulp.com/logs/irclogger_log/cxf?date=2011-10-05,Wed&sel=194#l190>
>>
>> That last st
On Wed, Oct 5, 2011 at 18:01, Daniel Kulp wrote:
> On Wednesday, October 05, 2011 5:22:01 PM Guillaume Nodet wrote:
> > I've started to re-architect the WS-Notification implementation to get
> rid
> > of JBI and be pure JAX-WS based.
> > The results are available at
ke to keep the implementation lightweight and keep it pure JAXWS
based if possible.
On Fri, Jul 8, 2011 at 10:20, Guillaume Nodet wrote:
> Just want to start a discussion on WS-Notification because I've had a chat
> last week with a ServiceMix user about that.
>
> That component
orks real well and hence becomes a perfect
> complement to the CXF architecture. Areas for interception are synchronous
> vs asynchronous (i.e. pull point immediate return value vs. pub/sub), etc.
>
> Just my 3.14159 cents ;-)
>
> Jeff
>
>
> On Jul 8, 2011, at 10:00 AM, Guill
11, at 7:47 AM, Guillaume Nodet wrote:
>
> > We're not talking about implementing something new here. We have an
> > existing code base in ServiceMix that we may work on to remove the ties
> onto
> > JBI. We were just wondering if CXF would be a better place for it
> Email:ff...@fusesource.com
> > Web: fusesource.com
> > Twitter: freemanfang
> > Blog: http://freemanfang.blogspot.com
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
> --
> Alessio Soldano
> Web Service Lead, JBoss
>
--
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
Best Regards
>> Freeman
>> --**---
>> Freeman Fang
>>
>> FuseSource
>> Email:ff...@fusesource.com
>> Web: fusesource.com
>> Twitter: freemanfang
>> Blog: http://freemanfang.blogspot.**com <http://freemanfang.blogspot.com>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
--
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
; >> > jetty, servlet, and OSGi. The user pretty much selects the one
>> >> > they want by importing the appropriate cxf-extension file and not the
>> >> > others in their spring config. While it works, there is a down side:
>> >> > you can only hav
Sorry for the nois, it was intended to be sent to d...@aries.apache.org
On Wed, Feb 9, 2011 at 18:31, Guillaume Nodet wrote:
> I would suggest the use of confluence as a real wiki.
> Keep our web site the way it is, but the page Zoe is currently working
> on imho could clearly fit in a
I would suggest the use of confluence as a real wiki.
Keep our web site the way it is, but the page Zoe is currently working
on imho could clearly fit in a real wiki, as it's not project
documentation ...
Thoughts ?
--
Cheers,
Guillaume Nodet
Blog:
gt;>>>>>>> Commercial CXF Offerings
>>>>>>>>>>
>>>>>>>>>> Apache CXF is a widely used project. As such several companies have
>>>>>>>>>> build
>>>>>>>
orgapachecxf-042/org/apache/cxf/apache-cxf/2.3.2/
>
> This release is tagged at:
> http://svn.apache.org/repos/asf/cxf/tags/cxf-2.3.2
> http://svn.apache.org/repos/asf/cxf/xjc-utils/tags/xjc-utils-2.3.2/
>
> The vote will be open for 72 hours.
>
> Here is my +1.
gged at:
> http://svn.apache.org/repos/asf/cxf/tags/cxf-2.1.7
>
>
> Here is my +1. The vote will be open here for at least 72 hours.
>
>
> --
> Daniel Kulp
> dk...@apache.org
> http://www.dankulp.com/blog
>
--
Cheers,
Guillaume Nodet
ing-009/org/apache/cxf/apache-cxf/2.2.4
>
> This release is tagged at:
> http://svn.apache.org/repos/asf/cxf/tags/cxf-2.2.4
>
>
> Here is my +1. The vote will be open here for at least 72 hours.
>
>
> --
> Daniel Kulp
> dk...@apache.org
> http://www.d
/src/main/java/org/apache/cxf/transport/http_jetty/JettyHTTPDestination.java
>>>>
>>>> 7. System tests :
>>>>
>>>>
>>>>
>>>> https://svn.apache.org/repos/asf/cxf/sandbox/2.2.x-continuations/systests/src/test/java/org/apache/cxf/s
ystest/jaxws/continuations/HelloImplWithContinuation.java
>>
>> check
>>
>> https://svn.apache.org/repos/asf/cxf/sandbox/2.2.x-continuations/systests/src/test/java/org/apache/cxf/systest/jaxws/continuations/jetty-engine.xml
>>
>> on how a jetty engine on a specific port can be told to ignore
>> continuations which are supported by default if true is set or that
>> attribute is omitted (not used in the test though)
>>
>> Ok - you can now see it it so shoot :-) Comments are welcome
>>
>> Sergey
>>
>>
>
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
etty
>> (that's the inbound path). If the existing message is found on the incoming
>> http request's continuatiuon - we resume a paused invocation otherwise we
>> start a new one. As I said - we might throw an exception at this point if we
>> find that the not-new continuation has no message attached to it - logging a
>> warning for now.
>>
>> Either way, eventually this invocation returns. Why should we do anything
>> about the fact at this stage that this invocation was 'resumed' by the timer
>> expiring ?
>>
>> Am I totally slow ?
>>
>> Cheers, Sergey
>>
>
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
t; >>>}
>>>>>>> >>>public void handleResponse(Response
>>>>>>> >>> response) { resp = response.get();
>>>>>>> >>> cont.resume();
>>>>>>> >>>
gt;>>> >>>>
>>>>> >>>> try {
>>>>> >>>> invoke(); // continuation.suspend() somehow by the code being
>>>>> >>>> invoked upon }
>>>>> >>>> catch (RuntimeExcept
XF (by extension via the dOSGi RI) in the wider OSGi
> community
>
> Consider this proposal a +1 from me.
>
> The vote will remain open for at least 72 hours.
>
> Cheers,
> Eoghan
>
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
gt; The JMS transport could just catch it and more or less ignore it.
>>> >>>> > We'd then have to add a "resume()" method to the chain which
>>> >>>> > would
>>> >>>> > call back onto a listener that the transport provides. Jetty
>>> >>>> > would
>>> >>>> > just call the jetty resume stuff. JMS would probably put a
>>> >>>> > runnable
>>> >>>> > on the workqueue to restart the chain.
>>> >>>>
>>> >>>> ok
>>> >>>>
>>> >>>> > Also, suspend() would need to check if there is a listener. If
>>> >>>> > not,
>>> >>>> > it should not throw the exception. Thus, the servlet transport
>>> >>>> > and
>>> >>>> > CORBA stuff that couldn't do this would pretty much just ignore
>>> >>>> > it.
>>> >>>>
>>> >>>> ok, not sure I understand about the listener but I think I see what
>>> >>>> you mean...
>>> >>>>
>>> >>>> > Basically, this needs to be done in such a way that it CAN work
>>> >>>> > for
>>> >>>> > the non-jetty cases. However, it also needs to be done in a way
>>> >>>> > that doesn't affect existing transports.
>>> >>>>
>>> >>>> +1
>>> >>>>
>>> >>>> Cheers, Sergey
>>> >>>>
>>> >>>> > Dan
>>> >>>> >
>>> >>>> >> 2. Now, if the above can be figured out, the next problem arises:
>>> >>>> >> when the "trigger" to wake up the continuation occurs
>>> >>>> >>
>>> >>>> >> I think we can can do in JettyDestination omething similar to
>>> >>>> >> what
>>> >>>> >> is done in SMX. When getting a SuspendedFault exception, we can
>>> >>>> >> extract from it the original continuation instance or else we can
>>> >>>> >> do ContinuationSupport.getContinuation(request) which should
>>> >>>> >> return
>>> >>>> >> us the instance. At this point we can use it as a ket to store
>>> >>>> >> the
>>> >>>> >> current exchange plus all the other info we may need.
>>> >>>> >>
>>> >>>> >> When the user/application code does continuation.resume(), the
>>> >>>> >> Jetty thread will come back and we will use the
>>> >>>> >> ContinuationSupport.getContinuation(request) to get us the active
>>> >>>> >> continuation and use it to extract the suspended exchange and
>>> >>>> >> proceed from there, say we'll call
>>> >>>> >> PhaseInterceptorPhase.resume(),
>>> >>>> >> etc, something along the lines you suggested
>>> >>>> >>
>>> >>>> >>
>>> >>>> >> 3. Basically, to do this "right", we'd need to audit pretty much
>>> >>>> >> everything to make sure nothing is stored on the stack and is
>>> >>>> >> "resumable". Once that is done, the rest is relatively easy.
>>> >>>> >>
>>> >>>> >> Yea - probably can be the quite challenging
>>> >>>> >>
>>> >>>> >>
>>> >>>> >> Thoughts ?
>>> >>>> >>
>>> >>>> >> Cheers, Sergey
>>> >>>> >>
>>> >>>> >>
>>> >>>> >>
>>> >>>> >>
>>> >>>> >> [1] http://docs.codehaus.org/display/JETTY/Continuations
>>> >>>> >> [2] https://issues.apache.org/jira/browse/CXF-1835
>>> >>>> >> [3]
>>> >>>> >>
>>> >>>> >> https://issues.apache.org/jira/browse/CXF-1835?focusedCommentId=126
>>> >>>> >>42361 #ac tion_12642361
>>> >>>> >
>>> >>>> > --
>>> >>>> > Daniel Kulp
>>> >>>> > [EMAIL PROTECTED]
>>> >>>> > http://dankulp.com/blog
>>> >>>
>>> >>> --
>>> >>> Daniel Kulp
>>> >>> [EMAIL PROTECTED]
>>> >>> http://dankulp.com/blog
>>
>>
>>
>> --
>> Daniel Kulp
>> [EMAIL PROTECTED]
>> http://dankulp.com/blog
>
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
retty much everything
>> to make sure nothing is stored on the stack and is "resumable". Once that
>> is done, the rest is relatively easy.
>>
>> Yea - probably can be the quite challenging
>>
>>
>> Thoughts ?
>>
>> Cheers, Sergey
to the central repository.
>
> This release is tagged at:
> http://svn.apache.org/repos/asf/cxf/tags/cxf-2.1.3
>
>
> Here is my +1. The vote will be open here for at least 72 hours.
>
> Willem
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
t; View this message in context:
> http://www.nabble.com/Potential-impact-of-SpringSource-Enterprise-Maintenance-Policy-on-CXF-tp19833297p19872906.html
> Sent from the cxf-dev mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://open.iona.com
art of the ConnectionFactory
set up by the user, so the CXF code should not really take care of it.
On Wed, Sep 3, 2008 at 7:23 PM, Christian Schneider
<[EMAIL PROTECTED]> wrote:
> Guillaume Nodet schrieb:
>>
>> The Spring JMS layer contains two parts: the JmsTemplate which can be
>
he other hand has to be cached as it is costly to
>> > create. I think the connection could be stored as a simple attribute of
>> > JMSConduit or JMSDestination.
>> > As far as I know it is thread safe too.
>> >
>> > What is your knowledge about this?
>> >
>> > Best regards
>> >
>> > Christian
>
>
>
> --
> Daniel Kulp
> [EMAIL PROTECTED]
> http://www.dankulp.com/blog
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
for at least 72 hours.
>
> - ---
> Daniel Kulp
> [EMAIL PROTECTED]
> http://www.dankulp.com/blog
>
>
>
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.4 (Darwin)
>
> iD8DBQFIhos1q8juObtVB0YRAu+GAJ9wlLmUL603COMNIv52xwvB2+XMgACaA8K2
> 0OImzd5F9+EtcKeWx+Rf7i0=
> =kqY9
> -END PGP SIGNATURE-
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
pi.bioinfo.no/stylesheets/WSDLDocumentation.xslt";?>
>> http://schemas.xmlsoap.org/wsdl/";
>>
>>
>> Is it possible that we publish stylesheet as well when we publish the wsdl,
>> I mean if customer get wsdl from http://serviceaddress?wsdl, they can also
&
- ---
> Daniel Kulp
> [EMAIL PROTECTED]
> http://www.dankulp.com/blog
>
>
>
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.4 (Darwin)
>
> iD8DBQFIV83Qq8juObtVB0YRAk9IAJ94zSGaE98mw4z2UOdcCeX8HzAntACfb4Zv
> Px3oDUHzRTC53LDAs2yxIz8=
> =fif0
> -END PGP SIGNATURE-
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
ved to CXF 2.1 yet, so we need this on 2.0.x-fixes
> initially.
>
> -Mike
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
all? Or is this not a concern at all?
> >
> > Bruce
> > --
> > perl -e 'print
> unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E > );'
> >
> > Apache ActiveMQ - http://activemq.org/
> > Apache Camel - http://activemq.org/camel/
> > Apache ServiceMix - http://servicemix.org/
> > Apache Geronimo - http://geronimo.apache.org/
> >
> > Blog: http://bruceblog.org/
> >
>
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
ncubator/cxf/tags/cxf-2.1/
>
>
>
> Here is my +1. The vote will be open here for at least 72 hours.
>
>
>
> --
> J. Daniel Kulp
> Principal Engineer, IONA
> [EMAIL PROTECTED]
> http://www.dankulp.com/blog
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
J. Daniel Kulp
> Principal Engineer, IONA
> [EMAIL PROTECTED]
> http://www.dankulp.com/blog
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
ry. (the REAL
> maven repository, not the incubating one this time!!!)
>
> This release is tagged at:
> http://svn.apache.org/repos/asf/incubator/cxf/tags/cxf-2.1/
>
>
>
> Here is my +1. The vote will be open here for at least 72 hours.
>
>
>
> --
&g
49 matches
Mail list logo
