All
Accepted answers
Michelle Stolwyk · Mar 11, 2016 go to post

Joyce is correct - we plan to create an extention point that can be used by other plugins. Extension points allow Eclipse plugins to cooperate with other installed plugins. As a result, your plugin will have safe and reliable access to the server connection and all related information.

Alternatively, you can pull the password from secure storage directly. The internal keys and data format is subject to change, so use of this method should be temporary.

ISecurePreferences secureStore = SecurePreferencesFactory.getDefault().node("com.intersys.eclipse.connmgr");
ISecurePreferences connectionNode = secureStore.node("Connection Name");  // replace with connection name
String password = node.get("pass","default"); // replace default as necessary
Michelle Stolwyk · Jun 20, 2017 go to post

We will be publishing a post describing the newly available changes and roadmap progress for Atelier 1.1 later this week. We will continue this policy with every new update release going forward as well. Please keep an eye on this space.

Michelle Stolwyk · Sep 22, 2017 go to post

We still plan to provide extension points, but customers have not requested this feature broadly. As a result, we have prioritized other features and bug fixes. You will be sure to see extension points made available as the product matures, though.

Michelle Stolwyk · Oct 12, 2017 go to post

If you are referencing Rational Software Architect like Eduard asked, then I expect Atelier can successfully integrate with the product.

Atelier is an Eclipse plugin which means that it can be installed into any Eclipse-based Rich Client Platform (RCP). Our team has not specifically tested this integration however, so you may come across problems. Please contact the WRC in that case.

Michelle Stolwyk · Dec 15, 2017 go to post

Which version of Atelier were you using before? Did you install it to an Eclipse instance using the update site or were you using the 1.0 standalone application?

Michelle Stolwyk · Dec 19, 2017 go to post

Hello, Jan. It seems you are having a problem with the Java class loader. The team responsible for the Java Gateway forwarded the following suggestion. Could you please give it a try? If it doesn't help, please contact the WRC for further support.

java.lang.NoClassDefFoundError: Could not initialize class com.tieto.dataLake.content.data.Content_Data_Record is a Java class loader error typically means that the class loader ran into an exception when trying to load (read) the class. To make sure this is not a user error, I would suggest they try to write a small Java program that simply loads the above class (use Class.forName()), they might get the same error. If not, then it’s probably something to do with the static initializer, I imagine there must be one. They should try to catch an exception in it and that should provide more info on the actual error. A good example of what can go wrong is that they might try to access the file system, right there in the static initializer, and that the path or permissions are different in their dev environment, and on the machine where they try to import the class using the Java Gateway.

To avoid these kinds of errors, we have been advocating the use of a so called ‘façade approach’, where the user makes sure to build most of the app on the Java side, hiding all sorts of things like massive dependencies, big jar files, file system dependencies etc. etc. and exposing only that small app to Cache/Ensemble via the JG

Michelle Stolwyk · Dec 19, 2017 go to post

Based on Kenneth's comment, it seems the problem is fixed in the 1.1 beta release. If this doesn't work for you, I recommend contacting support.

Michelle Stolwyk · Jan 11, 2018 go to post

Thomas, could you please open a WRC ticket? It might have something to do with Eclipse internals. Support would know what to look for on your system so that we can squash this issue for you.

Michelle Stolwyk · Apr 26, 2018 go to post

