[JBoss-user] [EJB 3.0] - Re: Web Services with EJB3
anonymous wrote : what does this means? need some light here-is it something like: servlet->web service->java endpoint interface->java impl class->do lookup to ejb3? update: answer: yes, it worksweb->servlet->web service->java endpoints->ejb3. performance is good...web to ldap login, load personalisation data, all ejb3s in less than a sec. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3914370#3914370 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3914370 --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [EJB 3.0] - Re: Web Services with EJB3
hi, been to http://wiki.jboss.org/wiki/Wiki.jsp?page=WebservicesAndEJB3 ... wish the xtra code was unnecessary-need some careful packaging. it works though :) question: - can someone xplain this statement? anonymous wrote : It is also possible to use a Java Service Endpoint instead of an EJB endpoint. This is especially useful if no other EJB 2.x code is required and a web tier already exists. what does this means? need some light here-is it something like: servlet->web service->java endpoint interface->java impl class->do lookup to ejb3? plus: - how's WS-EJB3 coming? still jboss 5? second quarter 2006? will this possibly include arjunaTS? this will be excellent. I wish the WS-ejb3 can be released sooner. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3913077#3913077 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3913077 --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBoss jBPM] - Re: Internal Error Processing Dirty Regions with jBPM Graphi
btw, i'll be looking into the bpel/workflow capabilities of jbpm and see how it fits to current soa architecture and process models...was excited with the news of drools being incorporated into jbpm. currently we have tried oracle bpel engine with some good result, but we are keeping our options open before committing. had a quick glance at the end xml codes and have a gut feeling jbpm can fulfill the needs. just need to test it out now :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911333#3911333 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911333 --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBoss jBPM] - Re: Internal Error Processing Dirty Regions with jBPM Graphi
Hi, update and questions. 'So removing it in the top of the processdefinition removes this error' How do i do this? can u guide me which section do i need to remove pls? i tried: - remove the http to xsd section - totally removed xsi:schemaLocation both had the same effect: the jbpm gpd cannot be used anymore, even if i right click gpd.xml->open with->gpd. here's the generic processdefinition.xml: | | | http://jbpm.org/3/jpdl"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; | xsi:schemaLocation="http://jbpm.org/3/jpdl http://jbpm.org/xsd/jpdl-3.0.xsd"; | name="ThisIsATest"> | | tx for spending time on this, i'll continue evaluating jbpm but would love if the designer is available for usage. Need to start the tutorials somehow :) It'll be a plus point. fyi, we do have licenses of RSAwas wondering if u guys can share any experiences that u may have on designing the process models in RSA, auto create the necessary files and then deploy in jbpm, currently we are using jboss as the development platform. not entirely sure how this could work, RSA->jbpm->jboss. appreciate any insights/ideas that u may have:) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911331#3911331 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911331 --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBoss jBPM] - Re: Internal Error Processing Dirty Regions with jBPM Graphi
tx for the swift attention :) here's the .log snippet: (let me know if u need anyhting else) !ENTRY org.eclipse.core.runtime 4 2 2005-12-08 08:49:03.781 !MESSAGE An internal error occurred during: "Processing Dirty Regions". !STACK 0 java.lang.NoSuchMethodError: org.apache.xerces.xni.XMLResourceIdentifier.getNamespace()Ljava/lang/String; at org.eclipse.wst.xml.core.internal.validation.XMLValidator._internalResolveEntity(XMLValidator.java:348) at org.eclipse.wst.xml.core.internal.validation.XMLValidator$MyEntityResolver.resolveEntity(XMLValidator.java:326) at org.apache.xerces.impl.XMLEntityManager.resolveEntity(XMLEntityManager.java:545) at org.apache.xerces.impl.xs.traversers.XSDHandler$LocationResolver.resolveEntity(XSDHandler.java:277) at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:359) at org.apache.xerces.impl.xs.XMLSchemaValidator.parseSchemas(XMLSchemaValidator.java:2059) at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:1620) at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:556) at org.apache.xerces.impl.XMLNamespaceBinder.handleStartElement(XMLNamespaceBinder.java:832) at org.apache.xerces.impl.XMLNamespaceBinder.startElement(XMLNamespaceBinder.java:568) at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:809) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:752) at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(XMLDocumentScannerImpl.java:950) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1523) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:333) at org.apache.xerces.parsers.StandardParserConfiguration.parse(StandardParserConfiguration.java:525) at org.apache.xerces.parsers.StandardParserConfiguration.parse(StandardParserConfiguration.java:581) at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:147) at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1158) at org.eclipse.wst.xml.core.internal.validation.XMLValidator.validate(XMLValidator.java:216) at org.eclipse.wst.xml.ui.internal.validation.XMLValidator.validate(XMLValidator.java:71) at org.eclipse.wst.xml.ui.internal.validation.ValidateAction$1.run(ValidateAction.java:97) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1719) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1739) at org.eclipse.wst.xml.ui.internal.validation.ValidateAction.validate(ValidateAction.java:123) at org.eclipse.wst.xml.ui.internal.validation.core.ValidateAction.run(ValidateAction.java:206) at org.eclipse.wst.xml.ui.internal.validation.Validator.validate(Validator.java:70) at org.eclipse.wst.xml.ui.internal.validation.Validator.validate(Validator.java:92) at org.eclipse.wst.xml.ui.internal.validation.DelegatingSourceValidator.validate(DelegatingSourceValidator.java:189) at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.validate(ReconcileStepForValidator.java:221) at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.reconcileModel(ReconcileStepForValidator.java:188) at org.eclipse.jface.text.reconciler.AbstractReconcileStep.reconcile(AbstractReconcileStep.java:96) at org.eclipse.wst.sse.ui.internal.reconcile.validator.ValidatorStrategy.reconcile(ValidatorStrategy.java:176) at org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionProcessor.process(StructuredRegionProcessor.java:137) at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor.run(DirtyRegionProcessor.java:412) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76) i'll see what i can do with kukeltje's solution and give and update View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911320#3911320 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911320 --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBoss jBPM] - Re: Internal Error Processing Dirty Regions with jBPM Graphi
currently trying to evaluate jbpm with eclipse as the ide...already tried drools separately, verdict: thumbs up :) Having problems with the designer which I hope someone could drop in and give some insight env: - winXP pro 1gb ram notebook - eclipse3.1, myeclipse4.0 - downloaded jbpm-3.0.2.zip, jbpm-bpel-1.0-alpha3.zip,jbpm-gpd-feature-3.0.5.zip,jbpm-gpd-site-3.0.5.zip steps taken: - create new jbpm project through wizard - create new process defn..click finish immediately got the same error'An Internal error occured during "Processing Dirty Regions"the details button is locked. Yes, could continue drawing (on gpd.xml)...but it's annoying if it pops up for every single update. steps taken... - did a fresh installation of eclipse and repeated the designer installation steps result: -same darn thing happened does anyone have a solution? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911070#3911070 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911070 --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
