Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Florian-Schoenherr
    @Florian-Schoenherr
    Hi @mstefaniuk I just saw this, that was just a mistake of mine. There was some tremendous work on the Xoom Starter UI, so these Screenshots will soon be replaced.
    The endpoint should just be POST /accounts :)
    Don Alfons Nisnoni
    @donnisnoni
    Hi guys.. I just made a PR. Need someone to review 🙂. Have a good day!!
    Vaughn Vernon
    @VaughnVernon
    @donnisnoni Thanks! I asked @Florian-Schoenherr to review.
    Vaughn Vernon
    @VaughnVernon
    @mstefaniuk I definitely speak REST with a DDD accent. My point is that when using REST over HTTP it is typical to think in terms of the 4-5 primary verbs, which is CRUD, and that leads to an anemic model. In essence implementing a Java or C# anemic/data model is waste. It should be Transaction Script. Please read the info box in our documentation: https://docs.vlingo.io/vlingo-http
    If using REST with a true behavioral domain model you want to, as you said, "reify" REST requests to behaviors on your domain model. That's what VLINGO encourages.
    Marcin Stefaniuk
    @mstefaniuk
    @VaughnVernon Now I understand your reasoning. I consider exposing domain model up to REST interface as an antipattern - flavour of that is described https://dzone.com/articles/domain-model-rest-anti-pattern.
    Marcin Stefaniuk
    @mstefaniuk
    Difference between domain and interfaces is usually addressed by adapter (eg. in hexagonal architecture) so there should not be direct link between REST and domain model.
    @Florian-Schoenherr Great!
    Vaughn Vernon
    @VaughnVernon
    @mstefaniuk Yes, it's an anti-pattern unless your platform ecosystem affords a Compressed Ports & Adapters Architecture, and have an Application Layer is actually a waste of effort.
    Vaughn Vernon
    @VaughnVernon
    In the Ports and Adapters Architecture the outside adapters adapt driver side requests to the Application Layer. In the case of VLINGO, the Application Layer and Domain Layer are one and the same. Aggregate actors are a perfect, race-free transactional boundary.
    Marcin Stefaniuk
    @mstefaniuk
    @VaughnVernon Thank you for explanation. It sounds reasonable and lean. Could you point me to any public product based on this approach that I can listen to REST with a DDD accent in the wild?
    Vaughn Vernon
    @VaughnVernon
    @mstefaniuk I don't think there is much "in the wild." IIRC @stilkov (Stefan Tilkov) had at some point discussed this.
    Vaughn Vernon
    @VaughnVernon
    @/all As a followup to the previous question about a GraphQL server for the platform, we have an initial implementation: vlingo-graphql. It's demo worthy but we will wait until we have better integration with actors as resolvers.
    Brian Wehrle
    @bwehrle
    Hi, I'm having some build problems with vlingo-http that I believe has to do with recent changes, perhaps?
    [INFO] Building vlingo-http 1.6.1-SNAPSHOT
    [INFO] --------------------------------[ jar ]---------------------------------
    Downloading from ossrh-snapshots: https://oss.sonatype.org/content/repositories/snapshots/io/vlingo/vlingo-common/1.6.1-SNAPSHOT/maven-metadata.xml
    Downloaded from ossrh-snapshots: https://oss.sonatype.org/content/repositories/snapshots/io/vlingo/vlingo-common/1.6.1-SNAPSHOT/maven-metadata.xml (2.0 kB at 1.4 kB/s)
    Downloading from ossrh-snapshots: https://oss.sonatype.org/content/repositories/snapshots/io/vlingo/vlingo-common/1.6.1-SNAPSHOT/vlingo-common-1.6.1-20210408.210144-16.pom
    Downloaded from ossrh-snapshots: https://oss.sonatype.org/content/repositories/snapshots/io/vlingo/vlingo-common/1.6.1-SNAPSHOT/vlingo-common-1.6.1-20210408.210144-16.pom (7.3 kB at 17 kB/s)
    Downloading from ossrh-snapshots: https://oss.sonatype.org/content/repositories/snapshots/io/vlingo/xoom/xoom-common/1.6.1-SNAPSHOT/xoom-common-1.6.1-20210408.210144-16.pom
    [WARNING] The POM for io.vlingo.xoom:xoom-common:jar:1.6.1-20210408.210144-16 is missing, no dependency information available
    [WARNING] The POM for io.vlingo.xoom:xoom-common:jar:1.6.1-20210408.210144-16 is missing, no dependency information available
    First, somehow I'm getting deps which are different than the project's defined deps (io.vlingo:vlingo-common -> io.vlingo.xoom:xoom-common). Second, these deps have no POMs.
    Now it appears to be working with latest pull from master..
    Vaughn Vernon
    @VaughnVernon
    @bwehrle Oops. We are doing repository renaming for rebranding purposes and the Java packages are also changing. It was not suppose to cause dependencies to break because those should be preserved, not deleted. If you check again on Friday it should all be settled. Apologies for the inconvenience.
    Vaughn Vernon
    @VaughnVernon
    Friday look for xoom-http to replace vlingo-http. Also the package names have gone from io.vlingo.http to io.vlingo.xoom.http.
    Brian Wehrle
    @bwehrle
    Got it, no problem.
    Marcus Lange
    @marcuslange
    I’m trying out the xoom GUI. In Aggregates I try to create a new aggregate and look to have everything filled out. The Add button stays disabled and there’s no feedback in the UI as to what the issue is. Any ideas?
    Vaughn Vernon
    @VaughnVernon
    @marcuslange Thanks for trying out XOOM Designer. At every location that displays a required field message, check that all fields are entered. I have had this happen and the blank field is right there but I didn't notice at first.
    Vaughn Vernon
    @VaughnVernon
    @marcuslange I recall that we did fix some usability issues last week that are still in the snapshot build. If you are using the current stable version you are probably hitting that. Please see the README for how to get the snapshot build package:
    Jonathan
    @steele232

    Hi all. I'm trying out Xoom Developer and I hit a snag. I installed Xoom Dev via Docker and that was great. I went through a couple scenarios quickly and I had one failure-to-generate without an error and then I succeeded in generating a project with a super simple domain and CQRS turned off and things. I was able to load up that project in Intellij but mvn clean package failed with a freemarker error. It seems like the bug is deep inside vlingo so I couldn't see any code for me to be able to change. I tried this once with the UI generation toggled on and once with the UI generation toggled off and both gave freemarker errors that caused the builds to fail. mvn compile works fine but mvn package does not. Any help would be appreciated.

    [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile (default-compile) on project hello-eric: Compilation failure
    [ERROR] freemarker.core.InvalidReferenceException: The following has evaluated to null or missing:
    [ERROR]   ==> imports  [in template "codegen/java/RestResource.ftl" at line 21, column 8]
    ...
    [ERROR]   FTL stack trace ("~" means nesting-related):
    [ERROR]       - Failed at: #list imports as import  [in template "codegen/java/RestResource.ftl" at line 21, column 1]

    Any help would be appreciated. PS I really love what vlingo promises.

    Vaughn Vernon
    @VaughnVernon
    That's
    Vaughn Vernon
    @VaughnVernon
    @steele232 That's strange. As far as I know we don't use Freemarker in the general XOOM runtime, only during the Designer codegen phase. Can you provide the JSON model that was saved with each project generation? You can submit an issue here:
    Danilo Ambrósio
    @danilo-ambrosio
    @steele232
    We're investigating this issue. Could you please share the designer-model.json file under the root folder of your generated project?
    Jonathan
    @steele232
    Thanks @VaughnVernon and @danilo-ambrosio , I created a Github issue per your suggestion and it has my designer-model.json file attached. I changed the extension to ".txt" because Github refused a ".json" file.
    Github issue: vlingo/xoom-designer#113
    Direct link to designer-model.json: https://github.com/vlingo/xoom-designer/files/6983935/designer-json.txt
    Vaughn Vernon
    @VaughnVernon
    Thanks, @steele232 Danilo is working on a fix. It seems to be something in a compile-time annotation (maybe a configuration choice we have not encountered... missing a test).
    Jonathan
    @steele232
    Awesome, thank you so much
    Vaughn Vernon
    @VaughnVernon

    @steele232 This has been fixed. Please see the following for details and confirm the fix:

    https://github.com/vlingo/xoom-designer/issues/113#issuecomment-899652759

    Jonathan
    @steele232
    Okay, I will try that out soon.
    My concern is basically resolved because I just wanted to get something to run
    My next step will be to run some requests against a generated API
    Danilo Ambrósio
    @danilo-ambrosio
    Excellent @steele232 !
    I'm not sure if you're familiar with the Designer API section (in the Aggregate Dialog). Note that you can easily create API endpoints by clicking on the "+" button:
    image.png
    Jonathan
    @steele232
    Perfect @danilo-ambrosio I'll try to give that a shot today
    Jonathan
    @steele232
    Hi @danilo-ambrosio and @VaughnVernon I ran into one or more issues. Do you want me to make Github issues for those? Essentially it seems I can't access the HTTP endpoint.
    But also one of the tests fail so I skipped the tests.
    Trying out the HTTP endpoint gives me a no-connection error.
    Vaughn Vernon
    @VaughnVernon
    @steele232 Thanks for the update. I'm glad you reported these outliers and that we had an opportunity to fix them and close the issue. Thanks again for your contribution to the upcoming release 1.8.4.