There were a couple of System.out.println() statements printing nice feeds :-), they've been
removed now.
Note the AtomPushEngine might do System.err.println() occasionally, but I believe it is the
only way AtomPushEngine can log itself, 
at least at the moment. I'm not sure how feasible it is for it to avoid handling its own logging
events...

Sergey

>
> The org.apache.cxf.systest.jaxrs.JAXRSLoggingAtomPushTest is spitting all
> kinds of stuff out to stdout/stderr.   Can that be fixed?
>
>
> -- 
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog 

Hi

> 
> Quick question about the Atom logging stuff...
> 
> Is this intended for 2.2.6 or just for 2.3?     Just wondering if I need to 
> merge it back or not.

I was planning to backmerge the Andy's commits, just haven't had a chance yet. I'll unblock
the relevant revisions if needed

cheers, Sergey
> 
> Thanks!
> 
> -- 
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog

   Dear community,

   It's a great honor for me to be welcomed in the Apache CXF community.
It's a great honor to contribute to a foundation that changed the face of
Open Source and I am specially touched to join a team that provides one of
the most widely used web services technologies.

   I will do my best to deserve your confidence, I must admit that I am very
impressed :-) .

   Cyrille.

On Mon, Dec 7, 2009 at 8:08 PM, Daniel Kulp <dkulp@apache.org> wrote:

>
> With 13 +1 votes and no other votes, this vote passes.
>
> Welcome aboard Cyrille!
>
> Dan
>
>
> On Thu December 3 2009 10:48:29 am Daniel Kulp wrote:
> > 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 answering some questions.    Thus, I think he's a bit
> >  over due to become a committer.
> >
> > Here is my +1.
> >
> > Vote will be open for at least 72 hours.
> >
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>

Quick question about the Atom logging stuff...

Is this intended for 2.2.6 or just for 2.3?     Just wondering if I need to 
merge it back or not.

Thanks!

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

The org.apache.cxf.systest.jaxrs.JAXRSLoggingAtomPushTest is spitting all 
kinds of stuff out to stdout/stderr.   Can that be fixed?


-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

With 13 +1 votes and no other votes, this vote passes.   

Welcome aboard Cyrille!

Dan


On Thu December 3 2009 10:48:29 am Daniel Kulp wrote:
> 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 answering some questions.    Thus, I think he's a bit
>  over due to become a committer.
> 
> Here is my +1.
> 
> Vote will be open for at least 72 hours.
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

Actually, it looks like the stack trace thing is fixed with ActiveMQ 5.3.   
Basically, at shutdown time, ActiveMQ was SOMETIMES throwing some sort of 
exception that spring was catching and calling printStackTrace on.    With 
updating to 5.3, it looks like things are shutting down cleanly and not stack 
trace.   Thus, I've updated the poms for 2.3 and 2.2.6 to grab Spring 2.5.6.

Dan


On Sat December 5 2009 5:52:03 am Alexandros Karypidis wrote:
> Sorry to bring this up again, but apparently "camel-cxf" version 2.1.0
> has started pulling in spring 2.5.6 modules (including spring-jms). A
> lot of people are using Camel + CXF so I was wondering whether:
> 
> 1) They should stick to older Camel versions
> 2) They can use Camel 2.1.0 as long as they override spring dependencies
> in their POMs to use 2.5.5
> 3) The "bug" can be fixed / worked around?
> 
> By the way, regarding (3), can someone provide more information on what
> the issue is? I wouldn't mind having a look at it to investigate.
> 
> Daniel Kulp wrote:
> > On Wed November 4 2009 10:43:38 am Eamonn Dwyer wrote:
> >> Hi
> >> is there a reason we are using version 2.5.5 of spring framework? I
> >> think servicemix and camel have already moved on up to 2.5.6, so would
> >> it be a good idea to upgrade to both stay in synch with them and also to
> >> avail of any bug fixes.
> >
> > Spring 2.5.6 has a "bug" in the JMS stuff that is resulting in stack
> > traces being printed out in several places when running out test suite. 
> > We've more or less stayed on 2.5.5 so that those stack traces aren't
> > confused with real errors.
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

