The wrong example would be valid if it was used a valid tag between the existents for the jboss-webserver31-tomcat8-openshift imagestream (1.0,1.1,1.2), then it could be:

$ oc new-build --binary=true --image-stream=jboss-webserver31-tomcat8-openshift:1.2 --name=test1
--> Found image 48ba94f (4 months old) in image stream "openshift/jboss-webserver31-tomcat8-openshift" under tag "1.2" for "jboss-webserver31-tomcat8-openshift:1.2"

JBoss Web Server 3.1
--------------------
Platform for building and running web applications on JBoss Web Server 3.1 - Tomcat v8

Tags: builder, java, tomcat8

• A source build using binary input will be created
• The resulting image will be pushed to image stream tag "test1:latest"
• A binary build was created, use 'start-build --from-dir' to trigger a new build

--> Creating resources with label build=test1 ...
imagestream.image.openshift.io "test1" created
buildconfig.build.openshift.io "test1" created
--> Success

One invalid example of it in the documentation is this:

$ oc new-build --binary=true --image-stream=jboss-webserver31-tomcat8-openshift --name=test1
error: unable to locate any images in image streams with name "jboss-webserver31-tomcat8-openshift"

The 'oc new-build' command will match arguments to the following types:

1. Images tagged into image streams in the current project or the 'openshift' project

• if you don't specify a tag, we'll add ':latest'
  2. Images in the Docker Hub, on remote registries, or on the local Docker engine
  3. Git repository URLs or local paths that point to Git repositories

--allow-missing-images can be used to force the use of an image that was not matched

See 'oc new-build -h' for examples.