Moqui - Issue retaining/passing the URL parameter -

-

i have referred similar issue on github (issue#18), nothing there worked me.

i trying use following transition/service:

<transition name="storecontactinfo">     <service-call name="mantle.party.contactservices.store#partycontactinfo" in-map="context" out-map="context" />     <default-response url="." /> </transition>

the url parameter screen workeffortid, gets stripped url once transition run.

i tried, no avail:

<transition name="storecontactinfo">     <path-parameter name="workeffortid"/>     <service-call name="mantle.party.contactservices.store#partycontactinfo" in-map="context" out-map="context" /> <default-response url="." >     <parameter name="workeffortid" from="workeffortid" /> </default-response> </transition>

and tried adding in action tag, saw resolved issue previously. didn't work either.

my other transitions screen work fine. there still issue there, or doing wrong?

i using 1.5.1.

update: assume problem doing , not previous issue #18.

following through maps , values passed through, seems there significant complexity understand - evolving through get#partycontactinfo through stupidutilities.flattennestedmap (creates single map fields passed in map , nested maps , removes entries null value map) through store#partycontactinfo called in transition utilises number of conditions passed through drive partyforms.xml#contactinfo.

i have tried pass value through right first service call:

<set field="partyid" from="facility.ownerpartyid" /> <service-call name="mantle.party.contactservices.get#partycontactinfo" out-map="projectsitecontactinfo" in-map="[partyid:partyid, workeffortid:workeffortid, postalcontactmechpurposeid:'postalshippingdest', telecomcontactmechpurposeid:'phoneshippingdest', emailcontactmechpurposeid:'emailshippingdest']" />

... way through, reason it's not coming out other side.

the solution add workeffortid field (hidden) in /mantle-usl/template/party/partyforms.xml#contactinfo widget component called in container dialogue before transition.

i see once added:

<parameter name="workeffortid" value="${workeffortid}" />

to transition, workeffort indeed null, , must getting stripped out somewhere.

adding workeffortid contactinfo form resolved issue.


Comments

Post a Comment

Popular posts from this blog

java - Custom OutputStreamAppender not run: LOGBACK: No context given for <MYAPPENDER> -

-
i wish write custom appender on basis of outputstreamappender . wrote following class package tests; import java.io.ioexception; import java.io.outputstream; import ch.qos.logback.core.outputstreamappender; public class myappender<e> extends outputstreamappender<e> { public myappender() { system.out.println("myappender created"); setoutputstream(new outputstream() { @override public void write(int b) throws ioexception { throw new unsupportedoperationexception(); } }); } } then wrote following runner: package tests; import org.slf4j.loggerfactory; import ch.qos.logback.classic.logger; public class runner { private static final logger log = (logger) loggerfactory.getlogger(runner.class); public static void main(string[] args) { //log.addappender(new myappender<iloggingevent>()); log.info("hello world"); } } finall...
Read more

java - UML - How would you draw a try catch in a sequence diagram? -

-
Image
is there standard way of drawing try catch sequence diagrams? i've made attempt based on this feel end result doesn't feel right. code diagram based around: public static void save () { try { filehandle filehandle = gdx.files.external(file); filehandle.writestring(boolean.tostring(constantshandler.soundenabled)+"\n", false); (int = 0; < 5; i++) { filehandle.writestring(integer.tostring(constantshandler.highscores[i])+"\n", true); } } catch (throwable e) { } } my attempt note: know still need add loop. that's ok. fragments meant show conditional control flow in sequence diagram. superstructures puts limitations on use of fragments (see pp. 467 of ss2.1.1). should use critical region try part above. , option catch . however, keep telling can take quite freedom in using uml. it's language , such changes in life time. long reader ge...
Read more

c++ - No viable overloaded operator for references a map -

-
i trying use map can make tag names reference number. when try , use it, in code error (6 in total every time reference map): src/main.cpp:25:45: error: no viable overloaded operator[] type 'std::map<std::string, std::string>' const char* idcs = node.child_value(tagmap[3]); this code: #include "pugi/pugixml.hpp" #include <iostream> #include <string> #include <map> int main() { pugi::xml_document doca, docb; std::map<std::string, pugi::xml_node> mapa, mapb; std::map<std::string, std::string> tagmap {{"1", "data"}, {"2", "entry"}, {"3", "id"}, {"4", "content"}}; if (!doca.load_file("a.xml") || !docb.load_file("b.xml")) { std::cout << "can't find input files"; return 1; } (auto& node: doca.child(tagmap[1]).children(tagmap[2])) { co...
Read more