David again,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.

Hi Nico, Thanks for the great post! I too have been looking for an example on this one! However your solution doesnt work in my case as I am getting a "Class Not found error" due to the fact that the .jar I reference in Java (adobe-usermanager-client.jar) is not located on the server. Do you have an...

Not sure if this will be helpful or not, but I found that you have to compile java components using the IBM Java 1.5 SDK (That comes with websphere) instead of the Sun Java 1.5 SDK when creating components for Websphere. Also make sure you have the latest updates to websphere 6.1 as the Java SDK did...

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 wor...

Hi all,We have developed a custom component that uses various custom Java Objects (POJOS). We have specified the java objects in the component.xml file as: using both true and false for the "standard" attribute. (neither seem to have an effect on the end result)When within workbench we can create ...