To prevent spam users, you can only post on this forum after registration, which is by invitation. If you want to post on the forum, please send me a mail (h DOT m DOT w DOT verbeek AT tue DOT nl) and I'll send you an invitation in return for an account.
Strange behaviour - parameter matching of plug-ins
Part of a conversation between Andrea Burattin and Boudewijn van Dongen in which Andrea asked:
I have the AuthoredType PLGProcessCollection that extends
Vector<PLGProcess>. When I use it, the action tab matches also the
second parameter of Declare miner, that is just a Vector.
I have the AuthoredType PLGProcessCollection that extends
Vector<PLGProcess>. When I use it, the action tab matches also the
second parameter of Declare miner, that is just a Vector.
Joos Buijs
Senior Data Scientist and process mining expert at APG (Dutch pension fund executor).
Previously Assistant Professor in Process Mining at Eindhoven University of Technology
Senior Data Scientist and process mining expert at APG (Dutch pension fund executor).
Previously Assistant Professor in Process Mining at Eindhoven University of Technology
Comments
-
To which Boudewijn replied:
This not strange behavior at all. You cannot use types with generics (i.e. <?>) as input for plugins. The reason for this is a limitation in Java that generics are only available at build time, not at runtime. ProM is simply unable to verify if the right generics are set, as this information is removed in class files.Joos Buijs
Senior Data Scientist and process mining expert at APG (Dutch pension fund executor).
Previously Assistant Professor in Process Mining at Eindhoven University of Technology
Howdy, Stranger!
Categories
- 1.6K All Categories
- 45 Announcements / News
- 225 Process Mining
- 6 - BPI Challenge 2020
- 9 - BPI Challenge 2019
- 24 - BPI Challenge 2018
- 27 - BPI Challenge 2017
- 8 - BPI Challenge 2016
- 68 Research
- 1K ProM 6
- 393 - Usage
- 287 - Development
- 9 RapidProM
- 1 - Usage
- 7 - Development
- 54 ProM5
- 19 - Usage
- 187 Event Logs
- 32 - ProMimport
- 75 - XESame