November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1109) WSRP integration API

by Julien Viet (JIRA)

WSRP integration API -------------------- Key: JBPORTAL-1109 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1109 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.Alpha1 Reporter: Julien Viet Assigned To: Chris Laprun Fix For: 2.6.Alpha1 -- 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

13 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1106) Find a way to prevent re-generation of Service Description for each call

by Chris Laprun (JIRA)

Find a way to prevent re-generation of Service Description for each call ------------------------------------------------------------------------ Key: JBPORTAL-1106 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1106 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.DR1, 2.4 Final Reporter: Chris Laprun Assigned To: Chris Laprun Priority: Minor Fix For: 2.6.Alpha1 A way to do it would be to be able to listen to portlet deployment inside the server. This way, we could mark the service description as dirty when a new remotable portlet is deployed and only re-generate the service description when it is dirty. -- 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

13 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1016) Allow creation and deployment of WSRP portlets from descriptors

by Chris Laprun (JIRA)

Allow creation and deployment of WSRP portlets from descriptors --------------------------------------------------------------- Key: JBPORTAL-1016 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1016 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.4 Final Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.4.1 Final Right now, the only way to deploy WSRP portlets is via the management portlet. We should be able to do this via the descriptors. Proposed solution is to evolve the -wsrp.xml file to accomodate portlet definition. -- 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

13 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-754) isCallerInRole checks should go through JACC layer (if JACC is configured)

by Anil Saldhana (JIRA)

isCallerInRole checks should go through JACC layer (if JACC is configured) -------------------------------------------------------------------------- Key: EJBTHREE-754 URL: http://jira.jboss.com/jira/browse/EJBTHREE-754 Project: EJB 3.0 Issue Type: Task Components: Security Affects Versions: EJB 3.0 RC9 - FD Reporter: Anil Saldhana Assigned To: Scott M Stark Fix For: EJB 3.0 RC10 - FD Since Scott is going to review the ejb3 JACC implementation, I am assigning this issue to Scott. The EJBContext.isCallerInRole checks need to go through the jacc layer, if the user has configured jacc. I am not sure what the best way to tell the xxxContext layer to use jacc helper if user desires. Maybe a simple system property may do 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

13 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-772) Add JBoss EULA

by Rajesh Rajasekaran (JIRA)

Add JBoss EULA -------------- Key: EJBTHREE-772 URL: http://jira.jboss.com/jira/browse/EJBTHREE-772 Project: EJB 3.0 Issue Type: Task Reporter: Rajesh Rajasekaran Fix For: EJB 3.0 RC10 - FD Attachments: JBossORG-EULA.txt Attached is the JBossORG-EULA.txt 1. The eula should be checked into the project's source tree. 2. The project's build should include the EULA in project distributables, ie, whatever is the unit of publish: zip, tgz, etc. -- 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

13 years, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (JBCOMMON-6) Archive Browser does not support jar:file: url protocol

by Chris Mercer (JIRA)

Archive Browser does not support jar:file: url protocol ------------------------------------------------------- Key: JBCOMMON-6 URL: http://jira.jboss.com/jira/browse/JBCOMMON-6 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Components: core Environment: jdk 1.5.8 jboss 4.0.4ga hibernate 3.2cr2 hibernate entity manager 3.2.0.CR1 Using ejb3/entity manager annotations Reporter: Chris Mercer Assigned To: Dimitris Andreadis Priority: Critical We have a seperate jar file that contains all of our model/entity objects. This jar gets put in the WEB-INF/lib directory, since we are only using wars and not ears. Using the hibernate auto-discovery feature causes an exception to occur. In this configuration. Caused by: java.lang.RuntimeException: NOT IMPLEMENTED at org.jboss.util.file.ArchiveBrowser.getBrowser(ArchiveBrowser.java:42) at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:541) ... 148 more org.jboss.util.file.ArchiveBrowser.getBrowser(URL url, Filter filter) only supports URLS that have a protocol of "file". However, jars have a protocol of "jar:file:" and therefore it will throw a RuntimeException saying "NOT IMPLEMENTED" (at least according to my debugger). There is already a JarArchiveBrowser class, the ArchiveBrowser just needs to recognize the protocol and handle it. This also affects Hibernate entity manager, since it gets included in the jboss-archive-browsing.jar in order to handle the auto-discovery of mapped entities feature. I've marked this as critical, since it effects entity manager features (though its only advanced hibernate only functionality) -- 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

