[Datasource Configuration] New message: "Re: How to configure Oracle with my application in jboss 5.0"
by Anand Kumar
User development,
A new message was posted in the thread "How to configure Oracle with my application in jboss 5.0":
http://community.jboss.org/message/528091#528091
Author : Anand Kumar
Profile : http://community.jboss.org/people/akstifr
Message:
--------------------------------------------------------------
Thanks once again for your reply
Here are the files which u have requested for...
The contents of jboss-web.xml is
<jboss-web>
<resource-ref>
<res-ref-name>jdbc/OracleDS</res-ref-name>
<jndi-name>java:jdbc/OracleDS</jndi-name>
</resource-ref>
</jboss-web>
and the contents of web.xml is:
<resource-ref>
<res-ref-name>jdbc/OracleDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
There are some more security-constraint also which i have already specified previously in the post here.
The contents of OracleDS.xm file are:
<?xml version="1.0" encoding="UTF-8"?>
<!-- ===================================================================== -->
<!-- -->
<!-- JBoss Server Configuration -->
<!-- -->
<!-- ===================================================================== -->
<!-- $Id: oracle-ds.xml,v 1.6 2004/09/15 14:37:40 loubyansky Exp $ -->
<!-- ==================================================================== -->
<!-- Datasource config for Oracle originally from Steven Coy -->
<!-- ==================================================================== -->
<datasources>
<local-tx-datasource>
<jndi-name>jdbc/OracleDS</jndi-name>
<connection-url>jdbc:oracle:thin:@xxx.yyy.zzz.www:1521:dbatest</connection-url>
<!--
See on WIKI page below how to use Oracle's thin JDBC driver to connect with enterprise RAC.
-->
<!--
Here are a couple of the possible OCI configurations.
For more information, see http://otn.oracle.com/docs/products/oracle9i/doc_library/release2/java.92...
<connection-url>jdbc:oracle:oci:@youroracle-tns-name</connection-url>
or
<connection-url>jdbc:oracle:oci:@(description=(address=(host=youroraclehost)(protocol=tcp)(port=1521))(connect_data=(SERVICE_NAME=yourservicename)))</connection-url>
Clearly, its better to have TNS set up properly.
-->
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<user-name>xxxxx</user-name>
<password>yyyyy</password>
<min-pool-size>5</min-pool-size>
<max-pool-size>100</max-pool-size>
<!-- Uses the pingDatabase method to check a connection is still valid before handing it out from the pool -->
<!--valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker</valid-connection-checker-class-name-->
<!-- Checks the Oracle error codes and messages for fatal errors -->
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
<!-- sql to call when connection is created
<new-connection-sql>some arbitrary sql</new-connection-sql>
-->
<!-- sql to call on an existing pooled connection when it is obtained from pool - the OracleValidConnectionChecker is prefered
<check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
-->
<!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
<metadata>
<type-mapping>Oracle9i</type-mapping>
</metadata>
</local-tx-datasource>
</datasources>
Now what should i have to do further ???
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/528091#528091
16 years, 2 months
[Beginner's Corner] New message: "Get an error when trying overwrite war from eclipse"
by Camron Rushin
User development,
A new message was posted in the thread "Get an error when trying overwrite war from eclipse":
http://community.jboss.org/message/528083#528083
Author : Camron Rushin
Profile : http://community.jboss.org/people/iamcootis
Message:
--------------------------------------------------------------
I'm trying to overwrite a war from eclipse, but I always get this error. The war deploys correctly the first time, but then gives an error the 2nd time. I'm using JBOSS 5.1.0
Here is the error:
org.eclipse.core.runtime.CoreException: Extended Operation failure: org.eclipse.jst.j2ee.internal.web.archive.operations.WebComponentExportOperation
at org.eclipse.wst.common.frameworks.internal.datamodel.ui.DataModelWizard.performFinish(DataModelWizard.java:190)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:742)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:373)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.internal.handlers.WizardHandler$Export.executeHandler(WizardHandler.java:97)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:273)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:281)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:247)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
at org.eclipse.ui.internal.actions.CommandAction.run(CommandAction.java:171)
at org.eclipse.ui.actions.ExportResourcesAction.run(ExportResourcesAction.java:116)
at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:168)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2384)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2348)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:490)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
Caused by: org.eclipse.core.commands.ExecutionException: Error exportingWar File
at org.eclipse.jst.j2ee.internal.archive.operations.J2EEArtifactExportOperation.execute(J2EEArtifactExportOperation.java:128)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl$1.run(DataModelPausibleOperationImpl.java:376)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:401)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:352)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.doExecute(DataModelPausibleOperationImpl.java:242)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.executeImpl(DataModelPausibleOperationImpl.java:214)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.cacheThreadAndContinue(DataModelPausibleOperationImpl.java:89)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.execute(DataModelPausibleOperationImpl.java:202)
at org.eclipse.wst.common.frameworks.internal.datamodel.ui.DataModelWizard$1$CatchThrowableRunnableWithProgress.run(DataModelWizard.java:219)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: org.eclipse.jst.j2ee.commonarchivecore.internal.exception.SaveFailureException: IWAE0017E Unable to replace original archive: C:\JBOSS\jboss-5.1.0.GA\server\default\deploy\SoyBombs.war
at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ArchiveImpl.cleanupAfterTempSave(ArchiveImpl.java:322)
at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ArchiveImpl.saveAsNoReopen(ArchiveImpl.java:1182)
at org.eclipse.jst.j2ee.internal.web.archive.operations.WebComponentExportOperation.export(WebComponentExportOperation.java:54)
at org.eclipse.jst.j2ee.internal.archive.operations.J2EEArtifactExportOperation.execute(J2EEArtifactExportOperation.java:120)
... 10 more
Contains: Extended Operation failure: org.eclipse.jst.j2ee.internal.web.archive.operations.WebComponentExportOperation
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/528083#528083
16 years, 2 months
[JBoss Remoting] New message: "Possible to define client truststore on server when using sslsocket transport?"
by Ben Schofield
User development,
A new message was posted in the thread "Possible to define client truststore on server when using sslsocket transport?":
http://community.jboss.org/message/528080#528080
Author : Ben Schofield
Profile : http://community.jboss.org/people/dbschofield
Message:
--------------------------------------------------------------
I am using JBoss Remoting 2.5.2 with JBoss EAP 5.0. When using the sslsocket transport, is it possible to configure the location of the truststore used by the remoting client during the ssl handshake? From what I have demonstrated to myself already the client will use the cacerts file or the truststore specified by the system property javax.net.ssl.trustStore. Instead of using either of these truststores I would like to define on the server side which truststore (and truststore password) the client should use. Is this possible?
I have configured both the socketFactory and serverSocketFactory properties of the Connector (xml bean configuration below). I anticipated that the client would honor the socketFacotory setting but this doesn't seem to be the case. Did some research and found the following in the remoting guide pdf.
5.7.4. Client side configuration from the JBoss Application Server
As described in sections Declarative configuration: MBeans and Declarative configuration: POJOs, the declarative
xml files used by the Application Server can be used to configure the client by way of the parameters included in
the InvokerLocator. However, a peculiarity in the way socket factories are created on the client restricts the parameters
taken into consideration to those passed in the configuration map passed to the
org.jboss.remoting.Client constructor. The following two parameters, introduced in releases 2.4.0.SP1 and
2.5.2, respectively, eliminate that restriction.
org.jboss.remoting.Remoting.SOCKET_FACTORY_NAME (actual value is 'socketFactory') - key for giving
the name of the socket factory class to be used by clients.
org.jboss.remoting.Remoting.USE_ALL_SOCKET_FACTORY_PARAMS (actual value is 'useAllSocketFactoryParams')
- key for indicating that all socket factory parameters in the InvokerLocator should be used by clients.
Note that the parameter org.jboss.remoting.Remoting.CONFIG_OVERRIDES_LOCATOR (actual value "configOverridesLocator"),
described in section org.jboss.remoting.Remoting, is also relevant.
I am not 100% these settings are what I need but would like to try them out. Unfortunately I am not sure how to set these in a JBoss MicroContainer bean xml file. Any insight on how to do this would be appreciated.
<deployment xmlns="urn:jboss:bean-deployer:2.0">
<!-- We don't want the AOPDependencyBuilder -->
<annotation>@org.jboss.aop.microcontainer.annotations.DisableAOP</annotation>
<!--
JBoss Remoting Connector
Note: Bean Name "org.jboss.ejb3.RemotingConnector" is used
as a lookup value; alter only after checking java references
to this key.
-->
<bean name="org.jboss.ejb3.RemotingConnector"
class="org.jboss.remoting.transport.Connector">
<property name="invokerLocator">
<value-factory bean="ServiceBindingManager"
method="getStringBinding">
<parameter>
jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3
</parameter>
<parameter>
<null />
</parameter>
<parameter>sslsocket://${jboss.bind.address}:${port}</parameter>
<parameter>
<null />
</parameter>
<parameter>3873</parameter>
</value-factory>
</property>
<property name="serverConfiguration">
<inject bean="ServerConfiguration" />
</property>
<property name="serverSocketFactory">
<inject bean="sslServerSocketFactory" />
</property>
<property name="socketFactory">
<inject bean="sslSocketFactory" />
</property>
</bean>
<bean name="sslServerSocketFactory" class="org.jboss.security.ssl.DomainServerSocketFactory">
<constructor>
<!-- defines the keystore to use -->
<parameter><inject bean="jboss.security:service=JAAS-Security-Domain"/></parameter>
</constructor>
</bean>
<bean name="sslSocketFactory" class="org.jboss.security.ssl.DomainSocketFactory">
<constructor>
<!-- hopefully defines the truststore configured in the injected JaasSecurityDomain to be used by the client -->
<parameter><inject bean="jboss.security:service=JAAS-Security-Domain"/></parameter>
</constructor>
</bean>
<!-- Remoting Server Configuration -->
<bean name="ServerConfiguration"
class="org.jboss.remoting.ServerConfiguration">
<property name="invocationHandlers">
<map keyClass="java.lang.String" valueClass="java.lang.String">
<entry>
<key>AOP</key>
<value>
org.jboss.aspects.remoting.AOPRemotingInvocationHandler
</value>
</entry>
</map>
</property>
</bean>
</deployment>
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/528080#528080
16 years, 2 months
[jBPM] New message: "Re: do you recomend jBPM 4.x for production use?"
by Javier Alperte
User development,
A new message was posted in the thread "do you recomend jBPM 4.x for production use?":
http://community.jboss.org/message/528077#528077
Author : Javier Alperte
Profile : http://community.jboss.org/people/xalperte
Message:
--------------------------------------------------------------
We are using the following configuration:
* JBoss AS 4.2.3
* JBoss Portal 2.7.2
* Seam 2.2.0, but jbpm-seam integration is not important for us. We do not use the jBPM-Seam functionality, we do by ourselves because it didn't exists support for portlet environment at the moment we integrated the 3.2.x version.
* MySQL 5.1.x
I'm attaching a zip with the model of the booking process. The process is composed by a Main Process and 7 Subprocesses.
As you can see in the diagrams, we are using the following bpm functionalities:
* Swim lanes
* Main Process Global Event Listeners (start-end) to free the rooms when the process ends abnormally or is canceled.
* Process-SubProcess communication. Main process waits until sub-processes ends.
* Task and Wait states with transition timers.
* The Task Nodes creates only 1 task, we do not need to create more than one task instance per node.
* Email nodes to send notifications to the users when needed.
* We have some Wait states that are waiting for a signal for external events like Payment Gateway and Insurance Services responses.
One think that I do not know if it will be available soon is the variable history support.
I have some questions and concerns but I will post new topics for them.
Thanks
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/528077#528077
16 years, 2 months