[JBoss JIRA] (AS7-5711) Add resteasy hibernate-validator-provider
by Mathieu Lachance (JIRA)
Mathieu Lachance created AS7-5711:
-------------------------------------
Summary: Add resteasy hibernate-validator-provider
Key: AS7-5711
URL: https://issues.jboss.org/browse/AS7-5711
Project: Application Server 7
Issue Type: Feature Request
Components: REST
Affects Versions: 7.1.3.Final (EAP)
Reporter: Mathieu Lachance
Assignee: Stuart Douglas
the hibernate-validator-provider is not bundled with resteasy.
javax.validation annotations doesn't seem to work as detailed in the forum post.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (AS7-5909) UnsupportedOperationException if a module's resource root defined in jboss-deployment-structure.xml does not exist
by Brad Maxwell (JIRA)
Brad Maxwell created AS7-5909:
---------------------------------
Summary: UnsupportedOperationException if a module's resource root defined in jboss-deployment-structure.xml does not exist
Key: AS7-5909
URL: https://issues.jboss.org/browse/AS7-5909
Project: Application Server 7
Issue Type: Bug
Components: Server
Affects Versions: 7.2.0.Alpha1
Reporter: Brad Maxwell
Assignee: Stuart Douglas
Priority: Minor
Fix For: Open To Community
An empty test.war with this will throw UnsupportedOperationException if a resource-root path is specified that does not exist.
<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
<module name="deployment.example">
<resources>
<resource-root path="../../../../../../../../work/workspace/release/build/classes/main" />
</resources>
</module>
</jboss-deployment-structure>
Here is the exception:
11:56:53,819 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015959: Additional resource root /work/workspace/release/build/classes/main added via jboss-deployment-structure.xml does not exist
11:56:53,821 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.deployment.unit."test.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."test.war".STRUCTURE: JBAS018733: Failed to process phase STRUCTURE of deployment "test.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:126) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_21]
at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_21]
Caused by: java.lang.UnsupportedOperationException
at java.util.Collections$UnmodifiableList$1.remove(Collections.java:1183) [rt.jar:1.6.0_21]
at org.jboss.as.server.deployment.module.descriptor.DeploymentStructureDescriptorParser.deploy(DeploymentStructureDescriptorParser.java:201) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
... 5 more
The issue looks like:
org.jboss.as.server.deployment.module.descriptor.DeploymentStructureDescriptorParser itr.remove() is called, but the additionalModule.getResourceRoots is returning the list as Collections.unmodifiableList.
It looks like if a <deployment> lists resource roots that do not exist, it just logs a warning. So I think the fix is to remove the Collections.unmodifiableList from ModuleStructureSpec, but I'm not sure if there was a reason unmodifiableList was added.
final ListIterator<ResourceRoot> itr = additionalModule.getResourceRoots().listIterator();
while (itr.hasNext()) {
final ResourceRoot resourceRoot = itr.next();
if(!resourceRoot.getRoot().exists()) {
ServerLogger.DEPLOYMENT_LOGGER.additionalResourceRootDoesNotExist(resourceRoot.getRoot().getPathName());
itr.remove();
}
}
org.jboss.as.server.deployment.module.descriptor.ModuleStructureSpec
class ModuleStructureSpec {
private final List<ResourceRoot> resourceRoots = new ArrayList<ResourceRoot>();
public List<ResourceRoot> getResourceRoots() {
return Collections.unmodifiableList(resourceRoots);
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (AS7-5937) UndeclaredThrowableException if EJB invocation fails with IOException
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/AS7-5937?page=com.atlassian.jira.plugin.s... ]
Stuart Douglas resolved AS7-5937.
---------------------------------
Fix Version/s: 7.2.0.Alpha1
7.1.4.Final (EAP)
Resolution: Done
> UndeclaredThrowableException if EJB invocation fails with IOException
> ---------------------------------------------------------------------
>
> Key: AS7-5937
> URL: https://issues.jboss.org/browse/AS7-5937
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Richard Janík
> Assignee: Stuart Douglas
> Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)
>
>
> UndeclaredThrowableExceptions were seen at failover testing through server crashes. Scenarios: jvmkill-dist-async, jvmkill-repl-async, jvmkill-repl-sync. Stack traces:
> {code}
> 2012/09/27 09:10:22:331 EDT [ERROR][Runner - 1533] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response. <java.lang.reflect.UndeclaredThrowableException>
> java.lang.reflect.UndeclaredThrowableException
> at $Proxy0.getSerialAndIncrement(Unknown Source)
> at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:75)
> at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
> at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.io.IOException: Broken pipe
> at sun.nio.ch.FileDispatcher.write0(Native Method)
> at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:29)
> at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:69)
> at sun.nio.ch.IOUtil.write(IOUtil.java:40)
> at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:334)
> at org.xnio.nio.AbstractNioStreamChannel.write(AbstractNioStreamChannel.java:303)
> at org.xnio.channels.FramedMessageChannel.doFlushBuffer(FramedMessageChannel.java:295)
> at org.xnio.channels.FramedMessageChannel.doFlush(FramedMessageChannel.java:309)
> at org.xnio.channels.FramedMessageChannel.send(FramedMessageChannel.java:236)
> at org.xnio.channels.Channels.sendBlocking(Channels.java:200)
> at org.jboss.remoting3.remote.OutboundMessage$1.accept(OutboundMessage.java:109)
> at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:126)
> at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:114)
> at org.xnio.streams.BufferPipeOutputStream.flush(BufferPipeOutputStream.java:143)
> at org.xnio.streams.BufferPipeOutputStream.close(BufferPipeOutputStream.java:161)
> at org.jboss.remoting3.remote.OutboundMessage.close(OutboundMessage.java:193)
> at org.jboss.ejb.client.remoting.ChannelAssociation.releaseChannelMessageOutputStream(ChannelAssociation.java:266)
> at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.processInvocation(RemotingConnectionEJBReceiver.java:203)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
> at org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:42)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:125)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
> ... 5 more
> {code}
> {code}
> 2012/09/27 09:10:22:344 EDT [ERROR][Runner - 114] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response. <java.lang.reflect.UndeclaredThrowableException>
> java.lang.reflect.UndeclaredThrowableException
> at $Proxy0.getSerialAndIncrement(Unknown Source)
> at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:75)
> at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
> at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: org.jboss.remoting3.NotOpenException: Writes closed
> at org.jboss.remoting3.remote.RemoteConnectionChannel.openOutboundMessage(RemoteConnectionChannel.java:107)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:296)
> at org.jboss.ejb.client.remoting.ChannelAssociation.acquireChannelMessageOutputStream(ChannelAssociation.java:249)
> at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.processInvocation(RemotingConnectionEJBReceiver.java:196)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
> at org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:42)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:125)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
> ... 5 more
> {code}
> {code}
> 2012/09/27 09:14:37:914 EDT [ERROR][Runner - 335] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response. <java.lang.reflect.UndeclaredThrowableException>
> java.lang.reflect.UndeclaredThrowableException
> at $Proxy0.getSerialAndIncrement(Unknown Source)
> at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:75)
> at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
> at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.io.IOException: Channel Channel ID 9d26983d (outbound) of Remoting connection 12dfbabd to null has been closed
> at org.jboss.ejb.client.remoting.ChannelAssociation$1.handleClose(ChannelAssociation.java:115)
> at org.jboss.ejb.client.remoting.ChannelAssociation$1.handleClose(ChannelAssociation.java:107)
> at org.jboss.remoting3.spi.SpiUtils.safeHandleClose(SpiUtils.java:54)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable$CloseHandlerTask.run(AbstractHandleableCloseable.java:501)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.runCloseTask(AbstractHandleableCloseable.java:406)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeComplete(AbstractHandleableCloseable.java:277)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:517)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:359)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:382)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.handleConnectionClose(RemoteConnectionHandler.java:103)
> at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:78)
> at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:45)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.nio.NioHandle.run(NioHandle.java:90)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:187)
> {code}
> These exceptions were numerous and were seen by clients (ejb remote calls) after node crash. This is the client call of the bean:
> {code}
> myBean = (RemoteStatefulSB) context.lookup("ejb:" + appName + "/" + moduleName + "/" + distinctName + "/" + beanName + "!" + viewClassName + "?stateful");
> {code}
> Links to hudson jobs:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Fail...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Fail...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Fail...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (AS7-6014) NamingContext.lookupLink(String) calls wrong method
by James Livingston (JIRA)
James Livingston created AS7-6014:
-------------------------------------
Summary: NamingContext.lookupLink(String) calls wrong method
Key: AS7-6014
URL: https://issues.jboss.org/browse/AS7-6014
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.3.Final (EAP), 7.2.0.Alpha1
Reporter: James Livingston
Assignee: Eduardo Martins
NamingContext.*(String) methods should convert the String to a Name and then call the equivalent method. lookupLink calls lookup rather than lookupLink.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (AS7-6001) Unable to lookup remote JNDI EJBs
by John Ament (JIRA)
John Ament created AS7-6001:
-------------------------------
Summary: Unable to lookup remote JNDI EJBs
Key: AS7-6001
URL: https://issues.jboss.org/browse/AS7-6001
Project: Application Server 7
Issue Type: Bug
Components: Remoting
Affects Versions: 7.1.1.Final
Reporter: John Ament
Assignee: David Lloyd
Based on the following arquillian test case:
@RunWith(Arquillian.class)
@RunAsClient
public class RemoteDatabaseIntegratorTest {
@Deployment(testable=false)
public static JavaArchive createTestArchive() {
return ShrinkWrap.create(JavaArchive.class,"myejb.jar")
.addClasses(RemoteDatabaseIntegrator.class,RemoteDatabaseIntegratorImpl.class);
}
@ArquillianResource
private Context context;
private static final String JNDI_LOC = "java:module/RemoteDatabaseIntegratorImpl";
private static final String[] JNDI_LOCS = {
//"java:global/myejb/RemoteDatabaseIntegratorImpl!com.tad.arquillian.chp5.remoteejb.RemoteDatabaseIntegrator",
//"java:app/myejb/RemoteDatabaseIntegratorImpl!com.tad.arquillian.chp5.remoteejb.RemoteDatabaseIntegrator",
"java:module/RemoteDatabaseIntegratorImpl!com.tad.arquillian.chp5.remoteejb.RemoteDatabaseIntegrator",
"java:jboss/exported/myejb/RemoteDatabaseIntegratorImpl!com.tad.arquillian.chp5.remoteejb.RemoteDatabaseIntegrator",
//"java:global/myejb/RemoteDatabaseIntegratorImpl",
//"java:app/myejb/RemoteDatabaseIntegratorImpl",
"java:module/RemoteDatabaseIntegratorImpl"
};
@Test
public void testDbServiceInjectionFailure() throws Exception{
//Thread.sleep(1000000);
//context.addToEnvironment(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.as.naming.InitialContextFactory");
Hashtable<String,String> env = new Hashtable<String,String>();
//env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");
env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.as.naming.InitialContextFactory");
env.put(Context.PROVIDER_URL, "remote://127.0.0.1:4447");
//env.put(Context.SECURITY_PRINCIPAL, "anon");
//env.put(Context.SECURITY_CREDENTIALS, "anon123");
Context context = new InitialContext(env);
for(String JNDI_LOC : JNDI_LOCS) {
try{
RemoteDatabaseIntegrator dbIntegrator = (RemoteDatabaseIntegrator)context.lookup(JNDI_LOC);
dbIntegrator.runQuery("select 1");
} catch (Exception e) {
System.out.println("Failed to lookup by "+JNDI_LOC);
e.printStackTrace();
}
}
}
}
I can see the JNDI locations populated, but cannot be retrieved, based on the following error:
20:19:02,743 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-7) JNDI bindings for session bean named RemoteDatabaseIntegratorImpl in deployment unit deployment "myejb.jar" are as follows:
java:global/myejb/RemoteDatabaseIntegratorImpl!com.tad.arquillian.chp5.remoteejb.RemoteDatabaseIntegrator
java:app/myejb/RemoteDatabaseIntegratorImpl!com.tad.arquillian.chp5.remoteejb.RemoteDatabaseIntegrator
java:module/RemoteDatabaseIntegratorImpl!com.tad.arquillian.chp5.remoteejb.RemoteDatabaseIntegrator
java:jboss/exported/myejb/RemoteDatabaseIntegratorImpl!com.tad.arquillian.chp5.remoteejb.RemoteDatabaseIntegrator
java:global/myejb/RemoteDatabaseIntegratorImpl
java:app/myejb/RemoteDatabaseIntegratorImpl
java:module/RemoteDatabaseIntegratorImpl
20:19:02,912 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "myejb.jar"
Failed to lookup by java:module/RemoteDatabaseIntegratorImpl!com.tad.arquillian.chp5.remoteejb.RemoteDatabaseIntegrator
javax.naming.NameNotFoundException: java:module/RemoteDatabaseIntegratorImpl!com.tad.arquillian.chp5.remoteejb.RemoteDatabaseIntegrator
at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:117)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at com.tad.arquillian.chp5.ejb.RemoteDatabaseIntegratorTest.testDbServiceInjectionFailure(RemoteDatabaseIntegratorTest.java:62)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270)
at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (AS7-6005) The weld-core module should not be loaded by default when beans.xml is found
by Ron Šmeral (JIRA)
Ron Šmeral created AS7-6005:
-------------------------------
Summary: The weld-core module should not be loaded by default when beans.xml is found
Key: AS7-6005
URL: https://issues.jboss.org/browse/AS7-6005
Project: Application Server 7
Issue Type: Enhancement
Components: CDI / Weld, Class Loading
Reporter: Ron Šmeral
Assignee: Stuart Douglas
Priority: Optional
AS7 automatically loads the {{weld-core}} module with any deployment which contains the {{beans.xml}} marker file. This doesn't seem like best practice. Only the APIs should be exposed by default.
>From {{weld/src/main/java/org/jboss/as/weld/deployment/processors/WeldDependencyProcessor.java}}:
{code:java}
addDependency(moduleSpecification, moduleLoader, JAVAX_PERSISTENCE_API_ID);
addDependency(moduleSpecification, moduleLoader, JAVAEE_API_ID);
addDependency(moduleSpecification, moduleLoader, JAVASSIST_ID);
addDependency(moduleSpecification, moduleLoader, WELD_CORE_ID);
addDependency(moduleSpecification, moduleLoader, WELD_API_ID);
addDependency(moduleSpecification, moduleLoader, WELD_SPI_ID);
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (AS7-6012) AS7 violating alternate client view of EJB 3.1 spec
by John Ament (JIRA)
John Ament created AS7-6012:
-------------------------------
Summary: AS7 violating alternate client view of EJB 3.1 spec
Key: AS7-6012
URL: https://issues.jboss.org/browse/AS7-6012
Project: Application Server 7
Issue Type: Bug
Components: EJB
Reporter: John Ament
Assignee: jaikiran pai
Section 4.4.2.2 of the EJB 3.1 spec states that the following JNDI locations should be populated for "other client views," which includes remote. AS7 is using a highly custom pattern for this view. This is shown when trying to run the following test case in Arquillian:
@Remote
public interface RemoteDatabaseIntegrator {
public void runQuery(String query) throws SQLException;
}
@Remote(RemoteDatabaseIntegrator.class)
@Stateless(name="RemoteDatabaseIntegrator")
public class RemoteDatabaseIntegratorImpl implements RemoteDatabaseIntegrator {
@Resource(name="jdbc/AppDS")
private DataSource ds;
private Connection conn;
@PostConstruct
public void init() throws SQLException {
this.conn = ds.getConnection();
}
@PreDestroy
public void cleanup() throws SQLException {
this.conn.close();
}
public void runQuery(String query) throws SQLException {
this.conn.createStatement().execute(query);
}
}
@RunWith(Arquillian.class)
@RunAsClient
public class RemoteDatabaseIntegratorTest {
@Deployment(testable=false)
public static JavaArchive createTestArchive() {
return ShrinkWrap.create(JavaArchive.class,"test.jar")
.addClasses(RemoteDatabaseIntegrator.class,RemoteDatabaseIntegratorImpl.class);
}
private static final String JNDI_LOC = "?";
@Test
public void testDbServiceInjectionFailure() throws Exception{
Context context = createAS7Context();
RemoteDatabaseIntegrator dbIntegrator = (RemoteDatabaseIntegrator)context.lookup(JNDI_LOC);
dbIntegrator.runQuery("select 1");
}
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (AS7-6020) Update slf4j-api dependency for module
by Bernd Eckenfels (JIRA)
Bernd Eckenfels created AS7-6020:
------------------------------------
Summary: Update slf4j-api dependency for module
Key: AS7-6020
URL: https://issues.jboss.org/browse/AS7-6020
Project: Application Server 7
Issue Type: Feature Request
Components: Build System, Logging
Affects Versions: 7.1.1.Final, 7.2.0.CR1
Reporter: Bernd Eckenfels
Assignee: Paul Gier
The org.slf4j-api artifact shipped with 7.1.1-final is at level 1.6.1 and I noticed that it is not upgraded with 7.2. There are newer 1.6.x versions but also the option to switch to 1.7.x which features vararg.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months