13 years, 8 months

11
22
0 / 0

[JBoss JIRA] Created: (EJBTHREE-729) Injecting a EJB 2.1 bean in EJB 3 bean can show misleading warning message: IGNORING DEPENDENCY:...

by Galder Zamarreno (JIRA)

Injecting a EJB 2.1 bean in EJB 3 bean can show misleading warning message: IGNORING DEPENDENCY:... --------------------------------------------------------------------------------------------------- Key: EJBTHREE-729 URL: http://jira.jboss.com/jira/browse/EJBTHREE-729 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Reporter: Galder Zamarreno Fix For: EJB 3.0 RC10 - FD An EJB 2.1 bean injected in a EJB 3 bean via: @EJB(mappedName="ejb/IdGenerator") private IdGeneratorHome idGeneratorHome; leads to the following warning message being logged: "server.log:6202:2006-10-05 14:28:36,171 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.acme.ejb2.uuid.IdGeneratorHome in ejb-jar.xml of SqlTimeStampBeannot used by any EJBs" The message is misleading as it seems to indicate that the dependency was not set, but it actually did. Create call on the home interface works returning a valid bean. -- 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

13 years, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-665) @PostConstruct throws NPE when EntityManager is used

by Steven Verze (JIRA)

@PostConstruct throws NPE when EntityManager is used ---------------------------------------------------- Key: EJBTHREE-665 URL: http://jira.jboss.com/jira/browse/EJBTHREE-665 Project: EJB 3.0 Issue Type: Bug Components: EJB3 Extensions Affects Versions: EJB 3.0 RC8 - FD Environment: Windows XP, JBoss 4.0.4.GA + EJB-3.0-RC8 Reporter: Steven Verze @PostConstruct method throws NPE when called on a stateless session bean. The method iteself accesses the enetity manager and tries create a query, the following exception is experienced: java.lang.RuntimeException: java.lang.NullPointerException at org.jboss.ejb3.interceptor.LifecycleInterceptorHandler.postConstruct(LifecycleInterceptorHandler.java:109) at org.jboss.ejb3.EJBContainer.invokePostConstruct(EJBContainer.java:582) at org.jboss.ejb3.AbstractPool.create(AbstractPool.java:108) at org.jboss.ejb3.ThreadlocalPool.get(ThreadlocalPool.java:48) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:54) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:78) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:227) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:398) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239) Caused by: java.lang.NullPointerException at org.jboss.ejb3.entity.ManagedEntityManagerFactory.getNonTxEntityManager(ManagedEntityManagerFactory.java:58) at org.jboss.ejb3.entity.ManagedEntityManagerFactory.getTransactionScopedEntityManager(ManagedEntityManagerFactory.java:163) at org.jboss.ejb3.entity.TransactionScopedEntityManager.createQuery(TransactionScopedEntityManager.java:125) at com.teleglobal.modules.snapaccount.services.SnapAccountSendProcessServiceBean.initialiseSpendCardQuery(SnapAccountSendProcessServiceBean.java:83) 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.ejb3.interceptor.LifecycleInvocationContextImpl.proceed(LifecycleInvocationContextImpl.java:159) at org.jboss.ejb3.interceptor.LifecycleInterceptorHandler.postConstruct(LifecycleInterceptorHandler.java:105) at org.jboss.ejb3.EJBContainer.invokePostConstruct(EJBContainer.java:582) at org.jboss.ejb3.AbstractPool.create(AbstractPool.java:108) at org.jboss.ejb3.ThreadlocalPool.get(ThreadlocalPool.java:48) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:54) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:78) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:227) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:398) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239) at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:190) at org.jboss.remoting.Client.invoke(Client.java:525) at org.jboss.remoting.Client.invoke(Client.java:488) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:55) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:78) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102) at $Proxy3.getBatchNumbers(Unknown Source) at com.teleglobal.modules.snapaccount.services.SnapAccountSendProcessServiceTest.testGetBatchNumbers(SnapAccountSendProcessServiceTest.java:57) 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.RemoteTestRunner.runTests(RemoteTestRunner.java:478) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:344) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Here is a the post construct method: @PostConstruct void initialiseSpendCardQuery() { StringBuilder sendCardQueryString = new StringBuilder(); sendCardQueryString.append("SELECT c FROM Card AS c WHERE c.status = 'U' AND c.batchNumber IN ("); long[] batchNumbers = getBatchNumbers(); for (int i = 0; i < batchNumbers.length; i++) { sendCardQueryString.append("?").append(i); if (i+1 < batchNumbers.length) sendCardQueryString.append(","); } sendCardQueryString.append(") AND c NOT IN (SELECT lc.sendCard FROM SendCardLock AS lc)"); sendCardQuery = entityManager.createQuery(sendCardQueryString.toString()); for (int i = 0; i < batchNumbers.length; i++) sendCardQuery.setParameter(i, batchNumbers[i]); } It happens when the entityManager is used. -- 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