+1

On Dec 7, 2009, at 1:05 AM, Ulhas Bhole wrote:

> +1,
> 
> -- Ulhas Bhole
> 
> Daniel Kulp wrote:
>> 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 answering some questions.    Thus,
I think he's a bit over due to become a committer.
>> 
>> Here is my +1.
>> 
>> Vote will be open for at least 72 hours.
>> 
>>  

> Hope everyone is ok with this.

Go for it!

And welcome to the project, Marc.

Cheers,
Eoghan

+1,

-- Ulhas Bhole

Daniel Kulp wrote:
> 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 answering some questions.    Thus, I think he's a bit over due 
> to become a committer.
>
> Here is my +1.
>
> Vote will be open for at least 72 hours.
>
>   

+1

Christian

Daniel Kulp schrieb:
> 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 answering some questions.    Thus, I think he's a bit over due 
> to become a committer.
>
> Here is my +1.
>
> Vote will be open for at least 72 hours.
>
>   


-- 

Christian Schneider
---
http://www.liquid-reality.de

Sorry to bring this up again, but apparently "camel-cxf" version 2.1.0 
has started pulling in spring 2.5.6 modules (including spring-jms). A 
lot of people are using Camel + CXF so I was wondering whether:

1) They should stick to older Camel versions
2) They can use Camel 2.1.0 as long as they override spring dependencies 
in their POMs to use 2.5.5
3) The "bug" can be fixed / worked around?

By the way, regarding (3), can someone provide more information on what 
the issue is? I wouldn't mind having a look at it to investigate.

Daniel Kulp wrote:
> On Wed November 4 2009 10:43:38 am Eamonn Dwyer wrote:
>   
>> Hi
>> is there a reason we are using version 2.5.5 of spring framework? I think
>>  servicemix and camel have already moved on up to 2.5.6, so would it be a
>>  good idea to upgrade to both stay in synch with them and also to avail of
>>  any bug fixes.
>>     
>
> Spring 2.5.6 has a "bug" in the JMS stuff that is resulting in stack traces 
> being printed out in several places when running out test suite.  We've more 
> or less stayed on 2.5.5 so that those stack traces aren't confused with real 
> errors.
>
>   

Thanks for the test case.  Helped a lot.   The problem is due to the partial 
responses on one-way operations.   In that case, the list IS null so the null 
check is appropriate.  

Fix is committed.   Thanks a bunch for the test case.

Dan


On Fri December 4 2009 5:19:35 am Alexandros Karypidis wrote:
> Hi,
> 
> I have created a test case that expsoses what I think is a bug, attached
> to issue:
> https://issues.apache.org/jira/browse/CXF-2572
> 
> BTW, this is in continuation of this thread from the user list:
> http://thread.gmane.org/gmane.comp.apache.cxf.user/4153
> 
> I am trying to figure out what is going on, but it has something to do
> with processing at the provider (server) side. The client proxy seems to
> do things correctly and sends out proper WS-Addressing headers in the
> request. Any pointers would be appreciated (especially if it would be
> easy to fix for a newcomer).
> 
> Thanks,
> Alex
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

Glen, 

At this point, you cannot turn off the WS-SecPol stuff, but you CAN turn off 
the entire Policy engine.  See:

http://cxf.apache.org/docs/wspconfiguration.html


  <p:engine enabled="false" />

Dan


On Sun November 22 2009 5:49:37 pm Glen Mazza wrote:
> Hello, on this page:
> http://cwiki.apache.org/confluence/display/CXF20DOC/WS-SecurityPolicy, it
> says:
> 
> "In CXF 2.2, if the cxf-rt-ws-policy and cxf-rt-ws-security modules are
> available on the classpath, the WS-SecurityPolicy stuff is automatically
> enabled. Since the entire security runtime is policy driven, the only
> requirement is that the policy engine and security policies be available.
> 
> If you are using the full "bundle" jar, all the security and policy stuff
>  is already included."
> 
> But can we explicitly *disable* WS-SecurityPolicy via configuration if we
> already have included those two modules?  Perhaps we should update our docs
> with this info.
> 
> Glen
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

