October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-747) bad documentation

by Jon Stevens (JIRA)

bad documentation ----------------- Key: EJBTHREE-747 URL: http://jira.jboss.com/jira/browse/EJBTHREE-747 Project: EJB 3.0 Issue Type: Bug Components: Documentation Reporter: Jon Stevens http://docs.jboss.org/ejb3/app-server/tutorial/relationships/relationship... @JoinTable(table = @Table(name = "flight_customer_table"), joinColumns = {@JoinColumn(name = "FLIGHT_ID")}, inverseJoinColumns = {@JoinColumn(name = "CUSTOMER_ID")}) the "table =" is wrong. This url...has it correct... http://docs.jboss.org/ejb3/app-server/tutorial/relationships/src/org/jbos... -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-424) stories example failes to compile

by jarkko Lietolahti (JIRA)

stories example failes to compile --------------------------------- Key: JBSEAM-424 URL: http://jira.jboss.com/jira/browse/JBSEAM-424 Project: JBoss Seam Issue Type: Bug Components: Examples Affects Versions: 1.1 Environment: Seam CVS / JBoss 4.0.5.CR1 / EJB 3 RC9 Reporter: jarkko Lietolahti Buildfile: /home/jarkko/seam-workspace/jboss-seam/examples/remoting/stories/build.xml init: [echo] Build Seam Stories Example 1.1 [mkdir] Created dir: /home/jarkko/seam-workspace/jboss-seam/examples/remoting/stories/build/classes compile: [javac] Compiling 6 source files to /home/jarkko/seam-workspace/jboss-seam/examples/remoting/stories/build/classes [javac] /home/jarkko/seam-workspace/jboss-seam/examples/remoting/stories/src/stories/ProjectsBean.java:5: cannot find symbol [javac] symbol : class Interceptors [javac] location: package javax.ejb [javac] import javax.ejb.Interceptors; [javac] ^ [javac] /home/jarkko/seam-workspace/jboss-seam/examples/remoting/stories/src/stories/StoriesBean.java:3: cannot find symbol [javac] symbol : class Interceptors [javac] location: package javax.ejb [javac] import javax.ejb.Interceptors; [javac] ^ [javac] /home/jarkko/seam-workspace/jboss-seam/examples/remoting/stories/src/stories/ProjectsBean.java:18: cannot find symbol [javac] symbol: class Interceptors [javac] @Interceptors(SeamInterceptor.class) [javac] ^ [javac] /home/jarkko/seam-workspace/jboss-seam/examples/remoting/stories/src/stories/StoriesBean.java:13: cannot find symbol [javac] symbol: class Interceptors [javac] @Interceptors(SeamInterceptor.class) [javac] ^ [javac] Note: /home/jarkko/seam-workspace/jboss-seam/examples/remoting/stories/src/stories/Project.java uses unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [javac] 4 errors BUILD FAILED /home/jarkko/seam-workspace/jboss-seam/build.xml:314: Compile failed; see the compiler error output for details. Total time: 1 second -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-423) seam-poker: Type cannot be determined for component [Component(playerAction)]. Please ensure that it has a local interface.

by jarkko Lietolahti (JIRA)

seam-poker: Type cannot be determined for component [Component(playerAction)]. Please ensure that it has a local interface. --------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-423 URL: http://jira.jboss.com/jira/browse/JBSEAM-423 Project: JBoss Seam Issue Type: Bug Components: Examples Affects Versions: 1.1 Reporter: jarkko Lietolahti 56160 00:11:40,539 ERROR [STDERR] 16.10.2006 21:11:40 com.sun.facelets.compiler.TagLibraryConfig loadImplicit INFO: Added Library from: jar:file:/home/jarkko/jboss/jboss-4.0.5.CR1/server/default/tmp/deploy/tmp60979seam-poker.ear-contents/seam-poker-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-html.taglib.xml 256610 00:11:40,989 ERROR [SeamServletFilter] Error java.lang.RuntimeException: Type cannot be determined for component [Component(playerAction)]. Please ensure that it has a local interface. at org.jboss.seam.remoting.InterfaceGenerator.appendComponentSource(InterfaceGenerator.java:283) at org.jboss.seam.remoting.InterfaceGenerator.generateComponentInterface(InterfaceGenerator.java:130) at org.jboss.seam.remoting.InterfaceGenerator.handle(InterfaceGenerator.java:100) at org.jboss.seam.remoting.SeamRemotingServlet.doPost(SeamRemotingServlet.java:76) at org.jboss.seam.remoting.SeamRemotingServlet.doGet(SeamRemotingServlet.java:62) at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:153) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:619) -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-271) Add graphical support for super states

