Age | Commit message (Collapse) | Author | Files | Lines |
|
This commit adds some robustness to the interface between the
API-H and BPMN, specifically, in how the response is handled.
I don't have proof, but there appears to be some randomness to
the json provider behavior when used with the jax-rs. Sometimes,
the serializer is adding the root element, and sometimes it
is not. Maybe there's something wrong with the configuration.
Maybe we have competing json providers. I couldn't pin this
down.
I'm almost certain it is the presence of the root element in
the content that causes the API-H code to fail parsing of the
BPMN response. This doesn't kill the request, as you might
expect, but rather, the API-H passes the BPMN response through
to the client (VID, or policy, or whatever).
The original problem (SO-586) was "fixed" by "removing the
wrapper". This "wrapper" is a needed feature of the interface
between BPMN and the API-H. We shouldn't have removed it.
The fact that the "fix" appeared to work is due to the
behavior I described in the previous paragraph. The API-H
chokes on the message, and it passes it through unchanged.
Not really what we want.
So, I don't know why the jackson/json behavior is flaky and
different now, but I can (and did) modify the API-H so it can
parse a json message whether or not it has a root element.
Note that WorkflowResponse.java (in BPMN) and CamundaResponse.java
(in the API-H) are basically the same bean representing the
message format. Seems less than ideal to have two different
classes.
Also note that I changed the name of the "response" attribute
of the WorkflowResponse and CamundaResponse classes to "content".
Got tired of seeing this nonsense everywhere in the code:
response.getResponse()
Change-Id: Icaf70f8457de99e493cf882170fe778c620308c9
Issue-ID: SO-586
Issue-ID: SO-618
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
Remove over 100 whitespaces from logger filename which causes the unit
tests to fail in some development environments.
Change-Id: I068f4d4562b635b19889c3537282949665348c21
Issue-ID: SO-604
Signed-off-by: Michal Kabaj <michal.kabaj@nokia.com>
|
|
Adding support for Basic Auth in the AAI Rest Clients because
ONAP uses this (whereas ECOMP uses 2-way SSL).
In general, each AAI client will allow the user to configure
properties called "aai.auth" and "mso.msoKey". If these are
set, then the client will add the Authorization header to every
request.
Change-Id: I7c81ec05d2ec4a7dca131f2e9e19d341ac89b09f
Issue-ID: SO-576
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
|
|
Change-Id: Ia4d9fedb023ef6893e887ff6b5802623649aeeba
Issue-ID: SO-466
Signed-off-by: Lukasz Muszkieta <lukasz.muszkieta@nokia.com>
|
|
junit coverage for UUIDChecker
Issue-ID: SO-558
Change-Id: I6203b970e9960ea8fba3a1c052cb24b0340b4284
Change-Id: I6203b970e9960ea8fba3a1c052cb24b0340b4284
Signed-off-by: Felix Sangalang <fs7692@us.att.com>
|
|
|
|
Change-Id: Ibe5319e9b795355372cbd5ef374a545fb3a9b1d3
Issue-ID: SO-542
Signed-off-by: Kalkere Ramesh, Sharan (sk720x) <sk720x@att.com>
|
|
Change-Id: I63802ea60d318626ae32e734167d2bce602d72e4
Issue-ID: SO-466
Signed-off-by: Lukasz Muszkieta <lukasz.muszkieta@nokia.com>
|
|
UT Coverage for so/common/src/main/java/org/openecomp/mso/entity
Issue-ID: SO-369
Change-Id: Ibf5859fb068abfadd7e9aa98e7ef2a82a2b654c7
Signed-off-by: Sindhu A <arcot.sindhuri@huawei.com>
|
|
Change-Id: I41031381e5cb5d2f9540e6c941479283f6a59280
Issue-ID: SO-512
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
|
|
Change-Id: Ie6162a62fb3e61d547a7dfd82f01f194127ac989
Issue-ID: SO-514
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
|
|
Change-Id: I185fb4262347120ae94c6d41e0a8de4d47d1ea0f
Issue-ID: SO-517
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
|
|
Change-Id: Id30228ee7b02d9200ca3c02b73e9b0cb9541df46
Issue-ID: SO-515
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
|
|
Change-Id: I97db02310eace781b41b1463239a519a7a167a12
Issue-ID: SO-513
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
|
|
UT Coverage for SO
Change-Id: Ib9517c25b22c37c85b2af84259911b01ddb4bbe5
Issue-ID: SO-369
Signed-off-by: Sindhu A <arcot.sindhuri@huawei.com>
|
|
Adding Junit for:
1.AAIOperationalEnvironmentTest
2.AAIOwningEntityTest
3.AAIProjectTest
4.AAIServiceInstanceTest
Sonar link:
https://sonar.onap.org/code?id=org.onap.so%3Aso&selected=org.onap.so%3Acommon%3Asrc%2Fmain%2Fjava%2Forg%2Fopenecomp%2Fmso%2Fclient%2Faai%2Fobjects
Change-Id: I68265d9df5094941bc6f85dd812b7c85480adf21
Issue-ID: SO-503
Signed-off-by: SP00501638 <SP00501638@techmahindra.com>
|
|
Add test case for DmaapPublisher.
Change-Id: Ia69b174eb429a1b9e69a250eb1110334a97785aa
Issue-ID: SO-369
Signed-off-by: subhash kumar singh <subhash.kumar.singh@huawei.com>
|
|
This is code from AT&T's 1712 and 1802 releases.
Change-Id: Ie1e85851e94bc66c4d9514a0226c221939531a04
Issue-ID: SO-425
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
This reverts commit 327b17ab250b4c17cf3f91f5e4cd9bffd89f3d1e.
It is seriously impeding our ability complete the promised merge of AT&T
1802 code.
While I'm all for coding standards, if we are serious about using spaces
instead of tabs, then I think we need to (1) agree with the community when
this will happen, (2) do consistently in all files, and (3) enforce it.
Change-Id: Ib9b996f6b6c7d81ac9ac95d58b0c7d8cc39675ff
Issue-ID: SO-368
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
Reduce build log warnings by formatting tests
to ONAP code conventions (removing tabs etc.)
Issue-ID: SO-368
Change-Id: I48c6d359b83617aebeb79db4e30c1d72d31f7eec
Signed-off-by: Marcus G K Williams <marcus.williams@intel.com>
|
|
Change-Id: Ibb0dcc412ae6243ee370b8e272455269303130eb
Issue-ID: SO-437
Signed-off-by: Munir Ahmad <munir.ahmad@bell.ca>
|
|
Change-Id: I1dedb9ef1ca7b734e3cfc0a3a594d733dbd298d4
Issue-ID: SO-437
Signed-off-by: Munir Ahmad <munir.ahmad@bell.ca>
|
|
Change-Id: Ic5a16598b1f1ac4f53ab651064b872316abafde0
Issue-ID: SO-437
Signed-off-by: Munir Ahmad <munir.ahmad@bell.ca>
|
|
IssueId : SO-120
Change-Id: I1a94ec1846caaa8968054eb0124fa7cf7885a432
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
This commit rebases changes from openecomp-mso/internal-staging-1710 up to and including this codecloud commit:
54483fc6606ddb1591a2e9da61bff8712325f924
Wed Sep 6 18:12:56 2017 -0400
Rebasing was done on a branch on top of this commit in so/master in ONAP:
93fbdfbe46104f8859d4754040f979cb7997c157
Thu Sep 7 16:42:59 2017 +0000
Change-Id: I4ad9abf40da32bf5bdca43e868b8fa2dbcd9dc59
Issue-id: SO-107
Signed-off-by: Arthur Martella <amartell@research.att.com>
|
|
Update the maven depenency for sdc-distribution-client to cooperate with the sdc changes.
Change-Id: I2da936e5c40cb68c7181bb78307192dd5655b5dc
Signed-off-by: xg353y <xg353y@intl.att.com>
|
|
Change-Id: Ia6a7574859480717402cc2f22534d9973a78fa6d
Signed-off-by: ChrisC <cc697w@intl.att.com>
|