Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 22 09:17

    atooni on 3.2.2

    (compare)

  • Oct 20 09:17

    atooni on 3.2.2-RC1

    (compare)

  • Oct 20 09:17

    atooni on main

    Adjusting buffer size for multi… (compare)

  • Oct 20 08:28

    atooni on main

    Making ackTimeout explicit (compare)

  • Oct 09 08:49

    atooni on 3.2.1

    (compare)

  • Oct 09 08:38

    atooni on main

    Making sure LDAP context is sti… (compare)

  • Oct 09 07:52

    atooni on main

    Ensuring close of LDAP connecti… (compare)

  • Oct 07 04:28

    atooni on 3.2.1-RC1

    (compare)

  • Oct 06 15:22

    atooni on main

    Adding SCEP stand alone client … (compare)

  • Oct 01 04:55

    atooni on 3.2

    (compare)

  • Oct 01 03:19

    atooni on docs

    Reconfiguring documentation (compare)

  • Sep 18 15:27

    atooni on docs

    efactored exiting configuration… Removing obsolete files Removing obsolete files and 13 more (compare)

  • Sep 18 15:26

    atooni on main

    Setting the default listener co… (compare)

  • Sep 16 08:18

    atooni on main

    Refactoring id handling for tes… (compare)

  • Sep 15 16:47

    atooni on main

    Refine test handling in Roundtr… (compare)

  • Sep 15 14:51

    atooni on main

    Refine test logging for failing… (compare)

  • Sep 15 13:39

    atooni on main

    Refactoring test API to allow c… (compare)

  • Sep 15 08:38

    atooni on main

    Refactoring test API (compare)

  • Sep 11 13:10

    atooni on main

    Exposing exception when message… (compare)

  • Sep 11 11:38

    atooni on main

    Max limit for tests now relates… (compare)

