Drawing and some layout help for a simple control: thin lines and application start

Question

I am trying to create a new, simple control. The control should act as a grouping marker much like that found in the Mathematica notebook interface. It is designed to sit to the right of a node and draw a simple bracket. The look of the bracket changes depending on whether the node is logically marked open or closed.
After looking at some blogs and searching, I tried setting the snapToPixels to true in the container holding the marker control as well as the strokewidth but I am still finding that the bracket line is too thick. I am trying to draw a thin line. Also, I am unable to get the layout to work when the test application is first opened. One of the outer brackets is cut-off. I hardcoded some numbers into the skin just to get something to work.
Is there a better way to implement this control?
How can I get the fine line drawn as well as the layout correct at application start?
package org.notebook;
import javafx.beans.property.BooleanProperty;
import javafx.beans.property.IntegerProperty;
import javafx.beans.property.SimpleBooleanProperty;
import javafx.beans.property.SimpleIntegerProperty;
import javafx.scene.control.Control;
* Provide a simple and thin bracket that changes
* it appearance based on whether its closed or open.
public class GroupingMarker extends Control {
  private final static String DEFAULT_STYLE_CLASS = "grouping-marker";
  private BooleanProperty open;
  private IntegerProperty depth;
  public BooleanProperty openProperty() { return open; }
  public IntegerProperty depthProperty() { return depth; }
  public GroupingMarker(boolean open) {
  this();
  setOpen(open);
  public GroupingMarker() {
  open = new SimpleBooleanProperty(true);
  depth = new SimpleIntegerProperty(0);
  getStyleClass().add(DEFAULT_STYLE_CLASS);
  // TODO: Change to use CSS directly
  setSkin(new GroupingMarkerSkin(this));
  public boolean isOpen() {
  return open.get();
  public void setOpen(boolean flag) {
  open.set(flag);
  public int getDepth() {
  return depth.get();
  public void setDepth(int depth) {
  this.depth.set(depth);
package org.notebook;
import javafx.scene.Group;
import javafx.scene.paint.Color;
import javafx.scene.shape.FillRule;
import javafx.scene.shape.LineTo;
import javafx.scene.shape.MoveTo;
import javafx.scene.shape.Path;
import com.sun.javafx.scene.control.skin.SkinBase;
* The skin draws some simple lines on the right hand side of
* the control. The lines reflect whether the control is considered
* open or closed. Since there is no content, there is no
* content handling code needed.
public class GroupingMarkerSkin extends SkinBase<GroupingMarker, GroupingMarkerBehavior> {
  GroupingMarker control;
  Color lineColor;
  double shelfLength;
  double thickness;
  private Group lines;
  public GroupingMarkerSkin(GroupingMarker control) {
  super(control, new GroupingMarkerBehavior(control));
  this.control = control;
  lineColor = Color.BLUE;
  shelfLength = 5.0;
  thickness = 1.0;
  init();
  * Attached listeners to the properties in the control.
  protected void init() {
  registerChangeListener(control.openProperty(), "OPEN");
  registerChangeListener(control.depthProperty(), "DEPTH");
  lines = new Group();
  repaint();
  @Override
  protected void handleControlPropertyChanged(String arg0) {
  super.handleControlPropertyChanged(arg0);
    @Override public final GroupingMarker getSkinnable() {
        return control;
    @Override public final void dispose() {
    super.dispose();
        control = null;
    @Override
    protected double computePrefHeight(double arg0) {
    System.out.println("ph: " + arg0);
    return super.computePrefHeight(arg0);
    @Override
    protected double computePrefWidth(double arg0) {
    System.out.println("pw: " + arg0);
    return super.computePrefWidth(40.0);
     * Call this if a property changes that affects the visible
     * control.
    public void repaint() {
    requestLayout();
    @Override
    protected void layoutChildren() {
    if(control.getScene() != null) {
    drawLines();
    getChildren().setAll(lines);
    super.layoutChildren();
    protected void drawLines() {
    lines.getChildren().clear();
    System.out.println("bounds local: " + control.getBoundsInLocal());
    System.out.println("bounds parent: " + control.getBoundsInParent());
    System.out.println("bounds layout: " + control.getLayoutBounds());
    System.out.println("pref wxh: " + control.getPrefWidth() + "x" + control.getPrefHeight());
    double width = Math.max(0, 20.0 - 2 * 2.0);
    double height = control.getPrefHeight() - 4.0;
    height = Math.max(0, control.getBoundsInLocal().getHeight()-4.0);
    System.out.println("w: " + width + ", h: " + height);
    double margin = 4.0;
    final Path VERTICAL = new Path();
    VERTICAL.setFillRule(FillRule.EVEN_ODD);
    VERTICAL.getElements().add(new MoveTo(margin, margin)); // start
    VERTICAL.getElements().add(new LineTo(margin + shelfLength, margin)); // top horz line
    VERTICAL.getElements().add(new LineTo(margin + shelfLength, height - margin)); // vert line
    if(control.isOpen()) {
    VERTICAL.getElements().add(new LineTo(margin, height - margin)); // bottom horz line
    } else {
    VERTICAL.getElements().add(new LineTo(margin, height-margin-4.0));
    //VERTICAL.getElements().add(new ClosePath());
    VERTICAL.setStrokeWidth(thickness);
    VERTICAL.setStroke(lineColor);
    lines.getChildren().addAll(VERTICAL);
    lines.setCache(true);
package org.notebook;
import com.sun.javafx.scene.control.behavior.BehaviorBase;
public class GroupingMarkerBehavior extends BehaviorBase<GroupingMarker> {
  public GroupingMarkerBehavior(final GroupingMarker control) {
  super(control);
package org.notebook;
import javafx.application.Application;
import javafx.scene.Node;
import javafx.scene.Scene;
import javafx.scene.control.Label;
import javafx.scene.control.TextArea;
import javafx.scene.layout.BorderPane;
import javafx.scene.layout.VBox;
import javafx.stage.Stage;
public class TestGroupingMarker extends Application {
  public static void main(String args[]) {
  launch(TestGroupingMarker.class, args);
  @Override
  public void start(Stage stage) throws Exception {
  VBox vbox = new VBox();
  BorderPane p = new BorderPane();
  VBox first = new VBox();
  first.getChildren().add(makeEntry("In[1]=", "my label", 200.0, true));
  first.getChildren().add(makeEntry("Out[1]=", "the output!", 200.0, true));
  p.setCenter(first);
  p.setRight(new GroupingMarker(true));
  vbox.getChildren().add(p);
  vbox.getChildren().add(makeEntry("In[2]=", "my label 2", 100.0, false));
  Scene scene = new Scene(vbox,500,700);
  scene.getStylesheets().add(TestGroupingMarker.class.getResource("main.css").toExternalForm());
  stage.setScene(scene);
  stage.setTitle("GroupingMarker test");
  stage.show();
  protected Node makeEntry(String io, String text, double height, boolean open) {
  BorderPane pane2 = new BorderPane();
  pane2.setSnapToPixel(true);
  Label label2 = new Label(io);
  label2.getStyleClass().add("io-label");
  pane2.setLeft(label2);
  TextArea area2 = new TextArea(text);
  area2.getStyleClass().add("io-content");
  area2.setPrefHeight(height);
  pane2.setCenter(area2);
  GroupingMarker marker2 = new GroupingMarker();
  marker2.setOpen(open);
  pane2.setRight(marker2);
  return pane2;

Answer 1

The test interfaces are already defined for you - the 3rd party session bean remote/local interfaces.
It is pretty trivial to create implementations of those interfaces to return the test data from your XML files.
There are a number of ways to handle the switching, if you have used the service locator pattern, then I would personally slot the logic in to the service locator, to either look up the 3rd party bean or return a POJO test implementation of the interface according to configuration.
Without the service locator, you are forced to do a little more work, you will have to implement your own test session beans to the same interfaces as the 3rd party session beans.
You can then either deploy them instead of the 3rd party beans or you can deploy both the test and the 3rd party beans under different JNDI names,and use ejb-ref tags and allow you to switch between test and real versions by changing the ejb-link value.
Hope this helps.
Bob B.