Rob Spoor wrote:I haven't worked with GlassFish for a while, but I assume that data source has a JNDI name. You then use that JNDI name in your persistence.xml file, and the persistence unit in your EntityManager declaration. You already have that, so it should work now.
Rob Spoor wrote:I have never used @DataSourceDefinition. Instead, I use a container-specific mechanism to define the data source. In JBoss I both used data source XML files in the deployments folder, and defining the data sources in the JBoss configuration (which can be configured using JBoss CLI, among others). In WebLogic and GlassFish I defined data sources in the WebLogic / GlassFish console application.
Jayesh A Lalwani wrote:Nowadays, most new applications that built on open source technologies are being built on the Spring stack. You don't see support for the full stack among PaaS providers simply because there isn't too much demand for it.
...
So, really there are 2 Java worlds out there
One which throws in a huge mix of Open source technologies into the project. None of these people have any need for a full fledged Application server
ANother which sticks to a supported stack (like Oracle's stack). These people are more likely to go with Oracle's cloud.
Jeanne Boyarsky wrote:Ashley,
If you are just learning/practicing you don't need to deploy anywhere. You can just test on your machine. A lot less people are using EJBs than in the past anyway. If you haven't taken a look at Spring, consider that. You'll learn about the same amount than if you used EJBs. And Spring runs on Tomcat.
Java and .NET are certainly more expensive to host when you need a full blown stack than Ruby and PHP. I think Ruby is more similar to what runs in a servlet container though. Which is plenty! See my reference to Spring above.
Ulf Dittmer wrote:This is an odd question, IMO. Developing an application without regard to the target platform where it should run, when you already know that the target platform might restrict what technologies you can use, doesn't strike me as a sensible approach. If you don't want to make assumptions as to the target platform during development (an odd assumption), then you should target virtual or physical hosts, where you can run pretty much anything you want. If you want to target an IaaS or PaaS platform, then that platform will impose restrictions on what you can do. That's true for any language you choose to develop in.
I'm not at all sure what "the disparity between Java and non-Java application servers in the cloud" is, nor do I find it unreasonable that the deployment platform influences the development technologies, especially when there is an extremely wide range of deployment technologies to chose from. Lastly, "having to pay through the nose" is completely context-sensitive as to your circumstances, so we can't comment on that.
Luan Cestari wrote:OpenShift does support the Java EE standards (you can deploy into a JBoss/WildFly/TomEE/EAP/etc) (and it is supporting (or it is almost supported,not sure) other interesting things like docker)
About the question, I don't think so. I think this is more a generation thing (younger people will have access to technology and want sth very easy to use, and ruby and python is much more intuitive for starters) (which I would summarize that Java get very known and could survive through the time). A second thing is the engineers that built the cloud platform. They had to choose what to support and if the put too much framework and technology that could lead to issues that those external libraries have which would make people lose the trust with the cloud provider which is bad. So they thought to build from the botton to avoid to ask requirements to any external project (making easy to test and maintain) .
william chaple wrote:Ok so do I need to convert checker or min into a string or both into a string? can someone offer me a clue on what method to use? parse, valueof, ect