September 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-2853) Integrate JBoss Cache 2.0 into AS 5.0

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2853?page=comments#action_12375159 ] Brian Stansberry commented on JBAS-2853: ---------------------------------------- AS 5 has moved to JBC 2.0.0.GA. This issue is still open due to the couple minor subtasks that are still open. I'll get those either closed or moved to a separate, non-critical parent this week. > Integrate JBoss Cache 2.0 into AS 5.0 > ------------------------------------- > > Key: JBAS-2853 > URL: http://jira.jboss.com/jira/browse/JBAS-2853 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JBoss Cache > Reporter: Manik Surtani > Assigned To: Brian Stansberry > Priority: Critical > Fix For: JBossAS-5.0.0.Beta3 > > > JBC 2.0.0.ALPHA1 was produced for JB5, Beta1. > I'm assigning this issue to the next beta, to track further integration 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

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBRULES-1112) drools-jbrms.war does not work with JBoss4.0.5 bundled with Jetty6.1.1

by Fernando Meyer (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-1112?page=all ] Fernando Meyer closed JBRULES-1112. ----------------------------------- Resolution: Cannot Reproduce Bug You can download faces libs from the sun website http://java.sun.com/javaee/javaserverfaces/download.html > drools-jbrms.war does not work with JBoss4.0.5 bundled with Jetty6.1.1 > ---------------------------------------------------------------------- > > Key: JBRULES-1112 > URL: http://jira.jboss.com/jira/browse/JBRULES-1112 > Project: JBoss Rules > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-brms > Affects Versions: 4.0.0.GA > Environment: Windows XP Professional 2002 service pack 2, JDK1.6.0 > Reporter: Huishan Zhou > Assigned To: Fernando Meyer > Priority: Critical > Fix For: FUTURE > > > The bugs of the following test is based on running drools-jbrms.war > on JBoss4.0.5 bundled with Jetty6.1.1. (No bugs on running this war in > JBoss4.0.5 bundled with Tomcat5.5) > drools-jbrms.war is extracted from drools-4.0.0-brms.zip > which is downloaded from > http://labs.jboss.com/drools/downloads.html on 08/21/2007. > (I also tested drools-jbrms.war extracted from > jbossrules-4.0.0.12865MR3-brms.zip > downloaded from > http://labs.jboss.com/jbossrules/downloads > on 08/20/2007. Identical error message.) > (1) during starting of JBoss, it throws the > ClassNotFoundException, javax/faces/context/FacesContext, > and in web browser console, it showed that drools-jbrms deployment > failed. > We have fixed this exception by adding two jar files, jsf-impl.jar > and jsf-api.jar, to WEB-INF/lib > (2) After fixing errors in (1) we can start JBoss. And we can go > to > http://localhost:8080/drools-jbrms/drools-jbrms/org.drools.brms.JBRMS/ > welcome.jsp > and > http://localhost:8080/drools-jbrms/drools-jbrms/org.drools.brms.JBRMS/ > JBRMS.html with the showup of the code of JBRMS.html itself, not > the user name and password form that was showed up in the JBoss4.0.5 > bundled with Tomcat5.5 > and > we can also go to > http://localhost:8080/drools-jbrms/drools-jbrms/org.drools.brms.JBRMS/ > login.jsp (What is the purpose of this page?) > If we try to go to > http://localhost:8080/drools-jbrms/drools-jbrms/org.drools.brms.JBRMS/ > JBRMS.jsp > we got error. We opened JBRMS.jsp, we found that it missed one very > basic line (but this missing didn't cause any trouble while testing in > JBoss bundled with Tomcat ?) > <%@ page language="java" import="org.jboss.seam.security.Identity" > pageEncoding="ISO-8859-1"%> > After adding this line to the code. We still got errors: > = = = = errors message = = = = > org.apache.jasper.JasperException: Unable to compile class for JSP > Generated servlet error: > Only a type can be imported. org.jboss.seam.security.Identity > resolves to a package > An error occurred at line: 11 in the jsp file: > /drools-jbrms/org.drools.brms.JBRMS/JBRMS.jsp > Generated servlet error: > Identity cannot be resolved to a type > An error occurred at line: 10 in the jsp file: > /drools-jbrms/org.drools.brms.JBRMS/JBRMS.jsp > Generated servlet error: > org.jboss.seam.security.Identity cannot be resolved to a type > = = = = = = = = = = = = = = = = = = = > We have checked that the jar file for the class > org.jboss.seam.security.Identity is in the WEB-INF/lib of > drools-jbrms.war. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-429) Support for external security systems

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-429?page=all ] Tom Baeyens closed JBPM-429. ---------------------------- Resolution: Done > Support for external security systems > ------------------------------------- > > Key: JBPM-429 > URL: http://jira.jboss.com/jira/browse/JBPM-429 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0 > Environment: NA > Reporter: Ashwini Kumar > Assigned To: Tom Baeyens > Priority: Critical > Fix For: jBPM jPDL 3.2.2 > > Original Estimate: 2 minutes > Remaining Estimate: 2 minutes > > Please change the readAssignmentDelegation method in org.jbpm.jpdl.xml.JpdlXmlReader to be the following. > The original method would ignore the class attribute assigned to swimlane assignments and default it to org.jbpm.identity.assignment.ExpressionAssignmentHandler > Thanks, > private Delegation readAssignmentDelegation(Element assignmentElement) { > Delegation assignmentDelegation = new Delegation(); > String expression = assignmentElement.attributeValue("expression"); > if (expression!=null) { > assignmentDelegation.setProcessDefinition(processDefinition); > String assignmentHandler = assignmentElement.attributeValue("class"); > if (assignmentHandler != null){ > assignmentDelegation.setClassName(assignmentHandler); > } > else{ > assignmentDelegation.setClassName("org.jbpm.identity.assignment.ExpressionAssignmentHandler"); > } > assignmentDelegation.setConfiguration("<expression>"+expression+"</expression>"); > > } else { > assignmentDelegation.read(assignmentElement, this); > } > return assignmentDelegation; > } -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1015) ProcessLogs that represent changes of process intance that take place within Timer.Execute are not saved in DB

