August 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-6722) Hot deployment broken with JBoss 5.0.1.GA

by Jozef Hartinger (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-6722?page=com.atlassian.jira.plug... ] Jozef Hartinger commented on JBAS-6722: --------------------------------------- I have verified that hot deployment of Seam components and xhtml files works with EAP 5 build from http://hudson.qa.jboss.com/hudson/view/EAP-CI/job/JBoss-EAP-5.0.x-noauth/... and JBDS 2.1 nightly build from http://reports.qa.atl.jboss.com/binaries/RHDS/nightly/2.1.0.GA/2009080518... > Hot deployment broken with JBoss 5.0.1.GA > ----------------------------------------- > > Key: JBAS-6722 > URL: https://jira.jboss.org/jira/browse/JBAS-6722 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Component > Environment: JBoss 5.0.1 GA > JDK 5 update 16 > Seam trunk > Reporter: Jozef Hartinger > Assignee: Ales Justin > Priority: Critical > > Hot deployment does not seem to work. I am using seam-gen to create a war packaged application and deploy it on JBoss 5.0.1 GA. It deploys fine, but: > a) deployment of XHTML template > modified facelet templates are not being picked up > b) deployment of action Java Bean > I run new-action to create a ping action component and run "explode" target. Component does not deploy. There is nothing in the server log that would indicate that server is even trying to load the component. > All mentioned above works fine on JBoss 4.2.3 and JBoss 5.0.0 -- 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

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (BPEL-308) Support variable initialization per OASIS BPEL 2.0 spec

by Aleksander Adamowski (JIRA)

Support variable initialization per OASIS BPEL 2.0 spec ------------------------------------------------------- Key: BPEL-308 URL: https://jira.jboss.org/jira/browse/BPEL-308 Project: JBoss jBPM BPEL Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Engine Affects Versions: jBPM BPEL 1.1 GA Reporter: Aleksander Adamowski Assignee: Alejandro Guizar OASIS Web Services Business Process Execution Language Version 2.0 specification, section 8.1, states that variables can be initialized upon definition: "The syntax of the <variables> declaration is: <variables> <variable name="BPELVariableName" messageType="QName"? type="QName"? element="QName"?>+ from-spec? </variable> </variables> .... A variable can optionally be initialized by using an in-line from-spec. From-spec is defined in section 8.4. Conceptually the in-line variable initializations are modeled as a virtual <sequence> activity that contains a series of virtual <assign> activities, one for each variable being initialized, in the order they are listed in the variable declarations. The virtual <assign> activities each contain a single virtual <copy> whose from-spec is as given in the variable initialization and the to-spec points to the variable being created. [SA00026] Variable initialization logic contained in scopes that contain or whose children contain a start activity MUST only use idempotent functions in the from-spec. The use of idempotent functions allows for all the values for such variables to be pre-computed and re-used on each process instance. " The Eclipse BPEL Business Process Editor supports this - one can select a variable, and in its properties panel choose "Initialization" tab, then e.g. specify From = "Expression", Expression language = "Same as Process (XPath 1.0 in BPEL 2.0)" and input an expression. Here's an example of such generated variable specification: <bpws:variable name="myVariable"> <bpws:from> <![CDATA[number(123)]]> </bpws:from> </bpws:variable> Unfortunately, jBPM BPEL ignores initialization from spec: DEBUG [org.jbpm.context.exe.VariableContainer] create variable 'myVariable' in 'TokenVariableMap10d7fa4' with value '[myVariable: null]' This feature of BPEL spec should be supported. -- 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

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (BPEL-244) Support for BPEL process instance monitoring in jBPM admin console

by Meghana Joglekar (JIRA)

Support for BPEL process instance monitoring in jBPM admin console ------------------------------------------------------------------ Key: BPEL-244 URL: http://jira.jboss.com/jira/browse/BPEL-244 Project: JBoss jBPM BPEL Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Engine Reporter: Meghana Joglekar Assigned To: Alejandro Guizar One can currently run BPEL processes on jBPM engine and check the log files to see the runtime report. But this process is not efficient in monitoring how the process is doing, what processes are running, what went wrong when a fault occurred etc. It will be nice to have administration console to see this information. The administration console can then list the process instances that are running, show visual graph of the instance and for each node in the graph more information about it. ActiveBPEL and OracleBPEL both provide such consoles and they are great tools for administrators. It will be nice if it also provides 'delete' functionality for stalled processes or old processes. The list could go on but in its basic form, processes listing, process instance listing and then more information about them [instances] will be useful. -- 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

