I have make library for solr data but it's not working with phalcon framwork
Getting error : SolrClient' class not found
if i can use core php then it's working proper.
Related
Is there any built-in way with Swashbuckle for ASP.NET Core to generate the swagger.json file at build or compile time (i.e. not with dotnet run)?
I'm starting down a path of microservices and I thought it would be nice to generate the swagger.json file at build time to allow other services to generate client APIs.
You can use the Swashbuckle.AspNetCore.Cli to do this.
The CLI is versioned alongside the main package Swashbuckle.AspNetCore, so despite at the time of writing the readme saying use version 2.1.0-beta1, use the version that matches your use of Swashbuckle.AspNetCore.
I was wondering, if it is possible to do live coding using Asp.Net core similar how it is possible to do this in node.js using nodemon. I am trying to learn asp.net core and I find the code-compile-debug cycle very slow and inconvenient.
Is possible to do live coding using ASP.NET Core similar how it is possible to do this in Node.js using nodemon?
Yes, it is. You can use the dotnet watch command. This command will allow you to do "live coding". In also works with tests, i.e.; if you find a bug and you can fix the bug and watch will detect the changes, recompile your code and re-execute the tests.
https://learn.microsoft.com/en-us/aspnet/core/tutorials/dotnet-watch
The swagger-core documentation describes how to incorporate swagger into the application. Annotations are scanned at runtime.
Instead, I would like to statically generate the swagger API specification at build time. Is this possible using swagger-core?
EDIT: We are building using ant.
swagger-core alone is a runtime library and cannot be used to generate Swagger definitions at build time.
You can use the swagger-maven-plugin which depends on swagger-core to produce such definitions. However, I'd recommend browsing around the branches and using the version that produces Swagger 2.0 definitions to keep up with the latest improvements.
I downloaded a Flickr module from kohana-modules.com and when I tested on my local server worked perfectly. But when I uploaded to a remote server, to the same directory as the default Koahan modules, I got a "ErrorException [ Fatal Error ]: Class 'Flickr' not found". The default Kohana modules are working as expected. I'm using Kohana 3.2.2.
Any pointers to why this is happening?
Thanks.
I experience that exact same behaviour with both Kohana 3.2 and 3.3 if a dynamic reference to a class can not be resolved by the autoloader on a Linux server. Mainly because filesystems used by Mac OSX and Windows are case insensitive but a Unix/Linux based server is not. What operating systems are your local and remote servers running on?
Since you are using Kohana 3.2 and the main branch of the mentioned flickr module is erroneously named 3.1/master but contains 3.3 PSR-0 updates try using the 3.0 branch instead: https://github.com/jeanmask/flickr/tree/3.0/master
Heads up: even better would be to fork the github repository, build a valid Kohana 3.2 branch that holds all changes but does not contain PSR-0 modifications and state a pull request.
I am migrating application from JBoss AS 4.X to JBoss AS 7.1. I am facing the following problem
I have a userdefined xml which has some configuration related stuff like paths, initial load setting etc which I used to place in Application Server/bin in JBoss AS 4.X. It was working fine.
Now i placed the same file in jboss-as-7.1.1.Final\bin but it is not working and loading on start up of server.
Where do I need to keep such XML's in 7.1 Server?
And do I need to explicitly mention in jboss-deployment-structure.xml?
You could try writing a custom module and place the xml file there. And then make your application depend on this module.
Edit:
The following Wiki page outlines it nicely How to put an external file in the classpath