This is really a Spring JMS thing, I think.   We just call the 
setReconnectOnException method on the Spring SingleConnectionFactory.   

You can probably ask at:
http://forum.springsource.org/forumdisplay.php?f=30

Dan




On Thu December 3 2009 9:06:09 pm Erich Hochmuth wrote:
> Not sure if this is the correct forum or the correct format.
> 
> In CXF 2.2.4 with a JMS bases service we are getting the following
> exception when the web application starts up in WebLogic 10.3.
> 
> This only seems to happen when we set the "reconnectOnException"
> property of the JMSConfiguration to true:
> http://cwiki.apache.org/CXF20DOC/using-the-jmsconfigfeature.html
> 
> Please let me know what additional information I can provide or any
> ideas on what I can do to fix this issue or if it is a configuration
> error on my side.
> 
> Caused by: org.springframework.jms.UncategorizedJmsException: Uncategorized
> exception occured during JMS processing; nested exception is
> javax.jms.JMSException: [JMSPool:169801]The JMS method setExceptionListener
> may not be called inside an EJB or servlet
>       at
> org.springframework.jms.support.JmsUtils.convertJmsAccessException(JmsUtils
> .java:308) at
> org.springframework.jms.support.JmsAccessor.convertJmsAccessException(JmsAc
> cessor.java:168) at
> org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:474)
>       at
> org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:436)
>       at
> org.apache.cxf.transport.jms.JMSFactory.resolveOrCreateDestination(JMSFacto
> ry.java:260) at
> org.apache.cxf.transport.jms.JMSFactory.createJmsListener(JMSFactory.java:2
> 40) at
> org.apache.cxf.transport.jms.JMSFactory.createJmsListener(JMSFactory.java:1
> 46) at
> org.apache.cxf.transport.jms.JMSDestination.activate(JMSDestination.java:11
> 1) at
> org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObse
> rvable.java:48) at
> org.apache.cxf.binding.AbstractBindingFactory.addListener(AbstractBindingFa
> ctory.java:164) at
> org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBindingFacto
> ry.java:766) at
>  org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:122) at
>  org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:271) ... 61
>  more
> Caused by: javax.jms.JMSException: [JMSPool:169801]The JMS method
> setExceptionListener may not be called inside an EJB or servlet
>       at
> weblogic.deployment.jms.JMSExceptions.getJMSException(JMSExceptions.java:22
> ) at
> weblogic.deployment.jms.PooledConnection.setExceptionListener(PooledConnect
> ion.java:180) at
> org.springframework.jms.connection.SingleConnectionFactory.prepareConnectio
> n(SingleConnectionFactory.java:365) at
> org.springframework.jms.connection.SingleConnectionFactory.initConnection(S
> ingleConnectionFactory.java:291) at
> org.springframework.jms.connection.SingleConnectionFactory.createConnection
> (SingleConnectionFactory.java:227) at
> org.springframework.jms.support.JmsAccessor.createConnection(JmsAccessor.ja
> va:184) at
> org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:461)
>       ... 71 more
> 
> 
> 
> Thanks,
> 
> Erich
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

Hi all,

As you've seen, the CXF-DOSGi 1.1 release is out [1]. Thanks Eoghan!
1.1 is compliant with the current OSGi 4.2 Remote Services spec [2].

In the mean time, in the OSGi Alliance an additional 'Distributed
OSGi' specification is nearing completion: Remote Service Admin [3].
This spec defines a number of APIs used internally in Distributed OSGi
implementations. The APIs define the interaction between the
Distribution Provider, Discovery System and a component called the
Topology Manager. The benefit of implementing this standard is that
you can mix & match components from various implementations together.
For instance if someone provided a compliant Discovery implementation
based on UDDI, you could just replace the ZooKeeper-based one in CXF
with that UDDI one. It would just be a matter of replacing the
bundles.

