You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Humberto Hernandez Torres <hh...@itweb.com.mx> on 2003/04/02 02:29:47 UTC
Websphere portal using Turbine?
A friend was testing the Websphere portal and found some references to
Turbine. Is this a coincidence? May be the Websphere portal uses Turbine or
perhaps it is based on jetspeed. Any guesses?
Here is the Websphere portal server log:
2003.03.28 15:14:22.091 com.ibm.wps.turbine.services.logging.JLogLogger
log()
--------------------------------------------------
WebSphere Portal Server
Version 4.1.0.0 Portal - Express
Build 4.1.2.412e_152_20021021
--------------------------------------------------
Licensed Materials - Property of IBM
5724-D65
(C) Copyright IBM Corp. 2001, 2002 All Rights Reserved.
--------------------------------------------------
2003.03.28 15:14:22.151 com.ibm.wps.turbine.services.logging.JLogLogger
log()
ServiceBroker: LoggingService enabled.
2003.03.28 15:14:48.850
com.ibm.wps.services.siteanalyzer.SiteAnalyzerLogServiceImpl init()
Entry, parm 1 = 0.9.7.2 starting SiteAnalyzerLogService
2003.03.28 15:14:50.572 com.ibm.wps.turbine.services.logging.JLogLogger
log()
@com.ibm.wps.command.xml.XmlAccessService: Registering engine
com.ibm.wps.command.xml.Engine: -//IBM//DTD Portal Configuration 1.0//EN
/com/ibm/wps/command/xml/PortalConfig.dtd
2003.03.28 15:14:50.743 com.ibm.wps.turbine.services.logging.JLogLogger
log()
@com.ibm.wps.command.xml.XmlAccessService: XML Access Service initialized
2003.03.28 15:16:19.080 com.ibm.wps.turbine.services.logging.JLogLogger
log()
DefaultVault.loadEncryptionExit() -- /defaultvault was not found,
defaulting to the DefaultEncryptionExit.
2003.03.28 15:16:19.120 com.ibm.wps.turbine.services.logging.JLogLogger
log()
VaultAdapterManager.loadVaultAdapter(): Vault Adapter Type default was
successfully loaded: WPS 4.1 Default Vault Implementation
2003.03.28 15:16:22.004 com.ibm.wps.turbine.services.logging.JLogLogger
log()
PortletInvokerService early init()....starting!
2003.03.28 15:16:22.034 com.ibm.wps.turbine.services.logging.JLogLogger
log()
PortletInvokerService early init()....finished!
2003.03.28 15:16:22.144 com.ibm.wps.turbine.services.logging.JLogLogger
log()
ThreadPoolServiceImpl.init: Early init started
2003.03.28 15:16:22.725 com.ibm.wps.turbine.services.logging.JLogLogger
log()
ThreadPoolServiceImpl.init: Early init finished
2003.03.28 15:16:22.915 com.ibm.wps.turbine.services.logging.JLogLogger
log()
FilePortletServiceRegistryService early init()....starting!
2003.03.28 15:16:23.015 com.ibm.wps.turbine.services.logging.JLogLogger
log()
FilePortletServiceRegistryService early init()....finished!
2003.03.28 15:24:53.960 com.ibm.wps.turbine.services.logging.JLogLogger
log()
Transaction.commit() was called before Transaction.begin()! Method call is
ignored!
2003.03.28 15:25:32.225
com.ibm.wps.services.siteanalyzer.SiteAnalyzerLogServiceImpl destroy()
Entry, parm 1 = 0.9.7.2 shutdown SiteAnalyzerLogService
2003.03.28 15:29:44.548 com.ibm.wps.datastore.MarkupDescriptorPersister
handleException
Error during database access!
2003.03.28 15:29:44.548 com.ibm.wps.datastore.core.DataStoreContext
handleException
java.lang.NullPointerException
at
com.ibm.wps.services.datastore.DataStoreServiceImpl.getConnection(DataStoreS
erviceImpl.java:89)
at
com.ibm.wps.services.datastore.DataStore.getConnection(DataStore.java:27)
at
com.ibm.wps.datastore.core.DataStoreContext.init(DataStoreContext.java:91)
at
com.ibm.wps.datastore.core.DataStoreContext.init(DataStoreContext.java:53)
at
com.ibm.wps.datastore.core.BasePersister.findInternal(BasePersister.java:453
)
at
com.ibm.wps.datastore.core.BasePersister.findInternal(BasePersister.java:421
)
at
com.ibm.wps.datastore.core.BasePersister.findAllInternal(BasePersister.java:
572)
at
com.ibm.wps.datastore.MarkupDescriptorPersister.findAll(MarkupDescriptorPers
ister.java:42)
at
com.ibm.wps.datastore.MarkupDescriptor.findAll(MarkupDescriptor.java:103)
at
com.ibm.wps.services.navigator.NavigatorServiceImpl.reload(NavigatorServiceI
mpl.java:187)
at com.ibm.wps.util.UpdateTrigger.run(UpdateTrigger.java:38)
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: Websphere portal using Turbine?
Posted by Wei He <we...@ldeo.columbia.edu>.
I read something somewhere long time ago (1.5+ years ago) about WebSphere
portal server was initially based on JetSpeed.
Humberto Hernandez Torres wrote:
> A friend was testing the Websphere portal and found some references to
> Turbine. Is this a coincidence? May be the Websphere portal uses Turbine or
> perhaps it is based on jetspeed. Any guesses?
>
> Here is the Websphere portal server log:
>
> 2003.03.28 15:14:22.091 com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> --------------------------------------------------
> WebSphere Portal Server
> Version 4.1.0.0 Portal - Express
> Build 4.1.2.412e_152_20021021
> --------------------------------------------------
> Licensed Materials - Property of IBM
> 5724-D65
> (C) Copyright IBM Corp. 2001, 2002 All Rights Reserved.
> --------------------------------------------------
>
> 2003.03.28 15:14:22.151 com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> ServiceBroker: LoggingService enabled.
>
> 2003.03.28 15:14:48.850
> com.ibm.wps.services.siteanalyzer.SiteAnalyzerLogServiceImpl init()
> Entry, parm 1 = 0.9.7.2 starting SiteAnalyzerLogService
>
> 2003.03.28 15:14:50.572 com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> @com.ibm.wps.command.xml.XmlAccessService: Registering engine
> com.ibm.wps.command.xml.Engine: -//IBM//DTD Portal Configuration 1.0//EN
> /com/ibm/wps/command/xml/PortalConfig.dtd
>
> 2003.03.28 15:14:50.743 com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> @com.ibm.wps.command.xml.XmlAccessService: XML Access Service initialized
>
> 2003.03.28 15:16:19.080 com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> DefaultVault.loadEncryptionExit() -- /defaultvault was not found,
> defaulting to the DefaultEncryptionExit.
>
> 2003.03.28 15:16:19.120 com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> VaultAdapterManager.loadVaultAdapter(): Vault Adapter Type default was
> successfully loaded: WPS 4.1 Default Vault Implementation
>
> 2003.03.28 15:16:22.004 com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> PortletInvokerService early init()....starting!
>
> 2003.03.28 15:16:22.034 com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> PortletInvokerService early init()....finished!
>
> 2003.03.28 15:16:22.144 com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> ThreadPoolServiceImpl.init: Early init started
>
> 2003.03.28 15:16:22.725 com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> ThreadPoolServiceImpl.init: Early init finished
>
> 2003.03.28 15:16:22.915 com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> FilePortletServiceRegistryService early init()....starting!
>
> 2003.03.28 15:16:23.015 com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> FilePortletServiceRegistryService early init()....finished!
>
> 2003.03.28 15:24:53.960 com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> Transaction.commit() was called before Transaction.begin()! Method call is
> ignored!
>
> 2003.03.28 15:25:32.225
> com.ibm.wps.services.siteanalyzer.SiteAnalyzerLogServiceImpl destroy()
> Entry, parm 1 = 0.9.7.2 shutdown SiteAnalyzerLogService
>
> 2003.03.28 15:29:44.548 com.ibm.wps.datastore.MarkupDescriptorPersister
> handleException
> Error during database access!
>
> 2003.03.28 15:29:44.548 com.ibm.wps.datastore.core.DataStoreContext
> handleException
> java.lang.NullPointerException
> at
> com.ibm.wps.services.datastore.DataStoreServiceImpl.getConnection(DataStoreS
> erviceImpl.java:89)
> at
> com.ibm.wps.services.datastore.DataStore.getConnection(DataStore.java:27)
> at
> com.ibm.wps.datastore.core.DataStoreContext.init(DataStoreContext.java:91)
> at
> com.ibm.wps.datastore.core.DataStoreContext.init(DataStoreContext.java:53)
> at
> com.ibm.wps.datastore.core.BasePersister.findInternal(BasePersister.java:453
> )
> at
> com.ibm.wps.datastore.core.BasePersister.findInternal(BasePersister.java:421
> )
> at
> com.ibm.wps.datastore.core.BasePersister.findAllInternal(BasePersister.java:
> 572)
> at
> com.ibm.wps.datastore.MarkupDescriptorPersister.findAll(MarkupDescriptorPers
> ister.java:42)
> at
> com.ibm.wps.datastore.MarkupDescriptor.findAll(MarkupDescriptor.java:103)
> at
> com.ibm.wps.services.navigator.NavigatorServiceImpl.reload(NavigatorServiceI
> mpl.java:187)
> at com.ibm.wps.util.UpdateTrigger.run(UpdateTrigger.java:38)
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
RE: Websphere portal using Turbine?
Posted by Quinton McCombs <qm...@nequalsone.com>.
Cool.....
> -----Original Message-----
> From: Humberto Hernandez Torres [mailto:hhernandez@itweb.com.mx]
> Sent: Tuesday, April 01, 2003 6:30 PM
> To: Turbine Users List
> Subject: Websphere portal using Turbine?
>
>
> A friend was testing the Websphere portal and found some
> references to Turbine. Is this a coincidence? May be the
> Websphere portal uses Turbine or perhaps it is based on
> jetspeed. Any guesses?
>
> Here is the Websphere portal server log:
>
> 2003.03.28 15:14:22.091
> com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> --------------------------------------------------
> WebSphere Portal Server
> Version 4.1.0.0 Portal - Express
> Build 4.1.2.412e_152_20021021
> --------------------------------------------------
> Licensed Materials - Property of IBM
> 5724-D65
> (C) Copyright IBM Corp. 2001, 2002 All Rights Reserved.
> --------------------------------------------------
>
> 2003.03.28 15:14:22.151
> com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> ServiceBroker: LoggingService enabled.
>
> 2003.03.28 15:14:48.850
> com.ibm.wps.services.siteanalyzer.SiteAnalyzerLogServiceImpl
> init()
> Entry, parm 1 = 0.9.7.2 starting SiteAnalyzerLogService
>
> 2003.03.28 15:14:50.572
> com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> @com.ibm.wps.command.xml.XmlAccessService: Registering engine
> com.ibm.wps.command.xml.Engine: -//IBM//DTD Portal
> Configuration 1.0//EN /com/ibm/wps/command/xml/PortalConfig.dtd
>
> 2003.03.28 15:14:50.743
> com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> @com.ibm.wps.command.xml.XmlAccessService: XML Access
> Service initialized
>
> 2003.03.28 15:16:19.080
> com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> DefaultVault.loadEncryptionExit() -- /defaultvault was not
> found, defaulting to the DefaultEncryptionExit.
>
> 2003.03.28 15:16:19.120
> com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> VaultAdapterManager.loadVaultAdapter(): Vault Adapter Type
> default was successfully loaded: WPS 4.1 Default Vault Implementation
>
> 2003.03.28 15:16:22.004
> com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> PortletInvokerService early init()....starting!
>
> 2003.03.28 15:16:22.034
> com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> PortletInvokerService early init()....finished!
>
> 2003.03.28 15:16:22.144
> com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> ThreadPoolServiceImpl.init: Early init started
>
> 2003.03.28 15:16:22.725
> com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> ThreadPoolServiceImpl.init: Early init finished
>
> 2003.03.28 15:16:22.915
> com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> FilePortletServiceRegistryService early init()....starting!
>
> 2003.03.28 15:16:23.015
> com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> FilePortletServiceRegistryService early init()....finished!
>
> 2003.03.28 15:24:53.960
> com.ibm.wps.turbine.services.logging.JLogLogger
> log()
> Transaction.commit() was called before Transaction.begin()!
> Method call is ignored!
>
> 2003.03.28 15:25:32.225
> com.ibm.wps.services.siteanalyzer.SiteAnalyzerLogServiceImpl
> destroy()
> Entry, parm 1 = 0.9.7.2 shutdown SiteAnalyzerLogService
>
> 2003.03.28 15:29:44.548
> com.ibm.wps.datastore.MarkupDescriptorPersister
> handleException
> Error during database access!
>
> 2003.03.28 15:29:44.548 com.ibm.wps.datastore.core.DataStoreContext
> handleException
> java.lang.NullPointerException
> at
> com.ibm.wps.services.datastore.DataStoreServiceImpl.getConnect
> ion(DataStoreS
> erviceImpl.java:89)
> at
> com.ibm.wps.services.datastore.DataStore.getConnection(DataSto
> re.java:27)
> at
> com.ibm.wps.datastore.core.DataStoreContext.init(DataStoreCont
> ext.java:91)
> at
> com.ibm.wps.datastore.core.DataStoreContext.init(DataStoreCont
> ext.java:53)
> at
> com.ibm.wps.datastore.core.BasePersister.findInternal(BasePers
> ister.java:453
> )
> at
> com.ibm.wps.datastore.core.BasePersister.findInternal(BasePers
> ister.java:421
> )
> at
> com.ibm.wps.datastore.core.BasePersister.findAllInternal(BaseP
> ersister.java:
> 572)
> at
> com.ibm.wps.datastore.MarkupDescriptorPersister.findAll(Markup
> DescriptorPers
> ister.java:42)
> at
> com.ibm.wps.datastore.MarkupDescriptor.findAll(MarkupDescripto
> r.java:103)
> at
> com.ibm.wps.services.navigator.NavigatorServiceImpl.reload(Nav
> igatorServiceI
> mpl.java:187)
> at com.ibm.wps.util.UpdateTrigger.run(UpdateTrigger.java:38)
>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org