Resolving Invalid property name: `shareBytes` on class `oracle.sql.TIMESTAMP` using Reflection

Discussed an alternative way to the commonly used property oracle.jdbc.j2ee13Compliant=true, to resolve the invalid property shareBytes error when dealing with timestamps in Oracle Database.

Actual logic implementation starts at 06:42 in case you might want to skip inital part on understanding the problem.

⏱ Video Timestamps
==========================
00:00 Introduction
01:06 Understanding the root cause
06:42 Code to convert oracle.sql.TIMESTAMP to java.sql.Timestamp
15:32 Access the function from dataweave
20:00 Testing the implementation

📌 Related Links
==========================
🔗 Classloading Isolation in Mule 4:    • Refined Error handling in Dataweave 2.0 | ...  
🔗 Cache in Mule 4:    • Mulesoft 4 | Cache Scope | Object Store v2...  
🔗 Transactions in Mule 4:    • Mule 4 | XA | Local Transactions | Bitroni...  
🔗 API Design Best Practices:    • API Design | Best Practices  
🔗 Custom Policy:    • Mule 4: Create Custom Policy  
🔗 API Gateway and Autodiscovery:    • Mule 4: API Gateway and Auto Discovery  
🔗 Global Error Handler:    • Mule 4: Create a Global Error Handler  

🎬 Popular Mule 4 Playlists
==========================
💥 Advanced Concepts in Mule: https://bit.ly/AdvancedMule



💥 Mule 4 Custom Connectors: https://bit.ly/Mule4CustomConnectors



💥 Dataweave Series: https://bit.ly/dataweave2



Let's connect:
=========================
💥 Twitter:   / vishwas_p13