Hi,
Given that we know the registry path of the resource of which cache to be
deleted and have an instance of the registry we can manually delete the
cache with a method like removeCache in the below file. However, it's not a
clean or correct way of manipulating the registry cache.
Hi,
The global cache invalidation implementation is complete long time ago and
the documentation can be found at [1]. This has been tested in registry and
it's working well. However this is implemented to support from carbon 4.3.0
onwards.
[1]
Ack?
Paul
On 10 October 2014 09:27, Paul Fremantle p...@wso2.com wrote:
I have a simple proposal, which is that we predefine a standard offset for
each product.
e.g. AS 0, ESB 1, AM 2, GovReg 3, BAM 4, IS 5, etc...
These would be baked into the distros. This would make life a lot easier
Hi,
I'm -0 on this proposal. If we have different offsets for different
products, we will have to maintain a document to show the offsets we have
given for each product.
When doing product integrations, setting offset is not the only
configuration step. It is a simple operation and I think it's
Hi Johan,
FYI. We have documented the ports used by WSO2 products [1].
Thanks!
Best Regards,
[1] https://docs.wso2.com/display/Carbon420/Default+Ports+of+WSO2+Products
On Wed, Nov 12, 2014 at 6:27 PM, Johan Kumps johan.ku...@realdolmen.com
wrote:
Hi,
I’ve been involved in the clustered
Hi,
If we come up with this standard port offset for each product , AFAIU we
are only thinking on scope within WSO2 products. Generally In most of the
cases , there is a standard default port for most of the products which is
related with their functionality. As an example most of the message
Hi ,
A small addition to the above:
- A Chevron Workflow could have one or more layouts
- The layout details need not be stored with the Workflow instance
Thank You,
Sameera
On Wed, Nov 12, 2014 at 5:20 PM, Himasha Guruge himas...@wso2.com wrote:
Hi Chathura,
After the meeting with
Hi Himasha,
A chevron in a chevron diagram may refer to another chevron diagram or to a
process model. Therefore, we can't create an asset for a chevron until the
user has specified its type. I think we should not prompt user to enter
details like type of each chevron when modeling an abstract
On Wed, Nov 12, 2014 at 6:27 PM, Johan Kumps johan.ku...@realdolmen.com
wrote:
Hi,
I’ve been involved in the clustered installation of several WSO2 products
for one of our customers lately. Indeed the fact to have to change the port
offset is not a big deal. What we would like more is a
Came upon this thread when trying to find a solution for this exact issue
we are facing right now. LDAPs cannot have password history policies
because of this. It seems rather than using a dummy password first time, it
uses the same password. We'll have to explore why it's done this way.
On Tue,
Hi Roshan,
I like to suggest the word none instead of empty
Touched, not typed. Erroneous words are a feature, not a typo.
On Nov 12, 2014 9:35 AM, Roshan Deniyage rosh...@wso2.com wrote:
Its breaking not because of * but, code changes in M6 release. I'm going
to change the * sign because
+1 for using none instead of empty
On Thu, Nov 13, 2014 at 12:12 AM, Udara Liyanage ud...@wso2.com wrote:
Hi Roshan,
I like to suggest the word none instead of empty
Touched, not typed. Erroneous words are a feature, not a typo.
On Nov 12, 2014 9:35 AM, Roshan Deniyage rosh...@wso2.com
Hi Anuruddha,
On Tue, Nov 11, 2014 at 8:12 PM, Anuruddha Premalal anurud...@wso2.com
wrote:
Hi,
Now in appfactory developer setup, we are using three single JVM
private-paases which have separate activemqs running on the same node with
port offsets. Appfactory use stratos messaging
Hi Harsha,
On Wed, Nov 12, 2014 at 8:38 AM, Harsha Thirimanna hars...@wso2.com wrote:
As we discussed with Imesh, we have to set this jndi property to system
variable for each enviorenment before start listener to that environment.
There is hard coded of this jndi property file in topology
On Wed, Nov 12, 2014 at 8:33 PM, Afkham Azeez az...@wso2.com wrote:
On Wed, Nov 12, 2014 at 6:12 PM, Isuru Perera isu...@wso2.com wrote:
Hi,
I'm -0 on this proposal. If we have different offsets for different
products, we will have to maintain a document to show the offsets we have
given
Hi Chathura,
Noted, will continue as we planned.
Thanks Regards,
Himasha Guruge
*Software Engineer*
WS*O2* *Inc.*
Mobile: +94 777459299
himas...@wso2.com
On Wed, Nov 12, 2014 at 8:24 PM, Chathura Ekanayake chath...@wso2.com
wrote:
Hi Himasha,
A chevron in a chevron diagram may refer to
Hi All,
Myself with Tharindu(tharin...@wso2.com) is going to develop $subject as
described below.
Work flow
-
Step 01 : User creates the .dbs file with the use of DSS
-
Step 02 : There will be an additional option to expose/publish the API
for the services exposed by the DSS
Adding Tharindu
On Thu, Nov 13, 2014 at 9:20 AM, Madusanka Premaratne madusan...@wso2.com
wrote:
Hi All,
Myself with Tharindu(tharin...@wso2.com) is going to develop $subject as
described below.
Work flow
-
Step 01 : User creates the .dbs file with the use of DSS
-
Step
any reason for suggestions?
Roshan Deniyage
Associate Technical Lead
WSO2, Inc: http://wso2.com
Mobile: +94 777636406
Twitter: *https://twitter.com/roshku https://twitter.com/roshku*
LinkedIn : https://www.linkedin.com/in/roshandeniyage
On Thu, Nov 13, 2014 at 12:36 AM, Mahesh
Hi,
Technically there is no difference. However having empty in a
configuration files does not look nice to me :-) .
On Thu, Nov 13, 2014 at 9:49 AM, Roshan Deniyage rosh...@wso2.com wrote:
any reason for suggestions?
Roshan Deniyage
Associate Technical Lead
WSO2, Inc: http://wso2.com
We need to pick offset values wisely which requires less number of changes
(in configurations)
for example: if we change Port Offset of APIM we require changes in 3 files
(carbon.xml, synapse token api etc).
On Thu, Nov 13, 2014 at 5:10 AM, Thilina Piyasundara thili...@wso2.com
wrote:
On
21 matches
Mail list logo
