⚡ Modernization of Leaflet After two and a half years of hard work, we’re thrilled to announce the first alpha release of Leaflet 2.0! This release marks a major modernization of the Leaflet codeba...

Este certificado comprova a utilização de energia renovável nas operações portuárias durante o ano de 2024

O objetivo do exercício foi preparar a equipe da companhia para agir de forma rápida e eficiente em momentos de pressão

⚡ Modernization of Leaflet After two and a half years of hard work, we’re thrilled to announce the first alpha release of Leaflet 2.0! This release marks a major modernization of the Leaflet codeba...

A Autoridade Portuária da Bahia (Codeba) registrou um aumento significativo na movimentação de cargas em seus portos no acumulado do ano, até junho de 2024, comparado ao mesmo período do ano anterior.  Os Portos de Salvador, Aratu-Candeias e Ilhéus…

Our research on Void Dokkaebi’s operations uncovered a campaign that turns infected developer repositories into malware delivery channels. By spreading through trusted workflows, organizational codeba...

Features & Enhancements Progress Bar: Implemented a new progress bar to track loading states. Transitions: Removed the black fade transition between map changes for more direct scene switching. Codeba...

Our research on Void Dokkaebi’s operations uncovered a campaign that turns infected developer repositories into malware delivery channels. By spreading through trusted workflows, organizational codeba...

Imóvel fica na Rua Estados Unidos, próximo à Codeba. Fogo foi apagado pelo Corpo de Bombeiros na manhã deste domingo (15).

Nesta segunda-feira (15), a Defensoria Regional de Direitos Humanos (DRDH) na Bahia acompanhará visita técnica à comunidade quilombola Boca do Rio, na região do Porto de Aratu, em Candeias. O local é alvo de disputa entre quilombolas e a Companhia Docas…

Yeah lol I love Frontiers but it doesn't surprise me to know it's coded so messy

O ministro da Casa Civil, Rui Costa, falou sobre o futuro das concessões das rodovias BR-324 e da BR-116 e o começo da requalificação das rodovias, previsto para o inicio do próximo ano, em encontro no Terminal da Codeba.

Exercício INTERPOTEX LE-I/2026 reuniu cerca de 120 militares em treinamento voltado à defesa de instalações portuárias

A ação foi coordenada pela Autoridade Portuária, em parceria com o Órgão Gestor de Mão de Obra – OGMOSA

Ele concilia o trabalho na Autoridade Portuária Federal – CODEBA com os treinos

