April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9237) TldParsingDeploymentProcessor should run before WebComponentProcessor

by jaikiran pai (JIRA)

TldParsingDeploymentProcessor should run before WebComponentProcessor --------------------------------------------------------------------- Key: JBAS-9237 URL: https://issues.jboss.org/browse/JBAS-9237 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: 7.0.0.Beta2 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: 7.0.0.Beta3 The WebComponentProcessor uses TldMetaData to identify web components. As such, the TldParsingDeploymentProcessor which is responsible for setting up the TldMetaData should run before the WebComponentProcessor. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-563) Consolidate state transfer API to use streams

by Vladimir Blagojevic (JIRA)

Consolidate state transfer API to use streams --------------------------------------------- Key: JGRP-563 URL: http://jira.jboss.com/jira/browse/JGRP-563 Project: JGroups Issue Type: Task Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Fix For: 3.0 Although streaming state transfer has its advantages over byte based state transfer, byte based state transfer is absolutely necessary since streaming based transfer relies on plain sockets that are not firewall friendly. However, that does not mean that we cannot consolidate state transfer API at application level and mask byte based transfer with streams. We have already done this in JBC 2.0 so there is no reason not to do it on JGroups level as well. Advantages: - simpler state transfer API - interchangeable state transfer mechanism without affect on application - simplification of client application Disadvantages: - we break current API by eliminating getState(byte[]) and setState(byte []) -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-9249) @Singleton bean can't be bound to a custom JNDI name

by Viggo Navarsete (JIRA)

@Singleton bean can't be bound to a custom JNDI name ---------------------------------------------------- Key: JBAS-9249 URL: https://issues.jboss.org/browse/JBAS-9249 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Final Reporter: Viggo Navarsete I have a Singleton bean like this: @Singleton public class DummySingleton implements Dummy { public String getHello() { return "Hello Dummy!"; } } and an interface like this: public interface Dummy { public String getHello(); } I've tried this in ejb-jar.xml (everything is packaged into an EAR file): <?xml version="1.0" encoding="UTF-8"?> <ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" version="3.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd"> <enterprise-beans> <session> <ejb-name>DummySingleton</ejb-name> <ejb-class>com.tracetracker.global.aps.DummySingleton</ejb-class> <session-type>Singleton</session-type> <init-on-startup>false</init-on-startup> <ejb-local-ref> <ejb-ref-name>ejb3/hub/DummySingleton</ejb-ref-name> <local>com.tracetracker.global.aps.Dummy</local> </ejb-local-ref> </session> </enterprise-beans> </ejb-jar> I've also tried to add it to jboss.xml like this: <session> <ejb-name>DummySingleton</ejb-name> <local-jndi>ejb3/hub/DummySingleton</local-jndi> </session> but no matter what I try it will not end up in JNDI bound to ejb3/hub/DummySingleton. I can have normal session beans, and they will bind to ejb3/hub/xxxxx, but not when it's a singleton. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] Deleted: (JGRP-501) JGroups demo hosted by jboss.org

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-501?page=com.atlassian.jira.plugin.s... ] Bela Ban deleted JGRP-501: -------------------------- > JGroups demo hosted by jboss.org > -------------------------------- > > Key: JGRP-501 > URL: https://issues.jboss.org/browse/JGRP-501 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Vladimir Blagojevic > Priority: Minor > > Goal: users can download a minimal JGroups installation (either via WebStart or as an applet) and explore JGroups. The configuration would probably include TUNNEL and there would be a GossipRouter instance running, e.g. on labs.jboss.org. > We could provide access to chat & whiteboard (org.jgroups.demos.wb.Whiteboard) > This would also be a good test case for the new revamped GossipRouter. Plus, once we have redundant GossipRouters, we can test client failover. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] Deleted: (JGRP-405) Get rid of the old STATE_TRANSFER, GMS and FLUSH protocols

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-405?page=com.atlassian.jira.plugin.s... ] Bela Ban deleted JGRP-405: -------------------------- > Get rid of the old STATE_TRANSFER, GMS and FLUSH protocols > ---------------------------------------------------------- > > Key: JGRP-405 > URL: https://issues.jboss.org/browse/JGRP-405 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > > - Get rid of these old protocols > - Possibly refactor the packages, name them e.g. > default, total, vsync etc -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-567) Add one shot state transfer for multiple substates

