Sorry I wasn’t very clear with the explanation. I asked about the content of the mandiri.sams.util to see if there were other Java services within. It is not about 2 services with the same name. It is about nested folders that both contain Java services. That cannot be done. Designer will let you create them, but once you edit the Java service in the nested folder, that is when the conflict arises. The way the Java code is managed is a combination of Java packages and classes.
For example:
The aggregated code, when you view the source in the file system on the server, looks like this:
The content of Sample/util.java is:
package Sample;
// -----( IS Java Code Template v1.2
import com.wm.data.*;
import com.wm.util.Values;
import com.wm.app.b2b.server.Service;
import com.wm.app.b2b.server.ServiceException;
// --- <<IS-START-IMPORTS>> ---
// --- <<IS-END-IMPORTS>> ---
public final class util
{
// ---( internal utility methods )---
final static util _instance = new util();
static util _newInstance() { return new util(); }
static util _cast(Object o) { return (util)o; }
// ---( server methods )---
public static final void myjava (IData pipeline)
throws ServiceException
{
// --- <<IS-START(myjava)>> ---
// @sigtype java 3.5
// --- <<IS-END>> ---
}
}
Note the name of the class.
The content of Sample/util/test.java is:
package Sample.util;
// -----( IS Java Code Template v1.2
import com.wm.data.*;
import com.wm.util.Values;
import com.wm.app.b2b.server.Service;
import com.wm.app.b2b.server.ServiceException;
// --- <<IS-START-IMPORTS>> ---
// --- <<IS-END-IMPORTS>> ---
public final class test
{
// ---( internal utility methods )---
final static test _instance = new test();
static test _newInstance() { return new test(); }
static test _cast(Object o) { return (test)o; }
// ---( server methods )---
public static final void yourjava (IData pipeline)
throws ServiceException
{
// --- <<IS-START(yourjava)>> ---
// @sigtype java 3.5
// --- <<IS-END>> ---
}
}
Note the package name. That is where the conflict is – package name (folder) collision with a class name (another folder). It is not the names of the Java services. It is the presence of Java services, with any name, at multiple levels within a single folder tree.
Editing and saving the Java service in the nested folder results in the error in your OP:
...packages/Sample/code/source/Sample/util/test.java:1: error: package Sample.util clashes with class of same name
package Sample.util;
Interestingly, the error does not appear when the Java service in the nested folder is initially created. Just when it is edited and saved.
Have you tried editing any of the Java services in any other child folder? My guess is the save will complain about those too.
Moving the Java services that are directly in the util folder to a child folder should do the trick.