[JBoss JIRA] Created: (JBAS-3409) Deploy a .ear file with no deployment descriptor(META-INF/application.xml)
by Rajesh Rajasekaran (JIRA)
Deploy a .ear file with no deployment descriptor(META-INF/application.xml)
--------------------------------------------------------------------------
Key: JBAS-3409
URL: http://jira.jboss.com/jira/browse/JBAS-3409
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Deployment services
Affects Versions: JBossAS-5.0.0.Beta
Reporter: Rajesh Rajasekaran
Assigned To: Dimitris Andreadis
Priority: Blocker
Fix For: JBossAS-5.0.0.Beta
The javaee5 spec (EE8.4.2 Deploying a Java EE application) has a set of rules to deploy an application .ear file which does not have a deployment descriptor. (descriptorMETA-INF/application.xml)
Currently we get a RunTimeException when the application.xml is not found.
org.jboss.deployment.spi.DeploymentManagerImpl@16b8f8eb
java.lang.RuntimeException: cannot obtain module type
07-21-2006 13:12:57: Harness - Deployment of app(s) from: /home/rrajasekaran/tck5/javaeetck/dist/com/sun/ts/tests/samples/javamail/ee/transport failed!
at org.jboss.deployment.spi.DeploymentManagerImpl.createDeployment(DeploymentManagerImpl.java:481)
at org.jboss.deployment.spi.DeploymentManagerImpl.distribute(DeploymentManagerImpl.java:348)
The moduleType in org.jboss.deployment.spi.DeploymentManageImpl.createDeployment() is not set when the application.xml is not set.
All CTS tests deploy .ear files with no application.xml
I ve made this issue a blocker because unless this is fixed we would be unable to run the cts tests.
--
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, 6 months
[JBoss JIRA] Created: (JBAS-3755) Expose all SSL socket factory settings via properties or attributes for UIL2
by Scott M Stark (JIRA)
Expose all SSL socket factory settings via properties or attributes for UIL2
----------------------------------------------------------------------------
Key: JBAS-3755
URL: http://jira.jboss.com/jira/browse/JBAS-3755
Project: JBoss Application Server
Issue Type: Support Patch
Security Level: Public (Everyone can see)
Components: JMS service, Security
Affects Versions: JBossAS-4.0.4.GA
Reporter: Scott M Stark
Assigned To: Adrian Brock
Currently the ssl socket factories don't have any notion of picking up settings like the enabled cipher suites from system properties or the security domain in the case of the org.jboss.security.ssl.DomainSocketFactory. We should be able to set any JSSE SSLSocketFactory setting from these external values by injecting a fully configured socket factory:
<mbean code="org.jboss.mq.il.uil2.UILServerILService"
name="jboss.mq:service=InvocationLayer,type=SSLUIL2">
...
<attribute name="ServerSocketFactoryBean">
attributeClass="org.jboss.security.ssl.DomainServerSocketFactory"
serialDataType="javaBean">
<property name="bindAddress">${jboss.bind.address}</property>
<property name="securityDomain">java:/jaas/rmi-ssl</property>
<property name="wantsClientAuth">true</property>
<property name="needsClientAuth">true</property>
<property name="CiperSuites">TLS_DHE_DSS_WITH_AES_128_CBC_SHA</property>
<property name="Protocols">SSLv2Hello,SSLv3,TLSv1</property>
</attribute>
</mbean>
--
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, 6 months
[JBoss JIRA] Updated: (JBAS-2073) Remove xalan.jar from ./lib/endorsed
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2073?page=all ]
Dimitris Andreadis updated JBAS-2073:
-------------------------------------
Fix Version/s: JBossAS-5.0.0.Beta2
(was: JBossAS-5.0.0.Beta1)
> Remove xalan.jar from ./lib/endorsed
> ------------------------------------
>
> Key: JBAS-2073
> URL: http://jira.jboss.com/jira/browse/JBAS-2073
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Other
> Affects Versions: JBossAS-4.0.3RC1
> Reporter: Dimitris Andreadis
> Assigned To: Dimitris Andreadis
> Fix For: JBossAS-5.0.0.Beta2
>
>
> In 4.0.x/HEAD we have:
> lib/endorsed/xalan.jar
> While in 3.2.x we have:
> server/default/lib/xalan.jar
> server/all/lib/xalan.jar
> The 3.2.x approach seems more correct, since xalan.jar contains org.apache.* stuff, not any of the following "endosed" packages:
> org.w3c.dom
> org.xml.sax
> org.xml.sax.ext
> org.xml.sax.helpers
> It should be moved out from the bootstrap libs to the default/all lib dirs.
--
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, 6 months
[JBoss JIRA] Created: (JBAS-3850) One to many relationships throwing a Excetion
by Santiago de la Nava Santos (JIRA)
One to many relationships throwing a Excetion
---------------------------------------------
Key: JBAS-3850
URL: http://jira.jboss.com/jira/browse/JBAS-3850
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: CMP service
Affects Versions: JBossAS-4.0.5.GA
Environment: Windows XP, JBoss 4.0.5GA, JBoss 4.0.4GA and JBoss 3.2.8.SP1
AMD Sempron 3000+
2.00 GHz
512 Mb RAM
Reporter: Santiago de la Nava Santos
Assigned To: Alexey Loubyansky
Hi all,
I'm having a similar problem with one to many relationship, CMP persistence and EJB 2 specification. I have tested the problem at versions 3.2.8.SP1, 4.0.4.GA and 4.0.5.GA, and they all throws the same Exception. I have an ExperimentEJB that is related to many ConfigurationEJB. When I try to add the ConfigurationEJB Collection to ExperimentEJB, the system throws this exception:
11:07:01,323 ERROR [LogInterceptor] RuntimeException in method: public abstract void softiam.services.ejbs.experiment.Ex
periment.setConfiguration(java.util.Collection) throws java.rmi.RemoteException:
java.lang.NullPointerException
at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.getRelatedPrimaryKey(JDBCCMRFieldBridge.java:1862)
at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.setInstanceValue(JDBCCMRFieldBridge.java:857)
at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.setValue(JDBCCMRFieldBridge.java:723)
at org.jboss.ejb.plugins.cmp.bridge.EntityBridgeInvocationHandler$FieldSetInvoker.invoke(EntityBridgeInvocationH
andler.java:170)
at org.jboss.ejb.plugins.cmp.bridge.EntityBridgeInvocationHandler.invoke(EntityBridgeInvocationHandler.java:105)
at org.jboss.proxy.compiler.Runtime.invoke(Runtime.java:76)
at softiam.services.ejbs.experiment.ExperimentEJB$Proxy.setConfiguration(<generated>)
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.jboss.invocation.Invocation.performCall(Invocation.java:359)
at org.jboss.ejb.EntityContainer$ContainerInterceptor.invoke(EntityContainer.java:1187)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCRelationInterceptor.invoke(JDBCRelationInterceptor.java:87)
at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invoke(EntitySynchronizationInterceptor.java:284)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:158)
at org.jboss.ejb.plugins.EntityReentranceInterceptor.invoke(EntityReentranceInterceptor.java:126)
at org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityInstanceInterceptor.java:276)
at org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor.java:104)
at org.jboss.ejb.plugins.EntityCreationInterceptor.invoke(EntityCreationInterceptor.java:68)
at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:350)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:136)
at org.jboss.ejb.EntityContainer.internalInvoke(EntityContainer.java:527)
at org.jboss.ejb.Container.invoke(Container.java:954)
at sun.reflect.GeneratedMethodAccessor79.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.invocation.local.LocalInvoker$MBeanServerAction.invoke(LocalInvoker.java:169)
at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:118)
at org.jboss.invocation.InvokerInterceptor.invokeLocal(InvokerInterceptor.java:209)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:195)
at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61)
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
at org.jboss.proxy.ejb.EntityInterceptor.invoke(EntityInterceptor.java:112)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
at $Proxy57.setConfiguration(Unknown Source)
at softiam.services.ui.gwtui.server.SoftIAMServiceImpl.experimentConfigurationSet(SoftIAMServiceImpl.java:212)
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 com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:260)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost(RemoteServiceServlet.java:147)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java
:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595)
I have checked all the deployment descriptors and are ok:
* ejb-jar.xml ------------------------------------------------------------------------------------------------------------------------------------------------------------------->
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
<ejb-jar>
<display-name>SoftiamEJBs</display-name>
<enterprise-beans>
<session>
<display-name>SessionControlEJB</display-name>
<ejb-name>SessionControlEJB</ejb-name>
<home>softiam.services.ejbs.sessioncontrol.SessionControlHome</home>
<remote>softiam.services.ejbs.sessioncontrol.SessionControl</remote>
<ejb-class>softiam.services.ejbs.sessioncontrol.SessionControlEJB</ejb-class>
<session-type>Stateful</session-type>
<transaction-type>Container</transaction-type>
</session>
<entity>
<ejb-name>ExperimentEJB</ejb-name>
<home>softiam.services.ejbs.experiment.ExperimentHome</home>
<remote>softiam.services.ejbs.experiment.Experiment</remote>
<ejb-class>softiam.services.ejbs.experiment.ExperimentEJB</ejb-class>
<abstract-schema-name>experiments</abstract-schema-name>
<prim-key-class>java.lang.Long</prim-key-class>
<primkey-field>experimentId</primkey-field>
<reentrant>True</reentrant>
<cmp-field>
<field-name>experimentId</field-name>
</cmp-field>
<cmp-field>
<field-name>user</field-name>
</cmp-field>
<cmp-field>
<field-name>coupling</field-name>
</cmp-field>
<cmp-field>
<field-name>state</field-name>
</cmp-field>
<cmp-field>
<field-name>experimentIndex</field-name>
</cmp-field>
<cmp-field>
<field-name>name</field-name>
</cmp-field>
<cmp-field>
<field-name>description</field-name>
</cmp-field>
<cmp-field>
<field-name>creationTime</field-name>
</cmp-field>
<cmp-field>
<field-name>operationTime</field-name>
</cmp-field>
<query>
<query-method>
<method-name>findExperiments</method-name>
<method-params>
<method-param>java.lang.String</method-param>
</method-params>
</query-method>
<ejb-ql>
SELECT OBJECT(e)
FROM experiments e
WHERE e.user=?1
</ejb-ql>
</query>
<query>
<query-method>
<method-name>findExperiments</method-name>
<method-params>
<method-param>java.lang.String</method-param>
<method-param>java.lang.String</method-param>
</method-params>
</query-method>
<ejb-ql>
SELECT OBJECT(e)
FROM experiments e
WHERE e.user=?1 AND e.coupling=?2
</ejb-ql>
</query>
<query>
<query-method>
<method-name>findRunningExperiments</method-name>
<method-params></method-params>
</query-method>
<ejb-ql>
SELECT OBJECT(e)
FROM experiments e
WHERE e.state=1
</ejb-ql>
</query>
<query>
<query-method>
<method-name>findNotStartedExperiments</method-name>
<method-params></method-params>
</query-method>
<ejb-ql>
SELECT OBJECT(e)
FROM experiments e
WHERE e.state=0
</ejb-ql>
</query>
<persistence-type>Container</persistence-type>
</entity>
<entity>
<ejb-name>ConfigurationEJB</ejb-name>
<home>softiam.services.ejbs.configuration.ConfigurationHome</home>
<remote>softiam.services.ejbs.configuration.Configuration</remote>
<ejb-class>softiam.services.ejbs.configuration.ConfigurationEJB</ejb-class>
<abstract-schema-name>configurations</abstract-schema-name>
<prim-key-class>softiam.services.ejbs.configuration.ConfigurationPK</prim-key-class>
<reentrant>True</reentrant>
<cmp-field>
<field-name>experimentId</field-name>
</cmp-field>
<cmp-field>
<field-name>coupling</field-name>
</cmp-field>
<cmp-field>
<field-name>module</field-name>
</cmp-field>
<cmp-field>
<field-name>parameter</field-name>
</cmp-field>
<cmp-field>
<field-name>type</field-name>
</cmp-field>
<cmp-field>
<field-name>singleValue</field-name>
</cmp-field>
<cmp-field>
<field-name>rangeInitial</field-name>
</cmp-field>
<cmp-field>
<field-name>rangeEnd</field-name>
</cmp-field>
<cmp-field>
<field-name>rangeIncrement</field-name>
</cmp-field>
<cmp-field>
<field-name>rangeCombine</field-name>
</cmp-field>
<cmp-field>
<field-name>multipleValues</field-name>
</cmp-field>
<cmp-field>
<field-name>multipleCombine</field-name>
</cmp-field>
<persistence-type>Container</persistence-type>
</entity>
</enterprise-beans>
<relationships>
<ejb-relation>
<ejb-relation-name>experiment-configuration</ejb-relation-name>
<ejb-relationship-role>
<description>experiment</description>
<ejb-relationship-role-name>ExperimentRole</ejb-relationship-role-name>
<multiplicity>One</multiplicity>
<relationship-role-source>
<description>experiment</description>
<ejb-name>ExperimentEJB</ejb-name>
</relationship-role-source>
<cmr-field>
<description>configuration</description>
<cmr-field-name>configuration</cmr-field-name>
<cmr-field-type>java.util.Collection</cmr-field-type>
</cmr-field>
</ejb-relationship-role>
<ejb-relationship-role>
<description>configuration</description>
<ejb-relationship-role-name>ConfigurationRole</ejb-relationship-role-name>
<multiplicity>Many</multiplicity>
<cascade-delete />
<relationship-role-source>
<description>configuration</description>
<ejb-name>ConfigurationEJB</ejb-name>
</relationship-role-source>
</ejb-relationship-role>
</ejb-relation>
</relationships>
</ejb-jar>
jboss.xml --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------->
<?xml version="1.0"?>
<!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 4.0//EN"
"http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd">
<jboss>
<enterprise-beans>
<session>
<ejb-name>SessionControlEJB</ejb-name>
<jndi-name>SessionControlEJB</jndi-name>
</session>
<entity>
<ejb-name>ExperimentEJB</ejb-name>
<jndi-name>ExperimentEJB</jndi-name>
</entity>
<entity>
<ejb-name>ConfigurationEJB</ejb-name>
<jndi-name>ConfigurationEJB</jndi-name>
</entity>
</enterprise-beans>
<relationships>
<ejb-relation>
<ejb-relation-name>experiment-configuration</ejb-relation-name>
<foreign-key-mapping />
<ejb-relationship-role>
<ejb-relationship-role-name>ExperimentRole</ejb-relationship-role-name>
<key-fields />
</ejb-relationship-role>
<ejb-relationship-role>
<ejb-relationship-role-name>ConfigurationRole</ejb-relationship-role-name>
<key-fields />
</ejb-relationship-role>
</ejb-relation>
</relationships>
</jboss>
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------->
The code that add the data to the relationship is like this:
* This is part of the function that generates the collection for the relationship:
public static Vector generateConfiguration(long experimentId, ConfigurationHome configurationHome,CouplingInfo coupling) throws RemoteException, CreateException{
...
while(it2.hasNext())
{
ParameterInfo parameter=(ParameterInfo)it2.next();
ConfigurationInfo configurationInfo=parameter.getConfigurationInfo();
Configuration config=configurationHome.create(new Long(experimentId),coupling.getName(),module.getName(),parameter.getName());
...
configurations.add(config);
}
return configurations;
}
* This is part of the code that add the collection generated by the previous function:
Experiment exp=(Experiment)session.getAttribute("currentExperiment");
ConfigurationHome configurationHome=this.softIAMInit.getConfigurationHome();
// This is the setter for the relationship
exp.setConfiguration((Collection)(ConfigurationControl.generateConfiguration(experimentId,configurationHome,coupling)));
--
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, 6 months
[JBoss JIRA] Commented: (JBTM-20) Ensure ATS logging capabilities are compatible with JBoss
by Mark Little (JIRA)
[ http://jira.jboss.com/jira/browse/JBTM-20?page=comments#action_12346766 ]
Mark Little commented on JBTM-20:
---------------------------------
It appears that the definition of INFO we use within JBossTS is more appropriate to TRACE when running within JBossAS. Look at adding a mapper from INFO-to-TRACE when running in AS. Should be possible to add another level of indirection (via a logger plugin) that does that and have the plugin used only when running within the application server. That way, we don't adversely affect any existing users of JBossTS who are happy with INFO output.
> Ensure ATS logging capabilities are compatible with JBoss
> ---------------------------------------------------------
>
> Key: JBTM-20
> URL: http://jira.jboss.com/jira/browse/JBTM-20
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: JTA Implementation, JTS Implementation
> Affects Versions: 4.2.2
> Reporter: Mark Little
> Assigned To: Jonathan Halliday
> Priority: Minor
> Fix For: 4.4
>
>
> ATS has its own way of logging errors, warnings, debugging etc. Although it follows JDK 1.4 logging specification (and can use log4j as an implementation), we need to ensure it is compatible with the standard way of logging in the result of JBoss.
--
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, 6 months