[Installation, Configuration & Deployment] - jboss 5.1.0/railo 3.1.1 context problem?
by tim.clarke
Getting a message "Document base /usr/local/jboss-5.1.0.GA/server/
default/deploy/railo/WEB-INF/web.xml does not exist or is not a
readable directory" whenever I place my railo files in my jboss deploy
folder. Any ideas please? Details below.
details:
On Fedora 11 I've deployed jboss successfully in /usr/local/jboss - it
starts without errors and presents the management page on :8080.
That's great; easy and quick.
Simply dropping the railo.war file into "(jbossroot)/server/default/
deploy/" yields "Failed to create a new SAX parser" - I cured that by
exploding the .war and removing the conflicting jars.
I am now trying to deploy by copying the tree forming the exploded
railo war contents to "(jbossroot)/server/default/deploy/railo/". All
files/folders in the jboss folder tree and railo folder tree are owned
jboss:jboss with rights 664/775. Pertinent stuff (I think?) from railo/
WEB-INF/web.xml file is:
<web-app>
<display-name>Railo</display-name>
<servlet-name>CFMLServlet</servlet-name>
CFML runtime Engine
<servlet-class>railo.loader.servlet.CFMLServlet</
servlet-class>
<init-param>
<param-name>configuration</param-name>
<param-value>/WEB-INF/railo/</param-value>
Configuraton directory</
description>
</init-param>
...
But I've been struggling to work out what that all means. The error
message "Document base ... does not exist or is not a readable
directory" isn't helping me - I haven't set a document base parameter?
Help!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260495#4260495
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260495
16 years, 8 months
[EJB 3.0 Users] - EJB3 and JBoss Portal 2.7.2 Bundle
by Fuchs
Hello!
I am using JBoss Portal 2.7.2 bundle with JBoss 4.2.3 and I have to import EJB3 into it, to get the EJB Timer-Service.
I found this installation guide for JBoss 4.X:
| 1. Download EJB 3.0 RC4 - PFD.
| 2. Unzip this file.
| 3. Copy ejb3.deployer from the lib/ directory of the distribution to jboss-4.0.x/server/all/deploy
| 4. Copy ejb3-clustered-sfsbcache-service.xml from the lib/ directory of the distribution to jboss-4.0.x/server/all/deploy
| 5. Copy ejb3-entity-cache-service.xml from the lib/ directory of the distribution to jboss-4.0.x/server/all/deploy
| 6. Copy ejb3-interceptors-aop.xml from the lib/ directory of the distribution to jboss-4.0.x/server/all/deploy
| 7. Copy jboss-aop-jdk50.deployer from the lib/ directory of the distribution to jboss-4.0.x/server/all/deploy
| 8. Copy jboss-remoting.jar from the lib/ directory of the distribution to jboss-4.0.x/server/all/lib
| 9. Copy jboss-serialization.jar from the lib/ directory of the distribution to jboss-4.0.x/server/all/lib
| 10. Copy jboss-j2ee.jar from the lib/ directory of the distribution to jboss-4.0.x/server/all/lib
| 11. Remove ejb3-persistence.jar from jboss-4.0.x/server/all/lib
| 12. Remove hibernate3.jar from jboss-4.0.x/server/all/lib
| 13. Remove hibernate-annotations.jar from jboss-4.0.x/server/all/lib
| 14. Remove hibernate-entitymanager.jar from jboss-4.0.x/server/all/lib
| 15. Remove jboss-aop.deployer/ from jboss-4.0.x/server/all/deploy
| 16. Start jboss up with the all configuration run.sh -c all
|
| If you do not want to run with the all configuration, the skip the steps of copying the ejb3-clustered-sfsbcache-service.xml and the ejb3-entity-cache-service.xml
|
But it is not the correct way for JBoss Portal or do I have to do additional things?
The Console displayed exceptions and the Timer-Service did not run.
Here is a small abstract of these exceptions:
| *** DEPLOYMENTS IN ERROR:
| WSSecurityHandlerEJB3 -> java.lang.NoClassDefFoundError: org/jboss/ejb3/Ejb3ModuleMBean
| WSDeployerHook_JAXWS_EJB3 -> java.lang.NoClassDefFoundError: org/jboss/ejb3/EJBContainer
| WSApplicationMetaDataAdapterEJB3 -> java.lang.NoClassDefFoundError: org/jboss/ejb3/EJBContainer
|
| *** DEPLOYMENTS MISSING DEPENDENCIES:
| WSContainerMetaDataDeploymentAspect -> WSContainerMetaDataAdapter{Configured:Instantiated}
| WSContainerMetaDataAdapter -> WSApplicationMetaDataAdapterEJB3{Configured:**ERROR**}, WSWebMetaDataAdapter{Configured:Installed}, WSApplicationMetaDat
| aAdapterEJB21{Configured:Installed}
| WSNativeDeploymentAspectInstallerPreJSE -> WSNativeContextPropertiesDeploymentAspect{Configured:Installed}, WSDeploymentAspectManagerPreJSE{Configured
| :Installed}, WSDeploymentAspectInstallerPreJSE{Create:Instantiated}, WSDeploymentAspectInstallerPreJSE{Start:Instantiated}
| WSWebAppGeneratorDeploymentAspect -> WSSecurityHandlerEJB21{Configured:Installed}, WSSecurityHandlerEJB3{Configured:**ERROR**}
| WSDeploymentAspectInstallerPostJSE -> WSDeploymentAspectManagerPostJSE{Configured:Installed}, WSEndpointLifecycleDeploymentAspect{Configured:Installed
| }, WSRuntimeLoaderDeploymentAspect{Configured:Installed}, WSDeploymentAspectInstallerPreJSE{Create:Instantiated}, WSDeploymentAspectInstallerPreJSE{St
| art:Instantiated}
| WSNativeDeploymentAspectInstallerEJB -> WSNativeContextPropertiesDeploymentAspect{Configured:Installed}, WSNativeEagerInitializeDeploymentAspect{Confi
| gured:Installed}, WSNativeEndpointHandlerDeploymentAspect{Configured:Installed}, WSNativeEndpointRecordProcessorDeploymentAspect{Configured:Installed}
| , WSNativeEventingDeploymentAspect{Configured:Installed}, WSNativePublishContractDeploymentAspect{Configured:Installed}, WSNativeServiceEndpointInvoke
| rDeploymentAspect{Configured:Installed}, WSNativeRMDeploymentAspect{Configured:Installed}, WSNativeUnifiedMetaDataDeploymentAspect{Configured:Installe
| d}, WSJAXBIntroDeploymentAspect{Configured:Installed}, WSDeploymentAspectManagerEJB{Configured:Installed}, WSDeploymentAspectInstallerEJB{Create:Insta
| ntiated}, WSDeploymentAspectInstallerEJB{Start:Instantiated}
| WSDeploymentAspectInstallerEJB -> WSContainerMetaDataDeploymentAspect{Configured:Instantiated}, WSContextRootDeploymentAspect{Configured:Installed}, W
| SEndpointAddressDeploymentAspect{Configured:Installed}, WSEndpointHandlerDeploymentAspect{Configured:Installed}, WSEndpointLifecycleDeploymentAspect{C
| onfigured:Installed}, WSEndpointMetricsDeploymentAspect{Configured:Installed}, WSEndpointNameDeploymentAspect{Configured:Installed}, WSEndpointRegistr
| yDeploymentAspect{Configured:Installed}, WSRuntimeLoaderDeploymentAspect{Configured:Installed}, WSURLPatternDeploymentAspect{Configured:Installed}, WS
| WebAppDeploymentAspect{Configured:Installed}, WSWebAppGeneratorDeploymentAspect{Configured:Instantiated}, WSDeploymentAspectManagerEJB{Configured:Inst
| alled}
| WSDeploymentAspectInstallerEndpointAPI -> WSDeploymentAspectManagerEndpointAPI{Configured:Installed}, WSEndpointAPIDeploymentAspect{Configured:Install
| ed}, WSEndpointAddressDeploymentAspect{Configured:Installed}, WSEndpointHandlerDeploymentAspect{Configured:Installed}, WSEndpointLifecycleDeploymentAs
| pect{Configured:Installed}, WSEndpointMetricsDeploymentAspect{Configured:Installed}, WSEndpointNameDeploymentAspect{Configured:Installed}, WSEndpointR
| egistryDeploymentAspect{Configured:Installed}, WSWebAppDeploymentAspect{Configured:Installed}, WSWebAppGeneratorDeploymentAspect{Configured:Instantiat
| ed}
| WSNativeDeploymentAspectInstallerEndpointAPI -> WSNativeContextPropertiesDeploymentAspect{Configured:Installed}, WSNativeEagerInitializeDeploymentAspe
| ct{Configured:Installed}, WSNativeEndpointHandlerDeploymentAspect{Configured:Installed}, WSNativeEndpointRecordProcessorDeploymentAspect{Configured:In
| stalled}, WSNativeEventingDeploymentAspect{Configured:Installed}, WSNativePublishContractDeploymentAspect{Configured:Installed}, WSNativeServiceEndpoi
| ntInvokerDeploymentAspect{Configured:Installed}, WSNativeRMDeploymentAspect{Configured:Installed}, WSNativeUnifiedMetaDataDeploymentAspect{Configured:
| Installed}, WSJAXBIntroDeploymentAspect{Configured:Installed}, WSDeploymentAspectManagerEndpointAPI{Configured:Installed}, WSDeploymentAspectInstaller
| EndpointAPI{Create:Instantiated}, WSDeploymentAspectInstallerEndpointAPI{Start:Instantiated}
| WSNativeDeploymentAspectInstallerPostJSE -> WSNativeEndpointHandlerDeploymentAspect{Configured:Installed}, WSNativeEndpointRecordProcessorDeploymentAs
| pect{Configured:Installed}, WSNativeEventingDeploymentAspect{Configured:Installed}, WSNativePublishContractDeploymentAspect{Configured:Installed}, WSN
| ativeServiceEndpointInvokerDeploymentAspect{Configured:Installed}, WSNativeRMDeploymentAspect{Configured:Installed}, WSNativeUnifiedMetaDataDeployment
| Aspect{Configured:Installed}, WSNativeEagerInitializeDeploymentAspect{Configured:Installed}, WSJAXBIntroDeploymentAspect{Configured:Installed}, WSDepl
| oymentAspectManagerPostJSE{Configured:Installed}, WSDeploymentAspectInstallerPostJSE{Create:Configured}, WSDeploymentAspectInstallerPostJSE{Start:Conf
| igured}
| WSDeploymentAspectInstallerPreJSE -> WSContainerMetaDataDeploymentAspect{Configured:Instantiated}, WSContextRootDeploymentAspect{Configured:Installed}
| , WSEndpointAddressDeploymentAspect{Configured:Installed}, WSEndpointHandlerDeploymentAspect{Configured:Installed}, WSEndpointMetricsDeploymentAspect{
| Configured:Installed}, WSEndpointNameDeploymentAspect{Configured:Installed}, WSEndpointRegistryDeploymentAspect{Configured:Installed}, WSModifyWebMeta
| DataDeploymentAspect{Configured:Installed}, WSURLPatternDeploymentAspect{Configured:Installed}, WSDeploymentAspectManagerPreJSE{Configured:Installed}
| )
|
| ObjectName: portal:service=PortletInvoker,type=Federating
| State: NOTYETINSTALLED
| Depends On Me:
| portal:service=Management,type=PortletDiscoveryManagement,name=Default
|
| ObjectName: jboss.ejb3:service=EJB3Deployer
| State: NOTYETINSTALLED
| Depends On Me:
| jboss.ws:service=DeployerInterceptorEJB3
|
| ObjectName: portal:urlFactory=Delegating
| State: NOTYETINSTALLED
| Depends On Me:
| portal:urlFactory=Configurator
| portal:urlFactory=CMSObject
| portal:urlFactory=IdentityUI
|
| ObjectName: portal:service=InstanceContainerContext
| State: NOTYETINSTALLED
| Depends On Me:
| portal.management:service=Management,type=Portal,name=Default
|
| ObjectName: portal:service=Module,type=IdentityServiceController
| State: NOTYETINSTALLED
| Depends On Me:
| portal:service=AuthorizationProvider,type=cms
| portal:service=Interceptor,type=Cms,name=ACL
| portal:service=ApprovePublish,type=Workflow
| portal:service=IdentityUIConfigurationService,type=IdentityUI
| portal:service=IdentityUserManagementService,type=IdentityUI
| portal.management:service=Management,type=Identity,name=Default
|
| ObjectName: portal:service=InterceptorStackFactory,type=Instance
| State: NOTYETINSTALLED
| Depends On Me:
| portal:service=InterceptorRegistration,type=Portlet,name=PortletContainerManagement
|
Each assistance would be welcome, please.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260482#4260482
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260482
16 years, 8 months
[jBPM Users] - JBPM and JBPM-BPEL version
by stmod
Hello to all,
I have a JBOSS 4.2.2GA up and running.
A part I have not directly deployed and that is totally out of my control, uses this two jar for jbpm (put in jboss/server/default/lib)
jbpm-3.1.2.jar
jbpm-identity-3.1.2.jar
The db used is Hypersonic.
I would like to add to Jboss a Jbpm-bpel (I tried both jbpm-bpel 1.1GA and jbpm-bpel 1.1.1), but when i tried to install it following the instructions I got several errors realted to jbpm context probably due to conflicts in JBPM version.
With jbpm-bpel 1.1.1 I have exceptions as soon as i try to deploy the jbpm-bpel.ear
With jbpm-bpel 1.1GA I do not have any exception when i deploy the ear, but I got exceptions when I try to use any of the link on the jbpm-bpel console.
I cannot change the jar already used in the Jboss, so my question is
which version of Jbpm-bpel I have to use for not changing JBPM jars?
thanks in advance
stmod
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260477#4260477
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260477
16 years, 8 months
[JBoss OSGi Users] - JBossOSGi vs. Pax-Runner/Pax-Exam
by thomas.diesler＠jboss.com
Kevin sais:
anonymous wrote :
| Congrats on the release, I am looking forward to playing with it.
|
| Can you explain the benefits of our own integration over something like the pax-runner/pax-exam framework? I have been using those for OSGi work and am very happy with it, what functionality do you provide above and beyond theirs?
|
| Do you plan on supporting Knoplerfish?
|
pax-runner/pax-exam is probably not much different to jboss osgi runtime/husky as long as you use the felix or equinox, in an embedded scenario.
The main objective of JBoss OSGi however is to bring OSGi functionality to the JBoss Application server. That JBoss OSGi has its own standalone runtime and can be bootstrapped embedded in you application is a by-product if you like.
With Beta4 you also get the first Alpha release of our own OSGi Framework implementation that is based on the JBoss Microcontainer.
Q: Why would we want to write our own OSGi Framework, if there are good open source alternatives out there?
A: Because eventually we want to bring added value to our customers that they can leverage the OSGi technology and at the same time talk to existing services that are deployed on JBoss. We would like to access OSGi services from EJB3, MCBeans, MBeans, WebBeans, and vica versa. This type of cross-component model integration would not be possible if we deployed a 3rd party framework like Felix or Equinox into JBoss.
For details on the various runtime model see: http://jbossosgi.blogspot.com/2009/06/jboss-osgi-runtime-as-integration.html
Because JBoss integration is at the heart of everything I do, I needed to find a way to write a plain JUnit4 test case and run that against multiple OSGi Frameworks in embedded mode as well as integrated in JBoss.
So what I actually do in Hudson is:
#1 build the installer
#2 auto execute the installer with a choice of container/framework
#3 run the test suite against that installation using a given jdk
I that way I can be sure that every functionality I ship and advertise actually runs in JBoss. Pax-Exam does not support the notion of remote OSGi Framework AFAIK.
If you'd like to read more on Husky, have a look at
http://jbossosgi.blogspot.com/2009/10/osgi-unit-testing.html
Here is the set of requirements that I had
# The solution MUST support plain JUnit4 POJO test cases
# There SHOULD be no requirement to extend a specific test base class
# There MUST be no requirement on a specific test runner
# There SHOULD be a minimum test framework leakage into the test case
# The test framework MUST support embedded and remote OSGi Runtimes with no change required to the test
# The same test case MUST be executable from outside as well as from within the OSGi Framework
# There SHOULD be a pluggable communication layer from the test runner to the OSGi Framework
# The test framework MUST NOT depend on OSGi Framework specific features
# There MUST be no automated creation of test bundles required by the test framework
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260471#4260471
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260471
16 years, 8 months