You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(10) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
|
Feb
(13) |
Mar
(15) |
Apr
(29) |
May
(28) |
Jun
(111) |
Jul
(185) |
Aug
(366) |
Sep
(121) |
Oct
(73) |
Nov
(57) |
Dec
(23) |
2005 |
Jan
(30) |
Feb
(49) |
Mar
(51) |
Apr
(47) |
May
(95) |
Jun
(74) |
Jul
(62) |
Aug
(61) |
Sep
(46) |
Oct
(73) |
Nov
(111) |
Dec
(59) |
2006 |
Jan
(114) |
Feb
(34) |
Mar
(47) |
Apr
(49) |
May
(106) |
Jun
(47) |
Jul
(78) |
Aug
(31) |
Sep
(35) |
Oct
(39) |
Nov
(63) |
Dec
(17) |
2007 |
Jan
(40) |
Feb
(32) |
Mar
(17) |
Apr
(15) |
May
(28) |
Jun
(20) |
Jul
(80) |
Aug
(83) |
Sep
(52) |
Oct
(26) |
Nov
(6) |
Dec
(9) |
2008 |
Jan
(22) |
Feb
(11) |
Mar
(45) |
Apr
(5) |
May
(8) |
Jun
|
Jul
(16) |
Aug
(5) |
Sep
(3) |
Oct
(4) |
Nov
(14) |
Dec
(3) |
2009 |
Jan
(25) |
Feb
(46) |
Mar
(17) |
Apr
(8) |
May
(74) |
Jun
(48) |
Jul
(11) |
Aug
(9) |
Sep
|
Oct
|
Nov
(2) |
Dec
(2) |
From: Chris B. <ch...@ru...> - 2004-05-21 15:32:44
|
I'm developing a new content type. I have created my PDL, domain objects, loader, initializer, content type deployment descriptor, and whatnot, and "ant deploy" runs without errors. The documentation (rhea-dg-waf-en-6.1-1.pdf, section 8.10) suggests that I now run "ccm load --interactive <projectname>", which results in java.lang.IllegalArgumentException: no such context: class com.arsdigita.runtime.RuntimeConfig; available contexts=[class com.arsdigita.packaging.RegistryConfig]; context->storage map: {class com.arsdigita.packaging.RegistryConfig=registry.properties} at com.arsdigita.packaging.ConfigRegistry.getStorage(ConfigRegistry.java:208) at com.arsdigita.packaging.ConfigRegistry.load(ConfigRegistry.java:281) at com.arsdigita.packaging.ConfigRegistry.load(ConfigRegistry.java:252) at com.arsdigita.runtime.AbstractConfig.load(AbstractConfig.java:107) at com.arsdigita.runtime.AbstractConfig.load(AbstractConfig.java:131) at com.arsdigita.runtime.AbstractConfig.require(AbstractConfig.java:148) at com.arsdigita.runtime.RuntimeConfig.getConfig(RuntimeConfig.java:49) at com.arsdigita.core.DBCheck.run(DBCheck.java:107) at com.arsdigita.packaging.Load.run(Load.java:260) at com.arsdigita.packaging.MasterTool.main(MasterTool.java:91) This is on a virgin APLAWS+ installation on Fedora Core. "ccm start" works fine. Any ideas? Perhaps there's an alternative to "ccm load"? - I'm happy to write a SQL script to create and drop my tables. |
From: Shubham N. [ntl] <Shu...@nt...> - 2004-05-18 11:22:36
|
Hi Daniel With regards to this problem, we made the changes to the auth-http files and the Theme files are validated fine. However when we see them in Preview mode the Themes seem applied OK to sub sites whereas when we Validate and Publish files it still uses the default APLAWS Theme on the sub site (i.e. does not apply the new theme). Are we missing any basic step here. It seems pretty straightforward. There is even our theme folder in Themes-prod directory. Somehow no Themes are being displayed. Any clues or someone seen or fixed this behaviour ? Regards Shubham -----Original Message----- From: Daniel P. Berrange [mailto:ber...@re...] Sent: 14 May 2004 10:41 To: Shubham Nagar [ntl] Cc: apl...@li... Subject: Re: [Aplaws-devel] APLAWS Themes problems On Fri, May 14, 2004 at 10:09:52AM +0100, Shubham Nagar [ntl] wrote: > Hi All > > Has anyone noticed any issues while validating themes in APLAWS using the > Themes Admin interface ? When we try and validate a theme following error > occurs as enclosed in the file. Further investigation revealed that the > application is not able to form the URL to the themes-dev folder. Actually the problem here is that the APLAWS thtme contains XSL for some applications which are only part of the devel/demo/complete bundle - but not the standard bundle. Thus when validating the theme there will be missing files for a cople of imports (ie auth-http-index.xsl and simplesurvey-index.xsl). The solution is to just remove/comment out the xsl:import for the handful of troublesome files. Dan. > 2004-05-11 13:03:21,165 [080-3] ERROR listeners.LoggingErrorListener - Transformer ERROR: ; SystemID: http://dream:8080/resource/ROOT/__ccm__/themes-dev/arun-theme/auth-http-inde x.xsl; Line#: 7; Column#: -1: URL does not exist: http://dream:8080/resource/ccm-auth-http/__ccm__/apps/auth-http/xsl/index.xs l > ; SystemID: http://dream:8080/resource/ROOT/__ccm__/themes-dev/arun-theme/auth-http-inde x.xsl; Line#: 7; Column#: -1 > javax.xml.transform.TransformerException: URL does not exist: http://dream:8080/resource/ccm-auth-http/__ccm__/apps/auth-http/xsl/index.xs l > at com.arsdigita.templating.SimpleURIResolver.resolve(SimpleURIResolver.java:11 5) > at com.icl.saxon.style.XSLGeneralIncorporate.getIncludedStyleSheet(XSLGeneralIn corporate.java:83) -- |=- Daniel P. Berrange - ber...@re... -=| |=- Red Hat, 338 Euston Road, London, NW1 3BT. +44 (0)7977 267 243 -=| |=- -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| |
From: Shubham N. [ntl] <Shu...@nt...> - 2004-05-18 09:56:52
|
Hi Daniel You are right on the main reason for this problem. I am not sure on whether the recreation of database will help though since we have installed the database a few times to no avail. We deleted a duplicate record from the database which did the trick. We deleted the record from the table: public.cat_root_cat_object_map This removed the default Use Context. Then we used terms admin to map our new content section to Default like other applications mapped to Default. This worked. I think there is definitely some issue with more than root category mapped to same object in same use context. May be this happens only in case of Default use context. Regards Shubham -----Original Message----- From: Daniel P. Berrange [mailto:ber...@re...] Sent: 18 May 2004 10:39 To: Shubham Nagar [ntl] Cc: apl...@li... Subject: Re: [Aplaws-devel] APLAWS-NAV list not appearing in new content section On Mon, May 17, 2004 at 03:19:32PM +0100, Shubham Nagar [ntl] wrote: > Hi Daniel > > It crashed at the point of accessing our /newcontent section while clicking > on the Content Center. Here is the stack trace. We deleted the entry in the > 'public.cat_root_cat_object_map ' table to get rid of it. However, till date > we have not been able to map any Nav List to default context of the new > content section (/newcontent). That error message indicates that there is more than one root category mapped to the same object in the same use context. This should not be possible when using the Category.java APIs since they are careful to replace any existing mapping. You'll need to investigate what SQL is being run when youmap the extra category fromthe Terms admin pages. I'd also recreate you database from scratch to ensure its in a consistent state. Dan. -- |=- Red Hat, 338 Euston Road, London, NW1 3BT. +44 (0)7977 267 243 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| |
From: Daniel P. B. <ber...@re...> - 2004-05-18 09:43:39
|
On Mon, May 17, 2004 at 03:19:32PM +0100, Shubham Nagar [ntl] wrote: > Hi Daniel >=20 > It crashed at the point of accessing our /newcontent section while clicki= ng > on the Content Center. Here is the stack trace. We deleted the entry in t= he > 'public.cat_root_cat_object_map ' table to get rid of it. However, till d= ate > we have not been able to map any Nav List to default context of the new > content section (/newcontent). That error message indicates that there is more than one root category mapped to the same object in the same use context. This should not be possible when using the Category.java APIs since they are careful to replace any existing mapping. You'll need to investigate what SQL is being run when youmap the extra category fromthe Terms admin pages. I'd also recreate you database from scratch to ensure its in a consistent state. Dan. -- |=3D- Red Hat, 338 Euston Road, London, NW1 3BT. +44 (0)7977 267 243 -= =3D| |=3D- Perl modules: http://search.cpan.org/~danberr/ -= =3D| |=3D- Projects: http://freshmeat.net/~danielpb/ -= =3D| |=3D- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -= =3D|=20 |
From: Shubham N. [ntl] <Shu...@nt...> - 2004-05-17 14:18:32
|
Hi Daniel It crashed at the point of accessing our /newcontent section while clicking on the Content Center. Here is the stack trace. We deleted the entry in the 'public.cat_root_cat_object_map ' table to get rid of it. However, till date we have not been able to map any Nav List to default context of the new content section (/newcontent). -*-*-*- Section: Stack trace -*-*-*- java.lang.IllegalStateException: there is more than one root for object: [com.arsdigita.cms.ContentSection:{id=1100}] first root: [com.arsdigita.categorization.UseContext:{id=18001}] second root: [com.arsdigita.categorization.UseContext:{id=1103}] at com.arsdigita.categorization.Category.getRootForObject(Category.java:1716) at com.arsdigita.cms.ui.category.CategoryAdminPane$ContextSelectionListener.sta teChanged(CategoryAdminPane.java:310) at com.arsdigita.bebop.List.fireStateChanged(List.java:628) at com.arsdigita.bebop.List$2.stateChanged(List.java:576) at com.arsdigita.bebop.AbstractSingleSelectionModel.fireStateChanged(AbstractSi ngleSelectionModel.java:86) at com.arsdigita.cms.ui.category.CategoryAdminPane$UseContextSelectionModel.get SelectedKey(CategoryAdminPane.java:289) at com.arsdigita.cms.ui.category.CategoryAdminPane.getUseContext(CategoryAdminP ane.java:295) at com.arsdigita.cms.ui.category.CategoryAdminPane$RootListener.actionPerformed (CategoryAdminPane.java:270) at com.arsdigita.bebop.Page.fireActionEvent(Page.java:896) at com.arsdigita.bebop.Page.process(Page.java:720) at com.arsdigita.bebop.Page.process(Page.java:686) at com.arsdigita.bebop.Page.buildDocument(Page.java:758) at com.arsdigita.cms.dispatcher.CMSPage$1.excurse(CMSPage.java:281) at com.arsdigita.cms.CMSExcursion$1.excurse(CMSExcursion.java:80) at com.arsdigita.kernel.KernelExcursion.run(KernelExcursion.java:57) at com.arsdigita.cms.CMSExcursion.run(CMSExcursion.java:75) at com.arsdigita.cms.dispatcher.CMSPage.dispatch(CMSPage.java:296) at _packages._content_22dsection._www._admin._index__jsp._jspService(_index__js p.java:54) at com.caucho.jsp.JavaPage.service(JavaPage.java:75) at com.caucho.jsp.Page.subservice(Page.java:506) at com.caucho.server.http.FilterChainPage.doFilter(FilterChainPage.java:182) at com.caucho.server.http.Invocation.service(Invocation.java:315) at com.caucho.server.http.QRequestDispatcher.forward(QRequestDispatcher.java:22 2) at com.caucho.server.http.QRequestDispatcher.forward(QRequestDispatcher.java:10 3) at com.caucho.server.http.QRequestDispatcher.forward(QRequestDispatcher.java:80 ) at com.arsdigita.cms.ContentSectionServlet.doService(ContentSectionServlet.java :171) at com.arsdigita.web.BaseApplicationServlet$1.excurse(BaseApplicationServlet.ja va:111) at com.arsdigita.kernel.KernelExcursion.run(KernelExcursion.java:57) at com.arsdigita.web.BaseApplicationServlet.doService(BaseApplicationServlet.ja va:105) at com.arsdigita.web.BaseServlet$1.excurse(BaseServlet.java:176) at com.arsdigita.kernel.KernelExcursion.run(KernelExcursion.java:57) at com.arsdigita.web.BaseServlet.internalService(BaseServlet.java:147) at com.arsdigita.web.BaseServlet.doGet(BaseServlet.java:272) at javax.servlet.http.HttpServlet.service(HttpServlet.java:126) at javax.servlet.http.HttpServlet.service(HttpServlet.java:103) at com.caucho.server.http.FilterChainServlet.doFilter(FilterChainServlet.java:9 6) at com.caucho.server.http.Invocation.service(Invocation.java:315) at com.caucho.server.http.QRequestDispatcher.forward(QRequestDispatcher.java:22 2) at com.caucho.server.http.QRequestDispatcher.forward(QRequestDispatcher.java:10 3) at com.caucho.server.http.QRequestDispatcher.forward(QRequestDispatcher.java:80 ) at com.arsdigita.web.BaseDispatcher.forward(BaseDispatcher.java:206) at com.arsdigita.web.BaseDispatcher.forward(BaseDispatcher.java:190) at com.arsdigita.web.BaseDispatcher.dispatch(BaseDispatcher.java:130) at com.arsdigita.web.DispatcherServlet.doService(DispatcherServlet.java:123) at com.arsdigita.web.BaseServlet$1.excurse(BaseServlet.java:176) at com.arsdigita.kernel.KernelExcursion.run(KernelExcursion.java:57) at com.arsdigita.web.BaseServlet.internalService(BaseServlet.java:147) at com.arsdigita.web.BaseServlet.doGet(BaseServlet.java:272) at javax.servlet.http.HttpServlet.service(HttpServlet.java:126) at javax.servlet.http.HttpServlet.service(HttpServlet.java:103) at com.caucho.server.http.FilterChainServlet.doFilter(FilterChainServlet.java:9 6) at com.arsdigita.london.shortcuts.ShortcutFilter.doService(ShortcutFilter.java: 79) at com.arsdigita.web.BaseFilter.doFilter(BaseFilter.java:96) at com.caucho.server.http.FilterChainFilter.doFilter(FilterChainFilter.java:88) at com.arsdigita.london.subsite.SubsiteFilter.doService(SubsiteFilter.java:69) at com.arsdigita.web.BaseFilter.doFilter(BaseFilter.java:96) at com.caucho.server.http.FilterChainFilter.doFilter(FilterChainFilter.java:88) at com.caucho.server.http.Invocation.service(Invocation.java:315) at com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:246) at com.caucho.server.http.HttpRequest.handleConnection(HttpRequest.java:164) at com.caucho.server.TcpConnection.run(TcpConnection.java:139) at java.lang.Thread.run(Thread.java:536) -----Original Message----- From: Daniel P. Berrange [mailto:ber...@re...] Sent: 17 May 2004 15:08 To: Shubham Nagar [ntl] Cc: apl...@li... Subject: Re: [Aplaws-devel] APLAWS-NAV list not appearing in new content section On Mon, May 17, 2004 at 03:03:55PM +0100, Shubham Nagar [ntl] wrote: > Hi Daniel > > We have tried that but when we map the URL of our new content section (Say > /newcontent ) in APLAWS NAVIGATION LIST using the Default Use Context, the > application crashes when we try and access our new content section. At what point did it crash & what was the error message ? Dan -- |=- Red Hat, 338 Euston Road, London, NW1 3BT. +44 (0)7977 267 243 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| |
From: Daniel P. B. <ber...@re...> - 2004-05-17 14:11:57
|
On Mon, May 17, 2004 at 03:03:55PM +0100, Shubham Nagar [ntl] wrote: > Hi Daniel >=20 > We have tried that but when we map the URL of our new content section (Say > /newcontent ) in APLAWS NAVIGATION LIST using the Default Use Context, the > application crashes when we try and access our new content section. At what point did it crash & what was the error message ? Dan --=20 |=3D- Red Hat, 338 Euston Road, London, NW1 3BT. +44 (0)7977 267 243 -= =3D| |=3D- Perl modules: http://search.cpan.org/~danberr/ -= =3D| |=3D- Projects: http://freshmeat.net/~danielpb/ -= =3D| |=3D- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -= =3D|=20 |
From: Shubham N. [ntl] <Shu...@nt...> - 2004-05-17 14:02:58
|
Hi Daniel We have tried that but when we map the URL of our new content section (Say /newcontent ) in APLAWS NAVIGATION LIST using the Default Use Context, the application crashes when we try and access our new content section. On the other hand, if we map the domain to another Use Context (MyNewContext) and then publish content, the content is always published in the Default context instead of the Category List mapped in MyNewContext. How can one add the APLAWS NAV List into a /newcontent (new content section) so that it appears in the <default> Use Context automatically (This behaviour is shown by default install) Regards Shubham -----Original Message----- From: Daniel P. Berrange [mailto:ber...@re...] Sent: 17 May 2004 14:44 To: Shubham Nagar [ntl] Cc: apl...@li... Subject: Re: [Aplaws-devel] APLAWS-NAV list not appearing in new content section On Mon, May 17, 2004 at 02:39:45PM +0100, Shubham Nagar [ntl] wrote: > Hi All > > We are created a new content section by modifying the enterprise.init file, > but we are having problems populating the default Use Context with APLAWS > Navigation List. Is there a documented method to do so. We had simply > modified the enterprise.init file with a new Section initializer as depicted > in the documentation from Red Hat/APLAWS but the navigational list does not > appear. You'venot associated any category trees wit your new content section. To do this go to the Terms administration UI at /ccm/admin/terms. Each tree that you wish to appear in the assign categories step, must be mapped into the URL for you new section. In addition to the Nav list you'll need the various ESD toolkit lists otherwise you'll mis out on the metadata facilities of APLAWS+. Dan. -- |=- Red Hat, 338 Euston Road, London, NW1 3BT. +44 (0)7977 267 243 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| |
From: Daniel P. B. <ber...@re...> - 2004-05-17 13:48:21
|
On Mon, May 17, 2004 at 02:39:45PM +0100, Shubham Nagar [ntl] wrote: > Hi All >=20 > We are created a new content section by modifying the enterprise.init fil= e, > but we are having problems populating the default Use Context with APLAWS > Navigation List. Is there a documented method to do so. We had simply > modified the enterprise.init file with a new Section initializer as depic= ted > in the documentation from Red Hat/APLAWS but the navigational list does n= ot > appear. You'venot associated any category trees wit your new content section. To do this go to the Terms administration UI at /ccm/admin/terms.=20 Each tree that you wish to appear in the assign categories step, must be mapped into the URL for you new section. In addition to the Nav list you'll need the various ESD toolkit lists otherwise you'll mis out on the metadata facilities of APLAWS+. Dan. --=20 |=3D- Red Hat, 338 Euston Road, London, NW1 3BT. +44 (0)7977 267 243 -= =3D| |=3D- Perl modules: http://search.cpan.org/~danberr/ -= =3D| |=3D- Projects: http://freshmeat.net/~danielpb/ -= =3D| |=3D- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -= =3D|=20 |
From: Shubham N. [ntl] <Shu...@nt...> - 2004-05-17 13:39:14
|
Hi All We are created a new content section by modifying the enterprise.init file, but we are having problems populating the default Use Context with APLAWS Navigation List. Is there a documented method to do so. We had simply modified the enterprise.init file with a new Section initializer as depicted in the documentation from Red Hat/APLAWS but the navigational list does not appear. Any clues from any one ? Regards Shubham |
From: Shubham N. [ntl] <Shu...@nt...> - 2004-05-14 09:58:27
|
Thanks again for a quick response Daniel, So the fix we did is what we really need to do to circumvent it. Fine about that. Also, has anyone come across the fact that Themes applied on Sub sites appear ok in Preview but are actually not published on the sub site. It seems it always takes the theme specified in: com.arsdigita.london.theme.default_theme_path even for sub sites. To use themes for subsites then do we need a separate JVM instance for each sub site so that the above default parameter can be set for each sub site ? For some reason we can not publish themes on a sub site. We are trying to understand whether others in the community have come across this and what could be the reason. Regards Shubham -----Original Message----- From: Daniel P. Berrange [mailto:ber...@re...] Sent: 14 May 2004 10:41 To: Shubham Nagar [ntl] Cc: apl...@li... Subject: Re: [Aplaws-devel] APLAWS Themes problems On Fri, May 14, 2004 at 10:09:52AM +0100, Shubham Nagar [ntl] wrote: > Hi All > > Has anyone noticed any issues while validating themes in APLAWS using the > Themes Admin interface ? When we try and validate a theme following error > occurs as enclosed in the file. Further investigation revealed that the > application is not able to form the URL to the themes-dev folder. Actually the problem here is that the APLAWS thtme contains XSL for some applications which are only part of the devel/demo/complete bundle - but not the standard bundle. Thus when validating the theme there will be missing files for a cople of imports (ie auth-http-index.xsl and simplesurvey-index.xsl). The solution is to just remove/comment out the xsl:import for the handful of troublesome files. Dan. > 2004-05-11 13:03:21,165 [080-3] ERROR listeners.LoggingErrorListener - Transformer ERROR: ; SystemID: http://dream:8080/resource/ROOT/__ccm__/themes-dev/arun-theme/auth-http-inde x.xsl; Line#: 7; Column#: -1: URL does not exist: http://dream:8080/resource/ccm-auth-http/__ccm__/apps/auth-http/xsl/index.xs l > ; SystemID: http://dream:8080/resource/ROOT/__ccm__/themes-dev/arun-theme/auth-http-inde x.xsl; Line#: 7; Column#: -1 > javax.xml.transform.TransformerException: URL does not exist: http://dream:8080/resource/ccm-auth-http/__ccm__/apps/auth-http/xsl/index.xs l > at com.arsdigita.templating.SimpleURIResolver.resolve(SimpleURIResolver.java:11 5) > at com.icl.saxon.style.XSLGeneralIncorporate.getIncludedStyleSheet(XSLGeneralIn corporate.java:83) -- |=- Daniel P. Berrange - ber...@re... -=| |=- Red Hat, 338 Euston Road, London, NW1 3BT. +44 (0)7977 267 243 -=| |=- -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| |
From: Daniel P. B. <ber...@re...> - 2004-05-14 09:44:46
|
On Fri, May 14, 2004 at 10:09:52AM +0100, Shubham Nagar [ntl] wrote: > Hi All >=20 > Has anyone noticed any issues while validating themes in APLAWS using the > Themes Admin interface ? When we try and validate a theme following error > occurs as enclosed in the file. Further investigation revealed that the > application is not able to form the URL to the themes-dev folder. Actually the problem here is that the APLAWS thtme contains XSL for some applications which are only part of the devel/demo/complete bundle - but not the standard bundle. Thus when validating the theme there will be missing files for a cople of imports (ie auth-http-index.xsl and simplesurvey-index.xsl). The solution is to just remove/comment out the xsl:import for the handful of troublesome files. Dan. > 2004-05-11 13:03:21,165 [080-3] ERROR listeners.LoggingErrorListener - Tr= ansformer ERROR: ; SystemID: http://dream:8080/resource/ROOT/__ccm__/themes= -dev/arun-theme/auth-http-index.xsl; Line#: 7; Column#: -1: URL does not ex= ist: http://dream:8080/resource/ccm-auth-http/__ccm__/apps/auth-http/xsl/in= dex.xsl > ; SystemID: http://dream:8080/resource/ROOT/__ccm__/themes-dev/arun-theme= /auth-http-index.xsl; Line#: 7; Column#: -1 > javax.xml.transform.TransformerException: URL does not exist: http://drea= m:8080/resource/ccm-auth-http/__ccm__/apps/auth-http/xsl/index.xsl > at com.arsdigita.templating.SimpleURIResolver.resolve(SimpleURIRe= solver.java:115) > at com.icl.saxon.style.XSLGeneralIncorporate.getIncludedStyleShee= t(XSLGeneralIncorporate.java:83) --=20 |=3D- Daniel P. Berrange - ber...@re... -= =3D| |=3D- Red Hat, 338 Euston Road, London, NW1 3BT. +44 (0)7977 267 243 -= =3D| |=3D- -= =3D| |=3D- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -= =3D|=20 |
From: Shubham N. [ntl] <Shu...@nt...> - 2004-05-14 09:09:02
|
Hi All Has anyone noticed any issues while validating themes in APLAWS using the Themes Admin interface ? When we try and validate a theme following error occurs as enclosed in the file. Further investigation revealed that the application is not able to form the URL to the themes-dev folder. We then resolved the problem by creating soft links to the themes-dev directory , but now we can see themes being applied in the preview but not on the published site. It seems that Themes are applied ever only to the default themes path set in WAF parameters but not subsites. Does this mean that each subsite should run in a separate JVM environment ? Regards Shubham |
From: Chris B. <ch...@ru...> - 2004-04-29 08:24:28
|
Daniel P. Berrange wrote: > > > There are some XML Schemas included with APLAWS but all the generic > > > content is for another content type 'ESDService', which doesn't have a > > > schema. The schemas are located in this directory in the source bundl= e: > > >=20 > > > ./aplaws-plus-1.0.0-1-src/ccm-ldn-aplaws-1.9.1/aplaws/doc/ct-schemas >=20 > Its worth noting that the primary purpose of these schemas is=20 > for standardizing import / export format for APLAWS CMS. They > are specifically not intended for people who author original > content, since there are a number of technical constraints in > these files that authors really don't want to be worrying about.=20 There also exist several .xsd files in the aplaws-plus-1.0.0-1-src/ccm-ldn-aplaws-1.9.1/aplaws/doc/app-schemas directory. It should be noted that it would not be possible to use these schemata to validate submitted or generated XML content, as several of them are not well-formed XML, and/or do not correspond to the published schema for XML Schema. What is the intended purpose of these files? |
From: Daniel P. B. <ber...@re...> - 2004-04-28 16:23:20
|
On Fri, Apr 23, 2004 at 04:00:22PM +0100, Miles Barr wrote: > On Fri, 2004-04-23 at 14:08, Miles Barr wrote: > > > > > Also where are the DTDs/XML Schemas that the content must follow = and the > > > > > one for the folder definition file? > > > >=20 > > > > I'm not sure about the DTDs etc. :( There is a class com.arsdigita.aplaws.ObjectTypeSchemaGenerator which is capable of auto-generating an XML schema which maps to the format produced by DomainObjectXMLRenderer. Unfortunately=20 I didn't get time to complete the command line tool to actually invoke the methods in this class (I had previously used a quick JSP file hack, but I've mislaid that file). It needs to be initialized=20 with a set of traversal rules which match those used to initialize the DOXR. > > There are some XML Schemas included with APLAWS but all the generic > > content is for another content type 'ESDService', which doesn't have a > > schema. The schemas are located in this directory in the source bundle: > >=20 > > ./aplaws-plus-1.0.0-1-src/ccm-ldn-aplaws-1.9.1/aplaws/doc/ct-schemas Its worth noting that the primary purpose of these schemas is=20 for standardizing import / export format for APLAWS CMS. They are specifically not intended for people who author original content, since there are a number of technical constraints in these files that authors really don't want to be worrying about.=20 This is why the master files for the generic content follow an official governement service content interchange format, which is that translated in the APLAWS import format automatically. For APLAWS+, if the 'ccm-ldn-exporter' application is installed then you get an additional command line tool called=20 c.a.london.exporter.ItemExportTool that can export from an existing CMS in the correct format.=20 > >From reading through the code it looks like the numbers don't actually > correspond to the object ID in the database (although they probably > originally did on someone's machine). Can anyone who's done an import > verify this? i.e. did you require a blank APLAWS installation? The import tool maintains a mapping of OIDs so that it can avoid importing the same object multiple times. The mapping is actually a triplet of system id, original OID and new OID. The system id is typically the hostname of the CMS containing the original content. The 'id' part of the original OID is a number that should be unique within the scope of the 'system id'. If the original system was not an APLAWS CMS, then the actual numbers in the 'original OID' can basically just be=20 made up - provided they are all unique of course - for the generic contet we just made up original OIDs based on the PID number. Dan. --=20 |=3D- Daniel P. Berrange - ber...@re... -= =3D| |=3D- Red Hat, 338 Euston Road, London, NW1 3BT. +44 (0)7977 267 243 -= =3D| |=3D- -= =3D| |=3D- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -= =3D|=20 |
From: Shubham N. [ntl] <Shu...@nt...> - 2004-04-26 10:55:06
|
Hi All I am planning to add a new content section within APLAWS. However, from documentation it was not clear how exactly this can be done. I edited the enterprise.init file as a test and then updated the ccm-cms Jar files, Restarted the servlet container but that did not result in any new content section appearing. Loading ccm-cms package again also did not result in any new content section appearing. Has anyone tried this before ? Regards Shubham |
From: Miles B. <mi...@ru...> - 2004-04-23 14:59:58
|
On Fri, 2004-04-23 at 14:08, Miles Barr wrote: > > > > Also where are the DTDs/XML Schemas that the content must follow and the > > > > one for the folder definition file? > > > > > > I'm not sure about the DTDs etc. :( > > > > I'll keep digging around and post here if I find anything. > > There are some XML Schemas included with APLAWS but all the generic > content is for another content type 'ESDService', which doesn't have a > schema. The schemas are located in this directory in the source bundle: > > ./aplaws-plus-1.0.0-1-src/ccm-ldn-aplaws-1.9.1/aplaws/doc/ct-schemas It looks like the XML schemas for the existing content types can be used, just changing the top level element from 'object' to 'item'. The problem now is getting existing content into the correct XML. This is fairly straightforward except for composite parts, e.g. images, text assets, dublin core metadata, etc. Each of these need to specify the Java domain object it uses. And if it has external files they need to synchronize on an ID. >From reading through the code it looks like the numbers don't actually correspond to the object ID in the database (although they probably originally did on someone's machine). Can anyone who's done an import verify this? i.e. did you require a blank APLAWS installation? -- Miles Barr <mi...@ru...> Runtime Collective Ltd. |
From: Etherington, S. <ste...@ca...> - 2004-04-23 14:51:18
|
I got a server 500 and an exception reporting Signature.class. In response I have carried out the measures that Dan suggests. Although this seems to get me past the particular problem I was having I am still getting RDBMSEngine related exceptions (eg, one reports ORA-00936). Do I need to drop the schema and reload the applications? Or something? thanks Steve -----Original Message----- From: apl...@li... [mailto:apl...@li...]On Behalf Of Shubham Nagar [ntl] Sent: 20 April 2004 11:10 To: Daniel P. Berrange Cc: apl...@li... Subject: RE: [Aplaws-devel] Error while running APLAWS Great Daniel !!! It worked !!!. Thanks for this input. Will this fix be provided in the upgraded releases of APLAWS or is this a special caveat operation one would need to do for Oracle. I agree, that its really stupid feature within Oracle. Can an upgrade to latest Oracle Patch solve the problem you think ? We are running Oracle 9.2.0.1. I must also mention here that we also recieved initialization errors while installing. These are related to INSO filter tests failing. Has anyone come across these ? We were planning to upgrade our Oracle and then see whether these errors disappear, but thout it worthwhile to mention to the community on whether anyone else has recieved the same problems... Regards Shubham -----Original Message----- From: Daniel P. Berrange [mailto:ber...@re...] Sent: 19 April 2004 23:53 To: Shubham Nagar [ntl] Cc: apl...@li... Subject: Re: [Aplaws-devel] Error while running APLAWS Unfortunately this is a bug that crept into persistence when running on Oracle. Identifiers in Oracle are limited to 31 characters, and in some circumstances the generated queries exceeded this limit. See https://bugzilla.redhat.com/119466 To get around this problem, you'll need an updated copy of the clas file com/redhat/persistence/Signature.class which I've put up at http://people.redhat.com/berrange/aplaws-plus/ You'll need to modify the file /usr/share/java/ccm-core-6.1.0.jar and replace the Signature.class, then re-run 'ccm hostinit-bundle' with same argments as before, but also appending '--clean'. NB, PostgreSQL is unaffected by this bug since it doesn't have such stupidly small limits as Oracle. Dan. On Mon, Apr 19, 2004 at 12:50:06PM +0100, Shubham Nagar [ntl] wrote: > Hi All > > > > We have set up APLAWS + Release 1 fine but while navigating from the Top > Level links (Business.. etc) the navigation fails with an error report. The > content center works ok. From the onset looks something elementary to me.... > > > > Environment: > > > > Redhat Enterprise Linux ES > > Oracle9i Enterprise Edition Release 9.2.0.1.0 > > Java - java version "1.4.1_05" > > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01) > > Java HotSpot(TM) Client VM (build 1.4.1_05-b01, mixed mode) > > > > Any clues ? > > > > The error we recieve in the stack trace is: > > =========================================== > > > > 2004-04-19 11:04:18,460 [080-1] FATAL logging.ErrorReport - > > -*-*-*-*-*- Begin Error Report -*-*-*-*-*- > > -*-*-*- ACS Error Report Code: localhost:3a30f3:fc0239269b -*-*-*- > > -*-*-*- Message 1: com.arsdigita.persistence.PersistenceException: null > (root cause: ORA-00972: identifier is too long > > ) -*-*-*- > > -*-*-*- Message 2: com.redhat.persistence.engine.rdbms.RDBMSEngine$4: > ORA-00972: identifier is too long > > -*-*-*- > > > > -*-*-*- Section: CCM User -*-*-*- > > Party not logged in > > > > -*-*-*- Section: System properties -*-*-*- > > ccm.conf: /usr/share/ccm/conf/registry > > ccm.home: /usr/share/ccm > > com.arsdigita.london.navigation.DefaultContentSection: /content/ > > com.arsdigita.util.Assert.enabled: true > > file.encoding: ISO-8859-1 > > file.encoding.pkg: sun.io > > file.separator: / > > java.awt.graphicsenv: sun.awt.X11GraphicsEnvironment > > java.awt.printerjob: sun.print.PSPrinterJob > > java.class.path: > /opt/j2sdk1.4.1_05/jre/lib/jce.jar:/opt/j2sdk1.4.1_05/jre/lib/ext/sunjce_pro > vider.jar:/data/oracle/jdbc/lib/classes12.jar:/opt/j2sdk1.4.1_05/lib/tools.j > ar:/data/resin-2.1.12/lib/resin.jar:/data/resin-2.1.12/lib/jdbc2_0-stdext.ja > r:/data/resin-2.1.12/lib/jta_101.jar:/data/resin-2.1.12/lib/jndi.jar:/data/r > esin-2.1.12/lib/dom.jar:/data/resin-2.1.12/lib/sax.jar:/data/resin-2.1.12/li > b/jaxp.jar:/data/resin-2.1.12/lib/jmx.jar:/data/resin-2.1.12/lib/webutil.jar > :/data/resin-2.1.12/lib/jdbc-mysql.jar:/data/resin-2.1.12/lib/jaxp_parser_im > pl.jar:/data/resin-2.1.12/lib/jaxp_transform_impl.jar:/data/resin-2.1.12/lib > /jtidy-1.0.jar:/data/resin-2.1.12/lib/servlet.jar:/data/resin-2.1.12/lib/xal > an-j2-2.4.jar:/data/resin-2.1.12/lib/xerces-j2-2.0.2.jar:/data/resin-2.1.12/ > lib/xml-commons-apis-1.0.jar:/opt/j2sdk1.4.1_05/lib/tools.jar:/opt/j2sdk1.4. > 1_05/jre/lib/rt.jar:/data/resin-2.1.12/lib/jsdk23.jar > > java.class.version: 48.0 > > java.endorsed.dirs: /opt/j2sdk1.4.1_05/jre/lib/endorsed > > java.ext.dirs: > /opt/j2sdk1.4.1_05/jre/lib/ext:/opt/j2sdk1.4.1_05/lib/ext:/usr/share/ccm/web > apps/WEB-INF/system:/usr/share/ccm-tools/lib/security > > java.home: /opt/j2sdk1.4.1_05/jre > > java.io.tmpdir: /tmp > > java.library.path: > /opt/j2sdk1.4.1_05/jre/lib/i386/client:/opt/j2sdk1.4.1_05/jre/lib/i386:/opt/ > j2sdk1.4.1_05/jre/../lib/i386:/data/oracle/lib:/data/oracle/ctx/lib:/data/re > sin-2.1.12/libexec > > java.naming.factory.initial: com.caucho.naming.InitialContextFactoryImpl > > java.naming.factory.url.pkgs: com.caucho.naming > > java.runtime.name: Java(TM) 2 Runtime Environment, Standard Edition > > java.runtime.version: 1.4.1_05-b01 > > java.specification.name: Java Platform API Specification > > java.specification.vendor: Sun Microsystems Inc. > > java.specification.version: 1.4 > > java.util.prefs.PreferencesFactory: > java.util.prefs.FileSystemPreferencesFactory > > java.vendor: Sun Microsystems Inc. > > java.vendor.url: http://java.sun.com/ > > java.vendor.url.bug: http://java.sun.com/cgi-bin/bugreport.cgi > > java.version: 1.4.1_05 > > java.vm.info: mixed mode > > java.vm.name: Java HotSpot(TM) Client VM > > java.vm.specification.name: Java Virtual Machine Specification > > java.vm.specification.vendor: Sun Microsystems Inc. > > java.vm.specification.version: 1.0 > > java.vm.vendor: Sun Microsystems Inc. > > java.vm.version: 1.4.1_05-b01 > > javax.xml.parsers.DocumentBuilderFactory: > org.apache.xerces.jaxp.DocumentBuilderFactoryImpl > > javax.xml.parsers.SAXParserFactory: > org.apache.xerces.jaxp.SAXParserFactoryImpl > > javax.xml.transform.TransformerFactory: > com.icl.saxon.TransformerFactoryImpl > > line.separator: > > > > log4j.configuration: file:///usr/share/ccm/conf/log4j.properties > > org.xml.sax.driver: com.caucho.xml.Xml > > os.arch: i386 > > os.name: Linux > > os.version: 2.4.9-e.34smp > > path.separator: : > > resin.home: /usr/share/ccm > > sun.arch.data.model: 32 > > sun.boot.class.path: > /opt/j2sdk1.4.1_05/jre/lib/rt.jar:/opt/j2sdk1.4.1_05/jre/lib/i18n.jar:/opt/j > 2sdk1.4.1_05/jre/lib/sunrsasign.jar:/opt/j2sdk1.4.1_05/jre/lib/jsse.jar:/opt > /j2sdk1.4.1_05/jre/lib/jce.jar:/opt/j2sdk1.4.1_05/jre/lib/charsets.jar:/opt/ > j2sdk1.4.1_05/jre/classes > > sun.boot.library.path: /opt/j2sdk1.4.1_05/jre/lib/i386 > > sun.cpu.endian: little > > sun.cpu.isalist: > > sun.io.unicode.encoding: UnicodeLittle > > sun.java2d.fontpath: > > sun.os.patch.level: unknown > > user.country: GB > > user.dir: /usr/share/ccm > > user.home: /var/www > > user.language: en > > user.name: servlet > > user.timezone: Europe/London > > > > -*-*-*- Section: Stack trace -*-*-*- > > com.redhat.persistence.engine.rdbms.RDBMSEngine$4: ORA-00972: identifier > is too long > > > > at > com.redhat.persistence.engine.rdbms.RDBMSEngine.execute(RDBMSEngine.java:517 > ) > > at > com.redhat.persistence.engine.rdbms.RDBMSEngine.execute(RDBMSEngine.java:431 > ) > > at > com.redhat.persistence.engine.rdbms.RDBMSEngine.execute(RDBMSEngine.java:265 > ) > > at com.redhat.persistence.Cursor.execute(Cursor.java:131) > > at com.redhat.persistence.Cursor.next(Cursor.java:115) > > at com.arsdigita.persistence.DataQueryImpl.next(DataQueryImpl.java:646) > > at com.arsdigita.london.navigation.Template.matchBest(Template.java:188) > > at > com.arsdigita.london.navigation.NavigationFileResolver.resolveTemplate(Navig > ationFileResolver.java:141) > > at > com.arsdigita.london.navigation.NavigationFileResolver.resolve(NavigationFil > eResolver.java:118) > > at > com.arsdigita.web.ApplicationFileServlet.doService(ApplicationFileServlet.ja > va:132) > > at > com.arsdigita.web.BaseApplicationServlet$1.excurse(BaseApplicationServlet.ja > va:111) > > at com.arsdigita.kernel.KernelExcursion.run(KernelExcursion.java:57) > > at > com.arsdigita.web.BaseApplicationServlet.doService(BaseApplicationServlet.ja > va:105) > > at com.arsdigita.web.BaseServlet$1.excurse(BaseServlet.java:176) > > at com.arsdigita.kernel.KernelExcursion.run(KernelExcursion.java:57) > > at com.arsdigita.web.BaseServlet.internalService(BaseServlet.java:147) > > at com.arsdigita.web.BaseServlet.doGet(BaseServlet.java:272) > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > > at > com.caucho.server.http.FilterChainServlet.doFilter(FilterChainServlet.java:9 > 6) > > at com.caucho.server.http.Invocation.service(Invocation.java:315) > > at > com.caucho.server.http.QRequestDispatcher.forward(QRequestDispatcher.java:22 > 2) > > at > com.caucho.server.http.QRequestDispatcher.forward(QRequestDispatcher.java:10 > 3) > > at > com.caucho.server.http.QRequestDispatcher.forward(QRequestDispatcher.java:80 > ) > > at com.arsdigita.web.BaseDispatcher.forward(BaseDispatcher.java:206) > > at com.arsdigita.web.BaseDispatcher.forward(BaseDispatcher.java:190) > > at com.arsdigita.web.BaseDispatcher.dispatch(BaseDispatcher.java:130) > > at > com.arsdigita.web.DispatcherServlet.doService(DispatcherServlet.java:123) > > at com.arsdigita.web.BaseServlet$1.excurse(BaseServlet.java:176) > > at com.arsdigita.kernel.KernelExcursion.run(KernelExcursion.java:57) > > at com.arsdigita.web.BaseServlet.internalService(BaseServlet.java:147) > > at com.arsdigita.web.BaseServlet.doGet(BaseServlet.java:272) > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > > at > com.caucho.server.http.FilterChainServlet.doFilter(FilterChainServlet.java:9 > 6) > > at > com.arsdigita.london.shortcuts.ShortcutFilter.doService(ShortcutFilter.java: > 79) > > at com.arsdigita.web.BaseFilter.doFilter(BaseFilter.java:96) > > at > com.caucho.server.http.FilterChainFilter.doFilter(FilterChainFilter.java:88) > > at > com.arsdigita.london.subsite.SubsiteFilter.doService(SubsiteFilter.java:69) > > at com.arsdigita.web.BaseFilter.doFilter(BaseFilter.java:96) > > at > com.caucho.server.http.FilterChainFilter.doFilter(FilterChainFilter.java:88) > > at com.caucho.server.http.Invocation.service(Invocation.java:315) > > at com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:246) > > at > com.caucho.server.http.HttpRequest.handleConnection(HttpRequest.java:164) > > at com.caucho.server.TcpConnection.run(TcpConnection.java:139) > > at java.lang.Thread.run(Thread.java:536) > > > > > > -*-*-*- Section: HTTP headers -*-*-*- > > Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, > application/vnd.ms-powerpoint, application/vnd.ms-excel, application/msword, > */* > > Accept-Language: en-gb > > Connection: keep-alive > > Cookie: JSESSIONID=aioWO1FqHmje > > Host: ciaplaws1-win:8080 > > Referer: http://ciaplaws1-win:8080/ccm/portal/ > > User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0) > > Via: 1.0 mast-dc0-sp07 (NetCache NetApp/5.3.1) > > X-Forwarded-For: 10.116.1.3 > > > > -*-*-*- Section: Servlet attributes -*-*-*- > > class com.arsdigita.london.navigation.NavigationFileResolver.categoryPath: > [Lcom.arsdigita.categorization.Category;@154fd7a > > com.arsdigita.dispatcher.RequestContext: > com.arsdigita.sitenode.SiteNodeRequestContext@c20307 > > com.arsdigita.dispatcher.RequestValue: > {com.arsdigita.dispatcher.RequestValue@7958ef=null} > > com.arsdigita.web.BaseApplicationServlet.application_id: 192 > > com.arsdigita.web.BaseDispatcher.dispatched: true > > com.arsdigita.web.BaseServlet.request_url: /ccm/navigation/business/ > > > > -*-*-*- Section: Request summary -*-*-*- > > Context path: > > Request URI: /ccm/navigation/business/ > > Query string: null > > Method: GET > > Remote user: null > > > > -*-*-*- Section: Cookies -*-*-*- > > JSESSIONID: aioWO1FqHmje (expires: -1) > > -*-*-*-*-*- End Error Report -*-*-*-*-*- > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Aplaws-devel mailing list > Apl...@li... > https://lists.sourceforge.net/lists/listinfo/aplaws-devel -- |=- Daniel P. Berrange - ber...@re... -=| |=- Red Hat, 338 Euston Road, London, NW1 3BT. +44 (0)7977 267 243 -=| |=- -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| |
From: Steve C. <st...@ru...> - 2004-04-23 13:09:27
|
Hi What would be involved in porting APLAWS Plus to a new database, specifically SQL Server? Would it be a question of writing a lot of new SQL? Or is it more a question of writing Java code to generate code for that database (or generically, data store) from PDL? Is PDL completely database neutral? And has anyone done any work in this area? Thanks in advance Steve http://www.runtime-collective.com t: 01273 234290 f: 01273 234291 m: 0789 984 1684 |
From: Miles B. <mi...@ru...> - 2004-04-23 13:07:42
|
> > > Also where are the DTDs/XML Schemas that the content must follow and the > > > one for the folder definition file? > > > > I'm not sure about the DTDs etc. :( > > I'll keep digging around and post here if I find anything. There are some XML Schemas included with APLAWS but all the generic content is for another content type 'ESDService', which doesn't have a schema. The schemas are located in this directory in the source bundle: ./aplaws-plus-1.0.0-1-src/ccm-ldn-aplaws-1.9.1/aplaws/doc/ct-schemas Based on them, I guess the ESDService schema should be: <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" targetNamespace="http://www.arsdigita.com/cms/1.0"> <xs:element name="item"> <xs:complexType> <xs:sequence> <xs:element name="name" type="xs:string"/> <xs:element minOccurs="0" name="language" type="xs:string"/> <xs:element minOccurs="0" name="title" type="xs:string"/> <xs:element minOccurs="0" name="dublinCore"> <xs:complexType> <xs:sequence> <xs:element name="name" type="xs:string"/> <xs:element minOccurs="0" name="dcAudience" type="xs:string"/> <xs:element minOccurs="0" name="dcContributor" type="xs:string"/> <xs:element minOccurs="0" name="dcCoverage" type="xs:string"/> <xs:element minOccurs="0" name="dcCoveragePostcode" type="xs:string"/> <xs:element minOccurs="0" name="dcCoverageSpatialRef" type="xs:string"/> <xs:element minOccurs="0" name="dcCoverageUnit" type="xs:string"/> <xs:element minOccurs="0" name="dcDateValid" type="xs:string"/> <xs:element minOccurs="0" name="dcDisposalReview" type="xs:string"/> <xs:element minOccurs="0" name="dcLanguage" type="xs:string"/> <xs:element minOccurs="0" name="dcTemporalBegin" type="xs:string"/> <xs:element minOccurs="0" name="dcTemporalEnd" type="xs:string"/> <xs:element minOccurs="0" name="dcCreatorOwner" type="xs:string"/> <xs:element minOccurs="0" name="dcCreatorContact" type="xs:string"/> <xs:element minOccurs="0" name="dcDescription" type="xs:string"/> <xs:element minOccurs="0" name="dcIdentifier" type="xs:string"/> <xs:element minOccurs="0" name="dcPreservation" type="xs:string"/> <xs:element minOccurs="0" name="dcPublisher" type="xs:string"/> <xs:element minOccurs="0" name="dcRelation" type="xs:string"/> <xs:element minOccurs="0" name="dcRights" type="xs:string"/> <xs:element minOccurs="0" name="dcSource" type="xs:string"/> <xs:element minOccurs="0" name="dcKeywords" type="xs:string"/> </xs:sequence> <xs:attribute name="oid" type="xs:string"/> </xs:complexType> </xs:element> <xs:element minOccurs="0" name="textAsset"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="description" type="xs:string"/> <xs:element minOccurs="0" name="content" type="xs:string"/> </xs:sequence> <xs:attribute name="oid" type="xs:string"/> </xs:complexType> </xs:element> </xs:sequence> <xs:attribute name="oid" type="xs:string"/> </xs:complexType> </xs:element> </xs:schema> There doesn't appear to be a schema for the folder listings or term mappings. -- Miles Barr <mi...@ru...> Runtime Collective Ltd. |
From: Miles B. <mi...@ru...> - 2004-04-23 10:01:24
|
On Thu, 2004-04-22 at 20:59, Oli Sharpe wrote: > I think the generic content is in the ccm-ldn-aplaws-1.9.1-v.rpm file with the > main binaries of the distribution. (There's a possibility that it's in the > ccm-ldn-aplaws-doc-1.9.1-v.rpm file that's with the binaries as well.) > > If you install this RPM it puts the generic content in the /usr/share/doc/ > location as indicated in the APLAWS+ administrator's guide. Also, if you cd > into the generic-content directory, I think there's a README file there that is > short but helpful. Thanks for the pointer Oli. I was building from source and it appears the documentation wasn't properly deployed. I've found where it's kept in the source package: ./aplaws-plus-1.0.0-1-src/ccm-ldn-aplaws-1.9.1/aplaws/doc/generic-content > > Also where are the DTDs/XML Schemas that the content must follow and the > > one for the folder definition file? > > I'm not sure about the DTDs etc. :( I'll keep digging around and post here if I find anything. -- Miles Barr <mi...@ru...> Runtime Collective Ltd. |
From: Oli S. <ol...@go...> - 2004-04-22 20:03:05
|
Miles, > Where do I get the generic content from? It doesn't appear to be on the > Sourceforge site nor is it in the src zip file. I think the generic content is in the ccm-ldn-aplaws-1.9.1-v.rpm file with the main binaries of the distribution. (There's a possibility that it's in the ccm-ldn-aplaws-doc-1.9.1-v.rpm file that's with the binaries as well.) If you install this RPM it puts the generic content in the /usr/share/doc/ location as indicated in the APLAWS+ administrator's guide. Also, if you cd into the generic-content directory, I think there's a README file there that is short but helpful. HTH > Also where are the DTDs/XML Schemas that the content must follow and the > one for the folder definition file? I'm not sure about the DTDs etc. :( Oli |
From: Miles B. <mi...@ru...> - 2004-04-22 15:43:09
|
On Tue, 2004-04-20 at 11:24, Andrew Palmer wrote: > Miles > > See document: rhea-ag-aplaws-en-1.0.0-2.pdf downloadable from sourceforge > > page 9 > > see also the instructions in the readme file under generic content Sorry if these are obvious questions. Where do I get the generic content from? It doesn't appear to be on the Sourceforge site nor is it in the src zip file. Also where are the DTDs/XML Schemas that the content must follow and the one for the folder definition file? Thanks -- Miles Barr <mi...@ru...> Runtime Collective Ltd. |
From: Andrew P. <and...@nt...> - 2004-04-20 10:26:03
|
Miles See document: rhea-ag-aplaws-en-1.0.0-2.pdf downloadable from sourceforge page 9 see also the instructions in the readme file under generic content -----Original Message----- From: apl...@li... [mailto:apl...@li...] On Behalf Of Miles Barr Sent: 20 April 2004 11:14 To: apl...@li... Subject: [Aplaws-devel] XML Bulk Upload Hi, Does anyone know anything about the bulk upload feature of APLAWS? I hear it's supposed to be in the release after APLAWS+. Has anyone used it? Does anyone know the DTD that uploaded documents must follow? Thanks -- Miles Barr <mi...@ru...> Runtime Collective Ltd. ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Aplaws-devel mailing list Apl...@li... https://lists.sourceforge.net/lists/listinfo/aplaws-devel |
From: Miles B. <mi...@ru...> - 2004-04-20 10:14:29
|
Hi, Does anyone know anything about the bulk upload feature of APLAWS? I hear it's supposed to be in the release after APLAWS+. Has anyone used it? Does anyone know the DTD that uploaded documents must follow? Thanks -- Miles Barr <mi...@ru...> Runtime Collective Ltd. |
From: Shubham N. [ntl] <Shu...@nt...> - 2004-04-20 10:13:22
|
Great Daniel !!! It worked !!!. Thanks for this input. Will this fix be provided in the upgraded releases of APLAWS or is this a special caveat operation one would need to do for Oracle. I agree, that its really stupid feature within Oracle. Can an upgrade to latest Oracle Patch solve the problem you think ? We are running Oracle 9.2.0.1. I must also mention here that we also recieved initialization errors while installing. These are related to INSO filter tests failing. Has anyone come across these ? We were planning to upgrade our Oracle and then see whether these errors disappear, but thout it worthwhile to mention to the community on whether anyone else has recieved the same problems... Regards Shubham -----Original Message----- From: Daniel P. Berrange [mailto:ber...@re...] Sent: 19 April 2004 23:53 To: Shubham Nagar [ntl] Cc: apl...@li... Subject: Re: [Aplaws-devel] Error while running APLAWS Unfortunately this is a bug that crept into persistence when running on Oracle. Identifiers in Oracle are limited to 31 characters, and in some circumstances the generated queries exceeded this limit. See https://bugzilla.redhat.com/119466 To get around this problem, you'll need an updated copy of the clas file com/redhat/persistence/Signature.class which I've put up at http://people.redhat.com/berrange/aplaws-plus/ You'll need to modify the file /usr/share/java/ccm-core-6.1.0.jar and replace the Signature.class, then re-run 'ccm hostinit-bundle' with same argments as before, but also appending '--clean'. NB, PostgreSQL is unaffected by this bug since it doesn't have such stupidly small limits as Oracle. Dan. On Mon, Apr 19, 2004 at 12:50:06PM +0100, Shubham Nagar [ntl] wrote: > Hi All > > > > We have set up APLAWS + Release 1 fine but while navigating from the Top > Level links (Business.. etc) the navigation fails with an error report. The > content center works ok. From the onset looks something elementary to me.... > > > > Environment: > > > > Redhat Enterprise Linux ES > > Oracle9i Enterprise Edition Release 9.2.0.1.0 > > Java - java version "1.4.1_05" > > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01) > > Java HotSpot(TM) Client VM (build 1.4.1_05-b01, mixed mode) > > > > Any clues ? > > > > The error we recieve in the stack trace is: > > =========================================== > > > > 2004-04-19 11:04:18,460 [080-1] FATAL logging.ErrorReport - > > -*-*-*-*-*- Begin Error Report -*-*-*-*-*- > > -*-*-*- ACS Error Report Code: localhost:3a30f3:fc0239269b -*-*-*- > > -*-*-*- Message 1: com.arsdigita.persistence.PersistenceException: null > (root cause: ORA-00972: identifier is too long > > ) -*-*-*- > > -*-*-*- Message 2: com.redhat.persistence.engine.rdbms.RDBMSEngine$4: > ORA-00972: identifier is too long > > -*-*-*- > > > > -*-*-*- Section: CCM User -*-*-*- > > Party not logged in > > > > -*-*-*- Section: System properties -*-*-*- > > ccm.conf: /usr/share/ccm/conf/registry > > ccm.home: /usr/share/ccm > > com.arsdigita.london.navigation.DefaultContentSection: /content/ > > com.arsdigita.util.Assert.enabled: true > > file.encoding: ISO-8859-1 > > file.encoding.pkg: sun.io > > file.separator: / > > java.awt.graphicsenv: sun.awt.X11GraphicsEnvironment > > java.awt.printerjob: sun.print.PSPrinterJob > > java.class.path: > /opt/j2sdk1.4.1_05/jre/lib/jce.jar:/opt/j2sdk1.4.1_05/jre/lib/ext/sunjce_pro > vider.jar:/data/oracle/jdbc/lib/classes12.jar:/opt/j2sdk1.4.1_05/lib/tools.j > ar:/data/resin-2.1.12/lib/resin.jar:/data/resin-2.1.12/lib/jdbc2_0-stdext.ja > r:/data/resin-2.1.12/lib/jta_101.jar:/data/resin-2.1.12/lib/jndi.jar:/data/r > esin-2.1.12/lib/dom.jar:/data/resin-2.1.12/lib/sax.jar:/data/resin-2.1.12/li > b/jaxp.jar:/data/resin-2.1.12/lib/jmx.jar:/data/resin-2.1.12/lib/webutil.jar > :/data/resin-2.1.12/lib/jdbc-mysql.jar:/data/resin-2.1.12/lib/jaxp_parser_im > pl.jar:/data/resin-2.1.12/lib/jaxp_transform_impl.jar:/data/resin-2.1.12/lib > /jtidy-1.0.jar:/data/resin-2.1.12/lib/servlet.jar:/data/resin-2.1.12/lib/xal > an-j2-2.4.jar:/data/resin-2.1.12/lib/xerces-j2-2.0.2.jar:/data/resin-2.1.12/ > lib/xml-commons-apis-1.0.jar:/opt/j2sdk1.4.1_05/lib/tools.jar:/opt/j2sdk1.4. > 1_05/jre/lib/rt.jar:/data/resin-2.1.12/lib/jsdk23.jar > > java.class.version: 48.0 > > java.endorsed.dirs: /opt/j2sdk1.4.1_05/jre/lib/endorsed > > java.ext.dirs: > /opt/j2sdk1.4.1_05/jre/lib/ext:/opt/j2sdk1.4.1_05/lib/ext:/usr/share/ccm/web > apps/WEB-INF/system:/usr/share/ccm-tools/lib/security > > java.home: /opt/j2sdk1.4.1_05/jre > > java.io.tmpdir: /tmp > > java.library.path: > /opt/j2sdk1.4.1_05/jre/lib/i386/client:/opt/j2sdk1.4.1_05/jre/lib/i386:/opt/ > j2sdk1.4.1_05/jre/../lib/i386:/data/oracle/lib:/data/oracle/ctx/lib:/data/re > sin-2.1.12/libexec > > java.naming.factory.initial: com.caucho.naming.InitialContextFactoryImpl > > java.naming.factory.url.pkgs: com.caucho.naming > > java.runtime.name: Java(TM) 2 Runtime Environment, Standard Edition > > java.runtime.version: 1.4.1_05-b01 > > java.specification.name: Java Platform API Specification > > java.specification.vendor: Sun Microsystems Inc. > > java.specification.version: 1.4 > > java.util.prefs.PreferencesFactory: > java.util.prefs.FileSystemPreferencesFactory > > java.vendor: Sun Microsystems Inc. > > java.vendor.url: http://java.sun.com/ > > java.vendor.url.bug: http://java.sun.com/cgi-bin/bugreport.cgi > > java.version: 1.4.1_05 > > java.vm.info: mixed mode > > java.vm.name: Java HotSpot(TM) Client VM > > java.vm.specification.name: Java Virtual Machine Specification > > java.vm.specification.vendor: Sun Microsystems Inc. > > java.vm.specification.version: 1.0 > > java.vm.vendor: Sun Microsystems Inc. > > java.vm.version: 1.4.1_05-b01 > > javax.xml.parsers.DocumentBuilderFactory: > org.apache.xerces.jaxp.DocumentBuilderFactoryImpl > > javax.xml.parsers.SAXParserFactory: > org.apache.xerces.jaxp.SAXParserFactoryImpl > > javax.xml.transform.TransformerFactory: > com.icl.saxon.TransformerFactoryImpl > > line.separator: > > > > log4j.configuration: file:///usr/share/ccm/conf/log4j.properties > > org.xml.sax.driver: com.caucho.xml.Xml > > os.arch: i386 > > os.name: Linux > > os.version: 2.4.9-e.34smp > > path.separator: : > > resin.home: /usr/share/ccm > > sun.arch.data.model: 32 > > sun.boot.class.path: > /opt/j2sdk1.4.1_05/jre/lib/rt.jar:/opt/j2sdk1.4.1_05/jre/lib/i18n.jar:/opt/j > 2sdk1.4.1_05/jre/lib/sunrsasign.jar:/opt/j2sdk1.4.1_05/jre/lib/jsse.jar:/opt > /j2sdk1.4.1_05/jre/lib/jce.jar:/opt/j2sdk1.4.1_05/jre/lib/charsets.jar:/opt/ > j2sdk1.4.1_05/jre/classes > > sun.boot.library.path: /opt/j2sdk1.4.1_05/jre/lib/i386 > > sun.cpu.endian: little > > sun.cpu.isalist: > > sun.io.unicode.encoding: UnicodeLittle > > sun.java2d.fontpath: > > sun.os.patch.level: unknown > > user.country: GB > > user.dir: /usr/share/ccm > > user.home: /var/www > > user.language: en > > user.name: servlet > > user.timezone: Europe/London > > > > -*-*-*- Section: Stack trace -*-*-*- > > com.redhat.persistence.engine.rdbms.RDBMSEngine$4: ORA-00972: identifier > is too long > > > > at > com.redhat.persistence.engine.rdbms.RDBMSEngine.execute(RDBMSEngine.java:517 > ) > > at > com.redhat.persistence.engine.rdbms.RDBMSEngine.execute(RDBMSEngine.java:431 > ) > > at > com.redhat.persistence.engine.rdbms.RDBMSEngine.execute(RDBMSEngine.java:265 > ) > > at com.redhat.persistence.Cursor.execute(Cursor.java:131) > > at com.redhat.persistence.Cursor.next(Cursor.java:115) > > at com.arsdigita.persistence.DataQueryImpl.next(DataQueryImpl.java:646) > > at com.arsdigita.london.navigation.Template.matchBest(Template.java:188) > > at > com.arsdigita.london.navigation.NavigationFileResolver.resolveTemplate(Navig > ationFileResolver.java:141) > > at > com.arsdigita.london.navigation.NavigationFileResolver.resolve(NavigationFil > eResolver.java:118) > > at > com.arsdigita.web.ApplicationFileServlet.doService(ApplicationFileServlet.ja > va:132) > > at > com.arsdigita.web.BaseApplicationServlet$1.excurse(BaseApplicationServlet.ja > va:111) > > at com.arsdigita.kernel.KernelExcursion.run(KernelExcursion.java:57) > > at > com.arsdigita.web.BaseApplicationServlet.doService(BaseApplicationServlet.ja > va:105) > > at com.arsdigita.web.BaseServlet$1.excurse(BaseServlet.java:176) > > at com.arsdigita.kernel.KernelExcursion.run(KernelExcursion.java:57) > > at com.arsdigita.web.BaseServlet.internalService(BaseServlet.java:147) > > at com.arsdigita.web.BaseServlet.doGet(BaseServlet.java:272) > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > > at > com.caucho.server.http.FilterChainServlet.doFilter(FilterChainServlet.java:9 > 6) > > at com.caucho.server.http.Invocation.service(Invocation.java:315) > > at > com.caucho.server.http.QRequestDispatcher.forward(QRequestDispatcher.java:22 > 2) > > at > com.caucho.server.http.QRequestDispatcher.forward(QRequestDispatcher.java:10 > 3) > > at > com.caucho.server.http.QRequestDispatcher.forward(QRequestDispatcher.java:80 > ) > > at com.arsdigita.web.BaseDispatcher.forward(BaseDispatcher.java:206) > > at com.arsdigita.web.BaseDispatcher.forward(BaseDispatcher.java:190) > > at com.arsdigita.web.BaseDispatcher.dispatch(BaseDispatcher.java:130) > > at > com.arsdigita.web.DispatcherServlet.doService(DispatcherServlet.java:123) > > at com.arsdigita.web.BaseServlet$1.excurse(BaseServlet.java:176) > > at com.arsdigita.kernel.KernelExcursion.run(KernelExcursion.java:57) > > at com.arsdigita.web.BaseServlet.internalService(BaseServlet.java:147) > > at com.arsdigita.web.BaseServlet.doGet(BaseServlet.java:272) > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > > at > com.caucho.server.http.FilterChainServlet.doFilter(FilterChainServlet.java:9 > 6) > > at > com.arsdigita.london.shortcuts.ShortcutFilter.doService(ShortcutFilter.java: > 79) > > at com.arsdigita.web.BaseFilter.doFilter(BaseFilter.java:96) > > at > com.caucho.server.http.FilterChainFilter.doFilter(FilterChainFilter.java:88) > > at > com.arsdigita.london.subsite.SubsiteFilter.doService(SubsiteFilter.java:69) > > at com.arsdigita.web.BaseFilter.doFilter(BaseFilter.java:96) > > at > com.caucho.server.http.FilterChainFilter.doFilter(FilterChainFilter.java:88) > > at com.caucho.server.http.Invocation.service(Invocation.java:315) > > at com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:246) > > at > com.caucho.server.http.HttpRequest.handleConnection(HttpRequest.java:164) > > at com.caucho.server.TcpConnection.run(TcpConnection.java:139) > > at java.lang.Thread.run(Thread.java:536) > > > > > > -*-*-*- Section: HTTP headers -*-*-*- > > Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, > application/vnd.ms-powerpoint, application/vnd.ms-excel, application/msword, > */* > > Accept-Language: en-gb > > Connection: keep-alive > > Cookie: JSESSIONID=aioWO1FqHmje > > Host: ciaplaws1-win:8080 > > Referer: http://ciaplaws1-win:8080/ccm/portal/ > > User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0) > > Via: 1.0 mast-dc0-sp07 (NetCache NetApp/5.3.1) > > X-Forwarded-For: 10.116.1.3 > > > > -*-*-*- Section: Servlet attributes -*-*-*- > > class com.arsdigita.london.navigation.NavigationFileResolver.categoryPath: > [Lcom.arsdigita.categorization.Category;@154fd7a > > com.arsdigita.dispatcher.RequestContext: > com.arsdigita.sitenode.SiteNodeRequestContext@c20307 > > com.arsdigita.dispatcher.RequestValue: > {com.arsdigita.dispatcher.RequestValue@7958ef=null} > > com.arsdigita.web.BaseApplicationServlet.application_id: 192 > > com.arsdigita.web.BaseDispatcher.dispatched: true > > com.arsdigita.web.BaseServlet.request_url: /ccm/navigation/business/ > > > > -*-*-*- Section: Request summary -*-*-*- > > Context path: > > Request URI: /ccm/navigation/business/ > > Query string: null > > Method: GET > > Remote user: null > > > > -*-*-*- Section: Cookies -*-*-*- > > JSESSIONID: aioWO1FqHmje (expires: -1) > > -*-*-*-*-*- End Error Report -*-*-*-*-*- > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Aplaws-devel mailing list > Apl...@li... > https://lists.sourceforge.net/lists/listinfo/aplaws-devel -- |=- Daniel P. Berrange - ber...@re... -=| |=- Red Hat, 338 Euston Road, London, NW1 3BT. +44 (0)7977 267 243 -=| |=- -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| |