Re: [Dev] Setting soap format to address endpoint in API Manager 2.1.0
On 25 September 2017 at 11:27, Shenavi de Mel <shen...@wso2.com> wrote: > Hi APIM Team, > > In APIM 2.0.0 there was an option where we were able to set the SOAP > format to the address endpoint from the advanced endpoint configuration. > However in APIM 2.1.0 I am unable to find the configuration. > > Is there anyway to configure that from the UI instead of having to > manually add it to the API synapse file? Or add a property to achieve it > through a custom sequence? I was not able to find a way to do this. Please > point me in the path this could be achieved. > If you set the correct messageType property via a custom inSequence, it should also do the same thing. If the SOAP format is 1.1, set it as text/xml and if it is 1.2, set as application/soap+xml. Also for SOAP 1.1, you have to send the SOAPAction header as well. Thanks, Lakmali > > Is there a specific reason that option was removed? > > I am trying to expose a SOAP based API as a REST API where the soap body > will be constructed within the sequence using a payload factory mediator > similar to the post I have written [1]. Without setting the soap format to > the address endpoint seems my payload is dropped from the request as I > observed per the wire logs. When i manually add it to the api synapse file > it works as expected. > > Your help on this would be much appreciated. > > [1] http://shenavid.blogspot.com/2017/03/in-this-post-i-will > -be-explaining-how.html > > Thanks and Regards, > Shenavi > > *Shenavi de Mel* > Senior Software Engineer > WSO2 Inc: http://wso2.com > email: shen...@wso2.com > mobile: 0711644470 > > -- Lakmali Baminiwatta Associate Technical Lead WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM] Read only source view not allowed to edit single API
Hi Lakshman, It is not recommended to update the API source code via source view UI or file system since it will get overridden by publisher updates. We have to update the docs by removing that part. The recommended way is to add it via the velocity template. If there is a requirement to add it only to a specific API, what we can do is write some logic in the velocity template. Thanks, Lakmali On 16 April 2017 at 21:51, Shazni Nazeer <sha...@wso2.com> wrote: > May be this is bug. > > In addition despite you add the handler via source view or through file > system in API level, and then if you happen to update the API in publisher, > all custom handler (or any property) that you add get vanished as the API > gets updated, the new synapse file overwrite it. So you'll have to add it > once again. So wouldn't it be good if the handler is added to > velocity-tempate.xml file if the handler is applicable to all the API? But > if it's not the case, I'm npt sure how to handle it. is there a way to > handle it it easily without always have to re-edit the API synapse file? > > On Sat, Apr 15, 2017 at 8:17 PM, Lakshman Udayakantha <lakshm...@wso2.com> > wrote: > >> Hi Folks, >> >> I was trying to add a custom handler to a single API in API Manager. >> According to [1], we can edit the source view of API and add customer >> handler in handler section. Anyway, I can't do that in APIM 2.0.0 because >> source view is read-only. This can be done in earlier versions like 1.10.0. >> Any way we can edit API file from the file system and engage the handler. >> What is the reason for making ESB source view read only? If it should be >> read only then we have to update the documentation and point a way to add >> handlers for single API as well. >> >> [1] https://docs.wso2.com/display/AM200/Writing+Custom+Handlers >> >> -- >> Lakshman Udayakantha >> WSO2 Inc. www.wso2.com >> lean.enterprise.middleware >> Mobile: *0717429601* >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Shazni Nazeer > > Mob : +94 37331 > LinkedIn : http://lk.linkedin.com/in/shazninazeer > Blog : http://shazninazeer.blogspot.com > > <http://wso2.com/signature> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Lakmali Baminiwatta Associate Technical Lead WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC4
Tested below scenarios for ST and tenants. 1. JWT token 2. Authorization code grant type 3. Implicit grant type 4. Password grant type 5. Scopes 6. SaaS Apps 7. API Walkthrough [+] Stable - Go ahead and release On 1 February 2017 at 07:07, Isuru Haththotuwa <isu...@wso2.com> wrote: > Tested the following: > > 1. Basic API creation, updating, subscription and invocation flows > 2. Workflows for application creation and API subscription > > [+] Stable - go ahead and release > > On Mon, Jan 30, 2017 at 10:28 PM, Malintha Amarasinghe <malint...@wso2.com > > wrote: > >> Hi All, >> >> This is the 4th Release Candidate of WSO2 API Manager 2.1.0 >> >> Please download, test the product and vote. The vote will be open for 72 >> hours or as needed. >> >> Source and distribution >> >> Run-time : https://github.com/wso2/product-apim/releases/download/v2. >> 1.0-rc4/wso2am-2.1.0-RC4.zip >> Analytics : https://github.com/wso2/anal >> ytics-apim/releases/download/v2.1.0-rc3/wso2am-analytics-2.1.0-RC3.zip >> Tooling : https://github.com/wso2/devstudio-tooling-apim/releases/ta >> g/v2.1.0-rc2 >> >> >> This release fixes the following issues: >> Runtime : https://wso2.org/jira/issues/?filter=13623 >> Analytics : https://wso2.org/jira/issues/?filter=13624 >> Tooling : https://wso2.org/jira/browse/DEVTOOLAPI-1 >> >> >> Please vote as follows. >> [+] Stable - go ahead and release >> [-] Broken - do not release (explain why) >> >> Thanks, >> - WSO2 API Manager Team - >> >> -- >> Malintha Amarasinghe >> Software Engineer >> *WSO2, Inc. - lean | enterprise | middleware* >> http://wso2.com/ >> >> Mobile : +94 712383306 <+94%2071%20238%203306> >> >> ___ >> Architecture mailing list >> architect...@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Thanks and Regards, > > Isuru H. > +94 716 358 048 <+94%2071%20635%208048>* <http://wso2.com/>* > > > > ___ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Lakmali Baminiwatta Associate Technical Lead WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM] Where I can find the source code for Admin Dashboard in API Manager
Hi Sumedha, Find the source location of APIM 2.0.0 admin app from [1] [1] https://github.com/wso2/carbon-apimgt/tree/v6.0.4/features/apimgt/org.wso2.carbon.apimgt.store.feature/src/main/resources/admin Thanks, Lakmali On 19 September 2016 at 18:43, Sumedha Kodithuwakku <sumed...@wso2.com> wrote: > Hi Devs, > > $subject.? In product-apim repo there is a jaggery app called > admin-dashboard-web [1], but it is different from the app found in the APIM > 2.0.0 released pack. > > Appriciate if you can share the location of the source code of the admin > dashboard. > > [1] https://github.com/wso2/product-apim/tree/master/ > modules/jaggery-apps/admin-dashboard-web/ > > Thanks > SumedhaS > > -- > *Sumedha Kodithuwakku* > Senior Software Engineer > WSO2 Inc. : http://wso2.com > lean . enterprise . middleware > > Mobile: +94 71 808 1124 > Blog: http://sumedhask.blogspot.com/ > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Lakmali Baminiwatta Associate Technical Lead WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM] Changing Default Tier Limits and Names
I think when migrating, we can't change the names/limits of exiting tiers since it will be a problem to existing subscriptions. So IMO, instead of renaming tiers, we should add these new resource level and app level tiers while keeping the old ones as well. Thanks, Lakmali On 26 May 2016 at 10:23, Nuwan Dias <nuw...@wso2.com> wrote: > Changing the names of the Resource Tiers and User Quota will be a problem > for migrating users :(. > > If these tier names are recorded in the DB only, we can simply write an > sql script that replaces the old names with the new ones. But if they are > recorded in the rxt/swagger, we'll have more problems. > > Thanks, > NuwanD. > > On Wed, May 25, 2016 at 2:51 PM, Harsha Kumara <hars...@wso2.com> wrote: > >> Hi All, >> >> Currently we are using very small number for our default tier values. We >> are going to change them to more meaningful counts. Here are the current >> limits. Also with the change of quota calculation and undesirability we >> think of change the tier names as well. >> >> Subscription Level Tiers >> >>- Gold - 20 req/min >>- Silver - 5 req/min >>- Bronze - 1 req/min >> >> >> >> Resource Level Tiers >> >>- Ultimate - 20 req/min >>- Plus - 5 req/min >>- Basic -1 req/min >> >> >> Application Level Tiers >> >>- Large - 20 req/min >>- Medium - 5 req/min >>- Small -1 req/min >> >> >> Unauthenticated Tier - 60 req/min >> >> *Proposed Limits* >> >> Subscription Level Tiers >> >>- Gold - 5000 req/min >>- Silver - 2000 req/min >>- Bronze - 1000 req/min >> >> Resource Level Tiers >> >>- 50KPerMin - 5 req/min >>- 20KPerMin - 2 req/min >>- 10KPerMin - 1 req/min >> >> Application Level Tiers -> Per User Quota >> >>- 50PerMin - 50 req/min >>- 20PerMin - 20 req/min >>- 10PerMin - 10 req/min >> >> Unauthenticated Tier - 500 req/min >> >> Thanks, >> Harsha >> >> -- >> Harsha Kumara >> Software Engineer, WSO2 Inc. >> Mobile: +94775505618 >> Blog:harshcreationz.blogspot.com >> > > > > -- > Nuwan Dias > > Technical Lead - WSO2, Inc. http://wso2.com > email : nuw...@wso2.com > Phone : +94 777 775 729 > -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV][IS] Getting an error when try to rtriw a Oauth token from IS server.
This can happen if you reuse the same refresh token more than once [1].
Please check whether you are using the latest refresh token returned or
reusing a old one.
Thanks,
Lakmali
On 11 March 2016 at 14:59, Ishara Cooray <isha...@wso2.com> wrote:
> Thanks Lakmali. It works!
>
> It works for the password grant type as you have pointed out.
> But for refresh_token grant type i get Provided Authorization Grant is
> invalid error.
>
> curl -k -d
> "grant_type=refresh_token_token=87c4145a25f2e72d6d51edce3362f382=PRODUCTION"
> -H "Authorization: Basic
> bTlKZ2dkaXhGOGs3Y09jS1lLcW5ZQU16Q2lBYTphS19meWRraVlmS3k3VXlicEZkMU53eF81WkFh"
> -H "Content-Type: application/x-www-form-urlencoded"
> https://api.cloudstaging.wso2.com:8243/token
> {"error":"invalid_grant","error_description":"Provided Authorization Grant
> is invalid"}
>
> is there something to change here?
>
>
>
> Ishara Cooray
> Senior Software Engineer
> Mobile : +9477 262 9512
> WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> On Fri, Mar 11, 2016 at 2:30 PM, Lakmali Baminiwatta <lakm...@wso2.com>
> wrote:
>
>> Hi Ishara,
>>
>> On 11 March 2016 at 14:27, Ishara Cooray <isha...@wso2.com> wrote:
>>
>>> Hi Malithi/Pushpalanka,
>>>
>>> I tried renewing access token by invoking TokenAPi. Below is my CURL.
>>>
>>> curl -d
>>> "grant_type=refresh_token_token=87c4145a25f2e72d6d51edce3362f382=PRODUCTION"
>>> -H "Authorization:Basic
>>> bTlKZ2dkaXhGOGs3Y09jS1lLcW5ZQU16Q2lBYTphS19meWRraVlmS3k3VXlicEZkMU53eF81WkFh,
>>> Content-Type: application/x-www-form-urlencoded"
>>> https://api.cloudstaging.wso2.com:8243/token -v
>>>
>>
>> Headers should be sent separately as given in [1]
>>
>> [1] https://wso2.org/jira/browse/APIMANAGER-4452
>>
>> Thanks,
>> Lakmali
>>
>>> I get Authentication failed error from the above command and Error Error
>>> decoding authorization header. Space delimited " "
>>> format violated. was observed in the keymanager console where we have APIM
>>> 1.10.0
>>> {"error":"invalid_client","error_description":"Client Authentication
>>> failed."}
>>>
>>> Followed the doc [1]. What could have went wrong?
>>>
>>> If i use the curl --user Client_Id:Client_Secret as pushpalanka
>>> suggested i get
>>> {"error":"invalid_grant","error_description":"Provided Authorization
>>> Grant is invalid"}
>>>
>>>
>>> Console Log:
>>>
>>> ERROR
>>> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>>> Error while extracting credentials from authorization header
>>> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint}
>>> org.wso2.carbon.identity.oauth.common.exception.OAuthClientException:
>>> Error decoding authorization header. Space delimited "
>>> " format violated.
>>> at
>>> org.wso2.carbon.identity.oauth.endpoint.util.EndpointUtil.extractCredentialsFromAuthzHeader(EndpointUtil.java:152)
>>> at
>>> org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.issueAccessToken(OAuth2TokenEndpoint.java:82)
>>> at sun.reflect.GeneratedMethodAccessor185.invoke(Unknown Source)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>> at
>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:188)
>>> at
>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:104)
>>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:204)
>>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:101)
>>> at
>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
>>> at
>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:94)
>>> at
>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
>>> at
>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>> at
>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:249
Re: [Dev] [DEV][IS] Getting an error when try to rtriw a Oauth token from IS server.
>>>>>> not >>>>>>> accept liability for any errors or omissions. >>>>>>> >>>>>>> On Wed, Oct 7, 2015 at 5:47 PM, Pushpalanka Jayawardhana < >>>>>>> la...@wso2.com> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> Optionally, can you try with below command format and check, >>>>>>>> >>>>>>>> curl --user Client_Id:Client_Secret -k -d >>>>>>>> "grant_type=password=admin=admin" -H >>>>>>>> "Content-Type:application/x-www-form-urlencoded" >>>>>>>> https://localhost:9443/oauth2/token >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Pushpalanka. >>>>>>>> -- >>>>>>>> Pushpalanka Jayawardhana, B.Sc.Eng.(Hons). >>>>>>>> Senior Software Engineer, WSO2 Lanka (pvt) Ltd; wso2.com/ >>>>>>>> Mobile: +94779716248 >>>>>>>> Blog: pushpalankajaya.blogspot.com/ | LinkedIn: >>>>>>>> lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Oct 7, 2015 at 5:40 PM, Sachith Punchihewa < >>>>>>>> sachi...@wso2.com> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> I am currently using a locally build of IS Server from the latest >>>>>>>>> code.When i try to get a OAuth Access token via a curl execution i am >>>>>>>>> getting an error. >>>>>>>>> >>>>>>>>> Curl Format used : >>>>>>>>> >>>>>>>>> *curl-k-d*** >>>>>>>>>> *"grant_type=password=userNamepasswork&=**passWord* >>>>>>>>>> *=carbon.super"-H*** >>>>>>>>>> *"Authorization:BasicBase 64 encoded >>>>>>>>>> clientID:clientSecret,Content-Type:*** >>>>>>>>>> *application/x-www-form-urlencoded"https://localhost:9443/oauth2/token >>>>>>>>>> <https://localhost:9443/oauth2/token>* >>>>>>>>> >>>>>>>>> >>>>>>>>> Actual command : >>>>>>>>> >>>>>>>>> curl -k -d >>>>>>>>>> "grant_type=password=x=x=carbon.super" >>>>>>>>>> -H "Authorization: Basic xx, >>>>>>>>>> Content-Type: application/x-www-form-urlencoded" >>>>>>>>>> https://localhost:9443/oauth2/token >>>>>>>>> >>>>>>>>> >>>>>>>>> Error : >>>>>>>>> >>>>>>>>> "Error decoding authorization header. Space delimited >>>>>>>>>> \" \" format violated." >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Is there is a issue with the curl command i am using here ? >>>>>>>>> >>>>>>>>> Thanks and Regards. >>>>>>>>> Kamidu Sachith Punchihewa >>>>>>>>> *Software Engineer* >>>>>>>>> WSO2, Inc. >>>>>>>>> lean . enterprise . middleware >>>>>>>>> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194> >>>>>>>>> >>>>>>>>> >>>>>>>>> Disclaimer: This communication may contain privileged or other >>>>>>>>> confidential information and is intended exclusively for the >>>>>>>>> addressee/s. >>>>>>>>> If you are not the intended recipient/s, or believe that you may have >>>>>>>>> received this communication in error, please reply to the sender >>>>>>>>> indicating >>>>>>>>> that fact and delete the copy you received and in addition, you >>>>>>>>> should not >>>>>>>>> print, copy, retransmit, disseminate, or otherwise use the information >>>>>>>>> contained in this communication. Internet communications cannot be >>>>>>>>> guaranteed to be timely, secure, error or virus-free. The sender does >>>>>>>>> not >>>>>>>>> accept liability for any errors or omissions. >>>>>>>>> >>>>>>>>> ___ >>>>>>>>> Dev mailing list >>>>>>>>> Dev@wso2.org >>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> ___ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> *Malithi Edirisinghe* >>>>>> Senior Software Engineer >>>>>> WSO2 Inc. >>>>>> >>>>>> Mobile : +94 (0) 718176807 >>>>>> malit...@wso2.com >>>>>> >>>>> >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Hasintha Indrajee >>>> Software Engineer >>>> WSO2, Inc. >>>> Mobile:+94 771892453 >>>> >>>> >>> >>> >>> -- >>> >>> *Malithi Edirisinghe* >>> Senior Software Engineer >>> WSO2 Inc. >>> >>> Mobile : +94 (0) 718176807 >>> malit...@wso2.com >>> >> >> >> >> -- >> Hasintha Indrajee >> Software Engineer >> WSO2, Inc. >> Mobile:+94 771892453 >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] APIM snapse file system migration
Hi all, In our migration guide, currently what we instruct is to copy & replace repository/deployment/server/synapse-config/default directory and repository/tenants from previous APIM version to new APIM version. Here we mention to skip replacing _TokenAPI_.xml, _RevokeAPI_.xml and _AuthorizeAPI_.xml files by which latest files of those will be remained. But with this approach, it will replace other system sequences with old ones (ex: _auth_failure_handler_.xml, _cors_request_handler_.xml, main.xml, fault.xml, etc). So some of the fixes went to those will be missed out. We have two ways to include those changes to the new version. 1. Include the missing changes through migration client. 2. Get the latest sequences from the new version pack and replace corresponded sequences of each tenant through migration client. Some of the changes done to these sequences are minor changes like adding a drop mediator after send, changing a regex value, removing a property etc. Since some of the users may have already done own customizations to these sequences, trying to add changes to existing ones may lead to complications. So I think it would be better to ask the users to add their changes (if there are any) to default sequences in the pack(repository/resources/apim-synapse-config) prior running the migration client and then through the client we can replace existing ones. WDYT? Thanks, Lakmali -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] APIM snapse file system migration
If we don't involve migration client to handle this, AFAIU we have below approaches. 1. If they don't have customizations: - Option 1: Copy everything from old synapse config to new synapse config. Later replace default sequences, apis of ST and tenants from the latest resources. - Option 2: Provide an instructions to avoid copying these sequences from old pack to new pack, which will remain the latest sequences. Note that have ~10 sequences. This needs to be taken care for each tenant as well. 2. If there are customizations: Apply the customizations to default latest sequences and replace in ST and tenant spaces. Thanks, Lakmali On 13 January 2016 at 18:08, Lakmali Baminiwatta <lakm...@wso2.com> wrote: > According to the current instructions, latest sequences get replaced by > the old sequences. So what I am suggesting is that we can assume that it's > the responsibility of the person who does the migration to add the > customizations to latest default sequences which reside in > repository/resources/apim-synapse-config and then migration client will > blindly replace old sequences with those. > > On 13 January 2016 at 17:56, Nuwan Dias <nuw...@wso2.com> wrote: > >> >> >> On Wed, Jan 13, 2016 at 5:51 PM, Uvindra Dias Jayasinha <uvin...@wso2.com >> > wrote: >> >>> I think the only way is to complicate the migration instructions, >>> >>> If user has customized any sequences they need to copy them over >>> manually to latest pack and we will use those.(Discalimer to user: You >>> maybe missing out on the latest changes shipped with the default sequences >>> in the latest pack) >>> >>> Migration client doesn't need to do anything then, its not in a position >>> to make a proper decision anyway. >>> >>> But its pretty clear this is a hole in our extensibility. We dont >>> provide official extension points to make changes in the areas that these >>> specific sequences address, forcing uses to change the default sequences >>> that are shipped which makes upgrading a pain. We should address this in a >>> future release >>> >> >> The sole purpose of these sequences are for extensibility. Ex: To change >> the message type of a auth failure error. So its understandable that people >> edit them. >> >>> >>> On 13 January 2016 at 05:23, Nuwan Dias <nuw...@wso2.com> wrote: >>> >>>> >>>> >>>> On Wed, Jan 13, 2016 at 3:30 PM, Lakmali Baminiwatta <lakm...@wso2.com> >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> In our migration guide, currently what we instruct is to copy & >>>>> replace repository/deployment/server/synapse-config/default directory and >>>>> repository/tenants from previous APIM version to new APIM version. Here we >>>>> mention to skip replacing _TokenAPI_.xml, _RevokeAPI_.xml and >>>>> _AuthorizeAPI_.xml files by which latest files of those will be remained. >>>>> >>>>> But with this approach, it will replace other system sequences with >>>>> old ones (ex: _auth_failure_handler_.xml, _cors_request_handler_.xml, >>>>> main.xml, fault.xml, etc). So some of the fixes went to those will be >>>>> missed out. We have two ways to include those changes to the new version. >>>>> >>>>> 1. Include the missing changes through migration client. >>>>> 2. Get the latest sequences from the new version pack and replace >>>>> corresponded sequences of each tenant through migration client. >>>>> >>>>> Some of the changes done to these sequences are minor changes like >>>>> adding a drop mediator after send, changing a regex value, removing a >>>>> property etc. Since some of the users may have already done own >>>>> customizations to these sequences, trying to add changes to existing ones >>>>> may lead to complications. >>>>> So I think it would be better to ask the users to add their changes >>>>> (if there are any) to default sequences in the >>>>> pack(repository/resources/apim-synapse-config) prior running the migration >>>>> client and then through the client we can replace existing ones. WDYT? >>>>> >>>> >>>> This part is tricky. Since we do not know the amount nor nature of >>>> customisations they may have done, can we guarantee the migration client >>>> will do its job properly since it doesn'
Re: [Dev] APIM snapse file system migration
According to the current instructions, latest sequences get replaced by the old sequences. So what I am suggesting is that we can assume that it's the responsibility of the person who does the migration to add the customizations to latest default sequences which reside in repository/resources/apim-synapse-config and then migration client will blindly replace old sequences with those. On 13 January 2016 at 17:56, Nuwan Dias <nuw...@wso2.com> wrote: > > > On Wed, Jan 13, 2016 at 5:51 PM, Uvindra Dias Jayasinha <uvin...@wso2.com> > wrote: > >> I think the only way is to complicate the migration instructions, >> >> If user has customized any sequences they need to copy them over manually >> to latest pack and we will use those.(Discalimer to user: You maybe missing >> out on the latest changes shipped with the default sequences in the latest >> pack) >> >> Migration client doesn't need to do anything then, its not in a position >> to make a proper decision anyway. >> >> But its pretty clear this is a hole in our extensibility. We dont provide >> official extension points to make changes in the areas that these specific >> sequences address, forcing uses to change the default sequences that are >> shipped which makes upgrading a pain. We should address this in a future >> release >> > > The sole purpose of these sequences are for extensibility. Ex: To change > the message type of a auth failure error. So its understandable that people > edit them. > >> >> On 13 January 2016 at 05:23, Nuwan Dias <nuw...@wso2.com> wrote: >> >>> >>> >>> On Wed, Jan 13, 2016 at 3:30 PM, Lakmali Baminiwatta <lakm...@wso2.com> >>> wrote: >>> >>>> Hi all, >>>> >>>> In our migration guide, currently what we instruct is to copy & replace >>>> repository/deployment/server/synapse-config/default directory and >>>> repository/tenants from previous APIM version to new APIM version. Here we >>>> mention to skip replacing _TokenAPI_.xml, _RevokeAPI_.xml and >>>> _AuthorizeAPI_.xml files by which latest files of those will be remained. >>>> >>>> But with this approach, it will replace other system sequences with old >>>> ones (ex: _auth_failure_handler_.xml, _cors_request_handler_.xml, main.xml, >>>> fault.xml, etc). So some of the fixes went to those will be missed out. We >>>> have two ways to include those changes to the new version. >>>> >>>> 1. Include the missing changes through migration client. >>>> 2. Get the latest sequences from the new version pack and replace >>>> corresponded sequences of each tenant through migration client. >>>> >>>> Some of the changes done to these sequences are minor changes like >>>> adding a drop mediator after send, changing a regex value, removing a >>>> property etc. Since some of the users may have already done own >>>> customizations to these sequences, trying to add changes to existing ones >>>> may lead to complications. >>>> So I think it would be better to ask the users to add their changes (if >>>> there are any) to default sequences in the >>>> pack(repository/resources/apim-synapse-config) prior running the migration >>>> client and then through the client we can replace existing ones. WDYT? >>>> >>> >>> This part is tricky. Since we do not know the amount nor nature of >>> customisations they may have done, can we guarantee the migration client >>> will do its job properly since it doesn't know the content/state of the >>> file before it starts to execute on it? >>> >>> >>> >>>> Thanks, >>>> Lakmali >>>> >>>> -- >>>> Lakmali Baminiwatta >>>> Senior Software Engineer >>>> WSO2, Inc.: http://wso2.com >>>> lean.enterprise.middleware >>>> mobile: +94 71 2335936 >>>> blog : lakmali.com >>>> >>>> >>> >>> >>> -- >>> Nuwan Dias >>> >>> Technical Lead - WSO2, Inc. http://wso2.com >>> email : nuw...@wso2.com >>> Phone : +94 777 775 729 >>> >> >> >> >> -- >> Regards, >> Uvindra >> >> Mobile: 33962 >> > > > > -- > Nuwan Dias > > Technical Lead - WSO2, Inc. http://wso2.com > email : nuw...@wso2.com > Phone : +94 777 775 729 > -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] APIM snapse file system migration
On 13 January 2016 at 18:34, Lakmali Baminiwatta <lakm...@wso2.com> wrote: > If we don't involve migration client to handle this, AFAIU we have below > approaches. > > 1. If they don't have customizations: > >- Option 1: Copy everything from old synapse config to new synapse >config. Later replace default sequences, apis of ST and tenants from the >latest resources. >- Option 2: Provide an instructions to avoid copying these sequences >from old pack to new pack, which will remain the latest sequences. Note >that have ~10 sequences. This needs to be taken care for each tenant as >well. > > Apparently we can't go with option 2, since in tenant space, default sequences are added only in the very first tenant load (adds if auth failure sequence is not there). So we can't just rely on that. Hence I think we should do as Option 1. 2. If there are customizations: Apply the customizations to default latest > sequences and replace in ST and tenant spaces. > > Thanks, > Lakmali > > > > On 13 January 2016 at 18:08, Lakmali Baminiwatta <lakm...@wso2.com> wrote: > >> According to the current instructions, latest sequences get replaced by >> the old sequences. So what I am suggesting is that we can assume that it's >> the responsibility of the person who does the migration to add the >> customizations to latest default sequences which reside in >> repository/resources/apim-synapse-config and then migration client will >> blindly replace old sequences with those. >> >> On 13 January 2016 at 17:56, Nuwan Dias <nuw...@wso2.com> wrote: >> >>> >>> >>> On Wed, Jan 13, 2016 at 5:51 PM, Uvindra Dias Jayasinha < >>> uvin...@wso2.com> wrote: >>> >>>> I think the only way is to complicate the migration instructions, >>>> >>>> If user has customized any sequences they need to copy them over >>>> manually to latest pack and we will use those.(Discalimer to user: You >>>> maybe missing out on the latest changes shipped with the default sequences >>>> in the latest pack) >>>> >>>> Migration client doesn't need to do anything then, its not in a >>>> position to make a proper decision anyway. >>>> >>>> But its pretty clear this is a hole in our extensibility. We dont >>>> provide official extension points to make changes in the areas that these >>>> specific sequences address, forcing uses to change the default sequences >>>> that are shipped which makes upgrading a pain. We should address this in a >>>> future release >>>> >>> >>> The sole purpose of these sequences are for extensibility. Ex: To change >>> the message type of a auth failure error. So its understandable that people >>> edit them. >>> >>>> >>>> On 13 January 2016 at 05:23, Nuwan Dias <nuw...@wso2.com> wrote: >>>> >>>>> >>>>> >>>>> On Wed, Jan 13, 2016 at 3:30 PM, Lakmali Baminiwatta <lakm...@wso2.com >>>>> > wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> In our migration guide, currently what we instruct is to copy & >>>>>> replace repository/deployment/server/synapse-config/default directory and >>>>>> repository/tenants from previous APIM version to new APIM version. Here >>>>>> we >>>>>> mention to skip replacing _TokenAPI_.xml, _RevokeAPI_.xml and >>>>>> _AuthorizeAPI_.xml files by which latest files of those will be remained. >>>>>> >>>>>> But with this approach, it will replace other system sequences with >>>>>> old ones (ex: _auth_failure_handler_.xml, _cors_request_handler_.xml, >>>>>> main.xml, fault.xml, etc). So some of the fixes went to those will be >>>>>> missed out. We have two ways to include those changes to the new version. >>>>>> >>>>>> 1. Include the missing changes through migration client. >>>>>> 2. Get the latest sequences from the new version pack and replace >>>>>> corresponded sequences of each tenant through migration client. >>>>>> >>>>>> Some of the changes done to these sequences are minor changes like >>>>>> adding a drop mediator after send, changing a regex value, removing a >>>>>> property etc. Since some of the users may have already done own >>>>
Re: [Dev] [VOTE] Release WSO2 API Manager 1.10.0 RC4
n: >>>>>>>>>> https://github.com/wso2/product-apim/tree/v1.10.0-rc4 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> [ ] Stable - go ahead and release >>>>>>>>>> [ ] Broken - do not release (explain why) >>>>>>>>>> >>>>>>>>>> Thanks and Regards, >>>>>>>>>> WSO2 API Manager Team >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Regards, >>>>>>>>>> Chamila Adhikarinayake >>>>>>>>>> Software Engineer >>>>>>>>>> WSO2, Inc. >>>>>>>>>> Mobile - +94712346437 >>>>>>>>>> Email - chami...@wso2.com >>>>>>>>>> Blog - http://helpfromadhi.blogspot.com/ >>>>>>>>>> >>>>>>>>>> ___ >>>>>>>>>> Dev mailing list >>>>>>>>>> Dev@wso2.org >>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> *Bhathiya Jayasekara* >>>>>>>>> *Senior Software Engineer,* >>>>>>>>> *WSO2 inc., http://wso2.com <http://wso2.com>* >>>>>>>>> >>>>>>>>> *Phone: +94715478185 <%2B94715478185>* >>>>>>>>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj >>>>>>>>> <http://www.linkedin.com/in/bhathiyaj>* >>>>>>>>> *Twitter: https://twitter.com/bhathiyax >>>>>>>>> <https://twitter.com/bhathiyax>* >>>>>>>>> *Blog: http://movingaheadblog.blogspot.com >>>>>>>>> <http://movingaheadblog.blogspot.com/>* >>>>>>>>> >>>>>>>>> ___ >>>>>>>>> Dev mailing list >>>>>>>>> Dev@wso2.org >>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> *Tharindu Dharmarathna*Associate Software Engineer >>>>>>>> WSO2 Inc.; http://wso2.com >>>>>>>> lean.enterprise.middleware >>>>>>>> >>>>>>>> mobile: *+94779109091 <%2B94779109091>* >>>>>>>> >>>>>>>> ___ >>>>>>>> Dev mailing list >>>>>>>> Dev@wso2.org >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Harsha Kumara >>>>>>> Software Engineer, WSO2 Inc. >>>>>>> Mobile: +94775505618 >>>>>>> Blog:harshcreationz.blogspot.com >>>>>>> >>>>>>> ___ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Thanks and Regards >>>>>> *,Shani Ranasinghe* >>>>>> Senior Software Engineer >>>>>> WSO2 Inc.; http://wso2.com >>>>>> lean.enterprise.middleware >>>>>> >>>>>> mobile: +94 77 2273555 >>>>>> Blog: http://waysandmeans.blogspot.com/ >>>>>> linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Roshan Wijesena. >>>>> Senior Software Engineer-WSO2 Inc. >>>>> Mobile: *+94719154640 <%2B94719154640>* >>>>> Email: ros...@wso2.com >>>>> *WSO2, Inc. :** wso2.com <http://wso2.com/>* >>>>> lean.enterprise.middleware. >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Thanks >>>> Abimaran Kugathasan >>>> >>>> Software Engineer | WSO2 Inc >>>> Data & APIs Technologies Team >>>> Mobile : +94 773922820 >>>> >>>> <http://stackoverflow.com/users/515034> >>>> <http://lk.linkedin.com/in/abimaran> >>>> <http://www.lkabimaran.blogspot.com/> <https://github.com/abimarank> >>>> <https://twitter.com/abimaran> >>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Sam Sivayogam* >>> >>> Software Engineer >>> Mobile : +94 772 906 439 >>> Office : +94 112 145 345 >>> *WSO2, Inc. :** wso2.com <http://wso2.com/>* >>> lean.enterprise.middleware. >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Praminda Jayawardana* >> Software Engineer >> WSO2 Inc.; http://wso2.com >> Mobile : +94 (0) 716 590818 >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Rukshan Chathuranga. > Software Engineer. > WSO2, Inc. > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 API Manager 1.10.0 RC3
Tested followings - SSO in Super Tenant and Tenant mode - Documentation Indexing and Search - API Tags with API visibility [X] Stable - go ahead and release. Thanks, Lakmali On 5 January 2016 at 17:46, Tharindu Dharmarathna <tharin...@wso2.com> wrote: > Hi, > > IS As A key manager Tested in Tenant and super tenant mode success. > > [x] Stable - go ahead and release > > Thanks > Tharindu > > > > On Tue, Jan 5, 2016 at 8:32 AM, Nuwan Dias <nuw...@wso2.com> wrote: > >> These scripts are no longer maintained within the release pack. The >> migration scripts, clients, etc are hosted on the documentation page which >> explains the steps for migration as well. >> >> Thanks, >> NuwanD. >> >> On Tue, Jan 5, 2016 at 3:51 AM, Vanjikumaran Sivajothy <va...@wso2.com> >> wrote: >> >>> I do not see the migration scripts for 1.9.X -> 1.10; >>> Does it mean that there is no schema change? >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Nuwan Dias >> >> Technical Lead - WSO2, Inc. http://wso2.com >> email : nuw...@wso2.com >> Phone : +94 777 775 729 >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > > *Tharindu Dharmarathna*Associate Software Engineer > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: *+94779109091 <%2B94779109091>* > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Bug in authenticationendpoint webapp?
On 7 December 2015 at 19:06, Pubudu Priyashan <pubu...@wso2.com> wrote: > Hey Nuwan, > > Looks like the root cause for this issue [1] is, due to the internal patch > changes we tested with in Alpha2 pack while debugging the LDAP connectivity > issue. Can you please take a look and make the necessary changes? Currently > this blocks us from testing in cluster due to user not being able to > generate keys since gateway cluster is broken. > > Please let me know if you require any further information. Thanks. > As per the offline discussion had with Pubudu, this looks like due to SVN having old authentication web app. As discussed, let's clean the SVN and try with the artifacts of the latest pack's deployment directory. Thanks, Lakmali > [1] https://wso2.org/jira/browse/APIMANAGER-4358 > > Cheers, > Pubudu D.P > Senior Software Engineer - QA Team | WSO2 inc. > Mobile : +94775464547 > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] JDBC Secondary User Store Test Connection not working
Hi IS team, When testing the connection of JDBC secondary user stores, parameters are passed in wrong order. In the UI, what we see is that, properties are ordered from 1 to 4 as driver, URL, name and password. But the testConnection method retrieves them in a different order [1], causing this issue [2]. Note that we are using carbon-identity master branch. [1] https://github.com/wso2/carbon-identity/commit/ba77bb67752dcb9871f664ad0cb14c3172f74613#diff-5147bb9e190ebb5151d30d462024f629 [2] https://wso2.org/jira/browse/APIMANAGER-4336 Thanks, Lakmali -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] ${carbon.management.port} evaluates to NIO port in APIM
Hi IS Team,
The variable "${carbon.management.port}" used in identity.xml is getting
evaluated to NIO port in APIM. We can see that IdentitUtil class[1]
resolves this variable.
I think instead of using your own variable here, we can use
"mgt.transport.https.port" system variable which is already available. So
you can just use System.getProperty("mgt.transport.https.port") and
System.getProperty("mgt.transport.http.port") [2] , which will return the
servlet HTTPS and HTTP ports.
[1]
https://github.com/wso2/carbon-identity/blame/master/components/identity-core/org.wso2.carbon.identity.core/src/main/java/org/wso2/carbon/identity/core/util/IdentityUtil.java
[2]
https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.wso2.carbon.tomcat.ext/src/main/java/org/wso2/carbon/tomcat/ext/transport/ServletTransportManager.java#L34
Thanks,
Lakmali
--
Lakmali Baminiwatta
Senior Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile: +94 71 2335936
blog : lakmali.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] APIM 1.10.0 latest pack - 30-11-2015
Hi, Please find the $subject from [1]. [1] http://builder1.us1.wso2.org/~apim/AM110/30-11-2015/wso2am-1.10.0-SNAPSHOT.zip Thanks, Lakmali -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ApplicationDAOImpl trying to query UM_PERMISSION tables against the Identity DB
Hi IS team, Can we get this fixed? Thanks, Lakmali On 24 November 2015 at 16:24, Lakmali Baminiwatta <lakm...@wso2.com> wrote: > Created a Jira. > > [1] https://wso2.org/jira/browse/IDENTITY-4128 > > On 23 November 2015 at 16:35, Nuwan Dias <nuw...@wso2.com> wrote: > >> Looks like a bug to me. This would require the Identity and UM tables to >> be on a single schema, which would be wrong. >> >> Thanks, >> NuwanD. >> >> On Mon, Nov 23, 2015 at 4:28 PM, Lakmali Baminiwatta <lakm...@wso2.com> >> wrote: >> >>> Hi all, >>> >>> In APIM 1.10.0, when we try to rename an Application, below error is >>> thrown. When I checked the code, there are queries to UM_PERMISSION table >>> against the Identity DB [1]. Shouldn't we use existing UM APIs or run these >>> against the UM DB? >>> >>> Caused by: org.h2.jdbc.JdbcSQLException: Table "UM_PERMISSION" not >>> found; SQL statement: >>> SELECT UM_ID, UM_RESOURCE_ID FROM UM_PERMISSION WHERE UM_RESOURCE_ID >>> LIKE ? [42102-140] >>> at org.h2.message.DbException.getJdbcSQLException(DbException.java:327) >>> at org.h2.message.DbException.get(DbException.java:167) >>> at org.h2.message.DbException.get(DbException.java:144) >>> at org.h2.command.Parser.readTableOrView(Parser.java:4498) >>> at org.h2.command.Parser.readTableFilter(Parser.java:1011) >>> at org.h2.command.Parser.parseSelectSimpleFromPart(Parser.java:1577) >>> at org.h2.command.Parser.parseSelectSimple(Parser.java:1682) >>> at org.h2.command.Parser.parseSelectSub(Parser.java:1571) >>> at org.h2.command.Parser.parseSelectUnion(Parser.java:1416) >>> at org.h2.command.Parser.parseSelect(Parser.java:1404) >>> at org.h2.command.Parser.parsePrepared(Parser.java:392) >>> at org.h2.command.Parser.parse(Parser.java:275) >>> at org.h2.command.Parser.parse(Parser.java:247) >>> at org.h2.command.Parser.prepare(Parser.java:201) >>> at org.h2.command.Parser.prepareCommand(Parser.java:214) >>> at org.h2.engine.Session.prepareLocal(Session.java:434) >>> at org.h2.engine.Session.prepareCommand(Session.java:384) >>> at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1071) >>> at >>> org.h2.jdbc.JdbcPreparedStatement.(JdbcPreparedStatement.java:71) >>> at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:234) >>> at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source) >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >>> at java.lang.reflect.Method.invoke(Method.java:606) >>> at >>> org.apache.tomcat.jdbc.pool.ProxyConnection.invoke(ProxyConnection.java:126) >>> at >>> org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109) >>> at >>> org.wso2.carbon.ndatasource.rdbms.ConnectionRollbackOnReturnInterceptor.invoke(ConnectionRollbackOnReturnInterceptor.java:51) >>> at >>> org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109) >>> at >>> org.apache.tomcat.jdbc.pool.interceptor.AbstractCreateStatementInterceptor.invoke(AbstractCreateStatementInterceptor.java:67) >>> at >>> org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109) >>> at >>> org.apache.tomcat.jdbc.pool.interceptor.ConnectionState.invoke(ConnectionState.java:153) >>> at >>> org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109) >>> at >>> org.apache.tomcat.jdbc.pool.TrapException.invoke(TrapException.java:41) >>> at >>> org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109) >>> at >>> org.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:80) >>> at com.sun.proxy.$Proxy13.prepareStatement(Unknown Source) >>> at >>> org.wso2.carbon.identity.application.mgt.dao.impl.ApplicationDAOImpl.readApplicationPermissions(ApplicationDAOImpl.java:2752) >>> at >>> org.wso2.carbon.identity.application.mgt.dao.impl.ApplicationDAOImpl.updateBasicApplicationData(ApplicationDAOImpl.java:442) >>> at >>> org.wso2.carbon.identity.application.mgt.dao.impl.ApplicationDAOImpl.updateApplication(ApplicationDAOImpl.java:337) >>> >>> [1] >>> https://github.com/wso2/carbon-identity/blob/master/components/application-mgt/org.wso2.carbon.identity.application.mgt/src/main/java/org/wso2/carbon/identity/application/mgt/dao/impl/ApplicationDAOImpl.java >>> >>> Than
Re: [Dev] Authentication Endpoint deployment failure with Securevault
Hi Tharindu, On 26 November 2015 at 00:37, Tharindu Edirisinghe <tharin...@wso2.com> wrote: > Hi Lakmali, > > This is related to the Tenants Dropdown feature in SSO login page [1]. In > this feature, it needs to have keystore/truststore passwords and so it > provides the option for using secure vault for securely storing the > password. > > By going through the code in [2], I see some erroneous scenario when > trying to read this EndpointConfig.properties file. Because in the code we > are inside the > *org.wso2.carbon.identity.application.authentication.endpoint.util > *component but try to load the file from > *org.wso2.carbon.identity.application.authentication.endpoint* > component's resources [3] which would not work. > > In this feature, first it looks for this EndpointConfig.properties file in > /repository/conf/identity/ directory. If the file is not > present there, it will try to load from the webapp which fails according to > the code in [2]. > > So can you please create the EndpointConfig.properties file (referring > [3]) in */repository/conf/identity/ *directory and try out > the same scenario. Enable the debug logs for > org.wso2.carbon.identity.application.authentication.endpoint when you try > this out. > Actually this file is there in */repository/conf/identity/ *directory. Find the relevant log lines of loading the file and the error. TenantDataManager EndpointConfig.properties file loaded from ./repository/conf/identity/EndpointConfig.properties [2015-11-26 04:09:45,259] ERROR - SecretCallbackHandlerFactory Invalid class as SecretCallbackHandler : Class Name : org.wso2.securevault.secret.handler.SecretManagerSecretCallbackHandler [2015-11-26 04:09:45,260] ERROR - StandardContext Exception sending context initialized event to listener instance of class org.wso2.carbon.identity.application.authentication.endpoint.util.listener.AuthenticationEndpointContextListener org.wso2.securevault.SecureVaultException: Invalid class as SecretCallbackHandler : Class Name : org.wso2.securevault.secret.handler.SecretManagerSecretCallbackHandler But it seems when you try this out you will run into another exception due > to not having a property named *secretProvider *in [3]. But first you can > try this out and share the log file so I can look further into this. > > As per my understanding this will need a code fix or some property value > changes anyway. BTW are you getting this in the alpha pack. If so please > share me the detailed steps so I can reproduce and get this fixed. > In the alpha pack we didn't have the cipher tool installed. You can try this in the latest jenkins build [1]. Find the steps to reproduce the issue. - Run ciphertool.sh with -Dconfigure option (with default settings) - Start the server [1] https://wso2.org/jenkins/job/product-apim_release-1.10.x/19/org.wso2.am$wso2am/ Thanks, Lakmali > > [1] > http://tharindue.blogspot.com/2015/04/enabling-tenant-domains-dropdown-in-sso.html > > [2] > https://github.com/wso2/carbon-identity/blob/master/components/authentication-framework/org.wso2.carbon.identity.application.authentication.endpoint.util/src/main/java/org/wso2/carbon/identity/application/authentication/endpoint/util/TenantDataManager.java > > [3] > https://github.com/wso2/carbon-identity/blob/master/components/authentication-framework/org.wso2.carbon.identity.application.authentication.endpoint/src/main/resources/EndpointConfig.properties > > Thank you, > Tharindu > > On Mon, Nov 23, 2015 at 12:40 AM, Lakmali Baminiwatta <lakm...@wso2.com> > wrote: > >> Hi all, >> >> We ran cipher tool for APIM 1.10 and when starting the server, >> authentication endpoint web app deployment fails saying "Invalid class as >> SecretCallbackHandler : Class Name : >> org.wso2.securevault.secret.handler.SecretManagerSecretCallbackHandler". >> >> In the code level it is trying to resolve Endpointconfig.properties file >> [1]. Even with this issue, server startup is successful and it seems the >> problem is only with authentication endpoint web app. >> >> What is the repository of this "org.wso2.securevault.secret" package ? >> >> Find the complete stack trace below. Any clue about this issue? >> >> [1] >> https://github.com/wso2/carbon-identity/blob/master/components/authentication-framework/org.wso2.carbon.identity.application.authentication.endpoint.util/src/main/java/org/wso2/carbon/identity/application/authentication/endpoint/util/TenantDataManager.java >> >> >> [2015-11-23 11:37:37,273] ERROR - SecretCallbackHandlerFactory Invalid >> class as SecretCallbackHandler : Class Name : >> org.wso2.securevault.secret.handler.SecretManagerSecretCallbackHa
Re: [Dev] Authentication Endpoint deployment failure with Securevault
Thanks Tharindu. On 26 November 2015 at 10:18, Tharindu Edirisinghe <tharin...@wso2.com> wrote: > Hi Lakmali, > > Yes this needs some code fix and I'm working on it. > > Regards, > Tharindu > > On Wed, Nov 25, 2015 at 8:45 PM, Lakmali Baminiwatta <lakm...@wso2.com> > wrote: > >> Hi Tharindu, >> >> On 26 November 2015 at 00:37, Tharindu Edirisinghe <tharin...@wso2.com> >> wrote: >> >>> Hi Lakmali, >>> >>> This is related to the Tenants Dropdown feature in SSO login page [1]. >>> In this feature, it needs to have keystore/truststore passwords and so it >>> provides the option for using secure vault for securely storing the >>> password. >>> >>> By going through the code in [2], I see some erroneous scenario when >>> trying to read this EndpointConfig.properties file. Because in the code we >>> are inside the >>> *org.wso2.carbon.identity.application.authentication.endpoint.util >>> *component but try to load the file from >>> *org.wso2.carbon.identity.application.authentication.endpoint* >>> component's resources [3] which would not work. >>> >>> In this feature, first it looks for this EndpointConfig.properties file >>> in /repository/conf/identity/ directory. If the file is not >>> present there, it will try to load from the webapp which fails according to >>> the code in [2]. >>> >>> So can you please create the EndpointConfig.properties file (referring >>> [3]) in */repository/conf/identity/ *directory and try >>> out the same scenario. Enable the debug logs for >>> org.wso2.carbon.identity.application.authentication.endpoint when you try >>> this out. >>> >> >> Actually this file is there in >> */repository/conf/identity/ *directory. Find the relevant >> log lines of loading the file and the error. >> >> TenantDataManager EndpointConfig.properties file loaded from >> ./repository/conf/identity/EndpointConfig.properties >> [2015-11-26 04:09:45,259] ERROR - SecretCallbackHandlerFactory Invalid >> class as SecretCallbackHandler : Class Name : >> org.wso2.securevault.secret.handler.SecretManagerSecretCallbackHandler >> [2015-11-26 04:09:45,260] ERROR - StandardContext Exception sending >> context initialized event to listener instance of class >> org.wso2.carbon.identity.application.authentication.endpoint.util.listener.AuthenticationEndpointContextListener >> org.wso2.securevault.SecureVaultException: Invalid class as >> SecretCallbackHandler : Class Name : >> org.wso2.securevault.secret.handler.SecretManagerSecretCallbackHandler >> >> >> >> But it seems when you try this out you will run into another exception >>> due to not having a property named *secretProvider *in [3]. But first >>> you can try this out and share the log file so I can look further into this. >>> >> >>> As per my understanding this will need a code fix or some property value >>> changes anyway. BTW are you getting this in the alpha pack. If so please >>> share me the detailed steps so I can reproduce and get this fixed. >>> >> >> In the alpha pack we didn't have the cipher tool installed. You can try >> this in the latest jenkins build [1]. Find the steps to reproduce the issue. >> >>- Run ciphertool.sh with -Dconfigure option (with default settings) >>- Start the server >> >> >> [1] >> https://wso2.org/jenkins/job/product-apim_release-1.10.x/19/org.wso2.am$wso2am/ >> >> >> Thanks, >> Lakmali >> >>> >>> [1] >>> http://tharindue.blogspot.com/2015/04/enabling-tenant-domains-dropdown-in-sso.html >>> >>> [2] >>> https://github.com/wso2/carbon-identity/blob/master/components/authentication-framework/org.wso2.carbon.identity.application.authentication.endpoint.util/src/main/java/org/wso2/carbon/identity/application/authentication/endpoint/util/TenantDataManager.java >>> >>> [3] >>> https://github.com/wso2/carbon-identity/blob/master/components/authentication-framework/org.wso2.carbon.identity.application.authentication.endpoint/src/main/resources/EndpointConfig.properties >>> >>> Thank you, >>> Tharindu >>> >>> On Mon, Nov 23, 2015 at 12:40 AM, Lakmali Baminiwatta <lakm...@wso2.com> >>> wrote: >>> >>>> Hi all, >>>> >>>> We ran cipher tool for APIM 1.10 and when starting the server, >>>> authentication endpoint web app deployment fails saying
Re: [Dev] ApplicationDAOImpl trying to query UM_PERMISSION tables against the Identity DB
Created a Jira. [1] https://wso2.org/jira/browse/IDENTITY-4128 On 23 November 2015 at 16:35, Nuwan Dias <nuw...@wso2.com> wrote: > Looks like a bug to me. This would require the Identity and UM tables to > be on a single schema, which would be wrong. > > Thanks, > NuwanD. > > On Mon, Nov 23, 2015 at 4:28 PM, Lakmali Baminiwatta <lakm...@wso2.com> > wrote: > >> Hi all, >> >> In APIM 1.10.0, when we try to rename an Application, below error is >> thrown. When I checked the code, there are queries to UM_PERMISSION table >> against the Identity DB [1]. Shouldn't we use existing UM APIs or run these >> against the UM DB? >> >> Caused by: org.h2.jdbc.JdbcSQLException: Table "UM_PERMISSION" not found; >> SQL statement: >> SELECT UM_ID, UM_RESOURCE_ID FROM UM_PERMISSION WHERE UM_RESOURCE_ID LIKE >> ? [42102-140] >> at org.h2.message.DbException.getJdbcSQLException(DbException.java:327) >> at org.h2.message.DbException.get(DbException.java:167) >> at org.h2.message.DbException.get(DbException.java:144) >> at org.h2.command.Parser.readTableOrView(Parser.java:4498) >> at org.h2.command.Parser.readTableFilter(Parser.java:1011) >> at org.h2.command.Parser.parseSelectSimpleFromPart(Parser.java:1577) >> at org.h2.command.Parser.parseSelectSimple(Parser.java:1682) >> at org.h2.command.Parser.parseSelectSub(Parser.java:1571) >> at org.h2.command.Parser.parseSelectUnion(Parser.java:1416) >> at org.h2.command.Parser.parseSelect(Parser.java:1404) >> at org.h2.command.Parser.parsePrepared(Parser.java:392) >> at org.h2.command.Parser.parse(Parser.java:275) >> at org.h2.command.Parser.parse(Parser.java:247) >> at org.h2.command.Parser.prepare(Parser.java:201) >> at org.h2.command.Parser.prepareCommand(Parser.java:214) >> at org.h2.engine.Session.prepareLocal(Session.java:434) >> at org.h2.engine.Session.prepareCommand(Session.java:384) >> at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1071) >> at org.h2.jdbc.JdbcPreparedStatement.(JdbcPreparedStatement.java:71) >> at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:234) >> at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> at java.lang.reflect.Method.invoke(Method.java:606) >> at >> org.apache.tomcat.jdbc.pool.ProxyConnection.invoke(ProxyConnection.java:126) >> at >> org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109) >> at >> org.wso2.carbon.ndatasource.rdbms.ConnectionRollbackOnReturnInterceptor.invoke(ConnectionRollbackOnReturnInterceptor.java:51) >> at >> org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109) >> at >> org.apache.tomcat.jdbc.pool.interceptor.AbstractCreateStatementInterceptor.invoke(AbstractCreateStatementInterceptor.java:67) >> at >> org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109) >> at >> org.apache.tomcat.jdbc.pool.interceptor.ConnectionState.invoke(ConnectionState.java:153) >> at >> org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109) >> at org.apache.tomcat.jdbc.pool.TrapException.invoke(TrapException.java:41) >> at >> org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109) >> at >> org.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:80) >> at com.sun.proxy.$Proxy13.prepareStatement(Unknown Source) >> at >> org.wso2.carbon.identity.application.mgt.dao.impl.ApplicationDAOImpl.readApplicationPermissions(ApplicationDAOImpl.java:2752) >> at >> org.wso2.carbon.identity.application.mgt.dao.impl.ApplicationDAOImpl.updateBasicApplicationData(ApplicationDAOImpl.java:442) >> at >> org.wso2.carbon.identity.application.mgt.dao.impl.ApplicationDAOImpl.updateApplication(ApplicationDAOImpl.java:337) >> >> [1] >> https://github.com/wso2/carbon-identity/blob/master/components/application-mgt/org.wso2.carbon.identity.application.mgt/src/main/java/org/wso2/carbon/identity/application/mgt/dao/impl/ApplicationDAOImpl.java >> >> Thanks, >> Lakmali >> >> -- >> Lakmali Baminiwatta >> Senior Software Engineer >> WSO2, Inc.: http://wso2.com >> lean.enterprise.middleware >> mobile: +94 71 2335936 >> blog : lakmali.com >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Nuwan Dias > > Technical Lead - WSO2, Inc. http://wso2.com > email : nuw...@wso2.com > Phone : +94 777 775 729 > -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] ApplicationDAOImpl trying to query UM_PERMISSION tables against the Identity DB
Hi all, In APIM 1.10.0, when we try to rename an Application, below error is thrown. When I checked the code, there are queries to UM_PERMISSION table against the Identity DB [1]. Shouldn't we use existing UM APIs or run these against the UM DB? Caused by: org.h2.jdbc.JdbcSQLException: Table "UM_PERMISSION" not found; SQL statement: SELECT UM_ID, UM_RESOURCE_ID FROM UM_PERMISSION WHERE UM_RESOURCE_ID LIKE ? [42102-140] at org.h2.message.DbException.getJdbcSQLException(DbException.java:327) at org.h2.message.DbException.get(DbException.java:167) at org.h2.message.DbException.get(DbException.java:144) at org.h2.command.Parser.readTableOrView(Parser.java:4498) at org.h2.command.Parser.readTableFilter(Parser.java:1011) at org.h2.command.Parser.parseSelectSimpleFromPart(Parser.java:1577) at org.h2.command.Parser.parseSelectSimple(Parser.java:1682) at org.h2.command.Parser.parseSelectSub(Parser.java:1571) at org.h2.command.Parser.parseSelectUnion(Parser.java:1416) at org.h2.command.Parser.parseSelect(Parser.java:1404) at org.h2.command.Parser.parsePrepared(Parser.java:392) at org.h2.command.Parser.parse(Parser.java:275) at org.h2.command.Parser.parse(Parser.java:247) at org.h2.command.Parser.prepare(Parser.java:201) at org.h2.command.Parser.prepareCommand(Parser.java:214) at org.h2.engine.Session.prepareLocal(Session.java:434) at org.h2.engine.Session.prepareCommand(Session.java:384) at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1071) at org.h2.jdbc.JdbcPreparedStatement.(JdbcPreparedStatement.java:71) at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:234) at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.tomcat.jdbc.pool.ProxyConnection.invoke(ProxyConnection.java:126) at org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109) at org.wso2.carbon.ndatasource.rdbms.ConnectionRollbackOnReturnInterceptor.invoke(ConnectionRollbackOnReturnInterceptor.java:51) at org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109) at org.apache.tomcat.jdbc.pool.interceptor.AbstractCreateStatementInterceptor.invoke(AbstractCreateStatementInterceptor.java:67) at org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109) at org.apache.tomcat.jdbc.pool.interceptor.ConnectionState.invoke(ConnectionState.java:153) at org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109) at org.apache.tomcat.jdbc.pool.TrapException.invoke(TrapException.java:41) at org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109) at org.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:80) at com.sun.proxy.$Proxy13.prepareStatement(Unknown Source) at org.wso2.carbon.identity.application.mgt.dao.impl.ApplicationDAOImpl.readApplicationPermissions(ApplicationDAOImpl.java:2752) at org.wso2.carbon.identity.application.mgt.dao.impl.ApplicationDAOImpl.updateBasicApplicationData(ApplicationDAOImpl.java:442) at org.wso2.carbon.identity.application.mgt.dao.impl.ApplicationDAOImpl.updateApplication(ApplicationDAOImpl.java:337) [1] https://github.com/wso2/carbon-identity/blob/master/components/application-mgt/org.wso2.carbon.identity.application.mgt/src/main/java/org/wso2/carbon/identity/application/mgt/dao/impl/ApplicationDAOImpl.java Thanks, Lakmali -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Authentication Endpoint deployment failure with Securevault
nager.serviceChanged(SCRManager.java:222) at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433) at org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81) at org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40) at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38) at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1284) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1197) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1087) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5262) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5550) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1575) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1565) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Thanks, Lakmali -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] APIM admin service to approve the application creation task
On 26 September 2015 at 19:36, Irham Iqbal <iq...@wso2.com> wrote: > Hi All, > > I am automating adding an application workflow by following the > document[1]. In order to do that under "Engaging the WS Workflow Executor > in the API Manager" in the 5th point I need to approve the application > creation task. Is there any admin service to do that from APIM? > Admin-dashboard internally uses BPS's admin service to approve the task. So you should be able to use that. Thanks, Lakmali > > [1] > https://docs.wso2.com/display/AM190/Adding+an+Application+Creation+Workflow > > Thanks, > Iqbal > > -- > Irham Iqbal > Software Engineer - Test Automation > WSO2, Inc.: http://wso2.com > lean. enterprise. middleware > phone: +94 777888452 > -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Deployment fails (Proxy services) for tenants in a ESB worker/manager separated setup
(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) [2013-10-09 19:37:22,493] WARN - SourceHandler Connection time out after request is read: http-incoming-3 [2013-10-09 19:37:23,501] ERROR - AxisEngine The service cannot be found for the endpoint reference (EPR) local://axis2services/evanInlineProxy2?wsdl org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) local://axis2services/evanInlineProxy2?wsdl at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:78) at org.apache.axis2.engine.Phase.invoke(Phase.java:329) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167) at org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.processRESTRequest(MultitenantMessageReceiver.java:543) at org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.doNhttpREST(MultitenantMessageReceiver.java:483) at org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.doREST(MultitenantMessageReceiver.java:313) at org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.processRequest(MultitenantMessageReceiver.java:206) at org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.receive(MultitenantMessageReceiver.java:77) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) at org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:337) at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:169) at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) [1] - https://wso2.org/jira/browse/CARBON-14508 Evanthika Amarasiri Senior Technical Lead - Quality Assurance Mobile: +94773125935 wso2.com Lean Enterprise Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Miyuru Wanninayaka Technical Lead WSO2 Inc. : http://wso2.com Mobile : +94 77 209 9788 Blog : http://miyurudw.blogspot.com Flickr : http://www.flickr.com/photos/miyuru_daminda ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Kishanthan Thangarajah* Senior Software Engineer, Platform Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan http://twitter.com/kishanthan* -- *Kishanthan Thangarajah* Senior Software Engineer, Platform Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan http://twitter.com/kishanthan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Which Git Repository belongs, org.wso2.carbon.transport.mgt.feature
Hi Gihan, On 20 March 2015 at 09:01, Gihan Anuruddha gi...@wso2.com wrote: On Fri, Mar 20, 2015 at 8:23 AM, Dhanuka Ranasinghe dhan...@wso2.com wrote: while building product-apim , I couldn't find Git repos for following features. Could you please help me to find these. org.wso2.carbon.transport.mgt.feature org.wso2.carbon.transport.mail.feature org.wso2.carbon.xfer.feature org.wso2.carbon.mex.feature org.wso2.carbon.mediation.security.server org.wso2.carbon.statistics.transport.feature org.wso2.carbon.ec2.client.feature org.wso2.carbon.registry.extensions.feature org.wso2.carbon.caching.server.feature org.wso2.carbon.jaxws.webapp.mgt.server.feature org.wso2.carbon.jaxws.webapp.mgt.feature org.wso2.carbon.bam. message.tracer.handler.feature use org.wso2.carbon.analytics. message.tracer.handler.feature in carbon-analytics repo Don't we have a carbon 4.4.0 based released version of org.wso2.carbon.analytics. message.tracer.handler.feature? Latest released version[1], seems to be carbon 4.3.0 based. [1] https://github.com/wso2/carbon-analytics/blob/v1.0.2/pom.xml Thanks, Lakmali org.wso2.carbon.mediator.bam.feature *Dhanuka Ranasinghe* Senior Software Engineer WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 715381915 On Thu, Mar 19, 2015 at 5:58 PM, Dhanuka Ranasinghe dhan...@wso2.com wrote: No they have told that it has been removed from carbon-commons. It's not in here [1]. [1] https://github.com/wso2/carbon-commons/blob/4.3.6/pom.xml Cheers, *Dhanuka Ranasinghe* Senior Software Engineer WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 715381915 On Thu, Mar 19, 2015 at 5:51 PM, Mahesh Chinthaka mahe...@wso2.com wrote: Hi Dhanuka, Isnt it in carbon-commons ? In [1] I can see org.wso2.carbon.transport.mgt.feature If so, I think carbon team manages this. [1] - https://github.com/wso2/carbon-commons/tree/master/features/transport-mgt On Thu, Mar 19, 2015 at 5:43 PM, Dhanuka Ranasinghe dhan...@wso2.com wrote: Hi, When I tried to build product-apim with carbon 4.4.0 I am getting following error. So could you please let us know, exactly which Git repository has/maintain org.wso2.carbon.transport.mgt.feature [ERROR] Failed to execute goal org.wso2.maven:carbon-p2-plugin:1.5.3:p2-repo-gen (2-p2-repo-generation) on project am-p2-profile: Error occured when processing the Feature Artifact: org.wso2.carbon.commons:org.wso2.carbon.transport.mgt.feature:4.3.6: ERROR: Could not find artifact org.wso2.carbon.commons:org.wso2.carbon.transport.mgt.feature:zip:4.3.6 in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) Cheers, *Dhanuka Ranasinghe* Senior Software Engineer WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 715381915 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Mahesh Chinthaka Vidanagama* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 63 63 083 | Work: +94 112 145 345 Email: mahe...@wso2.com | Web: www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- W.G. Gihan Anuruddha Senior Software Engineer | WSO2, Inc. M: +94772272595 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 API Manager 1.9.0 Released
issues pertaining to WSO2 API Manager are reported at the following location: - Known Issues https://wso2.org/jira/issues/?filter=12245 How You Can ContributeMailing Lists Join our mailing list and correspond with the developers directly. - Developer List : dev@wso2.org | Subscribe dev-requ...@wso2.org?subject=subscribe | Mail Archive http://wso2.org/mailarchive/dev/ - User List : u...@wso2.org | Subscribe user-requ...@wso2.org?subject=subscribe | Mail Archive http://wso2.org/mailarchive/user/ Reporting Issues We encourage you to report issues, documentation faults and feature requests regarding WSO2 API Manager through the public API Manager JIRA https://wso2.org/jira/browse/APIMANAGER. You can use the Carbon JIRA http://www.wso2.org/jira/browse/CARBON to report any issues related to the Carbon base framework or associated Carbon components. Support We are committed to ensuring that your enterprise middleware deployment is completely supported from evaluation to production. Our unique approach ensures that all support leverages our open development methodology and is provided by the very same engineers who build the technology. For more details and to take advantage of this unique opportunity please visit http://wso2.com/support. To learn more about WSO2 API Manager and WSO2 support offerings please visit http://wso2.com/products/api-manager. *-- The WSO2 API Manager Team --* -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] APIM 1.9.0 nightly build pack - 13-06-2015
Hi,
On 13 June 2015 at 12:50, Evanthika Amarasiri evanth...@wso2.com wrote:
Three of us are still seeing the issue [1] with latest packs. Tried with
private browsers (3 types of browsers).
[1] - https://wso2.org/jira/browse/APIMANAGER-3866
With the fix, it allows to define context with {xxx}, and does not allow
{}. But since we first type {}, and then only type the text in between,
still this validation triggers an error.
We'll provide a proper fix ASAP.
@Chamin,
I don't think we have to popup an error message for this validation.
Please check the existing UI field validations (Ex: special character
validation of context field).
Thanks,
Lakmali
Regards,
Evanthika
On Sat, Jun 13, 2015 at 3:03 AM, Roshan Wijesena ros...@wso2.com wrote:
Hi,
Please find $subject from [1]
[1]http://builder1.us1.wso2.org/~apim/13-06-2015/
Thanks,
Roshan
--
Roshan Wijesena.
Senior Software Engineer-WSO2 Inc.
Mobile: *+94719154640 %2B94719154640*
Email: ros...@wso2.com
*WSO2, Inc. :** wso2.com http://wso2.com/*
lean.enterprise.middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Lakmali Baminiwatta
Senior Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile: +94 71 2335936
blog : lakmali.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] APIM 1.9.0 nightly build pack - 13-06-2015
Fix is attached to the jira [1].
Thanks,
Lakmali
On 13 June 2015 at 13:25, Ushani Balasooriya ush...@wso2.com wrote:
Hi,
The issue [1] comes only when you type {} via keyboard. If you just paste
it or input the previously given context which is already comes from cache,
it won't come.
[1] https://wso2.org/jira/browse/APIMANAGER-3866
On Sat, Jun 13, 2015 at 1:23 PM, Lakmali Baminiwatta lakm...@wso2.com
wrote:
Hi,
On 13 June 2015 at 12:50, Evanthika Amarasiri evanth...@wso2.com wrote:
Three of us are still seeing the issue [1] with latest packs. Tried with
private browsers (3 types of browsers).
[1] - https://wso2.org/jira/browse/APIMANAGER-3866
With the fix, it allows to define context with {xxx}, and does not allow
{}. But since we first type {}, and then only type the text in between,
still this validation triggers an error.
We'll provide a proper fix ASAP.
@Chamin,
I don't think we have to popup an error message for this validation.
Please check the existing UI field validations (Ex: special character
validation of context field).
Thanks,
Lakmali
Regards,
Evanthika
On Sat, Jun 13, 2015 at 3:03 AM, Roshan Wijesena ros...@wso2.com
wrote:
Hi,
Please find $subject from [1]
[1]http://builder1.us1.wso2.org/~apim/13-06-2015/
Thanks,
Roshan
--
Roshan Wijesena.
Senior Software Engineer-WSO2 Inc.
Mobile: *+94719154640 %2B94719154640*
Email: ros...@wso2.com
*WSO2, Inc. :** wso2.com http://wso2.com/*
lean.enterprise.middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Lakmali Baminiwatta
Senior Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile: +94 71 2335936
blog : lakmali.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
*Ushani Balasooriya*
Senior Software Engineer - QA;
WSO2 Inc; http://www.wso2.com/.
Mobile; +94772636796
--
Lakmali Baminiwatta
Senior Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile: +94 71 2335936
blog : lakmali.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] APIM 1.9.0 nightly build pack - 12-06-2015
Hi, Please find $subject from [1] [1]http://builder1.us1.wso2.org/~apim/12-06-2015/ Thanks, Lakmali -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Clarification on import swagger doc
Hi Ushani, On 4 June 2015 at 11:58, Ushani Balasooriya ush...@wso2.com wrote: Hi Jo, Just to re confirm, all attributes include, context, tags, endpoints etc as well I suppose? Swagger documentation has the resource definition (paths, methods, auth types, tiers, scope), scope definition (name, key, roles) and API title version. It doesn't store any other information like endpoints, tags, context, etc. Thanks, Lakmali On Thu, Jun 4, 2015 at 11:29 AM, Joseph Fonseka jos...@wso2.com wrote: Hi Generally it should import the whole document but some of the attributes should be treated differently depending on the context ex. API Name should only get imported if the API is not saved. If the API is saved the designer should replace the name in swagger with the API's name. Cheers Jo On Thu, Jun 4, 2015 at 6:54 AM, Lakmali Baminiwatta lakm...@wso2.com wrote: Adding Jo and Madusanka. On 4 June 2015 at 11:09, Ushani Balasooriya ush...@wso2.com wrote: Hi APIm Team, When you import a swagger document, should it import only the swagger related resources (E.g., resource and scopes) or the whole API information? According to the issue [1] if it is only swagger information, it still imports the API name as well. Pls advice. [1] https://wso2.org/jira/browse/APIMANAGER-3722 Thanks! -- *Ushani Balasooriya* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com -- -- *Joseph Fonseka* WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 772 512 430 skype: jpfonseka * http://lk.linkedin.com/in/rumeshbandara* -- *Ushani Balasooriya* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. Mobile; +94772636796 -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Clarification on import swagger doc
Adding Jo and Madusanka. On 4 June 2015 at 11:09, Ushani Balasooriya ush...@wso2.com wrote: Hi APIm Team, When you import a swagger document, should it import only the swagger related resources (E.g., resource and scopes) or the whole API information? According to the issue [1] if it is only swagger information, it still imports the API name as well. Pls advice. [1] https://wso2.org/jira/browse/APIMANAGER-3722 Thanks! -- *Ushani Balasooriya* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please Review and Merge
Reviewed and merged. Thanks, Lakmali On 1 June 2015 at 16:02, Thilini Cooray thili...@wso2.com wrote: Please merge PR [1] for public JIRA [2]. [1] https://github.com/wso2/carbon-apimgt/pull/562 [2] https://wso2.org/jira/browse/APIMANAGER-3132 Thanks. On Mon, Jun 1, 2015 at 3:21 PM, Thilini Cooray thili...@wso2.com wrote: Hi, Please do not merge due to several modifications. thanks. On Mon, Jun 1, 2015 at 12:54 PM, Thilini Cooray thili...@wso2.com wrote: Hi, This is the fix [1] for public JIRA [2]. Please review and merge. [1] https://github.com/wso2/carbon-apimgt/pull/557 [2] https://wso2.org/jira/browse/APIMANAGER-3132 -- Best Regards, *Thilini Cooray* Software Engineer Mobile : +94 (0) 774 570 112 %2B94%20%280%29%20773%20451194 E-mail : thili...@wso2.com WSO2 Inc. www.wso2.com lean.enterprise.middleware -- Best Regards, *Thilini Cooray* Software Engineer Mobile : +94 (0) 774 570 112 %2B94%20%280%29%20773%20451194 E-mail : thili...@wso2.com WSO2 Inc. www.wso2.com lean.enterprise.middleware -- Best Regards, *Thilini Cooray* Software Engineer Mobile : +94 (0) 774 570 112 %2B94%20%280%29%20773%20451194 E-mail : thili...@wso2.com WSO2 Inc. www.wso2.com lean.enterprise.middleware -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 API Manager 1.9.0 Beta2 Released!
/jira/browse/APIMANAGER-3424] - No
Tier Availability warning if change to Available to specific tenants
Subscriptions
- [APIMANAGER-3524 https://wso2.org/jira/browse/APIMANAGER-3524] -
Expose API for deleting a subscription by the applicationName
- [APIMANAGER-3582 https://wso2.org/jira/browse/APIMANAGER-3582] -
Need an option to delete Parameters that we add for 'Resource Methods'
- [APIMANAGER-3604 https://wso2.org/jira/browse/APIMANAGER-3604] -
When scopes are not defined, pls include a proper message
- [APIMANAGER-3605 https://wso2.org/jira/browse/APIMANAGER-3605] -
Provide ability to skip certain scopes being validated
- [APIMANAGER-3626 https://wso2.org/jira/browse/APIMANAGER-3626] -
Grammar issue in the UI
Patch
- [APIMANAGER-2241 https://wso2.org/jira/browse/APIMANAGER-2241] -
ConcurrentModificationException at server startup
Your feedback are most welcome !!! Please report all the Jiras at [6] and
specify the affected version as 1.9.0 Beta2
https://wso2.org/jira/browse/APIMANAGER/fixforversion/11791.
[1]
https://github.com/wso2/product-apim/releases/download/v1.9.0-Beta-2/wso2am-1.9.0.zip
[2] https://docs.wso2.com/display/AM190/WSO2+API+Manager+Documentation
[3] AM Store : https://{host}:{9763}/store
[4] AM Publisher : https://{host}:{9763}/publisher
[5] AM Roadmap :
https://wso2.org/jira/browse/APIMANAGER#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
[6] https://wso2.org/jira/browse/APIMANAGER
Thanks,
API Manager Team.
--
Lakmali Baminiwatta
Senior Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile: +94 71 2335936
blog : lakmali.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] APIM-1.9.0 latest build pack - 26-05-2015
Hi all, On 28 May 2015 at 16:00, Ushani Balasooriya ush...@wso2.com wrote: Hi Lakmali, We cannot see the hazelcast latest jar inside the patch0010. Please confirm whether it should go in to these packs. Yes, this needs to be in the packs. Please find the released patch0010 attached here with. It would be good if you can apply this after removing the existing patch0010 in the packs. Thanks for pointing this. Thanks, Lakmali This is the md5sum of the jar what we find in plugins. 5e9697cd5298da85d1c2b0a0f336e4b9 hazelcast_3.0.1.wso2v1.jar Thanks! On Tue, May 26, 2015 at 8:22 PM, Lakmali Baminiwatta lakm...@wso2.com wrote: Hi, Please find the $subject from [1]. [1] http://builder1.us1.wso2.org/~apim/26-05-2015/wso2am-1.9.0-SNAPSHOT.zip Thanks, Lakmali -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Ushani Balasooriya* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. Mobile; +94772636796 -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware patch0010.zip https://docs.google.com/a/wso2.com/file/d/0B1mij-0CFKw2S1VaenUwUnNlMzA/edit?usp=drive_web mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Clarification on visibility of APIs in an external store for restricted by roles options
Hi Ushani, On 27 May 2015 at 13:57, Ushani Balasooriya ush...@wso2.com wrote: Hi APIM Team, During external API store testing, when creating the APIs, I have defined the visibility of APIs as, 1. Public 2. Visible to my domain 3. Restricted By Roles *When visibility is Public,* APIS will be visible in the store according to the store configurations defined in the registry. Which the functionality is clear. ExternalAPIStores StoreURLhttp://localhost:9763/store/StoreURL ExternalAPIStore id=Store2 type=wso2 className=org.wso2.carbon.apimgt.impl.publishers.WSO2APIPublisher DisplayNameStore1/DisplayName Endpointhttp://localhost:9773/store/Endpoint Usernameadmin/Username Passwordadmin/Password /ExternalAPIStore /ExternalAPIStores *When visibility is Visible to My Domain,* A tenant is created in the external store via admin console. Then define that tenant's configuration in registry in tenant mode via the publisher's admin console. E.g., ExternalAPIStores StoreURLhttp://localhost:9763/store/StoreURL ExternalAPIStore id=Store2 type=wso2 className=org.wso2.carbon.apimgt.impl.publishers.WSO2APIPublisher DisplayNameTenantStore/DisplayName Endpointhttp://localhost:9773/store/Endpoint Usernamead...@wso2.com/Username Passwordpassword/Password /ExternalAPIStore /ExternalAPIStores Then the APIs will be published to the particular domain and when I select the visibility of APIs as Visible to My Domain, it will display only when the tenant user is logged in to the store. Function is clear. *Restricted By Roles* During this, when I try to create an API, in publisher, it will validate with the roles created in publisher user store. Therefore should I create the same role in publisher's side even if I want to restrict to a role defined in External store side. How can I achieve this function? The idea of publishing to external store means, you have an API which you would like to advertise in another external store as well. What's appearing in the external store is just an advertisement only. The original API appears in the Publisher's store. So we can't just restrict the API to a role which is only in the external store. Because when someone tries to consume the API, he will be redirected to original store. So if the API is restricted by a role, then the role must be in both API stores. Thanks, Lakmali Pls advice. Thanks and Regards, -- *Ushani Balasooriya* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please Review and Merge.
Reviewed and merged. Thanks, Lakmali On 27 May 2015 at 17:30, Chamalee De Silva chama...@wso2.com wrote: Hi, This is the fix [1] for Public JIRA [2]. $Subject. [1] https://github.com/wso2/carbon-apimgt/pull/511 [2] https://wso2.org/jira/browse/APIMANAGER-2750 -- Thanks Regards, *Chamalee De Silva* Software Engineer *WS**O2* Inc. .:http://wso2.com lean *.* enterprise *.* middleware Office :- *+94 11 2145345 %2B94%2011%202145345* mobile :- *+94 7 %2B94%2077%2027820391 1540738* -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] APIM-1.9.0 latest build pack - 26-05-2015
Hi, Please find the $subject from [1]. [1] http://builder1.us1.wso2.org/~apim/26-05-2015/wso2am-1.9.0-SNAPSHOT.zip Thanks, Lakmali -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please Review and Merge
Reviewed and merged the PR. Thanks, Lakmali On 22 May 2015 at 13:56, Chamalee De Silva chama...@wso2.com wrote: Hi, This is the Fix [1] for publich JIRA [2]. Please review and merge. [1] https://github.com/wso2/carbon-apimgt/pull/459 [2] https://wso2.org/jira/browse/APIMANAGER-1821 -- Thanks Regards, *Chamalee De Silva* Software Engineer *WS**O2* Inc. .:http://wso2.com lean *.* enterprise *.* middleware Office :- *+94 11 2145345 %2B94%2011%202145345* mobile :- *+94 7 %2B94%2077%2027820391 1540738* -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Not removing resources copied using p2 touchpoints can cause to increase product distribution size
Hi Manoj, In APIM, we have more than one profile installing store and publisher features. Due to that if we remove resources through p2.inf, second profile fails when trying to copy those again. Is it possible to extract those features again before running the second profile? Thanks, Lakmali On 10 May 2015 at 12:30, Manoj Kumara ma...@wso2.com wrote: Hi APIM Team, $Subject on *carbon-apimgt* repo. In APIM 1.8.0 feature directory 50Mb. This can be reduced from the product distribution by removing resources after installing the features. Such sample can be found on [3]. [1] https://github.com/wso2/carbon-apimgt/blob/master/features/apimgt/org.wso2.carbon.apimgt.publisher.feature/src/main/resources/p2.inf [2] https://github.com/wso2/carbon-apimgt/blob/master/features/apimgt/org.wso2.carbon.apimgt.store.feature/src/main/resources/p2.inf [3] https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/features/org.wso2.carbon.kernel.patch0001.feature/1.0.0/src/main/resources/p2.inf Regards, Manoj *Manoj Kumara* Software Engineer WSO2 Inc. http://wso2.com/ *lean.enterprise.middleware* Mobile: +94713448188 On Sun, May 10, 2015 at 12:17 PM, Manoj Kumara ma...@wso2.com wrote: Hi IS Team, I noticed that in some of the feature pom files in *carbon-identity* repo you guys are using p2 touchpoints to copy resources (webapps, keystore, etc) to the product but not removing them from the feature after installing the feature [1], [2]. This can cause to increase the size of the product distribution since those resources will be under ProductHome/repository/components/features/relevent_feature directory as well. So better to remove those resources after installing the features. Such sample can be found on [3]. [1] https://github.com/wso2/carbon-identity/blob/master/features/identity-provider/org.wso2.carbon.identity.provider.server.feature/resources/p2.inf [2] https://github.com/wso2/carbon-identity/blob/master/features/oauth/org.wso2.carbon.identity.oauth.server.feature/resources/p2.inf [3] https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/features/org.wso2.carbon.kernel.patch0001.feature/1.0.0/src/main/resources/p2.inf Regards, Manoj ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 API Manager 1.9.0 Beta Released!
- [APIMANAGER-3551 https://wso2.org/jira/browse/APIMANAGER-3551] -
Swagger file import button isn't working
- [APIMANAGER-3552 https://wso2.org/jira/browse/APIMANAGER-3552] -
Only 37 tables are created in AM DB (MySQL script) when you run IS with
-Dsetup first when configured as IS as Key Manager
- [APIMANAGER-3554 https://wso2.org/jira/browse/APIMANAGER-3554] -
When subscribing to an api right after starting store node
java.io.NotSerializableException occurs.
- [APIMANAGER-3555 https://wso2.org/jira/browse/APIMANAGER-3555] -
Tenants cannot create applications when IS is configured as Key Manager
- [APIMANAGER-3558 https://wso2.org/jira/browse/APIMANAGER-3558] - API
Version is wrong in API Console for a copied API in Store
- [APIMANAGER-3570 https://wso2.org/jira/browse/APIMANAGER-3570] -
There is no way to invoke HTTP endpoint via API Console.
- [APIMANAGER-3574 https://wso2.org/jira/browse/APIMANAGER-3574] - API
Store breaks when listing Prototyped APIs
Improvement
- [APIMANAGER-2910 https://wso2.org/jira/browse/APIMANAGER-2910] -
helpful troubleshooting message?
- [APIMANAGER-3292 https://wso2.org/jira/browse/APIMANAGER-3292] -
Publisher Edit Swagger Definition : Add grammar check
- [APIMANAGER-3293 https://wso2.org/jira/browse/APIMANAGER-3293] -
Publisher Edit Swagger Definition : Resizable popup
- [APIMANAGER-3311 https://wso2.org/jira/browse/APIMANAGER-3311] -
There is no API to retrieve an API Document by File
- [APIMANAGER-3319 https://wso2.org/jira/browse/APIMANAGER-3319] -
There is no API to retrieve the endpoints of an API Store Item
- [APIMANAGER-3514 https://wso2.org/jira/browse/APIMANAGER-3514] -
Provide adequate information in exceptions throwing in key manager
- [APIMANAGER-3522 https://wso2.org/jira/browse/APIMANAGER-3522] - Add
link to store after publishing an API
New Feature
- [APIMANAGER-3487 https://wso2.org/jira/browse/APIMANAGER-3487] - API
Migration Client to migrate APIM 1.8.0 to 1.9.0
Patch
- [APIMANAGER-3088 https://wso2.org/jira/browse/APIMANAGER-3088] -
Fixing stats error page when no stats in database.
Security Vulnerability
- [APIMANAGER-3442 https://wso2.org/jira/browse/APIMANAGER-3442] - XSS
vulnerability in the API Manager
- [APIMANAGER-3443 https://wso2.org/jira/browse/APIMANAGER-3443] -
Reflected XSS vulnerability in the API Manager
Story
- [APIMANAGER-3481 https://wso2.org/jira/browse/APIMANAGER-3481] - How
to set default validity period of application access token by changing
identity.xml
Task
- [APIMANAGER-3531 https://wso2.org/jira/browse/APIMANAGER-3531] -
Deprecating WSDL Endpoints
Sub-task
- [APIMANAGER-3287 https://wso2.org/jira/browse/APIMANAGER-3287] -
Change validateKey operation in APIKeyValidationService to validate token
obtained from an external AS
- [APIMANAGER-3331 https://wso2.org/jira/browse/APIMANAGER-3331] -
Create a custom Grant Handler to generate Application Access Tokens
- [APIMANAGER-3480 https://wso2.org/jira/browse/APIMANAGER-3480] -
Call Authorization Server from API Store through an extensible interface
Your feedback are most welcome !!! Please report all the Jiras at [6] and
specify the affected version as 1.9.0 Beta
https://wso2.org/jira/browse/APIMANAGER/fixforversion/11768.
[1]
https://github.com/wso2/product-apim/releases/download/v1.9.0-Beta/wso2am-1.9.0-SNAPSHOT.zip
[2] https://docs.wso2.com/display/AM190/WSO2+API+Manager+Documentation
[3] AM Store : https://{host}:{9763}/store
[4] AM Publisher : https://{host}:{9763}/publisher
[5] AM Roadmap :
https://wso2.org/jira/browse/APIMANAGER#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
[6] https://wso2.org/jira/browse/APIMANAGER
Thanks,
API Manager Team.
--
Lakmali Baminiwatta
Senior Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile: +94 71 2335936
blog : lakmali.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Exception thrown in server shutdown with patch0010
On 14 May 2015 at 07:25, Lakmali Baminiwatta lakm...@wso2.com wrote: Hi all, @Kasun, Yes. This is the complete stack trace. see below [1]. @Tanya No we do not have any jars inside the jaggery application. I can be certain that this issue is coming with this CarbonTomcatSessionManager configuration. First we isolated that, this issue is coming only when we install web-app mgt 4.2.3 features and finally found that this configuration causes the issue in APIM. It was advised to remove the unused webapp STRATOS_ROOT under repository/deployment/server/webapps/ to avoid an error on server shutdown with this configuration. According to the offline discussion with SupunM we are removing STRATOS_ROOT webapp from APIM 1.9.0. Thanks, Lakmali [1] [2015-05-13 23:28:50,105] ERROR - ServerManager Error while stopping tomcat org.apache.catalina.LifecycleException: Failed to stop component [StandardServer[8005]] at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) at org.apache.catalina.startup.Tomcat.stop(Tomcat.java:351) at org.wso2.carbon.tomcat.internal.ServerManager.stop(ServerManager.java:113) at org.wso2.carbon.tomcat.internal.TomcatBundleActivator.stop(TomcatBundleActivator.java:65) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:771) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:764) at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:510) at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:566) at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1206) at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:592) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:257) at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:215) at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.suspend(InternalSystemBundle.java:284) at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:692) at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:600) at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:399) at org.wso2.carbon.core.init.CarbonServerManager.shutdown(CarbonServerManager.java:849) at org.wso2.carbon.core.init.CarbonServerManager.shutdownGracefully(CarbonServerManager.java:883) at org.wso2.carbon.core.init.CarbonServerManager$4.run(CarbonServerManager.java:894) Caused by: org.apache.catalina.LifecycleException: Failed to stop component [StandardService[Catalina]] at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) at org.apache.catalina.core.StandardServer.stopInternal(StandardServer.java:760) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) ... 19 more Caused by: org.apache.catalina.LifecycleException: Failed to stop component [StandardEngine[Catalina]] at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) at org.apache.catalina.core.StandardService.stopInternal(StandardService.java:502) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) ... 21 more Caused by: org.apache.catalina.LifecycleException: A child container failed during stop at org.apache.catalina.core.ContainerBase.stopInternal(ContainerBase.java:1186) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) ... 23 more [2015-05-13 23:28:50,107] INFO - CarbonTomcatServiceComponent Stopping the carbon web-app registered under : / [2015-05-13 23:28:51,011] INFO - CarbonServerManager Shutdown complete [2015-05-13 23:28:51,011] INFO - CarbonServerManager Halting JVM Thanks, Lakmali On 14 May 2015 at 06:37, Tanya Madurapperuma ta...@wso2.com wrote: The error in [1] occurs if the WEB-INF/lib or WEB-INF/classes directory has jars in the jaggery application. Does any of the jaggery apps has jars in the above folders? [1] https://wso2.org/jira/browse/JAGGERY-403 Thanks, Tanya On Thu, May 14, 2015 at 1:15 AM, KasunG Gajasinghe kas...@wso2.com wrote: Hi Lakmali, Is this the complete error? There was an issue with Jaggery webapp deployer, and we have fixed that recently. See [1]. Could that be the case for you as well? In that case, the stack trace clearly mentioned that the issue occurred with CarbonTomcatSessionManager. [1] https://wso2.org/jira/browse/JAGGERY-403 On Wed, May 13, 2015 at 11:38 PM, Lakmali Baminiwatta lakm...@wso2.com wrote: Hi all, Found out that, this issue is occurring due to org.wso2.carbon.webapp.mgt.CarbonTomcatSessionManager setting in the tomcat/context.xml. Issue get resolved and exception is no more thrown when I comment it out. Manager className=org.wso2
Re: [Dev] Exception thrown in server shutdown with patch0010
Hi all, @Kasun, Yes. This is the complete stack trace. see below [1]. @Tanya No we do not have any jars inside the jaggery application. I can be certain that this issue is coming with this CarbonTomcatSessionManager configuration. First we isolated that, this issue is coming only when we install web-app mgt 4.2.3 features and finally found that this configuration causes the issue in APIM. [1] [2015-05-13 23:28:50,105] ERROR - ServerManager Error while stopping tomcat org.apache.catalina.LifecycleException: Failed to stop component [StandardServer[8005]] at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) at org.apache.catalina.startup.Tomcat.stop(Tomcat.java:351) at org.wso2.carbon.tomcat.internal.ServerManager.stop(ServerManager.java:113) at org.wso2.carbon.tomcat.internal.TomcatBundleActivator.stop(TomcatBundleActivator.java:65) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:771) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:764) at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:510) at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:566) at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1206) at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:592) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:257) at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:215) at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.suspend(InternalSystemBundle.java:284) at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:692) at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:600) at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:399) at org.wso2.carbon.core.init.CarbonServerManager.shutdown(CarbonServerManager.java:849) at org.wso2.carbon.core.init.CarbonServerManager.shutdownGracefully(CarbonServerManager.java:883) at org.wso2.carbon.core.init.CarbonServerManager$4.run(CarbonServerManager.java:894) Caused by: org.apache.catalina.LifecycleException: Failed to stop component [StandardService[Catalina]] at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) at org.apache.catalina.core.StandardServer.stopInternal(StandardServer.java:760) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) ... 19 more Caused by: org.apache.catalina.LifecycleException: Failed to stop component [StandardEngine[Catalina]] at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) at org.apache.catalina.core.StandardService.stopInternal(StandardService.java:502) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) ... 21 more Caused by: org.apache.catalina.LifecycleException: A child container failed during stop at org.apache.catalina.core.ContainerBase.stopInternal(ContainerBase.java:1186) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) ... 23 more [2015-05-13 23:28:50,107] INFO - CarbonTomcatServiceComponent Stopping the carbon web-app registered under : / [2015-05-13 23:28:51,011] INFO - CarbonServerManager Shutdown complete [2015-05-13 23:28:51,011] INFO - CarbonServerManager Halting JVM Thanks, Lakmali On 14 May 2015 at 06:37, Tanya Madurapperuma ta...@wso2.com wrote: The error in [1] occurs if the WEB-INF/lib or WEB-INF/classes directory has jars in the jaggery application. Does any of the jaggery apps has jars in the above folders? [1] https://wso2.org/jira/browse/JAGGERY-403 Thanks, Tanya On Thu, May 14, 2015 at 1:15 AM, KasunG Gajasinghe kas...@wso2.com wrote: Hi Lakmali, Is this the complete error? There was an issue with Jaggery webapp deployer, and we have fixed that recently. See [1]. Could that be the case for you as well? In that case, the stack trace clearly mentioned that the issue occurred with CarbonTomcatSessionManager. [1] https://wso2.org/jira/browse/JAGGERY-403 On Wed, May 13, 2015 at 11:38 PM, Lakmali Baminiwatta lakm...@wso2.com wrote: Hi all, Found out that, this issue is occurring due to org.wso2.carbon.webapp.mgt.CarbonTomcatSessionManager setting in the tomcat/context.xml. Issue get resolved and exception is no more thrown when I comment it out. Manager className=org.wso2.carbon.webapp.mgt.CarbonTomcatSessionManager sessionIdLength=16 /Manager @Supun, Can this be due to jaggery apps not supporting this setting [1]? I can remember that the improvement done in [2] was not applicable to sessionId length of Jagger applications. Because the improvement is done only in TomcatGenericWebappsDeployer, but for jaggery app deployment we use TomcatJaggeryWebappsDeployer. [1]https
Re: [Dev] Exception thrown in server shutdown with patch0010
Hi all, Found out that, this issue is occurring due to org.wso2.carbon.webapp.mgt.CarbonTomcatSessionManager setting in the tomcat/context.xml. Issue get resolved and exception is no more thrown when I comment it out. Manager className=org.wso2.carbon.webapp.mgt.CarbonTomcatSessionManager sessionIdLength=16 /Manager @Supun, Can this be due to jaggery apps not supporting this setting [1]? I can remember that the improvement done in [2] was not applicable to sessionId length of Jagger applications. Because the improvement is done only in TomcatGenericWebappsDeployer, but for jaggery app deployment we use TomcatJaggeryWebappsDeployer. [1]https://wso2.org/jira/browse/JAGGERY-400 [2]https://wso2.org/jira/browse/WSAS-1818 Thanks, Lakmali On 12 May 2015 at 11:19, Manoj Kumara ma...@wso2.com wrote: Hi Kishanthan, Did you faced similar issues during tomcat upgrading ? *Manoj Kumara* Software Engineer WSO2 Inc. http://wso2.com/ *lean.enterprise.middleware* Mobile: +94713448188 On Mon, May 11, 2015 at 8:36 PM, Lakmali Baminiwatta lakm...@wso2.com wrote: Hi all, After including kernel patch0010 into APIM 1.9.0, we can see below exception in each server shutdown. Note that we upgraded org.wso2.carbon.webapp.mgt.server.feature version into 4.2.3-SNAPSHOT. Any idea? [2015-05-11 19:09:57,241] ERROR - ServerManager Error while stopping tomcat org.apache.catalina.LifecycleException: Failed to stop component [StandardServer[8005]] at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) at org.apache.catalina.startup.Tomcat.stop(Tomcat.java:345) at org.wso2.carbon.tomcat.internal.ServerManager.stop(ServerManager.java:113) at org.wso2.carbon.tomcat.internal.TomcatBundleActivator.stop(TomcatBundleActivator.java:65) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:771) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:764) at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:510) at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:566) at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1206) at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:592) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:257) at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:215) at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.suspend(InternalSystemBundle.java:284) at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:692) at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:600) at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:399) at org.wso2.carbon.core.init.CarbonServerManager.shutdown(CarbonServerManager.java:849) at org.wso2.carbon.core.init.CarbonServerManager.shutdownGracefully(CarbonServerManager.java:883) at org.wso2.carbon.core.init.CarbonServerManager$4.run(CarbonServerManager.java:894) Caused by: org.apache.catalina.LifecycleException: Failed to stop component [StandardService[Catalina]] at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) at org.apache.catalina.core.StandardServer.stopInternal(StandardServer.java:753) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) ... 19 more Caused by: org.apache.catalina.LifecycleException: Failed to stop component [StandardEngine[Catalina]] at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) at org.apache.catalina.core.StandardService.stopInternal(StandardService.java:502) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) ... 21 more Caused by: org.apache.catalina.LifecycleException: A child container failed during stop at org.apache.catalina.core.ContainerBase.stopInternal(ContainerBase.java:1186) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) ... 23 more Thanks, Lakmali -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Request to merge PR https://github.com/wso2/carbon-identity/pull/279
Hi, Please merge the PR [1], which fixes [2]. [1] https://github.com/wso2/carbon-identity/pull/279 [2] https://wso2.org/jira/browse/APIMANAGER-3410 Thanks, Lakmali -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Request to merge PR https://github.com/wso2/carbon-identity/pull/280
Hi, Please merge the PR [1], which fixes [2]. [1] https://github.com/wso2/carbon-identity/pull/280 [2] https://wso2.org/jira/browse/APIMANAGER-3410 Thanks, Lakmali -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Exception thrown in server shutdown with patch0010
Hi all, After including kernel patch0010 into APIM 1.9.0, we can see below exception in each server shutdown. Note that we upgraded org.wso2.carbon.webapp.mgt.server.feature version into 4.2.3-SNAPSHOT. Any idea? [2015-05-11 19:09:57,241] ERROR - ServerManager Error while stopping tomcat org.apache.catalina.LifecycleException: Failed to stop component [StandardServer[8005]] at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) at org.apache.catalina.startup.Tomcat.stop(Tomcat.java:345) at org.wso2.carbon.tomcat.internal.ServerManager.stop(ServerManager.java:113) at org.wso2.carbon.tomcat.internal.TomcatBundleActivator.stop(TomcatBundleActivator.java:65) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:771) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:764) at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:510) at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:566) at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1206) at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:592) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:257) at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:215) at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.suspend(InternalSystemBundle.java:284) at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:692) at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:600) at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:399) at org.wso2.carbon.core.init.CarbonServerManager.shutdown(CarbonServerManager.java:849) at org.wso2.carbon.core.init.CarbonServerManager.shutdownGracefully(CarbonServerManager.java:883) at org.wso2.carbon.core.init.CarbonServerManager$4.run(CarbonServerManager.java:894) Caused by: org.apache.catalina.LifecycleException: Failed to stop component [StandardService[Catalina]] at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) at org.apache.catalina.core.StandardServer.stopInternal(StandardServer.java:753) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) ... 19 more Caused by: org.apache.catalina.LifecycleException: Failed to stop component [StandardEngine[Catalina]] at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) at org.apache.catalina.core.StandardService.stopInternal(StandardService.java:502) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) ... 21 more Caused by: org.apache.catalina.LifecycleException: A child container failed during stop at org.apache.catalina.core.ContainerBase.stopInternal(ContainerBase.java:1186) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) ... 23 more Thanks, Lakmali -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please Review and Merge PR
Reviewed and merged. Thanks, Lakmali On 11 May 2015 at 20:56, Chamalee De Silva chama...@wso2.com wrote: Hi, Please $subject [1] for issue [2]. [1] https://github.com/wso2/carbon-apimgt/pull/368 [2] https://wso2.org/jira/browse/APIMANAGER-3547 -- Thanks Regards, *Chamalee De Silva* Software Engineer *WS**O2* Inc. .:http://wso2.com lean *.* enterprise *.* middleware Office :- *+94 11 2145345 %2B94%2011%202145345* mobile :- *+94 7 %2B94%2077%2027820391 1540738* -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] APIM-1.9.0 latest build pack - 09-05-2015
Hi, Please find $subject from [1]. [1]http://builder1.us1.wso2.org/~apim/09-05-2015/wso2am-1.9.0-SNAPSHOT.zip Thanks, Lakmali -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Manager 1.9.0: Publisher profile throws a java.lang.ClassNotFoundException exception.
Hi all, On 6 May 2015 at 15:23, Sewmini Jayaweera sewm...@wso2.com wrote: Hi All, While setting up a distributed setup [1], java.lang.ClassNotFoundException was observed when starting the publisher node given -Dprofile=api-publisher. Please refer to the [2] issue reported. This is due to missing org.jaggeryjs.modules.process.feature in api-publisher p2-profile. Fixed in https://github.com/wso2/product-apim/pull/146. Thanks, Lakmali [1]. https://docs.wso2.com/display/CLUSTER420/Clustering+API+Manager [2]. https://wso2.org/jira/browse/APIMANAGER-3518 Thanks Regards, Sewmini Sewmini Jayaweera *Software Engineer - QA Team* Mobile: +94 (0) 773 381 250 sewm...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Request to merge PR https://github.com/wso2/carbon-identity/pull/261
Hi, Please merge the PR [1], which upgrades amber version to 0.22.1358727.wso2v5 This upgrade is required for fixing [2]. [1] https://github.com/wso2/carbon-identity/pull/261 [2] https://wso2.org/jira/browse/APIMANAGER-3352 Thanks, Lakmali -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please review and Merge the PR
On 28 April 2015 at 16:52, Chamalee De Silva chama...@wso2.com wrote: Hi, This is the Fix [1] for the Public JIRA [2]. [1] https://github.com/wso2/carbon-apimgt/pull/257 [2] https://wso2.org/jira/browse/APIMANAGER-3270 Changes merged. Thanks. $subject. -- Chamalee De Silva Software Engineer | WSO2 E:chama...@wso2.com nirosh...@wso2.com M :0711540738| http://wso2.com http://wso2.com/ -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 API Manager 1.9.0 Alpha Released!
https://wso2.org/jira/browse/APIMANAGER-2787] -
Mis-spellings in the code for 'tenant' as 'tennat'
- [APIMANAGER-3351 https://wso2.org/jira/browse/APIMANAGER-3351] -
Improving Statistics graphs
- [APIMANAGER-3388 https://wso2.org/jira/browse/APIMANAGER-3388] -
Update API Manager to the latest Swagger version (2.0)
- [APIMANAGER-3395 https://wso2.org/jira/browse/APIMANAGER-3395] -
Need to provide proper instructions when adding tags to apis
- [APIMANAGER-3420 https://wso2.org/jira/browse/APIMANAGER-3420] -
Swagger v2.0 support for APIM
- [APIMANAGER-3431 https://wso2.org/jira/browse/APIMANAGER-3431] -
Override IP address with end user IP address for GA
- [APIMANAGER-3465 https://wso2.org/jira/browse/APIMANAGER-3465] -
Allow changing user password in API store.
- [APIMANAGER-3466 https://wso2.org/jira/browse/APIMANAGER-3466] -
Adding loading Indicators to buttons in API Design wizard
- [APIMANAGER-3467 https://wso2.org/jira/browse/APIMANAGER-3467] -
CORS Improvements
Moderation
- [APIMANAGER-3412 https://wso2.org/jira/browse/APIMANAGER-3412] -
Ability to use deferent context path for registry in reverse proxy
environments
New Feature
- [APIMANAGER-3415 https://wso2.org/jira/browse/APIMANAGER-3415] -
Providing a way to add event receiver and analyser configurations through
UI in APIM
Patch
- [APIMANAGER-1970 https://wso2.org/jira/browse/APIMANAGER-1970] -
Identify unsatisfied components in server startup - APIM
Task
- [APIMANAGER-3429 https://wso2.org/jira/browse/APIMANAGER-3429] -
Test case for API SCOPE to test access with different roles
- [APIMANAGER-3445 https://wso2.org/jira/browse/APIMANAGER-3445] -
Rename API Copy button as Create Version
Your feedback are most welcome !!! Please report all the Jiras at [6] and
specify the affected version as 1.9.0 Alpha
https://wso2.org/jira/browse/APIMANAGER/fixforversion/11768.
[1]
https://github.com/wso2/product-apim/releases/download/v1.9.0-Alpha/wso2am-1.9.0-SNAPSHOT.zip
[2] https://docs.wso2.com/display/AM190/WSO2+API+Manager+Documentation
[3] AM Store : https://{host}:{9763}/store
[4] AM Publisher : https://{host}:{9763}/publisher
[5] AM Roadmap :
https://wso2.org/jira/browse/APIMANAGER#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
[6] https://wso2.org/jira/browse/APIMANAGER
Thanks,
API Manager Team.
--
Lakmali Baminiwatta
Senior Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile: +94 71 2335936
blog : lakmali.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please Review and Merge the PR
Hi Chamalee, On 23 April 2015 at 11:13, Chamalee De Silva chama...@wso2.com wrote: Hi, This is the fix PR [1] for the public JIRA [2]. Consumer-key:authz_user combination is used to validate the subscription throttling tier instead of using access token. Through that the ability of the user to send more than permitted number of requests per minute by regenerating the access token is avoided. Please review and merge. Reviewed and merged. Thanks. [1] *https://github.com/wso2/carbon-apimgt/pull/208 https://github.com/wso2/carbon-apimgt/pull/208* [2] https://wso2.org/jira/browse/APIMANAGER-3406 Thanks and Regards, -- Chamalee De Silva Software Engineer | WSO2 E:chama...@wso2.com nirosh...@wso2.com M :0711540738| http://wso2.com http://wso2.com/ -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please Review and Merge the PR
On 24 April 2015 at 17:05, Chamalee De Silva chama...@wso2.com wrote: This is the Fix PR [1] for the JIRA [2]. Please review and merge. Reviewed and merged. Thanks. [1] https://github.com/wso2/carbon-apimgt/pull/229 [2] https://wso2.org/jira/browse/APIMANAGER-3129 -- Chamalee De Silva Software Engineer | WSO2 E:chama...@wso2.com nirosh...@wso2.com M :0711540738| http://wso2.com http://wso2.com/ -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV][Jaggery] how to handle exception come from XMLHttpRequestHostObject
Hi all,
Isn't it better to handle this error rather than hiding the logs through
log4j.properties? I think option 4 is better and has minimal changes to
existing logic.
ex: We can put a try/catch block and handle below before the XHR request.
var httpClient = new
Packages.org.apache.http.impl.client.DefaultHttpClient();
var httpPost = new
Packages.org.apache.http.client.methods.HttpPost(endpoint);
var response = httpClient.execute(httpPost);
BPSRunning = true;
Thanks,
Lakmali
On 20 March 2015 at 10:33, Rasika Perera rasi...@wso2.com wrote:
[Please ignore my previous reply, it was incomplete]
Hi Tharindu,
According to chat we had, IMO if your intention is to avoid error messages
from XMLHttpRequestHostObject.java rather than patching XHR, you can
add following to your log4j property file.
log4j.logger.your package = DEBUG|INFO|OFF|WARN...
log4j.logger.org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject = FATAL
Or...
log4j.logger.org.jaggeryjs.hostobjects.xhr= FATAL
Note that i used log level FATAL over completely turn off logging using
OFF.
Thank you
On Fri, Mar 20, 2015 at 10:27 AM, Rasika Perera rasi...@wso2.com wrote:
Hi Tharindu,
According to chat we had, IMO if your intention is to avoid error
messages from XMLHttpRequestHostObject.java rather than patching XHR, you
can add following to your log4j property file.
log4j.logger.your package = DEBUG|INFO|OFF|WARN...
log4j.logger.org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject =
FATAL
or
Note that i used log level FATAL over completely turn off logging using
OFF.
Thank you
On Thu, Mar 19, 2015 at 6:00 PM, Ruchira Wageesha ruch...@wso2.com
wrote:
Following are the possible options that I can think.
1. Patching XHR to get rid of the log message
2. Hiding the error from log4j, but AFAIK, then it will not log any
error from XHR
3. Using any Java's http-client directly from Jaggery[a] to do the HTTP
calls instead of XHR
4. Using any Java's http-client to check the endpoint status, and
continue original HTTP call with XHR
[a]
https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Rhino/Scripting_Java
/Ruchira
On Thu, Mar 19, 2015 at 5:18 PM, Lakmali Baminiwatta lakm...@wso2.com
wrote:
Hi Ruchira,
In APIM and APPM we talk to the BPS server and fetch Human Tasks
available. For that when the user is login to the admin-dashboard jaggery
app, we do a login call to BPS server using XMLHttpRequest. At this point,
if the BPS is not running we are getting this connection refused error in
the logs. We need to handle this.
As Tharindu mentioned, XMLHttpRequestHostObject.java uses
log.error(e.getMessage(),
e); [1]. Therefore we can't get rid of this stack trace in the log by
just catching the exception.
Is there any method in jaggery that we can use to check whether server
is up and running before doing the send call and handle this? Appreciate
any help on this.
[1]
https://github.com/wso2/jaggery/blob/0.9.0.ALPHA4.wso2v4/components/hostobjects/org.jaggeryjs.hostobjects.xhr/src/main/java/org/jaggeryjs/hostobjects/xhr/XMLHttpRequestHostObject.java
[2]https://wso2.org/jira/browse/APPM-587
[3]https://wso2.org/jira/browse/APIMANAGER-3139
Thanks,
Lakmali
On 18 March 2015 at 08:57, Tharindu Dharmarathna tharin...@wso2.com
wrote:
Hi Ruchira,
We want to carch the exception according to connection refused
exception from the jaggery side . Due to logging of this exception from
Hostobject We couldn't remove this exception come from the console.
Is there any way of check a server is up and running from jaggery side
. If there's a way we can avoid exception come from the console.
Thanks
Tharindu
On Wed, Mar 18, 2015 at 2:06 AM, Ruchira Wageesha ruch...@wso2.com
wrote:
What is the issue with going try/catch blocks?
/Ruchira
On Tue, Mar 17, 2015 at 5:56 PM, Tharindu Dharmarathna
tharin...@wso2.com wrote:
Hi all,
According to public jira [1] how can we handle connection refused
exception come from this issue . This come from the send method.
code snippest for this issue
try{
var xhr = new XMLHttpRequest();
var site = require(/site/conf/site.json);
var endpoint =
site.workflows.applicationWorkFlowServerURL+AuthenticationAdmin;
xhr.open(POST, endpoint);
var payload = 'soap:Envelope xmlns:soap=
http://www.w3.org/2003/05/soap-envelope; xmlns:aut=
http://authentication.services.core.carbon.wso2.org;soap:Header/soap:Bodyaut:loginaut:username'
+ username + '/aut:usernameaut:password' + password +
'/aut:passwordaut:remoteAddresslocalhost/aut:remoteAddress/aut:login/soap:Body/soap:Envelope';
xhr.send(payload);
var cookie = (xhr.getAllResponseHeaders());
log.info(xhr.readyState);
//session.put(workflowCookie,cookie.split(;)[0].split(:)[1]);
var sessionCookie = xhr.getResponseHeader(Set-Cookie);
session.put(workflowCookie,sessionCookie);
}catch (e) {
// log.error(e.message);
}
Exception come from the following jaggery hostobject code
Re: [Dev] [DEV][Jaggery] how to handle exception come from XMLHttpRequestHostObject
Hi Ruchira,
In APIM and APPM we talk to the BPS server and fetch Human Tasks available.
For that when the user is login to the admin-dashboard jaggery app, we do a
login call to BPS server using XMLHttpRequest. At this point, if the BPS is
not running we are getting this connection refused error in the logs. We
need to handle this.
As Tharindu mentioned, XMLHttpRequestHostObject.java uses
log.error(e.getMessage(),
e); [1]. Therefore we can't get rid of this stack trace in the log by just
catching the exception.
Is there any method in jaggery that we can use to check whether server is
up and running before doing the send call and handle this? Appreciate any
help on this.
[1]
https://github.com/wso2/jaggery/blob/0.9.0.ALPHA4.wso2v4/components/hostobjects/org.jaggeryjs.hostobjects.xhr/src/main/java/org/jaggeryjs/hostobjects/xhr/XMLHttpRequestHostObject.java
[2]https://wso2.org/jira/browse/APPM-587
[3]https://wso2.org/jira/browse/APIMANAGER-3139
Thanks,
Lakmali
On 18 March 2015 at 08:57, Tharindu Dharmarathna tharin...@wso2.com wrote:
Hi Ruchira,
We want to carch the exception according to connection refused exception
from the jaggery side . Due to logging of this exception from Hostobject
We couldn't remove this exception come from the console.
Is there any way of check a server is up and running from jaggery side .
If there's a way we can avoid exception come from the console.
Thanks
Tharindu
On Wed, Mar 18, 2015 at 2:06 AM, Ruchira Wageesha ruch...@wso2.com
wrote:
What is the issue with going try/catch blocks?
/Ruchira
On Tue, Mar 17, 2015 at 5:56 PM, Tharindu Dharmarathna
tharin...@wso2.com wrote:
Hi all,
According to public jira [1] how can we handle connection refused
exception come from this issue . This come from the send method.
code snippest for this issue
try{
var xhr = new XMLHttpRequest();
var site = require(/site/conf/site.json);
var endpoint =
site.workflows.applicationWorkFlowServerURL+AuthenticationAdmin;
xhr.open(POST, endpoint);
var payload = 'soap:Envelope xmlns:soap=
http://www.w3.org/2003/05/soap-envelope; xmlns:aut=
http://authentication.services.core.carbon.wso2.org;soap:Header/soap:Bodyaut:loginaut:username'
+ username + '/aut:usernameaut:password' + password +
'/aut:passwordaut:remoteAddresslocalhost/aut:remoteAddress/aut:login/soap:Body/soap:Envelope';
xhr.send(payload);
var cookie = (xhr.getAllResponseHeaders());
log.info(xhr.readyState);
//session.put(workflowCookie,cookie.split(;)[0].split(:)[1]);
var sessionCookie = xhr.getResponseHeader(Set-Cookie);
session.put(workflowCookie,sessionCookie);
}catch (e) {
// log.error(e.message);
}
Exception come from the following jaggery hostobject code
private static void executeRequest(Context cx, XMLHttpRequestHostObject
xhr) throws ScriptException {
try {
xhr.httpClient.executeMethod(xhr.method);
xhr.statusLine = xhr.method.getStatusLine();
xhr.responseHeaders = xhr.method.getResponseHeaders();
updateReadyState(cx, xhr, HEADERS_RECEIVED);
byte[] response = xhr.method.getResponseBody();
if (response.length 0) {
xhr.responseText = new String(response);
}
Header contentType = xhr.method.getResponseHeader(Content-Type);
if (contentType != null) {
xhr.responseType = contentType.getValue();
}
updateReadyState(cx, xhr, DONE);
} catch (IOException e) {
log.error(e.getMessage(), e);
throw new ScriptException(e);
} finally {
xhr.method.releaseConnection();
}
}
XMLHttpRequestHostObject.java
[1] - https://wso2.org/jira/browse/APIMANAGER-3139
Thanks and regards
*Tharindu Dharmarathna*Associate Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
mobile: *+94779109091 %2B94779109091*
--
*Ruchira Wageesha**Associate Technical Lead*
*WSO2 Inc. - lean . enterprise . middleware | wso2.com http://wso2.com*
*email: ruch...@wso2.com ruch...@wso2.com, blog:
ruchirawageesha.blogspot.com http://ruchirawageesha.blogspot.com,
mobile: +94 77 5493444 %2B94%2077%205493444*
--
*Tharindu Dharmarathna*Associate Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
mobile: *+94779109091 %2B94779109091*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Lakmali Baminiwatta
Senior Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile: +94 71 2335936
blog : lakmali.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Internal user roles are added/shown twice for users
Hi Pushpalanka, Find the latest App Manager pack [1]. By following the steps given in [2], this issue can be reproduced. [1] http://builder1.us1.wso2.org/~appm/17-02-2015/ [2] https://wso2.org/jira/browse/APPM-333 Thanks, Lakmali On 18 February 2015 at 09:47, Pushpalanka Jayawardhana la...@wso2.com wrote: Hi Nuwan, I couldn't reproduce the error with IS 5.0.0 default pack. Is this after the SP-01 applied or do you have any specific steps? Thanks, Pushpalanka. -- Pushpalanka Jayawardhana, B.Sc.Eng.(Hons). Software Engineer, WSO2 Lanka (pvt) Ltd; wso2.com/ Mobile: +94779716248 Blog: pushpalankajaya.blogspot.com/ | LinkedIn: lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka On Wed, Feb 18, 2015 at 3:46 AM, Nuwan Wimalasekara nuw...@wso2.com wrote: Hi I am getting this issue in Identity Server 5.0.0 as well. Is there any workaround to get rid of this issue Thanks, Nuwanw On Tue, Feb 17, 2015 at 5:18 AM, Lakmali Baminiwatta lakm...@wso2.com wrote: Hi IS team, In the latest APPM and APIM packs, if we create a user by assigning an Internal role, it lists the same role twice when viewing the roles of that user. This is reported in [1]. Can you please have a look? [1] https://wso2.org/jira/browse/APPM-333 Thanks, Lakmali https://wso2.org/jira/browse/APPM-333 -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Internal user roles are added/shown twice for users
Hi IS team, In the latest APPM and APIM packs, if we create a user by assigning an Internal role, it lists the same role twice when viewing the roles of that user. This is reported in [1]. Can you please have a look? [1] https://wso2.org/jira/browse/APPM-333 Thanks, Lakmali https://wso2.org/jira/browse/APPM-333 -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Need help with quote parameter in smooks mediator
Hi Kalpa, Did you try the with csv:reader in Smooks mediator instead of resource-config? ?xml version=1.0 encoding=UTF-8? localEntry xmlns=http://ws.apache.org/ns/synapse; key=smooks-csv smooks-resource-list xmlns=http://www.milyn.org/xsd/smooks-1.1.xsd; xmlns:csv= http://www.milyn.org/xsd/smooks/csv-1.2.xsd; csv:reader fields=Book,ISBN,Author,Comments separator=#09; quote=~ rootElementName=Books recordElementName=Book/ /smooks-resource-list description/ /localEntry Thanks, Lakmali On 17 February 2015 at 09:22, Kalpa Welivitigoda kal...@wso2.com wrote: Hi, Smooks has character as the default for quotes. According to smooks documentation [1], smooks configuration has a quote attribute we can use to set the quote character. I tried with the following local entry in esb as the smooks configuration and the quote param has no effect over the output. My csv file has records with character, and without the quote param, the output is wrong (some records are dropped). Also with setting the quote param to something else like ~ character, the result is the same. What could have gone wrong here? On a side note, I tried the same with the Smooks csv-to-xml sample and it works fine (by setting the quote attribute in csv:reader). ?xml version=1.0 encoding=UTF-8? localEntry xmlns=http://ws.apache.org/ns/synapse; key=smooks-csv smooks-resource-list xmlns=http://www.milyn.org/xsd/smooks-1.1.xsd; xmlns:csv= http://www.milyn.org/xsd/smooks/csv-1.2.xsd; resource-config selector=org.xml.sax.driver resourceorg.milyn.csv.CSVReader/resource param name=fieldsBook,ISBN,Author,Comments/param param name=separator#09;/param param name=quote~/param param name=rootElementNameBooks/param param name=recordElementNameBook/param /resource-config /smooks-resource-list description/ /localEntry [1] http://www.smooks.org/mediawiki/index.php?title=V1.5:Smooks_v1.5_User_Guide ?xml version=1.0? smooks-resource-list xmlns=http://www.milyn.org/xsd/smooks-1.1.xsd; xmlns:csv=http://www.milyn.org/xsd/smooks/csv-1.5.xsd; !-- Configure the CSV to parse the message into a stream of SAX events. -- csv:reader fields=firstname,lastname,gender,age,country separator=| quote=' skipLines=1 / /smooks-resource-list -- Best Regards, Kalpa Welivitigoda Software Engineer, WSO2 Inc. http://wso2.com Email: kal...@wso2.com Mobile: +94776509215 -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [API-M] Exception occurs while testing the Encrypting passwords process
Hi Kala, On 16 January 2015 at 15:13, Kala Weerawardana k...@wso2.com wrote: Hi, I followed the Encrypting passwords documentation at [1] to test the scenario. While doing that I got the below mentioned exception. Exception in thread main org.wso2.ciphertool.CipherToolException: Element for secret alias 'APIManager.WorkFlowExtensions.ApplicationCreation.Password' can not be found in api-manager.xml file or You have entered invalid Xpath value at org.wso2.ciphertool.CipherTool.handleException(CipherTool.java:882) at org.wso2.ciphertool.CipherTool.writeTokenToConfigFile(CipherTool.java:501) at org.wso2.ciphertool.CipherTool.writeSecureVaultConfigTokens(CipherTool.java:395) at org.wso2.ciphertool.CipherTool.main(CipherTool.java:83) And looking in to it I figured out that this has a new implementation as it is moved on to registry. So this content should be removed from the documentation as well. [2] +1. Yes we need to. How is secure vault testing with workflows done now? Since the workflow configuration file is moved to registry, now we don't have a password encryption related functionality on that. Thanks, Lakmali And is there a documentation I can refer to test this flow? [1] - https://docs.wso2.com/display/AM170/Encrypting+Passwords [2] - https://wso2.org/jira/browse/DOCUMENTATION-1413 Thanks Regards, Kala https://docs.wso2.com/display/AM170/Encrypting+Passwords-- Kala C. Weerawardana *Software Engineer - QA Team* *WSO2 Inc. * Mobile : +94 (0) 716189886 +94 (0) 772877683 k...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Limitations with Cache Mediator
Hi Lalaji, In REQUESTHASHGenerator, we excluded Date and User-Agent headers when generating the request hash. If there are any other or custom headers which need to be excluded, we can write a new Hash Generator implementation by extending REQUESTHASHGenerator and override 'getDigest()' method. Then we can use that in the cache mediator. Thanks, Lakmali On 22 October 2014 22:59, Lalaji Sureshika lal...@wso2.com wrote: Hi, On Fri, Dec 6, 2013 at 2:49 AM, Lakmali Baminiwatta lakm...@wso2.com wrote: Hi Sanjeewa, On 6 December 2013 07:48, Sanjeewa Malalgoda sanje...@wso2.com wrote: On Mon, Dec 2, 2013 at 6:23 PM, Lakmali Baminiwatta lakm...@wso2.com wrote: Hi, On 2 December 2013 18:02, Sumedha Rubasinghe sume...@wso2.com wrote: On Mon, Dec 2, 2013 at 5:24 PM, Lakmali Baminiwatta lakm...@wso2.com wrote: Hi Sanjeewa, On 2 December 2013 17:00, Sanjeewa Malalgoda sanje...@wso2.com wrote: On Sun, Dec 1, 2013 at 11:01 PM, Lakmali Baminiwatta lakm...@wso2.com wrote: Hi all, When processing the response, if the request is REST then soap format, transport headers and message type are also stored. Similarly when retrieving the cached response, if the request is REST then stored values are used to compose the response message. With these modifications cache mediator returns the response correctly for non SOAP requests. But we have another issue here. Currently the request Hash value is derived from the SOAP message body. So for REST calls it gets the same hash value for all requests which sent without a payload. ex: Both below requests are recognized as the same request according to the hash value derived from DOMHASHGenerator. curl -v -H Authorization: Bearer 1EV6Qqa_DboaBzNj2JfiyXoO1Ysa http://localhost:8280/test/1.0.0?regNo=001 curl -v -H Authorization: Bearer 1EV6Qqa_DboaBzNj2JfiyXoO1Ysa http://localhost:8280/test/1.0.0?regNo=002 http://localhost:8280/test/1.0.0?regNo=001 So right now we need to figure out a mechanism to generate hash value for REST calls. How if we consider full request path(including query params and etc) + headers. For above example something like follows (full request path and , separated transport headers list). We can compute hash value of that string and store it. *http://localhost:8280/test/1.0.0?regNo=002,Authorization http://localhost:8280/test/1.0.0?regNo=002,Authorization: Bearer 1EV6Qqa_DboaBzNj2JfiyXoO1Ysa* Here we cannot only consider full request path as we take some decisions at backend based on headers. WDYT? Yeah, need to consider request path + headers. But I think we don't need hash Authorization headers, as request hits the cache mediator after going through the handlers. So in default case, at the time of hashing we don't have the authorization header. So AFAIU, the only concern which comes up here is, same request invoked using different keys may get the response from the cache. I believe that is ok. WDYT? We simply store response values against a given request pattern. But Authorisation header should not be part of it. Otherwise it will become a token based cache. But are whole lot of other header parameter like content-type, accept header, accept language ( http://en.wikipedia.org/wiki/List_of_HTTP_header_fields). Let's ignore Authorisation header for time being. +1. So for now let's generate the hash based on request path, Accept Content-Type headers and payload (if available). +1. IMO we should use all other headers except authentication headers (Ex. sometimes response may depend on client type or sometimes it may depend on any other custom header). We can use all the headers [1]. But there are some headers which seems not correct to use for hashing the request. ex: Date - This is unique for each request. If this is used for generting the hash, cache will be never used. User-Agent - This is specific to the user client/browser who sent the request. So different caches for different users. So I think we need to figure out which headers to skip or which headers to use for hash generation. Did we consider , above unique request headers to include in hashing the request or are we generating the cache digest based on all transport headers..? [1]http://en.wikipedia.org/wiki/List_of_HTTP_header_fields Thanks, Lakmali Thanks, sanjeewa. Thanks, Lakmali I am writing a new Digest Generator implementation by extending DOMHASHGenerator. This basically does what DOMHASHGenerator had been doing and additionally it digests request path and available transport headers as well. Thanks, Lakmali Thanks, sanjeewa. Thanks, Lakmali On 29 November 2013 00:18, Lakmali Baminiwatta lakm...@wso2.com wrote: Hi all, Currently Cache mediator stores the response message as a byte array and builds the soap envelope from that when sending the cached response[1]. When building the response, it checks whether the request
Re: [Dev] [APIM] Access-Control-Allow-Methods header not getting set for CORS requests.
Hi Jo, On 5 September 2014 15:19, Joseph Fonseka jos...@wso2.com wrote: Hi In AM 1.7.1 Access-Control-Allow-Methods header is not getting set by the handler. When trouble shooting I found that particular line is commented. was there a reason to remove it ? Yes. When we had this, the configured Access-Control-Allow-Methods header value was completely overriding the actual value sent in the response for that header. As a result if someone checks the Methods supported by the API (with Max-Forwards:0) or the back-end service by sending an OPTIONS call to the API, the value is not correct. Therefore we decided to remove this header and only depend on the Access-Control-Allow-Methods value sent from the back-end service for Swagger call [1]. [1]https://wso2.org/jira/browse/APIMANAGER-2128 If Access-Control-Allow-Methods is not present PUT and DELETE requests will not work in swagger console + other web clients. May be we can check whether actual response contains this header and if not add the header with the methods only exposed by the API's resources. Thanks, Lakmali Thanks Jo -- -- *Joseph Fonseka* WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 772 512 430 skype: jpfonseka * http://lk.linkedin.com/in/rumeshbandara* -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Many instances of APIManagerInterceptorValve is being registered at startup
Hi Supun, We were registering APIManagerInterceptorValve, inside APIManagerInterceptorComponent.java and it is getting invoked when activating org.wso2.carbon.apimgt.interceptor bundle. So I am not sure how does many instances of the valve are getting registered. Reason for registering it in code level is, we need the valve to be registered only if api management is enabled. Thanks, Lakmali On 4 July 2014 19:45, Supun Malinga sup...@wso2.com wrote: HI, Found out $subject. Also what's the reason for it's being registered in code level ?.. We can register the valves via catalina-server.xml. thanks, -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com email: sup...@wso2.com sup...@wso2.com mobile: +94 (0)71 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [AM-1.7]Remove the migrations scripts/guide from the disrtibution
Hi Ajith, On 6 June 2014 19:06, Ajith Vitharana aji...@wso2.com wrote: Hi AM team, It is good to place the those scrips/guide out of the distribution and place some other place like SVN. +1. The reasons are, 1. It is not useful for the user who start first time with AM. 2. We have full fights to fix the bugs in scripts/guides even after the release. migration-1.0.0_to_1.2.0 migration-1.2.0_to_1.3.0 migration-1.3.0_to_1.4.0 migration-1.4.0_to_1.5.0 migration-1.5.0_to_1.6.0 migration-1.6.0_to_1.7.0 WDYT ? Yes, Right now since the migration scripts are inside the distribution, we have to wait until branching the product to new version in order to commit any fixes, readme updates etc. Thanks, Lakmali Thanks Ajith -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Manager 1.7.0 nightly build pack - 14-05-2014
Hi Charitha, On 16 May 2014 00:56, Sumedha Rubasinghe sume...@wso2.com wrote: Are there anything else missing? On May 15, 2014 11:46 PM, Charitha Kankanamge chari...@wso2.com wrote: It seems some fixes are missing in this pack? Specially https://wso2.org/jira/browse/APIMANAGER-2183 This is available in the pack. After discussing with the team we had renamed Private visibility as Visible to my domain [1]. [1] https://docs.wso2.org/display/AM170/API+Visibility Thanks, Lakmali Charitha Kankanamge cell: +1 812-391-7730 http://charithaka.blogspot.com *SOA and Testing without nonsense* On Thu, May 15, 2014 at 12:03 AM, Lakmali Baminiwatta lakm...@wso2.comwrote: Hi, Please find the $subject in [1]. [1] http://builder1.us1.wso2.org/~apim/14-05-2014/wso2am-1.7.0.zip Thanks, Lakmali -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] API Manager 1.7.0 nightly build pack - 14-05-2014
Hi, Please find the $subject in [1]. [1] http://builder1.us1.wso2.org/~apim/14-05-2014/wso2am-1.7.0.zip Thanks, Lakmali -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Renaming APIM workflow-admin appication as admin
Hi all, Please note that 'workflow-admin' jaggery application has been renamed as 'admin'[1], since now it is used to administer non workflow related tasks as well (tenant themes). For the backward compatibility an application with 'workflow-admin' context is still available and it redirects to this new 'admin' application. [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/apimgt/admin-web/1.2.2 Thanks, Lakmali -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Renaming APIM workflow-admin appication as admin
+1. Renamed as admin-dashboard [2]. [2] https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/apimgt/admin-dashboard-web/1.2.2 On 12 May 2014 15:43, Sumedha Rubasinghe sume...@wso2.com wrote: +1 for 'admin-dashboard'. On Mon, May 12, 2014 at 3:39 PM, Nuwan Dias nuw...@wso2.com wrote: +1 for something like admin-dashboard. admin-console sounds more like the management console. Thanks, NuwanD. On Mon, May 12, 2014 at 3:26 PM, Ruwan Yatawara ruw...@wso2.com wrote: On Mon, May 12, 2014 at 3:10 PM, Lakmali Baminiwatta lakm...@wso2.comwrote: is Shall we make it admin-console / admin-dashboard ? Just admin does not have that a cool ring to it. :) Thanks and Regards, Ruwan Yatawara WSO2 Inc. email : ruw...@wso2.com mobile : +94 77 9110413 blog : http://thoughts.ruwan-ace.com/ www: :http://wso2.com -- Nuwan Dias Associate Tech Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 -- /sumedha m: +94 773017743 b : bit.ly/sumedha -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Generting a Unique-ID from a Unique String
Hi all, For tracking API invocations through Google Analytic, we need to send an unique ID based on the API token. As a solution,we can generate the MD5Sum value of the API token and send it as the unique ID. Is it fine to proceed with this approach or do we have a better way to achieve this? Appreciate any thoughts. Thanks, Lakmali -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Blocker] Issues with AM_DB scripts for Oracle
On 6 May 2014 23:18, Nirodha Pramod niro...@wso2.com wrote: Hi Lakmali, There is another blocking issue[6] with Oracle when generating Keys in store. Please have a look. regards, Nirodha [6] https://wso2.org/jira/browse/APIMANAGER-2302 Fixed in r202087and r202103. On Mon, May 5, 2014 at 9:38 PM, Lakmali Baminiwatta lakm...@wso2.comwrote: Hi, Please find the fixed oracle script attached. Thanks, Lakmali On 5 May 2014 21:11, Nirodha Pramod niro...@wso2.com wrote: Hi Lakmali, Can we have a patch for this issue [3] this is an absolute blocker for testing on Oracle. regards, Nirodha On Mon, May 5, 2014 at 10:56 AM, Lakmali Baminiwatta lakm...@wso2.comwrote: Hi, On 3 May 2014 00:26, Nirodha Pramod niro...@wso2.com wrote: Hi, Following two blocking issues were found with the oracle script for AM_DB on 29th April pack. Please have a look. [1] https://wso2.org/jira/browse/APIMANAGER-2266 Had been Fixed now. [2] https://wso2.org/jira/browse/APIMANAGER-2268 It seems this issue has occurred due to user not having permissions to create triggers. Fixed the issue[3] in r201794. [3] https://wso2.org/jira/browse/APIMANAGER-2264 Thanks, Lakmali regards, Nirodha -- *Nirodha Gallage* Senior Software Engineer, QA. WSO2 Inc.: http://wso2.com/ Mobile: +94716429078 -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com -- *Nirodha Gallage* Senior Software Engineer, QA. WSO2 Inc.: http://wso2.com/ Mobile: +94716429078 -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com -- *Nirodha Gallage* Senior Software Engineer, QA. WSO2 Inc.: http://wso2.com/ Mobile: +94716429078 -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Blocker] Issues with AM_DB scripts for Oracle
Hi, Please find the fixed oracle script attached. Thanks, Lakmali On 5 May 2014 21:11, Nirodha Pramod niro...@wso2.com wrote: Hi Lakmali, Can we have a patch for this issue [3] this is an absolute blocker for testing on Oracle. regards, Nirodha On Mon, May 5, 2014 at 10:56 AM, Lakmali Baminiwatta lakm...@wso2.comwrote: Hi, On 3 May 2014 00:26, Nirodha Pramod niro...@wso2.com wrote: Hi, Following two blocking issues were found with the oracle script for AM_DB on 29th April pack. Please have a look. [1] https://wso2.org/jira/browse/APIMANAGER-2266 Had been Fixed now. [2] https://wso2.org/jira/browse/APIMANAGER-2268 It seems this issue has occurred due to user not having permissions to create triggers. Fixed the issue[3] in r201794. [3] https://wso2.org/jira/browse/APIMANAGER-2264 Thanks, Lakmali regards, Nirodha -- *Nirodha Gallage* Senior Software Engineer, QA. WSO2 Inc.: http://wso2.com/ Mobile: +94716429078 -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com -- *Nirodha Gallage* Senior Software Engineer, QA. WSO2 Inc.: http://wso2.com/ Mobile: +94716429078 -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com oracle.sql Description: application/sql ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Blocker] Issues with AM_DB scripts for Oracle
Hi, On 6 May 2014 02:37, Charitha Kankanamge chari...@wso2.com wrote: CREATE TABLE AM_API_DEFAULT_VERSION ( DEFAULT_VERSION_ID INTEGER NOT NULL IDENTITY, API_NAME VARCHAR(256) NOT NULL , API_PROVIDER VARCHAR(256) NOT NULL , DEFAULT_API_VERSION VARCHAR(30) , PUBLISHED_DEFAULT_API_VERSION VARCHAR(30) , PRIMARY KEY (DEFAULT_VERSION_ID) ); used to continue testing in mssql setup. Please update the mssql script to work OOTB. MSSQL script had been already updated with AM_API_DEFAULT_VERSION table definition (r201440) . Thanks, Lakmali Charitha Kankanamge cell: +1 812-391-7730 http://charithaka.blogspot.com *SOA and Testing without nonsense* On Tue, May 6, 2014 at 2:32 AM, Charitha Kankanamge chari...@wso2.comwrote: Hi, Can we please have the corresponding MSSQL script as well? Charitha Kankanamge cell: +1 812-391-7730 http://charithaka.blogspot.com *SOA and Testing without nonsense* On Mon, May 5, 2014 at 9:38 PM, Lakmali Baminiwatta lakm...@wso2.comwrote: Hi, Please find the fixed oracle script attached. Thanks, Lakmali On 5 May 2014 21:11, Nirodha Pramod niro...@wso2.com wrote: Hi Lakmali, Can we have a patch for this issue [3] this is an absolute blocker for testing on Oracle. regards, Nirodha On Mon, May 5, 2014 at 10:56 AM, Lakmali Baminiwatta lakm...@wso2.comwrote: Hi, On 3 May 2014 00:26, Nirodha Pramod niro...@wso2.com wrote: Hi, Following two blocking issues were found with the oracle script for AM_DB on 29th April pack. Please have a look. [1] https://wso2.org/jira/browse/APIMANAGER-2266 Had been Fixed now. [2] https://wso2.org/jira/browse/APIMANAGER-2268 It seems this issue has occurred due to user not having permissions to create triggers. Fixed the issue[3] in r201794. [3] https://wso2.org/jira/browse/APIMANAGER-2264 Thanks, Lakmali regards, Nirodha -- *Nirodha Gallage* Senior Software Engineer, QA. WSO2 Inc.: http://wso2.com/ Mobile: +94716429078 -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com -- *Nirodha Gallage* Senior Software Engineer, QA. WSO2 Inc.: http://wso2.com/ Mobile: +94716429078 -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Blocker] Issues with AM_DB scripts for Oracle
Hi, On 3 May 2014 00:26, Nirodha Pramod niro...@wso2.com wrote: Hi, Following two blocking issues were found with the oracle script for AM_DB on 29th April pack. Please have a look. [1] https://wso2.org/jira/browse/APIMANAGER-2266 Had been Fixed now. [2] https://wso2.org/jira/browse/APIMANAGER-2268 It seems this issue has occurred due to user not having permissions to create triggers. Fixed the issue[3] in r201794. [3] https://wso2.org/jira/browse/APIMANAGER-2264 Thanks, Lakmali regards, Nirodha -- *Nirodha Gallage* Senior Software Engineer, QA. WSO2 Inc.: http://wso2.com/ Mobile: +94716429078 -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM Interceptor modification]
Hi Gayan,
On 22 April 2014 09:04, Gayan Gunawardana ga...@wso2.com wrote:
Hi,
I am working on altering org.wso2.carbon.apimgt.interceptor component
to support generic API formats. In the available version it supports only
one context noun before version therefore we cannot define APIs like
foo/bar/1.0.0
What I am doing is make it generic to support any sub context after root
context like a/b/c/d/1.0.0
The logic is to compare existing AM_API table records against current
request including version and pick up context, version from database
record. The logic works fine and I had to modify
interceptorOps.doThrottle(request, accessToken) --
interceptorOps.doThrottle(request, accessToken, context, apiVersion); to
pass context and version
now altered doThrottle method like
public boolean doThrottle(Request request, String accessToken, String
context, String version) throws APIFaultException {
String apiName = context;
String apiVersion = version;
String apiIdentifier = apiName + - + apiVersion;
APIThrottleHandler throttleHandler = null;
ConfigurationContext cc = DataHolder.getServerConfigContext();
if (cc.getProperty(apiIdentifier) == null) {
throttleHandler = new APIThrottleHandler();
/* Add the Throttle handler to ConfigContext against
API Identifier */
cc.setProperty(apiIdentifier, throttleHandler);
} else {
throttleHandler = (APIThrottleHandler)
cc.getProperty(apiIdentifier);
}
if (throttleHandler.doThrottle(request, apiKeyValidationDTO,
accessToken)) {
return true;
} else {
throw new
APIFaultException(APIManagerErrorConstants.API_THROTTLE_OUT,
You have exceeded your
quota);
}
}
What happen here is ConfigurationContext getting null and throws null
pointer exception. This can be avoided by doing simple null check but will
there be any side effects by doing it ?
If configuration context is null how can I invoke setProperty ?
As found while debugging, interceptor component activation doesn't complete
successfully due to some unsatisfied dependencies with the usage.publisher
component. As a result ConfigurationContext become null. We need to further
debug and find the root cause of this issue. I'll also have a look.
Thanks,
Lakmali
--
Gayan Gunawardana
Software Engineer; WSO2 Inc.; http://wso2.com/
Email: ga...@wso2.com
Mobile: +94 (71) 8020933
--
Lakmali Baminiwatta
Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile: +94 71 2335936
blog : lakmali.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Identifier is too long for Sequences and Triggers of some Identity tables
Yes. Fixed the same identifiers in apim scripts as well. Thanks, Lakmali On 11 April 2014 12:29, Chamath Gunawardana chama...@wso2.com wrote: Seems this is already fixed in identity-core feature. On Fri, Apr 11, 2014 at 12:10 PM, Chamath Gunawardana chama...@wso2.comwrote: Created https://wso2.org/jira/browse/IDENTITY-2143 On Fri, Apr 11, 2014 at 12:05 PM, Sumedha Rubasinghe sume...@wso2.comwrote: Let's use SEQ and TRG at the end. On Apr 11, 2014 11:50 AM, Lakmali Baminiwatta lakm...@wso2.com wrote: Hi all, Oracle is complaining with identifier is too long for below Sequences and Triggers. IDN_APPMGT_CLAIM_MAPPING_SEQUENCE IDN_APPMGT_CLAIM_MAPPING_TRIGGER IDN_APPMGT_ROLE_MAPPING_SEQUENCE IDN_APPMGT_ROLE_MAPPING_TRIGGER We need to change those to smaller names ( 30 chars). Thanks, Lakmali -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks, Best Regards, Chamath Gunawardana Technical Lead; WSO2 Inc. Mobile : +94776322240 -- Thanks, Best Regards, Chamath Gunawardana Technical Lead; WSO2 Inc. Mobile : +94776322240 -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Chunk08 Service Stubs build failure
Hi, In a clean repo I could build the stubs, but still getting the same error for org.wso2.carbon.identity.scim.common.stub. /home/lakmali/trunk/platform/branches/turing/service-stubs/org.wso2.carbon.identity.scim.common.stub/4.2.1/target/generated-code/src/org/wso2/carbon/identity/scim/common/stub/SCIMConfigAdminServiceStub.java:[239,25] cannot access javax.wsdl.Definition [ERROR] class file for javax.wsdl.Definition not found [ERROR] _serviceClient = new org.apache.axis2.client.ServiceClient(configurationContext,_service); [ERROR] - [Help 1] Thanks, Lakmali On 22 March 2014 11:09, Manoj Kumara ma...@wso2.com wrote: Hi, Recently we patched wsdl4j dependency as request by Suho. There we have done a version upgrade on that dependency. This might be due to this fix. @Suho, Can you please check your fix has effect on this. Thanks, Manoj *Manoj Kumara* Software Engineer WSO2 Inc. http://wso2.com/ *lean.enterprise.middleware* Mobile: +94713448188 On Fri, Mar 21, 2014 at 8:25 PM, Lakmali Baminiwatta lakm...@wso2.comwrote: Hi Ishara, Yes it is up to date (198854), but still getting this error. AlsoI am gettinng the same error for all the service stubs and noticed after updating and building the kernel patches. BTW I am not trying in a clean repo. Thanks, Lakmali On 21 March 2014 20:15, Ishara Premadasa ish...@wso2.com wrote: Hi Lakmail, Did you try with updating org.wso2.carbon.andes.stub in service-stubs and rebuild? I tried in a clean repo and this builds fine for me. Can you please try updating andes.stub/4.2.1? thanks! On Fri, Mar 21, 2014 at 7:58 PM, Lakmali Baminiwatta lakm...@wso2.comwrote: Hi all, I am getting below error while building the service stubs. Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (default-compile) on project org.wso2.carbon.andes.stub: Compilation failure [ERROR] /home/lakmali/trunk/platform/branches/turing/service-stubs/org.wso2.carbon.andes.stub/4.2.1/target/generated-code/src/org/wso2/carbon/andes/stub/AndesAdminServiceStub.java:[199,25] cannot access javax.wsdl.Definition [ERROR] class file for javax.wsdl.Definition not found [ERROR] _serviceClient = new org.apache.axis2.client.ServiceClient(configurationContext,_service); My kernel changes are up to date , but getting this error. Any idea? Thanks, Lakmali -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ishara Premasada Software Engineer, WSO2 Inc. http://wso2.com/ *Blog : http://isharapremadasa.blogspot.com/ http://isharapremadasa.blogspot.com/Twitter : https://twitter.com/ishadil https://twitter.com/ishadil Mobile : +94 714445832 %2B94%20714445832* -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] API Manager - 2.0.0 nightly build packs 23-03-2014
Hi, Please find $Subject in [1] [1]http://builder1.us1.wso2.org/~apim/23-03-2014/wso2am-2.0.0.zip Thanks, Lakmali -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Manager - 2.0.0 nightly build packs 23-03-2014
On 23 March 2014 02:08, Lakmali Baminiwatta lakm...@wso2.com wrote: Hi, Please find $Subject in [1] [1]http://builder1.us1.wso2.org/~apim/23-03-2014/wso2am-2.0.0.zip Please note that from next pack onwards, release version will be changed to 1.7.0. Thanks, Lakmali Thanks, Lakmali -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Tenant specific external store feature is totally broken in API-M 2.0.0
Hi Norodha, On 21 March 2014 17:46, Nirodha Pramod niro...@wso2.com wrote: Hi, This new feature is totally broken in the 14th March pack. Please see the below issues reported. [1] https://wso2.org/jira/browse/APIMANAGER-2081 [2] https://wso2.org/jira/browse/APIMANAGER-2082 Fixed above two issues. Will be available in the next pack. Thanks, Lakmali [3] https://wso2.org/jira/browse/APIMANAGER-2083 [4] https://wso2.org/jira/browse/APIMANAGER-2084 regards, Nirodha -- *Nirodha Gallage* Senior Software Engineer, QA. WSO2 Inc.: http://wso2.com/ Mobile: +94716429078 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Chunk08 Service Stubs build failure
Hi all, I am getting below error while building the service stubs. Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (default-compile) on project org.wso2.carbon.andes.stub: Compilation failure [ERROR] /home/lakmali/trunk/platform/branches/turing/service-stubs/org.wso2.carbon.andes.stub/4.2.1/target/generated-code/src/org/wso2/carbon/andes/stub/AndesAdminServiceStub.java:[199,25] cannot access javax.wsdl.Definition [ERROR] class file for javax.wsdl.Definition not found [ERROR] _serviceClient = new org.apache.axis2.client.ServiceClient(configurationContext,_service); My kernel changes are up to date , but getting this error. Any idea? Thanks, Lakmali -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Chunk08 Service Stubs build failure
Hi Ishara, Yes it is up to date (198854), but still getting this error. AlsoI am gettinng the same error for all the service stubs and noticed after updating and building the kernel patches. BTW I am not trying in a clean repo. Thanks, Lakmali On 21 March 2014 20:15, Ishara Premadasa ish...@wso2.com wrote: Hi Lakmail, Did you try with updating org.wso2.carbon.andes.stub in service-stubs and rebuild? I tried in a clean repo and this builds fine for me. Can you please try updating andes.stub/4.2.1? thanks! On Fri, Mar 21, 2014 at 7:58 PM, Lakmali Baminiwatta lakm...@wso2.comwrote: Hi all, I am getting below error while building the service stubs. Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (default-compile) on project org.wso2.carbon.andes.stub: Compilation failure [ERROR] /home/lakmali/trunk/platform/branches/turing/service-stubs/org.wso2.carbon.andes.stub/4.2.1/target/generated-code/src/org/wso2/carbon/andes/stub/AndesAdminServiceStub.java:[199,25] cannot access javax.wsdl.Definition [ERROR] class file for javax.wsdl.Definition not found [ERROR] _serviceClient = new org.apache.axis2.client.ServiceClient(configurationContext,_service); My kernel changes are up to date , but getting this error. Any idea? Thanks, Lakmali -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ishara Premasada Software Engineer, WSO2 Inc. http://wso2.com/ *Blog : http://isharapremadasa.blogspot.com/ http://isharapremadasa.blogspot.com/Twitter : https://twitter.com/ishadil https://twitter.com/ishadil Mobile : +94 714445832 %2B94%20714445832* -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Chunk08 org.wso2.carbon.identity.application.mgt.ui build failure
Hi, Getting below build failure in org.wso2.carbon.identity.application.mgt.ui [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project org.wso2.carbon.identity.application.mgt.ui: Compilation failure: Compilation failure: [ERROR] /home/lakmali/trunk/platform/branches/turing/components/identity/org.wso2.carbon.identity.application.mgt.ui/4.2.0/src/main/java/org/wso2/carbon/identity/application/mgt/ui/ApplicationConfigBean.java:[39,9] cannot find symbol [ERROR] symbol : class SystemIDPList [ERROR] location: class org.wso2.carbon.identity.application.mgt.ui.ApplicationConfigBean [ERROR] /home/lakmali/trunk/platform/branches/turing/components/identity/org.wso2.carbon.identity.application.mgt.ui/4.2.0/src/main/java/org/wso2/carbon/identity/application/mgt/ui/ApplicationConfigBean.java:[183,8] cannot find symbol [ERROR] symbol : class SystemIDPList [ERROR] location: class org.wso2.carbon.identity.application.mgt.ui.ApplicationConfigBean [ERROR] /home/lakmali/trunk/platform/branches/turing/components/identity/org.wso2.carbon.identity.application.mgt.ui/4.2.0/src/main/java/org/wso2/carbon/identity/application/mgt/ui/ApplicationConfigBean.java:[187,27] cannot find symbol [ERROR] symbol : class SystemIDPList [ERROR] location: class org.wso2.carbon.identity.application.mgt.ui.ApplicationConfigBean [ERROR] /home/lakmali/trunk/platform/branches/turing/components/identity/org.wso2.carbon.identity.application.mgt.ui/4.2.0/src/main/java/org/wso2/carbon/identity/application/mgt/ui/client/ApplicationManagementServiceClient.java:[34,50] cannot find symbol [ERROR] symbol : class SystemIDPList [ERROR] location: package org.wso2.carbon.identity.application.mgt.ui Please have a look. Thanks, Lakmali -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Commit to kernel patch006
Thanks Manoj. Sent a pull request to Git dev repo. Please review and commit. Thanks, Lakmali On 14 March 2014 15:33, Manoj Kumara ma...@wso2.com wrote: Hi, Committed to patch0006 with 198373. Please add your changes to Git dev repo as well [1] [1] https://github.com/wso2-dev/carbon4-kernel Thanks, Manoj *Manoj Kumara* Software Engineer WSO2 Inc. http://wso2.com/ *lean.enterprise.middleware* Mobile: +94713448188 On Thu, Mar 13, 2014 at 6:42 PM, Lakmali Baminiwatta lakm...@wso2.comwrote: Hi Manoj, Please apply the attached patch fixing a debug log related to [1]. Patch goes to patch0006/core/org.wso2.carbon.user.core/4.2.0 [1] https://wso2.org/jira/browse/CARBON-14729 Thanks, Lakmali -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Chunk08 build failure in org.wso2.carbon.event.input.adaptor.kafka
Hi all, I am getting below build failure when building org.wso2.carbon.event.input.adaptor.kafka. Any idea how to get resolve this issue? BUILD FAILURE [INFO] [INFO] Total time: 4.581s [INFO] Finished at: Fri Mar 14 17:52:41 IST 2014 [INFO] Final Memory: 61M/1237M [INFO] [ERROR] Failed to execute goal on project org.wso2.carbon.event.input.adaptor.kafka: Could not resolve dependencies for project org.wso2.carbon:org.wso2.carbon.event.input.adaptor.kafka:bundle:1.0.0: Could not transfer artifact com.sun.jmx:jmxri:jar:1.2.1 from/to java.net ( https://maven-repository.dev.java.net/nonav/repository): No connector available to access repository java.net ( https://maven-repository.dev.java.net/nonav/repository) of type legacy using the available factories WagonRepositoryConnectorFactory - [Help 1] Thanks, Lakmali -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Chunk08 build failure in org.wso2.carbon.event.input.adaptor.kafka
It is fixed now. Thanks.. On 14 March 2014 18:12, Mohanadarshan Vivekanandalingam mo...@wso2.comwrote: Fixed in r198405.. Please check now.. Regards, Mohan On Fri, Mar 14, 2014 at 5:59 PM, Lakmali Baminiwatta lakm...@wso2.comwrote: Hi all, I am getting below build failure when building org.wso2.carbon.event.input.adaptor.kafka. Any idea how to get resolve this issue? BUILD FAILURE [INFO] [INFO] Total time: 4.581s [INFO] Finished at: Fri Mar 14 17:52:41 IST 2014 [INFO] Final Memory: 61M/1237M [INFO] [ERROR] Failed to execute goal on project org.wso2.carbon.event.input.adaptor.kafka: Could not resolve dependencies for project org.wso2.carbon:org.wso2.carbon.event.input.adaptor.kafka:bundle:1.0.0: Could not transfer artifact com.sun.jmx:jmxri:jar:1.2.1 from/to java.net( https://maven-repository.dev.java.net/nonav/repository): No connector available to access repository java.net ( https://maven-repository.dev.java.net/nonav/repository) of type legacy using the available factories WagonRepositoryConnectorFactory - [Help 1] Thanks, Lakmali -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com -- *V. Mohanadarshan* *Software Engineer,* *Data Technologies Team,* *WSO2, Inc. http://wso2.com http://wso2.com * *lean.enterprise.middleware.* email: mo...@wso2.com phone:(+94) 771117673 -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] API Manager - 2.0.0 nightly build packs 14-03-2014
Hi, Please find $Subject in [1] [1] http://builder1.us1.wso2.org/~apim/14-03-2014/wso2am-2.0.0.zip Thanks, Lakmali -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Commit to kernel patch006
Hi Manoj,
Please apply the attached patch fixing a debug log related to [1].
Patch goes to patch0006/core/org.wso2.carbon.user.core/4.2.0
[1] https://wso2.org/jira/browse/CARBON-14729
Thanks,
Lakmali
--
Lakmali Baminiwatta
Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile: +94 71 2335936
blog : lakmali.com
Index: src/main/java/org/wso2/carbon/user/core/ldap/ReadOnlyLDAPUserStoreManager.java
===
--- src/main/java/org/wso2/carbon/user/core/ldap/ReadOnlyLDAPUserStoreManager.java (revision 198277)
+++ src/main/java/org/wso2/carbon/user/core/ldap/ReadOnlyLDAPUserStoreManager.java (working copy)
@@ -2111,11 +2111,15 @@
if(debug) {
if(list != null) {
+ boolean isUserInRole = false;
for(String item : list) {
log.debug(Result: + item);
+if(item.equalsIgnoreCase(roleName)) {
+ isUserInRole = true;
+}
}
log.debug(Is user: + userName + in role: + roleName + ? +
- list.contains(roleName));
+ isUserInRole);
} else {
log.debug(No results found !);
}
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] API Manager - 2.0.0 nightly build packs 07-03-2014
Hi, Please find $Subject in [1] [1]http://builder1.us1.wso2.org/~apim/07-03-2014/wso2am-2.0.0.zip Thanks, Lakmali -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Manager - 2.0.0 nightly build packs 28-02-2014
Hi, On 6 March 2014 10:53, Chamara Ariyarathne chama...@wso2.com wrote: Can we start the testing for the release with this pack? Or is there a new build? Please let us know. This is the latest pack we have. So you can start testing this. We are planning to build a new pack Tomorrow. Thanks, Lakmali On Fri, Feb 28, 2014 at 9:23 PM, Lakmali Baminiwatta lakm...@wso2.comwrote: Hi, Please find $Subject in [1] [1]http://builder1.us1.wso2.org/~apim/28-02-2014/wso2am-2.0.0.zip Thanks, Lakmali -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Chamara Ariyarathne* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. Mobile; *+94772786766 %2B94772786766* -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] API Manager - 2.0.0 nightly build packs 28-02-2014
Hi, Please find $Subject in [1] [1]http://builder1.us1.wso2.org/~apim/28-02-2014/wso2am-2.0.0.zip Thanks, Lakmali -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] API Manager - 2.0.0 nightly build packs 21-02-2014
Hi, Please find $Subject in [1] [1] http://builder1.us1.wso2.org/~apim/21-02-2014/wso2am-2.0.0.zip Thanks, Lakmali -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Customizing properties of jwt assertion.
Hi Pushpalanka,
The claims in the sample assertion you have stated(applicationId, enduser,
etc) are derived from the API key. Then by using the 'enduser' value, that
user's claims are retrieved [1]. AFAIK those claims will be added to the
JWT token, if that claim had a value only. For example if you signup a new
user through API Store Signup page, you can give values to claims such as
firstname, lastname, etc. So when invoking from that newly added user's
token, JWT assertion will have those claims as well.
ex:
{iss:wso2.org/products/am,exp:1389711373801,
http://wso2.org/claims/subscriber:lakmali,;
http://wso2.org/claims/applicationid:9,;
http://wso2.org/claims/applicationname:DefaultApplication,;
http://wso2.org/claims/applicationtier:Unlimited,;
http://wso2.org/claims/apicontext:/findfeeds,;
http://wso2.org/claims/version:1.0,http://wso2.org/claims/tier:Gold,;
http://wso2.org/claims/keytype:PRODUCTION,;
http://wso2.org/claims/usertype:APPLICATION,;
http://wso2.org/claims/enduser:lakmali,;
http://wso2.org/claims/enduserTenantId:-1234;,
http://wso2.org/claims/custom:hello;, http://wso2.org/claims/emailaddress
:lakm...@wso2.com, http://wso2.org/claims/givenname:Lakmali;,
http://wso2.org/claims/lastname:Erandi;, http://wso2.org/claims/role
:subscriber,Internal/identity,Internal/everyone}
You can add new claim as Suresh mentioned. But we need to think about to
how to set the value to that new claim. If your requirement is to manually
add the value to new claim, then you can install User Profile feature and
add values to new claims.
[1]
https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.0/src/main/java/org/wso2/carbon/apimgt/impl/token/JWTGenerator.java
Thanks,
Lakmali
On 12 January 2014 08:08, Pushpalanka Jayawardhana la...@wso2.com wrote:
Thanks, I ll try out that.
Regards,
Pushapalanka
On Sat, Jan 11, 2014 at 1:09 AM, Suresh Attanayaka sur...@wso2.comwrote:
If you need to have a new claim, you can define it in the correct claim
dialect and map it to a LDAP attribute. So then the JWT claims retriever
will add that to the JWT. For ex, in this case
*http://wso2.org/claims/enduserWithoutTenant
http://wso2.org/claims/enduserWithoutTenant can be mapped to cn or uid.*
On Saturday, January 11, 2014, Pushpalanka Jayawardhana wrote:
Hi,
Is it possible to add a custom property to the JWT assertion as follows.
{
iss:wso2.org/products/am,
exp:1389378210204,
http://wso2.org/claims/subscriber:admin;,
http://wso2.org/claims/applicationid:1;,
http://wso2.org/claims/applicationname:DefaultApplication;,
http://wso2.org/claims/applicationtier:Unlimited;,
http://wso2.org/claims/apicontext:/pizzashack/menu;,
http://wso2.org/claims/version:1.0.0;,
http://wso2.org/claims/tier:Bronze;,
http://wso2.org/claims/keytype:PRODUCTION;,
http://wso2.org/claims/usertype:APPLICATION_USER;,
http://wso2.org/claims/enduser:admin@carbon.super;,
*http://wso2.org/claims/enduserWithoutTenant
http://wso2.org/claims/enduserWithoutTenant:admin,*
--
Suresh Attanayake
Senior Software Engineer; WSO2 Inc. http://wso2.com/
Blog : http://sureshatt.blogspot.com/
Web : http://www.ssoarcade.com/
Facebook : https://www.facebook.com/IdentityWorld
Twitter : https://twitter.com/sureshatt
LinkedIn : http://lk.linkedin.com/in/sureshatt
Mobile : +94755012060
Mobile : +016166171172
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Lakmali Baminiwatta
Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile: +94 71 2335936
blog : lakmali.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Test failures in synapse-commons
Hi Isuru, On 18 December 2013 15:10, Isuru Udana isu...@wso2.com wrote: Hi Dinusha, Synapse version 2.1.2.wso2v2 builds fine with tests in a clean repo. This is the version we released in chunk-04 with ESB 4.8.0 release. It looks like 2.1.2.wso2v3 has branched incorrectly. v3 was not created from the released revision of the v2. Please take necessary actions to make sure v3 has all the fixes done for v2. Looking into this. Thanks, Lakmali Thanks. On Wed, Dec 18, 2013 at 11:45 AM, Dinusha Senanayaka dinu...@wso2.comwrote: Hi, Getting following test failures in synapse.commons.executors module while building the dependencies. Surefire report attached herewith . Can someone from the esb team check it please ? Tests run: 17, Failures: 5, Errors: 0, Skipped: 0, Time elapsed: 0.501 sec FAILURE! Running org.apache.synapse.commons.executors.MultiPriorityBlockingQueueTest Results : Tests run: 77, Failures: 5, Errors: 0, Skipped: 0 Regards, Dinusha. -- Dinusha Dilrukshi Senior Software Engineer WSO2 Inc.: http://wso2.com/ Mobile: +94725255071 Blog: http://dinushasblog.blogspot.com/ -- *Isuru Udana* Senior * Software Engineer* WSO2 Inc.; http://wso2.com email: isu...@wso2.com cell: +94 77 3791887 blog: http://mytecheye.blogspot.com/ twitter: http://twitter.com/isudana -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Test failures in synapse-commons
Hi all, On 18 December 2013 15:21, Lakmali Baminiwatta lakm...@wso2.com wrote: Hi Isuru, On 18 December 2013 15:10, Isuru Udana isu...@wso2.com wrote: Hi Dinusha, Synapse version 2.1.2.wso2v2 builds fine with tests in a clean repo. This is the version we released in chunk-04 with ESB 4.8.0 release. It looks like 2.1.2.wso2v3 has branched incorrectly. v3 was not created from the released revision of the v2. Please take necessary actions to make sure v3 has all the fixes done for v2. Looking into this. Re-branched synapse 2.1.2.wso2v3 copied from relased 2.1.2.wso2v2. Then re-applied the fixes went on r192779, r192772, r192681. Thanks, Lakmali Thanks. On Wed, Dec 18, 2013 at 11:45 AM, Dinusha Senanayaka dinu...@wso2.comwrote: Hi, Getting following test failures in synapse.commons.executors module while building the dependencies. Surefire report attached herewith . Can someone from the esb team check it please ? Tests run: 17, Failures: 5, Errors: 0, Skipped: 0, Time elapsed: 0.501 sec FAILURE! Running org.apache.synapse.commons.executors.MultiPriorityBlockingQueueTest Results : Tests run: 77, Failures: 5, Errors: 0, Skipped: 0 Regards, Dinusha. -- Dinusha Dilrukshi Senior Software Engineer WSO2 Inc.: http://wso2.com/ Mobile: +94725255071 Blog: http://dinushasblog.blogspot.com/ -- *Isuru Udana* Senior * Software Engineer* WSO2 Inc.; http://wso2.com email: isu...@wso2.com cell: +94 77 3791887 blog: http://mytecheye.blogspot.com/ twitter: http://twitter.com/isudana -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Manager nightly build pack - 09/12/2013
.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141) at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936) at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908 [1] https://wso2.org/jira/browse/APIMANAGER-1843 Regards, /Pavithra On Tue, Dec 10, 2013 at 2:33 PM, Dinusha Senanayaka dinu...@wso2.comwrote: Hi All, Please find the $subject in [1]. [1]. http://builder1.us1.wso2.org/~apim/09-12-2013/wso2am-1.6.0.zip Regards, Dinusha. -- Dinusha Dilrukshi Senior Software Engineer WSO2 Inc.: http://wso2.com/ Mobile: +94725255071 Blog: http://dinushasblog.blogspot.com/ -- *Pavithra Madurangi* Senior Software Engineer - QA. WSO2 Inc.: http://wso2.com/ Mobile: +94777207357 -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Build Failure org.wso2.carbon.identity.authenticator.saml2.sso.common - Chunk06
Hi, Getting following build failure from org.wso2.carbon.identity.authenticator.saml2.sso.common component. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 14.559s [INFO] Finished at: Mon Dec 09 17:46:48 IST 2013 [INFO] Final Memory: 12M/981M [INFO] [ERROR] Failed to execute goal on project org.wso2.carbon.identity.authenticator.saml2.sso.common: Could not resolve dependencies for project org.wso2.carbon:org.wso2.carbon.identity.authenticator.saml2.sso.common:bundle:4.2.1: Could not find artifact org.wso2.carbon:org.wso2.carbon.identity.authenticator.saml2.sso.stub:jar:4.2.1 in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException Thanks, Lakmali -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Build Failure org.wso2.carbon.identity.authenticator.saml2.sso.common - Chunk06
Hi, Since org.wso2.carbon.identity.authenticator.saml2.sso.stub:jar:4.2.1 is not available in the svn, I reverted the version upgrade as a temprary fix (in r192821). Thanks, Lakmali On 9 December 2013 17:52, Lakmali Baminiwatta lakm...@wso2.com wrote: Hi, Getting following build failure from org.wso2.carbon.identity.authenticator.saml2.sso.common component. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 14.559s [INFO] Finished at: Mon Dec 09 17:46:48 IST 2013 [INFO] Final Memory: 12M/981M [INFO] [ERROR] Failed to execute goal on project org.wso2.carbon.identity.authenticator.saml2.sso.common: Could not resolve dependencies for project org.wso2.carbon:org.wso2.carbon.identity.authenticator.saml2.sso.common:bundle:4.2.1: Could not find artifact org.wso2.carbon:org.wso2.carbon.identity.authenticator.saml2.sso.stub:jar:4.2.1 in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException Thanks, Lakmali -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Limitations with Cache Mediator
Hi Sanjeewa, On 6 December 2013 07:48, Sanjeewa Malalgoda sanje...@wso2.com wrote: On Mon, Dec 2, 2013 at 6:23 PM, Lakmali Baminiwatta lakm...@wso2.comwrote: Hi, On 2 December 2013 18:02, Sumedha Rubasinghe sume...@wso2.com wrote: On Mon, Dec 2, 2013 at 5:24 PM, Lakmali Baminiwatta lakm...@wso2.comwrote: Hi Sanjeewa, On 2 December 2013 17:00, Sanjeewa Malalgoda sanje...@wso2.com wrote: On Sun, Dec 1, 2013 at 11:01 PM, Lakmali Baminiwatta lakm...@wso2.com wrote: Hi all, When processing the response, if the request is REST then soap format, transport headers and message type are also stored. Similarly when retrieving the cached response, if the request is REST then stored values are used to compose the response message. With these modifications cache mediator returns the response correctly for non SOAP requests. But we have another issue here. Currently the request Hash value is derived from the SOAP message body. So for REST calls it gets the same hash value for all requests which sent without a payload. ex: Both below requests are recognized as the same request according to the hash value derived from DOMHASHGenerator. curl -v -H Authorization: Bearer 1EV6Qqa_DboaBzNj2JfiyXoO1Ysa http://localhost:8280/test/1.0.0?regNo=001 curl -v -H Authorization: Bearer 1EV6Qqa_DboaBzNj2JfiyXoO1Ysa http://localhost:8280/test/1.0.0?regNo=002http://localhost:8280/test/1.0.0?regNo=001 So right now we need to figure out a mechanism to generate hash value for REST calls. How if we consider full request path(including query params and etc) + headers. For above example something like follows (full request path and , separated transport headers list). We can compute hash value of that string and store it. *http://localhost:8280/test/1.0.0?regNo=002,Authorization http://localhost:8280/test/1.0.0?regNo=002,Authorization: Bearer 1EV6Qqa_DboaBzNj2JfiyXoO1Ysa* Here we cannot only consider full request path as we take some decisions at backend based on headers. WDYT? Yeah, need to consider request path + headers. But I think we don't need hash Authorization headers, as request hits the cache mediator after going through the handlers. So in default case, at the time of hashing we don't have the authorization header. So AFAIU, the only concern which comes up here is, same request invoked using different keys may get the response from the cache. I believe that is ok. WDYT? We simply store response values against a given request pattern. But Authorisation header should not be part of it. Otherwise it will become a token based cache. But are whole lot of other header parameter like content-type, accept header, accept language ( http://en.wikipedia.org/wiki/List_of_HTTP_header_fields). Let's ignore Authorisation header for time being. +1. So for now let's generate the hash based on request path, Accept Content-Type headers and payload (if available). +1. IMO we should use all other headers except authentication headers (Ex. sometimes response may depend on client type or sometimes it may depend on any other custom header). We can use all the headers [1]. But there are some headers which seems not correct to use for hashing the request. ex: Date - This is unique for each request. If this is used for generting the hash, cache will be never used. User-Agent - This is specific to the user client/browser who sent the request. So different caches for different users. So I think we need to figure out which headers to skip or which headers to use for hash generation. [1]http://en.wikipedia.org/wiki/List_of_HTTP_header_fields Thanks, Lakmali Thanks, sanjeewa. Thanks, Lakmali I am writing a new Digest Generator implementation by extending DOMHASHGenerator. This basically does what DOMHASHGenerator had been doing and additionally it digests request path and available transport headers as well. Thanks, Lakmali Thanks, sanjeewa. Thanks, Lakmali On 29 November 2013 00:18, Lakmali Baminiwatta lakm...@wso2.comwrote: Hi all, Currently Cache mediator stores the response message as a byte array and builds the soap envelope from that when sending the cached response[1]. When building the response, it checks whether the request format is in SOAP11 or SOAP12 and do the build accordingly. For SOAP requests, the SOAP format for response and request messages are same since most of the time a WSDL is used. So above logic works. But the response message for REST calls may be in different SOAP formats than the request. This results in errors when building the message. ex: Below REST call's request message context is SOAP12. But the response SOAP envelope is SOAP11. Hence building the message throws an exception. curl -v -H Authorization: Bearer 1EV6Qqa_DboaBzNj2JfiyXoO1Ysa http://localhost:8280/test/1.0.0?regNo=001 Further Content-Type of the responses can be different (ex: application/xml, application/json). So
Re: [Dev] Limitations with Cache Mediator
Hi Sanjeewa, On 2 December 2013 17:00, Sanjeewa Malalgoda sanje...@wso2.com wrote: On Sun, Dec 1, 2013 at 11:01 PM, Lakmali Baminiwatta lakm...@wso2.comwrote: Hi all, When processing the response, if the request is REST then soap format, transport headers and message type are also stored. Similarly when retrieving the cached response, if the request is REST then stored values are used to compose the response message. With these modifications cache mediator returns the response correctly for non SOAP requests. But we have another issue here. Currently the request Hash value is derived from the SOAP message body. So for REST calls it gets the same hash value for all requests which sent without a payload. ex: Both below requests are recognized as the same request according to the hash value derived from DOMHASHGenerator. curl -v -H Authorization: Bearer 1EV6Qqa_DboaBzNj2JfiyXoO1Ysa http://localhost:8280/test/1.0.0?regNo=001 curl -v -H Authorization: Bearer 1EV6Qqa_DboaBzNj2JfiyXoO1Ysa http://localhost:8280/test/1.0.0?regNo=002http://localhost:8280/test/1.0.0?regNo=001 So right now we need to figure out a mechanism to generate hash value for REST calls. How if we consider full request path(including query params and etc) + headers. For above example something like follows (full request path and , separated transport headers list). We can compute hash value of that string and store it. *http://localhost:8280/test/1.0.0?regNo=002,Authorization http://localhost:8280/test/1.0.0?regNo=002,Authorization: Bearer 1EV6Qqa_DboaBzNj2JfiyXoO1Ysa* Here we cannot only consider full request path as we take some decisions at backend based on headers. WDYT? Yeah, need to consider request path + headers. But I think we don't need hash Authorization headers, as request hits the cache mediator after going through the handlers. So in default case, at the time of hashing we don't have the authorization header. So AFAIU, the only concern which comes up here is, same request invoked using different keys may get the response from the cache. I believe that is ok. WDYT? I am writing a new Digest Generator implementation by extending DOMHASHGenerator. This basically does what DOMHASHGenerator had been doing and additionally it digests request path and available transport headers as well. Thanks, Lakmali Thanks, sanjeewa. Thanks, Lakmali On 29 November 2013 00:18, Lakmali Baminiwatta lakm...@wso2.com wrote: Hi all, Currently Cache mediator stores the response message as a byte array and builds the soap envelope from that when sending the cached response[1]. When building the response, it checks whether the request format is in SOAP11 or SOAP12 and do the build accordingly. For SOAP requests, the SOAP format for response and request messages are same since most of the time a WSDL is used. So above logic works. But the response message for REST calls may be in different SOAP formats than the request. This results in errors when building the message. ex: Below REST call's request message context is SOAP12. But the response SOAP envelope is SOAP11. Hence building the message throws an exception. curl -v -H Authorization: Bearer 1EV6Qqa_DboaBzNj2JfiyXoO1Ysa http://localhost:8280/test/1.0.0?regNo=001 Further Content-Type of the responses can be different (ex: application/xml, application/json). So I think we should store the actual SOAP format and the Content-Type of the response than just storing the response envelope. One option would be to store them in CachableResponse object[2] (May be in a property map?) Any better way to fix this? [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/dependencies/synapse/2.1.2-wso2v2/modules/core/src/main/java/org/apache/synapse/mediators/builtin/CacheMediator.java [2] https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/dependencies/commons/caching/4.0.2/modules/core/src/main/java/org/wso2/caching/CachableResponse.java Thanks, Lakmali On 22 November 2013 15:59, Sumedha Rubasinghe sume...@wso2.com wrote: Dinusha, Did you identify what needs to be fixed? I think ESB team is busy with a release. On Thu, Nov 21, 2013 at 7:09 PM, Dinusha Senanayaka dinu...@wso2.comwrote: Hi All, We are trying to add response caching as a default feature in API Manager using Cache mediator. There, we found that Cache mediator could handle only SOAP-1.1 or SOAP-1.2 messages. - If backend returns a POX response, it throws the following exception [1] when request is served from the cache. - If backend returns a JSON response, and once the response get added to cache, client does not receive a response until cache expires. (No backend errors) Is it possible to fix those for API Manager-1.6.0 release ? [1] [2013-11-21 13:33:18,044] ERROR - NativeWorkerPool Uncaught exception org.apache.axiom.soap.SOAPProcessingException: Transport level information does not match with SOAP Message
