January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBESB-3) JBI core prototype

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-3?page=all ] Mark Little updated JBESB-3: ---------------------------- Fix Version/s: 5.0 > JBI core prototype > ------------------ > > Key: JBESB-3 > URL: http://jira.jboss.com/jira/browse/JBESB-3 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JBI > Reporter: Ovidiu Feodorov > Assigned To: Daniel Brum > Fix For: 5.0 > > -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-369) WAR deployment

by Mark Little (JIRA)

WAR deployment -------------- Key: JBESB-369 URL: http://jira.jboss.com/jira/browse/JBESB-369 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.0 CR2 Reporter: Mark Little Assigned To: Kevin Conner Priority: Optional Fix For: 4.0 Support for running within a Tomcat container, BEA and IBM. -- 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

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-136) Metadata Builder util class

by Ales Justin (JIRA)

Metadata Builder util class --------------------------- Key: JBMICROCONT-136 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-136 Project: JBoss MicroContainer Issue Type: Task Components: MetaData Reporter: Ales Justin Assigned To: Ales Justin Priority: Optional Fix For: JBossMC_2_0_0_CR1 Introducing C++ or StringBuffer kind of metadata Builder class: public class Builder { public Builder addPropertyMetaData(String propertyName) { ... return this; } } -- 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

19 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-134) Introduce KernelControllerContextAware into each KernelControllerContextAction

by Ales Justin (JIRA)

Introduce KernelControllerContextAware into each KernelControllerContextAction ------------------------------------------------------------------------------ Key: JBMICROCONT-134 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-134 Project: JBoss MicroContainer Issue Type: Task Components: Kernel Reporter: Ales Justin Assigned To: Ales Justin Priority: Minor Fix For: JBossMC_2_0_0_CR1 Since there were issues on where this KernelControllerContextAware support should be, we can introduce it in all Actions - as an optional overridding implementation. Maybe we can also introduce some fine grained Aware interfaces - depending on the state they support / are 'aware' of. -- 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

19 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-119) Add support for integer progression

by Adrian Brock (JIRA)

Add support for integer progression ----------------------------------- Key: JBMICROCONT-119 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-119 Project: JBoss MicroContainer Issue Type: Feature Request Components: BeanInfo Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock There are a number of places where it might be useful to support integer progression, e.g. float -> int or Float -> Integer and vice versa. This will mean that the exact type is not necessary when doing for example injection from one bean to another. -- 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

19 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-374) Getting Started Project Template for Eclipse/Ant

by Mark Little (JIRA)

Getting Started Project Template for Eclipse/Ant ------------------------------------------------ Key: JBESB-374 URL: http://jira.jboss.com/jira/browse/JBESB-374 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.0 CR2 Reporter: Mark Little Assigned To: Mark Little Priority: Optional Fix For: 4.0 -- 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

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-137) VirtualFile.findChild("WEB-INF/classes") fails for SyntheticDirEntries

by Thomas Diesler (JIRA)

