Re: [Dev] Mail Attachment
Hi Amit, Now you can able to send the email with the attachment. You can download the new connector from[1] and the documentation about sending the email with attachment can be found in[2] [1] - https://store.wso2.com/store/assets/esbconnector/details/74539b71-3b72-49c1-a21a-f08ad7d7d4ad [2] - https://docs.wso2.com/display/ESBCONNECTORS/Working+with+Messages+in+Gmail#WorkingwithMessagesinGmail-sendMailWithAttachment On Mon, Jul 24, 2017 at 9:46 AM, Amit Rajvanshi <arajvan...@salmon.com> wrote: > Hi Malaka, > > > > We are sending Email through ESB SMTP transport, I know that we can send > body as attachment through ESB but > > We need to send mail body and attachment together for notification purpose. > > > > *Scenario is* : we need to notify customer for processing of import file > through mail and need to attach Carbon log file as attachment. > > Which is present @ wso2esb-5.0.0\repository\logs\wso2carbon.log > > > > I am using below property for attachment : > > > > value=*"Attachment"*/> > > > > > > Which actually send mail body as attachment. But we cannot send mail body > with it. > > Best regards, > *Amit Rajvanshi* > > *Technical Consultant* > *Office: *+91-120-4737401 <+91%20120%20473%207401> > > *Mobile*: +91 9871001235 <+91%2098710%2001235> > > *Email*:arajvan...@salmon.com > > [image: cid:image003.png@01D2CA89.60AB8730] <https://salmon.com/in-en/> > > > > *[image: cid:image004.jpg@01D2CA89.60AB8730]* > <https://twitter.com/Salmon_India> *[image: > cid:image005.jpg@01D2CA89.60AB8730]* > <https://www.linkedin.com/company/salmon-india> *[image: > cid:image006.jpg@01D2CA89.60AB8730]* > <https://plus.google.com/116105780357981423232> *[image: > cid:image007.jpg@01D2CA89.60AB8730]* > <https://www.facebook.com/SalmonIndiaLtd/> *[image: > cid:image008.jpg@01D2CA89.60AB8730]* <http://www.pinterest.com/salmonltd/> > *[image: cid:image009.jpg@01D2CA89.60AB8730]* > <https://www.youtube.com/user/salmonlimited> *[image: > cid:image010.jpg@01D2CA89.60AB8730]* <http://www.slideshare.net/salmonltd> > > > > Information contained in this e-mail and any attachments is confidential > and intended for the use of the addressee only. Dissemination, > distribution, copying or use of this communication without prior permission > of the addressee is strictly prohibited. If you have received this > transmission in error, please advise the originator by reply e-mail and > delete it. Thank you. Salmon India’s Registered Address is: B-13, Sector > 57, Noida (U.P.) 201301. Registered in India U72200DL2003PTC120356. > > > > *From:* Malaka Silva [mailto:mal...@wso2.com] > *Sent:* 21 July 2017 19:59 > *To:* WSO2 Developers' List > *Cc:* Amit Rajvanshi; Hariprasath Thanarajah > *Subject:* Fwd: Mail Attachment > > > > Hi Amit, > > > > Can you provide more details how are you sending the mail. Are you using > ESB SMTP transport or GMail connector? > > > > We can send messages with attachments using gmail connector. [1] > > > > @Haprprasath - Can we do the same use case with GMail connector? > > > > [1] https://docs.wso2.com/display/ESBCONNECTORS/Working+ > with+Messages+in+Gmail#WorkingwithMessagesinGmail-sendMailWithAttachment > > > > + wso2 dev > > > > -- Forwarded message -- > From: *Amit Rajvanshi* <arajvan...@salmon.com> > Date: Fri, Jul 21, 2017 at 2:45 PM > Subject: Mail Attachment > To: Malaka Silva <mal...@wso2.com> > > Hi Malaka, > > > > Could you please help me , I have stuck in the middle of development in > WSO2 ESB. > > I need to attach a file (available on system directory) while sending the > mail through a sequence mediator. > > Any reference will be appreciated. > > > > Best regards, > *Amit Rajvanshi* > > *Technical Consultant* > *Office: *+91-120-4737401 <+91%20120%20473%207401> > > *Mobile*: +91 9871001235 <+91%2098710%2001235> > > *Email*:arajvan...@salmon.com > > [image: cid:image003.png@01D2CA89.60AB8730] <https://salmon.com/in-en/> > > > > *[image: cid:image004.jpg@01D2CA89.60AB8730]* > <https://twitter.com/Salmon_India> *[image: > cid:image005.jpg@01D2CA89.60AB8730]* > <https://www.linkedin.com/company/salmon-india> *[image: > cid:image006.jpg@01D2CA89.60AB8730]* > <https://plus.google.com/116105780357981423232> *[image: > cid:image007.jpg@01D2CA89.60AB8730]* > <https://www.facebook.com/SalmonIndiaLtd/> *[image: > cid:image008.jpg@01D2CA89.60AB8730]* <http://www.pinterest.com/salmon
Re: [Dev] Mail Attachment
Hi Malaka, For the moment we can't able send a mail with attachment using gmail connector. The issue can be track in the public jira[1], [1] - https://wso2.org/jira/browse/ESBCONNECT-214 On Fri, Jul 21, 2017 at 7:59 PM, Malaka Silva <mal...@wso2.com> wrote: > Hi Amit, > > Can you provide more details how are you sending the mail. Are you using > ESB SMTP transport or GMail connector? > > We can send messages with attachments using gmail connector. [1] > > @Haprprasath - Can we do the same use case with GMail connector? > > [1] https://docs.wso2.com/display/ESBCONNECTORS/Working+ > with+Messages+in+Gmail#WorkingwithMessagesinGmail-sendMailWithAttachment > > + wso2 dev > > -- Forwarded message -- > From: Amit Rajvanshi <arajvan...@salmon.com> > Date: Fri, Jul 21, 2017 at 2:45 PM > Subject: Mail Attachment > To: Malaka Silva <mal...@wso2.com> > > > Hi Malaka, > > > > Could you please help me , I have stuck in the middle of development in > WSO2 ESB. > > I need to attach a file (available on system directory) while sending the > mail through a sequence mediator. > > Any reference will be appreciated. > > > > Best regards, > *Amit Rajvanshi* > > *Technical Consultant* > *Office: *+91-120-4737401 <+91%20120%20473%207401> > > *Mobile*: +91 9871001235 <+91%2098710%2001235> > > *Email*:arajvan...@salmon.com > > [image: cid:image003.png@01D2CA89.60AB8730] <https://salmon.com/in-en/> > > > > *[image: cid:image004.jpg@01D2CA89.60AB8730]* > <https://twitter.com/Salmon_India> *[image: > cid:image005.jpg@01D2CA89.60AB8730]* > <https://www.linkedin.com/company/salmon-india> *[image: > cid:image006.jpg@01D2CA89.60AB8730]* > <https://plus.google.com/116105780357981423232> *[image: > cid:image007.jpg@01D2CA89.60AB8730]* > <https://www.facebook.com/SalmonIndiaLtd/> *[image: > cid:image008.jpg@01D2CA89.60AB8730]* <http://www.pinterest.com/salmonltd/> > *[image: cid:image009.jpg@01D2CA89.60AB8730]* > <https://www.youtube.com/user/salmonlimited> *[image: > cid:image010.jpg@01D2CA89.60AB8730]* <http://www.slideshare.net/salmonltd> > > > > Information contained in this e-mail and any attachments is confidential > and intended for the use of the addressee only. Dissemination, > distribution, copying or use of this communication without prior permission > of the addressee is strictly prohibited. If you have received this > transmission in error, please advise the originator by reply e-mail and > delete it. Thank you. Salmon India’s Registered Address is: B-13, Sector > 57, Noida (U.P.) 201301. Registered in India U72200DL2003PTC120356. > > > Information contained in this e-mail and any attachments is confidential > and intended for the use of the addressee only. Dissemination, > distribution, copying or use of this communication without prior permission > of the addressee is strictly prohibited. If you have received this > transmission in error, please advise the originator by reply e-mail and > delete it. Thank you. Salmon India’s Registered Address is: B-13, Sector > 57, Noida (U.P.) 201301. Registered in India U72200DL2003PTC120356. > > > > -- > > Best Regards, > > Malaka Silva > Associate Director / Architect > M: +94 777 219 791 <+94%2077%20721%209791> > Tel : 94 11 214 5345 > Fax :94 11 2145300 > Skype : malaka.sampath.silva > LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 > Blog : http://mrmalakasilva.blogspot.com/ > > WSO2, Inc. > lean . enterprise . middleware > https://wso2.com/signature > http://www.wso2.com/about/team/malaka-silva/ > <http://wso2.com/about/team/malaka-silva/> > https://store.wso2.com/store/ > > Don't make Trees rare, we should keep them with care > -- *Thank you and Regards,**Hariprasath Thanarajah* Software Engineer | WSO2 E: haripras...@wso2.com M: +94 75 2806528, +94 77 7216903 Blog: hariwso2.blogspot.com Skype : hariss636 LinkedIn : https://www.linkedin.com/in/hariprasath-thanarajah-5234b660 WSO2, Inc. lean . enterprise . middleware https://wso2.com/signature http://wso2.com/about/team/hariprashath-thanarajah/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Regarding the messageContext creation for Custom Inbounds
[-support-dev][+dev] On Fri, Jul 21, 2017 at 11:58 AM, Hariprasath Thanarajah < haripras...@wso2.com> wrote: > Hi All, > > When we extend the GenericPollingConsumer, ListeningConsumer or > EventBasedConsumer to create a custom inbound for ESB there we don't have a > method to pass the messageContext in that particular class[1]. In the > custom inbound, we have a requirement to set the property in the > messageContext[2] and need gets the values from the sequence For that we > need to override the injectMessage method within the custom inbound[3]. > > One way to overcome this we can create a utility method to create the > message context and for the injectMessage we can pass the messageContext in > the GenericPollingConsumer. > > Any thoughts? > > [1] - https://github.com/wso2/carbon-mediation/blob/master/ > components/inbound-endpoints/org.wso2.carbon.inbound. > endpoint/src/main/java/org/wso2/carbon/inbound/endpoint/protocol/generic/ > GenericPollingConsumer.java#L77 > > [2] - https://github.com/hariss63/esb-inbound-kafka/blob/master/ > src/main/java/org/wso2/carbon/inbound/kafka/KafkaMessageConsumer.java#L306 > > [3] - https://github.com/hariss63/esb-inbound-kafka/blob/master/ > src/main/java/org/wso2/carbon/inbound/kafka/KafkaMessageConsumer.java#L327 > > -- > > > *Thank you and Regards,**Hariprasath Thanarajah* > Software Engineer | WSO2 > E: haripras...@wso2.com > M: +94 75 2806528 <+94%2075%20280%206528>, +94 77 7216903 > <+94%2077%20721%206903> > Blog: hariwso2.blogspot.com > > Skype : hariss636 > LinkedIn : https://www.linkedin.com/in/hariprasath-thanarajah-5234b660 > > WSO2, Inc. > lean . enterprise . middleware > > https://wso2.com/signature > http://wso2.com/about/team/hariprashath-thanarajah/ > -- *Thank you and Regards,**Hariprasath Thanarajah* Software Engineer | WSO2 E: haripras...@wso2.com M: +94 75 2806528, +94 77 7216903 Blog: hariwso2.blogspot.com Skype : hariss636 LinkedIn : https://www.linkedin.com/in/hariprasath-thanarajah-5234b660 WSO2, Inc. lean . enterprise . middleware https://wso2.com/signature http://wso2.com/about/team/hariprashath-thanarajah/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Doing WSO2 ESB connector for Google Pub/Sub API
Hi All, On Fri, Jun 16, 2017 at 3:27 PM, Malaka Silva <mal...@wso2.com> wrote: > Hi Tharmalingam, > > We are happy to hear that you are interested in doing this. Yes you can > contribute connector and inbound for Google Pub/Sub API.. > > We will mentor you while doing this. You can also visit our Jaffna branch > or use this mail thread to communicate. > > > On Fri, Jun 16, 2017 at 3:09 PM, Amalanathan Thushanthan < > thushaama...@gmail.com> wrote: > >> Hi Malaka, >> >> I'm Thushanthan, doing computer science at University of Jaffna. I've >> been participating the Jaffna meetup continuously. I got some idea about >> how to contribute to WSO2 and about WSO2 extensions and their usages. I >> would like to contribute to WSO2(wso2-extension). Some of my colleagues >> were already done this and some are working on this. My friend and I would >> like to create an ESB-Connector. In lase meetup we talked you about our >> interest and as you suggested, we refereed the following links and got to >> know basic ideas. We tried linkedIn connector and understood the Oauth2 >> follow. >> And we found the public JIRA https://wso2.org/jira/pro >> jects/ESBCONNECT/issues/ESBCONNECT-197, >> is it possible to do connector for Google Pub/Sub API. >> > +1 for Google Pub/Sub API. You can create the Connector first. The following are some useful links to understand the Google Pub/Sub API and about WSO2 Extension. Please go through those and get back to us with your plan. [1] - https://wso2.org/jira/projects/ESBCONNECT/issues/ESBCONNECT-197 <https://www.google.com/url?q=https%3A%2F%2Fwso2.org%2Fjira%2Fprojects%2FESBCONNECT%2Fissues%2FESBCONNECT-197=D=1=AFQjCNH4_lCn9u1-Cay5Z7_53J6J1hueOA> [2] - https://cloud.google.com/pubsub/docs/overview [3] - https://cloud.google.com/pubsub/docs/reference/rest/ [4] - https://docs.wso2.com/display/ESBCONNECTORS/WSO2+ESB+Connectors [5] - https://docs.wso2.com/display/ESB500/Working+with+ Connectors+via+the+Management+Console [6] - https://store.wso2.com/store/pages/top-assets https://docs.wso2.com/display/ESBCONNECTORS/WSO2+ESB+Connect >> ors+Documentation >> https://docs.wso2.com/display/ESBCONNECTORS/LinkedIn+Connector >> https://alexbilbie.com/guide-to-oauth-2-grants/ >> <https://www.google.com/url?q=https%3A%2F%2Falexbilbie.com%2Fguide-to-oauth-2-grants%2F=D=1=AFQjCNGbLzkiZ54m_ZRLm5jIzfSSnngOPA> >> >> Thanks and Regards >> Thushanthan >> > > > > -- > > Best Regards, > > Malaka Silva > Associate Director / Architect > M: +94 777 219 791 <+94%2077%20721%209791> > Tel : 94 11 214 5345 > Fax :94 11 2145300 > Skype : malaka.sampath.silva > LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 > Blog : http://mrmalakasilva.blogspot.com/ > > WSO2, Inc. > lean . enterprise . middleware > https://wso2.com/signature > http://www.wso2.com/about/team/malaka-silva/ > <http://wso2.com/about/team/malaka-silva/> > https://store.wso2.com/store/ > > Don't make Trees rare, we should keep them with care > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Thank you and Regards,**Hariprasath Thanarajah* Software Engineer | WSO2 E: haripras...@wso2.com M: +94 75 2806528, +94 77 7216903 Blog: hariwso2.blogspot.com Skype : hariss636 LinkedIn : https://www.linkedin.com/in/hariprasath-thanarajah-5234b660 WSO2, Inc. lean . enterprise . middleware https://wso2.com/signature http://wso2.com/about/team/hariprashath-thanarajah/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ESBCONNECTORS Oauth2 with service account
Hi Iroshan, At the moment the Gmail connector doesn't support the service account authentication and from the official gmail api website[1] they have mentioed that all requests to the Gmail API must be authorized by an authenticated user. Regarding the response from[2] we can't use a service account with a normal users gmail account. [1] - https://developers.google.com/gmail/api/auth/about-auth [2] - https://stackoverflow.com/questions/42784640/client-is-unauthorized-to-retrieve-access-tokens-using-this-method-gmail-api-c-s On Tue, May 30, 2017 at 11:01 AM, Rajjaz Mohammed <raj...@wso2.com> wrote: > Hi Iroshan, > > AFAIK current Gmail connector doesn't support for service account type. > You can create a Jira[1] to track this feature. > > [1] https://wso2.org/jira/projects/ESBCONNECT/issues > > On Tue, May 30, 2017 at 9:41 AM, iroshan horathalge <testiros...@gmail.com > > wrote: > >> Hi All, >> >> have a good day. >> >> I am trying to send gmail by ESB- CONNECTOR[1] with Oauth2. >> >> Does this support for service account type which doesn't have redirect >> URL and client ID?. All the documentation I saw are based on Client ID and >> does not set up as service account . Do you have any sample or >> documentation on this. >> >> >> [1]https://docs.wso2.com/display/ESBCONNECTORS/Gmail+Connector . >> >> Thanks & Regards, >> Iroshan >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Thank you > Best Regards > > *Rajjaz HM* > Software Engineer > Platform Extension Team > WSO2 Inc. <http://wso2.com/> > lean | enterprise | middleware > Mobile | +94752833834 <+94%2075%20283%203834>|+94777226874 > <+94%2077%20722%206874> > Email | raj...@wso2.com > LinkedIn <https://lk.linkedin.com/in/hmohammedrajjaz> | Blogger > <http://rajjazhm.blogspot.com/> | WSO2 Profile > <http://wso2.com/about/team/mohammer-rajjaz/> > [image: https://wso2.com/signature] <https://wso2.com/signature> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Thank you and Regards,**Hariprasath Thanarajah* Software Engineer | WSO2 E: haripras...@wso2.com M: +94 75 2806528, +94 77 7216903 Blog: hariwso2.blogspot.com Skype : hariss636 LinkedIn : https://www.linkedin.com/in/hariprasath-thanarajah-5234b660 WSO2, Inc. lean . enterprise . middleware https://wso2.com/signature http://wso2.com/about/team/hariprashath-thanarajah/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Regarding gmail connector
Hi Varuni, Now you can able to send a mail in the html format in the mail body using the WSO2 ESB Gmail connector. The new gmail connector can be found in the store[1], and the documentation can be found in[2], [1] - https://store.wso2.com/store/assets/esbconnector/details/74539b71-3b72-49c1-a21a-f08ad7d7d4ad [2] - https://docs.wso2.com/display/ESBCONNECTORS/Working+with+Messages+in+Gmail#WorkingwithMessagesinGmail-sendMail On Thu, Apr 27, 2017 at 9:44 AM, Keerthika Mahendralingam < keerth...@wso2.com> wrote: > HI Varuni, > > As per the ticket [1], current connector only supports plain text messages. > > [1]. https://wso2.org/jira/browse/ESBCONNECT-147 > > Thanks, > > On Thu, Apr 27, 2017 at 9:37 AM, Supun Sethunga <sup...@wso2.com> wrote: > >> Which Gmail connector are you referring to? ESB[1] or Ballerina[2] ? >> >> [1] https://docs.wso2.com/display/ESBCONNECTORS/Gmail+Connector >> [2] http://ballerinalang.org/docs/api/0.8/org.wso2.ballerina >> .connectors.gmail.html >> >> On Wed, Apr 26, 2017 at 5:29 PM, Varuni Alwis <var...@wso2.com> wrote: >> >>> Hi all, >>> >>> I want to send a mail in the html format (not as a text) in the mail >>> body using the gmail connector? Is that possible with the connector? >>> >>> Thanks. >>> >>> >>> *Varuni Alwis* >>> *Software Engineer - Intern* >>> *WSO2* >>> >>> Email : var...@wso2.com >>> Mobile : +94 719865395 <+94%2071%20986%205395> >>> >>> >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Supun Sethunga* >> Senior Software Engineer >> WSO2, Inc. >> http://wso2.com/ >> lean | enterprise | middleware >> Mobile : +94 716546324 <+94%2071%20654%206324> >> Blog: http://supunsetunga.blogspot.com >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > <dev-requ...@wso2.org> > Keerthika Mahendralingam > Software Engineer > Mobile :+94 (0) 776 121144 <+94%2077%20612%201144> > keerth...@wso2.com > WSO2, Inc. > lean . enterprise . middleware > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Thank you and Regards,**Hariprasath Thanarajah* Software Engineer | WSO2 E: haripras...@wso2.com M: +94 75 2806528, +94 77 7216903 Blog: hariwso2.blogspot.com Skype : hariss636 LinkedIn : https://www.linkedin.com/in/hariprasath-thanarajah-5234b660 WSO2, Inc. lean . enterprise . middleware https://wso2.com/signature http://wso2.com/about/team/hariprashath-thanarajah/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Regarding wso2 gmail connector
Hi Varuni, According to the Malaka's reply, Yes we can do it by setting the from address. But before that, you need to add the different mail address as an alias to the primary e-mail address as follows, Click the setting icon in the right most top in your Gmail account -> Click Settings -> Click the tab "Accounts and Import" -> You can add the different email address in Send Mail As: block and confirm it via the mail send to your optional email address. Now you can able to send the mail from the different email address using the primary mail address. Thanks and Regards, Hariprasath T On Tue, Apr 25, 2017 at 8:56 PM, Malaka Silva <mal...@wso2.com> wrote: > Hi Varuni, > > Ideally this should work by setting the from address. However I think > first you need to enable sending mails from that email, from your gmail > account first. > > [1] https://docs.wso2.com/display/ESBCONNECTORS/Working+ > with+Messages+in+Gmail#WorkingwithMessagesinGmail-sendMail > > On Tue, Apr 25, 2017 at 6:05 PM, Varuni Alwis <var...@wso2.com> wrote: > >> Hi all, >> >> I want to send mails from a different mail account , not with the mail >> account I have given the configurations in the block . Is >> there a way I can accomplish that? >> >> Can’t I set a different mail address within tags in the >> ? >> >> Thanks >> >> >> *Varuni Alwis* >> *Software Engineer - Intern* >> *WSO2* >> >> Email : var...@wso2.com >> Mobile : +94 719865395 <071%20986%205395> >> >> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > > Best Regards, > > Malaka Silva > Associate Director / Architect > M: +94 777 219 791 <+94%2077%20721%209791> > Tel : 94 11 214 5345 > Fax :94 11 2145300 > Skype : malaka.sampath.silva > LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 > Blog : http://mrmalakasilva.blogspot.com/ > > WSO2, Inc. > lean . enterprise . middleware > https://wso2.com/signature > http://www.wso2.com/about/team/malaka-silva/ > <http://wso2.com/about/team/malaka-silva/> > https://store.wso2.com/store/ > > Don't make Trees rare, we should keep them with care > -- *Thank you and Regards,**Hariprasath Thanarajah* Software Engineer | WSO2 E: haripras...@wso2.com M: +94 75 2806528, +94 77 7216903 Blog: hariwso2.blogspot.com Skype : hariss636 LinkedIn : https://www.linkedin.com/in/hariprasath-thanarajah-5234b660 WSO2, Inc. lean . enterprise . middleware https://wso2.com/signature http://wso2.com/about/team/hariprashath-thanarajah/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue when saving and retrieving the login details in static variables in separate plug-in project for dynamic schema generation.
Hi All, I have discussed the issue in off-line with Malaka, Viraj and Kathees and I have found the root cause for this issue. The issue because of the object creation using Singleton pattern. Thank you for your suggestions. On Wed, Nov 23, 2016 at 11:41 AM, Hariprasath Thanarajah < haripras...@wso2.com> wrote: > Hi All, > > I am working on dynamic schema generation for dynamic connector > operations. For that, we create a separate plugin project with dialog boxes > for every operation and in the shell we need to give the login details to > connect with salesforce to generate the schema. We have finished the > implementation but in the current implementation if we need multiple > dynamic schema generations for connector operations then the user need to > give the login details every time. But we need to automate this if we need > to generate the subsequent dynamic schema generation. > > For that, we keep the login details in the static variables in the > separate plugin and check whether the details exists or not when clicking > the button(here login). When I do like this the dialog for the particular > operation has not been created. I guess the dialog creation part is in the > dev-tooling code and from that we create the shell for every operation. > So that we can't access those static variables from the non-static block. > Can you please guide me on this and correct me if I am wrong? > > -- > > > *Thank you and Regards,**Hariprasath Thanarajah* > Associate Software Engineer | WSO2 > E: haripras...@wso2.com > M: +94752806528, 0777216903 > Blog: hariwso2.blogspot.com > > Skype : hariss636 > LinkedIn : https://www.linkedin.com/in/hariprasath-thanarajah-5234b660 > > WSO2, Inc. > lean . enterprise . middleware > > https://wso2.com/signature > http://wso2.com/about/team/hariprashath-thanarajah/ > -- *Thank you and Regards,**Hariprasath Thanarajah* Associate Software Engineer | WSO2 E: haripras...@wso2.com M: +94752806528, 0777216903 Blog: hariwso2.blogspot.com Skype : hariss636 LinkedIn : https://www.linkedin.com/in/hariprasath-thanarajah-5234b660 WSO2, Inc. lean . enterprise . middleware https://wso2.com/signature http://wso2.com/about/team/hariprashath-thanarajah/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Issue when saving and retrieving the login details in static variables in separate plug-in project for dynamic schema generation.
Hi All, I am working on dynamic schema generation for dynamic connector operations. For that, we create a separate plugin project with dialog boxes for every operation and in the shell we need to give the login details to connect with salesforce to generate the schema. We have finished the implementation but in the current implementation if we need multiple dynamic schema generations for connector operations then the user need to give the login details every time. But we need to automate this if we need to generate the subsequent dynamic schema generation. For that, we keep the login details in the static variables in the separate plugin and check whether the details exists or not when clicking the button(here login). When I do like this the dialog for the particular operation has not been created. I guess the dialog creation part is in the dev-tooling code and from that we create the shell for every operation. So that we can't access those static variables from the non-static block. Can you please guide me on this and correct me if I am wrong? -- *Thank you and Regards,**Hariprasath Thanarajah* Associate Software Engineer | WSO2 E: haripras...@wso2.com M: +94752806528, 0777216903 Blog: hariwso2.blogspot.com Skype : hariss636 LinkedIn : https://www.linkedin.com/in/hariprasath-thanarajah-5234b660 WSO2, Inc. lean . enterprise . middleware https://wso2.com/signature http://wso2.com/about/team/hariprashath-thanarajah/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Automate namespace mapping using datamapper mediator
Hi Nuwan, On Tue, Nov 8, 2016 at 3:38 PM, Nuwan Pallewela <nuw...@wso2.com> wrote: > Hi Hari, > > The use-case you are explaining is little bit unclear. > We can not map values for properties from data mapper. We can only use > property values to map for the output payload. > Yes you are correct. The question was wrong. when we mapping the payload to properties, then the namespace needs to be given. Is there any way to automate it? > > Thanks, > Nuwan > > On Tue, Nov 8, 2016 at 3:10 PM, Hariprasath Thanarajah < > haripras...@wso2.com> wrote: > >> Hi All, >> >> When we mapping a payload(XML) to a properties using datamapper mediator >> in dev-tooling the namespace needs to be given. Is there any way to >> automate it in tooling? >> >> -- >> >> >> *Thank you and Regards,**Hariprasath Thanarajah* >> Associate Software Engineer | WSO2 >> E: haripras...@wso2.com >> M: +94752806528, 0777216903 >> Blog: hariwso2.blogspot.com >> >> Skype : hariss636 >> LinkedIn : https://www.linkedin.com/in/hariprasath-thanarajah-5234b660 >> >> WSO2, Inc. >> lean . enterprise . middleware >> >> https://wso2.com/signature >> http://wso2.com/about/team/hariprashath-thanarajah/ >> > > > > -- > -- > > *Nuwan Chamara Pallewela* > > > *Software Engineer* > > *WSO2, Inc. *http://wso2.com > *lean . enterprise . middleware* > > Email *nuw...@wso2.com <nuw...@wso2.com>* > Mobile *+94719079739 <%2B94719079739>@* > > > -- *Thank you and Regards,**Hariprasath Thanarajah* Associate Software Engineer | WSO2 E: haripras...@wso2.com M: +94752806528, 0777216903 Blog: hariwso2.blogspot.com Skype : hariss636 LinkedIn : https://www.linkedin.com/in/hariprasath-thanarajah-5234b660 WSO2, Inc. lean . enterprise . middleware https://wso2.com/signature http://wso2.com/about/team/hariprashath-thanarajah/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Automate namespace mapping using datamapper mediator
Hi All, When we mapping a payload(XML) to a properties using datamapper mediator in dev-tooling the namespace needs to be given. Is there any way to automate it in tooling? -- *Thank you and Regards,**Hariprasath Thanarajah* Associate Software Engineer | WSO2 E: haripras...@wso2.com M: +94752806528, 0777216903 Blog: hariwso2.blogspot.com Skype : hariss636 LinkedIn : https://www.linkedin.com/in/hariprasath-thanarajah-5234b660 WSO2, Inc. lean . enterprise . middleware https://wso2.com/signature http://wso2.com/about/team/hariprashath-thanarajah/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue while mapping the element from the salesforce query response using datamapper mediator on dev-tooling
Hi All,
When I debug the code I have found something as below,
If there is no prefix for the namespace then from the below code[1] it
manually puts axis2ns1 as the prefix in the created schema. That's the
reason I got the above error. But when I remove the part[1] from the
tooling and generate the schema I didn't get that error. Is there any other
particular reason to do the above[1] part?
[1] -
https://github.com/wso2/devstudio-tooling-esb/blob/b3c7995c5e07541540daa11471cbe5d057af1aa4/plugins/org.wso2.developerstudio.visualdatamapper.diagram/src/org/wso2/developerstudio/datamapper/diagram/schemagen/util/SchemaGeneratorForXML.java#L220-L222
On Mon, Oct 24, 2016 at 4:53 PM, Malaka Silva <mal...@wso2.com> wrote:
> Hi,
>
> I think the correct solution should be we fix this from ESB Tooling itself.
>
> Hariprasath is checking this.
>
> @Viraj / Nuwan - Please mentor this task.
>
> https://wso2.org/jira/browse/DEVTOOLESB-767
>
> On Mon, Oct 24, 2016 at 1:58 PM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Hi Nuwan,
>>
>> It is working for me with the sample xml that you sent me to generate the
>> schema. But the issue is, For the sample xml we just get the response from
>> the connector operation dynamically and from that only we can create the
>> schema.
>>
>> On Mon, Oct 24, 2016 at 11:54 AM, Nuwan Pallewela <nuw...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> Please apply the patch0493 to esb and try it.
>>>
>>> Thanks,
>>> Nuwan
>>>
>>> On Mon, Oct 24, 2016 at 11:31 AM, Hariprasath Thanarajah <
>>> haripras...@wso2.com> wrote:
>>>
>>>> Hi Nuwan,
>>>>
>>>> I have tried with the sample xml you sent to me to generate the schema.
>>>> But I got the below error.
>>>>
>>>>
>>>>
>>>> On Mon, Oct 24, 2016 at 10:58 AM, Nuwan Pallewela <nuw...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Hari,
>>>>>
>>>>> Can you try the attached sample xml to generate the schema?
>>>>>
>>>>> Thakns,
>>>>> Nuwan
>>>>>
>>>>> On Mon, Oct 24, 2016 at 9:37 AM, Nuwan Pallewela <nuw...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> HI Hari,
>>>>>>
>>>>>> There is an issue when schema generation for default name-spaced
>>>>>> elements of xml sample messages. Can you try a sample xml without default
>>>>>> name-spaces?
>>>>>>
>>>>>> Thanks,
>>>>>> Nuwan
>>>>>>
>>>>>> On Sun, Oct 23, 2016 at 9:18 PM, Hariprasath Thanarajah <
>>>>>> haripras...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi Nuwan,
>>>>>>>
>>>>>>> I have used the attached outQuery.xml file to generate the input
>>>>>>> schema(Response of query operation) and mapped a single element OwnerId
>>>>>>> to
>>>>>>> an output schema which is generated from the following content of a json
>>>>>>> file.
>>>>>>>
>>>>>>> {
>>>>>>> "name":"hari",
>>>>>>> "id":"12223dsfvx"
>>>>>>> }
>>>>>>>
>>>>>>> On Sun, Oct 23, 2016 at 6:45 AM, Nuwan Pallewela <nuw...@wso2.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Hari,
>>>>>>>>
>>>>>>>> Can you share the input schema, output schema and the mapping
>>>>>>>> configuration files to further analyze the issue?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Nuwan
>>>>>>>>
>>>>>>>> On Sun, Oct 23, 2016 at 1:06 AM, Hariprasath Thanarajah <
>>>>>>>> haripras...@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Create a public jira[1] to track this issue,
>>>>>>>>>
>>>>>>>>> [1] - https://wso2.org/jira/browse/DEVTOOLESB-767
>>>>>>>>>
>>>>>>>>> On Sun, Oct 23, 2016 at 1:04 AM, Hariprasath Thanarajah <
>>>>>>>>> haripras...@wso2.com> wrote:
>>>>>>>>>
>&g
Re: [Dev] Issue while mapping the element from the salesforce query response using datamapper mediator on dev-tooling
Hi Nuwan,
It is working for me with the sample xml that you sent me to generate the
schema. But the issue is, For the sample xml we just get the response from
the connector operation dynamically and from that only we can create the
schema.
On Mon, Oct 24, 2016 at 11:54 AM, Nuwan Pallewela <nuw...@wso2.com> wrote:
> Hi,
>
> Please apply the patch0493 to esb and try it.
>
> Thanks,
> Nuwan
>
> On Mon, Oct 24, 2016 at 11:31 AM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Hi Nuwan,
>>
>> I have tried with the sample xml you sent to me to generate the schema.
>> But I got the below error.
>>
>>
>>
>> On Mon, Oct 24, 2016 at 10:58 AM, Nuwan Pallewela <nuw...@wso2.com>
>> wrote:
>>
>>> Hi Hari,
>>>
>>> Can you try the attached sample xml to generate the schema?
>>>
>>> Thakns,
>>> Nuwan
>>>
>>> On Mon, Oct 24, 2016 at 9:37 AM, Nuwan Pallewela <nuw...@wso2.com>
>>> wrote:
>>>
>>>> HI Hari,
>>>>
>>>> There is an issue when schema generation for default name-spaced
>>>> elements of xml sample messages. Can you try a sample xml without default
>>>> name-spaces?
>>>>
>>>> Thanks,
>>>> Nuwan
>>>>
>>>> On Sun, Oct 23, 2016 at 9:18 PM, Hariprasath Thanarajah <
>>>> haripras...@wso2.com> wrote:
>>>>
>>>>> Hi Nuwan,
>>>>>
>>>>> I have used the attached outQuery.xml file to generate the input
>>>>> schema(Response of query operation) and mapped a single element OwnerId to
>>>>> an output schema which is generated from the following content of a json
>>>>> file.
>>>>>
>>>>> {
>>>>> "name":"hari",
>>>>> "id":"12223dsfvx"
>>>>> }
>>>>>
>>>>> On Sun, Oct 23, 2016 at 6:45 AM, Nuwan Pallewela <nuw...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Hari,
>>>>>>
>>>>>> Can you share the input schema, output schema and the mapping
>>>>>> configuration files to further analyze the issue?
>>>>>>
>>>>>> Thanks,
>>>>>> Nuwan
>>>>>>
>>>>>> On Sun, Oct 23, 2016 at 1:06 AM, Hariprasath Thanarajah <
>>>>>> haripras...@wso2.com> wrote:
>>>>>>
>>>>>>> Create a public jira[1] to track this issue,
>>>>>>>
>>>>>>> [1] - https://wso2.org/jira/browse/DEVTOOLESB-767
>>>>>>>
>>>>>>> On Sun, Oct 23, 2016 at 1:04 AM, Hariprasath Thanarajah <
>>>>>>> haripras...@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi All,
>>>>>>>>
>>>>>>>> Now I am working on the dynamic schema generation for connector
>>>>>>>> operations in dev-tooling. For the initial, I have completed the
>>>>>>>> dynamic
>>>>>>>> schema generation part for salesforce soap connector.I have tried a
>>>>>>>> simple
>>>>>>>> use case using salesforce connector. For that used the query
>>>>>>>> operation(from
>>>>>>>> the response) to create the input schema and map an element from that
>>>>>>>> to an
>>>>>>>> output schema element using data mapper mediator. I have used the
>>>>>>>> following
>>>>>>>> attached file to create the input schema(response of query operation)
>>>>>>>> and
>>>>>>>> map it to an output element. In the above case, I have created an ESB
>>>>>>>> config project and create a sample and invoke this service. When I
>>>>>>>> invoke
>>>>>>>> this service I got the following error in [1]
>>>>>>>>
>>>>>>>> [1] - [2016-10-22 23:16:58,563] WARN - XMLInputReader Element name
>>>>>>>> not found : axis2ns1:LimitInfoHeader
>>>>>>>> [2016-10-22 23:16:58,563] ERROR - DataMapperMediator DataMapper
>>>>>>>> mediator : mapping failed
>>>>>>>> Input type is incorrect or Invalid element found
Re: [Dev] Issue while mapping the element from the salesforce query response using datamapper mediator on dev-tooling
Hi Nuwan,
I have used the attached outQuery.xml file to generate the input
schema(Response of query operation) and mapped a single element OwnerId to
an output schema which is generated from the following content of a json
file.
{
"name":"hari",
"id":"12223dsfvx"
}
On Sun, Oct 23, 2016 at 6:45 AM, Nuwan Pallewela <nuw...@wso2.com> wrote:
> Hi Hari,
>
> Can you share the input schema, output schema and the mapping
> configuration files to further analyze the issue?
>
> Thanks,
> Nuwan
>
> On Sun, Oct 23, 2016 at 1:06 AM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Create a public jira[1] to track this issue,
>>
>> [1] - https://wso2.org/jira/browse/DEVTOOLESB-767
>>
>> On Sun, Oct 23, 2016 at 1:04 AM, Hariprasath Thanarajah <
>> haripras...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> Now I am working on the dynamic schema generation for connector
>>> operations in dev-tooling. For the initial, I have completed the dynamic
>>> schema generation part for salesforce soap connector.I have tried a simple
>>> use case using salesforce connector. For that used the query operation(from
>>> the response) to create the input schema and map an element from that to an
>>> output schema element using data mapper mediator. I have used the following
>>> attached file to create the input schema(response of query operation) and
>>> map it to an output element. In the above case, I have created an ESB
>>> config project and create a sample and invoke this service. When I invoke
>>> this service I got the following error in [1]
>>>
>>> [1] - [2016-10-22 23:16:58,563] WARN - XMLInputReader Element name not
>>> found : axis2ns1:LimitInfoHeader
>>> [2016-10-22 23:16:58,563] ERROR - DataMapperMediator DataMapper mediator
>>> : mapping failed
>>> Input type is incorrect or Invalid element found in the message payload
>>> : axis2ns1:LimitInfoHeader
>>> at org.wso2.carbon.mediator.datamapper.engine.input.readers.XML
>>> InputReader.xmlTraverse(XMLInputReader.java:170)
>>> at org.wso2.carbon.mediator.datamapper.engine.input.readers.XML
>>> InputReader.xmlTraverse(XMLInputReader.java:224)
>>> at org.wso2.carbon.mediator.datamapper.engine.input.readers.XML
>>> InputReader.xmlTraverse(XMLInputReader.java:224)
>>> at org.wso2.carbon.mediator.datamapper.engine.input.readers.XML
>>> InputReader.read(XMLInputReader.java:117)
>>> at org.wso2.carbon.mediator.datamapper.engine.input.InputBuilde
>>> r.buildInputModel(InputBuilder.java:59)
>>> at org.wso2.carbon.mediator.datamapper.engine.core.mapper.Mappi
>>> ngHandler.doMap(MappingHandler.java:67)
>>> at org.wso2.carbon.mediator.datamapper.DataMapperMediator.trans
>>> form(DataMapperMediator.java:306)
>>> at org.wso2.carbon.mediator.datamapper.DataMapperMediator.media
>>> te(DataMapperMediator.java:256)
>>> at org.apache.synapse.mediators.AbstractListMediator.mediate(Ab
>>> stractListMediator.java:97)
>>> at org.apache.synapse.mediators.base.SequenceMediator.mediate(S
>>> equenceMediator.java:281)
>>> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.mediat
>>> eFromContinuationStateStack(Axis2SynapseEnvironment.java:766)
>>> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.inject
>>> Message(Axis2SynapseEnvironment.java:282)
>>> at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handle
>>> Message(SynapseCallbackReceiver.java:554)
>>> at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receiv
>>> e(SynapseCallbackReceiver.java:188)
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>> at org.apache.synapse.transport.passthru.ClientWorker.run(Clien
>>> tWorker.java:261)
>>> at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.r
>>> un(NativeWorkerPool.java:172)
>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>>> Executor.java:1145)
>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>>> lExecutor.java:615)
>>> at java.lang.Thread.run(Thread.java:745)
>>>
>>>
>>> How can I overcome this issue?
>>>
>>> --
>>>
>>>
>>> *Thank you and Regards,**Hariprasath Thanarajah*
>>> Associate Software Engineer | WSO2
>>> E: haripras...@wso2.com
>>>
Re: [Dev] Issue while mapping the element from the salesforce query response using datamapper mediator on dev-tooling
Create a public jira[1] to track this issue, [1] - https://wso2.org/jira/browse/DEVTOOLESB-767 On Sun, Oct 23, 2016 at 1:04 AM, Hariprasath Thanarajah < haripras...@wso2.com> wrote: > Hi All, > > Now I am working on the dynamic schema generation for connector operations > in dev-tooling. For the initial, I have completed the dynamic schema > generation part for salesforce soap connector.I have tried a simple use > case using salesforce connector. For that used the query operation(from the > response) to create the input schema and map an element from that to an > output schema element using data mapper mediator. I have used the following > attached file to create the input schema(response of query operation) and > map it to an output element. In the above case, I have created an ESB > config project and create a sample and invoke this service. When I invoke > this service I got the following error in [1] > > [1] - [2016-10-22 23:16:58,563] WARN - XMLInputReader Element name not > found : axis2ns1:LimitInfoHeader > [2016-10-22 23:16:58,563] ERROR - DataMapperMediator DataMapper mediator : > mapping failed > Input type is incorrect or Invalid element found in the message payload : > axis2ns1:LimitInfoHeader > at org.wso2.carbon.mediator.datamapper.engine.input. > readers.XMLInputReader.xmlTraverse(XMLInputReader.java:170) > at org.wso2.carbon.mediator.datamapper.engine.input. > readers.XMLInputReader.xmlTraverse(XMLInputReader.java:224) > at org.wso2.carbon.mediator.datamapper.engine.input. > readers.XMLInputReader.xmlTraverse(XMLInputReader.java:224) > at org.wso2.carbon.mediator.datamapper.engine.input. > readers.XMLInputReader.read(XMLInputReader.java:117) > at org.wso2.carbon.mediator.datamapper.engine.input. > InputBuilder.buildInputModel(InputBuilder.java:59) > at org.wso2.carbon.mediator.datamapper.engine.core.mapper. > MappingHandler.doMap(MappingHandler.java:67) > at org.wso2.carbon.mediator.datamapper.DataMapperMediator. > transform(DataMapperMediator.java:306) > at org.wso2.carbon.mediator.datamapper.DataMapperMediator. > mediate(DataMapperMediator.java:256) > at org.apache.synapse.mediators.AbstractListMediator.mediate( > AbstractListMediator.java:97) > at org.apache.synapse.mediators.base.SequenceMediator.mediate( > SequenceMediator.java:281) > at org.apache.synapse.core.axis2.Axis2SynapseEnvironment. > mediateFromContinuationStateStack(Axis2SynapseEnvironment.java:766) > at org.apache.synapse.core.axis2.Axis2SynapseEnvironment. > injectMessage(Axis2SynapseEnvironment.java:282) > at org.apache.synapse.core.axis2.SynapseCallbackReceiver. > handleMessage(SynapseCallbackReceiver.java:554) > at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive( > SynapseCallbackReceiver.java:188) > at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) > at org.apache.synapse.transport.passthru.ClientWorker.run( > ClientWorker.java:261) > 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:745) > > > How can I overcome this issue? > > -- > > > *Thank you and Regards,**Hariprasath Thanarajah* > Associate Software Engineer | WSO2 > E: haripras...@wso2.com > M: +94752806528, 0777216903 > Blog: hariwso2.blogspot.com > > Skype : hariss636 > LinkedIn : https://www.linkedin.com/in/hariprasath-thanarajah-5234b660 > > WSO2, Inc. > lean . enterprise . middleware > > https://wso2.com/signature > http://wso2.com/about/team/hariprashath-thanarajah/ > -- *Thank you and Regards,**Hariprasath Thanarajah* Associate Software Engineer | WSO2 E: haripras...@wso2.com M: +94752806528, 0777216903 Blog: hariwso2.blogspot.com Skype : hariss636 LinkedIn : https://www.linkedin.com/in/hariprasath-thanarajah-5234b660 WSO2, Inc. lean . enterprise . middleware https://wso2.com/signature http://wso2.com/about/team/hariprashath-thanarajah/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Identity Server Error with MailChimp SSO
Hi Srikanth,
It should be https://us14.api.mailchimp.com/2.0/users/profile.
<https://us14.api.mailchimp.com/2.0/users/profile>
On Wed, Sep 28, 2016 at 12:27 PM, Srikanth Puppala <
puppala.srika...@gmail.com> wrote:
> Hi Hariprashant,
>
> I am using "https://us14.admin.mailchimp.com/2.0/users/profile; as URL
>
> Thanks & Regards,
> Srikanth Puppala.
>
> On Tue, Sep 27, 2016 at 11:02 PM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Hi Srikanth,
>>
>> What is your mailChimp instance URL? Can you please share it(For Example
>> https://us12.admin.mailchimp.com/account/). You don't need to use the
>> localhost configuration. The Redirect URI should be
>> https://52.41.122.92:9443/commonauth
>> <https://52.41.122.92:9443/commonauthv>
>>
>> On Wed, Sep 28, 2016 at 11:20 AM, Srikanth Puppala <
>> puppala.srika...@gmail.com> wrote:
>>
>>> Hi Hariprasant,
>>>
>>> Yes, I did followed documentation. I did not use "localhost", instead of
>>> localhost I used IP address of my machine where Identity Server is running.
>>> It is public IP.
>>>
>>> *In MailChimp Registration, I am using following:*
>>> For instance, configured app website as: http://52.41.122.92:8080/t
>>> ravelocity.com/index.jsp
>>> Redirect URI as: https://52.41.122.92:9443/commonauthv
>>>
>>> Do I need to use localhost configuration??
>>>
>>> Thanks & Regards,
>>> Srikanth Puppala.
>>>
>>> On Tue, Sep 27, 2016 at 9:56 PM, Hariprasath Thanarajah <
>>> haripras...@wso2.com> wrote:
>>>
>>>> Hi Srikanth,
>>>>
>>>> Did you follow the documentation? Here the error came because of the
>>>> wrong user info endpoint. You need to give the user info endpoint like in
>>>> the documentation. Please follow the documentation.
>>>>
>>>> On Wed, Sep 28, 2016 at 9:44 AM, Srikanth Puppala <
>>>> puppala.srika...@gmail.com> wrote:
>>>>
>>>>> Hi Hariprasant,
>>>>>
>>>>> Thanks a lot for the quick patch, I tried the patch and now I am
>>>>> getting different issue. I am I doing something wrong?
>>>>>
>>>>> *Following is the error stacktrace.*
>>>>>
>>>>> [2016-09-28 04:11:06,806] ERROR {org.wso2.carbon.identity.auth
>>>>> enticator.mailChimp.MailChimpAuthenticator} - Error occurred while
>>>>> accessing user info
>>>>> endpoint
>>>>> java.lang.IllegalArgumentException: String '
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> 404: Page Not Found | MailChimp
>>>>> https://fonts.googleapis.com/css?family=Open+Sans:300i
>>>>> talic,300,400italic,400,600italic,600,700italic,700,800italic,800"
>>>>> rel="styleshe
>>>>> et" type="text/css">
>>>>>
>>>>> /* Duplicating CSS classes since this page can not load
>>>>> theone.less */
>>>>> * { -moz-box-sizing: border-box; -webkit-box-sizing:
>>>>> border-box; box-sizing: border-box;}
>>>>> html, body, div, span, object, iframe,h1, h2, h3, h4, h5, h6,
>>>>> p, blockquote, pre,a, abbr, acronym, address, code,del, dfn, em, img, q,
>>>>> dl, dt,
>>>>> dd, ol, ul, li,fieldset, form, label, legend, textarea,table,
>>>>> caption, tbody, tfoot, thead, tr, th, td {margin: 0;padding: 0;border:
>>>>> 0;font-weight: i
>>>>> nherit;font-style: inherit;font-size: 100%;font-family:
>>>>> inherit;vertical-align: baseline;line-height: 1.5em;}
>>>>> body {color: #595959;font-family: "Helvetica
>>>>> Neue",Helvetica,Arial,Verdana,sans-serif;font-size: 1em;line-height:
>>>>> 0.375em;text-rendering: opti
>>>>> mizelegibility;vertical-align: baseline;}
>>>>> a, a:visited {color: #45BCD2;text-decoration: none;}
>>>>> a .nolink, a:visited .nolink {color: #595959;}
>>>>> a:hover {color: #2AA0B5;}
>>>>> .bg-white {background-color: #FF;}
>>>>> .centered{float: none; margin-left: auto; margin-right: auto;}
>>>>> .alignc {text-align: center;}
>>>>> .line {overfl
Re: [Dev] WSO2 Identity Server Error with MailChimp SSO
Hi Srikanth,
What is your mailChimp instance URL? Can you please share it(For Example
https://us12.admin.mailchimp.com/account/). You don't need to use the
localhost configuration. The Redirect URI should be
https://52.41.122.92:9443/commonauth <https://52.41.122.92:9443/commonauthv>
On Wed, Sep 28, 2016 at 11:20 AM, Srikanth Puppala <
puppala.srika...@gmail.com> wrote:
> Hi Hariprasant,
>
> Yes, I did followed documentation. I did not use "localhost", instead of
> localhost I used IP address of my machine where Identity Server is running.
> It is public IP.
>
> *In MailChimp Registration, I am using following:*
> For instance, configured app website as: http://52.41.122.92:8080/
> travelocity.com/index.jsp
> Redirect URI as: https://52.41.122.92:9443/commonauthv
>
> Do I need to use localhost configuration??
>
> Thanks & Regards,
> Srikanth Puppala.
>
> On Tue, Sep 27, 2016 at 9:56 PM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Hi Srikanth,
>>
>> Did you follow the documentation? Here the error came because of the
>> wrong user info endpoint. You need to give the user info endpoint like in
>> the documentation. Please follow the documentation.
>>
>> On Wed, Sep 28, 2016 at 9:44 AM, Srikanth Puppala <
>> puppala.srika...@gmail.com> wrote:
>>
>>> Hi Hariprasant,
>>>
>>> Thanks a lot for the quick patch, I tried the patch and now I am getting
>>> different issue. I am I doing something wrong?
>>>
>>> *Following is the error stacktrace.*
>>>
>>> [2016-09-28 04:11:06,806] ERROR {org.wso2.carbon.identity.auth
>>> enticator.mailChimp.MailChimpAuthenticator} - Error occurred while
>>> accessing user info
>>> endpoint
>>> java.lang.IllegalArgumentException: String '
>>>
>>>
>>>
>>>
>>>
>>>
>>> 404: Page Not Found | MailChimp
>>> https://fonts.googleapis.com/css?family=Open+Sans:300i
>>> talic,300,400italic,400,600italic,600,700italic,700,800italic,800"
>>> rel="styleshe
>>> et" type="text/css">
>>>
>>> /* Duplicating CSS classes since this page can not load
>>> theone.less */
>>> * { -moz-box-sizing: border-box; -webkit-box-sizing: border-box;
>>> box-sizing: border-box;}
>>> html, body, div, span, object, iframe,h1, h2, h3, h4, h5, h6, p,
>>> blockquote, pre,a, abbr, acronym, address, code,del, dfn, em, img, q, dl,
>>> dt,
>>> dd, ol, ul, li,fieldset, form, label, legend, textarea,table, caption,
>>> tbody, tfoot, thead, tr, th, td {margin: 0;padding: 0;border:
>>> 0;font-weight: i
>>> nherit;font-style: inherit;font-size: 100%;font-family:
>>> inherit;vertical-align: baseline;line-height: 1.5em;}
>>> body {color: #595959;font-family: "Helvetica
>>> Neue",Helvetica,Arial,Verdana,sans-serif;font-size: 1em;line-height:
>>> 0.375em;text-rendering: opti
>>> mizelegibility;vertical-align: baseline;}
>>> a, a:visited {color: #45BCD2;text-decoration: none;}
>>> a .nolink, a:visited .nolink {color: #595959;}
>>> a:hover {color: #2AA0B5;}
>>> .bg-white {background-color: #FF;}
>>> .centered{float: none; margin-left: auto; margin-right: auto;}
>>> .alignc {text-align: center;}
>>> .line {overflow: auto;}
>>> .size1of1 {width: 100%;}
>>> .lastUnit { background-clip: padding-box !important; float:
>>> none; overflow: hidden; padding-left: 15px; padding-right: 15px; width:
>>> auto }
>>> .below36 {margin-bottom: 2.25em !important;}
>>>
>>> h1, .h1, h2, .h2, h3, .h3, h4, .h4 {color: #595959; font-family:
>>> "Helvetica Neue",Helvetica,Arial,Verdana,sans-serif; font-weight: bold;}
>>> h1, .h1 {font-size: 2.5em; line-height: 1.2em; margin-bottom:
>>> 0.15em;}
>>> h4, .h4 {font-size: 1.125em; font-weight: 500; letter-spacing:
>>> 0.01em; line-height: 1.7em; margin-bottom: 0.33em;}
>>> p, .p {font-size: 0.9375em;line-height: 1.6em;margin-bottom:
>>> 1.2em;max-width: 550px;}
>>> button, .button, .button-small {-moz-user-select:
>>> none;background-color: #E0E0E0;border: medium none;border-radius: 3px 3px
>>> 3px 3px;color: #73
>>> 7373;cursor: pointer;display: inline-block;font-family: "Helvetica
>>> Neue",Helvetica,Ari
Re: [Dev] WSO2 Identity Server Error with MailChimp SSO
nternalDoFilter(ApplicationFilterChain.java:241) > at org.apache.catalina.core.ApplicationFilterChain.doFilter( > ApplicationFilterChain.java:208) > at org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter( > HttpHeaderSecurityFilter.java:120) > at org.apache.catalina.core.ApplicationFilterChain. > internalDoFilter(ApplicationFilterChain.java:241) > at org.apache.catalina.core.ApplicationFilterChain.doFilter( > ApplicationFilterChain.java:208) > at org.apache.catalina.core.StandardWrapperValve.invoke( > StandardWrapperValve.java:218) > at org.apache.catalina.core.StandardContextValve.invoke( > StandardContextValve.java:122) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke( > AuthenticatorBase.java:505) > at org.apache.catalina.core.StandardHostValve.invoke( > StandardHostValve.java:169) > at org.apache.catalina.valves.ErrorReportValve.invoke( > ErrorReportValve.java:103) > at org.wso2.carbon.tomcat.ext.valves.CompositeValve. > continueInvocation(CompositeValve.java:99) > at org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1. > invoke(CarbonTomcatValve.java:47) > at org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke( > TenantLazyLoaderValve.java:57) > at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer. > invokeValves(TomcatValveContainer.java:47) > at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke( > CompositeValve.java:62) > at org.wso2.carbon.tomcat.ext.valves. > CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValv > e.java:159) > at org.apache.catalina.valves.AccessLogValve.invoke( > AccessLogValve.java:956) > at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve. > invoke(CarbonContextCreatorValve.java:57) > at org.apache.catalina.core.StandardEngineValve.invoke( > StandardEngineValve.java:116) > at org.apache.catalina.connector.CoyoteAdapter.service( > CoyoteAdapter.java:442) > at org.apache.coyote.http11.AbstractHttp11Processor.process( > AbstractHttp11Processor.java:1082) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler. > process(AbstractProtocol.java:623) > at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor. > doRun(NioEndpoint.java:1756) > at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor. > run(NioEndpoint.java:1715) > at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown > Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown > Source) > at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run( > TaskThread.java:61) > at java.lang.Thread.run(Unknown Source) > > > > > > Thanks & Regards, > Srikanth Puppala. > > On Tue, Sep 27, 2016 at 1:14 AM, Hariprasath Thanarajah < > haripras...@wso2.com> wrote: > >> Hi Srikanth, >> >> You can find the new version of authenticator in [1] and the >> documentation in [2]. >> >> [1] - https://store.wso2.com/store/assets/isconnector/7c9237bc-6d3 >> 4-4416-8cbd-f69a6ca1893e >> >> [2] - https://docs.wso2.com/display/ISCONNECTORS/Configuring+MailC >> himp+Authenticator >> >> On Tue, Sep 27, 2016 at 4:02 AM, Hariprasath Thanarajah < >> haripras...@wso2.com> wrote: >> >>> Yes sure we will provide the fix version of mailChimp Authenticator soon. >>> >>> >>> On Monday, September 26, 2016, Srikanth Puppala < >>> puppala.srika...@gmail.com> wrote: >>> >>>> Hi Malaka/Hariparshath, >>>> >>>> It would be great if you provide a fix on top of Identity Server 5.2.0. >>>> I am even fine to go back to any of the versions where MailChimp SSO is >>>> functional. >>>> >>>> Thanks & Regards, >>>> Srikanth Puppala. >>>> >>>> On Mon, Sep 26, 2016 at 5:18 AM, Hariprasath Thanarajah < >>>> haripras...@wso2.com> wrote: >>>> >>>>> Yes noted Malaka. >>>>> >>>>> >>>>> On Monday, September 26, 2016, Malaka Silva <mal...@wso2.com> wrote: >>>>> >>>>>> Hi Srikanth, >>>>>> >>>>>> Thank you for reporting this and we will provide a solution soon. >>>>>> >>>>>> @Hariprasath - Yes you are correct API 2.0 is deprecated and that >>>>>> does not mean it's currently unavailable. So we should ideally be >>>>>> changing >>>>>> this to the latest version. >>>
Re: [Dev] WSO2 Identity Server Error with MailChimp SSO
Hi Srikanth, You can find the new version of authenticator in [1] and the documentation in [2]. [1] - https://store.wso2.com/store/assets/isconnector/7c9237bc-6d34-4416-8cbd-f69a6ca1893e [2] - https://docs.wso2.com/display/ISCONNECTORS/Configuring+MailChimp+Authenticator On Tue, Sep 27, 2016 at 4:02 AM, Hariprasath Thanarajah < haripras...@wso2.com> wrote: > Yes sure we will provide the fix version of mailChimp Authenticator soon. > > > On Monday, September 26, 2016, Srikanth Puppala < > puppala.srika...@gmail.com> wrote: > >> Hi Malaka/Hariparshath, >> >> It would be great if you provide a fix on top of Identity Server 5.2.0. I >> am even fine to go back to any of the versions where MailChimp SSO is >> functional. >> >> Thanks & Regards, >> Srikanth Puppala. >> >> On Mon, Sep 26, 2016 at 5:18 AM, Hariprasath Thanarajah < >> haripras...@wso2.com> wrote: >> >>> Yes noted Malaka. >>> >>> >>> On Monday, September 26, 2016, Malaka Silva <mal...@wso2.com> wrote: >>> >>>> Hi Srikanth, >>>> >>>> Thank you for reporting this and we will provide a solution soon. >>>> >>>> @Hariprasath - Yes you are correct API 2.0 is deprecated and that does >>>> not mean it's currently unavailable. So we should ideally be changing this >>>> to the latest version. >>>> >>>> I managed to reproduce the issue that Srikanth has experienced. The >>>> reason for that is endpoint is dynamic. For example my access token should >>>> be using https://*us14*.api.mailchimp.com/2.0/users/profile, where as >>>> you need to use https://*us12*.api.mailchimp.com/2.0/users/profile for >>>> your account. More details can be found in [1] >>>> >>>> Can we provide a fix for this? >>>> >>>> [1] http://stackoverflow.com/questions/27875405/invalid-mailchim >>>> p-api-key-in-mailchimp-export-api >>>> >>>> On Mon, Sep 26, 2016 at 4:02 PM, Hariprasath Thanarajah < >>>> haripras...@wso2.com> wrote: >>>> >>>>> Hi Srikanth, >>>>> >>>>> >>>>> On Mon, Sep 26, 2016 at 10:07 AM, Srikanth Puppala < >>>>> puppala.srika...@gmail.com> wrote: >>>>> >>>>>> Hi Malaka, >>>>>> >>>>>> Thanks for your response. I did not set any email configuration in >>>>>> Identity Server or MailChimp. I followed the doc " >>>>>> https://docs.wso2.com/display/ISCONNECTORS/Configuring+Mail >>>>>> Chimp+Authenticator". >>>>>> >>>>>> On forums, I see a bug in WSO2 Identity Server [ >>>>>> https://wso2.org/jira/browse/IDENTITY-4810]. I tried version 5.1.0 >>>>>> and 5.2.0 version of Identity Server and seeing the same problem. >>>>>> >>>>> I have tried with 5.1.0 and it is working for me(Tried with v2.0 app). >>>>> The issue because of the mailChimp API version, We created this for api >>>>> v2.0 their we created the federated authenticated User from the email got >>>>> from the response of https://apidocs.mailchimp.com/ >>>>> api/2.0/users/profile.php but now it is deprecated. Thank you for >>>>> pointing it. We will update with mailChimp Authenticator for current API >>>>> version. >>>>> >>>>>> , >>>>>> I am not really sure about subject identifier and how to configure >>>>>> it. Could you please share any doc which will be helpful. >>>>>> >>>>> You don't need it to configure. >>>>> >>>>>> >>>>>> Thanks & Regards, >>>>>> Srikanth Puppala. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Sun, Sep 25, 2016 at 8:53 PM, Malaka Silva <mal...@wso2.com> >>>>>> wrote: >>>>>> >>>>>>> Hi Srikanth, >>>>>>> >>>>>>> I guess you have setup this as the first step and won't be using any >>>>>>> other authenticator afterwards? >>>>>>> With mail chimp authinticator we are using email as the subject >>>>>>> identifier. Hope you have given a email for the user and set the >>>
Re: [Dev] WSO2 Identity Server Error with MailChimp SSO
Yes sure we will provide the fix version of mailChimp Authenticator soon. On Monday, September 26, 2016, Srikanth Puppala <puppala.srika...@gmail.com> wrote: > Hi Malaka/Hariparshath, > > It would be great if you provide a fix on top of Identity Server 5.2.0. I > am even fine to go back to any of the versions where MailChimp SSO is > functional. > > Thanks & Regards, > Srikanth Puppala. > > On Mon, Sep 26, 2016 at 5:18 AM, Hariprasath Thanarajah < > haripras...@wso2.com > <javascript:_e(%7B%7D,'cvml','haripras...@wso2.com');>> wrote: > >> Yes noted Malaka. >> >> >> On Monday, September 26, 2016, Malaka Silva <mal...@wso2.com >> <javascript:_e(%7B%7D,'cvml','mal...@wso2.com');>> wrote: >> >>> Hi Srikanth, >>> >>> Thank you for reporting this and we will provide a solution soon. >>> >>> @Hariprasath - Yes you are correct API 2.0 is deprecated and that does >>> not mean it's currently unavailable. So we should ideally be changing this >>> to the latest version. >>> >>> I managed to reproduce the issue that Srikanth has experienced. The >>> reason for that is endpoint is dynamic. For example my access token should >>> be using https://*us14*.api.mailchimp.com/2.0/users/profile, where as >>> you need to use https://*us12*.api.mailchimp.com/2.0/users/profile for >>> your account. More details can be found in [1] >>> >>> Can we provide a fix for this? >>> >>> [1] http://stackoverflow.com/questions/27875405/invalid-mailchim >>> p-api-key-in-mailchimp-export-api >>> >>> On Mon, Sep 26, 2016 at 4:02 PM, Hariprasath Thanarajah < >>> haripras...@wso2.com> wrote: >>> >>>> Hi Srikanth, >>>> >>>> >>>> On Mon, Sep 26, 2016 at 10:07 AM, Srikanth Puppala < >>>> puppala.srika...@gmail.com> wrote: >>>> >>>>> Hi Malaka, >>>>> >>>>> Thanks for your response. I did not set any email configuration in >>>>> Identity Server or MailChimp. I followed the doc " >>>>> https://docs.wso2.com/display/ISCONNECTORS/Configuring+Mail >>>>> Chimp+Authenticator". >>>>> >>>>> On forums, I see a bug in WSO2 Identity Server [https://wso2.org/jira/ >>>>> browse/IDENTITY-4810]. I tried version 5.1.0 and 5.2.0 version of >>>>> Identity Server and seeing the same problem. >>>>> >>>> I have tried with 5.1.0 and it is working for me(Tried with v2.0 app). >>>> The issue because of the mailChimp API version, We created this for api >>>> v2.0 their we created the federated authenticated User from the email got >>>> from the response of https://apidocs.mailchimp.com/ >>>> api/2.0/users/profile.php but now it is deprecated. Thank you for >>>> pointing it. We will update with mailChimp Authenticator for current API >>>> version. >>>> >>>>> , >>>>> I am not really sure about subject identifier and how to configure it. >>>>> Could you please share any doc which will be helpful. >>>>> >>>> You don't need it to configure. >>>> >>>>> >>>>> Thanks & Regards, >>>>> Srikanth Puppala. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Sun, Sep 25, 2016 at 8:53 PM, Malaka Silva <mal...@wso2.com> wrote: >>>>> >>>>>> Hi Srikanth, >>>>>> >>>>>> I guess you have setup this as the first step and won't be using any >>>>>> other authenticator afterwards? >>>>>> With mail chimp authinticator we are using email as the subject >>>>>> identifier. Hope you have given a email for the user and set the required >>>>>> visibility for the API? >>>>>> >>>>>> @Hariprasath - Please follow up on this issue. >>>>>> >>>>>> On Fri, Sep 23, 2016 at 9:31 PM, Srikanth Puppala < >>>>>> puppala.srika...@gmail.com> wrote: >>>>>> >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I am trying to connect to MailChimp via WSO2 server >>>>>>> using following document: >>>>>>> https://docs.wso2.com/display/ISCONNECTORS/Conf
Re: [Dev] WSO2 Identity Server Error with MailChimp SSO
Yes noted Malaka.
On Monday, September 26, 2016, Malaka Silva <mal...@wso2.com> wrote:
> Hi Srikanth,
>
> Thank you for reporting this and we will provide a solution soon.
>
> @Hariprasath - Yes you are correct API 2.0 is deprecated and that does
> not mean it's currently unavailable. So we should ideally be changing this
> to the latest version.
>
> I managed to reproduce the issue that Srikanth has experienced. The
> reason for that is endpoint is dynamic. For example my access token should
> be using https://*us14*.api.mailchimp.com/2.0/users/profile, where as you
> need to use https://*us12*.api.mailchimp.com/2.0/users/profile for your
> account. More details can be found in [1]
>
> Can we provide a fix for this?
>
> [1] http://stackoverflow.com/questions/27875405/invalid-
> mailchimp-api-key-in-mailchimp-export-api
>
> On Mon, Sep 26, 2016 at 4:02 PM, Hariprasath Thanarajah <
> haripras...@wso2.com
> <javascript:_e(%7B%7D,'cvml','haripras...@wso2.com');>> wrote:
>
>> Hi Srikanth,
>>
>>
>> On Mon, Sep 26, 2016 at 10:07 AM, Srikanth Puppala <
>> puppala.srika...@gmail.com
>> <javascript:_e(%7B%7D,'cvml','puppala.srika...@gmail.com');>> wrote:
>>
>>> Hi Malaka,
>>>
>>> Thanks for your response. I did not set any email configuration in
>>> Identity Server or MailChimp. I followed the doc "
>>> https://docs.wso2.com/display/ISCONNECTORS/Configuring+Mail
>>> Chimp+Authenticator".
>>>
>>> On forums, I see a bug in WSO2 Identity Server [https://wso2.org/jira/
>>> browse/IDENTITY-4810]. I tried version 5.1.0 and 5.2.0 version of
>>> Identity Server and seeing the same problem.
>>>
>> I have tried with 5.1.0 and it is working for me(Tried with v2.0 app).
>> The issue because of the mailChimp API version, We created this for api
>> v2.0 their we created the federated authenticated User from the email got
>> from the response of https://apidocs.mailchimp.com/
>> api/2.0/users/profile.php but now it is deprecated. Thank you for
>> pointing it. We will update with mailChimp Authenticator for current API
>> version.
>>
>>> ,
>>> I am not really sure about subject identifier and how to configure it.
>>> Could you please share any doc which will be helpful.
>>>
>> You don't need it to configure.
>>
>>>
>>> Thanks & Regards,
>>> Srikanth Puppala.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Sun, Sep 25, 2016 at 8:53 PM, Malaka Silva <mal...@wso2.com
>>> <javascript:_e(%7B%7D,'cvml','mal...@wso2.com');>> wrote:
>>>
>>>> Hi Srikanth,
>>>>
>>>> I guess you have setup this as the first step and won't be using any
>>>> other authenticator afterwards?
>>>> With mail chimp authinticator we are using email as the subject
>>>> identifier. Hope you have given a email for the user and set the required
>>>> visibility for the API?
>>>>
>>>> @Hariprasath - Please follow up on this issue.
>>>>
>>>> On Fri, Sep 23, 2016 at 9:31 PM, Srikanth Puppala <
>>>> puppala.srika...@gmail.com
>>>> <javascript:_e(%7B%7D,'cvml','puppala.srika...@gmail.com');>> wrote:
>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> I am trying to connect to MailChimp via WSO2 server
>>>>> using following document:
>>>>> https://docs.wso2.com/display/ISCONNECTORS/Configuring+MailC
>>>>> himp+Authenticator
>>>>>
>>>>>
>>>>> *However I ended up with following error(Any Idea??):*
>>>>> [2016-09-23 15:53:48,353] ERROR {org.wso2.carbon.identity.appl
>>>>> ication.authentication.framework.handler.request.impl.DefaultRequestCoordinator}
>>>>> - Exception in Authentication
>>>>> Frameworkjava.lang.IllegalArgumentException:
>>>>> Failed to create Federated Authenticated User from the given subject
>>>>> identifier. Invalid argument. authenticatedSubjectIdentifier : null
>>>>> at org.wso2.carbon.identity.appli
>>>>> cation.authentication.framework.model.AuthenticatedUser.crea
>>>>> teFederateAuthenticatedUserFromSubjectIdentifier(Authenticat
>>>>> edUser.java:123)
>>>>> at org.wso2.carbon.identity.authe
>>>>> nticator.mailChimp.MailChimpAuthenticator.processAuthenticat
>>>
Re: [Dev] WSO2 Identity Server Error with MailChimp SSO
servlet.http.HttpServlet.service(HttpServlet.java:620) >>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) >>> at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.se >>> rvice(ContextPathServletAdaptor.java:37) >>> at org.eclipse.equinox.http.servlet.internal.ServletRegistratio >>> n.service(ServletRegistration.java:61) >>> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce >>> ssAlias(ProxyServlet.java:128) >>> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi >>> ce(ProxyServlet.java:60) >>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) >>> at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service >>> (DelegationServlet.java:68) >>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi >>> lter(ApplicationFilterChain.java:303) >>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App >>> licationFilterChain.java:208) >>> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilte >>> r.java:52) >>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi >>> lter(ApplicationFilterChain.java:241) >>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App >>> licationFilterChain.java:208) >>> at org.wso2.carbon.ui.filters.CSRFPreventionFilter.doFilter(CSR >>> FPreventionFilter.java:88) >>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi >>> lter(ApplicationFilterChain.java:241) >>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App >>> licationFilterChain.java:208) >>> at org.wso2.carbon.ui.filters.CRLFPreventionFilter.doFilter(CRL >>> FPreventionFilter.java:59) >>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi >>> lter(ApplicationFilterChain.java:241) >>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App >>> licationFilterChain.java:208) >>> at org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilte >>> r(CharacterSetFilter.java:61) >>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi >>> lter(ApplicationFilterChain.java:241) >>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App >>> licationFilterChain.java:208) >>> at org.apache.catalina.core.StandardWrapperValve.invoke(Standar >>> dWrapperValve.java:220) >>> at org.apache.catalina.core.StandardContextValve.invoke(Standar >>> dContextValve.java:122) >>> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(A >>> uthenticatorBase.java:504) >>> at org.apache.catalina.core.StandardHostValve.invoke(StandardHo >>> stValve.java:170) >>> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo >>> rtValve.java:103) >>> at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInv >>> ocation(CompositeValve.java:99) >>> at org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke >>> (CarbonTomcatValve.java:47) >>> at org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(Tena >>> ntLazyLoaderValve.java:57) >>> at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invok >>> eValves(TomcatValveContainer.java:47) >>> at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(Comp >>> ositeValve.java:62) >>> at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetection >>> Valve.invoke(CarbonStuckThreadDetectionValve.java:159) >>> at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogVa >>> lve.java:950) >>> at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve. >>> invoke(CarbonContextCreatorValve.java:57) >>> at org.apache.catalina.core.StandardEngineValve.invoke(Standard >>> EngineValve.java:116) >>> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd >>> apter.java:421) >>> at org.apache.coyote.http11.AbstractHttp11Processor.process(Abs >>> tractHttp11Processor.java:1074) >>> at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler >>> .process(AbstractProtocol.java:611) >>> at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun >>> (NioEndpoint.java:1739) >>> at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor
Re: [Dev] All ESB service calls with data
Hi Palani, Yes it is possible in 4.8.1. You can refer [1] for further details, [1] - https://docs.wso2.com/display/ESB481/Log+Mediator On Tue, Sep 20, 2016 at 10:13 AM, Palani Tester <tmpal...@outlook.com> wrote: > Hi Team, > > > I'm looking for logs, which should record all ESB service calls, class > mediator calls and data. Is it possible to get from ESB 4.8.1 version? > Please let me know, how to configure and what info has to be set... > > > > Thanks, > > Palani > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Thank you and Regards,**Hariprasath Thanarajah* Associate Software Engineer | WSO2 E: haripras...@wso2.com M: +94752806528, 0777216903 Blog: hariwso2.blogspot.com Skype : hariss636 LinkedIn : https://www.linkedin.com/in/hariprasath-thanarajah-5234b660 WSO2, Inc. lean . enterprise . middleware https://wso2.com/signature http://wso2.com/about/team/hariprashath-thanarajah/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Elilmatha Sivanesan
Congratz Elilmatha... On Saturday, September 3, 2016, Kesavan Yogarajah <kesav...@wso2.com> wrote: > Congratulations Elilmatha !!! > > Kesavan Yogarajah > Software Engineer > Mobile :+94 (0) 779 758021 > kesav...@wso2.com <javascript:_e(%7B%7D,'cvml','kesav...@wso2.com');> > WSO2, Inc. > lean . enterprise . middleware > > On Sat, Sep 3, 2016 at 3:55 AM, Malaka Silva <mal...@wso2.com > <javascript:_e(%7B%7D,'cvml','mal...@wso2.com');>> wrote: > >> Hi Devs, >> >> Its my pleasure to welcome Elilmatha Sivanesan as a WSO2 Committer. >> >> She has been working with the WSO2 Platform Extensions Team for a while >> and has contributed to ESB and IS product extensions, >> >> Elilmatha, welcome aboard and keep up the good work. >> >> Best Regards, >> >> Malaka Silva >> Senior Technical Lead >> M: +94 777 219 791 >> Tel : 94 11 214 5345 >> Fax :94 11 2145300 >> Skype : malaka.sampath.silva >> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >> Blog : http://mrmalakasilva.blogspot.com/ >> >> WSO2, Inc. >> lean . enterprise . middleware >> https://wso2.com/signature >> http://www.wso2.com/about/team/malaka-silva/ >> <http://wso2.com/about/team/malaka-silva/> >> https://store.wso2.com/store/ >> >> Don't make Trees rare, we should keep them with care >> >> ___ >> Dev mailing list >> Dev@wso2.org <javascript:_e(%7B%7D,'cvml','Dev@wso2.org');> >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > -- *Thank you and Regards,**Hariprasath Thanarajah* Associate Software Engineer | WSO2 E: haripras...@wso2.com M: +94752806528, 0777216903 Blog: hariwso2.blogspot.com Skype : hariss636 LinkedIn : https://www.linkedin.com/in/hariprasath-thanarajah-5234b660 WSO2, Inc. lean . enterprise . middleware https://wso2.com/signature http://wso2.com/about/team/hariprashath-thanarajah/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] encodeURIComponent is not working in ESB-BETA
Hi Nuwan,
Now it is working as we expected. Thank you for your prompt response.
On Fri, Jun 24, 2016 at 10:36 AM, Nuwan Wimalasekara <nuw...@wso2.com>
wrote:
> Hi Hariprasath,
>
> Seems this is also the same issue as [1] with the rhino17 upgrade. You can
> get rid of this issue when using toString() function whenever accessing a
> string which is concatenated using +.
>
> mc.setProperty('uri.var.requestQuery',requestQuery.toString());
>
> [1]
> https://mozilla.github.io/rhino/javadoc/org/mozilla/javascript/ConsString.html
>
>
> Thanks,
> Nuwanw
>
> On Fri, Jun 24, 2016 at 9:01 AM, Malaka Silva <mal...@wso2.com> wrote:
>
>> Seems like the behavior of encodeURIComponent
>> changed due to rhino upgrade.
>>
>> @Hariprasath - Can you compare the out put from ESB 490 vs ESB 500?
>> Also why are we using [1] to call the endpoint
>> instead of call mediator? AFAIK we agreed to change this during the review?
>>
>>
>> @NuwanW - Any idea?
>>
>> [1]
>> https://github.com/wso2-extensions/esb-connector-powerbi/blob/master/src/main/java/org/wso2/carbon/connector/powerbi/auth/PowerBIAccessTokenGenerator.java
>>
>> On Thu, Jun 23, 2016 at 8:39 PM, Hariprasath Thanarajah <
>> haripras...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> When we trying to run the integration test for PowerBI with the BETA
>>> release we got the following error[1], but in 4.9.0 it is working fine. I
>>> think it is because of [2]. How can we handle this?
>>>
>>> [1]
>>> [2016-06-23 20:19:14,807] INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>> [2016-06-23 20:19:14,807] DEBUG - wire HTTP-Listener I/O dispatcher-1 >>
>>> "[\r][\n]"
>>> [2016-06-23 20:19:14,807] INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>> [2016-06-23 20:19:14,807] DEBUG - wire HTTP-Listener I/O dispatcher-1 >>
>>> "{[\n]"
>>> [2016-06-23 20:19:14,807] INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>> [2016-06-23 20:19:14,807] DEBUG - wire HTTP-Listener I/O dispatcher-1 >>
>>> "[\n]"
>>> [2016-06-23 20:19:14,807] INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>> [2016-06-23 20:19:14,807] DEBUG - wire HTTP-Listener I/O dispatcher-1 >>
>>> "[0x9]"authorizationCode":"AAABiL9Kn2Z27UubvWFPbm0gLdM9QCaEE__Umb9UkVqMUwnGW5ABwXLBdG5PDZbal_1sPGCDl9hb0BntSwR-Ru3gD5buzl8WmK-Xr2k8bIOw5sVZJgQOngtTEZIavKvrWs7vdbJy8VXNyv3YAlQrKDDwZ-MO8cZIOMDzg38LQUa4QwDZeaMr-xBenghSVA91OSr-GRtaMxEo_AZg_q_ajQEMThWYFMIfcjwPsXGf9YkMhNMW_rM_sKm6imyk9L6fkmCqL_AzdvT8WjbPHtam8uyQnTFKtv3Jt7wh3DVfVd1W73_I1k7LJd7ruKyMwiZOXwUDB_S4MnYUS-93_oPQm8V92c6aEOi87Hw9QdYP38mPY-mgYt8DcvSNYH8kBnUO59pC4MjLz34TjJA3VqfsOtUJ1o-AyLDZfpoxmMAIhhfq9gpnfBVA4vK22h_a8RHTQH--H1VUUiHQFhQAQVVsXVMPq2RensvexaJDHhDyhz-g6IKct9dZx6PwnFlHXYsmMuzTeC2BTKhdRnag1ZDzNIA7Q0C7C-mnWFR7n63VtMyMrwWXJQHStkWP7C0KjQFOBQCeZbQyJdGVRCc0nSELCtsgKkgnahvm_9mxmv3AlYjXUkGcUGzMAzsgVQxFzFn23B3B4at9N1BB69gm6vtUMTIkBwUqHtwzQqEEs4WO7WDVYPluq23i1IrmXug8qkoykarPujcccII57plUcj99_vVPPbfjIq51PjmMHpFZxbqjKQZ-pNy-OOLgTVyZDgit8Pt3IAA",[\n]"
>>> [2016-06-23 20:19:14,808] INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>> [2016-06-23 20:19:14,807] DEBUG - wire HTTP-Listener I/O dispatcher-1 >>
>>> "[0x9]"resource":"https://analysis.windows.net/powerbi/api"[\n];
>>> [2016-06-23 20:19:14,808] INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>> [2016-06-23 20:19:14,808] DEBUG - wire HTTP-Listener I/O dispatcher-1 >> "}"
>>> [2016-06-23 20:19:14,852] INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>> [2016-06-23 20:19:14,852] ERROR - SynapseJsonPath #stringValueOf. Error
>>> evaluating JSON Path <$.apiUrl>. Returning empty result. Error>>> invalid
>>> path
>>> [2016-06-23 20:19:14,856] INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>> [2016-06-23 20:19:14,856] ERROR - SynapseJsonPath #stringValueOf. Error
>>> evaluating JSON Path <$.defaultRetentionPolicy>. Returning empty result.
>>> Error>>> invalid path
>>> [2016-06-23 20:19:14,859] INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>> [2016-06-23 20:19:14,859] ERROR - SynapseJsonPath
[Dev] encodeURIComponent is not working in ESB-BETA
result. Error>>>
invalid path
[2016-06-23 20:19:16,267] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-23 20:19:16,267] ERROR - SynapseJsonPath #stringValueOf. Error
evaluating JSON Path <$.map.refresh_token>. Returning empty result.
Error>>> invalid path
[2016-06-23 20:19:16,297] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-23 20:19:16,296] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
"HTTP/1.1 200 OK[\r][\n]"
[2016-06-23 20:19:16,298] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-23 20:19:16,297] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
"Action: urn:getAccessTokenFromAuthorizationCode[\r][\n]"
[2016-06-23 20:19:16,298] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-23 20:19:16,297] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
"Host: localhost:8280[\r][\n]"
[2016-06-23 20:19:16,299] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-23 20:19:16,298] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
"Accept-Charset: UTF-8[\r][\n]"
[2016-06-23 20:19:16,299] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-23 20:19:16,298] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
"Content-Type: application/json; charset=UTF-8[\r][\n]"
[2016-06-23 20:19:16,299] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-23 20:19:16,298] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
"Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2[\r][\n]"
[2016-06-23 20:19:16,299] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-23 20:19:16,298] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
"Date: Thu, 23 Jun 2016 14:49:16 GMT[\r][\n]"
[2016-06-23 20:19:16,299] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-23 20:19:16,298] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
"Transfer-Encoding: chunked[\r][\n]"
[2016-06-23 20:19:16,299] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-23 20:19:16,298] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
"Connection: keep-alive[\r][\n]"
[2016-06-23 20:19:16,299] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-23 20:19:16,299] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
"[\r][\n]"
[2016-06-23 20:19:16,299] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-23 20:19:16,299] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
"1d5[\r][\n]"
[2016-06-23 20:19:16,300] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-23 20:19:16,299] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
"{"map":{"timestamp":"2016-06-23
14:49:15Z","error":"invalid_request","error_codes":{"myArrayList":[90014]},"trace_id":"7df362a8-c56d-401d-b654-93ecd331fbdd","error_description":"AADSTS90014:
The request body must contain the following parameter:
\u0027grant_type\u0027.\r\nTrace ID:
7df362a8-c56d-401d-b654-93ecd331fbdd\r\nCorrelation ID:
a6c86ecc-59ce-49b0-b074-07c3be2b10fb\r\nTimestamp: 2016-06-23
14:49:15Z","correlation_id":"a6c86ecc-59ce-49b0-b074-07c3be2b10fb"}}[\r][\n]"
[2016-06-23 20:19:16,300] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-23 20:19:16,299] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
"0[\r][\n]"
[2016-06-23 20:19:16,300] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-23 20:19:16,299] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
"[\r][\n]"
[2016-06-23 20:19:16,308] ERROR
{org.wso2.carbon.automation.core.PlatformTestManager} - On Test failure..
[2016-06-23 20:19:16,308] ERROR
{org.wso2.carbon.automation.core.PlatformTestManager} -
org.json.JSONException: JSONObject["token_type"] not found.
[2016-06-23 20:19:16,308] INFO
{org.wso2.carbon.automation.core.PlatformTestManager} -
--Tests Failed
org.wso2.carbon.connector.integration.test.powerbi.PowerbiConnectorIntegrationTest.testGetAccessTokenFromAuthorizationCode
[2] -
https://github.com/wso2-extensions/esb-connector-powerbi/blob/master/src/main/resources/powerbi-config/getAccessTokenFromAuthorizationCode.xml#L47
--
*Thank you and Regards**Hariprasath Thanarajah*
Associate Software Engineer | WSO2
E: haripras...@wso2.com
M: +94752806528, 0777216903
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ESB is not handling the invalid response type
at
> java.lang.Thread.run(Thread.java:745)
> [2016-06-21 16:13:54,246] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
> [2016-06-21 16:13:54,244] ERROR - AnonymousListMediator Error while
> building message
> [2016-06-21 16:13:54,246] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
> org.apache.axis2.AxisFault: Error while building Passthrough stream
> [2016-06-21 16:13:54,246] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at
> org.apache.synapse.transport.passthru.util.RelayUtils.handleException(RelayUtils.java:283)
> [2016-06-21 16:13:54,246] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at
> org.apache.synapse.transport.passthru.util.RelayUtils.builldMessage(RelayUtils.java:142)
> [2016-06-21 16:13:54,246] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at
> org.apache.synapse.transport.passthru.util.RelayUtils.buildMessage(RelayUtils.java:98)
> [2016-06-21 16:13:54,247] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:72)
> [2016-06-21 16:13:54,247] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at
> org.apache.synapse.mediators.filters.SwitchMediator.mediate(SwitchMediator.java:178)
> [2016-06-21 16:13:54,247] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at
> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:267)
> [2016-06-21 16:13:54,247] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at
> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.mediateFromContinuationStateStack(Axis2SynapseEnvironment.java:679)
> [2016-06-21 16:13:54,247] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at
> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:244)
> [2016-06-21 16:13:54,247] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at
> org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:529)
> [2016-06-21 16:13:54,247] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at
> org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
> [2016-06-21 16:13:54,247] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at
> org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> [2016-06-21 16:13:54,247] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at
> org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:247)
> [2016-06-21 16:13:54,248] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at
> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
> [2016-06-21 16:13:54,248] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> [2016-06-21 16:13:54,248] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> [2016-06-21 16:13:54,248] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at
> java.lang.Thread.run(Thread.java:745)
> [2016-06-21 16:13:54,248] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
> Caused by: org.apache.axis2.AxisFault: No JSON payload provided.
> [2016-06-21 16:13:54,248] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at
> org.apache.synapse.commons.json.JsonStreamBuilder.processDocument(JsonStreamBuilder.java:52)
> [2016-06-21 16:13:54,248] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at
> org.apache.synapse.transport.passthru.util.DeferredMessageBuilder.getDocument(DeferredMessageBuilder.java:138)
> [2016-06-21 16:13:54,248] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at
> org.apache.synapse.transport.passthru.util.RelayUtils.builldMessage(RelayUtils.java:133)
> [2016-06-21 16:13:54,248] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - ...
> 14 more
> [2016-06-21 16:13:54,249] INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
> [2016-06-21 16:13:54,247] INFO - LogMediator To:
> http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction: ,
> MessageID: urn:uuid:84033421-f5c1-47a3-a3c7-9764c6cd087d, Direction:
> request, MESSAGE = Executing default 'fault' sequence, ERROR_CODE = 0,
> ERROR_MESSAGE = Error while building message, Envelope: encoding='utf-8'?>http://schemas.xmlsoap.org/soap/envelope/
> ">
>
>
> Thank you
>
> --
> Shakila Sivagnanarajah
> Software Engineer
> Mobile :+94 (0) 768 856837
> shak...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
*Thank you and Regards**Hariprasath Thanarajah*
Associate Software Engineer | WSO2
E: haripras...@wso2.com
M: +94752806528, 0777216903
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV] Need to know and contribute
Hi Mayuran, Really nice to hear about your interest in WSO2. You will get some idea about connectors[1] and WSO2-ESB[2]. You may getting help from your seniors since they were already did this. [1] - https://docs.wso2.com/display/ESBCONNECTORS/WSO2+ESB+Connectors [2] - https://docs.wso2.com/display/ESB490/WSO2+Enterprise+Service+Bus+Documentation On Tue, Jun 14, 2016 at 12:08 AM, Tharmalingam Mayuran <tmayura...@gmail.com > wrote: > Hi All, > > I'm Mayuran doing computer science at Department of Computer Science, > University of Jaffna. I was participate the Jaffna meetup last month. I got > some idea about How to contribute to WSO2 and about WSO2 extensions and > their usages. I would like to contribute to WSO2(wso2-extension). Some of > my colleagues were already done this and some are working on this. Could > you please share some useful documentation to understand the basic about > ESB and wso2-extension. I and my friend would like to create an > ESB-Connector. Can anyone suggest a useful connector as well to create? > > Thanks and Regards > Mayuran T > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Thank you and Regards**Hariprasath Thanarajah* Associate Software Engineer | WSO2 E: haripras...@wso2.com M: +94752806528, 0777216903 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Rajjaz Mohammed
Congratz Rajjaz.. On Monday, June 6, 2016, Kanapriya Kuleswararajan <kanapr...@wso2.com> wrote: > Congratz Rajjaz :) > > Kanapriya Kuleswararajan > Associate Software Engineer > Mobile : - 0774894438 > Mail : - kanapr...@wso2.com > <javascript:_e(%7B%7D,'cvml','kanapr...@wso2.com');> > > On Mon, Jun 6, 2016 at 5:32 AM, Nifras Ismail <nif...@wso2.com > <javascript:_e(%7B%7D,'cvml','nif...@wso2.com');>> wrote: > >> congratz Rajjaz!!! >> >> On Mon, Jun 6, 2016 at 6:33 AM, Kevin Ratnasekera <ke...@wso2.com >> <javascript:_e(%7B%7D,'cvml','ke...@wso2.com');>> wrote: >> >>> Congratulations Rajjaz ! >>> >>> On Mon, Jun 6, 2016 at 4:13 AM, Malaka Silva <mal...@wso2.com >>> <javascript:_e(%7B%7D,'cvml','mal...@wso2.com');>> wrote: >>> >>>> Hi Devs, >>>> >>>> Its my pleasure to welcome Rajjaz Mohammed as a WSO2 Committer. >>>> >>>> He has been working with the WSO2 Platform Extensions Team and has >>>> contributed immensely to ESB, IS and CEP product extensions, He is a very >>>> dedicated and committed individual who is eager to learn. >>>> >>>> Rajjaz, welcome aboard and keep up the good work. >>>> >>>> >>>> >>>> Best Regards, >>>> >>>> Malaka Silva >>>> Senior Technical Lead >>>> M: +94 777 219 791 >>>> Tel : 94 11 214 5345 >>>> Fax :94 11 2145300 >>>> Skype : malaka.sampath.silva >>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >>>> Blog : http://mrmalakasilva.blogspot.com/ >>>> >>>> WSO2, Inc. >>>> lean . enterprise . middleware >>>> http://www.wso2.com/ >>>> http://www.wso2.com/about/team/malaka-silva/ >>>> <http://wso2.com/about/team/malaka-silva/> >>>> https://store.wso2.com/store/ >>>> >>>> Save a tree -Conserve nature & Save the world for your future. Print >>>> this email only if it is absolutely necessary. >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org <javascript:_e(%7B%7D,'cvml','Dev@wso2.org');> >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Kevin Ratnaskera* >>> Software Engineer >>> WSO2 Inc. - http://wso2.com >>> lean . enterprise . middleware >>> Mobile - +94774696950 >>> Linkedin - https://www.linkedin.com/in/djkevincr >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org <javascript:_e(%7B%7D,'cvml','Dev@wso2.org');> >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Nifras Ismail >> Associate Software Engineer >> WSO2 >> Email : nif...@wso2.com <javascript:_e(%7B%7D,'cvml','nif...@wso2.com');> >> Mobile : 0094 77 89 90 300 >> >> ___ >> Dev mailing list >> Dev@wso2.org <javascript:_e(%7B%7D,'cvml','Dev@wso2.org');> >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > -- *Thank you and Regards**Hariprasath Thanarajah* Associate Software Engineer | WSO2 E: haripras...@wso2.com M: +94752806528, 0777216903 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Gmail Connector] Error connecting to gmail connector
Hi Maheeka,
For the createAMail operation the required Parameter is raw and it is have
the entire message(eg: to, cc, subject ,etc) and it should be in the
base64url encoded string[1]. From that payload we are getting the "raw"[2]
object and it is in the encoded format, that's why we can't get the
{json-eval($.subject)}. Because in [2] we don't have the json object "
*subject".*
The connector was implemented with above logic(It is in the api
documentaion [1])
[1] -
https://developers.google.com/gmail/api/v1/reference/users/messages/send#auth
[2] - DEBUG - wire <<
"{"raw":"dG86dGhhcmlzNjNAZ21haWwuY29tCnN1YmplY3Q6dGVzdApmcm9tOnRoYXJpczYzQGdtYWlsLmNvbQpjYzp0aGFyaXM2M0BvdXRsb29rLmNvbQpiY2M6dGhhcmlzNjNAeWFob28uY29tCmlkOjE1NGI4YjIyNDVhZmYyMGUKdGhyZWFkSWQ6MTU0YjhiMjI0NWFmZjIwZQoKSGkgaGFyaXByYXNhdGgK"}[\r][\n]"
On Sun, Jun 5, 2016 at 11:55 PM, Maheeka Jayasuriya <mahe...@wso2.com>
wrote:
> Hi Hariprasath,
>
> I am using the connector's input schema and the default values property
> file to set the parameters for invoking the connector's createAMail
> operation. However, the parameter values are not picked up by the connector
> operation. Maybe the expressions are not correct. Can you please take a
> look? If I set as {$func:Recipient} from template parameters it works. It
> doesn't work for {json-eval($.subject)} type parameters.
>
> Please find below a sample proxy service. You can use this proxy to verify.
>
>
> http://ws.apache.org/ns/synapse;
>name="SampleProxy"
>transports="https,http"
>statistics="disable"
>trace="disable"
>startOnLoad="true">
>
>
>
> {"subject":"XXX","messageBody":"This is message
> body"}
>
>
>
> scope="axis2"/>
>
>
> {$ctx:TO}
> {json-eval($.subject)}
> {json-eval($.from)}
> {json-eval($.messageBody)}
> {json-eval($.cc)}
> {json-eval($.bcc)}
> {json-eval($.id)}
> {json-eval($.threadId)}
>
>
>
>
>
>
>
> Thanks,
> Maheeka
>
>
> Maheeka Jayasuriya
> Senior Software Engineer
> Mobile : +9450661
>
> On Sat, Jun 4, 2016 at 11:55 AM, Maheeka Jayasuriya <mahe...@wso2.com>
> wrote:
>
>> Thanks Hariprasad for taking time on helping to resolve the issue. The
>> mentioned approach is now working.
>>
>> Maheeka Jayasuriya
>> Senior Software Engineer
>> Mobile : +9450661
>>
>> On Sat, Jun 4, 2016 at 10:49 AM, Hariprasath Thanarajah <
>> haripras...@wso2.com> wrote:
>>
>>> Hi Maheeka,
>>>
>>> If you are trying to get the refresh token and accessToken from oAuth
>>> playground you should refresh the refreshToken in oAuth playground only
>>> because in oAuth playground it sets the redirect_uri as https%3A%2F%
>>> 2Fdevelopers.google.com%2Foauthplayground is not your app redirect_uri.
>>> So after one hour if you trying any method it gave the error.
>>> Better trying below url[1] to get the code and using [2] to get the
>>> refresh token.
>>>
>>> [1] - https://accounts.google.com/o/oauth2/auth?redirect_uri=*>> redirect-uri>*_type=code_id=**=
>>> https://mail.google.com/+https://www.googleapis.com/auth/gmail.compose+https://www.googleapis.com/auth/gmail.insert+https://www.googleapis.com/auth/gmail.labels+https://www.googleapis.com/auth/gmail.modify+https://www.googleapis.com/auth/gmail.readonly+https://www.googleapis.com/auth/gmail.send_prompt=force_type=offline
>>>
>>> [2] - I have attached below
>>>
>>>
>>> From [2] you can get the refresh_token and you can use it in the init
>>> call. Then you won't get the error.
>>>
>>> On Sat, Jun 4, 2016 at 8:09 AM, Malaka Silva <mal...@wso2.com> wrote:
>>>
>>>> Yes this should be the way. Only use init method before each call.
>>>>
>>>> On Sat, Jun 4, 2016 at 8:00 AM, Shakila Sivagnanarajah <
>>>> shak...@wso2.com> wrote:
>>>>
>>>>> Hi Maheeka,
>>>>>
>>>>> Since the refreshing access token is automated in the connector, you
>>>>> can use following init configuration.
>>>>>
>>>>>
>>>>> {$ctx:refreshToken}
>>>>> {$ctx:clientId}
>>>>> {$
Re: [Dev] Why do we have gmail and gmailRest connector?
Hi Rajkumar,
Yes It was happened like your comment.
Refer subject [1]
[1] - Removing wso2-extension-gmail and rename
wso2-extension-{gmailRest->gmail}
On Sun, Jun 5, 2016 at 8:28 PM, Rajkumar Rajaratnam <rajkum...@wso2.com>
wrote:
> Hi,
>
> I couldn't find gmailRest connector in the store. I think, it is renamed
> to gmail connector and the old gmail connector is removed from the store?
>
> Thanks,
> Raj.
>
> On Thu, May 26, 2016 at 10:49 AM, Malaka Silva <mal...@wso2.com> wrote:
>
>> +1 Latest connector only support all the integration use cases and
>> seamless refresh token logic. No point keeping the the previous one
>> since this is done at early stage.
>>
>> On Thu, May 26, 2016 at 2:38 PM, Hariprasath Thanarajah <
>> haripras...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> Currently we have two connector for gmail operations with ESB [1]
>>>
>>> gmail connector was implemented by using sdk and the gmailRest connector
>>> has implemented using REST api and gmailRest connector has more methods
>>> than gmail connector and has released with input and output schema as well.
>>>
>>> Use cases covered by gmail is already covered with gmailRest in addition
>>> to new methods.
>>>
>>> Can we deprecate the gmail connector?
>>>
>>> [1] - https://store.wso2.com/store/assets/esbconnector/?query=gmail
>>>
>>> --
>>>
>>>
>>> *Thank you and Regards**Hariprasath Thanarajah*
>>> Associate Software Engineer | WSO2
>>> E: haripras...@wso2.com
>>> M: +94752806528, 0777216903
>>>
>>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Malaka Silva
>> Senior Tech Lead
>> M: +94 777 219 791
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>> Skype : malaka.sampath.silva
>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>> Blog : http://mrmalakasilva.blogspot.com/
>>
>> WSO2, Inc.
>> lean . enterprise . middleware
>> http://www.wso2.com/
>> http://www.wso2.com/about/team/malaka-silva/
>> <http://wso2.com/about/team/malaka-silva/>
>> https://store.wso2.com/store/
>>
>> Save a tree -Conserve nature & Save the world for your future. Print this
>> email only if it is absolutely necessary.
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Rajkumar Rajaratnam
> Committer & PMC Member, Apache Stratos
> Software Engineer, WSO2
>
> Mobile : +94777568639
>
--
*Thank you and Regards**Hariprasath Thanarajah*
Associate Software Engineer | WSO2
E: haripras...@wso2.com
M: +94752806528, 0777216903
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Why do we have gmail and gmailRest connector?
Hi, Currently we have two connector for gmail operations with ESB [1] gmail connector was implemented by using sdk and the gmailRest connector has implemented using REST api and gmailRest connector has more methods than gmail connector and has released with input and output schema as well. Use cases covered by gmail is already covered with gmailRest in addition to new methods. Can we deprecate the gmail connector? [1] - https://store.wso2.com/store/assets/esbconnector/?query=gmail -- *Thank you and Regards**Hariprasath Thanarajah* Associate Software Engineer | WSO2 E: haripras...@wso2.com M: +94752806528, 0777216903 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Output Schema generation for Data Mapper - Byte generated as String
Yes then it would be fine Nuwan and I'll proceed with this.
On Wed, May 18, 2016 at 4:43 PM, Nuwan Pallewela <nuw...@wso2.com> wrote:
> Hi Hariprasath,
>
> Raw field holds a byte stream value. As the JSON Schema only have seven
> primitive data types[1], I think current way of defining the type as String
> is the correct way to represent it in the schema. That is because we are
> not going to process this raw in the data mapper any way. We will only map
> it's value into some field in the output message.
> WDYT?
>
> [1] http://json-schema.org/latest/json-schema-core.html#anchor8
>
> Thanks,
> Nuwan
>
> On Wed, May 18, 2016 at 3:47 PM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Hi Nuwan,
>>
>> I have attached the file that I used to create the output schema for
>> listTheHistory method for Gmail REST connector.
>>
>> On Wed, May 18, 2016 at 3:42 PM, Nuwan Pallewela <nuw...@wso2.com> wrote:
>>
>>> Hi Hariprasath,
>>>
>>> How did you generate the schema and what is the payload you used to
>>> generate it?
>>>
>>> Thanks,
>>> Nuwan
>>>
>>> On Wed, May 18, 2016 at 3:32 PM, Hariprasath Thanarajah <
>>> haripras...@wso2.com> wrote:
>>>
>>>> Hi All,
>>>>
>>>> Currently I am doing the schema generation for Gmail REST connector. In
>>>> most of the methods in this connector have the response part as[1], But in
>>>> the JSON schema the type was generated as string[2].
>>>>
>>>> Is there any way to generate as bytes or is it ok to proceed as below?
>>>>
>>>> [1] - {
>>>> "id": string,
>>>> "threadId": string,
>>>> "labelIds": [
>>>> string
>>>> ],
>>>> "snippet": string,
>>>> "historyId": unsigned long,
>>>> "internalDate": long,
>>>> "payload": {
>>>> "partId": string,
>>>> "mimeType": string,
>>>> "filename": string,
>>>> "headers": [
>>>> {
>>>> "name": string,
>>>> "value": string
>>>> }
>>>> ],
>>>> "body": users.messages.attachments Resource,
>>>> "parts": [
>>>> (MessagePart)
>>>> ]
>>>> },
>>>> "sizeEstimate": integer,
>>>> "raw": bytes
>>>> }
>>>>
>>>> [2] -
>>>> {"id":"http:\/\/wso2jsonschema.org","title":"root","$schema":"http:\/\/
>>>> json-schema.org
>>>> \/draft-04\/schema#","properties":{"history":{"id":"http:\/\/
>>>> wso2jsonschema.org\/history","items":[{"id":"http:\/\/
>>>> wso2jsonschema.org\/history\/0","properties":{"id":{"id":"http:\/\/
>>>> wso2jsonschema.org
>>>> \/history\/0\/id","type":"number"},"labelsRemoved":{"id":"http:\/\/
>>>> wso2jsonschema.org
>>>> \/history\/0\/labelsRemoved","items":[{"id":"http:\/\/
>>>> wso2jsonschema.org
>>>> \/history\/0\/labelsRemoved\/0","properties":{"message":{"id":"http:\/\/
>>>> wso2jsonschema.org
>>>> \/history\/0\/labelsRemoved\/0\/message","properties":{
>>>> "raw":{"id":"http:\/\/wso2jsonschema.org
>>>> \/history\/0\/labelsRemoved\/0\/message\/raw","type":"string"
>>>> },"id":{"id":"http:\/\/wso2jsonschema.org
>>>> \/history\/0\/labelsRemoved\/0\/message\/id","type":"string"},"labelIds":{"id":"http:\/\/
>>>> wso2jsonschema.org
>>>> \/history\/0\/labelsRemoved\/0\/message\/labelIds","items":[{"id":"http:\/\/
>>>> wso2jsonschema.org
>>>> \/history\/0\/labelsRemoved\/0\/message\/labelIds\/0","type":"string"}],"type":"array"},"threadId":{"id":"http:\/\/
>>>> wso2jsonschema.org
>>>> \/history\/0\/labelsRemoved\/0\/message\/threadId&q
[Dev] Output Schema generation for Data Mapper - Byte generated as String
quot;id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/headers\/0\/value","type":"string"}},"type":"object"}],"type":"array"},"filename":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/filename","type":"string"},"partId":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/partId","type":"string"},"mimeType":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/mimeType","type":"string"}},"type":"object"}],"type":"array"},"partId":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/partId","type":"string"},"mimeType":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/mimeType","type":"string"}},"type":"object"},"sizeEstimate":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/sizeEstimate","type":"number"},"snippet":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/snippet","type":"string"},"internalDate":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/internalDate","type":"string"}},"type":"object"},"labelIds":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/labelIds","items":[{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/labelIds\/0","type":"string"}],"type":"array"}},"type":"object"}],"type":"array"},"messagesDeleted":{"id":"http:\/\/
wso2jsonschema.org\/history\/0\/messagesDeleted","items":[{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/messagesDeleted\/0","type":"object"}],"type":"array"},"messagesAdded":{"id":"http:\/\/
wso2jsonschema.org\/history\/0\/messagesAdded","items":[{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/messagesAdded\/0","type":"object"}],"type":"array"},"labelsAdded":{"id":"http:\/\/
wso2jsonschema.org\/history\/0\/labelsAdded","items":[{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsAdded\/0","type":"object"}],"type":"array"},"messages":{"id":"http:\/\/
wso2jsonschema.org\/history\/0\/messages","items":[{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/messages\/0","type":"object"}],"type":"array"}},"type":"object"}],"type":"array"},"historyId":{"id":"http:\/\/
wso2jsonschema.org
\/historyId","type":"string"},"nextPageToken":{"id":"http:\/\/
wso2jsonschema.org\/nextPageToken","type":"string"}},"type":"object"}
--
*Thank you and Regards**Hariprasath Thanarajah*
Associate Software Engineer | WSO2
E: haripras...@wso2.com
M: +94752806528, 0777216903
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error while implementing the Integration test for salesforce(SOAP API) connector
Hi Malaka, As an offline chat with Buddhima, if a certain version of automation frame work needs a certain axis2 version, then there should be a release version of automation framework along with that axis2. On Mon, May 9, 2016 at 9:56 AM, Hariprasath Thanarajah <haripras...@wso2.com > wrote: > Noted malaka. > > > On Monday, May 9, 2016, Malaka Silva <mal...@wso2.com> wrote: > >> I think this is nothing to do with wso2-synapse. You need to change >> automation framework accordingly. >> >> On Mon, May 9, 2016 at 9:48 AM, Hariprasath Thanarajah < >> haripras...@wso2.com> wrote: >> >>> Yes Malaka. I think we have to change the axis2 version to 1.6.1-wso2v17 >>> in the wso2-synapse. Then we can release the connector with integration >>> test. >>> >>> >>> On Monday, May 9, 2016, Malaka Silva <mal...@wso2.com> wrote: >>> >>>> Hi Hariprasath, >>>> >>>> So clearly this is nothing to do with ESB. Dependency you are getting >>>> from automation is causing this issue. >>>> >>>> On Sun, May 8, 2016 at 10:01 PM, Hariprasath Thanarajah < >>>> haripras...@wso2.com> wrote: >>>> >>>>> Hi Malaka, >>>>> >>>>> In the integration test It takes the axis2-version from wso2-synapse >>>>> according to[1]. But still the version of axis2 in wso2-synapse is >>>>> 1.6.1-wso2v12 according to [2]. When I locally change the version to >>>>> axis2-1.6.1-wso2v17 >>>>> and built then the integration test for salesforce is running as we >>>>> expected. >>>>> >>>>> [1] - >>>>> https://github.com/wso2-extensions/esb-connector-salesforce/blob/master/pom.xml#L34 >>>>> [2] - https://github.com/wso2/wso2-synapse/blob/master/pom.xml#L1003 >>>>> >>>>> On Fri, May 6, 2016 at 9:49 AM, Malaka Silva <mal...@wso2.com> wrote: >>>>> >>>>>> Hi Hariprasath, >>>>>> >>>>>> I had an offline discussion with Dharshana. Seems like the issue is >>>>>> related the a mismatch and it takes the bundle from aytomation framework >>>>>> rather than from esb plugins. >>>>>> >>>>>> Since the issue is not related to ESB 5, send the pr so that we can >>>>>> resolve the issue. (Anyway we need to update the version in product ESB) >>>>>> >>>>>> Try upgrading the automation version or manually adding the >>>>>> axis2-1.6.1-wso2v17 dependency to >>>>>> test run time. >>>>>> >>>>>> On Tue, May 3, 2016 at 1:31 PM, Hariprasath Thanarajah < >>>>>> haripras...@wso2.com> wrote: >>>>>> >>>>>>> Noted Malaka. >>>>>>> >>>>>>> On Tue, May 3, 2016 at 1:05 PM, Malaka Silva <mal...@wso2.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Hariprasath great if you could create the pr(master branch) and add >>>>>>>> to the jira. >>>>>>>> >>>>>>>> On Tue, May 3, 2016 at 1:02 PM, Hariprasath Thanarajah < >>>>>>>> haripras...@wso2.com> wrote: >>>>>>>> >>>>>>>>> Hi Malaka/Chanaka, >>>>>>>>> >>>>>>>>> The axis2-1.6.1-wso2v17 is bundled with ESB 5.0.0 Alpha but For >>>>>>>>> the integration test it takes axis2-1.6.1-wso2v12 from the >>>>>>>>> highlighted in >>>>>>>>> [1]. >>>>>>>>> >>>>>>>>> This is required for Salesforce integration test. We need to get >>>>>>>>> it fix in BETA release. >>>>>>>>> >>>>>>>>> [1] - >>>>>>>>> https://github.com/wso2/product-esb/blob/v5.0.0-ALPHA/pom.xml#L1064 >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> >>>>>>>>> On Tue, May 3, 2016 at 12:09 PM, Malaka Silva <mal...@wso2.com> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hi Hariprasath, >>>>>>>>>> >>>>>>>>>> Can we verify the [1] fix is there with ESB 5.0.0 alph
[Dev] Fwd: Why we Keep older versions in the new Releases?
Hi All, In every release of our product we didn't upgrade the dependency versions in the pom file. For example take wso2-synapse and wso2-axis2. The new released version of axis2 according to [1] is v1.6.1-wso2v17 and wso2-synapse is 2.1.7-wso2v3-ALPHA. But in the synapse still the version of axis2 according to [2] is v1.6.1-wso2v12. Is there any particular reason to keep the older version in the new release? I think we need to check with latest releases before releasing a new version of product. When we using the older versions in the new releases we didn't get the new changes from those dependencies. correct If I am wrong. [1] - https://github.com/wso2/wso2-axis2/blob/v1.6.1-wso2v17/pom.xml#L31 [2] - https://github.com/wso2/wso2-synapse/blob/v2.1.7-wso2v3-ALPHA/pom.xml#L1003 -- *Thank you and Regards**Hariprasath Thanarajah* Associate Software Engineer | WSO2 E: haripras...@wso2.com M: +94752806528, 0777216903 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error while implementing the Integration test for salesforce(SOAP API) connector
Noted malaka. On Monday, May 9, 2016, Malaka Silva <mal...@wso2.com> wrote: > I think this is nothing to do with wso2-synapse. You need to change > automation framework accordingly. > > On Mon, May 9, 2016 at 9:48 AM, Hariprasath Thanarajah < > haripras...@wso2.com > <javascript:_e(%7B%7D,'cvml','haripras...@wso2.com');>> wrote: > >> Yes Malaka. I think we have to change the axis2 version to 1.6.1-wso2v17 >> in the wso2-synapse. Then we can release the connector with integration >> test. >> >> >> On Monday, May 9, 2016, Malaka Silva <mal...@wso2.com >> <javascript:_e(%7B%7D,'cvml','mal...@wso2.com');>> wrote: >> >>> Hi Hariprasath, >>> >>> So clearly this is nothing to do with ESB. Dependency you are getting >>> from automation is causing this issue. >>> >>> On Sun, May 8, 2016 at 10:01 PM, Hariprasath Thanarajah < >>> haripras...@wso2.com> wrote: >>> >>>> Hi Malaka, >>>> >>>> In the integration test It takes the axis2-version from wso2-synapse >>>> according to[1]. But still the version of axis2 in wso2-synapse is >>>> 1.6.1-wso2v12 according to [2]. When I locally change the version to >>>> axis2-1.6.1-wso2v17 >>>> and built then the integration test for salesforce is running as we >>>> expected. >>>> >>>> [1] - >>>> https://github.com/wso2-extensions/esb-connector-salesforce/blob/master/pom.xml#L34 >>>> [2] - https://github.com/wso2/wso2-synapse/blob/master/pom.xml#L1003 >>>> >>>> On Fri, May 6, 2016 at 9:49 AM, Malaka Silva <mal...@wso2.com> wrote: >>>> >>>>> Hi Hariprasath, >>>>> >>>>> I had an offline discussion with Dharshana. Seems like the issue is >>>>> related the a mismatch and it takes the bundle from aytomation framework >>>>> rather than from esb plugins. >>>>> >>>>> Since the issue is not related to ESB 5, send the pr so that we can >>>>> resolve the issue. (Anyway we need to update the version in product ESB) >>>>> >>>>> Try upgrading the automation version or manually adding the >>>>> axis2-1.6.1-wso2v17 dependency to >>>>> test run time. >>>>> >>>>> On Tue, May 3, 2016 at 1:31 PM, Hariprasath Thanarajah < >>>>> haripras...@wso2.com> wrote: >>>>> >>>>>> Noted Malaka. >>>>>> >>>>>> On Tue, May 3, 2016 at 1:05 PM, Malaka Silva <mal...@wso2.com> wrote: >>>>>> >>>>>>> Hariprasath great if you could create the pr(master branch) and add >>>>>>> to the jira. >>>>>>> >>>>>>> On Tue, May 3, 2016 at 1:02 PM, Hariprasath Thanarajah < >>>>>>> haripras...@wso2.com> wrote: >>>>>>> >>>>>>>> Hi Malaka/Chanaka, >>>>>>>> >>>>>>>> The axis2-1.6.1-wso2v17 is bundled with ESB 5.0.0 Alpha but For the >>>>>>>> integration test it takes axis2-1.6.1-wso2v12 from the highlighted in >>>>>>>> [1]. >>>>>>>> >>>>>>>> This is required for Salesforce integration test. We need to get it >>>>>>>> fix in BETA release. >>>>>>>> >>>>>>>> [1] - >>>>>>>> https://github.com/wso2/product-esb/blob/v5.0.0-ALPHA/pom.xml#L1064 >>>>>>>> >>>>>>>> Thanks, >>>>>>>> >>>>>>>> On Tue, May 3, 2016 at 12:09 PM, Malaka Silva <mal...@wso2.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi Hariprasath, >>>>>>>>> >>>>>>>>> Can we verify the [1] fix is there with ESB 5.0.0 alpha please? >>>>>>>>> >>>>>>>>> [1] https://github.com/wso2/wso2-axis2/pull/73 >>>>>>>>> >>>>>>>>> On Mon, May 2, 2016 at 11:16 PM, Chanaka Fernando < >>>>>>>>> chana...@wso2.com> wrote: >>>>>>>>> >>>>>>>>>> Hi Hariprasath, >>>>>>>>>> >>>>>>>>>> ESB 5.0.0 - Alpha has been released with the axis2 version >>>>>&g
Re: [Dev] Error while implementing the Integration test for salesforce(SOAP API) connector
Yes Malaka. I think we have to change the axis2 version to 1.6.1-wso2v17 in the wso2-synapse. Then we can release the connector with integration test. On Monday, May 9, 2016, Malaka Silva <mal...@wso2.com> wrote: > Hi Hariprasath, > > So clearly this is nothing to do with ESB. Dependency you are getting from > automation is causing this issue. > > On Sun, May 8, 2016 at 10:01 PM, Hariprasath Thanarajah < > haripras...@wso2.com > <javascript:_e(%7B%7D,'cvml','haripras...@wso2.com');>> wrote: > >> Hi Malaka, >> >> In the integration test It takes the axis2-version from wso2-synapse >> according to[1]. But still the version of axis2 in wso2-synapse is >> 1.6.1-wso2v12 according to [2]. When I locally change the version to >> axis2-1.6.1-wso2v17 >> and built then the integration test for salesforce is running as we >> expected. >> >> [1] - >> https://github.com/wso2-extensions/esb-connector-salesforce/blob/master/pom.xml#L34 >> [2] - https://github.com/wso2/wso2-synapse/blob/master/pom.xml#L1003 >> >> On Fri, May 6, 2016 at 9:49 AM, Malaka Silva <mal...@wso2.com >> <javascript:_e(%7B%7D,'cvml','mal...@wso2.com');>> wrote: >> >>> Hi Hariprasath, >>> >>> I had an offline discussion with Dharshana. Seems like the issue is >>> related the a mismatch and it takes the bundle from aytomation framework >>> rather than from esb plugins. >>> >>> Since the issue is not related to ESB 5, send the pr so that we can >>> resolve the issue. (Anyway we need to update the version in product ESB) >>> >>> Try upgrading the automation version or manually adding the >>> axis2-1.6.1-wso2v17 dependency to >>> test run time. >>> >>> On Tue, May 3, 2016 at 1:31 PM, Hariprasath Thanarajah < >>> haripras...@wso2.com >>> <javascript:_e(%7B%7D,'cvml','haripras...@wso2.com');>> wrote: >>> >>>> Noted Malaka. >>>> >>>> On Tue, May 3, 2016 at 1:05 PM, Malaka Silva <mal...@wso2.com >>>> <javascript:_e(%7B%7D,'cvml','mal...@wso2.com');>> wrote: >>>> >>>>> Hariprasath great if you could create the pr(master branch) and add to >>>>> the jira. >>>>> >>>>> On Tue, May 3, 2016 at 1:02 PM, Hariprasath Thanarajah < >>>>> haripras...@wso2.com >>>>> <javascript:_e(%7B%7D,'cvml','haripras...@wso2.com');>> wrote: >>>>> >>>>>> Hi Malaka/Chanaka, >>>>>> >>>>>> The axis2-1.6.1-wso2v17 is bundled with ESB 5.0.0 Alpha but For the >>>>>> integration test it takes axis2-1.6.1-wso2v12 from the highlighted in >>>>>> [1]. >>>>>> >>>>>> This is required for Salesforce integration test. We need to get it >>>>>> fix in BETA release. >>>>>> >>>>>> [1] - >>>>>> https://github.com/wso2/product-esb/blob/v5.0.0-ALPHA/pom.xml#L1064 >>>>>> >>>>>> Thanks, >>>>>> >>>>>> On Tue, May 3, 2016 at 12:09 PM, Malaka Silva <mal...@wso2.com >>>>>> <javascript:_e(%7B%7D,'cvml','mal...@wso2.com');>> wrote: >>>>>> >>>>>>> Hi Hariprasath, >>>>>>> >>>>>>> Can we verify the [1] fix is there with ESB 5.0.0 alpha please? >>>>>>> >>>>>>> [1] https://github.com/wso2/wso2-axis2/pull/73 >>>>>>> >>>>>>> On Mon, May 2, 2016 at 11:16 PM, Chanaka Fernando <chana...@wso2.com >>>>>>> <javascript:_e(%7B%7D,'cvml','chana...@wso2.com');>> wrote: >>>>>>> >>>>>>>> Hi Hariprasath, >>>>>>>> >>>>>>>> ESB 5.0.0 - Alpha has been released with the axis2 version >>>>>>>> 1.6.1.wso2v17 (kernel 4.4.5) and it should have this fix included. >>>>>>>> Please >>>>>>>> double check this on the correct alpha pack. >>>>>>>> >>>>>>>> On Mon, May 2, 2016 at 12:12 PM, Malaka Silva <mal...@wso2.com >>>>>>>> <javascript:_e(%7B%7D,'cvml','mal...@wso2.com');>> wrote: >>>>>>>> >>>>>>>>> Thx >>>>>>>>> >>>>>>>>> On Mon, May 2, 2016 at 12:11 PM, Hariprasath Thanarajah < >>>>>&
Re: [Dev] Error while implementing the Integration test for salesforce(SOAP API) connector
Hi Malaka, In the integration test It takes the axis2-version from wso2-synapse according to[1]. But still the version of axis2 in wso2-synapse is 1.6.1-wso2v12 according to [2]. When I locally change the version to axis2-1.6.1-wso2v17 and built then the integration test for salesforce is running as we expected. [1] - https://github.com/wso2-extensions/esb-connector-salesforce/blob/master/pom.xml#L34 [2] - https://github.com/wso2/wso2-synapse/blob/master/pom.xml#L1003 On Fri, May 6, 2016 at 9:49 AM, Malaka Silva <mal...@wso2.com> wrote: > Hi Hariprasath, > > I had an offline discussion with Dharshana. Seems like the issue is > related the a mismatch and it takes the bundle from aytomation framework > rather than from esb plugins. > > Since the issue is not related to ESB 5, send the pr so that we can > resolve the issue. (Anyway we need to update the version in product ESB) > > Try upgrading the automation version or manually adding the > axis2-1.6.1-wso2v17 dependency to > test run time. > > On Tue, May 3, 2016 at 1:31 PM, Hariprasath Thanarajah < > haripras...@wso2.com> wrote: > >> Noted Malaka. >> >> On Tue, May 3, 2016 at 1:05 PM, Malaka Silva <mal...@wso2.com> wrote: >> >>> Hariprasath great if you could create the pr(master branch) and add to >>> the jira. >>> >>> On Tue, May 3, 2016 at 1:02 PM, Hariprasath Thanarajah < >>> haripras...@wso2.com> wrote: >>> >>>> Hi Malaka/Chanaka, >>>> >>>> The axis2-1.6.1-wso2v17 is bundled with ESB 5.0.0 Alpha but For the >>>> integration test it takes axis2-1.6.1-wso2v12 from the highlighted in [1]. >>>> >>>> This is required for Salesforce integration test. We need to get it fix >>>> in BETA release. >>>> >>>> [1] - >>>> https://github.com/wso2/product-esb/blob/v5.0.0-ALPHA/pom.xml#L1064 >>>> >>>> Thanks, >>>> >>>> On Tue, May 3, 2016 at 12:09 PM, Malaka Silva <mal...@wso2.com> wrote: >>>> >>>>> Hi Hariprasath, >>>>> >>>>> Can we verify the [1] fix is there with ESB 5.0.0 alpha please? >>>>> >>>>> [1] https://github.com/wso2/wso2-axis2/pull/73 >>>>> >>>>> On Mon, May 2, 2016 at 11:16 PM, Chanaka Fernando <chana...@wso2.com> >>>>> wrote: >>>>> >>>>>> Hi Hariprasath, >>>>>> >>>>>> ESB 5.0.0 - Alpha has been released with the axis2 version >>>>>> 1.6.1.wso2v17 (kernel 4.4.5) and it should have this fix included. Please >>>>>> double check this on the correct alpha pack. >>>>>> >>>>>> On Mon, May 2, 2016 at 12:12 PM, Malaka Silva <mal...@wso2.com> >>>>>> wrote: >>>>>> >>>>>>> Thx >>>>>>> >>>>>>> On Mon, May 2, 2016 at 12:11 PM, Hariprasath Thanarajah < >>>>>>> haripras...@wso2.com> wrote: >>>>>>> >>>>>>>> Hi Malaka, >>>>>>>> >>>>>>>> I have created the jira[1] with highest priority, >>>>>>>> >>>>>>>> [1] >>>>>>>> https://wso2.org/jira/browse/ESBJAVA-4582 >>>>>>>> >>>>>>>> On Mon, May 2, 2016 at 11:31 AM, Malaka Silva <mal...@wso2.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi Hariprasath, >>>>>>>>> >>>>>>>>> Ideally fix should go with latest ESB. If you find the same issue >>>>>>>>> with ESB 5 Alpha, please report a jira with highest priority. >>>>>>>>> >>>>>>>>> On Mon, May 2, 2016 at 11:25 AM, Hariprasath Thanarajah < >>>>>>>>> haripras...@wso2.com> wrote: >>>>>>>>> >>>>>>>>>> Hi Malaka, >>>>>>>>>> >>>>>>>>>> I have changed the code in wso2-axis2 according to [1] and put it >>>>>>>>>> as a patch. Now it's working perfectly. Thank you everyone for your >>>>>>>>>> suggestions. >>>>>>>>>> >>>>>>>>>> [1] >>>>>>>>>> https://github.com/wso2-support/wso2-axis2/pull/1/files >>>>>>>>>> <https://www.
Re: [Dev] Fwd: Removing is-connectors and esb-connectors from wso2
+1 for Malaka's suggestion, Because we have already released those connectors with new repos. On Sat, May 7, 2016 at 8:04 PM, Malaka Silva <mal...@wso2.com> wrote: > Most of those were added internally. Can we soon move those to new repos > and close these repos? > > This is confusing since there are duplicates. > > On Sat, May 7, 2016 at 4:35 PM, Kathees Rajendram <kath...@wso2.com> > wrote: > >> Hi Malaka, >> >> Before removing two is-connectors and esb-connectors repos, we need to >> check the open PRs [1] [2] and incorporate the changes to new extension >> repo if those changes are required. >> >> [1] - https://github.com/wso2/is-connectors/pulls >> [2] - https://github.com/wso2/esb-connectors/pulls >> >> Thanks, >> >> On Sat, May 7, 2016 at 3:10 PM, Rajjaz Mohammed <raj...@wso2.com> wrote: >> >>> +1, >>> >>> Having codes in two places may mislead outside contributors. >>> >>> On Sat, May 7, 2016 at 2:52 PM, Malaka Silva <mal...@wso2.com> wrote: >>> >>>> >>>> Hi All, >>>> >>>> We may not need [1] and [2] anymore since all the extensions are >>>> already moved to individual repos in [3]. If there are objections let me >>>> know? >>>> >>>> [1] https://github.com/wso2/is-connectors >>>> [2] https://github.com/wso2/esb-connectors >>>> [3] https://github.com/wso2-extensions >>>> >>>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Thank you >>> Best Regards >>> >>> *Rajjaz HM* >>> Associate Software Engineer >>> Platform Extension Team >>> WSO2 Inc. <http://wso2.com/> >>> lean | enterprise | middleware >>> Mobile | +94752833834|+94777226874 >>> Email | raj...@wso2.com >>> LinkedIn <https://lk.linkedin.com/in/hmohammedrajjaz> | Blogger >>> <http://wso2experience.blogspot.com/> | WSO2 Profile >>> <http://wso2.com/about/team/mohammer-rajjaz/> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Kathees >> Software Engineer, >> email: kath...@wso2.com >> mobile: +94772596173 >> > > > > -- > > Best Regards, > > Malaka Silva > Senior Tech Lead > M: +94 777 219 791 > Tel : 94 11 214 5345 > Fax :94 11 2145300 > Skype : malaka.sampath.silva > LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 > Blog : http://mrmalakasilva.blogspot.com/ > > WSO2, Inc. > lean . enterprise . middleware > http://www.wso2.com/ > http://www.wso2.com/about/team/malaka-silva/ > <http://wso2.com/about/team/malaka-silva/> > https://store.wso2.com/store/ > > Save a tree -Conserve nature & Save the world for your future. Print this > email only if it is absolutely necessary. > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Thank you and Regards**Hariprasath Thanarajah* Associate Software Engineer | WSO2 E: haripras...@wso2.com M: +94752806528, 0777216903 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error while implementing the Integration test for salesforce(SOAP API) connector
Noted malaka. On Thursday, April 21, 2016, Malaka Silva <mal...@wso2.com> wrote: > Hi Hariprasath, > > Best is start debugging fresh pack with the release tag and apply the fix > and check [1]. > > Did you check this with esb 5 alpha alread? If not do so. > > [1] > https://docs.wso2.com/display/TA430/Debugging+Product+Integration+Tests > > On Thu, Apr 21, 2016 at 2:53 AM, Hariprasath Thanarajah < > haripras...@wso2.com > <javascript:_e(%7B%7D,'cvml','haripras...@wso2.com');>> wrote: > >> As malaka said this is slightly different from the usual way and Malaka, >> I copied the patch to the folder and put the zip to the repository. Need to >> investigate further. >> >> >> On Wednesday, April 20, 2016, Malaka Silva <mal...@wso2.com >> <javascript:_e(%7B%7D,'cvml','mal...@wso2.com');>> wrote: >> >>> Hariprasath is doing this for connectors. It is slightly different than >>> running esb integration tests. We need to copy the zip file >>> to repository folder. Hope you have updated the zip file with patch in that >>> case. >>> >>> On Wed, Apr 20, 2016 at 10:08 PM, Thusitha Thilina Dayaratne < >>> thusit...@wso2.com> wrote: >>> >>>> Hi Hariprasath, >>>> >>>> Did you apply the patch manually to the pack when you run the >>>> integration test? AFAIK when you run integration tests it will use the >>>> already built default pack. It will not contains the patch. >>>> >>>> Thanks >>>> Thusitha >>>> >>>> On Wed, Apr 20, 2016 at 9:32 AM, Malaka Silva <mal...@wso2.com> wrote: >>>> >>>>> Hi Hariprasath, >>>>> >>>>> You need to debug and investigate this further. Find details on >>>>> debugging integration test in [1] >>>>> >>>>> [1] >>>>> https://docs.wso2.com/display/TA430/Debugging+Product+Integration+Tests >>>>> >>>>> On Wed, Apr 20, 2016 at 6:18 PM, Hariprasath Thanarajah < >>>>> haripras...@wso2.com> wrote: >>>>> >>>>>> Hi All, >>>>>> >>>>>> I have apply the patch to ESB 4.9.0 have mentioned above in [1], but >>>>>> I got the same error. If I create the test case for another >>>>>> method(describeSObject) also show the same error. I have attached the >>>>>> wire >>>>>> log for this method also, >>>>>> >>>>>> Can anyone give any suggestion on this? >>>>>> >>>>>> On Tue, Apr 19, 2016 at 1:36 PM, Hariprasath Thanarajah < >>>>>> haripras...@wso2.com> wrote: >>>>>> >>>>>>> Noted Malaka, >>>>>>> >>>>>>> I will check and update on this. >>>>>>> >>>>>>> On Tue, Apr 19, 2016 at 1:11 PM, Malaka Silva <mal...@wso2.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Hariprasath, >>>>>>>> >>>>>>>> Seems like a issue is mentioned in [1]. Ideally this should be >>>>>>>> fixed in ESB alpha release. Please check. >>>>>>>> >>>>>>>> If not apply the fix and see if that works. If works add a jira for >>>>>>>> esb 5. >>>>>>>> >>>>>>>> [1] https://wso2.org/jira/browse/ESBJAVA-4388 >>>>>>>> >>>>>>>> On Thu, Apr 7, 2016 at 3:59 PM, Hariprasath Thanarajah < >>>>>>>> haripras...@wso2.com> wrote: >>>>>>>> >>>>>>>>> Hi All, >>>>>>>>> >>>>>>>>> I am working on to create integration test for salesforce >>>>>>>>> connector. When I create the testcase for a particular >>>>>>>>> method(getUserInfo) >>>>>>>>> I got the response via the ESB call but after that I get the following >>>>>>>>> error in [1]. >>>>>>>>> >>>>>>>>> I have added the proxy[2] and soap request[3] as well. >>>>>>>>> >>>>>>>>> Can anyone suggest me what could be the reason for this follwing >>>>>>>>> error. >>>>>>>>> >>>>>&
Re: [Dev] Error while implementing the Integration test for salesforce(SOAP API) connector
As malaka said this is slightly different from the usual way and Malaka, I
copied the patch to the folder and put the zip to the repository. Need to
investigate further.
On Wednesday, April 20, 2016, Malaka Silva <mal...@wso2.com> wrote:
> Hariprasath is doing this for connectors. It is slightly different than
> running esb integration tests. We need to copy the zip file
> to repository folder. Hope you have updated the zip file with patch in that
> case.
>
> On Wed, Apr 20, 2016 at 10:08 PM, Thusitha Thilina Dayaratne <
> thusit...@wso2.com <javascript:_e(%7B%7D,'cvml','thusit...@wso2.com');>>
> wrote:
>
>> Hi Hariprasath,
>>
>> Did you apply the patch manually to the pack when you run the
>> integration test? AFAIK when you run integration tests it will use the
>> already built default pack. It will not contains the patch.
>>
>> Thanks
>> Thusitha
>>
>> On Wed, Apr 20, 2016 at 9:32 AM, Malaka Silva <mal...@wso2.com
>> <javascript:_e(%7B%7D,'cvml','mal...@wso2.com');>> wrote:
>>
>>> Hi Hariprasath,
>>>
>>> You need to debug and investigate this further. Find details on
>>> debugging integration test in [1]
>>>
>>> [1]
>>> https://docs.wso2.com/display/TA430/Debugging+Product+Integration+Tests
>>>
>>> On Wed, Apr 20, 2016 at 6:18 PM, Hariprasath Thanarajah <
>>> haripras...@wso2.com
>>> <javascript:_e(%7B%7D,'cvml','haripras...@wso2.com');>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> I have apply the patch to ESB 4.9.0 have mentioned above in [1], but I
>>>> got the same error. If I create the test case for another
>>>> method(describeSObject) also show the same error. I have attached the wire
>>>> log for this method also,
>>>>
>>>> Can anyone give any suggestion on this?
>>>>
>>>> On Tue, Apr 19, 2016 at 1:36 PM, Hariprasath Thanarajah <
>>>> haripras...@wso2.com
>>>> <javascript:_e(%7B%7D,'cvml','haripras...@wso2.com');>> wrote:
>>>>
>>>>> Noted Malaka,
>>>>>
>>>>> I will check and update on this.
>>>>>
>>>>> On Tue, Apr 19, 2016 at 1:11 PM, Malaka Silva <mal...@wso2.com
>>>>> <javascript:_e(%7B%7D,'cvml','mal...@wso2.com');>> wrote:
>>>>>
>>>>>> Hi Hariprasath,
>>>>>>
>>>>>> Seems like a issue is mentioned in [1]. Ideally this should be fixed
>>>>>> in ESB alpha release. Please check.
>>>>>>
>>>>>> If not apply the fix and see if that works. If works add a jira for
>>>>>> esb 5.
>>>>>>
>>>>>> [1] https://wso2.org/jira/browse/ESBJAVA-4388
>>>>>>
>>>>>> On Thu, Apr 7, 2016 at 3:59 PM, Hariprasath Thanarajah <
>>>>>> haripras...@wso2.com
>>>>>> <javascript:_e(%7B%7D,'cvml','haripras...@wso2.com');>> wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> I am working on to create integration test for salesforce connector.
>>>>>>> When I create the testcase for a particular method(getUserInfo) I got
>>>>>>> the
>>>>>>> response via the ESB call but after that I get the following error in
>>>>>>> [1].
>>>>>>>
>>>>>>> I have added the proxy[2] and soap request[3] as well.
>>>>>>>
>>>>>>> Can anyone suggest me what could be the reason for this follwing
>>>>>>> error.
>>>>>>>
>>>>>>> [1]
>>>>>>> FAILED: testGetUserInfoWithMandatoryParameters
>>>>>>> Salesforce {getUserInfo} integration test with mandatory
>>>>>>> parameters.
>>>>>>> java.lang.NullPointerException
>>>>>>> at
>>>>>>> org.apache.axis2.transport.http.AbstractHTTPSender.processCookieHeaders(AbstractHTTPSender.java:213)
>>>>>>> at
>>>>>>> org.apache.axis2.transport.http.AbstractHTTPSender.obtainHTTPHeaderInformation(AbstractHTTPSender.java:170)
>>>>>>> at
>>>>>>> org.apache.axis2.transport.http.AbstractHTTPSender.processResponse(AbstractHTTPSender.java:224)
>>>>>>> at
>>>>>>> org.apache.a
Re: [Dev] Error while implementing the Integration test for salesforce(SOAP API) connector
Noted Malaka,
I will check and update on this.
On Tue, Apr 19, 2016 at 1:11 PM, Malaka Silva <mal...@wso2.com> wrote:
> Hi Hariprasath,
>
> Seems like a issue is mentioned in [1]. Ideally this should be fixed in
> ESB alpha release. Please check.
>
> If not apply the fix and see if that works. If works add a jira for esb 5.
>
> [1] https://wso2.org/jira/browse/ESBJAVA-4388
>
> On Thu, Apr 7, 2016 at 3:59 PM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Hi All,
>>
>> I am working on to create integration test for salesforce connector. When
>> I create the testcase for a particular method(getUserInfo) I got the
>> response via the ESB call but after that I get the following error in [1].
>>
>> I have added the proxy[2] and soap request[3] as well.
>>
>> Can anyone suggest me what could be the reason for this follwing error.
>>
>> [1]
>> FAILED: testGetUserInfoWithMandatoryParameters
>> Salesforce {getUserInfo} integration test with mandatory
>> parameters.
>> java.lang.NullPointerException
>> at
>> org.apache.axis2.transport.http.AbstractHTTPSender.processCookieHeaders(AbstractHTTPSender.java:213)
>> at
>> org.apache.axis2.transport.http.AbstractHTTPSender.obtainHTTPHeaderInformation(AbstractHTTPSender.java:170)
>> at
>> org.apache.axis2.transport.http.AbstractHTTPSender.processResponse(AbstractHTTPSender.java:224)
>> at
>> org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:294)
>> at
>> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:196)
>> at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
>> at
>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:451)
>> at
>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:278)
>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>> at
>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
>> at
>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
>> at
>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
>> at
>> org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.sendSOAPRequest(ConnectorIntegrationTestBase.java:616)
>> at
>> org.wso2.carbon.connector.integration.test.salesforce.SalesforceConnectorIntegrationTest.testGetUserInfoWithMandatoryParameters(SalesforceConnectorIntegrationTest.java:60)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at
>> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
>> at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
>> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
>> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
>> at
>> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
>> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
>> at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
>> at org.testng.TestRunner.privateRun(TestRunner.java:757)
>> at org.testng.TestRunner.run(TestRunner.java:608)
>> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
>> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
>> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
>> at org.testng.SuiteRunner.run(SuiteRunner.java:240)
>> at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
>> at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
>> at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
>> at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
>> at org.testng.TestNG.run(TestNG.java:999)
>> at
>> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178)
>> at
>> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92)
>> at
>> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96)
>> at sun.reflect.NativeMethodAccessor
Re: [Dev] Error while implementing the Integration test for salesforce(SOAP API) connector
Hi Malaka,
I am doing it now. I'll update the status by evening.
On Fri, Apr 8, 2016 at 2:24 PM, Malaka Silva <mal...@wso2.com> wrote:
> Hariprasath shall we try debugging this?
>
> On Thu, Apr 7, 2016 at 10:47 PM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Hi Malaka,
>>
>> No In this I set the blocking as false and also test it with ESB
>> 5.0.0-M1.
>>
>> On Thu, Apr 7, 2016 at 9:08 PM, Malaka Silva <mal...@wso2.com> wrote:
>>
>>> Hariprasath seems like this is related to [1]. Are you using call
>>> mediator in blocking mode? If so avoid it for integration tests with esb
>>> 490.
>>>
>>> [1] https://wso2.org/jira/browse/ESBJAVA-4388
>>>
>>> On Thu, Apr 7, 2016 at 3:59 PM, Hariprasath Thanarajah <
>>> haripras...@wso2.com> wrote:
>>>
>>>> Hi All,
>>>>
>>>> I am working on to create integration test for salesforce connector.
>>>> When I create the testcase for a particular method(getUserInfo) I got the
>>>> response via the ESB call but after that I get the following error in [1].
>>>>
>>>> I have added the proxy[2] and soap request[3] as well.
>>>>
>>>> Can anyone suggest me what could be the reason for this follwing error.
>>>>
>>>> [1]
>>>> FAILED: testGetUserInfoWithMandatoryParameters
>>>> Salesforce {getUserInfo} integration test with mandatory
>>>> parameters.
>>>> java.lang.NullPointerException
>>>> at
>>>> org.apache.axis2.transport.http.AbstractHTTPSender.processCookieHeaders(AbstractHTTPSender.java:213)
>>>> at
>>>> org.apache.axis2.transport.http.AbstractHTTPSender.obtainHTTPHeaderInformation(AbstractHTTPSender.java:170)
>>>> at
>>>> org.apache.axis2.transport.http.AbstractHTTPSender.processResponse(AbstractHTTPSender.java:224)
>>>> at
>>>> org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:294)
>>>> at
>>>> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:196)
>>>> at
>>>> org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
>>>> at
>>>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:451)
>>>> at
>>>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:278)
>>>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>>>> at
>>>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
>>>> at
>>>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
>>>> at
>>>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
>>>> at
>>>> org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.sendSOAPRequest(ConnectorIntegrationTestBase.java:616)
>>>> at
>>>> org.wso2.carbon.connector.integration.test.salesforce.SalesforceConnectorIntegrationTest.testGetUserInfoWithMandatoryParameters(SalesforceConnectorIntegrationTest.java:60)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>> at
>>>> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
>>>> at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
>>>> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
>>>> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
>>>> at
>>>> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
>>>> at
>>>> org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
>>>> at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
>>>> at org.testng.TestRunner.privateRun(TestRunner.java:757)
>>>> at org.testng.TestRunner.run(TestRunner.java:608)
>>>> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
>>
Re: [Dev] Error while implementing the Integration test for salesforce(SOAP API) connector
Hi Malaka,
No In this I set the blocking as false and also test it with ESB 5.0.0-M1.
On Thu, Apr 7, 2016 at 9:08 PM, Malaka Silva <mal...@wso2.com> wrote:
> Hariprasath seems like this is related to [1]. Are you using call mediator
> in blocking mode? If so avoid it for integration tests with esb 490.
>
> [1] https://wso2.org/jira/browse/ESBJAVA-4388
>
> On Thu, Apr 7, 2016 at 3:59 PM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Hi All,
>>
>> I am working on to create integration test for salesforce connector. When
>> I create the testcase for a particular method(getUserInfo) I got the
>> response via the ESB call but after that I get the following error in [1].
>>
>> I have added the proxy[2] and soap request[3] as well.
>>
>> Can anyone suggest me what could be the reason for this follwing error.
>>
>> [1]
>> FAILED: testGetUserInfoWithMandatoryParameters
>> Salesforce {getUserInfo} integration test with mandatory
>> parameters.
>> java.lang.NullPointerException
>> at
>> org.apache.axis2.transport.http.AbstractHTTPSender.processCookieHeaders(AbstractHTTPSender.java:213)
>> at
>> org.apache.axis2.transport.http.AbstractHTTPSender.obtainHTTPHeaderInformation(AbstractHTTPSender.java:170)
>> at
>> org.apache.axis2.transport.http.AbstractHTTPSender.processResponse(AbstractHTTPSender.java:224)
>> at
>> org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:294)
>> at
>> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:196)
>> at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
>> at
>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:451)
>> at
>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:278)
>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>> at
>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
>> at
>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
>> at
>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
>> at
>> org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.sendSOAPRequest(ConnectorIntegrationTestBase.java:616)
>> at
>> org.wso2.carbon.connector.integration.test.salesforce.SalesforceConnectorIntegrationTest.testGetUserInfoWithMandatoryParameters(SalesforceConnectorIntegrationTest.java:60)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at
>> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
>> at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
>> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
>> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
>> at
>> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
>> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
>> at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
>> at org.testng.TestRunner.privateRun(TestRunner.java:757)
>> at org.testng.TestRunner.run(TestRunner.java:608)
>> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
>> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
>> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
>> at org.testng.SuiteRunner.run(SuiteRunner.java:240)
>> at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
>> at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
>> at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
>> at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
>> at org.testng.TestNG.run(TestNG.java:999)
>> at
>> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178)
>> at
>> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92)
>> at
>> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0
Re: [Dev] Error while implementing the Integration test for salesforce(SOAP API) connector
Hi All,
I have attached the wire log here.
On Thu, Apr 7, 2016 at 3:59 PM, Hariprasath Thanarajah <haripras...@wso2.com
> wrote:
> Hi All,
>
> I am working on to create integration test for salesforce connector. When
> I create the testcase for a particular method(getUserInfo) I got the
> response via the ESB call but after that I get the following error in [1].
>
> I have added the proxy[2] and soap request[3] as well.
>
> Can anyone suggest me what could be the reason for this follwing error.
>
> [1]
> FAILED: testGetUserInfoWithMandatoryParameters
> Salesforce {getUserInfo} integration test with mandatory
> parameters.
> java.lang.NullPointerException
> at
> org.apache.axis2.transport.http.AbstractHTTPSender.processCookieHeaders(AbstractHTTPSender.java:213)
> at
> org.apache.axis2.transport.http.AbstractHTTPSender.obtainHTTPHeaderInformation(AbstractHTTPSender.java:170)
> at
> org.apache.axis2.transport.http.AbstractHTTPSender.processResponse(AbstractHTTPSender.java:224)
> at
> org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:294)
> at
> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:196)
> at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:451)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:278)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
> at
> org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.sendSOAPRequest(ConnectorIntegrationTestBase.java:616)
> at
> org.wso2.carbon.connector.integration.test.salesforce.SalesforceConnectorIntegrationTest.testGetUserInfoWithMandatoryParameters(SalesforceConnectorIntegrationTest.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
> at
> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
> at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
> at org.testng.TestRunner.privateRun(TestRunner.java:757)
> at org.testng.TestRunner.run(TestRunner.java:608)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
> at org.testng.SuiteRunner.run(SuiteRunner.java:240)
> at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
> at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
> at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
> at org.testng.TestNG.run(TestNG.java:999)
> at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178)
> at
> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92)
> at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInPr
[Dev] Error while implementing the Integration test for salesforce(SOAP API) connector
tx:username}
{$ctx:password}
[3]
http://schemas.xmlsoap.org/soap/envelope/;
xmlns:urn="wso2.connector.salesforce">
%s(loginUrl)
%s(username)
%s(password)
getUserInfo
--
*Thank you and Regards**Hariprasath Thanarajah*
Associate Software Engineer | WSO2
E: haripras...@wso2.com
M: +94752806528, 0777216903
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [IS Authenticator] Issue in logout from mailchimp authenticator
As Malithi mentioned the issue is by the host. I have changed the
SAML2.IdPURL as https://127.0.0.1:9443/samlsso in the travelocity webapp.
Now it is working. Thank you guys for your help.
On Thu, Feb 18, 2016 at 2:48 PM, Indunil Upeksha Rathnayake <
indu...@wso2.com> wrote:
> Hi Hariprasath,
>
> This error occurs when session has already been expired, when logout
> request is sent. Please try the same scenario, after enabling session
> persistence and configuring a higher value for SSO session time out as
> follows(Default : 15min).
>
> You can enable session persistence using following property in
> identity.xml file.
>
> * true*
> After WSO2IS 5.1.0, it has been enabled by default.
>
>
> You can configure SSO session time out as follows.
> If you are using WSO2IS 5.1.0. you can configure it using following
> property in repository/conf/identity/identity.xml file
>
> * 15*
>
> If you are using WSO2IS 5.0.0, you can configure it using following
> property in repository/conf/tomcat/carbon/WEB-INF/web.xml file
>
>
> * 15 *
>
> Please refer [1] for more details.
>
> Thanks and Regards
>
> On Thu, Feb 18, 2016 at 11:24 AM, Malithi Edirisinghe <malit...@wso2.com>
> wrote:
>
>> Hi Haripasath,
>>
>> When analyzing the trace that you have attached I noted that the IdP
>> hostname has been changed from localhost -> 127.0.0.1 -> localhost. IS
>> maintains the logged in session via a cookie set to the IdP Url. These
>> cookies are set against the hostname in the browser.
>>
>> So in your case, after the successful authentication 'samlssoTokenId' is
>> set against 127.0.0.1 hostname. But the login request is sent under
>> 'localhost' hostname. So the cookie is not sent back to the server there.
>> So the server cannot find the session with regard to this logout request.
>>
>> Please make sure that you use the same hostname along the full flow
>> either localhost or 127.0.0.1
>>
>> Thanks,
>> Malithi.
>>
>> On Thu, Feb 18, 2016 at 12:45 AM, Hariprasath Thanarajah <
>> haripras...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> I couldn't find the reason behind this why is this happening. Can anyone
>>> have any idea ?
>>>
>>> On Fri, Feb 5, 2016 at 12:56 PM, Hariprasath Thanarajah <
>>> haripras...@wso2.com> wrote:
>>>
>>>> Hi Philips,
>>>>
>>>> Any update on this?
>>>>
>>>> On Tue, Feb 2, 2016 at 2:57 PM, Hariprasath Thanarajah <
>>>> haripras...@wso2.com> wrote:
>>>>
>>>>> Hi Philips,
>>>>>
>>>>> You can find the SSO tracer in the following attachment.
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Feb 2, 2016 at 2:22 PM, Chamara Philips <chama...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Hariprasath,
>>>>>> It is because the sessionID is null. It will be helpfull, if you can
>>>>>> attach the SSO tracer.
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> On Tue, Feb 2, 2016 at 11:58 AM, Hariprasath Thanarajah <
>>>>>> haripras...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> I have implemented mailChimp Authenticator for IS. When I logout
>>>>>>> from sample webapp(travelocity.com) i got the below error,
>>>>>>>
>>>>>>> [2016-02-02 11:41:01,907] ERROR
>>>>>>> {org.wso2.carbon.identity.sso.saml.processors.SPInitLogoutRequestProcessor}
>>>>>>> - ssoTokenId cookie not found in the logout request
>>>>>>>
>>>>>>>
>>>>>>> Any suggestions?
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>>
>>>>>>> *Thank you and Regards**Hariprasath Thanarajah*
>>>>>>> Associate Software Engineer | WSO2
>>>>>>> E: haripras...@wso2.com
>>>>>>> M: +94752806528
>>>>>>>
>>>>>>>
>>>>>>> ___
>>>>>>> Dev mailing list
>>>>>>> Dev@wso2.org
>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>&
Re: [Dev] [IS Authenticator] Issue in logout from mailchimp authenticator
Hi All,
I couldn't find the reason behind this why is this happening. Can anyone
have any idea ?
On Fri, Feb 5, 2016 at 12:56 PM, Hariprasath Thanarajah <
haripras...@wso2.com> wrote:
> Hi Philips,
>
> Any update on this?
>
> On Tue, Feb 2, 2016 at 2:57 PM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Hi Philips,
>>
>> You can find the SSO tracer in the following attachment.
>>
>>
>>
>> On Tue, Feb 2, 2016 at 2:22 PM, Chamara Philips <chama...@wso2.com>
>> wrote:
>>
>>> Hi Hariprasath,
>>> It is because the sessionID is null. It will be helpfull, if you can
>>> attach the SSO tracer.
>>>
>>> Thanks.
>>>
>>> On Tue, Feb 2, 2016 at 11:58 AM, Hariprasath Thanarajah <
>>> haripras...@wso2.com> wrote:
>>>
>>>> Hi All,
>>>>
>>>> I have implemented mailChimp Authenticator for IS. When I logout from
>>>> sample webapp(travelocity.com) i got the below error,
>>>>
>>>> [2016-02-02 11:41:01,907] ERROR
>>>> {org.wso2.carbon.identity.sso.saml.processors.SPInitLogoutRequestProcessor}
>>>> - ssoTokenId cookie not found in the logout request
>>>>
>>>>
>>>> Any suggestions?
>>>>
>>>> --
>>>>
>>>>
>>>> *Thank you and Regards**Hariprasath Thanarajah*
>>>> Associate Software Engineer | WSO2
>>>> E: haripras...@wso2.com
>>>> M: +94752806528
>>>>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Hareendra Chamara Philips
>>> *Software Engineer*
>>> Mobile : +94 (0) 767 184161 <%2B94%20%280%29%20773%20451194>
>>> chama...@wso2.com <thili...@wso2.com>
>>>
>>>
>>
>>
>> --
>>
>>
>> *Thank you and Regards**Hariprasath Thanarajah*
>> Associate Software Engineer | WSO2
>> E: haripras...@wso2.com
>> M: +94752806528
>>
>>
>
>
> --
>
>
> *Thank you and Regards**Hariprasath Thanarajah*
> Associate Software Engineer | WSO2
> E: haripras...@wso2.com
> M: +94752806528
>
>
--
*Thank you and Regards**Hariprasath Thanarajah*
Associate Software Engineer | WSO2
E: haripras...@wso2.com
M: +94752806528
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [IS Authenticator] Issue in logout from mailchimp authenticator
Hi Philips,
You can find the SSO tracer in the following attachment.
On Tue, Feb 2, 2016 at 2:22 PM, Chamara Philips <chama...@wso2.com> wrote:
> Hi Hariprasath,
> It is because the sessionID is null. It will be helpfull, if you can
> attach the SSO tracer.
>
> Thanks.
>
> On Tue, Feb 2, 2016 at 11:58 AM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Hi All,
>>
>> I have implemented mailChimp Authenticator for IS. When I logout from
>> sample webapp(travelocity.com) i got the below error,
>>
>> [2016-02-02 11:41:01,907] ERROR
>> {org.wso2.carbon.identity.sso.saml.processors.SPInitLogoutRequestProcessor}
>> - ssoTokenId cookie not found in the logout request
>>
>>
>> Any suggestions?
>>
>> --
>>
>>
>> *Thank you and Regards**Hariprasath Thanarajah*
>> Associate Software Engineer | WSO2
>> E: haripras...@wso2.com
>> M: +94752806528
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Hareendra Chamara Philips
> *Software Engineer*
> Mobile : +94 (0) 767 184161 <%2B94%20%280%29%20773%20451194>
> chama...@wso2.com <thili...@wso2.com>
>
>
--
*Thank you and Regards**Hariprasath Thanarajah*
Associate Software Engineer | WSO2
E: haripras...@wso2.com
M: +94752806528
trace
Description: Binary data
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [IS Authenticator] Issue in logout from mailchimp authenticator
Hi All,
I have implemented mailChimp Authenticator for IS. When I logout from
sample webapp(travelocity.com) i got the below error,
[2016-02-02 11:41:01,907] ERROR
{org.wso2.carbon.identity.sso.saml.processors.SPInitLogoutRequestProcessor}
- ssoTokenId cookie not found in the logout request
Any suggestions?
--
*Thank you and Regards**Hariprasath Thanarajah*
Associate Software Engineer | WSO2
E: haripras...@wso2.com
M: +94752806528
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Sachith Withana
Congratz Sachith... On Tue, Dec 1, 2015 at 11:17 AM, Nalaka Perera <nal...@wso2.com> wrote: > Congratz Sachith Aiya..! :) > > *Nalaka Perera* > > *Intern - Software Engineering* > *WSO2* > > *Mobile: * *+94 71 9165748 <%2B94%2071%209165748>* > > On Tue, Dec 1, 2015 at 11:14 AM, Vithulan Vijayanandan <vithu...@wso2.com> > wrote: > >> Congratzz aiyaa! :D >> >> On Tue, Dec 1, 2015 at 11:10 AM, Nuwan Pallewela <nuw...@wso2.com> wrote: >> >>> Congratz sachith >>> >>> On Tue, Dec 1, 2015 at 11:00 AM, Malintha Adikari <malin...@wso2.com> >>> wrote: >>> >>>> Congratulations Sachith... >>>> >>>> On Tue, Dec 1, 2015 at 10:59 AM, Dunith Dhanushka <dun...@wso2.com> >>>> wrote: >>>> >>>>> Congrats Sachith! >>>>> >>>>> On Tue, Dec 1, 2015 at 10:54 AM, Anjana Fernando <anj...@wso2.com> >>>>> wrote: >>>>> >>>>>> Hi everyone, >>>>>> >>>>>> It is my pleasure to welcome Sachith as a WSO2 committer. He has done >>>>>> numerous contributions to the Data Analytics Server product, in doing >>>>>> development and bringing in ideas, and has proved to be a valuable and a >>>>>> dependable person. So Sachith welcome aboard, and keep up with the good >>>>>> work! .. >>>>>> >>>>>> Cheers, >>>>>> Anjana. >>>>>> -- >>>>>> *Anjana Fernando* >>>>>> Senior Technical Lead >>>>>> WSO2 Inc. | http://wso2.com >>>>>> lean . enterprise . middleware >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Regards, >>>>> >>>>> Dunith Dhanushka, >>>>> Senior Software Engineer >>>>> WSO2 Inc, >>>>> >>>>> Mobile - +94 71 8615744 >>>>> Blog - dunithd.wordpress.com <http://blog.dunith.com> >>>>> Twitter - @dunithd <http://twitter.com/dunithd> >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Malintha Adikari* >>>> Software Engineer >>>> WSO2 Inc.; http://wso2.com >>>> lean.enterprise.middleware >>>> >>>> Mobile: +94 71 2312958 >>>> Blog:http://malinthas.blogspot.com >>>> Page: http://about.me/malintha >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> -- >>> >>> *Nuwan Chamara Pallewela* >>> >>> >>> *Software Engineer* >>> >>> *WSO2, Inc. *http://wso2.com >>> *lean . enterprise . middleware* >>> >>> Email *nuw...@wso2.com <nuw...@wso2.com>* >>> Mobile *+94719079739 <%2B94719079739>@* >>> >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Vithulan MV* >> >> Intern-Software Engineering >> WSO2, Inc : wso2.com >> Mobile: +94712540524 >> >> ___ >> 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 > > -- *Thank you and Regards**Hariprasath Thanarajah* Associate Software Engineer | WSO2 E: haripras...@wso2.com M: +94752806528 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Connection issue in Salesforce Streaming API
Hi all, I am working on Salesforce Streaming Inbound. There is only problem i noticed in my code is that if there is a network failure then the CometD session is expired , from that it can't reconnect because the HttpSession is remains as same but the cometD Rehandshake happened with different clientId(Server Session is different). But in the documentation they mentioned that we must reconnect the connection if there any unexpected network distruption, From my home network it is working continuously But if the network failure around 2 minutes only the problem will occur. Any suggestion? -- *Thank you and Regards**Hariprasath Thanarajah* Associate Software Engineer | WSO2 E: haripras...@wso2.com M: +94752806528 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Shakila Sivagnanarajah
Congratz Shakila... On Wed, Oct 28, 2015 at 8:51 PM, Malaka Silva <mal...@wso2.com> wrote: > Hi Devs, > > Its my pleasure to welcome Shakila Sivagnanarajah as a WSO2 Committer. > > Shakila has been a member of the Platform Extensions Team (Earlier > Connector Team) contributing immensely to many aspects ESB Product, ESB > Connectors development ever since she joined us. butions, ownership shown > towards the tasks/responsibilities assigned to her. She is always > enthusiastic to learn new things by further investigating the issues > in-depth. > > Shakila, welcome aboard and keep up the good work .. ! > > Best Regards, > > Malaka Silva > Senior Tech Lead > M: +94 777 219 791 > Tel : 94 11 214 5345 > Fax :94 11 2145300 > Skype : malaka.sampath.silva > LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 > Blog : http://mrmalakasilva.blogspot.com/ > > WSO2, Inc. > lean . enterprise . middleware > http://www.wso2.com/ > http://www.wso2.com/about/team/malaka-silva/ > <http://wso2.com/about/team/malaka-silva/> > https://store.wso2.com/store/ > > Save a tree -Conserve nature & Save the world for your future. Print this > email only if it is absolutely necessary. > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Thank you and Regards**Hariprasath Thanarajah* Associate Software Engineer | WSO2 E: haripras...@wso2.com M: +94752806528 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error on FHIR connector integration Test case
Hi Saneth, FHIR is in the development phase and they released a set of third party testing server to check the FHIR resources. You can find the list of test servers on [1] [1] http://wiki.hl7.org/index.php?title=Publicly_Available_FHIR_Servers_for_testing I manually checked with the same pack it is working fine. I resolved this issue by adding the certificate to the product and ESB. Earlier I only added the certification to the ESB. Now it's working fine. Thank you all. On Wed, Oct 14, 2015 at 8:25 AM, Saneth Dharmakeerthi <sane...@wso2.com> wrote: > Hi Hariprasath, > > 1) What do you mean by "testing with the test server"? > 2) Could you able to do this task manually using same pack?. > 3) Put a debug point at the line you add the certification and > execute that line, then try the rest of the actions manually and see > the behaviour. > > Also share the testcase code > > Thanks and Best Regards, > > Saneth Dharmakeerthi > Senior Software Engineer > WSO2, Inc. > Mobile: +94772325511 > > On Tue, Oct 13, 2015 at 4:52 PM, Hariprasath Thanarajah < > haripras...@wso2.com> wrote: > >> Hi Rajjaz, >> >> I already added the certification like you mentioned in [2]. But still >> it's giving the same error. >> >> On Tue, Oct 13, 2015 at 4:41 PM, Rajjaz Mohammed <raj...@wso2.com> wrote: >> >>> Hi, >>> its seems to be like a error i got earlier so what i did is i import the >>> certificate through the terminal like[1] and its solved my error. >>> >>> AFAIK test server not will be the reason for this error. and try the way >>> [2]. >>> >>> [1]Navigate to "/repository/resources/security/" using command prompt >>> and execute keytool -importcert -file CERT_FILE_NAME -keystore >>> client-truststore.jks -alias "CERT_NAME" in command line to import api >>> certificate in to keystore. Give "*wso2carbon*" as password. >>> >>> [2] >>> http://wso2-oxygen-tank.10903.n7.nabble.com/Dev-Connector-Integration-Test-Error-SSL-Handshake-Exception-td98612.html >>> >>> On Tue, Oct 13, 2015 at 3:55 PM, Rajeenthini Satkunam < >>> rajeenth...@wso2.com> wrote: >>> >>>> Hi Hariprasanth, >>>> >>>> You can search for this subject "*[Dev] Connector Integration Test >>>> Error!- SSL Handshake Exception*" .This could help you to give some >>>> idea about the error. >>>> >>>> On Tue, Oct 13, 2015 at 3:42 PM, Hariprasath Thanarajah < >>>> haripras...@wso2.com> wrote: >>>> >>>>> Hi all, >>>>> >>>>> Is it the error came because of the testing server? I am testing with >>>>> the test server because it is only available for FHIR. The FHIR is in the >>>>> development phase. >>>>> >>>>> On Tue, Oct 13, 2015 at 11:13 AM, Hariprasath Thanarajah < >>>>> haripras...@wso2.com> wrote: >>>>> >>>>>> Hi All , >>>>>> >>>>>> I got the response at the wire. But after that only i am getting the >>>>>> above error[1]. >>>>>> >>>>>> On Tue, Oct 13, 2015 at 11:08 AM, Hariprasath Thanarajah < >>>>>> haripras...@wso2.com> wrote: >>>>>> >>>>>>> Hi Elilmatha, >>>>>>> >>>>>>> I already included the certificates at client-truststore.jks as well >>>>>>> as wso2carbon.jks. >>>>>>> >>>>>>> On Tue, Oct 13, 2015 at 11:06 AM, Elilmatha Sivanesan < >>>>>>> elilma...@wso2.com> wrote: >>>>>>> >>>>>>>> Hi Hariprasath, >>>>>>>> >>>>>>>> As per you error log you need to include the certificate. >>>>>>>> >>>>>>>> Thanks. >>>>>>>> >>>>>>>> On Tue, Oct 13, 2015 at 10:56 AM, Hariprasath Thanarajah < >>>>>>>> haripras...@wso2.com> wrote: >>>>>>>> >>>>>>>>> Hi All, >>>>>>>>> >>>>>>>>> I am working on FHIR connector. I got the following[1] error while >>>>>>>>> I am running the integration test case of FHIR. Any suggestion on this >>>>>>>>> error? >>>>>>>>> >>>>>>>>> >>&g
Re: [Dev] Error on FHIR connector integration Test case
Hi all,
Is it the error came because of the testing server? I am testing with the
test server because it is only available for FHIR. The FHIR is in the
development phase.
On Tue, Oct 13, 2015 at 11:13 AM, Hariprasath Thanarajah <
haripras...@wso2.com> wrote:
> Hi All ,
>
> I got the response at the wire. But after that only i am getting the
> above error[1].
>
> On Tue, Oct 13, 2015 at 11:08 AM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Hi Elilmatha,
>>
>> I already included the certificates at client-truststore.jks as well as
>> wso2carbon.jks.
>>
>> On Tue, Oct 13, 2015 at 11:06 AM, Elilmatha Sivanesan <elilma...@wso2.com
>> > wrote:
>>
>>> Hi Hariprasath,
>>>
>>> As per you error log you need to include the certificate.
>>>
>>> Thanks.
>>>
>>> On Tue, Oct 13, 2015 at 10:56 AM, Hariprasath Thanarajah <
>>> haripras...@wso2.com> wrote:
>>>
>>>> Hi All,
>>>>
>>>> I am working on FHIR connector. I got the following[1] error while I am
>>>> running the integration test case of FHIR. Any suggestion on this error?
>>>>
>>>>
>>>>
>>>> [1]
>>>> [2015-10-13 10:49:58,488] ERROR
>>>> {org.wso2.carbon.automation.core.PlatformTestManager} - On Test failure..
>>>> [2015-10-13 10:49:58,488] ERROR
>>>> {org.wso2.carbon.automation.core.PlatformTestManager} -
>>>> javax.net.ssl.SSLHandshakeException:
>>>> sun.security.validator.ValidatorException: PKIX path building failed:
>>>> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
>>>> valid certification path to requested target
>>>> [2015-10-13 10:49:58,489] INFO
>>>> {org.wso2.carbon.automation.core.PlatformTestManager} -
>>>> --Tests Failed
>>>> org.wso2.carbon.connector.integration.test.fhir.fhirConnectorIntegrationTest.readResource
>>>> [2015-10-13 10:49:58,503] INFO
>>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>>> [2015-10-13 10:49:58,503] WARN - ProxyServiceAdmin No proxy service exists
>>>> by the name : fhir
>>>> [2015-10-13 10:49:58,525] INFO
>>>> {org.wso2.carbon.automation.api.clients.proxy.admin.ProxyServiceAdminClient}
>>>> - Proxy Deleted
>>>> FAILED: readResource
>>>> fhir {readResource} integration test.
>>>> javax.net.ssl.SSLHandshakeException:
>>>> sun.security.validator.ValidatorException: PKIX path building failed:
>>>> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
>>>> valid certification path to requested target
>>>> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
>>>> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1904)
>>>> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:279)
>>>> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:273)
>>>> at
>>>> sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1446)
>>>> at
>>>> sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:209)
>>>> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:901)
>>>> at sun.security.ssl.Handshaker.process_record(Handshaker.java:837)
>>>> at
>>>> sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1023)
>>>> at
>>>> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1332)
>>>> at
>>>> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1359)
>>>> at
>>>> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1343)
>>>> at
>>>> sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:563)
>>>> at
>>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
>>>> at
>>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1301)
>>>> at
>>>> java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468)
>>>> at
>>>> sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338)
>>>> at
>>>> org.wso2.connector.integration.test.base.ConnectorIntegratio
Re: [Dev] Error on FHIR connector integration Test case
Hi Rajjaz,
I already added the certification like you mentioned in [2]. But still it's
giving the same error.
On Tue, Oct 13, 2015 at 4:41 PM, Rajjaz Mohammed <raj...@wso2.com> wrote:
> Hi,
> its seems to be like a error i got earlier so what i did is i import the
> certificate through the terminal like[1] and its solved my error.
>
> AFAIK test server not will be the reason for this error. and try the way
> [2].
>
> [1]Navigate to "/repository/resources/security/" using command prompt and
> execute keytool -importcert -file CERT_FILE_NAME -keystore
> client-truststore.jks -alias "CERT_NAME" in command line to import api
> certificate in to keystore. Give "*wso2carbon*" as password.
>
> [2]
> http://wso2-oxygen-tank.10903.n7.nabble.com/Dev-Connector-Integration-Test-Error-SSL-Handshake-Exception-td98612.html
>
> On Tue, Oct 13, 2015 at 3:55 PM, Rajeenthini Satkunam <
> rajeenth...@wso2.com> wrote:
>
>> Hi Hariprasanth,
>>
>> You can search for this subject "*[Dev] Connector Integration Test
>> Error!- SSL Handshake Exception*" .This could help you to give some idea
>> about the error.
>>
>> On Tue, Oct 13, 2015 at 3:42 PM, Hariprasath Thanarajah <
>> haripras...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> Is it the error came because of the testing server? I am testing with
>>> the test server because it is only available for FHIR. The FHIR is in the
>>> development phase.
>>>
>>> On Tue, Oct 13, 2015 at 11:13 AM, Hariprasath Thanarajah <
>>> haripras...@wso2.com> wrote:
>>>
>>>> Hi All ,
>>>>
>>>> I got the response at the wire. But after that only i am getting the
>>>> above error[1].
>>>>
>>>> On Tue, Oct 13, 2015 at 11:08 AM, Hariprasath Thanarajah <
>>>> haripras...@wso2.com> wrote:
>>>>
>>>>> Hi Elilmatha,
>>>>>
>>>>> I already included the certificates at client-truststore.jks as well
>>>>> as wso2carbon.jks.
>>>>>
>>>>> On Tue, Oct 13, 2015 at 11:06 AM, Elilmatha Sivanesan <
>>>>> elilma...@wso2.com> wrote:
>>>>>
>>>>>> Hi Hariprasath,
>>>>>>
>>>>>> As per you error log you need to include the certificate.
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> On Tue, Oct 13, 2015 at 10:56 AM, Hariprasath Thanarajah <
>>>>>> haripras...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> I am working on FHIR connector. I got the following[1] error while I
>>>>>>> am running the integration test case of FHIR. Any suggestion on this
>>>>>>> error?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> [1]
>>>>>>> [2015-10-13 10:49:58,488] ERROR
>>>>>>> {org.wso2.carbon.automation.core.PlatformTestManager} - On Test
>>>>>>> failure..
>>>>>>> [2015-10-13 10:49:58,488] ERROR
>>>>>>> {org.wso2.carbon.automation.core.PlatformTestManager} -
>>>>>>> javax.net.ssl.SSLHandshakeException:
>>>>>>> sun.security.validator.ValidatorException: PKIX path building failed:
>>>>>>> sun.security.provider.certpath.SunCertPathBuilderException: unable to
>>>>>>> find
>>>>>>> valid certification path to requested target
>>>>>>> [2015-10-13 10:49:58,489] INFO
>>>>>>> {org.wso2.carbon.automation.core.PlatformTestManager} -
>>>>>>> --Tests Failed
>>>>>>> org.wso2.carbon.connector.integration.test.fhir.fhirConnectorIntegrationTest.readResource
>>>>>>> [2015-10-13 10:49:58,503] INFO
>>>>>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>>>>>> [2015-10-13 10:49:58,503] WARN - ProxyServiceAdmin No proxy service
>>>>>>> exists
>>>>>>> by the name : fhir
>>>>>>> [2015-10-13 10:49:58,525] INFO
>>>>>>> {org.wso2.carbon.automation.api.clients.proxy.admin.ProxyServiceAdminClient}
>>>>>>> - Proxy Deleted
>>>>>>> FAILED: readResource
>>>>>>> f
Re: [Dev] WSO2 Committers += Sasikala Kottegoda
Congratz Sasikala ! On Mon, Oct 12, 2015 at 3:15 PM, Rajith Roshan <raji...@wso2.com> wrote: > Congratz !!! > > On Mon, Oct 12, 2015 at 1:47 PM, Isuru Wijesinghe <isur...@wso2.com> > wrote: > >> Congratulations :) >> >> On Mon, Oct 12, 2015 at 12:10 PM, Malintha Amarasinghe < >> malint...@wso2.com> wrote: >> >>> Congratulations Sasikala!! :) >>> >>> On Mon, Oct 12, 2015 at 11:28 AM, Kirishanthy Tharmalingam < >>> kirishan...@wso2.com> wrote: >>> >>>> Congrats Sasikala ! >>>> >>>> On Mon, Oct 12, 2015 at 11:13 AM, Sasikala Kottegoda <sasik...@wso2.com >>>> > wrote: >>>> >>>>> Thanks all... :) >>>>> >>>>> And special thanks to the MB team for the help that I've received so >>>>> far... :) >>>>> >>>>> On Mon, Oct 12, 2015 at 10:59 AM, Ramith Jayasinghe <ram...@wso2.com> >>>>> wrote: >>>>> >>>>>> Hi Sasikala, >>>>>> Congratulations! >>>>>> It is with great pleasure that we welcome you as a WSO2 committer. >>>>>> Keep up the good work! >>>>>> regards, >>>>>> >>>>>> -- >>>>>> Ramith Jayasinghe >>>>>> Technical Lead >>>>>> WSO2 Inc., http://wso2.com >>>>>> lean.enterprise.middleware >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Sasikala Kottegoda >>>>> *Software Engineer* >>>>> WSO2 Inc., http://wso2.com/ >>>>> lean. enterprise. middleware >>>>> Mobile: +94 774835928/712792401 >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Thanks & Regards, >>>> Kirishanthy >>>> Associate Software Engineer >>>> Mobile : +94 778333939 >>>> kirishan...@wso2.com >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Malintha Amarasinghe >>> Software Engineer >>> *WSO2, Inc. - lean | enterprise | middleware* >>> http://wso2.com/ >>> >>> Mobile : +94 712383306 >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Isuru Wijesinghe >> *Software Engineer* >> Mobile: 0710933706 >> isur...@wso2.com >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Rajith Roshan > Software Engineer, WSO2 Inc. > Mobile: +94-72-642-8350 <%2B94-71-554-8430> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Thank you and Regards**Hariprasath Thanarajah* Associate Software Engineer | WSO2 E: haripras...@wso2.com M: +94752806528 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error on FHIR connector integration Test case
Hi All ,
I got the response at the wire. But after that only i am getting the above
error[1].
On Tue, Oct 13, 2015 at 11:08 AM, Hariprasath Thanarajah <
haripras...@wso2.com> wrote:
> Hi Elilmatha,
>
> I already included the certificates at client-truststore.jks as well as
> wso2carbon.jks.
>
> On Tue, Oct 13, 2015 at 11:06 AM, Elilmatha Sivanesan <elilma...@wso2.com>
> wrote:
>
>> Hi Hariprasath,
>>
>> As per you error log you need to include the certificate.
>>
>> Thanks.
>>
>> On Tue, Oct 13, 2015 at 10:56 AM, Hariprasath Thanarajah <
>> haripras...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> I am working on FHIR connector. I got the following[1] error while I am
>>> running the integration test case of FHIR. Any suggestion on this error?
>>>
>>>
>>>
>>> [1]
>>> [2015-10-13 10:49:58,488] ERROR
>>> {org.wso2.carbon.automation.core.PlatformTestManager} - On Test failure..
>>> [2015-10-13 10:49:58,488] ERROR
>>> {org.wso2.carbon.automation.core.PlatformTestManager} -
>>> javax.net.ssl.SSLHandshakeException:
>>> sun.security.validator.ValidatorException: PKIX path building failed:
>>> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
>>> valid certification path to requested target
>>> [2015-10-13 10:49:58,489] INFO
>>> {org.wso2.carbon.automation.core.PlatformTestManager} -
>>> --Tests Failed
>>> org.wso2.carbon.connector.integration.test.fhir.fhirConnectorIntegrationTest.readResource
>>> [2015-10-13 10:49:58,503] INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>> [2015-10-13 10:49:58,503] WARN - ProxyServiceAdmin No proxy service exists
>>> by the name : fhir
>>> [2015-10-13 10:49:58,525] INFO
>>> {org.wso2.carbon.automation.api.clients.proxy.admin.ProxyServiceAdminClient}
>>> - Proxy Deleted
>>> FAILED: readResource
>>> fhir {readResource} integration test.
>>> javax.net.ssl.SSLHandshakeException:
>>> sun.security.validator.ValidatorException: PKIX path building failed:
>>> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
>>> valid certification path to requested target
>>> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
>>> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1904)
>>> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:279)
>>> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:273)
>>> at
>>> sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1446)
>>> at
>>> sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:209)
>>> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:901)
>>> at sun.security.ssl.Handshaker.process_record(Handshaker.java:837)
>>> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1023)
>>> at
>>> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1332)
>>> at
>>> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1359)
>>> at
>>> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1343)
>>> at
>>> sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:563)
>>> at
>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
>>> at
>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1301)
>>> at
>>> java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468)
>>> at
>>> sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338)
>>> at
>>> org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.readResponse(ConnectorIntegrationTestBase.java:898)
>>> at
>>> org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.sendJsonRestRequest(ConnectorIntegrationTestBase.java:371)
>>> at
>>> org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.sendJsonRestRequest(ConnectorIntegrationTestBase.java:253)
>>> at
>>> org.wso2.carbon.connector.integration.test.fhir.fhirConnectorIntegrationTest.readResource(fhirConnectorIntegrationTest.java:69)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.r
[Dev] Error on FHIR connector integration Test case
) at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:385) at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:292) at sun.security.validator.Validator.validate(Validator.java:260) at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:326) at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:231) at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:126) at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1428) ... 50 more Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:196) at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:268) at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:380) ... 56 more -- *Thank you and Regards**Hariprasath Thanarajah* Associate Software Engineer | WSO2 E: haripras...@wso2.com M: +94752806528 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error on FHIR connector integration Test case
Hi Elilmatha,
I already included the certificates at client-truststore.jks as well as
wso2carbon.jks.
On Tue, Oct 13, 2015 at 11:06 AM, Elilmatha Sivanesan <elilma...@wso2.com>
wrote:
> Hi Hariprasath,
>
> As per you error log you need to include the certificate.
>
> Thanks.
>
> On Tue, Oct 13, 2015 at 10:56 AM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Hi All,
>>
>> I am working on FHIR connector. I got the following[1] error while I am
>> running the integration test case of FHIR. Any suggestion on this error?
>>
>>
>>
>> [1]
>> [2015-10-13 10:49:58,488] ERROR
>> {org.wso2.carbon.automation.core.PlatformTestManager} - On Test failure..
>> [2015-10-13 10:49:58,488] ERROR
>> {org.wso2.carbon.automation.core.PlatformTestManager} -
>> javax.net.ssl.SSLHandshakeException:
>> sun.security.validator.ValidatorException: PKIX path building failed:
>> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
>> valid certification path to requested target
>> [2015-10-13 10:49:58,489] INFO
>> {org.wso2.carbon.automation.core.PlatformTestManager} -
>> --Tests Failed
>> org.wso2.carbon.connector.integration.test.fhir.fhirConnectorIntegrationTest.readResource
>> [2015-10-13 10:49:58,503] INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>> [2015-10-13 10:49:58,503] WARN - ProxyServiceAdmin No proxy service exists
>> by the name : fhir
>> [2015-10-13 10:49:58,525] INFO
>> {org.wso2.carbon.automation.api.clients.proxy.admin.ProxyServiceAdminClient}
>> - Proxy Deleted
>> FAILED: readResource
>> fhir {readResource} integration test.
>> javax.net.ssl.SSLHandshakeException:
>> sun.security.validator.ValidatorException: PKIX path building failed:
>> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
>> valid certification path to requested target
>> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
>> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1904)
>> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:279)
>> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:273)
>> at
>> sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1446)
>> at
>> sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:209)
>> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:901)
>> at sun.security.ssl.Handshaker.process_record(Handshaker.java:837)
>> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1023)
>> at
>> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1332)
>> at
>> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1359)
>> at
>> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1343)
>> at
>> sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:563)
>> at
>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
>> at
>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1301)
>> at
>> java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468)
>> at
>> sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338)
>> at
>> org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.readResponse(ConnectorIntegrationTestBase.java:898)
>> at
>> org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.sendJsonRestRequest(ConnectorIntegrationTestBase.java:371)
>> at
>> org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.sendJsonRestRequest(ConnectorIntegrationTestBase.java:253)
>> at
>> org.wso2.carbon.connector.integration.test.fhir.fhirConnectorIntegrationTest.readResource(fhirConnectorIntegrationTest.java:69)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at
>> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
>> at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
>> at org.testng.internal.Invoker.invokeTestMethod(Invoke
Re: [Dev] Error in salesforce rest api connector test case
Thank you all for your help. Now it's working.
On Fri, Aug 21, 2015 at 12:57 PM, Kesavan Yogarajah kesav...@wso2.com
wrote:
Hi Hariprasath* ,*
As Elilmatha said syntax errors in your configurations causing this
error.Closing tag is missing in queryAllMore and queryMore proxy
configurations .
Thanks.
Kesavan Yogarajah
Associate Software Engineer
Mobile :+94 (0) 779 758021
kesav...@wso2.com
WSO2, Inc.
lean . enterprise . middleware
On Fri, Aug 21, 2015 at 9:27 AM, Elilmatha Sivanesan elilma...@wso2.com
wrote:
Hi Hariprasath* ,*
It seems some syntax error , missing the closing tag in BeforeClass
setEnvironment.
Thanks.
On Fri, Aug 21, 2015 at 8:11 AM, Rajjaz Mohammed raj...@wso2.com wrote:
Hi harprasath,
Can you upload your code?
On 21 Aug 2015 08:01, Hariprasath Thanarajah haripras...@wso2.com
wrote:
Hi all,
I got the following error while doing the salesforce rest api connector
test case. Anyone help me.
[2015-08-21 07:53:39,248] WARN
{org.wso2.carbon.automation.core.PlatformTestManager} - On Test Skipped
[2015-08-21 07:53:39,248] INFO
{org.wso2.carbon.automation.core.PlatformTestManager} - --Test
Skipped null
[2015-08-21 07:53:39,254] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2015-08-21 07:53:39,254] WARN - ProxyServiceAdmin No proxy service exists
by the name : salesforcerest
[2015-08-21 07:53:39,266] INFO
{org.wso2.carbon.automation.api.clients.proxy.admin.ProxyServiceAdminClient}
- Proxy Deleted
FAILED CONFIGURATION: @BeforeClass setEnvironment
org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxParsingException:
Unexpected '' character in element (missing closing ''?)
at [row,col {unknown-source}]: [13,13]
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
at
org.apache.axiom.om.impl.llom.OMElementImpl.buildNext(OMElementImpl.java:653)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.getNextOMSibling(OMNodeImpl.java:122)
at
org.apache.axiom.om.impl.traverse.OMChildrenIterator.getNextNode(OMChildrenIterator.java:36)
at
org.apache.axiom.om.impl.traverse.OMAbstractIterator.hasNext(OMAbstractIterator.java:58)
at
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeChildren(OMSerializerUtil.java:554)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:875)
at
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeChildren(OMSerializerUtil.java:555)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:875)
at
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeChildren(OMSerializerUtil.java:555)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:875)
at
org.apache.axiom.om.impl.llom.OMSerializableImpl.serialize(OMSerializableImpl.java:125)
at
org.apache.axiom.om.impl.llom.OMSerializableImpl.serialize(OMSerializableImpl.java:113)
at
org.apache.axiom.om.impl.llom.OMElementImpl.toString(OMElementImpl.java:988)
at
org.wso2.carbon.automation.api.clients.proxy.admin.ProxyServiceAdminClient.addProxyService(ProxyServiceAdminClient.java:129)
at
org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.init(ConnectorIntegrationTestBase.java:198)
at
org.wso2.carbon.connector.integration.test.salesforcerest.SalesforceRestConnectorIntegrationTest.setEnvironment(SalesforceRestConnectorIntegrationTest.java:50)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at
org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525)
at
org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202)
at
org.testng.internal.Invoker.invokeConfigurations(Invoker.java:130)
at
org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:173)
at
org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:105)
at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
at org.testng.TestRunner.privateRun(TestRunner.java:757)
at org.testng.TestRunner.run(TestRunner.java:608)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158
[Dev] Error in salesforce rest api connector test case
--- [INFO] Building jar: /home/hariprasath/Desktop/salesforce/salesforcerest/salesforcerest/salesforcerest-connector/salesforcerest-connector-1.0.0/org.wso2.carbon.connector/target/org.wso2.carbon.connector.salesforcerest-4.2.0.jar [INFO] [INFO] --- maven-jar-plugin:2.4:test-jar (default) @ org.wso2.carbon.connector.salesforcerest --- [INFO] Building jar: /home/hariprasath/Desktop/salesforce/salesforcerest/salesforcerest/salesforcerest-connector/salesforcerest-connector-1.0.0/org.wso2.carbon.connector/target/org.wso2.carbon.connector.salesforcerest-4.2.0-tests.jar [INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @ org.wso2.carbon.connector.salesforcerest --- [INFO] Installing /home/hariprasath/Desktop/salesforce/salesforcerest/salesforcerest/salesforcerest-connector/salesforcerest-connector-1.0.0/org.wso2.carbon.connector/target/org.wso2.carbon.connector.salesforcerest-4.2.0.jar to /home/hariprasath/.m2/repository/org/wso2/carbon/connector/org.wso2.carbon.connector.salesforcerest/4.2.0/org.wso2.carbon.connector.salesforcerest-4.2.0.jar [INFO] Installing /home/hariprasath/Desktop/salesforce/salesforcerest/salesforcerest/salesforcerest-connector/salesforcerest-connector-1.0.0/org.wso2.carbon.connector/pom.xml to /home/hariprasath/.m2/repository/org/wso2/carbon/connector/org.wso2.carbon.connector.salesforcerest/4.2.0/org.wso2.carbon.connector.salesforcerest-4.2.0.pom [INFO] Installing /home/hariprasath/Desktop/salesforce/salesforcerest/salesforcerest/salesforcerest-connector/salesforcerest-connector-1.0.0/org.wso2.carbon.connector/target/salesforcerest-connector-1.0.0.zip to /home/hariprasath/.m2/repository/org/wso2/carbon/connector/org.wso2.carbon.connector.salesforcerest/4.2.0/org.wso2.carbon.connector.salesforcerest-4.2.0.zip [INFO] Installing /home/hariprasath/Desktop/salesforce/salesforcerest/salesforcerest/salesforcerest-connector/salesforcerest-connector-1.0.0/org.wso2.carbon.connector/target/org.wso2.carbon.connector.salesforcerest-4.2.0-tests.jar to /home/hariprasath/.m2/repository/org/wso2/carbon/connector/org.wso2.carbon.connector.salesforcerest/4.2.0/org.wso2.carbon.connector.salesforcerest-4.2.0-tests.jar [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 01:32 min [INFO] Finished at: 2015-08-21T07:54:03+05:30 [INFO] Final Memory: 73M/679M [INFO] -- *Thank you and Regards**Hariprasath Thanarajah* Associate Software Engineer | WSO2 E: haripras...@wso2.com M: +94752806528 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
