December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-402) add support for exporting / importing

by Michael Neale (JIRA)

add support for exporting / importing ------------------------------------- Key: JBRULES-402 URL: http://jira.jboss.com/jira/browse/JBRULES-402 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale Import and exporting to/from a package DRL. An alternative may be to alter the IDE to understand the repository format somehow. But import and export of DRL would be nice (export at least). -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBCOMMON-1) ArchiveBrowser does not handle Windows directories with whitespace

by Emmanuel Bernard (JIRA)

ArchiveBrowser does not handle Windows directories with whitespace ------------------------------------------------------------------ Key: JBCOMMON-1 URL: http://jira.jboss.com/jira/browse/JBCOMMON-1 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Emmanuel Bernard Assigned To: Emmanuel Bernard Priority: Minor new File(url.toString()) fails on white spaced directories -- 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

2
3
0 / 0

[JBoss JIRA] Created: (JBCOMMON-5) fix file structure of subprojects

by Ruel Loehr (JIRA)

fix file structure of subprojects --------------------------------- Key: JBCOMMON-5 URL: http://jira.jboss.com/jira/browse/JBCOMMON-5 Project: JBoss Common Issue Type: Feature Request Security Level: Public (Everyone can see) Components: core, logging-jdk, logging-log4j, logging-spi Reporter: Ruel Loehr Assigned To: Ruel Loehr Move the subprojects from repos/common/trunk/ ..... to repos/common -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3937) ejb 3.0- jsf application: deploy error for session bean with no local home interface

by mauro avon (JIRA)

ejb 3.0- jsf application: deploy error for session bean with no local home interface ------------------------------------------------------------------------------------ Key: JBAS-3937 URL: http://jira.jboss.com/jira/browse/JBAS-3937 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-4.0.5.GA Environment: the as runs on a windows server 2003 enterprise edition service pack 1 Reporter: mauro avon Assigned To: Bill Burke Priority: Blocker I have developed a very simple web application with Oracle JDeveloper 10.1.3.1 j2ee edition (no adf). The application uses ejb 3.0 and jsf technology. The application has two projects: Model and ViewController. To deploy the application I created an ejb jar deployment profile for the model project and a war deployment profile for the ViewController. Then I created a new 'Deployment' project with an ear deployment profile to assemble the ejb jar and war deployment profiles. In this way I was able to deploy to standalone oc4j. Now I want to deploy to jboss 4.0.5 GA, I mapped the jboss connection within jdev and selected 'deploy to jboss'. The ear file is transferred to the correct folder, but the application folder is not generated and the jboss log shows at least one error. It seems it expects a local-home tag in the web.xml (related to a session bean). Below I enclose the jboss log, the session bean definition, the web.xml file. As you can see in the web.xml the <local-home> tag is really missing. But home interfaces should not be used in ejb 3.0, and I cannot manage to add a local interface to my session bean and make the application work. I posted the problem to the forum but nobody answered (see reference) // log 2006-12-01 16:20:51,250 WARN [org.jboss.util.NestedThrowable] Duplicate throwable nesting of same base type: class org.jboss.deployment.DeploymentException is assignable from: class org.jboss.deployment.DeploymentException 2006-12-01 16:20:51,250 DEBUG [org.jboss.web.tomcat.tc5.Tomcat5] Problem in init org.jboss.deployment.DeploymentException: Failed to parse WEB-INF/web.xml; - nested throwable: (org.jboss.deployment.DeploymentException: expected one local-home tag) at org.jboss.web.AbstractWebContainer.parseMetaData(AbstractWebContainer.java:749) at org.jboss.web.AbstractWebContainer.init(AbstractWebContainer.java:356) // session bean class package provascr.business; import java.util.List; import javax.ejb.Stateless; import javax.persistence.EntityManager; import javax.persistence.PersistenceContext; import provascr.persistence.SoCnfCategTpinvito; @Stateless(name="ProvaScrFacade") public class ProvaScrFacadeBean implements ProvaScrFacade, ProvaScrFacadeLocal { @PersistenceContext(unitName="Model") private EntityManager em; public ProvaScrFacadeBean() { } public Object mergeEntity(Object entity) { return em.merge(entity); } public Object persistEntity(Object entity) { em.persist(entity); return entity; } /** <code>select o from SoCnfCategTpinvito o</code> */ public List<SoCnfCategTpinvito> querySoCnfCategTpinvitoFindAll() { return em.createNamedQuery("SoCnfCategTpinvito.findAll").getResultList(); } } // web.xml <?xml version = '1.0' encoding = 'windows-1252'?> <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee"> <description>Empty web.xml file for Web Application</description> <servlet> <servlet-name>Faces Servlet</servlet-name> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <url-pattern>/faces/*</url-pattern> </servlet-mapping> <session-config> <session-timeout>35</session-timeout> </session-config> <mime-mapping> <extension>html</extension> <mime-type>text/html</mime-type> </mime-mapping> <mime-mapping> <extension>txt</extension> <mime-type>text/plain</mime-type> </mime-mapping> <jsp-config/> <ejb-local-ref> <ejb-ref-name>ejb/ProvaScrFacade</ejb-ref-name> <ejb-ref-type>Session</ejb-ref-type> <local>provascr.business.ProvaScrFacadeLocal</local> <ejb-link>ProvaScrFacade</ejb-link> </ejb-local-ref> </web-app> -- 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

