David here again,
The problem was that the Websphere server (for whatever reason) could not find the .class files that where in the component (as a jar). The work around was to add an additional classpath to websphere and manually copy our class files to that directory and restart websphere. This works, but its far from elegant.
Can anyone shed some more light of the subject?
The above hack causes Websphere to forget where its adobe classes are and causes a host of other problems.
Can someone from Adobe have a look at this issue please.
Do you ever find a resolution to this? My issue right now is that I can add a custom datatype as a process variable but am unable to create a new instance of it without calling out to my dsc which isn't ideal for security reasons.
If you run into this issue, you not only need to have your class in the DataTypes section of your component.xml, but you also need to have that package defined in the Export Packages of your RunTime section of your component.xml.