Hi all,
As a follow up of the previous emails by Roberto Cappa on this topic we'd like
to update you on the results of some testing
Our restful service to be mediated has two operations. One is somenthing like
GET http://host:port/people/{id} to get the XML representing a person and the
other
Sanjiva Weerawarana wrote:
I don't understand the client repo bit .. we've agreed to package up
WSF/Java as a client stack. Is that not sufficient?
Anyway we can have repository/client like we have
repository/deployment I assume?
+1, when you say deployment, client doesn't seem to fit
Isuru Suriarachchi wrote:
On Thu, Feb 18, 2010 at 9:57 AM, Sanjiva Weerawarana sanj...@wso2.com
mailto:sanj...@wso2.com wrote:
I don't understand the client repo bit ..
AFAIK, this client repo is used by the server to create the client
side Configuration context which is used to
Hi Folks,
With registry separation work shaping up we need to rethink how we are going
to handle dynamic sequences and endpoints in the ESB. Earlier users were
able to save sequences and endpoints anywhere in the registry and refer to
them using keys as shown below.
endpoint
On Thu, Feb 18, 2010 at 5:31 PM, Hiranya Jayathilaka hira...@wso2.comwrote:
Hi Folks,
With registry separation work shaping up we need to rethink how we are
going to handle dynamic sequences and endpoints in the ESB. Earlier users
were able to save sequences and endpoints anywhere in the
+1
I think we shouldn't let users store sequences, endpoints and stuff into
the local, even giving the option to store sequences, endpoints into the
config registry is not useful, because we are anyway saving stuff into
the config registry, but having this enabled for config registry has
only
When I took an svn update and did an online build, I got this error.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
Hi Senaka,
We did a version change in shindig, follow the steps and you should be fine
:)
[1] Take an up of orbit/shindig. build it online.
[2] Take an up of components/dashboard - build it
[3] Take an up of features/dashboard - build it.
Regards
/Nuwan
On Thu, Feb 18, 2010 at 9:15 PM, Senaka
On Thu, Feb 18, 2010 at 8:35 PM, Ruwan Linton ru...@wso2.com wrote:
+1
I think we shouldn't let users store sequences, endpoints and stuff into
the local,
It seems most are in favor of not allowing the user to store stuff into the
local repo. In that case we can leave it out of the picture.
I have tried registry eventing by subscribing to a collection for create
child event and added a child to that collection;
Following log was there on the console; Please have a look.
[Note: I didn't configured the mail transport properly, even though I
subscribed with the email address, and
On Thu, Feb 18, 2010 at 10:03 PM, Ruwan Linton ru...@wso2.com wrote:
I have tried registry eventing by subscribing to a collection for create
child event and added a child to that collection;
Following log was there on the console; Please have a look.
Will have a look into this. Need to
Hi,
There seems to be a build error. The issue is one of the artifacts haven't
been uploaded to our wso2 repository.
[1] http://dist.wso2.org/maven2/org/apache/shindig/shindig-common/r910768/
@Chamith can you please upload the common jar
Regards
/Nuwan
On Thu, Feb 18, 2010 at 9:20 PM, Nuwan
Hi Nuwan,
Is this shindig version (r910768) a custom built one by us??
If so we need to have the source of that some where, ideally under
trunk/carbon/dependencies/shindig
Thanks,
Ruwan
Nuwan Bandara wrote:
Hi,
There seems to be a build error. The issue is one of the artifacts
haven't
On Thu, Feb 18, 2010 at 10:17 PM, Senaka Fernando sen...@wso2.com wrote:
Will have a look into this. Need to have a look into how logs are written
in registry.
Logs shouldn't be written in the registry! Why are we doing that?
Sanjiva.
--
Sanjiva Weerawarana, Ph.D.
Founder, Chairman CEO;
On Fri, Feb 19, 2010 at 2:06 AM, Ruwan Linton ru...@wso2.com wrote:
Hi Nuwan,
Is this shindig version (r910768) a custom built one by us??
If so we need to have the source of that some where, ideally under
trunk/carbon/dependencies/shindig
+1 It would be easier to track our changes, if
Hi Nuwan,
This is due to having checksumPolicy fail in the orbit parent pom. If are
just copying jar files to the repo, change the checksum policy of
orbit-parent pom file to checksumPolicy ignore like
this checksumPolicyignore/checksumPolicy
Lahiru
On Fri, Feb 19, 2010 at 9:23 AM, Nuwan
Hi,
Just to clarify, What is the best way to do this ?, since we used the latest
revision (as of yesterday) and made a wso2 version out of it, would it be
better to do a mvn deploy, or keep it as it is and ignore the checksum
policy check.
Regards
/Nuwan
On Fri, Feb 19, 2010 at 10:04 AM, Lahiru
Hi,
There are some blocking issues which prevent us from doing a full test on
M2. E.g:- App server deployment issue, Jaxws, Spring, keystore upload issue,
oracle script issue etc (please look at carbon JIRA open highest priority
issues list for more information)... AFAIK, some of these blocking
18 matches
Mail list logo
