Weave Code
Apache Tika Bundle Laravel Package
jolicode/apache-tika-bundle
Symfony bundle that integrates Apache Tika to extract text and metadata from PDFs, Office documents, and other files. Provides simple services and configuration for document content extraction in PHP applications.
:file_folder: Symfony Bundle for https://github.com/vaites/php-apache-tika
Frequently asked questions about Apache Tika Bundle
- Does jolicode/apache-tika-bundle work with Laravel?
- No. It is a Symfony bundle, and Laravel never loads Bundle classes, runs Extension::load(), or compiles third-party ContainerBuilder service definitions. The entire value proposition — the apache_tika config tree, autowired TikaClient service, and compiler passes — is inert under Laravel. Version 1.1.0 only relaxes a Composer constraint; it adds no service provider, facade, or package discovery, so the bundle is structurally unusable in a Laravel app.
- Can I install jolicode/apache-tika-bundle in a Laravel 10 or 11 project?
- Possibly, since v1.1.0. The release note claims compatibility with Symfony >= 4.0, which may co-resolve with Laravel 10/11's Symfony 6/7 components instead of hard-failing the resolver. That must be verified by running the actual Composer resolver, not inferred from a changelog. Even if it installs, it still cannot be used, because nothing in Laravel loads the bundle.
- What part of this package actually works inside a Laravel application?
- Only the underlying library, vaites/php-apache-tika, which is a plain PHP HTTP client for a Tika Server and has no Symfony coupling. You can call it directly from a Laravel service class, job, or command. Treat the bundle as a wrapper you bypass rather than a dependency you adopt.
- Do I need Java and a running Tika Server to extract text from PDFs with this package?
- Yes. Apache Tika Server is a JVM service, so you need a running Java process reachable over HTTP plus the PHP client that talks to it. That is an operational cost many PHP shops are not staffed for, and it applies to any PHP client you choose. It is entirely independent of the Symfony bundle question.
- Is jolicode/apache-tika-bundle still maintained?
- Marginally. The repo sat silent for years after its 2019 release, and v1.1.0 is a merged community contribution credited to @Baachi — a heartbeat showing the maintainer is reachable, not a maintenance cadence or roadmap. Bus factor is 1 and it is run as an internal-utility-grade project. If it breaks under your use case, you fork it or you own it.
- How do I configure the Tika server endpoint in Laravel with this bundle?
- You can't through the bundle. Configuration is a Symfony apache_tika config tree loaded by the bundle's Extension class, which Laravel never executes. In Laravel you configure the endpoint yourself, for example in config/services.php, and construct the Tika client manually or bind it in a service provider.
- Is document extraction with this package safe for user-uploaded files?
- Treat it with care. Document extraction means a parser is processing untrusted input, and Apache Tika has a real CVE history. The v1.1.0 constraint-widening release says nothing about which Tika Server version the client targets, so you can still end up stranded on an unpatched parser. Run Tika Server sandboxed and keep it updated independently.
- Are there real production projects using jolicode/apache-tika-bundle?
- Public evidence shows zero dependents. No known production project has taken a dependency, so there is no downstream bug surface, no integration reports, and no proof it functions in a real deployment — let alone under Laravel. That remains the sharpest risk indicator, and v1.1.0 does not change it.
- What should I use instead in Laravel to extract text from PDFs and Office documents?
- There is no Laravel-specific wrapper from this maintainer. The practical route is calling vaites/php-apache-tika from a queued job or dedicated service, paired with a self-hosted or containerized Tika Server you control. If you want to avoid a Java runtime entirely, evaluate pure-PHP or managed extraction services per file format.
- Does this package support Laravel package auto-discovery or ship a service provider?
- No. There is no Laravel service provider, facade, config publish path, or extra.laravel auto-discovery block, and v1.1.0 does not add any of that. Without an upstream rewrite that explicitly targets Laravel, the bundle remains structurally unusable regardless of which Symfony or PHP constraints it allows.
Weaver
How can I help you explore Laravel packages today?