# Java 5 Legacy Patterns and Migration Strategies Released in 2004, Java 5 (also known as Java 1.5) introduced language features that fundamentally changed how developers write Java: generics, annotations, enums, autoboxing, varargs, and the enhanced for-loop. Nearly two decades later, many enterprise systems still contain code written against Java 5 idioms—or worse, pre-Java 5 patterns that were never modernized. This post examines common Java 5-era patterns you'll encounter in legacy codebases and provides practical strategies for migrating them to modern Java. ## Why Migrate? Before diving into patterns, it's worth clarifying the motivation: * **Security** : Java 5 reached end-of-life in 2015. Running on unsupported runtimes exposes you to unpatched vulnerabilities. * **Performance** : Modern JVMs offer significantly better garbage collection (G1, ZGC), JIT optimization, and startup times. * **Maintainability** : Newer language features reduce boilerplate and clarify intent. * **Ecosystem** : Contemporary libraries and frameworks frequently require Java 8+. ## Pattern 1: Raw Types and Unchecked Collections A frequent legacy pattern is the use of raw collection types, either from pre-generics habits or incomplete generic adoption. // Legacy: raw types List names = new ArrayList(); names.add("Alice"); String first = (String) names.get(0); // manual cast required ### Migration Strategy Introduce generics and, where possible, the diamond operator (Java 7+): // Modern List<String> names = new ArrayList<>(); names.add("Alice"); String first = names.get(0); // no cast For large codebases, enable the `-Xlint:unchecked` compiler flag to systematically surface raw type usage. Address warnings incrementally, starting with public APIs where type safety benefits propagate to callers. ## Pattern 2: Verbose Iteration Java 5 introduced the enhanced for-loop, but many codebases retained iterator-based or index-based loops. // Legacy: explicit iterator for (Iterator it = orders.iterator(); it.hasNext();) { Order order = (Order) it.next(); process(order); } ### Migration Strategy Convert to enhanced for-loops, then consider Stream API (Java 8+) for transformation-heavy logic: // Enhanced for-loop for (Order order : orders) { process(order); } // Or streams for functional transformations orders.stream() .filter(Order::isPending) .forEach(this::process); Be cautious: streams are not always clearer or faster than loops. Reserve them for genuine data pipelines rather than simple iteration. ## Pattern 3: Manual Boxing and Numeric Wrappers Autoboxing arrived in Java 5, but legacy code often mixes explicit and implicit conversions, sometimes hiding performance pitfalls. // Legacy: explicit boxing Integer count = new Integer(0); Map<String, Integer> counts = new HashMap<String, Integer>(); counts.put(key, new Integer(counts.get(key).intValue() + 1)); ### Migration Strategy Rely on autoboxing and factory methods, and use modern map operations: // Modern Map<String, Integer> counts = new HashMap<>(); counts.merge(key, 1, Integer::sum); // Java 8+ > **Watch out** : `new Integer(0)` always allocates, while `Integer.valueOf(0)` uses the integer cache. The constructors were deprecated in Java 9. Replace them during migration. ## Pattern 4: Enum-Like Constants Pre-Java 5 code often used integer or string constants where enums are appropriate. Some Java 5 code adopted enums but underutilized their capabilities. // Legacy: int constants public static final int STATUS_ACTIVE = 0; public static final int STATUS_INACTIVE = 1; ### Migration Strategy Replace with type-safe enums, leveraging behavior-bearing enum bodies: public enum Status { ACTIVE { @Override public boolean canTransact() { return true; } }, INACTIVE { @Override public boolean canTransact() { return false; } }; public abstract boolean canTransact(); } This eliminates invalid states and centralizes status-specific logic. ## Pattern 5: Null-Heavy APIs Java 5 predates `Optional`. Legacy methods commonly return `null` to signal absence, forcing defensive null checks throughout the caller code. // Legacy public User findUser(String id) { // returns null if not found } ### Migration Strategy For new and refactored APIs, return `Optional<T>` (Java 8+): public Optional<User> findUser(String id) { return Optional.ofNullable(lookup(id)); } // Caller findUser(id).map(User::getName) .orElse("Unknown"); Avoid using `Optional` for fields or method parameters—it's designed for return types signaling optional results. ## Migration Roadmap A pragmatic, low-risk migration follows these stages: 1. **Establish a safety net** : Ensure adequate test coverage before refactoring. Legacy code without tests should be characterized with approval tests first. 2. **Upgrade the runtime incrementally** : Move from Java 5 to a modern LTS (Java 8, 11, 17, or 21) in staged jumps, validating at each step. 3. **Enable compi

Exercícios foram realizados nos portos de Salvador, Aratu-Candeias e Ilhéus para avaliar procedimentos e fortalecer a integração das equipes

AWS GovCloud (US) now offers Claude Opus 5 — the most advanced Opus model yet, and compatible with zero data retention (ZDR) — bringing a step-change in coding, long-running agents, and complex professional work to teams building at the highest level. Claude Opus 5 is available via the bedrock-runtime endpoint in both AWS GovCloud (US) regions, and available via the bedrock-mantle endpoint in AWS GovCloud (US-West) Claude Opus 5 delivers advances in coding, understanding and navigating codebases like an experienced engineer and writing production-quality code while adapting its strategy as it works. It powers dependable agents that run for hours and even overnight, finding paths around obstacles, recovering from errors, and reaching their objectives. And it brings deeper reasoning to long documents and higher accuracy to complex analysis, with the largest gains on document-heavy enterprise work.  Amazon Bedrock offers Claude Opus 5 with zero data retention (ZDR) enabled by default, giving you Opus' top-tier intelligence while meeting your data governance requirements. It keeps your data within AWS infrastructure with regional data residency and provides access through a unified service with AWS-managed features like Guardrails and Knowledge Bases. To learn more, see the Amazon Bedrock documentation and regional availability.