CXF-DOSGi is the Reference Implementation of chapter 13, and will also
be the reference implementation of chapter 122.

Marc Schaaf has been working on refactoring the CXF-DOSGi
implementation to also be compliant with Remote Service Admin while
maintaining backward compatibility. Marc and I are planning to
contribute this work to CXF-DOSGi trunk over the coming weeks.

This might destabilize http://svn.apache.org/repos/asf/cxf/dosgi/trunk
for a little while, which is one of the reasons why we waited until
after the 1.1 release.

Hope everyone is ok with this.

Best regards,

David

[1] http://cxf.apache.org/dosgi-releases.html
[2] Chapter 13 in the 4.2 Compendium http://www.osgi.org/Download/Release4V42
[3] Chapter 122 in
http://www.osgi.org/download/osgi-4.2-enterprise-early-draft4.pdf

Hi,

I have created a test case that expsoses what I think is a bug, attached 
to issue:
https://issues.apache.org/jira/browse/CXF-2572

BTW, this is in continuation of this thread from the user list:
http://thread.gmane.org/gmane.comp.apache.cxf.user/4153

I am trying to figure out what is going on, but it has something to do 
with processing at the provider (server) side. The client proxy seems to 
do things correctly and sends out proper WS-Addressing headers in the 
request. Any pointers would be appreciated (especially if it would be 
easy to fix for a newcomer).

Thanks,
Alex

+1

Daniel Kulp wrote:
> 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 answering some questions.    Thus, I think he's a bit over due 
> to become a committer.
>
> Here is my +1.
>
> Vote will be open for at least 72 hours.
>
>   


-- 
Alessio Soldano
Web Service Lead, JBoss

+1

Cheers,
Eoghan

2009/12/3 Daniel Kulp <dkulp@apache.org>

>
>
> 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 answering some questions.    Thus, I think he's a bit over
> due
> to become a committer.
>
> Here is my +1.
>
> Vote will be open for at least 72 hours.
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>

Not sure if this is the correct forum or the correct format. 

In CXF 2.2.4 with a JMS bases service we are getting the following 
exception when the web application starts up in WebLogic 10.3. 

This only seems to happen when we set the "reconnectOnException" 
property of the JMSConfiguration to true: 
http://cwiki.apache.org/CXF20DOC/using-the-jmsconfigfeature.html  

Please let me know what additional information I can provide or any 
ideas on what I can do to fix this issue or if it is a configuration 
error on my side. 

Caused by: org.springframework.jms.UncategorizedJmsException: Uncategorized
exception occured during JMS processing; nested exception is
javax.jms.JMSException: [JMSPool:169801]The JMS method setExceptionListener
may not be called inside an EJB or servlet
      at
org.springframework.jms.support.JmsUtils.convertJmsAccessException(JmsUtils.java:308)
      at
org.springframework.jms.support.JmsAccessor.convertJmsAccessException(JmsAccessor.java:168)
      at
org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:474)
      at
org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:436)
      at
org.apache.cxf.transport.jms.JMSFactory.resolveOrCreateDestination(JMSFactory.java:260)
      at
org.apache.cxf.transport.jms.JMSFactory.createJmsListener(JMSFactory.java:240)
      at
org.apache.cxf.transport.jms.JMSFactory.createJmsListener(JMSFactory.java:146)
      at
org.apache.cxf.transport.jms.JMSDestination.activate(JMSDestination.java:111)
      at
org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObservable.java:48)
      at
org.apache.cxf.binding.AbstractBindingFactory.addListener(AbstractBindingFactory.java:164)
      at
org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBindingFactory.java:766)
      at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:122)
      at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:271)
      ... 61 more
Caused by: javax.jms.JMSException: [JMSPool:169801]The JMS method
setExceptionListener may not be called inside an EJB or servlet
      at
weblogic.deployment.jms.JMSExceptions.getJMSException(JMSExceptions.java:22)
      at
