[jboss-jira] [JBoss JIRA] (DROOLS-682) Build and deploy option required in Standalone mode editors
Michael Anstis (JIRA)
issues at jboss.org
Thu Jul 23 08:48:02 EDT 2015
[ https://issues.jboss.org/browse/DROOLS-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13092190#comment-13092190 ]
Michael Anstis commented on DROOLS-682:
---------------------------------------
[~mark.proctor] Well.. generally speaking we don't use REST but Errai's RPC mechanism.
"Compile\install" a Project however can be triggered with a REST call; see http://docs.jboss.org/drools/release/6.2.0.Final/drools-docs/html/ch17.html#drools.WorkbenchRemoteAPI
Alternatively a custom "Header" could be written to invoke the Project Build service. See http://docs.jboss.org/drools/release/6.2.0.Final/drools-docs/html/ch15.html#wb.Embedding.
I agree we probably won't fix this directly as there are alternatives available.
> Build and deploy option required in Standalone mode editors
> -----------------------------------------------------------
>
> Key: DROOLS-682
> URL: https://issues.jboss.org/browse/DROOLS-682
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.1.0.Final
> Environment: JDK 1.8 / Wildfly 8.1 / Drools Work bench 6.1 Final
> Reporter: Ramesh C
> Assignee: Michael Anstis
> Priority: Blocker
>
> Integration of an asset editor to edit in external application is works well
> for an asset. if user edits and saves the asset it only saves the editor.
> As of now It does not builds the project and deploys the code into local repository and work bench repository. So,it is not possible to use the work bench in standalone mode effectively in production.
> kindly provide build and deploy button in standalone mode asset editors.
> So, Admins can edit, build and deploy the changes to repository and in the application, it will be read dynamically using ReleaseId mechanism or Scan mechanism. In this way, it will help for rules editing and building
> without restarting the application servers.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jboss-jira
mailing list