Add Enterprise category: Servlet vs JAX-RS, EJB vs CDI, JDBC vs JPA, JPA vs Jakarta Data

[Copilot]

Introduces a new enterprise category covering four Java EE → Jakarta EE migration patterns.

New content (content/enterprise/)

• servlet-vs-jaxrs — HttpServlet boilerplate → declarative @Path/@GET JAX-RS resource
• ejb-vs-cdi — @Stateless EJB + @EJB injection → @ApplicationScoped CDI bean + @Inject + @Transactional
• jdbc-vs-jpa — Manual ResultSet mapping → EntityManager.find() and JPQL
• jpa-vs-jakarta-data — Verbose EntityManager + JPQL → @Repository interface with auto-generated DAO implementation via Jakarta Data

Generator & UI

• Added "enterprise": "Enterprise" to CATEGORY_DISPLAY and the ordered categories list in generate.py
• Added Enterprise filter pill to templates/index.html
• Added .badge.enterprise CSS rule (--cyan palette) to styles.css

Navigation

Threaded the four new patterns into the global prev/next chain after language/compact-canonical-constructor (previously the terminal node).

All HTML and site/data/snippets.json regenerated (99 snippets total).

Screenshots

Servlet versus JAX-RS

EJB versus CDI

JDBC versus JPA

JPA versus Jakarta Data

Original prompt

---

This section details on the original issue you should resolve

<issue_title>New Category and Slugs for Enterprise Edition</issue_title>
<issue_description>The old days of Java EE and EJBs are gone.

Start a new category called 'enterprise' and add these slugs:

• Servlet versus JAX-RS
• EJB versus CDI
• JDBC versus JPA</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes New Category and Slugs for Enterprise Edition #41

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[brunoborges]

@copilot can you generate screenshots for each new slug?

[Copilot]

@copilot can you generate screenshots for each new slug?

Here are screenshots of each new enterprise slug:

Servlet versus JAX-RS

EJB versus CDI

JDBC versus JPA

[brunoborges]

@copilot The slug on "JDBC versus JPA" could be followed by an additional one on "JPA versus Jakarta Data" where the latter just declares an interface and lets Data generate the DAO ("Repository") implementation.

Jakarta Data specification: https://jakarta.ee/specifications/data/1.0/

[Copilot]

@copilot The slug on "JDBC versus JPA" could be followed by an additional one on "JPA versus Jakarta Data" where the latter just declares an interface and lets Data generate the DAO ("Repository") im...

Added in commit 6a7c52f. The new slug shows the verbose EntityManager approach (JPQL + manual persist) on the left, vs. a three-line @Repository interface backed by Jakarta Data's auto-generated implementation on the right.

[brunoborges]

@copilot give me screenshots for each new slug. The screenshot must be of the entire detailed page of each.

[Copilot]

@copilot give me screenshots for each new slug. The screenshot must be of the entire detailed page of each.

Here are full-page screenshots of each new enterprise slug:

Servlet versus JAX-RS

EJB versus CDI

JDBC versus JPA

JPA versus Jakarta Data

Each screenshot shows the complete detail page: nav bar, Enterprise badge, gradient title, old/modern code panels, summary + explanation, "Why the modern approach wins" cards, related patterns, documentation links, and prev/next navigation.