-
How is JAAS going to be handled in the JEE deployment? APLAWS uses javax.security.auth.login.Configuration.setConfiguration(getLoginConfig()) to set the JAAS configuration. In JBoss this overides it's way of configuring JAAS and breaks the ability to login to the admin and jmx consoles. The way to package an EAR and configure it in JBoss is described pretty well at...
2009-08-12 16:06:52 UTC in APLAWS
-
This patch allows APLAWS+ to run under a context other than root.
It also adds support for running APLAWS+ under a secure https connection and better error reproting for XSLT errors. I added these additional changes with the patch because the files that were changed to add support for different contexts also contained the other changes.
2009-07-02 13:13:52 UTC in APLAWS
-
> Is it really true, that each module should be able to run in its own context?
I don't see modules necessarily as being an extension to the existing functionality. A module can provide completely new and independent functionality. Developers should be able to use the core as a lower level framework for their own applications. This is what I use the code for. I tap into the...
2009-07-02 13:02:33 UTC in APLAWS
-
> I think XML templates, which render a xml information to html, are very private
> to the module which maintains that information. It should never be used by any
> other module directly, and even more so by another web application
The problem is that the presentation layer depends upon Bebop XSLT in ccm-core. Each module should be able to run in its own context but it also needs...
2009-06-29 18:50:04 UTC in APLAWS
-
Just to throw my $.02 in, I agree with others about adopting Hibernate or another implementation of Java Persistence API. It is a standard just like JCR so I don't get the argument that companies will want JCR over it. It fits in well with the exising architecture. I have looked into the Alfresco code and it's use of JCR and I considered the design very messy and not scalable. The developers...
2009-06-24 15:26:05 UTC in APLAWS
-
Just to throw my $.02 in, I agree with others about adopting Hibernate or another implementation of Java Persistence API. It is a standard just like JCR so I don't get the argument that companies will want JCR over it. It fits in well with the exising architecture. I have looked into the Alfresco code and it's use of JCR and I considered the design very messy and not scalable. The developers...
2009-06-23 19:27:41 UTC in APLAWS
-
Peter,
You must be refering to packages other than ccm-core or ccm-cms. I do not use the other packages so don't know about how they include other XML templates.
In the XML templates for ccm-core and ccm-cms I had to replace the <a href="/somefile"> urls with <a href="{$context-prefix}/somefile">. For APLAWS applications that I developed myself that run...
2009-05-29 17:07:09 UTC in APLAWS
-
> I will start to make APLAWS installable in any arbitrary directory, specified in project.xml webapp tag or during installation time. This involves a massive rewriting of xsl files and a lot of work in web.xml and the dispatcher magic and may take some time.
Peter, I have already done work to get APLAWS to run under a context other than root. It does not require a massive rewrite of xsl...
2009-05-22 10:30:24 UTC in APLAWS
-
Removes the resource protocol handler dependency in ContentSectionConfig by using a modified version of the deprecated ResourceParameter.
2009-05-20 12:49:15 UTC in APLAWS
-
I ran into this problem when using JBoss. Because JBoss uses it's own resource handler I couldn't just add the ccm-core-system jar. I will submit the patches to SourceForge Patch Tracker.
2009-05-20 12:28:32 UTC in APLAWS