weblogic.deployment.jms.PooledConnection.setExceptionListener(PooledConnection.java:180)
      at
org.springframework.jms.connection.SingleConnectionFactory.prepareConnection(SingleConnectionFactory.java:365)
      at
org.springframework.jms.connection.SingleConnectionFactory.initConnection(SingleConnectionFactory.java:291)
      at
org.springframework.jms.connection.SingleConnectionFactory.createConnection(SingleConnectionFactory.java:227)
      at
org.springframework.jms.support.JmsAccessor.createConnection(JmsAccessor.java:184)
      at
org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:461)
      ... 71 more

  

Thanks, 

Erich 
-- 
View this message in context: http://old.nabble.com/JMS-reconnectOnException-tp26635744p26635744.html
Sent from the cxf-dev mailing list archive at Nabble.com.

+1

Willem

Daniel Kulp wrote:
> 
> 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 answering some questions.    Thus, I think he's a bit over due 
> to become a committer.
> 
> Here is my +1.
> 
> Vote will be open for at least 72 hours.
> 

+1

-----Original Message-----
From: Daniel Kulp [mailto:dkulp@apache.org] 
Sent: 03 December 2009 15:48
To: dev@cxf.apache.org
Subject: [VOTE] Cyrille Le Clerc for committer....



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 answering some questions.    Thus, I think he's a bit over
due 
to become a committer.

Here is my +1.

Vote will be open for at least 72 hours.

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

+1

thanks, Sergey

----- Original Message ----- 
From: "Daniel Kulp" <dkulp@apache.org>
To: <dev@cxf.apache.org>
Sent: Thursday, December 03, 2009 3:48 PM
Subject: [VOTE] Cyrille Le Clerc for committer....


> 
> 
> 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 answering some questions.    Thus, I think he's a bit over due 
> to become a committer.
> 
> Here is my +1.
> 
> Vote will be open for at least 72 hours.
> 
> -- 
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog

+1

Freeman
On 2009-12-3, at 下午11:48, Daniel Kulp wrote:

>
>
> 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 answering some questions.    Thus, I think he's a bit  
> over due
> to become a committer.
>
> Here is my +1.
>
> Vote will be open for at least 72 hours.
>
> -- 
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog


-- 
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com

+1

David

2009/12/3 Daniel Kulp <dkulp@apache.org>:
>
>
> 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 answering some questions. � �Thus, I think he's a bit over due
> to become a committer.
>
> Here is my +1.
>
> Vote will be open for at least 72 hours.
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>

+1

Thanks,
Bharath

On 03-Dec-2009, at 9:18 PM, Daniel Kulp <dkulp@apache.org> wrote:

>
>
> 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 answering some questions.    Thus, I think he's a bit  
> over due
> to become a committer.
>
> Here is my +1.
>
> Vote will be open for at least 72 hours.
>
> -- 
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog

  +1



On Thu, Dec 3, 2009 at 10:48 AM, Daniel Kulp <dkulp@apache.org> wrote:
>
>
> 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 answering some questions.    Thus, I think he's a bit over due
> to become a committer.
>
> Here is my +1.
>
> Vote will be open for at least 72 hours.
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>

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 answering some questions.    Thus, I think he's a bit over due 
to become a committer.

Here is my +1.

Vote will be open for at least 72 hours.

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

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 to
the cxf/dosgi/dist directory.

Cheers,
Eoghan

+1,

-- Ulhas Bhole

