Nabble - java.net - glassfish dev

Re: REVIEW REQUESTED: GlassFish v3 Release Notes

2009-12-06T14:23:46Z

Hi, Gail.

Clarifying one of Anissa's comments...

Anissa Lam wrote:

- pg 12. Enhancements to the appclient Utility

The -targetserver option is added to enable the server and port number of the target to be
specified.

The above applies to cluster profile in v2, I think this sentence should be removed.

I'm not familiar with what Anissa is referring to, but this is definitely a new feature for v3 for the appclient command. Anissa is correct that in v3.0 there are no clusters and in v3.x this option will support a comma-separated list of host[:port] values. In v3.0 only a single value makes sense, but a single value is supported for v3.0.

- Tim

Re: REVIEW REQUESTED: GlassFish v3 Release Notes

2009-12-06T09:09:09Z

Hi, Gail.

I've provided a couple of notes on the wiki page, providing issue numbers for two of the release notes.

- Tim

Gail Risdal wrote:

Hello,

The GlassFish v3 Release Notes are available for final review:
http://wiki.glassfish.java.net/Wiki.jsp?page=ReleaseNotes

Please review this document and return your comments to me no later than COB Monday, December 7. Sooner would be even better.

Given the schedule, your comments should focus on changes that must be made for the GlassFish v3 release. Enhancements must wait until later.

If something must be changed or added, please provide the exact content, description, location, URL, etc. I won't have time to search for it or do a lot of follow up.

Thanks in advance,
Gail

Re: REVIEW REQUESTED: GlassFish v3 Release Notes

2009-12-05T23:05:38Z

Hi Gail,

Following is my comment for the release notes. Most of that applies to the Known Issues section.
This section really needs the initial evaluator to confirm for you that the issue still exists, especially those filed many months ago. I commented on a few which i know or i can try that out myself.   But there are still quite a few that needs to be looked at by others.

pg 11. Update Tool Integration
This tool provides automated updates, and facilitates managing add-on components
and related applications that are available for extending Enterprise Server v3 functions.

UpdateTool in admin console will NOT provide updates. It allows you to install additional components, which will then be available after server restart.   Installed Components and available updates will be provided for "view" only.   User cannot update or remove any components when server is running. Thus , this operation cannot be preformed in Admin Console.   Even if using the standalone updatetool, server must be stopped for this operation.

pg 12. Support for Scripting Languages

-   jMaki: A framework for creating Ajax web applications
Support for these scripting languages is provided by components that are available through
Update Tool.

I don't think there is any component specific for jMaki.   Please confirm with other developer.

- pg 12. Enhancements to the appclient Utility

The -targetserver option is added to enable the server and port number of the target to be
specified.

The above applies to cluster profile in v2, I think this sentence should be removed.

-pg 21 Known Issues

It seems that a few of the older issues has been fixed. You may want to confirm that.
Here is a few that i can no longer reproduce and could be removed.

pg 23.   [JDK_Issue] Warnings in server.log during clicks in the Administration Console GUI on
deployed samples (Issue 7206)
I have tried many applications including the 2 attached in the issue. No longer see this warning.

pg 24. [JDK_Issue] Null pointer exception on server restart (Issue 8299)
I don't think this issue still exists.   I never see this when i tested out restart feature in GUI.

