You are hereForums / JDF Tools / JDF Editor / HTTP Server - does it support MIME packages?

HTTP Server - does it support MIME packages?

1 reply [Last post]
Sat, 11/05/2011 - 08:17
ranko
Offline
Joined: 06/09/2011

I was wondering if the JDF Editor's HTTP server supports MIME packages? Furthermore, what is causing the Java NullPointerException?

I downloaded and ran the JDF Editor with HTTP server support (see CIP4 JDF Editor - Http Server). Furthermore, I set it up to receive JMF messages as described in Http Server.

Unfortunately I get a HTTP 500 error in my .NET application:

System.Net.WebException: The remote server returned an
error: (500) Internal Server Error.
    at
System.Net.HttpWebRequest.GetResponse()

On the console I see:

java.lang.NullPointerException
        at org.cip4.jdfeditor.transport.JMFServlet.processMessage(JMFServlet.java:141)
        at org.cip4.jdfeditor.transport.JMFServlet.doPost(JMFServlet.java:112)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:616)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:427)
        at org.mortbay.jetty.servlet.ServletHandler.dispatch(ServletHandler.java:654)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:556)
        at org.mortbay.http.HttpContext.handle(HttpContext.java:1563)
        at org.mortbay.http.HttpContext.handle(HttpContext.java:1515)
        at org.mortbay.http.HttpServer.service(HttpServer.java:956)
        at org.mortbay.http.HttpConnection.service(HttpConnection.java:814)
        at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:981)
        at org.mortbay.http.HttpConnection.handle(HttpConnection.java:831)
        at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
        at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
        at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)

The same message is correctly received by Bambi.

The message sent looks like this (actual Base64 data removed):

MIME-Version: 1.0
From: jdf@aquila-solutions.com
Date: 5 Nov 2011 09:07:40 +0100
Content-Type: multipart/related; boundary=--boundary_0_fee98f72-60d9-4fac-9af1-957909c8373a
----boundary_0_fee98f72-60d9-4fac-9af1-957909c8373a
Content-Type: application/vnd.cip4-jmf+xml
Content-Transfer-Encoding: base64
Content-ID: <1238@aquila-solutions.com>
<removed>
----boundary_0_fee98f72-60d9-4fac-9af1-957909c8373a
Content-Type: application/vnd.cip4-jdf+xml
Content-Transfer-Encoding: base64
Content-ID: <1238@aquila-solutions.com>
Content-Disposition: attachment; filename=1238.jdf
<removed>
----boundary_0_fee98f72-60d9-4fac-9af1-957909c8373a--
       


          

  


  

    

      Top
    


          

              

      



  

    


  

    

      Sat, 11/05/2011 - 15:33
          


          #1 
      


  


    

      



 

        

            

        stefan      


                    
      
                    

           Offline        

      
            
            
            
                    

          Joined: 11/02/2010        

      
            
                


        

            
            
            
                


        

            
          
               

  



    


    

              

          Is not supported        

      
      

         
Hi Ranko,
JDF Editor currently does not support receiving MIME packages via HTTP. If you think it would be a useful feature you can propose it on the cip4 jira system (http://jira.cip4.org/jira).
But in my daily job I don't work with CIP4 JDF Editor. My favourit tools are CIP4 Alces and for editing JDF / JMF documents I use "Nodepad++" (http://notepad-plus-plus.org/). On last one you only have to activate the XML Syntax Highlighting for JDF /JMF files.
Stefan
       


          

  


  

    

      Top
    


          

              

      


  

      


    



   
   
   
        	
                  


          
            
 

    
In Cooperation With

   
 
CIP4 Organization
 



 

    

   
 


JDF Profit Smartly

 



 

    
   







 

    
Newsletter

   
      
Subscribe to news and page updates.

  
      



 
 




 




 









  
  
  
  



 

    
Site License

   





		Creative Commons Attribution-ShareAlike 3.0 Unported
This Work, jdf4you.org, is licensed under a Creative Commons Attribution-ShareAlike license, although certain works referenced herein may be separately licensed.









 

    
Glossary

   
JDF Controller


 Agents create and modify JDF information; Controllers route it to the appropriate
Devices. The minimum requirement of a Controller is that it can initiate Processes on at least one Device, or at least one other Slave Controller that will then initiate Processes on a Device. In other words, a Controller is not a
Controller if it has nothing to control. In some cases, a pyramid-like hierarchy of Controllers can be built, with Controllers at the top of the pyramid controlling a series of lower-level Controllers at the bottom. The lowest-level
Controllers in the pyramid, however, MUST have Device capability. Therefore, Controllers MUST be able to work in collaboration with other Controllers. In order to communicate with one another, and to communicate with Devices, Controllers MUST support the JDF file-exchange protocol and MAY support JMF. Controllers can also determine Process planning and scheduling data, such as Process times and planned production amounts.

(Source: JDF Spec. 1.4a)