December 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBXB-254) expose Unmarshaller[Factory].WarnOnParserErrors property via JBossXBHelper

by Alexey Loubyansky (JIRA)

expose Unmarshaller[Factory].WarnOnParserErrors property via JBossXBHelper -------------------------------------------------------------------------- Key: JBXB-254 URL: https://jira.jboss.org/browse/JBXB-254 Project: JBoss XML Binding (JBossXB) Issue Type: Task Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky This is related to JBAS-8268 and JBXB-252. This property needs to be exposed so the deployers can in their turn expose it as a config option. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBXB-255) misspelled UnorderedSequenceWIthCollections.xml

by Alexey Loubyansky (JIRA)

misspelled UnorderedSequenceWIthCollections.xml ----------------------------------------------- Key: JBXB-255 URL: https://jira.jboss.org/browse/JBXB-255 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky UnorderedSequenceWIthCollections.xml the 'I' in 'WIth' should be lower-cased. Why did it work on windows?.. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2815) Simplify build profiles and make the default profile faster

by Geoffrey De Smet (JIRA)

Simplify build profiles and make the default profile faster ----------------------------------------------------------- Key: JBRULES-2815 URL: https://jira.jboss.org/browse/JBRULES-2815 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Components: All Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Fix For: 5.2.0.M1 >From mailing list: I 'd like to refactor the maven build to use exactly 3 profiles and remove all other profiles: * default o Fast, for during development * full o Slow, but builds everything. Used by hudson, releases and before you go to sleep * soa o Prunes the non-soa stuff away What do you think? Long explanation: * The maven build is too slow atm: o GWT compilation of all permutations (during development 1 permutation is enough) * yet some parts of the code don't build with maven o such as + in the past GWT compilation + antlr generation + eclipse plugin + examples o problems with this approach + they use unmanaged dependency versions (antlr generation might use a different version than antlr dependency in pom) + require tool installations (gwt dev kit under /home/Rikkola/gwt :) + commit generated files to svn o adding them to maven will make the maven build even slower... unless... The profiles are too complicated, currently we have these profiles: * default (the one you run with "mvn clean install") o Build these too + drools-clips + drools-planner + drools-pipeline + drools-simulator + osgi-bundles o Proposition: don't build those in soa * documentation o Build drools-docs too o Proposition: merge into profile full * build-eclipse o Build drools-eclipse too o Proposition: merge into profile full * cibuild (hudson) o Build these too: + drools-docs + drools-eclipse + drools-examples too o In drools-process, build these too: + drools-bpel + drools-jpdl o Proposition: merge into profile full * soa o in drools (parent) + assembly: use soa assembly description alternatives o in drools-guvnor + change some tokens in some files (ant based, not maven filtering yet) + run pre-integration-test o in drools-eclipse + Don't build org.drools.eclipse.task o in drools-docs + Don't build drools-docs-planner and drools-docs-integration * grammars o in drools-core and drools-compiler + runs the antlr file generation o Proposition: replace with maven antlr plugin + if fast, do part of the default profile and output to target dir + if slow, do part of the full profile and output to src dir (just as it is now) * gen-brms-import (not part of any top-level build) o Proposition: Leave it alone until we deal with that commented out module bulk-importer-util * ydoc-doclet (commented out on drools parent pom) o Proposition: remove it -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2161) Implement @WebService support for @Singleton EJB3 beans

by Richard Opalka (JIRA)

Implement @WebService support for @Singleton EJB3 beans ------------------------------------------------------- Key: EJBTHREE-2161 URL: https://jira.jboss.org/browse/EJBTHREE-2161 Project: EJB 3.0 Issue Type: Bug Components: ejb3_1 Reporter: Richard Opalka Assignee: Carlo de Wolf <ropalka> carlo, When @Stateless session beans are @WebService annotated, they usually implement this org.jboss.wsf.spi.invocation.integration.ServiceEndpointContainer <carlo> ropalka: right, let me check spec, but I think WS endpoint is allowed on Singleton <carlo> ropalka: okay, singleton container needs to implement that spi. I see a couple of problems with its dependencies though. -- 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

15 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1832) Client.removeListener() should be called before Client.disconnect() is called.

by Yong Hao Gao (JIRA)

Client.removeListener() should be called before Client.disconnect() is called. ------------------------------------------------------------------------------ Key: JBMESSAGING-1832 URL: https://jira.jboss.org/browse/JBMESSAGING-1832 Project: JBoss Messaging Issue Type: Bug Reporter: Yong Hao Gao Assignee: Yong Hao Gao (From Ron) there are a bunch of Remoting threads that are created but not > destroyed. These are BisocketServerInvoker$ControlConnectionThreads. > They run on the client and handle "create connection" requests from > the server coming in on the control connection. > > When org.jboss.remoting.Client.addListener() is called, a > BisocketServerInvoker is created on the client side, and a > BisocketServerInvoker$ControlConnectionThread is created. When > Client.removeListener() is called, the > BisocketServerInvoker$ControlConnectionThread is shut down. But in > this case (and it happened in one other support case), the number of > BisocketServerInvoker$ControlConnectionThreads just keeps growing. I > created a jboss-remoting.jar with extra logging which shows that > JBossMessaging doesn't seem to be calling Client.removeListener() > before it calls Client.disconnect(). > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2818) Deploy Task Service as Jboss Service

