Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Adobe Summit 2023 [19th to 23rd March, Las Vegas and Virtual] | Complete AEM Session & Lab list

Error invoking a custom component in a Process.

Avatar

Not applicable
Hi,



I've build a custom component that uses Output ES services.

If i run it as a Java app all runs well, he generates the output pdf files and output report .xml file.



If i import it as a component into Livecycle ES and use it in a process i get the following error:



2008-05-20 11:35:52,390 INFO [STDOUT] com.adobe.livecycle.output.exception.OutputException: java.lang.ClassCastException: com.adobe.livecycle.output.client.OutputResult



2008-05-20 11:35:52,390 INFO [STDOUT] at com.adobe.livecycle.output.client.OutputClient.generatePDFOutput(OutputClient.java:138)



2008-05-20 11:35:52,390 INFO [STDOUT] at outputfactory.Output.outputFromXML(Output.java:55)



2008-05-20 11:35:52,390 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)



2008-05-20 11:35:52,390 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)



2008-05-20 11:35:52,390 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

.

.

.

2008-05-20 11:35:52,390 INFO [STDOUT] Caused by: java.lang.ClassCastException: com.adobe.livecycle.output.client.OutputResult



2008-05-20 11:35:52,390 INFO [STDOUT] at com.adobe.livecycle.output.client.OutputClient.generatePDFOutput(OutputClient.java:122)



I deploy it with th adobe-output-client.jar in my component jar and the reference for it in the component.xml file (also in my component.jar).



How can i solve this problem? thanks
2 Replies

Avatar

Level 9
Hi Rui

Very difficult to know from your description.

It's a class-cast exception - try to find the line in your code that's doing the cast, and find out what the actual object is.

It could also be a jar versioning problem, or a class-loader problem.

Sorry, very difficult to help without doing some detailed debugging.

Howard

http://www.avoka.com