[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
| 
Re: [glassfish-dev] Glassfish Jakarta EE9 - No Docker images!?
 | 
  
  
    Hello Arjan,
    thanks for your response.
    I did some short testing with the Dockerfile you mentioned
      (https://github.com/arjantijms/glassfish-docker/blob/main/Dockerfile)
      but I failed  - I think because of the missing Microprofile
      parts...
    I guess your answer will be that is that Microprofile and
      Glassfish are different things ;-) Sure, but how can we improve
      the situation for new developers who want to test Jakarta EE 9? In
      my eyes this is an unsatisfactory situation now that they can't
      find a Docker image. 
    
    It looks to me that Wildfly wildfly-preview-26.0.0-final is
      currently the only runtime providing the new namespaces and
      delivering all the promised features (including microprofile 3.2).
      But also Wildfly is not offering a Docker Image for the preview
      version. 
    
    To be clear, I don't blame you or the Glassfish project here. I
      just want to point out that the situation is really strange. You
      all did so much great work behind the scene. But for nearly one
      year now we (the normal Jakarta EE developers who are migrating
      there Java EE projects) have no chance to get a working Jakarta EE
      9 Docker image out of the box.
    
    I have migrated my own open source workflow engine to Jakarta EE
      9 a half year ago
(https://github.com/imixs/imixs-workflow/releases/tag/imixs-workflow-6.0.0),
      but I still can't promote it because there are no official Docker
      based runtimes available. 
    
     You mentioned that EE 9 is just an intermediate version. But
      what did this mean? Will it take much more time now until 9.1 is
      available? Or will be version 10 the goal? It doesn't make sense
      to push the specification if there are no runtime environments
      available.
    
    Why I'm riding around on it has the following practical reason. I
      am currently in a larger enterprise project in which the question
      is asked whether microservices should be developed with SpringBoot
      or with Jakarta EE. What would you advise here? Go ahead with
      Jakarta EE 8 (meaning Java EE8)?
    
    
    
    Best regards
    Ralph
    
    
    
    On 16.01.22 23:09, arjan tijms wrote:
    
    
      
      Hi,
        
        
        
        
        
        
        
        
        Ed, Ivar, do you know who has access to this?
        
        
        p.s.
        
        
        Regarding the promotion of EE 9; EE 9 is mostly intended as
          an intermediate version to prepare tool vendors.
        
        
        Kind regards,
        Arjan
        
        
        
        
        
        
       
      
      
        
        
          
            Hello,
            I wonder why there is no Docker image for Glassfish
              available? Docker makes it more convenient for users to
              get started. The official Docker repo is totally outdated
              (https://hub.docker.com/_/glassfish).
              
            
            Ok, there are Jakarta EE8 images from Payara and Wildfly
              available, but still only for Jakarta 8 and nothing
              working with Jakarta EE9 (including JAX-RS and EJBs)
            
            Within the Eclipse Jakarta EE project ther is one version
            after the other being discussed - we are already at Jakarta
            EE 10 - but there is still no official server for Jakarta
            EE9 available. If Payara and Wildfly are for what reason
            ever not allowed to publish Jakarta EE9 Severs on Docker Hub
            than at least a Glassfish Server would be great. 
            
If you want to start a new Project with Jakarta EE9 you
              have no official Docker Image at all. Why?? It looks like
              the community wants to do everything to ensure that
              Jakarta 9 does not establish itself as a new platform. 
            
            What is your opinion about this situation?
            
            
            p.s:
            
            The only way I solved this for my current dev project, is
              building my own Jakarta EE9 Docker image by downloading
              the wildfly-preview-26.0.0.Final : 
            
            
            
            ###################################################################
              # We are building our own jakarta 9 sever
              #
              # See: https://github.com/jboss-dockerfiles/wildfly
              FROM jboss/base-jdk:11
              # Set the WILDFLY_VERSION env variable
              ENV WILDFLY_VERSION 26.0.0.Final
              ENV JBOSS_HOME /opt/jboss/wildfly
              USER root
              # Add the WildFly distribution to /opt, and make wildfly
              the owner of the extracted tar content
              # Make sure the distribution is available from a
              well-known place
              RUN cd $HOME \
                  && curl -L -O
              https://github.com/wildfly/wildfly/releases/download/$WILDFLY_VERSION/wildfly-preview-$WILDFLY_VERSION.tar.gz
              \
                  && tar xf
              wildfly-preview-$WILDFLY_VERSION.tar.gz \
                  && mv $HOME/wildfly-preview-$WILDFLY_VERSION
              $JBOSS_HOME \
                  && rm wildfly-preview-$WILDFLY_VERSION.tar.gz
              \
                  && chown -R jboss:0 ${JBOSS_HOME} \
                  && chmod -R g+rw ${JBOSS_HOME}
              # Ensure signals are forwarded to the JVM process
              correctly for graceful shutdown
              ENV LAUNCH_JBOSS_IN_BACKGROUND true
              USER jboss
              # Expose the ports in which we're interested
              EXPOSE 8080
              EXPOSE 9990
              COPY ./target/*.war
              /opt/jboss/wildfly/standalone/deployments/
              # Run with microprofiles
              CMD ["/opt/jboss/wi
###################################################################
            
            
            
            Regards
            Ralph
            
            
            
            
            -- 
              
                Imixs Software Solutions GmbH 
                Web: www.imixs.com
                Phone: +49 (0)89-452136 16 
                Timezone: Europe/Berlin - CET/CEST
                Office: Agnes-Pockels-Bogen 1, 80992 München
                Registergericht: Amtsgericht Muenchen, HRB 136045
                Geschaeftsführer: Gaby Heinle u. Ralph Soika 
              
                Imixs is an open source company, read more: www.imixs.org
              
             
           
          _______________________________________________
          glassfish-dev mailing list
          glassfish-dev@xxxxxxxxxxx
          To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev
        
       
      
      
      _______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev
    
    -- 
      
        Imixs Software Solutions GmbH
        
        Web: www.imixs.com Phone:
        +49 (0)89-452136 16 
        Timezone: Europe/Berlin - CET/CEST
        Office: Agnes-Pockels-Bogen 1, 80992 München
        Registergericht: Amtsgericht Muenchen, HRB 136045
        Geschaeftsführer: Gaby Heinle u. Ralph Soika
      
      
        Imixs is an open source company, read more: www.imixs.org