by Cristiano Nicolai (JIRA)

Deploy Task Service as Jboss Service ------------------------------------ Key: JBRULES-2818 URL: https://jira.jboss.org/browse/JBRULES-2818 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-process-task Affects Versions: 5.1.1.FINAL Environment: Jboss AS 5.1 Reporter: Cristiano Nicolai Assignee: Mark Proctor Deploy a new Jboss Service (.sar) with the required jars to start the MinaTaskServer and manage it using admin-console. The drools-process-task jar shouldn't package the persistence.xml file because will cause the server to try to deploy the persistence unit. In order to have the mbean exposed in the admin-console I included the following in the rhq-plugin.xml: <service name="Drools Task Server" description="Drools Task Server" displayName="Drools Task Server" discovery="org.rhq.plugins.jmx.MBeanResourceDiscoveryComponent" class="org.rhq.plugins.jmx.MBeanResourceComponent"> <runs-inside> <parent-resource-type name="JMX Server" plugin="JMX"/> <parent-resource-type name="JBossAS Server" plugin="JBossAS"/> <parent-resource-type name="JBossAS Server" plugin="JBossAS5"/> </runs-inside> <plugin-configuration> <c:simple-property name="objectName" readOnly="true" default="org.drools:type=DroolsTaskServer"/> </plugin-configuration> <operation name="start" displayName="Start" /> <operation name="stop" displayName="Stop" /> </service> -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2817) Make the KnowledgeAgent Tests more robust and faster

by Mark Proctor (JIRA)

Make the KnowledgeAgent Tests more robust and faster ---------------------------------------------------- Key: JBRULES-2817 URL: https://jira.jboss.org/browse/JBRULES-2817 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-5745) ServerMBean.InShutdown flag won't turn on when the shutdown hook is called directly

by Takayoshi Kimura (JIRA)

ServerMBean.InShutdown flag won't turn on when the shutdown hook is called directly ----------------------------------------------------------------------------------- Key: JBAS-5745 URL: http://jira.jboss.com/jira/browse/JBAS-5745 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: System service Affects Versions: JBossAS-5.0.0.CR1, JBossAS-5.0.0.Beta4, JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA, JBossAS-4.2.1.GA, JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta2, JBossAS-5.0.0.Beta1, JBossAS-4.0.5.GA, JBossAS-4.0.4.GA Reporter: Takayoshi Kimura Assigned To: Dimitris Andreadis The ServerMBean.InShutdown flag is only turned on when the shutdown() operation is called. There is another shutdown path, a shutdown hook called by signals including Ctrl+c. This flag is needed to update in the shutdownHook.shutdown() method to reflect the sever status. -- 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, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-656) RichFaces project: current build problems

by Ilya Shaikovsky (JIRA)

RichFaces project: current build problems ----------------------------------------- Key: JBBUILD-656 URL: https://jira.jboss.org/browse/JBBUILD-656 Project: JBoss Build System Issue Type: Bug Components: Artifact Repositories Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 22:16:01+0300) Java version: 1.6.0_20 Reporter: Ilya Shaikovsky 1) https://jira.jboss.org/browse/RF-9483 - I was not able to build RF 3.3.3 as far as moved my environment to new PC (except local maven repo :( ) Note - removing wagon dependency I'm running with another "not found" issues. Last time when I succesfully tried with clean repo and it was fine - was before going to Nexus. 2) I even can't build the RF-4.0.0 project with *clean install* getting [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-clean-plugin Reason: POM 'org.apache.maven.plugins:maven-clean-plugin' not found in repositor y: Unable to download the artifact from any repository org.apache.maven.plugins:maven-clean-plugin:pom:2.3 from the specified remote repositories: jboss-deprecated (https://repository.jboss.org/nexus/content/repositories/depr ecated/), jboss-public-repository-group (http://repository.jboss.org/nexus/content/group s/public/) Note - works if execute just install for sure.. all the other dependencies fine. Check my environment and my settings.xml attached. Sorry if missed something obvious during migration and please point me to the right direction in that case. -- 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

15 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-267) Fix Top NameIgnoreMechanism

by Ales Justin (JIRA)

Fix Top NameIgnoreMechanism --------------------------- Key: JBDEPLOY-267 URL: https://jira.jboss.org/browse/JBDEPLOY-267 Project: JBoss Deployers Issue Type: Bug Reporter: Ales Justin Top NIM should check the paths relative to top level. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 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 2010