Hi All,
This has been fixed now and will be available from Developer Studio 3.8.0
Beta.
Thanks,
Rajeevan
On Thu, Sep 10, 2015 at 4:41 PM, Rajeevan Vimalanathan
wrote:
> Thanks Kathees for the info, will do the implementation accordingly.
>
> Thanks,
> Rajeevan
>
> On Thu,
Hi Sameera,
Yes, we will discuss this with the team and will provide a meaningful name
according to the feature group. We just prepared IS for profiling and not
finalized yet. Thanks for prompting this.
*Harsha Thirimanna*
Senior Software Engineer; WSO2, Inc.; http://wso2.com
*
profile=all doesn't makes sense to me :)
Can we have proper name for this profile?
On Fri, Sep 11, 2015 at 11:51 AM, Chamila Wijayarathna
wrote:
> Hi Sameera,
>
> In IS 5.1.0 we are supporting workflow for user management operations.
> There we have added BPEL and Human Task
Thanks Hasintha for pointing this out.
@Manu, UES team, would you be able to do another release with the above fix?
On 11 September 2015 at 12:04, Hasintha Indrajee wrote:
> The issue with jaggery-extension release was referring and old pom as
> parent pom [1]. You need to
Hi Sameera,
In IS 5.1.0 we are supporting workflow for user management operations.
There we have added BPEL and Human Task components of BPS to IS.
But in default profile we don't enable those features and they are only
enabled in "profile=all".
Thanks
On Fri, Sep 11, 2015 at 11:45 AM, Sameera
The issue with jaggery-extension release was referring and old pom as
parent pom [1]. You need to update it into a new version of jaggery-parent
pom which is released with wss4j version upgrade.
[1] https://github.com/wso2/jaggery-extensions/blob/v1.4.1/pom.xml#L23
On Thu, Sep 10, 2015 at 9:10
Hi Devs,
$subject,
org.wso2.carbon.deployment
carbon-deployment
4.5.3
--
Best Regards,
Kalpa Welivitigoda
Software Engineer, WSO2 Inc. http://wso2.com
Email: kal...@wso2.com
Mobile: +94776509215
___
Dev mailing list
Dev@wso2.org
Hi Devs,
This is the second release candidate of WSO2 AS 5.3.0.
This release fixes the following issues:
https://wso2.org/jira/issues/?filter=12251
Please download, test and vote. Vote will be open for 72 hours or as needed.
*Binary distribution files:*
Hi Chamila,
What do you mean by profile=all?
On Fri, Sep 11, 2015 at 11:00 AM, Chamila Wijayarathna
wrote:
> Hi all,
>
> We start WSO2 IS using following profiles.
>
> ./wso2server.sh
> ./wso2server.sh -Dprofile=all
>
> Is it possible to check from java code, for which
Hi Nuwan,
Could you please point me to the test case location, me too is looking for
a similar sample.
On Fri, Sep 11, 2015 at 3:39 PM, Nuwan Wimalasekara wrote:
> Hi Udara,
>
> In APIM integration test, HTTP endpoint is used to call the
> RestAPI(Publisher and Store) and It
Thanks a lot Manu for your help!!
On 11 September 2015 at 21:47, Manuranga Perera wrote:
> done
>
>
> On Fri, Sep 11, 2015 at 9:37 PM, Lasantha Fernando
> wrote:
>
>> Hi Manu,
>>
>> Tested the CEP pack with the staged artifacts and the functionality is
>>
Hi Vinod,
At creation of workflows we can assign both users and roles to own the
human tasks. All so we can assign more than one user to own tasks. Above
question occurred since I was unaware of the difference between two states.
Since we can assign roles to own human tasks, I human tasks going
Thanks for your thoroughness folks !!
I'm not sure, from the description, what gets sent to the
message.processor.deactivate.sequence
- is it the message that failed or just the reply from the server or both?
cheers,
John.
John Hawkins
Director: Solutions Architecture
On Thu, Sep 10, 2015 at
Closed the staging repo as requested by Jaggery team. Please find the url -
http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-075/
On Fri, Sep 11, 2015 at 12:45 PM, Manuranga Perera wrote:
> will release with today.
>
> On Fri, Sep 11, 2015 at 12:13 PM, Lasantha
Is there anyway that we can support older ESB versions with the new
release? since we are giving many bug fixes with 3.8.0 it is better if we
can support older versions as well.
Just My opinion though..
Regards
Awanthika
Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791
On
Hi All,
This is regarding a known issue of the permission tree. When you try to
configure permissions of a Role in Management Console, we can either select
the parent and enable all the permissions under the parent or deselect the
parent and enable only few permissions under the parent. In this
only problem case is if user waiting for a fix which will be coming with
this release but that user may use older ESB version , but any way now we
have to remove this , we have to educate users via the documentations
Thanks and Regards
/Jasintha
On Fri, Sep 11, 2015 at 3:09 PM, Harshana
See, there are nothing called intermittent issue. Just wrong way of doing
stuff :)
On Fri, Sep 11, 2015 at 3:36 PM, Niranjan Karunanandham
wrote:
> Hi Shankar,
>
> I went through the log and noticed that in the ServerRestartTestCase, it
> sends a command to restart the server
will release with today.
On Fri, Sep 11, 2015 at 12:13 PM, Lasantha Fernando
wrote:
> Thanks Hasintha for pointing this out.
>
> @Manu, UES team, would you be able to do another release with the above
> fix?
>
> On 11 September 2015 at 12:04, Hasintha Indrajee
Hi,
We have observed that RMSequence mediator has been removed from ESB 4.8.1.
We also planning to remove that from ESB palette as well from Developer
Studio 3.8.0 since synapse libraries have been updated accordingly.
Here our concern is what if a user wants to develop ESB 4.8.0 stuff with
Hi Udara,
In APIM integration test, HTTP endpoint is used to call the
RestAPI(Publisher and Store) and It is working fine without any issue. This
should work
Thanks,
Nuwanw
On Fri, Sep 11, 2015 at 9:41 AM, Nuwan Dias wrote:
> They run on HTTPS only. If you send an http
Hi Rajeevan,
In that case you may recommend to use an older stable version of DevS such
as DevS 3.7.0 or 3.7.1 since that supports full feature set of ESB 4.8.0.
Thanks and Regards,
Harshana
On Friday, September 11, 2015, Rajeevan Vimalanathan
wrote:
> Hi,
>
> We have
I created a JIRA [1] to track this task.
[1] https://wso2.org/jira/browse/DOCUMENTATION-2366
Regards,
Mariangela
*Mariangela Hills*
Senior Technical Writer - WSO2, Inc. http://wso2.com
Committer and PMC member - Apache Stratos
email:mariang...@wso2.com | mobile: +94 773 500185
On Fri, Sep 11,
Hi Shankar,
I went through the log and noticed that in the ServerRestartTestCase, it
sends a command to restart the server and waits for 15 seconds and
proceeds. If in case the server takes longer time then there is an issue.
Therefore I added the check to wait for the http port to be closed (or
Even waiting for 30 seconds might not work. Can we loop with a sleep and
see whether the process is not there and proceed? Port will be closed
immediately, but the process might still run AFAIK.
On Fri, Sep 11, 2015 at 3:41 PM, Selvaratnam Uthaiyashankar <
shan...@wso2.com> wrote:
> See, there
the question in SO:
http://stackoverflow.com/questions/32531169/extract-year-from-timestamp-with-spark-sql-in-wso2-das
Jorge.
2015-09-10 12:32 GMT-04:00 Jorge :
> Hi folks,
>
> In my hive scripts if I want to extract the year from timestamp I used
> this:
>
>
When the jaggery versions are downgraded, it starts functioning properly
without any issue, albeit with the startup delay issue.
If we can get releases of jaggery and jaggery-extensions for 0.10.x and
1.3.x respectively, that uses the wss4j-1.5.11.wso2v11, then it should
resolve all the issues we
If you checked the "Events" tab in code editor when you saw that exception,
some more information could have been revealed. If you come across this
again, please check the events tab too.
On Fri, Sep 11, 2015 at 10:46 AM, Kavitha Subramaniyam
wrote:
> Hi Manjula,
>
> I was
attaching POM file used to install key manager features.
On Thu, Sep 10, 2015 at 10:56 AM, Krishantha Samaraweera <
krishan...@wso2.com> wrote:
> Hi Malintha,
>
> Shall we try to installed the feature using osgi console. You can refer
> [1]. Automation of this approach would be bit tricky as we
Hi Jorge,
You can use Spark UDFs to write a function to extract the year from epoch
time. Please refer to the blog [1] for example implementation of UDFs.
@Niranda, is there any other way to achieve the same?
[1]
http://thanu912.blogspot.com/2015/08/using-user-defined-function-udf-in.html
On
Hi Manu,
Tested the CEP pack with the staged artifacts and the functionality is
working fine. Please release the repo from staging.
Thanks,
Lasantha
On 11 September 2015 at 21:10, Manuranga Perera wrote:
> update
+1 for a button for each property. I thought we already had that.
Thanks & Regards
Danushka Fernando
Senior Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729
On Fri, Sep 11, 2015 at 9:23 PM, Amalka Subasinghe wrote:
>
> Hi,
>
> With the improvement we have
done
On Fri, Sep 11, 2015 at 9:37 PM, Lasantha Fernando
wrote:
> Hi Manu,
>
> Tested the CEP pack with the staged artifacts and the functionality is
> working fine. Please release the repo from staging.
>
> Thanks,
> Lasantha
>
> On 11 September 2015 at 21:10, Manuranga
Hi Shankar,
We wait for 5 min(by looping till 5 min) to let the server port open. if
the server failed to open the port within 5 min, We failed the test case or
skip all the tests. However 30 sec may be not enough for server to close
the port when restart, if it fail, Test case will be failed and
Hi Nuwan,
My comment is, don't assume a particular duration where it will happen. I
agree we have to have a maximum, and beyond that we have to fail the test
case. If we are doing that, then fine. Just wanted to make sure we are not
assuming if we wait for n minutes, anyway the port will be
please try 1.3.4 version with
http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-079/
On Fri, Sep 11, 2015 at 3:54 PM, Manuranga Perera wrote:
> ok will do. reverting the staging.
>
> On Fri, Sep 11, 2015 at 3:48 PM, Lasantha Fernando
> wrote:
>
>>
Will be moving throttle.core to a new component under carbon-mediation. The
new component name will be throttle-core and a new feature with the same
name will be created. Planning to do these changes on
carbon-mediation 4.4.11-SNAPSHOT and synapse 2.1.3-wso2v12-SNAPSHOT.
On Mon, Sep 7, 2015 at
Hi Chamila,
It is the correct behaviour as Hasitha mentioned.
But, Are you assigning users for the human task using roles? As I remember,
in the bpel process we created for the workflow support, you can pass users
also as the potential owners to the ht. Try passing only the user name in
the
Hi Shankar,
In the code currently we are looping to check if the port is close. If the
port does not close within 30 seconds then there should be an issue (please
correct me if am wrong). Then we wait for 15 seconds and then check if the
port is open (using the waitForPort provided by the
I will check this.
On Fri, Sep 11, 2015 at 5:18 PM, Malintha Adikari wrote:
> attaching POM file used to install key manager features.
>
> On Thu, Sep 10, 2015 at 10:56 AM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> Hi Malintha,
>>
>> Shall we try to
Yes. We have to check whether the port is closed by looping within a
defined max time (30 sec) just after *restart* is called. then we know It
is shutdown and going to restart. Then we have to wait for port to open.
Note : 30 sec is depends on the server load at that time. We can increase
the
sorry I misunderstood your comment previously.. Yes, what you have done is
correct, but my thinking is, what will happen if the port is not closed
within 30 seconds? Do we fail the test case? Same for the check on port
open. If it didn't open within 15 seconds, do we fail the test case?
On Fri,
ok will do. reverting the staging.
On Fri, Sep 11, 2015 at 3:48 PM, Lasantha Fernando
wrote:
> When the jaggery versions are downgraded, it starts functioning properly
> without any issue, albeit with the startup delay issue.
>
> If we can get releases of jaggery and
Hi,
This is regarding $subject raised in [1] and [2].
Currently the default version of an application is given the version
"trunk" (which corresponds to "master" branch of the git repo). When
checking out a version, DevStudio checks whether the user is checking out
the version "trunk" and if so,
I guess we use trunk because we started this with svn and then moved on to
git. +1 for renaming. @Manjula WDYT?
Thanks & Regards
Danushka Fernando
Senior Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729
On Fri, Sep 11, 2015 at 5:00 PM, Kavith Lokuhewage wrote:
Hi Amila,
You can find [1] which already has the throttle policy editor related
packages and named as mediation-throttle. You can move the throttle-core
packages to this component.
[1]
https://github.com/wso2/carbon-mediation/tree/master/components/mediation-throttle
On Fri, Sep 11, 2015 at
Hi All
This is to update the current status of CEP400 Release
Current pack used for testing is the pack we took on :9th September 2015
*Areas Covered up to now*
1.Event Receivers and Publishes
Email
File-tail
HTTP
JMS
MQTT
RDBMS
SOAP(receiver only)
WSO2Event (Thrift/Binary)(receiver only)
+1.
On Fri, Sep 11, 2015 at 5:20 PM, Amila De Silva wrote:
> Will be moving throttle.core to a new component under carbon-mediation.
> The new component name will be throttle-core and a new feature with the
> same name will be created. Planning to do these changes on
>
please try with
http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-083/
On Fri, Sep 11, 2015 at 4:59 PM, Manuranga Perera wrote:
> please try 1.3.4 version with
> http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-079/
>
>
> On Fri, Sep 11, 2015 at 3:54 PM,
Hi Chanaka,
Since throttle core can be used on its own, thought of creating a separate
feature out of that - so a new place to put throttle component. If we put
it under mediation-throttle, that would imply two components have to be
used together, isn't it?
On Fri, Sep 11, 2015 at 6:45 PM,
update http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-084/
please try and let me know
On Fri, Sep 11, 2015 at 8:00 PM, Manuranga Perera wrote:
> please try with
> http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-083/
>
> On Fri, Sep 11, 2015 at 4:59
Hi,
With the improvement we have made in 2.2.0-M3 release to the Runtime Config
pages [1], we have introduced a new button called "Show More Detail" to
show all details of resources only when the user click on it. otherwise we
display name and description only.
Let's say we have 10 properties
Hi ES Team,
I tried to create an Asset Type with following model elements in RXT using
ES v2.3.6;
>
> Step Description
>
>
> Step Description
>
>
When creating an asset using "ES Publisher"; All model elements are
rendered correctly as per the image.
[image:
Hi Nirmal,
Please find the document at [1] and I have already created the PR.
[1] -
https://docs.google.com/document/d/172MavBl2TuBNHVoyEPuRIPwmSW5lBljHFSNxrq4gclQ/edit?usp=sharing
Danula
On Sat, Sep 5, 2015 at 12:25 PM, Danula Eranjith
wrote:
> Sure. Ill send the
54 matches
Mail list logo