15 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (SECURITY-427) Mapping Type - Attribute

by Anil Saldhana (JIRA)

Mapping Type - Attribute ------------------------ Key: SECURITY-427 URL: https://jira.jboss.org/jira/browse/SECURITY-427 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX, Security SPI Affects Versions: JBossSecurity_2.0.3.SP2 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: JBossSecurity_2.0.4 Attribute mapping mainly to gather attributes (email, department etc) to apply for a principal. -- 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

15 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-429) ModuleOption: additional constructor to take the name and value

by Anil Saldhana (JIRA)

ModuleOption: additional constructor to take the name and value --------------------------------------------------------------- Key: SECURITY-429 URL: https://jira.jboss.org/jira/browse/SECURITY-429 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security SPI Affects Versions: JBossSecurity_2.0.3.SP2 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: JBossSecurity_2.0.4 -- 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

15 years, 8 months

1
1
0 / 0

test

by Bounced mail

The message was undeliverable due to the following reason(s): Your message could not be delivered because the destination server was unreachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely there is a network problem that prevented delivery, but it is also possible that the computer is turned off, or does not have a mail system running right now. Your message could not be delivered within 5 days: Server 213.129.30.230 is not responding. The following recipients did not receive this message: <jboss-jira(a)lists.jboss.org> Please reply to postmaster(a)lists.jboss.org if you feel this message to be in error.

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-140) add payload into user defined Constraint

by Jeff Zhang (JIRA)

add payload into user defined Constraint ---------------------------------------- Key: JBJCA-140 URL: https://jira.jboss.org/jira/browse/JBJCA-140 Project: JBoss JCA Issue Type: Task Components: Deployer Affects Versions: 1.0.0.Alpha2 Reporter: Jeff Zhang Assignee: Jeff Zhang Fix For: 1.0.0.Alpha3 the Constraint in the ra16user303.rar ra16user303jbossra.rar need payload parameter "contains Constraint annotation, but does not contain a payload parameter." -- 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

15 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-209) Introduce file filter that only accepts files matched by some FileMatcher

by Ales Justin (JIRA)

Introduce file filter that only accepts files matched by some FileMatcher ------------------------------------------------------------------------- Key: JBDEPLOY-209 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-209 Project: JBoss Deployers Issue Type: Feature Request Affects Versions: JBDEPLOY-2.0.8.GA Reporter: Ales Justin Assignee: Ales Justin Fix For: JBDEPLOY-2.2.x FileStructure already implements all the needed pieces, hence it can be easily used as this filter. -- 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

15 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2227) nested DSL Constraints don't work because compiler adds comma at beginning

by Frederik Reifschneider (JIRA)

nested DSL Constraints don't work because compiler adds comma at beginning -------------------------------------------------------------------------- Key: JBRULES-2227 URL: https://jira.jboss.org/jira/browse/JBRULES-2227 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler-DSL Affects Versions: 5.0.1.FINAL Reporter: Frederik Reifschneider Assignee: Mark Proctor Priority: Minor The following DSL expression: [condition]When there are {facts} which dont match constraints=not( forall ( {facts}( ))) [condition]When there is a {fact} with the following constraints={fact} ( ) [condition]- {field} has a value={field} != null [condition]- {field} has no value={field} == null || matches "[\S]*" with the rule: When there are Projects which dont match constraints - description has no value - objectives has a value produces: not( forall ( ProjectRow(, description == null || matches "[S]*", objectives != null ))) everything works just as expected except the comma in front of "description". When using the rule "When there is a {fact} with the following constraints" everything works fine as described in the documentation. -- 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

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-1022) S3_PING: discovery protocol using S3

by Bela Ban (JIRA)

S3_PING: discovery protocol using S3 ------------------------------------ Key: JGRP-1022 URL: https://jira.jboss.org/jira/browse/JGRP-1022 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.6.12, 2.8 -- 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

15 years, 8 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2009