May 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-6938) in KnownDeploymentTypes, JavaEEResourceAdaptor enum, should be named JavaEEResourceAdapter (i.e. "adapter" with an "e" rather than an "o")

by Ian Springer (JIRA)

in KnownDeploymentTypes, JavaEEResourceAdaptor enum, should be named JavaEEResourceAdapter (i.e. "adapter" with an "e" rather than an "o") ------------------------------------------------------------------------------------------------------------------------------------------ Key: JBAS-6938 URL: https://jira.jboss.org/jira/browse/JBAS-6938 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: ProfileService Affects Versions: JBossAS-5.1.0.CR1 Reporter: Ian Springer Assignee: Scott M Stark Fix For: JBossAS-5.1.0.GA -- 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

14 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-5044) Rework the JavaEE deployers to fix problems in the current implementation

by Adrian Brock (JIRA)

Rework the JavaEE deployers to fix problems in the current implementation ------------------------------------------------------------------------- Key: JBAS-5044 URL: http://jira.jboss.com/jira/browse/JBAS-5044 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Deployment services Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.Beta3, JBossAS-5.0.0.CR1 See the forum thread and subtasks for specific 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

14 years, 1 month

4
7
0 / 0

[JBoss JIRA] Created: (JBAS-5046) Move code from JBossEjbParsingDeployer out of createMetaData into relevant deployers

by Adrian Brock (JIRA)

Move code from JBossEjbParsingDeployer out of createMetaData into relevant deployers ------------------------------------------------------------------------------------ Key: JBAS-5046 URL: http://jira.jboss.com/jira/browse/JBAS-5046 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: EJB2, EJB3 Affects Versions: JBossAS-5.0.0.Beta3 Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.CR1 The processing that is now in JBossEjbParsingDeployer.createMetaData() should be moved into more relevant deployers. -- 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

14 years, 1 month

4
6
0 / 0

[JBoss JIRA] Created: (JBAOP-792) Port weaving synchronization to 1.5

by Flavia Rainone (JIRA)

Port weaving synchronization to 1.5 ----------------------------------- Key: JBAOP-792 URL: https://jira.jboss.org/browse/JBAOP-792 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 1.5.6.GA, 1.5.5 CP04 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 1.5.7.GA We need to have synchronization on Branch 1.5. Whilst this has been implemented in newer versions, we lack this mechanism in the older versions. Since trunk is somewhat different from branch 1.5, we need to adapt what we have in trunk. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (GPD-392) Force a transition to have its name in case of Fork

by Toshiya Kobayashi (JIRA)

Force a transition to have its name in case of Fork --------------------------------------------------- Key: GPD-392 URL: https://jira.jboss.org/jira/browse/GPD-392 Project: jBPM GPD Issue Type: Feature Request Components: jpdl Affects Versions: jBPM jPDL Designer 3.1.7, jBPM jPDL Designer 3.2 Reporter: Toshiya Kobayashi Assignee: Koen Aers When you add transitions from a fork to nodes, GPD omits the name of the first transition. <fork name="fork1"> <transition to="node1" ></transition> <transition to="node2" name="to node2"></transition> <transition to="node3" name="to node3"></transition> </fork> This works without problem. Tokens go to node1, node2, node3. But, after some modification, you may have a process definition like: <fork name="fork1"> <transition to="node1" name="to node1"></transition> <transition to="node2" ></transition> <transition to="node3" name="to node3"></transition> </fork> In this case, tokens go to node1, node1, node3. Because if there is a transition without name, the child token goes to default leaving transition (in this case, node1). This problem may be fixed on jBPM side, but forcing a transition to have its name on GDP side will help users avoid such odd process definition. -- 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

14 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (GPD-391) Limit assignment operation for Start Task

by Toshiya Kobayashi (JIRA)

Limit assignment operation for Start Task ----------------------------------------- Key: GPD-391 URL: https://jira.jboss.org/jira/browse/GPD-391 Project: jBPM GPD Issue Type: Feature Request Components: jpdl Affects Versions: jBPM jPDL Designer 3.1.7 Reporter: Toshiya Kobayashi Assignee: Koen Aers Priority: Minor TaskMgmtInstance#createStartTaskInstance() fills actorId with authenticatedActorId regardless <assignment> settings in <task> in <start-state>. But currently GPD allows users to assign the start task (e.g. to actor). It's useless and confuses them. See attached screen shot. So this request is "In case of Start State, only 'Swimlane' should be selectable in Task -> Assignment tab." -- 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

14 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-599) repository blacklisted messages with new Nexus repo

by Emmanuel Bernard (JIRA)