Eoghan Glynn wrote:
> 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 issues fixed in
> this release:
>
>
> http://svn.apache.org/repos/asf/cxf/dosgi/trunk/distribution/multi-bundle/src/main/release/release_notes.txt
>
> The staging area is at:
>
>   https://repository.apache.org/content/repositories/orgapachecxf-021
>
> The various distributions can be downloaded as follows:
>
>    -   *Source:*
>    https://repository.apache.org/content/repositories/orgapachecxf-021/org/apache/cxf/dosgi/cxf-dosgi-ri-source-distribution/1.1
>    -   *Multi-bundle:*
>    https://repository.apache.org/content/repositories/orgapachecxf-021/org/apache/cxf/dosgi/cxf-dosgi-ri-multibundle-distribution/1.1
>    -   *Single-bundle:*
>    https://repository.apache.org/content/repositories/orgapachecxf-021/org/apache/cxf/dosgi/cxf-dosgi-ri-singlebundle-distribution/1.1
>
> This release is tagged with cxf-dosgi-ri-1.1 at:
>
>   http://svn.apache.org/repos/asf/cxf/dosgi/tags/cxf-dosgi-ri-1.1
>
> The vote will remain open for at least 72 hours.
>
> Please consider this call to vote as my +1.
>
> Cheers,
> Eoghan
>
> [1] http://www.osgi.org/Download/Release4V42
>
>   

