You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by dsjaxen <do...@siemens.com> on 2015/06/02 18:08:42 UTC

No SessionManager

Hi!
We have the following in our blueprint:
    <httpj:engine-factory bus="cxf">
     <httpj:engine port="$[rest.port]">
            <httpj:sessionSupport>true</httpj:sessionSupport>
        </httpj:engine>
     <httpj:engine port="$[websvc.port]">
            <httpj:sessionSupport>true</httpj:sessionSupport>
        </httpj:engine>
    </httpj:engine-factory>

    <jaxrs:server id=&quot;rest&quot;
                  address=&quot;&lt;a
href=&quot;http://0.0.0.0:$&quot;>http://0.0.0.0:$[rest.port]/xxx">


However, the HTTP Session manager is not started.  This became a problem
when switching to
karaf 3.0.3/cxf 3.0.2/camel 2.14.1.  This is still the documented way to set
up the jetty endpoints on the cxf page.  Is there a better way to set these
up?

Is anyone familiar with a way to get this to work?

Thanks in advance,
Doug 



--
View this message in context: http://cxf.547215.n5.nabble.com/No-SessionManager-tp5757890.html
Sent from the cxf-user mailing list archive at Nabble.com.

Re: No SessionManager

Posted by Sergey Beryozkin <sb...@gmail.com>.
FYI:
https://issues.apache.org/jira/browse/CXF-6481

Cheers, Sergey
On 03/06/15 10:20, Sergey Beryozkin wrote:
> Hi
>
> I've never used this mechanism myself, can you please let us know with
> which versions of Karaf/CXF/Camel it did work and may be it will be
> possible to trace the relevant changes that have affected it.
>
> Perhaps another way is to control it with the pax web properties ?
>
> It is also quite easy to control it directly with JAX-RS API but the
> downside is that the application code has to be updated accordingly.
>
> Cheers, Sergey
>
> On 02/06/15 17:08, dsjaxen wrote:
>> Hi!
>> We have the following in our blueprint:
>>      <httpj:engine-factory bus="cxf">
>>       <httpj:engine port="$[rest.port]">
>>              <httpj:sessionSupport>true</httpj:sessionSupport>
>>          </httpj:engine>
>>       <httpj:engine port="$[websvc.port]">
>>              <httpj:sessionSupport>true</httpj:sessionSupport>
>>          </httpj:engine>
>>      </httpj:engine-factory>
>>
>>      <jaxrs:server id=&quot;rest&quot;
>>                    address=&quot;&lt;a
>> href=&quot;http://0.0.0.0:$&quot;>http://0.0.0.0:$[rest.port]/xxx">
>>
>>
>> However, the HTTP Session manager is not started.  This became a problem
>> when switching to
>> karaf 3.0.3/cxf 3.0.2/camel 2.14.1.  This is still the documented way
>> to set
>> up the jetty endpoints on the cxf page.  Is there a better way to set
>> these
>> up?
>>
>> Is anyone familiar with a way to get this to work?
>>
>> Thanks in advance,
>> Doug
>>
>>
>>
>> --
>> View this message in context:
>> http://cxf.547215.n5.nabble.com/No-SessionManager-tp5757890.html
>> Sent from the cxf-user mailing list archive at Nabble.com.
>>
>

Re: No SessionManager

Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi

I've never used this mechanism myself, can you please let us know with 
which versions of Karaf/CXF/Camel it did work and may be it will be 
possible to trace the relevant changes that have affected it.

Perhaps another way is to control it with the pax web properties ?

It is also quite easy to control it directly with JAX-RS API but the 
downside is that the application code has to be updated accordingly.

Cheers, Sergey

On 02/06/15 17:08, dsjaxen wrote:
> Hi!
> We have the following in our blueprint:
>      <httpj:engine-factory bus="cxf">
>       <httpj:engine port="$[rest.port]">
>              <httpj:sessionSupport>true</httpj:sessionSupport>
>          </httpj:engine>
>       <httpj:engine port="$[websvc.port]">
>              <httpj:sessionSupport>true</httpj:sessionSupport>
>          </httpj:engine>
>      </httpj:engine-factory>
>
>      <jaxrs:server id=&quot;rest&quot;
>                    address=&quot;&lt;a
> href=&quot;http://0.0.0.0:$&quot;>http://0.0.0.0:$[rest.port]/xxx">
>
>
> However, the HTTP Session manager is not started.  This became a problem
> when switching to
> karaf 3.0.3/cxf 3.0.2/camel 2.14.1.  This is still the documented way to set
> up the jetty endpoints on the cxf page.  Is there a better way to set these
> up?
>
> Is anyone familiar with a way to get this to work?
>
> Thanks in advance,
> Doug
>
>
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/No-SessionManager-tp5757890.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>