I am using CallerServices & CertificateAPIProfile from the paypal_base.jar, and I am using a bunch of SOAP methods from the paypal_stubs.jar. Getting worried about this deadline, not sure if these are affected or not.
You must fix your app before June 17th as paypal will stop to use TLS 1.0 that is the only protocol supported by that jar version.
https://www.paypal-knowledge.com/infocenter/index?page=content&widgetview=true&id=FAQ1914&viewlocale=en_US
Here you can find a replacement for that jar supplied by PayPal:
https://github.com/paypal/PayPal-Legacy-Java-SDK
Related
I have a task where I need to use ARM template to "setup SQL server with elastic pool and 2 databases (imported from bacpac files) use Microsoft Adventureworks samples."
Most of the template I made using "101-sql-elastic-pool-create" template that is available here: https://github.com/Azure/azure-quickstart-templates/tree/master/101-sql-elastic-pool-create
I used it for the elastic pool setup and used a sample from this documentation (https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/template-tutorial-deploy-sql-extensions-bacpac) to have the .bacpac imported to the database
But when I try to deploy this template (the template is available to see here: https://github.com/KarlisAG/SQL_ARM/blob/main/azuredeploy.json ) it throws me an error
("Resource Microsoft.Sql/servers/elasticPools 'task4sql/elasticp' failed with message '{ "code": "BadRequest", "message": "An error occurred while processing this request.", "target": null, "details": [], "innererror": [] }' ")
So, the biggest problem is (besides me being an absolute newbie) not knowing what I need to fix, because there is no additional information granted, besides the "BadRequest". For deployment I used two different methods: 1) the automatically generated one from VS when created Azure resource groups, 2) One shown in this documentation, with few of my own changes, so it could work for me ( https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/template-tutorial-deploy-sql-extensions-bacpac#deploy-the-template ), from where I also got the code part for importing .bacpac to my newly created database. [Both of the are available at the same repository, named "Deploy-AzureResourceGroups.ps1" and "DeployScript.ps1" respectively].
Both of the methods return the same error.
I even manually created these things in Azure portal to see what their template looks like and maybe copy some things that are not present in my template, but from what I saw I have exactly what they automatically generate.
And when I checked the deployment status in Azure portal I can also see that during the elastic pool creation it fails: screenshot from that section available here
So does anyone know how should I have created this type of template, or did I recreate it poorly, or am I missing some small mistake that keeps blocking me?
So after multiple tries it seems that I finally figured out what I was doing wrong. I am still not sure which of the changes made a difference, besides the last one, so I will write what I changed, so other people who could be facing similar issue know what they could do fix the issue.
At first, after #stringfellow noted, I thought that Free Trial is restricting me from doing anything, but after I lowered my DTU multiple times, to the point where it was at 5 (starting from 100), the same issue persisted, so probably it was not the issue (later on I had to change it at minimum to 50). I also changed the Elastic Pool edition from Standard to Basic. But doing these changes still didn't fix the issue.
At last, after answering #NachoMartínez-Aedo comment about the api version, it got me thinking. Because in the code that I posted I used "2020-08-01-preview" api version, but in reality I used "2014-04-01-preview", because when I changed the api version of all my parts to the 2020 one, then powershell told me that (No registered resource provider found for location 'northeurope' and API version '2020-08-01-preview' for type 'servers/databases/extensions'. The supported api-versions are '2014-01-01, 2014-04-01, 2014-04-01-preview'.). And after reading through that again and remembering that when I was looking at some documentation and Azure portals automatically generated templates I knew that I always say them using the 2020 api, not the 2014, which left me confused as to why I couldn't also use the newest version. And reading that error again I saw, that it specifically told that 2020 api version was not supported for the type "servers/databases/extensions", not that all of the parts must be in 2014 version (which is what I thought when I saw that error), so I tried and changed all the 2014 back to 2020 and left the extension api back at 2014 (previously I thought that all api versions should be the same, not sure why, maybe because most of the examples and documentation had everything have the same api version) and the everything worked, even the import part, about which I was worried.
So in the future I am not too sure if there is a better/newer way to import .bacpac file to newly created database with ARM, or just have to leave it as is and in the future use this same approach. Does anyone know?
I got the import extension from here: https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/template-tutorial-deploy-sql-extensions-bacpac
, where they use examples with 2014 api for the extension, so because of that I tried to use it for all my parts, but only during this answer writing did I realize and look through it again, that they used the 2014 api only for the extension part and not other parts, like server, database, etc.
TL;DR
So basically I needed to use the '2020-08-01-preview' api for everything besides from the extension part, where the newest api version is only '2014-04-01-preview'
I was able to deploy most of your template and use similar parameters in my own subscription. I saw in your screen capture that you are using a Free Trial subscription. I am curious if that has anything to do with the 'BadRequest' due to any sort of DTU limitation.
Here is my deployment, which failed as expected when it tried to import the databases.
I'm trying to use the QBO Rest API to insert invoices into our system and want to use the BillEmailCc attribute of invoices. I've read on their site that these are only available for minor version 7. I've try setting the minor version in my queries but still I get errors saying this attribute is not valid. How can you access the minor version 7?
url: https:https://sandbox-quickbooks.api.intuit.com/v3/company/193514338926917/query?query=SELECT%20BillEmail%20FROM%20Invoice%20WHERE%20CustomerRef%20%3D%20%2760%27&minorversion=7
After doing some digging in the console, I deduced that the fields to set are as follows
"AllowOnlinePayment":true,
"AllowOnlineCreditCardPayment":true,
"AllowOnlineACHPayment":true,
Quickbooks support has said these attributes aren't supported, however.
I have an existing integration with Paypal using the java sdk. We're planning a production release, but we can't let it got to prod with the current log level of the sdk. It seems to be set to DEBUG and logs every request going/coming from Paypal. I guess there must be a parameter to add to the paypal_sdk_config.properties file, but I can't seem to guess it and documentation is inexistant on the matter.
Anyone has ever done this before?
We just discovered, going through the code source of the com.paypal.core.LoggingManager class, that the logger creation is not intuitive.
The logger name is always something like class for example: class com.paypal.core.APIService
It means that you cannot set the log level through this call
getLogger("com.paypal.core.APIService").setLevel(Level.WARNING);
To set the log level, you need to do that:
getLogger("class com.paypal.core.APIService").setLevel(Level.WARNING);
I just open an issue on the Paypal github repo for that strange behavior: https://github.com/paypal/sdk-core-java/issues/13
I use SBJsonStreamParser(class of SBJson) to parse JSON.now I want to know how to cancel parsing of the class when the class is parsing at runtime.I couldn't find such API.someone please help me !!
I'm afraid there is no such API at the moment. If you need it, I suggest raising an issue in the issue tracker. You are also free to implement it yourself, and send a pull request. I will accept the patch if it's any good.
Disclaimer: I am SBJson's author.
Update: just to let you know, SBJson 4 (released December 2013) supports cancelling.
I am not a professional programmer. I am "a kitchen table programming enthusiast." My question is at the very end of this narrative.
In March of 2010, I figured out how to introduce my interactive database driven web app to the world by turning my web app into a Facebook Canvas Application.
Basically I built my web app prior to March 2010 using MYSQL, PHP, HTML, JavaScript, etc. using "dummies" books. Once I was convinced that my web app was functional as a standalone website, I pored through Facebook online documents to figure out how to turn my app into a FB Canvas App.
That was in March of 2010. Back then the process for turning a web app into a FB Canvas App basically involved getting files like the following, and saving them to the directories on my web host server:
-- At public_html:
-- config.php
-- facebook_desktop.php
-- facebook_mobile.php
-- facebookapi_php5_restlib.php
-- fbtest.htm
-- JSON.php
-- jsonwrapper_inner.php
-- xd_receiver.htm
-- At public_html/php:
-- facebook.php
Now here is my question:
My app has been working fine since March 2010, but now (since this morning) my app doesn't work at all (doesn't even open). I suspect this is due to requirements that changed related to migration to OAuth 2.0 and HTTPS -- requirements which I need to learn how to respond to.
What should be my first step toward at least enabling myself to continue using my own app on FB? Once we have figured that out, I will be seeking guidance on how to once again enable other FB members to use my app.
I hope some will find this thread helpful.
Thank You,
FL
There's an overview here: https://developers.facebook.com/docs/oauth2-https-migration/ which links to the docs and the blog posts which gave examples of how to migrate
Thank you, so much!
I have begun reviewing the material you have referred. I will continue to dig in, but I'd like to let you know that for now, I see these phrases which raise questions in my mind:
-- "If you are only using the PHP SDK (Software Development Kit) for authentication..."
-- "If you are using the JavaScript SDK for login..."
-- "Update to PHP SDK..."
-- "Update to JavaScript SDK..."
-- "Implementing the OAuth 2.0 authentication system..."
-- "Using the latest SDKs..."
Based on details in my original post is one able to determine whether I have currently implemented a PHP SDK or the JavaScript SDK? I don't know that I ever even used an SDK for establishing my means for Authentication and Authorization. I only knew my method as applying for a FB App ID, App Secret and copying a set of files to my server. Was my implementation method from March 2010 so old that it is neither PHP SDK nor JavaScript SDK?
Doesn't "updating an SDK" require that I had first implemented some sort of SDK?
If it turns out that I haven't used an SDK as part of my archaic means for authentication and authorization then what set of instructions is really applicable for me to migrate to OAuth2.0?
I am concerned that without seeing a step by step set of instructions, I will end up with extraneous and conflicting files on my server.
Does anyone know of any migration instructions like, "replace these files (file A, file B, file C and file D) from your web host server with these files (file E, file F, file G and file H)"
Thank you,
FL.