Hi,
We have been using PF for JSON based RESTful integration and there seems to
have several areas to improve.
- JSON-JSON - This works fine with JSON Path[1].. but we have to use JSON
streaming builders/formatters.
- XML- JSON - This is not supported with JSON streaming builder, but have
to
One of the problems we encounter when transforming between XML and JSON is
that there's no one-to-one mapping between the two formats. This leads to
lossy conversion and an inability to format messages exactly as required.
In the java world this tends to be handled by using data bindings - where
Thanks all.
Yes, a text field in the Publisher GUI allowing a user to enter the
URI-template would satisfy our requirement. Our use case is that we
have client developers with access only to the Publisher application who
need to be able to register APIs with uri-templates in them. Please
Hi all,
I have added the authorization for goose.js and below is an example of how
this works -
In the router creation, we have to add the user's roles to the router
object. If we are cacheing the router outside, we'll have to refresh the
router based on login event.
*var router = new
*WSO2 Enterprise Store 1.0.0 ALPHA-3 Released !*
This is the ALPHA-3 release of WSO2 Enterprise Store, which will create a
marketplace for your enterprise assets. You can download the Alpha-3 at
[1]. This release specifically contains following tasks, improvements and
bug fixes towards 1.0.0 GA.
This is more a conceptual question than anything else. One feature of
interest to myself and my clients, is the ability to sell access to our
data and events. Our system generates data and events and one way we
currently recoup our costs is to license access to this to our clients and
their
Hi All,
We need to think about $subject and come up with a proper way.
Currently (pre C5) we can add deployers to the depolyment engine (which is
Axis2Deployment Engine) using the following different ways.
1. Reading from component.xml using bundle listener and adding to
axisConfig (widely
