June 2007 - jboss-user - Jboss List Archives

[Messaging, JMS & JBossMQ] - Re: JBoss startup problems with existing messages in queue

by adrian＠jboss.org

It <depends> :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058163#4058163 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058163

18 years, 10 months

1
0
0 / 0

[JBoss Seam] - Re: entity update without submit

by pete.muir＠jboss.org

Try bypassUpdates="true" ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058162#4058162 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058162

18 years, 10 months

1
0
0 / 0

[JBoss Seam] - Re: Seam 2.0.0CR1 and 1.3.0GA

by enzhao

In case someone do not want to bother accessing the CVS or having trouble accessing CVS, here is the migration guide I saw this morning. Written by Gavin King. I think this will appear in the Seam site soon, but if you desparately want to get things straight now.... anonymous wrote : | Seam 2.0 Migration Guide | ======================== | Before you get started with Seam2, you'll need to make a few changes to | your existing code and configuration. This process should not be too | painful - if you get stuck, just refer back to the updated Seam examples. | | Supported container environments | -------------------------------- | Seam 2.0 has been tested on the following containers: | | * JBoss 4.2 (it is possible to run Seam2 on JBoss 4.0.5 by upgrading JSF) | * Tomcat 6.0 (Tomcat 5.5 is not compatible with JSF 1.2) | * GlassFish V2 | * OC4J 11g Technology Preview | | Migration to JSF 1.2 | -------------------- | Seam 2.0 requires JSF 1.2. We now recommend Sun's JSF RI as the most | mature JSF implementation, and this is the version that ships with | most EE 5 application servers, including JBoss 4.2. To switch to the | JSF RI, you'll need to make some changes to web.xml: | | * remove the MyFaces StartupServletContextListener | * remove the Ajax4JSF filter and mappings | * rename org.jboss.seam.web.SeamFilter to | org.jboss.seam.servlet.SeamFilter | | Also note that for the JSF RI, client-side state saving is not required. | | You'll also need to make some changes to faces-config.xml: | | * Remove the (Tranactional)SeamPhaseListener declaration | * Remove the SeamELResolver declaration, if you have one | * Change the declaration of SeamFaceletViewHandler to the standard | com.sun.facelets.FaceletViewHandler | | Since Seam 1.2, you didn't need any declarations of SeamExceptionFilter | or SeamRedirectFilter in web.xml, just a single declaration of | SeamFilter. Make sure you've already made that change. | | Code migration | -------------- | Seam's built-in components have undergone a major reorganization | designed to organize them for easier learning, and to isolate | dependencies upon particular technologies like JSF into specific | packages. | | * Persistence-related components moved to org.jboss.seam.persistence | * jBPM related components moved to org.jboss.seam.bpm | * JSF-related components moved org.jboss.seam.faces | * Servlet-related components have moved to org.jboss.seam.web | * Components related to asynchronicity moved to org.jboss.seam.async | * i18n-related components moved to org.jboss.seam.international | * The Pageflow component moved to org.jboss.seam.pageflow | * The Pages component moved to org.jboss.seam.navigation | | Code which depends on these APIs will need to be changed to reflect | the new Java package names. | | Annotations have also been reorganized: | | * BPM-related annotations moved to org.jboss.seam.annotations.bpm | * JSF-related annotations moved to org.jboss.seam.annotations.faces | * Interceptor annotations moved to | org.jboss.seam.annotations.intercept | * Annotations related to asynchronicity moved to | org.jboss.seam.annotations.async | * @RequestParameter moved to org.jboss.seam.annotations.web | * @WebRemote moved to org.jboss.seam.annotations.remoting | * @Restrict moved to org.jboss.seam.annotations.security | * Exception handling annotations moved to | org.jboss.seam.annotations.exception | | Migration of components.xml | --------------------------- | The new packaging comes with new namespaces and new schemas for | components.xml. The namespace for components in package | | org.jboss.seam.foobar | | Is now: | | http://jboss.com/products/seam/foobar | | And the schema is: | | http://jboss.com/products/seam/foobar-2.0.xsd | | You'll need to update your components.xml file to reflect that chance. | Take a look at the Seam examples if you're unsure of exactly what you | need to do. | | Finally, some declarations must be removed completely: | | * remove <conversation-is-long-running-parameter> from <core:init/> | * remove <core:ejb/> | * remove <core:microcontainer/> | * replace <core:transaction-listener/> with | <transaction:ejb-transaction/> | | Migration to JBoss Embedded | --------------------------- | Support for deployment to JBoss Embeddable EJB3 and JBoss Microcontainer | has been removed. Instead, the new JBoss Embedded distribution gives you | a full set of EE-compatible APIs with simplified deployment. | | For testing, you need the jars in Seam's lib/ directory, together with | the bootstrap/ directory in your classpath. SeamTest will automatically | start the container. Refer to the Seam examples, or seam-gen, if you have | trouble. | | For Tomcat deployment, follow the instructions in the user guide. You no | longer need any special configuration or packaging for Tomcat deployments. | | Note that JBoss Embedded is able to bootstrap a datasource from a -ds.xml | file, so there is no longer a need for jboss-beans.xml. | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058161#4058161 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058161

18 years, 10 months

1
0
0 / 0

[JBoss jBPM] - Re: Decision using java code

by nageshreddy1981

Thanks a lot if you can help me by leeting me know where can i find those. I will be greatfull. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058160#4058160 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058160

18 years, 10 months

1
0
0 / 0

[Messaging, JMS & JBossMQ] - Re: Message visible before transaction commit

by adrian＠jboss.org

java:/JmsXA View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058159#4058159 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058159

18 years, 10 months

1
0
0 / 0

[JBossWS] - Re: Jboss 4.2.0 and SQL Server

by davideling

Your problem is Hibernate related. When you load a persistent object it's related objects are lazily loaded. That is these objects aren't actually loaded, but will be loaded only when you try to access them. The problem take place when you access to lazily loaded object proxy when it's owner session is terminated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058158#4058158 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058158

18 years, 10 months

1
0
0 / 0

[Messaging, JMS & JBossMQ] - Re: SpyJMSException !!!

by adrian＠jboss.org

docs/examples/jms View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058157#4058157 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058157

18 years, 10 months

1
0
0 / 0

[JBoss Seam] - Re: My Upgrade Guide (1.2.1 to 1.3.0 CVS) for Glassfish user

by pete.muir＠jboss.org

Sorry, probably a bit grumpy as I've just been having dental work, which is never nice ;) That should have been anonymous wrote : Brilliant, thanks for the guide! Btw The jee5 example (used to be glassfish example) running fine on the latest promoted build of glassfish (b52 I think) in 2.0.0.CR1 - best to run the build, and take a look at the built ear/war/jar So, thanks :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058156#4058156 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058156

18 years, 10 months

1
0
0 / 0

[JBoss jBPM] - Re: JBPM Decision node implementation with Decision handler

by nageshreddy1981

the above is a new thread View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058155#4058155 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058155

18 years, 10 months

1
0
0 / 0

[JBoss jBPM] - Re: JBPM Decision node implementation with Decision handler

by nageshreddy1981

hi, i can create the decision handler classes as you have mentioned. My question is . I would like to create a decision node in my java code and then add a decision handler to it as i am editing my process definition by adding few more node in my through my application. -Nagesh View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058154#4058154 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058154

18 years, 10 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-user June 2007