Hey there, let's figure out why you're hitting that PropertyNotFoundException when trying to access the pasien property of your Rawatjalan entity in JSP. I've dealt with similar headaches before, so here's a step-by-step breakdown of what to check and fix:

1. The #1 Culprit: Missing or Misspelled Getter Method #

EL expressions in JSP strictly follow JavaBean conventions—this means it looks for a getPasien() method in your Rawatjalan class, not just the private pasien field.

Double-check your Rawatjalan entity:

• Make sure you have a public getter method for pasien with exact spelling.
• Avoid typos like getPasienn() or incorrect capitalization (e.g., getpasien()).

Example of a correct getter setup:

@Entity
public class Rawatjalan {
    @ManyToOne
    @JoinColumn(name = "pasien_id") // Ensure this matches your DB column name
    private Pasien pasien;

    // Required getter for EL to access the property
    public Pasien getPasien() {
        return pasien;
    }

    // Optional setter (if you need to modify the association)
    public void setPasien(Pasien pasien) {
        this.pasien = pasien;
    }

    // Other properties, constructors, and methods...
}

2. Check JSP Expression Spelling & Case Sensitivity #

EL is case-sensitive, so even a tiny typo here will trigger the error.

Verify your JSP code:

• Ensure you're using ${rawatjalan.pasien} (all lowercase for pasien) instead of variations like ${rawatjalan.Pasien} or ${rawatjalan.pasienn}.
• If you're accessing a property of Pasien (like nama), make sure that property also has its own getter in the Pasien entity.

Example of correct JSP usage:

<!-- Accessing pasien's nama property -->
<tr>
    <td>${rawatjalan.pasien.nama}</td>
    <td>${rawatjalan.dokter.nama}</td>
    <td>${rawatjalan.treatment.nama}</td>
</tr>

3. Verify the Object in Your Model is a Rawatjalan Instance #

Sometimes the error pops up because the object you're passing to the JSP (via your controller) isn't actually a Rawatjalan object.

Check your controller code:

• Ensure you're adding the correct entity to the model, like:

  @GetMapping("/rawatjalan/{id}")
  public String showRawatJalan(@PathVariable Long id, Model model) {
      Rawatjalan rawatjalan = rawatjalanService.findById(id);
      model.addAttribute("rawatjalan", rawatjalan); // Make sure this is the right object
      return "indextrx";
  }
  

• Avoid accidentally passing a different object (like a DTO without a pasien getter) under the same rawatjalan attribute name.

4. Lazy Loading Edge Case (Less Likely, But Worth Checking) #

If your @ManyToOne annotation uses fetch = FetchType.LAZY, you might run into a LazyInitializationException later, but this doesn't usually cause a PropertyNotFoundException. However, if you're not initializing the pasien association before rendering the JSP, it's still a good practice to fetch it upfront.

Modify your repository query to use JOIN FETCH to load all associations eagerly:

@Repository
public interface RawatjalanRepository extends JpaRepository<Rawatjalan, Long> {
    @Query("SELECT r FROM Rawatjalan r JOIN FETCH r.pasien JOIN FETCH r.dokter JOIN FETCH r.treatment WHERE r.id = :id")
    Rawatjalan findByIdWithAssociations(@Param("id") Long id);
}

Then call this method in your service layer to ensure all associated entities are loaded before passing to the view.

Final Quick Checklist #

1. Confirm Rawatjalan has a public getPasien() method.
2. Double-check JSP expressions for typos and correct case.
3. Ensure the controller passes a valid Rawatjalan instance to the model.
4. If using lazy loading, fetch associations upfront with JOIN FETCH.

内容的提问来源于stack exchange，提问作者Airlangga