JADE Environment Development Ideas

What's new in the upcoming JADE release?

IMPROVED DEVELOPER EFFICIENCY. ENHANCED SECURITY. SMOOTHER INTEGRATION

The JADE 2022 release meets tomorrow’s business demands.


Start your update to JADE's latest release

Not obvious when working with 'exclusive' properties

Sometimes I will code something that causes a runtime exception: 1307 : Cannot pass an exclusive subobject reference to this method.

The compiler doesn't give any warning I have coded something this way, collection.add(someExclusiveObject) compiles as normal.

When looking at 'someExclusiveObject' Property Details, the only hint I get that it's an Exclusive is an extremely subtle "non-virtual" at the bottom of the details. Compare this to a Non-Exclusive which has the words "non-virtual embedded" at the bottom, this is confusing.

It's very hard to catch this mistake before runtime. Some ideas:

- Property Details "non-virtual" / "non-virtual embedded" have a suffix afterwards to stipulate which one of these phrases is the 'Exclusive' version.

- Can the compiler check this and error instead of waiting for me to get a runtime error.

- Hover-text (and maybe IDE colour option) to help identify these while I'm coding.

Thanks

  • Guest
  • Oct 6 2025
  • Needs review
  • Attach files