I guess this happen due to the database connection mentioned in the dbs. It
requires to restart the server.
Thanks,
Gayan
On Thu, Jan 4, 2018 at 7:17 AM, Shazni Nazeer wrote:
> I have noticed the same. This happens in the data services server 3.5.1
> too. Always requires a
Yeah, I also felt the same, It's confusing to have one behaviour for Proxy
and another for DSS. There should be a consistency.
Thanks
Godwin
On Thu, Jan 4, 2018 at 12:22 PM, Gihan Anuruddha wrote:
> Ideally, we should have a consistent behavior in EI for both proxies and
> data
Ideally, we should have a consistent behavior in EI for both proxies and
data services. But since this is not a recommended way can leave it this
way for now.
On Thu, Jan 4, 2018 at 10:43 AM, Rajith Vitharana wrote:
> Hi Godwin,
>
> AFAIR deployment flows are different for ESB
Hi Godwin,
AFAIR deployment flows are different for ESB artifacts and DSS artifacts,
DSS artifacts are getting deployed via axis2 deployer(that is it will pick
up changes from file system and get deployed, so with car files, this won't
happen as the actual file does not get changed) whereas when
Hi Vinod,
If you change anything in Proxy (deployed using CAR) it's getting hot
deploy. Yeah, changes get discard once server restart. Again my problem is
why proxy services changes reflect and not in DSS.
Thanks
Godwin
On Thu, Jan 4, 2018 at 11:57 AM, Vinod Kavinda wrote:
>
Hi Godwin,
Proxy deployers and DSS deployers are different components. Maybe we are
not listening to the unpacked carbon apps folder by the DSS deployer. Yes,
this is useful for testing. Let's report a bug. We can fix if it is
technically feasible.
Regards,
Vinod
On Thu, Jan 4, 2018 at 10:33 AM,
Hi Godwin,
In proxy services also, changes do not get persisted. If you restart the
server, the changes will be discarded.
Regards,
Vinod
On Wed, Jan 3, 2018 at 12:58 PM, Godwin Shrimal wrote:
> Hi Nandika,
>
> Thanks for the response. I understand it's not recommending to
Yes, It's a bug. Normally If we do a change in CApp, It will reflect the
service. but In this case, It's not working as expected.
Thanks,
Madhawa
On Thu, Jan 4, 2018 at 7:17 AM, Shazni Nazeer wrote:
> I have noticed the same. This happens in the data services server 3.5.1
>
I have noticed the same. This happens in the data services server 3.5.1
too. Always requires a restart to take effect.
Is this a bug?
On Tue, Jan 2, 2018 at 1:15 AM, Godwin Shrimal wrote:
> Hi Devs,
>
> We can change proxy services (Deployed using CAR) from UI and its getting
Hi Pubudu,
Yeah, I know it's not recommending, But when we are doing testing, think
you want to add a small log to the proxy, you simply can add it via UI and
test it.
My Question is not about the recommendation, it's about why DSS behaving
differently than the proxy services.
Thanks
Godwin
On
Hi Godwin,
AFAIK, we should not change any artifact which is deployed using a CAR
file. This is not recommended. I am not sure about the reasons for this
behavior.
Thank you!
On Tue, Jan 2, 2018 at 12:45 PM, Godwin Shrimal wrote:
> Hi Devs,
>
> We can change proxy services
Hi Nandika,
Thanks for the response. I understand it's not recommending to change the
artifact from UI, my problem is if we change proxy service (deployed using
CAR) it's getting hot deploy. But it's not working with Data services. Is
this intentionally done or is this a bug?
Thanks
Godwin
On
HI Godwin,
It is not recommended to make changes to artefacts deployed using a car
file from the management console. And these changes are not persisted and
server restart will result in the changes being discarded. Hence pls use
dev studio to make any changes necessary to artefacts contained
13 matches
Mail list logo