arrow_back history picture_as_pdf This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong. ~~NOTRANS~~ ~~Title: Rename server-side objects and action names~~ If you call an action or request a server-side object, you should know the name of the action or the object. Usually this isn't a big problem because it's your application and you know everything about it. But it's different if you use pre-defined application frames like ProjX. The application frame has some pre-requirements, e.g. the menu will be created after authentication. The application frame does following call: <file java> AbstractConnection con = getConnection(); Object[] oResult = con.call(new String[] {"workScreenAccess", "workScreenAccess", "workScreenAccess"}, new String[] {"getAvailableWorkScreens", "getAvailableRoles", "getAvailableMetaData"}); </file> This means that you have following in your Session LCO: <file java> public IWorkScreenAccess getWorkScreenAccess() throws Exception { IWorkScreenAccess wsac = (IWorkScreenAccess)get("workScreenAccess"); if (wsac == null) { wsac = new DBWorkScreenAccess(); ((DBWorkScreenAccess)wsac).setDBDataSource(getDBAccess()); put("workScreenAccess", wsac); } return wsac; } </file> The application frame won't work if the method name isn't getWorkScreenAccess. If you have a specific naming schema and won't use the same method name, you could do following: <file java> @Replacement(name="workScreenAccess") public IWorkScreenAccess getWSAccess() throws Exception { ... } </file> The Replacement annotation maps the custom method to the expected name. This annotation can be used for object and action names: <file java> @Replacement(name="sendCustomerEmail") public void notifyCustomer() throws Exception { ... } </file>