OpenEdit Developer ForumWelcome to the OpenEdit User Forum. You must be registered and logged in to post a new comment or topic. This forum is only for developers who want to discuss the technical aspects of the OpenEdit Framework. For end user technical support please visit the EnterMedia web site. eclipse projectsHi, Since my last question I have been doing a lot of fun stuff and managed to get my plugins served from a local server etc etc. There is basically only one thing I am a bit confused about and that is how to use the eclipse projects in the right way. Maybe I do something wrong or not as intended but this is what I do: I checkout openedit, openedit-editor and resin3.x as the workspace is build automatically I can run the openedit-editor-resin run configuration and surfing to localhost:8080 works nice. I ran the build.xml files as ant build files and that yielded ROOT.war (strangely after that I need to clean the workspace to run the open-editor-resin configuration again without exceptions) So far so good. After that I wanted to test some plugins so I took openedit-search to start with and checked it out in the workspace. Now the questions came. How can I run/debug this newly checked out plugin? I decided to leave that one for a while as I also had problems installing the plugin in a normal installation. (It never shows up as installed and query.html yield a blank screen) So I decided to try openedit cart (and money) checked out the projects and noticed a copy.bat and copy.sh ;-) it did what I was about to do by hand to get it running. And after that it actually worked sort of to run the openedit-cart-resin configuration. Still some things didnt work as I think they were intended. After this I realized that I must be doing something wrong and that that probably has to do with some missing knowledge. I think the idea is that one can checkout the various projects and create ones own projects and debug that within the eclipse environment. btw the cart plugin junit target fails because of ALLVARLIG(Swedish for serious): Should define catalogid property. Defaulting to /store/ I use: Eclipse SDK
Thanks in advance. Posted by Peter Friebel Thu, Oct 30 2008 2:17 PM
|
Most Recent Posts
encodings ...
(4 comments)
Slamdance
(7 comments)
Help upgrading jars on starter war
(6 comments)
Help, Velocity Generator not initializing
(4 comments)
Multiple Main Sites
(10 comments)
Search filtering by theme
(3 comments)
xml version "s1.0" error
(4 comments)
How can i localization the openedit?
(3 comments)
Problem with the interface
(4 comments)
latest openedit-editor build
(2 comments) Archive
Log in
Syndicate:
|
Copyright 2008 OpenEdit Inc. All rights reserved. last modified: Oct 30 2008

The junit runs works fine fine in the current copy, so I'd suggest you update today and try it again. To actually run the webapp, you're on the right track - run the copy.bat to get the files. (Eclispe will also let you checkout remote folders INTO another project which works fairly well - you can checkout the /WEB-INF/base/openedit folder directly into openedit-cart).
Unless you have a local SMTP server running some of those tests will fail - you can ignore that. The plugins make a great starting point for your own project - I'd copy one like openedit-cart or openedit-blog to myproject and then rename/edit the files in /etc - resin.conf to point at your project, and customize a launcher for your tests and resin instance.
The architecture of a plugin is typically to put your view layer stuff in /WEB-INF/base/myproject and your new plugin.jar in the lib folder. That'll cause oe to load your spring plugin.xml during bootup to load any modules and beans. You're right, you can debug all of this in eclipse locally.
Feel free to ask more - hopefully this'll get you moving forward.
Thanks Ian,
I think It would help with some more "best practise documentation" and development tutorials. I will manage as I love figuring stuff out but I am not sure all the developers that i sometimes need to work with are just as "interested" :-)
Thanks for your help and I will certainly ask more!
I agree with you - I've been trying to find the time to put together a "best practice/quick start" guide for a while. There is a lot of documentation written though - make sure you take a good look through what's there as there are a lot of little gems intermixed.
Cheers,
Ian