complete exasperation

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Smith, Donald wrote:

> Then we started an internal project and I recommended we use Orbeon. We
> initially started the application in 2.8 but decided mid-way through to
> upgrade to 3.0. I didn’t realize initially all the changes that came
> with 3.0, so it was a learning curve again to catch up. But I did enough
> that I was able to get my 2.8 pages converted to 3.0 and it all runs
> just fine in the demo environment.

We reckon that there is a learning curve between 2.8 and 3.0, especially
when it comes to XForms support. Unfortunately, this was difficult to
avoid with the move to a much better XForms engine. The good news is
that there is now a much better XForms engine, so we hope that the
transition will be worth it.

> So now we’ve been trying to deploy our app as a .war file in Tomcat and
> no matter what we do, it always deploys as a 2.8 app. We downloaded the
> latest Studio and as far as we can tell, it doesn’t do 3.0.
>
> Now I’m sure I’ve missed something in the documentation that would tell
> me what I’ve missed or done wrong. But at this point I don’t even know
> what to look for. Can someone please have enough patience to explain to
> me what I need to do. If not, I’ll have no choice but to walk away from
> Orbeon.

The good news is that I think it has to be something really simple, you
know, like the typical programmer thing where you spend hours editing a
file, and your bug is not fixed, and it turns out eventually that you
were just editing the file in the wrong location.

Now, can you give more details about the following:

o How exactly do you deploy into Tomcat, and what are the differences
with what you were doing before, which was working?

o How can you tell that it "deploys as 2.8" vs. 3.0? Just that the
application doesn't work?

o How do you build your WAR file? In particular, where did you get the
JAR files under the WEB-INF directory?

-Erik



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Erik,

Thanks. I really appreciate it.

>The good news is
>that there is now a much better XForms engine, so we hope that the
>transition will be worth it.

I agree. It's one reason why I've been happy to keep working to
understand how it all works.

>The good news is that I think it has to be something really simple

From your mouth to God's ear. :-)


>Now, can you give more details about the following:

>o How exactly do you deploy into Tomcat, and what are the differences
>with what you were doing before, which was working?

I'll have to get my tech lead to explain this one. See subsequent post.

>o How can you tell that it "deploys as 2.8" vs. 3.0? Just that the
>application doesn't work?

Yes, but more specifically, we get errors that 3.0 syntax in the
page-flow.xml file isn't allowed, which is obviously a sign we're still
running the 2.8 engine.

>o How do you build your WAR file? In particular, where did you get the
>JAR files under the WEB-INF directory?

This is no doubt a huge part of our problem. We just went with the
content of the latest Studio download. After our failure, we looked and
realized that it's running orbeon.jar instead of ops.jar. So clearly we
need to switch that. But is there more we need to switch? Where is this
documented (I'm sure you guys have documented it and we've just missed
it)?

Thanks,

Don





--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Smith, Donald wrote:
 >> Now, can you give more details about the following:
 >
 >> o How exactly do you deploy into Tomcat, and what are the differences
 >> with what you were doing before, which was working?
 >
 > I'll have to get my tech lead to explain this one. See subsequent post.
 >
 >> o How can you tell that it "deploys as 2.8" vs. 3.0? Just that the
 >> application doesn't work?
 >
 > Yes, but more specifically, we get errors that 3.0 syntax in the
 > page-flow.xml file isn't allowed, which is obviously a sign we're still
 > running the 2.8 engine.
 >
 >> o How do you build your WAR file? In particular, where did you get the
 >> JAR files under the WEB-INF directory?
 >
 > This is no doubt a huge part of our problem. We just went with the
 > content of the latest Studio download. After our failure, we looked and
 > realized that it's running orbeon.jar instead of ops.jar. So clearly we
 > need to switch that. But is there more we need to switch? Where is this
 > documented (I'm sure you guys have documented it and we've just missed
 > it)?

It looks like this is a hole in the doc. We will be working on
improving this real soon. In the meanwhile, a way to go forward:

o Download a fresh OPS 3.0.1 if you haven't done so already.

o Extract the zip or tgz archive. A directory called
   "ops-3.0.1.200602032326" will be created.

o Under that directory, you will find a file called ops.war.

o Extract ops.war with an "unzip" tool into some directory, for
   example ops-war. Under ops-war, you will find a "WEB-INF" directory,
   and under that directory, a "resources" directory.

o Under the "resources" directory, remove the following folders:

   o "doc"
   o "examples"
   o "examples-portal"
   o "examples-standalone"
   o "init-database"

   o Some images under the "images" directory can also be removed, but
     for now you can leave them. In the future, we will reorganize the
     images to make it clearer.

 
http://forge.objectweb.org/tracker/index.php?func=detail&aid=304626&group_id=168&atid=350207

o Add your own resource files under the "resources" directory. If your
   application is a purchase order application, you may want to locate
   all your application's under a directory called
   "purchase-order". Alternatively, you may want to create one
   subdirectory per page or service in your application. The choice is
   yours.

o Replace the "page-flow.xml" file under "resources" with your own. A
   minimal version of the page flow is attached. In your own page flow,
   you must obviously have your own page declarations. Paths for page
   models, page views, etc. must point to your own files under
   "purchase-order".

o Optionally, you may remove the "context" directory under
   "resources", after having removed references to the listners in
   "web.xml".

o At this stage, your are left with the following under "resources":

   o "config": files needed by OPS (theme, etc.) but that you can
     configure for your own needs.

   o "ops": files needed by OPS that you should not modify unless you
     really know what you are doing.

   o "images": some images (see above). Not crucial, but currently the
     XForms engine uses some of those.

   o "page-flow.xml": your page flow configuration.

o You now have a nice exploded WAR file under ops-war, which contains
   your application. If you are using Tomcat, you can create a
   <context> in server.xml to just point to the ops-war directory.

   With other application servers, you may have to create an actual
   .war file, by zipping the WEB-INF directory and its content.

   Note that it is still preferable to tell your application server to
   work on an "exploded" WAR file.

I hope this helps a bit. What we plan to do from here:

o Put an improved version of the above in the OPS doc.

o Create a minimal template WAR that you can use directly, or a tool
   to create such a template WAR.

-Erik




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws