[
https://issues.jboss.org/browse/JBIDE-7379?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-7379:
------------------------------------
The upshot of this is that with your API only expecting to export
server configuration, only the Teiid server configuration would be exportable. However,
Teiid also has file artefacts, stored in other parts of the workspace which need a
separate storage unit (not implemented yet).
The API I wrote completely allows any import / export participant to add an arbitrary
number of files to the resultant archive. I didn't add them yet, but I have two
additional files I'd like to be adding for JBoss AS / wildfly servers. They would just
be contributed in a higher-level plugin of mine so I didn't get around to do it yet.
I think it's reasonable to expect a specific archive format for our import/export, and
I think a zip / jar is a reasonable decision. So I think this is a fair assumption that
I'd like to keep.
I think you'll find you can actually add any number of files to the jar. It is *not*
limited to server configuration / runtime / launch. You can add anything you want at any
path you want. Of course if there's any changes you'd like to suggest, I'd be
willing to hear.
I already have the import / export actions with some minimal UI but I had planned to
enable a more fully-featured UI eventually... so some discussion on what type of UI
we'd like for the import could be useful.
Importing / Exporting of AS servers ignore command line args,
filesets, xpaths, and even runtimes
-------------------------------------------------------------------------------------------------
Key: JBIDE-7379
URL:
https://issues.jboss.org/browse/JBIDE-7379
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 3.2.0.Beta1
Reporter: Rob Stryker
Assignee: Paul Richardson
Fix For: 4.3.x
Exporting of servers is incomplete. It does not export any saved filesets, xpaths, or
custom launch configuration args.
Importing of servers is also incomplete, not importing any of these elements. Also, while
the servers themselves are imported, sometimes their runtimes are not created at all, and
you get a server with no runtime. This has been very hard to track down, but no
runtimeAdded event is ever fired, and in our code it looks as if they're not even
created or looked for.
This needs to be re-visited and tested extensively. I expect I will move import / export
functionality into the AS plugin for now since hte o.j.t.runtime plugin already depends on
AS. This will allow me to use classes already in the AS test suite for filesets and xpaths
properly. I will keep the handler in the runtimes plugin but merely have it delegate to
the functionality stored in the as plugin.
It currently seems to be saving only servers and not the runtimes.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)