March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBOSGI-10) OSGi Listeners

by Adrian Brock (JIRA)

OSGi Listeners -------------- Key: JBOSGI-10 URL: http://jira.jboss.com/jira/browse/JBOSGI-10 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Adrian Brock Assigned To: Adrian Brock OSGi defines three types of listeners 1) Framework listener for global events related to the server 2) Bundle listener for events related to the deployments 3) Service listener for events related services Where these already exist, these need to be "adapted" to the OSGi api. The missing notifications need to be implemented. -- 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

18 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-7) OSGi ClassLoader

by Adrian Brock (JIRA)

OSGi ClassLoader ---------------- Key: JBOSGI-7 URL: http://jira.jboss.com/jira/browse/JBOSGI-7 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Adrian Brock Assigned To: Adrian Brock Implementation of the OSGi classloader. This should be usable for both OSGi bundles and all other JBoss deployments. An new classloader.xml will be supported such that non OSGi deployments can specify their classloading constraints (import, export, etc.) Additionally, it should provide support for things outside the OSGi spec that are required in JavaEE or for backwards compatibility like scoping and j2se classloading compliance. -- 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

18 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-4) Deployer changes for OSGi

by Adrian Brock (JIRA)

Deployer changes for OSGi ------------------------- Key: JBOSGI-4 URL: http://jira.jboss.com/jira/browse/JBOSGI-4 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Adrian Brock Assigned To: Adrian Brock This is a holder task for the Deployer changes need to make OSGi work and integrate OSGi bundles with other JBoss deployments (and vice versa). -- 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

18 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-444) RequestCorrelator does not respect FLUSH.FlushHeader.BYPASS_FLUSH

by Michael Newcomb (JIRA)

RequestCorrelator does not respect FLUSH.FlushHeader.BYPASS_FLUSH ----------------------------------------------------------------- Key: JGRP-444 URL: http://jira.jboss.com/jira/browse/JGRP-444 Project: JGroups Issue Type: Bug Affects Versions: 2.5 Environment: 2.5 alpha 2 Reporter: Michael Newcomb Assigned To: Bela Ban private void handleRequest(Message req, Header hdr) { ... rsp=req.makeReply(); if(rsp_buf != null) rsp.setBuffer(rsp_buf); rsp_hdr=new Header(Header.RSP, hdr.id, false, name); rsp.putHeader(name, rsp_hdr); // *************** patch ***************** // can't check for FLUSH.FlushHeader.BYPASS_FLUSH because it has package protection, so just check for FLUSH header // if (req.getHeader(org.jgroups.protocols.pbcast.FLUSH.NAME) != null) { rsp.putHeader(org.jgroups.protocols.pbcast.FLUSH.NAME, new org.jgroups.protocols.pbcast.FLUSH.FlushHeader(org.jgroups.protocols.pbcast.FLUSH.FlushHeader.FLUSH_BYPASS)); } // *************** patch ***************** if(log.isTraceEnabled()) log.trace(new StringBuffer("sending rsp for ").append(rsp_hdr.id).append(" to ").append(rsp.getDest())); ... } -- 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

18 years, 1 month

3
10
0 / 0

[JBoss JIRA] Created: (JBAS-4242) Port Hibernate depoyer to VDF

by Scott M Stark (JIRA)

Port Hibernate depoyer to VDF ----------------------------- Key: JBAS-4242 URL: http://jira.jboss.com/jira/browse/JBAS-4242 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Deployment services, Hibernate service Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Scott M Stark Assigned To: Steve Ebersole Fix For: JBossAS-5.0.0.Beta3 The current hibernate integration tests are broken in jboss5 trunk, and the deployer needs to be ported to the VDF (http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss5DeploymentFramework). This really should be done in concert with the ejb3 deployer refactoring as there should be minimal duplication of the various deployment aspects related to persistence. -- 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

18 years, 1 month

4
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-697) First concurrent call doesn't throw exception

by Carlo de Wolf (JIRA)

