[Outsystems Java stack: Catchup to .NET stack] - add missing feature "Automatic upgrade" support [MUST HAVE]

Install Processes
Not right now

Just like Outsystems .NET stack, the Java stack should also have "Automatic upgrade"

  1. .NET stack, when a solution (eSpace/Extension) is deployed, by default the .NET stack will takecare of automatially updating eSpaces and extensions to match the Outsystems platform that its deployed to. In the Java stack this feature is not supported instead the following error is returned "Automatic upgrade is not supported in J2EE servers. Please upgrade the eSpace with your local Service Studio."

Why is this a must have feature? It is not ideal for Java developers to update one file at a time to deploy a solution.

Without this feature most of outsystems solution packages (including forge solutions) could not be publish without first manually updating one eSpace/extension at a time. 

Created on 6 Apr 2014
Comments (8)
This idea is related to the following forum thread 
(contains possible solution)


Changed the status to
Not right now

Our long term vision includes feature parity between supported stacks. However, that includes significant architecture changes and due to that this particular feature related to automatic upgrades will only be addressed in the context of this long term roadmap. Therefore, I will mark this idea as "not right now".

Nonetheless, thank you very much for your idea, and keep it coming.

Merged from 'Allow easy version upgrades of eSpaces' (idea created on 2015-08-10 21:55:12 by Justin James), on 2018-03-22 09:32:45 by Tiago Leão
Creating a solution with ALL the espaces in your environment and publishing it doesn't solve your problem?
Joao -

Not on a Linux server. It is unable to perform the automatic upgrade when going from 8 to 9. That code is buried in Service Studio (which is why you need to install Studio on the server!) and of course it's a Linux server so...

ah, if we only knew how the commandline parameters of servicestudio are, then perhaps you can build a  script for it..

I actually was working on that *when I posted this*. My current challenge is figuring out what hashing algorithm is used in the Solution manifest file so we can just pop the saved eSpaces back into the Solution and get them republished with one upload.


I already mentioned this to outsystems this is one of the main reason we are not using outsystems java stack!
Manually upgrading was so painful it was just not worth it! (this is not the only problem btw!)

I also provided outsystems with a solution on how to fix this! it can be technically fixed!  

Outsystems you can only upgrade the eSpace in windows because service studio can only be installed on windows!

Outsystems could either implement the code to upgrade eSpace on the outsystems platform server itself (now you dont need to install service studio on a production server, which makes more sense than installing outsystems service studio IDE on the production server, this never makes sense, would you install visual studio IDE on a production server???)

If outsystems is unable to implement the upgrade service in outsystems platform server itself, (this might be due to 3rd party libraries or other reason) well outsystems could link the production server to a "HOST" deployment server that is capable of upgrading the eSpace. This way now the "HOST" deployment server will compile the eSpace and push the eSpace out for deployment on to the production server! problem solved!