Hi Muhammad,
can you share a screen shot of the import section of your java service, please?
Are you uisng Local Service Development feature?
There is a little difference where the classes are available dependend on where you place them:
When placing them in the package, they will be only visible within this package and all packages that declare this one as a package dependency. This one only requires package reload when jar changes.
When placing them under lib/jars of the IntegrationServer (a better place would be lib/jars/custom), they are vislble to all packages on IS.
This one requires IS restart when jar changes.
Unfortunately they need to be imported to Designer separately to get the warnings about missing imports resolved.
But this does not hinder you to develop without this. You will have to write down the import statements manually in this case, leading to the missing imports warning, but when saving the service it will be compiled on the server without issue as the classes are loaded by reloading the package or restarting the IS.
Regards,
Holger
#Integration-Server-and-ESB#webMethods#Flow-and-Java-services