by Gil Messerman (JIRA)

ProcessLogs that represent changes of process intance that take place within Timer.Execute are not saved in DB -------------------------------------------------------------------------------------------------------------- Key: JBPM-1015 URL: http://jira.jboss.com/jira/browse/JBPM-1015 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.1 Environment: Tomcat 5.0.28 or Jboss Reporter: Gil Messerman Assigned To: Tom Baeyens It seems to be a problem with Timer implementation. When some change in process occurs (such as transition or action call), the process instance should be added to jbpmContext to the list of auto saved process instances (actual saving occurs when JBPMContex.close() is called). Apparently Timer.execute does not do it and as a result, the log of all operations performed by Timer.execute is not stored in DB and getting lost. To fix the problem, the token.getProcessInstance() should be added to "autoSaveProcessInstances" list in JBPMContext. -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-823) Unable to call ejb remotely

by Sureshbabu Thyvalappil (JIRA)

Unable to call ejb remotely --------------------------- Key: EJBTHREE-823 URL: http://jira.jboss.com/jira/browse/EJBTHREE-823 Project: EJB 3.0 Issue Type: Bug Environment: JBOSS 4.0.5 with EJB 3.0 Reporter: Sureshbabu Thyvalappil I'm using JBOSS 4.0.5GA with ejb3. I am running into weird behavior when running java client from remote machine. If I run it from the same machine where the jboss server is running, no problem. So here is the behavior I'm noticing. FOr the jndi lookup of ejb, it is connecting the remote server and gets a reference to the ejb. But when I call a method on the ejb reference, it is trying to call a method on the local machine( I mean the same machine where the client is running). Sounds very weird to me. Any help is appreciated from EJB3 experts. I upgraded to EJB3 RC9 patch1, but same behavior. Here is the client code .. try { Properties p=new Properties(); p.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory"); p.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces"); p.put(Context.PROVIDER_URL,"jnp://remote-host:1099"); InitialContext ctx = new InitialContext(p); IReportService report = (IReportService) ctx.lookup( "ejb3/xxx/ReportService"); System.out.println("Got the ejb remote reference = "+report); System.out.println("report.resubmit.."+report.resubmit(null,0L)); ReportJob reportJob = new ReportJob(); System.out.println("B4 report.submitRequest.."); report.submitRequest(reportJob); System.out.println("After report.submitRequest.."); } catch (Exception e) { e.printStackTrace(); } -- 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, 10 months