by Vladimir Blagojevic (JIRA)

Add one shot state transfer for multiple substates -------------------------------------------------- Key: JGRP-567 URL: http://jira.jboss.com/jira/browse/JGRP-567 Project: JGroups Issue Type: Feature Request Affects Versions: 2.x Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Currently (2.5) each sub state transfer requires separate state transfer invocation for each sub state. It would be very convenient if we could transfer a list of substates all in one underlying state transfer. This would require introduction of a new method in JChannel API, however we should avoid additional callbacks on application level. Proposed API for additional JChannel method is: public boolean getState(Address target, List<String> state_ids, long timeout) throws ChannelNotConnectedException, ChannelClosedException; -- 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, 1 month

2
9
0 / 0

[JBoss JIRA] Created: (JBAS-9217) make undeploy cmd w/o args list the existing deployments

by Alexey Loubyansky (JIRA)

make undeploy cmd w/o args list the existing deployments -------------------------------------------------------- Key: JBAS-9217 URL: https://issues.jboss.org/browse/JBAS-9217 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.Beta3 It would be useful to see the existing deployments listed before executing the command. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-9218) Tab-completion for undeploy command argument

by Alexey Loubyansky (JIRA)

Tab-completion for undeploy command argument -------------------------------------------- Key: JBAS-9218 URL: https://issues.jboss.org/browse/JBAS-9218 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.Beta3 It'd natural to support tab-completion for undeploy arguments. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-9215) delete key acts like a backspace on linux

by Alexey Loubyansky (JIRA)

delete key acts like a backspace on linux ----------------------------------------- Key: JBAS-9215 URL: https://issues.jboss.org/browse/JBAS-9215 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.Beta3 The delete key on linux deletes the previous key instead of the next key. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8024) Weld deployments fail with "Error in zip file" message

by jaikiran pai (JIRA)

Weld deployments fail with "Error in zip file" message ------------------------------------------------------ Key: JBAS-8024 URL: https://jira.jboss.org/jira/browse/JBAS-8024 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.M3 Reporter: jaikiran pai More than one user has now reported that weld deployments which used to work in earlier AS versions (6.0.0.M2) have started failing in M3 with the following error: 18:51:45,567 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] : java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) [:1.6.0_17] at java.util.zip.ZipFile.<init>(ZipFile.java:114) [:1.6.0_17] at java.util.jar.JarFile.<init>(JarFile.java:133) [:1.6.0_17] at sun.net.www.protocol.jar.URLJarFile.<init>(URLJarFile.java:67) [:1.6.0_17] at sun.net.www.protocol.jar.URLJarFile$1.run(URLJarFile.java:214) [:1.6.0_17] at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_17] at sun.net.www.protocol.jar.URLJarFile.retrieve(URLJarFile.java:198) [:1.6.0_17] at sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:50) [:1.6.0_17] at sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:68) [:1.6.0_17] at sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:104) [:1.6.0_17] at sun.net.www.protocol.jar.JarURLConnection.getJarFile(JarURLConnection.java:71) [:1.6.0_17] at com.sun.faces.config.AnnotationScanner.processClasspath(AnnotationScanner.java:290) [:2.0.2-FCS] at com.sun.faces.config.AnnotationScanner.getAnnotatedClasses(AnnotationScanner.java:215) [:2.0.2-FCS] at com.sun.faces.config.ConfigManager$AnnotationScanTask.call(ConfigManager.java:765) [:2.0.2-FCS] at com.sun.faces.config.ConfigManager$AnnotationScanTask.call(ConfigManager.java:736) [:2.0.2-FCS] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [:1.6.0_17] at java.util.concurrent.FutureTask.run(FutureTask.java:138) [:1.6.0_17] at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:329) [:2.0.2-FCS] at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:223) [:2.0.2-FCS] at org.jboss.web.jsf.integration.config.JBossJSFConfigureListener.contextInitialized(JBossJSFConfigureListener.java:72) [:6.0.0.20100429-M3] Please see the referenced forum thread for the complete details -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

9
15
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2011