4
5
0 / 0

[JBoss JIRA] Created: (JGRP-312) Make testsuite configurable to run with different stack configurations

by Bela Ban (JIRA)

Make testsuite configurable to run with different stack configurations ---------------------------------------------------------------------- Key: JGRP-312 URL: http://jira.jboss.com/jira/browse/JGRP-312 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 All test programs should use a system property (with a default if the system property is not defined). The testsuite can then be run with the system property, so all tests use TCP, for example. We could also use multiple targets, one for each major stack configuration. An 'all-unittests' target would run all of them. -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-321) CloseTest.testShutdown() fails with -Dconfig=tcp.xml

by Bela Ban (JIRA)

CloseTest.testShutdown() fails with -Dconfig=tcp.xml ---------------------------------------------------- Key: JGRP-321 URL: http://jira.jboss.com/jira/browse/JGRP-321 Project: JGroups Issue Type: Bug Affects Versions: 2.3 SP1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.4 -- 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

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-840) Make testsuite configurable to run with different Jgroups stack configurations

by Vladimir Blagojevic (JIRA)

Make testsuite configurable to run with different Jgroups stack configurations ------------------------------------------------------------------------------ Key: JBCACHE-840 URL: http://jira.jboss.com/jira/browse/JBCACHE-840 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Fix For: 2.0.0.GA All junit tests should have a system property (with a default if the system property is not defined) to use a certain JGroups protocol stack. Thus, for example, we can run whole JBC testsuite with Jgroups tcp stack. We should have multiple tests targets that run testsuite with tcp,udp, and other supported protocols. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-3917) The JMS JCA adapter's DLQMaxResent is set by default to 0, causing messages to go straight to DLQ

by Ovidiu Feodorov (JIRA)

The JMS JCA adapter's DLQMaxResent is set by default to 0, causing messages to go straight to DLQ ------------------------------------------------------------------------------------------------- Key: JBAS-3917 URL: http://jira.jboss.com/jira/browse/JBAS-3917 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.0.5.GA Reporter: Ovidiu Feodorov Assigned To: Weston Price Priority: Minor The JMS JCA adapter's DLQMaxResent is set by default to 0, causing messages to go straight to DLQ. Needs to be raised to something like 10. The workaround is to override the value in MDB's config: @MessageDriven(activationConfig = { ... @ActivationConfigProperty(propertyName="DLQMaxResent", propertyValue="10") }) -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-704) Close a dead remoting client from failover

by Clebert Suconic (JIRA)

Close a dead remoting client from failover ------------------------------------------ Key: JBMESSAGING-704 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-704 Project: JBoss Messaging Issue Type: Feature Request Reporter: Clebert Suconic Assigned To: Ovidiu Feodorov We should disconnect a client from a dead server. Remoting will keep trying leases on dead connections. There is a feature request within remoting (JBREM-657). We need to implement this feature as soon as JBREM-657 is finished. -- 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

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-276) Increase level of exception granularity

by Mark Little (JIRA)

Increase level of exception granularity --------------------------------------- Key: JBESB-276 URL: http://jira.jboss.com/jira/browse/JBESB-276 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Reporter: Mark Little Assigned To: Mark Little Fix For: 5.0 Many of the classes and methods either throw Exception or a single exception instance. This masks many of the underlying reasons for an error, making it difficult to track down issues. -- 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

1
2
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 December 2006