+1 also (if it hasn't been decided yet.)

Glen


bimargulies wrote:
> 
> I'm +1 for turning off 2.1 support.
> 
> On Mon, Nov 16, 2009 at 10:05 AM, Daniel Kulp <dkulp@apache.org> wrote:
> 
>>
>> Question for everyone.....
>>
>> What are peoples thoughts about making 2.1.9 (in January) the last of the
>> 2.1.x line?
>>
>> 2.2.x will have been out for 10 months by then so users definitely should
>> have
>> had plenty of time to migrate.   2.2.x is generally a simple migration
>> from
>> 2.1.x.   I think most of the other major open source projects that were
>> tracking 2.1.x have already moved onto 2.2.x.   ServiceMix, Camel, JBoss,
>> etc...     The remaining projects that are using 2.1.x seem to be stuck
>> on
>> a
>> particular version (like Mule stuck on 2.1.3) and not "tracking" the
>> fixes
>> anyway.
>>
>> The main migration issue from 2.1.x to 2.2.x is the JAX-RS version (0.8
>> ->
>> 1.0).   However, we aren't fixing any of the JAX-RS issues on 2.1.x
>> anyway.
>> Thus, that's not a real reason.  If you are using JAX-RS, you definitely
>> want
>> the compliant implementation in 2.2.
>>
>> Anyway, making 2.1.9 the end of the line should then make it such that
>> when
>> 2.3 is ready (hopefully in Q1), we can just keep 2 fixes branches active.
>>
>> Thoughts?  Comments?
>>
>> --
>> Daniel Kulp
>> dkulp@apache.org
>> http://www.dankulp.com/blog
>>
> 
> 

-- 
View this message in context: http://old.nabble.com/Thoughts-about-dropping-support-for-2.1.x......-tp26373514p26545380.html
Sent from the cxf-dev mailing list archive at Nabble.com.

+1

-----Original Message-----
From: Eoghan Glynn [mailto:eoglynn@gmail.com] 
Sent: 25 November 2009 17:32
To: dev@cxf.apache.org
Subject: [VOTE] Release CXF dOSGi 1.1

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 issues fixed
in
this release:


http://svn.apache.org/repos/asf/cxf/dosgi/trunk/distribution/multi-bundl
e/src/main/release/release_notes.txt

The staging area is at:

  https://repository.apache.org/content/repositories/orgapachecxf-021

The various distributions can be downloaded as follows:

   -   *Source:*
 
https://repository.apache.org/content/repositories/orgapachecxf-021/org/
apache/cxf/dosgi/cxf-dosgi-ri-source-distribution/1.1
   -   *Multi-bundle:*
 
https://repository.apache.org/content/repositories/orgapachecxf-021/org/
apache/cxf/dosgi/cxf-dosgi-ri-multibundle-distribution/1.1
   -   *Single-bundle:*
 
https://repository.apache.org/content/repositories/orgapachecxf-021/org/
apache/cxf/dosgi/cxf-dosgi-ri-singlebundle-distribution/1.1

This release is tagged with cxf-dosgi-ri-1.1 at:

  http://svn.apache.org/repos/asf/cxf/dosgi/tags/cxf-dosgi-ri-1.1

The vote will remain open for at least 72 hours.

Please consider this call to vote as my +1.

Cheers,
Eoghan

[1] http://www.osgi.org/Download/Release4V42

Big +1 from me!

David

2009/11/25 Eoghan Glynn <eoglynn@gmail.com>:
> 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 issues fixed in
> this release:
>
>
> http://svn.apache.org/repos/asf/cxf/dosgi/trunk/distribution/multi-bundle/src/main/release/release_notes.txt
>
> The staging area is at:
>
> �https://repository.apache.org/content/repositories/orgapachecxf-021
>
> The various distributions can be downloaded as follows:
>
> � - � *Source:*
> � https://repository.apache.org/content/repositories/orgapachecxf-021/org/apache/cxf/dosgi/cxf-dosgi-ri-source-distribution/1.1
> � - � *Multi-bundle:*
> � https://repository.apache.org/content/repositories/orgapachecxf-021/org/apache/cxf/dosgi/cxf-dosgi-ri-multibundle-distribution/1.1
> � - � *Single-bundle:*
> � https://repository.apache.org/content/repositories/orgapachecxf-021/org/apache/cxf/dosgi/cxf-dosgi-ri-singlebundle-distribution/1.1
>
> This release is tagged with cxf-dosgi-ri-1.1 at:
>
> �http://svn.apache.org/repos/asf/cxf/dosgi/tags/cxf-dosgi-ri-1.1
>
> The vote will remain open for at least 72 hours.
>
> Please consider this call to vote as my +1.
>
> Cheers,
> Eoghan
>
> [1] http://www.osgi.org/Download/Release4V42
>

+1 !

On Nov 25, 2009 12:36 PM, "Sergey Beryozkin" <sberyozk@progress.com> wrote:

+1

thanks, Sergey

----- Original Message ----- From: "Eoghan Glynn" <eoglynn@gmail.com>
To: <dev@cxf.apache.org>
Sent: Wednesday, November 25, 2009 5:31 PM
Subject: [VOTE] Release CXF dOSGi 1.1

> Folks, > > I'm calling a vote to release CXF Distributed OSGi 1.1. > > The
dOSGi subproject of ...

+1

thanks, Sergey

----- Original Message ----- 
From: "Eoghan Glynn" <eoglynn@gmail.com>
To: <dev@cxf.apache.org>
Sent: Wednesday, November 25, 2009 5:31 PM
Subject: [VOTE] Release CXF dOSGi 1.1


> 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 issues fixed in
> this release:
>
>
> http://svn.apache.org/repos/asf/cxf/dosgi/trunk/distribution/multi-bundle/src/main/release/release_notes.txt
>
> The staging area is at:
>
>  https://repository.apache.org/content/repositories/orgapachecxf-021
>
> The various distributions can be downloaded as follows:
>
>   -   *Source:*
>   https://repository.apache.org/content/repositories/orgapachecxf-021/org/apache/cxf/dosgi/cxf-dosgi-ri-source-distribution/1.1
>   -   *Multi-bundle:*
> 
> https://repository.apache.org/content/repositories/orgapachecxf-021/org/apache/cxf/dosgi/cxf-dosgi-ri-multibundle-distribution/1.1
>   -   *Single-bundle:*
> 
> https://repository.apache.org/content/repositories/orgapachecxf-021/org/apache/cxf/dosgi/cxf-dosgi-ri-singlebundle-distribution/1.1
>
> This release is tagged with cxf-dosgi-ri-1.1 at:
>
>  http://svn.apache.org/repos/asf/cxf/dosgi/tags/cxf-dosgi-ri-1.1
>
> The vote will remain open for at least 72 hours.
>
> Please consider this call to vote as my +1.
>
> Cheers,
> Eoghan
>
> [1] http://www.osgi.org/Download/Release4V42
> 

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 issues fixed in
this release:


http://svn.apache.org/repos/asf/cxf/dosgi/trunk/distribution/multi-bundle/src/main/release/release_notes.txt

The staging area is at:

  https://repository.apache.org/content/repositories/orgapachecxf-021

The various distributions can be downloaded as follows:

   -   *Source:*
   https://repository.apache.org/content/repositories/orgapachecxf-021/org/apache/cxf/dosgi/cxf-dosgi-ri-source-distribution/1.1
   -   *Multi-bundle:*
   https://repository.apache.org/content/repositories/orgapachecxf-021/org/apache/cxf/dosgi/cxf-dosgi-ri-multibundle-distribution/1.1
   -   *Single-bundle:*
   https://repository.apache.org/content/repositories/orgapachecxf-021/org/apache/cxf/dosgi/cxf-dosgi-ri-singlebundle-distribution/1.1

This release is tagged with cxf-dosgi-ri-1.1 at:

  http://svn.apache.org/repos/asf/cxf/dosgi/tags/cxf-dosgi-ri-1.1

The vote will remain open for at least 72 hours.

Please consider this call to vote as my +1.

Cheers,
Eoghan

[1] http://www.osgi.org/Download/Release4V42

Hi all,

should be up again..

Bye,
Norman

2009/11/23 Tim Ellison <t.p.ellison@gmail.com>:
> On 23/Nov/2009 14:00, David Bosschaert wrote:
>> I normally look at http://hudson.zones.apache.org/hudson/view/CXF/ to
>> see the status of CXF builds but the whole
>> http://hudson.zones.apache.org/hudson site seems to be down.
>> Could someone please take a look?
>
> David,
>
> The whole machine is down, see [1] for "hyperion.apache.org".
>
> When it is back up Hudson will be restarted. �News about expected outage
> time etc. will be posted on that same page in the "Scheduled Host
> Downtime" panel.
>
> [1] http://monitoring.apache.org/status/
>
> Regards,
> Tim
>

Hi Glen
 
The Jira already contains the sample. The idea of this jira is to review it and include it
within the cxf distribution under samles/ws-security.
 
Thanks
 

________________________________

Von: Glen Mazza [mailto:glen.mazza@gmail.com]
Gesendet: Mo 23.11.2009 15:50
An: dev@cxf.apache.org
Betreff: Re: WS-SecurityPolicy based sample for UsernameToken




Here you go:  http://www.jroller.com/gmazza/entry/cxf_usernametoken_profile


Oliver Wulff-2 wrote:
>
> Hi there
> 
> I've raised a jira (CXF-2553) to add a WS-SecurityPolicy based sample for
> UsernameToken.
> 
> Can anybody have a look into this?
> 
> Thanks
> Oli
>

--
View this message in context: http://old.nabble.com/WS-SecurityPolicy-based-sample-for-UsernameToken-tp26473919p26479408.html
Sent from the cxf-dev mailing list archive at Nabble.com.

Here you go:  http://www.jroller.com/gmazza/entry/cxf_usernametoken_profile


Oliver Wulff-2 wrote:
> 
> Hi there
>  
> I've raised a jira (CXF-2553) to add a WS-SecurityPolicy based sample for
> UsernameToken.
>  
> Can anybody have a look into this?
>  
> Thanks
> Oli
> 

-- 
View this message in context: http://old.nabble.com/WS-SecurityPolicy-based-sample-for-UsernameToken-tp26473919p26479408.html
Sent from the cxf-dev mailing list archive at Nabble.com.

On 23/Nov/2009 14:00, David Bosschaert wrote:
> I normally look at http://hudson.zones.apache.org/hudson/view/CXF/ to
> see the status of CXF builds but the whole
> http://hudson.zones.apache.org/hudson site seems to be down.
> Could someone please take a look?

David,

The whole machine is down, see [1] for "hyperion.apache.org".

When it is back up Hudson will be restarted.  News about expected outage
time etc. will be posted on that same page in the "Scheduled Host
Downtime" panel.

[1] http://monitoring.apache.org/status/

Regards,
Tim