pg 24. Load average climbs to 2 or 3 every few days and stays there until Enterprise Server is restarted.
For more information, see Issue report (http://glassfish.dev.java.net/issues/show_bug.cgi?id=6819).
This issue is filed against 9.1peur2.   Is this really an issue with v3 now ?
Workaround tells user to add a JAR to classpath-prefix in domain.xml,   where classpath-prefix is not even supported in v3.

pg 25. At startup, Enterprise Server throws a null pointer exception.
see Issue report (http://glassfish.dev.java.net/issues/show_bug.cgi?id=9472).
I haven't seen an NPE during startup for a long time, is this still an issue now ?

pg. 26. The command does not check that domain is not running (Issue 6196)
I believe this has been fixed, and should be removed from the release note.

I feel that there should be some 'separator' or 'heading' or more spaces after the Workaround and the Description of the next issue.    The current layout gives me a feeling that Workaround continues until the Description section.

thanks
Anissa

Gail Risdal wrote:

Hello,

The GlassFish v3 Release Notes are available for final review:
http://wiki.glassfish.java.net/Wiki.jsp?page=ReleaseNotes

Please review this document and return your comments to me no later than COB Monday, December 7. Sooner would be even better.

Given the schedule, your comments should focus on changes that must be made for the GlassFish v3 release. Enhancements must wait until later.

If something must be changed or added, please provide the exact content, description, location, URL, etc. I won't have time to search for it or do a lot of follow up.

Thanks in advance,
Gail

--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@...

REVIEW REQUESTED: GlassFish v3 Release Notes

2009-12-05T15:58:17Z

Hello,

The GlassFish v3 Release Notes are available for final review:
http://wiki.glassfish.java.net/Wiki.jsp?page=ReleaseNotes

Please review this document and return your comments to me no later than COB Monday, December 7. Sooner would be even better.

Given the schedule, your comments should focus on changes that must be made for the GlassFish v3 release. Enhancements must wait until later.

If something must be changed or added, please provide the exact content, description, location, URL, etc. I won't have time to search for it or do a lot of follow up.

Thanks in advance,
Gail

Re: stealing jsp and servlet api jars for my source build

2009-12-04T16:25:15Z

Kin-man,
>
> If so, then it's OK for jstl to be dependent on servlet-api-2.5 too.
>
Yes. Thanks to Dhiru, he has committed the source build for
servlet-api-2.5. I have not seen your commit for jstl source-build.

Thanks,
Jane

> -Kin-man
>
>> Thanks,
>> Jane
>>
>>
>>> Thanks again,
>>> Bobby
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>> For additional commands, e-mail: dev-help@...
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: Sending JMS messages between systems doesn't work any more

2009-12-04T12:31:37Z

After much experimentation, I've determined that the ability to send JMS
messages between systems disappeared between b68 and b71. It works fine
with promoted b68. Promoted b69 and promoted b70 both had the problem
that if you tried to run a JMS client, you would get a message in the
server log about jts starting up, and everything would hang -- so JMS
didn't really work at all. At promoted b71, the ConnectException
messages start to appear.

I'll file an issue.

Kim

On 12/03/09 13:04, Kim Haase wrote:

> Many thanks, Nigel. It looks as if the problem is with GlassFish, not MQ
> -- see below.
>
> On 12/03/09 12:05, Nigel Deakin wrote:
>> Kim,
>>
>> Kim Haase wrote:
>>> On 12/03/09 06:20, Nigel Deakin wrote:
>>>> Kim,
>>>>
>>>> Kim Haase wrote:
>>>>> JMS applications that send messages from one system to another
>>>>> stopped working for me in b73 and also fail in b74. They worked in
>>>>> earlier builds -- I think I last tested them around b69.
>>>>>
>>>>> Several examples in the Java EE Tutorial are based on sending JMS
>>>>> messages between systems, so this is an issue for docs.
>>>>>
>>>>> For a number of releases, the way to enable the sending of messages
>>>>> to a remote system has been to create a JMS connection factory
>>>>> resource whose AddressList property is set to the name of the
>>>>> remote system. (The connector connection pool, therefore, has its
>>>>> AddressList property set to this value.)
>>>>>
>>>>> Now, when I try to send messages to the remote system, I get the
>>>>> following error over and over:
>>>>>
>>>>> WARNING: [C4003]: Error occurred on connection creation
>>>>> [jdench:7676]. - cause: java.net.ConnectException: Connection
>>>>> refused: connect
>>>>> Dec 2, 2009 11:31:55 AM
>>>>> com.sun.messaging.jmq.jmsclient.ExceptionHandler
>>>>> throwConnectionException
>>>>
>>>> This means it is trying to connect to a MQ broker running on machine
>>>> jdench on port 7676, and it is getting no response, perhaps because
>>>> the broker isn't running or it is using a different port.
>>>>
>>>> Can you connect to it using other tools on your windows machine,
>>>> such as imqcmd (which is in the mq/bin directory of a Glassfish V3
>>>> installation)?
>>>>
>>>> For example this command lists the destinations on the broker:
>>>> imqcmd list dst -b jdench:7676
>>>> (it will prompt for user and password: typically admin/admin)
>>>
>>> Thanks, Nigel. The broker is running on jdench at port 7676 -- these
>>> are the server log messages on jdench, which look the way they always
>>> do:
>>>
>>> [#|2009-12-03T11:12:59.008-0500|INFO|glassfishv3.0|javax.enterprise.system.core.transaction.com.sun.jts.CosTransactions|_ThreadID=17;_ThreadName=Thread-1;|JTS5014:
>>> Recoverable JTS instance, serverId = [3700]|#]
>>>
>>> [#|2009-12-03T11:13:03.745-0500|INFO|glassfishv3.0|com.sun.enterprise.connectors.jms.system.ActiveJmsResourceAdapter|_ThreadID=32;_ThreadName=Thread-1;|JMS
>>> Service Connection URL is :mq://localhost:7676/|#]
>>>
>>> [#|2009-12-03T11:13:03.878-0500|INFO|glassfishv3.0|org.hibernate.validator.engine.resolver.DefaultTraversableResolver|_ThreadID=32;_ThreadName=Thread-1;|Instantiated
>>> an instance of
>>> org.hibernate.validator.engine.resolver.JPATraversableResolver.|#]
>>>
>>> [#|2009-12-03T11:13:04.170-0500|INFO|glassfishv3.0|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=32;_ThreadName=Thread-1;|MQJMSRA_RA1101:
>>> SJSMQ JMS Resource Adapter starting: DIRECT|#]
>>>
>>> [#|2009-12-03T11:13:14.151-0500|INFO|glassfishv3.0|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=32;_ThreadName=Thread-1;|MQJMSRA_RA1101:
>>> SJSMQ JMSRA Started:DIRECT|#]
>>>
>>> [#|2009-12-03T11:13:20.619-0500|INFO|glassfishv3.0|javax.resourceadapter.mqjmsra.outbound.connection|_ThreadID=30;_ThreadName=Thread-1;|MQJMSRA_MF1101:
>>> setAddressList:NOT setting default value=localhost|#]
>>>
>>> [#|2009-12-03T11:13:20.633-0500|INFO|glassfishv3.0|javax.resourceadapter.mqjmsra.outbound.connection|_ThreadID=30;_ThreadName=Thread-1;|MQJMSRA_MF1101:
>>> setPassword:NOT setting default value|#]
>>>
>>> [#|2009-12-03T11:13:20.634-0500|INFO|glassfishv3.0|javax.resourceadapter.mqjmsra.outbound.connection|_ThreadID=30;_ThreadName=Thread-1;|MQJMSRA_MF1101:
>>> setUserName:NOT setting default value=guest|#]
>>
>> Yes, this suggests the embedded broker has started. You could also
>> look at the broker log in
>> domains\domain1\imq\instances\imqbroker\log\log.txt (or similar) to
>> confirm this.
>>
>>>
>>> I ran the imqcmd on jdench and after some experimentation I found
>>> that the correct username and password were admin/admin.
>>
>> I did mention the default username and password in my previous email :-)
>
> Sorry to have spaced out!
>
>>
>>>
>>> jdench 52 =>imqcmd list dst
>>> Username: admin
>>> Password:
>>> Listing all the destinations on the broker specified by:
>>>
>>> -------------------------
>>> Host Primary Port
>>> -------------------------
>>> localhost 7676
>>>
>>> ---------------------------------------------------------------------------
>>>
>>> Name Type State Producers Consumers Msgs
>>> Total Count UnAck
>>> Avg Size
>>> ---------------------------------------------------------------------------
>>>
>>> PhysicalQueue Queue RUNNING 0 1 0 0 0.0
>>> mq.sys.dmq Queue RUNNING 0 0 0 0 0.0
>>>
>>> Successfully listed destinations.
>>
>> Yes, so the broker is definitely working.
>>
>>>
>>> jdench 53 =>pwd
>>> /home/chaase/glassfish-v3-b74/mq/bin
>>>
>>> However, the imqcmd on the Windows system fails:
>>>
>>> C:\Program Files\glassfish-v3-b74\mq\bin>imqcmd list dst -b jdench:7676
>>> Username: admin
>>> Password: admin
>>> Listing all the destinations on the broker specified by:
>>>
>>> ----------------------
>>> Host Primary Port
>>> ----------------------
>>> jdench 7676
>>>
>>> Dec 3, 2009 11:19:40 AM
>>> com.sun.messaging.jmq.jmsclient.ExceptionHandler
>>> throwConnectionException
>>> WARNING: [C4003]: Error occurred on connection creation
>>> [jdench:7676]. - cause:
>>> java.net.ConnectException: Connection refused: connect
>>> Error while connecting to the broker on host 'jdench' and port '7676'.
>>> com.sun.messaging.jms.JMSException: [C4003]: Error occurred on
>>> connection creation [jdench:7676]. - cause:
>>> java.net.ConnectException: Connection refused: connect
>>> Please verify that there is a broker running on the specified host
>>> and port or use the '-b' option to specify the correct broker host
>>> and port.
>>>
>>> Listing destinations failed.
>>
>> This eliminates your client code as the cause of the problem. It has
>> found the host but received no reply on the port.
>>
>>>
>>> I notice that on Windows the password shows up in clear text, whereas
>>> on Solaris it doesn't appear. Hard to believe that makes a
>>> difference, though.
>>>
>>> And I can still ping jdench, save files to it, etc. from my Windows
>>> system.
>>
>> This is sounding like a network issue. Do you have a hardware or
>> software firewall?
>
> Not that I know of.
>
>>
>> You could try shutting down the Glassfish instance and instead
>> starting a standalone MQ broker by running the imqbrokerd command
>> directly, and seeing if you can "imqcmd list dst" it from the PC.
>
> Without GlassFish, it works! I started the broker on jdench, and it runs
> fine (had to specify -javahome to keep it from picking up some jdk 5
> somewhere):
>
> jdench 59 =>./imqbrokerd -javahome /home/chaase/jdk1.6.0_17
> [03/Dec/2009:12:59:11 EST]
> ================================================================================
>
> Open Message Queue 4.4
> Sun Microsystems, Inc.
> Version: 4.4 Update 1 (Build 7-b)
> Compile: Wed Nov 18 23:21:05 PST 2009
>
> Copyright (c) 2009 Sun Microsystems, Inc. All rights reserved. Use is
> subject to license terms.
> ================================================================================
>
> Java Runtime: 1.6.0_17 Sun Microsystems Inc. /home/chaase/jdk1.6.0_17/jre
> [03/Dec/2009:12:59:12 EST] IMQ_HOME=/home/chaase/glassfish-v3-b74/mq
> [03/Dec/2009:12:59:12 EST]
> IMQ_VARHOME=/home/chaase/glassfish-v3-b74/glassfish/domains/domain1/imq
> [03/Dec/2009:12:59:12 EST] SunOS 5.10 sparc jdench (1 cpu) chaase
> [03/Dec/2009:12:59:12 EST] Max file descriptors: 65536 (65536)
> [03/Dec/2009:12:59:12 EST] Java Heap Size: max=190080k, current=190080k
> [03/Dec/2009:12:59:12 EST] Arguments: -javahome /home/chaase/jdk1.6.0_17
> [03/Dec/2009:12:59:12 EST] [B1060]: Loading persistent data...
> [03/Dec/2009:12:59:12 EST] Using built-in file-based persistent store:
> /home/chaase/glassfish-v3-b74/glassfish/domains/domain1/imq/instances/imqbroker/
>
> [03/Dec/2009:12:59:13 EST] [B1039]: Broker "imqbroker@jdench:7676" ready.
>
> And I did an imqcmd list dst and got the system queue, as expected.
>
> Then on Windows, imqcmd is able to list the destinations for the jdench
> broker too:
>
> C:\Program Files\glassfish-v3-b74\mq\bin>imqcmd list dst -b jdench:7676
> Username: admin
> Password: admin
> Listing all the destinations on the broker specified by:
>
> ----------------------
> Host Primary Port
> ----------------------
> jdench 7676
>
> --------------------------------------------------------------------------------------------
>
> Name Type State Producers Consumers Msgs
>
> Total Wildcard Total Wildcard Count
> Remote UnAck Avg Size
> --------------------------------------------------------------------------------------------
>
> mq.sys.dmq Queue RUNNING 0 - 0 - 0 0
> 0 0.0
>
> Successfully listed destinations.
>
> So it's not MQ that's causing the problem but GlassFish apparently. What
> now, I wonder?
>
> Thanks again!!
>
> Kim
>
>>
>> Nigel
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: javadocs for glassfish and related modules.

2009-12-04T11:56:07Z

"we should only publish doc for the exported public packages"

Ideally, yes. But there can be packages which have a few public classes and some private ones.

I use @org.glassfish.external.arc.Taxonomy to declare such things eg:

@Taxonomy( Stability.PRIVATE )

@Taxonomy( NOT_AN_INTERFACE )

On Dec 4, 2009, at 11:45 AM, Ludovic Champenois wrote:

> Siraj Ghaffar wrote:
>> There are some interfaces in that package - however I see your point in not publishing javadocs for packages that are unlikely to be used by end users. That makes sense. One interface in that package that might be useful for those using the embedded APIs would be the CommandRunner interface that allows you to run administrative commands.
>>
>> Rajiv Mordani wrote:
>>> Siraj, Jane,
>>> We want to publish javadocs for the APIs that developers can use, not the implementation classes. If there are some packages from admin that are useful for end users / developers that are not being published let me know. However some things that I see in the admin modules didn't seem to make sense for end users (at least that's what I think) so I did not include it.
>>>
>>> - Rajiv
> In fact, we should only publish doc for the exported public packages that have been declared as such in the ARC cases, right?
>
> Ludo
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

Lloyd Chambers
lloyd.chambers@...
GlassFish Team

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: javadocs for glassfish and related modules.

2009-12-04T11:45:39Z

Siraj Ghaffar wrote:

> There are some interfaces in that package - however I see your point
> in not publishing javadocs for packages that are unlikely to be used
> by end users. That makes sense. One interface in that package that
> might be useful for those using the embedded APIs would be the
> CommandRunner interface that allows you to run administrative commands.
>
> Rajiv Mordani wrote:
>> Siraj, Jane,
>> We want to publish javadocs for the APIs that developers can use,
>> not the implementation classes. If there are some packages from admin
>> that are useful for end users / developers that are not being
>> published let me know. However some things that I see in the admin
>> modules didn't seem to make sense for end users (at least that's what
>> I think) so I did not include it.
>>
>> - Rajiv

In fact, we should only publish doc for the exported public packages
that have been declared as such in the ARC cases, right?

Ludo

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: javadocs for glassfish and related modules.

2009-12-04T11:37:23Z

There are some interfaces in that package - however I see your point in
not publishing javadocs for packages that are unlikely to be used by end
users. That makes sense. One interface in that package that might be
useful for those using the embedded APIs would be the CommandRunner
interface that allows you to run administrative commands.

Rajiv Mordani wrote:

> Siraj, Jane,
> We want to publish javadocs for the APIs that developers can use,
> not the implementation classes. If there are some packages from admin
> that are useful for end users / developers that are not being
> published let me know. However some things that I see in the admin
> modules didn't seem to make sense for end users (at least that's what
> I think) so I did not include it.
>
> - Rajiv
>
> Jane Young wrote:
>> Hi Rajiv,
>>
>> Thank you for updating the v3 javadocs. Siraj was wondering why the
>> complete package for "org.glassfish.api.admin.*" is not in the v3
>> javadocs.
>>
>> Thanks,
>> Jane
>>
>>
>> Rajiv Mordani wrote:
>>> And the v3 javadocs (including the com.sun, org.* packages) are
>>> published at
>>>
>>> http://javadoc.glassfish.org/v3/apidoc.
>>>
>>> Please review those as well and let us know if anything is missing
>>> from that.
>>>
>>> - Rajiv
>>>
>>>
>>> Jane Young wrote:
>>>> Thanks, Kin-man.
>>>> The latest EE 6 apis javadoc is published:
>>>> http://javadoc.glassfish.org/javaee6/apidoc/
>>>>
>>>> Can the module owners and doc team review this and let me know if
>>>> you see anything missing.
>>>>
>>>> Thanks,
>>>> Jane
>>>>
>>>>
>>>>
>>>> Kin-man Chung wrote:
>>>>>
>>>>>
>>>>> On 12/03/09 16:24, Kin-man Chung wrote:
>>>>>> The javax.servlet group is just a repackage and the source there is
>>>>>> empty. I'll publish the jstl source in a minute. It might take
>>>>>> a while
>>>>>> for it to get to the repo though.
>>>>>>
>>>>> Done. It's now in
>>>>> http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2/
>>>>>
>>>>>
>>>>> Kin-man
>>>>>> On 12/03/09 16:09, Rajiv Mordani wrote:
>>>>>>> There seems to be jstl sources published in the javax.servlet
>>>>>>> group. I have changed to download that. If that is incorrect
>>>>>>> please let me know .
>>>>>>>
>>>>>>> - Rajiv
>>>>>>>
>>>>>>> Jane Young wrote:
>>>>>>>> Hi Kin-man,
>>>>>>>>
>>>>>>>> The jstl api version 1.2 sources artifacts are missing in
>>>>>>>> Maven repo. See:
>>>>>>>> http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2/
>>>>>>>>
>>>>>>>>
>>>>>>>> Previously, version 1.2-rev-1 is referenced to generate the
>>>>>>>> javadoc:
>>>>>>>> http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2-rev-1/.
>>>>>>>>
>>>>>>>>
>>>>>>>> Can you publish the sources artifact?
>>>>>>>> Jane
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Kin-man Chung wrote:
>>>>>>>>> I noticed that the javadocs for jstl api (package
>>>>>>>>> javax.servlet.jsp.jstl.*) is also missing.
>>>>>>>>>
>>>>>>>>> On 12/03/09 14:55, Rajiv Mordani wrote:
>>>>>>>>>> I just looked at the hudson job that creates and pushes the
>>>>>>>>>> javadocs and looks like the checkout of the bean-validation
>>>>>>>>>> api failed -
>>>>>>>>>>
>>>>>>>>>> bean-validator.checkout:
>>>>>>>>>> [echo] checkout Bean validation from
>>>>>>>>>> "https://glassfish-svn.dev.java.net/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1".
>>>>>>>>>>
>>>>>>>>>> [exec] Authentication realm:
>>>>>>>>>> <https://glassfish-svn.dev.java.net:443> CollabNet Subversion
>>>>>>>>>> Repository
>>>>>>>>>> [exec] svn: PROPFIND request failed on
>>>>>>>>>> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src'
>>>>>>>>>>
>>>>>>>>>> [exec] svn: PROPFIND of
>>>>>>>>>> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src':
>>>>>>>>>> authorization failed (https://glassfish-svn.dev.java.net)
>>>>>>>>>> [exec] Result: 1
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Fixing it now.
>>>>>>>>>>
>>>>>>>>>> - Rajiv
>>>>>>>>>>
>>>>>>>>>> Ludovic Champenois wrote:
>>>>>>>>>>> Kim Haase wrote:
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> I noticed today that the API docs at
>>>>>>>>>>>> http://javadoc.glassfish.org/javaee6/apidoc/ don't include
>>>>>>>>>>>> the Bean Validation API docs, in the package
>>>>>>>>>>>> javax.validation. Since the API is part of the EE 6
>>>>>>>>>>>> platform, shouldn't they be there?
>>>>>>>>>>>>
>>>>>>>>>>>> They are available on the final release download page at
>>>>>>>>>>>> http://jcp.org/en/jsr/summary?id=303.
>>>>>>>>>>>>
>>>>>>>>>>>> Kim
>>>>>>>>>>>
>>>>>>>>>>> Good catch...It was there in a previous javadoc push
>>>>>>>>>>> (11/24th) reviewed by the validation spec lead himself, so
>>>>>>>>>>> not sure why it is gone now.
>>>>>>>>>>>
>>>>>>>>>>> Ludo
>>>>>>>>>>>
>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>> dev-help@...
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>>>>>>> For additional commands, e-mail: dev-help@...
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>>>>>> For additional commands, e-mail: dev-help@...
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>>>>> For additional commands, e-mail: dev-help@...
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>>>> For additional commands, e-mail: dev-help@...
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>>> For additional commands, e-mail: dev-help@...
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>> For additional commands, e-mail: dev-help@...
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>> For additional commands, e-mail: dev-help@...
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>> For additional commands, e-mail: dev-help@...
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: javadocs for glassfish and related modules.

2009-12-04T10:51:37Z

Siraj, Jane,
We want to publish javadocs for the APIs that developers can use,
not the implementation classes. If there are some packages from admin
that are useful for end users / developers that are not being published
let me know. However some things that I see in the admin modules didn't
seem to make sense for end users (at least that's what I think) so I did
not include it.

- Rajiv

Jane Young wrote:

> Hi Rajiv,
>
> Thank you for updating the v3 javadocs. Siraj was wondering why the
> complete package for "org.glassfish.api.admin.*" is not in the v3
> javadocs.
>
> Thanks,
> Jane
>
>
> Rajiv Mordani wrote:
>> And the v3 javadocs (including the com.sun, org.* packages) are
>> published at
>>
>> http://javadoc.glassfish.org/v3/apidoc.
>>
>> Please review those as well and let us know if anything is missing
>> from that.
>>
>> - Rajiv
>>
>>
>> Jane Young wrote:
>>> Thanks, Kin-man.
>>> The latest EE 6 apis javadoc is published:
>>> http://javadoc.glassfish.org/javaee6/apidoc/
>>>
>>> Can the module owners and doc team review this and let me know if
>>> you see anything missing.
>>>
>>> Thanks,
>>> Jane
>>>
>>>
>>>
>>> Kin-man Chung wrote:
>>>>
>>>>
>>>> On 12/03/09 16:24, Kin-man Chung wrote:
>>>>> The javax.servlet group is just a repackage and the source there is
>>>>> empty. I'll publish the jstl source in a minute. It might take a
>>>>> while
>>>>> for it to get to the repo though.
>>>>>
>>>> Done. It's now in
>>>> http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2/
>>>>
>>>>
>>>> Kin-man
>>>>> On 12/03/09 16:09, Rajiv Mordani wrote:
>>>>>> There seems to be jstl sources published in the javax.servlet
>>>>>> group. I have changed to download that. If that is incorrect
>>>>>> please let me know .
>>>>>>
>>>>>> - Rajiv
>>>>>>
>>>>>> Jane Young wrote:
>>>>>>> Hi Kin-man,
>>>>>>>
>>>>>>> The jstl api version 1.2 sources artifacts are missing in
>>>>>>> Maven repo. See:
>>>>>>> http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2/
>>>>>>>
>>>>>>>
>>>>>>> Previously, version 1.2-rev-1 is referenced to generate the
>>>>>>> javadoc:
>>>>>>> http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2-rev-1/.
>>>>>>>
>>>>>>>
>>>>>>> Can you publish the sources artifact?
>>>>>>> Jane
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Kin-man Chung wrote:
>>>>>>>> I noticed that the javadocs for jstl api (package
>>>>>>>> javax.servlet.jsp.jstl.*) is also missing.
>>>>>>>>
>>>>>>>> On 12/03/09 14:55, Rajiv Mordani wrote:
>>>>>>>>> I just looked at the hudson job that creates and pushes the
>>>>>>>>> javadocs and looks like the checkout of the bean-validation
>>>>>>>>> api failed -
>>>>>>>>>
>>>>>>>>> bean-validator.checkout:
>>>>>>>>> [echo] checkout Bean validation from
>>>>>>>>> "https://glassfish-svn.dev.java.net/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1".
>>>>>>>>>
>>>>>>>>> [exec] Authentication realm:
>>>>>>>>> <https://glassfish-svn.dev.java.net:443> CollabNet Subversion
>>>>>>>>> Repository
>>>>>>>>> [exec] svn: PROPFIND request failed on
>>>>>>>>> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src'
>>>>>>>>>
>>>>>>>>> [exec] svn: PROPFIND of
>>>>>>>>> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src':
>>>>>>>>> authorization failed (https://glassfish-svn.dev.java.net)
>>>>>>>>> [exec] Result: 1
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Fixing it now.
>>>>>>>>>
>>>>>>>>> - Rajiv
>>>>>>>>>
>>>>>>>>> Ludovic Champenois wrote:
>>>>>>>>>> Kim Haase wrote:
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> I noticed today that the API docs at
>>>>>>>>>>> http://javadoc.glassfish.org/javaee6/apidoc/ don't include
>>>>>>>>>>> the Bean Validation API docs, in the package
>>>>>>>>>>> javax.validation. Since the API is part of the EE 6
>>>>>>>>>>> platform, shouldn't they be there?
>>>>>>>>>>>
>>>>>>>>>>> They are available on the final release download page at
>>>>>>>>>>> http://jcp.org/en/jsr/summary?id=303.
>>>>>>>>>>>
>>>>>>>>>>> Kim
>>>>>>>>>>
>>>>>>>>>> Good catch...It was there in a previous javadoc push
>>>>>>>>>> (11/24th) reviewed by the validation spec lead himself, so
>>>>>>>>>> not sure why it is gone now.
>>>>>>>>>>
>>>>>>>>>> Ludo
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>>>>>>> For additional commands, e-mail: dev-help@...
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>>>>>> For additional commands, e-mail: dev-help@...
>>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>>>>> For additional commands, e-mail: dev-help@...
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>>>> For additional commands, e-mail: dev-help@...
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>>> For additional commands, e-mail: dev-help@...
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>> For additional commands, e-mail: dev-help@...
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>> For additional commands, e-mail: dev-help@...
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>> For additional commands, e-mail: dev-help@...
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: this may be jumping the gun...

2009-12-04T10:51:19Z

Any update on this?

Thanks,
vbk

On 11/24/09 16:46, Vince Kraemer wrote:

> but where will I be able to download post v3 FCS builds from...
>
> currently, I get bits from
> http://java.net/download/glassfish/v3/promoted/latest-glassfish.zip.
>
> Will the new place be something like
> http://java.net/download/glassfish/v3.1/promoted/latest-glassfish.zip?
>
> has that been decided yet?
>
> thanks,
> vbk

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: javadocs for glassfish and related modules.

2009-12-04T10:25:40Z

Hi Rajiv,

Thank you for updating the v3 javadocs.
Siraj was wondering why the complete package for
"org.glassfish.api.admin.*" is not in the v3 javadocs.

Thanks,
Jane

Rajiv Mordani wrote:

> And the v3 javadocs (including the com.sun, org.* packages) are
> published at
>
> http://javadoc.glassfish.org/v3/apidoc.
>
> Please review those as well and let us know if anything is missing
> from that.
>
> - Rajiv
>
>
> Jane Young wrote:
>> Thanks, Kin-man.
>> The latest EE 6 apis javadoc is published:
>> http://javadoc.glassfish.org/javaee6/apidoc/
>>
>> Can the module owners and doc team review this and let me know if you
>> see anything missing.
>>
>> Thanks,
>> Jane
>>
>>
>>
>> Kin-man Chung wrote:
>>>
>>>
>>> On 12/03/09 16:24, Kin-man Chung wrote:
>>>> The javax.servlet group is just a repackage and the source there is
>>>> empty. I'll publish the jstl source in a minute. It might take a
>>>> while
>>>> for it to get to the repo though.
>>>>
>>> Done. It's now in
>>> http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2/
>>>
>>>
>>> Kin-man
>>>> On 12/03/09 16:09, Rajiv Mordani wrote:
>>>>> There seems to be jstl sources published in the javax.servlet
>>>>> group. I have changed to download that. If that is incorrect
>>>>> please let me know .
>>>>>
>>>>> - Rajiv
>>>>>
>>>>> Jane Young wrote:
>>>>>> Hi Kin-man,
>>>>>>
>>>>>> The jstl api version 1.2 sources artifacts are missing in Maven
>>>>>> repo. See:
>>>>>> http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2/
>>>>>>
>>>>>>
>>>>>> Previously, version 1.2-rev-1 is referenced to generate the
>>>>>> javadoc:
>>>>>> http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2-rev-1/.
>>>>>>
>>>>>>
>>>>>> Can you publish the sources artifact?
>>>>>> Jane
>>>>>>
>>>>>>
>>>>>>
>>>>>> Kin-man Chung wrote:
>>>>>>> I noticed that the javadocs for jstl api (package
>>>>>>> javax.servlet.jsp.jstl.*) is also missing.
>>>>>>>
>>>>>>> On 12/03/09 14:55, Rajiv Mordani wrote:
>>>>>>>> I just looked at the hudson job that creates and pushes the
>>>>>>>> javadocs and looks like the checkout of the bean-validation api
>>>>>>>> failed -
>>>>>>>>
>>>>>>>> bean-validator.checkout:
>>>>>>>> [echo] checkout Bean validation from
>>>>>>>> "https://glassfish-svn.dev.java.net/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1".
>>>>>>>>
>>>>>>>> [exec] Authentication realm:
>>>>>>>> <https://glassfish-svn.dev.java.net:443> CollabNet Subversion
>>>>>>>> Repository
>>>>>>>> [exec] svn: PROPFIND request failed on
>>>>>>>> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src'
>>>>>>>>
>>>>>>>> [exec] svn: PROPFIND of
>>>>>>>> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src':
>>>>>>>> authorization failed (https://glassfish-svn.dev.java.net)
>>>>>>>> [exec] Result: 1
>>>>>>>>
>>>>>>>>
>>>>>>>> Fixing it now.
>>>>>>>>
>>>>>>>> - Rajiv
>>>>>>>>
>>>>>>>> Ludovic Champenois wrote:
>>>>>>>>> Kim Haase wrote:
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> I noticed today that the API docs at
>>>>>>>>>> http://javadoc.glassfish.org/javaee6/apidoc/ don't include
>>>>>>>>>> the Bean Validation API docs, in the package
>>>>>>>>>> javax.validation. Since the API is part of the EE 6 platform,
>>>>>>>>>> shouldn't they be there?
>>>>>>>>>>
>>>>>>>>>> They are available on the final release download page at
>>>>>>>>>> http://jcp.org/en/jsr/summary?id=303.
>>>>>>>>>>
>>>>>>>>>> Kim
>>>>>>>>>
>>>>>>>>> Good catch...It was there in a previous javadoc push (11/24th)
>>>>>>>>> reviewed by the validation spec lead himself, so not sure why
>>>>>>>>> it is gone now.
>>>>>>>>>
>>>>>>>>> Ludo
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>>>>>> For additional commands, e-mail: dev-help@...
>>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>>>>> For additional commands, e-mail: dev-help@...
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>>>> For additional commands, e-mail: dev-help@...
>>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>>> For additional commands, e-mail: dev-help@...
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>> For additional commands, e-mail: dev-help@...
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>> For additional commands, e-mail: dev-help@...
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>> For additional commands, e-mail: dev-help@...
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: javadocs for glassfish and related modules.

2009-12-04T10:21:22Z

And the v3 javadocs (including the com.sun, org.* packages) are
published at

http://javadoc.glassfish.org/v3/apidoc.

Please review those as well and let us know if anything is missing from
that.

- Rajiv

Jane Young wrote:

> Thanks, Kin-man.
> The latest EE 6 apis javadoc is published:
> http://javadoc.glassfish.org/javaee6/apidoc/
>
> Can the module owners and doc team review this and let me know if you
> see anything missing.
>
> Thanks,
> Jane
>
>
>
> Kin-man Chung wrote:
>>
>>
>> On 12/03/09 16:24, Kin-man Chung wrote:
>>> The javax.servlet group is just a repackage and the source there is
>>> empty. I'll publish the jstl source in a minute. It might take a
>>> while
>>> for it to get to the repo though.
>>>
>> Done. It's now in
>> http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2/
>>
>>
>> Kin-man
>>> On 12/03/09 16:09, Rajiv Mordani wrote:
>>>> There seems to be jstl sources published in the javax.servlet
>>>> group. I have changed to download that. If that is incorrect please
>>>> let me know .
>>>>
>>>> - Rajiv
>>>>
>>>> Jane Young wrote:
>>>>> Hi Kin-man,
>>>>>
>>>>> The jstl api version 1.2 sources artifacts are missing in Maven
>>>>> repo. See:
>>>>> http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2/
>>>>>
>>>>>
>>>>> Previously, version 1.2-rev-1 is referenced to generate the
>>>>> javadoc:
>>>>> http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2-rev-1/.
>>>>>
>>>>>
>>>>> Can you publish the sources artifact?
>>>>> Jane
>>>>>
>>>>>
>>>>>
>>>>> Kin-man Chung wrote:
>>>>>> I noticed that the javadocs for jstl api (package
>>>>>> javax.servlet.jsp.jstl.*) is also missing.
>>>>>>
>>>>>> On 12/03/09 14:55, Rajiv Mordani wrote:
>>>>>>> I just looked at the hudson job that creates and pushes the
>>>>>>> javadocs and looks like the checkout of the bean-validation api
>>>>>>> failed -
>>>>>>>
>>>>>>> bean-validator.checkout:
>>>>>>> [echo] checkout Bean validation from
>>>>>>> "https://glassfish-svn.dev.java.net/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1".
>>>>>>>
>>>>>>> [exec] Authentication realm:
>>>>>>> <https://glassfish-svn.dev.java.net:443> CollabNet Subversion
>>>>>>> Repository
>>>>>>> [exec] svn: PROPFIND request failed on
>>>>>>> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src'
>>>>>>>
>>>>>>> [exec] svn: PROPFIND of
>>>>>>> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src':
>>>>>>> authorization failed (https://glassfish-svn.dev.java.net)
>>>>>>> [exec] Result: 1
>>>>>>>
>>>>>>>
>>>>>>> Fixing it now.
>>>>>>>
>>>>>>> - Rajiv
>>>>>>>
>>>>>>> Ludovic Champenois wrote:
>>>>>>>> Kim Haase wrote:
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I noticed today that the API docs at
>>>>>>>>> http://javadoc.glassfish.org/javaee6/apidoc/ don't include the
>>>>>>>>> Bean Validation API docs, in the package javax.validation.
>>>>>>>>> Since the API is part of the EE 6 platform, shouldn't they be
>>>>>>>>> there?
>>>>>>>>>
>>>>>>>>> They are available on the final release download page at
>>>>>>>>> http://jcp.org/en/jsr/summary?id=303.
>>>>>>>>>
>>>>>>>>> Kim
>>>>>>>>
>>>>>>>> Good catch...It was there in a previous javadoc push (11/24th)
>>>>>>>> reviewed by the validation spec lead himself, so not sure why
>>>>>>>> it is gone now.
>>>>>>>>
>>>>>>>> Ludo
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>>>>> For additional commands, e-mail: dev-help@...
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>>>> For additional commands, e-mail: dev-help@...
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>>> For additional commands, e-mail: dev-help@...
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>> For additional commands, e-mail: dev-help@...
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>> For additional commands, e-mail: dev-help@...
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>> For additional commands, e-mail: dev-help@...
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: Dev Guide JDBC Questions

2009-12-04T08:30:33Z

On 12/03/09 18:54, Shalini Muthukrishnan wrote:

> Hi June,
>
> June.Parks@... wrote:
>> Hi Shalini,
>>
>> Great review. I have a couple of questions, see below.
>>
>> On 11/27/09 03:02 AM, Shalini Muthukrishnan wrote:
>>> - Page 240, Making JDBC Driver Jars available : Please add
>>> glassfish_home/lib directory to the list.
>> How would this differ from adding the driver JARs to
>> <domain-dir>/lib? Why would a user want to put them in
>> <install-dir>/lib instead?
> This is an other directory where user can put his jdbc driver to make
> it available to the application server.

I figured that was the case, but you still haven't answered my
question. Why would a user want to put the driver JARs in
<install-dir>/lib instead of <domain-dir>/lib? Would they be available
to multiple domains, if the user had them? Would they override JARs in
<domain-dir>/lib? If there's no advantage to putting them in
<install-dir>/lib, why bother telling users they can do so?

June

>>> - Page 247, section Handling Invalid Connections : the examples for
>>> asadmin set on the property should be changed to :
>>> asadmin set
>>> server.resources.jdbc-connection-pool.JCPool1.property.Prefer-Validate-Over-Recreate="true"
>>>
>> Jagadish says the property name is all caps,
>> PREFER-VALIDATE-OVER-RECREATE. Please confirm the spelling.
> It could also be set with init-caps like "Prefer-Validate-Over-Recreate".
>
> Thanks,
> Shalini.
>> Unfortunately, because this is a property and not an attribute, I
>> can't extract it from the configuration myself.
>>
>> June
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: javadocs for glassfish and related modules.

2009-12-04T02:25:16Z

Thanks, Kin-man.

The latest EE 6 apis javadoc is published:
http://javadoc.glassfish.org/javaee6/apidoc/

Can the module owners and doc team review this and let me know if you
see anything missing.

Thanks,
Jane

Kin-man Chung wrote:

>
>
> On 12/03/09 16:24, Kin-man Chung wrote:
>> The javax.servlet group is just a repackage and the source there is
>> empty. I'll publish the jstl source in a minute. It might take a while
>> for it to get to the repo though.
>>
> Done. It's now in
> http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2/
>
>
> Kin-man
>> On 12/03/09 16:09, Rajiv Mordani wrote:
>>> There seems to be jstl sources published in the javax.servlet group.
>>> I have changed to download that. If that is incorrect please let me
>>> know .
>>>
>>> - Rajiv
>>>
>>> Jane Young wrote:
>>>> Hi Kin-man,
>>>>
>>>> The jstl api version 1.2 sources artifacts are missing in Maven
>>>> repo. See:
>>>> http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2/
>>>>
>>>>
>>>> Previously, version 1.2-rev-1 is referenced to generate the
>>>> javadoc:
>>>> http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2-rev-1/.
>>>>
>>>>
>>>> Can you publish the sources artifact?
>>>> Jane
>>>>
>>>>
>>>>
>>>> Kin-man Chung wrote:
>>>>> I noticed that the javadocs for jstl api (package
>>>>> javax.servlet.jsp.jstl.*) is also missing.
>>>>>
>>>>> On 12/03/09 14:55, Rajiv Mordani wrote:
>>>>>> I just looked at the hudson job that creates and pushes the
>>>>>> javadocs and looks like the checkout of the bean-validation api
>>>>>> failed -
>>>>>>
>>>>>> bean-validator.checkout:
>>>>>> [echo] checkout Bean validation from
>>>>>> "https://glassfish-svn.dev.java.net/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1".
>>>>>>
>>>>>> [exec] Authentication realm:
>>>>>> <https://glassfish-svn.dev.java.net:443> CollabNet Subversion
>>>>>> Repository
>>>>>> [exec] svn: PROPFIND request failed on
>>>>>> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src'
>>>>>>
>>>>>> [exec] svn: PROPFIND of
>>>>>> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src':
>>>>>> authorization failed (https://glassfish-svn.dev.java.net)
>>>>>> [exec] Result: 1
>>>>>>
>>>>>>
>>>>>> Fixing it now.
>>>>>>
>>>>>> - Rajiv
>>>>>>
>>>>>> Ludovic Champenois wrote:
>>>>>>> Kim Haase wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I noticed today that the API docs at
>>>>>>>> http://javadoc.glassfish.org/javaee6/apidoc/ don't include the
>>>>>>>> Bean Validation API docs, in the package javax.validation.
>>>>>>>> Since the API is part of the EE 6 platform, shouldn't they be
>>>>>>>> there?
>>>>>>>>
>>>>>>>> They are available on the final release download page at
>>>>>>>> http://jcp.org/en/jsr/summary?id=303.
>>>>>>>>
>>>>>>>> Kim
>>>>>>>
>>>>>>> Good catch...It was there in a previous javadoc push (11/24th)
>>>>>>> reviewed by the validation spec lead himself, so not sure why it
>>>>>>> is gone now.
>>>>>>>
>>>>>>> Ludo
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>>>> For additional commands, e-mail: dev-help@...
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>>> For additional commands, e-mail: dev-help@...
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>> For additional commands, e-mail: dev-help@...
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>> For additional commands, e-mail: dev-help@...
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>> For additional commands, e-mail: dev-help@...
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: Dev Guide JDBC Questions

2009-12-03T18:54:29Z

Hi June,

June.Parks@... wrote:

This is an other directory where user can put his jdbc driver to make it
available to the application server.
>> - Page 247, section Handling Invalid Connections : the examples for
>> asadmin set on the property should be changed to :
>> asadmin set
>> server.resources.jdbc-connection-pool.JCPool1.property.Prefer-Validate-Over-Recreate="true"
>>
> Jagadish says the property name is all caps,
> PREFER-VALIDATE-OVER-RECREATE. Please confirm the spelling.
It could also be set with init-caps like "Prefer-Validate-Over-Recreate".

Thanks,
Shalini.
> Unfortunately, because this is a property and not an attribute, I
> can't extract it from the configuration myself.
>
> June
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: javadocs for glassfish and related modules.

2009-12-03T17:10:30Z

On 12/03/09 16:24, Kin-man Chung wrote:
> The javax.servlet group is just a repackage and the source there is
> empty. I'll publish the jstl source in a minute. It might take a while
> for it to get to the repo though.
>
Done. It's now in
http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2/

Kin-man

> On 12/03/09 16:09, Rajiv Mordani wrote:
>> There seems to be jstl sources published in the javax.servlet group. I
>> have changed to download that. If that is incorrect please let me know .
>>
>> - Rajiv
>>
>> Jane Young wrote:
>>> Hi Kin-man,
>>>
>>> The jstl api version 1.2 sources artifacts are missing in Maven
>>> repo. See:
>>> http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2/
>>>
>>>
>>> Previously, version 1.2-rev-1 is referenced to generate the javadoc:
>>> http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2-rev-1/.
>>>
>>>
>>> Can you publish the sources artifact?
>>> Jane
>>>
>>>
>>>
>>> Kin-man Chung wrote:
>>>> I noticed that the javadocs for jstl api (package
>>>> javax.servlet.jsp.jstl.*) is also missing.
>>>>
>>>> On 12/03/09 14:55, Rajiv Mordani wrote:
>>>>> I just looked at the hudson job that creates and pushes the
>>>>> javadocs and looks like the checkout of the bean-validation api
>>>>> failed -
>>>>>
>>>>> bean-validator.checkout:
>>>>> [echo] checkout Bean validation from
>>>>> "https://glassfish-svn.dev.java.net/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1".
>>>>>
>>>>> [exec] Authentication realm:
>>>>> <https://glassfish-svn.dev.java.net:443> CollabNet Subversion
>>>>> Repository
>>>>> [exec] svn: PROPFIND request failed on
>>>>> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src'
>>>>>
>>>>> [exec] svn: PROPFIND of
>>>>> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src':
>>>>> authorization failed (https://glassfish-svn.dev.java.net)
>>>>> [exec] Result: 1
>>>>>
>>>>>
>>>>> Fixing it now.
>>>>>
>>>>> - Rajiv
>>>>>
>>>>> Ludovic Champenois wrote:
>>>>>> Kim Haase wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I noticed today that the API docs at
>>>>>>> http://javadoc.glassfish.org/javaee6/apidoc/ don't include the
>>>>>>> Bean Validation API docs, in the package javax.validation. Since
>>>>>>> the API is part of the EE 6 platform, shouldn't they be there?
>>>>>>>
>>>>>>> They are available on the final release download page at
>>>>>>> http://jcp.org/en/jsr/summary?id=303.
>>>>>>>
>>>>>>> Kim
>>>>>>
>>>>>> Good catch...It was there in a previous javadoc push (11/24th)
>>>>>> reviewed by the validation spec lead himself, so not sure why it
>>>>>> is gone now.
>>>>>>
>>>>>> Ludo
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>>> For additional commands, e-mail: dev-help@...
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>> For additional commands, e-mail: dev-help@...
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>> For additional commands, e-mail: dev-help@...
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>> For additional commands, e-mail: dev-help@...
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: javadocs for glassfish and related modules.

2009-12-03T16:24:09Z

The javax.servlet group is just a repackage and the source there is
empty. I'll publish the jstl source in a minute. It might take a while
for it to get to the repo though.

On 12/03/09 16:09, Rajiv Mordani wrote:

> There seems to be jstl sources published in the javax.servlet group. I
> have changed to download that. If that is incorrect please let me know .
>
> - Rajiv
>
> Jane Young wrote:
>> Hi Kin-man,
>>
>> The jstl api version 1.2 sources artifacts are missing in Maven
>> repo. See:
>> http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2/
>>
>>
>> Previously, version 1.2-rev-1 is referenced to generate the javadoc:
>> http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2-rev-1/.
>>
>>
>> Can you publish the sources artifact?
>> Jane
>>
>>
>>
>> Kin-man Chung wrote:
>>> I noticed that the javadocs for jstl api (package
>>> javax.servlet.jsp.jstl.*) is also missing.
>>>
>>> On 12/03/09 14:55, Rajiv Mordani wrote:
>>>> I just looked at the hudson job that creates and pushes the javadocs
>>>> and looks like the checkout of the bean-validation api failed -
>>>>
>>>> bean-validator.checkout:
>>>> [echo] checkout Bean validation from
>>>> "https://glassfish-svn.dev.java.net/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1".
>>>>
>>>> [exec] Authentication realm:
>>>> <https://glassfish-svn.dev.java.net:443> CollabNet Subversion
>>>> Repository
>>>> [exec] svn: PROPFIND request failed on
>>>> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src'
>>>>
>>>> [exec] svn: PROPFIND of
>>>> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src':
>>>> authorization failed (https://glassfish-svn.dev.java.net)
>>>> [exec] Result: 1
>>>>
>>>>
>>>> Fixing it now.
>>>>
>>>> - Rajiv
>>>>
>>>> Ludovic Champenois wrote:
>>>>> Kim Haase wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I noticed today that the API docs at
>>>>>> http://javadoc.glassfish.org/javaee6/apidoc/ don't include the
>>>>>> Bean Validation API docs, in the package javax.validation. Since
>>>>>> the API is part of the EE 6 platform, shouldn't they be there?
>>>>>>
>>>>>> They are available on the final release download page at
>>>>>> http://jcp.org/en/jsr/summary?id=303.
>>>>>>
>>>>>> Kim
>>>>>
>>>>> Good catch...It was there in a previous javadoc push (11/24th)
>>>>> reviewed by the validation spec lead himself, so not sure why it is
>>>>> gone now.
>>>>>
>>>>> Ludo
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>> For additional commands, e-mail: dev-help@...
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>> For additional commands, e-mail: dev-help@...
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>> For additional commands, e-mail: dev-help@...
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: javadocs for glassfish and related modules.

2009-12-03T16:21:27Z

That's fine.
What is the url for jstl sources?

Thanks,
Jane

Rajiv Mordani wrote:

> There seems to be jstl sources published in the javax.servlet group. I
> have changed to download that. If that is incorrect please let me know .
>
> - Rajiv
>
> Jane Young wrote:
>> Hi Kin-man,
>>
>> The jstl api version 1.2 sources artifacts are missing in Maven
>> repo. See:
>> http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2/
>>
>>
>> Previously, version 1.2-rev-1 is referenced to generate the javadoc:
>> http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2-rev-1/.
>>
>>
>> Can you publish the sources artifact?
>> Jane
>>
>>
>>
>> Kin-man Chung wrote:
>>> I noticed that the javadocs for jstl api (package
>>> javax.servlet.jsp.jstl.*) is also missing.
>>>
>>> On 12/03/09 14:55, Rajiv Mordani wrote:
>>>> I just looked at the hudson job that creates and pushes the
>>>> javadocs and looks like the checkout of the bean-validation api
>>>> failed -
>>>>
>>>> bean-validator.checkout:
>>>> [echo] checkout Bean validation from
>>>> "https://glassfish-svn.dev.java.net/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1".
>>>>
>>>> [exec] Authentication realm:
>>>> <https://glassfish-svn.dev.java.net:443> CollabNet Subversion
>>>> Repository
>>>> [exec] svn: PROPFIND request failed on
>>>> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src'
>>>>
>>>> [exec] svn: PROPFIND of
>>>> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src':
>>>> authorization failed (https://glassfish-svn.dev.java.net)
>>>> [exec] Result: 1
>>>>
>>>>
>>>> Fixing it now.
>>>>
>>>> - Rajiv
>>>>
>>>> Ludovic Champenois wrote:
>>>>> Kim Haase wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I noticed today that the API docs at
>>>>>> http://javadoc.glassfish.org/javaee6/apidoc/ don't include the
>>>>>> Bean Validation API docs, in the package javax.validation. Since
>>>>>> the API is part of the EE 6 platform, shouldn't they be there?
>>>>>>
>>>>>> They are available on the final release download page at
>>>>>> http://jcp.org/en/jsr/summary?id=303.
>>>>>>
>>>>>> Kim
>>>>>
>>>>> Good catch...It was there in a previous javadoc push (11/24th)
>>>>> reviewed by the validation spec lead himself, so not sure why it
>>>>> is gone now.
>>>>>
>>>>> Ludo
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>>> For additional commands, e-mail: dev-help@...
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>> For additional commands, e-mail: dev-help@...
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>> For additional commands, e-mail: dev-help@...
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: javadocs for glassfish and related modules.

2009-12-03T16:09:51Z

There seems to be jstl sources published in the javax.servlet group. I
have changed to download that. If that is incorrect please let me know .

- Rajiv

Jane Young wrote:

> Hi Kin-man,
>
> The jstl api version 1.2 sources artifacts are missing in Maven
> repo. See:
> http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2/
>
>
> Previously, version 1.2-rev-1 is referenced to generate the javadoc:
> http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2-rev-1/.
>
>
> Can you publish the sources artifact?
> Jane
>
>
>
> Kin-man Chung wrote:
>> I noticed that the javadocs for jstl api (package
>> javax.servlet.jsp.jstl.*) is also missing.
>>
>> On 12/03/09 14:55, Rajiv Mordani wrote:
>>> I just looked at the hudson job that creates and pushes the javadocs
>>> and looks like the checkout of the bean-validation api failed -
>>>
>>> bean-validator.checkout:
>>> [echo] checkout Bean validation from
>>> "https://glassfish-svn.dev.java.net/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1".
>>>
>>> [exec] Authentication realm:
>>> <https://glassfish-svn.dev.java.net:443> CollabNet Subversion
>>> Repository
>>> [exec] svn: PROPFIND request failed on
>>> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src'
>>>
>>> [exec] svn: PROPFIND of
>>> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src':
>>> authorization failed (https://glassfish-svn.dev.java.net)
>>> [exec] Result: 1
>>>
>>>
>>> Fixing it now.
>>>
>>> - Rajiv
>>>
>>> Ludovic Champenois wrote:
>>>> Kim Haase wrote:
>>>>> Hi,
>>>>>
>>>>> I noticed today that the API docs at
>>>>> http://javadoc.glassfish.org/javaee6/apidoc/ don't include the
>>>>> Bean Validation API docs, in the package javax.validation. Since
>>>>> the API is part of the EE 6 platform, shouldn't they be there?
>>>>>
>>>>> They are available on the final release download page at
>>>>> http://jcp.org/en/jsr/summary?id=303.
>>>>>
>>>>> Kim
>>>>
>>>> Good catch...It was there in a previous javadoc push (11/24th)
>>>> reviewed by the validation spec lead himself, so not sure why it is
>>>> gone now.
>>>>
>>>> Ludo
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>> For additional commands, e-mail: dev-help@...
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>> For additional commands, e-mail: dev-help@...
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: javadocs for glassfish and related modules.

2009-12-03T16:01:04Z

Hi Kin-man,

The jstl api version 1.2 sources artifacts are missing in Maven repo.
See:
http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2/

Previously, version 1.2-rev-1 is referenced to generate the javadoc:
http://download.java.net/maven/glassfish/javax/servlet/jsp/jstl/jstl-api/1.2-rev-1/.

Can you publish the sources artifact?

Jane

Kin-man Chung wrote:

> I noticed that the javadocs for jstl api (package
> javax.servlet.jsp.jstl.*) is also missing.
>
> On 12/03/09 14:55, Rajiv Mordani wrote:
>> I just looked at the hudson job that creates and pushes the javadocs
>> and looks like the checkout of the bean-validation api failed -
>>
>> bean-validator.checkout:
>> [echo] checkout Bean validation from
>> "https://glassfish-svn.dev.java.net/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1".
>>
>> [exec] Authentication realm:
>> <https://glassfish-svn.dev.java.net:443> CollabNet Subversion Repository
>> [exec] svn: PROPFIND request failed on
>> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src'
>>
>> [exec] svn: PROPFIND of
>> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src':
>> authorization failed (https://glassfish-svn.dev.java.net)
>> [exec] Result: 1
>>
>>
>> Fixing it now.
>>
>> - Rajiv
>>
>> Ludovic Champenois wrote:
>>> Kim Haase wrote:
>>>> Hi,
>>>>
>>>> I noticed today that the API docs at
>>>> http://javadoc.glassfish.org/javaee6/apidoc/ don't include the Bean
>>>> Validation API docs, in the package javax.validation. Since the API
>>>> is part of the EE 6 platform, shouldn't they be there?
>>>>
>>>> They are available on the final release download page at
>>>> http://jcp.org/en/jsr/summary?id=303.
>>>>
>>>> Kim
>>>
>>> Good catch...It was there in a previous javadoc push (11/24th)
>>> reviewed by the validation spec lead himself, so not sure why it is
>>> gone now.
>>>
>>> Ludo
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>> For additional commands, e-mail: dev-help@...
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: javadocs for glassfish and related modules.

2009-12-03T15:08:29Z

Thank you, Rajiv!

Jane

Rajiv Mordani wrote:

> I just looked at the hudson job that creates and pushes the javadocs
> and looks like the checkout of the bean-validation api failed -
>
> bean-validator.checkout:
> [echo] checkout Bean validation from
> "https://glassfish-svn.dev.java.net/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1".
>
> [exec] Authentication realm:
> <https://glassfish-svn.dev.java.net:443> CollabNet Subversion Repository
> [exec] svn: PROPFIND request failed on
> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src'
>
> [exec] svn: PROPFIND of
> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src':
> authorization failed (https://glassfish-svn.dev.java.net)
> [exec] Result: 1
>
>
> Fixing it now.
>
> - Rajiv
>
> Ludovic Champenois wrote:
>> Kim Haase wrote:
>>> Hi,
>>>
>>> I noticed today that the API docs at
>>> http://javadoc.glassfish.org/javaee6/apidoc/ don't include the Bean
>>> Validation API docs, in the package javax.validation. Since the API
>>> is part of the EE 6 platform, shouldn't they be there?
>>>
>>> They are available on the final release download page at
>>> http://jcp.org/en/jsr/summary?id=303.
>>>
>>> Kim
>>
>> Good catch...It was there in a previous javadoc push (11/24th)
>> reviewed by the validation spec lead himself, so not sure why it is
>> gone now.
>>
>> Ludo
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: javadocs for glassfish and related modules.

2009-12-03T15:00:28Z

I noticed that the javadocs for jstl api (package
javax.servlet.jsp.jstl.*) is also missing.

On 12/03/09 14:55, Rajiv Mordani wrote:

> I just looked at the hudson job that creates and pushes the javadocs and
> looks like the checkout of the bean-validation api failed -
>
> bean-validator.checkout:
> [echo] checkout Bean validation from
> "https://glassfish-svn.dev.java.net/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1".
>
> [exec] Authentication realm:
> <https://glassfish-svn.dev.java.net:443> CollabNet Subversion Repository
> [exec] svn: PROPFIND request failed on
> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src'
>
> [exec] svn: PROPFIND of
> '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src':
> authorization failed (https://glassfish-svn.dev.java.net)
> [exec] Result: 1
>
>
> Fixing it now.
>
> - Rajiv
>
> Ludovic Champenois wrote:
>> Kim Haase wrote:
>>> Hi,
>>>
>>> I noticed today that the API docs at
>>> http://javadoc.glassfish.org/javaee6/apidoc/ don't include the Bean
>>> Validation API docs, in the package javax.validation. Since the API
>>> is part of the EE 6 platform, shouldn't they be there?
>>>
>>> They are available on the final release download page at
>>> http://jcp.org/en/jsr/summary?id=303.
>>>
>>> Kim
>>
>> Good catch...It was there in a previous javadoc push (11/24th)
>> reviewed by the validation spec lead himself, so not sure why it is
>> gone now.
>>
>> Ludo
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: javadocs for glassfish and related modules.

2009-12-03T14:55:49Z

I just looked at the hudson job that creates and pushes the javadocs and
looks like the checkout of the bean-validation api failed -

bean-validator.checkout:
[echo] checkout Bean validation from "https://glassfish-svn.dev.java.net/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1".
[exec] Authentication realm: <https://glassfish-svn.dev.java.net:443> CollabNet Subversion Repository
[exec] svn: PROPFIND request failed on '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src'
[exec] svn: PROPFIND of '/svn/glassfish-svn/tags/20091014-bean-validator-jsr-303-v4_0_1/api/checkout-source/src': authorization failed (https://glassfish-svn.dev.java.net)
[exec] Result: 1

Fixing it now.

- Rajiv

Ludovic Champenois wrote:

> Kim Haase wrote:
>> Hi,
>>
>> I noticed today that the API docs at
>> http://javadoc.glassfish.org/javaee6/apidoc/ don't include the Bean
>> Validation API docs, in the package javax.validation. Since the API
>> is part of the EE 6 platform, shouldn't they be there?
>>
>> They are available on the final release download page at
>> http://jcp.org/en/jsr/summary?id=303.
>>
>> Kim
>
> Good catch...It was there in a previous javadoc push (11/24th)
> reviewed by the validation spec lead himself, so not sure why it is
> gone now.
>
> Ludo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: Dev Guide JDBC Questions

2009-12-03T14:34:47Z

Thanks, Anissa! In that case, I'll use all lower case, because it's
more consistent with other property names.

June

On 12/ 3/09 02:25 PM, Anissa Lam wrote:

>
>
> June.Parks@... wrote:
>> Hi Shalini,
>>
>> Great review. I have a couple of questions, see below.
>>
>> On 11/27/09 03:02 AM, Shalini Muthukrishnan wrote:
>>> - Page 240, Making JDBC Driver Jars available : Please add
>>> glassfish_home/lib directory to the list.
>> How would this differ from adding the driver JARs to
>> <domain-dir>/lib? Why would a user want to put them in
>> <install-dir>/lib instead?
>>> - Page 247, section Handling Invalid Connections : the examples for
>>> asadmin set on the property should be changed to :
>>> asadmin set
>>> server.resources.jdbc-connection-pool.JCPool1.property.Prefer-Validate-Over-Recreate="true"
>>>
>> Jagadish says the property name is all caps,
>> PREFER-VALIDATE-OVER-RECREATE. Please confirm the spelling.
>> Unfortunately, because this is a property and not an attribute, I
>> can't extract it from the configuration myself.
> I just looked at the code. The pool property name is converted to
> all upper case first before looking at. So, capitalization doesn't
> matter.
>
> Anissa.
>>
>> June
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: Dev Guide JDBC Questions

2009-12-03T14:25:43Z

June.Parks@... wrote:

> Hi Shalini,
>
> Great review. I have a couple of questions, see below.
>
> On 11/27/09 03:02 AM, Shalini Muthukrishnan wrote:
>> - Page 240, Making JDBC Driver Jars available : Please add
>> glassfish_home/lib directory to the list.
> How would this differ from adding the driver JARs to
> <domain-dir>/lib? Why would a user want to put them in
> <install-dir>/lib instead?
>> - Page 247, section Handling Invalid Connections : the examples for
>> asadmin set on the property should be changed to :
>> asadmin set
>> server.resources.jdbc-connection-pool.JCPool1.property.Prefer-Validate-Over-Recreate="true"
>>
> Jagadish says the property name is all caps,
> PREFER-VALIDATE-OVER-RECREATE. Please confirm the spelling.
> Unfortunately, because this is a property and not an attribute, I
> can't extract it from the configuration myself.

I just looked at the code. The pool property name is converted to all
upper case first before looking at. So, capitalization doesn't matter.

Anissa.
>
> June
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: javadocs for glassfish and related modules.

2009-12-03T14:05:59Z

Kim Haase wrote:

> Hi,
>
> I noticed today that the API docs at
> http://javadoc.glassfish.org/javaee6/apidoc/ don't include the Bean
> Validation API docs, in the package javax.validation. Since the API is
> part of the EE 6 platform, shouldn't they be there?
>
> They are available on the final release download page at
> http://jcp.org/en/jsr/summary?id=303.
>
> Kim

Good catch...It was there in a previous javadoc push (11/24th) reviewed
by the validation spec lead himself, so not sure why it is gone now.

Ludo

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: javadocs for glassfish and related modules.

2009-12-03T13:57:02Z

Hi,

I noticed today that the API docs at
http://javadoc.glassfish.org/javaee6/apidoc/ don't include the Bean
Validation API docs, in the package javax.validation. Since the API is
part of the EE 6 platform, shouldn't they be there?

They are available on the final release download page at
http://jcp.org/en/jsr/summary?id=303.

Kim

On 11/24/09 01:26, Rajiv Mordani wrote:

> I have a first stab at the javadocs and they are published at
>
> http://javadoc.glassfish.org/v3/apidoc/
>
> Alexis I will include the packages you list below. I am debugging an
> issue about ClassCastException while generating javadocs for certain
> packages.
>
> - Rajiv
>
> Alexis Moussine-Pouchkine wrote:
>> It would certainly be nice for people looking into GlassFish embedded
>> to have public JavaDoc's to
>> org.glassfish.api.embedded.* and org.glassfish.api.deployment.* for
>> instance.
>> -Alexis
>>
>> On Nov 21, 2009, at 9:37, Rajiv Mordani wrote:
>>
>>> All,
>>> During Java EE 5 / v2 days javadocs for GlassFish were published at -
>>>
>>> https://glassfish.dev.java.net/nonav/javaee5/api/index.html
>>>
>>> Question - should we be publishing the APIs for the various com.sun.*
>>> packages that are listed here? I know that we have some new packages
>>> that we should include - like hk2 but I would like for everyone to
>>> review the javadocs for the com.sun.* packages and let me know if we
>>> should indeed generate the javadocs for them and publish them for
>>> developers. If it does not make sense for the developer, or is not a
>>> committed API that a developer can use, then IMHO we should not publish
>>> the javadocs for the same. Please let me know if in addition to these,
>>> if we should generate and publish the javadocs for other packages in v3,
>>> including modules like metro.
>>>
>>> Thanks
>>>
>>> - Rajiv
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>> For additional commands, e-mail: dev-help@...
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: Dev Guide JDBC Questions

2009-12-03T12:48:20Z

Hi Shalini,

Great review. I have a couple of questions, see below.

On 11/27/09 03:02 AM, Shalini Muthukrishnan wrote:
> - Page 240, Making JDBC Driver Jars available : Please add
> glassfish_home/lib directory to the list.
How would this differ from adding the driver JARs to <domain-dir>/lib?
Why would a user want to put them in <install-dir>/lib instead?
> - Page 247, section Handling Invalid Connections : the examples for
> asadmin set on the property should be changed to :
> asadmin set
> server.resources.jdbc-connection-pool.JCPool1.property.Prefer-Validate-Over-Recreate="true"
>
Jagadish says the property name is all caps,
PREFER-VALIDATE-OVER-RECREATE. Please confirm the spelling.
Unfortunately, because this is a property and not an attribute, I can't
extract it from the configuration myself.

June

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: 3rd party source build with dependencies

2009-12-03T10:35:46Z

Re: Sending JMS messages between systems doesn't work any more

2009-12-03T10:04:10Z

Many thanks, Nigel. It looks as if the problem is with GlassFish, not MQ
-- see below.

On 12/03/09 12:05, Nigel Deakin wrote:

> Kim,
>
> Kim Haase wrote:
>> On 12/03/09 06:20, Nigel Deakin wrote:
>>> Kim,
>>>
>>> Kim Haase wrote:
>>>> JMS applications that send messages from one system to another
>>>> stopped working for me in b73 and also fail in b74. They worked in
>>>> earlier builds -- I think I last tested them around b69.
>>>>
>>>> Several examples in the Java EE Tutorial are based on sending JMS
>>>> messages between systems, so this is an issue for docs.
>>>>
>>>> For a number of releases, the way to enable the sending of messages
>>>> to a remote system has been to create a JMS connection factory
>>>> resource whose AddressList property is set to the name of the remote
>>>> system. (The connector connection pool, therefore, has its
>>>> AddressList property set to this value.)
>>>>
>>>> Now, when I try to send messages to the remote system, I get the
>>>> following error over and over:
>>>>
>>>> WARNING: [C4003]: Error occurred on connection creation
>>>> [jdench:7676]. - cause: java.net.ConnectException: Connection
>>>> refused: connect
>>>> Dec 2, 2009 11:31:55 AM
>>>> com.sun.messaging.jmq.jmsclient.ExceptionHandler
>>>> throwConnectionException
>>>
>>> This means it is trying to connect to a MQ broker running on machine
>>> jdench on port 7676, and it is getting no response, perhaps because
>>> the broker isn't running or it is using a different port.
>>>
>>> Can you connect to it using other tools on your windows machine, such
>>> as imqcmd (which is in the mq/bin directory of a Glassfish V3
>>> installation)?
>>>
>>> For example this command lists the destinations on the broker:
>>> imqcmd list dst -b jdench:7676
>>> (it will prompt for user and password: typically admin/admin)
>>
>> Thanks, Nigel. The broker is running on jdench at port 7676 -- these
>> are the server log messages on jdench, which look the way they always do:
>>
>> [#|2009-12-03T11:12:59.008-0500|INFO|glassfishv3.0|javax.enterprise.system.core.transaction.com.sun.jts.CosTransactions|_ThreadID=17;_ThreadName=Thread-1;|JTS5014:
>> Recoverable JTS instance, serverId = [3700]|#]
>>
>> [#|2009-12-03T11:13:03.745-0500|INFO|glassfishv3.0|com.sun.enterprise.connectors.jms.system.ActiveJmsResourceAdapter|_ThreadID=32;_ThreadName=Thread-1;|JMS
>> Service Connection URL is :mq://localhost:7676/|#]
>>
>> [#|2009-12-03T11:13:03.878-0500|INFO|glassfishv3.0|org.hibernate.validator.engine.resolver.DefaultTraversableResolver|_ThreadID=32;_ThreadName=Thread-1;|Instantiated
>> an instance of
>> org.hibernate.validator.engine.resolver.JPATraversableResolver.|#]
>>
>> [#|2009-12-03T11:13:04.170-0500|INFO|glassfishv3.0|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=32;_ThreadName=Thread-1;|MQJMSRA_RA1101:
>> SJSMQ JMS Resource Adapter starting: DIRECT|#]
>>
>> [#|2009-12-03T11:13:14.151-0500|INFO|glassfishv3.0|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=32;_ThreadName=Thread-1;|MQJMSRA_RA1101:
>> SJSMQ JMSRA Started:DIRECT|#]
>>
>> [#|2009-12-03T11:13:20.619-0500|INFO|glassfishv3.0|javax.resourceadapter.mqjmsra.outbound.connection|_ThreadID=30;_ThreadName=Thread-1;|MQJMSRA_MF1101:
>> setAddressList:NOT setting default value=localhost|#]
>>
>> [#|2009-12-03T11:13:20.633-0500|INFO|glassfishv3.0|javax.resourceadapter.mqjmsra.outbound.connection|_ThreadID=30;_ThreadName=Thread-1;|MQJMSRA_MF1101:
>> setPassword:NOT setting default value|#]
>>
>> [#|2009-12-03T11:13:20.634-0500|INFO|glassfishv3.0|javax.resourceadapter.mqjmsra.outbound.connection|_ThreadID=30;_ThreadName=Thread-1;|MQJMSRA_MF1101:
>> setUserName:NOT setting default value=guest|#]
>
> Yes, this suggests the embedded broker has started. You could also look
> at the broker log in domains\domain1\imq\instances\imqbroker\log\log.txt
> (or similar) to confirm this.
>
>>
>> I ran the imqcmd on jdench and after some experimentation I found that
>> the correct username and password were admin/admin.
>
> I did mention the default username and password in my previous email :-)

Sorry to have spaced out!

>
>>
>> jdench 52 =>imqcmd list dst
>> Username: admin
>> Password:
>> Listing all the destinations on the broker specified by:
>>
>> -------------------------
>> Host Primary Port
>> -------------------------
>> localhost 7676
>>
>> ---------------------------------------------------------------------------
>>
>> Name Type State Producers Consumers Msgs
>> Total Count UnAck Avg
>> Size
>> ---------------------------------------------------------------------------
>>
>> PhysicalQueue Queue RUNNING 0 1 0 0 0.0
>> mq.sys.dmq Queue RUNNING 0 0 0 0 0.0
>>
>> Successfully listed destinations.
>
> Yes, so the broker is definitely working.
>
>>
>> jdench 53 =>pwd
>> /home/chaase/glassfish-v3-b74/mq/bin
>>
>> However, the imqcmd on the Windows system fails:
>>
>> C:\Program Files\glassfish-v3-b74\mq\bin>imqcmd list dst -b jdench:7676
>> Username: admin
>> Password: admin
>> Listing all the destinations on the broker specified by:
>>
>> ----------------------
>> Host Primary Port
>> ----------------------
>> jdench 7676
>>
>> Dec 3, 2009 11:19:40 AM
>> com.sun.messaging.jmq.jmsclient.ExceptionHandler throwConnectionException
>> WARNING: [C4003]: Error occurred on connection creation [jdench:7676].
>> - cause:
>> java.net.ConnectException: Connection refused: connect
>> Error while connecting to the broker on host 'jdench' and port '7676'.
>> com.sun.messaging.jms.JMSException: [C4003]: Error occurred on
>> connection creation [jdench:7676]. - cause: java.net.ConnectException:
>> Connection refused: connect
>> Please verify that there is a broker running on the specified host and
>> port or use the '-b' option to specify the correct broker host and port.
>>
>> Listing destinations failed.
>
> This eliminates your client code as the cause of the problem. It has
> found the host but received no reply on the port.
>
>>
>> I notice that on Windows the password shows up in clear text, whereas
>> on Solaris it doesn't appear. Hard to believe that makes a difference,
>> though.
>>
>> And I can still ping jdench, save files to it, etc. from my Windows
>> system.
>
> This is sounding like a network issue. Do you have a hardware or
> software firewall?

Not that I know of.

>
> You could try shutting down the Glassfish instance and instead starting
> a standalone MQ broker by running the imqbrokerd command directly, and
> seeing if you can "imqcmd list dst" it from the PC.

Without GlassFish, it works! I started the broker on jdench, and it runs
fine (had to specify -javahome to keep it from picking up some jdk 5
somewhere):

jdench 59 =>./imqbrokerd -javahome /home/chaase/jdk1.6.0_17
[03/Dec/2009:12:59:11 EST]
================================================================================
Open Message Queue 4.4
Sun Microsystems, Inc.
Version: 4.4 Update 1 (Build 7-b)
Compile: Wed Nov 18 23:21:05 PST 2009

Copyright (c) 2009 Sun Microsystems, Inc. All rights reserved. Use is
subject to license terms.
================================================================================
Java Runtime: 1.6.0_17 Sun Microsystems Inc. /home/chaase/jdk1.6.0_17/jre
[03/Dec/2009:12:59:12 EST] IMQ_HOME=/home/chaase/glassfish-v3-b74/mq
[03/Dec/2009:12:59:12 EST]
IMQ_VARHOME=/home/chaase/glassfish-v3-b74/glassfish/domains/domain1/imq
[03/Dec/2009:12:59:12 EST] SunOS 5.10 sparc jdench (1 cpu) chaase
[03/Dec/2009:12:59:12 EST] Max file descriptors: 65536 (65536)
[03/Dec/2009:12:59:12 EST] Java Heap Size: max=190080k, current=190080k
[03/Dec/2009:12:59:12 EST] Arguments: -javahome /home/chaase/jdk1.6.0_17
[03/Dec/2009:12:59:12 EST] [B1060]: Loading persistent data...
[03/Dec/2009:12:59:12 EST] Using built-in file-based persistent store:
/home/chaase/glassfish-v3-b74/glassfish/domains/domain1/imq/instances/imqbroker/
[03/Dec/2009:12:59:13 EST] [B1039]: Broker "imqbroker@jdench:7676" ready.

And I did an imqcmd list dst and got the system queue, as expected.

Then on Windows, imqcmd is able to list the destinations for the jdench
broker too:

C:\Program Files\glassfish-v3-b74\mq\bin>imqcmd list dst -b jdench:7676
Username: admin
Password: admin
Listing all the destinations on the broker specified by:

----------------------
Host Primary Port
----------------------
jdench 7676

--------------------------------------------------------------------------------------------
Name Type State Producers Consumers
Msgs

Total Wildcard Total Wildcard Count
Remote UnAck Avg Size
--------------------------------------------------------------------------------------------
mq.sys.dmq Queue RUNNING 0 - 0 - 0 0
0 0.0

Successfully listed destinations.

So it's not MQ that's causing the problem but GlassFish apparently. What
now, I wonder?

Thanks again!!

Kim

>
> Nigel
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: Sending JMS messages between systems doesn't work any more

2009-12-03T09:05:04Z

Kim,

Kim Haase wrote:

> On 12/03/09 06:20, Nigel Deakin wrote:
>> Kim,
>>
>> Kim Haase wrote:
>>> JMS applications that send messages from one system to another
>>> stopped working for me in b73 and also fail in b74. They worked in
>>> earlier builds -- I think I last tested them around b69.
>>>
>>> Several examples in the Java EE Tutorial are based on sending JMS
>>> messages between systems, so this is an issue for docs.
>>>
>>> For a number of releases, the way to enable the sending of messages
>>> to a remote system has been to create a JMS connection factory
>>> resource whose AddressList property is set to the name of the remote
>>> system. (The connector connection pool, therefore, has its
>>> AddressList property set to this value.)
>>>
>>> Now, when I try to send messages to the remote system, I get the
>>> following error over and over:
>>>
>>> WARNING: [C4003]: Error occurred on connection creation
>>> [jdench:7676]. - cause: java.net.ConnectException: Connection
>>> refused: connect
>>> Dec 2, 2009 11:31:55 AM
>>> com.sun.messaging.jmq.jmsclient.ExceptionHandler
>>> throwConnectionException
>>
>> This means it is trying to connect to a MQ broker running on machine
>> jdench on port 7676, and it is getting no response, perhaps because
>> the broker isn't running or it is using a different port.
>>
>> Can you connect to it using other tools on your windows machine, such
>> as imqcmd (which is in the mq/bin directory of a Glassfish V3
>> installation)?
>>
>> For example this command lists the destinations on the broker:
>> imqcmd list dst -b jdench:7676
>> (it will prompt for user and password: typically admin/admin)
>
> Thanks, Nigel. The broker is running on jdench at port 7676 -- these are
> the server log messages on jdench, which look the way they always do:
>
> [#|2009-12-03T11:12:59.008-0500|INFO|glassfishv3.0|javax.enterprise.system.core.transaction.com.sun.jts.CosTransactions|_ThreadID=17;_ThreadName=Thread-1;|JTS5014:
> Recoverable JTS instance, serverId = [3700]|#]
>
> [#|2009-12-03T11:13:03.745-0500|INFO|glassfishv3.0|com.sun.enterprise.connectors.jms.system.ActiveJmsResourceAdapter|_ThreadID=32;_ThreadName=Thread-1;|JMS
> Service Connection URL is :mq://localhost:7676/|#]
>
> [#|2009-12-03T11:13:03.878-0500|INFO|glassfishv3.0|org.hibernate.validator.engine.resolver.DefaultTraversableResolver|_ThreadID=32;_ThreadName=Thread-1;|Instantiated
> an instance of
> org.hibernate.validator.engine.resolver.JPATraversableResolver.|#]
>
> [#|2009-12-03T11:13:04.170-0500|INFO|glassfishv3.0|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=32;_ThreadName=Thread-1;|MQJMSRA_RA1101:
> SJSMQ JMS Resource Adapter starting: DIRECT|#]
>
> [#|2009-12-03T11:13:14.151-0500|INFO|glassfishv3.0|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=32;_ThreadName=Thread-1;|MQJMSRA_RA1101:
> SJSMQ JMSRA Started:DIRECT|#]
>
> [#|2009-12-03T11:13:20.619-0500|INFO|glassfishv3.0|javax.resourceadapter.mqjmsra.outbound.connection|_ThreadID=30;_ThreadName=Thread-1;|MQJMSRA_MF1101:
> setAddressList:NOT setting default value=localhost|#]
>
> [#|2009-12-03T11:13:20.633-0500|INFO|glassfishv3.0|javax.resourceadapter.mqjmsra.outbound.connection|_ThreadID=30;_ThreadName=Thread-1;|MQJMSRA_MF1101:
> setPassword:NOT setting default value|#]
>
> [#|2009-12-03T11:13:20.634-0500|INFO|glassfishv3.0|javax.resourceadapter.mqjmsra.outbound.connection|_ThreadID=30;_ThreadName=Thread-1;|MQJMSRA_MF1101:
> setUserName:NOT setting default value=guest|#]

Yes, this suggests the embedded broker has started. You could also look at the broker log in
domains\domain1\imq\instances\imqbroker\log\log.txt (or similar) to confirm this.

>
> I ran the imqcmd on jdench and after some experimentation I found that
> the correct username and password were admin/admin.

I did mention the default username and password in my previous email :-)

>
> jdench 52 =>imqcmd list dst
> Username: admin
> Password:
> Listing all the destinations on the broker specified by:
>
> -------------------------
> Host Primary Port
> -------------------------
> localhost 7676
>
> ---------------------------------------------------------------------------
> Name Type State Producers Consumers Msgs
> Total Count UnAck Avg Size
> ---------------------------------------------------------------------------
> PhysicalQueue Queue RUNNING 0 1 0 0 0.0
> mq.sys.dmq Queue RUNNING 0 0 0 0 0.0
>
> Successfully listed destinations.

Yes, so the broker is definitely working.

>
> jdench 53 =>pwd
> /home/chaase/glassfish-v3-b74/mq/bin
>
> However, the imqcmd on the Windows system fails:
>
> C:\Program Files\glassfish-v3-b74\mq\bin>imqcmd list dst -b jdench:7676
> Username: admin
> Password: admin
> Listing all the destinations on the broker specified by:
>
> ----------------------
> Host Primary Port
> ----------------------
> jdench 7676
>
> Dec 3, 2009 11:19:40 AM com.sun.messaging.jmq.jmsclient.ExceptionHandler
> throwConnectionException
> WARNING: [C4003]: Error occurred on connection creation [jdench:7676]. -
> cause:
> java.net.ConnectException: Connection refused: connect
> Error while connecting to the broker on host 'jdench' and port '7676'.
> com.sun.messaging.jms.JMSException: [C4003]: Error occurred on
> connection creation [jdench:7676]. - cause: java.net.ConnectException:
> Connection refused: connect
> Please verify that there is a broker running on the specified host and
> port or use the '-b' option to specify the correct broker host and port.
>
> Listing destinations failed.

This eliminates your client code as the cause of the problem. It has found the host but received no reply on the port.

>
> I notice that on Windows the password shows up in clear text, whereas on
> Solaris it doesn't appear. Hard to believe that makes a difference, though.
>
> And I can still ping jdench, save files to it, etc. from my Windows system.

This is sounding like a network issue. Do you have a hardware or software firewall?

You could try shutting down the Glassfish instance and instead starting a standalone MQ broker by running the imqbrokerd
command directly, and seeing if you can "imqcmd list dst" it from the PC.

Nigel

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: Sending JMS messages between systems doesn't work any more

2009-12-03T08:38:24Z

On 12/03/09 06:20, Nigel Deakin wrote:

> Kim,
>
> Kim Haase wrote:
>> JMS applications that send messages from one system to another stopped
>> working for me in b73 and also fail in b74. They worked in earlier
>> builds -- I think I last tested them around b69.
>>
>> Several examples in the Java EE Tutorial are based on sending JMS
>> messages between systems, so this is an issue for docs.
>>
>> For a number of releases, the way to enable the sending of messages to
>> a remote system has been to create a JMS connection factory resource
>> whose AddressList property is set to the name of the remote system.
>> (The connector connection pool, therefore, has its AddressList
>> property set to this value.)
>>
>> Now, when I try to send messages to the remote system, I get the
>> following error over and over:
>>
>> WARNING: [C4003]: Error occurred on connection creation [jdench:7676].
>> - cause: java.net.ConnectException: Connection refused: connect
>> Dec 2, 2009 11:31:55 AM
>> com.sun.messaging.jmq.jmsclient.ExceptionHandler throwConnectionException
>
> This means it is trying to connect to a MQ broker running on machine
> jdench on port 7676, and it is getting no response, perhaps because the
> broker isn't running or it is using a different port.
>
> Can you connect to it using other tools on your windows machine, such as
> imqcmd (which is in the mq/bin directory of a Glassfish V3 installation)?
>
> For example this command lists the destinations on the broker:
> imqcmd list dst -b jdench:7676
> (it will prompt for user and password: typically admin/admin)

Thanks, Nigel. The broker is running on jdench at port 7676 -- these are
the server log messages on jdench, which look the way they always do:

[#|2009-12-03T11:12:59.008-0500|INFO|glassfishv3.0|javax.enterprise.system.core.transaction.com.sun.jts.CosTransactions|_ThreadID=17;_ThreadName=Thread-1;|JTS5014:
Recoverable JTS instance, serverId = [3700]|#]

[#|2009-12-03T11:13:03.745-0500|INFO|glassfishv3.0|com.sun.enterprise.connectors.jms.system.ActiveJmsResourceAdapter|_ThreadID=32;_ThreadName=Thread-1;|JMS
Service Connection URL is :mq://localhost:7676/|#]

[#|2009-12-03T11:13:03.878-0500|INFO|glassfishv3.0|org.hibernate.validator.engine.resolver.DefaultTraversableResolver|_ThreadID=32;_ThreadName=Thread-1;|Instantiated
an instance of
org.hibernate.validator.engine.resolver.JPATraversableResolver.|#]

[#|2009-12-03T11:13:04.170-0500|INFO|glassfishv3.0|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=32;_ThreadName=Thread-1;|MQJMSRA_RA1101:
SJSMQ JMS Resource Adapter starting: DIRECT|#]

[#|2009-12-03T11:13:14.151-0500|INFO|glassfishv3.0|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=32;_ThreadName=Thread-1;|MQJMSRA_RA1101:
SJSMQ JMSRA Started:DIRECT|#]

[#|2009-12-03T11:13:20.619-0500|INFO|glassfishv3.0|javax.resourceadapter.mqjmsra.outbound.connection|_ThreadID=30;_ThreadName=Thread-1;|MQJMSRA_MF1101:
setAddressList:NOT setting default value=localhost|#]

[#|2009-12-03T11:13:20.633-0500|INFO|glassfishv3.0|javax.resourceadapter.mqjmsra.outbound.connection|_ThreadID=30;_ThreadName=Thread-1;|MQJMSRA_MF1101:
setPassword:NOT setting default value|#]

[#|2009-12-03T11:13:20.634-0500|INFO|glassfishv3.0|javax.resourceadapter.mqjmsra.outbound.connection|_ThreadID=30;_ThreadName=Thread-1;|MQJMSRA_MF1101:
setUserName:NOT setting default value=guest|#]

I ran the imqcmd on jdench and after some experimentation I found that
the correct username and password were admin/admin.

jdench 52 =>imqcmd list dst
Username: admin
Password:
Listing all the destinations on the broker specified by:

-------------------------
Host Primary Port
-------------------------
localhost 7676

---------------------------------------------------------------------------
Name Type State Producers Consumers Msgs

Total Count UnAck Avg Size
---------------------------------------------------------------------------
PhysicalQueue Queue RUNNING 0 1 0 0 0.0
mq.sys.dmq Queue RUNNING 0 0 0 0 0.0

Successfully listed destinations.

jdench 53 =>pwd
/home/chaase/glassfish-v3-b74/mq/bin

However, the imqcmd on the Windows system fails:

C:\Program Files\glassfish-v3-b74\mq\bin>imqcmd list dst -b jdench:7676
Username: admin
Password: admin
Listing all the destinations on the broker specified by:

----------------------
Host Primary Port
----------------------
jdench 7676

Dec 3, 2009 11:19:40 AM com.sun.messaging.jmq.jmsclient.ExceptionHandler
throwConnectionException
WARNING: [C4003]: Error occurred on connection creation [jdench:7676]. -
cause:
java.net.ConnectException: Connection refused: connect
Error while connecting to the broker on host 'jdench' and port '7676'.
com.sun.messaging.jms.JMSException: [C4003]: Error occurred on
connection creation [jdench:7676]. - cause: java.net.ConnectException:
Connection refused: connect
Please verify that there is a broker running on the specified host and
port or use the '-b' option to specify the correct broker host and port.

Listing destinations failed.

I notice that on Windows the password shows up in clear text, whereas on
Solaris it doesn't appear. Hard to believe that makes a difference, though.

And I can still ping jdench, save files to it, etc. from my Windows system.

Kim

>
> Nigel
>
>>
>> The JMS service is running on jdench.
>>
>> This probably has nothing to do with it, but I also notice that when
>> JMS started up on the system named jdench, it reported that its
>> connection URL had the :mq: prefix:
>>
>> [#|2009-12-02T11:27:54.660-0500|INFO|glassfishv3.0|com.sun.enterprise.connectors.jms.system.ActiveJmsResourceAdapter|_ThreadID=28;_ThreadName=p:
>> thread-pool-1; w: 5;|JMS Service Connection URL is
>> :mq://localhost:7676/|#]
>
> When the MQ broker (the JMS service) starts, you will see this message:
>
> MQJMSRA_RA1101: SJSMQ JMS Resource Adapter starting: DIRECT (or LOCAL).
>
> Note that in Glassfish 3 the broker isn't started when the Glassfish
> server starts, but is started lazily, so you may not see this message
> until when the first client (either your own app or imqcmd) tries to
> connect to it.
>
>>
>> Or do I have to do something explicit now to allow other systems to
>> connect to the JMS running on GlassFish?
>>
>
> No...
>
> Nigel
>
>> I'm running the client on my Windows XP system, and the remote system
>> (jdench) is my Solaris 10 system. I can ping jdench from the Windows
>> system just fine. The problem happens whether I run the client from
>> NetBeans or from the command line.
>>
>> Thanks,
>> Kim Haase
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: 3rd party source build with dependencies

2009-12-03T07:54:13Z

On Dec 3, 2009, at 7:40 AM, Jane Young wrote:
> Have you tried the native build? Not sure if it's doable. At least
> there are links to download the tools. Looks like there are some
> manual steps like modifying the Makefile for mozilla and gecko
> environments. Can this be automated?
>
> Why do you need the Hudson job to debug? Can this be done on your
> local system?

There is no native build on mac, which is what I have. I have remote
access to an old (5.8?) solaris machine, but immediately ran into
troubles with make and couldn't find any answers. Side note:
apparently javahelp and jdic are no longer supported and we should not
use javahelp going forward unless someone wants to put me in charge of
it and give me time to fix it.

Rather than spend a week trying to figure out that one system and then
repeating the whole ordeal on the hudson machine with a different
configuration, I'd rather just do it once on the one server that *has*
to work. For the manual steps, I guess I can just store the modified
files in the source-build workspace and copy them into the jdic
download before building.

If we don't build jdic from source, javahelp will still build by
downloading the zip file it needs (this is what's happening now).
Technically, it downloads the windows version of the zip so, unless
the build machine is windows, we can't actually recreate exactly what
we're using now.

Here's the diff to start building jdic (and once it builds I'd need to
change the build file to actually use the jdic output):

hostname% svn diff javahelp.xml
Index: javahelp.xml
===================================================================
--- javahelp.xml (revision 34876)
+++ javahelp.xml (working copy)
@@ -57,7 +57,9 @@

<target name="jdic.build" depends="jdic.checkout">
<echo message="Attempting to build jdic. Keep your fingers
crossed." />
-
+ <ant antfile="${external.dir}/jdic/src/build.xml"
+ target="buildall"
+ inheritall="false"/>
</target>

<target name="jdic.checkout" depends="init">

We can always just give it a shot, right?

Thanks,
Bobby

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: 3rd party source build with dependencies

2009-12-03T04:40:51Z

>
> Nope, no way to avoid it. I don't know any way to handle this except
> to commit my changes and then debug the continuous build server as
> errors pop up. Is that ok with you? The requirements are here:
>
> https://jdic.dev.java.net/documentation/README.html#Build%20the%20Source
>
> Let me know when you've had a chance to look to see if that's doable.
> Even if it all builds correctly, the javahelp build won't work because
> I don't know what the jdic output is in order to use it to build
> javahelp.

Have you tried the native build? Not sure if it's doable. At least
there are links to download the tools. Looks like there are some manual
steps like modifying the Makefile for mozilla and gecko environments.
Can this be automated?

Why do you need the Hudson job to debug? Can this be done on your local
system?

Thanks,
Jane

> So my initial commit will have a few things commented out and I'll
> have to look at what's produced in the hudson server.
>
> Thanks,
> Bobby
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...