I'm migrating my Symfony application from 2.8 to 3.4 (then to 4.1) and I get this deprecation message in profiler.
Does anyone know how to I fix it?
Autowiring services based on the types they implement is deprecated
since Symfony 3.3 and won't be supported in version 4.0. You should
alias the "Core\Infrastructure\Utils\TokenGenerator" service to
"Core\Application\Utils\TokenGenerator" instead.
In my services.yml I have
Core\Infrastructure\Utils\TokenGenerator:
arguments: ["#logger"]
app.token_generator: '#Core\Infrastructure\Utils\TokenGenerator'
In my code the class Core\Infrastructure\Utils\TokenGenerator implements Core\Application\Utils\TokenGenerator interface
Related
I'm developing a new application using Symfony 3.1. I'm trying to find the oAuth2.0 bundle for the API build. I didn't find suitable bundle for the latest symfony version. I need help on getting the new bundle or suggest me any other alternative if anything available.
I tried to deploy an application with JSF 1.2 to TomEE 1.7.1 Web Profile and of course got exceptions because of the JSF 2.0-Libs in TomEE ... .
According to the article Is it possible to deploy JSF MyFaces 1.1.5 applications to TomEE I removed the following libs from the TomEE lib dir:
- myfaces-api-2.1.15.jar
- myfaces-impl-2.1.15.jar
When starting the application I get:
SEVERE: Exception sending context initialized event to listener instance of class org.apache.myfaces.webapp.StartupServletContextListener
java.lang.NoClassDefFoundError: javax/faces/application/ApplicationWrapper
Is there any way to disable JSF 2.x support per application?
Current environment: WebSphere 6.1 with IBM java jdk 1.5 with Struts 1.3 and some version of Tiles.
I would like to replace Structs 1.3 with Spring MVC. What is the maximum Spring Framework version can I use? Fortunately, JPA 2.0 compatibility is not required because the current system uses REST calls for all database access instead of using Hibernate. We will eventually move WebSphere to 8.5, but not anytime time soon.
Again, upto which version of Spring framework can I use with Websphere 6.1 (with IBM jdk 1.5)? Thanks in advance.
You can use spring with the latest 3.2 version.
We're using Spring 3.0 today with WebSphere 6.1, and I'm pretty sure there's no reason we can't use 3.1.
I wanted to upgrade from Servlet 2.4 to Servlet 3.0. Currently we are using ESAPI in our application and would like to upgrade.
Latest ESAPI release depends on servlet-api-2.4.jar. Does ESAPI support Servlet 3.0?
I upgraded my application to support Servlet 3.0 and ESAPI seems to work. So it is backwards compatible.
is jbos5.1.0 compatible with jdk6 and spring2.5.X.
I am also integraion acegi security and not spring security 3.0 as i am using spring 2.5.0?
IS jboss 5.1.0 comaptible with spribng3.0 andjdk6 ?
A few months ago, I've tried JBoss 5 with Spring 2.5.6 and couldn't deploy my application, because of this bug. The comments on the issue, mention the problem only happens with EJB, but my application didn't make use of EJB and it was packed as a war.
According to the JIRA, this was fixed in spring 3.0RC1, but I haven't tried it (for now, I gave up updating to a new version of JBoss).