Good sleuthing Tony.

I opened a ticket here for the localhost fix:
https://tickets.openmrs.org/browse/TRUNK-2765

Can you add a link to the other thread you found about it?

Ben

On Wed, Oct 12, 2011 at 9:03 PM, Tony Dunbar <[email protected]> wrote:

> Thanks Janet...Thanks Daniel!
>
> Wow...after about 2 full days I was finally able to get my build
> environment setup and the OpenMRS application deployed and running.
>
> The two main problems I experienced were that I couldnt use the default
> port 8080 as the port which jetty listens on.  I could not initially find
> the place to change it to an alternate port number.  I finally found a
> reference on the web to adding the following to the maven.jetty.plugin
> configuration in the file webapp/pom.xml:
>
>                <connectors>
>                   <connector
> implementation="org.mortbay.jetty.nio.SelectChannelConnector">
>                      <port>8083</port>
>                      <maxIdleTime>60000</maxIdleTime>
>                   </connector>
>                </connectors>
>
> Afterwards, I was able to launch the jetty server and install the app.
> Then, the install was failing due to not being able to create the
> openrms_user or set its permissions in the database.  I discovered from past
> issue threads that others had similar problems and a code change was made to
> specify 'root'@'localhost' instead of 'root'@'%' in the database
> installation script.  This was a problem for me in that mysql is not
> installed on the same machine as the web servers.  In both my dev and
> production environments this will always be a different server.  Therefore,
> I specfied during the install that I did not need a separate login to be
> created and this step was skipped.  Afterwards, the remainder of the install
> went smoothly.  Just to make sure I could repeat the install process, I
> dropped everything and reinstalled from nothing two more times.  Repeating
> the process took less than an hour and was successful.
>
> Thanks for the links to the web service information.  I will review and
> consider it.  I am still leaning toward using the API directly for
> concurrency, speed and scalability but the info is useful.
>
> Thanks,
> Tony
>
>
> On Wed, Oct 12, 2011 at 6:44 AM, jriley <[email protected]> wrote:
>
>> Hi Tony-
>>
>> Great question.
>>
>> Here's a wiki page that addresses using the API:
>> https://wiki.openmrs.org/display/docs/How+To+Use+the+OpenMRS+API
>>
>> As Daniel mentioned, you can set up an OpenMRS server and call web
>> services.
>> The section called "In an External Application using web services" links
>> to
>> that documentation.
>>
>> If you prefer to use the libraries in your own app, look at the section
>> "In
>> an External Application using the API Jar" .
>>
>> You can jump-start your application in Eclipse with the Maven module
>> archetype.  This will make a mavenized skeleton for an OpenMRS module.  It
>> makes an Eclipse project with a Maven pom.xml for you, which will take
>> care
>> of downloading all the OpenMRS jars that you need.  You can delete the
>> "web"
>> folder entirely, and rename the "api" folder to something more suited to
>> your project.
>>
>> There are directions at:
>>
>> https://wiki.openmrs.org/display/docs/Step+by+Step+Installation+for+Developers
>>
>> The maven archetype directions are at:
>> https://wiki.openmrs.org/display/docs/Using+the+Module+Maven+Archetype
>>
>> You can find API documentation at
>> https://wiki.openmrs.org/display/archive/Developer+Resources .  There's
>> no
>> separate documentation for 1.8.x, the current stable release.  I believe
>> all
>> the differences between 1.7 and 1.8 were behind the scenes performance
>> improvements, so download the 1.7 .  Version 1.9 is in development now.
>> You
>> can see the documentation for it at http://resources.openmrs.org/doc .
>>
>> The API docs often have some helpful examples at the beginning of class
>> descriptions.   You might also take a look at
>> org.openmrs.api.context.Context .  Browse all the services called
>> getXYZService() .  These services have the "big picture" methods that show
>> you what kinds of things you can save or search for.
>>
>> Finally, the unit tests are an excellent way to see how to call the API.
>> The OpenMRS source code is at
>> https://source.openmrs.org/changelog/~br=trunk/OpenMRS .
>>
>> For your own unit tests, if you need to test things with API calls or have
>> a
>> database populated with  OpenMRS objects, make your JUnit classes extend
>> the
>> BaseContextSensitive class.  Details at
>> https://wiki.openmrs.org/display/docs/Unit+Tests .
>>
>> Cheers-
>> Janet
>>
>>
>>
>> --
>> View this message in context:
>> http://openmrs-mailing-list-archives.1560443.n2.nabble.com/OpenMRS-Dev-Forum-tp6882651p6884428.html
>> Sent from the Developers mailing list archive at Nabble.com.
>>
>> _________________________________________
>>
>> To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to
>> [email protected] with "SIGNOFF openmrs-devel-l" in the  body
>> (not the subject) of your e-mail.
>>
>> [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
>>
>
> ------------------------------
> Click here to 
> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from 
> OpenMRS Developers' mailing list

_________________________________________

To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to 
[email protected] with "SIGNOFF openmrs-devel-l" in the  body (not 
the subject) of your e-mail.

[mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]

Reply via email to