Using ABP Framework v3.2.1, we are wanting to use the ABP IHttpClientProxy dynamic proxy classes in application environments other than .NET Core hosts (E.g, AWS Lambda function, Xamarin client app) - where the only ABP modules required are those that IHttpClientProxy depends on.
Firstly, is this supported?
Secondly, what would be the process to load a single "entry" module that's not a hosted service?
Going through the source, I can only find the IServiceCollection.AddApplication extension methods - there doesn't appear to be the same for "AddModule"
Related
Does DotNetNuke have a built in web services API I can call or do I have to create my own end point? All the documentation I can find about the services framework talks about creating your own module with a service to extend theirs. What I would like to do is authenticate against an existing / built in web service that will allow me to create users from an external application. A similar example would be me calling the built in SharePoint web services to retrieve list information with an external application. I don't have to write anything in SharePoint to call the built in web services. They are just there.
If this built in service(s) does exist do you have a link or some sample code about how to call it without writing my own web service module?
Thanks,
Bill
DNN does not (as of version 9.1) have a (supported) external API. There are web services designed to the internal modules to use, but you have to get a little hacky in order to make them usable outside of the site. There has been talk of creating a more standard API like this, but until the happens the scenario requires that you create specific APIs for your exact purposes.
We currently have our API set up in azure and use deployment slots which each have their own app settings. For example, on our live slot we set our connection string to the live database. On our dev slot we set the connection string to the test database.
So, I have been tasked with doing something similar with our SPA. I created it using .net core and angular. Currently it has a constant set up:
.constant('apiUrl', 'https://ourlive.api.com')
I have a few set up and I just comment out the ones I am not using. What I have been tasked with, is putting these into the application settings and using deployment slots for different URLs. For example, the live slot will use the Live URL and the Dev slot will use the Dev URL.
I read that you can do this using npm but this isn't an option for us because we are using .net and the npm doesn't seem to work like that. Is there another way we can read the application settings?
Per my understanding, your scenario is a purely HTML + angularjs SPA, although they are running in a .NET core runtime. And your requirement is that you want to get the slot application settings in your SPA application. If I have any misunderstanding about your structure, please feel free to let me know.
You can try to leverage the .net core runtime to get the application settings in slot, and expose as an RESTful API for your SPA application.
And in your SPA application, you can create a server, to call your .net core's API, and you can inject this server and call this api when your SPA bootstrap in and keep the settings in $rootscope for your entire SPA application.
For slot application settings, you can refer to https://learn.microsoft.com/en-us/azure/app-service-web/web-sites-staged-publishing#configuration-for-deployment-slots for more info.
I have ported a Java EE web application from JBoss 4.0.5/Java 5 to Tomcat 6.0.33/Java 6.
The web application exposes some web services. They were implemented as JAX-RPC web services in JBoss, I have adapted them as JAX-WS web services using CXF 2.6 as the implementation run-time. Now I have been requested to make available in the new environment (Tomcat 6.0.33/Java 6) also the JAX-RPC web services for compatibility with existing clients. The two versions of the same web services would of course be available through two different end point URLs.
The JAX-RPC web services in JBoss 4.0.5/Java 5 are implemented using Spring (the implementation class extends org.springframework.remoting.jaxrpc.ServletEndpointSupport, found in spring-remoting-2.0.8.jar) but I cannot guess which is the underlaying implementation framework for JAX-RPC made available by JBoss. I just can see that the configuration files are webservices.xml and jaxrpc-mapping.xml.
I tried to "replicate" that Spring configuration in Tomcat but when I try to retrieve the WSDL I get an error javax.servlet.ServletException: Class pack.age.MyEndPoint is not a Servlet. Indeed that class (the JAX-RPC end point implementation class) is not a servlet but under JBoss 4.0.5/Java 5 it is declared in web.xml as a servlet and it works.
Could you please help? I imagine I just have to supply the proper JAX-RPC implementation framework to Tomcat (I would like to avoid AXIS because it uses different configuration files). Thanks in advance.
We are developing a java based web application. This application needs a commenting functionality. The commercially available commenting services (http://aboutecho.com/ or http://www.livefyre.com/ etc) are not inside my budget. Can I use Drupal's commenting functionality with my Java application?
Am afraid there are no out of the box solutions in drupal that am aware of.
But its is totally possible to use drupal to power your java application's comments. Am afraid you would have to do some custom coding to make it happen.
Install drupal 7 and a contrib module called services. By installing services you can extend drupal's resource as services resource. I recommend enabling a REST server (a sub module for services) and using it to communicate with drupal.
I have an EJB accessed remotely from a Swing client as well as locally by servlet/JSP. I want to switch the packaging for my EJB from a EJB/WAR/EAR to a EJB/WAR since it is simpler to work with.
What do I mean by simpler? In Eclipse, for example, I can have a single project with my EJB/web classes rather than having a EJB + WAR + EAR project (My client is a separate project in Eclipse).
Is it possible to package a EJB in a WAR and have it be accessible remotely?
The intent of EJB-in-WAR was primarily to simplify packaging for local EJBs used by the WAR. However, I cannot find a restriction for remote EJBs packaged in a WAR even though there are restrictions on other technologies (specifically, entity beans and JAX-RPC endpoints are not allowed), which leads me to believe remote views are allowed in WARs from a specification perspective. I don't have broad knowledge of vendor implementations, but I have tested that it works on WebSphere Application Server.
According to the web profile and EJB 3.1 specs, Java EE web profile products are only required to provide EJB Lite, which doesn't support remote clients to EJBs.
But they can provide remote ejb client connection as a product optional component.
So if you want to package remote EJBs in a WAR you'll have to look for a Java EE web server that provides this service and be aware that the same behaviour isn't required in other Java EE 6 web servers.
Useful links:
http://download.oracle.com/otndocs/jcp/javaee_web_profile-6.0-fr-eval-oth-JSpec/
http://download.oracle.com/otndocs/jcp/ejb-3.1-fr-eval-oth-JSpec/