• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Small Consulting Gig to Start with

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello All. I am a freelance database/network engineer who has been asked by a long term client of mine to move their old java application to new java editions as who they work with are forcing them to do the same because of security needs. This is a 21 page application that was developed 7-8 years ago. It is for all purposed a stand alone web application in which users enter data from 6-7 warehouses in the country and it generates reports/pricing. I need to provide a plan for my upgrade and, if approved, I might be back here to get it done! Can someone please help me with creating the plan/approach. I am willing to pay for few consulting hours for the plan/approach.

Present ---> Moving To
Java EE 1.4 --->Java EE 7
Apache Struts 1.3 ---> Apache Struts 2.3
Hibernate 3.0 ---> Hibernate 4.3
Apache Ant 1.3 ---> Apache Ant 1.9
XDoclet ---> Unacceptable. Application to be refactored to remove this technology
JBoss Application Server 4.0 ---> JBoss Application Server 7.3

Database is Microsoft SQL and I will be upgrading to 2014 from 2008.

Presently the JBoss Application Server 4.0 has been bundled into the application (tool) ecosystem, along with patches to support SOAP and EJB 3. The application build scripts are designed to output a standalone package consisting of the JBoss server with the application (tool) installed in it. This package can then be run as a self-contained server. According to the system admin, who is not Java savy, tight integration of an application server with the application itself, the sophisticated Ant build scripts, and the use of XDoclet for code generation and configuration generation might present a unique challenge in modernizing this application.


Thanks.
 
Bartender
Posts: 9626
16
Mac OS X Linux Windows
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Ben Edwards wrote:
Java EE 1.4 --->Java EE 7


That would depend on exactly what you are using from EE.

Ben Edwards wrote:
Apache Struts 1.3 ---> Apache Struts 2.3


There's upgrade resources here (scroll down to "Struts 1 to Struts 2")

Ben Edwards wrote:
Hibernate 3.0 ---> Hibernate 4.3


upgrade guide here

Ben Edwards wrote:
Apache Ant 1.3 ---> Apache Ant 1.9


Depends on how it is used. I recently went from running a build script from 1.6 to 1.9 without any issues

Ben Edwards wrote:
XDoclet ---> Unacceptable. Application to be refactored to remove this technology


Never used it so I can't say.

Ben Edwards wrote:
JBoss Application Server 4.0 ---> JBoss Application Server 7.3


No idea. Googling turned up this article which may be a good starting point.
Where's my check?
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic