October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4878) TECH REVIEW: Installation Guide - Chapter 5 -

by Michael Smith (JIRA)

TECH REVIEW: Installation Guide - Chapter 5 - ---------------------------------------------- Key: JBAS-4878 URL: http://jira.jboss.com/jira/browse/JBAS-4878 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.2.GA Reporter: Michael Smith Attachments: JBAS-422-Installation_Guide-Chapter-5.odt Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide. 1. Open document in Open Office 2. Edit -> Changes -> Record 3. Edit the document 4. Save changes and reattach to this Jira It is important for track changes to be enabled so the re-write can be easily performed. -- 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

16 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-4821) TECH REVIEW: Installation Guide - Chapter 3 - The Default Server Configuration File Set

by Michael Smith (JIRA)

TECH REVIEW: Installation Guide - Chapter 3 - The Default Server Configuration File Set ---------------------------------------------------------------------------------------- Key: JBAS-4821 URL: http://jira.jboss.com/jira/browse/JBAS-4821 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Installation Guide Affects Versions: JBossAS-4.2.2.GA Reporter: Michael Smith Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide. 1. Open document in Open Office 2. Edit -> Changes -> Record 3. Edit the document 4. Save changes and reattach to this Jira It is important for track changes to be enabled so the re-write can be easily performed. http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch03.html -- 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

16 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPM-807) Allow assignment of jBPM variables via EL evaluation

by Gavin King (JIRA)

Allow assignment of jBPM variables via EL evaluation ---------------------------------------------------- Key: JBPM-807 URL: http://jira.jboss.com/jira/browse/JBPM-807 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Reporter: Gavin King Assigned To: Tom Baeyens Priority: Critical A really major issue in terms of Seam integration with jBPM is to be able to have the process "remember" state coming from Seam, w/o the Seam component needing to outject the value. What I want is to be able to say: <assign variable="orderId" value="#{order.id}"/> when a transition occurs. -- 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

16 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-1074) Allow simple configuration of jbpm-mail.war.

by Chris Sweeney (JIRA)

Allow simple configuration of jbpm-mail.war. -------------------------------------------- Key: JBPM-1074 URL: http://jira.jboss.com/jira/browse/JBPM-1074 Project: JBoss jBPM Issue Type: Feature Request Affects Versions: jBPM jPDL 3.2.2 Environment: Jboss AS Reporter: Chris Sweeney Assigned To: Tom Baeyens Allow the port and page refresh to be configured using "standard" web.xml servlet init parameters. -- 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

16 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1296) Drools Release 4.0.3

by Fernando Meyer (JIRA)

Drools Release 4.0.3 -------------------- Key: JBRULES-1296 URL: http://jira.jboss.com/jira/browse/JBRULES-1296 Project: JBoss Drools Issue Type: Task Security Level: Public (Everyone can see) Reporter: Fernando Meyer Assigned To: Fernando Meyer -- 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

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBAS-3040) Add jboss-ws4ee.sar to docs/examples/ws4ee

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3040?page=all ] Dimitris Andreadis closed JBAS-3040. ------------------------------------ Fix Version/s: (was: JBossAS-4.0.4.CR2) Resolution: Won't Fix Re-open to indicate that this was actually not done. > Add jboss-ws4ee.sar to docs/examples/ws4ee > ------------------------------------------ > > Key: JBAS-3040 > URL: http://jira.jboss.com/jira/browse/JBAS-3040 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Scott M Stark > Assigned To: Scott M Stark > > The jboss-ws4ee.sar that is being replaced with the jbossws14.sar should still be available from the docs/examples/ws4ee dir of the dist so users can easily rollback to that if needed. -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBAS-3040) Add jboss-ws4ee.sar to docs/examples/ws4ee

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3040?page=all ] Dimitris Andreadis reopened JBAS-3040: -------------------------------------- > Add jboss-ws4ee.sar to docs/examples/ws4ee > ------------------------------------------ > > Key: JBAS-3040 > URL: http://jira.jboss.com/jira/browse/JBAS-3040 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Scott M Stark > Assigned To: Scott M Stark > > The jboss-ws4ee.sar that is being replaced with the jbossws14.sar should still be available from the docs/examples/ws4ee dir of the dist so users can easily rollback to that if needed. -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3040) Add jboss-ws4ee.sar to docs/examples/ws4ee

by janssk1 (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3040?page=comments#action_12383963 ] janssk1 commented on JBAS-3040: ------------------------------- This docs/examples/ws4ee dir is not available in 4.0.5.GA. Quite annoying.. > Add jboss-ws4ee.sar to docs/examples/ws4ee > ------------------------------------------ > > Key: JBAS-3040 > URL: http://jira.jboss.com/jira/browse/JBAS-3040 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Scott M Stark > Assigned To: Scott M Stark > Fix For: JBossAS-4.0.4.CR2 > > > The jboss-ws4ee.sar that is being replaced with the jbossws14.sar should still be available from the docs/examples/ws4ee dir of the dist so users can easily rollback to that if needed. -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-785) Local interface implemented by superclass

by Gavin King (JIRA)

Local interface implemented by superclass ----------------------------------------- Key: EJBTHREE-785 URL: http://jira.jboss.com/jira/browse/EJBTHREE-785 Project: EJB 3.0 Issue Type: Bug Reporter: Gavin King Currently, local interfaces have to be directly implemented by the bean class. But it should be perfectly acceptable for a superclass of the bean class to implement them: 17:55:20,484 WARN [ServiceController] Problem creating service jboss.j2ee:service=EJB3,module=MyDomain.jar java.lang.RuntimeException: bean class has no local, webservice, or remote interfaces defined and does not implement at least one business interface at org.jboss.ejb3.ProxyFactoryHelper.getLocalInterfaces(ProxyFactoryHelper.java:107) at org.jboss.ejb3.ProxyDeployer.initializeLocalBindingMetadata(ProxyDeployer.java:115) at org.jboss.ejb3.SessionContainer.instantiated(SessionContainer.java:110) at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:415) at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:397) at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:378) at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:350) at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:305) at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:77) at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243) 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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:330) at org.jboss.system.ServiceController.create(ServiceController.java:273) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy36.create(Unknown Source) at org.jboss.ejb3.EJB3Deployer.create(EJB3Deployer.java:429) 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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97) at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238) at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:74) at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy37.create(Unknown Source) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy6.deploy(Unknown Source) -- 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

16 years, 11 months

6
15
0 / 0

[JBoss JIRA] Created: (JBAS-4822) TECH REVIEW: Installation Guide - Chapter 4 - The Default Server Configuration File Set

by Michael Smith (JIRA)

TECH REVIEW: Installation Guide - Chapter 4 - The Default Server Configuration File Set ---------------------------------------------------------------------------------------- Key: JBAS-4822 URL: http://jira.jboss.com/jira/browse/JBAS-4822 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Installation Guide Affects Versions: JBossAS-4.2.2.GA Reporter: Michael Smith Attachments: JBAS-422-Installation_Guide-Chapter-4.odt Attached is an Open Office 2.0 Document contain Chapter 4 of the Installation Guide. 1. Open document in Open Office 2. Edit -> Changes -> Record 3. Edit the document 4. Save changes and reattach to this Jira It is important for track changes to be enabled so the re-write can be easily performed. http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch04.html -- 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

16 years, 11 months

2
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007