This sounds like a problem that has been reported previously. I recommend you contact the WRC with your environment details (Eclipse version, Atelier version, Cache'/Ensemble/InterSystems IRIS version, OS flavor) and they should be able to get you sorted quickly.

Michelle Stolwyk · May 14, 2018 go to post

Based on the screen shot, it looks like you tried to save a MAC routine in the RemoteSystemsTempFiles project. This project is not related to Atelier in any way, but should not be blocking you from persisting your change to the file system. 

I encourage you to watch the getting started videos pointed to in other comments and to use the "Cheat Sheets" within the product itself. Go to Help > Cheat Sheets... > Atelier and click the first one. Go through them in order to get a good understanding of Atelier basics.

If after you've done this you are still having trouble, please contact the WRC who are best able to help you troubleshoot. 

Let us know what fixed the problem as an answer here as well please.

Michelle Stolwyk · Jul 18, 2018 go to post

Looks to me like there is a problem with your server connection. I recommend you contact the WRC who will be able to resolve the problem quickly.

Michelle Stolwyk · Dec 26, 2018 go to post

Hi Anthony,

This is not expected behavior and might point to your environment configuration. I recommend you contact the WRC so the team can dig into the details with you.

When I go to the stable update site for 1.3, I can see that the proper version is available. You can see this yourself by pasting the update site URL in your browser.

Hope this helps!

Michelle Stolwyk · Aug 9, 2019 go to post

I agree that this sounds like a configuration issue. I recommend you contact the WRC and an expert will help you diagnose and resolve your issue. They'll have you coding in no time.

Michelle Stolwyk · Aug 16, 2019 go to post

Atelier uses this task to update its cache of your namespace(s). It might also be doing some validation. Does this task always need to be killed? 

You could try playing with your user preferences for caching and validation. Otherwise, I'd go to the WRC. I believe others have had trouble like this before in the past.

Michelle Stolwyk · Sep 13, 2019 go to post

try copying the 1.3 stable update site (jfrog.io) into your browser - if you can't access it, then verify your connection settings

Michelle Stolwyk · Oct 8, 2019 go to post

If your code base is especially large, you might want to consider creating projects like

  • site.system1.routers
  • site.system1.processes
  • site.system2.routers
  • site.system2.processes
  • site.common.routers
  • site.common.productions

Keep in mind that Atelier projects don't play nicely with XML files that aren't supported by the UDL transformation engine. The community should be able to steer you in the right direction if that becomes a blocker for you.

Michelle Stolwyk · Oct 21, 2019 go to post

My guess is that it has something to do with a recent Eclipse upgrade. Photon is Eclipse version 4.8, which is the last officially supported version for use with Atelier.

Michelle Stolwyk · Mar 21, 2016 go to post

I could not recreate this error, so I need a few other details.

How did you delete the class from the server? Did you use the Server Explorer view?

When you deleted the file from the server, did you notice any errors in your Error Log view? You can also test if Atelier successfully deleted the file from its cache by navigating to your Atelier Explorer view, selecting the deleted file from your project, and verifying that the "server version" is blank.

When you say you deleted the server, do you mean the server instance or the server connection within Atelier?

If you create a new connection with a different name, do you still see the deleted class from the Server Explorer view when you expand the classes from the new connection?

Ultimately, you should report a bug with your error log so developers can pin point the cause. I suspect there's a problem with your cache.

Michelle Stolwyk · Feb 24, 2017 go to post

Users with high resolution screens on Windows 10 will see pixelated icons if they have the Atelier IDE HiDPI feature installed.

If you've installed the standalone Atelier application from the WRC distribution page, then updating to version 1.0.263 may have automatically added this feature erroneously.

To fix:

  1. Close the Atelier application
  2. Navigate to <installation directory>/Atelier/plugins/
    • Note: default installation directory is C:\InterSystems
  3. Delete com.intersys.eclipse.hidpi.aspects.jar
  4. Open the Atelier application

If you've installed the Atelier plugin to an Eclipse application, the steps are a bit more straightforward.

To fix:

  1. Open Eclipse
  2. Navigate to Help > Installation Details > Installed Software
  3. Select the "Atelier IDE HiDPI Support" feature
  4. Click the "Uninstall" button at the bottom of the page
  5. In the future, make sure that you do not install this feature when updating from the Atelier update sites

If these steps don't help, please contact support and they will be able to further assist you.

Michelle Stolwyk · Sep 22, 2017 go to post

The process for merging changes is described in a new post from the Atelier team. It boils down to this: use your version control system to merge conflicts. The conflict wizard that appears when saving changes to the server does not support merging by design.

Michelle Stolwyk · Oct 23, 2017 go to post

Hi, Mike. That error is referring to your file path. I recommend you contact the WRC with these sorts of problems as they will be able to quickly solve the problem.

Michelle Stolwyk · Nov 9, 2017 go to post

The Server Explorer view from the Atelier perspective provides a shortcut to the Management Portal.

  1. Open the Server Explorer view
  2. Right-click on the connection you are interested in
  3. Select "Management Portal" from the context menu

The Management Portal will be opened in an external browser.