[JBoss JIRA] Updated: (JBAS-2644) Revisit the use of the jndi bindings in the tomcat server.xml
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2644?page=all ]
Dimitris Andreadis updated JBAS-2644:
-------------------------------------
Component/s: Web (Tomcat) service
Fix Version/s: JBossAS-4.0.6.CR1
(was: JBossAS-4.0.5.GA)
Assignee: Remy Maucherat
Remy could provide input for this, for the next release.
> Revisit the use of the jndi bindings in the tomcat server.xml
> -------------------------------------------------------------
>
> Key: JBAS-2644
> URL: http://jira.jboss.com/jira/browse/JBAS-2644
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Web (Tomcat) service
> Affects Versions: JBossAS-4.0.3 SP1
> Reporter: Scott M Stark
> Assigned To: Remy Maucherat
> Fix For: JBossAS-4.0.6.CR1
>
>
> We have never supported the declaration of jndi bindings from the tomcat server.xml because we do not use the tomcat jndi service. We should look at whether such bindings just work or can be made to work as a portability aide in moving from standalone tomcat to embedded tomcat.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months
[JBoss JIRA] Created: (JBAS-3638) Extra option for Hibernate MBean to specify which modules should be scanned for hbm files
by Roel Adriaensens (JIRA)
Extra option for Hibernate MBean to specify which modules should be scanned for hbm files
-----------------------------------------------------------------------------------------
Key: JBAS-3638
URL: http://jira.jboss.com/jira/browse/JBAS-3638
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Hibernate service
Affects Versions: JBossAS-4.0.4.GA
Reporter: Roel Adriaensens
Assigned To: Steve Ebersole
We have an ear which contains a set of modules and multiple hibernate session factories (via Hibernate MBean). The complication is that a session factory might need hbm files from multiple modules. This is not possible now since the Hibernate MBean will scan either only the har module or the complete ear.
So it would be nice if the JBoss Hibernate MBean would provide the option to specify which modules (jars) of the ear must be scanned for hbm mapping files.
Now, we can't use the option of having multiple *.har modules in the *.ear, with one *.har for each session factory. We have different projects and each project leads to an artifact (eg. jar, har,sar,...). Some of those projects must use the same session factory, but the mapping files are distributed over multiple artifacts (projects). So it's not possible to have *.har for each of the session factories. Also if we should stick to the *.har, we should split every project into a 'persistence unit' (-> the har) and a 'ejb' jar (which contains the ejb3 session beans etc..). We also don't want to have one project for things that correspond to one session factory. There are different sets of mapping files that are maintained by different teams, but actually belong to the same session factory.
The alternative would be to have a *.ear for each session factory and then turn on the scanning of the entire *.ear.
But to me it seems better to have one *.ear that contains multiple modules and multiple session factories + the option for each session factory to indicate which modules should be scanned for mapping files.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months
Virus intercepted
by MAILER-DAEMON＠lists.jboss.org
A message sent from <MAILER-DAEMON(a)lists.jboss.org> to
<jboss-jira(a)lists.jboss.org>
contained Worm.Mydoom.M and has not been delivered.
19 years, 8 months
Virus intercepted
by MAILER-DAEMON＠lists.jboss.org
A message sent from <MAILER-DAEMON(a)lists.jboss.org> to
<jboss-jira(a)lists.jboss.org>
contained Worm.Mydoom.M and has not been delivered.
19 years, 8 months
Virus intercepted
by MAILER-DAEMON＠lists.jboss.org
A message sent from <MAILER-DAEMON(a)lists.jboss.org> to
<jboss-jira(a)lists.jboss.org>
contained Worm.Mydoom.M and has not been delivered.
19 years, 8 months
[JBoss JIRA] Commented: (JBAS-3343) JCA 1.5 Resource Adapter Config Properties cannot be specified
by Andreas Mueller (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3343?page=comments#action_12343111 ]
Andreas Mueller commented on JBAS-3343:
---------------------------------------
In which release will this issue be fixed?
The fix is very important because no JCA RA can be properly configured except with cracking the rar and overwriting the default props.
> JCA 1.5 Resource Adapter Config Properties cannot be specified
> --------------------------------------------------------------
>
> Key: JBAS-3343
> URL: http://jira.jboss.com/jira/browse/JBAS-3343
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JCA service
> Affects Versions: JBossAS-4.0.4.GA
> Environment: All.
> Reporter: Andreas Mueller
> Assigned To: Weston Price
> Attachments: ra.xml
>
>
> A JCA 1.5 resource adapter might contain config properties in ra.xml. It is not possible in JBoss to override them with -ds.xml file.
> For example, here is an excert of SwiftMQ's intraVM ra.xml:
> <resourceadapter>
> <resourceadapter-class>
> com.swiftmq.connector.v15.ResourceAdapterImpl
> </resourceadapter-class>
> <config-property>
> <config-property-name>ProviderURL</config-property-name>
> <config-property-type>java.lang.String</config-property-type>
> <config-property-value>smqp://intravm/timeout=10000</config-property-value>
> </config-property>
> <config-property>
> <config-property-name>IntraVM</config-property-name>
> <config-property-type>java.lang.Boolean</config-property-type>
> <config-property-value>true</config-property-value>
> </config-property>
> <config-property>
> <config-property-name>DebugMode</config-property-name>
> <config-property-type>java.lang.Boolean</config-property-type>
> <config-property-value>false</config-property-value>
> </config-property>
> <config-property>
> <config-property-name>RouterWorkingDirectory</config-property-name>
> <config-property-type>java.lang.String</config-property-type>
> <config-property-value><swiftmq_dir>/scripts/unix</config-property-value>
> </config-property>
> <config-property>
> <config-property-name>ConfigurationFilename</config-property-name>
> <config-property-type>java.lang.String</config-property-type>
> <config-property-value>../../config/router1/routerconfig.xml</config-property-value>
> </config-property>
> It is not possible to overwrite them during deployment. It is only possible to specify the config properties of the ManagedConnectionFactory in -ds.xml.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months
[JBoss JIRA] Created: (JBAS-3604) 2 failed tests - org.jboss.test.jmx.test.DeployXMBeanUnitTestCase (jrockit)
by Dimitris Andreadis (JIRA)
2 failed tests - org.jboss.test.jmx.test.DeployXMBeanUnitTestCase (jrockit)
---------------------------------------------------------------------------
Key: JBAS-3604
URL: http://jira.jboss.com/jira/browse/JBAS-3604
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: JMX, Test Suite
Environment: Java Version 1.4.2_11
Java Vendor BEA Systems, Inc.
Java VM Name BEA JRockit(R)
Java VM Version R26.4.0-63-63688-1.4.2_11-20060626-2259-linux-ia32
Java VM Info
OS Name Linux
OS Version 2.6.9-34.0.2.ELsmp
OS Arch i386
Reporter: Dimitris Andreadis
Fix For: JBossAS-4.0.5.GA
testPersistentJndiXMBean Error Hello not bound
javax.naming.NameNotFoundException: Hello not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
at org.jboss.naming.NamingService.invoke(NamingService.java:354)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.test.jmx.interceptors.JNDIPersistence.invoke(JNDIPersistence.java:114)
at org.jboss.test.jmx.interceptors.JNDISecurity.invoke(JNDISecurity.java:130)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Lorg.jboss.invocation.Invocation;)Ljava.lang.Object;(Unknown Source)
at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
at $Proxy1.lookup(Ljavax.naming.Name;)Ljava.lang.Object;(Unknown Source)
at org.jboss.test.jmx.test.DeployXMBeanUnitTestCase.testPersistentJndiXMBean(DeployXMBeanUnitTestCase.java:520)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
testSecuredJndiXMBean Failure Was able to invoke secretEcho
junit.framework.AssertionFailedError: Was able to invoke secretEcho
at org.jboss.test.jmx.test.DeployXMBeanUnitTestCase.testSecuredJndiXMBean(DeployXMBeanUnitTestCase.java:459)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months
[JBoss JIRA] Created: (JBAS-3605) test failures org.jboss.test.jmx.test.JMXInvokerUnitTestCase/SecureJMXInvokerUnitTestCase (jrockit)
by Dimitris Andreadis (JIRA)
test failures org.jboss.test.jmx.test.JMXInvokerUnitTestCase/SecureJMXInvokerUnitTestCase (jrockit)
---------------------------------------------------------------------------------------------------
Key: JBAS-3605
URL: http://jira.jboss.com/jira/browse/JBAS-3605
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: JMX, Test Suite
Environment: Java Version 1.4.2_11
Java Vendor BEA Systems, Inc.
Java VM Name BEA JRockit(R)
Java VM Version R26.4.0-63-63688-1.4.2_11-20060626-2259-linux-ia32
Java VM Info
OS Name Linux
OS Version 2.6.9-34.0.2.ELsmp
OS Arch i386
Reporter: Dimitris Andreadis
Fix For: JBossAS-4.0.5.GA
testGetCustom Failure expected:<InitialValue> but was:<changed>
junit.framework.ComparisonFailure: expected:<InitialValue> but was:<changed>
at org.jboss.test.jmx.test.JMXInvokerUnitTestCase.testGetCustom(JMXInvokerUnitTestCase.java:85)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months