by Syed Arshad (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-271?page=comments#action_12345331 ] Syed Arshad commented on JBPM-271: ---------------------------------- any idea about the release of this feature? > Add graphical support for super states > -------------------------------------- > > Key: JBPM-271 > URL: http://jira.jboss.com/jira/browse/JBPM-271 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Graphical Process Designer > Reporter: Koen Aers > Assigned To: Koen Aers > -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMICROCONT-11) Extend the VDF BasicComponent to handle http and/or webdav

by Scott M Stark (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-11?page=all ] Scott M Stark updated JBMICROCONT-11: ------------------------------------- Fix Version/s: (was: JBossMC_2_0_0RC1) > Extend the VDF BasicComponent to handle http and/or webdav > ---------------------------------------------------------- > > Key: JBMICROCONT-11 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-11 > Project: JBoss MicroContainer > Issue Type: Feature Request > Components: Deployment > Environment: org.jboss.deployment.vdf.plugins.basic > Reporter: Dimitris Andreadis > > Currently it handles locals files/directories (file:/...../xx) so it should be extended to handle remote urls, including webdav enabled ones. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-63) MicroContainer work for JBoss-5.0.0.Beta

by Scott M Stark (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-63?page=all ] Scott M Stark updated JBAS-63: ------------------------------ Due Date: 03/Nov/06 We need to tie this to an mc 2.0.0 release. > MicroContainer work for JBoss-5.0.0.Beta > ---------------------------------------- > > Key: JBAS-63 > URL: http://jira.jboss.com/jira/browse/JBAS-63 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: MicroContainer bus > Reporter: Adrian Brock > Priority: Blocker > Fix For: JBossAS-5.0.0.Beta > > > Schedule -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMICROCONT-57) Add VFS prototype for review/testing

by Scott M Stark (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-57?page=all ] Scott M Stark closed JBMICROCONT-57. ------------------------------------ Resolution: Done We have the VFS working. The only remaining issue is refactoring the isArchive attribute which is really a deployment related feature. This refactoring should be another issue. > Add VFS prototype for review/testing > ------------------------------------ > > Key: JBMICROCONT-57 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-57 > Project: JBoss MicroContainer > Issue Type: Task > Components: Deployment > Reporter: Scott M Stark > Assigned To: Scott M Stark > Priority: Critical > Fix For: JBossMC_2_0_0RC1 > > > Need to get the VFS prototype into jboss-head for evaluation. The basic VFS interface needs to be validated and the initial file system based implementation proven usable. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-140) Move responsibility for management of delivery list from receiver into channel

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-140?page=all ] Ovidiu Feodorov updated JBMESSAGING-140: ---------------------------------------- Fix Version/s: 1.2.0.CR1 (was: 1.2.0.Beta1) > Move responsibility for management of delivery list from receiver into channel > ------------------------------------------------------------------------------ > > Key: JBMESSAGING-140 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-140 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.CR1 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Currently each receiver has the responsibility for managing it's list of deliveries. This is to avoid a race condition whereby the message can be acked before the call to handle has returned. > This is a high burden of responsibility for the receiver and results in a lot of unnecessary code in the receiver implementation, plus an extra hashmap lookup > We should consider whether we can give the responsibiltty to the channel. > We could still acknowledge and cancel throught the delivery object, by creating one when required and calling cancel/acknowledge on it. > the instance of delivery won't contain a message reference but just a message id. then inside delivery.cancel()/acknowledge(), it calls > channel.cancel(this) and the channel is smart enought to lookup the delivery/reference as required. > This won't require ANY changes to the receiver/channel interface and will allow us to get rid of the delivery list -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-275) Move Selector processing IN the Channel

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-275?page=all ] Ovidiu Feodorov updated JBMESSAGING-275: ---------------------------------------- Fix Version/s: 1.2.0.CR1 (was: 1.2.0.Beta1) > Move Selector processing IN the Channel > --------------------------------------- > > Key: JBMESSAGING-275 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-275 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Fix For: 1.2.0.CR1 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Currently, a consumer "arrests" a message that is being handled to it and doesn't match the Selector. That means it returns an active Delivery for it, but it doesn't forward the message to the client. This is because the consumer needs to be able to receiver further messages coming after the non-matching message, and that may potentially match the selector. > This is a poor solution that doesn't scale. We may end up with lots of non-matching messages being "arrested" by a consumer, while they could just be simply returned to the channel and forwarded to other potential consumers. > A possible (right) approach is to move selector processing in the Channel, so the message is not even handled to the non-accepting cosumer. Review this and refactor. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-314) Ensure Messaging core has no dependencies on the JMS facade

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-314?page=all ] Ovidiu Feodorov updated JBMESSAGING-314: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.2.0.Beta1) > Ensure Messaging core has no dependencies on the JMS facade > ----------------------------------------------------------- > > Key: JBMESSAGING-314 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-314 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Fix For: 1.2.1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Messaging core still has some dependencies on the jms facade. These should be factored out. -- 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, 7 months

1
0
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 October 2006