Hi DAS team,
We have a scenario in which data publishing failed because of incorrect
data. We are using 200 ok for health check in data publishing. So even
though data was not published, we are getting 200 ok responses. In that
case, how do we differ data successfully published case from data
You are working in an OSGi environment, so you need to be thinking from the
osgi classloading perspective. Each osgi bundle under
repository/components/{plugins,dropins} has its own classloader and a
classpath.
Hence, the place you put your persistence.xml is important. I'm not sure
how you call
Hello everybody,
I am currently writing a custom connector to retrieve information from a
database. Because the mediators to do so does not fit my needs, I am using
a custom Java class which is currently implemented to retrieve a DataSource
via the JNDI name I configured in the ESB interface.
Hello,
We are trying to make the URL for the referenced XSD schemas to be full
instead of relative on generated wsdl on ESB.
We tried some properties defined in the documentation but they didn't work.
I've asked the same question on Stackoverflow[1] but didn't get any answer
from there.
Does
Hi All,
Thanks for testing and verifying the WSO2 Enterprise Integrator 6.1.1 RC1.
We are closing the vote now. This vote has passed with 8 +1s and 0 -1s.
Therefore we are proceeding with the WSO2 Enterprise Integrator 6.1.1
release.
8 +1
0 -1
Thanks.
On Wed, May 3, 2017 at 3:14 PM, Madhawa
Hi All,
I have tested simple CRUD operations with data services.
tested request box, nested queries for MySQL.
I found an edge case issue with JSON with nested queries in data services,
which was reported in [1] JIRA. This is reproducible in 6.1.1. Since the
fix has merged to the axis2
Hi all,
Tested and verified followings:
- JMS with Broker Profile (Consumer, Producer, Message store, Processor)
- Broker Profile basic functionality (Queues, Topics, Durable/Non
durable subscriptions)
- MSF4J service deployment
No issues found.
[+] Stable - go ahead and release
Hi All,
Below areas were tested in tenant mode.
- CAPP deployment and invoke an api deployed through capp
- Salesfore connector scenario
- Use of local entries
General
- Encrypt passwords using secure vault
- Offset
Above scenarios worked fine. +1 for featurea
Below Readme issues were
Hi all,
Tested and verified following
- EI tooling (Server startup and CAPP deployment)
- Humantask Basic functionalities
- Humantask Explorer with samples
- Feature installation
[+] Stable - go ahead and release
Thanks,
On Wed, May 3, 2017 at 12:55 PM, Isuru Wijesinghe
Hi all,
Based on above feedback, I have created the branch "4.x.x" for MB 4
development work excluding the product directory.
https://github.com/wso2/carbon-business-messaging/tree/4.x.x
Thanks
On Thu, Apr 27, 2017 at 5:50 PM, Hasitha Hiranya wrote:
> +1 for a single
Tested and verified the following:
Proxy services, APIs
JMS (Message Store/Processor) with WSO2 MB
Data Mapper scenarios
CAR file deployment through management console
MSF4J service deployment
BPMN processors (Mail Task, Rest Task, User Task)
Mail Connector integration
Data Services Sample
Hi All,
Tested and verified following
Proxy services, APIs
CAR file deployment through management console
JMS (Message Store/Processor, JMS Consumerand Producer scenarios)
BPMN basic functionality
BPMN Explorer
BPMN samples
No issues found.
[x] Stable - go ahead and release
Thanks,
Isuru.
On
Hi All,
Tested the BPEL and BPMN functionality including BPMN explorer in BPS
profile.
[+] Stable - go ahead and release
Regards,
Vinod
On Tue, May 2, 2017 at 4:31 PM, Sasikala Kottegoda
wrote:
> Hi all,
>
> I have tested distributed transactions for the broker profile of
13 matches
Mail list logo