repository blacklisted messages with new Nexus repo --------------------------------------------------- Key: JBBUILD-599 URL: https://jira.jboss.org/jira/browse/JBBUILD-599 Project: JBoss Build System Issue Type: Bug Components: Artifact Repositories Reporter: Emmanuel Bernard I've updated my settings.xml and see weird errors when building my projects (Hibernate Search in this case) {code} [INFO] Scanning for projects... [INFO] artifact org.eclipse.wst.css:core: checking for updates from jboss-public-repository-group [WARNING] repository metadata for: 'artifact org.eclipse.wst.css:core' could not be retrieved from repository: jboss-public-repository-group due to an error: Authorization failed: Access denied to: https://repository.jboss.org/nexus/content/groups/developer/org/eclipse/w... [INFO] Repository 'jboss-public-repository-group' will be blacklisted [INFO] artifact org.eclipse.wst.css:core: checking for updates from twdata-m2-repository [WARNING] repository metadata for: 'artifact org.eclipse.wst.css:core' could not be retrieved from repository: twdata-m2-repository due to an error: Authorization failed: Access denied to: https://repository.jboss.org/nexus/content/groups/developer/org/eclipse/w... [INFO] Repository 'twdata-m2-repository' will be blacklisted [INFO] artifact org.eclipse.wst.css:core: checking for updates from jboss-public-repository-group [WARNING] repository metadata for: 'artifact org.eclipse.wst.css:core' could not be retrieved from repository: jboss-public-repository-group due to an error: Authorization failed: Access denied to: https://repository.jboss.org/nexus/content/groups/developer/org/eclipse/w... [INFO] Repository 'jboss-public-repository-group' will be blacklisted [INFO] artifact org.eclipse.wst.css:core: checking for updates from repository.jboss.com [WARNING] repository metadata for: 'artifact org.eclipse.wst.css:core' could not be retrieved from repository: repository.jboss.com due to an error: Authorization failed: Access denied to: https://repository.jboss.org/nexus/content/groups/developer/org/eclipse/w... [INFO] Repository 'repository.jboss.com' will be blacklisted [INFO] artifact org.eclipse.wst.css:core: checking for updates from maven-repository.dev.java.net [WARNING] repository metadata for: 'artifact org.eclipse.wst.css:core' could not be retrieved from repository: maven-repository.dev.java.net due to an error: Authorization failed: Access denied to: https://repository.jboss.org/nexus/content/groups/developer/org.eclipse.w... [INFO] Repository 'maven-repository.dev.java.net' will be blacklisted [INFO] artifact org.eclipse.wst.css:core: checking for updates from central [WARNING] repository metadata for: 'artifact org.eclipse.wst.css:core' could not be retrieved from repository: central due to an error: Authorization failed: Access denied to: https://repository.jboss.org/nexus/content/groups/developer/org/eclipse/w... [INFO] Repository 'central' will be blacklisted {code} Here is my settings.xml for info {code} <?xml version="1.0"?> <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"> <interactiveMode>true</interactiveMode> <offline>false</offline> <pluginGroups> <pluginGroup>org.jboss.maven.plugins</pluginGroup> <pluginGroup>org.twdata.maven</pluginGroup> </pluginGroups> <activeProfiles> <activeProfile>jboss-public-repository</activeProfile> </activeProfiles> <profiles> <profile> <id>jboss-public-repository</id> <properties> <maven.repository.root>/Users/manu/projects/notbackedup/repository.jboss.org</maven.repository.root> <jdk16_home>/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/</jdk16_home> </properties> <repositories> <repository> <id>jboss-public-repository-group</id> <name>JBoss Public Maven Repository Group</name> <url>https://repository.jboss.org/nexus/content/groups/public/</url> <layout>default</layout> <releases> <enabled>true</enabled> <updatePolicy>never</updatePolicy> </releases> <snapshots> <enabled>true</enabled> <updatePolicy>never</updatePolicy> </snapshots> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>jboss-public-repository-group</id> <name>JBoss Public Maven Repository Group</name> <url>https://repository.jboss.org/nexus/content/groups/public/</url> <layout>default</layout> <releases> <enabled>true</enabled> <updatePolicy>never</updatePolicy> </releases> <snapshots> <enabled>true</enabled> <updatePolicy>never</updatePolicy> </snapshots> </pluginRepository>  <pluginRepository> <id>twdata-m2-repository</id> <name>twdata.org Maven 2 Repository</name> <url>http://twdata-m2-repository.googlecode.com/svn/</url> </pluginRepository> </pluginRepositories> </profile> </profiles> <servers> <server> <id>jboss-developer-repository-group</id>  </server> <server> <id>jboss-snapshots-repository</id>  </server> <server> <id>jboss-releases-repository</id>  </server> </servers> <mirrors> <mirror> <id>jboss-developer-repository-group</id> <mirrorOf>*,!jboss-deprecated</mirrorOf> <name>JBoss.org Developer Repository Group</name> <url>https://repository.jboss.org/nexus/content/groups/developer/</url> </mirror> </mirrors> </settings> {code} -- 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

14 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBEE-31) Add saaj-api_1.3_spec

by Richard Opalka (JIRA)

Add saaj-api_1.3_spec --------------------- Key: JBEE-31 URL: https://jira.jboss.org/jira/browse/JBEE-31 Project: JBoss JavaEE APIs Issue Type: Sub-task Reporter: Richard Opalka Assignee: Shelly McGowan Fix For: 6.0.0.Alpha1 -- 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

14 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBEE-28) Add jboss-jaxws-api_2.2_spec

by Richard Opalka (JIRA)

Add jboss-jaxws-api_2.2_spec ---------------------------- Key: JBEE-28 URL: https://jira.jboss.org/jira/browse/JBEE-28 Project: JBoss JavaEE APIs Issue Type: Sub-task Reporter: Richard Opalka Assignee: Shelly McGowan Fix For: 6.0.0.Alpha1 -- 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

14 years, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (JBEE-30) Add jaxb-api_2.2_spec

by Richard Opalka (JIRA)

Add jaxb-api_2.2_spec --------------------- Key: JBEE-30 URL: https://jira.jboss.org/jira/browse/JBEE-30 Project: JBoss JavaEE APIs Issue Type: Sub-task Reporter: Richard Opalka Assignee: Shelly McGowan Fix For: 6.0.0.Alpha1 -- 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

14 years, 1 month

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2010