13 years, 8 months

11
19
0 / 0

[JBoss JIRA] Created: (EJBTHREE-789) build.xml and component-info.xml - version numbers and imports need to be updated

by Vladimir Ralev (JIRA)

build.xml and component-info.xml - version numbers and imports need to be updated --------------------------------------------------------------------------------- Key: EJBTHREE-789 URL: http://jira.jboss.com/jira/browse/EJBTHREE-789 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Reporter: Vladimir Ralev Priority: Critical The repository-zip target's comp-version, like this (use appropriate version string): <target name="repository-zip" depends="jars" description="Create the repository.jboss.com jboss/ejb3 component contents">  <property name="comp-version" value="1.0.0.CR9-jboss4.0.5" />  <zip destfile="${build.lib}/ejb3-deployer.zip"> <zipfileset dir="${build.lib}"> <include name="ejb3.deployer/**" /> </zipfileset> </zip>  <zip destfile="${build.lib}/jboss-ejb3-repo.zip">  <zipfileset dir="${build.etc}" prefix="${comp-version}"> <include name="component-info.xml" /> </zipfileset>  <zipfileset dir="${build.lib}" fullpath="${comp-version}/bin/ejb3.deployer"> <include name="ejb3-deployer.zip" /> </zipfileset>  <zipfileset dir="${build.lib}" prefix="${comp-version}/lib"> <include name="hibernate-client.jar" /> <include name="jboss-ejb3-client.jar" /> </zipfileset>  <zipfileset dir="${build.lib}" prefix="${comp-version}/resources"> <include name="ejb3-clustered-sfsbcache-service.xml" /> <include name="ejb3-entity-cache-service.xml" /> <include name="ejb3-interceptors-aop.xml" /> </zipfileset> </zip> </target> and ejb3\src\etc\component-info.xml (the version attribute): <project name="jboss/ejb3-component-info"> <component id="jboss/ejb3" licenseType="lgpl" version="1.0.0.CR9-jboss4.0.5" description="The EJB3 deployer for integration with jboss-4.0.x"> <artifact id="ejb3-clustered-sfsbcache-service.xml"/> <artifact id="ejb3-entity-cache-service.xml"/> <artifact id="ejb3-interceptors-aop.xml"/> <artifact id="ejb3.deployer" /> <artifact id="hibernate-client.jar"/> <artifact id="jboss-ejb3-client.jar"/> <import componentref="javassist"> <compatible version="3.2.0.CR1"/> <compatible version="3.2.0.CR2"/> </import> <import componentref="hibernate-annotations"> <compatible version="3.2.0.GA"/> </import> <import componentref="hibernate-entitymanager"> <compatible version="3.2.0.GA"/> </import> <import componentref="jboss/remoting"> <compatible version="1.4.1_final"/> <compatible version="1.4.2.GA"/> </import> <import componentref="jboss/aop"> <compatible version="1.5.1.GA"/> <compatible version="1.5.2.GA"/> <--------------- IS 1.5.2.GA COMPATIBLE? </import> <export> <include input="hibernate-client.jar"/> <include input="jboss-ejb3-client.jar"/> </export> </component> </project> -- 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

13 years, 8 months

4
9
0 / 0

[JBoss JIRA] Created: (JBAS-3648) Need a clustered ejb compatibility test

by Scott M Stark (JIRA)

Need a clustered ejb compatibility test --------------------------------------- Key: JBAS-3648 URL: http://jira.jboss.com/jira/browse/JBAS-3648 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-3.2.8.SP1 Reporter: Scott M Stark Assigned To: Brian Stansberry We need a test of a 3.2.x client talking to a 4.0.x clustered ejb to validate interop. -- 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

13 years, 9 months

4
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2006