Hi,
Currently we are in the process of implementing the correlation support for
for BPMN process instances.
This correlation request will resume the execution of a particular process
instance based on the provided variable values.
Correlation request can be accessed by using following json
The deployment engine should call the deployer only for valid artifact
types. So yes, it looks like the fixes have to be done in the kernel.
On Thu, Dec 10, 2015 at 1:47 PM, Samiyuru Senarathne
wrote:
> First part of this issue is trying to deploy invalid files. The second
>
First part of this issue is trying to deploy invalid files. The second part
of the issue is deployment engine tries to deploy the artifact again and
again even though an exception is thrown for that particular artifact by
the deployer. Because of this the exception is thrown again and again.
The
Yes, we can move them to the CARBON_HOME. Repository directory has been
there for historic reasons since 2007 or so. We don't need it anymore.
On Thu, Dec 10, 2015 at 9:32 PM, Sameera Jayasoma wrote:
> Hi Folks,
>
> How about the @Subject? We've introduced repository directory
Hi,
Currently in the BPMN Rest API, process instance start operations are not
conditional. But there are occasions, process instances should not be
initialized when ever there is a already created instance with same state (
Same variable values).
Therefore, in order to perform checked instance
Hi,
@Vinod, I used the format given in the Activiti rest api documentation to
include the response codes.
@Nuwan, I have updated the user guide with the response codes and the
sample success responses.
Thanks,
Natasha
On Thu, Dec 10, 2015 at 8:39 AM, Vinod Kavinda wrote:
> Hi
Hi All,
As you know AppFac product is moving to use kubernetes and we are in
the process of integrating kubernetes with fabric8 api for the first mile
stone release.
In this process we are changing some of the work flows and in later
releases enhance it.
When it comes to build the artifacts
Can't we combine the components having the same deployment directory? Let's
say if we are combining GW and AS. Then we can have the same deployment
directory and under that, we can have folders for webapps(AS),
carbonapps(Common), gw-routes(GW), etc.
On Thu, Dec 10, 2015 at 3:43 PM, Afkham Azeez
Hi Folks,
How about the @Subject? We've introduced repository directory a long time
back to support deploying our product in other Application servers. Now we
don't support that, therefore there is no need to maintain that directory
structure.
Thanks,
Sameera.
--
Sameera Jayasoma,
Software
In MSS case there are no more subfolders under 'mss' directory. It is named
'mss' because our artifacts are different from others. If that name is
confusing I think we can come up with a different name.
On Thu, Dec 10, 2015 at 9:22 PM, Chanaka Fernando wrote:
> Can't we
Hi all ,
Now I'm working on following improvement in the VFS inbound and ESB polling
inbound.
1. For VFS inbound we only have the option to delete or move file after
processed or after error. Need to give the options copy and leave as it is.
2. Current ESB polling inbound only support
Hi,
To get the input for polling interval/cron configuration, how about using a
toggle button like in Scheduled Tasks.
[image: Inline image 1]
In this case, we can set interval as default selection. Based on the
selection, you can use required implementation.
Thanks.
On Fri, Dec 11, 2015 at
Do we really need "mss" at the end? If we take the MSS server, then we are
already inside it. Wouldn't that be enough having
"$CARBON_HOME/repository/deployment" ?
On Thu, Dec 10, 2015 at 6:33 AM, Aruna Karunarathna wrote:
>
>
> On Thu, Dec 10, 2015 at 11:57 AM, Sameera Jayasoma
+1. Most of the other servers simply have conf, bin, lib etc. at server
home.
Thanks.
On Thu, Dec 10, 2015 at 9:32 PM, Sameera Jayasoma wrote:
> Hi Folks,
>
> How about the @Subject? We've introduced repository directory a long time
> back to support deploying our product in
14 matches
Mail list logo