First concurrent call doesn't throw exception --------------------------------------------- Key: EJBTHREE-697 URL: http://jira.jboss.com/jira/browse/EJBTHREE-697 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC8 - FD Reporter: Carlo de Wolf Priority: Critical Fix For: EJB 3.0 RC10 - FD Concurrency check is in the server interceptor, while identity is established in the proxy after the first call. So if the first call is concurrent no exception is thrown. (see unit test concurrent) -- 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

18 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBREM-698) Update Remoting Marshaller/UnMarshallers to implement PreferredStreamMarshaller/PreferredStreamUnMarshaller interfaces.

by Ron Sigal (JIRA)

Update Remoting Marshaller/UnMarshallers to implement PreferredStreamMarshaller/PreferredStreamUnMarshaller interfaces. ----------------------------------------------------------------------------------------------------------------------- Key: JBREM-698 URL: http://jira.jboss.com/jira/browse/JBREM-698 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta2 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Beta2 (Bluto) In response to JBREM-692 the org.jboss.remoting.marshal.PreferredStreamMarshaller and org.jboss.remoting.marshal.PreferredStreamUnMarshaller interfaces were introduced, and org.jboss.remoting.marshal.serializable.SerializableMarshaller and org.jboss.remoting.marshal.serializable.SerializableUnMarshaller were modified to implement them. In particular, they implement a getMarshallingStream() method which returns an object stream that can be cached and reused by the transport layer. Now, the other Remoting marshallers (http, compressing, encrypting) should also be made to implement those interfaces. -- 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

18 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBREM-716) Reduce log output from test suite

by Ron Sigal (JIRA)

Reduce log output from test suite --------------------------------- Key: JBREM-716 URL: http://jira.jboss.com/jira/browse/JBREM-716 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta2 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Minor Fix For: 2.2.0.Beta2 (Bluto) Looks like jdk 1.5 test suite on cruisecontrol didn't produce a report. Maybe it ran out of memory. -- 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

18 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-665) Need better error reporting of response marshalling errors

by Scott M Stark (JIRA)

Need better error reporting of response marshalling errors ---------------------------------------------------------- Key: JBREM-665 URL: http://jira.jboss.com/jira/browse/JBREM-665 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Alpha4 Reporter: Scott M Stark Assigned To: Tom Elrod A failure to write a response on the server such as: 21:03:32,935 ERROR [ServerThread] failed to process invocation. java.io.NotSerializableException: java.util.HashMap$KeySet at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) at org.jboss.aop.joinpoint.InvocationResponse.writeExternal(InvocationResponse.java:101) at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1310) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1288) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.sendObject(JavaSerializationManager.java:85) at org.jboss.remoting.marshal.serializable.SerializableMarshaller.write(SerializableMarshaller.java:84) at org.jboss.invocation.unified.marshall.InvocationMarshaller.write(InvocationMarshaller.java:66) at org.jboss.remoting.transport.socket.ServerThread.versionedWrite(ServerThread.java:491) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:470) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:527) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:261) results in this uninformative exception on the client: java.rmi.MarshalException: Failed to communicate. Problem during marshalling/unmarshalling; nested exception is: ... Caused by: java.net.SocketException at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:352) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:125) at org.jboss.remoting.Client.invoke(Client.java:589) at org.jboss.remoting.Client.invoke(Client.java:581) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at AOPProxy$1.getTemplateNames(AOPProxy$1.java) at org.jboss.test.profileservice.test.ProfileServiceUnitTestCase.testAddDataSource(ProfileServiceUnitTestCase.java:72) 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 junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74) ... 23 more Need to look at how this can be improved. -- 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

18 years, 2 months

3
9
0 / 0

[JBoss JIRA] Created: (JBRULES-479) Wizard for autopopulating a decision table

by Michael Neale (JIRA)

Wizard for autopopulating a decision table ------------------------------------------ Key: JBRULES-479 URL: http://jira.jboss.com/jira/browse/JBRULES-479 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Decision tables Reporter: Michael Neale Assigned To: Mark Proctor Priority: Minor This could be done quite easily by a contributor. Have a wizard (in the IDE) which takes information regarding the facts to be used, fields, actions (and the number of each) and generates a decision table based on that info capture (ie populates it). -- 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

18 years, 2 months

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2007