Texo provides both a development as well as a runtime solution. The development plugins can be downloaded and installed in Eclipse using the update manager. For runtime usage you can use maven or download directly. See further below for more information.

−

== Update Manager Locations ==

+

== Development Environment: update manager ==

−

To enable code generation in Eclipse or to use Texo in an OSGI-plugin environment in Eclipse, you need to install Texo into Eclipse. This is done through an update manager. For runtime usage of Texo see the next section.

+

For Texo's development solutions you need to install Texo into Eclipse. This is done through an update manager. For runtime usage of Texo see the next section.

Texo is available through this update site:

Texo is available through this update site:

Line 11:

Line 11:

The last successful nightly build is available through this update site:

The last successful nightly build is available through this update site:

After installing and restarting you can generate code from ecore/xsd models and refer to Texo plugins from plugin MANIFEST.MF files.

After installing and restarting you can generate code from ecore/xsd models and refer to Texo plugins from plugin MANIFEST.MF files.

−

== Using Texo at runtime outside of Eclipse/OSGI ==

+

== Runtime usage, web container ==

−

To use the runtime layer of Texo outside of OSGI/Eclipse (for example in a web containter) you need to take the org.eclipse.emf.texo jar file which is located in the plugins directory of the Eclipse installation.

+

For runtime usage you have several options to download the Texo jar files and their dependencies.

−

The Texo runtime jar depends on three other jars which are also located in the plugins directory:

+

=== Texo jar files and dependencies ===

−

* org.eclipse.emf.ecore

+

−

* org.eclipse.emf.ecore.xmi

+

To use the runtime layer of Texo in a web container you need the following jar files:

These jar files are available through maven (for example version 2.8.0-v20120911-0500), or can be found in the plugins directory of your Eclipse installation.

+

+

Note: you can also configure Texo to [[Texo/Code_Generation_Patterns#Only_Generate_Entities_-_No_EMF_dependencies | only generate Entities, without EMF dependencies]]. In this case there is no dependency on EMF.

+

+

For '''JSON''' web service support you also need to obtain org.json jar file. These can be downloaded from the maven central repository, or try [http://www.eclipse.org/downloads/download.php?r=1&file=/tools/orbit/downloads/drops/R20110523182458/repository/plugins/org.json_1.0.0.v201011060100.jar this] location.

+

+

=== Maven ===

+

+

Texo jars (and their EMF dependencies) are also available in the [http://search.maven.org/#search%7Cga%7C1%7Corg.eclipse.emf.texo maven central repository] and in the [https://oss.sonatype.org/content/repositories/snapshots/org/eclipse/emf/ sonatype snapshot repository].

+

+

Here is an example on how to make use of Texo snapshots available through sonatype:

+

<source lang="xml">

+

<repositories>

+

<repository>

+

<id>sonatype-oss-public</id>

+

<url>https://oss.sonatype.org/content/groups/public/</url>

+

<releases>

+

<enabled>true</enabled>

+

</releases>

+

<snapshots>

+

<enabled>true</enabled>

+

</snapshots>

+

</repository>

+

</repositories>

+

</source>

+

+

The EMF jar files are published within the same group id as Texo: [http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.eclipse.emf%22 org.eclipse.emf]. Texo will work fine with older versions of EMF (from 2.5.0 onwards), but if you can, use the latest EMF versions available in maven central.

+

+

When using maven in your project it makes sense to check this troubleshooting tip:

'''Note: the Texo pom files currently do not explicitly define dependencies to the EMF and json libraries. This means that you manually need to define the dependency to these libraries in your own pom. This will be re-solved/fine-tuned in later versions.'''

+

+

=== Download Texo jar files ===

+

+

The Texo jar files can also be downloaded directly from this page: http://download.eclipse.org/modeling/emft/texo/updates/interim

(These are just the steps that worked for me, not "official" Texo docs.. Hopefully it will help other non-webdev folks.. --[[User:Milesparker.gmail.com|Milesparker.gmail.com]] 02:36, 10 September 2013 (UTC))

+

+

#(You need Eclipse for Java EE, or a whole bunch of EE features, but I'm not really sure what. Probably better just to install EE...)

+

#Install Tomcat. I used 7.0. If you're on *nix / Mac, be sure to set permissions and owner for the install dirs, or Tomcat will fail in a totally unhelpful way. See this [http://wolfpaulus.com/jounal/mac/tomcat7 helpful page]

+

#Import the project from git://github.com/mtaal/texo.git

+

#Copy the following from you eclipse plugins dir into /WebContent/WEB-INF/lib

+

#*org.eclipse.emf.texo

+

#*org.eclipse.emf.texo.datagenerator

+

#*org.eclipse.emf.texo.json

+

#*org.eclipse.emf.texo.server

+

#*org.eclipse.emf.texo.xml

+

#You also probably need

+

#*org.json

+

#You need servlet-api.jar as well to build, at least on Mac. But don't put it into /WebContent/WEB-INF/lib -- Tomcat has a small heart attack and then complains about it in a really obscure message referencing a server spec (I kid you not). So put it in say "lib". Then add it to your build path Libraries.

+

#It should build now, but Tomcat is still unhappy. Ready for something ''really'' obscure? Select Project:Properties:Deployment Assembly. Then add the libraries that you just added to the WEB-INF there as well. No idea why this seems to be necessary but see this [http://www.eclipse.org/forums/index.php/t/169465/ thread] for some (painfully obscure) context.

+

#Create the server. See this [http://www.coreservlets.com/Apache-Tomcat-Tutorial/tomcat-7-with-eclipse.html helpful page], especially the "Copy the ROOT..." section (assuming you want Tomcat to actually work properly).

+

#Add the org.eclipse.emf.texo.web.example to that.

+

#Start the server.

+

#At this point, there is a pretty good chance that navigating to http://localhost:8080/org.eclipse.emf.texo.web.example/model/library will bring joy.

Revision as of 22:41, 9 September 2013

Contents

Texo provides both a development as well as a runtime solution. The development plugins can be downloaded and installed in Eclipse using the update manager. For runtime usage you can use maven or download directly. See further below for more information.

Development Environment: update manager

For Texo's development solutions you need to install Texo into Eclipse. This is done through an update manager. For runtime usage of Texo see the next section.

The EMF jar files are published within the same group id as Texo: org.eclipse.emf. Texo will work fine with older versions of EMF (from 2.5.0 onwards), but if you can, use the latest EMF versions available in maven central.

When using maven in your project it makes sense to check this troubleshooting tip:

Note: the Texo pom files currently do not explicitly define dependencies to the EMF and json libraries. This means that you manually need to define the dependency to these libraries in your own pom. This will be re-solved/fine-tuned in later versions.

Copy the following from you eclipse plugins dir into /WebContent/WEB-INF/lib

org.eclipse.emf.texo

org.eclipse.emf.texo.datagenerator

org.eclipse.emf.texo.json

org.eclipse.emf.texo.server

org.eclipse.emf.texo.xml

You also probably need

org.json

You need servlet-api.jar as well to build, at least on Mac. But don't put it into /WebContent/WEB-INF/lib -- Tomcat has a small heart attack and then complains about it in a really obscure message referencing a server spec (I kid you not). So put it in say "lib". Then add it to your build path Libraries.

It should build now, but Tomcat is still unhappy. Ready for something really obscure? Select Project:Properties:Deployment Assembly. Then add the libraries that you just added to the WEB-INF there as well. No idea why this seems to be necessary but see this thread for some (painfully obscure) context.

Create the server. See this helpful page, especially the "Copy the ROOT..." section (assuming you want Tomcat to actually work properly).