I'm using IBM WebSphere 7.0 with MyFaces 2.0.7 installed as shared library.
Because there are issues with PrimeFaces (for example, p:messages autoUpdate not working) I'm considering the upgrade to newer version (which is not trivial, because this must be the team decision in corporation).
So, my question is, which is the newest version of MyFaces that will work with IBM WebSphere 7.0? The newest version is for now 2.1.10, but according to the answer to the question Can JSF 2.0 be used with Websphere application server version 7.x MyFaces versions starting from 2.1 will not work with WebSphere 7.0.
Have someone managed to run version 2.1.x? If so, which version, and was something additional to do? As I said, I've successfully configured shared library, similar to solution from article like that: http://wasbehindtheglass.blogspot.co.uk/2011/11/myfaces-20-and-websphere-application.html
The MyFaces Core 2.1.10 works well with IBM WebSphere 7.0.
Release notes can be found at MyFaces Core 2.1.10.
Related
I created a hosted WASM Blazor app using the Blazor client template in Visual Studio. I am trying to upgrade the Microsoft.AspNetCore.Components.WebAssembly package in the Client project from 3.2.1 to 5.0. I get this error:
Package Microsoft.AspNetCore.Components.WebAssembly 5.0.0 is not compatible with netstandard2.1 (.NETStandard,Version=v2.1). Package Microsoft.AspNetCore.Components.WebAssembly 5.0.0 supports: net5.0 (.NETCoreApp,Version=v5.0) BlazorApp1.Client
The client project is targeting .NET Standard 2.1. I am not clear about the difference between targeting .NET standard and targeting .Net Core. I thought .NET Core 5.0 implements all of .NET Standard 2.1. Only .NET Standard target options are available.
How does one upgrade that package?
Also, there's no version 5.0 of Microsoft.AspNetCore.Components.WebAssembly.Build. Did the package get obsoleted?
Although you can reference netstandard2.1 packages in a .NET5 application (targeting net5.0), to upgrade your Blazor app to 5.0.0 (.NET5) you also have to change target framework to net5.0 since it depends on it, as you have noticed.
But other than this, there are more changes to be made to get it fully upgraded. The MS Docs on how to Migrate from ASP.NET Core 3.1 to 5.0 (as Brian already pointed out) should help get the job done.
According to https://devblogs.microsoft.com/dotnet/announcing-net-core-3-0/, the newest version of .NET core should be backward compatible with the previous versions.
However, building a docker image with 2.2sdk won't run on a container with runtime 3.0... Am I missing something or is it the normal behavior?
There is no mention of that in the linked article?
What you are experiencing is normal behavior. Major versions are not backwards compatible (for runtimes).
In your case running a .net core 2.2 app will not work on an image with a .net core 3.0 runtime.
You can read more about version selection where the following is mentioned:
The host chooses the latest patch version installed on the machine. For example, if you specified netcoreapp2.0 in your project file, and 2.0.4 is the latest .NET runtime installed, the 2.0.4 runtime is used.
If no acceptable 2.0.* version is found, a new 2.* version is used. For example, if you specified netcoreapp2.0 and only 2.1.0 is installed, the application runs using the 2.1.0 runtime. This behavior is referred to as "minor version roll-forward." Lower versions also won't be considered. When no acceptable runtime is installed, the application won't run.
A few usage examples demonstrate the behavior, if you target 2.0:
2.0 is specified. 2.0.5 is the highest patch version installed. 2.0.5 is used.
2.0 is specified. No 2.0.* versions are installed. 1.1.1 is the highest runtime installed. An error message is displayed.
2.0 is specified. No 2.0.* versions are installed. 2.2.2 is the highest 2.x runtime version installed. 2.2.2 is used.
2.0 is specified. No 2.x versions are installed. 3.0.0 is installed. An error message is displayed.
They also mention roughly adhering to semantic versioning here:
MAJOR is incremented when:
Significant changes occur to the product, or a new product direction.
Breaking changes were taken. There's a high bar to accepting breaking changes.
An old version is no longer supported.
A newer MAJOR version of an existing dependency is adopted.
I'm trying to work out which version of the ASP.NET related packages I should be using.
We are trying to stick to LTS versions of ASP.NET Core, meaning we are still on version 2.1 and not 2.2 for the compiler and runtime. However I'm having a hard to trying to find out what version of the nuget packages we should be using.
for example, Microsoft.AspNetCore.Mvc says that its latest version is 2.2.0 and visual studio wants me to upgrade to this. However, I am wondering if we should stay on 2.1.3 since we are still on 2.1 for the compiler.
Are these version numbers related? Should we be staying back on 2.1.x to match pace with the compiler or are we doing things wrong?
in the new versions of eclipse. glassfish server tools found in the eclipse market. only support glassfish 3.1 and above.
there is no support for glassfish 2.1 in glassfish tools downloaded from the market for any version of eclipse. I have tried several without success.
I have to maintain glassfish 2.1 jee5 code.
found there is oracle archive for bundles of all Oracle tools for eclipse.
the last version that supports glassfish 2.1 - is 12.1.1.2.1 - March 2013.
https://www.oracle.com/technetwork/developer-tools/eclipse/downloads/oepe-archive-1716547.html
I downloaded oepe-12.1.1.2.1-kepler-repository.zip
then in to the new version of eclipse 2018-09 - 4.9 I installed from the repository
only glass fish tools - and it worked
i developed a JSF(2.1) Application (JavaEE5) in GlassFish(ver.3) Application server with primefaces (ver 2.x) and Eclipse Link( ver 2 JPA 2.0). now i need to install the application in WebLogic Server(10.x or11 ). when i try to install application on Weblogics web interface it shows a big error message
How i can mive my application from one application server to another?
IDE Netbeans 7.0
JSF 2.1 primefaces libraries included in lib of the project
Error message starts like this
Message icon - Error Exception in AppMerge flows' progression
Message icon - Error Exception in AppMerge flows' progression
Message icon - Error Error loading the persistence descriptor WEB-INF/classes/META-INF/persistence.xml from the module Lee5.war.
See the following stack trace for nested errors:
weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND D:\bea\user_projects\domains\base_domain\weblogic.utils.classloaders.GenericClassLoader#1702c48
finder: weblogic.utils.classloaders.CodeGenClassFinder#44757a
annotation: \WEB-INF\classes\META-INF\persistence.xml:2:3:2:3:
problem: cvc-attribute.4: The value '2.0' does not equal the fixed value '1.0' of attribute 'version':<weblogic.utils.classloaders.GenericClassLoader#1702c48
finder: weblogic.utils.classloaders.CodeGenClassFinder#44757a annotation: /WEB-INF/classes/META-INF/persistence.xml:2:3>
at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:245)
at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:231)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:155)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:411)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
at weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDescriptor(AbstractPersistenceUnitRegistry.java:177)
at weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDescriptors(AbstractPersistenceUnitRegistry.java:101)
annotation: \WEB-INF\classes\META-INF\persistence.xml:2:3:2:3:
problem: cvc-attribute.4: The value '2.0' does not equal the fixed value '1.0' of attribute 'version':<weblogic.utils.classloaders.GenericClassLoader#1702c48
This particular problem is caused because the webapp is supplying a persistence.xml which is written for JPA 2.0 while Weblogic 10.3.x only supports JPA 1.0. You need to read the following developer guide how to get JPA 2.0 to run on Weblogic 10.3.x: Running JPA 2.0 API on WebLogic 10.3.
Once you fix this, you'll however hit a new problem as already hinted by Spauny: JSF 2.1 requires Servlet 3.0 and this can only be solved by upgrading Weblogic 10.3 to Weblogic 11. You need to downgrade to JSF 2.0. JSF 2.0 is supported out the box in Weblogic 10.3.3 and newer. For older versions I'm not sure how to upgrade it. See also Steps to deploy latest JSF version in weblogic 10.3.
You could look at this Eclipse bug, very close with your problem, also please note that WebLogic 10.3 has Java EE 5 and Servlets 2.5 and JSF 2.1 requires Servlets 3.0.\
Also you could see this topic which points to the types differences of schemaLocation: http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg05639.html
You should look carefully at a migration guide!
Edit: This post could also be of help: http://blog.eisele.net/2011/01/weblogic-10340-oepe-maven-primefaces.html