Tobias Roeser
@lefou
@atooni The class ContainerInfo is currently located in bundle blended.container.registry and is meant to be shared between containers and the management node. In activated state, the bundle blended.container.registry acts as the management node. I strongly suggest to separate the ContainerInfo class from the active management node code. I'd like to discuss the best location with you.
Tobias Roeser
@lefou
My first naive idea was to just move ContainerInfo and Co. into blended.mgmt.base bundle. Unfortunately, it also implements DataObject from blended.persistence.
My hope is we can avoid inheriting DataObject at all.
Andreas Gies
@atooni
i ll touch base tomorrow morning
Tobias Roeser
@lefou
I'll ignore the persistence part for now to make progress. We can discuss persistence later.
Tobias Roeser
@lefou
@atooni Ping
Andreas Gies
@atooni
Pong
Tobias Roeser
@lefou
Because you asked: http://bikeshed.com/
Andreas Gies
@atooni
@lefou ping
Tobias Roeser
@lefou
@atooni: pong
Andreas Gies
@atooni
@lefou Just wanted to touch base
Tobias Roeser
@lefou
So, your are back home?
Andreas Gies
@atooni
ok….I have now pushed all my changes
Tobias Roeser
@lefou
@atooni Great, that you started cleaning up the code base.
One thing though. I'd like to keep the curly braces for simple variable replacements in strings. Or can you tell me a reason why s"a $var" is better than s"a ${var}"?
Andreas Gies
@atooni
Hmmm....not really. Primarily I was fixing things highlighted in the IDE. I think this is not even related to ScalaStyle, but comes from one of the IntelliJ inspections. We could create a profile for Scala Checks in IntelliJ that just highlights Scala Style and Codacy Meta issues.
Andreas Gies
@atooni
@/all Hi, I am currently working to fine tune the build image that has all the tools to build and test the blend core, itestsupport and also the ui. I will write up some doc later today, so new users will be able to get started with building blended without installing all the tools, especially stuff like the chromedriver for Selenium, npm, yarn and whatever ....
Tobias Roeser
@lefou
:+1:
Andreas Gies
@atooni
@/all The docker files will live on woq-blended/blended-docker. The sample LDAP server that we have used in the test will also move there
Andreas Gies
@atooni
@/all I have created and published the first cut of useful docker images at https://github.com/woq-blended/blended-docker. Please refer to the build image for a docker image that has all the tools required to build and test any of the sbt based projects
Andreas Gies
@atooni
That should read "refer to build-alpine"
Juanba98
@Juanba98
@atooni Hi i need help about the log when i run index-dev.html into the blended.mgmt.ui, because i don't know the credentials that i must introduce to login
Juanba98
@Juanba98
@atooni I have found two possible errors at the README.adoc at the building section, one is "blendedMgmtUiApp//fastOptJS/webpack" that should be "blendedMgmtUiApp/fastOptJS/webpack", and the other one is that the directory where the management console was build didn't be "./sampleApp/target/scala-2.12/scalajs-bundler/main" but it was "blended.mgmt.ui-master/mgmt-app/target/scala-2.12/scalajs-bundler/main"
Andreas Gies
@atooni
@Juanba98, to log into the management console, you will need a blended container up and running to connect to. Otherwise a login is impossible
For now you can take a look at the structure of the sample app and the components, especially the table and the tree
For starters, I would like to add a "sort" to the React Table, so that when you click on the header of one column the sort changes from NotSorted -> Ascending -> Descending -> Ascending -> Descending etc. Clicking on the header of another column should switch the sort order to that column
It might be an interesting task for you to think about how to implement this. Hint: You will need "state" on the level of the table component to keep track of the "current sorting state", which is to be modified whenever you click on one of the column headers
Andreas Gies
@atooni
secondly you will need to introduce a "sort function" which sorts the individual rows of the table in the desired order.
You can test and play with the changed table in the SampleApp
Of course, you will need to visualize the sorting state with a small icon next to the column header
Juanba98
@Juanba98
so i have to setup the sampleApp too?
Juanba98
@Juanba98
i mean how can i run it? because if i use the index-dev.html i just obtain a empty window @atooni
Andreas Gies
@atooni
I am wondering if we want to include the scala binary version in our symbolic names. We did not before, but with changing the build to potentially support multiple scalaversion may be we should
A side effect is that all config files would change their name as well as it is per default ${bundleSymbolicName}.conf
Tobias Roeser
@lefou
Yes, we should. We decided against before to avoid potential conflicts downstream, but IMHO we should correct this now.
Andreas Gies
@atooni
ok
Tobias Roeser
@lefou
@atooni You added another activator to blended.akka.http. Can you provide some context for it? dc48df13d8241417ecd48eac1f5c05fc08e0976d
Andreas Gies
@atooni
Yes. This is in relation to our ui projects. The idea is that in an UI project we do have the ScalaJS code that makes up the UI. The build process then goes and does its magic to apply webpack and create an OSGi bundle, so that the resulting UI can be hosted in a blended container. Within that magic we generate code for an Activator that is based on the Activator you have seen. I have included it in the core and Akka HTTP API because it seemed a common use case to me
In other words, It is to simplify the code generate and remove the boilerplate code to host the UI from the UI projects themselves
Tobias Roeser
@lefou
What's strange is that the bundle now has two activators
But only one is it's activator. Maybe it's just the misleading name.
Or we could move this into some kind of support package
Andreas Gies
@atooni
Could Rename it to something like ...ActivatorBase or ActivatorSupport
This a class that will never be instantiated itself, just inherited from
could also make it abstract
just saw it is abstract
it kind of belongs into that bundle unless we move the entire blended related API .... I would opt for renaming to something not ending in "activator"
Andreas Gies
@atooni
@lefou Do you think we should keep the projects creating the container separate from the integration tests ? - I am thinking along the lines that the result of a container project build are published / updated docker images. Then the integration test project could simply be turned into a nightly build grabing the latest image(s) of the containers and execute. Would probably also make it easier to create a configuration matrix, create a container for each element and IT test it