Hi
On 10/07/12 12:15, Sergey Beryozkin wrote:
Hi,
On Mon, Jul 2, 2012 at 11:13 AM, Sergey Beryozkin
wrote:
As far as CXF is concerned, I'm biased but I also believe getting Tika
server supporting CXF was the right decision. CXF, like JAX-RS, is only
going to become better, with things like the
new module.
Thanks
Jörg
-Original Message-
From: Ray Gauss II [mailto:ray.ga...@alfresco.com]
Sent: Montag, 2. Juli 2012 01:56
To: dev@tika.apache.org
Subject: Re: JAX-RS overhead in tika-server
Is there any consensus on TIKA-930 [1]? I don't want to wipe out properties
that o
Hi,
On Mon, Jul 2, 2012 at 11:13 AM, Sergey Beryozkin wrote:
> As far as CXF is concerned, I'm biased but I also believe getting Tika
> server supporting CXF was the right decision. CXF, like JAX-RS, is only
> going to become better, with things like the good support for attachments,
> advanced s
Hi All,
On 01/07/12 17:27, Mattmann, Chris A (388J) wrote:
Hey Jukka,
On Jul 1, 2012, at 5:09 AM, Jukka Zitting wrote:
Hi,
I looked at tika-server in a bit more detail, and I'm a bit concerned
about the dependency overhead it needs for the JAX-RS support:
+- org.apache.cxf:cxf-rt-frontend-
Hi Ray,
I'd say what you proposed is fine by me. Doesn't seem to have generated
objections so please move forward.
Cheers,
Chris
On Jul 1, 2012, at 4:56 PM, Ray Gauss II wrote:
> Is there any consensus on TIKA-930 [1]? I don't want to wipe out properties
> that others feel are critical or inc
Is there any consensus on TIKA-930 [1]? I don't want to wipe out properties
that others feel are critical or include non-ratified standards if that's
outside of policy.
If there's no objection to what's outlined in that issue I can commit those
changes tomorrow morning (GMT -4).
Regards,
Ray
On Sun, 1 Jul 2012, Mattmann, Chris A (388J) wrote:
It can be a big pain if an in-progress API is suddenly effectively
frozen by the need to be compatible into the future...
Agreed -- so, what do you think? How much longer do we need to wrap up
the API changes or whatever going on with the met
Hey Nick,
On Jul 1, 2012, at 2:52 PM, Nick Burch wrote:
> On Sun, 1 Jul 2012, Mattmann, Chris A (388J) wrote:
>> I also plan to spin a 1.2 release candidate at some point in the next week
>> or so. I realize the metadata stuff isn't done yet, but it's better to
>> simply release early and often
On Sun, 1 Jul 2012, Mattmann, Chris A (388J) wrote:
I also plan to spin a 1.2 release candidate at some point in the next
week or so. I realize the metadata stuff isn't done yet, but it's better
to simply release early and often, and then when stuff is ready it can
be included. Releasing is a l
Hey Jukka,
On Jul 1, 2012, at 12:01 PM, Jukka Zitting wrote:
> Hi,
>
> On Sun, Jul 1, 2012 at 6:27 PM, Mattmann, Chris A (388J)
> wrote:
>> On Jul 1, 2012, at 5:09 AM, Jukka Zitting wrote:
>> Sergey Beryozkin (who I'm CC'ing on this email since I'm not sure
>> he's subscribed to dev@) helped by
Hi,
On Sun, Jul 1, 2012 at 6:27 PM, Mattmann, Chris A (388J)
wrote:
> On Jul 1, 2012, at 5:09 AM, Jukka Zitting wrote:
> Sergey Beryozkin (who I'm CC'ing on this email since I'm not sure
> he's subscribed to dev@) helped by providing guidance on the CXF
> side while I was working on this with Max
Hey Jukka,
On Jul 1, 2012, at 5:09 AM, Jukka Zitting wrote:
> Hi,
>
> I looked at tika-server in a bit more detail, and I'm a bit concerned
> about the dependency overhead it needs for the JAX-RS support:
>
> +- org.apache.cxf:cxf-rt-frontend-jaxrs:jar:2.5.2
> +- org.apache.cxf:cxf-common-
Hi,
I looked at tika-server in a bit more detail, and I'm a bit concerned
about the dependency overhead it needs for the JAX-RS support:
+- org.apache.cxf:cxf-rt-frontend-jaxrs:jar:2.5.2
+- org.apache.cxf:cxf-common-utilities:jar:2.5.2
| +- org.apache.ws.xmlschema:xmlschema-core:jar:
13 matches
Mail list logo
