facebook

Brief ToDo for deploying an EJB

  1. MyEclipse Archived
  2.  > 
  3. Old Posts
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #196363 Reply

    pbrown74
    Member

    Hi there

    i’ve installed your stuff and been through the Web App demo, which i have got working (almost-the servlet doesn’t seem to be accessible but that may be due to something i’ve missed in the steps) …

    since browsing the online docs i have found that EJB support is not yet in place…fair enough, but have you got a brief TODO/readme for how to this by hand?

    i’d like to know where in the Project tree to put each of the minimum req files and if/how i need extra steps to deploy an “exploded EAR” (just guessing this is how it would be done…)

    basically, i need to get a development environment up and running where i can hack out some servlets/EJBs using your stuff and get them deployed into JBoss3.2.1… i’m willing to wait for the next release of your stuff as i like your IDE/Eclipse2.1 but i need a manual stop gap to get something out right now.

    we are a reasonably sized team and i’d like to get everyone into MyEclipse over the coming months if possible

    thanks
    Paul

    #196364 Reply

    Scott Anderson
    Participant

    Paul,

    Since we’re all working very hard to get the next release of Enterprise Workbench out the door, including the deployment tooling, I’ll do my best to give you a quick sketch of how you can set up an exploded EAR with Eclipse and debug it using version 2.0.3’s application server adaptors.

    The information below should only be used prior to the release of Enterprise Workbench EA2 since that release will have a full EAR project model and deployment tooling to facilitate this work.

    You can debug an enterprise application using MyEclipse provided:
    1) The source is contained in one or more open projects.
    2) The application was deployed as an archive (EAR, WAR) or in exploded format to the application server
    3) The server was started using the appropriate MyEclipse application server connector.

    So, all you have to do is get your project(s) set up and deployed manually. A tutorial, using some of the JBoss examples, on how to do that with Eclipse is available at: http://mywebpages.comcast.net/sgjava/jboss_examples.htm

    Please note that this configuration most likely will NOT be compatible with the deployment tooling of MyEclipse, when available so it should primarily be done simply for education.

    In order to deploy the project(s), you can either write an Ant script to create an EAR or WAR file or you can use exploded format. If you create an archive, you simply copy it to the ‘deploy’ directory under your JBoss domain. If you use an exploded format, you need to point the jboss-service.xml file to it by editing the URLs “attribute” of the URLDeploymentScanner mbean as follows:
    <attribute name=”URLs”>deploy/,file:///C:/dev/workspaces/runtime-workspace/JBossTest/</attribute>

    Hopefully that’s enough to get you started. If you have specific questions later, just ask.

    –Scott
    MyEclipse Support

    #196365 Reply

    Scott Anderson
    Participant

    Paul,

    Since we’re all working very hard to get the next release of Enterprise Workbench out the door, including the deployment tooling, I’ll do my best to give you a quick sketch of how you can set up an exploded EAR with Eclipse and debug it using version 2.0.3’s application server adaptors.

    The information below should only be used prior to the release of Enterprise Workbench EA2 since that release will have a full EAR project model and deployment tooling to facilitate this work.

    You can debug an enterprise application using MyEclipse provided:
    1) The source is contained in one or more open projects.
    2) The application was deployed as an archive (EAR, WAR) or in exploded format to the application server
    3) The server was started using the appropriate MyEclipse application server connector.

    So, all you have to do is get your project(s) set up and deployed manually. A tutorial, using some of the JBoss examples, on how to do that with Eclipse is available at: http://mywebpages.comcast.net/sgjava/jboss_examples.htm

    Please note that this configuration most likely will NOT be compatible with the deployment tooling of MyEclipse, when available so it should primarily be done simply for education.

    In order to deploy the project(s), you can either write an Ant script to create an EAR or WAR file or you can use exploded format. If you create an archive, you simply copy it to the ‘deploy’ directory under your JBoss domain. If you use an exploded format, you need to point the jboss-service.xml file to it by editing the URLs “attribute” of the URLDeploymentScanner mbean as follows:
    <attribute name=”URLs”>deploy/,file:///C:/dev/workspaces/runtime-workspace/JBossTest/</attribute>

    Hopefully that’s enough to get you started. If you have specific questions later, just ask.

    –Scott
    MyEclipse Support

    #196366 Reply

    pbrown74
    Member

    thanks for the quick response. i’ll give it a try in the morning. time to eat and drink now. see ya. paul.

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: Brief ToDo for deploying an EJB

You must be logged in to post in the forum log in