You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Andrew M <an...@jibeya.com> on 2004/12/03 20:24:56 UTC
[users@httpd] Error in Jboss when deploying cocoon 2.1.6
Hi,
when deploying cocoon 2.1.6 in Jboss 4.0 on OS X 10.3.6 I get the
following error message:
18:33:00,169 INFO [STDOUT] WARN! *** JMS block is installed but jms
client library not found. ***
- For the jms block to work you must install and start a JMS server and
place the client jar in WEB-INF/lib.
- The default server, OpenJMS is configured in cocoon.xconf but is not
bundled with Cocoon.
18:33:07,615 INFO [STDOUT] Loading properties file: resourceName =
'/org/exolab/castor/castor.properties' fileName = 'castor.properties'
18:33:08,123 INFO [STDOUT] org.exolab.castor.mapping.MappingException:
Could not find the class
org.apache.cocoon.portal.pluto.om.common.DisplayNameImpl
How do i resolve these issue?
I have included both my blocks.properties and local.blocks.properties
files to view
regards
Andrew
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: [users@httpd] Error in Jboss when deploying cocoon 2.1.6
Posted by Andrew M <an...@jibeya.com>.
Any ideas anyone?
On 4 Dec 2004, at 12:25, Andrew M wrote:
> one down, one to go. I have resolved the first message:
>
>>> 18:33:00,169 INFO [STDOUT] WARN! *** JMS block is installed but jms
>>> client library not found. ***
>>> - For the jms block to work you must install and start a JMS server
>>> and place the client jar in WEB-INF/lib.
>>> - The default server, OpenJMS is configured in cocoon.xconf but is
>>> not bundled with Cocoon.
>
> by commenting out:
> <!--<jms-connection-manager logger="core.jms">
> <topic-connection name="local-topics">
> <parameter name="java.naming.factory.initial"
> value="org.exolab.jms.jndi.InitialContextFactory"/>
> <parameter name="java.naming.provider.url"
> value="rmi://localhost:1099/"/>-->
> <!-- OpenJMS RMI topic connection factory
> <parameter name="connection-factory"
> value="JmsTopicConnectionFactory"/>-->
> <!--
> <parameter name="username" value="user"/>
> <parameter name="password" value="secret"/>
> -->
> <!--</topic-connection>
> </jms-connection-manager>-->
>
> from the cocoon.xconf file. Any ideas about the castor.properties
> error???
>
> regards
>
>
> Andrew
> On 4 Dec 2004, at 11:42, Andrew M wrote:
>
>> Any ideas?
>> On 3 Dec 2004, at 19:24, Andrew M wrote:
>>
>>> Hi,
>>> when deploying cocoon 2.1.6 in Jboss 4.0 on OS X 10.3.6 I get the
>>> following error message:
>>>
>>> 18:33:00,169 INFO [STDOUT] WARN! *** JMS block is installed but jms
>>> client library not found. ***
>>> - For the jms block to work you must install and start a JMS server
>>> and place the client jar in WEB-INF/lib.
>>> - The default server, OpenJMS is configured in cocoon.xconf but is
>>> not bundled with Cocoon.
>>>
>>> 18:33:07,615 INFO [STDOUT] Loading properties file: resourceName =
>>> '/org/exolab/castor/castor.properties' fileName =
>>> 'castor.properties'
>>> 18:33:08,123 INFO [STDOUT]
>>> org.exolab.castor.mapping.MappingException: Could not find the class
>>> org.apache.cocoon.portal.pluto.om.common.DisplayNameImpl
>>>
>>> How do i resolve these issue?
>>>
>>> I have included both my blocks.properties and
>>> local.blocks.properties files to view
>>>
>>> regards
>>>
>>> Andrew
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>>> For additional commands, e-mail: users-help@cocoon.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>> For additional commands, e-mail: users-help@cocoon.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: [users@httpd] Error in Jboss when deploying cocoon 2.1.6
Posted by Andrew M <an...@jibeya.com>.
one down, one to go. I have resolved the first message:
>> 18:33:00,169 INFO [STDOUT] WARN! *** JMS block is installed but jms
>> client library not found. ***
>> - For the jms block to work you must install and start a JMS server
>> and place the client jar in WEB-INF/lib.
>> - The default server, OpenJMS is configured in cocoon.xconf but is
>> not bundled with Cocoon.
by commenting out:
<!--<jms-connection-manager logger="core.jms">
<topic-connection name="local-topics">
<parameter name="java.naming.factory.initial"
value="org.exolab.jms.jndi.InitialContextFactory"/>
<parameter name="java.naming.provider.url"
value="rmi://localhost:1099/"/>-->
<!-- OpenJMS RMI topic connection factory
<parameter name="connection-factory"
value="JmsTopicConnectionFactory"/>-->
<!--
<parameter name="username" value="user"/>
<parameter name="password" value="secret"/>
-->
<!--</topic-connection>
</jms-connection-manager>-->
from the cocoon.xconf file. Any ideas about the castor.properties
error???
regards
Andrew
On 4 Dec 2004, at 11:42, Andrew M wrote:
> Any ideas?
> On 3 Dec 2004, at 19:24, Andrew M wrote:
>
>> Hi,
>> when deploying cocoon 2.1.6 in Jboss 4.0 on OS X 10.3.6 I get the
>> following error message:
>>
>> 18:33:00,169 INFO [STDOUT] WARN! *** JMS block is installed but jms
>> client library not found. ***
>> - For the jms block to work you must install and start a JMS server
>> and place the client jar in WEB-INF/lib.
>> - The default server, OpenJMS is configured in cocoon.xconf but is
>> not bundled with Cocoon.
>>
>> 18:33:07,615 INFO [STDOUT] Loading properties file: resourceName =
>> '/org/exolab/castor/castor.properties' fileName = 'castor.properties'
>> 18:33:08,123 INFO [STDOUT]
>> org.exolab.castor.mapping.MappingException: Could not find the class
>> org.apache.cocoon.portal.pluto.om.common.DisplayNameImpl
>>
>> How do i resolve these issue?
>>
>> I have included both my blocks.properties and local.blocks.properties
>> files to view
>>
>> regards
>>
>> Andrew
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>> For additional commands, e-mail: users-help@cocoon.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: [users@httpd] Error in Jboss when deploying cocoon 2.1.6
Posted by Andrew M <an...@jibeya.com>.
Any ideas?
On 3 Dec 2004, at 19:24, Andrew M wrote:
> Hi,
> when deploying cocoon 2.1.6 in Jboss 4.0 on OS X 10.3.6 I get the
> following error message:
>
> 18:33:00,169 INFO [STDOUT] WARN! *** JMS block is installed but jms
> client library not found. ***
> - For the jms block to work you must install and start a JMS server
> and place the client jar in WEB-INF/lib.
> - The default server, OpenJMS is configured in cocoon.xconf but is not
> bundled with Cocoon.
>
> 18:33:07,615 INFO [STDOUT] Loading properties file: resourceName =
> '/org/exolab/castor/castor.properties' fileName = 'castor.properties'
> 18:33:08,123 INFO [STDOUT]
> org.exolab.castor.mapping.MappingException: Could not find the class
> org.apache.cocoon.portal.pluto.om.common.DisplayNameImpl
>
> How do i resolve these issue?
>
> I have included both my blocks.properties and local.blocks.properties
> files to view
>
> regards
>
> Andrew
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org