September 2006 - jboss-dev-forums

[Design of JBossXB] - Re: GenericObjectModelProvider not setting attributes in XML

by info＠connext.co.za

Good Day, Thanks, I will check it out. Regards, Mark P Ashworth View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969367#3969367 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969367

17 years, 8 months

1
0
0 / 0

DEFINTIVAMENTE LOS MEJORES PRECIOS PARA LLAMAR A CHILE Y AL EXTRANJERO :: CARRIER 179 :: OFERTA LANZAMIENTO

by 179.cl

17 years, 8 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Portal 2.4.1

by roy.russo＠jboss.com

"sohil.shah(a)jboss.com" wrote : I am hoping to squeeze the performance boost by using a JBossCache PersistenceManager immediately in the 2.4.1 release. The jackrabbit caching issue may have to be addressed after that depending on what strategy we pick for it. | Performance enhancements should be taken care of before feature additions planned for CMS 2.6 (fine-grained security & workflow integration). So if these changes are possible to be squeezed in to 2.4.1, they should also be included in 2.6 w/ tests. UI changes are not affected by these enhancements, so the plan will continue with that regard. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969337#3969337 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969337

17 years, 8 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Portal 2.4.1

by sohil.shah＠jboss.com

anonymous wrote : | 1) Is disabling jackrabbit's in-memory cache an option from performance perspective? Is it a config or source code change? | Currently, this is a source code change. Yes. if we have our JBossCache based PersistenceManager layer, caching in the jackrabbit layer is actually redundant. The performance boost will be unaffected and we have a fully clustered CMS instead of requiring a singleton cluster node for CMS administration functions anonymous wrote : | 2) http://issues.apache.org/jira/browse/JCR-169 was supposed to provide hooks for distributed cache, but it doesn't seem like this will be done by jackrabbit developers soon. Is it a possibility to just implement a hook for external cache and give it to jackrabbit? Then we could integrate it with JBossCache without having to fork jackrabbit. | This shouldn't be a bad strategy. Definitely more preferable to forking jackrabbit codebase. anonymous wrote : | 3) 3.0 timeframe? | I am hoping to squeeze the performance boost by using a JBossCache PersistenceManager immediately in the 2.4.1 release. The jackrabbit caching issue may have to be addressed after that depending on what strategy we pick for it. I am looking at the jackrabbit codebase currently and see if something can be done for 2.4.1 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969335#3969335 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969335

17 years, 8 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Portal 2.4.1

by alex.pinkin＠jboss.com

1) Is disabling jackrabbit's in-memory cache an option from performance perspective? Is it a config or source code change? 2) http://issues.apache.org/jira/browse/JCR-169 was supposed to provide hooks for distributed cache, but it doesn't seem like this will be done by jackrabbit developers soon. Is it a possibility to just implement a hook for external cache and give it to jackrabbit? Then we could integrate it with JBossCache without having to fork jackrabbit. 3) 3.0 timeframe? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969306#3969306 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969306

17 years, 8 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Portlet and CMS

by alain_fr

thank you Julien for your quick answer i was a bit confused because the definition of CMSPortlet is not in a directory called CMS. It's really easy to have a portlet that access an html file in the CMS. Just use a CMSPortlet instance and modify the key indexpage in Preferences to point to the desired html file. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969305#3969305 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969305

17 years, 8 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Portlet and CMS

by julien＠jboss.com

it is because we create in the tree or PortalObject configured in jboss-portal.sar/conf/data/default-object.xml a page containing a window that points to the cms portlet instance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969304#3969304 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969304

17 years, 8 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Portlet and CMS

by alain_fr

thank you Julien, I've downloaded the source code of the project. And i have found this definition for the portlet: jboss-portal-2.4.0-src\core\src\resources\portal-core-war\WEB-INF\portlet.xml | <portlet> | <description>Content Management System Portlet</description> | <portlet-name>CMSPortlet</portlet-name> | <display-name>Content Management System Portlet</display-name> | | <portlet-class>org.jboss.portal.core.portlet.cms.CMSPortlet</portlet-class> | <supports> | <mime-type>text/html</mime-type> | <portlet-mode>VIEW</portlet-mode> | </supports> | <supported-locale>en</supported-locale> | <supported-locale>fr</supported-locale> | <supported-locale>es</supported-locale> | <resource-bundle>Resource</resource-bundle> | <portlet-info> | <title>CMS</title> | </portlet-info> | <portlet-preferences> | <preference> | <name>indexpage</name> | <value>/default/index.html</value> | </preference> | </portlet-preferences> | </portlet> | The html file used in the portlet is: jboss-portal-2.4.0-src\core\src\bin\portal-cms-sar\portal\cms\conf\default-content\default\index.html Well, how is made the link between /default/index.html in portlet.xml and jboss-portal-2.4.0-src\core\src\bin\portal-cms-sar\portal\cms\conf\default-content\default\index.html the CMS is a kind of default path where the portal look if the file is present? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969303#3969303 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969303

17 years, 8 months

1
0
0 / 0

[Design of JBoss Serialization] - Re: What should I create to frequently ask it for smart clon

by elijah.epifanov＠gmail.com

"clebert.suconic(a)jboss.com" wrote : | So... I created the feature just for you (as it was simple creating it). As an exchange now, can you provide me what would be a nice UseCase? :-) | )) I am implementing a highly concurrent cache for an in-house project. Currently it performs faster than other caches, and it has some useful features included by default (like blocking concurrent threads getting the same value). The key of performance gain is the use of highly nondeterministic algorithms, which achieve this boost at the price of providing much weaker guarantees. Later (if my employeer will allow this:)) I will opensource it. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969260#3969260 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969260

17 years, 8 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Contract definition language

by mark.little＠jboss.com

WSDL is fine if you're in a Web Services world and even then up to a point. It isn't a generic contract definition language. A combination of WSDL and WS-Policy gets you a little closer to things, but even then you can't define meta-data easily, such as SLAs. WSDL tools are also pretty poor for working at the SOA level: most take the approach of distributed objects, which isn't what SOA is about. Finally, WSDL isn't simple! WSDL 2.0 adds more complexity. We should add nothing to the ESB that acts as a barrier to adoption and ease of use. People who are using JBossESB for Web Services may well expect to see some aspect of the contract definition appear in XML and WSDL. People who are using JBossESB for REST, JMS, or anything other than Web Services, may not expect to see WSDL anywhere. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969248#3969248 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969248

17 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums September 2006