4
7
0 / 0

[JBoss JIRA] Commented: (JBAS-2853) Integrate JBoss Cache 2.0 into AS 5.0

by Sacha Labourey (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2853?page=comments#action_12375113 ] Sacha Labourey commented on JBAS-2853: -------------------------------------- Any update on this? > Integrate JBoss Cache 2.0 into AS 5.0 > ------------------------------------- > > Key: JBAS-2853 > URL: http://jira.jboss.com/jira/browse/JBAS-2853 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JBoss Cache > Reporter: Manik Surtani > Assigned To: Brian Stansberry > Priority: Critical > Fix For: JBossAS-5.0.0.Beta3 > > > JBC 2.0.0.ALPHA1 was produced for JB5, Beta1. > I'm assigning this issue to the next beta, to track further integration 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

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1532) Write JMX MBeans chapter

by Julien Viet (JIRA)

Write JMX MBeans chapter ------------------------ Key: JBPORTAL-1532 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1532 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Reference Guide Reporter: Julien Viet Assigned To: Thomas Heute Fix For: 2.6.2 Final, 2.8 Final -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Commented: (JBPM-457) Parent process deployment does not link process-state with subprocess definition

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-457?page=comments#action_12375105 ] Tom Baeyens commented on JBPM-457: ---------------------------------- in the ant task DeployProcessTask i see: JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext(); try { ZipInputStream zipInputStream = new ZipInputStream(new FileInputStream(file)); ProcessDefinition processDefinition = ProcessDefinition.parseParZipInputStream(zipInputStream); jbpmContext.deployProcessDefinition(processDefinition); } finally { jbpmContext.close(); } in the DeployProcessCommand i see: public Object execute(JbpmContext jbpmContext) throws Exception { ProcessDefinition processDefinition = null; if (par != null && par.length > 0) { log.info("start parsing process from par"); // Thanks to George Mournos who helped to improve this: ZipInputStream zipInputStream = new ZipInputStream( new ByteArrayInputStream(par)); processDefinition = ProcessDefinition .parseParZipInputStream(zipInputStream); jbpmContext.deployProcessDefinition(processDefinition); log.info("deployment sucessfull"); } ... In the ProcessUploadServlet, i see: JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext(); try { response.setContentType("text/html"); response.getWriter().println(handleRequest(request)); } finally { jbpmContext.close(); } So I don't see where sub processes are being parsed without a JbpmContext. If you know a specific scenario in 3.2.1, please reopen the case > Parent process deployment does not link process-state with subprocess definition > -------------------------------------------------------------------------------- > > Key: JBPM-457 > URL: http://jira.jboss.com/jira/browse/JBPM-457 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Reporter: Eduardo Jimenez > Assigned To: Tom Baeyens > Priority: Critical > > From the ProcessState code: > Code: > if (jbpmSession != null) { > > // now, we must be able to find the sub-process > if (subProcessName != null) { > > // if the name and the version are specified > if (subProcessVersion != null) { > > try { > int version = Integer.parseInt(subProcessVersion); > // select that exact process definition as the subprocess definition > subProcessDefinition = jbpmSession.getGraphSession().findProcessDefinition(subProcessNam > e, version); > } catch (NumberFormatException e) { > jpdlReader.addWarning("version in process-state was not a number: " + processStateElement.asXML()); > } > > } else { // if only the name is specified > // select the latest version of that process as the subprocess > // definition > subProcessDefinition = jbpmSession.getGraphSession().findLatestProcessDefinition(subProces > sName); > } > } else { > jpdlReader.addWarning("no sub-process name specified in process-state " + processStateElement.asXML()); > } > } > > if there is no session open, it simply won't look for the parent process. > Now, from the ProcessArchiveDeployer: > Code: > public static void deployZipInputStream(ZipInputStream zipInputStream, JbpmSessionFactory jbpmSessio > nFactory) { > ProcessDefinition processDefinition = ProcessDefinition.parseParZipInputStream(zipInputStream); > deployProcessDefinition(processDefinition, jbpmSessionFactory); > } > > It reads the process definition first, then calls deploy, which opens the first jbpmSession!!!. The session must be open first before attempting to deploy!. > Now, you might say, use the ant task, but the bug is still there: > Code: > private void deploy(File file, JbpmSessionFactory jbpmSessionFactory) throws IOException, FileNotFou > ndException { > ZipInputStream zipInputStream = new ZipInputStream(new FileInputStream(file)); > ProcessArchiveDeployer.deployZipInputStream(zipInputStream,jbpmSessionFactory); > } > > See, the ant task doens't open a jbpmSession either, so its up to ProcessArchiveDeployer.deployZipInputStream() to do it, which is the same method I'm having an issue with. > Examining ProcessArchiveDeployer, every way of deploying a process would have the same problem. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-457) Parent process deployment does not link process-state with subprocess definition

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-457?page=all ] Tom Baeyens closed JBPM-457. ---------------------------- Fix Version/s: (was: jBPM jPDL 3.2.2) Resolution: Incomplete Description > Parent process deployment does not link process-state with subprocess definition > -------------------------------------------------------------------------------- > > Key: JBPM-457 > URL: http://jira.jboss.com/jira/browse/JBPM-457 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Reporter: Eduardo Jimenez > Assigned To: Tom Baeyens > Priority: Critical > > From the ProcessState code: > Code: > if (jbpmSession != null) { > > // now, we must be able to find the sub-process > if (subProcessName != null) { > > // if the name and the version are specified > if (subProcessVersion != null) { > > try { > int version = Integer.parseInt(subProcessVersion); > // select that exact process definition as the subprocess definition > subProcessDefinition = jbpmSession.getGraphSession().findProcessDefinition(subProcessNam > e, version); > } catch (NumberFormatException e) { > jpdlReader.addWarning("version in process-state was not a number: " + processStateElement.asXML()); > } > > } else { // if only the name is specified > // select the latest version of that process as the subprocess > // definition > subProcessDefinition = jbpmSession.getGraphSession().findLatestProcessDefinition(subProces > sName); > } > } else { > jpdlReader.addWarning("no sub-process name specified in process-state " + processStateElement.asXML()); > } > } > > if there is no session open, it simply won't look for the parent process. > Now, from the ProcessArchiveDeployer: > Code: > public static void deployZipInputStream(ZipInputStream zipInputStream, JbpmSessionFactory jbpmSessio > nFactory) { > ProcessDefinition processDefinition = ProcessDefinition.parseParZipInputStream(zipInputStream); > deployProcessDefinition(processDefinition, jbpmSessionFactory); > } > > It reads the process definition first, then calls deploy, which opens the first jbpmSession!!!. The session must be open first before attempting to deploy!. > Now, you might say, use the ant task, but the bug is still there: > Code: > private void deploy(File file, JbpmSessionFactory jbpmSessionFactory) throws IOException, FileNotFou > ndException { > ZipInputStream zipInputStream = new ZipInputStream(new FileInputStream(file)); > ProcessArchiveDeployer.deployZipInputStream(zipInputStream,jbpmSessionFactory); > } > > See, the ant task doens't open a jbpmSession either, so its up to ProcessArchiveDeployer.deployZipInputStream() to do it, which is the same method I'm having an issue with. > Examining ProcessArchiveDeployer, every way of deploying a process would have the same problem. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1019) 3.2.1 Admin Console: You can signal "ended" tokens/instances, causes an exception

by Burr Sutter (JIRA)

3.2.1 Admin Console: You can signal "ended" tokens/instances, causes an exception --------------------------------------------------------------------------------- Key: JBPM-1019 URL: http://jira.jboss.com/jira/browse/JBPM-1019 Project: JBoss jBPM Issue Type: Bug Components: Web Interface Affects Versions: jBPM jPDL 3.2.1 Reporter: Burr Sutter Assigned To: Tom Baeyens Fix For: jBPM jPDL 3.2.2 Signal shouldn't be an option for a token/process instance which has ended, right? -- 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, 10 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 September 2007