VirtualFile.findChild("WEB-INF/classes") fails for SyntheticDirEntries ---------------------------------------------------------------------- Key: JBMICROCONT-137 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-137 Project: JBoss MicroContainer Issue Type: Bug Components: VFS Reporter: Thomas Diesler Priority: Blocker I have two WARs. The first (generated by the CTS porting layer) fails because the DeploymentUnit.classLoader cannot load com.sun.ts.tests.webservices.deploy.warDeploy.HelloJavaBean The reason is that WEB-INF/classes is not added to the the the classloader [tdiesler@localhost cts]$ jar -tf WarDeployApp_web.war WarDeploy.xml WEB-INF/webservices.xml WEB-INF/wsdl/WarDeploy.wsdl WEB-INF/classes/com/sun/ts/tests/webservices/deploy/warDeploy/HelloJavaBean.class WEB-INF/classes/com/sun/ts/tests/webservices/deploy/warDeploy/HelloWs.class WEB-INF/web.xml META-INF/MANIFEST.MF The second (generated by ant) is fine. It contains jar entries for every directory level [tdiesler@localhost cts]$ jar -tf jaxrpc-samples-jsr109pojo-rpc.war META-INF/ META-INF/MANIFEST.MF WEB-INF/ WEB-INF/classes/ WEB-INF/classes/org/ WEB-INF/classes/org/jboss/ WEB-INF/classes/org/jboss/test/ WEB-INF/classes/org/jboss/test/ws/ WEB-INF/classes/org/jboss/test/ws/jaxrpc/ WEB-INF/classes/org/jboss/test/ws/jaxrpc/samples/ WEB-INF/classes/org/jboss/test/ws/jaxrpc/samples/jsr109pojo/ WEB-INF/classes/org/jboss/test/ws/jaxrpc/samples/jsr109pojo/JaxRpcJSEEndpoint.class WEB-INF/classes/org/jboss/test/ws/jaxrpc/samples/jsr109pojo/JaxRpcTestService.class WEB-INF/classes/org/jboss/test/ws/jaxrpc/samples/jsr109pojo/SimpleUserType.class WEB-INF/wsdl/ WEB-INF/jaxrpc-mapping.xml WEB-INF/webservices.xml WEB-INF/wsdl/TestService.wsdl WEB-INF/web.xml I set this as blocking issue because all WS war deployments fail that don't have a WEB-INF/classes jar entry. -- 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

19 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-699) Ensure remoting implements true asynchronous callbacks

by Tim Fox (JIRA)

Ensure remoting implements true asynchronous callbacks ------------------------------------------------------ Key: JBMESSAGING-699 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-699 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Priority: Blocker We need to chase remoting to make sure they implement true asynchronous invocations. We need these for delivering messages from the server to the client, and for sending certain invocations from client to server. Without this, performance will greatly suffer. A "true" asynchonous callback is where the invocation is written to the transport using the same thread as the invoking thread, and returns immediately. It does not wait to read a response, and it just execute a normal invocation using a thread from a pool and discard the result. -- 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

19 years, 3 months

2
5
0 / 0

[JBoss JIRA] Resolved: (JBAS-3183) Integration with WebSphere MQ 5.x

by Weston Price (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3183?page=all ] Weston Price resolved JBAS-3183. -------------------------------- Resolution: Done A new JcaXAResourceWrapper has been added to allow for the isSameRMOverrideValue mechanism. This will enable JBoss to enlist multiple WASMQ resources in the same transaction. Note, the configuration for this will be specified on the Wiki, but the short of it is that the isSameRMOverrideValue is now configurable per datasource/connection-factory definition; it is not just for JDBC resources. Depending upon demmand, this fix may need to be ported to previous JBoss releases to address WASMQ integration issues. > Integration with WebSphere MQ 5.x > --------------------------------- > > Key: JBAS-3183 > URL: http://jira.jboss.com/jira/browse/JBAS-3183 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMS service > Environment: WebSphereMQ 5.3 with Extended TX client > Reporter: Luc Texier > Assigned To: Weston Price > Priority: Critical > Fix For: JBossAS-4.2.0.CR1 > > Attachments: mq-trace.jar, mq-xa.zip > > > http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingWebSphereMQSeriesWithJBossA... > we need to make some changes to StdServerSession and StdServerSessionPool to integrate two workarounds in order to properly integrate with WSMQ 5.x and support their XA resource implementation and transaction handling -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-156) consistent packaging

by Kurt Stam (JIRA)

consistent packaging -------------------- Key: JBESB-156 URL: http://jira.jboss.com/jira/browse/JBESB-156 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kurt Stam Assigned To: Mark Little Can we do some more refactoring of package names? For example I'd like to see everything in 'product/core/common' directory to be rooted in the org.jboss.soa.esb.common.* package. 'product/core/services' directory to be rooted in the org.jboss.soa.esb.services.* package. Somehow it's all mixed up right now and I keep on having to click around to find classes. -- 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

19 years, 3 months

2
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 January 2007