[JBoss Seam] - Re: propagation
by codelion
A question then is:
What's the different behavior then with the back-button in the browser, different for propagation "none" versus "end".
Seam supposedly (and as far as I have seen) is quite gracious about using the browser back button and then continuing to work from there.
But isn't that ability a bit dependent on the conversation still being around, either active or at least inactive?
So then if "none" has been used and the conversation is "gone", what will happen when the user uses the back button and goes to where that conversation has been? A new conversation, if configured right?
Where is the conversation stored anyway? Is that part of what we decide in web.xml to be javax.faces.STATE_SAVING_METHOD client or server? Or is the conversation independent of that? Always on server?
If on client, then does "client" store one conversation, or all inactive conversations as well? Maximum size in theory and in some real use sizes?
As summary question: Will the back button work better if we use "none", at higher cost of storing? Will the back button work less well if we use "end", but give benefit of less state being shuffled to client and back?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028487#4028487
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028487
19Â years, 1Â month
[JBoss jBPM] - Re: intigration of an jbpm with an webapplication.
by zipwow
I added this ant task to the starter kit buildfile:
<target name="build.warfile" depends="build.webapp, build.jbpm, build.identity, build.processes" description="builds jbpm-console-${jbpm.version}.war">
|
| <war destfile="build/jbpm-console-${jbpm.version}.war" webxml="src/resources/jbpm.war/WEB-INF/web.xml">
| <classes dir="src/resources/jbpm.war/WEB-INF/classes" />
|
| <!-- careful,the log4j logger is set to debug by default -->
| <zipfileset prefix="WEB-INF/classes" dir="src/config.files" />
| <zipfileset prefix="WEB-INF/classes" dir="build/classes.webapp" />
|
| <zipfileset prefix="" dir="src/resources/jbpm.war"/>
| <zipfileset prefix="WEB-INF/lib" dir="lib/jsf" />
| <zipfileset prefix="WEB-INF/lib" dir="lib/jboss" includes="**.jar, **.license*" excludes="**javax*"/>
| <zipfileset prefix="WEB-INF/lib" dir="lib/hibernate" />
| <zipfileset prefix="WEB-INF/lib" dir="lib/dom4j" />
| <zipfileset prefix="WEB-INF/lib" dir="lib/commons" />
| <zipfileset prefix="WEB-INF/lib" dir="build" includes="**.jar, **.license*" />
| </war>
| </target>
This probably includes more jarfiles than it needs, but it produces a warfile that at least starts up on Tomcat 5.5.16
-Kevin Klinemeier
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028483#4028483
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028483
19Â years, 1Â month
[EJB 3.0] - Stateless Session Beans - Static Variables - Concurrency and
by trickyvail
I've been trying to find out what (if any) consequences there may be for implementing static class variables inside ejb3 stateless session beans. I've created some beans in this manner and they appear to function as I would expect on a standalone JBoss server, but I'm concerned that this technique may break clustering.
Essentially I'm trying to cache seldomly updated data (in the database) that is requested very frequently on the web front end.
@Stateless
| public class CatalogBean implements Catalog
| {
| static boolean current = false;
| static String data = null;
|
| public void refresh()
| {
| current = false;
| }
|
| public String getData()
| {
| if(! current)
| {
| update();
| }
| return data;
| }
|
| private void update()
| {
| data = getDataFromTheDatabase();
| current = true;
| }
| }
Beans that are responsible for CRUD call the refresh method on this stateless bean - in turn updating their shared cache. My (hazy) understanding is that the ejb container is responsible to ensure that only one thread at a time can access a bean? Does this mean that different instances can be accessed concurrently - and therefore I could have syncronization issues? I suspect that static variables may be a bad idea - especially in a clustered environment.
Perhaps there is a different or recomended approach that I have not considered? Thank you in advance for all your comments and insights.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028479#4028479
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028479
19Â years, 1Â month
[JBossWS] - wsconsume -- unable to resolve type definition
by tperrigo
I'm trying to use wsconsume to generate a client for a (.NET) web service, but I'm getting the following error:
anonymous wrote :
| [exec] warning: src-resolve: Cannot resolve the name 'soapenc:Array' to a(n) 'type definition' component.
| [exec] line ? of http://oma-svr-miler1c/MultiMiler/RandWS_01/MileMaker.asmx?WSDL#types?sch...
| [exec] error: undefined simple or complex type 'soapenc:Array'
| [exec] line 0 of http://oma-svr-miler1c/MultiMiler/RandWS_01/MileMaker.asmx?WSDL#types?sch...
| [exec] error: undefined attribute 'soapenc:arrayType'
| [exec] line 0 of http://oma-svr-miler1c/MultiMiler/RandWS_01/MileMaker.asmx?WSDL#types?sch...
| [exec] error: undefined simple or complex type 'soapenc:Array'
| [exec] line 0 of http://oma-svr-miler1c/MultiMiler/RandWS_01/MileMaker.asmx?WSDL#types?sch...
| [exec] error: undefined attribute 'soapenc:arrayType'
| [exec] line 0 of http://oma-svr-miler1c/MultiMiler/RandWS_01/MileMaker.asmx?WSDL#types?sch...
| [exec] error: undefined simple or complex type 'soapenc:Array'
| [exec] line 0 of http://oma-svr-miler1c/MultiMiler/RandWS_01/MileMaker.asmx?WSDL#types?sch...
| [exec] error: undefined attribute 'soapenc:arrayType'
| [exec] line 0 of http://oma-svr-miler1c/MultiMiler/RandWS_01/MileMaker.asmx?WSDL#types?sch...
| [exec] error: undefined simple or complex type 'soapenc:Array'
| [exec] line 0 of http://oma-svr-miler1c/MultiMiler/RandWS_01/MileMaker.asmx?WSDL#types?sch...
| [exec] error: undefined attribute 'soapenc:arrayType'
| [exec] line 0 of http://oma-svr-miler1c/MultiMiler/RandWS_01/MileMaker.asmx?WSDL#types?sch...
| [exec] org.xml.sax.SAXParseException: undefined attribute 'soapenc:arrayType'
| [exec] at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModeler.java:213)
| [exec] at org.jboss.com.sun.tools.ws.processor.config.ModelInfo.buildModel(ModelInfo.java:88)
| [exec] at org.jboss.com.sun.tools.ws.processor.Processor.runModeler(Processor.java:82)
| [exec] at org.jboss.com.sun.tools.ws.wscompile.CompileTool.run(CompileTool.java:543)
| [exec] at org.jboss.com.sun.tools.ws.util.ToolBase.run(ToolBase.java:57)
| [exec] at org.jboss.ws.tools.jaxws.impl.WSContractConsumerImpl$1.run(WSContractConsumerImpl.java:163)
| [exec] at org.jboss.ws.tools.jaxws.impl.WSContractConsumerImpl.consume(WSContractConsumerImpl.java:166)
| [exec] at org.jboss.ws.tools.jaxws.command.wsconsume.importServices(wsconsume.java:194)
| [exec] at org.jboss.ws.tools.jaxws.command.wsconsume.main(wsconsume.java:77)
| [exec] Caused by: org.xml.sax.SAXParseException: undefined attribute 'soapenc:arrayType'
| [exec] at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.JAXBModelBuilder.bind(JAXBModelBuilder.java:128)
| [exec] at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildJAXBModel(WSDLModeler.java:2207)
| [exec] at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.internalBuildModel(WSDLModeler.java:224)
| [exec] at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModeler.java:181)
| [exec] ... 8 more
| [exec] Caused by: org.xml.sax.SAXParseException: undefined attribute 'soapenc:arrayType'
| [exec] at com.sun.xml.xsom.impl.parser.ParserContext$1.reportError(ParserContext.java:130)
| [exec] at com.sun.xml.xsom.impl.parser.NGCCRuntimeEx.reportError(NGCCRuntimeEx.java:131)
| [exec] at com.sun.xml.xsom.impl.parser.DelayedRef.resolve(DelayedRef.java:90)
| [exec] at com.sun.xml.xsom.impl.parser.DelayedRef.run(DelayedRef.java:65)
| [exec] at com.sun.xml.xsom.impl.parser.ParserContext.getResult(ParserContext.java:94)
| [exec] at com.sun.xml.xsom.parser.XSOMParser.getResult(XSOMParser.java:190)
| [exec] at com.sun.tools.xjc.ModelLoader.createXSOM(ModelLoader.java:487)
| [exec] at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImpl.java:203)
| [exec] at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImpl.java:67)
| [exec] at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.JAXBModelBuilder.bind(JAXBModelBuilder.java:126)
| [exec] ... 11 more
| [exec] error: org.xml.sax.SAXParseException: undefined attribute 'soapenc:arrayType'
|
I'm really quite clueless as to what this means, or how to resolve it. I'm using JBossWS 1.2.0.SP1 and JBoss 4.2.0.CR1. Any help would be very much appreciated!
Thanks,
Tim
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028474#4028474
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028474
19Â years, 1Â month