-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AET as clientless application #50
Labels
Comments
3ndriu
pushed a commit
that referenced
this issue
Jan 30, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 1, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 2, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 6, 2017
Previously, the message queue had been polled when the client made processing status request. This commits changed it, so the SuiteExecutor service polls the message queue continuously and status request only returns previously obtained status. This commit also adds support for suite locking.
3ndriu
pushed a commit
that referenced
this issue
Feb 6, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 7, 2017
This commit removes JMS communication from client app. The client app now communicates with AET server via HTTP.
3ndriu
pushed a commit
that referenced
this issue
Feb 7, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 7, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 7, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 7, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 7, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 8, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 8, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 8, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 9, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 9, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 24, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 24, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 24, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 24, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 24, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 24, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 27, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 27, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 27, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 27, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 27, 2017
3ndriu
pushed a commit
that referenced
this issue
Feb 27, 2017
3ndriu
pushed a commit
that referenced
this issue
Mar 7, 2017
3ndriu
pushed a commit
that referenced
this issue
Mar 8, 2017
malaskowski
pushed a commit
that referenced
this issue
Mar 9, 2017
…lient-app Feature/#50 remove logic from client app
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Scheduling AET job should be as simle as performing http request. Remove client application (AET Maven Plugin) and move its logic to AET Server. Create a web service that consumes e.g. HTTP request with suite XML file. Thanks to this scheduling AET job will be available without need to install Java and Maven.
Technical challenges:
After this enhancement user should be able to schedule AET job with this simple command:
curl POST http://server/api/scheduleJob -d @suite.xml
The text was updated successfully, but these errors were encountered: