Re: [Hypercontent-users] Newbies Questions
Brought to you by:
alexvigdor
Menu
▾
▴
Re: [Hypercontent-users] Newbies Questions
|
From: Alex V. <av...@co...> - 2005-07-01 21:00:17
|
Hi Liying, There is no build filesystem actually configured for the bootstrap project; the build script is present in the bootstrap project because this is where the default set of scripts are stored that all new projects inherit, but the bootstrap project does not itself represent a web site you would want to externalize (although technically you could). Thus you have turned up a bug by doing what new users do best, by performing an unanticipated activity! I suspect your build attempt has corrupted your filesystem.xml, because the system tried to overwrite the file with a copy of itself when it couldn't find a dedicated build filesystem. I will try to get some safeguards in there for the next beta, but now you know, don't try and build the bootstrap project! You'll probably need to recreate your filesystem.xml to recover. Building is the process of rendering a snapshot of your project web site to a flat filesystem; this is referred to as "staging" in some other systems. The premise is that you will build your web site, and review it before publishing, which is the act of copying the built version of the site to its final, public destination (usually a filesystem which is then served by Apache or another dedicated web server). You never have to build during development of a project (though you certainly can); its only purpose is to get your content into a static form in which it can be served by another web server. Until you're ready to push the site out to a dedicated web server, you can continue using the built-in web server. Also, it is completely safe to start a build, and then do other things in the system (this is new in 2.0); the build is spooled off and handled in the background, and you can return later to check its progress, or even logout and log back in later to check on it. Just to give a sense of perspective, our biggest sites, ranging from 1000-2000 pages, will take anywhere from 30 seconds to 5 minutes to build, depending on a number of factors including the volume of includes being processed, the complexity of the XSL transformations, the number of changes since the last build and of course the overall server load. The sample project included with HC2 generally builds in a minute or less on recent hardware, most of which is dedicated to generating the PDF of the manual (100+ pages). To build the sample project, you need to be on a screen under its mountpoint (e.g. http://localhost:8080/sample/index.html?mode=interactive). "Build" instructs the system to build only the current file or directory; "Build All" is used to build the entire project, and is actually the more useful of the two options since it will render all the files that are dependent on changes you have made. Good luck, and thanks for finding that bug! - Alex On Jul 1, 2005, at 4:19 PM, Liying Miao wrote: > Hi Alex, > > I restarted a few times, but the new project still didn't show. > > I'm sorry I can't get to filesystem.xml now because I just started > build > process from Workflow (I was just trying things out and this build > works so > hard and doesn't seem to get anywhere). > _______________________________________________________ > History > 7/1/05 4:01:31 PM Processing > 0% complete: 0 changed, 0 deleted and 0 errors more details > 0 Changed: > > > 0 Deleted: > 0 Errors: > 7/1/05 4:01:29 PM Build > by you > Current Queues > /workflow-data/queues/principal/admin > /workflow-data/queues/build/building > > Attributes > builder = admin > href = http://localhost:8080/projects/SACS/ > path = /projects/SACS/ > ________________________________________________________ > > And all I see now are filesystem.xml.lock and filesystem.xml.lock.rdf > file > under > C: > \Hypercontent\hypercontent2.0b2\hypercontent2\repositories\bootstrap\pr > oje > cts\SACS > > But just for my information, when do we need to build, and how long it > should take? > > Thanks, > Liying > > -----Original Message----- > From: hyp...@li... > [mailto:hyp...@li...] On Behalf Of > Alex > Vigdor > Sent: Friday, July 01, 2005 3:48 PM > To: 'Hypercontent-users' > Subject: Re: [Hypercontent-users] Newbies Questions > > Hi Liying, > There's about a 10 second lag after you add a new project before it > > becomes available at its mounted url, and one person reported that they > had to stop and restart the server before their new project showed up. > But if it's still not showing up after a server restart, you should > check the log for errors, and look to see if the config and > workflow-data directories were generated in your repository directory. > Double-check your filesystem.xml; your mount point should have a > trailing slash as well. (In general, every path that denotes a > directory in any HC configuration file should have a trailing slash). > Feel free to post your filesystem.xml to the list and I'll have a look > at it. > > Alex > > On Jul 1, 2005, at 3:32 PM, Liying Miao wrote: > >> Hi Alex, >> >> Thanks, it was the "/" that caused error. >> >> But I still can't see this page: >> http://localhost:8080/sacs/?mode=interactive >> >> When I clicked SACS Test link from the project index page, it >> says:"The page >> can't be found." >> http://localhost:8080/projects/index.html?mode=interactive >> >> >> Mounted projects: >> >> SACS Test http://purl.org/dc/dcmitype/Text Admin User liying >> /projects/SACS/filesystem.xml 2005-07-01 text/xml Admin User SACS Test >> /simple/ >> /sample/ >> >> Sorry for questions like these, hopefully I'll catch up soon. >> >> Liying >> >> -----Original Message----- >> From: hyp...@li... >> [mailto:hyp...@li...] On Behalf Of >> Alex >> Vigdor >> Sent: Friday, July 01, 2005 11:50 AM >> To: 'Hypercontent-users' users >> Subject: Re: [Hypercontent-users] Newbies Questions >> >> Liying, >> Did you try to stop and restart the server? It sounds like it might >> >> be related to a bug that has been fixed since the beta2 release. >> Also, >> try adding a trailing slash to the path in your filesystem.xml if you >> still have problems. >> >> -Alex >> >> On Jul 1, 2005, at 11:27 AM, Liying Miao wrote: >> >>> Thanks so much Carl. >>> >>> I added a new project, chose argument to insert and set the path >>> repositories/project-repository/test in the index 0. I could see it's >>> added >>> and filesystem.xml is there, but when I type >>> http://localhost:8080/test, >>> says page not found. Then when I went back to projects index page >>> http://localhost:8080/projects, I got following error, and same error >>> occurs >>> when I even tried to edit sample project. Well, right before I got >>> these >>> errors, I did change the path from repositories/project-repository to >>> repositories/project-repository/test >>> >>> (here is what's in the filesystem.xml <argument index="0"/><argument >>> index="0" value="repositories/project-repository/test"/>) >>> >>> and change "test" from upper case to lower case letters. But that's >>> all I >>> did. >>> >>> There was an error processing your request >>> null >>> >>> org.hypercontent.project.FileOpener.<init>(FileOpener.java:34) >>> org.hypercontent.server.Session.getFileOpener(Session.java:153) >>> org.hypercontent.project.engine.Task.getFileOpener(Task.java:49) >>> org.hypercontent.server.Session.bindForm(Session.java:165) >>> org.hypercontent.project.engine.stage.FormBindingStage.process(FormBi >>> n >>> d >>> ingSt >>> age.java:60) >>> org.hypercontent.project.engine.Pipeline.process(Pipeline.java:308) >>> org.hypercontent.project.engine.Pipeline.process(Pipeline.java:282) >>> org.hypercontent.project.Project.getAsset(Project.java:542) >>> org.hypercontent.project.AssetRequest.getAsset(AssetRequest.java:150) >>> org.hypercontent.server.ContentServer.service(ContentServer.java:415) >>> org.hypercontent.servlet.CompositionServlet.doGet(CompositionServlet. >>> j >>> a >>> va:10 >>> 4) >>> javax.servlet.http.HttpServlet.service(HttpServlet.java:697) >>> javax.servlet.http.HttpServlet.service(HttpServlet.java:810) >>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl >>> i >>> c >>> ation >>> FilterChain.java:237) >>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF >>> i >>> l >>> terCh >>> ain.java:157) >>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV >>> a >>> l >>> ve.ja >>> va:214) >>> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv >>> e >>> C >>> ontex >>> t.java:104) >>> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav >>> a >>> : >>> 520) >>> org.apache.catalina.core.StandardContextValve.invokeInternal(Standard >>> C >>> o >>> ntext >>> Valve.java:198) >>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextV >>> a >>> l >>> ve.ja >>> va:152) >>> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv >>> e >>> C >>> ontex >>> t.java:104) >>> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav >>> a >>> : >>> 520) >>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j >>> a >>> v >>> a:137 >>> ) >>> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv >>> e >>> C >>> ontex >>> t.java:104) >>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j >>> a >>> v >>> a:117 >>> ) >>> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv >>> e >>> C >>> ontex >>> t.java:102) >>> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav >>> a >>> : >>> 520) >>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal >>> v >>> e >>> .java >>> :109) >>> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv >>> e >>> C >>> ontex >>> t.java:104) >>> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav >>> a >>> : >>> 520) >>> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) >>> org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java: >>> 160) >>> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java >>> : >>> 793) >>> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce >>> s >>> s >>> Conne >>> ction(Http11Protocol.java:702) >>> org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java >>> : >>> 571) >>> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP >>> o >>> o >>> l.jav >>> a:644) >>> java.lang.Thread.run(Thread.java:595) >>> >>> >>> -----Original Message----- >>> From: hyp...@li... >>> [mailto:hyp...@li...] On Behalf Of >>> Carl >>> Barrow >>> Sent: Friday, July 01, 2005 4:50 AM >>> To: 'Hypercontent-users' >>> Subject: Re: [Hypercontent-users] Newbies Questions >>> >>> Hi Lillian >>> >>> I'm still evaluating HC2.0 but I've been live with HC 1.4 here for >>> some >>> time. I'll do my best to answer your questions. Alex might want to >>> add >>> to what I've written later on, but hopefully this will help. >>> >>> Answers embedded below >>> >>> Many Thanks >>> Carl >>> >>> Liying Miao wrote: >>> >>>> Hi Experts, >>>> >>>> We are trying HC2.0 now to implement a test version of our >>>> university's website. We are still at the stage of understanding >>>> more >>>> of HC by playing with the sample project, modifying content. I know >>>> we >>>> can add items under News directory, but when we can't do certain >>>> things like adding a root menu item or changing the navigation to be >>>> a >>>> drop down list, we are stuck. >>>> >>>> I read the Hypercontent 1.4 Manual, and thanks, that was helpful in >>>> understanding the building blocks. However, I still don't know where >>>> to start. Here are the questions: >>>> >>>> 1. In order to meet our needs, do we modify the definitions in the >>>> sample project, or do we need a brand new project built? >>>> >>> From my experience you should always start a new project from >>> scratch. >>> Spend some time planning out the structure of your site, how your >>> template and navigation will work and getting your dtds correct from >>> the >>> start and this will make live much easier in the future. >>> >>>> 2. If we need to build project from scratch, then, >>>> >>>> . Do we create a test-repository folder under >>>> C:\hypercontent2.0b2\hypercontent2.0b2\hypercontent2 (same directory >>>> where sample-build and sample-repository exist) and leave webapp >>>> folder alone? >>>> >>> Yes, you'll need to create the directory for the repository. You >>> don't >>> need to do anything with the webapp directory. >>> >>>> . Do we first create Project Definition, filesystem, under >>>> >>> C: >>> \hypercontent2.0b2\hypercontent2.0b2\hypercontent2\repositories\boots >>> t >>> r >>> ap\ >>> config >>>> and projects? How do we define it if we don't have user.xml, >>>> index.xml, index.xsl, projet.xsl, etc created yet? >>>> >>> If you login to http://localhost:8080/projects/ as admin. >>> Add a new project by typing a name in the box and press enter. >>> Set the mount point, /newproject/ ( will be accessible at >>> http://localhost:8080/newproject) >>> Set the repository path, repositories/project-repository/newproject >>> login to your new site and you'll see the following directories >>> config/ >>> workflow/ >>> You will see nothing else since it's not defined in the project >>> definition at this point. >>> In config you will see project-definition.xml where you can now build >>> up >>> your project. Adding your XML doctypes, build, publish paths etc... >>> You can set up permissions in permissions.xml although thats not >>> something I've done since HC1.4 used the uPortal group/permissions >>> manager. >>> >>>> . What source can we borrow for the new project, what need to be >>>> modified and recompiled? >>>> >>> I'm not too sure what you meant by that, can you clarify >>> >>>> Thanks so much for helping me get started. slowly. >>>> >>>> Lillian Miao >>>> >>>> ERP/IT >>>> Florida A&M University >>>> (850) 412-7999 >>>> >>> >>> -- >>> ************************************ >>> >>> Carl Barrow >>> Web Developer >>> e-Services >>> The University of Hull >>> Cottingham Road >>> Hull >>> HU6 7RX >>> Ext. 6838 >>> >>> ************************************ >>> >>> >>> >>> ------------------------------------------------------- >>> SF.Net email is sponsored by: Discover Easy Linux Migration >>> Strategies >>> from IBM. Find simple to follow Roadmaps, straightforward articles, >>> informative Webcasts and more! Get everything you need to get up to >>> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click >>> _______________________________________________ >>> Hypercontent-users mailing list >>> Hyp...@li... >>> https://lists.sourceforge.net/lists/listinfo/hypercontent-users >>> >>> >>> >>> ------------------------------------------------------- >>> SF.Net email is sponsored by: Discover Easy Linux Migration >>> Strategies >>> from IBM. Find simple to follow Roadmaps, straightforward articles, >>> informative Webcasts and more! Get everything you need to get up to >>> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click >>> _______________________________________________ >>> Hypercontent-users mailing list >>> Hyp...@li... >>> https://lists.sourceforge.net/lists/listinfo/hypercontent-users >> >> >> >> ------------------------------------------------------- >> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies >> from IBM. Find simple to follow Roadmaps, straightforward articles, >> informative Webcasts and more! Get everything you need to get up to >> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click >> _______________________________________________ >> Hypercontent-users mailing list >> Hyp...@li... >> https://lists.sourceforge.net/lists/listinfo/hypercontent-users > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Hypercontent-users mailing list > Hyp...@li... > https://lists.sourceforge.net/lists/listinfo/hypercontent-users |
